Re-lock bootloader - Sony Xperia XZ Questions & Answers

Hi,
I want to know if it is possible to relock the bootloader and get the drm back?
I backup the TA partition before unlock my bootloader
Thanks in advance

You followed the last link in point #2 on https://forum.xda-developers.com/showpost.php?p=70504721&postcount=2 ?
Hint: read the thread. one answer is in post #20

DHGE said:
You followed the last link in point #2 on https://forum.xda-developers.com/showpost.php?p=70504721&postcount=2 ?
Hint: read the thread. one answer is in post #20
Click to expand...
Click to collapse
I read it yes. But I was thinking at something :
I have a battery issue, after one day of use, I have to recharge it. Could it be the cause of the unlocked bootloader ? Or the stock ROM ?
Other things, I was trying to flash superSU via TWRP but I have a password to enter when I open TWRP to decrypt data. After cancel this step, I flash the superSU zip, and then I brick my phone. I have to boot in flashmode to flash via flashtool. I try 2 superSU zip and always the same problem.
For you, is it better to re-lock the bootloader (hard step for me, regarding the #20 on the thread) of find a solution for my TWRP/root problem and then flash another custom ROM ? (If option 1, any ideas about this problem ?)
Thanks in advance

nathan30 said:
I read it yes. But I was thinking at something :
I have a battery issue, after one day of use, I have to recharge it. Could it be the cause of the unlocked bootloader ? Or the stock ROM ?
Other things, I was trying to flash superSU via TWRP but I have a password to enter when I open TWRP to decrypt data. After cancel this step, I flash the superSU zip, and then I brick my phone. I have to boot in flashmode to flash via flashtool. I try 2 superSU zip and always the same problem.
For you, is it better to re-lock the bootloader (hard step for me, regarding the #20 on the thread) of find a solution for my TWRP/root problem and then flash another custom ROM ? (If option 1, any ideas about this problem ?)
Thanks in advance
Click to expand...
Click to collapse
I really doubt you read my post or understood it or made some effort to follow the links I provide (your repeated questions here of obvious issues all handled there).
I recommend you reset/complete wipe your phone in TWRP. Delete everything except SD-Card.
Then flash a stock SONY ROM via FlashTool. Then relax and enjoy for some days.
Check if you are really allowed to unlock your phone and if check if it is unlocked (all in my long post!).
I wrote "NEVER EVER ..." Did you read this? Your problems could stem from the enbling of MyXperia. Then you might be even beyond repair...
If you still want to root the phone - print my long post and proceed one step after the other and make some remarks on the progress on the printout.
What you write here could (besides MyXperia) also be the problem that you did not follow the steps and flashed SupeerSu before the custom kernel.
I am getting tired of this ...

DHGE said:
I really doubt you read my post or understood it or made some effort to follow the links I provide (your repeated questions here of obvious issues all handled there).
I recommend you reset/complete wipe your phone in TWRP. Delete everything except SD-Card.
Then flash a stock SONY ROM via FlashTool. Then relax and enjoy for some days.
Check if you are really allowed to unlock your phone and if check if it is unlocked (all in my long post!).
I wrote "NEVER EVER ..." Did you read this? Your problems could stem from the enbling of MyXperia. Then you might be even beyond repair...
If you still want to root the phone - print my long post and proceed one step after the other and make some remarks on the progress on the printout.
What you write here could (besides MyXperia) also be the problem that you did not follow the steps and flashed SupeerSu before the custom kernel.
I am getting tired of this ...
Click to expand...
Click to collapse
Hi, and thanks again for your patience and help. You're right, I've missed the kernel part, before flash SuperSU. I'll read again you're post and follow instructions step by step.
Thanks again, and sorry for this :/

DHGE said:
I really doubt you read my post or understood it or made some effort to follow the links I provide (your repeated questions here of obvious issues all handled there).
I recommend you reset/complete wipe your phone in TWRP. Delete everything except SD-Card.
Then flash a stock SONY ROM via FlashTool. Then relax and enjoy for some days.
Check if you are really allowed to unlock your phone and if check if it is unlocked (all in my long post!).
I wrote "NEVER EVER ..." Did you read this? Your problems could stem from the enbling of MyXperia. Then you might be even beyond repair...
If you still want to root the phone - print my long post and proceed one step after the other and make some remarks on the progress on the printout.
What you write here could (besides MyXperia) also be the problem that you did not follow the steps and flashed SupeerSu before the custom kernel.
I am getting tired of this ...
Click to expand...
Click to collapse
So, here I try to re flash TWRP properly. I re flash latest Nougat with FlashTool (wipe APPS_LOG and USERDATA and exclude CUST_RESET and FOTA_RESET) to start clean. Then I flash AndroPlus kernel v19 with
Code:
fastboot flash boot boot.img
. After I flash latest TWRP and flash it with
Code:
fastboot flash recovery twrp-3.0.2-0-kagura.img
. I can access to recovery with POWER and VOL - (I can access, unless you said we can be stuck at this point) and I always have the ask for a password to decrypt data. What is wrong now ?..

use the LATEST TWRP
https://drive.google.com/drive/folders/0B0j3VJ1Xp5N8Y1FZSmMwM1BOZDQ

Related

[Q] ATT HTC One X not booting

Hello,
I have a carrier unlocked ATT HTC One x (sim unlocked), it is not rebooting after the battery was accedently drained. That happened after I put it on the charger and I saw it starting to charge, and then I hit the power on, but it did not go past the HTC One white screen. After the battery is fully charged, I tried to recover it but I got a red triangle with exclamation mark on a phone icon during the recovery process, then it go to the freezing welcome screen again. I saw many very useful posts but they all do not address the specific problem I am facing. The phone is locked for boot-loader, so I have problem installing an new image. As the phone shut down accidentally I did not set the usb debugger enable mode that seams to be required, also it is not rooted. From the posts I see that I needed to get a temporary superuser by accessing one of the phone files (mmcblk0p4) which is also not possible at this stage. I am able to communicate with the phone with my computer (I got fastboot usb on my phone when connected to the windows 7 pc), I can use fastboot command from the cmd-shell screen (when I do fastboot device, I get the serial number, when I do fastboot oem readcid I get CWS__001 as expected from a loced ATT booter as I understood, I got the identifier but got MID not allowed from the HTCdev site, fastboot command seams to work but when I try anything else that seams more useful to me, suggested in the posts, I got FAILD (remote: not allowed) error, when did fastboot flash recovery recoveryimage.img got sending, then writing, then FAILD (remote: signature verify fail) fastboot oem unlock give Command error, I can also do fastboot oem rebootRUU and reboot-bootloader, not sure what is rebootRUU does but seams that I can flash the system this way.. not sure if I need that now or not yet, or if it is even doable), also it seams that I can not use adb that is described in the very useful post below, when I do adb devices (The adb version 1.0.29) it give me "list of the devices attached" message only with no devices, it seams that adb is the key to what I am doing here and if it is not working then I do not know how to proceed.
http://forum.xda-developers.com/showpost.php?p=49019103
doing adb shell give error: device not found. I downloaded many useful packages that I think for 3.18 or 5.18 software, but I am not sure if these are appropriate to my phone software as I do not recall the exact build, not sure if the Hboot version can tell anything about that or not.
Now I know that I need to get superCID, unlock the bootloader, and then recovery, but I can not pass the first step. I am not clear about what is the S-on or off has to do with that or if it is a required step.
Sorry for the very long post, but wanted to be clear as much as I can, the bootloader info is below.
I appraciate your help very much
EVITA PVT SHIP s-on RL
Hboot ver 1.14.0002
radio ver 0.19as.32.09.11_2
openDSP-v29.1.0.45.0622
eMMc-boot
jun 11 2012, 14:36:28
As long as you have fastboot access you can run an RUU. I'd suggest running the 3.18 RUU to get your phone back up and running again. If you need a tutorial there's one here:
http://forum.xda-developers.com/showthread.php?t=2593037
The fastboot oem unlock command doesn't work on this phone unless you have s-off, to unlock the bootloader you need to go to htcdev and do it there. But you first need to follow section 1a in my guide thread to get SuperCID. You must run the 3.18 RUU first though.
I'd advise against using the rebootRUU mode unless you really know what you're doing, messing around with this stuff without proper knowledge is how phones become fully bricked.
So anyway, run the RUU and that should get your phone up and running again. If you want to unlock your bootloader after that then do what I suggested above.
Transmitted via Bacon
timmaaa said:
As long as you have fastboot access you can run an RUU. I'd suggest running the 3.18 RUU to get your phone back up and running again. If you need a tutorial there's one here:
http://forum.xda-developers.com/showthread.php?t=2593037
The fastboot oem unlock command doesn't work on this phone unless you have s-off, to unlock the bootloader you need to go to htcdev and do it there. But you first need to follow section 1a in my guide thread to get SuperCID. You must run the 3.18 RUU first though.
I'd advise against using the rebootRUU mode unless you really know what you're doing, messing around with this stuff without proper knowledge is how phones become fully bricked.
So anyway, run the RUU and that should get your phone up and running again. If you want to unlock your bootloader after that then do what I suggested above.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you timmaaa, I will go through this instruction and will tell you how it goes. I appreciate your prompt replay.. Regards ..
timmaaa said:
As long as you have fastboot access you can run an RUU. I'd suggest running the 3.18 RUU to get your phone back up and running again. If you need a tutorial there's one here:
http://forum.xda-developers.com/showthread.php?t=2593037
The fastboot oem unlock command doesn't work on this phone unless you have s-off, to unlock the bootloader you need to go to htcdev and do it there. But you first need to follow section 1a in my guide thread to get SuperCID. You must run the 3.18 RUU first though.
I'd advise against using the rebootRUU mode unless you really know what you're doing, messing around with this stuff without proper knowledge is how phones become fully bricked.
So anyway, run the RUU and that should get your phone up and running again. If you want to unlock your bootloader after that then do what I suggested above.
Transmitted via Bacon
Click to expand...
Click to collapse
Timmaaa, thank you again, your help is highly appreciated, I was able to run the specific RUU, as it turned out that I have the 2.20 software, after little hassle as the process stopped at 56% and I did not know what to do, but saw your comment on another post saying that there is no option, actually I did not take the USB cable out, but rebooted with fastboot from the command window and it worked in the second time. After that I went one step and rooted the phone successfully. Now, I need to get red of the AT&T software currently installed, I saw many posts about that where you also were involved, but the posts were old, so which is the most updated image that I should use to replace the AT&T image that you recommend? I also saw people updating the HTC One X with lollypop android .. is that good or bad, is the hardware able to work good with that new release? I am not clear on the relation between the software update from AT&T to another image, and updating the Android version, are they the same or two different steps? Thank you.
aabdo said:
Timmaaa, thank you again, your help is highly appreciated, I was able to run the specific RUU, as it turned out that I have the 2.20 software, after little hassle as the process stopped at 56% and I did not know what to do, but saw your comment on another post saying that there is no option, actually I did not take the USB cable out, but rebooted with fastboot from the command window and it worked in the second time. After that I went one step and rooted the phone successfully. Now, I need to get red of the AT&T software currently installed, I saw many posts about that where you also were involved, but the posts were old, so which is the most updated image that I should use to replace the AT&T image that you recommend? I also saw people updating the HTC One X with lollypop android .. is that good or bad, is the hardware able to work good with that new release? I am not clear on the relation between the software update from AT&T to another image, and updating the Android version, are they the same or two different steps? Thank you.
Click to expand...
Click to collapse
If you want to use custom ROMs you'll need to do some more work first.
1. Flash the Kickdroid 5.0 ROM. This is only temporary, you need this ROM to get s-off in the next step.
2. Go to the Rumrunner Site and follow the instructions there to get s-off.
3. Go to my guide thread and follow instructions there to flash the 2.15 firmware.
Now you can flash whatever ROM you like. Lollipop is perfectly fine for this device.
Transmitted via Bacon
timmaaa said:
If you want to use custom ROMs you'll need to do some more work first.
1. Flash the Kickdroid 5.0 ROM. This is only temporary, you need this ROM to get s-off in the next step.
2. Go to the Rumrunner Site and follow the instructions there to get s-off.
3. Go to my guide thread and follow instructions there to flash the 2.15 firmware.
Now you can flash whatever ROM you like. Lollipop is perfectly fine for this device.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you timmaaa, I will work on that and I will let you know how it goes. Best regards ..
timmaaa said:
If you want to use custom ROMs you'll need to do some more work first.
1. Flash the Kickdroid 5.0 ROM. This is only temporary, you need this ROM to get s-off in the next step.
2. Go to the Rumrunner Site and follow the instructions there to get s-off.
3. Go to my guide thread and follow instructions there to flash the 2.15 firmware.
Now you can flash whatever ROM you like. Lollipop is perfectly fine for this device.
Transmitted via Bacon
Click to expand...
Click to collapse
I went through the steps, studied them all first .. then started one by one. First I downloaded Kickdroid 5.0 Rom on my phone storage, although I saw a requirement to have a special firmware package (that to install I needed S-off) post #4 in http://forum.xda-developers.com/showthread.php?t=2485865 , I skipped that requirement and then was able to install Kickdroid 5.0 from the recovery, it flashed successfully, but then the phone did not boot, it hanged on the first white screen, I tried 3 times with changing the options .. I started by not downloading any thing in the flashing process, then last I kept the default except I had to choose to keep sense 5 as there was no default option .. then I cleaned the catch and rebooted .. same result. So I had to go back and restore my original system (as I had it backed up before). I went through the post and in page 19 I saw someone had a similar problem and someone suggested to wipe the storage in order to make it work, which I did not, but then he said it worked without needing to do that. Another suggested to flash a boot.img first with fastboot, which was not in the instructions. Not sure what is the problem I am facing exactly. I use TWRP 2.3.1 to run the zip file on the phone SD, with 75 to 80% battery charged. One more question, I saw a youtube for someone who is getting S-off for HTC One (not x) without that Kikdroid step, https://www.youtube.com/watch?v=MCMJkVbIiIg , he is using your step 2 exactly, Would you please explain to me why I need the first step in my case? Thank you very much for your help.
aabdo said:
I went through the steps, studied them all first .. then started one by one. First I downloaded Kickdroid 5.0 Rom on my phone storage, although I saw a requirement to have a special firmware package (that to install I needed S-off) post #4 in http://forum.xda-developers.com/showthread.php?t=2485865 , I skipped that requirement and then was able to install Kickdroid 5.0 from the recovery, it flashed successfully, but then the phone did not boot, it hanged on the first white screen, I tried 3 times with changing the options .. I started by not downloading any thing in the flashing process, then last I kept the default except I had to choose to keep sense 5 as there was no default option .. then I cleaned the catch and rebooted .. same result. So I had to go back and restore my original system (as I had it backed up before). I went through the post and in page 19 I saw someone had a similar problem and someone suggested to wipe the storage in order to make it work, which I did not, but then he said it worked without needing to do that. Another suggested to flash a boot.img first with fastboot, which was not in the instructions. Not sure what is the problem I am facing exactly. I use TWRP 2.3.1 to run the zip file on the phone SD, with 75 to 80% battery charged. One more question, I saw a youtube for someone who is getting S-off for HTC One (not x) without that Kikdroid step, https://www.youtube.com/watch?v=MCMJkVbIiIg , he is using your step 2 exactly, Would you please explain to me why I need the first step in my case? Thank you very much for your help.
Click to expand...
Click to collapse
You need to flash the boot.img from the Kickdroid ROM zip via fastboot after flashing the ROM in recovery because you're s-on. I'm guessing you haven't done that, and that's why it didn't boot. I wouldn't go anywhere anything that OneXRoot posted honestly, just follow my directions here.
Transmitted via Bacon
timmaaa said:
You need to flash the boot.img from the Kickdroid ROM zip via fastboot after flashing the ROM in recovery because you're s-on. I'm guessing you haven't done that, and that's why it didn't boot. I wouldn't go anywhere anything that OneXRoot posted honestly, just follow my directions here.
Transmitted via Bacon
Click to expand...
Click to collapse
Yes I did not flash the boot.img after I used Kikdroid Rom .. Thank you for clarifying this .. I will try again and let you know .. best regards ..
timmaaa said:
You need to flash the boot.img from the Kickdroid ROM zip via fastboot after flashing the ROM in recovery because you're s-on. I'm guessing you haven't done that, and that's why it didn't boot. I wouldn't go anywhere anything that OneXRoot posted honestly, just follow my directions here.
Transmitted via Bacon
Click to expand...
Click to collapse
But would you please confirm that the second step is exactly as shown in the youtube clip? I am just not positive as it is another device and wanted to hear your opinion .. not sure if there is a difference or not between the hardware of HTC One X and HTC One. Thanks.
aabdo said:
But would you please confirm that the second step is exactly as shown in the youtube clip? I am just not positive as it is another device and wanted to hear your opinion .. not sure if there is a difference or not between the hardware of HTC One X and HTC One. Thanks.
Click to expand...
Click to collapse
Seeing as the steps in the clip aren't numbered I have no idea which part you're talking about. It's very straight forward though, flash Kickdroid (including the boot.img), go to Rumrunner and follow their instructions, flash the firmware in my guide.
timmaaa said:
Seeing as the steps in the clip aren't numbered I have no idea which part you're talking about. It's very straight forward though, flash Kickdroid (including the boot.img), go to Rumrunner and follow their instructions, flash the firmware in my guide.
Click to expand...
Click to collapse
Thanks .. yes it seams straight forward, but as I have no experience, I try to be cautious as much as I can, the entire clip is your step 2 in the instructions you gave me for running the rumrunner .. Sorry if I wasted your time to watch the clip, I should not have asked that, but thanks.
Now I am still stuck actually at the first step, I flashed the KickdroidXL 5 successfully, then I flashed the boot.img (fastboot flash boot boot.img) using the boot.img in the Kickdroid package, as you recommended, a little progress I saw, it start with a new logo "T" then the first HTC white screen I used to be stuck on before, then the One X white screen .. but then does not boot. I flashed the Kickdroid twice and every time I do cache erase with the TWRP and with fastboot (fastboot erase cache). Please let me know if I seam to be missing any steps that cause it to not boot .. Thank you for your help and prompt response .. Regards ..
aabdo said:
Thanks .. yes it seams straight forward, but as I have no experience, I try to be cautious as much as I can, the entire clip is your step 2 in the instructions you gave me for running the rumrunner .. Sorry if I wasted your time to watch the clip, I should not have asked that, but thanks.
Now I am still stuck actually at the first step, I flashed the KickdroidXL 5 successfully, then I flashed the boot.img (fastboot flash boot boot.img) using the boot.img in the Kickdroid package, as you recommended, a little progress I saw, it start with a new logo "T" then the first HTC white screen I used to be stuck on before, then the One X white screen .. but then does not boot. I flashed the Kickdroid twice and every time I do cache erase with the TWRP and with fastboot (fastboot erase cache). Please let me know if I seam to be missing any steps that cause it to not boot .. Thank you for your help and prompt response .. Regards ..
Click to expand...
Click to collapse
Ok, dust things first, lets get Kickdroid booting. When you flash a new ROM you need to perform a full wipe, this means wiping system, data, cache, and dalvik cache.
Transmitted via Bacon
timmaaa said:
Ok, dust things first, lets get Kickdroid booting. When you flash a new ROM you need to perform a full wipe, this means wiping system, data, cache, and dalvik cache.
Transmitted via Bacon
Click to expand...
Click to collapse
OK thank you temmaaa, that was my mistake the, I was trying to not wipe anything, but that seams to be wrong. The strange thing is that after I was able to boot, I still see my data on the phone sd storage. Question for you, when I failed to boot Kickdroid 5, I tried to restore my old AT&T system which I backed up with TWRP and saved on the phone (as well as outside) but that did not restore .. does the boot.img flashing is the reason for that? it seams that I needed to flash another boot.img to get back the old system.. is my understanding correct?
Now I will proceed to the second step .. running rumrunner.. I will follow the instruction from the link you gave me.
Also, would you please explain to me why I need to flash the 2.15 software which is step 3 in your instructions?
Is there any risky step here that I need to take special attention to?
Thank you for your help .. really appropriate it.
aabdo said:
OK thank you temmaaa, that was my mistake the, I was trying to not wipe anything, but that seams to be wrong. The strange thing is that after I was able to boot, I still see my data on the phone sd storage. Question for you, when I failed to boot Kickdroid 5, I tried to restore my old AT&T system which I backed up with TWRP and saved on the phone (as well as outside) but that did not restore .. does the boot.img flashing is the reason for that? it seams that I needed to flash another boot.img to get back the old system.. is my understanding correct?
Now I will proceed to the second step .. running rumrunner.. I will follow the instruction from the link you gave me.
Also, would you please explain to me why I need to flash the 2.15 software which is step 3 in your instructions?
Is there any risky step here that I need to take special attention to?
Thank you for your help .. really appropriate it.
Click to expand...
Click to collapse
No worries, please refer to my guide that I've linked you to, it contains instructions for pretty much anything you need to do.
The wipes that I mentioned don't wipe your sd card, that isn't wiped unless you explicitly choose to wipe it in the advanced wipe menu.
When you made the backup of your stock ROM did you backup boot? If not, that's why your restore isn't booting. If you did, did you restore that as well?
You need to flash the 2.15 firmware because all recent ROMs require the updated firmware to be installed in order to operate correctly. In fact, they won't even flash of the firmware isn't present as there's a check in the updater script that'll stop the install if you don't have the correct firmware. There's no real risk, as long as you follow the directions correctly. In saying that though, there's always a small risk when flashing anything to your phone, but as long as you do what you're supposed to do you can mitigate that risk.
Transmitted via Bacon
timmaaa said:
No worries, please refer to my guide that I've linked you to, it contains instructions for pretty much anything you need to do.
The wipes that I mentioned don't wipe your sd card, that isn't wiped unless you explicitly choose to wipe it in the advanced wipe menu.
When you made the backup of your stock ROM did you backup boot? If not, that's why your restore isn't booting. If you did, did you restore that as well?
You need to flash the 2.15 firmware because all recent ROMs require the updated firmware to be installed in order to operate correctly. In fact, they won't even flash of the firmware isn't present as there's a check in the updater script that'll stop the install if you don't have the correct firmware. There's no real risk, as long as you follow the directions correctly. In saying that though, there's always a small risk when flashing anything to your phone, but as long as you do what you're supposed to do you can mitigate that risk.
Transmitted via Bacon
Click to expand...
Click to collapse
First I would like to express my appreciation for your help and detailed instructions, Thank you.
Kikdroid 5 seams really nice, I finally got rid of the AT&T image.
You are right, I did not backup the stock boot.img .. I did not know I needed to .. or overlooked it in some instructions, well as I said, I have no experience and trying to learn... If there is a reference that I can read to understand mainly the terminology and the relationship better them .. please point it to me .. I have problem understanding some the used terminology, specially that kernel word seams that the kernel is the Android version .. maybe..
My worry with firmware flash is that I see in some instructions .. if it did not work .. or give an error .. flash it again "immediately" .. that immediately word scares me very much .. what if I did not do it fast enough .. am I going to loose my phone. That is something completely unclear to me, I have some knowledge in computers, but I do not understand how a software can damage a hardware.
Best regards ..
aabdo said:
First I would like to express my appreciation for your help and detailed instructions, Thank you.
Kikdroid 5 seams really nice, I finally got rid of the AT&T image.
You are right, I did not backup the stock boot.img .. I did not know I needed to .. or overlooked it in some instructions, well as I said, I have no experience and trying to learn... If there is a reference that I can read to understand mainly the terminology and the relationship better them .. please point it to me .. I have problem understanding some the used terminology, specially that kernel word seams that the kernel is the Android version .. maybe..
My worry with firmware flash is that I see in some instructions .. if it did not work .. or give an error .. flash it again "immediately" .. that immediately word scares me very much .. what if I did not do it fast enough .. am I going to loose my phone. That is something completely unclear to me, I have some knowledge in computers, but I do not understand how a software can damage a hardware.
Best regards ..
Click to expand...
Click to collapse
The XDA Encyclopedia is pretty handy for learning terminology:
http://forum.xda-developers.com/other-special/encyclopedia
The kernel isn't the Android version, it's a low level layer of firmware that basically handles interactions between the hardware and the software. Searching "what is a kernel" on Google should return a much better explanation than I can give.
When those instructions say you must give the same command again immediately it really just means to do it without anything else in between. You should actually give the command twice even if you don't receive the error, so make sure you do it twice.
Transmitted via Bacon
timmaaa said:
The XDA Encyclopedia is pretty handy for learning terminology:
http://forum.xda-developers.com/other-special/encyclopedia
The kernel isn't the Android version, it's a low level layer of firmware that basically handles interactions between the hardware and the software. Searching "what is a kernel" on Google should return a much better explanation than I can give.
When those instructions say you must give the same command again immediately it really just means to do it without anything else in between. You should actually give the command twice even if you don't receive the error, so make sure you do it twice.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you timmaaa .. I will work on the following steps and update you with my progress .. best regards ..
timmaaa said:
The XDA Encyclopedia is pretty handy for learning terminology:
http://forum.xda-developers.com/other-special/encyclopedia
The kernel isn't the Android version, it's a low level layer of firmware that basically handles interactions between the hardware and the software. Searching "what is a kernel" on Google should return a much better explanation than I can give.
When those instructions say you must give the same command again immediately it really just means to do it without anything else in between. You should actually give the command twice even if you don't receive the error, so make sure you do it twice.
Transmitted via Bacon
Click to expand...
Click to collapse
timmaaa, I successfully got S-off on my phone, which is the second step in your instruction, that was not possible without your help, Thank you ..
I will now study the third step which I see explained very well in your guide to flash the 2.15 firmware.
I still have the Kickdroid 5 and I noticed that the phone is restarting very often now, it also looses signal, and that Google hangouts is not working, hopefully that will get better with the 2.15 firmware. By the way, what is that 2.15 Firmware? is that HTC officially released ROM? (firmware is a ROM?), I hope the relationship between the recovery, the boot, and the firmware are explained in the link you provided, because still these not clear to me. I am guessing I will not have Kickdroid 5 after flashing the 2.15 firmware .. is that correct?
Thank you very much for your help throughout this process.
aabdo said:
timmaaa, I successfully got S-off on my phone, which is the second step in your instruction, that was not possible without your help, Thank you ..
I will now study the third step which I see explained very well in your guide to flash the 2.15 firmware.
I still have the Kickdroid 5 and I noticed that the phone is restarting very often now, it also looses signal, and that Google hangouts is not working, hopefully that will get better with the 2.15 firmware. By the way, what is that 2.15 Firmware? is that HTC officially released ROM? (firmware is a ROM?), I hope the relationship between the recovery, the boot, and the firmware are explained in the link you provided, because still these not clear to me. I am guessing I will not have Kickdroid 5 after flashing the 2.15 firmware .. is that correct?
Thank you very much for your help throughout this process.
Click to expand...
Click to collapse
Those problems will stop once you have flashed the firmware. The firmware isn't a ROM, it's a lower level of firmware that includes the radio/modem, hboot, and various drivers. It is official from HTC. You will still have Kickdroid after installing the firmware.
XDA Moderator
Transmitted via Bacon

[Q] HTC One E8 - root guide help

Can anyone give a step by step root guide of this phone on lollipop version 5.0.2? i wanna try rooting
nisekoi said:
Can anyone give a step by step root guide of this phone on lollipop version 5.0.2? i wanna try rooting
Click to expand...
Click to collapse
May i know what is the varient of your phone? Because the method i followed is to root my E8 M8sX single sim. Im not sure if daul sim will cause a problem or not.
Firstly, you need an unlocked bootloader which can be unlocked through htcdev. You will need to create an account and follow the steps on the website. By unlocking the bootloader, it will wipe away all your data(messages, contacts, Apps etc.) on your phone so do a BACKUP before proceeding on the website.
Next, you will need a TWRP (which is a custom recovery to flash custom ROMs and root). TWRP can be found here. Finally, you need a flashable SuperSU to install through TWRP from here. Save the TWRP and SuperSU zip files on your sd card.
Then, follow the steps in this link. Download Minimal ADB and fastboot. Skip step 2 on the page after the one to download adb and fastboot. Just go straight to command without turning off your phone. Also, there is no need to download TWRP and SuperSU again from the page.
If you encounter any errors during the rooting process, just stop and get back to the state where the device is still bootable and for daily use. Ask me and i will try to reply ASAP.
**Disclaimer: I am in no way responsible if your device becomes unusable after the rooting process. Btw, Nisekoi is quite fun to watch but becomes draggy in the manga
JuzARandomGuy said:
May i know what is the varient of your phone? Because the method i followed is to root my E8 M8sX single sim. Im not sure if daul sim will cause a problem or not.
Firstly, you need an unlocked bootloader which can be unlocked through htcdev. You will need to create an account and follow the steps on the website. By unlocking the bootloader, it will wipe away all your data(messages, contacts, Apps etc.) on your phone so do a BACKUP before proceeding on the website.
Next, you will need a TWRP (which is a custom recovery to flash custom ROMs and root). TWRP can be found here. Finally, you need a flashable SuperSU to install through TWRP from here. Save the TWRP and SuperSU zip files on your sd card.
Then, follow the steps in this link. Download Minimal ADB and fastboot. Skip step 2 on the page after the one to download adb and fastboot. Just go straight to command without turning off your phone. Also, there is no need to download TWRP and SuperSU again from the page.
If you encounter any errors during the rooting process, just stop and get back to the state where the device is still bootable and for daily use. Ask me and i will try to reply ASAP.
**Disclaimer: I am in no way responsible if your device becomes unusable after the rooting process. Btw, Nisekoi is quite fun to watch but becomes draggy in the manga
Click to expand...
Click to collapse
Thanks for your reply. My phone is m8sx single sim just like yours. You mean by "stop and get back to the state where the device is bootable" is restore the phone from it backup?
** i watched the nisekoi anime only. will read the manga later.
nisekoi said:
Thanks for your reply. My phone is m8sx single sim just like yours. You mean by "stop and get back to the state where the device is bootable" is restore the phone from it backup?
** i watched the nisekoi anime only. will read the manga later.
Click to expand...
Click to collapse
Well, yeah thats what i meant. One way just to be safe would be after flashing twrp, boot to homescreen. After that then flash SuperSU. Other than while unlocking the bootloader will wipe away everything, i don't think flashing twrp and supersu will cause your phone to brick. Now knowing that we have the same varient then things should also go smoothly with yours. Do take note that the phone may take longer to boot after factory reset.
Just in case you didn't know, in order to boot the phone to recovery is by pressing power and volume down at the same time while the phone is off.
JuzARandomGuy said:
Well, yeah thats what i meant. One way just to be safe would be after flashing twrp, boot to homescreen. After that then flash SuperSU. Other than while unlocking the bootloader will wipe away everything, i don't think flashing twrp and supersu will cause your phone to brick. Now knowing that we have the same varient then things should also go smoothly with yours. Do take note that the phone may take longer to boot after factory reset.
Just in case you didn't know, in order to boot the phone to recovery is by pressing power and volume down at the same time while the phone is off.
Click to expand...
Click to collapse
I can't find the fast boot option under settings/power.
i can already boot to recovery.
nisekoi said:
I can't find the fast boot option under settings/power.
i can already boot to recovery.
Click to expand...
Click to collapse
They removed the fastboot option for lollipop. I think they set it on by default but it seems to boot slower compared to kitkat.
JuzARandomGuy said:
They removed the fastboot option for lollipop. I think they set it on by default but it seems to boot slower compared to kitkat.
Click to expand...
Click to collapse
I still get stuck at the unlocking the bootloader. In step 5, it asked to enter this command "fastboot oem get_identifier_token" but it says that " the program cants start because AdbWinApi.dll is missing". I did follow the steps correctly.
Download Android sdk and update it
nisekoi said:
I still get stuck at the unlocking the bootloader. In step 5, it asked to enter this command "fastboot oem get_identifier_token" but it says that " the program cants start because AdbWinApi.dll is missing". I did follow the steps correctly.
Click to expand...
Click to collapse
snoopyhaeckers said:
Download Android sdk and update it
Click to expand...
Click to collapse
Did the solution work? On google also says to just update android sdk for htc drivers.
JuzARandomGuy said:
Did the solution work? On google also says to just update android sdk for htc drivers.
Click to expand...
Click to collapse
yup it works for me. but now i can't flash the TWRP recovery. it keep saying " error: can't load twrp.img ". i did change the name of the twrp file to twrp.img in my pc.
i did managed to flash the custom recovery... the instruction is not clear. so i search for other information. it turns out i hve to put the twrp file in the same folder as minimal adb
How to root and update htc e8 android version
Hello,
Please I need steps to root my HTC E8 and upgrade the android version.
HTC E8, M8sn Single SIM, Android 4.4.2

Request: Up to date step by step guide for flashing TWRP and Root?

OK so I'm no noob when it comes to rooting anything up to lollipop, but with marshmallow it seems alot more complicated. Can someone with an HTC a9 6.0.1 plz post step by step guide for flashing TWRP? And if feeling generous, root as well? I see all this stuff about patching boot .imgs and other little stuff, and I'm ready to flash TWRP on my sprint a9 and wanna double check before I do...
bdizzle1686 said:
OK so I'm no noob when it comes to rooting anything up to lollipop, but with marshmallow it seems alot more complicated. Can someone with an HTC a9 6.0.1 plz post step by step guide for flashing TWRP? And if feeling generous, root as well? I see all this stuff about patching boot .imgs and other little stuff, and I'm ready to flash TWRP on my sprint a9 and wanna double check before I do...
Click to expand...
Click to collapse
First you have to enable developer options and click enable OEM Unlocking and usb debugging to on. After that visit htcdev.com and follow the steps to unlock the bootloader. After you have an unlocked bootloader, visit the twrp thread for the HTC One A9, it gives you the download link for the One A9. After doing this, download SuperSU. Zip from online and flash it through twrp.
Htcdev: http://www.htcdev.com/bootloader/
TWRP thread can be found here: http://forum.xda-developers.com/one-a9/orig-development/recovery-twrp-touch-recovery-t3257023/page25
Steps to flash twrp:http://rootmygalaxy.net/how-to-install-twrp-recovery-on-htc-one-a9/
SuperSU: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703/page43
(Use the twrp flashable one in this case)
Good luck, and feel free to ask if you have any more questions
MGfusion said:
First you have to enable developer options and click enable OEM Unlocking and usb debugging to on. After that visit htcdev.com and follow the steps to unlock the bootloader. After you have an unlocked bootloader, visit the twrp thread for the HTC One A9, it gives you the download link for the One A9. After doing this, download SuperSU. Zip from online and flash it through twrp.
Htcdev: http://www.htcdev.com/bootloader/
TWRP thread can be found here: http://forum.xda-developers.com/one-a9/orig-development/recovery-twrp-touch-recovery-t3257023/page25
Steps to flash twrp:http://rootmygalaxy.net/how-to-install-twrp-recovery-on-htc-one-a9/
SuperSU: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703/page43
(Use the twrp flashable one in this case)
Good luck, and feel free to ask if you have any more questions
Click to expand...
Click to collapse
Ty, Sry I should've mentioned I already unlocked through htcdev, downloaded TWRP and supersu, installed adb & fastboot/drivers on my CPU, etc.
I'm moreso confused with all this wiping / formatting data to disable encryption, + with the system image backup, do I do that before or after I format data, plus I've seen many say to flash super-su by adb side loading it... can't flash it directly from external SD card?
Pretty much that stuff and the correct order to do that stuff is what has me all flabbergasted right now... lol, any advice would be MUCH appreciated
bdizzle1686 said:
Ty, Sry I should've mentioned I already unlocked through htcdev, downloaded TWRP and supersu, installed adb & fastboot/drivers on my CPU, etc.
I'm moreso confused with all this wiping / formatting data to disable encryption, + with the system image backup, do I do that before or after I format data, plus I've seen many say to flash super-su by adb side loading it... can't flash it directly from external SD card?
Pretty much that stuff and the correct order to do that stuff is what has me all flabbergasted right now... lol, any advice would be MUCH appreciated
Click to expand...
Click to collapse
Lol, forced encryption is no fun, I've never had a problem with it on the stock HTC Sense ROM, only when I've gone to cyanogenmod have I had a problem with it, and when you face that problem you would have to format data (factory reset) to access the internal storage through TWRP. However, in the TWRP thread you can find a file call A9 boot image patcher (or something like that, lol) that you flash after flashing cyanogenmod (or any ROM with forced encryption) but BEFORE you boot the ROM, this will install a custom kernel that disables forced encryption. So basically right after flashing any ROM flash the boot image patcher to never have a problem with forced encryption. You shouldn't have to flash a system image backup, I've never had to do that before when formatting data.
And to answer your second question, I have always flashed SuperSU from external SD card, never have done anything else, so basically it is fine to do so.
Hope you find the answers to all your questions, and good luck :good:
Thanks man, I just want the system image backup just in case, like whenever OTA time rolls around. Not planning on flashing cm or anything, just rooting the stock Rom
bdizzle1686 said:
Thanks man, I just want the system image backup just in case, like whenever OTA time rolls around. Not planning on flashing cm or anything, just rooting the stock Rom
Click to expand...
Click to collapse
Oh I see. Well I'm not sure on that one I usually just flash updates through TWRP

Unlock bootloader then rooting method?

Hey everyone, I've been lurking around for about two months, from when I picked up this phone. It's still completely stock. Unrooted, S-ON, all that. Well, after the update to Nougat, I've been searching for a way to unlock the bootloader & root. Is it safe for me to use WinDroid Toolkit for the process? Just need a guide for the process, for the most part. I appreciate any help that anyone is willing to offer.
acesavant00 said:
Is it safe for me to use WinDroid Toolkit for the process? Just need a guide for the process, for the most part. I appreciate any help that anyone is willing to offer.
Click to expand...
Click to collapse
Go to http://htcdev.com and make an account, then follow the steps and unlock your bootloader from there. After that you fastboot flash TWRP using ADB, and then use TWRP to flash a root solution. I prefer Magisk.
Alright, just unlocked the bootloader, going through the process of setting up my phone once again. Do you have a link to the Magisk & TWRP programs that I can use? Also, should I put the TWRP file in the same folder as the fastboot files?
I greatly appreciate the assistance you've given me so far, I'm deeply grateful man.
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
acesavant00 said:
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
Click to expand...
Click to collapse
try this step by step.. :good:
1.Flash TWRP 3.0.3-8 via Fastboot.. Do not reboot into system, enter into recovery..
2.Do a factory Reset via TWRP.. Do not reboot into system
3.Now flash SuperSU 2.79 SR3.. Reboot into system..
couple of bootloops are common, do not give up for at least 3 bootloops..
It will take a long time to boot as you have done a factory reset..
So be patient and wait for at least half hour..
acesavant00 said:
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
Click to expand...
Click to collapse
Sorry about this - I updated the TWRP thread with the current/preferred root method: MagiskSU.
You need to flash a stock boot.img and then flash the Magisk zip from the linked thread.
Captain_Throwback said:
Sorry about this - I updated the TWRP thread with the current/preferred root method: MagiskSU.
You need to flash a stock boot.img and then flash the Magisk zip from the linked thread.
Click to expand...
Click to collapse
Aw crap, I wish I would have seen this yesterday. I tried to format data & flash one of the stock rooted roms for marshmallow roms for my sprint one a9... now it just hangs at the HTC One logo. I'm gonna assume that I'm screwed until a stock rooted Nougat rom is released for sprint.
acesavant00 said:
Aw crap, I wish I would have seen this yesterday. I tried to format data & flash one of the stock rooted roms for marshmallow roms for my sprint one a9... now it just hangs at the HTC One logo. I'm gonna assume that I'm screwed until a stock rooted Nougat rom is released for sprint.
Click to expand...
Click to collapse
Can't you just flash the Nougat RUU?
Captain_Throwback said:
Can't you just flash the Nougat RUU?
Click to expand...
Click to collapse
I found the post about the Nougat RUU, but the program won't recognize my phone cause it won't boot. I'm gonna try & flash the firmware through TWRP.
acesavant00 said:
I found the post about the Nougat RUU, but the program won't recognize my phone cause it won't boot. I'm gonna try & flash the firmware through TWRP.
Click to expand...
Click to collapse
You don't flash firmware with TWRP. But you can use the SD card method to flash the RUU, which doesn't require a computer.
Captain_Throwback said:
You don't flash firmware with TWRP. But you can use the SD card method to flash the RUU, which doesn't require a computer.
Click to expand...
Click to collapse
Sorry to bother you again, but you wouldn't happen to know a method of extracting the rom.zip from the exe file, would you?
acesavant00 said:
Sorry to bother you again, but you wouldn't happen to know a method of extracting the rom.zip from the exe file, would you?
Click to expand...
Click to collapse
[TOOL][LINUX|WIN|MAC][64bit][29-SEP-2016]Universal HTC RUU/ROM Decryption Tool 3.1.0
Run the tool with the -z flag to output a zip to the "OUT" folder.
Captain_Throwback said:
[TOOL][LINUX|WIN|MAC][64bit][29-SEP-2016]Universal HTC RUU/ROM Decryption Tool 3.1.0
Run the tool with the -z flag to output a zip to the "OUT" folder.
Click to expand...
Click to collapse
Thank you so much, man. The zip is prepped, just gotta charge my phone again to 30%. But afterwards, will I have to go through the unlock bootloader process? If I do, I don't wanna mess up on the rooting process.
acesavant00 said:
Thank you so much, man. The zip is prepped, just gotta charge my phone again to 30%. But afterwards, will I have to go through the unlock bootloader process? If I do, I don't wanna mess up on the rooting process.
Click to expand...
Click to collapse
Your bootloader will stay unlocked.
Captain_Throwback said:
Your bootloader will stay unlocked.
Click to expand...
Click to collapse
Awesome, I appreciate all of the help, man. Sorry again if I annoyed you with all of my incessant questions. Just didn't wanna mess up my phone even further.
Hello Guys,
I Have an HTC one a9 with 7.0, s-off, bootloader locked
I have some concerns before I root my phone
If I unlock the bootloader and root the phone, Will I have the option of phone encryption as it used to be ?
If I unlock the bootloader with HTCDev and flash the TWRP with SuperSu and boot file, it is a MUST to do a data factory reset? or I`m able to do all the process without loosing my data?
Thank you in advance
rilley said:
Hello Guys,
I Have an HTC one a9 with 7.0, s-off, bootloader locked
I have some concerns before I root my phone
If I unlock the bootloader and root the phone, Will I have the option of phone encryption as it used to be ?
If I unlock the bootloader with HTCDev and flash the TWRP with SuperSu and boot file, it is a MUST to do a data factory reset? or I`m able to do all the process without loosing my data?
Thank you in advance
Click to expand...
Click to collapse
Unlocking your bootloader will wipe the device.
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
sandreas said:
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
Click to expand...
Click to collapse
+1 I`m interested on this question, I have Nougat installed
sandreas said:
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
Click to expand...
Click to collapse
rilley said:
+1 I`m interested on this question, I have Nougat installed
Click to expand...
Click to collapse
Yes, you can root and debloat Nougat. Though you should make a stock system image backup first of you ever want to receive an OTA again. The TWRP thread FAQ has a lot of information about this.

[GUIDE]Unlock Realme 3 Pro Bootloader , Twrp and Root

Delete this thread
have u try flash magisk with twrp ??is it work?
Relocking device with modified partitions can possibly brick your device, please do not post guides without trying it on your device first.
Regards,
acervenky
@sayan8, please be careful as to what you are posting in your help thread / guide...
1. You have almost copied the unlock /relock steps from the realme website...https://c.realme.com/in/post-details/1134295513231785984 without giving credit to the website link.
2. Mistake as pointed out above by @acervenky.
3. You have linked the twrp to the realme3pro twrp thread where NOBODY has been able to boot up his phone / boot into twrp after flashing the twrp posted there.. Under these circumstances, why would you advise anyone else (probably a noob) ti brick his phone by doing what you posted?
A better method would be to add the caveats (warnings) for flashing twrp (nobody has successfully done it, yet) or the relock method.
Regards.
acervenky said:
Relocking device with modified partitions can possibly brick your device, please do not post guides without trying it on your device first.
Regards,
acervenky
Click to expand...
Click to collapse
Yeah , I know that. You are right I should not have posted the thread without trying it first.
Cookie Ninja said:
@sayan8, please be careful as to what you are posting in your help thread / guide...
1. You have almost copied the unlock /relock steps from the realme website...https://c.realme.com/in/post-details/1134295513231785984 without giving credit to the website link.
2. Mistake as pointed out above by @acervenky.
3. You have linked the twrp to the realme3pro twrp thread where NOBODY has been able to boot up his phone after flashing the twrp posted there.. Under these circumstances why would you advise anyone else (probably a noob) ti brick his phone by doing what you posted?
A better method would be to add the caveats (warnings) for flashing twrp (nobody has successfully done it, yet) or the relock method.
Regards.
Click to expand...
Click to collapse
Hey ,
1. I have given proper credits to everyone. See at the bottom.
2. I know that and should have mentioned the warning there.
3. I know that , I thought anyone who's familiar with xda would've known that custom partition can brick your device while relocking. Yeah you are right , should have tried this on a device first before posting the guide .
I'm removing this guide and request the mods to delete this thread.
No need for such an extreme step. Keep it as work in progress...after all you are the OP of the thread....wait a while twrp, root, all will fall in place...

Categories

Resources