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.
Related
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!!!
UPDATE: After completely wiping everything(recovery, ROM, bootloader, etc), and putting it back in with fastboot I no longer have this problem. My recovery probably just got corrupted or something while getting sent over to the device.
Got my Nexus 7 3 days ago, had it unlocked and all that jazz within the hour(thanks to the people who put the stuff together). It's great, but I have a problem with flashing .zip files in recovery. It doesn't matter what type of thing I'm wanting to flash(ex-kernel,rom, or even the uber-simple 720p camera mod), if I don't do a full wipe before flashing, then it just ends up boot looping my device. The boot loop doesn't turn the phone all the way off, just the boot animation. Sometimes the launcher will pop up for half a second and then go back to the boot animation.
For example, whenever I flashed the rasbeanjelly rom, I first flashed that, then rebooted(got excited and forgot about gapps) and checked it out. Remembering about gapps, I went back to recovery and flashed gapps. Then it boot looped the animation. After flashing gapps again(trying different combos of wiping cache/davlik), I flashed the rasbeanjelly rom again, and then gapps immediately afterwards. Still a bootloop. So I did a full wipe(including data this time), sideloaded my .zips, and then it flashed and rasbeanjelly booted up with gapps just fine.
This exact same problem has been happening with every .zip that I try to flash(running TWRP, yes all my stuff is updated). If I want to flash a kernel, I have to flash it when I flash my ROM or else I'll get boot loop. I can't really make any modifications without having to completely wipe my device(which is annoying because I carry a lot of data around on my stuff)
I'm asking if there is a way to flash a .zip without having to completely wipe my device. I'm not a noob to android at all(ROM cooker over at androidforums), but I can't figure it out, I'd love to make stuff for the grouper but this is kind of a big roadblock for me. Logcat isn't helping either. Hopefully I just skimmed over something and it's a simple fix. Thank you for your tips/suggestions/solutions.
EDIT: forgot to mention something. When I flash a new ROM and get it going, I always make a full backup in recovery. If I flash something, and boot loop it, I can't restore it correctly. Recovery says that it restores all good, but it still boot loops(even though I just restored a backup of a non-boot looping system from no more than 5 minutes ago).
If I read your post correctly, you've only tried this on one ROM. Try the same thing on CM10 or PA or whatever you want.
korockinout13 said:
If I read your post correctly, you've only tried this on one ROM. Try the same thing on CM10 or PA or whatever you want.
Click to expand...
Click to collapse
I've actually used several, and it seems to be happening on all of them. I've tried flashing things with PA, CM10, Stock, and RasberryJelly. The kernels I have attempted to flash have been Trinity, Motley, and Franco. All with no success and boot looping me :/
Hi guys, the times has come for me to open up my own account - I screwed up. I hope this is the right sub forum and apologize if it is not.
LG G2 Germany, formerly: TWRP recovery, Paranoid Android 5.1.1
Loved the rom but there were some issues like the screen turning off and on randomly, wouldn't accept pin right away, so I decided to go for CM 12.1.
Booted into recovery, factory wiped, tried to flash the .zip, but neither the rom nor the gapps would even begin to flash. It just said error.
Went crazy, tried some other CM versions, none of them worked. I've never had this issue before, when I flashed PA it all went just peachy.
Went even crazier and I can't really remember what I did in my panic spiral, but I somehow ended up with a soft-bricked phone. Managed to re-install the LG firmware .kdz, however, only the 4.2 one worked (4.4 gave me a bootloop.)
Now, getting this bad boy rooted and ready to flash custom roms is somewhat of a problem. I managed to get it into recovery though (after some issues with the recovery image), but flashing CM still won't work. Same error as before. I think there may be something wrong with the recovery image. I still had the image .apk from the first time I rooted my phone (also with 4.2) and it worked just fine so I figured I'd just use it again and do it like I did it last time. However, I am able to get into recovery mode. I've tried ClockworkMod and TWRP, but as a result of my panicking, it's just really a big ol' mess right now. I hope I've included all the info needed.
Please help, I'm actually lost.
Are you flashing the latest TWRP which is 2.8.7.1?
http://blastagator.ddns.net/twrp.html
Hey, thanks for replying. At the moment it only boots into recovery, unfortunately. ADB does not work, even after re-installing the usb drivers. My computer recognizes the device now though, but I can't get any files onto that thing at the moment.
Edit: It's not the latest TWRP
If you install the latest TWRP, you may be able to boot into TWRP and copy over a ROM to flash.
Hi guys, been using my rooted but otherwise stock OOS rom with TWRP and Magisk for the past few weeks. Today I decided to take the plunge and try either the Lineage OS or Resurrection Remix roms.
I'm using the latest OFFICIAL TWRP.
So I decrypted following the instructions to flash "no-verity-opt-encrypt-5.1.zip", then format data. All went well, so I then sent over the ROMS I wanted to try out. I started with the official ResurrectionRemix. Bootloop. Then the unofficial LineageOS. Bootloop.
Ok, well I guess I'm not gonna get to use any of the cool new OS's for awhile. I'll install the full stock firmware zip so I can have a working phone again. Bootloop.
Now when I say bootloop, the phone is booting to the BootAnimation and just repeating it. It shows the proper boot animation for whatever zip I have installed (resurrection/LOS/OOS), but it stays on there for up to 20 minutes before I have to hard reboot to the recovery again.
I decided to install the stock recovery trying a few methods. I first tried the ALL-IN-ONE tool. It said it flashed the recovery fine, so I booted to the recovery and after staying on a black screen for too long, the language options came up and I sighed a breath of relief. But before I could select English with the volume buttons, it rebooted by itself. It did this again when I manually entered recovery. So I figured maybe the tool flashed the wrong version, so I googled stock recovery for OnePlus 5, I found a few random links for stock recoveries for the OP5 and flashed them, but they more or less do the same thing or not boot at all.
I've tried changing the filesystem for both Data and System using any combinations of EXT4 and F2FS. Everything results in boot animation bootloops.
I have been flashing Roms since the Samsung Galaxy S3 and every phone since and never had any problems.
Currently when trying to install the stock Full OOS official zip with TWRP, the phone won't even go to the boot animation, it only goes to a black screen with the top LED in a light blue color.
I have also tried every version of TWRP there is for the OnePlus 5. Unofficial, Official, 3.1.1-0 and 3.1.1-1.
So I guess my question is....What filesystem is each partition supposed to be on and for which OS?
Lineage based:
System: ?
Data: ?
OOS Based:
System: ?
Data: ?
And any ideas on getting my phone running again?
And anyone have an official confirmed working version of the stock recovery? The one from ALL-IN-ONE TOOL doesn't work for me. It loads the language selection, then the screen goes black with a light blue LED on the top of the phone.
Actually I'm getting that on some roms instead of the bootanimation, like FreedomOOS. What does it mean when you have a black screen and a white LED?
Man, I really thought I was getting somewhere. If I boot into TWRP, change the Data partition to "F2FS", then flash the stock recovery, the stock recovery will boot, however, when inside the stock recovery and I try to flash the stock zip, it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
Ok, I have the official stock recovery from the OnePlus site, but still can't use it. Here is was happens depending on how I left it with TWRP:
System: F2FS
DATA: F2FS
- Stock recovery will load after some time, freeze, then the screen goes black with white LED on top.
System: EXT4
DATA: F2FS
- Stock recovery loads fine, I can go through the settings and install from SD card, but when I do it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
System: EXT4
DATA: F2FS
- If I try to flash stock rom through TWRP, it just boot loops on the animation forever.
I have now also tried flashing the stock boot.img, but no difference.
I have 2 things you can try!
First, replace the bootloader with stock and do a factory reset:
1. flash the stock recovery over
2. then in fastboot mode enter, fastboot oem lock (This forces the phone to wipe cache and data, and also do a complete reset)
Did it work? if yes YAY if not go to Second!
Second if your system.img is ****ed up you have to replace it!
Download the newest version of the stock rom from oneplus link here
Unpack it
research how to use an extractor to convert the system.new.dat to system.img
once thats completed enter fastboot mode and flash the new system.img over with Fastboot flash system system.img
now go into recovery and do a factory reset and wipe cache, and dalvik
Please reply back wether or not this work
"Ihave 2 things you can try! First, replace the bootloader with stock and do a factory reset..."
Is the bootloader simply the boot.img?
After doing the first thing, it simply says that the device is corrupt and will not boot. But it is locked again.
But I will have to unlock it again to do any further flashing.
Hmm, I think I may have gotten it. After unlocking again, flashing the stock recovery and boot.img, then locking again and wiping in the stock recovery, I have finally booted into the stock rom.
I still have no idea what went wrong, and I really want to know, so that in the future I can flash other Roms, like LineageOS.
I mean, I followed the steps exactly.
If it says the device is corrupt it simply means you got something else besides stock rom.
So now unlock it and try the system.img instead
It was because I still had TWRP with the stock rom.
I got it working though, thanks for your help.
Do you have any idea on what might have went wrong when trying to flash the lineageOS based roms and why it got messed up so royally?
Great to hear you fixed it ^_^
Probably some minor bug, if you wanna try installing lineageos again use the 3.1.1 TWRP build that supports backups and do a full backup so you don't have to go thru all this again
---------- Post added at 12:17 AM ---------- Previous post was at 12:13 AM ----------
Not really just try again but remember to use TWRP 3.1.1, as 3.1.0 don't support backup and probably have been part of your problem
If your trying again and gets it successfully installed could you do me a favor and test if Drivedroid works on it? And pm me the result, I'm looking for a rom where Drivedroid will work... Haven't found one so far
You know, I did do a backup with the OFFICIAL TWRP, but it also resulted in a bootloop. I made the backup after decrypting, so I don't know why it bootlopped.
https://forum.xda-developers.com/oneplus-5/development/rom-unified-lineageos-7-1-2-t3635483
Is this the one you tried installing?
I tried like every ROM at one point yesterday, but I think I started with
https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578
Did you remember Gapps?
Also in some cases its better not to root before you have the custom rom running, you usually only need a custom bootloader like TWRP
Yeah, I tried with Gapps, and I never rooted before first trying to boot.
As of yesterday Ressurrection remix, released the first official stable build so try again your should'nt have any problems if you follow the guide 100%
Ever find a solution? I'm stuck here now. Can't get any ROM to boot up, they all get stuck on the boot animation
Bump. I am also stuck in this state
Hey, I'm new here when it comes to writing forum posts, so bare with me.
I've had this tablet for a few years now and I had flashed it with one of Magendanz roms (Nexus Stock) and I wanted to change to the LineageOS rom he had. I downloaded the .zip file and copied it to my sdcard and tried to get into TWRP to flash it. I did restart to recovery in the OS and once it restarted, it's been doing a boot loop ever since. I have tried using Odin to flash the rom that way, but for some reason it'll keep doing a boot loop after it's done flashing and restart. I can try going back to the stock firmware if it's a final option to get this tablet working again, but I would love to see if I can get LineageOS to work.
DengekiMatsuko said:
I did restart to recovery in the OS and once it restarted, it's been doing a boot loop ever since.
Click to expand...
Click to collapse
I had a similar issue once. It turned out that after flashing, not all the partitions mounted properly.
Are you still using TWRP? Boot to recovery, and go into "Mount". Make sure the system and other partitions are actually ticked. That solved the problem for me, and I was able to successfully boot to the system.
Hopefully your issue is that simple!
I managed to brick my Tab A 10.1 (2019) last year by dirty flashing ROMs I shouldn't have. I properly munted it, I couldn't even get into recovery. But I could still get into download mode with a USB cable plugged in to my laptop (it needed to be plugged in for download mode to come up). I flashed the stock ROM, which made it bootable again, which then allowed me to re-flash TWRP and then Magendanz' LOS18.1 ROM.
If you completely break your tablet, reflashing the latest stock ROM for your region is a great way to get back to a familiar starting point. You can then follow people's guides online to get where you want to be.