Nexus S & Galaxy Nexus one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu
This tool will root you nexus s/Galaxy Nexus install su or super su and ClockWorkMod recovery!!
For Nexus S:4G,I9020T,I9023,I9020A.
Galaxy Nexus:GSM/Verizon/Sprint
Disclaimer!
Your warranty is now void.
I am not responsible for bricked or damaged devices
YOU are choosing to make these modifications.
Click to expand...
Click to collapse
DOWNLOAD
Click to expand...
Click to collapse
Current Version (Nexus S + Galaxy Nexus) 3.5: http://d-h.st/qaL
MIRROR:http://www.mediafire.com/download.php?1if2rvgpcte2rcs
Old versions:
3.0: http://d-h.st/mhO
2.0: http://dev-host.org/gcZ (nexus s only)
1.0: http://dev-host.org/bEE (nexus s only)
HOW-TO
Click to expand...
Click to collapse
just unzip the content and run the tool ! drivers are included in case you need them.
incase you had any problems try rerunning the tool,and if you got superuser/supersu app but you are unable to use root apps,update superuser/supersu from the play store then update the binary from inside the app.
CHANGELOG
Click to expand...
Click to collapse
V3.5
-added support for jelly bean
-few script optimization
-updated superuser and supersu
V3.0
-added support to galaxy nexus and all it's variants.
-added support to install super su.
-moved from *.bat to *.exe
-new icon
-su/super su, will now automatically flash no need to touch "install zip"
-skip bootloader unlock if you are already unlocked.
-update drivers
V2.0
-Removed "sticky.bat"
-modified su flashing script.
-the recovery now will stick automatically no need to flash any file after rooting or running any script.
V1.0
-initial release
ALL DATA WILL BE WIPED FROM DEVICE(only if bootloader is locked)
credits
-Chainfire for super su
-ChainsDD for superuser
-Pdanet for drivers
-Clockworkmod team for recovery
-my friend for the icon
am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?
raducux said:
am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?
Click to expand...
Click to collapse
if your bootloader is locked then yes you will loose everything on USB storage,if the bootloader is already unlocked you will not loose any data,you don't need to flash a rom after rooting the device as it will not wipe the system.
Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?
Sticky please
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.
Romaniac said:
Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?
Click to expand...
Click to collapse
Turn off the usb storage,you just need usb debugging enabled if you turned on usb storage it will not work
stewie-droid said:
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.
Click to expand...
Click to collapse
The tool includes the latest cwm img,but if you want to replace it with another one you can do,just make sure you rename it to same name of the img in the root tool folder,but make sure that the recovery you will use is compatible with the nexus s
After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.
Ritwik7 said:
After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.
Click to expand...
Click to collapse
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.
Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.
Ritwik7 said:
Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.
Click to expand...
Click to collapse
My friend can you guide where i can find this .zip because i m facing the same problem.thank you in advance
Ok I got it to stick by using Root Explorer to mount it as read/write first then ran the sticky.bat. ICS is the rm /etc/install-recovery.sh command.
m.sabra said:
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.
Click to expand...
Click to collapse
I tried this and when I want to do the sticky.bat, when I type the "rm /etc/install-recovery.sh" it sais rm failed for /etc/.., Read-only file system
I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966
karx23 said:
I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966
Click to expand...
Click to collapse
thanks ! added the link to the OP in case anyone had problems like this.
Argh, I seem to have successfully unrooted my Nexus S 9020t and had it rebooted back in, but while it was booting up again I accidentally pressed a button and it told me "error: device not found" twice followed by "<waiting for device>".
Unfortunately my phone has already been rebooted, but it still seems to be waiting for my device. I'm not sure if I can disconnect this device from USB while this is going on, so uh, what do I do?
Edit: Disconnected and reconnected the USB cable on the phone to see what would happen, and it seems to be ok. I'm still stuck on "waiting for device" though. Should I consider restarting the process again?
Edit Edit: Decided to just try to redo the process all over again...seems to have worked!
Updated tool to version 2.0 ! check the changelog in OP, it should solve all sticky recovery related problems,as i removed sticky.bat and now the recovery will stick automatically without the need of running any commands or flashing any fixes.
thanks for reporting problems and feedbacks
thank you for this
Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?
Lelouche said:
Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?
Click to expand...
Click to collapse
Ok first have you unlocked your bootloader when the tool asked you to use volume buttons to chose yes and unlock ? (If you did this you should see an unlocked lock under google logo when booting the phone) if you didn't just run the script again and unlock the bootloader.
Are the drivers installed properly ? When you connect the phone to the pc check device manager to see if the PC recognizes the phone (the drivers are included in the tool in case you need them .
And last check the root tool folder on your pc it should have a file called cwm.img if it doesn't then download the tool again.
SuperUser is not visible after the process
I am on stock ICS, I had previously unlocked the bootloader, then I did the whole process mentioned in this thread. It showed me the CWM menu but when I did the reboot, I couldn't find the superuser app. Then to test whether it is rooted or not, I installed titanium backup but it says the device isnt rooted. What to do now? I tried SuperOneClick but it doesn't seem to work.
Edit: Thanks guys, sorry. It was my mistake, I didnt do the whole process in a right way. It is working as expected.
Related
Ok guys I noticed a lot of people are getting stuck with this myself included and for me it was because the information I needed was fragmented all over the place, So here is all the information that I used some parts have been edited to fit the purpose of rooting 1.01 as there is no definative guide at the minute.
1st thing to do is make a goldcard even if you already have a working goldcard make it again mine was working for other phones but wouldnt work for this.
All credit for the goldcard guide goes to BlaY0
BlaY0 said:
Here are few easy steps on how to make Goldcard without taking it out of your phone but you have to be root (VISIONary temproot is fine).
You will be doing this from command prompt:
Code:
adb shell
su
First you need to find out sdcard's CID:
Code:
cat /sys/class/mmc_host/mmc0/mmc0:*/cid
...copy it into text box on http://hexrev.soaa.me/. Now go to http://psas.revskills.de/?q=goldcard and put in the reversed CID you have got on previous web page. Push goldcard.img to your phone via 2nd command prompt:
Code:
adb push goldcard.img /data/local/
...unmount sdcard via Settings, go back to 1st command prompt and make a backup then make goldcard:
Code:
dd if=/dev/block/mmcblk0 count=1 of=/data/local/sdcard_backup.img
cat /data/local/goldcard.img > /dev/block/mmcblk0
sync
exit
You may also pull that backup to your PC:
Code:
adb pull /data/local/sdcard_backup.img .
Click to expand...
Click to collapse
The 2nd guide you will need to use is also by BlaY0
BlaY0 said:
Preface
Because there are too many ppl without any knowledge spreading false findings and statements I decided to write this HOWTO.
Audience
This HOWTO is primarily ment for those who already have rooted Legends but they recently experienced problems flashing CM's or new Vodafone FroYo boot.img.
Background
HBOOT is like a BIOS in our PCs and to cut a long story short it also contains partition table for phone's internal storage. That means it has info on where exactly certain partition starts and how big it is.
At HTC they decided to partition Legend's internal storage this way:
misc 640 kB
recovery 4,375 MB
boot 2,5 MB
system 240 MB
cache 40 MB
data 185 MB
...but as we found out (first with CM nightly) boot partition was a little short for the boot.img to fit in if we had one or more bad cells (sectors) on it. Eventually we found out that quite some Legend's had bad cell on boot partition and those unfortunate souls that owned such phone were unable to upgrade to Vodafone FroYo rooted ROM too.
I think that HTC also recognized that Legend's boot partition was kinda small so they rearanged partition table in HBOOT 1.00 a bit making boot partition bigger (now it is 3 MB) by shrinking recovery partition a little.
So now we know that some of us actually need HBOOT 1.00 in order to flash FroYo's boot.img without a problem. But how do we keep root then?
Prerequirements
Android SDK (primarily adb)
working USB drivers (for adb to work)
goldcard (in case you are trying to flash ROMs with different CID than your phone has)
ClockWorkMod recovery (if your Legend is already rooted)
Rerequirements
Vodafone FroYo OTA update (actually just firmware.zip from OTA)
Legend rooting tools (just testimage.zip)
Hack 4 Legend v5(just misc1-2.img and flash_image)
VISIONary r13(r14 is out also but i haven't tested it yet)
Instructions
I will split instructions into two parts... for already rooted phones and phones that were already updated with Vodafone OTA thus they lost root.
Already OTA updated with HBOOT 1.00
That one is relatively easy. You could also follow Paul's guide but I like my approach better
Connect your phone to your PC. Second you have to install VISIONary r13 into your phone and do the "temproot" procedure. After a successful "temproot" you should be able to adb shell and then su. Fire up command prompt and issue:
Code:
adb shell
su
...you should have root privileges now (showing #). Next thing is backing up misc partition and replacing it with one from hack4legend-v5.zip. Extract this zip somewhere and fire another command promt there. Now you should upload flash_image binary and misc1-2.img:
Code:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
...switch back to 1st command prompt and change permission of flash_image_binary:
Code:
chmod 755 /data/local/flash_image
...and backup your current misc partition:
Code:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
Now flash misc1-2.img:
Code:
/data/local/flash_image misc /data/local/misc1-2.img
exit
...and you are set to downgrade retaining HBOOT 1.00.
Unzip r4-legend-root.zip and find testimage.zip in it. Put it on your phone's sdcard renaming it to LEGEIMG.zip. You can then reboot into bootloader issuing:
Code:
adb reboot bootloader
...from command prompt. Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard. Make your sdcard gold and try again. After successful flash and reboot you may remove LEGEIMG.zip from sdcard. Next step is upgrading of rooted FroYo ROM. Put FroYo update ROM zip to your sdcard and install it via ClockworkMod recovery. You may also flash backed up misc partition after that. Still in recovery mode and hooked with your PC switch to command prompt and restore it back:
Code:
adb shell
flash_image misc /sdcard/misc_backup.img
exit
...and reboot.
Click to expand...
Click to collapse
So by now you will be on an unrooted Eclair rom. The third guide I used was by David Cogen
David Cogen said:
I. Before You Begin
1. YOU MUST BE ON VERSION 1.31 IN ORDER TO ROOT THE LEGEND, IF YOU ARE NOT YOU CAN DOWNGRADE USING THIS PROCEDURE.
2. This will erase all the data on your phone so please at least sync your contacts with Google before continuing.
3. You must have HTC Sync version 2.0.33, not a newer version. Uninstall HTC Sync and install this version instead.
1. Download the Rooting Tools
Legend Rooting Tools
2. Unzip them to the C: drive on your computer (so the file path is C:\r4-legend-root\)
3. Turn off your phone and turn it back on by holding down Back and Power until you see Fastboot come up on the screen. Push the Power button while highlighting Fastboot on the phone and Fastboot should show up in red now on the phone (if it doesn’t push Power again until it does).
4. Plug the phone in via USB cable to the computer.
5. Open the folder you extracted to the C drive and double click “step1-windows.bat” and wait for it to finish.
6. Once you see the menu on the phone come back up, navigate to BOOTLOADER and push power, then navigate to RECOVERY using the volume buttons to navigate and the power button to select and the phone should boot to the ! screen.
7. Now on the computer double click the “step2-windows.bat” file and wait for it to finish. (UPDATE 12.13.10 – You MUST have HTC Sync version 2.0.33 not a newer version for step2 to work. Please uninstall HTC Sync and download and install this version instead, unplug then plug your phone back in, then rerun step2-windows.bat).
8. Now you should see a custom recovery screen, using the optical trackpad navigate to Wipe and push on the trackpad to select it. Then navigate to Wipe data/factory reset and select that.
9. Once that is done, push volume down to go back to the main menu and select Flash zip from sdcard and select the rootedupdate.zip file and wait for it to flash. All done, you have root access and can use any root required app! Enjoy!
IV. Load a Custom ROM etc (Optional)
1. Head over to our How To Load a Custom ROM on the HTC Legend procedure and continue with that to load custom ROMs and other fun stuff!
Thanks to Paul at Modaco for his awesome scripts!
Click to expand...
Click to collapse
By now you should have HBOOT 1.01 with a rooted Ecclair ROM and Clockwork Recovery Mod So you can flash any custom rom that you like although I would recommend you try B 0.2
If you use this guide, you do so at your own risk.
wow...nice tutorial
I've requested that this goes in the stickies. Well done mate
FeaRThiS said:
The 2nd guide you will need to use is also by http://forum.xda-developers.com/member.php?u=609649
So by now you will be on an unrooted Eclair rom.
Click to expand...
Click to collapse
Question: So the second guide is to downgrade Froyo 3.5 to Eclair 1.3?
smartsreenath said:
wow...nice tutorial
Click to expand...
Click to collapse
Thanks glad it helped.
TheGrammarFreak said:
I've requested that this goes in the stickies. Well done mate
Click to expand...
Click to collapse
Cheers m8 Might not be the best way but it was the only way I managed to root mine on 1.01.
nxdu said:
Question: So the second guide is to downgrade Froyo 3.5 to Eclair 1.3?
Click to expand...
Click to collapse
Fist FroYo is 2.2 not 3.5 and Eclair is 2.1 not 1.3 but yes it is to downgrade to Eclair so that you can root and then upgrade back to FroYo so you end up with rooted FroYo.
FeaRThiS said:
Fist FroYo is 2.2 not 3.5 and Eclair is 2.1 not 1.3 but yes it is to downgrade to Eclair so that you can root and then upgrade back to FroYo so you end up with rooted FroYo.
Click to expand...
Click to collapse
FroYo is HTC WWE 3.x, and éclair is 1.x and 2.x
Thank you!, so it doesn't matter which version of Froyo you're on but what the Hboot version of your phone is on that varies what guide you'll be using ? mine is asia's 3.15.707.3
Yes , one last thing;o how do I check whether all my contacts are properly syncd with Google ? As gmail does not display any of my contacts, if so how would I go about doing it ?._.
Sent from my HTC Legend using XDA App
TheGrammarFreak said:
FroYo is HTC WWE 3.x, and éclair is 1.x and 2.x
Click to expand...
Click to collapse
Ahh I was talkin Android version not HTC version more confusion.
Sent from my HTC Legend using XDA App
FeaRThiS said:
You will be doing this from command prompt:
Code:
adb shell
su
Click to expand...
Click to collapse
Creating a goldcard procedure
What I did, installed visionary r13, clicked on "temproot now"
Access the adb shell via "cd c:\windows-anroid-sdk\platform-tools\adb shell"
however I got the $ sign and when I typed su it says "permission denied" what might be the problem? sorry._. new to this
Hi Folks,
If you don't mind me asking, do you reckon this will work for HTC Wildfire running 2.2 RUU from shipped ROMs with Hboot of 1.01? TIA.
First I was like... but then I was like
Hey Guys,
I hope someone can help me. I followed some tutorials about rooting the HTC Legend. I followed some steps but when I had to downgrade my HTC Legend it went wrong, whatever I try every methode keeps saying, permission denied. And when I use the RUU Bootloader it says some kind of error:S I really want my Legend to get rooted! Can anyone help me?
Kind Regards Tom
After rebooting the bootloader in the second guide, it can't find LEGEIMG.zip. It says image is wrong. I have the LEGEIMG.zip in goldcard root. please help!
haha123 said:
After rebooting the bootloader in the second guide, it can't find LEGEIMG.zip. It says image is wrong. I have the LEGEIMG.zip in goldcard root. please help!
Click to expand...
Click to collapse
Format your SD card in a card reader, as FAT32, then create the Goldcard as described in the first post in this thread.
Make sure you get a NEW goldcard.img as Blay0 describes in the quoted post, my old Goldcard image I used with the 2.1-update1 no longer worked and I needed to get a new one. I think the CID changed when upgrading to 2.2.
This was my problem and doing what I described above solved my problem.
TheLegendaryJay said:
Format your SD card in a card reader, as FAT32, then create the Goldcard as described in the first post in this thread.
Make sure you get a NEW goldcard.img as Blay0 describes in the quoted post, my old Goldcard image I used with the 2.1-update1 no longer worked and I needed to get a new one. I think the CID changed when upgrading to 2.2.
This was my problem and doing what I described above solved my problem.
Click to expand...
Click to collapse
What about this?:
What I did, installed visionary r13, clicked on "temproot now"
Access the adb shell via "cd c:\windows-anroid-sdk\platform-tools\adb shell"
however I got the $ sign and when I typed su it says "permission denied" what might be the problem?
justcookiesncream said:
What about this?:
What I did, installed visionary r13, clicked on "temproot now"
Access the adb shell via "cd c:\windows-anroid-sdk\platform-tools\adb shell"
however I got the $ sign and when I typed su it says "permission denied" what might be the problem?
Click to expand...
Click to collapse
you could try visionary r14 but r13 worked fine for me and many others.
Is this safe?
(or safe as it can be?)
I was previously rooted, but then the microphone on my handset broke, and I replaced it under warranty.
I now have a new handset, but it's back to the stock Vodafone UK Froyo build, with HBOOT 1.0
I'm really liking the look of Blay0's ROM, but fearful of breaking the phone...
brypie said:
Is this safe?
(or safe as it can be?)
I was previously rooted, but then the microphone on my handset broke, and I replaced it under warranty.
I now have a new handset, but it's back to the stock Vodafone UK Froyo build, with HBOOT 1.0
I'm really liking the look of Blay0's ROM, but fearful of breaking the phone...
Click to expand...
Click to collapse
I would say its as safe as it can be and BlaY0's rom is amazin 1500+ score on quadrant with data2ext
I have personally used this method to root my phone without any problems but if you are on hboot 1.00 there may be a easier/safer way of rooting but I am unsure about that.
Trying it now...
In the 2nd guide, I can't crete the misc_backup.img --> "read-only file system".
Is this the S-ON / S-OFF thing?
How can I get around this?
Thanks.
brypie said:
Trying it now...
In the 2nd guide, I can't crete the misc_backup.img --> "read-only file system".
Is this the S-ON / S-OFF thing?
How can I get around this?
Thanks.
Click to expand...
Click to collapse
Nothing to do with s-on looks like you dont have root when you type su in adb do you get a # ?
FeaRThiS said:
Nothing to do with s-on looks like you dont have root when you type su in adb do you get a # ?
Click to expand...
Click to collapse
Yep - tempRoot using Visionary
EDIT - just figured it out - I still had the SD Card connected as a disk drive to my PC D'oh!
The Ultimate guide on how to do everything for noobs
Anyone taking these steps please be aware, you do this as your own choice/Risk....If you have anything important on your phone, back it up right now before you proceed....as everything will be wiped by the bootloader unlock!
Bootloader unlock.
Download this >http://www.mediafire.com/download.php?uma19r3pysr93dr
Unzip into a new folder on your c: called Android (C:/Android)
Plug your Phone into Computer/PC and select charge only.
Follow the guide precisely on HTC
1. Go to HTCDEV website: http://www.htcdev.com/bootloader/
2. Click on "Begin Unlock Bootloader" (create a user if you don't have one)
3. follow the instructions step 1 through step 10 on htcdev.com
4. In step 10, when posting your token, make sure you remove the blanks preceding each line
5. After you receive your Unlock_code.bin in email, follow step 11.
6. Now your rezound should reboot and you have your bootloader unlocked.
so you have updated the HBOOT and unlock bootloader....
Good now for the next bit.
If by chance you cannot unlock via HTC Dev please tell me as i maybe able to help you on that.
I require knowing which RUU you have installed, this u will find out by using HTC Dev.
Using HBOOT 1.0.7 and updating should be easy and fast.
Installing CWM 5 (Recovery Menu)
Please also read my orther thread on recoverys...it hold same details with extras >http://forum.xda-developers.com/showthread.php?t=1791707
This is a program installed into the phone itself.
This allows you to do pretty much anything you want.
Main things are Backup and restore of your device.
Flashing of custom Roms
Here is the recovery file >http://forum.xda-developers.com/attachment.php?attachmentid=852074&d=1326296914
Save the recovery.img and flash_image in the root of your adb folder.(this means C:/Android)
Now using DOS CMD window
goto C:/Android
*hint, copy the txt in these windows into your DOS window and press enter....it saves time and spelling errors*
DOS txt
Code:
adb reboot bootloader
it should now reboot and show Fastboot USB mode
DOS txt
Code:
fastboot flash recovery recovery.img
from the hboot menu, go to recovery.
now if above doesn't work and you cannot get into bootloader to flash the cwm. follow this
pull out battery
insert battery
hold volume down key and press power at same time
Hboot will appear
scroll down and select bootloader option, press power.
and your ready now in fastboot usb mode
Rooting
Please note, this method is old, current methods are simply just flash a new rom!
All roms come Pre Rooted with all apps required to run with root (Superuser)
For details in these check out the Android Development forum in our salsa section.
or go here>http://forum.xda-developers.com/forumdisplay.php?f=1043
Download this file >http://www.mediafire.com/download.php?pypn6v69o0vnvl9
(This is outdated somewhat and requires updating via Google Play)
place this file on the base of your sd card.
Now goto your new recovery menu.
use this cmd from DOS Windows
Code:
adb reboot recovery
it will reboot automatically
1-Select Install Zip from SDcard
2-Choose Zip from SDcard
3-Find Root.Zip on the SD card
4-Scroll upto Yes-Install Root.zip
it will now flash the root.zip
5-Go back
6-Reboot System Now
Now from here you will have done the following
Unlocked your bootloader
Flashed recovery system
Rooted your stock device.
if by any chance you make a mistake which is not very likely, but odd chance u do...redo the steps per section till you get it right.
WIKI
Root-2 meanings
System root giving superuser access pr SU
Root of SD - meaning base of sd no folders
ADB Android debug bridge - used with dos commands when phone is plugged into computer via USB cable
extra Utilities are Java SDK
>http://www.oracle.com/technetwork/java/javase/downloads/index.html
Download and install accordingly to instructions given.
this gives access to more functions via ADB
thanks
thank you sir, you are a genius. i was stuck in 'adb'. and dont know what does it mean. got it cleared from geek.com . would like to suggest that please also add things like 'installing utilities from android sdk platform, root means the root directory of system(usually c:\ )for amateurs like me.
nevertheless it's really a useful post.... hats off to you and developers of this site!!!!!!
Save the recovery.img and flash_image in the root of your adb folder
MOD EDIT: No need to quote the whole post when asking a question
"Save the recovery.img and flash_image in the root of your adb folder"What does this mean root of adb folder???and from where will i get this file- flash_image??
raghavaggsss said:
"Save the recovery.img and flash_image in the root of your adb folder"What does this mean root of adb folder???and from where will i get this file- flash_image??
Click to expand...
Click to collapse
read the OP, the files are in the link provided!
>Here is the recovery file >http://forum.xda-developers.com/atta...4&d=1326296914<
can u also trim down the quotes too....being as the first post is big...
Files given by your link
Do we have to download these files from htcdev.com or can we just use your files posted here????
the files are:
adb.exe
AdbWinApi.dll
fastboot.exe
kashttl said:
Do we have to download these files from htcdev.com or can we just use your files posted here????
the files are:
adb.exe
AdbWinApi.dll
fastboot.exe
Click to expand...
Click to collapse
i've hosted the files here in my thread so u don't have to get them from HTCDEV.
Stuck at step 8.. please help!!!!
I am stuck at step 8
It's supposed to show some block of text
Which didn't come up.....
Instead I got a message saying--
<Waiting for the device>
Please help me out....
kashttl said:
I am stuck at step 8
It's supposed to show some block of text
Which didn't come up.....
Instead I got a message saying--
<Waiting for the device>
Please help me out....
Click to expand...
Click to collapse
settings>applications>Development>Debugging mode (Select this option)
Now retry the cmds.
already in debug mode
BigBearEvo said:
settings>applications>Development>Debugging mode (Select this option)
Now retry the cmds.
Click to expand...
Click to collapse
its already in debug mode...... Still not working
kashttl said:
its already in debug mode...... Still not working
Click to expand...
Click to collapse
only thing left is your hboot update!
do u have locked or unlocked in pink?
I dit it all
BigBearEvo said:
only thing left is your hboot update!
do u have locked or unlocked in pink?
Click to expand...
Click to collapse
What is
locked or unlocked in pink
Click to expand...
Click to collapse
kashttl said:
What is
Click to expand...
Click to collapse
in your hboot menu or bootloader menu, at the top of the screen it will show up locked or unlocked in a pink background, u can't miss it!
do u have this locked or unlocked?
Unlocked or locked....
It's locked..... It shows something like
LOCKED(OOW)
Click to expand...
Click to collapse
What could i do now.......!!!
kashttl said:
It's locked..... It shows something like
What could i do now.......!!!
Click to expand...
Click to collapse
unlock it...simple...without going to htcdev and following the steps which you didn't do, i cannot help
Another problem(the CWM recovery part)........ when i use the adb reboot bootloader cmd command.... it show device not found.........What can I do........!!!
kashttl said:
Another problem(the CWM recovery part)........ when i use the adb reboot bootloader cmd command.... it show device not found.........What can I do........!!!
Click to expand...
Click to collapse
select debugging mode in settings>application>Development
if this is unchecked, check it. then try cmds.
if this is already enabled and it still dont work on cmds then reboot into hboot yourself.
to do this, pull out battery, insert battery, hold volume key down while pressing power on button, hboot will appear, now wait...then select bootloader, and then fastboot usb will appear.
now follow cmds to install recovery
again all this is explained in main thread
SuperUser?
Hi BBE,
Followed your tutorial and was successful at every step. But one thing that is bothering me (or maybe I messed up at some step) is that I still do not have the Superuser (Su) rights. I used "Root Check Basic" and it says I have Root access. But when I try to run "Link2sd" or "Titanium Backup" it says I do not have Superuser rights. Is this method supposed to give us Superuser rights? If yes then what should I do now? If no then how can I get Superuser rights for my HTC Salsa?
Thanks.
Zaeem
Look in the apps list and you should see a pirate like app icon. If you do open app up and update it. This should rectify the su problem. If not.gimme a shout
BB is using Xparent Tapatalk ICS Blue
BigBearEvo said:
Look in the apps list and you should see a pirate like app icon. If you do open app up and update it. This should rectify the su problem. If not.gimme a shout
BB is using Xparent Tapatalk ICS Blue
Click to expand...
Click to collapse
Yea I did update it myself and now I have Su on my Salsa . However the binary is out dated and when I try to update it, it gives me 'failure' status. Downloaded the SuperUser binary installer fix from Market but still getting the error. Any help with that? (I think I am good even with the out dated binary though)
ZaeemRaza said:
Yea I did update it myself and now I have Su on my Salsa . However the binary is out dated and when I try to update it, it gives me 'failure' status. Downloaded the SuperUser binary installer fix from Market but still getting the error. Any help with that? (I think I am good even with the out dated binary though)
Click to expand...
Click to collapse
ok goto market, download, SuperSU looks like a large blue hashtag lol.
install that, update it etc, see if that runs, if you get successful updated binary, reboot the phone. u can run with both SU apps, but you would be better removing the old Su in favour of the new one...im gonna look around for a root.zip with new Super Su in there
I originally posted this method at AddictiveTips. The method I posted there is targeted at everyone including the absolute beginners and I have also included instructions there for setting up the required tools, and for reverting back to the original recovery and boot image in case anything goes wrong. All external credits should be given to that guide (it does link back to this thread). Here is the link: How To Root Nexus 4 and Install ClockworkMod Recovery on it.
To my knowledge, this is the first confirmed working rooting method for Nexus 4 posted here at XDA. Though my knowledge is limited, so please correct me if I am wrong.
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
This method requires an unlocked bootloader. You can find instructions for unlocking it at XDA, or at the AddictiveTips guide linked above (the link to the bootloader unlock guide is in the requirements section there).
UPDATE 2: If your device does NOT get wiped after unlocking the bootloader, fret not. While this isn't expected behavior, several users have experienced the same on the Nexus 4. This could be due to some error at Google's end, but unlocking still works perfectly fine.
That said, let's get on with rooting and flashing CWM.
ClockworkMod Recovery Method:
Download the latest official ClockworkMod recovery from CWM website and rename it to recovery.img
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Download the recovery flashable SuperSU package with Busybox and transfer it to your phone's internal SD card.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Enter this command in a command prompt to flash the ClockworkMod recovery (making sure you are in the directory where you downloaded the recovery file):
Code:
fastboot flash recovery recovery.img
OR
If you simply want to root without flashing a custom recovery and want to stick to your stock recovery, simply boot this recovery once using this command:
Code:
fastboot boot recovery.img
If you flashed the recovery in the previous step, you can now boot into recovery by pressing volume-up or volume-down twice to select the recovery option, and then the power button to enter it. If you simply booted into the recovery file without flashing it in the previous step, you should already be in recovery now.
Once in recovery, take a backup to be on the safe side.
Flash the downloaded SuperSU and busybox package zip file from recovery.
Clear cache and dalvik cache just in case (not required but won't hurt).
Reboot the device.
ADB and Insecure Boot Image Method:
Grab the insecure boot image from this thread.
Also download these root files. This package includes the latest SuperSU 0.98, latest su binary that comes with it, and working busybox (not sure if latest).
Extract the contents of the downloaded zip file to your computer.
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Get back into bootloader mode and boot into the downloaded insecure boot image:
Code:
fastboot boot boot.img
Don't worry, this will not replace your existing boot image and will only boot from the insecure one once.
If it does NOT work for you and you get stuck in a boot loop, simply reboot your phone into bootloader and use the above command again. Some users had issues with booting from it the first time, but a second attempt worked.
Once booted into Android successfully using the insecure boot image, simply enter these commands one by one in command prompt (making sure you are in the directory where you downloaded the files):
Code:
adb shell mount -o remount,rw /system
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit
Reboot your device.
You will now have root access. Tested and confirmed working by Stryder5 and many others.
Credits:
Stryder5 for testing, confirming, tipping me about working CWM, providing the required drivers, and helping others on the thread. :highfive:
Harry GT-S5830 for the insecure boot image.
fkrone for his recovery revert disabler script and his unofficial working CWM before an official one became available.
Kstarz for posting this same recovery method with his own working CWM in this thread before an official one was out.
evaradar for informing about the release of official ClockworkMod recovery.
Koush for developing ClockworkMod recovery.
Chainfire for developing SuperSU.
Everyone else on this thread for testing, providing feedback and hitting the 'THANKS' button. =)
I have tried my best to give everyone the due credit but if I have missed out on anyone, please do remind me.
Yep, worked like a charm. Got Titanium running and restored all my apps
Btw, check your PM.
Checked...thanks. =) Added the links.
stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied
jshaw06 said:
stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied
Click to expand...
Click to collapse
You need to boot the unsecure boot.img first.
BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.
HQRaja said:
BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.
Click to expand...
Click to collapse
I'm pretty sure I used the one Harry GT-S5830 provided.
I used the one in the OP of that thread.. is there a different one I'm supposed yo use?
Sent from my SGH-T999 using Tapatalk 2
---------- Post added at 06:41 AM ---------- Previous post was at 06:23 AM ----------
It works
Sent from my SGH-T999 using Tapatalk 2
jshaw06 said:
It works
Click to expand...
Click to collapse
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.
Stryder5 said:
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.
Click to expand...
Click to collapse
No issues with installing the OTA after root?
Edit: Just noticed in your sig that you did not install the update.
I installed after ota
Sent from my SGH-T999 using Tapatalk 2
jshaw06 said:
I installed after ota
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
You mean you gained root after you installed the OTA?
---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------
apzalo said:
No issues with installing the OTA after root?
Click to expand...
Click to collapse
I gained root, but haven't installed the OTA yet.
when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?
Yes sorry gained root after OTA
Sent from my SGH-T999 using Tapatalk 2
Elemenopee said:
when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?
Click to expand...
Click to collapse
Nope, it isn't. Try again...it's safe to try as many times as you want since we're not flashing the boot image; merely booting from it, which is temporary and doesn't last after reboot. Hope it works on the next try.
After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!
quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?
Ngo93 said:
After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!
Click to expand...
Click to collapse
Step 8 itself will boot up the phone normally into Android, just using that insecure boot image instead of the stock one. And yes, you then just start entering those adb commands. =)
0.0 said:
quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?
Click to expand...
Click to collapse
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.
HQRaja said:
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.
Click to expand...
Click to collapse
so i extract the "occam-jop40c-factory-cd3dc140.tgz" file, then double-click the "flash-all.bat" file?
Disclaimer: If you are not comfortable with using Fastboot and ADB and editing system files than this guide might not be for you. At this point this is what I have to offer.
Click here for the unofficial twrp image - Latest version as of 12/27/14
So getting right into it.
1. Turn on ADB mode on the watch by going to about and tapping the build info 7 times.
2. Download ADB and Fastboot utilties
3. Plug the watch into the computer and your phone should vibrate and ask you to accept the computers fingerprint, tick the check box to always allow and hit ok
4. Open up a command prompt or terminal inside of where the ADB utilities are located and enter
Code:
adb reboot bootloader
This next step will wipe your data!
5. Now you should be in fastboot, go ahead and on the terminal use the next code and follow prompts to unlock
Code:
fastboot oem unlock
6. Now after you re-set up your watch again you will need to do step 1 and 3 again.
Please do not skip step 6!
7. Go ahead and issue
Code:
adb reboot bootloader
8. Flash unofficial twrp, make sure the recovery image file is in the same location as fastboot than issue
Code:
fastboot flash recovery YOURIMGNAMEHERE.img
9. Upon successfully doing that you should have twrp installed
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB use the proper name of what you downloaded. Issue
Code:
adb push SUPERSUNAMEHERE.zip /sdcard/
11. Issue
Code:
adb reboot recovery
12. than using the very tiny TWRP and somewhat messed up go ahead and use it to install the supersu.zip under the folder /sdcard
13. Enjoy root and twrp.
I will make this guide into a much easier Java program in the very near future to make it easier to use.
This was typed up pretty fast and it is kinda hacky, I will work on a bat script and a shell script if we have enough osx users here. I'm sure someone will come along and make this better if I don't get around to it.
Credits:
Dees-Troy for his TWRP support for dory our fish brother device which worked on our device
Chainfire for all his hard work these many years
Q: ADB complains there is no device listed.
A: Install universal ADB drivers and then go to device manager and under the device with a yellow warning icon go to update driver, Browse my computer, let me pick from list of device drivers, than Google ADB interface. If it still complains turn off debugging, than turn it back on, revoke authorization, then disable and re-enable again.
One more just in case.
Great work!!
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
hatefuel19 said:
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
Click to expand...
Click to collapse
The latest supersu is version 2.36 dated 11.27.2014. 1.94 is well over a year old, you need to update for sure that is why you are force closing.
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
hatefuel19 said:
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
Click to expand...
Click to collapse
I'm here to help! I'm working on adding other mods to my other thread right now I'm working on getting busybox working.
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
---------- Post added at 09:31 PM ---------- Previous post was at 09:28 PM ----------
jimmydigital00 said:
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
Click to expand...
Click to collapse
Disregard I did it again and for some reason it worked. Maybe I need to reboot first.
Recovery
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
adamrobles said:
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
Click to expand...
Click to collapse
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
reflashed
tonu42 said:
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
adamrobles said:
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
Click to expand...
Click to collapse
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
Thank you for that information, I stopped the download of the dump.
Downloading the stock recovery now.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
I must have skipped a step...
installed stock recovery
booted into the watch system
enabled adb debugging
reboot to bootloader
install your recovery image
rebooted
pushed supersu
rebooted to twrp
installed supersu
rebooted to system
adb shell - verified root!
You are awesome! Thank you for taking the time to help me!
HYPE for 5.0.1
'm Hype! can't wait to flash the first 5.0.1 system dump on this as stated by +Darek Ross we MAY be receiving update as early as today!
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
zvieratko said:
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
Click to expand...
Click to collapse
My guide is setup like the one you put there. In order to get adb working again you need to re setup the watch step 6. Read the instructions carefully. I'll post a batch script later to simplify this.
Sent from my A0001 using XDA Free mobile app
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
zvieratko said:
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
Click to expand...
Click to collapse
By default debugging is disabled, I'm not sure how you were able to issue an ADB command on step 7 with out first performing step 6.
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
zvieratko said:
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
Click to expand...
Click to collapse
Ah I see, yea the guide is written as the absolute minimum to work right now. Like I said later today I'll try to post a script that automates all of this, its much easier.
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
mca1 said:
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
Click to expand...
Click to collapse
How did you install that Hong Kong lollipop?
mca1 said:
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
Click to expand...
Click to collapse
Hi there.If you have root access and unlocked bootloader,you can install TWRP even without pc connection.
first you should download a terminal emulator app from google play.
then you should download the latest version of TWRP image file from here https://dl.twrp.me/yuga/.
Place it in the root of your /sdcard folder and rename it to twrp.img
Run the following commands in terminal app
Code:
su
and then we write recovery image file to FOTA with dd command.
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
and it's done.
press thanks if it was helpful.
i installed hk lollipop zip from my custom twrp recovery. and when rom istall has finished ; recovery gone.
mrp1375 said:
Hi there.If you have root access and unlocked bootloader,you can install TWRP even without pc connection.
first you should download a terminal emulator app from google play.
then you should download the latest version of TWRP image file from here https://dl.twrp.me/yuga/.
Place it in the root of your /sdcard folder and rename it to twrp.img
Run the following commands in terminal app
Code:
su
and then we write recovery image file to FOTA with dd command.
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
and it's done.
press thanks if it was helpful.
Click to expand...
Click to collapse
thank you mrp1375 but i tried this method and when i want to go recovery phone only restarts. because phone has no stock recovery.
mca1 said:
thank you mrp1375 but i tried this method and when i want to go recovery phone only restarts. because phone has no stock recovery.
Click to expand...
Click to collapse
Below are 2 solutions to get a properly working recovery
Preperation:
1. Download Dual recovery installer: XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip
2. Install NDRUtils
Next up we will test if the TWRP you installed works or not
-open NDRUtils and choose to boot into TWRP recovery.
Now unhide the result that you got to continue with the installation:
OK: I am now in TWRP
flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and reboot.
Everything will work normally now.
Not OK: I am not in TWRP
Reboot the phone if you have to (hold power until you feel 3 vibrations and then turn the phone back on)
You need to download this: http://nut.xperia-files.com/path/XZDualRecovery/Kernel_Builder
To get the right file make sure to selec the xperia z c6603 and select the rom version you are using, you can view what you have in settings, about phone, build number.
it will be much easier for you if you install this: X-plore File Manager The reason i recommend this application is that it automatically makes sure the file rights are correct.
Go into the settings and enable superuser +mount root mode
Now you can browse to the folder where you downloaded the zip in the left pane.
go into the zip and and then into tmp
Select the boot.img
now move to the right pane and browse to the root of your SD card like the comment above
go back to the left pane and with boot.img still checked click copy.
Now follow the original instructions mrp1375 gave you, but notice the different filename
Open terminal
Type : su
Type: dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now you can reboot and if it worked the phone will vibrate twice and show a green led meaning you can press the down button to enter TWRP recovery.
Go into the recovery and now flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip so you get a proper installation
Now remember this very important fact:
Whenever you flash or wipe anything you MUST reinstall recovery and root again.
This is a failsafe strategy you can NEVER ignore becaus of your usb issues.
Keep SuperSu installer and XZ-lockeddualrecovery installer on your device at all times!
thank you
mca1 said:
thank you
Click to expand...
Click to collapse
Does that mean it worked?
tetsuo55 said:
Does that mean it worked?
Click to expand...
Click to collapse
Yes it worked, thank you much. :good:
tetsuo55 said:
Below are 2 solutions to get a properly working recovery
Next up we will test if the TWRP you installed works or not
-open NDRUtils and choose to boot into TWRP recovery.
Now unhide the result that you got to continue with the installation:
OK: I am now in TWRP
flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and reboot.
Everything will work normally now.
Not OK: I am not in TWRP
Reboot the phone if you have to (hold power until you feel 3 vibrations and then turn the phone back on)
You need to download this:
To get the right file make sure to selec the xperia z c6603 and select the rom version you are using, you can view what you have in settings, about phone, build number.
it will be much easier for you if you install this: The reason i recommend this application is that it automatically makes sure the file rights are correct.
Go into the settings and enable superuser +mount root mode
Now you can browse to the folder where you downloaded the zip in the left pane.
go into the zip and and then into tmp
Select the boot.img
now move to the right pane and browse to the root of your SD card like the comment above
go back to the left pane and with boot.img still checked click copy.
Now follow the original instructions mrp1375 gave you, but notice the different filename
Open terminal
Type : su
Type: dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now you can reboot and if it worked the phone will vibrate twice and show a green led meaning you can press the down button to enter TWRP recovery.
Go into the recovery and now flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip so you get a proper installation
Now remember this very important fact:
Whenever you flash or wipe anything you MUST reinstall recovery and root again.
This is a failsafe strategy you can NEVER ignore becaus of your usb issues.
Keep SuperSu installer and XZ-lockeddualrecovery installer on your device at all times!
Click to expand...
Click to collapse
Hey! I have the same problem as the OP here. I followed the instructions like 5 times and still couldnt get it to work. The terminal is saying that "No space left on device" when i type "dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
any way to fix this? Thanks!
comcastic08 said:
Hey! I have the same problem as the OP here. I followed the instructions like 5 times and still couldnt get it to work. The terminal is saying that "No space left on device" when i type "dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
any way to fix this? Thanks!
Click to expand...
Click to collapse
That error sounds like either you dont have root or you have a typo, can you make a screenshot?
tetsuo55 said:
That error sounds like either you dont have root or you have a typo, can you make a screenshot?
Click to expand...
Click to collapse
snag. gy/gi8Ji. jpg
sorry i cant post links yet
comcastic08 said:
snag. gy/gi8Ji. jpg
sorry i cant post links yet
Click to expand...
Click to collapse
That doesnt look quite right it should look like this:
Code:
[email protected]:/ $
Then you type "su" (without the quotes) and press enter
The display then changes to:
Code:
[email protected]:/ #
Now you type "dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel" (without the quotes) and press enter
And then it should work properly.
tetsuo55 said:
That doesnt look quite right it should look like this:
Code:
[email protected]:/ $
Then you type "su" (without the quotes) and press enter
The display then changes to:
Code:
[email protected]:/ #
Now you type "dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel" (without the quotes) and press enter
And then it should work properly.
Click to expand...
Click to collapse
i typed su before that code and the same error occured sadly
why did my usb port had to break ugh
comcastic08 said:
i typed su before that code and the same error occured sadly
why did my usb port had to break ugh
Click to expand...
Click to collapse
Can I have another screenshot of that?
tetsuo55 said:
Can I have another screenshot of that?
Click to expand...
Click to collapse
snag .gy/AekHa. jpg
comcastic08 said:
snag .gy/AekHa. jpg
Click to expand...
Click to collapse
In that screenshot i see again the same mistake i mentioned before
please do this
Just type only su and enter
and then send me the screenshot of that.
tetsuo55 said:
In that screenshot i see again the same mistake i mentioned before
please do this
Just type only su and enter
and then send me the screenshot of that.
Click to expand...
Click to collapse
snag. gy/aWyCY .jpg
comcastic08 said:
snag. gy/aWyCY .jpg
Click to expand...
Click to collapse
All i can think of is that you have the wrong boot.img
tetsuo55 said:
All i can think of is that you have the wrong boot.img
Click to expand...
Click to collapse
i downloaded the one you said XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and renamed it to boot.img
even the twrp.img doesnt work ugh