• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.
Sign in to follow this  
Followers 0

Bootloop/Blank screen Problem. Need help.

21 posts in this topic

Posted

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!

post-982019-0-21508100-1393172755_thumb.

0

Share this post


Link to post
Share on other sites

Posted

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?

0

Share this post


Link to post
Share on other sites

Posted

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?

post-982019-0-46893600-1393174989_thumb.

0

Share this post


Link to post
Share on other sites

Posted

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

0

Share this post


Link to post
Share on other sites

Posted

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.

0

Share this post


Link to post
Share on other sites

Posted (edited)

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

Edited by bob3450
0

Share this post


Link to post
Share on other sites

Posted

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.

0

Share this post


Link to post
Share on other sites

Posted

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...

0

Share this post


Link to post
Share on other sites

Posted

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.

0

Share this post


Link to post
Share on other sites

Posted

Share this post


Link to post
Share on other sites

Posted (edited)

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!

 

 

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 by bob3450
0

Share this post


Link to post
Share on other sites

Posted

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.

0

Share this post


Link to post
Share on other sites

Posted

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".

0

Share this post


Link to post
Share on other sites

Posted

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  ^_^

0

Share this post


Link to post
Share on other sites

Posted

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?

0

Share this post


Link to post
Share on other sites

Posted

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!

0

Share this post


Link to post
Share on other sites

Posted

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?

0

Share this post


Link to post
Share on other sites

Posted (edited)

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 by bob3450
1

Share this post


Link to post
Share on other sites

Posted (edited)

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 by BlueMoonRising
0

Share this post


Link to post
Share on other sites

Posted

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

0

Share this post


Link to post
Share on other sites

Posted

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!

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.