I've tried using ROM manager and booting back into recovery mode but it stalls at the Google unlock screen. I've also tried installing the stock version of 2.3.2 version from Rom manager but got the same results.
I've also flashed the clockworkMod recovery to 3.0.0.5 then rebooted into Bootloader where i selected the "Recovery" option but again I only reach the Google unlock icon screen. It's been sitting at that screen for the past 20mins. Only way past it is to boot normally (after i reinsert the battery).
I have tried restoring from a previous backup but that too fails because it cant reach the recovery portion of the process after rebooting.
About Phone
Version: 2.3.2
Baseband Version: I9020XXJK8
Kernel Version: 2.6.35.7-g81433b [[email protected]#1]
CPU INFO: ARMv7 Processor Rev 2 (v7l)
Mod Version: CyanogenMod-7-02102011-NIGHTLY-NS
Build #: GRH78C
Click to expand...
Click to collapse
any help is greatly appreciated.
reflash recovery
thejron said:
reflash recovery
Click to expand...
Click to collapse
try reflashing the recovery from within the bootloader with "fastboot flash recovery recovery.img" or something like that. you should find something about this here on XDA i think.
floomat said:
try reflashing the recovery from within the bootloader with "fastboot flash recovery recovery.img" or something like that. you should find something about this here on XDA i think.
Click to expand...
Click to collapse
thx. i'll try that now.
thx for the reply, this page worked:
http://forum.xda-developers.com/sho...ighlight=fastboot+flash+recovery+recovery.img
i was able to update the ROM to 2.3.3, while in recovery mode. I rebooted the device but now when i go to Reboot>Recovery it still hangs at the google unlock screen. I think the only way for me to successfully access the recovery screen would be to connect my phone to the pc and run the fastboot boot-recovery-clockwork-3.0.0.5-crespo.img file.
headsh0tshurt said:
I think the only way for me to successfully access the recovery screen would be to connect my phone to the pc and run the fastboot boot-recovery-clockwork-3.0.0.5-crespo.img file.
Click to expand...
Click to collapse
What's happening is that Android is overwriting your custom recovery whenever it reboots.
To fix it, you first have to go back to the stock rom. Then, using either root explorer or adb, you have to rename /etc/install-recovery.sh
That way, when you flash your custom recovery, it doesn't rewrite the stock one when you reboot.
Check out this link:
http://forum.xda-developers.com/showthread.php?t=740748
edit: Also, in case someone else reads your post about using fastboot to get into recovery... the command is actually: "fastboot boot recovery-clockwork-3.0.0.5-crespo.img"
Note the space, not hyphen, between boot and the recovery image
Edit2: Ugh, the link I gave is pretty unclear (very shoddy google work). Anyway, the idea in the link is right, the command to remount your system in adb is:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
The full list of commands would be:
adb shell
su [you have to allow root access on your phone at this point - superuser will give you a popup]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /
cd etc
mv ./install-recovery.sh ./install-recovery.sh.old
kaimyn said:
What's happening is that Android is overwriting your custom recovery whenever it reboots.
To fix it, you first have to go back to the stock rom. Then, using either root explorer or adb, you have to rename /etc/install-recovery.sh
That way, when you flash your custom recovery, it doesn't rewrite the stock one when you reboot.
Check out this link:
http://forum.xda-developers.com/showthread.php?t=740748
edit: Also, in case someone else reads your post about using fastboot to get into recovery... the command is actually: "fastboot boot recovery-clockwork-3.0.0.5-crespo.img"
Note the space, not hyphen, between boot and the recovery image
Edit2: Ugh, the link I gave is pretty unclear (very shoddy google work). Anyway, the idea in the link is right, the command to remount your system in adb is:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
The full list of commands would be:
adb shell
su [you have to allow root access on your phone at this point - superuser will give you a popup]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /
cd etc
mv ./install-recovery.sh ./install-recovery.sh.old
Click to expand...
Click to collapse
i ran adb shell and entered the commands listed above. Below is a screenshot of what was entered.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now after I entered the mv ./install-recovery.sh ./install-recovery.sh.old
command it says that i can't rename the .install-recovery.sh because it doesn't exist. do i have to manually create a folder on the root with this name?
Did you go back to stock first? I think the files get deleted on a new rom, but for some reason you still have to rename the files while in stock. I had the same issue the first time I went to a custom rom.
I'm about to head to bed (asia) but I'll double check the directory in the morning.
You should also be able to Google the answer... I may have told you the wrong directory for the file. Look for something along the lines of android mount install-recovery.sh
Sent from my Nexus S using XDA App
No i didn't go back to stock prior to running the earlier cmd lines.
while in USB Debug mode, i transferred over the GRI40-2.3.3-rooted.zip into the phones' clockworkmod/backup folder. i then rebooted it into the bootloader and:
ran fastboot boot recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
I then chose the Backup & Restore option and selected to Restore the GRI40-2.3.3-rooted.
Once it was done i then selected reboot, it powered back on with full stock image. i rebooted it once more to confirm it had the stock image of 2.3.3. then from the bootloader screen i selected the recovery option and it took me to the screen with the android icon and the exclamation mark above it.
headsh0tshurt said:
No i didn't go back to stock prior to running the earlier cmd lines.
while in USB Debug mode, i transferred over the GRI40-2.3.3-rooted.zip into the phones' clockworkmod/backup folder. i then rebooted it into the bootloader and:
I then chose the Backup & Restore option and selected to Restore the GRI40-2.3.3-rooted.
Once it was done i then selected reboot, it powered back on with full stock image. i rebooted it once more to confirm it had the stock image of 2.3.3. then from the bootloader screen i selected the recovery option and it took me to the screen with the android icon and the exclamation mark above it.
Click to expand...
Click to collapse
So now if you delete or rename install-recovery.sh you should be good. For future reference
Code:
fastboot boot
Doesn't flash anything so you're literally just booting into an image so no matter what you wouldn't boot back into that image without the command again. If you want to flash a new recovery without using ROM Manager you can use the following command:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img
kenvan19 said:
So now if you delete or rename install-recovery.sh you should be good. For future reference
Click to expand...
Click to collapse
Okay I was not able to locate the file "install-recovery.sh" file on the SD, so from bootloader, I ran the code:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img
and went into recovery mode where i ran the latest nightly (cm_crespo_full-12.zip) and rebooted it more than once and each time it gets stuck @ the cyanogen mod7 boot screen....progress :/
headsh0tshurt said:
Okay I was not able to locate the file "install-recovery.sh" file on the SD, so from bootloader, I ran the code:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img
and went into recovery mode where i ran the latest nightly (cm_crespo_full-12.zip) and rebooted it more than once and each time it gets stuck @ the cyanogen mod7 boot screen....progress :/
Click to expand...
Click to collapse
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.
Suggest you try the instructions at the bottom of this page > http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
7-step process that will help you go to CMR instead of stock recovery. Worked perfectly for me.
kenvan19 said:
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.
Click to expand...
Click to collapse
yeah i copy/pasted what you wrote in my response but in actuality i wrote the correct file name into the the CMD and it went through. IF/when i get past the CM7 boot screen i'll look into the root explorer app. thx for the assist
kenvan19 said:
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.
Click to expand...
Click to collapse
.cruiser said:
Suggest you try the instructions at the bottom of this page > http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
7-step process that will help you go to CMR instead of stock recovery. Worked perfectly for me.
Click to expand...
Click to collapse
Thanks for the link. I went through the instructions and the results were the same. the end of the instructions mentions to get the Root explorer on the phone but that doesnt work b/c i cant bypass the CM7 boot screen. so i just restored it to GRI40-2.3.3-rooted.zip via the clockwork recovery
The install-recovery.sh file is missing in CM7 - you have to do this process from a stock rom.
Personally, this is exactly how I did it. You may try it this way if you like... you should have instructions for all the individual pieces.
1. Go back to stock 2.3.2
2. Get the OTA update to 2.3.3
3. Unlock your bootloader
4. Using the fastboot boot recovery method, install SU
5. Boot in to Android and then rename install-recovery.sh
6. Install rom manager
7. Flash CWM 3.0.0.5
Good luck! Who knows, maybe you have to have an unlocked bootloader to get CWM to stick.
kaimyn said:
The install-recovery.sh file is missing in CM7 - you have to do this process from a stock rom.
Personally, this is exactly how I did it. You may try it this way if you like... you should have instructions for all the individual pieces.
1. Go back to stock 2.3.2
2. Get the OTA update to 2.3.3
3. Unlock your bootloader
4. Using the fastboot boot recovery method, install SU
5. Boot in to Android and then rename install-recovery.sh
6. Install rom manager
7. Flash CWM 3.0.0.5
Good luck! Who knows, maybe you have to have an unlocked bootloader to get CWM to stick.
Click to expand...
Click to collapse
my impatience got the best of me. after restoring it to the stock 2.3.3. i just reinstalled all the applications. none of my downloaded files (music/wallpapers) were lost.
[sarcasm]just have to go through the joy of reorganizing each screen [/sarcasm]. Mostly i am pisssed that i'd have to start from scratch in Angry birds .
This happened to me with gingercollab. I did fastboot flash then booted straight to recovery and installed cm7. Everything was working fine until I restored my nandroid of gingercollab by mistake.
Sent from my Nexus S using XDA Premium App
the issue was never resolved. and i get the system update for 2.3.4 about twice a week and i cant install it b/c after it restarts it bombs out at the android icon w/ the excalamtion mark.
i've tried the factory wipe/reset thinking that would start me off clean but that didnt work.
Unless you RENAME the stock recovery it WILL NEVER STICK. Unlocked bootloader or not. I just reflash recovery from fastboot if/when I need it.
Sent from a bird cage, with a swing!
Related
Update - 2/21/2011
If you have bricked an HTC EVO this will likely NOT work for you and this is the wrong info to be reading. I have gotten a few emails from this link about EVO 110 errors.
12/26/2010 - This thread is super old now:
If you ran the 1.56 RUU and your phone no longer turns on visit htc.com, go to support, choose Hero (Sprint) and download the 2.1 system update.
Remove battery from your phone and start it up again, then run the exe file that you just downloaded -
http://member.america.htc.com/downlo...2.27.651.6.exe
------All the info below is kept for reference -------
(As of 3/31/2010 - I am 10 for 10 for getting these back and working!! 3/3 of going back to 100% stock)
Edit: I have no longer kept track... its been over a month and I know personally I've done about 15 more of these... with about half being return to stock.
If you need to contact me, PLEASE EMAIL instead of using private messages, it'll probably turn into a google talk chat anyways, so add me on there, [email protected] (Its just easier than having to log in here and reply to private messages, since I get emails on the go as well.)
So you just ran the 1.56 RUU and got a 110 error. Now your screen turns on and stays black and if you plug the phone into USB you see the HTC logo. Unplug it and see the RUU menu.
Like you, I decided to attempt to roll back using the RUU 1.56. I was hit with the 110 error, and nothing but fastboot would work, I was able to launch ./fastboot-mac oem boot to get into the system.
I tried ./fastboot-mac boot image/bootname.img and a billion other things like everyone else who is having the issue, but just like them I had no success. In the second post below are the steps to resolve this issue. This will either take you to your first Nandroid backup or to whatever ROM you choose to flash once you get recovery back. I have not found a way to get back to 100% stock, but at least your phone wont be a brick.
EDIT:As of 3/30/2010 @ 8:30 PM I was able to get my phone completely 100% to stock. I was able to do this by retrieving a Nandroid restore from someone who used flashrec to make their initial backup. This restore does not touch the recovery image but I was able to boot into my recovery then write the HTC recovery back on top of it. I now have 100% un-rooted phone. See Post number 2 for the right way to do this.?
I've helped a few people over log me in now.
I'm willing to continue doing this but it is cutting into my family time, I will do this for a "respectable" amount of money.
Feel like I've helped you??
Buy me some coffee!
(Zip attached includes fix and stock folders. Use the fix folder FIRST to get completely booted. You can use the stock folder if you want to get 100% stock after you have a running unrooted system but have RA recovery.)
Steps to resolve:
(You SHOULD have a Nandroid backup of some sort, if not download a ROM... Fresh1.1??)
1) Boot the phone to black screen
2) Plug phone into PC/MAC - The HTC logo should appear at this point
---- If you've been doing anything else, rerun the RUU and let it fail and reboot to the HTC logo.
3) PC - fastboot oem boot | MAC - ./fastboot oem boot
(Make sure you turn on USB Debugging under Settings --> Applications --> Developer)
4) Root your phone using asroot2
Code:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
5) This is where your Nandroid backup comes into play.
(Browse to your nandroid folder, find your first backup and copy all of the .img files except system and cache to your SD card root directory)
NOTE: At this point you should dismount the SD card if you mounted inside of Android OS(Sense/Launcher)
6) run adb shell (PC - adb shell | Mac - ./adb shell)
7) type su
8) Run the following commands (if you get out of memory errors, type su again and try once more)
NOTE: Do not copy the "#"'s in the commands, the # just means you are running as SU, as opposed to the "$"
Code:
# flash_image recovery /sdcard/recovery.img
# flash_image boot /sdcard/boot.img
# flash_image misc /sdcard/misc.img
9) now... type reboot recovery
This time you should get your recovery menu, should have been RA or whatever you used... from there I did a complete nandroid restore and my system booted.
Also, after I did this I did try to let it boot without doing a recovery and it wouldnt go anywhere... but I'm fairly impatient... it may have wanted to load. I figured it best to do an entire Nandroid restore though.
-------------------------------------------------------------
100% Stock Configuration Work Around
-------------------------------------------------------------
Non-Rooted Nandroid Backup:
nandroid.7z
I was able to get my phone completely 100% to stock. I was able to do this by retrieving a Nandroid restore from someone who used flashrec to make their initial backup. This restore does not touch the recovery image but I was able to boot into my recovery then write the HTC recovery back on top of it. I now have 100% un-rooted phone. I'm not sure how to go about posting a 127MB file, what do you think it the best place?
After restoring the Nandroid backup I tried this:
Code:
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb shell
$ su
su: permission denied
Then I rebooted to recovery (I used RA 1.5.2)
Code:
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb remount
remount succeeded
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb shell
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
/ # cd /sdcard
/sdcard # flash_image recovery /sdcard/Stock/recovery.img
flashing recovery from /sdcard/Stock/recovery.img
/sdcard # reboot recovery
I was booted to the Triangle and exclamation mark... I pulled the battery and booted up normally.
Stock Kernel - 2.6.27-533ce29d [email protected] )
Stock Build - 1.56.651.2 CL85027 release-keys
Other things that should be mentioned:
If you used RA 1.6.2 - I was unable to get my boot.img or the stock boot.img from the RUU's rom.zip to flash back to the recovery partition. I had to use the RA 1.6.2.img and "flash_image recovery /sdcard/recoverynamegoeshere.img"
It seems that if you've flashed the radio update, the RUU does not write the radio back successfully. Others have had issues going back to the stock radio using the upgrade.zip option as well.
I attempted to use the boot.img, recovery.img, from the RUU's rom.zip with no success. I might try it again. I was able to get to stock recovery (Triangle and exclamation) and to the Hboot menu... but from hboot I had to run the RUU and rebrick the device cause I couldnt get anything at that point, even fastboot oem boot wouldnt load.
There have been times when I get weird issues writing the flash recovery, boot, or misc and when you reboot and load "fastboot oem boot" it wont look like it goes anywhere.... check "adb devices" and your device should be listed. From there do an "adb remount" and then "adb shell" and reflash once more and then "reboot recovery".
If all else fails, I'm available for a small fee.
[email protected]
Anxiously waiting your news. Just encountered this problem today.
Updated ...
imekul said:
Anxiously waiting your news. Just encountered this problem today.
Click to expand...
Click to collapse
Wow! If you've fixed this, I think you're everyone's hero now. We won't have to worry about using the RUU now
I was going to try something similar to this today, but i was unable to brick my phone using the 1.56.651.2 RUU. I was running Flipz updated radio and DamageControl v2.0r2.. The RUU completed successfully..
I was reading over the forum post in http://forum.xda-developers.com/showthread.php?t=645002 and i read that you could boot the system using the command 'fastboot oem boot' I was going to try to use FlashRec to do the work of Flashing the recovery, then booting into recovery and use nandroid.. but you beat me to it! Good work!
I attempted flashing a new recovery image this way with no avail... I also attempted only
Code:
flash_image recovery /sdcard/recovery.img
and still was unable to boot the phone into recovery. I think it had to have been something with doing boot.img and recovery.img at the same time... I dont know what the misc.img does and I'm assuming data.img is userdata... but I did them all and then it worked...
Other users also tried flashrec and with no success... right track though.
chavo2005 said:
I was going to try something similar to this today, but i was unable to brick my phone using the 1.56.651.2 RUU. I was running Flipz updated radio and DamageControl v2.0r2.. The RUU completed successfully..
I was reading over the forum post in http://forum.xda-developers.com/showthread.php?t=645002 and i read that you could boot the system using the command 'fastboot oem boot' I was going to try to use FlashRec to do the work of Flashing the recovery, then booting into recovery and use nandroid.. but you beat me to it! Good work!
Click to expand...
Click to collapse
What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?
blankd3ckskat3r said:
What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?
Click to expand...
Click to collapse
if your using a pc type fastboot oem boot
if your using a mac type ./fastboot oem boot
This!
Thanks Regaw
regaw_leinad said:
if your using a pc type fastboot oem boot
if your using a mac type ./fastboot oem boot
Click to expand...
Click to collapse
Trying this right now.
So far, am getting lots of "mtd: write error" and "mtd: re-read error" Out of memory errors for flashing the recovery image. Guess I'll give this some time, and try to su again and reflash? Or should I kill it as soon as the Out of memory errors pop up and try again?
If you get errors like...
adb shell
su
flash_image recovery .........
(out of memory... etc)
Then...
just su again... so you really su twice
its what I had to do.
imekul said:
Trying this right now.
So far, am getting lots of "mtd: write error" and "mtd: re-read error" Out of memory errors for flashing the recovery image. Guess I'll give this some time, and try to su again and reflash? Or should I kill it as soon as the Out of memory errors pop up and try again?
Click to expand...
Click to collapse
Trying it a second time, and so far am getting a bunch of Out of memory errors. After the first one "finished," I did as you recommended and typed "su" a second time, and then typed the "flash_image recovery /sdcard/recovery.img" command.
So far, looks like it's giving the same errors the second time around.
This second attempt, it ended with "error writing recovery: No space left on device."
Just to be sure, I checked the SD card, and that has over 1 GB of free space.
If you're willing to allow something like logmein.com or some way for me to remote assist you, I would like to try. [email protected] if you're in.
imekul said:
This second attempt, it ended with "error writing recovery: No space left on device."
Just to be sure, I checked the SD card, and that has over 1 GB of free space.
Click to expand...
Click to collapse
Sounds awesome. Thanks. I'll e-mail you now.
Dun Dun Dun... The results are in!
imekul said:
Sounds awesome. Thanks. I'll e-mail you now.
Click to expand...
Click to collapse
dfbonney is the man!!
After a friendly little session on LogMeIn Express, I am good as new! How awesome!!
imekul said:
dfbonney is the man!!
After a friendly little session on LogMeIn Express, I am good as new! How awesome!!
Click to expand...
Click to collapse
We ended up just needing to run
Code:
adb shell
reboot
fastboot oem boot
adb shell
su
//flash commands here
that seemed to do it. so make sure if you're having issues to restart the device and try again!
Edit: Also, we didnt get data.img to work so we only did boot, recovery, and misc.img's
Scroll to the bottom for a fix to the newest clockwork recovery flasher...
UPDATING TO DI07
First things first, you must update to the latest firmware and kernel, but in order to do this you must un-root and return to the stock kernel in order to avoid problems.
Simply download the zip here, and run the run.bat inside, after extracting the folder to your desktop.
You must have debugging mode enabled for this to work.
Once that's finished you can update to DI07 using the stock recovery. You do this, like any other update, by renaming the zip (found here, to update.zip on throwing it onto the root of your sdcard.
Then, boot up into the stock recovery (power+camera+volume down) and press home to apply the update.zip.
The update will install and your phone will reboot into DI07.
First boot will take some time, so be patient.
Now onto the fun part, rooting your phone.
OBTAINING ROOT
Just as you obtained root before DI07, you obtain root on DI07, if you have the right tools. Download the one click root here, and once more extract the included folder to you desktop, make sure you have usb debugging enabled, and run the run.bat. Your phone will reboot, and you will have root.
FLASHING CUSTOM RECOVERY
Here is where it gets a tad bit more complicated. First off, you have to download the zip here, but this time before running the bat you have to open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code.
adb devices
adb shell
su
remount rw
exit
exit
Now the command prompt should close, and you can run the run.bat for build 31 of clockwork recovery flasher. Once more, your phone will reboot and after the script is done running and says "press any key to exit...." you can press enter and boot into recovery.
That's it, three simple steps to updating, obtaining root, and flashing clockwork recovery!
Also, don't forget to check out my ROM coming later today, as well as noobnl's Andromeda Galaxy ROM v1, just released.
great tutorial...and i can use these instructions even if i am using aridons v4 rom and heros overclocked kernel?
Well, it basically reverts you back to the stock kernal, so you will for sure lose the overclocked kernal. However, I'm not sure about the ROM. Your best bet would be either to hold off on this as the ROM you are suing isn't based on DI07, or flash to stock and then follow this guide. Your choice.
bubby323 said:
Well, it basically reverts you back to the stock kernal, so you will for sure lose the overclocked kernal. However, I'm not sure about the ROM. Your best bet would be either to hold off on this as the ROM you are suing isn't based on DI07, or flash to stock and then follow this guide. Your choice.
Click to expand...
Click to collapse
Well I just ran this and at first glance, it got me right into clockwork. I selected one of my nandroid and restored it. After the phone finished restoring and everything, I wanted to make sure that I still had clockwork but instead it was stock recovery once more.
Since I still had root, I redid the steps starting with entering the commands, then I re-ran the bat file for clockwork. I checked and clockwork is back...unknown as to how long though.
Thank you!!! the remount rw was what I needed to get the clockwork custom recovery to flash!!!
I have another question for you? Is it possible to install the custom recovery without having root? I suspect not? The reason I ask is that I would like to have a nandroid backup of the completely stock rom although I guess I could use the one noobnl has posted
well, i got back to a stock rom....applied the stock kernal...but when i went to apply the update.zip...it took me back to clockwork...not the stock recovery....so i tried to apply the update from there but it aborted...how do i get rid of clockwork so i can go into stock recovery and will that fix it?
mrkrabs said:
well, i got back to a stock rom....applied the stock kernal...but when i went to apply the update.zip...it took me back to clockwork...not the stock recovery....so i tried to apply the update from there but it aborted...how do i get rid of clockwork so i can go into stock recovery and will that fix it?
Click to expand...
Click to collapse
Three options I can think of- if you use adb reboot recovery I believe it will load the stock recovery- the other option is to use odin to go back to complete stock. Finally you could use the option for clockwork in this thread look for the link under "B]Update.zip (for clockwork recovery and includes all the listed apps below)"
EDIT: I can confirm that "adb reboot recovery" loads the stock recovery when you have clockwork
bubby323 said:
FLASHING CUSTOM RECOVERY
Here is where it gets a tad bit more complicated. First off, you have to download the zip --- but this time before running the bat you have to open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code.
adb devices
adb shell
su
remount rw
exit
exit
Now the command prompt should close, and you can run the run.bat for build 31 of clockwork recovery flasher. Once more, your phone will reboot and after the script is done running and says "press any key to exit...." you can press enter and boot into recovery.
Click to expand...
Click to collapse
Im having a little issue with this. Im running windows 7. Can I do this in windows 7? Also when it says redirect it to your C:/Android---- do I have to change the drive to ex. cd c:/ first or do i just type in the command prompt C:/android-sdk-windows/tools and hit enter and follow the rest of the commands? Sorry extreme noob here..
Thank you for any help!!
I have ClockworkMod Recovery installed, how can I get into the stock recovery to apply this?
Look 2 posts up
Sent from my SPH-D700 using XDA APP
You need to use the DG27 uninstaller instead of the DI07 uninstaller to update to DI07.
The DI07 uninstaller is just to go back to stock DI07 kernel if you already updated
DG27 uninstaller: http://www.sdx-downloads.com/devs/noobnl/one.click.stock.&.root.uninstallerv1.0.1.zip
I think it needs to be pointed out that this alone won't work if you are like me and have removed apps from the phone. All those apps must be restored in addition to reverting to stock kernel before the OTA update can be applied. At least that's how I understand it. Feel free to correct me if I'm wrong.
Thanks a lot, I appreciate step-by-step tutorials like this for noobs like myself ... this made things a lot easier since some of the stuff (files, instructions, etc.) was all over the place.
would seem that way because I removed the alarmclock to start and when i try to run update.zip from sd it fails when checking current system @ /system/app/AlarmClock.odex
i tried rerooting and reinstalling alarm clock using the backup from titanium. says it is successful but i do not find it in my apps drawer. it still fails there too..
WisdomWolf said:
I think it needs to be pointed out that this alone won't work if you are like me and have removed apps from the phone. All those apps must be restored in addition to reverting to stock kernel before the OTA update can be applied. At least that's how I understand it. Feel free to correct me if I'm wrong.
Click to expand...
Click to collapse
Titanium backup does not restore apps in /system. You have to restore those by hand.
Im officially struggling, undid the root then copy/paste the update to the sdcard, renamed it. It unzips but says its failed to open /sdcard/update.zip(no such file or directory)...suggestions?
I know that in the step it said to copy it to the root on the sd but im am very green to this stuff, and didnt see a folder marked that, therefore I just copied it to the sd card
I can't get Clockwork to flash now. I walked through the steps...I did the remount crap and ran the bat and it rebooted the phone but when i reboot into recovery it goes to the normal recovery screen. Now if I try to redo it it does not recognize the remount rw and i can't get anywhere with it and i'm stuck with no clockwork.
but this time before running the bat you have to open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code.
adb devices
adb shell
su
remount rw
exit
exit
Click to expand...
Click to collapse
This part is unnecessary because the recovery zip comes with adb built in
is there a manual way to push this to the phone? These one clicks never seem to work for me ever it's just easier to do it myself.
Whosdaman said:
This part is unnecessary because the recovery zip comes with adb built in
Click to expand...
Click to collapse
No you must do this in order to get clockwork.
WARNING: IN THE EVENT THAT ANYTHING GOES WRONG, I WILL NOT BE HELD ACCOUNTABLE. I CANNOT STRESS THIS ENOUGH!!!
EDIT: I FORGOT, BEFORE CHANGING RECOVERY OR DOING ANYTHING, ALWAYS DO A NANDROID BACKUP!!!
If you have flashed a custom recovery (clockwork, j_r0dd, etc.) but you want to
1) accept OTA updates but cant do so with the custom recovery
2) send your phone for repair and not void your warranty
3) or UNROOT YOUR PHONE,
it should be easy to revert back to your stock recovery that came with your phone.
NOTE: THIS PROCEDURE WILL ONLY WORK IF THERE IS AN AVAILABLE OTA UPDATE FOR YOUR PHONE!!!
YOU WILL HAVE TO RE-ROOT YOUR PHONE IF YOU WANT ROOT ACCESS AFTER UPDATING! DO NOT RE-ROOT IF YOUR PHONE IS TO BE SENT FOR REPAIR!
Step 1) Download the OTA update. (I have a uploaded a sample update zip at
www . sidsoftinc . com / Blur_Version.0.3.9.MB300.Retail.en.03.zip
*remove the spaces)
Step 2) On completion, the phone should reboot and enter recovery mode, using the custom recovery to update. However, this should fail as most custom recoveries prevent original updates. Note the location of the downloaded update (likely at /cache)
Step 3) Power down the phone and enter into recovery mode manually
Step 4) Using ADB, pull the folder containing the update zip to your computer
Code:
adb pull /**storedlocation**/**nameoftheupdate**.zip update.zip
Step 5) Open the update.zip in your adb folder and look for a file called recovery.img (most likely in system folder)
Step 6) Open up the adb shell and flash the new recovery (recommended)
Code:
adb shell
su
flash_image recovery recovery.img
or you can place it in /system and it will be auto-flashed (not recommended)
Code:
adb push recovery.img /system/recovery.img
Step 7 (if possible) Make it permanent by deleting the custom recovery in /system
Code:
adb shell
cd system
su
mount -o rw,remount /dev/block/mtdblock1 /system
rm recovery.img
mount -o ro,remount /dev/block/mtdblock1 /system
exit
exit
Step 8) Reboot the phone and if you see a triangle warning sign, reboot your phone again. You should see your homescreen before it reboots to install the update again. This time, the original recovery will be used.
Once finished, your phone will be upgraded, unrooted and your applications and data will still be retained.
If you wish to install your previously used custom rom again, you must flash the custom recovery and install the rom, again
If I made a mistake, please do inform me. Thank you
I'm trying to do this for the Tmo G2 and I have reverted using another technique but the clockworkmod is still there. I thought it would get removed!
I have no idea how to get rid of it. Can you give me alittle help?
Did your clockworkmod recovery flash itself into your nv ram. If so then no one can help you there. If you have an ota update and pulled it to your pc, send me a coy and I'll see if I can help you. If you can, send me your ota update zip to [email protected].
Sent from my Motorola Backflip using the XDA App
I'm honestly unsure if it flashed to the nv-ram. Possibly, basically if I do a system boot (power +vol down) and select recovery, it will load the HTC green text with white background then go into clockword recovery. I'm not exactly sure why it still does this.
I used the method on this FORUM THREAD to un-root and get back to stock (using the available files there and method 1-a). I'm just unsure why the clockwork recovery is still there. I'm hoping I can still get back to stock recovery. Possibly I just need to flash the stock recovery.img??
Also, I had some troubles initially with ADB, which is why I used the VISIONary method of rooting. I'd love to try out the gfree method since I believe my ADB is working correctly now and test out some other roms to see what I like the most.
I know you are probably in a different time zone that is way ahead of mine........but can't I just reflash the stock or update ota recovery.img in fastboot mode.......OR is this a bad Idea???
Many users have accidently accepted ota updates on custom rims and recoveries. for fastboot, I did mention that flashing stock recovery and update is possible via adb shell.
Sent from my Motorola Backflip using the XDA App
siidheesh said:
Many users have accidently accepted ota updates on custom rims and recoveries. for fastboot, I did mention that flashing stock recovery and update is possible via adb shell.
Sent from my Motorola Backflip using the XDA App
Click to expand...
Click to collapse
I tried flashing the stock recovery but I'm not sure why it didn't work, I had hboot and flash_image. I used the adb shell way as well. It gave me error in partitions or whatever. I don't know what to do.
do you have Blur_Version.0.3.10.MB300.Retail.en.03.sbf file?
I dont happen to have that file, but i do have Blur_Version.0.3.9.MB300.Retail.en.03.zip
if you need it.
Cockwork Mod
I'm pretty green so this may sound really dumb, but can you flash sbf files to your phone via Clockwork Mod, or does it have to be done via RSD Lite. I cannot get RSD to recognize my device in 4.7 or 4.8. Please help.
do you have a stock image for the huawei ascend for cricket or does anyone here have it?
Unrooting......
I download the RECOVERY file you supplied (thank you)
"Blur_Version.0.3.9.MB300.Retail.en.03.zip"
If I reboot into Recovery and just flashed that zip file, would it work that way to unroot?
Provided you are flashing on a MOTOROLA BACKFLIP, yes. However, you might want to flash the AT&T 2.1 update for the backflip instead, if you reside in the US. Flashing back any official firmware unroots your phone
I'm looking to root and unlock my AT&F Motorola Backflip (MB300).. Any suggestions?
Sent from my NexusHD2 using Tapatalk
OTA for Samsung Galaxy Ace is a CFG file, not ZIP
Hello,
Just for interest, I received an OTA for my Samsung Galaxy Ace but it didn't come as a ZIP file - it came as a CFG file (which is not a ZIP, but actually a proprietary package - which I can't remember the name right now).
However, I did find the stock recovery elsewhere in this forum, and I installed it. But that wasn't enough for the OTA to be installed - it still fails.
Corrupted?
siidheesh said:
Step 5) Open the update.zip in your adb folder and look for a file called recovery.img (most likely in system folder)
Click to expand...
Click to collapse
I can't find it. I have an Alcatel Pop C1 4015X. Help?
Trying to unroot Xperia Z2
I am trying to unroot using update files from the Sony Xperia Companion. I found the update files (I think). I used Flashtool to decrypt the FILESET, but there is no recovery.img in the decrypted folder. The folder I decrypted is in Xperia Companion/Sony Mobile Update Engine/localstorage/db/13740270 and that is the only folder that has decryptable files. They are named FILE_8977018 and similar before decryption and various .sin .ta files (examples auto-boot.ta, cust-reset.ta, simlock.ta). Am I using the right decryption to get the recovery.img?
Liberty still has something no other device has - ARIA!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
..........
Downloads:
cwm-5.0.2.3-liberty-agse.zip AGSE (ARIA) Edition - with cap key lights enabled
cwm-5.0.2.3-liberty.zip Stock Clockworkmod 5.0.2.3 - with cap key lights enabled
attn1 said:
Liberty still has something no other device has - ARIA!
Download: cwm-5.0.2.3-liberty-agse.zip
Click to expand...
Click to collapse
and apparently , interesting background images
*****
I am still on v2.5.0.1 - and help on how to install this img?
Thanks so much attn1!
Edit: found this for instructions, would this do?.....
HTML:
http://forum.xda-developers.com/showthread.php?t=1122694
here's 2 ways to do it:
if you have s-off:
boot phone into fastboot mode
hook phone to computer with usb cable
ON COMPUTER:
unzip cwm-5.0.2.3-liberty-agse.zip
command prompt
fastboot flash recovery cwm-5.0.2.3-liberty-agse.img
without s-off: (this is what I did, didn't have a USB cable handy)
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
tommyguns818 said:
Thanks so much attn1!
Edit: found this for instructions, would this do?.....
HTML:
http://forum.xda-developers.com/showthread.php?t=1122694
Click to expand...
Click to collapse
yep, if you are s-off with Revolutionary or AlpharevX.
Nutshell69 said:
and apparently , interesting background images
Click to expand...
Click to collapse
that's Aria herself.
Looking forward to the HTC Jenna
Sent from my Liberty using XDA App
i was wondering.....i've got s-off but no computer around me at the moment. is there a way to install this through the terminal app? I see sObe did it via terminal way but im not sure if he's s-off or not.
EDIT: I went for it and did it through terminal just like sObe and I have s-off. Worked like a charm. Thanks guys!!!
When I chose internal card I get
E:Can't mount /emc/
???
s0be said:
here's 2 ways to do it:
without s-off: (this is what I did, didn't have a USB cable handy)
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
Click to expand...
Click to collapse
tried this twice still failing :S
do i need to be running a certain rom?
I get through su just fine, i cd to the /sdcard/download (where my img is)
type in the flash_image .....
getting sh: flash_image: command not found
so looks like the terminal emulator isnt getting the PATH correctly
echo $PATH returns
/data/local/bin:/sbin:/system/sbin:/system/bin:/system/xbin
ug.
If your doing it through terminal, you need to make sure that your doing it exactly as shown in s0bes post. Also make sure that you have your new cwm 5.0.2.3 download in the download folder on your sd card.
Nutshell69 said:
tried this twice still failing :S
do i need to be running a certain rom?
I get through su just fine, i cd to the /sdcard/download (where my img is)
type in the flash_image .....
getting sh: flash_image: command not found
so looks like the terminal emulator isnt getting the PATH correctly
echo $PATH returns
/data/local/bin:/sbin:/system/sbin:/system/bin:/system/xbin
ug.
Click to expand...
Click to collapse
probably any aosp or cm based rom would work. the stock cleaned up roms, not so much.
Aside from the background thing, what advantages does this recovery have over 2.5.1.7? Is it faster? are the backups compatible?
T
s0be said:
probably any aosp or cm based rom would work. the stock cleaned up roms, not so much.
Click to expand...
Click to collapse
yea - i think thats the problem - not running a cm rom - will install 209 and try
thanks
***EDIT***
Installed CM 211 ROM
did these steps
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
getting errors :
mtd: erase failure at 0x00000000 (I/O error)
.......
thoughts?
Also curious of the benifit vs backward or forward compatibility gotchas. Anyone?
Edit. Tried to instal and get the same errors as above. S-on
Sent from my Liberty using XDA App
Nutshell69 said:
yea - i think thats the problem - not running a cm rom - will install 209 and try
thanks
***EDIT***
Installed CM 211 ROM
did these steps
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
getting errors :
mtd: erase failure at 0x00000000 (I/O error)
.......
thoughts?
Click to expand...
Click to collapse
Perhaps you can't flash a recovery from the rom without s-off? I'm not an expert to say that's the case... If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago. You might try rebooting into recovery, and using adb shell to do those steps. If you don't have ADB available, this may be beyond an easy upgrade.
I know of no advantages of this recovery over 2.5, btw.
SoCalHTCFuze said:
Also curious of the benifit vs backward or forward compatibility gotchas. Anyone?
Edit. Tried to instal and get the same errors as above. S-on
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
s0be said:
Perhaps you can't flash a recovery from the rom without s-off? I'm not an expert to say that's the case... If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago. You might try rebooting into recovery, and using adb shell to do those steps. If you don't have ADB available, this may be beyond an easy upgrade.
I know of no advantages of this recovery over 2.5, btw.
Click to expand...
Click to collapse
In fact, you cannot flash a recovery without S-OFF, unless you use the original unrevoked tool and select custom recovery (the original unrevoked only managed to install a custom recovery which was good enough at the time).
The whole point of S-OFF is that you can flash the system partition. Like Gene said, if you don't have S-OFF, you'd need to unroot and use unrevoked again.
If you do have S-OFF, it's easy:
(OS X)
md5 /path/to/cwm-5.0.2.3-liberty-agse.img (confirm md5 sum)
./adb devices (confirm you're connected)
./adb reboot bootloader
./fastboot-mac devices
./fastboot-mac flash recovery /path/to/cwm-5.0.2.3-liberty-agse.img
./fastboot-mac reboot
./adb reboot recovery (wait to hit enter until the boot animation starts)
I haven't used it yet but I hear the backups are faster in 5.x
^^^ 5.0.2.3 is a little faster. I saw the new option to fix permissions in the recovery and tried it. Man it took like 30 min to run and chewed about 60 percent of battery. From now on I'll just use ROM manager. It never failed me and is way quicker. On further note....I like it. Go miss aria!
s0be said:
If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago.
Click to expand...
Click to collapse
Just so people in this situation are aware, you do not have to "unroot" your phone first. Just run Unrevoked a second time on your device and it will overwrite the recovery with the one you select.
drumist said:
Just so people in this situation are aware, you do not have to "unroot" your phone first. Just run Unrevoked a second time on your device and it will overwrite the recovery with the one you select.
Click to expand...
Click to collapse
egads - got this error
Error: failed to get root. Is your firmware too new?
Hi everybody,
I upgraded to Lollipop using the original image. Everything was fine. No problem of any kind. Then I decided to flash the TWRP recovery. At the first run (just after installation) it was there and worked fine (I even made a backup). However, after a reboot when I went to the recovery I found that it was the stock recovery and TWRP was gone. The back up is also gone from my internal storage. The same thing happened when I flashed the latest version of CWM. After a reboot the flashed recovery is gone.
Please help. Thanks in advance.
joojooman said:
Hi everybody,
I upgraded to Lollipop using the original image. Everything was fine. No problem of any kind. Then I decided to flash the TWRP recovery. At the first run (just after installation) it was there and worked fine (I even made a backup). However, after a reboot when I went to the recovery I found that it was the stock recovery and TWRP was gone. The back up is also gone from my internal storage. The same thing happened when I flashed the latest version of CWM. After a reboot the flashed recovery is gone.
Please help. Thanks in advance.
Click to expand...
Click to collapse
are you using.. fastboot flash recovery recoveryname.img or fastboot boot recovery recoveryname.img?
simms22 said:
are you using.. fastboot flash recovery recoveryname.img or fastboot boot recovery recoveryname.img?
Click to expand...
Click to collapse
I have used "fastboot flash recovery recovery.img"
joojooman said:
I have used "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
well, if you used boot instead of flash, itll only boot the recovery for a one time use. flash should make it stick. if not sticking, flash a recovery 2 or 3 times, itll stick eventually.
simms22 said:
well, if you used boot instead of flash, itll only boot the recovery for a one time use. flash should make it stick. if not sticking, flash a recovery 2 or 3 times, itll stick eventually.
Click to expand...
Click to collapse
Thank you, I will try that and then report...
Do you have the latest version of the recovery and the root files?
I used CF Root as Chainfire is the man. I ran it first, then I added the recovery.
It stuck for me.
Remove the scripts etc that install recovery such as inatall-recovery.sh and recovery.boot.p in system and system/bin
Just double check your install-recovery.sh isn't one used to call su because you don't want to remove that if it is.
simms22 said:
well, if you used boot instead of flash, itll only boot the recovery for a one time use. flash should make it stick. if not sticking, flash a recovery 2 or 3 times, itll stick eventually.
Click to expand...
Click to collapse
I flashed ( flash .img ) the recovery 2 or 3 times (even more) but it won't stick. If I do not reboot to system it remains there but as soon as I reboot to system it is gone.
joojooman said:
I flashed ( flash .img ) the recovery 2 or 3 times (even more) but it won't stick. If I do not reboot to system it remains there but as soon as I reboot to system it is gone.
Click to expand...
Click to collapse
you want to find and rename or delete install-recovery.sh in /system/. thats whats replacing your recovery with stock.
simms22 said:
you want to find and rename or delete install-recovery.sh in /system/. thats whats replacing your recovery with stock.
Click to expand...
Click to collapse
I actually tried that, but had the following problem:
Code:
sudo adb shell mv /system/bin/install-recovery.sh{,.bak}
mv: rename /system/bin/install-recovery.sh to /system/bin/install-recovery.sh.bak: Read-only file system
Do you have an idea how I can come around this issue?
edit: I have figured that out, check post #15
tweaked said:
Do you have the latest version of the recovery and the root files?
I used CF Root as Chainfire is the man. I ran it first, then I added the recovery.
It stuck for me.
Click to expand...
Click to collapse
I do not want to root. Is it possible? I just want to have recovery. The problem is remained.
joojooman said:
I do not want to root. Is it possible? I just want to have recovery. The problem is remained.
Click to expand...
Click to collapse
From my understanding you need root to be able to edit files in /system. And in there is the script that "misbehaves" for us.
But I've not quite understood how to come by the read only file system problem
naro said:
From my understanding you need root to be able to edit files in /system. And in there is the script that "misbehaves" for us.
But I've not quite understood how to come by the read only file system problem
Click to expand...
Click to collapse
Does it mean that lollipop behaves differently from KitKat? I could have recovery without root there. It stuck at the first flash. But now it is removed every time I boot to the system.
I've ran into the same problem except for me I'm not even getting stock recovery. I don't even have one lol
Okay guys so I figured out how to get it to work (and the recovery to stick!)
First of all, get root. CF Auto root is your friend here.
Now to the problem: The recovery seems to be "reflashed" at every boot. (with an "empty" recovery).
To fix it, boot your phone up and connect it to a pc that has adb installed.
remember to not use sudo under windows, just keep that part out
Code:
sudo adb shell
Now you are on a shell in your android. Since /system is mounted readonly, we first have to remount it:
Code:
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /system
now change the install script (I just added a .bak to the name so we do not have to delete it) and remount the filesystem and read only again:
Code:
[email protected]:/ # mv /system/bin/install-recovery.sh{,.bak}
[email protected]:/ # mount -o ro,remount /system
Finally flash the recovery as you are used to, it will now stick:
Code:
sudo adb reboot-bootloader
sudo fastboot flash recovery openrecovery-twrp-2.8.1.0-hammerhead.img
sudo fastboot reboot
From here on, you are back in android and your recovery should have sticked
Maybe you should go to system and find a file like this
recover --from--boot
then delete it
Alright, well the above solution definitely helped, but now when i try to enter super su, it tells me the binaries arent updated and the root needs to be done manually.....but didnt i just do this?
naro said:
From my understanding you need root to be able to edit files in /system. And in there is the script that "misbehaves" for us.
But I've not quite understood how to come by the read only file system problem
Click to expand...
Click to collapse
joojooman said:
Does it mean that lollipop behaves differently from KitKat? I could have recovery without root there. It stuck at the first flash. But now it is removed every time I boot to the system.
Click to expand...
Click to collapse
You can have a recovery without root. Also root is only "in" android. If your recovery has a file manager, it can edit /system files without root because android isn't running lg, ergo no protection. Its just like taking a hard drive out of a computer and adding it as a 2nd in another computer. You don't need that computers password to get the data.
So flash the ROM and see if you can delete them using the recovery file manager or adb whilst booted into recovery
---------- Post added at 08:45 AM ---------- Previous post was at 08:43 AM ----------
naro said:
Okay guys so I figured out how to get it to work (and the recovery to stick!)
First of all, get root. CF Auto root is your friend here.
Now to the problem: The recovery seems to be "reflashed" at every boot. (with an "empty" recovery).
To fix it, boot your phone up and connect it to a pc that has adb installed.
remember to not use sudo under windows, just keep that part out
Code:
sudo adb shell
Now you are on a shell in your android. Since /system is mounted readonly, we first have to remount it:
Code:
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /system
now change the install script (I just added a .bak to the name so we do not have to delete it) and remount the filesystem and read only again:
Code:
[email protected]:/ # mv /system/bin/install-recovery.sh{,.bak}
[email protected]:/ # mount -o ro,remount /system
Finally flash the recovery as you are used to, it will now stick:
Code:
sudo adb reboot-bootloader
sudo fastboot flash recovery openrecovery-twrp-2.8.1.0-hammerhead.img
sudo fastboot reboot
From here on, you are back in android and your recovery should have sticked
Click to expand...
Click to collapse
This was all unnecessary.
boot recovery
Flash ROM
mount system
adb shell
rm /system/blah
That was all.
Re
I had the same problem yesterday except that i was intending to install both root and TWRP recovery. I flashed TWRP and ran it then installed supersu, the root did not work and TWRP was gone after rebooting the system.
I used the "cf auto root" utility made by chainfire. It worked (even though the root has few bugs)
I noticed that cf-auto-root flashed some boot img before installing root and twrp. I think you may want to give it a look.
rootSU said:
This was all unnecessary.
boot recovery
Flash ROM
mount system
adb shell
rm /system/blah
That was all.
Click to expand...
Click to collapse
This is what I did:
Boot to recovery-->
Flashing TWRP img-->
Then immediately going to TWRP file manager-->
Changing install-recovery.sh to install-recovery.sh.old -->
Then immediately made a backup --> reboot to system, turning the cellphone on and off several times
TWRP is there BUT:
The only point is that I cannot see the backup folder in my internal storage. It is clear that it has taken some
space (almost 2GB) but I cannot see the TWRP backup folder.