Okay so last night I was putting on a new theme on my phone(MT3G/32B/T-MO Branded).
After applying the update, rebooted and it started to hang. Tried running one of the nandroid backups that I have saved and it booted backup but all sorts of processes kept force closing, not allowing me to do anything.
Tried a few more nandroid backups, with same results, so I decided to flash the stock firmware back on. So I put the sappimg.nbh file on sdcard and updated it with that.
Now the stock image ALWAYS works with no problem. It lets me flash a new recovery image with Recovery Flasher(Tried Rav 1.2 and CM-1.4). Both recovery images work but when trying to update with a new rooted rom it sits at the first splash screen forever. I've tried a few roms like CM-4.0.4 and 4.1.11.1.
By this time i thought maybe the roms were corrupt so I downloaded a new CM-4.1.11.1 and it took a while but it did boot up, but once i put in my log in info it just froze on the home screen. Rebooted and stuck at the first splash again.
Remember how I said I reverted back to stock firmware? well once I did that and after all this trouble, I tried running a nandroid backup and no matter which one I run, it being and old one or if i just make a new backup they all come out with the same error: "Nandroid failed:run "nandroid-mobile.sh restore" from adb.
Any ideas??? At the moment i'm downloading CM-4.0.4 to try that because i've had problems with 4.1.11.1 and flashing that without having 4.0.4 already flashed. So i will try 4.0.4 right now, hopefully it works and if it does I will update to 4.1.11.1
Thanks guys, first post so don't be too rough...
my experience with that is solvet by booting recovery ROM from say raon and choose wipe data, then reboot
lupascu.marius said:
Okay so last night I was putting on a new theme on my phone(MT3G/32B/T-MO Branded).
After applying the update, rebooted and it started to hang. Tried running one of the nandroid backups that I have saved and it booted backup but all sorts of processes kept force closing, not allowing me to do anything.
Tried a few more nandroid backups, with same results, so I decided to flash the stock firmware back on. So I put the sappimg.nbh file on sdcard and updated it with that.
Now the stock image ALWAYS works with no problem. It lets me flash a new recovery image with Recovery Flasher(Tried Rav 1.2 and CM-1.4). Both recovery images work but when trying to update with a new rooted rom it sits at the first splash screen forever. I've tried a few roms like CM-4.0.4 and 4.1.11.1.
By this time i thought maybe the roms were corrupt so I downloaded a new CM-4.1.11.1 and it took a while but it did boot up, but once i put in my log in info it just froze on the home screen. Rebooted and stuck at the first splash again.
Remember how I said I reverted back to stock firmware? well once I did that and after all this trouble, I tried running a nandroid backup and no matter which one I run, it being and old one or if i just make a new backup they all come out with the same error: "Nandroid failed:run "nandroid-mobile.sh restore" from adb.
Any ideas??? At the moment i'm downloading CM-4.0.4 to try that because i've had problems with 4.1.11.1 and flashing that without having 4.0.4 already flashed. So i will try 4.0.4 right now, hopefully it works and if it does I will update to 4.1.11.1
Thanks guys, first post so don't be too rough...
Click to expand...
Click to collapse
???
I've wiped so many times i can't even remember. Before and after each thing i said that i did a wipe...so no go on that, but it doesn't matter anymore. i've updated to rooted Donut 1.6 now. Thanks anyways tho
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.
Heres my situation:
I installed the froyo rom without installing the new CWM first. So i tried renaming the new cwm and replacing it with update.zip to no success, and never reverted back to the old one. Now i decided to revert back to stock, install the new CWM, and than flash the froyo rom. But something went wrong.
I flashed odin stock-i500-vzw-system.tar.md5, and upon reboot it sounds the vzw sound, but stays in the samsung bootup screen, and it won't go into recovery because my update.zip is broken.
My odin for some reason fails every time i try to flash the old recovery, or the old kernels, it only wants to flash system.tar.
Thats as detailed as i can get it for now, any help would be great.
look around for some different stock odin files. i had a hard time with flashing cwm files as my phone just wouldnt accept them for some reason.
i'm gonna try adrenalyn's system.tar, kernel and CWM DI01 package, see if this works. keep fingers crossed
After playing a youtube video, suddenly my tab reboot by itself, and it stuck in a boot loop.
I tried to wipe factory setting and cache, still the same problem occured. I even tried to reinstall the same rom, it still give the same problem.
When i tried to install other rom (My-Rom 1.0) it stucks on installing kernel.
i try to find any hint on the xda, brought me to this post
http://forum.xda-developers.com/showthread.php?t=1128565
it still unable to solve my problem. Hope anyone can help.
Try installing a different ROM, besides the two you installed, I had the same problem when I flashed HoneyVillain to Taboonay then to Lightspeed, I was stuck on a bootloop, couldn't flash back Taboonay, but was able to get HoneyVillain.
Still has the problem
I tried as you said, Installed honeyvillain 1.2 rom, and still has the same problem.
2 things which i realized is that,
1. there is sudden blink of loop screen that is different from boot loop that i have seen before.
2. there is error when i tried to do factory wipe
error moving data/data/com.estrong.android.pop/lib/libes_dropbox.so
hopefully anyone can help me
have you tried using acer recovery app to reinstal CWM, then use it to download just a basic 3.2 rom if possible and see how that goes
I am having the exact same problem error removing data/bluestacks, bootloops with little flashes in boot animation. tried every option in recovery and like 4 different back up restoration and the boot animation changes to that of the new restore but same thing.Help!!
thor's 13 then updated to 14 and this started
If you want, go to www.tegraowners.com . Thor's site. He made the recovery. If you go to his forums, Rom section, you will see he posted some steps to completely wipe internal memory. More than what the usual steps we take.
I suppose, there is some residual data left, which is why some errors are happening.
Also, any files named "update.zip", should be removed from SD.
Then you should be able to flash a new rom.
Here are the steps....
go to in recovery enter Backup and Restore and click on Toggle backup and restore of internal storage (/data/media)
should say enabled....
then go into Mounts and Storage and format /data
this will REALLY format data and you will loose all you have in the in the internal memory
then reinstall the rom and everything should work as expected....
im currently having this issue as of right now , idk wat the problem is
EDIT: and i cannot access CWM either
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.
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!