Related
I used the appropriate nandroid backup to restore the stock file system and restored the stock recovery (from this thread). But now the "tampered" banner is back (I had removed it), and I can't get root without screwing with the file system again (I can't find any temp root for the M8). Also, the stock recovery seems broken as it does nothing. I just see the red exclamation point thing, and I swear it used to do something before when I moved the volume buttons.
How do I go back to stock WHILE keeping "tampered" removed? And can I get rid of "unlocked"? I need to return this phone (poor coverage) so I am trying to avoid issues with the carrier.
Anyone have any idea?
quinxy said:
I used the appropriate nandroid backup to restore the stock file system and restored the stock recovery (from this thread). But now the "tampered" banner is back (I had removed it), and I can't get root without screwing with the file system again (I can't find any temp root for the M8). Also, the stock recovery seems broken as it does nothing. I just see the red exclamation point thing, and I swear it used to do something before when I moved the volume buttons.
How do I go back to stock WHILE keeping "tampered" removed? And can I get rid of "unlocked"? I need to return this phone (poor coverage) so I am trying to avoid issues with the carrier.
Anyone have any idea?
Click to expand...
Click to collapse
Which backup is the apporiate one for sprint? I need to revert to stock and cant figure out which back up to use
quinxy said:
I used the appropriate nandroid backup to restore the stock file system and restored the stock recovery (from this thread). But now the "tampered" banner is back (I had removed it), and I can't get root without screwing with the file system again (I can't find any temp root for the M8). Also, the stock recovery seems broken as it does nothing. I just see the red exclamation point thing, and I swear it used to do something before when I moved the volume buttons.
How do I go back to stock WHILE keeping "tampered" removed? And can I get rid of "unlocked"? I need to return this phone (poor coverage) so I am trying to avoid issues with the carrier.
Anyone have any idea?
Click to expand...
Click to collapse
soff, unlock bootloader, flash stock rom and recovery, boot into twrp "don't flash recovery" flash supersu in twrp, load system, use soff to remove tampered banner, use soff to relock boot loader so it doesn't say relocked, load supersu and remove root, restore factory settings
an0ther said:
soff, unlock bootloader, flash stock rom and recovery, boot into twrp "don't flash recovery" flash supersu in twrp, load system, use soff to remove tampered banner, use soff to relock boot loader so it doesn't say relocked, load supersu and remove root, restore factory settings
Click to expand...
Click to collapse
You are awesome! Thanks, that's just the list of steps I needed.
quinxy said:
You are awesome! Thanks, that's just the list of steps I needed.
Click to expand...
Click to collapse
No problem
which one is the Verizon stock recovery? I cant figure it out
trikotret said:
which one is the Verizon stock recovery? I cant figure it out
Click to expand...
Click to collapse
Check the verizon forums. They have it there.
an0ther said:
soff, unlock bootloader, flash stock rom and recovery, boot into twrp "don't flash recovery" flash supersu in twrp, load system, use soff to remove tampered banner, use soff to relock boot loader so it doesn't say relocked, load supersu and remove root, restore factory settings
Click to expand...
Click to collapse
Does S-OFF become S-ON again after factory reset or how do you get it to be S-ON again?
Fastboot oem writesecureflag 3
Sent from my HTC One_M8 using XDA Free mobile app
quinxy said:
You are awesome! Thanks, that's just the list of steps I needed.
Click to expand...
Click to collapse
Did that remove the red text on the splash screen too?
Sent from my HTC One_M8 using XDA Free mobile app
How do i relock the bootloader without that it says relocked? Fastboot oem lock gives me relocked.
Nevermind, found it.
http://forum.xda-developers.com/showthread.php?t=2708571
Hey guys !
As the title suggests. What does that mean? and how do i revert to official locked ?
I have s-on and have rooted and installed twrp, and cwm afterwards. And decided to go back to stock( because the current methods of changing to s-off are not working) by flashing through cwm a RUU backup. And flashing the stock recovery afterwards. I have also declined root access when prompted by cwm after RUU install.
What can I do to return to 100% stock ?
After entering fastboot The first text is ***MODIFIED*** and at os there is blank space. I want to return my phone to out of the box state.
sherbibv said:
Hey guys !
As the title suggests. What does that mean? and how do i revert to official locked ?
I have s-on and have rooted and installed twrp, and cwm afterwards. And decided to go back to stock( because the current methods of changing to s-off are not working) by flashing through cwm a RUU backup. And flashing the stock recovery afterwards. I have also declined root access when prompted by cwm after RUU install.
What can I do to return to 100% stock ?
After entering fastboot The first text is ***MODIFIED*** and at os there is blank space. I want to return my phone to out of the box state.
Click to expand...
Click to collapse
You need S-OFF. With S-ON you cannot remove the 'MODIFIED' text.
XSL-FO said:
You need S-OFF. With S-ON you cannot remove the 'MODIFIED' text.
Click to expand...
Click to collapse
I don't just want to remove the text. I want the whole rom to be brand new and stock. And LOCKED
sherbibv said:
I don't just want to remove the text. I want the whole rom to be brand new and stock. And LOCKED
Click to expand...
Click to collapse
You must S-OFF. Remove texts, unroot, relock bootloader and go S-ON.
sherbibv said:
I don't just want to remove the text. I want the whole rom to be brand new and stock. And LOCKED
Click to expand...
Click to collapse
Doesn't matter, you can restore stock ROM until the cows come home. You won't be able to change the modified flag in the bootloader. You need S-OFF to change the text to "official" just like you'll need S-OFF to change the bootloader "locked" text to "Locked" and not "Relocked" if you relock the bootloader.
You will NOT be able to have it show the same way it was "out of box" if you do NOT have S-OFF.
So the only way is to buy the s-off service with 25$ right?
BerndM14 said:
Doesn't matter, you can restore stock ROM until the cows come home. You won't be able to change the modified flag in the bootloader. You need S-OFF to change the text to "official" just like you'll need S-OFF to change the bootloader "locked" text to "Locked" and not "Relocked" if you relock the bootloader.
You will NOT be able to have it show the same way it was "out of box" if you do NOT have S-OFF.
Click to expand...
Click to collapse
Sorry for the noob question, but what does modified imply ? What does it mean exactly?
sherbibv said:
Sorry for the noob question, but what does modified imply ? What does it mean exactly?
Click to expand...
Click to collapse
It means unlocked botloader and of course rooted. It means that you have tampered with the software.
XSL-FO said:
It means unlocked botloader and of course rooted. It means that you have tampered with the software.
Click to expand...
Click to collapse
But I can continue running like this without a problem right?
It won't cause any instability ?
And also, can I install OTAs?
sherbibv said:
But I can continue running like this without a problem right?
It won't cause any instability ?
Click to expand...
Click to collapse
Any at all. You can run it safely like this.
XSL-FO said:
Any at all. You can run it safely like this.
Click to expand...
Click to collapse
what about OTAs?
sherbibv said:
what about OTAs?
Click to expand...
Click to collapse
You will be able to recieve OTA's but if you want to install them you will need to go back to stock recovery. Easy. After OTA flash again a custom one.
XSL-FO said:
You will be able to recieve OTA's but if you want to install them you will need to go back to stock recovery. Easy. After OTA flash again a custom one.
Click to expand...
Click to collapse
I'm currently on stock recovery
sherbibv said:
I'm currently on stock recovery
Click to expand...
Click to collapse
It's ok. Keep it if you want.
sherbibv said:
I'm currently on stock recovery
Click to expand...
Click to collapse
Then you're fine.
Rooted, S-OFF, Modified status, none of those will prevent OTA updates. You MUST have stock reocovery and stock ROM for OTA updates i.e No changes to system files, no deleted apps, no xposed framework.
If all those are stock you can get and install OTA no problem. Don't even have to relock the bootloader for it.
BerndM14 said:
Then you're fine.
Rooted, S-OFF, Modified status, none of those will prevent OTA updates. You MUST have stock reocovery and stock ROM for OTA updates i.e No changes to system files, no deleted apps, no xposed framework.
If all those are stock you can get and install OTA no problem. Don't even have to relock the bootloader for it.
Click to expand...
Click to collapse
I had Xposed and still I was able to upgrade.
Thanks allot guys !
Have e great day ! :good:
sherbibv said:
Thanks allot guys !
Have e great day ! :good:
Click to expand...
Click to collapse
You too. Good luck.
I have an international stock HTC One M9. CID is: HTC__621 and firmware version: 210.709.1 - I've already found the stock recovery for 210.709.1 - I'm looking to install a custom ROM, but I may want to go back to stock later on. I found a TWRP stock backup for 210.709.1, but because I am S-ON, will I not have to manually flash the boot.img? I used winrar to look into the TWRP backup, and I could not find a boot.img. So, my question is: if I flash the TWRP backup using TWRP, will the boot.img automatically get flashed?
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
mrbtree98 said:
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
Click to expand...
Click to collapse
Should I rename this to: "boot.img"? And then, use command: " fastboot flash boot boot.img"?
mrbtree98 said:
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
Click to expand...
Click to collapse
There's no "boot.emmc.win" within the archive? I can't find it...
arif9m9 said:
Should I rename this to: "boot.img"? And then, use command: " fastboot flash boot boot.img"?
Click to expand...
Click to collapse
Some weeks ago I was told that all newer phones than the HTC One M7 are able to flash boot images with TWRP even if they are S-ON. (I wasn't able to verify that since my phone is S-OFF.) So there should be no need to rename and manually flash the boot image if it's already inside the backup.
arif9m9 said:
There's no "boot.emmc.win" within the archive? I can't find it...
Click to expand...
Click to collapse
You can find the needed boot image in my signature.
Flippy498 said:
You can find the needed boot image in my signature.
Click to expand...
Click to collapse
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
arif9m9 said:
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
Click to expand...
Click to collapse
If you use the backup from my signature you only need to follow the instructions on the first page of my google sheet to get back to stock.
Be warned: Since Android 5.1 you should only relock the bootloader if you are completely sure that your phone is able to boot to system and that you ticked the new option that allows a bootloader unlock (can be found in the developers options). Many users already got stuck with a non-booting phone that cannot be re-unlocked because they didn't fulfill these requirements. (Sidenote: If you only want to get back to stock to install new OTAs you don't need to relock your bootloader.)
Besides I read that some people stated that the AOSP roms of the M9 messed up their LTE reception (so that LTE was even unusable on other custom roms or stock rom). I don't know whether this problem is already fixed. Some weeks passed since I read about that problem so I suggest you to read the corresponding threads before you start flashing.
arif9m9 said:
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
Click to expand...
Click to collapse
There is no need to flash the boot.img separately on this phone.
As noted DO NOT RELOCK unless you have ticked that "allow oem unlocking" option first. I cannot stress this enough.
Also, no AOSP rom currently has a working camera.
iElvis said:
There is no need to flash the boot.img separately on this phone.
As noted DO NOT RELOCK unless you have ticked that "allow oem unlocking" option first. I cannot stress this enough.
Also, no AOSP rom currently has a working camera.
Click to expand...
Click to collapse
My phone is S-ON, won't I have to flash the boot.img via fastboot?
arif9m9 said:
My phone is S-ON, won't I have to flash the boot.img via fastboot?
Click to expand...
Click to collapse
Flippy498 said:
Some weeks ago I was told that all newer phones than the HTC One M7 are able to flash boot images with TWRP even if they are S-ON.
Click to expand...
Click to collapse
iElvis said:
There is no need to flash the boot.img separately on this phone.
Click to expand...
Click to collapse
No, it's not needed. The only exceptions are backups that don't contain a boot image (like mine for example). That's why I created the google sheet with the instructions.
Flippy498 said:
No, it's not needed.
Click to expand...
Click to collapse
But, when installing custom ROMS, I'll definitely have to use the fastboot command to flash the boot image, right?
arif9m9 said:
But, when installing custom ROMS, I'll definitely have to use the fastboot command to flash the boot image, right?
Click to expand...
Click to collapse
No.
Flippy498 said:
No.
Click to expand...
Click to collapse
But, I'm S-ON....
arif9m9 said:
But, I'm S-ON....
Click to expand...
Click to collapse
It hasn't been an S-on restriction since the M7.
iElvis said:
It hasn't been an S-on restriction since the M7.
Click to expand...
Click to collapse
Does that mean I can flash RUUs even if I'm S-ON?
arif9m9 said:
Does that mean I can flash RUUs even if I'm S-ON?
Click to expand...
Click to collapse
For your CID/MID, yes.
iElvis said:
For your CID/MID, yes.
Click to expand...
Click to collapse
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
arif9m9 said:
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
Click to expand...
Click to collapse
It depends. If you have a current RUU for your phone (i.e., you don't need to downgrade), you can run it S-on, as that's what it's for.
But if you need to downgrade because the only RUU is an earlier version, yes you do need s-off.
S-off also allows you to go back to LOCKED instead of RELOCKED.
iElvis said:
It depends. If you have a current RUU for your phone (i.e., you don't need to downgrade), you can run it S-on, as that's what it's for.
But if you need to downgrade because the only RUU is an earlier version, yes you do need s-off.
S-off also allows you to go back to LOCKED instead of RELOCKED.
Click to expand...
Click to collapse
When going back to stock, at which stage should I relock my bootloader?
arif9m9 said:
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
Click to expand...
Click to collapse
Because if you follow these guides your phone will state "locked" instead of "relocked" at the end. And that is only possible with S-OFF. Besides with S-ON you can only use RUUs with the same firmware version as your phone (or newer RUUs)*.
*Actually downgrades seem to be possible, too, but as far as I know only if the two first numbers of the firmware versions before and after the downgrade are the same. Like from 1.32.xxx.15 to 1.32.xxx.8 but not from 1.40 versions to 1.32 versions or from 2.xx versions to lower versions.
Edit: Looks like I didn't type fast enough.
I was messing about... as you do!!
I think I corrupted the boot img and my phone boots straight to the bootloader menu, no s-off, i want to go back to stock anyway to get my phone on N firmware.
My question is, do i have to oem re lock before I apply the RUU or has this changed since I last done this? or do I do it after or not at all?
\cheers
anarchyuk said:
I was messing about... as you do!!
I think I corrupted the boot img and my phone boots straight to the bootloader menu, no s-off, i want to go back to stock anyway to get my phone on N firmware.
My question is, do i have to oem re lock before I apply the RUU or has this changed since I last done this? or do I do it after or not at all?
\cheers
Click to expand...
Click to collapse
If you extract the ROM.zip from the RUU.exe, you should be able to flash that via the SDcard method without relocking your bootloader first.
Or maybe your volume key is stucked?
Sounds stupid but that happened once to me
xunholyx said:
If you extract the ROM.zip from the RUU.exe, you should be able to flash that via the SDcard method without relocking your bootloader first.
Click to expand...
Click to collapse
yeah ended up extracting them to the twrp folder although it started booting using that but it wouldnt accept my pin to decrypt, eventually got Lineage 14.1 running and then leedroid's rom and it decrypted fine.
All i wanted was to be able to use android pay ha
BrianKuo1853 said:
Or maybe your volume key is stucked?
Sounds stupid but that happened once to me
Click to expand...
Click to collapse
Not stupid perfectly possible but I managed to sort it, thanks for the response
Hello there,
After unlocking my bootloader, flashed a new recovery twrp I tried to enter the recovery mode. It keeps showing a red message saying "This build is for development purposes only" and after a while reboots to bootloader menu without allowing me to enter recovery mode. Any guesses?
Thank you in advance!
Which recovery version did you flash? And what did you do to enter recovery mode?
ordeniz said:
Which recovery version did you flash? And what did you do to enter recovery mode?
Click to expand...
Click to collapse
Hello,
It's the twrp-3.0.2-2-pme.
When phone is off, I push the volume down and the power button to enter to download mode, after that boot to bootloader and to recovery. That is when an HTC logo appears with this strange red message and after a while it reboots to bootloader mode.
Lothorin said:
Hello,
It's the twrp-3.0.2-2-pme.
When phone is off, I push the volume down and the power button to enter to download mode, after that boot to bootloader and to recovery. That is when an HTC logo appears with this strange red message and after a while it reboots to bootloader mode.
Click to expand...
Click to collapse
Try 3.1.1-0-pme.img .
https://eu.dl.twrp.me/pme/
ordeniz said:
Try 3.1.1-0-pme.img .
https://eu.dl.twrp.me/pme/
Click to expand...
Click to collapse
Ok thank you, I will try!!
Just a hint; after the reboot, it says "reboot reason: 0x776655aa", reboot message: RPM:APPS NS-WD!" - if that means smth..
What's your cid-mid number?
ordeniz said:
What's your cid-mid number?
Click to expand...
Click to collapse
CID: 11111111
MID: 2PS640000
Tried the new twrp and the problem persists..
Lothorin said:
CID: 11111111
MID: 2PS640000
Tried the new twrp and the problem persists..
Click to expand...
Click to collapse
Does download mode show that it is Unlocked for sure?
You may need to do the RUU for your exact model to get things right again.
Lothorin said:
CID: 11111111
MID: 2PS640000
Tried the new twrp and the problem persists..
Click to expand...
Click to collapse
This phone is new to you I assume since you stated that you've just unlocked the bootloader, but your CID is changed to SuperCID and that wouldn't be done without some previous modifications?
You have a Sprint device (according to your MID), so SuperCID is useless. You can only use Sprint firmware on a Sprint model.
What does it say next to "OS" in download mode? It should be x.xx.651.x
I would suggest you run the newest Sprint RUU. The RUU will wipe your phone, but since it's new to you that shouldn't matter. Plus unlocking the bootloader already wiped it.
Click on this link.
Scroll down to the "Manual System Update Instructions" and read them. The RUU download is at the end of the instruction.
After you've run the RUU, flash TWRP 3.1.1-0 again and it should work.
EDIT: I forgot to mention the red warning "This build is for development purposes only". That is nothing to worry about. You get it after you unlock the bootloader
michaelbsheldon said:
Does download mode show that it is Unlocked for sure?
You may need to do the RUU for your exact model to get things right again.
Click to expand...
Click to collapse
Yes it does.
I'll try to put the stock RUU again and flash directly the twrp, without unlocking the bootloader.
xunholyx said:
This phone is new to you I assume since you stated that you've just unlocked the bootloader, but your CID is changed to SuperCID and that wouldn't be done without some previous modifications?
You have a Sprint device (according to your MID), so SuperCID is useless. You can only use Sprint firmware on a Sprint model.
What does it say next to "OS" in download mode? It should be x.xx.651.x
I would suggest you run the newest Sprint RUU. The RUU will wipe your phone, but since it's new to you that shouldn't matter. Plus unlocking the bootloader already wiped it.
Click on this link.
Scroll down to the "Manual System Update Instructions" and read them. The RUU download is at the end of the instruction.
After you've run the RUU, flash TWRP 3.1.1-0 again and it should work.
EDIT: I forgot to mention the red warning "This build is for development purposes only". That is nothing to worry about. You get it after you unlock the bootloader
Click to expand...
Click to collapse
Thank you very much for your time,
So, if I get it right, I put the stock RUU again and without unlocking the bootloader (as I previously did), I will flash directly the twrp. Right?
Lothorin said:
Yes it does.
I'll try to put the stock RUU again and flash directly the twrp, without unlocking the bootloader.
Click to expand...
Click to collapse
Once unlocked, the bootloader remains unlocked forever or until you give Android tools command to relock.
Running the Sprint RUU will most likely fixxxx it...
And yes, after you have it running right, boot to download mode and flash the newer TWRP that someone here recommended.
Then root with SuperSU or Magisk v14 and above, or install a custom rom from great choices here.
Lothorin said:
Thank you very much for your time,
So, if I get it right, I put the stock RUU again and without unlocking the bootloader (as I previously did), I will flash directly the twrp. Right?
Click to expand...
Click to collapse
No. Leave the bootloader unlocked. You don't need to relock it, and it should remain unlocked after the RUU has run.
You can't flash TWRP with a locked bootloader
xunholyx said:
No. Leave the bootloader unlocked. You don't need to relock it, and it should remain unlocked after the RUU has run.
You can't flash TWRP with a locked bootloader
Click to expand...
Click to collapse
Ok ok, sorry but this is my first time with this kind of stuff, so... I will flash the twrp and then I will try to install the official unlocked ROM
Lothorin said:
Ok ok, sorry but this is my first time with this kind of stuff, so... I will flash the twrp and then I will try to install the official unlocked ROM
Click to expand...
Click to collapse
No need to be sorry.
Don't bother flashing TWRP first. When you run the RUU it will install the stock recovery and TWRP will get overwritten.
Run the RUU, then install TWRP after.
xunholyx said:
No need to be sorry.
Don't bother flashing TWRP first. When you run the RUU it will install the stock recovery and TWRP will get overwritten.
Run the RUU, then install TWRP after.
Click to expand...
Click to collapse
I put the stock SPRINT RUU, flashed the TWRP, wiped data, adb pushed the supersu.zip file into the phone and flashed it. After the flash was successful I reboot the system but it isn't setting. After the HTC logo on the starup it reboots automatically to bootloader.. :$
reboot reason: 0x776655aa
reboot message: KP: init PC:adsp_boot_store+0x2cc/0x368 LR:ad sp_boot_store+0x2cc/0x368
Lothorin said:
I put the stock SPRINT RUU, flashed the TWRP, wiped data, adb pushed the supersu.zip file into the phone and flashed it. After the flash was successful I reboot the system but it isn't setting. After the HTC logo on the starup it reboots automatically to bootloader.. :$
reboot reason: 0x776655aa
reboot message: KP: init PC:adsp_boot_store+0x2cc/0x368 LR:ad sp_boot_store+0x2cc/0x368
Click to expand...
Click to collapse
I'll send you a PM to ask for some info to check if your device is indeed a Sprint one. With SuperCID enabled (and s-off obviously), it's hard to tell what has been done to you phone.
Lothorin said:
CID: 11111111
MID: 2PS640000
Tried the new twrp and the problem persists..
Click to expand...
Click to collapse
Do you have custom recovery or stock?
---------- Post added at 08:29 AM ---------- Previous post was at 08:25 AM ----------
Here is a guide I found on web showing how to boot into recovery (Stock as well as Custom)
Rashmi9658 said:
Do you have custom recovery or stock?
---------- Post added at 08:29 AM ---------- Previous post was at 08:25 AM ----------
Here is a guide I found on web showing how to boot into recovery (Stock as well as Custom)
Click to expand...
Click to collapse
Hey,
I have already solved this problem, but thank you very much!
Now I have another one:
I put the stock SPRINT RUU (because my cell phone is a sprint unlocked), flashed the TWRP, wiped data, adb pushed the supersu.zip file into the phone and flashed it. After the flash was successful I reboot the system but it isn't setting. After the HTC logo on the starup it reboots automatically on bootloader.. :$
reboot reason: 0x776655aa
reboot message: KP: init PC:adsp_boot_store+0x2cc/0x368 LR:ad sp_boot_store+0x2cc/0x368
Lothorin said:
Hey,
I have already solved this problem, but thank you very much!
Now I have another one:
I put the stock SPRINT RUU (because my cell phone is a sprint unlocked), flashed the TWRP, wiped data, adb pushed the supersu.zip file into the phone and flashed it. After the flash was successful I reboot the system but it isn't setting. After the HTC logo on the starup it reboots automatically on bootloader.. :$
reboot reason: 0x776655aa
reboot message: KP: init PC:adsp_boot_store+0x2cc/0x368 LR:ad sp_boot_store+0x2cc/0x368
Click to expand...
Click to collapse
Seems like you wiped system.