Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much
Hello, I have the HTC tmobile mytouch 4g and it is acting up. Stock phone, no roms or rooted.
Three days ago, at night, doing some browsing and then everything froze, would not respond. I removed battery, and then it did a boot loop so i kept trying for a while, taking out battery, and turning on but still boot loop, so then left it alone.
The next morning i held the power and home button and it turned on and it worked normally for the whole day! until about the same time two days ago. Doing a little reading and browsing before bed (same website too, but i didn't download anything and the site works fine on a computer) and it froze. Did the same routine except it didnt work in the morning again. I removed sd and sim card too, left everything out for a long time, but whatever i tried it wouldn't work.
Yesterday i tried all day and then I read online I should do a wipe cache partition from the recovery menu. So i did that, but it was still a boot loop. After a few tries, it stopped turning on. Now the screen doesn't even turn on, but the phone vibrates 7 times when power is pressed, then will not respond at all unless i take battery out, then it will do the 7 vibrations and etc.
All htc said is to try a factory reset, but it wont even go to that menu. I can send it to them, but will probably lose everything on my phone ( like messages, contacts, and app data?) BUT I'm convinced there is another way, since it fixed itself the first time.
Just recently, now it has started blinking the charging light when charging (i charged it about 10 hours ago and it didn't blink)
I don't really know much about how these things work, but I have been reading some stuff about pd15??.jzip and putting it on the sd card (i have access to a micro sdcard reader) Also about a stock image or something. I don't know much so please give a simple-ish answer.
IF THE SOLUTION YOU WILL PROPOSE HAS A LOW SUCCESS RATE OR HAS A POSSIBILITY OF FURTHER DAMAGING THE PHONE, PLEASE LET ME KNOW... If it is too difficult/ too much work/ or dangerous, then I don't mind losing whatever i have on the phone
The PD15IMG.zip is the "stock image." It has to be installed in the bootloader, and you WILL lose all of your data. Usually you can get to the bootloader by holding volume down while booting. It will scan for the file there. Can you get into your bootloader?
sigh
cannot turn on no matter what i hold.
I think the blinking last night meant that it isn't charging the battery anymore. wont even vibrate now unless it is plugged in. its not an issue with the battery is it??
if this stock image is going to delete everything anyway, i might as well send it to htc. i just hoped i might be able to save my messages because i have some really hilarious ones, but oh well.
Can you please tell me exactly what ill lose? so,
bookmarks on the browsers
contacts and messages
all apps (they're on my phone) and app data? (like will i lose my progress in temple run 2, lol)
myTouch 4g HELP said:
cannot turn on no matter what i hold.
I think the blinking last night meant that it isn't charging the battery anymore. wont even vibrate now unless it is plugged in. its not an issue with the battery is it??
if this stock image is going to delete everything anyway, i might as well send it to htc. i just hoped i might be able to save my messages because i have some really hilarious ones, but oh well.
Can you please tell me exactly what ill lose? so,
bookmarks on the browsers
contacts and messages
all apps (they're on my phone) and app data? (like will i lose my progress in temple run 2, lol)
Click to expand...
Click to collapse
I don't have this phone with me ATM.but I seem to remember when you press volume UP: and POWER it if i remember correctly would do the blinking light and vibrating a few times .Anyways to get in recovery You Press Volume DOWN and press POWER at same time should bring you to recovery and if running a custom recovery such as CWM or 4EXT you can try the wipe cache and wipe dalvik cache to see if fix issue or try if using a custom ROM you can try installing the ROM again without wiping data and system first.I Read your post and the replies and correct me if I am wrong it sounds like this might work and sounds like you are able to get to recovery from reading your post I think.I would try and confirm that you are or are not able to try these suggestions before you try the boot-loader suggestion with the PD15IMG.zip or whatever it is called ,these are assuming your rooted with a custom recovery such 4EXT if not and I read wrong again I apologize. Good Luck!
alternatively you could use adb if u installed it
1. connect ur phone via usb cable.
2. run cmd from ur android-sdk folder (or whatever you named it). by running in folder I mean, ur path in cmd should be C:/whatever-is-your-sdk-folder path
3. type this in cmd window "adb reboot bootloader" (without ")
it should load your phone in bootloader from where u can get more options like factory reset or install new rom (u can mount ur sd card in recovery & put new rom to flash on sd card)
First of all, lets get something straight. Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is*actually*bricked, you won't be able to fix it yourself (but there are things you can do—see the end of this article). For those other problems, you have a few options.
If Your Phone Keeps Rebooting: Wipe Your Data and Cache

If you've flashed a ROM and your phone won't boot into the home screen, it's probably because you forgot to wipe your data and/or cache. It's trying to boot into the ROM, but some leftover data from your last ROM is causing it to error out, and it'll reboot itself over and over again. If your phone's eating a big bowl of boot loops, your first course of action should be to wipe its data and cache, which you can do from recovery mode. This method assumes you're using ClockworkMod Recovery, like the majority of Android users, but if your particular phone uses a different third-party recovery (like AmonRA), you should still be able to find these options in the interface. They might just be in a different place. To wipe your data and cache:
Power down your phone. Turn it back on and boot into Recovery mode. This is a bit different for every phone, so you'll have to Google how to do it for your specific model. Usually it involves holding down another button, like Volume Down, as you turn your phone on. HTC phones will have to then select "Recovery" from a menu, while other phones will boot directly into ClockworkMod. You'll know you're in ClockworkMod by the words "ClockworkMod Recovery" at the top of the screen.Use your volume keys to navigate the menus, and your power button to select menu items. Scroll down to Advanced, and choose "Wipe Dalvik Cache". When that's finished, go back to the main screen and choose "Wipe Cache Partition". Lastly, head to "Wipe Data/Factory Reset". This will delete all your settings and apps, but you should still be using the correct ROM.Reboot your phone.
With any luck, it should boot right into your ROM. If that didn't work, try the below method with the same ROM (or with a different ROM) and see if you get different results.
If Your Phone Boots Straight Into Recovery: Flash a New ROM

If, when you boot up your phone, it goes straight into ClockworkMod, then there's likely an issue with the ROM you flashed. Note that some ROMs boot into recovery mode automatically after flashing, so reboot your phone once from recovery mode to make sure you're having a problem. HTC users: if you boot up your phone, it might go straight into the bootloader—check to see whether you can choose "Recovery" from the list before continuing to the next step. HTC phones usually don't boot straight into recovery.
In this case, you'll want to reflash the ROM from scratch. Try again with the ROM that messed up your phone, if you so choose, but if that doesn't work, try an entirely different ROM. The best way to do this is to download a ROM from somewhere on the net and putting it on your*SD card. You'll need to take the SD card out of your phone, and you'll need an SD card reader that you can plug into your computer. Here's how it works:
Plug the SD card into your computer. Drag the ROM's ZIP file to your SD card, and wait for it to copy.When it's done copying, eject the SD card and put it back in your phone. Reboot into Recovery mode. This is a bit different for every phone, so you'll have to Google how to do it for your specific model. Usually it involves holding down another button, like Volume Down, as you turn your phone on. HTC phones will have to then select "Recovery" from a menu, while other phones will boot directly into ClockworkMod. You'll know you're in ClockworkMod by the words "ClockworkMod Recovery" at the top of the screen.Use your volume keys to navigate the menus, and your power button to select menu items. Scroll down to "Install ZIP From SD Card" and navigate to the ZIP file you just copied over. Give it time to flash the ROM.When it's done, reboot your phone.
Hopefully, your phone should successfully boot into the new ROM. From there, you can probably assume that the previous ROM that messed up your phone isn't going to work, and you'll have to find another ROM for now—or find another copy of that ROM that isn't corrupted. Remember to make backups of your working ROMs so you don't lose all your data!
If Your Phone Boots Straight Into its Bootloader: Restore From a Stock ROM
If you're really having trouble, one of the most surefire ways to get your phone working again is to restore from the original ROM your phone came with—unrooted, stock, stable goodness. Each manufacturer and phone has a different method for doing this, and we can't go into too much detail here, but we can steer you in the right direction.
Note that this will unroot your phone, and return it to exactly how it was when you bought it from the store. You'll lose all your apps, settings, ClockworkMod recovery, you'll get over-the-air updates again, and you'll even have to re-activate your phone if you're on a CDMA provider like Verizon or Sprint.
This is less likely, but it's a problem I and a few others have run into on occasion: sometimes your SD card just gets corrupted, which makes the above methods useless (since they rely on your SD card to work). Take your SD card out of your phone, put it into your computer using an SD card reader, and format it. It's very important that you format it through an SD card reader directly and not by plugging in your phone in USB mode—I learned this the hard way. Format it as FAT32 and try the above methods again.
Other errors, like during the ROM flashing process, might give you a hint as to what's wrong. Try heading to the*XDA Developers forums*and asking for help, as your phone could have one of a million specific problems we can't address here today. Remember, if your phone turns on, there's still a good chance you can recover from whatever error you're experiencing, so don't give up just yet!
If Your Phone Is Truly Bricked: Take It Into the Store and Play Dumb
If your phone is actually bricked—that is, it won't turn on at all, no matter how hard you try—it's time to give up and move on. The first thing you can do in this situation is try to take it back to your carrier's store and play dumb—just say something like "I don't know what happened, but my phone won't turn on anymore" (don't tell them you rooted it, obviously). Most carriers don't have time to deal with such issues and they'll just give you a new phone. Sure, it's a tad evil, but it should work most of the time.
If they're wise to your act, though, you can try another store or just sell your bricked phone for a few bucks on Craigslist. Sadly, if no one will replace your phone, you'll have to buy an entirely new one. Such are the dangers of rooting, but don't be discouraged! Bricking your phone is pretty rare, so I wouldn't worry about it being a common occurrence. As always, though, when you void your warranty, only do so if you're ready to replace that device completely, since you never know what can happen.
Sincerely,
Clowntown Developers
⊙facebook.com/clowntowndevs⊙ ♥Please like Us♥
Hey there.
I flashed a new ROM (Kaos Droid 7.0.0) and the fitting gapps some minutes ago from CWM Touch. Everything worked as supposed, no errors, no warnings, nothing. Then I rebooted the Nexus 7 and now it's stuck in the worst bootloop I have seen so far:
The Google Screen appears, stays for some seconds, then I see a screen with the CWM Logo and the text "ClockworkmodRecovery 6.0.38", after this the device seems to reboot and the sequence starts from the beginning again.
I can not get into recovery, I can connect to my PC via USB but connection and disconnection happens every few seconds (because of the bootloop).
I guess that's it for my Nexus 7 or does anyone have an idea what I can try to do. I'd be really thankful.
Jagutherrschaften said:
Hey there.
I flashed a new ROM (Kaos Droid 7.0.0) and the fitting gapps some minutes ago from CWM Touch. Everything worked as supposed, no errors, no warnings, nothing. Then I rebooted the Nexus 7 and now it's stuck in the worst bootloop I have seen so far:
The Google Screen appears, stays for some seconds, then I see a screen with the CWM Logo and the text "ClockworkmodRecovery 6.0.38", after this the device seems to reboot and the sequence starts from the beginning again.
I can not get into recovery, I can connect to my PC via USB but connection and disconnection happens every few seconds (because of the bootloop).
I guess that's it for my Nexus 7 or does anyone have an idea what I can try to do. I'd be really thankful.
Click to expand...
Click to collapse
Hi, Jagutherrschaften...
Try pressing VOLUME DOWN + THE POWER ON KEY and HOLD BOTH for 30 seconds (or as long as it takes to break out of the 'bootloop').
(or BOTH VOL KEYS + POWER ON if the above doesn't work... although it should).
Keep them pressed until you boot you into the bootloader....
You should now be free to run fastboot commands, to either fastboot flash back to factory stock... or you could attempt to just boot into recovery, and maybe do a Nandroid Backup restore from your previous setup (assuming of course, you created one).
Anyway... as long as you can still access the bootloader... all is not lost.
Rgrds,
Ged.
GedBlake said:
Hi, Jagutherrschaften...
Try pressing VOLUME DOWN + THE POWER ON KEY and HOLD BOTH for 30 seconds (or as long as it takes to break out of the 'bootloop').
(or BOTH VOL KEYS + POWER ON if the above doesn't work... although it should).
Keep them pressed until you boot you into the bootloader....
You should now be free to run fastboot commands, to either fastboot flash back to factory stock... or you could attempt to just boot into recovery, and maybe do a Nandroid Backup restore from your previous setup (assuming of course, you created one).
Anyway... as long as you can still access the bootloader... all is not lost.
Rgrds,
Ged.
Click to expand...
Click to collapse
Sorry, I forgot to mention that I can't boot into bootloader. I tried every single combination of keys. The bootloop goes on and is completely unimpressed by my keypresses. Bad bad thing.
Jagutherrschaften said:
Sorry, I forgot to mention that I can't boot into bootloader. I tried every single combination of keys. The bootloop goes on and is completely unimpressed by my keypresses. Bad bad thing.
Click to expand...
Click to collapse
How fast is the bootloop? and how long are you pressing the buttons for?
Lean on them, as it where, for a good minute or so... the device has to pick up the 'interrupts' sooner or later.
Rgrds,
Ged.
GedBlake said:
How fast is the bootloop? and how long are you pressing the buttons for?
Lean on them, as it where, for a good minute or so... the device has to pick up the 'interrupts' sooner or later.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you for your answers. I tried every combination and kept the keys pressed for 2 mins. Nothing. The only thing I can actually do is shut the device down by pressing POWER + VOL UP for a long while.
If bootloop doesnt stop and you cant get into bootloader....then just long press power button..that should stop the cycle...and then volm down plus power button....should get u into bootloader..atleast worked for me..
Sent from my Nexus 7 using xda app-developers app
Now here is what it looks like (doesn't matter if I press keys or not): https://dl.dropboxusercontent.com/u/12668781/Nexus7_bootloop.mkv
The normal method you described neo45215 doesn't work for me as well.
Jagutherrschaften said:
Thank you for your answers. I tried every combination and kept the keys pressed for 2 mins. Nothing. The only thing I can actually do is shut the device down by pressing POWER + VOL UP for a long while.
Here is a video what it looks like (if I press keys or not or keep keys pressed or not doesn't matter):
www.michi-fehr.de/Nexus7_bootloop.mkv
(Sorry, youtube messes with me as well. Seems not to be my day today.)
Click to expand...
Click to collapse
Mmm... this is a strange one...
Just had a look a your video... and I've seen a few bootoops, but never one involving a Custom Recovery and ONLY the Bootloader Unlock screen (yes, that is the Bootloader - it's just not normally recognized as such, because it's not in FASTBOOT mode).
If you've shutdown the tablet by pressing VOL UP + POWER ON, you've effectively booted the device into APX mode (it looks like it's shutdown, but it isn't) - if it is in APX mode, the device is now awaiting for you to run some nvFlash commands, which currently can't be done (though there is now, a very specific exception, which is not applicable here).
I agree with the previous poster, @neo45215, VOLUME DOWN (hold), then POWER BUTTON, (whilst still holding VOLUME DOWN), should boot you into the bootloader... but I think precise timing is required. Please read the following, carefully, several times.
----------------------------------------
QUOTE from http://forum.xda-developers.com/showthread.php?t=2133986
"Starting from booted or boot-looping OS:
Power (10-15 seconds) -> Normal OS Boot**
** Bootloader Interrupt: In any of the cases where you hold the power button down to try to break out of the current operating mode, if you press the Vol-Down button right after you first see the black and white screen with the Google logo, the tablet will proceed immediately to bootloader/fastboot mode, rather than booting the normal OS. You need to be ready though - you only get about 1 or 2 seconds to do this! (Thanks to RMXO for pointing this out) Note that this means you can get to the bootloader directly from any other mode!
This also explains why, when attempting a cold start using Vol-Down + Power, if you accidentally let go of the vol-down button when the screen first lights up, the Nexus 7 will boot to the normal OS. In this case, pressing Vol-Down initially is actually superfluous - what makes the device go into bootloader/fastboot mode is the Vol-Down press immediately following the google splash screen - there actually is no unique "Go to fastboot from a cold start" method."
----------------------------------------
I'm at loss to suggest anything more helpful... this looks like the bootloop from hell! But I'm convinced, that with the correct timing and persistence, some key-combo interrupt could break the Nexus 7 out of it.
Rgrds,
Ged.
GedBlake said:
Mmm... this is a strange one...
Just had a look a your video... and I've seen a few bootoops, but never one involving a Custom Recovery and ONLY the Bootloader Unlock screen (yes, that is the Bootloader - it's just not normally recognized as such, because it's not in FASTBOOT mode).
If you've shutdown the tablet by pressing VOL UP + POWER ON, you've effectively booted the device into APX mode (it looks like it's shutdown, but it isn't) - if it is in APX mode, the device is now awaiting for you to run some nvFlash commands, which currently can't be done (though there is now, a very specific exception, which is not applicable here).
I agree with the previous poster, @neo45215, VOLUME DOWN (hold), then POWER BUTTON, (whilst still holding VOLUME DOWN), should boot you into the bootloader... but I think precise timing is required. Please read the following, carefully, several times.
----------------------------------------
QUOTE from http://forum.xda-developers.com/showthread.php?t=2133986
"Starting from booted or boot-looping OS:
Power (10-15 seconds) -> Normal OS Boot**
** Bootloader Interrupt: In any of the cases where you hold the power button down to try to break out of the current operating mode, if you press the Vol-Down button right after you first see the black and white screen with the Google logo, the tablet will proceed immediately to bootloader/fastboot mode, rather than booting the normal OS. You need to be ready though - you only get about 1 or 2 seconds to do this! (Thanks to RMXO for pointing this out) Note that this means you can get to the bootloader directly from any other mode!
This also explains why, when attempting a cold start using Vol-Down + Power, if you accidentally let go of the vol-down button when the screen first lights up, the Nexus 7 will boot to the normal OS. In this case, pressing Vol-Down initially is actually superfluous - what makes the device go into bootloader/fastboot mode is the Vol-Down press immediately following the google splash screen - there actually is no unique "Go to fastboot from a cold start" method."
----------------------------------------
I'm at loss to suggest anything more helpful... this looks like the bootloop from hell! But I'm convinced, that with the correct timing and persistence, some key-combo interrupt could break the Nexus 7 out of it.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks a lot for your help, I have tried everything, I can't get anywhere... neither bootloader nor recovery.
Additionally I can't make the device do anything I want by adb.
And as a "bonus" I can't send my Nexus7 to repair because this stupid bootloop shows "ClockworkMod Recovery v6.0.3.8" :silly:
Jagutherrschaften said:
Thanks a lot for your help, I have tried everything, I can't get anywhere... neither bootloader nor recovery.
Additionally I can't make the device do anything I want by adb.
And as a "bonus" I can't send my Nexus7 to repair because this stupid bootloop shows "ClockworkMod Recovery v6.0.3.8" :silly:
Click to expand...
Click to collapse
Really sorry to hear this... it is baffling:.
I've been hanging around on XDA since January, and I've come across a lot of weird behaviour, reported by other posters. But this is something that is outside my experience.
A few questions... (no guarantees, but I'll try to see if I can come up with something)...
Can you post download links for EVERYTHING you've flashed...
The ROM, the Gapps, the CWM recovery.
Also, what order did you flash them in?
Did you use fastboot? or a Toolkit at any time?
Where you rooted BEFORE you embarked on this endeavour?
How did you acquire root?
How long have you had the Nexus 7?
Is it a WiFi only model or a WiFi and 3G model?
Have you flashed any other Custom ROMs prior to this one?
If, so, any problems?
Do you know your current bootloader version number?
What was the battery status (percentage) prior to you flashing this ROM?
Sorry for all the questions... but something, some tiny litlle detail, might set a 'eureka!' light bulb off in my head.
Rgrds,
Ged.
GedBlake said:
Really sorry to hear this... it is baffling:.
I've been hanging around on XDA since January, and I've come across a lot of weird behaviour, reported by other posters. But this is something that is outside my experience.
A few questions... (no guarantees, but I'll try to see if I can come up with something)...
Can you post download links for EVERYTHING you've flashed...
The ROM, the Gapps, the CWM recovery.
Also, what order did you flash them in?
Did you use fastboot? or a Toolkit at any time?
Where you rooted BEFORE you embarked on this endeavour?
How did you acquire root?
How long have you had the Nexus 7?
Is it a WiFi only model or a WiFi and 3G model?
Have you flashed any other Custom ROMs prior to this one?
If, so, any problems?
Do you know your current bootloader version number?
What was the battery status (percentage) prior to you flashing this ROM?
Sorry for all the questions... but something, some tiny litlle detail, might set a 'eureka!' light bulb off in my head.
Rgrds,
Ged.
Click to expand...
Click to collapse
OK, I'll try to answer as detailed as possible:
ROM KaosDroid7.0.0
FittingGApps
CWM Recovery (Touch) was installed through ROM Manager Premium
The order of what I did was: I made a backup in Titanium Backup Pro, then I made a nandroid backup by ROM Manager Premium. I went to recovery, wiped /cache and /data, then flashed KaosDroid7.0.0, flashed GApps and rebooted. After my Nexus7 had fully booted I restored some user apps and settings via Titanium Backup Pro. I had to reboot. After that I explored that clock was force closed whenever I tried to access the alarm clock. I wondered if I could possibly have overseen a checkmark when restoring with Titanium Backup Pro (maybe forgotten to untick a system app or setting) which could lead to the force close. So I decided to start over again.
This time I thought about using ROM Manager Premium for wiping and flashing. I started the app and it told me there was an update for CWM Recovery. So I installed this update through ROM Manager Premium - CWM Recovery Touch 6.0.3.8. I rebooted and went to recovery to flash ROM and GApps again the normal way. Before flashing I wiped /cache and /data again. Everything went fine until I rebooted the tablet and found myself in this "bootloop of hell" as you called it... After having tried a lot to break it, I opened the Nexus7 to remove battery for the first time.
OK, now the other questions:
I bought my Nexus7 about 11 months ago, it's the 16 GB WiFi only version. I aquired root by using this Toolkit and everything went really smooth. I tried several ROMs yes, after some time I came across KaosDroid (don't exactly know which version I started with, maybe v5.0.0) and really liked it. I flashed a new version whenever there was one and never had any problems before.
I am not sure about my current bootloader version, I have some not too long ago nandroid backups on my PC, can I find out anywhere in there? About battery, it was 55 % or so before I started flashing, maybe even more.
The way I see this is: It looks like ROM Manager has messed something up. I have never seen a screen like the ROM Manager screen that occurs in the bootloop right after the Google screen before. Unless maybe when making a nandroid backup through ROM Manager, not sure about this. But it shouldn't be there in a normal boot sequence as far as I understand it.
The only way I can access my Nexus7 is via USB on my PC. And I have like 5 seconds to act while this ROM Manager screen is on, that's the time frame when my PC says "Nexus7 connected" and even the Toolkit finds the device and says it's in "ADB mode", then prints the serial number, but sadly after that it waits for the device to enter adb mode forever.
EDIT: And of course I can get access in APX mode, but from what I have read there is no way to do anything because commands etc. to install a new bootloader are not known (yet?).
Thanks a lot for your help and patience, it actually helps to know there is someone who reads this :good:.
It's not the end of the world if I can't reanimate my Nexus7 but it served me so well for almost a year and I really like it .
Jagutherrschaften said:
OK, I'll try to answer as detailed as possible:
ROM KaosDroid7.0.0
FittingGApps
CWM Recovery (Touch) was installed through ROM Manager Premium
The order of what I did was: I made a backup in Titanium Backup Pro, then I made a nandroid backup by ROM Manager Premium. I went to recovery, wiped /cache and /data, then flashed KaosDroid7.0.0, flashed GApps and rebooted. After my Nexus7 had fully booted I restored some user apps and settings via Titanium Backup Pro. I had to reboot. After that I explored that clock was force closed whenever I tried to access the alarm clock. I wondered if I could possibly have overseen a checkmark when restoring with Titanium Backup Pro (maybe forgotten to untick a system app or setting) which could lead to the force close. So I decided to start over again.
This time I thought about using ROM Manager Premium for wiping and flashing. I started the app and it told me there was an update for CWM Recovery. So I installed this update through ROM Manager Premium - CWM Recovery Touch 6.0.3.8. I rebooted and went to recovery to flash ROM and GApps again the normal way. Before flashing I wiped /cache and /data again. Everything went fine until I rebooted the tablet and found myself in this "bootloop of hell" as you called it... After having tried a lot to break it, I opened the Nexus7 to remove battery for the first time.
OK, now the other questions:
I bought my Nexus7 about 11 months ago, it's the 16 GB WiFi only version. I aquired root by using this Toolkit and everything went really smooth. I tried several ROMs yes, after some time I came across KaosDroid (don't exactly know which version I started with, maybe v5.0.0) and really liked it. I flashed a new version whenever there was one and never had any problems before.
I am not sure about my current bootloader version, I have some not too long ago nandroid backups on my PC, can I find out anywhere in there? About battery, it was 55 % or so before I started flashing, maybe even more.
The way I see this is: It looks like ROM Manager has messed something up. I have never seen a screen like the ROM Manager screen that occurs in the bootloop right after the Google screen before. Unless maybe when making a nandroid backup through ROM Manager, not sure about this. But it shouldn't be there in a normal boot sequence as far as I understand it.
The only way I can access my Nexus7 is via USB on my PC. And I have like 5 seconds to act while this ROM Manager screen is on, that's the time frame when my PC says "Nexus7 connected" and even the Toolkit finds the device and says it's in "ADB mode", then prints the serial number, but sadly after that it waits for the device to enter adb mode forever.
EDIT: And of course I can get access in APX mode, but from what I have read there is no way to do anything because commands etc. to install a new bootloader are not known (yet?).
Thanks a lot for your help and patience, it actually helps to know there is someone who reads this :good:.
It's not the end of the world if I can't reanimate my Nexus7 but it served me so well for almost a year and I really like it .
Click to expand...
Click to collapse
Hello again, Jagutherrschaften...
Sorry for taking so long to get back to you, but I've been really busy with non-Android stuff all day.
Before I signed off XDA early this morning, (Fri, UK time)... and before you posted your explanation of how you got into your undesirble predicament, I was trying to think why your Nexus 7 is attempting to boot into CWM. It's something I've never seen before... it occurred to me, CWM may have been incorrectly flashed to the boot partition, instead of the recovery partition. This would go some way to explaining why your Nexus 7 is attempting to boot into CWM instead of normal Android.
So in an attempt to replicate your situation, I fastboot flashed CWM on my Nexus 7, to the boot partition with...
Code:
fastboot flash boot recovery-clockwork-touch-6.0.3.8-grouper.img
...instead of (and correctly)...
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.3.8-grouper.img
Upon completion of this flash, I hit START (from the bootloader)... and as expected my Nexus 7 booted into the Google logo, and then directly into CWM.
...but it didn't bootloop as depicted in your video, it just ran CWM as normal..
I booted several times into CWM, but no bootloop. (It's kind of weird having two custom recoveries installed... there's an option in CWM to restart Recovery, which upon tapping, my N7 booted straight into TWRP !, which is my Custom Recovery of choice. And resides correctly in the recovery partition. I had to make a conscious effort to reboot as normal, in order to boot into CWM).
Anyway, more puzzled more than ever, I fastboot flashed the Jellybean 4.3 stock boot .img back to it's rightful place, rebooted the tablet, to make sure everything was working as normal, and went to bed.
Later, after you posted, I re-read it many times (and took a look at the links), and re-watched your video several more times (by the way, Nandroid backups don't backup the bootloader), and nothing occurred to me; no 'euraka' ! moment.
The bootloader is obviously still intact... if it wasn't, then your Nexus 7 wouldn't boot at all. Besides, it's there, visible, with the unlocked padlock symbol !
I'm inclined to tentatively agree with your assessment that ROM Manager screwed something up. I haven't used ROM Manager for ages, due to known issues on my Advent Vega. And on the Nexus 7, I just use fastboot. On the Vega, you use a command called flash_image to flash images, and is syntactically very similar to fastboot.
Sticking with my Vega for a moment... some users are unable to boot into CWM at all. And nobody seems to know why. But a while ago, somebody did some research into this problem, and it was speculated that on some Vegas there are BAD NAND BLOCKS (like bad sectors on a hard drive, only on a chip instead) in the MISC partition, where a binary state flag is set, telling the tablet to boot into Recovery instead of Android.
Now it's a bit a leap... and hugely speculative... but I wonder if the MISC partition on your Nexus 7 may have become corrupted... ?POSSIBLY? as a result of using ROM Manager... and that is telling the tablet to boot into Recovery instead of Android.
This is a far from satisfactory explanation, though, for several reasons...
* I'm not sure how far you can extrapolate the partition structures of one completely different tablet to another completely different tablet.
* It doesn't explain why your tablet is bootlooping and mine didn't (after replacing the stock boot.img with the CWM recovery .img in the boot partition.
* And finally... I'm still baffled why VOL DOWN+POWER ON doesn't break out of the bootloop and boot directly into the bootloader. Everything I know about the Nexus 7 tells me that this should happen... and it's always been the case, that as long as you can access the bootloader, the tablet is recoverable.
I'm afraid I have nothing else to suggest or try... other than what you've tried already.
I can only offer my apologies that I was unable to assist you... maybe somebody with more technical expertise might offer some new insight or suggestions.
Rgrds,
Ged.
GedBlake said:
Hello again, Jagutherrschaften...
Sorry for taking so long to get back to you, but I've been really busy with non-Android stuff all day.
Before I signed off XDA early this morning, (Fri, UK time)... and before you posted your explanation of how you got into your undesirble predicament, I was trying to think why your Nexus 7 is attempting to boot into CWM. It's something I've never seen before... it occurred to me, CWM may have been incorrectly flashed to the boot partition, instead of the recovery partition. This would go some way to explaining why your Nexus 7 is attempting to boot into CWM instead of normal Android.
So in an attempt to replicate your situation, I fastboot flashed CWM on my Nexus 7, to the boot partition with...
Code:
fastboot flash boot recovery-clockwork-touch-6.0.3.8-grouper.img
...instead of (and correctly)...
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.3.8-grouper.img
Upon completion of this flash, I hit START (from the bootloader)... and as expected my Nexus 7 booted into the Google logo, and then directly into CWM.
...but it didn't bootloop as depicted in your video, it just ran CWM as normal..
I booted several times into CWM, but no bootloop. (It's kind of weird having two custom recoveries installed... there's an option in CWM to restart Recovery, which upon tapping, my N7 booted straight into TWRP !, which is my Custom Recovery of choice. And resides correctly in the recovery partition. I had to make a conscious effort to reboot as normal, in order to boot into CWM).
Anyway, more puzzled more than ever, I fastboot flashed the Jellybean 4.3 stock boot .img back to it's rightful place, rebooted the tablet, to make sure everything was working as normal, and went to bed.
Later, after you posted, I re-read it many times (and took a look at the links), and re-watched your video several more times (by the way, Nandroid backups don't backup the bootloader), and nothing occurred to me; no 'euraka' ! moment.
The bootloader is obviously still intact... if it wasn't, then your Nexus 7 wouldn't boot at all. Besides, it's there, visible, with the unlocked padlock symbol !
I'm inclined to tentatively agree with your assessment that ROM Manager screwed something up. I haven't used ROM Manager for ages, due to known issues on my Advent Vega. And on the Nexus 7, I just use fastboot. On the Vega, you use a command called flash_image to flash images, and is syntactically very similar to fastboot.
Sticking with my Vega for a moment... some users are unable to boot into CWM at all. And nobody seems to know why. But a while ago, somebody did some research into this problem, and it was speculated that on some Vegas there are BAD NAND BLOCKS (like bad sectors on a hard drive, only on a chip instead) in the MISC partition, where a binary state flag is set, telling the tablet to boot into Recovery instead of Android.
Now it's a bit a leap... and hugely speculative... but I wonder if the MISC partition on your Nexus 7 may have become corrupted... ?POSSIBLY? as a result of using ROM Manager... and that is telling the tablet to boot into Recovery instead of Android.
This is a far from satisfactory explanation, though, for several reasons...
* I'm not sure how far you can extrapolate the partition structures of one completely different tablet to another completely different tablet.
* I't doesn't explain why your tablet is bootlooping and mine didn't (after replacing the stock boot.img with the CWM recovery .img in the boot partition.
* And finally... I'm still baffled why VOL DOWN+POWER ON doesn't break out of the bootloop and boot directly into the bootloader. Everything I know about the Nexus 7 tells me that this should happen... and it's always been the case, that as long as you can access the bootloader, the tablet is recoverable.
I'm afraid I have nothing else to suggest or try... other than what you've tried already.
I can only offer my apologies that I was unable to assist you... maybe somebody with more technical expertise might offer some new insight or suggestions.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hey again GedBlake.
The last thing you have to do is apologize for helping me a lot, reading through all my text and making things clear for me. And even more you flashed stuff to your device to test if my situation can be reproduced - good that it's not . You've spent a lot of free time just to help, that's really great :good:.
With my bootloader still being intact and the device being recognized by my PC I wonder if maybe I can manage to fastboot flash a different bootloader and/or a new recovery which might maybe break the silly loop when booting. That's my only idea left but if the bootloader isn't in fastboot mode at some time during the loop this won't work too. But I'll give it a try, it's better than cutting tomatoes on my Nexus7 :laugh:.
Thank you very much for your help. If there is anything worth reporting I will of course.
Jagutherrschaften said:
Hey again GedBlake.
The last thing you have to do is apologize for helping me a lot, reading through all my text and making things clear for me. And even more you flashed stuff to your device to test if my situation can be reproduced - good that it's not . You've spent a lot of free time just to help, that's really great :good:.
With my bootloader still being intact and the device being recognized by my PC I wonder if maybe I can manage to fastboot flash a different bootloader and/or a new recovery which might maybe break the silly loop when booting. That's my only idea left but if the bootloader isn't in fastboot mode at some time during the loop this won't work too. But I'll give it a try, it's better than cutting tomatoes on my Nexus7 :laugh:.
Thank you very much for your help. If there is anything worth reporting I will of course.
Click to expand...
Click to collapse
Thanks for your kind words... they're appreciated.
Unfortunately, before you can fastboot flash anything, the Nexus 7 needs to be properly booted into the bootloader (the screen with the green Android lying on its back, and the word START adjacent to the POWER BUTTON)... and that requires breaking out of the bootloop first.
Indeed, if the VOL DOWN+POWER ON button combo was working as it should... breaking out of the bootloop would AUTOMATICALLY boot your Nexus 7 into the bootloader.
Finally, your bootloader doesn't need to re-flashed. One you have a stable bootloader boot, normally, (and the easiest way), would just be to flash back to factory stock.
Rgrds,
Ged.
GedBlake said:
Thanks for your kind words... they're appreciated.
Unfortunately, before you can fastboot flash anything, the Nexus 7 needs to be properly booted into the bootloader (the screen with the green Android lying on its back, and the word START adjacent to the POWER BUTTON)... and that requires breaking out of the bootloop first.
Indeed, if the VOL DOWN+POWER ON button combo was working as it should... breaking out of the bootloop would AUTOMATICALLY boot your Nexus 7 into the bootloader.
Finally, your bootloader doesn't need to re-flashed. One you have a stable bootloader boot, normally, (and the easiest way), would just be to flash back to factory stock.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hey again.
Thanks for your explanation, I am not really a newbie with PCs and Tablets etc. but some things are not very interesting until you really need to know them. Like bootloader and fastboot in Android.
So the conclusion in my case is that maybe some day someone will find out how to get access to the N7 via APX - or to be precise, someone finds out or gets to know the necessary commands to flash something to the N7 over the APX-interface. Right?
Because from what I've read it doesn't really make sense to send my N7 in for repair right? Although it hasn't even had its 1st birthday yet I have no chance to get a warranty repair or exchange as it's very obvious I rooted the device and flashed stuff (the damned ROM Manager-screen clearly shows this). And ASUS charges 90 $ (or €, don't know) just for diagnosis, that's a bit much for a device that cost 199 €.
Any further advise? Could I buy a broken N7 from eBay for example and repair mine this way? I would have to change the mainboard right?
Have a nice sunday everyone .
U said you opened the battery...so wen u plugged it back in again,u shouldn't be in bootloop technically... Just a boot!...wat happens if u press the volm down and power button combo just as u insert the battery?
Sent from my Nexus 7 using xda app-developers app
Jagutherrschaften said:
Hey again.
Thanks for your explanation, I am not really a newbie with PCs and Tablets etc. but some things are not very interesting until you really need to know them. Like bootloader and fastboot in Android.
So the conclusion in my case is that maybe some day someone will find out how to get access to the N7 via APX - or to be precise, someone finds out or gets to know the necessary commands to flash something to the N7 over the APX-interface. Right?
Because from what I've read it doesn't really make sense to send my N7 in for repair right? Although it hasn't even had its 1st birthday yet I have no chance to get a warranty repair or exchange as it's very obvious I rooted the device and flashed stuff (the damned ROM Manager-screen clearly shows this). And ASUS charges 90 $ (or €, don't know) just for diagnosis, that's a bit much for a device that cost 199 €.
Any further advise? Could I buy a broken N7 from eBay for example and repair mine this way? I would have to change the mainboard right?
Have a nice sunday everyone .
Click to expand...
Click to collapse
Hi, Jagutherrschaften...
Really sorry it had to end like this... but... perhaps it doesn't...
Nothing about your situation makes logical sense... but reading through your posts again, I find this- On the 3rd October, you posted...
Jagutherrschaften said:
Thank you for your answers. I tried every combination and kept the keys pressed for 2 mins. Nothing. The only thing I can actually do is shut the device down by pressing POWER + VOL UP for a long while.
Click to expand...
Click to collapse
QUOTE FOR EMPHASIS:- "...by pressing POWER + VOL UP for a long while..."
This key press combo doesn't actually shut down the device... it just pushes it into APX mode. It just looks like it's shutdown.
But that's not my point... my point is your Nexus 7 detected that key press interrupt... and acted accordingly.
It did what it was supposed to do.
Maybe you hit the buttons at JUST THE RIGHT INSTANT during the bootloop... and if it can do it for one key press combo... it can do it for another. Namely, POWER+VOL DOWN.
And for this reason... I think you need to try and try and try and try and try again... until you hit the same PRECISE TIMING SWEET SPOT... such that POWER+VOL DOWN takes you into the bootloader.
Vary the timings a bit here and there... alternate pressing the buttons, both before AND after when the Google logo appears.
By your own account... you've already done it once (you just got into the wrong mode... APX mode instead of bootloader mode).
But here's the danger... if after your Herculean efforts, you do manage, finally, to access the bootloader... you absolutely cannot afford to reboot the device normally until after you've fastboot flashed back to factory stock... otherwise the whole cycle will begin again.
So... you need, in preparation...
* A fully charged Nexus 7.
* All the drivers needed (if you don't already have them) installed on your PC.
* The Jellybean 4.3 Factory Stock image downloaded (see my Sig, second link) and unzipped and ready to go.
* A working knowledge of how to use Fastboot.
* And finally... an indomitable spirit! of perseverance... and, of course, a fair amount of free time.
------------------------------------------
I am convinced that your tablet is recoverable.
It's gotta be worth a shot... "once more unto the breach, dear friends", as old Bill Shakespeare would have it.
Anyway... the very best of luck.
Rgrds,
Ged.
GedBlake said:
Hi, Jagutherrschaften...
Really sorry it had to end like this... but... perhaps it doesn't...
Nothing about your situation makes logical sense... but reading through your posts again, I find this- On the 3rd October, you posted...
QUOTE FOR EMPHASIS:- "...by pressing POWER + VOL UP for a long while..."
This key press combo doesn't actually shut down the device... it just pushes it into APX mode. It just looks like it's shutdown.
But that's not my point... my point is your Nexus 7 detected that key press interrupt... and acted accordingly.
It did what it was supposed to do.
Maybe you hit the buttons at JUST THE RIGHT INSTANT during the bootloop... and if it can do it for one key press combo... it can do it for another. Namely, POWER+VOL DOWN.
And for this reason... I think you need to try and try and try and try and try again... until you hit the same PRECISE TIMING SWEET SPOT... such that POWER+VOL DOWN takes you into the bootloader.
Vary the timings a bit here and there... alternate pressing the buttons, both before AND after when the Google logo appears.
By your own account... you've already done it once (you just got into the wrong mode... APX mode instead of bootloader mode).
But here's the danger... if after your Herculean efforts, you do manage, finally, to access the bootloader... you absolutely cannot afford to reboot the device normally until after you've fastboot flashed back to factory stock... otherwise the whole cycle will begin again.
So... you need, in preparation...
* A fully charged Nexus 7.
* All the drivers needed (if you don't already have them) installed on your PC.
* The Jellybean 4.3 Factory Stock image downloaded (see my Sig, second link) and unzipped and ready to go.
* A working knowledge of how to use Fastboot.
* And finally... an indomitable spirit! of perseverance... and, of course, a fair amount of free time.
------------------------------------------
I am convinced that your tablet is recoverable.
It's gotta be worth a shot... "once more unto the breach, dear friends", as old Bill Shakespeare would have it.
Anyway... the very best of luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
@neo45215:
Technically yes, but my N7 doesn't seem to know this . Of course I've tried to get into fastboot mode right after putting back the battery as well. No chance, same bootloop.
@GedBlake:
Thanks for the encouragement, I will for sure give this a try (or several long trys to be precise). Hopefully tonight I'll have a lot of time to press keys .
And my answer to what Bill says would be: "To infinity... and beyond!"
No success so far, I tried pressing buttons for at least 1 h, nothing...
Just wanted to update the status .
Gesendet von meinem Nexus 7 mit Tapatalk 4
Facing same problem
Hello guys. I've done pretty much the same thing and my tab is in the same boot loop that this thread is all about.
The interesting thing is that the ROM I flashed is also KaosDroid7.0.0. I'm unable to prevent any further insight. Sorry for bumping. My clockwork mod version is btw, 6.0.4.1 which proves that the problem might not be clockworkmods or even ROM manager's problem. Since I hadn't used ROM manager.
Also, Is there any way whatsoever to use this APX mode? To fix my nexus.
---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------
Well, I followed OP's steps almost exactly. First I'd restored the Kitkat factory image, and then I'd proceeded to install the KD 7.0.0. And after that, I realised I'd forgotten to flash Gapps. So I rebooted and then went into CWM to reflash and after that is when my Nexus 7 became useless :crying:
---------- Post added at 02:14 PM ---------- Previous post was at 02:05 PM ----------
Jagutherrschaften, did you send in your Nexus 7 for repair?
My HTC U Ultra suddenly froze past nigth, then it rebooted... and never came back, it won't go past the HTC logo over and over. I am not able to enter in recovery mode either, the only thing I can do is, by pressing both volume buttons and power, entering in what seems to be fastboot menu. In that state I can send the phone fastboot commands (no adb commands though) but If i try to wipe it it says "unable to do in s-on" or similar. I was pretty happy with this phone, and spent a few bucks in a new battery not two months ago.... anything I can do?
Thanks.
PS: I failed to state that the phone is stock, not unlocked or rooted.
If it has just happened out of the blue and you haven't been doing anything with your phone, have you tried a simple reset? (Press and hold volume down and power button until your phone vibrates - Usually about 20 seconds for me)
If not, and you are struggling to get into recovery etc, see if you can follow the method in the thread linked below if you are currently on stock rom!?
(Not sure if this would delete all your data or not, so perhaps only use as a last resort....)
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
spikey001 said:
If it has just happened out of the blue and you haven't been doing anything with your phone, have you tried a simple reset? (Press and hold volume down and power button until your phone vibrates - Usually about 20 seconds for me)
If not, and you are struggling to get into recovery etc, see if you can follow the method in the thread linked below if you are currently on stock rom!?
(Not sure if this would delete all your data or not, so perhaps only use as a last resort....)
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
Click to expand...
Click to collapse
Reset doesn't work, and the other procedure didn't work either.
If I leave it plugged to the charger, it will fall into an endless reboot loop. Sometimes (few) it will end up booting, but If i try to do something with the phone it doesn't respond and reboots again.
Thanks.
As you can send fastboot commands, can you flash a recovery.img (i.e. TWRP), and then wipe cache and dalvik/art to see if that helps, but if not, flash corresponding rom to that which you already have?
spikey001 said:
As you can send fastboot commands, can you flash a recovery.img (i.e. TWRP), and then wipe cache and dalvik/art to see if that helps, but if not, flash corresponding rom to that which you already have?
Click to expand...
Click to collapse
I tried that, too, but didn't work. If I do a fastboot devices it detects the phone, but if I do a fastboot getvar all it doesn't give me any information, it doesn't admit adb commands, when I try to flash a rom or a recovery, it fails, I suspect it needs to have the USB debugging enabled, but I can't enable it in this state.
As I said before, if I leave it plugged to the charger, It will randomly end up booting (it can happen in the third loop or in the 50th), but it will freeze or reboot again in few seconds.
Ah I see, if you haven't got USB debugging enabled then I am unsure how to help sorry. Have you got your media backed up, or stored on micro sd? If so, might have to bite the bullet and do a factory reset. Sorry I couldn't be of any help. Maybe someone else would be able to help you further?
spikey001 said:
Ah I see, if you haven't got USB debugging enabled then I am unsure how to help sorry. Have you got your media backed up, or stored on micro sd? If so, might have to bite the bullet and do a factory reset. Sorry I couldn't be of any help. Maybe someone else would be able to help you further?
Click to expand...
Click to collapse
The data is not a problem, every important file has been backed up.
Regarding factory reset, since the device won't go to recovery, I can't see how can I do it.
-- Edit --
I noticed that when the phone is cold, those few times it boots, it lasts a little bit more (a matter of seconds) until it freezes again, so I tried to leave it in the freezer for a few minutes, and tried to boot it, and had enough time to do a factory reset. The factory reset worked, because now, when it boots, it goes straight to the intial setup, but keeps hanging after a few seconds. I suspect that the internal memory was somehow damaged, I don't think there is much left to do...
Is it possible to skip setup in order to get to settings and enable USB debugging so you can install a recovery?
If you can, then it might be an idea to try performing a repair of all the partitions and install a fresh ROM... Just to ensure it isn't a hardware issue!!
spikey001 said:
Is it possible to skip setup in order to get to settings and enable USB debugging so you can install a recovery?
If you can, then it might be an idea to try performing a repair of all the partitions and install a fresh ROM... Just to ensure it isn't a hardware issue!!
Click to expand...
Click to collapse
I can't see how to skip initial setup... and I don't have time enough to go through it, the phone will hang in 30 seconds or less. At this point, I really needed a working phone, so I bite the bullet and bought a new one... I will deal with the old one later, or I might sell it for parts.
Thanks everybody for the help.
No worries, enjoy your new phone