Database Users

Solved:I guess I'm stuck in boot loop....now what?

Ok guys..... newbie here .... literally I'm new to Boot unlocking, root, Flashing etc.
Anyway I have followed this forum for so long that I decided to take plunge yesterday and get my hands dirty.
Here is what I did:
Unlock bootloader, root and install recovery on my Atrix 4G. Atrix was @ 2.3.4 and 4.5.91 during unlocking & root.
Rebooted the phone and everything seems to be in place. Atrix loaded like the way I bought it 7 months back. No problem until now.
Also created a restore folder on my external SD. Worked fine and was successful in creating backup with time stamp
Now here are my steps and subsequent issues that I'm facing:
1. Downloaded CM9 zip file from this thread(http://forum.xda-developers.com/showthread.php?t=1500535) along with Gapps to my external SD
2.Entered recovery mode during bootup and tried to flash CM9 and Gapps. Flashing seem to have gone well and completed (note I did not do clear data, clear cache or clear dalvik cache under advanced options being a newbie)
3. Reboot the phone and can only see red Moto logo and unlocked on top. Left for about 5 minutes and nothing happened.
4.Did a battery pull and entered recovery mode. wiped data, cache & cleared dalvik cache
5.Went to Install zip from sdcard option and tried to reflash CM9. Flashing seems to have gone well and completed
6. Reboot phone and again can only see Moto Red logo with unlock on top and nothing more.
7.Battery pull followed by recovery. But This time I tried to restore from my external SD. also wiped data, cache & dalvik cache
8.Restore took about 3 minutes and completed.
9.Reboot the phone. Now the phone boots and goes to Rethink possible screen and get sstuck.
10. Left it for 1 hr....nothing.
11.tried steps 7-9 again and still stuck in "Rethink possible" screen during boot.
What did I do wrong? Did I soft brick the phone? I can still enter recovery mode and read my internal and external SD and can see all files. i hope I didn't brick my phone doing this. If I did, I would regret!
Here are my options:
1.Try a stable ROM like CM7 and see what happens. I didn't want to do too much damage so haven't tried this option yet.
2.I know there is a way to hide 'unlock' during boot up (if someone can point to it obviously). Hide the 'unlock' and return the phone to ATT and tell them that phone would not boot after 2.3.6 update and get a refurbished one
Please let me know what your thoughts are. I'm currently crapping on my pants
Edit: I just tried Newtrino rom and stuck @ Moto screen which says unlock.
Edit 3/4/2012: Please go to the last post for the solution. Tenfar's CWM is old and cannot deal with latest ROMs. Use ROMRACERS latest CWM or touch based Koush's CWM for future ROM flashing.
Old CWMs will give you sleepless nights!

Ok tried restore again after wiping data, cache & dalvik cache.
Now after reboot, My Moto Logo screen says unlock and just starts flashing.
I can still get into recovery......
can someone please help me......

What you can do is: install a "stable" ROM of Gingerbread:
--Go in recovery, put a .zip of the ROM on your sdcard (with your computer), and after wiping data, install it .zip.
--Or you install a new ROM with fastboot
Anyway, be careful with your battery, because if it is empty, with no ROM on your phone, it'll be crap!

vsg005 said:
What you can do is: install a "stable" ROM of Gingerbread:
--Go in recovery, put a .zip of the ROM on your sdcard (with your computer), and after wiping data, install it .zip.
--Or you install a new ROM with fastboot
Anyway, be careful with your battery, because if it is empty, with no ROM on your phone, it'll be crap!
Click to expand...
Click to collapse
thank you for your response. However I tried that already Nutrino GB ROM. Again, I would go to 'M' screen which says unlocked and its stuck there for ever.
I used tenfar's CWM. Not sure if I need to use any other CWM. Also since my phone doesn't boot, I'm not sure how I can install any other CWM

Masterguy said:
thank you for your response. However I tried that already Nutrino GB ROM. Again, I would go to 'M' screen which says unlocked and its stuck there for ever.
I used tenfar's CWM. Not sure if I need to use any other CWM. Also since my phone doesn't boot, I'm not sure how I can install any other CWM
Click to expand...
Click to collapse
Don't worry, soft bricks are easy to recover on the Atrix thanks to us being able to access fastboot.
For flashing a new recovery:
While your phone is off, press Volume Up + Power to power up, then release when a menu appears on your screen and navigate with volume down until you see Fastboot, select it with the volume up key.
Get the necessary files for fastboot, place them all in a folder called "moto" in your C: drive, and type in the following in a cmd window (assuming you're using windows and that the recovery image is called recovery.img):
C:/Moto> fastboot flash recovery recovery.img
C:/Moto> fastboot -w
C:/Moto> fastboot reboot
Now access your recovery wipe dalvik cache, cache, factory reset and then flash a new ROM. It SHOULD boot without issues. I personally use Koush's Clockworkmod Touch, also remember that Neutrino tends to get "stuck" sometimes after the first attempt to boot and requires a battery pull and then you try to boot again. (It takes a while)

littleemp said:
Don't worry, soft bricks are easy to recover on the Atrix thanks to us being able to access fastboot.
For flashing a new recovery:
While your phone is off, press Volume Up + Power to power up, then release when a menu appears on your screen and navigate with volume down until you see Fastboot, select it with the volume up key.
Get the necessary files for fastboot, place them all in a folder called "moto" in your C: drive, and type in the following in a cmd window (assuming you're using windows and that the recovery image is called recovery.img):
C:/Moto> fastboot flash recovery recovery.img
C:/Moto> fastboot -w
C:/Moto> fastboot reboot
Now access your recovery wipe dalvik cache, cache, factory reset and then flash a new ROM. It SHOULD boot without issues. I personally use Koush's Clockworkmod Touch, also remember that Neutrino tends to get "stuck" sometimes after the first attempt to boot and requires a battery pull and then you try to boot again. (It takes a while)
Click to expand...
Click to collapse
Many people also seem to have suggested RACEROM CWM. Which one would you suggest? I'm so nervous about all this now. Just have this butterfly in my stomach

flash the latest recovery and wipe everything in recovery and flash neutrino again. It should work after that. try neutrino 2.2 though. 2.5 still has it's kinks.

1st off, relax. It's difficult to brick your phone from this point Just don't get any bright ideas with .sbfs lol.
As others have said, make sure you're on latest recovery.
Question: are you installing from internal or external SD? Internal is recommended for flashing most ROMs.
Sent from my MB860 using xda premium

Masterguy said:
Many people also seem to have suggested RACEROM CWM. Which one would you suggest? I'm so nervous about all this now. Just have this butterfly in my stomach
Click to expand...
Click to collapse
As someone else said, the ONLY thing you should NEVER do is flash an .sbf or go through an OTA update, that's a surefire way to hard brick your phone. From this point on it's VERY DIFFICULT to completely brick your phone using software only.
RomRacer's CWM is based I think on v5.0.2.7? Koush's latest recovery is v5.8.1.5. I honestly couldn't name any tangible differences other than the touch interface, which is the reason I use it in the first place. (I hate mashing volume keys like a madman) It really doesn't matter which CWM you use, but when I soft bricked my phone I recovered with CWM Touch.
I would recharge your battery to 100% before trying to recover it, as that is one less headache to worry about, but if your phone starts saying 'Battery is too low to flash', do not panic, you only need a USB cable you don't mind sacrificing (doesn't have to be new). I will go into detail in case you actually need to do this.
Just make sure you use the fastboot -w command and wipe EVERYTHING through CWM before trying to flash anything else.

Solved:boot loop issue
littleemp said:
As someone else said, the ONLY thing you should NEVER do is flash an .sbf or go through an OTA update, that's a surefire way to hard brick your phone. From this point on it's VERY DIFFICULT to completely brick your phone using software only.
RomRacer's CWM is based I think on v5.0.2.7? Koush's latest recovery is v5.8.1.5. I honestly couldn't name any tangible differences other than the touch interface, which is the reason I use it in the first place. (I hate mashing volume keys like a madman) It really doesn't matter which CWM you use, but when I soft bricked my phone I recovered with CWM Touch.
I would recharge your battery to 100% before trying to recover it, as that is one less headache to worry about, but if your phone starts saying 'Battery is too low to flash', do not panic, you only need a USB cable you don't mind sacrificing (doesn't have to be new). I will go into detail in case you actually need to do this.
Just make sure you use the fastboot -w command and wipe EVERYTHING through CWM before trying to flash anything else.
Click to expand...
Click to collapse
Thanks I was able to fix my boot up issue using ROMRACERS CWM. I didn't use any command prompt or anything. I just downloaded zip file from this thread, entered recovery mode -->Install Zip from SD card --> Chose ROMRACERS zip --> it automatically flashed the recovery and I then rebooted recovery under advanced options.
After that Wiped data,cache & Dalvik Cache and proceeded to install CM9 and it booted up up flawlessly.
I'm kind of surprised that tenfar didn't add a not to use his CWM as the latest ROMs use latest ext format.
That seems to be issue. However, I'm pleased with your guidance and final output. Thanks a lot dude.

Masterguy said:
Thanks I was able to fix my boot up issue using ROMRACERS CWM. I didn't use any command prompt or anything. I just downloaded zip file from this thread, entered recovery mode -->Install Zip from SD card --> Chose ROMRACERS zip --> it automatically flashed the recovery and I then rebooted recovery under advanced options.
After that Wiped data,cache & Dalvik Cache and proceeded to install CM9 and it booted up up flawlessly.
I'm kind of surprised that tenfar didn't add a not to use his CWM as the latest ROMs use latest ext format.
That seems to be issue. However, I'm pleased with your guidance and final output. Thanks a lot dude.
Click to expand...
Click to collapse
Thank you sooo much. I was having this exact problem. I did what you suggested and my phone works. Thanks!

Flashing Rom always ends in boot loop?

I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.

By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app

redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm

could that be the problem? that my cwm is just outdated already?

No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium

CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.

Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7

am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?

crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.

simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?

I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?

spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?

Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.

dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?

If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2

Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!

[Q] What to do after a brick?

Hello everyone.
I hope you can help me.
I had an A500 bricked spontaneously (I was checking Twitter, the screen frozen, I turned off the tablet and when I turned it on again, it stucked on Acer logo) so I used the guide to recover recovery (this: http://forum.xda-developers.com/showthread.php?t=1751978, because I rooted my tablet but I didn't install recovery).
Everything was ok, I flashed the V7-Thor v1.7.3 but when I tried to install stock ROM of ICS (wipe data and cache), the tablet got "re-bricked" and only enter in APX mode.
Then I reflashed and installed V8-Thor_1.7.3_recovery and I tried to install Acer_AV041_A500_1.054.00_WW_GEN1-DEODEXED-FULLROOT through update.zip (turned on the tablet in recovery --> Install from zip file --> Install zip file from SD card --> update.zip, then it said "Installed" and I rebooted the tablet, but it stuck on "Booting primary kernel image"...
What I'm missing or doing wrong? :/
What should I do to run ICS in my tablet again?
I'm not familiarized with the ROMs, Recoverys or flash... sorry if my question is stupid or something, but before this I never moved anything to my tablet (except for root it).
And sorry too for my bad English.

Mafvtapatio said:
Hello everyone.
I hope you can help me.
I had an A500 bricked spontaneously (I was checking Twitter, the screen frozen, I turned off the tablet and when I turned it on again, it stucked on Acer logo) so I used the guide to recover recovery (this: http://forum.xda-developers.com/showthread.php?t=1751978, because I rooted my tablet but I didn't install recovery).
Everything was ok, I flashed the V7-Thor v1.7.3 but when I tried to install stock ROM of ICS (wipe data and cache), the tablet got "re-bricked" and only enter in APX mode.
Then I reflashed and installed V8-Thor_1.7.3_recovery and I tried to install through update.zip (turned on the tablet in recovery --> Install from zip file --> Install zip file from SD card --> update.zip, then it said "Installed" and I rebooted the tablet, but it stuck on "Booting primary kernel image"...
What I'm missing or doing wrong? :/
What should I do to run ICS in my tablet again?
I'm not familiarized with the ROMs, Recoverys or flash... sorry if my question is stupid or something, but before this I never moved anything to my tablet (except for root it).
And sorry too for my bad English.
Click to expand...
Click to collapse
I think where you went wrong was choosing "install zip file from sdcard >update.zip"
Go back into recovery again > install from zip file > Choose zip from SD card (
if the file is on your micro sd card)
You should see a list of all your files and choose your rom file:
Acer_AV041_A500_1.054.00_WW_GEN1-DEODEXED-FULLROOT.zip
Once its done, Stay in recovery and go to: Wipe Menu and do all the wipes there
Data -cache and dalvi-cache then reboot
Once you're all set up and before you reboot again, make sure there is not an "update.zip" on your sdcard - if you boot to recovery it may flash automatically and you will end up "stuck" again
good luck
dibb

dibb_nz said:
I think where you went wrong was choosing "install zip file from sdcard >update.zip"
Go back into recovery again > install from zip file > Choose zip from SD card (
if the file is on your micro sd card)
You should see a list of all your files and choose your rom file:
Acer_AV041_A500_1.054.00_WW_GEN1-DEODEXED-FULLROOT.zip
Once its done, Stay in recovery and go to: Wipe Menu and do all the wipes there
Data -cache and dalvi-cache then reboot
Once you're all set up and before you reboot again, make sure there is not an "update.zip" on your sdcard - if you boot to recovery it may flash automatically and you will end up "stuck" again
good luck
dibb
Click to expand...
Click to collapse
Thanks! I did it and it worked, but after the reboot the tablet only shows the animated android logo... what's the problem? The ROM?
When I did the "Wipe data" it said "Formatting data" and after "Skipping erase of /data/media". I checked with the "Mount and Storage" menu in recovery and seems like my data before the brick's still in the internal storage of the tablet... is that normal?

EDIT: what version of cwm to have now? If its not 1.7.3 then go ahead and reflash the v8
Mafvtapatio said:
Thanks! I did it and it worked, but after the reboot the tablet only shows the animated android logo... what's the problem? The ROM?
When I did the "Wipe data" it said "Formatting data" and after "Skipping erase of /data/media". I checked with the "Mount and Storage" menu in recovery and seems like my data before the brick's still in the internal storage of the tablet... is that normal?
Click to expand...
Click to collapse
Yes it is - keeps your data intact but 'resets' the rom to like it is when you first flash, there is an option to wipe data/media if you wish to - theres a toggle to enable it but on every boot to recovery it will be disabled again...
You can try another flash of the rom itself otherwise reflash the v8 bootloader.
Do you have access to "fastboot mode" power vol down - just wondering
dibb

dibb_nz said:
EDIT: what version of cwm to have now? If its not 1.7.3 then go ahead and reflash the v8
Yes it is - keeps your data intact but 'resets' the rom to like it is when you first flash, there is an option to wipe data/media if you wish to - theres a toggle to enable it but on every boot to recovery it will be disabled again...
You can try another flash of the rom itself otherwise reflash the v8 bootloader.
Do you have access to "fastboot mode" power vol down - just wondering
dibb
Click to expand...
Click to collapse
I tried to reflash the same ROM, but this time nothing happened, again only says "Booting primary kernel image"... a question, if I try to flash a stock ROM (like Acer_A500_1.031.00_WW_GEN1.zip from the post of stock roms)... it will let my tablet again only in APX mode when I turn on it, right?
And I see the option "Fastboot mode" when I turn on the tablet holding Vol +.
About your question I don't know how to answer, I flashed V8-Thor_1.7.3_recovery... is that a CWM?
In the top it says CWM Recovery v5.5.0.x(thor2002ro/digetx rev 1.7.3) Iconia A50x...

Mafvtapatio said:
a question, if I try to flash a stock ROM (like Acer_A500_1.031.00_WW_GEN1.zip from the post of stock roms)... it will let my tablet again only in APX mode when I turn on it, right?
Click to expand...
Click to collapse
sorry, not sure I understand your question...are you saying you're now stuck in apx mode - black screen power light on?
There are 2 types of stock rom on here....
1) Official Acer EUU or OTA roms
2) Official Stock roms which are Custom - pre-rooted and able to flash CWM etc -
If you flash one of the Acer EUU or OTA roms you will lose CWM and Root
To be honest - with your tab "spontaneously" booting and being stuck on the acer logo and the issues that have followed - its sounding more and more like a faulty chip - this is something that only acer can fix...I could be wrong about this and I hope I am...but something is just not feeling right...
- you still have cwm and access to fastboot - thats a bonus - maybe do a complete format thru CWM of data/media, system (and flexrom if its there) then try to flash a rom again - if it still won't flash AND if you're not stuck in apx mode then I think you'd be best to download an official update.zip - from Blackthund3rs thread here this one -
Acer_AV041_1.054.00_WW_GEN1:
Once you've d/l'ed it...try opening it if you can't then it will need decrypting the instructions for this are in the OP..
Once you have extracted the "update.zip" and have it on your sdcard - flash via CWM
good luck
dibb

dibb_nz said:
EDIT: what version of cwm to have now? If its not 1.7.3 then go ahead and reflash the v8
Yes it is - keeps your data intact but 'resets' the rom to like it is when you first flash, there is an option to wipe data/media if you wish to - theres a toggle to enable it but on every boot to recovery it will be disabled again...
You can try another flash of the rom itself otherwise reflash the v8 bootloader.
Do you have access to "fastboot mode" power vol down - just wondering
dibb
Click to expand...
Click to collapse
What do you mean "If if its not 1.7.3"? Are there problems with flashing the bootloader with 1.7.3?

no, no, not at all, i meant if he didnt have that version to reflash v8 to get it
oops clicked wrong button
he said he flashed stock rom and ended up with dead android = stock recovery

A500 V8 booting primary kernel image
dibb_nz said:
no, no, not at all, i meant if he didnt have that version to reflash v8 to get it
oops clicked wrong button
he said he flashed stock rom and ended up with dead android = stock recovery
Click to expand...
Click to collapse
Hello everyone!
I have a similar issue whith my a500. but i can restore the backup i did of my honeycomb sistem in cwm (i have acess)
aftter making the backup i have flashed V8-Thor_1.7.3_recovery.a500apx in apxflashtool in order to get ics boot loader and install ICS roms.
so far so good after the flash i had already a ICS rom in my sd card redy to flash so imediatly after V8 flash entered cwm and did clean format and wipe all. Next installed the rom (aroma instalation) no problems what so ever. After instalation is finished reboted and now im stuck on skilax v8 bootloader boting primary kernel image
i tried the folowing
- chage kernel multiboot fix partitions redo clean format etc etc etc (ALL THE STEPS)
-many other ics jellybean rooms (all of the install but dont boot)
- honey comb rooms install and BOOT normaly.
at this point thought maybe it was a bad V8 flash and decided to reflash the V8-Thor_1.7.3_recovery.a500apx
Now the flash tool can get pass uploading image phase.
i have correct sbk and cpuuid since i had to recover last week from boot verified failed error and use the flash tool whith correct sbk to recover the tablet with sucess.
So basicly im stuck wit
h my honeycomb rom backup or other HC roms
any news on this subject?

cybersaicho said:
Hello everyone!
I have a similar issue whith my a500. but i can restore the backup i did of my honeycomb sistem in cwm (i have acess)
aftter making the backup i have flashed V8-Thor_1.7.3_recovery.a500apx in apxflashtool in order to get ics boot loader and install ICS roms.
so far so good after the flash i had already a ICS rom in my sd card redy to flash so imediatly after V8 flash entered cwm and did clean format and wipe all. Next installed the rom (aroma instalation) no problems what so ever. After instalation is finished reboted and now im stuck on skilax v8 bootloader boting primary kernel image
i tried the folowing
- chage kernel multiboot fix partitions redo clean format etc etc etc (ALL THE STEPS)
-many other ics jellybean rooms (all of the install but dont boot)
- honey comb rooms install and BOOT normaly.
at this point thought maybe it was a bad V8 flash and decided to reflash the V8-Thor_1.7.3_recovery.a500apx
Now the flash tool can get pass uploading image phase.
i have correct sbk and cpuuid since i had to recover last week from boot verified failed error and use the flash tool whith correct sbk to recover the tablet with sucess.
So basicly im stuck wit
h my honeycomb rom backup or other HC roms
any news on this subject?
Click to expand...
Click to collapse
Yes just one question what is - " chage kernel multiboot "???? Sounds dodgy
You can boot to fastboot mode then do an erase of data and cache, see if that helps for a start....
Do you stil have recovery and can you still restore your HC backup?
I have seen a post or two where tabs can only boot HC Roms and no ICS
It "maybe" the dreaded hardware fault - you might be best to d/l the babsector.rar and run that - it will give you a proper error if theres something wrong - can get it from the root guide in my sig. Give me a minute or two and I'll post some steps in using it
---------- Post added at 09:12 AM ---------- Previous post was at 08:53 AM ----------
How to use babsector.rar
Download and extract the babsector.rar to a folder on your PC
Turn your tab off and put it in apx mode manually. Press and hold reset button, hold power for 3 secs after the light comes on and release it, after another second release the reset button. Your screen is black and the power light is on.
Connect your tab to your PC
Navigate to the babsector folder and click on 501 A.bat, when its done
Reboot into recovery
Go to Mounts and Storage and Format System twice and Power Off
Go back into apx mode and run 501 B.bat
Reboot into recovery and do the wipes and flash your rom
Reboot

[Q] A500 hangs at booting primary kernel image

My Acer Iconia A500 was frozen, I turned it off by holding the power button, since then, I can not reboot the tab, it hangs at booting primary kernel image.
I have Skrilax_CZ V8 bootloader, CWM recovery 1.7.3, and the Flex-Resurrection_Rev1-Aroma-Public Rom.
-----------------------
I searched here, tried the methods by Moscow Desire
"Boot to recovery, and this time, do all your wipes
Wipes Menu
a. wipe Data/factory reset
b. wipe cache
c. wipe Dalvik
Go to Mounts and storage
a. Format system
b. Format Flexrom
Install rom, and make sure it's a rom with an ICS kernel.
As a last chance if the above normal things don;t work,
you may have corrupted data somewhere, and in this case, go to Backup and Restore and toggle Data Media."
------------------------
And tried method by Skrilax_CZ
"You can also wipe userdata from fastboot: "fastboot erase userdata".
-----------------------
I did it several times, after installed the Flex Rom, ( I also tried the Lightspeed_4.8,) it still stuck on the booting primary kernel image, What should be my next step?
I saw somewhere Dibb_nz mentioned that re-flash the BL, recovery.img, not sure if I should try. I do have the CPUID and SBK numbers.
Thanks for your help, anyone out there.

I'm having the exact same problem. I tried what you did, and it still didn't work. This is my first time flashing, so I'm not sure what to try next. I do have one idea - I thought the ROM did have a kernal, so I didn't flash one. I'm going to search for one and try that.

I switched to Skrilax's V9 bootloader thinking that might help but it didn't. When I do a recovery with the back up of my normal rom I made before flashing then and only then can I get past the bootloader. The backup says there's an error when recovering my data though, so I'm going to have to start over from fresh either way.
Any help would be greatly appreciated. I've been at this for over 7 hours now.

Run babsector file, download and instructions here http://forum.xda-developers.com/showthread.php?p=35500589
Sent from my GT-I9300 using Tapatalk 4

dibb_nz said:
Run babsector file, download and instructions here http://forum.xda-developers.com/showthread.php?p=35500589
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for replying. I went back to the normal ota rom from Acer, but will keep this in my notes if I try it again.

OS wiped accidentally from TWRP recovery

I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Please help.
Thanks.

Kalaxy said:
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Please help.
Thanks.
Click to expand...
Click to collapse
Just flash it from custom recovery, so download it into ur phone go to recovery and simply flash it and all should be good.
Sent from my Nexus 6P using Tapatalk

Exiwolfman said:
Just flash it from custom recovery, so download it into ur phone go to recovery and simply flash it and all should be good.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
How do I download it to my phone if I cannot boot into it. Is there any way I can copy a zip file (rom) onto the phone's internal memory.?

Your phone should boot into recovery, so as long as it goes on and boots all u do u is use ur pc to move file over and flash it...
Sent from my Nexus 6P using Tapatalk

Kalaxy said:
How do I download it to my phone if I cannot boot into it. Is there any way I can copy a zip file (rom) onto the phone's internal memory.?
Click to expand...
Click to collapse
Boot into bootloader (hold power and system on), flash the though recovery through adb, mount your .zip,, flash your .zip through recovery. Sorry if that doesn't make sense, I've been drinking with the roommates, lol.
Edit: if that doesn't work, send me an IM and I will help you in the morning
Sent from my Huawei Nexus 6P using XDA Labs

Which state is your phone in right now? Is it bootlooping or in recovery?
Sent from my HTC 10 using Tapatalk

The same thing happened to me also! The whole /data (incl. sdcard) partition went corrupt (showed up in TWRP as eemc instead of ext4) & the /vendor failed to mount.
First I had to repair the /data partition (unfortunately the data was lost, as it repaired to a blank partition). I ended up having to go home (was at work at the time) & hook the phone up to the PC & download the ROM & transfer it onto the sdcard. I'm not entirely sure why/how this happened, but I believe it was because a corrupt vendor IMG. Although that theory doesnt include why the /data partition corrupted, it only explains why the /vendor partition failed to mount.

Fastboot flash system system.img
?

removed

I have the same issue. The problem is, that my computer will not recognize the phone in bootloader mode or in recovery mode(MTP enabled). How can install usb drivers without being able to boot into phone OS???? I've tried Nexus Toolkit with no success. Please help?

Have a look here how to load in bootloader, flash, etc.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.

dbroer91884 said:
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
Click to expand...
Click to collapse
Hi... Just boot into recovery and reflash system.img from the factory image of your choice in bootloader with fastboot. Also flash the vendor image from the same factory image. Done...
Or reflash the whole package with flash all (manually is better imho). But you'll waisted time... Let your phone reboot into Android and you'll have your internal storage back.

5.1 said:
Hi... Just boot into recovery and reflash system.img from the factory image of your choice in bootloader with fastboot. Also flash the vendor image from the same factory image. Done...
Or reflash the whole package with flash all (manually is better imho). But you'll waisted time... Let your phone reboot into Android and you'll have your internal storage back.
Click to expand...
Click to collapse
Thats what I thought. JUst wanted to make sure I could get into bootloader still

dbroer91884 said:
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
Click to expand...
Click to collapse
Yes TWRP has a reboot to bootloader option available. So you can access fastboot via bootloader to flash the necessary images. Just don't forget to re flash TWRP image again in case the stock recovery image was flashed beforehand.

The odd thing was that I did choose that option to boot to bootloader in twrp and it didn't work. I ended up having to reboot to bootloader manually. Not a big deal. All is working now, but thought that was interesting.

Kalaxy said:
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Click to expand...
Click to collapse
Exactly which partitions did you wipe? system? data? Internal Storage (userdata)? all of the above? Hopefully you did not wipe userdata (all your stuff). Were you on a stock ROM? You should be able to d/l the Google image from the same build you were on, extract system and data and fastboot flash those. Don't flash userdata. All your stuff should be there. Follow the tutorial on how to set up fastboot and selectively flash partitions.
---------- Post added at 06:49 AM ---------- Previous post was at 06:44 AM ----------
This thread got hijacked at least 3 times. Let's hope OP can find his way back.

pocholo36 said:
I have the same issue. The problem is, that my computer will not recognize the phone in bootloader mode or in recovery mode(MTP enabled). How can install usb drivers without being able to boot into phone OS???? I've tried Nexus Toolkit with no success. Please help?
Click to expand...
Click to collapse
Try this Hope you get solution to your problem of installing adb and fastboot tools in the correct manner.

I just by mistake deleted my internal storage.
I have TWRP, how do i put the ROM on there and flash it? Someone please help.
Thanks