I posted this in the Android Development Thread under Fuji-Vega. Hope I can get some help with more exposure on my problem.
I think I've busted my Vega. I installed Fuji-Vega V.07, then I wiped the device/factory reset, I then wiped Davlik cache and then I wiped the Battery Stats.
Now its stuck on the Vega bootup animation and it doesn't go any further.
Any suggestions of what to do?
I've shut the device down and powered back on but the same thing happens.
I personally now don't think I should have wiped the caches.
The device Recovery is ClockWorkMod 3.
Help much appreciated.
luckily for you the vega is almost impossible to brick so do a full system restore
http://www.myadventvega.co.uk/full_system_flash_instructions.pdf
If you have a nandroid backup then you can try to restore with the VegaFixer. I wrote a small tutorial how to use it.
C64c said:
I posted this in the Android Development Thread under Fuji-Vega. Hope I can get some help with more exposure on my problem.
I think I've busted my Vega. I installed Fuji-Vega V.07, then I wiped the device/factory reset, I then wiped Davlik cache and then I wiped the Battery Stats.
Now its stuck on the Vega bootup animation and it doesn't go any further.
Any suggestions of what to do?
I've shut the device down and powered back on but the same thing happens.
I personally now don't think I should have wiped the caches.
The device Recovery is ClockWorkMod 3.
Help much appreciated.
Click to expand...
Click to collapse
All fixed now. Many Thanks!!
C64c said:
All fixed now. Many Thanks!!
Click to expand...
Click to collapse
A tip, next time wipe first then flash, not the other way around.
Some ROM have stuff in the data partition that they need and if you wipe after flashing, this stuff is missing when it boots.
VEGA CANNOT BE BRICKED! There's always a way out.
No you have not bricked your Vega it is not possible.
boot into recovery and install the official rom from Advent website by following their instructions. Then reflash your custom rom
Hi Guys,
I don't know if I am in the right thread but I try...
I have kind of the same problem, but with a newly acquired Viewpad 10s (I haven't found any specific section for this tablet in the forum) and I am a true newbie...
I wanted to install the Android Market following the procedure described here:
oudmaijer.com/2010/12/12/android-market-on-pov-mobii-101-tablet/
and after having transfered the market_update0.zip file on my sd-card and applied it through the Software Tool (in Settings menu), the tablet turned off then on.. but I only get a black screen. It won't even show the Android robot picture again.
The stupid thing is that I have no backup rom (the one delivered with the Viewpad 10s) on my computer and I don't even know what I can do (I guess the aforementioned rom for advent would not work)...
Please help! I just want the tablet to work again, whatever rom it uses!
Thank you,
Elena
Try VEGAFixer (a few posts above) to get your tablet back to work without data loss.
If this doesn't fix it, get stock Viewpad 10s ROM and flash it. Get the PDF file from this site as well, so you know how to flash it.
You can as well flash my Gambaro ROM V0.2 ROM. Download the Gambaro ROM V0.2NV version, for this the flash procedure is the same as for stock ROM.
elena007 said:
Hi Guys,
I don't know if I am in the right thread but I try...
I have kind of the same problem, but with a newly acquired Viewpad 10s (I haven't found any specific section for this tablet in the forum) and I am a true newbie...
I wanted to install the Android Market following the procedure described here:
oudmaijer.com/2010/12/12/android-market-on-pov-mobii-101-tablet/
and after having transfered the market_update0.zip file on my sd-card and applied it through the Software Tool (in Settings menu), the tablet turned off then on.. but I only get a black screen. It won't even show the Android robot picture again.
The stupid thing is that I have no backup rom (the one delivered with the Viewpad 10s) on my computer and I don't even know what I can do (I guess the aforementioned rom for advent would not work)...
Please help! I just want the tablet to work again, whatever rom it uses!
Thank you,
Elena
Click to expand...
Click to collapse
Thank you BeeGee_Tokyo!
I followed the instructions of the pdf and downloaded the files from the official link and after having struggled a bit for the reboot procedure (with the timing if the back/power buttons).
Then it went smoothly!
You are a guru BeeGee_Tokyo, thanks again!
I will definitely try your ROM soon too!
Elena
Got same problem few times on my Viewpad 10s. At last I installed market via CWM and finally it works fine.
yioti said:
VEGA CANNOT BE BRICKED! There's always a way out.
Click to expand...
Click to collapse
So I will give it a new try.
It seems mine is broken.
No Advent Vega, but POV Mobii - however using nvflash to put back Stockrom on machine is the same procedure on both.
POV got rooted with this Add-On.
http://forum.xda-developers.com/showthread.php?t=931337
Put CWM on tablet via Recovery Easy Install ( http://android.modaco.com/content/a...d-clockwork-recovery-3-0-2-4-easy-install-v2/ )
and Wireless ADB. (No ADB via USB with POV because OF different USB-behaviour)
Yesterday tab was runnning fine - nothing put on additionally (my Mom is using it) and suddenly restarting the POV only gives a black sreen (backlight is on, but nothing else to see)
Drivers are fine - NVIDIA USB-Boot-recovery driver shown in Win7x64. OS is recognizing the Tablet when switched on with specialkeys connected via USB.
Running ****POV-Full-Flash.exe or ****Vega.exe gives the same message in DOS-BOX:
"Unknown device found"
Press enter to continue
So connection s good, but for whatever reason device is not recognized as vaild.
Did flash Stock-Rom 2 days before this way succesfully. (purchased as returned but new article and wanted to start from clean ROM)
I am having a Nadroid-Backup, thought easy cake, StockRom - CWM and restore nandroid - but I am totally stuck...
Any hint to get out of there welcome..
I don`t wanna t be the first who succeeded in .. *Grmpf*
For whatever reason flashing the StockRom via nvflash was possible now - nvflash accepted the connected device.
So I am not the first one who brickes his POV/Vega
HELP Hard Brick Novice
I thought I could do it I really did... I cant, I cant hack, or do anything with code... its just not me.
Today I tried to flash my Viewsonic Viewpad 10 with a rom (vegan tab) and completely bricked the device. I see posts about restoring the system using an SD card... problem the system runs on the internal SD card is there anything I can do?
Ok, I'm usually a lurker, but I need help.
HAppens that I was trying VegaComb 1.5.2 (works great, but I NEED flash) and decided to go back to CorvusV5. I flashed correctly, or so I thought, but now my Vega loops on the Boot Logo.
I've tried to get it into NVRecovery, but the screen just flashes with light for 2-3 secs and then the device turns off everytime I repeat the sequence. Additionally, the PC does not seem to recognize the device at any time.
Some help here?
Thanks!
jhondidfool said:
Ok, I'm usually a lurker, but I need help.
HAppens that I was trying VegaComb 1.5.2 (works great, but I NEED flash) and decided to go back to CorvusV5. I flashed correctly, or so I thought, but now my Vega loops on the Boot Logo.
I've tried to get it into NVRecovery, but the screen just flashes with light for 2-3 secs and then the device turns off everytime I repeat the sequence. Additionally, the PC does not seem to recognize the device at any time.
Some help here?
Thanks!
Click to expand...
Click to collapse
screen does not come on in nvflash mode your doing it wrong
right turn of vega (hold power for 6 secs)
put vega on charge connect to computer via usb
hold back for two seconds
hold power until computer bleeps recognises device
release power then back
ensure correct drivers installed
run recovery program
Edit: You will never brick your vega no one ever will if it is at all possible it will be an extremely experienced dev doing something extremely complicated you cant do it from CWM im not annoyed just informing you all
Fixed! thanks!
what most people forget, including me, is that you need a minimum 60% charge before you can flash the stock rom using the power button method, so you can press away all you want, but if it's not charged, it's not happening
Although I followed all above instructions, I can not restore my Vega.
Had it off for a couple of days, tried to switch it on and it stuck in blank screen (screen on). Have it on the charger but light indicates battery is full (thought that battery could be dead).
Used the Advent Vega Driver Installer, drivers are installed properly, but can not enter recovery mode at all, every time it goes into this "blank screen" state with the screen being on.
Any ideas?
have you installed vega tools?
Hello. I have an Acer Iconia Tab A200, and recently I tried a factory reset. However, due to my meddling with system files, it won't reset.
I've tried to do a hard reset (Power on, Volume+, Orientation lock switch) but it says the following:
Erasing Userdata...
Erasing Cache...
It then reboots, and does nothing. It hangs on the Acer logo.
When trying to go into recovery (Power On, Volume-), it says the following:
Erasing Cache before SD update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified fail ...
Now, I mentioned that I meddled with the System Files. Here is what I did:
1. Removed unwanted Vendor Apps
2. Removed the DEFAULT LAUNCHER <-- I think this plays a big part in this
3. Placed a CUSTOM LAUNCHER in the VENDOR APPS FILE
4. Did a FACTORY RESET
My brother is more techy than me, so he tried to fix it. However, he somehow re-locked the bootloader and even replaced the bootloader with a newer version.
I talked to Acer Support claiming it's system files corrupted itself, but they won't fix it unless I also pay to fix my cracked screen. I'm willing to do so, but hey, I'd like to see if I could save $120. I don't mind the cracked screen.
NOTES:
The Acer Iconia Tab A200, along with their other tablets, has a USB port. I can probably load stuff from there somehow, but not sure.
It is a 16GB model with a 32GB Class 10 MicroSD card in it.
Any ideas? All help is appreciated.
Vuciz said:
Hello. I have an Acer Iconia Tab A200, and recently I tried a factory reset. However, due to my meddling with system files, it won't reset.
I've tried to do a hard reset (Power on, Volume+, Orientation lock switch) but it says the following:
Erasing Userdata...
Erasing Cache...
It then reboots, and does nothing. It hangs on the Acer logo.
When trying to go into recovery (Power On, Volume-), it says the following:
Erasing Cache before SD update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified fail ...
Now, I mentioned that I meddled with the System Files. Here is what I did:
1. Removed unwanted Vendor Apps
2. Removed the DEFAULT LAUNCHER <-- I think this plays a big part in this
3. Placed a CUSTOM LAUNCHER in the VENDOR APPS FILE
4. Did a FACTORY RESET
My brother is more techy than me, so he tried to fix it. However, he somehow re-locked the bootloader and even replaced the bootloader with a newer version.
I talked to Acer Support claiming it's system files corrupted itself, but they won't fix it unless I also pay to fix my cracked screen. I'm willing to do so, but hey, I'd like to see if I could save $120. I don't mind the cracked screen.
NOTES:
The Acer Iconia Tab A200, along with their other tablets, has a USB port. I can probably load stuff from there somehow, but not sure.
It is a 16GB model with a 32GB Class 10 MicroSD card in it.
Any ideas? All help is appreciated.
Click to expand...
Click to collapse
Do you have access to any a200 Update roms? Sometimes, you can pull the update.zip from the rom, place it on your ext sd card, reboot holding Vol+ and PWR, and it might install.
MD
Moscow Desire said:
Do you have access to any a200 Update roms? Sometimes, you can pull the update.zip from the rom, place it on your ext sd card, reboot holding Vol+ and PWR, and it might install.
MD
Click to expand...
Click to collapse
I have searched for some A200 ROMs, but can't find any that work using that method. I'm open for ANY Acer A200 official ROM, then simply updating using OTA. I tried an Acer A200 Recovery Pack I found. It is the exact stock Honeycomb image, but it didn't go. It always says recovery verified fail. I cannot unlock the BootLoader either.
Stockimage flashable while having bricked /DATA Partition
Hi Vuciz,
do you still have the issue with your bricked A200 ?
I got the same problem with mine, the only solution was to send it to repair, it seems the storage controller chip has some bug which destroyed the /DATA partition unrecoverable.
if you need to revert your Tablet to an locked bootloader you have to download an StockRom and modify it by removing the partition check (called "assert") in the update script.
please send me an message if you need further assistance.
regards and good luck with your tab.
Nickbert said:
Hi Vuciz,
do you still have the issue with your bricked A200 ?
I got the same problem with mine, the only solution was to send it to repair, it seems the storage controller chip has some bug which destroyed the /DATA partition unrecoverable.
if you need to revert your Tablet to an locked bootloader you have to download an StockRom and modify it by removing the partition check (called "assert") in the update script.
please send me an message if you need further assistance.
regards and good luck with your tab.
Click to expand...
Click to collapse
Yes I do. However the screen is also cracked so they want me to pay for that. Which I'm unable to do at this time.
anything I do, fails
Vuciz said:
Yes I do. However the screen is also cracked so they want me to pay for that. Which I'm unable to do at this time.
Click to expand...
Click to collapse
I also have this tablet. I bought it for 20 bucks because the screen was cracked. replaced the screen and then found out that the bootloader was trashed. I've done almost everything I can think of to fix it. Used APX mode to get UID from ubuntu, tried to use that UID to get sbk, got the SBK and then tried using blackthunder's tool got connection failure, tried using babsector same thing, even went in ubuntu, with tablet in manual apx mode for all three and when I attempt to reflash the bootloader, all I get is that command failure message with a nvflash connection failed nv error 0x30011 message and when that happens in windows, the tablet disappears from device manager, and in ubuntu when I run nvflash with the sbk function --sbk XXXX and so on, I get the command sent failure message, and then when i rerun lsusb, the nvidia device that represents my tablet in apx mode that showed before is no longer listed unless i reboot the tablet in apx mode again. If i boot it normally, the acer logo appears and then goes to the little animation and then the iconia tab screen and thats it. I've tried attempting to flash the bootloader from that screen which i know probably wasn't going to work anyways. If anyone has any advice on something I've missed, or anything that could help, i'll all eyes. thanks in advance.
twanhines said:
I also have this tablet. I bought it for 20 bucks because the screen was cracked. replaced the screen and then found out that the bootloader was trashed. I've done almost everything I can think of to fix it. Used APX mode to get UID from ubuntu, tried to use that UID to get sbk, got the SBK and then tried using blackthunder's tool got connection failure, tried using babsector same thing, even went in ubuntu, with tablet in manual apx mode for all three and when I attempt to reflash the bootloader, all I get is that command failure message with a nvflash connection failed nv error 0x30011 message and when that happens in windows, the tablet disappears from device manager, and in ubuntu when I run nvflash with the sbk function --sbk XXXX and so on, I get the command sent failure message, and then when i rerun lsusb, the nvidia device that represents my tablet in apx mode that showed before is no longer listed unless i reboot the tablet in apx mode again. If i boot it normally, the acer logo appears and then goes to the little animation and then the iconia tab screen and thats it. I've tried attempting to flash the bootloader from that screen which i know probably wasn't going to work anyways. If anyone has any advice on something I've missed, or anything that could help, i'll all eyes. thanks in advance.
Click to expand...
Click to collapse
Just so you know, I was never able to resolve this issue.
Hello,
I search help for my Acer Iconia Tab A200.
During a flash with TWRP, it block and I have to set my A200 off using Power.
And then, my A200 don't work, don't vibrate.
I try :
Reset + Power : nothing, no vibration
Power + Vol- : nothing, no vibration
Power + Vol+ + switch : same result
Connected to PC : adb devices : nothing
All commands adb or fastboot : waiting for device
I don't know what to do...
where can I send my Acer tablet to fixed stuck on bootloader
hello I have an acer iconia 200 stuck bootloader cant find anyone to fix it. Acer wont touch it unless its under warrenty! my 90 day store warrenty has been way past! taken to 2 local computer tech both told me I needed to send it back to acer but I cant! so what can ido i or where can I send it?? anyones time and effort would greatly appreicated!!! thanx for your time
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?