Database Users

[Q] Boot hangs at Android sign.

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.

[Q] Possible to unbrick?

Hey guys so i recently flashed 4.2.2 (11a i believe from a tot file). It worked great then i tried to get malladus 3.0.2 running, i got cwm installed (latest one) then i flashed 1xx to 24ap prep file then rebooted, both my twrp and download mode were broken. so i used the tutorial here http://forum.xda-developers.com/showthread.php?t=2582142 and now all i get is a black screen, also for some reason android seems to mount a bunch of partitions (i accidentaly formatted the first to fat). is there any way to fix the phone, or is it a goner?

[Q] CWM disapeared, boot loop, only have access to android system recovery

Hi guys
(SM-N9005)
So yesterday I had liquid smooth rom installed for the past month or so (I have been trying a variety of roms for the last year or so) and I was getting some bugs occuring and decided to put a new rom on.
I booted into recovery, did the normal backup, factory restore, clear cache and dalvik, installed the rom and restarted my phone. It then went into a boot loop.
At this point I assumed it was no biggy, so I just went back to recovery and chose to restore with the backup... except it wouldnt. it couldnt recognise the file it had just made.
So I then coppied some previous backups to the external micro sd, stuck the micro sd card in, booted in recovery and tried to recover with them... couldnt recognise them.
I also noticed that when trying to reboot, it came up saying that I didn't have root access... even though I certainly have for the past year.
I tried flashing an updated version of superuser as that was the suggested method on some forum - didnt help the situation.
Now when my phone boot loops, it goes straight to android system recovery <3e> and nolonger have access to CWM
No idea what to do, and my uni work greatly depends on me having access to my phone :/
Any help would be greatly appreciated

my baseband version is LRX21V.N9005XXUGBOB6

i got some problem ... it freak me oute but i founnd how to back my stock firmware backk
you shoud find your firmware ... it can be downloaded from sammobile.
and flash tar.md5 file via ONDIN.
good luck!

[Q] TWRP restore hung at "Restoring system" on G2/D800-20y

Hi,
This is the first time I rooted and installed a custom ROM.
I wanted Android 5.x on my new LG G2 AT&T (D800 20y) which came with 4.x.
So I
- rooted using ioroot10
- installed ROM Manager, TWRP Manager, AutoRec, (SuperSU,...)
- reboot to restore
- created a backup (checked all check boxes) using TWRP Backup, it created 2.5-3GB backup.
- reboot system, downloaded latest CM12.2 nightly from cyanogenmod dot org and put the zip file in /sdcard.
- from ROM Manager GUI -> Install ROM from SD Card and followed all prompts (reboot to restore, ...)
- rebooted a couple of times and finally booted up in CM12
- things were bad, Play Store didn't work (I tried installing GApps, it was still crashing), browser was crashing and so on. So I decided to go back.
- Rebooted to restore
- TWRP restore -> Selected the backup I had created earlier.
It started restoring but it's stuck at "Restoring system" since 3+ hours.
I'm scared of stopping it in between by hardbooting for obvious reasons, so for now I'm leaving it connected to charger.
Only screwup I think I might've done is there is no SD card on the phone, so I don't know if it's trying to restore the backup onto the backup file itself or something.
Thanks
Using TWRP 2.7.0.0
See attached screen shot.

thekashyap1 said:
Hi,
This is the first time I rooted and installed a custom ROM.
I wanted Android 5.x on my new LG G2 AT&T (D800 20y) which came with 4.x.
So I
- rooted using ioroot10
- installed ROM Manager, TWRP Manager, AutoRec, (SuperSU,...)
- reboot to restore
- created a backup (checked all check boxes) using TWRP Backup, it created 2.5-3GB backup.
- reboot system, downloaded latest CM12.2 nightly from cyanogenmod dot org and put the zip file in /sdcard.
- from ROM Manager GUI -> Install ROM from SD Card and followed all prompts (reboot to restore, ...)
- rebooted a couple of times and finally booted up in CM12
- things were bad, Play Store didn't work (I tried installing GApps, it was still crashing), browser was crashing and so on. So I decided to go back.
- Rebooted to restore
- TWRP restore -> Selected the backup I had created earlier.
It started restoring but it's stuck at "Restoring system" since 3+ hours.
I'm scared of stopping it in between by hardbooting for obvious reasons, so for now I'm leaving it connected to charger.
Only screwup I think I might've done is there is no SD card on the phone, so I don't know if it's trying to restore the backup onto the backup file itself or something.
Thanks
Using TWRP 2.7.0.0
See attached screen shot.
Click to expand...
Click to collapse
So... you did all of this on a recovery dated before the release of lollipop?

Choristav said:
So... you did all of this on a recovery dated before the release of lollipop?
Click to expand...
Click to collapse
Of course. That's why I come here for help.
I could've added that I [thought I] had clicked on stable before taking the latest ROM in the last, but just because I thought I was not making a mistake is not an excuse.
Anyway, I hard booted, and restored to D80010o using tot method. Of course it was a horror story, me being a noob at this, I spent solid 10-12 hours on my laptop.
But thanks for your help!
Sent from my Nexus 5 using Tapatalk

Galaxy S5: Stuck "Flashing File 1 of 1" When Installing CM

CM Installation Problems
I posted this last night on the CM forums and have had one responder but thought this might reach a wider audience. I'm copying and pasting the OP and I'll try to include as much info as possible.
Hi,
I'm fairly new to flashing etc. New as in this was the first time I tried it. I'm fairly tech savvy, I just haven't flashed a custom rom before.
I followed all the instructions on the CM wiki for the S5 (AU).
Long story short, every step in those instructions worked perfectly once I accounted for my own errors or misunderstandings. Flashed the TWRP recovery just fine. There were problems with ADB not working when the phone was in recovery mode (discovered it's something to do with win 8 and above) so I just rebooted into stock rom (where ADB worked) and used adb push to copy the files to sdcard. Everything went swimmingly until the actual CM installation. I followed the instructions and did the factory reset, went to install and the installation took something like 10 mins before I started to wonder how long it was meant to take. Little bit of googling got me more worried, after about 20 I pulled the battery, back into recovery and went into Wipe again. Cleared Dalvik, cache, system all manually and then did the factory reset option on top of that just to be thorough. Installation is still taking forever. It's currently been around 20 minutes. Some posts I've read say rooting is required but that installation article specifically says rooting is neither required nor recommended. I've no idea where to turn now. I can't use ADB to copy a stock firmware back on as it doesn't work in recovery mode, nor can I try the klte or kltedev versions (don't think they're meant for this model anyway). It's just stuck on "flashing file 1 of 1" - the last thing in the log is "Patching system image unconditionally..." I'm running windows 10, not that that should make any difference.
Any help would be hugely appreciated.
Update: After about 40 mins I pulled battery again and thought I'd try booting normally and seeing what it does. Just sits at "Samsung Galaxy S5" splash screen.
TL;DR/Extra info:
Galaxy S5 G900I (AU) Vodafone
Was running Lollipop 5.0 as per Vodafone OTA update
Using instructions on the CM wiki page for the GS5 (AU) I flashed TWRP using Heimdall with no errors. ADB would not work in download/recovery (couldn't see device) so booted phone into stock ROM and used ADB push to copy the CM file to sdcard root. Note: I don't have an sd card, it's internal storage. Rebooted into recovery, tried to flash CM, it sat on installation screen for about 20 mins. Tried 3 times, leaving it for 40 mins, still nothing. Stock OS has been wiped so I can't get back into that, and because ADB doesn't work I can't reflash recovery from scratch, can't copy a new download of CM on, can't copy the stock ROM to flash. ADB Sideload just tries to run and fails. Currently trying to get ADB working. Running Win 10, device stopped showing up in device manager or Zadig at this point. Restarted PC, ran Zadig again, it saw device, reinstalled driver, now shows up in device manager under USB Devices as MSM8960 (so not under Portable Devices as it once did). Note: the safely remove icon in system tray showed "Galaxy S5 (Phone name)" before I ran Zadig again, now it shows MSM8960.
Help

Reflashed TWRP with Heimdall. Didn't change a thing.
After the biggest headache of my life I got ADB working in TWRP. Had to modify the .inf of the google usb driver that the SDK installs and add the hardware ID of the device in recovery mode. Apparently the ID changes when in recovery so the driver doesn't recognise it anymore. Success!
I downloaded the nightly from 30/09, renamed it update.zip so the filename was simpler, pushed it with ADB to sdcard and am now trying to install it. So far same issue, but at least I can push files to the phone now. It definitely seems to be an issue with the install process.
Update: Still same issue. New zip, new build, reflashed recovery and still hangs on install. Would trying ClockWorkMod be worth it rather than TWRP?

When sideloading the ROM and viewing command prompt on the PC everything works fine until it hits 90% and then it stops suddenly and stays there. During the TWRP factory reset it also says unable to mount system several times if that's any help

I've now tried flashing Philz Touch and given that a go. Factory reset/wiping seemed to run with less of a hitch but still exactly the same deal, gets to "patching system unconditionally" when installing CM and just sits there, progress bar doesn't even fill up a bit. I'm stumped.