Hi awesome XDA dudes
I've searched the forums, and even posted in the basic QA section to no avail. I may have just missed it somewhere, but here is the issue.
Tablet will work fine in Lightspeed 4.8 ROM. No issue there. But, when I try to get into the recovery (power and volume down) I get "booting recovery kernel image," forever.
I recently changed from the Clockwork to TWRP recovery and that is when the recovery function would no longer load.
How can I get back to Clockwork or smililar so that I can put a different ROM on my tab?
Thanks in advance!
Tom
Fixed this problem, only to find another.
So, since my tablet would still function normally (aside from recovery) I downloaded the Acer Recovery Installer App. And this did what everything else failed to do. It installed Clockwork Mod and I was actually able to get into the recovery. Whew!
So I went to install Flex shockwave ROM but the install froze at the Aroma 2.56 stage...forever. Tried again unsuccessfully and gave up. I did properly wipe and format beforehand. I then tried installing CM10 Rom, same exact problem.
So, I used Acer Recovery installer and loaded the TWRP recovery. Here is where things get interesting. I booted into recovery, wiped data and caches, and tried to install the aforementioned ROMs. Each time, Aroma installer worked fine and I was presented with all the install options, all the bells and whistles. After completing my selections, I was prompted to reboot.....
And each time the tablet hangs on the Acer spalsh screen.
So now my problem is reversed. I have access to recovery, but no ROM. :crying:
SOLVED !!
tfbielawski said:
So, since my tablet would still function normally (aside from recovery) I downloaded the Acer Recovery Installer App. And this did what everything else failed to do. It installed Clockwork Mod and I was actually able to get into the recovery. Whew!
So I went to install Flex shockwave ROM but the install froze at the Aroma 2.56 stage...forever. Tried again unsuccessfully and gave up. I did properly wipe and format beforehand. I then tried installing CM10 Rom, same exact problem.
So, I used Acer Recovery installer and loaded the TWRP recovery. Here is where things get interesting. I booted into recovery, wiped data and caches, and tried to install the aforementioned ROMs. Each time, Aroma installer worked fine and I was presented with all the install options, all the bells and whistles. After completing my selections, I was prompted to reboot.....
And each time the tablet hangs on the Acer spalsh screen.
So now my problem is reversed. I have access to recovery, but no ROM. :crying:
Click to expand...
Click to collapse
Ok, so I had a working ROM but my recovery was fried. So, using Acer Recovery Installer I was able to get a working recovery going.
Then the next problem was that I could not get CM10 to install. When I realized I needed to flash the bootloader (and yes fellow noobs this is different than the recovery) I was unsuccessful.
I tried the automated route using the Blackthund3r app, but the process would just hang at Entering bootloader.
I tried the manual NVFlash route provided by Dibbs and it would get past this point and then hang.
So Dibbs (thanks dude) helped me out via email and suggested I download babsector.rar
After I extracted the rar file, I saw the A501 A.bat file and flashed it. This provided me with hope as it flashed the tablet and the screen atcually read "PASS." But, I wasn't done yet as I still could not install CM10. So, back to APX mode and back into the babsector rar folder. I flashed the Tab with A501 B.bat and followed that immediately with flashing the v8.bat file. In the V8.bet file I chose the Thor 1.7.3 recovery (as suggested by Dibbs and others) and WOOHOOO.....PASS on the tablet again.
Feeling ever more confident, I booted into recovery and flashed the CM10 Rom....SUCCESS!!!!!!!!!!!!!!!
If you are having trouble....don't give up. Thanks again for the help to Dibbs and OKAstro!!
Related
I tried yesterday to one-click root my MT3G following unlockr.
Got the Amon-Ra recovery on there, but it hung on the green MT3G splash screen when I tried flashing cyanogen 4.1.11 .
Waited like over 20 minutes. So I took out battery, and tried to boot again. Same thing. So I rebooted into recovery and tried flashing ROM again.
No matter what ROM I tried, I got a "E:Can't open /sdcard/update.zip (bad)" message. (I redownloaded ROMs from different sources given the message thinking maybe they were bad or incomlplete, but nothing worked).
I finally did a nandroid restore.
Now I'm not sure where I am. Given that I restored my stock nandroid backup, my understanding is I'm no longer rooted. Though, I am still able to boot into the Amon-Ra recovery. which I thought would have not still been possible. I downloaded better terminal and tried typing "su" but it wouldn't let me continue, so that confirms not rooted, right?
Do I run the recovery flasher app again (which is still on the phone), and reflash a recovery image? Or should I delete the app and redownload the recovery flasher apk.
Just not sure how to safely retry.
You need to provide more details about your process. I actually unrooted mine previously done with Cyanogen Recovery and rerooted with same instructions on that site only this time with Amon Ra recovery image without problems. In my case I wanted the option of formatting partitions. Maybe you should try Cyanogen stable Rom first, like 3.68.1 version. I had an issue with 4.1.11.1 after I partitioned the card so I did 3.68.1>4.0.4>4.1.11.1.
My Iconia has CWM installed. I used it a while ago to install the leaked ICS rom. I tried to install the most recent (official) ICS rom. Now my Iconia will not boot past the Iconia logo. I've loaded CWM and formatted everything and reinstalled the official rom. No go.
I figure at this point I have to use nvflash to install a new recovery image and rom. Could somebody tell me how to do that and what files to get?
Thanks
Before doing anything else have you tried wiping cache and data? Has worked for me when a rom wont boot. Have you still got cwm can you access it? If no cwm you can accomplish this by holding power and volume up then toggle the rotation lock.
Yes, I have access to CWM. I have tried wiping everything. I even successfully installed a new rom. The device still will not boot past the Acer logo.
I booted wit hte method you described. Two messages appeared in quick succession, "Clearing data..." and "Clearing cache". After the cache message, the device just sits there doing nothing at all.
Previously I had the data partition encrypted. Could that be causing trouble?
did you install an ICS bootloader?
I'm not sure. That is why I created this thread. I'm looking to get the recovery and OS image necessary to get this device working again.
As the previous poster noted, have you switched to the ICS bootloader? When I flashed my A500 with an ICS rom it too got stuck in a bootloop. I then discovered that I actually had to flash the ICS bootloader berfore installing the new rom.
vangorra said:
My Iconia has CWM installed. I used it a while ago to install the leaked ICS rom. I tried to install the most recent (official) ICS rom. Now my Iconia will not boot past the Iconia logo. I've loaded CWM and formatted everything and reinstalled the official rom. No go.
I figure at this point I have to use nvflash to install a new recovery image and rom. Could somebody tell me how to do that and what files to get?
Thanks
Click to expand...
Click to collapse
You can't install official ROM with CWM. You need Acer recovery! This issue has been answered several times. Use search button!!!
I have an Acer A500, it has the v9 bootloader installed. I also have TWRP 2.6.3 installed as the secondary ROM, the recovery is also completely broken, fastboot and zip will not install on it (TWRP 2.6 is to big), but recovery using 2.4.4.0 does boot. That fine since with secondary and recovery installed I can use TWRP from either, which works great, but if I install a ROM it only boots once, then poof, its as if there is no kernel it will not boot. To boot a new ROM I have to format everything except the external SD (which I have removed) then install the ROM reboot to TWRP install it again, then reboot at which time it will boot about 1 is 3 times, if it fails try again and repeat.
Now the ACER is basically useless now as I can not boot safely to anything other than TWRP, I've tried 2 4.0.3 ROMs but I can not get the Installers to run, I've tried 2 10.1 ROMS boot both booted only once and also a 4.3 ROM (build 5 and 6) boot again both booted only once. I'm out of ideas I'd flash almost anything at this point to reset, but then there is that Windows 8.1 issue in which I can not get ACER driver to work (Duh!), and I do not think the issue is going to be fixed, I can only come up with 2 options 1 the internal storage is going bad, or the entire setup is just toast, since it can work, it just does not do so more than once.
Currently I have 10.2 (build6) running, so long as I do not need to reboot, so for now it is charging.
Any suggestions,
ERIC
egandt said:
Now the ACER is basically useless now as I can not boot safely to anything other than TWRP
ERIC
Click to expand...
Click to collapse
I have same problem with TWRP. Try to replace TWRP with TouchRecovery
Simply put, this is what happens when a rooting newbie discovers custom bootloaders and ROMs.
Current State:
A full stock ROM installed (no root) with the Skrillax V8 bootloader plopped on top of it. (which of course means the recovery-from-boot.p file still exists and that I don't have CWM.) The tablet will show the Acer logo then the Android logo and will give the appearance of booting. Then the icon flashes. It does this intermittently and forever.
What I want:
CM 10+ running with Skrillax and TWRP stably. I'd go with Flexreaper for next choice. Maybe I'll try to compile a KitKat version for it someday. Who knows.
How I managed to get my tablet in this crappy state:
Rooted tab a long while ago with a probably far outdated method.
Looked all over the internet later on how to unlock the bootloader and settled on the manual method in this excellent thread.
I flashed V8 and TWRP without a hitch using nvflash.
I wiped and installed Flexreaper.
I liked it but wanted a higher prize. I make a nandroid backup of it onto the external_sd and wiped and installed CM 10.1 from this thread.
This is where everything started going sour. It told me the install was invalid halfway. Disappointed, I wiped again and tried to restore my nandroid backup. It seemed to restore properly, but then Skrillax hung forever loading the kernel.
I wiped again and installed Flexreaper fresh. This time it booted. I downloaded the newest unofficial version of CM they mention on their wiki.
Booted to recovery and installed CM 10. It ran fine and I was impressed with the new OS. Then I noticed the apparent lack of Gapps.
I flashed the Gapps Jellybean package and rebooted. Skrillax hung.
Wiped everything I could fine in the TWRP menu and installed Flexreaper. Got past the primary kernel loading but the android icon would work for a bit then flash, starting all over again.
At this point I flashed several other recoveries, hoping it was my recovery. No such luck. I tried all of them included in V8.
Then finally, I downloaded full stock ICS and flashed it. I rebooted and noticed the same Android flashing thing.
Finally, I flashed V8 again, being the newbie I was, and then suddenly remembered while trying to boot to recovery that the Full install probably rewrote the recovery-from-boot.p.
And here I am.
Tl;dr version:
Went click-happy with ROMs, wiping, and recovery flashing until I was left with a stock OS that wouldn't boot with a Skrillax bootloader but no recovery.
The good news is, I still have cpuid+sbk, it still boots to APX (no idea how I didn't screw that up too.), and I have a nandroid backup on my external_sd which is probably untouched, since I was careful to not wipe it in TWRP.
Please help me fix this. I don't want an excuse to waste money on a flashy new Nexus or Asus Transformer tablet, I already have too many for my wallet's comfort.
I quess you renamed stock rom to update.zip and than flashed it? If you havent do it, put it on sd card and pres power+vol down (if nuttin happens than vol up). That shld trigger flashing proces
poslato sa elmag radija
uglyjohny said:
I quess you renamed stock rom to update.zip and than flashed it? If you havent do it, put it on sd card and pres power+vol down (if nuttin happens than vol up). That shld trigger flashing proces
poslato sa elmag radija
Click to expand...
Click to collapse
I don't have access to a micro sd card reader if the file must be placed on the micro SD card. I already have flashed the stock rom supposedly via TWRP, so I shouldn't have to flash it again, I wouldn't think. If I do, I guess I'll have to get a reader.
Yes. Micro sd. Rename it. You have guodes gere on xda. Im hoping it will help you.
poslato sa elmag radija
It didn't work. Still in same state as before.
I also have access to fastboot if that would help.
m27frogy said:
Simply put, this is what happens when a rooting newbie discovers custom bootloaders and ROMs.
Current State:
A full stock ROM installed (no root) with the Skrillax V8 bootloader plopped on top of it. (which of course means the recovery-from-boot.p file still exists and that I don't have CWM.) The tablet will show the Acer logo then the Android logo and will give the appearance of booting. Then the icon flashes. It does this intermittently and forever.
What I want:
CM 10+ running with Skrillax and TWRP stably. I'd go with Flexreaper for next choice. Maybe I'll try to compile a KitKat version for it someday. Who knows.
How I managed to get my tablet in this crappy state:
Rooted tab a long while ago with a probably far outdated method.
Looked all over the internet later on how to unlock the bootloader and settled on the manual method in this excellent thread.
I flashed V8 and TWRP without a hitch using nvflash.
I wiped and installed Flexreaper.
I liked it but wanted a higher prize. I make a nandroid backup of it onto the external_sd and wiped and installed CM 10.1 from this thread.
This is where everything started going sour. It told me the install was invalid halfway. Disappointed, I wiped again and tried to restore my nandroid backup. It seemed to restore properly, but then Skrillax hung forever loading the kernel.
I wiped again and installed Flexreaper fresh. This time it booted. I downloaded the newest unofficial version of CM they mention on their wiki.
Booted to recovery and installed CM 10. It ran fine and I was impressed with the new OS. Then I noticed the apparent lack of Gapps.
I flashed the Gapps Jellybean package and rebooted. Skrillax hung.
Wiped everything I could fine in the TWRP menu and installed Flexreaper. Got past the primary kernel loading but the android icon would work for a bit then flash, starting all over again.
At this point I flashed several other recoveries, hoping it was my recovery. No such luck. I tried all of them included in V8.
Then finally, I downloaded full stock ICS and flashed it. I rebooted and noticed the same Android flashing thing.
Finally, I flashed V8 again, being the newbie I was, and then suddenly remembered while trying to boot to recovery that the Full install probably rewrote the recovery-from-boot.p.
And here I am.
Tl;dr version:
Went click-happy with ROMs, wiping, and recovery flashing until I was left with a stock OS that wouldn't boot with a Skrillax bootloader but no recovery.
The good news is, I still have cpuid+sbk, it still boots to APX (no idea how I didn't screw that up too.), and I have a nandroid backup on my external_sd which is probably untouched, since I was careful to not wipe it in TWRP.
Please help me fix this. I don't want an excuse to waste money on a flashy new Nexus or Asus Transformer tablet, I already have too many for my wallet's comfort.
Click to expand...
Click to collapse
Babsector should still work - you would need t do a search for it
It seems to have worked properly, sort of. Flashing FLEXReaper results in an "Encryption failed." prompt at boot, which the button, of course, does not work. Wiping everything works except that the prompt notes "E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p4" Trying to reflash V8 with TWRP with the V8.bat file fails at format. More help?
My tablet is still displaying "Encryption failed", the button still doesn't work, and I still love my a500. Help?
Anyone?
I guess I'm screwed, then.
In the end, I think my data partition failed. Formatting or wiping data fails and when installing FlexReaper, it reports /data size as -1. Unless anyone knows how to fix flash memory, I think I'm stuck.
Hello,
I am having some problems since today i flashed the su binaries over my completely new lineageos install. (a14.4, fully wiped before).
it was stuck during boot at the android logo(let it boot for half an hour, multiple times, no progress). so naturally i wanted to boot to recovery, though it would not boot into recovery with any imaginable key combo.
so i went into bootloader mode (which, in my case, is jsut download mode, no fastboot whatsoever, and yes, i checked fastboot devices, (also adb), nothing to be found there)
next, knowing i had no other choide at that moment, i flashed a stock rom, via download mode. worked so far.
stock rom was running (ics), bootloader was still download mode only, and recovery was now stock android rec.
my next step was flashing a custom rom, since this was the most important thing to get to working then.
via adb sideload i fashed lineageos, once again. was working fine, so recovery next. but nothing worked.
included with lineageos is root access, so i enabled all the stuff, incl. adb, on my phone. but adb sideload always spit out errors (code 7 or 255) on rec install (twrp 2.8.something touch.zip) [some error about /tmp/update.zip] trying cwm resulted in the same thing, like did flashing gapps.
pushing the files to the internal memory (/sdcard) did not help, since 'flash from sdcard' resulted in an empty sdcard folder with no files to install (in recovery. in the file explorer while running the os, the files where there)
then i tried rashr (not sure exactly which app it was) to install rec. it said everything worked fine, trying to install cwm. so i rebooted
and nothing worked. the rom would not boot anymore (again, stuck at android logo) since the stock recovery only allows for adb access in form of sideload, no push whatsoever, and sideload did not let me install the os via zip, it was back to flashing a stock rom once again.
so i did that again (this time lolipop)
this is where i am now:
the rom boots perfectly, like does the kinda stock recovery, but again: no files in the sdcard path within the rec menu, though i pushed them there, and they appear there in the file manager.
i installed root, for those neat apps, that maybe one would work, but they need root and the stock rom does not know how to give those rights to apps, no option found for this whatsoever.
also, download mode is gone. (still no fastboot)
when i try to boot the bootloader, i just goes on to usual os boot (key combo and adb reboot bootloader result in the same thing)
recovery is still working, but pretty useless still. when i try to sideload a file, it quits with failed verification of the file. which is no surprise to me, since it shows the message halfway through the send process (observed from the adb terminal on my pc, never gets even close to 100% before the message appears on the phone which also cuts the connection therefore the file send process.)
i have absolutely no idea what the hell will get this working again. i dont really care about the download mode, but what i really need is a custom recovery to finally work, so i can install all of my stuff again.
does anyone have any idea on what i could try next?
hopefully yours,
azyrael
SOLVED
so i noticed for root apps i need to install supersu (or something like this) to give root access to apps if there is no native way within the rom to do this stuff.
install supersu and found out i somehow had no root access at all. tried ioroot etc, did not work
so i installed a stock jb android rom, rooted the device via ioroot, install recovery via autorec, and it finally worked!
this took me only two days.
thx xda for providing all of the tools i needed for this <3
kinda unsolved
so, it got recovery to work. installation of lineageos also worked perfectly., though this bricks my device.
no matter what i wipe, installing a custom rom will stop it from booting. this could only be fixed by installing a stock rom again, which also reverses root and install a stock recovery. since i only need root and the rec for installing a custom rom, which does not work anymore, i wont bother with this anymore. i have abosutely no idea whatsoever, and tried everything even barely coming to my mind.
still open for suggestions, but the stock rom will have to suffice for now.