Ok, so i have a fresh new stock of 21e flashed onto my phone. Rooted with no errors, and I have Clockwork ROM Manager installed.
If I use the app to boot into recovery my phone just automatically Wipes all data then loads back up as if a fresh install was done, so I thought I would check the problem out myself (Power and vol.down), and the only options I have in the Clockwork Boot Menu are as follows:
Android system recovery <3e>
Confirm wipe of all user data?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes -- delete all user data
No
No
No
Click to expand...
Click to collapse
If I go back one page the only options I have are as follows:
Android system recovery <3e>
Android system recovery utility
reboot system now
wipe data/factory reset
wipe cache partition
wipe cache partition and package recovery
wipe nv dynamic partition
Click to expand...
Click to collapse
I can not go back any further, they are my only options in boot recovery of which I find extremely odd. (Until this is sorted I can not install a new ROM/Kernel and fix my network)
Any help would be much appreciated.
Kind Regards.
Loopy Frog said:
Ok, so i have a fresh new stock of 21e flashed onto my phone. Rooted with no errors, and I have Clockwork ROM Manager installed.
If I use the app to boot into recovery my phone just automatically Wipes all data then loads back up as if a fresh install was done, so I thought I would check the problem out myself, and the only options I have in the Clockwork Boot Menu are as follows:
If I go back one page the only options I have are as follows:
I can not go back any further, they are my only options in boot recovery of which I find extremely odd. (Until this is sorted I can not install a new ROM/Kernel and fix my network)
Any help would be much appreciated.
Kind Regards.
Click to expand...
Click to collapse
That's not ClockworkMod.
That's the stock Android recovery.
ah lol (embarrassing)
Thanks though... ok so it seems that my problem is that the copious amount of things that I try to install clockwork boot, it just wont happen. Any ideas?
Regards
Loopy Frog said:
ah lol (embarrassing)
Thanks though... ok so it seems that my problem is that the copious amount of things that I try to install clockwork boot, it just wont happen. Any ideas?
I am just about to see if I can do something with the LGDP2 V36 UMTS.
Regards
Click to expand...
Click to collapse
You can flash ClockworkMod Recovery with this.
[GUIDES/TOOLS]Making Developing/Flashing/Returning to Stock Easier
The Dark Lestat said:
1. Recovery Manager
This is a flashing tool that will let you install:
Stock Recovery
ClockworkMod Recovery
Touch ClockworkMod Recovery
Requirement:
You'll need to have the LG Thrill / Optimus 3D
You'll need to be rooted.
Superuser and SU have to be updated to the latest app and binary
Update Superuser in the market
Open Superuser app and go to the options
Scroll to the bottom and click "Su binary"
DOWNLOAD LINK: Recovery Manager - 18 MB
How To Use:
Extract the files with WinRar or 7zip
Launch "Recovery Manager.bat"
Make sure your phone is in "USB Debugging Mode" and is plugged in
Choose your option
Wait for the screen to refresh
Boot into recovery to verify it was flashed successfully
Click to expand...
Click to collapse
No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?
Loopy Frog said:
No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?
Click to expand...
Click to collapse
Try: 3d+volume down+power button
hold til 3 sec after seeing the logo.
Loopy Frog said:
No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?
Click to expand...
Click to collapse
You can also use the ROM Manager app to boot into recovery.
p-vlad said:
Try: 3d+volume down+power button
hold til 3 sec after seeing the logo.
Click to expand...
Click to collapse
Nope doesn't work. >_<
The Dark Lestat said:
You can also use the ROM Manager app to boot into recovery.
Click to expand...
Click to collapse
Yeah that's what I was using when it used to work, however now when I do it, It just "deletes all user data". Obviously because it is not having any response from the Clockwork recovery boot, and goes straight into:
Android system recovery <3e>
Confirm wipe of all user data?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes -- delete all user data
No
No
No
Click to expand...
Click to collapse
I just don't understand why My boot wont change from android to the clockwork boot. >_<
Is it being flashed properly?
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
(I took the commands from The Dark Lestat's batch file, props go to him. I was too lazy to search for it Don't judge me, it's 12.30am here)
pandaball said:
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
Click to expand...
Click to collapse
Thanks Panda, I'll give it ago later when I have time, and let ya know how I go.
Loopy Frog said:
Thanks Panda, I'll give it ago later when I have time, and let ya know how I go.
Click to expand...
Click to collapse
Also, I'll update the scripts with a newer version, so that it's simplified.
Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!
JastaPein said:
Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!
Click to expand...
Click to collapse
It's not using ROM Manager to BOOT into recovery.
It's using ROM Manager to install ClockworkMod that was the issue.
Very weird indeed. I also have flashed yhe 21E rom from LG. Next I rooted the phone and installed CWM touch. I have no problems with it.
JastaPein said:
Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!
Click to expand...
Click to collapse
Thanks, either/or this doesn't matter at this stage, I need to able to boot into recover for this or even clockwork to do it anyway. I'll keep this in mind nonetheless.
pandaball said:
Is it being flashed properly?
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
(I took the commands from The Dark Lestat's batch file, props go to him. I was too lazy to search for it Don't judge me, it's 12.30am here)
Click to expand...
Click to collapse
All went well, expect for the last string, see below;
I renamed "recovery-clockwork-touch-5.8.1.5-p920" - "x"
C:\Users\Astro\ADB>adb push x.img /data/local/tmp
3204 KB/s (5995063 bytes in 1.827s)
C:\Users\Astro\ADB>adb shell su -c "dd if=/data/local/tmp/x.img of=/dev/block/mmcblk0p6 bs=4096"
1463+1 records in
1463+1 records out
5995063 bytes transferred in 0.992 secs (6043410 bytes/sec)
C:\Users\Astro\ADB>adb shell "rm/data/local/tmp/x.img"
rm failed for /data/local/tmp/x.img, No such file or directory
Click to expand...
Click to collapse
Loopy Frog said:
All went well, expect for the last string, see below;
I renamed "recovery-clockwork-touch-5.8.1.5-p920" - "x"
Click to expand...
Click to collapse
I'm about to upload a newer version of it. Let me know if it works.
Alright.
Here's the new Recovery Manager with updated scripts. It should be a lot cleaner now.
Recovery Manager
The Dark Lestat said:
Alright.
Here's the new Recovery Manager with updated scripts. It should be a lot cleaner now.
Recovery Manager
Click to expand...
Click to collapse
You my friend, are truly amazing!! what ever your alterations were; it worked!
Thank you.
Loopy Frog said:
You my friend, are truly amazing!! what ever your alterations were; it worked!
Thank you.
Click to expand...
Click to collapse
I think it's because my scripts were thrown together in the previous one.
Anyways, it's cleaned up.
Glad it worked!
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
All credit for this goes to Razor950
Coby Kyros MID-7015
Download recovery.img from Sendspace.com - send big files the easy way
use flash_image and flash recovery to tablet. (ex flash_image recovery /sdcard/recovery.img)
Navigating:
Home is down
Menu is select
Back is back
Everything works and I'll post stock nandroid dumps on here soon.
Update some are reporting that they are unable to Flash to the recent firmware update that was posted
on the coby website do to the clockworkmod being installed.
Thanks to Kasten for coding this then thanks to adamdietrick for creating a new zip
That can be flashed with the clockworkmod installed.
Clockworkmod Coby Firmware update
Donate if you like Razor950's work!
thanks for posting
any issues that anyone gets with this recovery, please pm me.
enjoy
havic said:
Everything works and I'll post stock nandroid dumps on here soon.
Donate if you like Razor950's work!
Click to expand...
Click to collapse
Here's my backup
http://www.megaupload.com/?d=5ALHYN80
You must be rooted (I assume z4root or universal android root works)
then either using terminal (grab terminal app from market) or using adb.
Grab the recovery.img and drop it into sdcard via usb or adb push.
Open terminal and type su and then flash_image recovery /sdcard/recovery.img
or if using adb, its adb shell and then su and then flash_image recovery /sdcard/recovery.img
Note: I am not the best at writing noobie guides but hopefully it helps
Thanks for this. I do not have mine yet( lol, just ordered it) but I donated for your work!
Thanks!
Anyone have a idea on how to get back into recovery? I have it installed but have tried holding every button to get me back and nothing kinda sucks since I have been testing new mods for this and cant get to my backup because the first shot at the mod was a fail.
I was able to get clockwork installed thanks to you. Do you know of any images that are out for the 7015?
Lawful123 said:
I was able to get clockwork installed thanks to you. Do you know of any images that are out for the 7015?
Click to expand...
Click to collapse
Aside from stock(rooted) dump, there is nothing, I'll work with havic to get a rooted dump with google apps(market mostly) working correctly.
Besides that there is nothing else from my end for now. I personally don't like telechip tablets, bad experience from a gentouch :X
Also telechip company are retards and don't release kernel source, it'd help developers optimize a 2.1 rom and also be able to port kernel to a newer one for 2.2
I can see that this model gained popularity this black Friday. We are just now starting to see android tablets hit " Joe User ". I think that the telechip tabs will become popular so long as the price is on point. Thanks for all you do.
what exactly is this recovery for?
does installing this offer me additional features, or is it merely what we would restore to in case of disaster?
Deenybird said:
what exactly is this recovery for?
does installing this offer me additional features, or is it merely what we would restore to in case of disaster?
Click to expand...
Click to collapse
For now it is a good way to backup your unit so that if you screw it up you can go back. In the future people will make images for it. Hopefully someday android 2.2
Which version of flash_image tool is needed to flash this recovery or is the tool stock on the tablet?
EDIT: figured it out. stock. Looking through the dump now =)
adamdietrick said:
Here's my backup
http://www.megaupload.com/?d=5ALHYN80
Click to expand...
Click to collapse
If you try and recover from the backup that is in the link you may or may not get a error.The error is md5 mismatch. So the recovery fails to install.
What needs to be done is need to have busybox installed then shell in and run the following commands.
This has to be ran from the dir. that contains the backup files.
Which will more than likely be similar to this
/sdcard/clockworkmod/backup/2010-12-01.20.41.18
#busybox md5sum -c nandroid.md5
boot.img: OK
cache.img: OK
data.img: OK
recovery.img: OK
system.img: OK
# reboot recovery
reboot recovery
Once in clockwork then run a recovery.
If you have a Issue let me know I will try my best to get you some answers.
razor950 said:
You must be rooted (I assume z4root or universal android root works)
then either using terminal (grab terminal app from market) or using adb.
Grab the recovery.img and drop it into sdcard via usb or adb push.
Open terminal and type su and then flash_image recovery /sdcard/recovery.img
or if using adb, its adb shell and then su and then flash_image recovery /sdcard/recovery.img
Note: I am not the best at writing noobie guides but hopefully it helps
Click to expand...
Click to collapse
When I type this it it says its file not found.
I double checked and in astro I see
sdcard/recovery.img
any ideas?
beccaannabell said:
When I type this it it says its file not found.
I double checked and in astro I see
sdcard/recovery.img
any ideas?
Click to expand...
Click to collapse
where are you when you type that? does it not find the flash_image binary or the .img?
Worked for me
I got it working by doing the following.
1. Download and installed "Android Terminal Emulator" on to the device.
2. Download and installed Z4Root 1.3.0.apk from here http://forum.xda-developers.com/showthread.php?t=833953
3. Run it and pressed the "Permanent Root" button. It took a bit and it auto rebooted.
4. Place the recovery.img on the root of my sd card. (Razor950's recovery.img is from post#1 on this thread.)
5. Opened "Android Terminal Emulator".
6. Entered the following.
su
flash_image recovery /sdcard/recovery.img
7. Locked everything up for about 5 min and it went back to # prompt when it was done.
8. I powered off the device.
9. After it turned off I pressed and held the back button then pressed the power button. Kept holding it until you see clockworkMod v2.5.1.3. (If it says Android it's too late.)
I have a question myself what is sd-ext on clockwork? Also is there a way to do a selective backup? Just system with no data?
Thanks.
Thanks for your procedure, will try it when I receive my tablet.
Regarding your question about sd-ext, it's a partition of your sdcard. One will be in fat32 and the other in ext2 or ext3. Usually ext2 is used when you have app2sd or 12sd+. The purpose of this is to have more apps in install by installing them on your ext partition instead of internal memory. I use it for my HTC desire (smartphone)
Regarding your second question, I don't know anyway of doing a backup without data but pretty sure it's possible, for example, if you go in your Android do a factory reset. reboot in recovery then do your backup. Not sure if there's another way to do it
Yezir!
Kasten said:
I got it working by downing the following.
1. Download and installed "Android Terminal Emulator" on to the device.
2. Download and installed Z4Root 1.3.0.apk from here http://forum.xda-developers.com/showthread.php?t=833953
3. Ran it and pressed the "permit root" button. It look a bit and it auto rebooted.
4. Place the recovery.img on the root of my sd card.
5. Opened "Android Terminal Emulator.
6. Entered the following.
su
flash_image recovery /sdcard/recovery.img
7. Locked everything up for about 5 min and went back to # prompt when done.
8. Powered off device.
9. Press and held the back button then pressed the power button. Kept holding it until I saw clockworkMod v2.5.1.3. (If it says Android its too late)
I have a question myself what is sd-ext on clockwork? Also is there a way to do a selective backup? Just system with no data?
Thanks.
Click to expand...
Click to collapse
this is perfect!!!!! thanks for thinking of us dummies
Daali said:
where are you when you type that? does it not find the flash_image binary or the .img?
Click to expand...
Click to collapse
same thing for me
"error opening /sdcard/recovery.img:No such file or directory"
Help
noonerealy said:
same thing for me
"error opening /sdcard/recovery.img:No such file or directory"
Help
Click to expand...
Click to collapse
Can you see the recovery.img on your sd card from a file manger app like Astro? If so when your in the terminal can you cd to /sdcard? If so can you enter ls -l recovery.img? Check the size to make sure it is all there.
I have anther question myself.
At cobyusa.com/?p=prod&prod_num_id=10498&pcat_id=1013 there is a firmware update. in the update.zip in system in the build.prop file i see a line that says "ro.build.version.incremental=eng.enzo.20101125.200217". I notice that the build number on the device says "MID7015 1.6a_20101105-2". Looks like they may have changed somethings but not sure what. What would be bet best way to figure out what they changed?
I tried to run it from clockwork and i get
assert failed: getprop("ro.product.device") == "tcc8900" || getprop("ro.build.product") == "tcc8900"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
To install this update would I just have to unroot my device? Not sure how to look what the current ro.build.product is now.
Thanks.
Hi.
First, I'd like to say I tried searching but no luck.
Second, I'm a total Asus noob. I'm pretty good with my HTC Legend, but I don't quite understand the transformer.
My problem: It boots directly into recovery. I bought it used, and it was rooted and running ARHD. When I bought it the seller showed me how to boot it : Boot it regularly, then select "reboot" in recovery, hold "vol-" and it boots into some sort of "menu" where I should press "vol+" to do a cold boot. This is necessary every time. He claimed that all rooted Transformers were like this; I highly doubt that.
So, is there any way I can make it boot normally?
He got it into a boot-loop, you can try fixing it by running my One-Click PERI tool, and then choosing the 'fix-bootloop' option.
This is not normal for rooted transformers, but is a very common and relatively easy to fix problem.
Thing O Doom said:
He got it into a boot-loop, you can try fixing it by running my One-Click PERI tool, and then choosing the 'fix-bootloop' option.
This is not normal for rooted transformers, but is a very common and relatively easy to fix problem.
Click to expand...
Click to collapse
Downloaded, but ADB doesn't recognize my TF101 (adb devices returns nothing)
Tried installing the supplied .inf , but it isn't supported (Windows echoes "The selected INF-file does not support this installation method") and nothing is changed.
So I guess I need some drivers now..
EDIT: Okay, I got the drivers working thanks to Brk's rootkit.
Ran your tool, with "u" as first argument.
Finished without problems.
Still goes to recovery and not booting Android.
Tried applying the "r" option, still boots into CWM 5.5.0.4.
EDIT2: New touch recovery installed, new ROM flashed but still no instant boot.
Ok good, you got out of the bad CWM.
Now you need to reflash your bad bootloader, goto the asus tf101 site, pick download, android, firmware. Then find the firmware for your Region (it'll be WW I believe)
download blobunpack from either searching 'windows' in rayman's blobtools thread or downloading the blob.zip from my boot splash change guide, take the new firmware, unzip the file called 'blob' to a folder with blobunpack.exe in there, then open cmd and cd to the folder, then run 'blobunpack blob', the blob will now be split into many smaller blobs. What you'll want to do is take the one named blob.EBT, then put it on the root of your transformer's INTERNAL storage (So either adb push blob /sdcard/) or use windows to just place it there.
Then go into adb shell or terminal emulator app and type"
Code:
su (Grant root if it asks)
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
reboot
It will reboot, you'll see a blue bar for just a moment, then it reboots again, and *Hopefully* won't get stuck.
Thing O Doom said:
Ok good, you got out of the bad CWM.
Now you need to reflash your bad bootloader, goto the asus tf101 site, pick download, android, firmware. Then find the firmware for your Region (it'll be WW I believe)
download blobunpack from either searching 'windows' in rayman's blobtools thread or downloading the blob.zip from my boot splash change guide, take the new firmware, unzip the file called 'blob' to a folder with blobunpack.exe in there, then open cmd and cd to the folder, then run 'blobunpack blob', the blob will now be split into many smaller blobs. What you'll want to do is take the one named blob.EBT, then put it on the root of your transformer's INTERNAL storage (So either adb push blob /sdcard/) or use windows to just place it there.
Then go into adb shell or terminal emulator app and type"
Code:
su (Grant root if it asks)
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
reboot
It will reboot, you'll see a blue bar for just a moment, then it reboots again, and *Hopefully* won't get stuck.
Click to expand...
Click to collapse
This pad is bought in the US. So I guess I should go with the US file?
Edit: Went for the US file, extracted blob.EBT, tried your command in the Terminal Emulator (i had to add ".EBT" after if=/sdcard/blob to make it work) but it still didn't- It moved the file, and I typed in "reboot". It rebooted, but no blue bar and I went straight to recovery. Trying again, but I doubt it will be any different.
Edit2: Nope, same sh*t. Getting kinda annoyed now...
No you don't want .ebt
You want the file to jsut be 'blob'
You may want to run roach's fix directly after, run the above, then also type:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3
Then reboot.
Thing O Doom said:
No you don't want .ebt
You want the file to jsut be 'blob'
You may want to run roach's fix directly after, run the above, then also type:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3
Then reboot.
Click to expand...
Click to collapse
Oh thank you very much,this worked. The trick was to let the blob be extensionless.
However, I saw no blue bar, but it booted without going into recovery atleast
Glad it's finally working right
Go call the seller and complain >.<
Thing O Doom said:
Glad it's finally working right
Go call the seller and complain >.<
Click to expand...
Click to collapse
I thought it was solved, but no.
This comes back every time something in CWM is flashed - flashed a bootanimation, it came back, i ran your commands and it was solved. Flashed a new kernel now, it came back.
Ran the commands, it went away but I noticed my kernel wasn't changed and I can't overclock... I think I have a bad CWM accually.
You need to reflash a working CWM recovery then, I take it you're on that infernal ROM manager version. I'd flash Rouge XM 1.5 touch
Thing O Doom said:
You need to reflash a working CWM recovery then, I take it you're on that infernal ROM manager version. I'd flash Rouge XM 1.5 touch
Click to expand...
Click to collapse
Tried PERI but apperantly I cant give ADB SU rights, because wrote failed at /dev/block/mmcblk0p4 because of denied permissions.
Can I use dd to flash it like I did previousley?
Edit: I looked at the sauce of PERI and saw that it was flashing using a shell and DD so I entered it in a regular elevated ADB shell. Finally saw that blue bar I've been looking for and I have Team Rouge's (5.0.2.8) 1.5.0 recovery now. Thank you very much.
Actually, the same has happened to be, and i was trying to go back to stock ww, and i seem unable to find some kind of tutorial for that... I will try what was posted here at least to remove that initial loop.
MarkInDaPark said:
Tried PERI but apperantly I cant give ADB SU rights, because wrote failed at /dev/block/mmcblk0p4 because of denied permissions.
Can I use dd to flash it like I did previousley?
Edit: I looked at the sauce of PERI and saw that it was flashing using a shell and DD so I entered it in a regular elevated ADB shell. Finally saw that blue bar I've been looking for and I have Team Rouge's (5.0.2.8) 1.5.0 recovery now. Thank you very much.
Click to expand...
Click to collapse
Running PERI In CWM always gives root access x)
Try doing the fix bootloop function inside cwm.
Nice to see that you figured it out!
Thing O Doom said:
No you don't want .ebt
You want the file to jsut be 'blob'
You may want to run roach's fix directly after, run the above, then also type:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3
Then reboot.
Click to expand...
Click to collapse
That did the trick for me, my "boot direct to recovery" problem started when I accidentely selected Reboot to recovery under Advanced when I was "on that infernal ROM manager version" of recovery.
im having similar problems ..... Yep i updated CWM via ROM Manager to 5.8.3.4 (although since managed to downgrade it in theory to 5.8.2.1)
only way i can get into full Android is via a cold boot (but then i have no SD card or Wifi support) or by flashing a full new ROM each time I reboot !!!
problem i have is that im on my holidays and have no access to a PC
Google brought up a patched CWM version but even after flashing that in recovery it was still booting straight into CWM.
Well you r on holiday so can't do anything now... when you come back home try easy flasher to unroot and root again by that way you can get rid of that recovery....
Sent from my Transformer TF101 using xda app-developers app
Weird. I've been running CM7.1.1 on a Nexus S D720 for several months with no issues. This morning, I made some calls, a few texts and suddenly the phone said "No Service". Signal status was -1dbm. Called Sprint service they said they had no outages in this area. After removing battery, powering off, rebooting several times I figured she was toast. I booted into CWM recovery and restored a backup image from Jan 2012. Took about 5 mins. Rebooted phone and suddenly I had service. Also noticed my phone downloading ICS from Sprint updates.
So, what's up with that? Did sprint send out the update, noticed my phone didn't match stock, and disabled service?
They were probably mad that you were still on CM7. Kidding, sounds like a PRL problem.
xdart said:
Weird. I've been running CM7.1.1 on a Nexus S D720 for several months with no issues. This morning, I made some calls, a few texts and suddenly the phone said "No Service". Signal status was -1dbm. Called Sprint service they said they had no outages in this area. After removing battery, powering off, rebooting several times I figured she was toast. I booted into CWM recovery and restored a backup image from Jan 2012. Took about 5 mins. Rebooted phone and suddenly I had service. Also noticed my phone downloading ICS from Sprint updates.
So, what's up with that? Did sprint send out the update, noticed my phone didn't match stock, and disabled service?
Click to expand...
Click to collapse
If you ever have some funky issues like that you could always try a hands free activation.. Has helped me in the past on any issues.
qccoles said:
They were probably mad that you were still on CM7. Kidding, sounds like a PRL problem.
Click to expand...
Click to collapse
Haha.. could be. How do I re-root this thing with 4.0.4 on it? Found some stickies in the nexus s forum but they are from 2011... still looking.
xdart said:
Haha.. could be. How do I re-root this thing with 4.0.4 on it? Found some stickies in the nexus s forum but they are from 2011... still looking.
Click to expand...
Click to collapse
Do you mean how do you root while on stock ICS? http://www.youtube.com/watch?v=GSD92Qjt5Og works perfectly.
qccoles said:
Do you mean how do you root while on stock ICS?
Click to expand...
Click to collapse
Yep, that's what I mean. I'm on Linux though, so would need to dig out the appropriate files as well as commands from the run.bat file and apply them at the command line (I have adb and fastboot).
The dates on some of the files in One-Click-Nexus-S-4G-5.1.zip are from Nov. and Dec of 2011. Would it be wise to use these even though there are newer versions available?
eg:
* Superuser-3.1.3-arm-signed.zip from androidsu.com/superuser/
* download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.1.0-crespo4g.img
xdart said:
Yep, that's what I mean. I'm on Linux though, so would need to dig out the appropriate files as well as commands from the run.bat file and apply them at the command line (I have adb and fastboot).
The dates on some of the files in One-Click-Nexus-S-4G-5.1.zip are from Nov. and Dec of 2011. Would it be wise to use these even though there are newer versions available?
eg:
* Superuser-3.1.3-arm-signed.zip from androidsu.com/superuser/
* download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.1.0-crespo4g.img
Click to expand...
Click to collapse
I used the exact file not even a month ago. Although SU updates through market and I went with TWRP instead of CWM. Everythings perfect over here. I couldn't tell you a thing about linux, although I do plan on making the switch from Win7 very soon.
qccoles said:
I couldn't tell you a thing about linux, although I do plan on making the switch from Win7 very soon.
Click to expand...
Click to collapse
UPDATE#2: Ok, so it seems the red triangle+bugdroid has something to do with the recovery image being hosed. There is also a file named /system/recovery-from-boot.p which needs to be renamed PRIOR to flashing with CWM, or CWM will not "stick" and the red triangle+bugdroid will keep coming up.
In order to rename it, you have to remount /system as read-write. After renaming the file to /system/recovery-from-boot.p.bac I rebooted into recovery and re-flashed CWM with fastboot, only this time I flashed in CWM 6.0.1.0 instead of the recovery image from the One-Click-Nexus-S-4G file. After wiping cache, dalvik cache, data and factory reset (from CWM) I selected "reboot system now" and was presented with and option to "YES - Disable recovery flash". This option apparently fixes the hosed recovery issue somehow (maybe renaming /system/recovery-from-boot.p ?) so I selected YES and rebooted. rebooting into recovery seems to work OK now with no red triangle.
UPDATE #1: I tried rebooting into recovery a few hours later and just get a screen with a green droid+red triangle icon. Um any ideas where CWM went?
Thanks for the info. I just got my D720 rooted in Linux with the commands below. Maybe it will be of help when you switch.
I am kind of picky about verifying md5sums. I like to be able to make sure they downloaded correctly/haven't been altered. I wasn't able to google the md5sum (c4cecfc494610d6c0f13b2237bd212a0) for root.zip in the One-Click-Nexus-S-4G file. Hard to say why it's not out there, but I opted instead for Superuser-3.1.3-arm-signed.zip from androidsu.com.
files used:
recovery.img (from the One Click..) - md5sum - 5988836a66f535c4a7d499ee417ee9c5
Superuser-3.1.3-arm-signed.zip renamed to root.zip - md5sum - b3c89f46f014c9df7d23b94d37386b8a
unlock phone (!!! wipes it !!!)
need to enable settings > applications > developer options > select "USB debugging" or adb won't see it
# adb devices (should show your device. if not adb kill-server; adb start-server and try again)
# adb reboot-bootloader
# fastboot oem unlock
# fastboot reboot
** Phone took longer than normal to reboot after this.
After rebooting
# adb reboot-bootloader
# fastboot flash recovery recovery.img << from One-Click-Nexus-S-4G
- use volume-down, select recovery and press power
- go to the mounts and storage menu
- if it says "unmount /sdcard" then you do not need to follow this step)
- if it says "mount /sdcard", then select it.
- select "+++++ Go Back +++++"
push root.zip to phone and install it
# adb push root.zip /sdcard/
- Select "install zip" from sd card
- Select "choose zip" from sdcard
- Scroll all the way down and select root.zip
- choose yes
- select "+++++ Go Back +++++"
- select "Reboot System now"
After rebooting, I found the SuperUser icon was indeed in able to su to root
# adb -s 416321DE1F8100FD shell
[email protected]:/ $ su -
[email protected]:/ #
UPDATE - Red Triangle + Bugdroid Fix
Login to the device and su to root. All the commands starting with 'su -' up to 'exit' are done on the device and NOT the host OS.
# adb shell
$ su -
# cd /system
# mount -o remount,rw /system
# mv recovery-from-boot.p recovery-from-boot.p.bac
# mount -o remount,ro /system
# exit
Reboot the device into recovery mode using volume+power, or adb reboot recovery
(These commands are done from the host, just for clarification)
# fastboot flash recovery /tmp/recovery-clockwork-6.0.1.0-crespo4g.img
After that, select recovery from the menu and you should get CWM 6.0.1.0 where you can do a backup or whatever.
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.