Related
so i decided to root my phone today, and flash a custom rom. i am using the t-mobile variant.
i used the all in one toolkit to unlock bootloader, and everything was going good, but i think i might have forgot to install superuser? i am not sure what went wrong. but i was trying to flash android revolution hd, and it was stuck in the bootloop. so i thought i needed to flash the boot.img like i had to in past devices. did that, but still nothing.
i go into CWM and now i can't access the sd card. so i did a wipe and it still won't mount on my computer. did a little reading around, and someone suggested relocking the bootloader, and flashing stock recovery file (i don't think i got the right one), and then unlocked the bootloader and reflash CWM, and that sideloading a rom would work. everytime i try to sideload a rom, i get a device not found error, but fastboot responds to other adb commands. i did make a backup in CWM, but i moved it from the phone to my laptop, but i have no idea how to even use it. adb push to device does nothing. =/
i really really really hope i didn't brick my phone. anyone have some insight? help? i tried looking for a RUU but it seems there isn't one for t-mobile.
so i am able to flash recovery, and get into it, when i try to mount sdcard in the options, it doesn't say anything. stuck in bootloop still. can't sideload. can't push. really really wish it had an external sd card which would make issues like this a bit easier to solve.
Nah, mods don't delete threads like this. Thread moved to T-Mobile HTC One Q&A (and don't post questions anywhere other than the Q&A section in the forum of your device's variant )
fastboot won't respond to adb commands because it's fastboot not adb. i would use the toolkit and install TWRP recovery and load up TWRP. from there you can adb sideload or do other adb commands once you get it loaded.
orvon.freeman said:
I advise this due to the fact you can use adb commands.
relock bootloader then run an RUU here is the one from AT&T http://forum.xda-developers.com/showthread.php?t=2287036&highlight=ruu.
Click to expand...
Click to collapse
Do not attempt to flash an AT&T RUU to your T-Mobile device. In the best case scenario, it should fail(due to S-ON). I would not recommend fooling around with RUUs on different carrier-branded devices.
As for the OP, I'm not sure what to recommend. Most internal storage-only devices won't mount in USB. Wiping your internal storage was the worst thing that you could have done. I'm not sure why adb sideload won't work if normal adb commands and fastboot commands are being accepted. Have you tried a different USB port? I know it sounds strange, but sometimes that can make a difference.
unremarked said:
Do not attempt to flash an AT&T RUU to your T-Mobile device. In the best case scenario, it should fail(due to S-ON). I would not recommend fooling around with RUUs on different carrier-branded devices.
As for the OP, I'm not sure what to recommend. Most internal storage-only devices won't mount in USB. Wiping your internal storage was the worst thing that you could have done. I'm not sure why adb sideload won't work if normal adb commands and fastboot commands are being accepted. Have you tried a different USB port? I know it sounds strange, but sometimes that can make a difference.
Click to expand...
Click to collapse
just thought about that. Each carrier is diff my bad. good catch unremarked.
I looked for a nandroid that you could use with the toolbox to flash it is t-mobile http://forum.xda-developers.com/showthread.php?t=2182823
orvon.freeman said:
this is the wrong section for this. This belongs in QA not dev. Next time read the rules http://forum.xda-developers.com/showthread.php?t=2158147
Good luck
Click to expand...
Click to collapse
pandaball said:
Nah, mods don't delete threads like this. Thread moved to T-Mobile HTC One Q&A (and don't post questions anywhere other than the Q&A section in the forum of your device's variant )
Click to expand...
Click to collapse
appreciate it, xda forums sure has grown since when i was on here with my g2/my4g slide, lots of subforums, and in a haze of having soft bricked my phone, i posted in the wrong section. sorry!
TygerByte said:
fastboot won't respond to adb commands because it's fastboot not adb. i would use the toolkit and install TWRP recovery and load up TWRP. from there you can adb sideload or do other adb commands once you get it loaded.
Click to expand...
Click to collapse
unremarked said:
Do not attempt to flash an AT&T RUU to your T-Mobile device. In the best case scenario, it should fail(due to S-ON). I would not recommend fooling around with RUUs on different carrier-branded devices.
As for the OP, I'm not sure what to recommend. Most internal storage-only devices won't mount in USB. Wiping your internal storage was the worst thing that you could have done. I'm not sure why adb sideload won't work if normal adb commands and fastboot commands are being accepted. Have you tried a different USB port? I know it sounds strange, but sometimes that can make a difference.
Click to expand...
Click to collapse
i did what tygerbyte suggested several times with no success. then i decided to reinstall htc drivers, restart the laptop, and use a different usb port like unremarked suggested, i am able to sideload now! flashing my backup i made in CWM right now, hopefully this will give me a working phone again before i try to flash a custom rom again lol.
i have my fingers crossed.
thanks for the suggestions everyone. ill post back in a bit with results.
just wanted to update, i was able to flash android revolution after several tries / freezing, but phone is back on and functional now.
thanks for walking me through this, i would have gone insane if i bricked my one.
mky4b11 said:
just wanted to update, i was able to flash android revolution after several tries / freezing, but phone is back on and functional now.
thanks for walking me through this, i would have gone insane if i bricked my one.
Click to expand...
Click to collapse
Isn't it the worst feeling, thinking you have bricked your $600 phone? I soft-bricked my husbands Bionic once, stayed up all night long and finally figured out I had skipped a step.
The BEST feeling, though, is realizing that you can, and did, recover from what appeared to be a catastrophic fail. Congratulations!
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Update: I've finally figured out how to get the TWRP recovery booted. Now working on trying to get my phone to boot up an OS of some sort. Very slowly but surely.
bullmurf said:
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Click to expand...
Click to collapse
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Addicted2xda said:
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Click to expand...
Click to collapse
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
bullmurf said:
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
Click to expand...
Click to collapse
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Addicted2xda said:
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Click to expand...
Click to collapse
"use sideload to copy / install a custom ROM..." OK I don't know anything about this but it will point me in the right direction. I have the phone unlocked. The HBOOT version is 1.40.0000. I'll see if I can do what you suggested, thanks.
Update: Atempting an adb sideload using TWRP which seems to be the only option for me.
ADB Sideload
What is ADB sideload?
--------------------------------------------------------------------------------
ADB sideload is a new feature that was added to AOSP recovery in Jelly Bean. As of version 2.3, TWRP now supports ADB sideload mode. ADB sideload is a different ADB mode that you can use to push and install a zip using one command from your computer. Most likely ADB sideload won't be very useful for your average recovery user, but ADB sideload can be a huge time-saver for a ROM developer.
How do I use ADB sideload?
--------------------------------------------------------------------------------
1.Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher
2.Have newer ADB binaries installed on your computer. If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from the Android SDK. You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line.
3.Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
4.From the command line, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
Click to expand...
Click to collapse
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
bullmurf said:
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
Click to expand...
Click to collapse
Update: after trying the same thing 100 times it decided to send "sideload". command line was adb sideload name.zip. Installing Viper ROM for HOX+ atm. I'll see if it fixes all of my problems. Thanks for all of the help to this point. I'll type up a guide of what went wrong with my root and how we managed to get it fixed.
Update: Phone is booting to HTC white screen and then shutting off. Now trying to figure that one one out.
Update" Phone is booting to HTC white screen now and staying there. In TWRP under reboot is says "no os installed, do you still wish to reboot". Still digging in the forums to figure this one out and how to fix it. I installed the Viper ROM fine but when it asked to reboot now it just rebooted to HTC white screen. Missing something here? The phone is S-ON, does that make a difference in using the TWRP?
Is there an RUU exe file I can run from my computer? I relocked the phone but the links you gave me are for installing the ap through google play. Not sure how you do that with a phone that wont boot past htc screen.
Update: I've found an RUU application from these boards that is supposed to work for HOX+ so i'm downloading it. It really is taking forever to find the information I need along the way from this board but it's here....somewhere...I think...Will keep plugging away but feel free to throw me a bone ever once in a while! =)
Update: The version that worked for others isn't the same version I have. Going to dig again for 1.19.502.1 version.
Update: Found the version in the last place I thought it would be...HTC website...Downloading it and just hoping its and application I can run on my computer.
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
I would suggest you to use hasoon's all in one toolkit
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
bullmurf said:
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
Click to expand...
Click to collapse
There is a great lockscreen called CLocker
Addicted2xda said:
There is a great lockscreen called CLocker
Click to expand...
Click to collapse
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
bullmurf said:
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
Click to expand...
Click to collapse
You will find it in the playstore itself
You need to set lockscreen to None
Addicted2xda said:
You will find it in the playstore itself
You need to set lockscreen to None
Click to expand...
Click to collapse
Thanks again man. I got it and the ring is gone \0/ Phone looks freakin amazing now with that lock screen and Elegancia rom. Glad you stopped by to help :good: Still learning my way around the forums and my rooted phone. It's great to not be stressed about bricking it ^^
suppils soars
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
mrmagoogt said:
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
Click to expand...
Click to collapse
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Addicted2xda said:
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Click to expand...
Click to collapse
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
mrmagoogt said:
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
Click to expand...
Click to collapse
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Addicted2xda said:
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Click to expand...
Click to collapse
Thanks, I used a script to charge my battery, relock bootloader and installed ruu file to get back to stock, rooted again using Hasoon2000's all in one kit...
Can anyone tell me where to get my At One M8 repairs?
I can't take it to AT&T since they will say it's been tampered. I would appreciate any advice because I couldn't get any ROM into it. Only cyanogen would work but no WiFi.
ricm68 said:
Can anyone tell me where to get my At One M8 repairs?
I can't take it to AT&T since they will say it's been tampered. I would appreciate any advice because I couldn't get any ROM into it. Only cyanogen would work but no WiFi.
Click to expand...
Click to collapse
Not enough information. What about it is "broken" requiring repair? In what way is it "tampered"?
Oh, and HTC will most likely refuse to repair it directly, telling you that if you bought it from AT&T, that AT&T needs to act as the agent for repair. You can always try to head over to HTC's website (I'm sure you can find it), find the support section, and make a support inquiry from them directly.
garyd9 said:
Not enough information. What about it is "broken" requiring repair? In what way is it "tampered"?
Oh, and HTC will most likely refuse to repair it directly, telling you that if you bought it from AT&T, that AT&T needs to act as the agent for repair. You can always try to head over to HTC's website (I'm sure you can find it), find the support section, and make a support inquiry from them directly.
Click to expand...
Click to collapse
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
ricm68 said:
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
Click to expand...
Click to collapse
Did you flash the google play edition ruu? If so, the phone was repartitioned, and sense will no longer "fit" on the system partition. There's a way to deal with that if that's the case...
garyd9 said:
Did you flash the google play edition ruu? If so, the phone was repartitioned, and sense will no longer "fit" on the system partition. There's a way to deal with that if that's the case...
Click to expand...
Click to collapse
I flashed the one found at the post: [RUU] att ruu 1.58.502.1 posted
Hmm.. Not sure what to suggest in that case. I'm not very familiar with the whole RUU thing myself...
Sent from my Nexus 7 using Tapatalk
Download the ota update. Extract the firmware.zip from it but don't extract firmware.zip. boot to fastboot.
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Do it again
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
Fastboot flash recovery twrp.img
Fastboot erase cache
Load recovery
Wipe, advanced wipe
Select dalvik, cache, data, system, internal. Wipe.
Put Rom on ext sd card or
Adb push Rom.zip /sdcard/
Install zip this will obviously erase everything on your phone.
Click thanks.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
ricm68 said:
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
Click to expand...
Click to collapse
You don't need to repair. You just need to troubleshoot. You are throwing the baby out with the bath water, if you go for a hardware repair for what is likely a software issue that is easy to resolve.
You also need to provide more details, and be specific as possible. Namely:
What recovery and version number?
S-on or off?
What exactly have you tried to flash?
Did you factory reset in bootloader?
Do you have working adb?
What happened when you ran the RUU?
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back. They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Thanks so much for your help.
ricm68 said:
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back. They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Thanks so much for your help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
You wont need the whole thing but some of it might pertain to you
ricm68 said:
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back.
Click to expand...
Click to collapse
I've already asked what happened when you ran the RUU, and you didn't answer. Any error messages, etc.? This is very critical information, so its hard to help when you don't provide the answers requested (especially this one).
RUU is meant to recover the device in most cases. So if it didn't work, its very posible you have a fundamental USB connectivity issue. What response do you get when you type the adb command:
adb devices
What happens when you try to install recovery or a stock ROM? You need to give more information and specifics if you really want help.
And "don't know how many things" is not meaningful information. You need to list all the things you tried, and the results. Again, the lack of specific info makes it hard to help. I literally typed more asking you questions, than you bothered typing the answers. This does not bode well if you really want help.
You did not even answer all the questions I asked:
- What exactly have you tried to flash? (list the ROMs)
- Did you factory reset in bootloader?
ricm68 said:
They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Click to expand...
Click to collapse
Who is "they"? Again, you are being too vague.
I am personally more familiar with TWRP, so I would advise staying with that if you want help from me. Nothing against CWM. But again, its just what I'm more familiar with.
redpoint73 said:
I've already asked what happened when you ran the RUU, and you didn't answer. Any error messages, etc.? This is very critical information, so its hard to help when you don't provide the answers requested (especially this one).
RUU is meant to recover the device in most cases. So if it didn't work, its very posible you have a fundamental USB connectivity issue. What response do you get when you type the adb command:
adb devices
What happens when you try to install recovery or a stock ROM? You need to give more information and specifics if you really want help.
And "don't know how many things" is not meaningful information. You need to list all the things you tried, and the results. Again, the lack of specific info makes it hard to help. I literally typed more asking you questions, than you bothered typing the answers. This does not bode well if you really want help.
You did not even answer all the questions I asked:
- What exactly have you tried to flash? (list the ROMs)
- Did you factory reset in bootloader?
Who is "they"? Again, you are being too vague.
I am personally more familiar with TWRP, so I would advise staying with that if you want help from me. Nothing against CWM. But again, its just what I'm more familiar with.
Click to expand...
Click to collapse
I Hi, thanks a lot. I did the factory reset from bootloader and tried to install Android_Revolution_HD-One_M8_5.0 and after doing the process it returns failed. Also One_M8_1.54.401.10_odexed and Jmz_M8_StockRootedOdex-ATT and I just tried with cyanogenmod 11. While I installed this in twrp recovery it said failed but when I reboo0ted in stared loading. I installed gapps and now my phone is working at least. But I still can't flash a snse rom or a gpe rom because it fails in twrp.
That's about all I can tell you. Oh, and I see it's in android 4.4.4.
ricm68 said:
I Hi, thanks a lot. I did the factory reset from bootloader and tried to install Android_Revolution_HD-One_M8_5.0 and after doing the process it returns failed. Also One_M8_1.54.401.10_odexed and Jmz_M8_StockRootedOdex-ATT and I just tried with cyanogenmod 11. While I installed this in twrp recovery it said failed but when I reboo0ted in stared loading. I installed gapps and now my phone is working at least. But I still can't flash a snse rom or a gpe rom because it fails in twrp.
That's about all I can tell you. Oh, and I see it's in android 4.4.4.
Click to expand...
Click to collapse
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
redpoint73 said:
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
Click to expand...
Click to collapse
The phone was working ok but suddenly wifi wouldn't turn on and mobile network stopped again!!!
I tried to intall android revolution but when it gets to installing the apps is says "set_perm: some changes failed". I click next and reboot and it just takes me back to recovery
redpoint73 said:
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
Click to expand...
Click to collapse
I did the factory reset from within cyanogenmod and it didn't wipe it. It restarted back to cyanogenmod. I copied andoid revolution to my internal memory and try to install from there.
ricm68 said:
The phone was working ok but suddenly wifi wouldn't turn on and mobile network stopped again!!!
I tried to intall android revolution but when it gets to installing the apps is says "set_perm: some changes failed". I click next and reboot and it just takes me back to recovery
Click to expand...
Click to collapse
You need to try the things I've suggested. I've made some definitive recommendations, and you seem to have ignored them. Honestly, I don't see a point in trying to help anymore, if you don't read what I'm taking the time to post; or you don't try what I've suggested.
Worst case is RUU and start over (install custom recovery again, etc.). But again, I have no idea what happened when you tried to RUU since you still haven't answered that.
You aren't going to make any progress, if you keep ignoring the advice that is given to you.
I'm doing what you told me!!!
I reinstalled twrp and tried but it failed again. Believe me, I've been doing what you suggested.
Can you please give me the steps to RUU and what ruu file to download and use. I really appreciate all you're doing for me and the time you are taking to help.
Sent from my One M8 using XDA Premium 4 mobile app
I was able to install cyanogen mod again and I am using the phone but I want to install sense again.
Sent from my One M8 using XDA Premium 4 mobile app
I know there has been many threads giving explicit instructions on how to unlock bootloader, gain s-off, and install TWRP recovery. But I am having problems/questions that no one (at least of what I've read) has encountered. I will try and make this clear for y'all but bear with me. Before I start just let it be known that I DO HAVE my bootloader unlocked. I ended up going to a cell phone repair place and paying a small fee to get my bootloader unlocked.
1. Do I need to gain s-off to be able to root and install TWRP recovery?
I say this because the I have tried the has00n application to unlock bootloader, gain s-off, root, and install TWRP recovery, but I ran into problems with my computer recognizing my device. I had all the necessary files downloaded (at least to my knowledge) but it honestly just wouldn't recognize my device.
2. If I do not need to gain s-off to install TWRP recovery and install a custom ROM (I'm going to be installing Cyanogenmod), how do I go about doing that?
Honestly I'm so fed up with this that I just want to sell this phone and get another one, all I want to do is get Cyanogenmod on this phone but it's so immensely difficult.
Please help me! I have been trying to get this accomplished for so long but I feel like because this phone is older all the info about how to root and gain s-off is outdated.....
All of your help is greatly appreciated!!
You shouldn't need s-off for installing a custom rom. That's for tinkering with model id and scary stuff like that. I'm not sure what that tool is but I only know of one way to get s-off, and that's sunshine s-off.
As for rooting, when you install a custom rom via twrp or cwm, it will typically ask you if you'd like to root your phone AFTER installing the rom, but BEFORE you restart the first time. So the process should be:
Unlock
Install twrp or cwm
Wipe and factory reset
Install rom
Once completed, phone will prompt if you want to restart
Select YES to root on restart
And then wait for the phone to reboot! (it'll take a little while first time)
After the boot, it'll probably ask you to install superSU, which is the root manager app. If it doesn't, find it in the play store and you're set.
Sent from my HTC One_M8 using Tapatalk
shoe-jitsu said:
You shouldn't need s-off for installing a custom rom. That's for tinkering with model id and scary stuff like that. I'm not sure what that tool is but I only know of one way to get s-off, and that's sunshine s-off.
As for rooting, when you install a custom rom via twrp or cwm, it will typically ask you if you'd like to root your phone AFTER installing the rom, but BEFORE you restart the first time. So the process should be:
Unlock
Install twrp or cwm
Wipe and factory reset
Install rom
Once completed, phone will prompt if you want to restart
Select YES to root on restart
And then wait for the phone to reboot! (it'll take a little while first time)
After the boot, it'll probably ask you to install superSU, which is the root manager app. If it doesn't, find it in the play store and you're set.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply. So as of right now I am using the fastboot adb to control my phone from the command prompt on the computer, but there is a problem. When I try and flash the custom recovery (either TWRP or CWM) it says that the files are unrecognizable, so they're pretty much corrupted. I honestly don't know that to do. I know I can achieve root if I just get either one of these recoveries to flash but it seems that all the files for the htc one m8 TWRP and CWM are corrupted. What are you suggestions at this point? The fastboot iadb is working perfect I just need a non-corrupted recovery file and I'm searching around the internet withno luck of finding one. Is there one that you can attest to working? If so that would be amazing. Again, thanks for your help, hopefully we can get this sorted out!
Hmm, do you have the latest version of twrp? Sometimes older versions don't install, I would try to see what version of twrp htc one m8 users are using, I'm not by my computer right now so I'm not sure. I also know that twrp works better on htc one for some reason, I've never found a version of cwm that works on my htc one. Make sure you are using the proper install command to install it too, I think it's fastboot flash recovery FILENAME.IMG
If all else fails, all I can think of at this point is that you got a bad download or something ?
Sent from my HTC One_M8 using Tapatalk
shoe-jitsu said:
Hmm, do you have the latest version of twrp? Sometimes older versions don't install, I would try to see what version of twrp htc one m8 users are using, I'm not by my computer right now so I'm not sure. I also know that twrp works better on htc one for some reason, I've never found a version of cwm that works on my htc one. Make sure you are using the proper install command to install it too, I think it's fastboot flash recovery FILENAME.IMG
If all else fails, all I can think of at this point is that you got a bad download or something
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yeah I've been trying to use the most current version of twrp and it didn't work. I ended up trying past versions and those didn't work either. The fastboot command i am using is the same as the one you stated. There's just a problem with the files. I'm beyond frustrated but really thank you for your help. When you're by your computer can you please send me the twrp version you have, it would be much appreciated.
flapjackSam said:
Yeah I've been trying to use the most current version of twrp and it didn't work. I ended up trying past versions and those didn't work either. The fastboot command i am using is the same as the one you stated. There's just a problem with the files. I'm beyond frustrated but really thank you for your help. When you're by your computer can you please send me the twrp version you have, it would be much appreciated.
Click to expand...
Click to collapse
Can you copy and paste your command window to this thread? It would help to see the exact error outputting. You can highlight and right click to copy anything from command window.
flapjackSam said:
Yeah I've been trying to use the most current version of twrp and it didn't work. I ended up trying past versions and those didn't work either.
Click to expand...
Click to collapse
Is the phone currently on Lollipop, or otherwise? You can't know what version TWRP is correct, without this info. Current TWRP (2.8.7.0) won't work if the phone is on older OS version. Vice versa, if the phone is currently on Lollipop, older versions of TWRP (I believe older than 2.8) won't work. You have to flash the specific TWRP version that matches your OS version. Guessing which TWRP version to flash is not the right way to go about this.
Also, you need to tell us the actual TWRP version number you got, and where you downloaded it from. I've seen quite a few instances where folks thought they had the "most recent" version, but in fact they weren't even close. Its always best to be specific as possible, and provide all the details when getting help here.
Additionally, go into Settings (or do getvar all), and tell us the software number. If you got the Stagefright patch, it might be screwing up install of TWRP as well.
flapjackSam said:
The fastboot command i am using is the same as the one you stated. There's just a problem with the files..
Click to expand...
Click to collapse
Again, just saying you used the "same" command isn't enough. A single wrong character, wrong file name, wrong path will cause the command to fail. As the previous response requested, please cut/paste, or better yet post a screenshot of your command prompt window, so we can see the exact command syntax, and the specific error message.
I can virtually guarantee that as long as you downloaded the file direct from the TWRP website, and tried downloading (and flashing) it more than once (to eliminate the possibility of corruption during file transfer); that the issue is almost certainly pilot error.
Somehow I'm a little frusrated. I've brought my phone since today. So it is currently on Lollipop. There is no Power in setting to uncheck Fastboot. Is there any way I can root my phone?
MistakenUtopia said:
Somehow I'm a little frusrated. I've brought my phone since today. So it is currently on Lollipop. There is no Power in setting to uncheck Fastboot. Is there any way I can root my phone?
Click to expand...
Click to collapse
Press and hold the power button until is hard reboots, then hold vol down as well. You should go to boot loader before the HTC screen pops up.
Back Up!
Just a reminder, after you install TWRP, boot into recovery (TWRP) and create a backup file saved to your SD card first before trying to install a new ROM!
Always can restore if things go wrong or you don't like it.
:fingers-crossed:
Hello everyone this is my fist guide so be kind with the formatting, i will get better as I post more. I am writing this guide, because like you, the reader, I had installed lineageOS 14.1 and set up the phone and realized there was encryption on it, and with that tried to wipe it in twrp just to find out that it only wiped the encryption key, but not the encryption itself. Don't panic, it isn't all your fault, XD. Stay calm, the last thing you need is to be freaking out, flashing random zips in hopes of fixing it. I will give credit to all of the developers whose tools i am linking at the bottom.
Now that the introductions are out of the way, time for the complimentary dose of warning.
WARNING: Doing this won't guarantee that this will fix it, as every situation can vary. I am not responsible for any bricked devices, thermal reactors coming from your phone after this, or modding before it was cool.
Assuming you can still get into fastboot first you need to gather these files if you don't have them yet.
- Minimal adb and fastboot on windows after installing just drag to desktop to add files to it
- Qualcomm fastboot drivers for axon7tool.exe and for fastboot and adb
- TWRP 3.0.4-1 official for Axon 7
- B29 rollback modded zip on the second tab
- Nougat modem and bootstack
- Tenfar's axon7root.exe (just in case you can't use fastboot. that's what i used because i don't know how to use axon7tool.exe)
- Fastboot image to get fastboot working again flash it in twrp after getting twrp installed again through axon7root.exe
- Some time because this will likely take an hour of your time, assuming you have the drivers and files already downloaded, longer if not and slow internet.
- LineageOS 14.1
- GAPPS 7.1.1 ARM 64
- almost forgot, you also need a microsd card to store the files because we will be wiping your entire internal with this, so back up your lovely dank memes or forever hold the loss.
Step 0.5. if you don't have fastboot working flash the bootloader unlock file by drakenfx to get it working again. if you don't have twrp for whatever reason go to the guide for axon7root.exe linked above and reboot to edl mode by holding all buttons down and have your phone connected to computer to know you are there. there won't be a vibration to let you know, just your computer telling you it has a connected device. now flash twrp, by first renaming the recovery to recovery.img and putting it in the adb folder along with the the root exe and do 'axon7root.exe -p (insert your com number listed in device manager) -r' (without the ' obviously) and it should send the recovery. if it doesn't see your device. make sure you have the drivers installed and make sure you have put down your com number where i left the () at
Step 1. assuming your device boots to this beautiful screen. you need to go back to twrp and drag the B29 zip from your computer to your external sd card from mtp and go to mount and mount system read-only this is very important.
Step 2. flash the B29 modded and let it go through. this will take a few minutes. if the progress bar automatically jumps to the end, you didn't go read only.
Step 3. after it finishes reboot into system and let it set up your system, you can skip through because we will be resetting again anyhow.
Step 4. reboot back to recovery. you can do this by using that pesky bl unlocked message by pressing up on volume as soon as it shows and selecting recovery. there you can see you have stock recovery, don't panic this is what we need. select wipe data factory reset and let it do it
Step 5. go back and skip set up again and reboot to bootloader where you can now 'fastboot flash recovery recovery.img' to get back twrp.
Step 6. flash the nougat bootstack and modem i had you download. after flashing that, go to wipe: Advanced wipe. Select Dalvik, system, data, cache and swipe to wipe. this will format it as ext4 which is what is required to get to lineageOS
Step 7. flash lineageos 14.1 and your gapps category and wait to let it finish. Note, you don't have to flash the modem more than once after flashing lineageos, even for updating. just after leaving B29
Step 8. reboot to make sure your encryption problem is not there
Step 9. set up phone and profit.
If you have done everything right, you shouldn't have bricked and should be back to lineageos 14.1 with no further problems. If you skipped around and got yourself bricked, congratulations because i am not the best at fixing problems, and i can try to help, but you will be at the mercy of the Best devs this community has to offer.
Now to the part where I thank all the Devs who, without their tireless time and effort, would not have made this guide possible and development into this phone in the first place. @Unjustified Dev for the lineageOS build i use as my daily driver for now; you rock dude. ^^
@DrakenFX oh god where do i begin. for the bl unlock zip, B29 modded ota, inspiration to the rest of the community, etc.
@tenfar for the axon7root.exe tool used
@sixohtew for his constant help and advice with not only this guide, but with teaching me to build android. if you are interest in learning how to compile android for any device, he can probably help. he has a very fair deal and is amazing at what he does.
Thank you all for your copious hours of time spent in the building of each great tool and to the community as a whole. Everyone, these guys are amazing, even if i have only talked to one of them. Be sure to stop by and donate.
If i have left anyone's name out, please hit me up and i will add you to the credits, and to that i apologize.
Happy flashing!
I read through your guide several times. I'm missing the point here. At which step does the decryption get removed?
gpz1100 said:
I read through your guide several times. I'm missing the point here. At which step does the decryption get removed?
Click to expand...
Click to collapse
Sorry for delayed response, it gets removed when you do the factory reset in stock recovery. For some reason TWRP can't remove it from /data in nougat but stock recovery can in B29.
Wipe->Format Data in TWRP removes all encryption from /data and /sdcard. Did you try that before reinstalling the stock recovery? I've had weird experiences in the past with stuck encryption.
QuantumFluxx said:
Wipe->Format Data in TWRP removes all encryption from /data and /sdcard. Did you try that before reinstalling the stock recovery? I've had weird experiences in the past with stuck encryption.
Click to expand...
Click to collapse
I did try it. It doesn't wipe it because there is a bug with TWRP for our phone. I would wipe and even format data and it wouldn't work. If you go to the official TWRP thread it even warns you that if you have encryption to not wipe. We had a dev who wiped and it got rid of the encryption key and not the encryption, like what happened to me. I tried to wipe so many times and had to revert. Long process but I got my phone to work again
Rip me
So I was bricked to the point where I was able to access TWRP and if I flashed any ROM, even after formatting data, I would reach a Decryption unsuccessful screen on my A2017U. I followed the guide from step 0.5, since fastboot was not working. After flashing the bootloader unlock file via TWRP, I was not able to access anything, further bricking the device. It boots within a second to a black screen, and reboots to it if I hold the power button or any combination for recovery.etc. I can not go to EDL mode; Axon7tool detects it though when it is in this state, and is able to send files successfully. However, it still stays in this black screen. Is there any way to get back to a functioning phone at this point?
Edit: It is apparently always in EDL? It shows up and is identified by my PC as QUSB_BULK...
navsterama said:
So I was bricked to the point where I was able to access TWRP and if I flashed any ROM, even after formatting data, I would reach a Decryption unsuccessful screen on my A2017U. I followed the guide from step 0.5, since fastboot was not working. After flashing the bootloader unlock file via TWRP, I was not able to access anything, further bricking the device. It boots within a second to a black screen, and reboots to it if I hold the power button or any combination for recovery.etc. I can not go to EDL mode; Axon7tool detects it though when it is in this state, and is able to send files successfully. However, it still stays in this black screen. Is there any way to get back to a functioning phone at this point?
Edit: It is apparently always in EDL? It shows up and is identified by my PC as QUSB_BULK...
Click to expand...
Click to collapse
Can you still get into recovery with power & vol+? and what happened as soon as you flashed the zip?
twilighttony said:
Can you still get into recovery with power & vol+? and what happened as soon as you flashed the zip?
Click to expand...
Click to collapse
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
navsterama said:
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
Click to expand...
Click to collapse
I am not sure what happened to that, were you originally on B15? i was simply on the modem/bootstack which allowed me to succeed in flashing that file. that could be a variable. i will be sure to look into a tool ive heard of called miflash which works through edl mode to unbrick.
navsterama said:
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
Click to expand...
Click to collapse
try this.
twilighttony said:
I am not sure what happened to that, were you originally on B15? i was simply on the modem/bootstack which allowed me to succeed in flashing that file. that could be a variable. i will be sure to look into a tool ive heard of called miflash which works through edl mode to unbrick.
Click to expand...
Click to collapse
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
navsterama said:
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
Click to expand...
Click to collapse
ok that does make sense as to why it failed. i was on the modded modem file that allowed me to install los
twilighttony said:
ok that does make sense as to why it failed. i was on the modded modem file that allowed me to install los
Click to expand...
Click to collapse
Wait...in terms of the bootstack I was also on the modded one for LOS 14.1. However, it was when the last unofficial build came out (Feb 3rd???). I tried to clean flash LOS Weekly today and thats when I ran into the dilemma of the decryption. Idk why I said yes for being on B15, for some reason that translated to generally Nougat bootstack in my head. My bad, OP.
---------- Post added at 10:47 PM ---------- Previous post was at 10:30 PM ----------
navsterama said:
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
Click to expand...
Click to collapse
Unbricked, booted up, now its on the "beautiful" screen. Thanks!
twilighttony said:
try this.
Click to expand...
Click to collapse
This is posted in the dev section. No need for external linkage.
navsterama said:
Wait...in terms of the bootstack I was also on the modded one for LOS 14.1. However, it was when the last unofficial build came out (Feb 3rd???). I tried to clean flash LOS Weekly today and thats when I ran into the dilemma of the decryption. Idk why I said yes for being on B15, for some reason that translated to generally Nougat bootstack in my head. My bad, OP.
---------- Post added at 10:47 PM ---------- Previous post was at 10:30 PM ----------
Unbricked, booted up, now its on the "beautiful" screen. Thanks!
Click to expand...
Click to collapse
glad that worked. perhaps i will edit the guide to where fastboot is added at the end as an extra. seems that if we at least have twrp we can go from there. do you still have an unlocked bl?
lafester said:
This is posted in the dev section. No need for external linkage.
Click to expand...
Click to collapse
will remember for future reference. thanks
lafester said:
This is posted in the dev section. No need for external linkage.
Click to expand...
Click to collapse
At least the poster of the blog gives credit to the original author and thread.
The method referenced at the blog is confusing though. If one is in a bricked state (edl only), they can't access developer options or even boot into android.
gpz1100 said:
At least the poster of the blog gives credit to the original author and thread.
The method referenced at the blog is confusing though. If one is in a bricked state (edl only), they can't access developer options or even boot into android.
Click to expand...
Click to collapse
If you are in edl only with an unlocked bootloader than the part of enabling bl unlock won't apply.
twilighttony said:
If you are in edl only with an unlocked bootloader than the part of enabling bl unlock won't apply.
Click to expand...
Click to collapse
Right, I understand that, but the person reading your blog won't, and thus the confusion.
This guide really needs to be stickied or higher up. Restarted my phone yesterday and it randomly got encrypted upon booting. Was locked out of everything and no keyboard was popping up to be able to put in a PIN or Password. This guide saved me. Thank you.