Related
[HOWTO] ClockworkMod Recovery & TWRP - Upgrade/Downgrade (Touch/Non-Touch Recovery)
IF YOU TRASH YOUR PHONE USING THIS PROCEDURE, THEN IT IS A VERY GOOD INDICATION YOU ARE AN IDIOT AND SHOULD NOT BE FLASHING ANY ROMS NOR PARTICIPATING ON THESE FORUMS. . . . JUST SAYIN'. . . .
Please be VERY careful when using this method as you can brick your phone. Make sure you triple check the file you downloaded is the right size and placed in the right area, but most importantly that the command lines you type are exactly right. If you are not comfortable using this method, then please do not and go find a flashable version of these recoveries.
I've posted a procedure to format/'flash' your recovery while on your phone in one of the threads on here and was asked by a Forum Mod to make a quickie guide to be placed as a sticky on the dev boards so others might benefit.
Anyway, here is a very quick and easy way to change your ClockworkMod recovery with a couple of command lines.
The TWRP link is in the second post.
Now for the ClockworkMod Instructions:
1. First, go here and look up your ClockworkMod recovery that pertains to your phone: http://www.clockworkmod.com/rommanager
2. Download the .img file for your phone and save it on your computer.
3. Rename the .img file to recovery.img and save it to your internal sd card of your phone. For example: recovery-clockwork-6.0.1.4-hercules.img ------> recovery.img
4. Open up Terminal Emulator on your phone and type the following 2 commands:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
(please note the second command is a one line command with spaces between "dd & if=" and ".img & of=")
If your Rom identifies your internal sdcard as /emmc instead of /sdcard, then make the adjustment to command line (dd if=/emmc/recovery.img) instead of what is posted above.
That simple.
You can also issue these commands from adb shell if you are connected to your computer.
If Terminal Emulator does not have Superuser or SuperSU permissions for root privileges then make sure it does. You can also go from NON Touch CWM to Touch CWM using this and vice versa. Simply make sure you have the right recovery for your phone and rename it to recovery.img.
As for explanations:
dd if= command is a common Unix program whose primary purpose is the low-level copying and conversion of raw data.
dd stands for "data description"
if stands for "input file"
of stands for "output file"
the = is the location of the data you are using. ie. /sdcard/recovery.img
the /dev/block/mmcblk0p22 is the location/partition of the recovery on your phone.
So essentially you are doing a low level rewrite of the recovery image on your phone via command lines.
***Also, the best way to remember this command line is to not to. Copy the command line and save it to your own personal contact info in Google under Notes and then you will have it with you wherever you go. You really do not want to mess with getting it wrong. You could brick your phone if you mess things up.
Anyway, I hope this helps. . . . it really is very easy to execute without fault.
Works with TWRP too.
This also works with changing to and from TWRP. Download the image (for our phones it's TWRP 2.3.1.1) rename it to recovery.img and follow the above instructions and you are good to go.
Follow this link to get the image file: http://teamw.in/project/twrp2/101
***I attached the old TWRP 2.2.2.0 is case you run into problems with the newer versions not restoring backups properly or renaming backups correctly.***
Excellent Thread, I hope Dev's requiring specific CWM versions can link to your post.
Thanks for your efforts.
Noellenchris
XDA Forum MOD
Thanks for the instructions! Thanks even more for explaining the command lines.
Just thought I'd point out a small bug with the Touch Recovery. If you flash one of the newer ICS roms like Darkside Evolution through the Touch Recovery, once booted, the ROM WILL NOT SLEEP through time out. I've confirmed this with 2 separate ICS roms. Flashing non-touch recovery through Rom Manager fixes this problem.
Wouldn't it be easier to use gscript and run the commands as you need them?
Thanks for the HOW TO I actually was looking for it.
What is wrong with ROM Manager? I use it to go between Touch and normal all the time and it works flawlessly.
dextroamphetamine said:
What is wrong with ROM Manager? I use it to go between Touch and normal all the time and it works flawlessly.
Click to expand...
Click to collapse
For some people Rom Manager doesn't work. On the T-Mobile SGH-T989 Galaxy SII, Rom Manager will only allow you to go to 5.0.2.6 not 5.0.2.7. And, I think you have to upgrade Rom Manager to go to Touch. I bought Rom Manager, and don't use Touch Recovery, so I am not sure.
I like to use the command structure verses program because I know it works, it's fast, and I can see the results if an error occurs.
Oh yeah...this was really simple...Thanks...went from Touch back to Non Touch.
Give this a try
If you want a simple way to flash the Touch Recovery then give this a try. I will be adding the Hard Recovery as well in the next release.
SGSII T989 Root Toolkit
http://forum.xda-developers.com/showthread.php?t=1650908
http://forum.xda-developers.com/showthread.php?p=26200755
I get a write error: No space left on device. 1001+0 records in 1000+0 records out 512000 bytes transferred in 0.132 secs.
I reboot into recovery and it's still on 5.0.2.6
Edit: so i closed the terminal and I ran it again, and now my phone won't turn on. I get a USB device in windows called QHSUSB_DLOAD. I hold the power button, and the device disappears, but it won't turn on. I let go of the button, the same device reappears.
albanianbrotha said:
Edit: so i closed the terminal and I ran it again, and now my phone won't turn on. I get a USB device in windows called QHSUSB_DLOAD. I hold the power button, and the device disappears, but it won't turn on. I let go of the button, the same device reappears.
Click to expand...
Click to collapse
hate to be the dude that tells you this but i'm pretty sure qhsusb_dload is magic windows talk for "hard bricked phone." had that problem a while back. however all is not lost - these guys have a great reputation for Lazarus-ing dead phones.
hobakill said:
hate to be the dude that tells you this but i'm pretty sure qhsusb_dload is magic windows talk for "hard bricked phone." had that problem a while back. however all is not lost - these guys have a great reputation for Lazarus-ing dead phones.
Click to expand...
Click to collapse
Haha no worries bro. I mean worries that it failed for no reason, but I already sent it in, he just got it today. Same person you linked. Definitely trying to install ics again when i get it. Plus I think the ota ics for tmo came out yesterday or something? Probably a better experience than what was already out there with the radio and stuff.
the files from the CWM site are not .img for me, they are .ndif is it the same procedure?
MustangFTW said:
the files from the CWM site are not .img for me, they are .ndif is it the same procedure?
Click to expand...
Click to collapse
No! Do NOT use this procedure with that file extension!
What recovery are you trying to install? And for what phone? I briefly ran my cursor over the various files and the download links are either .img or .zip files. I did not see .ndif file extension.
PM me if you need additional help.
Would you happen to have the .img file for 5.0.2.7??
Edit* Nvm.. a quick google search and I was able to find it. You are a life saver.. I tried updating my recovery to the 6.0.1.2 Hercules port and for a couple days, it was working great up until an hr. ago. Nothing would flash and it would just hang in recovery... so I found this thread and thankfully I was able to downgrade back down to 5.0.2.7.
If you were local, I would take you out and get you piss drunk for helping me save my device. Cheers!!!!
fresherthanU said:
Would you happen to have the .img file for 5.0.2.7??
Edit* Nvm.. a quick google search and I was able to find it. You are a life saver.. I tried updating my recovery to the 6.0.1.2 Hercules port and for a couple days, it was working great up until an hr. ago. Nothing would flash and it would just hang in recovery... so I found this thread and thankfully I was able to downgrade back down to 5.0.2.7.
If you were local, I would take you out and get you piss drunk for helping me save my device. Cheers!!!!
Click to expand...
Click to collapse
You're welcome, I'm glad I could help you. But, the link to the .img files is in the OP instructions. . . .
Unfortunately this method did not work for me... I have tried many ways to update my CWM and none of them worked, it is almost hopeless for me
Good news! You made front page! http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)
First, I'd like to thank Chlinkchlink, Heritz, and Superoneclick application for your help and original Root.zip File! Wouldn't work without this!
I Finally found the perfect method to root this Virgin Mobile Device with S-On (Or OFF)! I Spent 3 days on my customers phone at my computer shop figuring a good method without read/write or freeze errors. I Simply EXTRACTED the SUPERUSER and ROOT files from SUPERONECLICK application and PASTED those files into the ROOT.ZIP File provided. Result? The ULTIMATE ROOT.ZIP MODIFICATION! Below are the methods....
Forget to mention... "I AM NOT RESPONSIBLE IF YOU BRICK/BREAK/THROUGH YOUR PHONE OUT THE WINDOW/ Etc!" That can only happen if you fail to backup your device or fail to read my steps and HTC Dev. Thanks and HAPPY ROOTING!
Follow The HTC Dev method to unlock your bootloader. Sorry. Due to rules I am too new to submit links.
Then install clockworkmod recovery like you would through adb on your computer. Download from attachment. make sure you Extract it!
Place the clockworkrecovery image inside your Android Adb folder. Place your phone in bootloader usb mode and plug it into the computer. Open command prompt and browse to the folder where you placed the recovery
example how:
cd c:/
cd Android
Now Flash this bad recovery!
example on cmd prompt:
fastboot flash recovery recovery-clockwork-5.0.2.8-marvelc.img
Now you have clockworkmod recovery!
Now hit Recovery on your cell...
Get My Modified Root.Zip File on link attached.
Now mount USB Storage and make sure your phone is still plugged in to computer.
Copy my modified Root.zip file you downloaded into the root of your MicroSD Card.
Unmount USB and flash the Root.zip file.
Reboot phone and you are now rooted! Donate / Like Me/ And good comments if I helped you!!!
Thanks for your help with my phone. I'm glad you were able to figure it out after i gave up trying. In a few wks i'll get the VM Evo 3d 4g and swing by to have you do that phone as well. I'll let you know if i run into any issues or updates. Thanks once again!
Can anyone else verify this works?
Finally found something for wf s CDMA. Only 1 other person out there that has tried this? Anyone else?
This would of helped me a while ago.
I had an issue where CWM 5.0.2.8 would freeze and restart itself. I had to use 4.X.X.X (don't remember the exact numbers) in order to be able to flash roms.
And maybe you can help me with this. I installed HenseMod with the VirginMobile patch, but I have no service. My carrier doesn't seem to know why either.
Does anyone know what the problem is?
Here you go
F9zSlavik said:
This would of helped me a while ago.
I had an issue where CWM 5.0.2.8 would freeze and restart itself. I had to use 4.X.X.X (don't remember the exact numbers) in order to be able to flash roms.
And maybe you can help me with this. I installed HenseMod with the VirginMobile patch, but I have no service. My carrier doesn't seem to know why either.
Does anyone know what the problem is?
Click to expand...
Click to collapse
Yes.. I am sure you need to go back to stock rooted rom. Then activate (or reactivate) with your carrier, then put the Hensemod back.
(Most HTC phones with SENSE won't activate with the carrier with any cyanogen based rom). It must have SENSE.
Nice tut, thanks
Sent from my new LG Optimus Elite
F9zSlavik said:
This would of helped me a while ago.
I had an issue where CWM 5.0.2.8 would freeze and restart itself. I had to use 4.X.X.X (don't remember the exact numbers) in order to be able to flash roms.
And maybe you can help me with this. I installed HenseMod with the VirginMobile patch, but I have no service. My carrier doesn't seem to know why either.
Does anyone know what the problem is?
Click to expand...
Click to collapse
what provider do you have? and if its vm try another ROM that was made by someone with a marvelc (the guy who made your ROM doesn't have the phone)
Sent from my HTC_A510c using Tapatalk
I never had a problem with any of the cwm on the marvelc, maybe it was a bad install? I just use the old version then use ROM manager to flash the new version
Sent from my new LG Optimus Elite
sweet, thanks
Very helpful and a good consolidated version. I had more trouble unlocking the bootloader than following your HowTo!!!
Thanx Again!
Unroot??
rgsgroup2005 said:
First, I'd like to thank Chlinkchlink, Heritz, and Superoneclick application for your help and original Root.zip File! Wouldn't work without this!
I Finally found the perfect method to root this Virgin Mobile Device with S-On (Or OFF)! I Spent 3 days on my customers phone at my computer shop figuring a good method without read/write or freeze errors. I Simply EXTRACTED the SUPERUSER and ROOT files from SUPERONECLICK application and PASTED those files into the ROOT.ZIP File provided. Result? The ULTIMATE ROOT.ZIP MODIFICATION! Below are the methods....
Forget to mention... "I AM NOT RESPONSIBLE IF YOU BRICK/BREAK/THROUGH YOUR PHONE OUT THE WINDOW/ Etc!" That can only happen if you fail to backup your device or fail to read my steps and HTC Dev. Thanks and HAPPY ROOTING!
Follow The HTC Dev method to unlock your bootloader. Sorry. Due to rules I am too new to submit links.
Then install clockworkmod recovery like you would through adb on your computer. Download from attachment. make sure you Extract it!
Place the clockworkrecovery image inside your Android Adb folder. Place your phone in bootloader usb mode and plug it into the computer. Open command prompt and browse to the folder where you placed the recovery
example how:
cd c:/
cd Android
Now Flash this bad recovery!
example on cmd prompt:
fastboot flash recovery recovery-clockwork-5.0.2.8-marvelc.img
Now you have clockworkmod recovery!
Now hit Recovery on your cell...
Get My Modified Root.Zip File on link attached.
Now mount USB Storage and make sure your phone is still plugged in to computer.
Copy my modified Root.zip file you downloaded into the root of your MicroSD Card.
Unmount USB and flash the Root.zip file.
Reboot phone and you are now rooted! Donate / Like Me/ And good comments if I helped you!!!
Click to expand...
Click to collapse
Hey do you know how to unroot the vmwfs? i used this to root
r=watch?v=rIKsoZf2BCA&list=PL44107726C058E557&index=1&feature=plpp_video[/url]
but i wanna unroot any ideas??
Finally a method easy and straightforward! well done!
I'm stuck at the end, this is a bit vague:
rgsgroup2005 said:
Unmount USB and flash the Root.zip file.
Click to expand...
Click to collapse
searching the forum I found this http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android is that what you mean?
Can't find any option to flash the on the boot menu... .zip file
Has anyone tried this with a recently purchased VM Wildfire S? Say July 2012 or after?
do we need to s-off
do we need to s-off the phone befor going ahead with the steps mentioned.I mean can we root the phone even without s-off
This is an all new way to root and install bootmenu (2nd init) with only one click!
Just running runme.bat you will have a Bravo ready to use new roms in less than a minute.
Instructions:
1. Download: http://www.mediafire.com/?yfgvds9a1w8sbds
2. Extract files whenever you want.
3. Enable USB debugging (menu > Settings > Applications > Development) and connect your phone to the PC.
4. Run runme.bat, in folder Root+Boot-AIO.
5. Press Enter when script ask you to do it and READY!
Note: remenber to install motorola drivers first.
Reserved for instructions in spanish and other language!
Thanks. Finally find another one click option.
Sent from my HTC Sensation using Tapatalk 2
Tested, worked like a charm!
Thank you! :good:
Wow
Just one word, wow, works like a charm. Now we can install a custom rom with like 4 steps now. Your 1 click would be step one for sure!
Good job and lots of props man!
Junkyardjames87 said:
Just one word, wow, works like a charm. Now we can install a custom rom with like 4 steps now. Your 1 click would be step one for sure!
Good job and lots of props man!
Click to expand...
Click to collapse
I've looked into it. While there are a few options to install roms from the pc, some of the commands are known to hang on completion, which means you can't really script them safely (you could add in some kill and restart commands, but you'd have to put like 2-5 min buffers on them to make sure it was done).
I've found that the quickest way to install roms is to use TWRP in the Defy Forums. It allows you to select multiple zips at a time to flash at once. I haven't used clockwork touch recovery yet.
I'll look into it a little more, cause typing something like "./rom_install.sh /path/to/rom.zip -gbgapps" to install a rom and gb gapps would be easy. If I can find a way to execute edify scripts (the ones used to install roms) from adb then this can be done. I can only make and test linux scripts since I no longer have windows, but Josuearisty can port it to windows shell script. I formatted my old windows drive to use my android compile drive .
skeevy420 said:
I've looked into it. While there are a few options to install roms from the pc, some of the commands are known to hang on completion, which means you can't really script them safely (you could add in some kill and restart commands, but you'd have to put like 2-5 min buffers on them to make sure it was done).
I've found that the quickest way to install roms is to use TWRP in the Defy Forums. It allows you to select multiple zips at a time to flash at once. I haven't used clockwork touch recovery yet.
I'll look into it a little more, cause typing something like "./rom_install.sh /path/to/rom.zip -gbgapps" to install a rom and gb gapps would be easy. If I can find a way to execute edify scripts (the ones used to install roms) from adb then this can be done. I can only make and test linux scripts since I no longer have windows, but Josuearisty can port it to windows shell script. I formatted my old windows drive to use my android compile drive .
Click to expand...
Click to collapse
Im not using TWRP either Touch Clockworkmod, both of them are not working as they should sometimes.
I supose that a fully working Touch Clockworkmod would restore an old backup made with our actual Clockworkmod recovery, but does not.
In the case of TWRP, works fine for some time but later it seems to get tired and when you make a backup, it says its complete inmediatly but it is still creating backup files.
It would be great to install roms with just hitting Enter coming from froyo. Do you think that just making some changes to the script, is it possible to install a rom the pc?
josuearisty said:
It would be great to install roms with just hitting Enter coming from froyo. Do you think that just making some changes to the script, is it possible to install a rom the pc?
Click to expand...
Click to collapse
I'm sure its possible somehow, I've just never looked too deep into doing it. What ways I have found either used commands that would hang and require you to quit after 2 mins of activity and start the 2nd command which hangs the same thing -- not safe enough to script. The other ways were for broke\no sdcard and involved copying the rom to /data and then installing as normal.
What I think needs to be done is set up a script that copies the rom & gapps to the sdcard and executes their edify scripts. We need to figure out what command recovery uses to execute the script\install roms then incorporate it into an install script. You'd still have to reboot to bootmenu and enable adb, but that's all (unless we find a way to reboot and have adb already enabled (not good for all the time use, security concerns - it'd be possible to get around the bootmenu pin if adb was enabled on power up).
skeevy420 said:
I'm sure its possible somehow, I've just never looked too deep into doing it. What ways I have found either used commands that would hang and require you to quit after 2 mins of activity and start the 2nd command which hangs the same thing -- not safe enough to script. The other ways were for broke\no sdcard and involved copying the rom to /data and then installing as normal.
What I think needs to be done is set up a script that copies the rom & gapps to the sdcard and executes their edify scripts. We need to figure out what command recovery uses to execute the script\install roms then incorporate it into an install script. You'd still have to reboot to bootmenu and enable adb, but that's all (unless we find a way to reboot and have adb already enabled (not good for all the time use, security concerns - it'd be possible to get around the bootmenu pin if adb was enabled on power up).
Click to expand...
Click to collapse
Well, look at the rom manager, watch how it does it. I think that looking into adb commands we can make a script works like rom manager.
When you select the rom, rom manager lets you wipe data & cache and also install gapps. The rom manager goes to recovery and inmediatly do all steps it self, you can also backup your actual rom.
Try it, download it from market and try it, I see your roms there too.
Some windows commands are:
Adb reboot recovery = reboot into recovery mode
Adb push FILE = copy files to whatever place into out phones. Example to copy a rom.zip to sdcard
Adb push rom.zip /sdcard/rom.zip
Those are windows commands, dont know if they could work on linux. If my pc wasnt broke I would be making some tests!
Does this install a custom recovery? And if not how do I install one? Will a goo manager from the play store install one?
Sent from my Nexus 4
obsanity said:
Does this install a custom recovery? And if not how do I install one? Will a goo manager from the play store install one?
Sent from my Nexus 4
Click to expand...
Click to collapse
This will root and install a custom recovery.
Excellent tool, recommended! :good:
josuearisty said:
This will root and install a custom recovery.
Excellent tool, recommended! :good:
Click to expand...
Click to collapse
Great. Thank you. I'm rooting a friend's phone. He just wants something more reliable than stock. Would you say the CM7 is stable and reliable or should I put CM10 on it?
obsanity said:
Does this install a custom recovery? And if not how do I install one? Will a goo manager from the play store install one?
Sent from my Nexus 4
Click to expand...
Click to collapse
CM7 is more stable now, I have installed an official cm7 and then a patch for it.
Give me some minutes to upload it!
josuearisty said:
CM7 is more stable now, I have installed an official cm7 and then a patch for it.
Give me some minutes to upload it!
Click to expand...
Click to collapse
Which one should I use? Also, what is the SBF for Motorola Bravo? Sorry about the questions in this thread, I'm not familiar with this phone.
obsanity said:
Which one should I use? Also, what is the SBF for Motorola Bravo? Sorry about the questions in this thread, I'm not familiar with this phone.
Click to expand...
Click to collapse
Use cm7. Very fast and stable with no random hiccups, rare force-closes. The SBF is the Motorola Bravo "factory ROM". To install it, you can use RSDlite or do it in linux, both of those tuts are found in the bravo general section. You probably won't have to use the SBF unless you brick your phone, which is a possibility, but flashing the sbf will unbrick it 99% of the time.
Current ROM: CM7.2 Euroskank Cherry Picks | Bravo port
I think I have a problem. The sim I put in to this phone is asking to log in with moto blur and nothing I try is working. So I can't switch the debug mode on. I even tried the bypass suggested by someone but fastboot is not preinstalled on this phone. All I get is the bootloader or stock recovery.
I also tied resetting the password but after I go thru it it just says there is no phone on this moto blur account.
Any help would be appreciated.
Edit:
I got it. I factory reset the phone and then was able to use the bypass motoblur ****.
Sent from my Nexus 4
Ruined my device,now it won't even boot.
How do I fix it? factory reset doesn't help
shvelo said:
Ruined my device,now it won't even boot.
How do I fix it? factory reset doesn't help
Click to expand...
Click to collapse
Post a little more info.
What did you do?
Can you access custom, stock, or bootloader recovery?
Does it still charge?
And did you factory reset from Custom recovery or Stock recovery? Custom only wipes all data where Stock actually formats the partitions.
The easy way and a common issue we're having now.
Unless this is one of those CM10 ext4 issues, just flash the sbf and you should be good to go.
If you downgraded from CM10 and you were using ext4 /data and /cache, reinstall CM10, format back to ext3, then flash whatever you want.
skeevy420 said:
Post a little more info.
What did you do?
Can you access custom, stock, or bootloader recovery?
Does it still charge?
And did you factory reset from Custom recovery or Stock recovery? Custom only wipes all data where Stock actually formats the partitions.
The easy way and a common issue we're having now.
Unless this is one of those CM10 ext4 issues, just flash the sbf and you should be good to go.
If you downgraded from CM10 and you were using ext4 /data and /cache, reinstall CM10, format back to ext3, then flash whatever you want.
Click to expand...
Click to collapse
What is that issue with cm10 ext4? Is that very dangerous for us?
I have been sometime out of the forum and I have lost some things!
josuearisty said:
What is that issue with cm10 ext4? Is that very dangerous for us?
I have been sometime out of the forum and I have lost some things!
Click to expand...
Click to collapse
The CM10 ext4 issue is when you flash a CM10 custom kernel rom and select format /data & /cache to ext4 in the bootmenu. Only custom kernels can use the ext4 file system, so what happens is you format them as ext4, install CM9, and it doesn't load because it can't mount /data and /cache to write them because they're on an unsupported file system. The only things you can do are reinstalling CM10 and formatting back to ext4 of flash the sbf in extreme cases. Its not dangerous at all, just very annoying if you forget to format back to ext3 .
Hello,
I've just bought my new Samsung Galaxy Gio, and on it I had Android 2.3 version.
I performed a Root on my phone, and after that, I updated the Android version with Kies and now I have Android version 2.3.6, Baseband version S5660XXKT6, , Kernel version 2.6.35.7-perf-CL1047966 [email protected]#1 Build number GINGERBREAD.XXKTK
I've downloaded Clorkwork mode recovery and I to installed it, but after that I did a recheck to see if my phone is still rooted and with the help of Root Checker Basic app it says that the device does not have proper root access.
I've tried to root it againg but in recovery, and it's showing these messages : E:Can't mount /cache/recovery/command' and 'E:Can't open /cache/recovery/last_log',
I don't know what to do know, all that I want is to have a proper root on my phone and CMM recovery nicely installed.
Did I do wrong my rooting my phone before updating it to 2.3.6?
How can I make it ok?
arina_arina said:
Hello,
I've just bought my new Samsung Galaxy Gio, and on it I had Android 2.3 version.
I performed a Root on my phone, and after that, I updated the Android version with Kies and now I have Android version 2.3.6, Baseband version S5660XXKT6, , Kernel version 2.6.35.7-perf-CL1047966 [email protected]#1 Build number GINGERBREAD.XXKTK
I've downloaded Clorkwork mode recovery and I to installed it, but after that I did a recheck to see if my phone is still rooted and with the help of Root Checker Basic app it says that the device does not have proper root access.
I've tried to root it againg but in recovery, and it's showing these messages : E:Can't mount /cache/recovery/command' and 'E:Can't open /cache/recovery/last_log',
I don't know what to do know, all that I want is to have a proper root on my phone and CMM recovery nicely installed.
Did I do wrong my rooting my phone before updating it to 2.3.6?
How can I make it ok?
Click to expand...
Click to collapse
i think you are wrong with the step that you performed..
after you upgrade your firmware,root access was lost,so you have to root it again before install the CWM cz root file can only flashed via stock recovery..
to fix it just install stock recovery again (search for that in development forum),root the device and install the CWM again..
CMIIW
Sent from my GT-S5660 using Tapatalk 2
Step is :
1. Upgrade to latest
2. Install Root From stock recovery
3. Install CWM
4. Upgrade to custom...
Many thanks for the answers, but how do I install stock recovery? I didn't find details or I don't get them. Please explain,
arina_arina said:
Many thanks for the answers, but how do I install stock recovery? I didn't find details or I don't get them. Please explain,
Click to expand...
Click to collapse
Have a look here: http://forum.xda-developers.com/showpost.php?p=20896513&postcount=2
You can download the stock recovery and flash it via Odin.
No need for the stock recovery.
However, the stock Samsung ROM uses RFS and most CWM builds out there are meant for ext4 partitions.
Get a proper CWM, along with ChainsDD's super user zip and you'll be good to go.
Darkshado said:
No need for the stock recovery.
However, the stock Samsung ROM uses RFS and most CWM builds out there are meant for ext4 partitions.
Get a proper CWM, along with ChainsDD's super user zip and you'll be good to go.
Click to expand...
Click to collapse
So, I don't need to stock recovery?
Where can I fiind a good root zip for my phone???? After that, what CWM should I use? Please answer because my phone is working really slow and I can't root it for good! :crying:
arina_arina said:
So, I don't need to stock recovery?
Where can I fiind a good root zip for my phone???? After that, what CWM should I use? Please answer because my phone is working really slow and I can't root it for good! :crying:
Click to expand...
Click to collapse
And your PM while I'm at it.
Hello,
I've already posted a new thread and I didn't get the right answer...
I just want to root my phone again and I can't find the propper zip for android 2.3.6, and also I don't know what RFS means,
I know how to install a stock ROM, but before that I need to have my phone rooted and CWM installed .
Sorry for the many questions,
Good day!
Click to expand...
Click to collapse
Keep the conversation in the thread. We're lacking a bit of information...
How did you root the first time, prior to the official Kies update?
Remember, in most situations, official updates will remove root, simply because they completely overwrite the /system partition where your su binary and Superuser.apk reside. You need to put those back, either with CWM or by using an exploit of some kind, SuperOneClick being a very handy tool in this scenario. (It uses the different included exploits to gain a temporary root shell, remount the /system partition in read-write, pushes the binary and the apk, then sets the proper ownership and permissions to them. In contrast, CWM is already rooted without any exploits, but can only be installed from a live and rooted device, or Download Mode, or for some other devices with fastboot and an unlocked bootloader.)
RFS: Robust FAT File System. A Samsung proprietary file system format used in many mid-range, older devices such as the Gio. Deprecated in newer models, which favor ext4. Similar to good old FAT32, but adds *nix style file permissions support amongst other features. For this reason RFS images may be read but not safely modified on most *nix systems and with some Windows based programs. Modified ROMs enable ext4 support on the Gio as well. Switching back and forth between ext4 and RFS is possible, but that is beyond the scope of this post.
This file system also adds a little gotcha to CWM not found in ext4-based devices. Some CWM builds are meant for use with RFS, others with ext4. I'd avoid those claiming support for both if only because they're not very clear in which format they're working for a given operation.
I'm going with the idea that you want an essentially unmodified, Samsung stock ROM with CWM and root, and that you've only flashed over recovery since updating, or that you've reflashed the whole phone to stock with Odin:
Get the real deal ChainsDD "official" superuser zip file for ARM devices from androidsu.com and put it on your MicroSD card.
Find an RFS-compatible CWM image (iirc Phiexz and Hyriand both have built such recoveries) and flash it with Odin.
Reboot in recovery, and mount the /system partition manually prior to installing the superuser zip. I'm pretty sure the mount command in the updater-script will not work since it assumes an ext4 file system.
While you're at it double check that the files are there with adb shell and have the proper permissions. If the superuser zip installation has failed for some reason you could always manually push the two files, and chown/chmod them like the script does.
Reboot the phone, check for root.
You should be done!
Remember, root isn't a magical make-phone-go-fast panacea. The Gio isn't very fast to begin with, and there's only so much you can do...
Darkshado said:
And your PM while I'm at it.
Keep the conversation in the thread. We're lacking a bit of information...
How did you root the first time, prior to the official Kies update?
Remember, in most situations, official updates will remove root, simply because they completely overwrite the /system partition where your su binary and Superuser.apk reside. You need to put those back, either with CWM or by using an exploit of some kind, SuperOneClick being a very handy tool in this scenario. (It uses the different included exploits to gain a temporary root shell, remount the /system partition in read-write, pushes the binary and the apk, then sets the proper ownership and permissions to them. In contrast, CWM is already rooted without any exploits, but can only be installed from a live and rooted device, or Download Mode, or for some other devices with fastboot and an unlocked bootloader.)
RFS: Robust FAT File System. A Samsung proprietary file system format used in many mid-range, older devices such as the Gio. Deprecated in newer models, which favor ext4. Similar to good old FAT32, but adds *nix style file permissions support amongst other features. For this reason RFS images may be read but not safely modified on most *nix systems and with some Windows based programs. Modified ROMs enable ext4 support on the Gio as well. Switching back and forth between ext4 and RFS is possible, but that is beyond the scope of this post.
This file system also adds a little gotcha to CWM not found in ext4-based devices. Some CWM builds are meant for use with RFS, others with ext4. I'd avoid those claiming support for both if only because they're not very clear in which format they're working for a given operation.
I'm going with the idea that you want an essentially unmodified, Samsung stock ROM with CWM and root, and that you've only flashed over recovery since updating, or that you've reflashed the whole phone to stock with Odin:
Get the real deal ChainsDD "official" superuser zip file for ARM devices from androidsu.com and put it on your MicroSD card.
Find an RFS-compatible CWM image (iirc Phiexz and Hyriand both have built such recoveries) and flash it with Odin.
Reboot in recovery, and mount the /system partition manually prior to installing the superuser zip. I'm pretty sure the mount command in the updater-script will not work since it assumes an ext4 file system.
While you're at it double check that the files are there with adb shell and have the proper permissions. If the superuser zip installation has failed for some reason you could always manually push the two files, and chown/chmod them like the script does.
Reboot the phone, check for root.
You should be done!
Remember, root isn't a magical make-phone-go-fast panacea. The Gio isn't very fast to begin with, and there's only so much you can do...
Click to expand...
Click to collapse
Thanks for the answers:
After I bought the phone, I've rooted it with an update.zip which I found on google. It worked and my phone was rooted. After that, I updated through KIES to 2.3.6 and then I noticed that my phone wasn;t rooted anymore. I should've read firs the instructions I found on xda forum, but I was too eager on updating and playing with this phone.
From your explanations I understand that I should do the following:
- install superoneclick
- find a good superuser app
- install cwm.
Am I right? I originally thought that I should install a root zip file again and then cwm....
Nope, reread the second to last paragraph, it's: CWM, then su.zip. No need for SuperOneClick this way.
Or, just use SuperOneClick and leave the stock recovery as is.
Sent from my Nexus S using xda app-developers app
Darkshado said:
Nope, reread the second to last paragraph, it's: CWM, then su.zip. No need for SuperOneClick this way.
Or, just use SuperOneClick and leave the stock recovery as is.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
I searched for a propper CWM and I couldn't find it...where can I find CWM for android 2.3.6?
The Android version you're using is unrelated to the CWM version. So the same 5 or 6.something will work with GB, ICS and JB.
Well, I've downloaded Odin and the S5660M_CWM-5.0.2.7_ext4+rfs_feb_23_12.tar.md5 file which I found on this thread : http://forum.xda-developers.com/showpost.php?p=20896513&postcount=2
I switched to downloading mode, connected the phone with the pc and started the cwm installation through Odin, but after 50 minutes nothing happens and it's stuck on this :
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> recovery.img download..
What did I do wrong?
Did I downloaded the wrong CWM file for my android 2.3.6 version?
Did I downloaded the wrong ops file?
If so, where are the corret CWM and ops files?
Please answer!!!
HTC One Mini - AT&T
Tried installing Busybox from GooglePlay .apk, FAILED.
Now what?
I'm guessing I have root, not sure how to be completely sure.
Unlocked fastboot, flashed recovery w/ orange, installed SU from .zip
Gave BB SU permission.
FAILED.
Now what? I need BB. Tried looking for flashable .zip to flash from orange, but can't find any DL's.
S = ON :/
I have no idea where to begin fixing this issue...
On a side note...
Still can't find flashable .zip BB version.
Tried using Jrummy BB installer w/ root, still crashes.
Someone help before I manually brick this POS... i.e. throw it at a brick wall....
I just did a search on Google it said you need an app called busy box installer from the playstore
Sent from my GT-P3113 using xda app-developers app
.APK Method/Apps DO NOT WORK.
djerk said:
I just did a search on Google it said you need an app called busy box installer from the playstore
Click to expand...
Click to collapse
They do not work. Both of these:
google*com/store/apps/details?id=stericson.busybox[/url]
google*com/store/apps/details?id=com.jrummy.busybox.installer[/url]
(Official GooglePlay Online Store)
...either crash/reboot during "Advanced/smart" install, or fail using "Normal" install.
I need to to turn "S" off to enable write to nand possibly?
Tried both /xbin/ and /bin/ install directory through .apk
Also tried both Advanced & Normal install on both apps...
OP Specifically says .apk method = FAIL....
Next answer please, lol
Also....
I also verified root, it's there. Both .apk's (Apps) had SU privelage.
Even restarted the apps to make sure they had SU right from the beginning of their loading.
So to summarize:
AT&T HTC One mini
- fastboot : UNLOCKED
- recovery flashed : recovery-clockwork-touch-6.0.3.6-m4.img
- gained root : ClockWorkMod loaded "root.zip" (.zip courtesy root-wiki)
- DL'ed BusyBox .apk's : TWO FAILURES.
- And here I am....
Android version : 4.2.2
HTC Sense Ver : 5.0
Software number : 1.24.502.3
HTC SDK API level : 5.41
Kernel version:
- 3.4.10-10-gae2031e
[email protected] #1
SMP PREEMPT
Baseband version : 1.19.40d.00.14_10.20.40.4408L
Build number : 1.24.502.3 CL224405 release-keys
Browser version : Webkit/534.30
Moderator please move post
Move post to "AT&T HTC One Q&A"
Plz & TY:angel:
I just installed busy box with no issues on my Verizon htc one running 4.3 maybe you have the wrong version for 4.22
Sent from my GT-P3113 using xda app-developers app
Which ver?
djerk said:
I just installed busy box with no issues on my Verizon htc one running 4.3 maybe you have the wrong version for 4.22
Click to expand...
Click to collapse
Which version of Busy did you use?
1.20.2
1.20.1
1.20
1.19
or earlier?
screens
Here's my screens
I installed version 1.22.1
Sent from my GT-P3113 using xda app-developers app
This needs to be in proper section. This is the HTC One Verizon section. Not mini.
http://forum.xda-developers.com/htc-one-mini
Typed on a HTCone via rumrunners
I know this is the wrong forum, but im gonna help a guy out anyways.
Does the mini have ext4 formating for system and cache partitions? If so flash this https://www.dropbox.com/s/losui4x6nkt47nx/busybox_recovery_flashable.zip
cmlusco said:
I know this is the wrong forum, but im gonna help a guy out anyways.
Does the mini have ext4 formating for system and cache partitions? If so flash this https://www.dropbox.com/s/losui4x6nkt47nx/busybox_recovery_flashable.zip
Click to expand...
Click to collapse
DL'ed your .zip, but i'm waiting to figure out if my Mini has this "ext4" formating.
I don't know how to check if it does, and I don't want to flash something w/o knowing more.
I know ext4 is the newest? linux file structure, but I'm not sure if my Mini is formatted to it....
Anybody know how to check this?
The Mini when hooked up to a PC is recognizable as an external storage device,
so doesn't that mean its FAT or NTFS if windows can recognize it? Right?
Windows won't automatically recognize ext4 w/o installing something right?
If you have to alter or change your phone to ext4, then mine is not. I have never formatted my phone.
How can I check if this is safe for my phone?
I plan on using ClockworkMod to install this through the GUI.
What exactly is this "recovery-flashable-busybox"?
Does it get flashed over top of my recovery partition?
If so, does that mean I will lose my clockworkmod recovery?
Somehow with no idea what I was doing, I managed to unlock fastboot, and get SU.
Now I'm thinking I have no real idea of how this all works......
I would feel more comfortable installing BusyBox using an .APK because I'm a n00b
at this with an expensive toy that i don't want to break.... Like I mentioned before, would
turning S "off", would that allow me to use an .APK to install BusyBox? Or did my two .APK
installations I attempted before fail bc my internal "emulated" SD card is not formatted to
"ext3/4"? I'm lost now...
I guess in summary I need to know WHY I can't install busybox via GooglePlay .APK's,
and is this .zip safe for me to use, and if it is, how would I even use it?
It seems like the more answers I get, the more complications and questions I have...
How would I message or get help from somebody "high up" on this forum, somebody that knows all the in and outs?
I'm not gunna lie, I need a "babysitter" for this....
All I want to do is install Busybox, and after that I'm good, I don't need to play around with the "sensitive internals" of my phone.
I don't want any special roms, or anything else special. I just want SU privelages, and busybox installed.
Soooo.... how do I find a babysitter lol....
cmlusco said:
I know this is the wrong forum, but im gonna help a guy out anyways.
Does the mini have ext4 formating for system and cache partitions? If so flash this https://www.dropbox.com/s/losui4x6nkt47nx/busybox_recovery_flashable.zip
Click to expand...
Click to collapse
Also, I forgot to ask, did you mean can my phone "READ" ext3/4, or did you mean is my device "FORMATTED" to ext3/4
Neither of which do I know how to check or verify, but it would at least tell me what to do next i guess....
I think I'm may be on to something... The Util's known as "BusyBox", are a bunch of basic/necessary/commonly.used Linux commands wrapped up in a package, correct? So if they are Linux commands, then they probably have to be written to a Linux formatted partition? Correct? And if they are Linux commands, on a Linux partition, then that means my phone must be able to "speak" Linux? Correct?
So essentially I need to create an ext3/4 partition, and then write/install BusyBox to that partition?
Is my assumption correct?
Now another assumption is that the .APK's I want to use, which require these Linux commands, act as an interpreter to translate these Linux commands for my phone? Essentially, my phone does not need to speak Linux bc the .APK's know how to use the Linux commands "automatically" or "within themselves" so to speak?
lgally80 said:
I think I'm may be on to something... The Util's known as "BusyBox", are a bunch of basic/necessary/commonly.used Linux commands wrapped up in a package, correct? So if they are Linux commands, then they probably have to be written to a Linux formatted partition? Correct? And if they are Linux commands, on a Linux partition, then that means my phone must be able to "speak" Linux? Correct?
So essentially I need to create an ext3/4 partition, and then write/install BusyBox to that partition?
Is my assumption correct?
Now another assumption is that the .APK's I want to use, which require these Linux commands, act as an interpreter to translate these Linux commands for my phone? Essentially, my phone does not need to speak Linux bc the .APK's know how to use the Linux commands "automatically" or "within themselves" so to speak?
Click to expand...
Click to collapse
All you need to do is flash it thru recovery. If your phones partitions are not formated ext4, the install will fail before anything is ever changed.
To find out how there fornated type mount into a terminal emulator, or at an adb shell. Look for lines with /system and /cache. In those same lines it will say ext4, ext3, etc. If there not ext4 tell me, and i will edit the flashable with the correct partitions.
All this zip does is install the busybox binary file to /system/xbin, and then make the appropirate symlinks.
Yes i reccomend getting s-off. The reason the apk wont work is because your s-on and have a secured boot.img
Busybox is a bunch of linux commands rolled into one. Your phone is already linux, but busybox puts all these commands in one place, and adds some additiinal commands not native to the phone.
Your partitions are most likely ext4 as the regular one is. Are you sure you have an unsecured boot img installed. Pretty sure busy box won't work without one. If you are not s off flashing a rom will not change the boot img. You will have to extract the image and flash via fastboot manually.
Typed on a HTCone via rumrunners
Sounds good, hopefully w this info I can move on, stuck at the laundrmat w my b**** gf, so ill post results in or about 2 hours. Thnx in adv.:good:
Hello guys, I've been trying to install BusyBox myself too today, but without success.
The flashable via Recovery Mode linked file is dead.
Could somebody please re-upload the file ?
Thanks!
htc_one_mini_m4 said:
Hello guys, I've been trying to install BusyBox myself too today, but without success.
The flashable via Recovery Mode linked file is dead.
Could somebody please re-upload the file ?
Thanks!
Click to expand...
Click to collapse
http://vzw1files.dyndns.org/BUSYBOX/busybox_recovery_flashable.zip