Every time I install a new zip, I have to reset the IDME boot to 4000 before I can use the device again in Android. What can I do to prevent this?
I've heard that one way to prevent this (not sure if this is your problem or not) is to only boot to TWRP from firefirefire. IE, if you are running CM7, don't select reboot to recovery, or something like that.
The reason being, there is a bug in TWRP which causes it to not reset the bootmode when you select reboot.
I have always done it this way (saw someone mention it in a post) and have never had the problems of TWRP endless reboots that I keep seeing...
podspi said:
I've heard that one way to prevent this (not sure if this is your problem or not) is to only boot to TWRP from firefirefire. IE, if you are running CM7, don't select reboot to recovery, or something like that.
The reason being, there is a bug in TWRP which causes it to not reset the bootmode when you select reboot.
I have always done it this way (saw someone mention it in a post) and have never had the problems of TWRP endless reboots that I keep seeing...
Click to expand...
Click to collapse
For my one information, what is "firefirefire"? Is that pushing the on button several times to get the TWRP to come up?
ontwowheels said:
For my one information, what is "firefirefire"? Is that pushing the on button several times to get the TWRP to come up?
Click to expand...
Click to collapse
Yes, firefirefire is the yellow triangle.
To clarify the answer to to OP. Always turn POWER OFF before installing a new rom. Don't reboot into TWRP and you won't get stuck in the boot loop.
furtom said:
Yes, firefirefire is the yellow triangle.
To clarify the answer to to OP. Always turn POWER OFF before installing a new rom. Don't reboot into TWRP and you won't get stuck in the boot loop.
Click to expand...
Click to collapse
Thanks....I currently have this and TWRP installed via the KFUtility.
Can also verify I have avoided this by always powering down and not rebooting into recovery. At least with the 4 zips I have flashed.
install clockworkmod touch recovery
twrp never fixed the reboot option.
Sent from my HTC Glacier using xda premium
Fix TWRP boot loop
Turn off Kindle. Plug Kindle into computer. Load fire utility. Choose option 5 for TWRP install, but don't hit enter yet. Turn on Kindle. Once yellow triangle appears, hit enter on keyboard to install TWRP, let it power cycle one or two times. This fixes boot loop.
citizenandroid said:
Turn off Kindle. Plug Kindle into computer. Load fire utility. Choose option 5 for TWRP install, but don't hit enter yet. Turn on Kindle. Once yellow triangle appears, hit enter on keyboard to install TWRP, let it power cycle one or two times. This fixes boot loop.
Click to expand...
Click to collapse
Thank you for this! I've been looking through the forums trying to find something that would work. ADB won't launch for me, something I need to look into, but this worked. Thank! :]
Hi all,
I thought I'd consult the brains trust to see if anyone thinks this is salvageable. Was using my A500 about 2 hours ago, suddenly the screen powered off. Thinking nothing of it, I held down the power button to restart it. When powering back on, nothing appears to happen except for the power button lighting up. No screen on, no vibe, nothing except the power light on.
Tried power cycling a few times to no avail. Tried the reset button. Tried the Vol+ Power and Rotation switch reset. Nothing.
Out of morbid curiousity, I plugged it into the PC and switched it on and I get an APX driver being installed. So, clearly something is happening here.
It has done this once before and came back to life of its own accord very shortly afterwards, this time it's been dead for quite some time.
Any suggestions? It's well out of warranty now, so I doubt Acer would be interested in it at all.
Dopius_Fishius said:
Hi all,
I thought I'd consult the brains trust to see if anyone thinks this is salvageable. Was using my A500 about 2 hours ago, suddenly the screen powered off. Thinking nothing of it, I held down the power button to restart it. When powering back on, nothing appears to happen except for the power button lighting up. No screen on, no vibe, nothing except the power light on.
Tried power cycling a few times to no avail. Tried the reset button. Tried the Vol+ Power and Rotation switch reset. Nothing.
Out of morbid curiousity, I plugged it into the PC and switched it on and I get an APX driver being installed. So, clearly something is happening here.
It has done this once before and came back to life of its own accord very shortly afterwards, this time it's been dead for quite some time.
Any suggestions? It's well out of warranty now, so I doubt Acer would be interested in it at all.
Click to expand...
Click to collapse
In the Dev threads, or possibly Q&A, there is a thread called "stuck in APX mode". In there I believe are some steps to see if you can recover.
But, if you're in APX mode, you could probably try NVFlashing the bootloader and recovery the old fashioned way manually.
But look up that APX thread first. Will probably have the answer. I'll see if I can find it in a little while, if you don't find it first.
MD
Moscow Desire said:
In the Dev threads, or possibly Q&A, there is a thread called "stuck in APX mode". In there I believe are some steps to see if you can recover.
But, if you're in APX mode, you could probably try NVFlashing the bootloader and recovery the old fashioned way manually.
But look up that APX thread first. Will probably have the answer. I'll see if I can find it in a little while, if you don't find it first.
MD
Click to expand...
Click to collapse
Thanks MD. I looked up the threads you suggested, and after a lot of screwing around I have installed the APX drivers and used blackthund3r's APX Flash Util 0.3 (The link is broken to the current version) to attempt a recovery of my tab.
Its now sitting at an Acer screen, "Entering Acer Download Mode" while the flash util is sitting at:
Nvflash started
[resume mode]
It's been there for about 10 minutes now, no progress to report. Is it worth just sitting it out, or now that the damn tab shows SOME signs of life, can I just restart it and reset to factory?
And then most bizarre of all. I declared no progress, rebooted it. It went back to APX mode.
Re-ran the blackthund3r tool, it didnt do much so I bailed that. Restarted tab and attempted to load recovery (vol + and power) and it booted normally.
What the hell...
Dopius_Fishius said:
And then most bizarre of all. I declared no progress, rebooted it. It went back to APX mode.
Re-ran the blackthund3r tool, it didnt do much so I bailed that. Restarted tab and attempted to load recovery (vol + and power) and it booted normally.
What the hell...
Click to expand...
Click to collapse
erm for now i would make sure you have all backups of data, cpud etc,.. just incase. you can just sit em on your computer i always try to keep a nandroid of all 3 of my devices each month or so.:good:
edit: and of course keep the link for the thread MD recommended.
Gee. Sounds exactly like mine....
The only thing I haven't tried is an update .zip, but I don't hold out much hope.
Considering parting out at this point....
Yeah, I dont have high hopes that it will last a whole lot longer. Up to this point it has been running Acer OTA updates only, no custom ROMs and no root.
I restarted the tab a little while ago and it went back into APX mode again and stayed there. Some more furious button mashing and attempted restore-mode boots, and it booted normally.
I made the point of wiping it this time using the Vol+ & Power & Rotation Lock trick and its been ok so far.
Dopius_Fishius said:
Yeah, I dont have high hopes that it will last a whole lot longer. Up to this point it has been running Acer OTA updates only, no custom ROMs and no root.
I restarted the tab a little while ago and it went back into APX mode again and stayed there. Some more furious button mashing and attempted restore-mode boots, and it booted normally.
I made the point of wiping it this time using the Vol+ & Power & Rotation Lock trick and its been ok so far.
Click to expand...
Click to collapse
I have a cousin in Jamaica. She might possibly help (chicken foot and some frogs blood...voodoo you know)
Here's What I think.
You got some corrupt data or a partially bad devblock. This might explain the strange behavior on boot.
Like the tab really doesn't know how to boot.
Personally I would do 1 of 2 things at this point. Either;
1. Root that thing, and try running Timmy Deans root back to 3.2. This should reset your partitions back to normal. Then work your way back to an ICS rooted, Bootloader, and custom rom.
2. Leave it alone, and don;t turn the tab off. Clearly some partitions are messed up at this point. The toggle of the lock usually wipes user data. But the core issue is still there.
If it were me, I would pull out the nuclear missile and go for it all.
MD
Moscow Desire said:
I have a cousin in Jamaica. She might possibly help (chicken foot and some frogs blood...voodoo you know)
Here's What I think.
You got some corrupt data or a partially bad devblock. This might explain the strange behavior on boot.
Like the tab really doesn't know how to boot.
Personally I would do 1 of 2 things at this point. Either;
1. Root that thing, and try running Timmy Deans root back to 3.2. This should reset your partitions back to normal. Then work your way back to an ICS rooted, Bootloader, and custom rom.
2. Leave it alone, and don;t turn the tab off. Clearly some partitions are messed up at this point. The toggle of the lock usually wipes user data. But the core issue is still there.
If it were me, I would pull out the nuclear missile and go for it all.
MD
Click to expand...
Click to collapse
Tried the update.zip - nada
Tried timmiedean yesterday, went into Acer Download mode OK, failed....
If dolps is like mien, the first time he tries to go into recovery, it will crash again...
It's baaaack!
Tried blackthunder flash again, failed.
Went to turn off to get out of APX, and it booted!
Now boots, boots to recovery and boots to primary.
I have no explanation.
We will see.
I am suspicious....
tennessee_titan said:
It's baaaack!
Tried blackthunder flash again, failed.
Went to turn off to get out of APX, and it booted!
Now boots, boots to recovery and boots to primary.
I have no explanation.
We will see.
I am suspicious....
Click to expand...
Click to collapse
I told you maaaannnn, go see me cousin in Jamaica maaaannnnn. She do some good things you see
Glad it's running again.
MD
First, is this a SOD?
I can kill it by booting into recovery and get it back by using Blackthunder flash tool to go into APX and letting it sit for 20 minutes or so. Close the program, unplug, reboot and it is back. I would like to use timmiedean (td) and go back to square 1, but it fails at the image detect ( displays ICS 4.0.3 Civato as the current image, a red X for the new image). Has td been proven to work reverting from ICS? Will a boot recovery reflash and a new ROM flash solve this? Is there another way to get out of ICS back to HC?
Any suggestions/comments welcome!
EDIT: I flashed FLEXxx V4. Shut it off, problem still there....
Really frustrated. Trying to use the timmiedean tool, but it requires that the unit be shut off in the middle of the process, which kills it. Does anyone know the whereabouts of the blackthund3r revert tool, or the .apx package for his flash tool. I can't find it...
I'm done with this one. On Ebay for parts.... GONE!!!
Have an A100 now, rooted, unlocked,. on Relix
1 more A500 coming next week
I have an a500 with a thor 3.2 rom. I recently used CWM to reset to factory to install the Thor ICS v170 rom. I got an error when restarting into recovery to install it so I restarted again. There it hung up on the logo. So I restarted into recovery holding the power and volume down, but here is where it goes nuts. Once into recovery, the tablet vibrates nonstop and a Team Rogue logo comes up in the background and gives me errors for reading system data and cache. It gives me menu items listen but doesnt let me do anything and I have to Hold power to power down. Still even restarting doesnt get past the Acer boot logo. Please help me out!
Staples01 said:
I have an a500 with a thor 3.2 rom. I recently used CWM to reset to factory to install the Thor ICS v170 rom. I got an error when restarting into recovery to install it so I restarted again. There it hung up on the logo. So I restarted into recovery holding the power and volume down, but here is where it goes nuts. Once into recovery, the tablet vibrates nonstop and a Team Rogue logo comes up in the background and gives me errors for reading system data and cache. It gives me menu items listen but doesnt let me do anything and I have to Hold power to power down. Still even restarting doesnt get past the Acer boot logo. Please help me out!
Click to expand...
Click to collapse
That's what happens when you run stuff from Dev's that don't adhere to GPL. Undoubtedly some leftover code from whomever it was taken from and "somebody" didn't bother to clean it out all the way. FYI, Team Rogue did ICS development for the Xoom tablet, and also some early CWM work. Guess we know where "somebody" got some code from
Ok, back to your current issue at hand. For starters, you're probably still on an HC Bootloader and probably running a really old version of CWM recovery. If you are going to run ICS or JB roms, I highly suggest you upgrade your bootloader to the patched ICS Unlocked bootloader. Also, I would update to the latest version of CWM. You can get it at his site.
I believe your next rom may be able to run on an HC bootloader, or so I've heard, but your CWM needs to be updated, and that's what probably threw out the errors.
You can find a guide for the unlocked bootloader installation in the Dev Forum. It's stickied.
Hope this fixes your issue. If not, post back.
MD
Staples01 said:
I have an a500 with a thor 3.2 rom. I recently used CWM to reset to factory to install the Thor ICS v170 rom. I got an error when restarting into recovery to install it so I restarted again. There it hung up on the logo. So I restarted into recovery holding the power and volume down, but here is where it goes nuts. Once into recovery, the tablet vibrates nonstop and a Team Rogue logo comes up in the background and gives me errors for reading system data and cache. It gives me menu items listen but doesnt let me do anything and I have to Hold power to power down. Still even restarting doesnt get past the Acer boot logo. Please help me out!
Click to expand...
Click to collapse
All I can say is WOW!!
linuxsociety said:
All I can say is WOW!!
Click to expand...
Click to collapse
Yeah, its strange but doesn't surprise me.
OP, your partitions are also undoubtedly messed up as well. I suppose you didn't by chance write down your UID number did you? You may be able to get by with installing an ICS full update zip. Maybe.
MD
Soo...nothing. is it just a piece of junk now?
Staples01 said:
Soo...nothing. is it just a piece of junk now?
Click to expand...
Click to collapse
I wouldn't think it is 100% bricked, but I'd definitely ask on tegraowners.com since it is from one of their recovery/roms. Guess you may have already asked Thor about the issue though?
I have my cpuid but when i run the dotnetdetector to update the usb doesnt stay connected long at all.
Staples01 said:
I have my cpuid but when i run the dotnetdetector to update the usb doesnt stay connected long at all.
Click to expand...
Click to collapse
Are you trying to manipulate the A500 from a Windows PC or Linux? Notice you said Dotnetdetector, sounds like windows, but not familiar with it exactly. Maybe you could try using a live linux distribution (such as Ubuntu or Fedora) to try to get fastboot/adb and reflash the recovery partition with a known working recovery for A500. The teamrogue thing still puzzles me and I'm just curious if bits of Team Rogue's code has been pieced in with the A500 recovery you are trying to use, or if you may have got a hold of a recovery that was for a different device ? I'm not trying to say that you are a nub and flashed a recovery for the wrong device, but there is a possibility depending on where you obtained the rom from, that it could have been mis-labeled for your device ( but been for a different one) If it was for a diff device it would make sense why you can't do anything with it.
Let me get it straight how this happened.
1. You had CWM installed for A500 and recovery was working fine
2. You used CWM to try to flash a Thor ROM, in which the installation failed.
3. After reboot you have nothing but the Acer logo
4. When you boot back into recovery, it is no longer CWM, but a Team Rogue logo is displayed, and that is all you see?
That's the way I interpret the issue you are having anyway. Can you please send me a link to the ROM that you tried to install that triggered all of this. That way I can see exactly what the installer script attempted to do (because it very well could have tried to flash a diff recovery to your device and failed on something else)
Hope we can get things straightened up for you. Good luck again bud
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?