Related
Dear Memeber
i find that my htc legend is un rooted and i need to root it to install a room to it i try many ways i find other the internet and it doesn't success to do it so am look for how and the way to root it
and will be thankful for you
-Unlock the boot loader using HTCDev
-Use HTCSuperTools v3 to gain root access
-Flash ClockworkMod Recovery
-Flash any ROM you want.
These are the basic steps. I might write up an updated, more detailed guide for others when I get back to a computer.
Sent from my Legend using XDA
Go to http://www.htcdev.com/bootloader/
Register, select your device and unlock the bootloader
Get HTC Super Tools from
http://forum.xda-developers.com/showthread.php?t=1343114
Run it, do options 1 and 3, in that order, to root your phone
Get Clockwork Recovery Mod from
http://forum.xda-developers.com/showthread.php?t=1290841
Use 1st step for S-OFF method to install ClockworkRecovery
Boot into Recovery mode and take a backup of your ROM
Download the ROM of your choice and copy it to your SD card
Boot into Recovery Mode, do a data wipe/factory reset and a cache wipe
Select Install from zip in Recovery, navigate to your ROM in SD Card and install it. Hope this helps.
This is a long process, at least for the first timers. You may get stuck at various places, please let us know if you do
Unlock the boot loader using HTCDev
-Use HTCSuperTools v3 to gain root access
i download this two items and i try to root it but it dosen't work with me or maybe i did something wrong
what is the steps that i have to follow by using them
and thanks for your replies
Regards
sometimes it says like this
C:\Android>fastboot oem get_identifier_token
< waiting for device >
...
and it stuck for along time and nothing changed
and other times when i press power button for the fastboot it change to be like this
(bootloader) [ERR] Command error !!!
OKAY [ 0.008s]
finished. total time: 0.008s
C:\Android>fastboot oem get_identifier_token
...
FAILED (status read failed (Too many links))
finished. total time: 4.670s
All I can think of is that you should start again reading every step carefully.
Also, jc36 that's a great guide
Sent from my Legend using XDA
clarify jc36 clockwork recovery mod step
I need to clarify something important for the "Get Clockwork Recovery Mod step which says to follow the 1st step for S-OFF method to install ClockworkRecovery.
On the linked page http://forum.xda-developers.com/show....php?t=1290841
Where it says the following:
"How to use S-OFF user
Download file and move on adb fastboot folder"
Does "move on adb fastboot folder" mean, put the file into the folder? And if so where is the folder?
There is no such folder: "adb fastboot folder"?
Does it mean:
1. put it in the Android folder created (C:\android) to hold the files instructed by HTC Dev for unlocking the bootloader?
2. Or put it in the android-sdk folder, somewhere? May be the Platform Tools folder where adb.exe exists?
Thanks to anyone who can help clarify this step for me
Yes it means put the recovery into the folder with adb.exe and fastboot.exe
Sent from my Legend using XDA
Thanks again
Thanks for clarifying that. As you can imagine I am a noob. It would be awesome if the brief procedure by jc36 could be expanded upon into an exact step-by-step (hand-holding) for all the noobs out there. Jumping back and forth between the forum links can get confusing -- especially some of the posts are old... leaving one wonder if the instructions are outdated etc!
May be I will do it if I get through this safely....
xdadufus said:
Thanks for clarifying that. As you can imagine I am a noob. It would be awesome if the brief procedure by jc36 could be expanded upon into an exact step-by-step (hand-holding) for all the noobs out there. Jumping back and forth between the forum links can get confusing -- especially some of the posts are old... leaving one wonder if the instructions are outdated etc!
May be I will do it if I get through this safely....
Click to expand...
Click to collapse
Brief is good although I do understand how a noob would want a step-by-step guide. In relation to date, none of the links I gave you were really outdated. The datestamp at the top of the thread might say '6th October 2011, 10:00 AM' but if you look at the bottom of the post it'll say something like 'Last edited by (username); 21st March 2012 at 09:32 AM' on threads/posts that get updated. Welcome to the Legend forums!
Further Clarification
I am continuing with my quest to clarify and document the whole jc36 procedure accurately.
1. After you have unlocked the bootloader are there any mode changes to be made before running SuperTools?
2. After running SuperTools, following the 1st step for S-OFF Clockwork Recovery Mod how do you put the phone into "fastboot" mode? Does the phone have to be disconnected again, powered down, restart with volume held down, highlighting Fastboot then press Power button and reconnecting to computer? Is this the procedure or is there another way while it still connected to the computer?
3. Continueing with Clockwork Recovery Mod code where it says:
"In fastboot mode:
Code:
adb reboot bootloader
fastboot flash recovery recovery_legend_5.0.2.8.img"
I'm guessing the code above is for command prompt for the c:\android directory as done previously for HTC Dev unlocking of the bootloader?
Open up command prompt. ( Start> Run> Type CMD,).
Command Prompt: cd c:\Android)
Type in Command Prompt:
adb reboot bootloader
fastboot flash recovery recovery_legend_5.0.2.8.img
Correct?
4. After completing Clockwork recovery Mod it says to "Boot into Recovery mode and take a backup of your ROM" -- again do you disconnect the phone to do this and boot into the bootloader to select Recovery mode? And how to you backup? Is it to an SD card or is the phone connected to the computer to take the backup to your hardrive?
Thank you to all in advance who take the time to go over these questions.
1. By mode changes I'm assuming you mean something like enabling USB debugging which is definitely recommended.
2.You get into fastboot mode by rebooting into the bootloader (Hold volume down+trackball+power button). Fastboot is the first selected option so all you have to do is press the power button to choose it and then it will go into fastboot mode
3.Yes in command prompt you navigate to the folder that has adb.exe, fastboot.exe and the recovery image and then carry out those commands
4.If you've flashed a ROM that supports it then in phone options(hold down power button) you can select Reboot and then Recovery. Otherwise to get to recovery you would have to go through the bootloader. To backup you go to Backup and Restore in CWM and select Backup or alternatively you can use ROM Manager to do a backup. The phone doesn't have to be disconnected and the backups are made to the micro SD Card.
Sent from my Legend using XDA
run in to trouble at the beginning
I have run into an error with the command provided with HTC Dev Unlock Bootloader.
I have followed all instructions very carefully. When in command prompt I get this error after entering:
fastboot oem get_identifier_token
...
<bootloader> [ERR] Command error !!!
I am in the android directory in c:\android and have the three files there:
adb.exe
adbWinApi.dll
fastboot (which I extracted from an older version of SDK as instructed by HTC because it doesn't exist in the latest SDK software)
Is your phone connected with USB Debugging on and HTC drivers installed on your computer?
bootloader now unlocked successfully
I just flashed the RUU that HTC Dev recommended for my phone, the version it should have before attempting to unlock the bootloader.
My phone originally had this updated version anyway so I never updated it on my first attempt.
After reading the forums here for people having similar issues I flashed their recommended RUU for the Legend and from that point on the command in command prompt worked. I have now unlocked the bootloader ...
what about gapps?
I finally rooted my phone and flashed cm7.2 ROM successfully after some nail biting experiences... it is not as simple as the instructions posted earlier in this forum make it appear... There were some issues I ran into. I will post an explanation of how I resolved them soon.
What good is a new android ROM without essential Google apps? I know they are not packaged due to licensing but I can not find a reasonable explanation of how to get them on my phone. I thought it would be simple but it is not. Right now I can not download any apps...
I read the gapps packages should be installed during the flashing of the ROM... that point is missing from the instructions here! So what now? Do I have to run through the process of flashing the ROM again along with the gapps package this time?
I tried installing the latest Google Play app but it would not connect to the server -- whatever that means -- after entering in my google account.
Is there any way to get the apps downloaded directly to my computer so I can copy them to the SD card? I did find a couple of solutions to do this but you need to enter google account details and some id number for the phone which I can not find... what is the identifier for the phone and where?
Any assistance on this would be greatly appreciated because at this point the whole new fresh ROM is useless...
You can flash GApps at any time. Whether it's during installation, right after first boot, or years later. Make sure you flash the appropriate .zip.
You can use APK Downloader to get them straight from the Play Store to your computer in .APK format.
http://codekiem.com/2012/02/24/apk-downloader/
All the latest Gapps packages can be found here. Use the 'gapps-gb-20110828-signed.zip' package if you're running Gingerbread and 'gapps-ics-20120429-signed.zip' if you're running ICS.
I need a bit more help please!
I have had the legend for ages and wanted to breath new life into it. I am using a ssensation as my everyday phone and that was a doddle to root compared to this!
I have gotten as far as flashing recovery. I dl'd the S-OFF .img from here and placed it in my adb folder. I tried running the adb command and only got as far as
"fastboot flash recovery" when
"error: neither -p product specified or ANDROID_PRODUCT_OUT set" shows up.
Any help? the HTCdev and Supertools seemed to go flawlessly for me. My HBOOT was 1.01 and HTCdev changed it to 1.02. It also now has *** LOCKED (OOW) *** at the top. I'm still S-ON too. What's going wrong? There is no su app in the app drawer like there was when I rooted my sensation. do I have to start over? any help would be great!
icanttinkofaname said:
I need a bit more help please!
I have had the legend for ages and wanted to breath new life into it. I am using a ssensation as my everyday phone and that was a doddle to root compared to this!
I have gotten as far as flashing recovery. I dl'd the S-OFF .img from here and placed it in my adb folder. I tried running the adb command and only got as far as
"fastboot flash recovery" when
"error: neither -p product specified or ANDROID_PRODUCT_OUT set" shows up.
Any help? the HTCdev and Supertools seemed to go flawlessly for me. My HBOOT was 1.01 and HTCdev changed it to 1.02. It also now has *** LOCKED (OOW) *** at the top. I'm still S-ON too. What's going wrong? There is no su app in the app drawer like there was when I rooted my sensation. do I have to start over? any help would be great!
Click to expand...
Click to collapse
You do see the words "locked"? that means its "locked" you need to follow the steps provided by htcdev in the email they would have sent you including the unlock.bin file with out those steps you can't do anything, its like its still not rooted.
Sent from my Legend using XDA
This is long, but it's nice for noobs because it's detailed. It's honestly kind of fun, I promise. I'm assuming you have WINDOWS. This is based off of the guide by torxx!. It's modified because some of the info is outdated (you don't have to flash the boot.mg separately, for example). If you are NOT a noob you can just look at the "overview" for each step.
UNLOCKING YOUR DEVICE WILL WIPE YOUR DEVICE. THIS IS A SECURITY FEATURE. BACKUP FIRST.
Part 1- gaining unlock token
Overview: go to htcdev.com and unlock bootloader
Be sure you've turned off fast boot option in power menu; usb debugging should be on (settings -> developer options).
Go to http://www.htc.com/www/software/htc-sync-manager/[1] and install HTC SYNC. Alternatively, if you know what you're doing, you can install these drivers:
x86 http://www.mediafire.com/?qabo1tue2v1ky75 x64 http://www.mediafire.com/?8dl8s3l9mr6ggr9
Go on http://www.htcdev.com[4] and create yourself an account on HTCDEV.
Download these adb/fastboot files: http://d-h.st/RvD
Make a new folder anywhere. We'll use C:/fastboot as an example.
Extract the zip downloaded to the new folder
Go Here http://www.htcdev.com/bootloader/[6] and select "All Other Supported Models" and "then begin unlock bootloader" (check the boxes, click proceed, all that good stuff). YOU CAN IGNORE THE DIRECTIONS THAT THEY TELL YOU (and follow this guide instead).
Power off your phone. Power your phone on by holding power and volume down.
Highlight 'Fastboot' the volume buttons then press power to "select".
Plug your phone into your PC and open a Command Prompt. (windows XP - Click Start > Run > type CMD in box then press OK; Windows 7 - Click Start > type CMD in search box then press Enter) Change directory to your folder where we put fastboot files by typing cd c:\fastboot for example.*
*Alternatively, you can just hold down shift and right click in the folder and select "open command window here". Neat huh?
Type this into your command prompt window: fastboot oem get_identifier_token
Select & copy the text as per step 9 on the HTCDev website
Paste your identifier token into the box at the bottom and submit
You Will Very Shortly Receive an email from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached
Download the "Unlock_code.bin" from the email and save it to the same folder that we extracted fastboot files
Type this into your command prompt window: fastboot flash unlocktoken Unlock_code.bin
The Display Will change on your phone, press Vol+ to accept and power to confirm.
Part 2
Overview: flash your recovery. Boot into recovery. Turn phone off if it boots into OS. Boot into back into recovery. You're done!
Download a recovery:
TWRP (the one I use): http://forum.xda-developers.com/showthread.php?t=2173870
CWM 2: http://forum.xda-developers.com/showthread.php?t=2172979
CWM: http://forum.xda-developers.com/showthread.php?t=2173863
Place the Recovery file to the folder where the fastboot.exe is.
Same thing as above- boot (volume down + power) into the bootloader and highlight 'Fastboot' the volume buttons then press power to "select".
Do the same thing as with the command prompt above. This time, however, you'll be typing:
fastboot flash recovery "name_of_the_recovery.img"
For example:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
then type:
fastboot erase cache
From the menu, boot into recovery (use volume to move up and down, power to select). The phone might boot to the OS instead of recovery, don't worry!
Turn off phone then turn on (while holding volume down) to boot back into the bootloader.
TAMPERED shows up, boot into recovery and now your recovery should be working!
Part 3- obtaining root
Overview: flash a super tool
Download a super user tool for root:
SuperSU (I use this one): http://forum.xda-developers.com/showthread.php?t=1538053
SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Alternatively, download this: http://forum.xda-developers.com/showthread.php?t=2252959. This is a stock rooted rom for ATT. If you download and flash this instead of the super user tool, you're done. (This rom includes super user) Or you can download a custom rom such as this one: http://forum.xda-developers.com/showthread.php?t=2183023
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip super user tool to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead.
I recommend these kernels: http://forum.xda-developers.com/showthread.php?t=2255900 or http://forum.xda-developers.com/showthread.php?t=2233665&highlight=menu
Download it.
Installing custom rom/kernel ("flashing a rom")
Overview: Download Rom, boot into recovery and wipe and then flash.
According to Shenye, even though your device is s-on, you can still flash boot now. So just do this:
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip kernel/cutom rom to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
I feel like this title should be changed to clarify that it's unlocking the bootloader, not the SIM lock.
Just wanted to say this tutorial was 100% dead on and what I used to unlock bootloader and root/rom my One.
Oddity - Did everything, I've got root but I -AM- out of the woods. Was installing bulletproof mod through recovery but it kept failing due to missing a MD5 file or something -- Trying to work that out through that thread atm but anyway, rebooted the phone a couple of times now and I still have root, Tit back up works OR are we talking about things like CPU clocking won't work since it can't rewrite?
Sticking this.
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Does anyone know if this will work on the Rogers HTC One?
Thank you. Followed this last night. Worked flawlessly. The only thing that threw me was rebooting into recovery. It took maybe 3 or 4 reboots for it to say "TAMPERED" at the top. When it didn't say tampered, it would not boot to recovery.
TELUS?
DannySmurf said:
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Click to expand...
Click to collapse
Did you happen do run this tutorial on a TELUS device?
Viceroy_N said:
Does anyone know if this will work on the Rogers HTC One?
Click to expand...
Click to collapse
Yes it does. I have a Rogers phone, and it worked perfectly.
richnanaimo said:
Did you happen do run this tutorial on a TELUS device?
Click to expand...
Click to collapse
No, I have a Rogers device. But the procedure should not be any different.
followed step by step and got an error that says submitted token wrong length
I'm on ubuntu 13.04 and I get stuck at getting the token. I type in fastboot oem get unlock_identifier_token and it says waiting for device. Tried it with sudo and it says error and sudo ./fastboot and it says no such command.
Sent from my HTC One using xda app-developers app
Having a really odd problem. I flash the twrp recovery per instructions. I try to reboot to recovery and it seems to try and then, blam, the att boot.
I have tried this from the bootloader, selecting Recovery, as well as from a booted stated using "adb reboot recovery".
Any hints for me? I originally had a silver One and today got my Black One replacement,. Had no issues on the original one. Hmm. Guess I will try CWM.
FYI: Yes I unlocked the bootloader and it says Unlocked in there
-I also notice that I seem to go right into fastboot, when I boot the bootloader. Now, I believe that is normal if you have the usb cable attached, but this happens regardless.
-flashed stock recovery back and can get into it. trying twrp again, renaming the file to "recovery.img" just because...and it worked on that stock recovery file
-Also, very hard to get into bootloader from powered off state. I may flash RUU_M7_UL_JB_50_Cingular and see if it helps me.
OK, maybe it is the phone or ATT has done something screwy on the latest. I can not even get the RUU install to pass inspection. Wants me to check the connection. I know all my stuff is in order, as I did this all on the previous one. grrr
-Just noticed mine does say Unlocked but it does not say Tampered.
-Crazy. I decided to get a new Unlock token and redo the unlock with it. Now, the bootloader finally says Tampered and I got into TWRP. I have no idea why, since I would think that if the original Unlock token was incorrect, it would not have unlocked the phone.
So, rather than providing worthwhile information for anyone else having problems, I think this post is probably deletable and that is fine by me should the powers so decide.
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
tacotino said:
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
fastboot oem lock
but, it will say relocked. nobody cares or seems to check. also, it will say tampered until you restore a stock ruu to flash. I used RUU_M7_UL_JB_50_Cingular.exe for mine when switching from silver to black. it is the right one for att. sorry, don't have the link to the download anymore.
great writeup! quick comment though, just helped my brother unlock his phone. i had a similar issue to @Barsky above so I decided to try to reflash the recovery. The first time I used the line fastboot erase cache after flashing the recovery and I think that's what caused it to not boot into recovery. The second time I flashed TWRP, I didn't enter that line and voila it worked on the first try!
can anyone post a mirror of the dev host files? devhost seems to be down.
nice...
help please
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
mbroch89 said:
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
Click to expand...
Click to collapse
I think the last bit was your problem. You can't factory reset from bootloader. Try to push twrp again in fastboot then load/flash clean romantic, then boot up. It already has root so you don't need to push su.
Sent from my HTC One X using xda app-developers app
So I recently had my phone temporarily rooted via weaksauce, however, after updating to Sense 6 with the Verizon OTA update, weaksauce will not root properly and it continues to fail. Is there no way to fix this or am I missing something with the OTA update? I sort of need to use weaksauce because I am not confident in my rooting ability to be able to restore the phone to factory when I turn it in for an upgrade in a few months.
none
I would start over. The posts on how to root are very good. There are also youtube videos you can watch. It really is very easy to root this device. if nothing else load a program called team viewer on your computer and I will root it for you, but I want you to try first. You will use something called rumrunner. PM me if you need help
AlphaMons said:
So I recently had my phone temporarily rooted via weaksauce, however, after updating to Sense 6 with the Verizon OTA update, weaksauce will not root properly and it continues to fail. Is there no way to fix this or am I missing something with the OTA update? I sort of need to use weaksauce because I am not confident in my rooting ability to be able to restore the phone to factory when I turn it in for an upgrade in a few months.
Click to expand...
Click to collapse
I would second that. If you are going to root a phone for the first time this is the one to start with. It is extremely well documented and this is a very helpful forum. I had the same feelings when I started (HTC Wildfire) back in the day and I did about everything wrong but in the end figured it out. Now there a several helpful threads and videos as stated above. I would recommend that you do a dry run, have everything together and go through the steps one by one in your mind or on paper before doing the actual root. You may miss something but your odds are better. Trust yourself I thoroughly believe any can root this phone and it's easier than you think and the value besides learning of the great ROMs that are here etc. is well worth it. Even if you temp root it you are going to have to know what to do to get it back before you turn it in so the knowledge will be necessary.
Are you on hboot 2.49
statmonkey said:
I would second that. If you are going to root a phone for the first time this is the one to start with. It is extremely well documented and this is a very helpful forum. I had the same feelings when I started (HTC Wildfire) back in the day and I did about everything wrong but in the end figured it out. Now there a several helpful threads and videos as stated above. I would recommend that you do a dry run, have everything together and go through the steps one by one in your mind or on paper before doing the actual root. You may miss something but your odds are better. Trust yourself I thoroughly believe any can root this phone and it's easier than you think and the value besides learning of the great ROMs that are here etc. is well worth it. Even if you temp root it you are going to have to know what to do to get it back before you turn it in so the knowledge will be necessary.
Click to expand...
Click to collapse
rumrunner will not work if he's on the ota update of sense 6, he will have to flash a custom recovery, do a nandroid backup, flash vipermax rom, and run firewater.
as to the OP, it's very easy to do, follow the guides for setting up SDK/ADB, download the appropriate custom recovery for your device (i personally like TWRP the best), place that file in your adb folder that you made from the SDK/ADB guide, unlock your bootloader if not already (i did mine via HTCdev, they have a guide). then boot into the bootloader via power+vol down, scroll with volume keys, and select with power button, go to fastboot, plug in your usb cable to your computer, if you have the drivers it will change on your device "fastboot usb". then open up a command prompt in your SDK/ADB folder (do this by shift+right click in the folder and select open command prompt here). in your command prompt type in "adb devices" to make sure your drivers are right and it see's your device. now type in "fastboot oem rebootRUU", your phone will go to a black screen that says HTC on it. now type in "fastboot flash recovery "put the name of the recovery file here".img", then after that completes without any errors, type "fastboot reboot-bootloader" press the power button with bootloader selected, scroll to recovery and press power button, once you're in recovery, do a nand backup of your stock rom, after you've done that while still in recovery, i would strongly suggest saving this backup file to your computer, you can do this in ADB by typing in "adb pull /sdcard/TWRP" and it will pull the entire directory with your backup in it.
to gain s-off and fullroot, download vipermax rom for your device, while in recovery still, you can put the rom zip file in your ADB folder, and in ADB type "adb push "Name of the zip file" /sdcard" and it will copy and paste the rom zip to your sd card, once you see it finish in the command prompt, click on install on your phone, scroll to the zip file and click on it.
when the phone boots up, make sure you connect to wifi and go through the setup, once that is done download the Firewater file, and follow the instructions. and you should get s-off, now in adb type "adb reboot recovery" and then click on restore, and restore your stock rom, now you're stock rooted, with s-off.
set up ADB guide/download here http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=226534558
TWRP guid/download here http://forum.xda-developers.com/showthread.php?t=2498746
Vipermax rom download here http://forum.xda-developers.com/showthread.php?t=2596938
Firewater guide/downloade here http://firewater-soff.com/instructions/
And i think that should be it, if after you do this and want to flash back stock recovery it's pretty simple, find and download the recovery image for the version of rom, you're using, for instance, your ota update should or will probably be in your downloads folder, if you open it with zip, (i use winrar) you will find a zip in it named "Firmware.zip" open it up, and you will see a file named recovery, extract it to your ADB Folder, boot into the "Fastboot oem rebootRUU", then simply type "fastboot flash recovery recovery.img" let that finish, then type "fastboot reboot" and it will start your phone, and now you'll have the stock recovery and be able to receive and install future OTA updates, if there is any. >.<
mrkrowely said:
rumrunner will not work if he's on the ota update of sense 6, he will have to flash a custom recovery, do a nandroid backup, flash vipermax rom, and run firewater.
as to the OP, it's very easy to do, follow the guides for setting up SDK/ADB, download the appropriate custom recovery for your device (i personally like TWRP the best), place that file in your adb folder that you made from the SDK/ADB guide, unlock your bootloader if not already (i did mine via HTCdev, they have a guide). then boot into the bootloader via power+vol down, scroll with volume keys, and select with power button, go to fastboot, plug in your usb cable to your computer, if you have the drivers it will change on your device "fastboot usb". then open up a command prompt in your SDK/ADB folder (do this by shift+right click in the folder and select open command prompt here). in your command prompt type in "adb devices" to make sure your drivers are right and it see's your device. now type in "fastboot oem rebootRUU", your phone will go to a black screen that says HTC on it. now type in "fastboot flash recovery "put the name of the recovery file here".img", then after that completes without any errors, type "fastboot reboot-bootloader" press the power button with bootloader selected, scroll to recovery and press power button, once you're in recovery, do a nand backup of your stock rom, after you've done that while still in recovery, i would strongly suggest saving this backup file to your computer, you can do this in ADB by typing in "adb pull /sdcard/TWRP" and it will pull the entire directory with your backup in it.
to gain s-off and fullroot, download vipermax rom for your device, while in recovery still, you can put the rom zip file in your ADB folder, and in ADB type "adb push "Name of the zip file" /sdcard" and it will copy and paste the rom zip to your sd card, once you see it finish in the command prompt, click on install on your phone, scroll to the zip file and click on it.
when the phone boots up, make sure you connect to wifi and go through the setup, once that is done download the Firewater file, and follow the instructions. and you should get s-off, now in adb type "adb reboot recovery" and then click on restore, and restore your stock rom, now you're stock rooted, with s-off.
set up ADB guide/download here http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=226534558
TWRP guid/download here http://forum.xda-developers.com/showthread.php?t=2498746
Vipermax rom download here http://forum.xda-developers.com/showthread.php?t=2596938
Firewater guide/downloade here http://firewater-soff.com/instructions/
And i think that should be it, if after you do this and want to flash back stock recovery it's pretty simple, find and download the recovery image for the version of rom, you're using, for instance, your ota update should or will probably be in your downloads folder, if you open it with zip, (i use winrar) you will find a zip in it named "Firmware.zip" open it up, and you will see a file named recovery, extract it to your ADB Folder, boot into the "Fastboot oem rebootRUU", then simply type "fastboot flash recovery recovery.img" let that finish, then type "fastboot reboot" and it will start your phone, and now you'll have the stock recovery and be able to receive and install future OTA updates, if there is any. >.<
Click to expand...
Click to collapse
Really an excellent post it's nice to have all that in one place. I also was unable to get rumrunner to work and have used firewater quite successfully (which was part of what I was trying to point out above). Also, I was unable to get HTCdev to unlock my phone. That may or may not be about me. I am a Linux person and I think I might have had the wrong adb/fastboot at the time. The one in the android sdk did not work for me but for anyone on LInux who is interested the one in this link did http://forum.xda-developers.com/htc-one-max/help/andrenaline-rom-constant-reboot-t2853591
Once again, excellent summary, I will be bookmarking this for later.
I think all of the above info is great and everyone trying to help is awesome. However I really liked having a soft root via weaksauce for a very limited amount of apps like titanium backup and root explorer. So am I to understand that there is no newer Weaksauce or similar available for 4.4.2 and sense 6?
Enjoyment to the MAX!
bryanfritz1 said:
I think all of the above info is great and everyone trying to help is awesome. However I really liked having a soft root via weaksauce for a very limited amount of apps like titanium backup and root explorer. So am I to understand that there is no newer Weaksauce or similar available for 4.4.2 and sense 6?
Enjoyment to the MAX!
Click to expand...
Click to collapse
As far as I am aware firewater still works. I used it just a few days ago and just saw a post today http://forum.xda-developers.com/htc-one-max/help/gain-s-off-t2849836 although he doesn't clearly state that he was using sense 6,
First you must be HTCDEV unlocked. This will wipe data. You need ADB installed personally I use minimal adb fastboot
Step 1: Go to htcdev.com/bootloader, make sure you’re registered with HTC. Once the process of signing up is complete, log into HTC Dev. Also, make sure HTC Sync Manager is installed on your PC.
Step 2: Select your device from the Unlock Bootloader page. Select the “All Other Supported Models” as shown in the screenshot below. Click “Begin Unlock Bootloader” and confirm all dialogue boxes on screen that are presented to you.
Step 3: Now, you’re going to be presented with a series of four steps to put your device in bootloader mode: Disconnect the device from PC, turn it off completely, press and hold Volume Down button and the Power button to start the device in Bootloader mode.
Step 4: Once you’re into the bootloader mode, use the device’s volume keys to select the download mode option and press power button to confirm. At this point, you’ll need to connect your HTC One M9 to your computer via USB cable.
Step 5: Now on your PC, go to fastboot folder, hold down your keyboard’s shift key and click on any empty space and then click on “Open command window here.”
Step 6: Type in fastboot devices in the command prompt window and press enter. If your drivers are installed correctly, then your HTC One M9 should show up in the command prompt.
Note: if you don’t see your device, don’t panic, reinstall HTC Sync Manager, restart your computer and try again.
Step 7: On page 3 of HTC Dev’s website, click on “Proceed to Step 8”. Follow the listed steps all the way to Step 10 and click on Submit. HTC will mail you your unlock token for your device. Download the token, it should be named “Unlock_code.bin” and then should be placed in your fastboot folder.
Step 8: Now back to the command prompt window, type the following: fastboot flash unlocktoken Unlock_code.bin
Step 9: On your device you’ll get a message saying if you want to unlock your bootloader. Use the volume keys to select your choice, and hit the power button to confirm. Once you’re done, your device will restart and you’ll have an unlocked bootloader.
From there you need to install a custom recovery (TWRP)
Follow instructions in this thread http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
CREATE A FREAKING NANDROID BACKUP RIGHT NOW. According to some recognized members of the community, HTC updates only work on an unmodified system. If you ever want to receive official updates from HTC, you HAVE to create a NANDROID RIGHT NOW. Do it. I'll wait.
Then you will need to install Chainfires superuser beta 2.45 http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
These are not my threads just pointing you in the right direction. If someone wants to make a more detailed version I would not oppose.
wytecaztle said:
First you must be HTCDEV unlocked. This will wipe data. You need ADB installed personally I use minimal adb fastboot
Step 1: Go to htcdev.com/bootloader, make sure you’re registered with HTC. Once the process of signing up is complete, log into HTC Dev. Also, make sure HTC Sync Manager is installed on your PC.
Step 2: Select your device from the Unlock Bootloader page. Select the “All Other Supported Models” as shown in the screenshot below. Click “Begin Unlock Bootloader” and confirm all dialogue boxes on screen that are presented to you.
Step 3: Now, you’re going to be presented with a series of four steps to put your device in bootloader mode: Disconnect the device from PC, turn it off completely, press and hold Volume Down button and the Power button to start the device in Bootloader mode.
Step 4: Once you’re into the bootloader mode, use the device’s volume keys to select the download mode option and press power button to confirm. At this point, you’ll need to connect your HTC One M9 to your computer via USB cable.
Step 5: Now on your PC, go to fastboot folder, hold down your keyboard’s shift key and click on any empty space and then click on “Open command window here.”
Step 6: Type in fastboot devices in the command prompt window and press enter. If your drivers are installed correctly, then your HTC One M9 should show up in the command prompt.
Note: if you don’t see your device, don’t panic, reinstall HTC Sync Manager, restart your computer and try again.
Step 7: On page 3 of HTC Dev’s website, click on “Proceed to Step 8”. Follow the listed steps all the way to Step 10 and click on Submit. HTC will mail you your unlock token for your device. Download the token, it should be named “Unlock_code.bin” and then should be placed in your fastboot folder.
Step 8: Now back to the command prompt window, type the following: fastboot flash unlocktoken Unlock_code.bin
Step 9: On your device you’ll get a message saying if you want to unlock your bootloader. Use the volume keys to select your choice, and hit the power button to confirm. Once you’re done, your device will restart and you’ll have an unlocked bootloader.
From there you need to install a custom recovery (TWRP)
Follow instructions in this thread http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
Then you will need to install Chainfires superuser beta 2.45 http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
These are not my threads just pointing you in the right direction. If someone wants to make a more detailed version I would not oppose.
Click to expand...
Click to collapse
Does using the HTC DEV unlock void our HTC 1 year warranty we receive? I am assuming yes....
tws101 said:
Does using the HTC DEV unlock void our HTC 1 year warranty we receive? I am assuming yes....
Click to expand...
Click to collapse
Yes but you can re-lock your device if needed. I do not think there is a way yet to put stock recovery back on.
No RUU is out yet.
You should read the other threads in the M9 forum and add the info here from there regarding OTA impact to rooting and what users should to to be able to take regular OTA if they root and end up mounting system r/w at some point...
tws101 said:
Does using the HTC DEV unlock void our HTC 1 year warranty we receive? I am assuming yes....
Click to expand...
Click to collapse
No it does not...
I've been able to HTC Unlock, but I can't flash TWRP. When I try "fastboot flash recovery TWRP-Recovery-2.8.6.0-Hima-CPTB.img" from download mode it says:
Code:
FAILED (remote: 35: SD_PARTITION_NOT_SUPPORT receovery)
And when I try "fastboot flash recovery TWRP-Recovery-2.8.6.0-Hima-CPTB.img" from bootloader I get:
Code:
FAILED (remote: cannot flash this partition in s-on state)
So how am I supposed to flash the recovery?
m03sizlak said:
I've been able to HTC Unlock, but I can't flash TWRP. When I try "fastboot flash recovery TWRP-Recovery-2.8.6.0-Hima-CPTB.img" from download mode it says:
Code:
FAILED (remote: 35: SD_PARTITION_NOT_SUPPORT receovery)
And when I try "fastboot flash recovery TWRP-Recovery-2.8.6.0-Hima-CPTB.img" from bootloader I get:
Code:
FAILED (remote: cannot flash this partition in s-on state)
So how am I supposed to flash the recovery?
Click to expand...
Click to collapse
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery TWRP.img (TWRP.img represents recovery file’s name, whatever that be)
This worked for me no problem at all. Make sure device is connected to adb and you have usb debugging on.
Yes I have a Sprint M9.
Try and change the recovery name to just twrp.IMG
See if that works.
Are you in download mode? That is the new fastboot
m03sizlak said:
Yeah it doesn't. Recovery will not flash in download mode nor bootloader mode. And yes it is UNLOCKED via HTC method.
Click to expand...
Click to collapse
I saw your post in the other thread that you finally got the recovery flashed. That is good.
wytecaztle said:
I saw your post in the other thread that you finally got the recovery flashed. That is good.
Click to expand...
Click to collapse
Yes apparently helps if you are able to spell recovery correctly. Now that it's rooted need a boot.img with a writable /system. As currently I don't believe changes to system will persist.
Soon. I popped over to the other M9 international thread to see if there was a dev willing to port. He said maybe. So maybe sooner than later.
Hey everyone!! Im have a small problem, I got the twrp recovery installed OK but im have a problem getting root installed.. I have the superuser zip on the root of my internal Sd card but still no go. I have a Sprint One M9
Edit.... Im going to try to install TWRP. 2.8.5.0 I read somewhere that the newest version won't mount system to read and write just read only....
I got root!!
Got it all done but TWRP fails on backup for some reason......? Error starts with E:/.....
Bikegeek said:
Got it all done but TWRP fails on backup for some reason......? Error starts with E:/.....
Click to expand...
Click to collapse
Follow instructions here. http://forum.xda-developers.com/one...h-recovery-t3066720/post59759441#post59759441
Yup, found that and used 2.8.6.3 and all is well. Thanks.
data preload directory
In the past with both the M7 and the M8, when you unlocked the device from HTCDev and it wiped the device, it also wiped files in the /data/preload directory, which usually contained a calculator app, and some images for mail customization.
The only way to ever get those files back was to later run an RUU once rooted, and copy the directory contents at that point for backup.
I wanted to know if anyone knows if this is still the case with the M9?
Looks like everything is still in place.
wytecaztle said:
Looks like everything is still in place.
Click to expand...
Click to collapse
Does that mean you can see /data/preload and its contents in a file manager? That would be encouraging because that would mean they have fixed a long standing bug in their unlocking process and reset process.
PillowMetal said:
Does that mean you can see /data/preload and its contents in a file manager? That would be encouraging because that would mean they have fixed a long standing bug in their unlocking process and reset process.
Click to expand...
Click to collapse
Preload stuff will be there still... It's on a different partition now and thus not lost when unlocking like before on M8.
There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622
Download: https://dl.twrp.me/blueline/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
GitHub: https://github.com/topjohnwu/Magisk/releases
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone
Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
Was my misunderstanding. I thought you were implying people should go back to stock recovery to flash ota. You are talking about flashing ota in twrp. You might clear that up a little bit in that section.
Great post.
Unfortunately, if you are writing a process, then writing everything out is a requirement. Especially with item numbers or using an outline format. Not everyone understands shortcuts taken or abbreviated words, unless they are spelled out in the beginning. IMO, wrote and read too many processes. Including software requirement documentation.
Hi,
thanks for the thread :good:
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
Yes, I think so too.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
The boot.img is into "image.zip"
Then I suggest to flash into a and b (or both)
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
or
fastboot flash boot --slot all boot.img
Edit
be careful here: Factory reset via ADB sideload (can also do this without wiping data)
bootloader is bootloader, boot is boot, bootloader.img isn't boot.img
so, maybe better to write:
fastboot flash bootloader nameofbootloader.img or if simply renamed fastboot flash bootloader bootloader.img
deleted, bug.
trouble flashing files
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
wangdaning said:
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
Click to expand...
Click to collapse
Thanks, but still no luck.
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
fyrmd said:
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
Click to expand...
Click to collapse
I always buy Anker cables and chargers. All have been good so far.
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
Are you able to get into recovery? If so, download the full ota to your pc and side load it with adb.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
i same issue
rczrider said:
[*]Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
Click to expand...
Click to collapse
why not copy all files?
---------- Post added at 11:58 AM ---------- Previous post was at 11:55 AM ----------
fyrmd said:
Thanks, but still no luck.
Click to expand...
Click to collapse
boot to the twrp.img and flash the twrp.zip, unless you are on android 10 you should have no problem unless you are doing it wrong. not exactly hard to do.
How to enable oem unlock in this case?
pedro5148 said:
How to enable oem unlock in this case?
Click to expand...
Click to collapse
There are a few suggestions at https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
However, if the network carrier has locked the bootloader, you cannot unlock it. In the U.S., Verizon and AT&T phones generally cannot be unlocked due to locked bootloaders.