Bootloop/Blank screen Problem. Need help.

[Guest bob3450]

Hello all. I have a slight problem;

 

Right, here's the deal.

 

I have a rooted OSD running the Xolo ICS rom with the 58mb patched update. I also remapped the camera button to a power button, although this shouldn't make a difference.

 

I was trying to install Google Now onto my San Diego (See here). Despite not having a custom recovery I tried it anyway.

I got to the point of downloading a flashable zip (the M7 Offline), extracting it and manually copying and changing permissions of the various files/directories in /system/ . This included /system/app/ (GoogleTTS.apk and Velvet.apk), /system/lib/ and /system/usr/srec/ [see attached screenshot].

All went OK until I rebooted, where the phone showed the Xolo boot logo as usual, and then bootloop.

Now, it doesn't get as far as the 'Intel Inside' animation. After the Xolo logo, there is just a blank screen. After the first time you power on, it waits for ~18 seconds on the black screen (After Xolo logo) before rebooting. Then it reboots. This time, however, it hangs on the black screen, and doesn't reboot subsequently.

 

The problem is that it doesn't boot up enough for ADB to recognise it, so I can't push the /system/ directory. DDMS (in the Android SDK) lists it as 'Offline'.

 

I have tried to boot into recovery, but the screen doesn't work, and so I am not sure if I'm successful. Once I did, and the screen started flashing different colours, but I am not able to reproduce this.

 

Also, my HDMI out doesn't work. It hasn't for a while. It did work perfectly, but I have tested on multiple monitors/TVs, and it no longer does. It could be the HDMI to mini-HDMI adapter, but I haven't bought another one yet.

 

Any ideas/help as the making it work again would be much appreciated!

[Guest BlueMoonRising]

Get a new HDMI to mini-HDMI adapter first and pray it is the cable, I can't see any way of helping without a display.

Does Windows recognise the phone at any time when plugged in?

[Guest bob3450]

Haha ok, will do.

 

Yes, when I leave it plugged in and then turn the phone on, Windows makes the sound as if a device has been connected, but then it disconnects about a second later.

 

I also forgot to mention in the OP that when I plug it into the computer when it is off, as if to charge it, ADB recognises it but says its Offline (see attachment). When this happens, the screen flashes colours.

The screen also flashes colours when using a wall charger.

 

Also, could you upload your adb_usb.ini , as I have just reinstalled Windows and forgot to back mine up?

[Guest BlueMoonRising]

I'm at work at the moment, I'll have a look tomorrow.

[Guest BlueMoonRising]

After searching my entire C:\ drive I finally came to the conclusion that I don't have adb_usb.ini file because I don't have the Android SDK installed (at least I think that's the reason). <_<  Sorry, perhaps someone else can help you with that.

[Guest bob3450]

Cheers for looking, but I've think got it sorted. Just waiting for an HDMI cable now...

Edited February 24, 2014 by bob3450

[Guest Darael]

Can you access fastboot by powering it on with the vol- key held?  If all else fails you will then be able to use fastboot to flash the 299MiB update.zip.  Sure, you'll lose a whole lot of settings, but at least you'll have a working phone.

[Guest bob3450]

Can you access fastboot by powering it on with the vol- key held?  If all else fails you will then be able to use fastboot to flash the 299MiB update.zip.  Sure, you'll lose a whole lot of settings, but at least you'll have a working phone.

 

I don't think so... running 'fastboot devices' doesn't return anything..?

 

Or am I running the wrong commands? I remember Paul saying that we need to use a custom vendor ID, but that just returns an error for me...

[Guest Darael]

I don't think so... running 'fastboot devices' doesn't return anything..?

 

Or am I running the wrong commands? I remember Paul saying that we need to use a custom vendor ID, but that just returns an error for me...

 

Yeah, the vendor ID we need to use is 8087, which we pass with the '-i 0x8087' flag.  'fastboot devices' won't return anything unless the device is actually in the bootloader at the time (hence the mention of holding the vol- key when powering it on), and under Linux I've found that fastboot works most reliably across different distros if run as root.

[Guest BlueMoonRising]

Have a look at :-

 

http://www.modaco.com/topic/362139-any-ideas/?p=2116804 for the fastboot command. 

 

This may be useful when you've got an hdmi cable. :-

 

http://www.modaco.com/topic/362574-solved-problem-of-screen-flashing-different-colors-after-flashing-updatezip-after-installing-37mb-or-12mb-update-on-xolo-ics-rom/?p=2128134

[Guest bob3450]

Yeah, the vendor ID we need to use is 8087, which we pass with the '-i 0x8087' flag.  'fastboot devices' won't return anything unless the device is actually in the bootloader at the time (hence the mention of holding the vol- key when powering it on), and under Linux I've found that fastboot works most reliably across different distros if run as root.

 

Ahh right. I'll have a go on ubuntu now!

 

Have a look at :-

 

http://www.modaco.com/topic/362139-any-ideas/?p=2116804 for the fastboot command. 

 

This may be useful when you've got an hdmi cable. :-

 

http://www.modaco.com/topic/362574-solved-problem-of-screen-flashing-different-colors-after-flashing-updatezip-after-installing-37mb-or-12mb-update-on-xolo-ics-rom/?p=2128134

 

Cheers for the links! I will try the fastboot command now. The problem is that I think it boots into recovery/fastboot successfully the first time, but after 18-ish seconds it reboots on its own, and holding down vol- doesn't affect it...

 

Hopefully the HDMI cable will arrive tomorrow!

 

EDIT: Ok, ADB recognises the phone on the first power on holding down vol-. However, once the phone restarts, it isn't recognised.

 

Fastboot, on both startups, just waits for a device. Doesn't seem to be playing ball for me.

 

Also, I read somewhere that there was a bit of ADB code that 'froze' the phone in its current state incase of bootloops. Could this be useful?

Edited February 26, 2014 by bob3450

[Guest BlueMoonRising]

Ahh right. I'll have a go on ubuntu now!

 

 

Cheers for the links! I will try the fastboot command now. The problem is that I think it boots into recovery/fastboot successfully the first time, but after 18-ish seconds it reboots on its own, and holding down vol- doesn't affect it...

 

Hopefully the HDMI cable will arrive tomorrow!

 

EDIT: Ok, ADB recognises the phone on the first power on holding down vol-. However, once the phone restarts, it isn't recognised.

 

Fastboot, on both startups, just waits for a device. Doesn't seem to be playing ball for me.

 

Also, I read somewhere that there was a bit of ADB code that 'froze' the phone in its current state incase of bootloops. Could this be useful?

Don't know about 'freezing' the phone but the reason it's not recognised on a reboot is because you have to kill adb in task manager before it reboots.

[Guest Darael]

Don't know about 'freezing' the phone but the reason it's not recognised on a reboot is because you have to kill adb in task manager before it reboots.

Given the mention of using Ubuntu, I suggest running "adb kill-server" rather than trying to find a task manager.  Alternatively, "killall adb".

[Guest BlueMoonRising]

Given the mention of using Ubuntu, I suggest running "adb kill-server" rather than trying to find a task manager.  Alternatively, "killall adb".

That was a test, congratulations, you passed  ^_^

[Guest bob3450]

Don't know about 'freezing' the phone but the reason it's not recognised on a reboot is because you have to kill adb in task manager before it reboots.

 

Ahh forgot about that! 

 

On the first boot I held down vol- to go into recovery where ADB works. The I did 'adb reboot [recovery]' which works, but no matter how many times I do it one-after-the-other, the phone still reboots and then ADB doesn't work. Its very annoying...

 

Still can't get fastboot to work in recovery on windows or linux.. it just 'waits for device' until the phone reboots. Running 

fastboot -i 0x8087 devices

doesn't work. Am I still missing something?

[Guest bob3450]

Okay, so the HDMI cable was delivered, and the output still doesn't show, so it must be the hardware in the phone.

 

I have given up, and bought a moto g for £99 instead!

[Guest BlueMoonRising]

Okay, so the HDMI cable was delivered, and the output still doesn't show, so it must be the hardware in the phone.

 

I have given up, and bought a moto g for £99 instead!

Unlucky on the OSD.

 

£99 is a good price, is that the 8GB? Can I ask where from?

[Guest bob3450]

Unlucky on the OSD.

 

£99 is a good price, is that the 8GB? Can I ask where from?

 

I know, I guessed it might be futile.

 

Yes the 8GB version. I got mine from o2, but Vodafone are selling them at the same price. Tesco's is selling them for £110. They are all locked to the respective carrier, but an unlock code is only £2 on eBay, so it still works out cheaper!

Edited March 5, 2014 by bob3450

[Guest BlueMoonRising]

I know, I guessed it might be futile.

 

Yes the 8GB version. I got mine from o2, but Vodafone are selling them at the same price. Tesco's is selling them for £110. They are all locked to the respective carrier, but an unlock code is only £2 on eBay, so it still works out cheaper!

 

Cheers for that, the son is looking for a new phone so I'll pass it on.

Edited March 6, 2014 by BlueMoonRising

[Guest glossywhite]

Just bought me a Moto G 8Gb, it is sitting here looking very pretty :) what a gorgeous phone for the £99.99!

[Guest bob3450]

Just bought me a Moto G 8Gb, it is sitting here looking very pretty :) what a gorgeous phone for the £99.99!

 

Mine arrived today, and so far I am very pleased with it! I agree, it does look very nice!