Related
HTC HOLIDAY SUPERGUIDESTOCK ICS ROOT NOW WORKS
***(BEFORE YOU BEGIN)
- You MUST be on a stock ROM with the bootloader locked or re-locked
- If you are NOT locked/re-locked or you are on a custom ROM, then you MUST follow the following directions...
- Boot into H-Boot by powering off. Once off, power back on and hold VOL DOWN + POWER BUTTON, once in HBOOT go to "fastboot" and click the power button to select
- Download the WCXJB ROOT PACK zip from the bottom to your desktop and unzip it
- Inside the unzipped WCXJB ROOT PACK folder, hold SHIFT and RIGHT CLICK, select open a command window here
- Run this code in the command prompt without quotes
- "fastboot oem lock"
- Now reboot
- Now, we will flash you back to the original stock ROM you were on
- Pick the RUU for your specific device. For example, the one for AT&T has the word "Cingular" in it, the one for Rogers says "Rogers" in it.
- You will find the RUU's here http://www.filefactory.com/f/002b74e0f4775869/ (THANKS to user football)
- Once you download the correct RUU, make sure your phone is plugged in via USB to your computer and you have the correct drivers (or just HTC Sync) installed on your computer
- Run the executable and follow the steps to flash the stock ROM
- Once the ROM loads, you can move on to the next steps
Click to expand...
Click to collapse
***(IF YOU ARE ON AT&T AND YOU DON'T WANT TO S-OFF)
- Go here and under software downloads, download the file that is over 400mb
- Follow the instructions that are listed right above the download button to run the RUU
- Once that is done, do step 1 and then step 4. I repeat, SKIP steps 2 and 3.
Click to expand...
Click to collapse
1) Unlock the bootloader via HTCdev website
- You need to go the the HTC dev website and do the unlock (THIS WILL WIPE ALL YOUR PERSONAL DATA). You must follow the exact instructions they give you. Most people seem to have the biggest problem with the token.
http://htcdev.com/bootloader
- Tip: When copying your token, start with and INCLUDE the line that says "<<<<< Identifier Token Start >>>>>", end with and INCLUDE the line that says "<<<<< Identifier Token End >>>>>"
- Tip 2: Do NOT include the "INFO" portion of every line
- Tip 3: Keep the bin file it gives you just in case you need to relock the bootloader in the future
- Tip 3: On Linux, when getting the token, remember to run fastboot under sudo
Click to expand...
Click to collapse
2) S Off the device (Juopunutbear/WildChild)
- MAKE SURE YOU ARE ON A STOCK ROM WITH AN UNLOCKED BOOTLOADER
- Download the WCXJB ROOT PACK zip below to your desktop and UNZIP it
- On your phone, make sure in your settings, USB Debugging is ENABLED in development
- Turn off your phone, turn it back on my holding power + volume down
- Use the volume rocker and power button to select fastboot
- Connect your phone to your PC
- Inside the WCXJB ROOT PACK, click shift + right click and select "Open command window here"
- Enter in these commands without the quotes
- "fastboot flash recovery wcxrecovery.img"
- Now you can boot up your phone
- Download and put Vivid_CWM_Root_VER2 zip file on root of internal sdcard (aka NOT in any folders)
- Boot into H-Boot like you did before (turn off phone, turn back on holding power + vol down), and use the volume rockers to go to "recovery" and press the power button to select it
- Select "install zip from sdcard"
- Select the VIVID_CWM_ROOT_VER2.zip through recovery and then reboot your phone
- You are now ready to S-OFF
- Go to the link below and click the URL in the first post and follow the instructions
http://forum.xda-developers.com/showthread.php?t=1576668
Click to expand...
Click to collapse
3) Update the HBOOT (Juopunutbear)
- If you haven't already, download the WCXJB ROOT PACK zip below to your desktop and UNZIP it
- Make sure in your settings, USB Debugging is ENABLED in development
- Turn off your phone, turn it back on my holding power + volume down
- Use the volume rocker and power button to select fastboot
- Connect your phone to your PC
- Inside the WCXJB ROOT PACK you just downloaded, click shift + right click and select "Open command window here"
- Enter in these commands without the quotes
- "fastboot erase cache"
- "fastboot oem rebootRUU"
- "fastboot flash zip jb_hboot.zip"
Click to expand...
Click to collapse
4) Perm-Root your device (WildChild)
- Turn off your phone, turn it back on my holding power + volume down
- Use the volume rocker and power button to select fastboot
- Connect your phone to your PC
- Inside the WCXJB ROOT PACK, click shift + right click and select "Open command window here"
- Enter in these commands without the quotes
- "fastboot flash recovery wcxrecovery.img"
- Now you can boot up your phone
- Download and put Vivid_CWM_Root_VER2 zip file on root of internal sdcard (aka NOT in any folders)
- Boot into H-Boot like you did before (turn off phone, turn back on holding power + vol down), and use the volume rockers to go to "recovery" and press the power button to select it
- Select "install zip from sdcard"
- Select the VIVID_CWM_ROOT_VER2.zip through recovery and then reboot your phone
- You are now rooted and I recommend flashing a matching kernel + ROM for root to stick
Click to expand...
Click to collapse
(Optional) Flash a custom Kernel/Recovery (Three options, I suggest the THIRD)
*ATTENTION* IF FLASHING A KERNEL FOR A NEW ROM YOU WANT, YOU MUST FLASH THE ROM IMMEDIATELY AFTER FLASHING THE KERNEL WITHOUT BOOTING UP, THE KERNEL COMES FIRST. OTHERWISE, YOU MIGHT BOOT LOOP.
FIRST (AUTO) (joeykrim's FlashImageGUI method)
http://forum.xda-developers.com/showthread.php?t=1423151
OR
SECOND (AUTO) (xboarder56's method)
- First, turn off wifi on your phone
- If you have SetCPU installed or any other program where you have altered to overclock or underclock, DISABLE the "set on boot" option
- You will have to download Easy Kernel Flasher v03.zip which is attached below
- Next plug in your phone and make sure its getting detected
- After that extract the zip file (kernel flasher)
- Place the boot.img of the kernel you want flashed in the "Kernel-Here" folder.
- Make sure android debugging is enabled on your phone via settings
- Click Flash.bat for windows or Flash.sh for linux and wait for it to close terminal
- Wait for your phone to reboot and wait 5-10 minutes. Then reboot again and wait 5 minutes, then you're good to go!
http://forum.xda-developers.com/showthread.php?t=1328141
OR
THIRD (Manual) (Pirateghost's method)
- Extract the boot.img out of the kernel file or ROM zip that you want and put it in the same directory as your fastboot.exe/fastboot executable (it might be easiest to download the WCXJB_ROOT_PACK.zip from below and unzip it, put the boot.img in there)
- Boot phone into hboot/bootloader (make sure you are in fastboot mode)
- Connect phone to PC
- Inside the unzipped WCXJB_ROOT_PACK folder, click shift + right click, select "open a command window here"
- Enter these codes separately to flash the kernel and reboot the phone
Code:
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
(Optional) Flash a custom ROM
*ATTENTION* IF FLASHING A KERNEL IS NEEDED FOR THE ROM YOU WANT TO FLASH, FLASH THE KERNEL FIRST, THEN THE ROM AFTER, OR ELSE YOU MAY BOOT LOOP.
1) Download a ROM, it should be in a zip file (MAKE SURE the ROM is pre rooted, or else you might lose root. If you do not know, ask the respective dev)
2) Connect your phone to your computer through the USB and mount the storage card (storage mode)
3) Copy the ROM you downloaded and put it on the ROOT of your storage card (not in any folders)
4) Power off your phone. Then power it on holding the POWER and VOLUME DOWN buttons. You should be in H-Boot, now use the volume rocker to select recovery (the power button "selects" it)
5) Once in recovery, scroll down to "backup and restore" and select it, now select "backup". This will give you a safe ROM to fall back on and restore in case anything goes wrong
- IF YOU ARE HAVING ISSUES WITH BACKING UP, pull the battery, boot back into recovery (power + vol down then select recovery) and try again. OR you may have to boot up and delete the old partial backups with a file explorer and try again. OR make sure your USB is no longer connected and try again.
6) Get back to the main recovery menu and select "wipe data/factory reset". Select "Yes" when prompted.
7) Get back to the main recovery menu and select "wipe cache partition". Select "Yes" when prompted.
8) Get back to the main recovery menu and select "advanced". Now select "Wipe dalvik cache" and select "Yes" when prompted.
9) Get back to the main recovery menu and select "Install zip from SD card". Choose the ROM you just put on the storage card, and select "Yes".
10) IF your ROM will not install correctly or you get an error and you are using the recovery from the superguide (this one) then tell the dev of the ROM to update their script to work with the new recovery
11) Get back to the main recovery menu and select "Reboot now". Your ROM will now be loaded up. Do not panic if it takes a small while (5 minutes at most I'd say) because the first boot always takes some time.
Click to expand...
Click to collapse
(Optional) Remove CIQ (8125Omnimax's method)
Go here and follow every step precisely
http://forum.xda-developers.com/showthread.php?t=1415335
Click to expand...
Click to collapse
Wondering about a basic question? Look in this General Knowledge Thread to see if your answer is there.
MORE INFO IN THE SECOND POST
THANKS to GSLEON3, EvilDevnull, WildChild, xboarder56, erik10002, frigid, 8125Omnimax, Pirateghost, thecubed, bjg222, drewdatrip, pside15 (let me know if I missed anyone else)
(If you think I am missing something, please tell me and I'll add it )
6) (Optional) Return to stock (locked bootloader, unrooted, etc) (Many thanks to Pirateghost)
- First, you are going to need to re-lock your bootloader.
- Boot into H-Boot by powering off. Once off, power back on and hold VOL DOWN + POWER BUTTON, once in HBOOT go to "fastboot" and click the power button to select
- Download the adbfastbootrecovery zip from the bottom of the post and EXTRACT it to your desktop
- Go to your computer file explorer and find your desktop "folder", hold SHIFT and RIGHT CLICK, select open a command window here
- Run this code in the command prompt
Code:
fastboot oem lock
- Now reboot
- Now, we will flash you back to the original stock ROM you were on. There are two options for this, the second does NOT need a windows device.
FIRST OPTION (RUU)
- Pick the RUU for your specific device. For example, the one for AT&T has the word "Cingular" in it, the one for Rogers says "Rogers" in it.
- You will find the RUU's here http://www.filefactory.com/f/002b74e0f4775869/ (THANKS to user football)
- Once you download the correct RUU, make sure your phone is plugged in via USB to your computer and you have the correct drivers (or just HTC Sync) installed on your computer
- Run the executable and follow the steps to flash the stock ROM
- Once the ROM loads, you should be good to go
- If you returned to stock because of a bug or issue, and want to root again, make sure to go back and follow the steps PRECISELY to perm root, flash CWM, flash a ROM, flash a kernel, etc. Remember, flash ROM IMMEDIATELY after flashing the kernel
OR
SECOND OPTION (PH39IMG.zip flash)
- Put this file for AT&T or this file for Rogers on a microSD card as is (it should be named PH39IMG.zip)
- Power down the phone, insert microSD and boot back into bootloader (power button + vol down)
- It should automatically find the zip file and flash the stock image (this includes recovery, system, everything stock.)
- If you returned to stock because of a bug or issue, and want to root again, make sure to go back and follow the steps PRECISELY to perm root, flash CWM, flash a ROM, flash a kernel, etc. Remember, flash ROM IMMEDIATELY after flashing the kernel
Click to expand...
Click to collapse
..........
radi0chik said:
can anyone confirm that HTC supertool works with the vivid?
Click to expand...
Click to collapse
Works great
Woohoo! Thanks all Finally rooted!
radi0chik said:
Woohoo! Thanks all Finally rooted!
Click to expand...
Click to collapse
Good deal
Sent from my HTC PH39100 using xda premium
Just a quick question, is there a way to relock the bootloader?
markjo said:
Just a quick question, is there a way to relock the bootloader?
Click to expand...
Click to collapse
Yes. That is why the guide says to keep that bin file. However, relocking the bootloader does not necessarily fix your voided warranty. If relocked, your device will not show up as "Locked", it will show up as "Relocked" to HTC.
You could add a part about flashing custom kernels like the one for the hollicakes ROM. That was even confusing to me and I've flashed numerous phones hundreds of times.
pside15 said:
You could add a part about flashing custom kernels like the one for the hollicakes ROM. That was even confusing to me and I've flashed numerous phones hundreds of times.
Click to expand...
Click to collapse
I was actually thinking about doing that earlier but got cut short in time. I'll add it though.
Sent from my HTC PH39100 using xda premium
Looks great, thanks for collecting all this stuff in one place! So happy to finally have a bootloader unlock, CWM, and permanent root!
bjg222 said:
Looks great, thanks for collecting all this stuff in one place! So happy to finally have a bootloader unlock, CWM, and permanent root!
Click to expand...
Click to collapse
Thanks man. It didn't take too long, maybe 20-30 minutes. The flashing ROM and kernel parts may be a little outdated though. I took them from old notepad files from when I had my Inspire. Oh well, it still should do the job .
So I followed your guide and was able to unlock my bootloader, and root my phone. It is hard to tell if it truly is rooted or not, but I loaded up a couple
apps that only work when rooted and SuperUser passed them through. Good stuff all around
However that WiFi tether just doesn't seem to be working for me. I turn it on, connect my MAC but then can't actually get on the internet.
I know when I had my Inspire, I would a custom ROM on and I was able to just turn on mobile hotspot in the settings area and it worked without saying I needed a plan. Is there anything like that for the Vivid? Or does someone need to make a custom ROM with that feature included.
I mainly need root, so I could get that feature, everything is perfect!
verseman said:
So I followed your guide and was able to unlock my bootloader, and root my phone. It is hard to tell if it truly is rooted or not, but I loaded up a couple
apps that only work when rooted and SuperUser passed them through. Good stuff all around
However that WiFi tether just doesn't seem to be working for me. I turn it on, connect my MAC but then can't actually get on the internet.
I know when I had my Inspire, I would a custom ROM on and I was able to just turn on mobile hotspot in the settings area and it worked without saying I needed a plan. Is there anything like that for the Vivid? Or does someone need to make a custom ROM with that feature included.
I mainly need root, so I could get that feature, everything is perfect!
Click to expand...
Click to collapse
To double check root, I use Root Checker (just search the market for Root Checker), and it'll tell you. Also, TitaniumBackup will tell you if you're rooted or not when you start it.
As for WiFi Tether, rooting by itself doesn't unlock that feature. Most custom roms make tweaks to enable it. So far, it doesn't look like anybody's found to right way to release the AT&T check that's performed when trying to turn it on, so in the stock ROM, you still won't be able to use if without the proper plan. There's been enough posts asking about it, though, that I'm sure a way will show up soon enough. I'm poking around in the system files right now to see if can find something useful.
Nice job getting all this in on place.
One question:
3) (Optional) Custom CWM Recovery
Go here and follow every step precisely
http://forum.xda-developers.com/show....php?t=1343625
This thread looks like it is for creating a CWM Recovery and root do both files need to be used and is this working on Vivid as well as Raider? (I know it should just don't want to assume)
adbfastbootrecovery.zip (this seems to be the recovery file)
VIVID_CWM_ROOT.zip (this one seems to be for rooting, is this one necessary as well to ge the recovery?)
Thanks just don't want to screw up and have to reload everything since I can't do NAND yet.
Having trouble with the HTC Super Tool. The drivers file won't launch, and when I try to run the bat file it says file path not specified... I am running windows using parallels on Mac OSX Lion. It's just weird that the driver file won't open up and run completely. I even tried running as admin.
Also, when i connect it to the computer, do i pick just charge only, htc sync, or disk drive? Or does it matter?
cyber_pete said:
Nice job getting all this in on place.
One question:
3) (Optional) Custom CWM Recovery
Go here and follow every step precisely
http://forum.xda-developers.com/show....php?t=1343625
This thread looks like it is for creating a CWM Recovery and root do both files need to be used and is this working on Vivid as well as Raider? (I know it should just don't want to assume)
adbfastbootrecovery.zip (this seems to be the recovery file)
VIVID_CWM_ROOT.zip (this one seems to be for rooting, is this one necessary as well to ge the recovery?)
Thanks just don't want to screw up and have to reload everything since I can't do NAND yet.
Click to expand...
Click to collapse
This has been reported working for.the Vivid once the bootloader is unlocked.
Sent from my HTC PH39100 using xda premium
cyber_pete said:
Nice job getting all this in on place.
One question:
3) (Optional) Custom CWM Recovery
Go here and follow every step precisely
http://forum.xda-developers.com/show....php?t=1343625
This thread looks like it is for creating a CWM Recovery and root do both files need to be used and is this working on Vivid as well as Raider? (I know it should just don't want to assume)
adbfastbootrecovery.zip (this seems to be the recovery file)
VIVID_CWM_ROOT.zip (this one seems to be for rooting, is this one necessary as well to ge the recovery?)
Thanks just don't want to screw up and have to reload everything since I can't do NAND yet.
Click to expand...
Click to collapse
There's no need to flash the VIVD_CWM_ROOT.zip if you root using the SuperTool. I used the SuperTool (options 1, then 2 - prep, then root) to get root, then flashed CWM using the fastboot command given in the linked thread. Worked like a charm. I suppose it would work just as well, however, if you unlock the bootloader, flash CWM, then flash the VIVID_CWM_ROOT.zip, bypassing the SuperTool all together.
bjg222 said:
There's no need to flash the VIVD_CWM_ROOT.zip if you root using the SuperTool. I used the SuperTool (options 1, then 2 - prep, then root) to get root, then flashed CWM using the fastboot command given in the linked thread. Worked like a charm. I suppose it would work just as well, however, if you unlock the bootloader, flash CWM, then flash the VIVID_CWM_ROOT.zip, bypassing the SuperTool all together.
Click to expand...
Click to collapse
the idea behind using the CWM rooting method is that you dont have to root using any kind of exploits. the exploits were leaving residual problems with sdcard mounting and the CWM is the much cleaner way of rooting. those residuals may not exist any more, but when i threw the CWM together, it was because of a request for it, and it didnt require an exploit.
slapshot30 said:
This has been reported working for.the Vivid once the bootloader is unlocked.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
In reality, it might be best to just do the steps involving flashing the recovery, as using the SuperTool, su & busybox are already installed. So I think all that's needed are steps 2 - 6, as the rest deal with stuff already done by the SuperTool
bjg222 said:
There's no need to flash the VIVD_CWM_ROOT.zip if you root using the SuperTool. I used the SuperTool (options 1, then 2 - prep, then root) to get root, then flashed CWM using the fastboot command given in the linked thread. Worked like a charm. I suppose it would work just as well, however, if you unlock the bootloader, flash CWM, then flash the VIVID_CWM_ROOT.zip, bypassing the SuperTool all together.
Click to expand...
Click to collapse
I'll update the post, thanks for that. Do you think doing away with the supertool would be an easier method then?
Sent from my HTC PH39100 using xda premium
Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.
limache said:
Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.
Click to expand...
Click to collapse
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium
Quis89 said:
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.
Toxicoblivion said:
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.
Click to expand...
Click to collapse
It's thought this is a safety feature so that you can't accidentally long press power and restart in dark places like your pocket.
@rider5512 Sounds right to me. Thanks for clarifying.
Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?
limache said:
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?
Click to expand...
Click to collapse
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.
crushalot said:
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.
Click to expand...
Click to collapse
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
fastboot erase cache
limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.
crushalot said:
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.
Click to expand...
Click to collapse
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".
limache said:
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".
Click to expand...
Click to collapse
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?
crushalot said:
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?
Click to expand...
Click to collapse
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.
I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium
hardstuffmuc said:
I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
limache said:
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.
Click to expand...
Click to collapse
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.
limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
crushalot said:
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.
Click to expand...
Click to collapse
Hmmm okay so the other poster's suggestion was to get an OTG cable (a micro usb to USB cable right?) and connect the USB with the ROM directly the phone. Do you think this would be a big difference or no? I just don't know if the issue is the internal storage itself or the mode of pushing the ROM.
Otherwise, I'm pretty much scratching my head and have no idea what else I could do =/.
Just for anyone else who's having issues, I've tried using TWRP's install function with the OTG cable but it still doesn't mount. Just letting people know.
if you are noob to recover your phone you can try some services like this
i revived my HTC one by them
http://goo.gl/1DMXlq
I'm very new to all this, so if this is a stupid please forgive me.
I have a z3c with Android 4.4.4, I believe last night I've unlocked the bootloader via Sony's process. Phone rebooked and reset (and did see the green android doing stuff).
I want to install TWRP and then CM12.
Firstly, I can't seem to get into the standard (if there is one) bootloader by holding the volume button down.
Also, Is there a step by step guide to installing TWRP and some way of confirming I have actually unlocked the stock bootloader?
Regards.
>R.
rowlandski said:
I'm very new to all this, so if this is a stupid please forgive me.
I have a z3c with Android 4.4.4, I believe last night I've unlocked the bootloader via Sony's process. Phone rebooked and reset (and did see the green android doing stuff).
I want to install TWRP and then CM12.
Firstly, I can't seem to get into the standard (if there is one) bootloader by holding the volume button down.
Also, Is there a step by step guide to installing TWRP and some way of confirming I have actually unlocked the stock bootloader?
Regards.
>R.
Click to expand...
Click to collapse
use this code in the same way if you go to call *#*#7378423#*#* and check it on Service info configuration you should see something like this :
1 - bootloader unlock allowed: No
2- bootloader unlock allowed : Yes
3 -bootloader unlock: Yes
But for root the phone you don´t need unlock bootloader I don´t know in your country but here you lost warranty if you open it. You just need dowgrade to kitkat using flashtool, root with one script and you should to make a copy of TA partiton with other script and install dual recovery.
You have a lot of tutorials and videos arround.
---------- Post added at 04:31 PM ---------- Previous post was at 04:17 PM ----------
pibcs81 said:
use this code in the same way if you go to call *#*#7378423#*#* and check it on Service info configuration you should see something like this :
1 - bootloader unlock allowed: No
2- bootloader unlock allowed : Yes
3 -bootloader unlock: Yes
But for root the phone you don´t need unlock bootloader I don´t know in your country but here you lost warranty if you open it. You just need dowgrade to kitkat using flashtool, root with one script and you should to make a copy of TA partiton with other script and install dual recovery.
You have a lot of tutorials and videos arround. Just search it.
http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 I did it yesterday and i follow this guide until step 26, after this i just dowload dual recovery installer use this script and i get dual recovery http://nut.xperia-files.com/ if you dont have root you must use the other script and is done. i have installed miui 7 i love miui roms but i like sony roms as well.
Good luck
Click to expand...
Click to collapse
update
pibcs81 said:
use this code in the same way if you go to call *#*#7378423#*#* and check it on Service info configuration you should see something like this :
1 - bootloader unlock allowed: No
2- bootloader unlock allowed : Yes
3 -bootloader unlock: Yes
But for root the phone you don´t need unlock bootloader I don´t know in your country but here you lost warranty if you open it. You just need dowgrade to kitkat using flashtool, root with one script and you should to make a copy of TA partiton with other script and install dual recovery.
You have a lot of tutorials and videos arround.
---------- Post added at 04:31 PM ---------- Previous post was at 04:17 PM ----------
pibcs81 said:
use this code in the same way if you go to call *#*#7378423#*#* and check it on Service info configuration you should see something like this :
1 - bootloader unlock allowed: No
2- bootloader unlock allowed : Yes
3 -bootloader unlock: Yes
But for root the phone you don´t need unlock bootloader I don´t know in your country but here you lost warranty if you open it. You just need dowgrade to kitkat using flashtool, root with one script and you should to make a copy of TA partiton with other script and install dual recovery.
You have a lot of tutorials and videos arround. Just search it.
http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 I did it yesterday and i follow this guide until step 26, after this i just dowload dual recovery installer use this script and i get dual recovery http://nut.xperia-files.com/ if you dont have root you must use the other script and is done. i have installed miui 7 i love miui roms but i like sony roms as well.
Good luck
Click to expand...
Click to collapse
Thank you for the information. I have used *#*#7378423#*#* and get:
3 -bootloader unlock: Yes
I'm now following a post (DoomLord's) and trying to install CWM.
With the phone powered up and connected to PC, I can use adb and see a connection
I have tried getting into fastboot mode using two ways:
1. From adb and reboot in fastboot
2. Hold volume-up and connect usb....
I get a BLUE LED, but when using Android platform tools, "fastboot devices", none are shown....
I'm assuming blue LED means fastboot?
Note: I've turned on anti-virus / firewall... etc.
Basically, can't connect to phone via fastboot command....
Any ideas?
Regards,
>R
Click to expand...
Click to collapse
power off phone conect usb to computer and hold down and conect to microusb.
update
pibcs81 said:
power off phone conect usb to computer and hold down and conect to microusb.
Click to expand...
Click to collapse
For some reason my windows machine didn't work but my mac did.
Managed to fastboot cwm:
&&&&&-MacBook-Prolatform-tools &&&&&&$ /Users/me/Library/Android/sdk/platform-tools/fastboot flash boot Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img
sending 'boot' (13014 KB)...
OKAY [ 0.410s]
writing 'boot'...
OKAY [ 0.867s]
finished. total time: 1.277s
&&&&&&-MacBook-Prolatform-tools me$ /Users/me/Library/Android/sdk/platform-tools/fastboot reboot
rebooting...
finished. total time: 0.002s
After reboot - NEW PROBLEM:
Trying to switch on wifi, the switch moves across and turns light blue (and shaded out).... and no wifi.
Have i broken it?
>R
Men try basics, wipe cache davlink, if doesn't work you should try factory reset. If doesn't work you should try other Rom now you have recovery try any rom.
pibcs81 said:
Men try basics, wipe cache davlink, if doesn't work you should try factory reset. If doesn't work you should try other Rom now you have recovery try any rom.
Click to expand...
Click to collapse
Thanks for your reply.
I've tried:
Clearing clearing the Dalvik Cache.
Factor reset
> Still the same; no wifi (light blue and shaded out)
I then:
Flashed Sony 4.4.4 stock ROM (D5803_23.0.1.A.5.77_RU.ftf)
> Got phone working again.
Then fastboot loaded CWM as per:
http://forum.xda-developers.com/z3-...58xx-cwm-based-recovery-6-0-4-7-root-t2890231
And again have the same issue, wifi will not turn on and is blue / shaded out.
Any ideas?
Is it worth trying TWRP? If so, is there a version for z3c?
Regards,
Rowland
Try with Dual Recovery (CWM / TWRP)
You can find it here in XDA previous posts
CM12....
Hucast_DL said:
Try with Dual Recovery (CWM / TWRP)
You can find it here in XDA previous posts
Click to expand...
Click to collapse
I had to move to CM12 (nightly), which was ok but now has CM recovery....
I'm going round in circles.
I just want, if possible, the file (TWRP) and instructions to install on my z3c with CM12...
Regards,
R.
rowlandski said:
I had to move to CM12 (nightly), which was ok but now has CM recovery....
I'm going round in circles.
I just want, if possible, the file (TWRP) and instructions to install on my z3c with CM12...
Regards,
R.
Click to expand...
Click to collapse
You can use this app for flash TWRP, i read this works in many people
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I'm running the Android SDK on linux (Ubuntu). My stock H81110n G4 is connected via USB cable and it is listed properly when I run `adb devices`. However, the command `adb reboot bootloader` simply reboots the phone into Android.
I can't boot into the bootloader. What is the solution for this?
Of course, I have USB Debugging enabled. I also checked OEM Unlock just to see if that helped. It didn't. My phone is not bootloader unlocked yet. I plan to do that next, but first I want to be reboot into the bootloader (e.g., to get the device ID for the LGE Developer site).
Thanks for any assistance.
You don't need to use the LGE developer site to unlock your bootloader. From what I understand, as soon as you tick the OEM unlock then you are unlocked. The LG site is for 815 only.
hyperfriend said:
You don't need to use the LGE developer site to unlock your bootloader. From what I understand, as soon as you tick the OEM unlock then you are unlocked. The LG site is for 815 only.
Click to expand...
Click to collapse
Thanks for that info. However, that's not really my question. My question is why `adb reboot bootloader` causes the phone to boot into Android instead of into the bootloader. That's my real issue.
`adb reboot download` doesn't work either. It simply reboots into Android. Therefore, I'm not able to install TWRP or do anything else I want to do.
Also, using the phone's power and vol-down buttons will not boot it into the bootloader, so something seems strange with this phone. I haven't run into this issue on other phones. I rooted an HTC One M9 today. But I can't get past this step with the LG G4.
MountainX said:
Thanks for that info. However, that's not really my question. My question is why `adb reboot bootloader` causes the phone to boot into Android instead of into the bootloader. That's my real issue.
`adb reboot download` doesn't work either. It simply reboots into Android. Therefore, I'm not able to install TWRP or do anything else I want to do.
Also, using the phone's power and vol-down buttons will not boot it into the bootloader, so something seems strange with this phone. I haven't run into this issue on other phones. I rooted an HTC One M9 today. But I can't get past this step with the LG G4.
Click to expand...
Click to collapse
That is strange, but I don't see why you need to reboot to the bootloader if it's already unlocked. Try to flash TWRP and see what happens.
hyperfriend said:
That is strange, but I don't see why you need to reboot to the bootloader if it's already unlocked. Try to flash TWRP and see what happens.
Click to expand...
Click to collapse
Like I mentioned in the OP, my H81110n LG G4 is stock. It is not rooted. As far as I know, flashing TWRP requires booting into recovery / download mode first. Here's how I usually do it:
In a linux terminal:
Code:
/opt/android-sdk-linux/platform-tools# ./adb devices
/opt/android-sdk-linux/platform-tools# ./adb reboot download
/opt/android-sdk-linux/platform-tools# ./fastboot flash recovery recovery.img
This phone will not boot into download (or bootloader). All it does is reboot into Android OS. Any ideas?
Bump.
I'm having this same issue. Hardware keys and proper adb commands to get to bootloader are ineffective. Suggestions??
---------- Post added at 02:33 AM ---------- Previous post was at 02:25 AM ----------
MattKilla said:
Bump.
I'm having this same issue. Hardware keys and proper adb commands to get to bootloader are ineffective. Suggestions??
Click to expand...
Click to collapse
ACTUALLY-- solved.
Hold Vol-Up and plug into the PC. Do not press power. Holing Vol-Up and inserting the USB cable will trigger "download mode". Bootloader.
Booting into download mode is Vol UP + Plug in USB (While the phone is off)
You can then use the low effort root if on firmware H or Rhyda's thread in the dev section for firmware N to get root.
I can't get into the bootloader either, I think T-Mobile did something. After rooting you can download a terminal emulating app and just run the command:
>su
(grant SU permissions)
>reboot bootloader
Have you tried flashing TWRP using Flashify? I think that how I installed it on my H811 (should've taken notes >.< )
I don't know of any way to access the bootloader either. Typing "su" and "reboot bootloader" in the terminal doesn't work, nor does using an app like ROM Toolbox.
I posted this in another thread. This was the only way I could workaround this problem.
Many ADB bootloader commands do not work on this model. Nor do I think they work on any G4. Not sure why LG went this route, whereas on the V10 (some models at least) it's as easy as a Nexus.
I forgot, how do you reboot into fastboot again?
After seeing people not being able to root their S3 and rooting mine successfully, I have decided to make this tutorial to help those out there. This tutorial covers the procedures I took to successfully root my LeEco S3 US edition with EUI 5.8.018S and Snapdragon 652 processor. My phone is permantly rooted and has permanent TWRP recovery.
Make sure your phone has developer options and has usb debugging as well as the option to unlock the bootloader enabled
First off, download the AIO Toolkit created by Rishabh Rao here
Secondly, open the toolkit. Make sure to turn off your antivirus to avoid any interruptions. Once in the toolkit, select item 6 and allow the program to download necessary files. After the files have downloaded, select item 1 to install ADB/Fastboot USB drivers. During this process, PDA Net will prompt you to connect your phone to the computer. It will download the client onto your computer and install the PDA Net application onto your phone. When the drivers are fully installed, close the toolkit.
Open command prompt and run ADB. With your phone plugged in and in recovery mode, type fastboot oem unlock-go and you should see it attempting to unlock the bootloader. If you get a successful message of unlocking your bootloader, you are ready to move on to the next step as this is a temporary unlock. Close the command prompt.
Open the toolkit again, select item 6 and then select item 3 to unlock bootloader completely. When it has finished, go back to select item 4 to check and see if the bootloader has been unlocked. If so, move on to selecting item 5 to flash the latest TWRP recovery.
When the TWRP recovery has installed, if it has not booted into recovery by itself, hold down power + volume up to enter it. You will see the recovery all in the chinese language. Simply swipe the unlock to proceed and from the menu, select the box to the right and three down (which is settings). There, select the globe icon and scroll down to select the english language. Now that you can read what is there, go back to the main menu and select wipe to completely wipe the phone back to factory defaults. When it has finished, go back and select Advanced > Tools > Root Device. Your phone will now be rooted when you reboot and will have the latest TWRP recovery installed.
- If you receive the error message saying the device is locked while you are trying to unlock the bootloader from the toolkit, you need to run ADB again to temporary unlock the bootloader.
Quick question - will this only work on 18s and is it possible to update the firmware and keep root after doing this? Or would it work after updating to I think 21s which is the latest?
Thank you!
Hi
Can you break this down further with pictures too? How do I do the command prompt ABD thing?
Root
was this the easiest way? I'm going to try it in two days. Scared to mess my phone up though..
This method does not work on the 23s ROM. Does nothing
What's the best way? Simple way I mean?
Worked for anyone?
these instructions are for the le s3 with SNAPDRAGON processor, not for the MEDIATEK x20 that is where we have the problem
Just got this phone and gonna try this out, thanks ;p
---------- Post added at 11:06 AM ---------- Previous post was at 10:13 AM ----------
Actually Ima wait...I've never rooted using TWRP Recovery so not quite familiar with it after the phone's been rooted. I've only used a couple of the one-click root apps, KingRoot and KingoRoot, for a couple phones.
Rooted it fine, now I need to figure out what I can do ;P <--- noob
How were you able to successfully root the phone?
GWARslave119 said:
Rooted it fine, now I need to figure out what I can do ;P <--- noob
Click to expand...
Click to collapse
How were you able to successfully root the phone?
i dont know what to do,, it says "waiting for device" what should i do ? i already installed the 15 sec ADB something like that.. i need your help plsssss
Rooting Le S3.
XtraTerr3sTRiAL said:
After seeing people not being able to root their S3 and rooting mine successfully, I have decided to make this tutorial to help those out there. This tutorial covers the procedures I took to successfully root my LeEco S3 US edition with EUI 5.8.018S and Snapdragon 652 processor. My phone is permantly rooted and has permanent TWRP recovery.
Make sure your phone has developer options and has usb debugging as well as the option to unlock the bootloader enabled
First off, download the AIO Toolkit created by Rishabh Rao here
Secondly, open the toolkit. Make sure to turn off your antivirus to avoid any interruptions. Once in the toolkit, select item 6 and allow the program to download necessary files. After the files have downloaded, select item 1 to install ADB/Fastboot USB drivers. During this process, PDA Net will prompt you to connect your phone to the computer. It will download the client onto your computer and install the PDA Net application onto your phone. When the drivers are fully installed, close the toolkit.
Open command prompt and run ADB. With your phone plugged in and in recovery mode, type fastboot oem unlock-go and you should see it attempting to unlock the bootloader. If you get a successful message of unlocking your bootloader, you are ready to move on to the next step as this is a temporary unlock. Close the command prompt.
Open the toolkit again, select item 6 and then select item 3 to unlock bootloader completely. When it has finished, go back to select item 4 to check and see if the bootloader has been unlocked. If so, move on to selecting item 5 to flash the latest TWRP recovery.
When the TWRP recovery has installed, if it has not booted into recovery by itself, hold down power + volume up to enter it. You will see the recovery all in the chinese language. Simply swipe the unlock to proceed and from the menu, select the box to the right and three down (which is settings). There, select the globe icon and scroll down to select the english language. Now that you can read what is there, go back to the main menu and select wipe to completely wipe the phone back to factory defaults. When it has finished, go back and select Advanced > Tools > Root Device. Your phone will now be rooted when you reboot and will have the latest TWRP recovery installed.
- If you receive the error message saying the device is locked while you are trying to unlock the bootloader from the toolkit, you need to run ADB again to temporary unlock the bootloader.
Click to expand...
Click to collapse
Hi Everyone. I recently got a new le s3 x522. Its great only that sim 2 slot doesn't connect to mobile data. I have tried rooting so that I can use build prop editor to fix this, but rooting has become a real problem. I used Kingo root, framaroot but not successful. I have downloaded AIO toolkit on pc but installng is a problem. Please guide me on how to install AOI toolkit on pc. I pretty new to this things you know. Any help will be greatly appreciated.