Related
Hi people,
I have a bit of a problem here
Recently updated my Nexus S i9020t (unlocked uk version) to 4.0.3, all done no hassle and working fine.
Then I rooted the device following the instructions on nexushacks .com, including flashing TWRP recovery and superuser.
Again, all fine no hassle.
HOWEVER now, whenever I try to boot into recovery, i see a belly up android with a big exclamation mark
Any ideas as to how to fix this, ie re-install stock recovery?
Much appreciated in advance,
All the best
if you still have root just download rom manager and install recovery from there.
Sent from my Nexus S using XDA App
Hi Camalus,
I already tried installing clockworkmod recovery from rom manager, unfortunately the issue persists (same deal, android belly up with exclamation)
Is Root working? You can test this by using terminal emulator and typing in "su".
If it is, rename /etc/install-recovery.sh to something else (ie. /etc/install-recovery.sh.bak). This will stop stock recovery installing each boot. After this, flashing CWM or TWRP again will keep it there.
Job Done
Hi Harbb,
Thanks an absolute million, I did as you suggested and then flashed an old version of CWM recovery.
Result: SUCCESS!
Awesome job done, nice one bro
Flash the new one, save you trouble down the track. Also remember to rename that file i said so stock doesn't replace recovery
And of course you're welcome.
Hi Harbb,
Can I flash the new version of CWM recovery through ROM manager, or would it be advisable to do it manually, with fastboot (as I did successfully just now)?
Also, I have renamed install-recovery.sh to install-recovery.sh.bak just as you suggested.
Are there any other files I need to rename in order to ensure recovery works as it's supposed to, or should that be ok now?
Once again, thanks for your help
That's all you need to rename. I'd generally just advise wiping/flashing manually, ROM Manager should be fine for recovery since it doesn't actually reboot into recovery and execute commands.
So, I just did a backup of my Glorious Overdose setup using the voodoo recovery it comes with and I got MD5 errors while trying to restore...
Anyone else have this issue?
I never restored from a cwm successfully, I think its not fully functional. Red nor orange... luckily I saved my apps & settings using mybackup
I have also had this problem. if anyone knows why, please let us know. I was able to restore data, but a couple funny things happened. when restoring, i get error restoring boot image or md5 sum mismatch. when restoring data, my phone stuck at restoring android_secure. i pulled the battery and rebooted. luckily that didnt brick my phone.
fiveseven808, did you flash cwm through rom manager? if so, i think that might be the problem. i flashed through rom manager and was having problems backing up/restoring. i went to this thread: forum.xda-developers.com/showthread.php?t=1124453 and downloaded the update.zip file in the first post, saved in my download folder. i then went to the root of my sd card and deleted the update.zip file that was there. i moved the other update.zip from my download folder to the root of my sd card. rebooted into cwm and took a backup no problem.
sidekick_fanatic said:
fiveseven808, did you flash cwm through rom manager? if so, i think that might be the problem. i flashed through rom manager and was having problems backing up/restoring. i went to this thread: forum.xda-developers.com/showthread.php?t=1124453 and downloaded the update.zip file in the first post, saved in my download folder. i then went to the root of my sd card and deleted the update.zip file that was there. i moved the other update.zip from my download folder to the root of my sd card. rebooted into cwm and took a backup no problem.
Click to expand...
Click to collapse
I did! But I was unable to use it... or something really strange happened..
Before Glorious Overdose, I could boot into CWM 3 using the recovery boot method. After Glorious Overdose, I realized I could boot into CWM Voodoo with the three button method getting around the stock recovery, and boot into a VERY broken CWM 4 via ROM manager.
Will your advice fix whatever I did wrong?
I have no idea, but you could try it and see. if it doesnt, your no worse off than you were to start with.
Update: I now know for sure that having the right update.zip file will fix the issue. I had to restore my phone today due to issues caused by unknown sources. I tried to fix the issues before doing a restore, but no luck. so I booted into cwm and hit restore. it worked without a single hitch. So the problem (for me at least) was definitely having the wrong update.zip file.
I have never had this issue, with VooDoo or regular CWM... Bad update.zip sounds like it would be the problem, as you said
i believe the issue is in the update.zip file. when flashing cwm through rom manager, i was unable to properly backup and restore. after switching the update.zip with the one found in the dev thread, i can backup and restore to my hearts content. i am very glad to have fully functional cwm on this device, as i had it on my last phone, the tmobile comet. the comet was my first android device. i was not entirely happy with it, but it gave me enough of a taste of android to figure out i wasnt going back to blackberry. prior to android, the best phone i had ever owned was a blackberry pearl. now, the sk4g is the best phone i have ever had, even better than the blackberry pearl. for me, this keyboard has no parallel, and the setup and ui is nowhere near as tough to get used to as people had been saying it was on the forums. but i digress. cwm is the best alternative to the stock recovery, and its good to have it working on this phone.
I'm running a B90 TF101 and I run CM9. I tried a few other ROMs and decided to go back to CM9, so I used CWM to restore one of my backups. Problem is, now my installation does not see the internal memory (the one it thinks is the sd card), so I cannot get at my backups or use ROM Manager (because it requires an SD card to be mounted).
However, my card does seem to be mounted in the usual places (/sdcard, /storage, etc.) so I cannot figure out why it's not seeing it, and I need it mounted to do anything useful on my tablet.
I did read of a bug in CM9 where we need to create certain directories (/Removable) on each boot, but the script provided didn't seem to make a difference, so I'm a little lost at the moment about how to fix this. Can anyone suggest any articles/posts/info, or give me some advice on this?
Hi,
Sorry, but it is not the bootloop issue. I've had (and solved) that problem several times before, with the exact solution you detailed below. It is something else, because I am able to boot into Android, but not able to see the internal storage memory.
guiloma said:
Hi, i think i might help you. I've just solved this issue(i think). Do you have the recovery bootloop problem?(this means the only way to get into the ROM is pressing PWR+VolDown and Cold Boot). That was my case, and i wasn't able to access de sdcard from the ROM, althought a can access it through ADB. If thats your case, next lines can be helpful.
I just applied the the fix for the recovery loop fix and i get it solved.(You can find this fix on several forums)
(Through ADB)
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
I think this may be related with "forcing" the deviced to coldbot, not exiting properly from CWM Recovery. I hope this helps you!
P.D.: I apologize for my english, i've done my best to get undestood
Click to expand...
Click to collapse
Well, if I find out, I'll post it here (unless someone else has a solution)
guiloma said:
Sorry it didn't help. That worked for me. I still think that the issue must be somehow related to a previous uncorrect dismount of the storage, or something similar. I hope you can sort it out!.
Click to expand...
Click to collapse
lingh said:
Well, if I find out, I'll post it here (unless someone else has a solution)
Click to expand...
Click to collapse
Same thing happened to me today after trying the official CM10 nightly and then trying to revert to an AOKP (ICS) nandroid. Did you try a JB ROM and then try to go back to ICS?
I read in the CM10 preview thread that nandroid backups don't include kernels (which was a surprise to me)...I'd suggest either reflashing the ROM that you're trying to use over itself (immediately after restoring your backup), or just reflashing the kernel itself (if you were using a custom one). I reflashed guevor's kernel after my nandroid restore and that fixed the problem for me. Reflashing the entire ROM should maintain your data/settings and also include the kernel.
My guess is that options or mount points for the internal storage are just not compatible between ICS and JB.
Yes, I tried CM10 preview, then tried to revert to my CM9 CWM backup. And reflashing CM9 did not work. I have had to flash Android Revolution to get my system workable again.
buck2202 said:
Same thing happened to me today after trying the official CM10 nightly and then trying to revert to an AOKP (ICS) nandroid. Did you try a JB ROM and then try to go back to ICS?
I read in the CM10 preview thread that nandroid backups don't include kernels (which was a surprise to me)...I'd suggest either reflashing the ROM that you're trying to use over itself (immediately after restoring your backup), or just reflashing the kernel itself (if you were using a custom one). I reflashed guevor's kernel after my nandroid restore and that fixed the problem for me. Reflashing the entire ROM should maintain your data/settings and also include the kernel.
My guess is that options or mount points for the internal storage are just not compatible between ICS and JB.
Click to expand...
Click to collapse
guiloma said:
Hi, i think i might help you. I've just solved this issue(i think). Do you have the recovery bootloop problem?(this means the only way to get into the ROM is pressing PWR+VolDown and Cold Boot). That was my case, and i wasn't able to access de sdcard from the ROM, althought a can access it through ADB. If thats your case, next lines can be helpful.
I just applied the the fix for the recovery loop fix and i get it solved.(You can find this fix on several forums)
(Through ADB)
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
I think this may be related with "forcing" the deviced to coldbot, not exiting properly from CWM Recovery. I hope this helps you!
P.D.: I apologize for my english, i've done my best to get undestood
Click to expand...
Click to collapse
Dude you Rock! Fixed my problem
Alright, problem fixed, but it took a lot of work.
What I did first is downloaded and flashed Android Revolution for my TF101 (link on these forums), then, after verifying it picked up my storage correctly, I downloaded and installed SuperSU, ROM Manager and ROM Manager Premium (the last I had paid for previously anyway).
I downloaded via the manager the CGM 10 Nightly for my TF101 (I guess this would also work with CGM 9 Nightly, RC or Full Release)
I opted to Backup the current rom, clear the Dalvik cache and also to wipe system and data and let it do its work. And bingo, it booted into CGM with a working internal storage, and also on JB now, since this is the CGM10 nightly which uses JB instead of ICS as base.
Hello guys,
I installed cm-13 successfully and it was operating fine until yesterday. Today I tried to install a theme or something and it hung. So i just felt like doing a factory reset and I did it through my cwm recovery. But before that i made a backup, then i did the reset, then i did the restore...ever since then i havent been able to open the OS...it gets stuck on the samsung GALAXY Tab2 10.1 screen. I can however access the cwm recovery. I did infact try to unzip the cm-13 that i had previously used, and it doesnt work...
Please help guys!
I am pretty new to this and i feel like i cant figure out what to do next.
Is there a way to maybe restart the whole process, like get rid of the cm-13 that is already installed and redo the whole thing again?
Kindly help guys, i was really enjoying the cm experience and i messed it up :/
killermara said:
Is there a way to maybe restart the whole process, like get rid of the cm-13 that is already installed and redo the whole thing again?
Kindly help guys, i was really enjoying the cm experience and i messed it up :/
Click to expand...
Click to collapse
you did a backup before factory reset, then you restored the same data after reset. this hardly changed anything. the reason it didn't boot, is that The problem lies at the system partition, you should wipe system partition, data partition as well and flash the same cm-13 zip again along with gapps, if you had.
now let the system start. it should boot up with a clean installation. you can then try to advance restore and chose only data partition.
later just switch to twrp recovery by Android-Andi
HELP!
billysam said:
you did a backup before factory reset, then you restored the same data after reset. this hardly changed anything. the reason it didn't boot, is that The problem lies at the system partition, you should wipe system partition, data partition as well and flash the same cm-13 zip again along with gapps, if you had.
now let the system start. it should boot up with a clean installation. you can then try to advance restore and chose only data partition.
later just switch to twrp recovery by Android-Andi
Click to expand...
Click to collapse
Hello, actually I did exactly that, i wiped system partition and all of that...then i did try with cwm, and it didnt work, what is happening is that i select the option to flash the ROM, then the screen goes blank for a second and comes back to the home screen of the cwm recovery. So basically i selected the zip and nothing happened! I then tried flashing using twrp and the problem now was that there was the "no md5 file found" message and the installation would not stop, it would go on for too long, like some sort of loop. I then switched back to cwm and tried again and it still doesnt seem to work...kindly advice on what to do next
killermara said:
Hello, actually I did exactly that, i wiped system partition and all of that...then i did try with cwm, and it didnt work, what is happening is that i select the option to flash the ROM, then the screen goes blank for a second and comes back to the home screen of the cwm recovery. So basically i selected the zip and nothing happened! I then tried flashing using twrp and the problem now was that there was the "no md5 file found" message and the installation would not stop, it would go on for too long, like some sort of loop. I then switched back to cwm and tried again and it still doesnt seem to work...kindly advice on what to do next
Click to expand...
Click to collapse
first thing check if you have updated to last official stock jellybean rom prior to cm13 upgrade.
this thread will help you to update your bootloader to jb from ics. if you have a jb bootloader already. you can skip this.
forum.xda-developers.com/showthread.php?t=2642005
next thing you should get twrp 3.0.2.8
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
after wiping, restart recovery, then flash the Rom zip
it takes time with the new CM13 builds to complete installation. some earlier twrp recoveries had issues(3.0.0.1 and 0.2, not sure right now, try latest only). cwm is not supported and twrp is the only preferred recovery by the Rom developers to flash the newer roms.
remember p5100 tab is called espresso3g now, since development has been unified. you need files marked as espresso3g for your p5100.
I don't which files are you using, development has changed so confirm the files that you're using are for unified builds and not device specific.
billysam said:
first thing check if you have updated to last official stock jellybean rom prior to cm13 upgrade.
this thread will help you to update your bootloader to jb from ics. if you have a jb bootloader already. you can skip this.
forum.xda-developers.com/showthread.php?t=2642005
next thing you should get twrp 3.0.2.8
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
after wiping, restart recovery, then flash the Rom zip
it takes time with the new CM13 builds to complete installation. some earlier twrp recoveries had issues(3.0.0.1 and 0.2, not sure right now, try latest only). cwm is not supported and twrp is the only preferred recovery by the Rom developers to flash the newer roms.
remember p5100 tab is called espresso3g now, since development has been unified. you need files marked as espresso3g for your p5100.
I don't which files are you using, development has changed so confirm the files that you're using are for unified builds and not device specific.
Click to expand...
Click to collapse
I followed all the steps that you suggested, and the thread suggested.
I installed custom recovery, then I updated the bootloader.
Then i flashed the new twrp, which is alot more easier to operated compared to the cwm .
then i wiped , restarted recovery, then flashed the rom,
the exact same thing that was previously happening with the cwm happened : I tapped on the rom, then a blank screen appeared and it went back to the main menu of the twrp...
The ROM i am using is: cm-13.0-20160220-1347-UNOFFICIAL-p5100.zip
i also tried using the ROM i got from get.cm : cm-11-20160822-NIGHTLY-p5100.zip
Okay so i played a slow mo video to see what the screen says before it goes back to the welcome screen:
Updating partition details. . .
. . . done
Full SElinux support is present.
MTP Enabled
Then after this pops up, it goes back to the main menu of the twrp.
What if i just reinstall the stock OS then do the whole process of getting cyanogenmod again from rooting onwards?
Kindly assist!!
killermara said:
I followed all the steps that you suggested, and the thread suggested.
I installed custom recovery, then I updated the bootloader.
Then i flashed the new twrp, which is alot more easier to operated compared to the cwm .
then i wiped , restarted recovery, then flashed the rom,
the exact same thing that was previously happening with the cwm happened : I tapped on the rom, then a blank screen appeared and it went back to the main menu of the twrp...
The ROM i am using is: cm-13.0-20160220-1347-UNOFFICIAL-p5100.zip
i also tried using the ROM i got from get.cm : cm-11-20160822-NIGHTLY-p5100.zip
Okay so i played a slow mo video to see what the screen says before it goes back to the welcome screen:
Updating partition details. . .
. . . done
Full SElinux support is present.
MTP Enabled
Then after this pops up, it goes back to the main menu of the twrp.
What if i just reinstall the stock OS then do the whole process of getting cyanogenmod again from rooting onwards?
Kindly assist!!
Click to expand...
Click to collapse
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
killermara said:
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
Click to expand...
Click to collapse
do what @billysam said.
dont use device specific stuff. the latest twrp will only work with unified builds. for your device you need espresso3g builds.
you will find the latest roms on android-andis github site http://andi34.github.io/index.html
killermara said:
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
Click to expand...
Click to collapse
you're using device specific Rom build, cm13.0 unofficial p5100, the latest twrp recovery you have, is a unfied espresso3g one.
latest roms, are build upon espresso3g for p5100,p3100 and espressowifi for p5110,p5113 p3113.
use latest cm13 rom zip, marked espresso3g.
there are device specific roms and recovery, which developers have stopped working on, your issue is because of this. get unified recovery and rom.
billysam said:
you're using device specific Rom build, cm13.0 unofficial p5100, the latest twrp recovery you have, is a unfied espresso3g one.
latest roms, are build upon espresso3g for p5100,p3100 and espressowifi for p5110,p5113 p3113.
use latest cm13 rom zip, marked espresso3g.
there are device specific roms and recovery, which developers have stopped working on, your issue is because of this. get unified recovery and rom.
Click to expand...
Click to collapse
Yea i thought so too, thats why i downloaded the cm-13.0-20161117-NIGHTLY-espresso3g.zip, then i wiped and tried to flash this rom, this also gave me the same error,
i also noticed that before the lines
Zip file is corrupt
there was:
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
killermara said:
Yea i thought so too, thats why i downloaded the cm-13.0-20161117-NIGHTLY-espresso3g.zip, then i wiped and tried to flash this rom, this also gave me the same error,
i also noticed that before the lines
Zip file is corrupt
there was:
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
Click to expand...
Click to collapse
maybe the zip got corrupted, checked your pc with anti-virus? are you downloading the zip file from androidfilehost of android-andi? or some other source? checked your sd card as well?
Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Install the 3.0.3-0 common TWRP, then try to format data (Wipe ->Format Data-> type yes). Reboot recovery once and then perform a wipe of all partitions (Wipe->Advanced Wipe-> select everything). If you get stuck at "updating partition details..." just wait. It could take as long as five minutes some times to get unstuck.
This is the link for the thread of Slim6, the mm rom I recommend by Andi:
https://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-slim6-t3414798/page1
And this is an aosp mm rom also by Andi, try it if above fails
http://builds.unlegacy-android.org/aosp-6.0
Flash both with TWRP 3.0.3-0
If problems continue, post the recovery log (you can find it after reboot at /cache/recovery/ )
landetta said:
Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Click to expand...
Click to collapse
have you used the twrp on the http://andi34.github.io/ website? and roms compiled before 3/22/16 dont flash with common twrp when I updated twrp I had downloaded the zip and went into twrp to flash it I havent used a pc at all to install twrp and root . so I just put the zip on my sd card and it updated it did you update twrp with odin?
Thank you for your reply,
Yes I used the recoveries from Android Andi, and yes I have installed recoveries in zip form through recovery and Odin. Unfortunately neither have worked. I did use the latest recoveries when I tried to install the newer roms but it just gets stuck, I can't even make nandroid backups it also gets stuck with the newer recoveries.
Edit:
@ john99ap Sorry i just got home, I tried what you said but it just got stuck at both wipes, I waited 10 mins but a no-go. I found the logs, I couldn't paste them in here because it exceeded character length so I put it in pastebin. I didn't know which log to use so I am giving you the ones that I think are more relevant
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
landetta said:
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
Click to expand...
Click to collapse
I can't find anything in these logs
I need the log in which you try to install the zip file.
Try this:
-Install TWRP 3.0.3-0 (if it's not already there)
-Reboot and delete all recovery logs you can find
-Install the zip without doing anything else before or after so that the log is as clean as possible
-Post any log you find
PS: you could upload logs in your reply by hitting the button with a stapler on the bottom left corner
Thanks for your reply, sorry about the old logs, here are the new ones like you requested. Hopefully you find something in these new ones. Thanks again for all your help BTW I don't have any staples in my advanced reply so I had to use Pastebin again sorry. I think its because of my low post count.
pastebin/UcntGLTZ
pastebin/Fq8V7WUf
PS: Not even the reboot button works on 3.0.3-0.
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
john99ap said:
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
Click to expand...
Click to collapse
Awe thanks anyways dude, I really appreciate you trying. One last thing, on Andi's website he say that device specific 3.0.0-0 recovery should work to flash the latest roms. If anyone can confirm this maybe I can get the new roms working on it. Thanks again for all your help john99ap :good: