Related
I successfully had Cyanogenmod installed, but now when I turn my phone on it stays stuck at the loading screen and goes back and forth to the HTC start up (the screen before the Cyanogen loading screen). I tried reverting back to stock using the RUU but it fails every. single. time. and there's nothing I can find that will help me at least get my phone back working.
Any help? My carrier is T-Mobile
moneyhbags said:
I successfully had Cyanogenmod installed, but now when I turn my phone on it stays stuck at the loading screen and goes back and forth to the HTC start up (the screen before the Cyanogen loading screen). I tried reverting back to stock using the RUU but it fails every. single. time. and there's nothing I can find that will help me at least get my phone back working.
Any help? My carrier is T-Mobile
Click to expand...
Click to collapse
Sounds like possibly you need to flash the boot.img on it. I think , a senior member will correct me, but if your S-On and rooted, you should do that , S-Off don't require the boot.img.
leesumm said:
Sounds like possibly you need to flash the boot.img on it. I think , a senior member will correct me, but if your S-On and rooted, you should do that , S-Off don't require the boot.img.
Click to expand...
Click to collapse
I don't know what S-On or S-Off means, but it's been like 20 minutes and it's now stuck at the HTC quietly brilliant screen.
I did do a back-up before I rooted it. I tried re-installing Cyanogenmod but the installer says my phone is unrecognizable.
edit: still stuck at Cyanogen loading screen =(
moneyhbags said:
I don't know what S-On or S-Off means, but it's been like 20 minutes and it's now stuck at the HTC quietly brilliant screen.
I did do a back-up before I rooted it. I tried re-installing Cyanogenmod but the installer says my phone is unrecognizable.
edit: still stuck at Cyanogen loading screen =(
Click to expand...
Click to collapse
S-ON or off means security is on or off, If you haven't done the mod to S-Off , your still stock S-On. To see for sure though , in the bootloader mode at the top it will say Tampered first line , then the second should say something like M7 ??? PVT ship. S-On
What recovery are you using? CWM or TWRP . Do you know or use ADB?
I just reread your OP and you said you RUU'd. why? I think too with S-On you have to relock the bootloader to RUU then unlock after boot. You can use the same unlock.bin code that you used to unlock the first time if you still have it too . Best if you done the root and everything else , do some reading on S-Off procedure and do that .
leesumm said:
S-ON or off means security is on or off, If you haven't done the mod to S-Off , your still stock S-On. To see for sure though , in the bootloader mode at the top it will say Tampered first line , then the second should say something like M7 ??? PVT ship. S-On
What recovery are you using? CWM or TWRP . Do you know or use ADB?
Click to expand...
Click to collapse
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.
moneyhbags said:
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.
Click to expand...
Click to collapse
I have had better luck with TWRP the latest one which is I think 2.6.3.
leesumm said:
I have had better luck with TWRP the latest one which is I think 2.6.3.
Click to expand...
Click to collapse
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?
moneyhbags said:
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.
Click to expand...
Click to collapse
I had the same problem like you... I have installed first twrp 2.6.3.3 then root the VIPER ROM, so I finelly got into the phone... Then I have flashed again vith ARHD 41.0 ROM and my phone is working perfect But I had the same problem as you... this is becouse of the S-ON and you stuck in boot-loop
moneyhbags said:
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?
Click to expand...
Click to collapse
IF you can get to recovery, do you have a backup that is working ? If not you may have to unzip the CM rom, look for the boot.img , put that into the adb folder then run adb with fastboot flash boot.img , then reboot and it should go. If you have a back up of the Cm rom you might be able to go to recovery and do a restore from the backup there. And another thing you might do. Not sure if it will mess it up but/ fastboot erase cache then boot
peca_slo said:
I had the same problem like you... I have installed first twrp 2.6.3.3 then root the VIPER ROM, so I finelly got into the phone... Then I have flashed again vith ARHD 41.0 ROM and my phone is working perfect But I had the same problem as you... this is becouse of the S-ON and you stuck in boot-loop
Click to expand...
Click to collapse
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.
moneyhbags said:
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.
Click to expand...
Click to collapse
Good glad to know it works again.. Now do some reading on S-Off sounds like you have some idea of ADB so it really isn't that hard and it will make flashing easier in the future. You might even consider a full GPE conversion. I did it and like the Kit Kat but running Elegancia and once in a while revert back to the GPE with Xposed and Gravity Box KK for a mod. Super good battery.
moneyhbags said:
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?
Click to expand...
Click to collapse
boot to recovery
clear cache and delvik
reboot to bootloader
fastboot USB and type
fastboot erase cache
now see if your phone will bootup
If no, find a different rom to flash
and here is a recovery flashable version of TWRP, flash it the same you do a rom and reboot to recovery to see it
moneyhbags said:
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.
Click to expand...
Click to collapse
whoops looks like i got here late ..
I want to start this off with that i really don't know anything about ROMs and flashing and stuff like that, so just hold that in mind. I am pretty sure that I have the international version of the HTC One since I live in Sweden.
Ok, so here is what happened: I rooted my phone bu using TWRP 2.6.3.3 and SuperSU 1.91. The reason i wanted to root my phone was to be able to use an app that you can only use if you have rooted your phone. When i rooted my phone and downloaded the app it said that i needed to uppdate my busybox so i downloaded a busybox installer from the appstore. When i tried to uppdate my busybox to the latest version it wouldnt work for some reason so i was going to re-root my phone with Superuser instead. However when I couldnt drag the Superuser folder into my sd card i started messing around in twerp recovery and being an idiot as i am i did a "Format data" in TWRP, when i did that obviusly everything got removed and now i don't have an os the only things i can do is booting into bootloader and TWRP otherwise my device is stuck on the HTC bootscreen. Also when i connect my phone to my computer nothing pops up so im guessing that my computer can't recognise it anymore.
I have using google but i couln't find anything. I will be monitoring this thread like a hawk so please help me.
Edit: Here is more information: I have S-on, it also says ***tampered*** and ***unlocked***
Edit2:If you need any more information for helping me please let me know and ill get it.
TL;DR: Rooted HTC One with SuperSU, Formatted data, no os, need help.
Cyanisyde said:
I want to start this off with that i really don't know anything about ROMs and flashing and stuff like that, so just hold that in mind. I am pretty sure that I have the international version of the HTC One since I live in Sweden.
Ok, so here is what happened: I rooted my phone bu using TWRP 2.6.3.3 and SuperSU 1.91. The reason i wanted to root my phone was to be able to use an app that you can only use if you have rooted your phone. When i rooted my phone and downloaded the app it said that i needed to uppdate my busybox so i downloaded a busybox installer from the appstore. When i tried to uppdate my busybox to the latest version it wouldnt work for some reason so i was going to re-root my phone with Superuser instead. However when I couldnt drag the Superuser folder into my sd card i started messing around in twerp recovery and being an idiot as i am i did a "Format data" in TWRP, when i did that obviusly everything got removed and now i don't have an os the only things i can do is booting into bootloader and TWRP otherwise my device is stuck on the HTC bootscreen. Also when i connect my phone to my computer nothing pops up so im guessing that my computer can't recognise it anymore.
I have using google but i couln't find anything. I will be monitoring this thread like a hawk so please help me.
Edit: Here is more information: I have S-on, it also says ***tampered*** and ***unlocked***
TL;DR: Rooted HTC One with SuperSU, Formatted data, no os, need help.
Click to expand...
Click to collapse
Don't panic mate, it's ok you didn't break anything.
Ok, so you can go into twrp. That's enough
All you have to do is installing a custom ROM and you will have your phone back.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=2183023 to install Android revolution HD 51 (4.4.2 android)
Since you can't access the internal SD from your computer, you will have to Sideload it. Don't worry nothing so difficult:
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2318497
So: -Download the file from the first link.
- sideload it into your TWRP
- install it from twrp
- Done!!
Uxepro said:
Don't panic mate, it's ok you didn't break anything.
Ok, so you can go into twrp. That's enough
All you have to do is installing a custom ROM and you will have your phone back.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=2183023 to install Android revolution HD 51 (4.4.2 android)
Since you can't access the internal SD from your computer, you will have to Sideload it. Don't worry nothing so difficult:
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2318497
So: -Download the file from the first link.
- sideload it into your TWRP
- install it from twrp
- Done!!
Click to expand...
Click to collapse
THANK YOU SO MUCH FOR THIS! I will be trying this right now!
Uxepro said:
Don't panic mate, it's ok you didn't break anything.
Ok, so you can go into twrp. That's enough
All you have to do is installing a custom ROM and you will have your phone back.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=2183023 to install Android revolution HD 51 (4.4.2 android)
Since you can't access the internal SD from your computer, you will have to Sideload it. Don't worry nothing so difficult:
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2318497
So: -Download the file from the first link.
- sideload it into your TWRP
- install it from twrp
- Done!!
Click to expand...
Click to collapse
I just have one question: Do i download the HD 31.6 or do i download HD 51.0 version of the ROM?
Cyanisyde said:
I just have one question: Do i download the HD 31.6 or do i download HD 51.0 version of the ROM?
Click to expand...
Click to collapse
51.0!
Uxepro said:
51.0!
Click to expand...
Click to collapse
Thank you once again!
Cyanisyde said:
Thank you once again!
Click to expand...
Click to collapse
You are welcome! Last raccomandations, when you flash Android rev. remember to select the wipe option in Aroma installer.
Also at the end of the installation press on "wipe davilk cache"
If you encounter bootloop do a "fastboot erase cache".
Also, remember that the first boot after flashing it takes long time (even 10 mins) and it's seems stuck on the htc logo but it's not
Good luck!
Long story short usually first thing I do is root and rom my phones, but I recently got an HTC One off of swappa and loved it, didnt see a reason to root. I figured I would give dual-booting via multiboot a shot, so I HTC Dev unlocked it, rooted it, installed elemental kernel, and flashed CM11. Well CM11 wouldnt boot and I tinkered so I just figured I would cut my losses, so I followed the instructions to remove it which wiped my SD card. I was on linux, and couldn't get fastboot usb, just fastboot ac. So I hopped on a friends computer, Win8.1 and downloaded a special set of drivers and whatnot, got ADB and fastboot running. TWRP wasnt working very well, it wouldnt let me use ADB so I fastboot installed CWM. I managed to push cyanogenmod to it, but kept getting an error that wouldnt let me install it. So I figured next thing to do would be RUU it, and I got my version number and matched the CID and all that, it failed with an error 12. Both .exe and .zip give me the same error. Well not its 3am and I've been at it for 5 hours now, I dont know what to do. It seems like everything I try to do fails. Please give me some advice.
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.000
RADIO-4T.27.3218.14
OS-
eMMC-boot 2048MB
flapflip22 said:
Long story short usually first thing I do is root and rom my phones, but I recently got an HTC One off of swappa and loved it, didnt see a reason to root. I figured I would give dual-booting via multiboot a shot, so I HTC Dev unlocked it, rooted it, installed elemental kernel, and flashed CM11. Well CM11 wouldnt boot and I tinkered so I just figured I would cut my losses, so I followed the instructions to remove it which wiped my SD card. I was on linux, and couldn't get fastboot usb, just fastboot ac. So I hopped on a friends computer, Win8.1 and downloaded a special set of drivers and whatnot, got ADB and fastboot running. TWRP wasnt working very well, it wouldnt let me use ADB so I fastboot installed CWM. I managed to push cyanogenmod to it, but kept getting an error that wouldnt let me install it. So I figured next thing to do would be RUU it, and I got my version number and matched the CID and all that, it failed with an error 12. Both .exe and .zip give me the same error. Well not its 3am and I've been at it for 5 hours now, I dont know what to do. It seems like everything I try to do fails. Please give me some advice.
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.000
RADIO-4T.27.3218.14
OS-
eMMC-boot 2048MB
Click to expand...
Click to collapse
Your problems started at trying to install cm11 with elementalx kernel, that's a sense kernel and cm is not a sense Rom, so unlock your bootloader again and flash twrp 2.6.3.3 to your phone, push a sense Rom of your choice to the phone and flash it, I'm guessing the ruu isn't working as you can't back flash with s-on and you already have the newest os / firmware on your phone according to your hboot version
Seanie280672 said:
Your problems started at trying to install cm11 with elementalx kernel, that's a sense kernel and cm is not a sense Rom, so unlock your bootloader again and flash twrp 2.6.3.3 to your phone, push a sense Rom of your choice to the phone and flash it, I'm guessing the ruu isn't working as you can't back flash with s-on and you already have the newest os / firmware on your phone according to your hboot version
Click to expand...
Click to collapse
Will give this a try, thanks
and dont forget, 4.4+ sense roms (i.e arhd) must be flashed using twrp 2.6.3.3 or 2.6.3.4 and newest CM11 roms must be flashed using twrp 2.7.1.1 because of the new fstab layout introduced May, 2014
alray said:
and dont forget, 4.4+ sense roms (i.e arhd) must be flashed using twrp 2.6.3.3 or 2.6.3.4 and newest CM11 roms must be flashed using twrp 2.7.1.1 because of the new fstab layout introduced May, 2014
Click to expand...
Click to collapse
Noted, just flased 2.6.3.3 and adb pushing a sense 6 rom. Kinda funny, 2.6.3.3 connects to adb on linux but no other recovery would. Granted it wont let me side-load but as long as I can push files I'm good. Just tested it by pushing a random zip file, all is good. Just gonna wait for it to finish downloading, adb push it and try to flash it. If all goes as well as I hope it should work. I'll let you guys know if I need more help.
Thank you so much.
flapflip22 said:
Noted, just flased 2.6.3.3 and adb pushing a sense 6 rom. Kinda funny, 2.6.3.3 connects to adb on linux but no other recovery would. Granted it wont let me side-load but as long as I can push files I'm good. Just tested it by pushing a random zip file, all is good. Just gonna wait for it to finish downloading, adb push it and try to flash it. If all goes as well as I hope it should work. I'll let you guys know if I need more help.
Thank you so much.
Click to expand...
Click to collapse
if you cant sideload its probably because you are using an outdated version of adb. latest version of adb is 1.0.31. however, you'll be fine using adb push.
alray said:
if you cant sideload its probably because you are using an outdated version of adb. latest version of adb is 1.0.31. however, you'll be fine using adb push.
Click to expand...
Click to collapse
Alright, managed to adb push to files to my phone but now it just says "updating partition details..." then "error flashing zip /sdcard/myrom.zip" and FAILED at the bottom. What next?
flapflip22 said:
Alright, managed to adb push to files to my phone but now it just says "updating partition details..." then "error flashing zip /sdcard/myrom.zip" and FAILED at the bottom. What next?
Click to expand...
Click to collapse
you might want to wipe everything + format data then push the rom again and install it. Also check MD5 of the rom
alray said:
you might want to wipe everything + format data then push the rom again and install it. Also check MD5 of the rom
Click to expand...
Click to collapse
It worked! Followed your instructions, then I used a CM 10.2 rom and a JB kernel and it worked just fine. Next I'm gonna s-off and superCID it so I wont have to go through any of this again, and then flash the ROM and kernel I want. Probably not gonna tinker anymore until later when the newest HTC sense release comes out.
flapflip22 said:
It worked! Followed your instructions, then I used a CM 10.2 rom and a JB kernel and it worked just fine. Next I'm gonna s-off and superCID it so I wont have to go through any of this again, and then flash the ROM and kernel I want. Probably not gonna tinker anymore until later when the newest HTC sense release comes out.
Click to expand...
Click to collapse
:good: happy flashing
I have had inklings that something was a little off with my installation for a little bit. It has always been like pulling teeth to get a rom installed on my htc one, and for the most part I had to sideload everything I wanted to install.
I ran a snapshot of cyanogen for a while, but my phone refused to update to new versions. I got frustrated and installed the nocturnal GPE rom which worked fine for a few months, but recently would not connect to the networks. I attempted to run the factory reset command from TWRP, but the phone hung for an hour trying to erase the cache. Then when I restarted the phone, instead of seeing the boot screen for the GPE rom I had most recently installed, I saw the cyanogen boot screen.
I have had little luck reinstalling roms since then and also have some problems with the recoveries. I have to install CWM or whatever recovery I dont have installed to even get sideloading to work. I've installed the nocturnal GPE rom again, but when it gets to the screen to select English it just restarts without warning.
Right now I just want to know if it is possible to nuke everything but the bootloader and just start fresh from factory settings. I want the nightmare to be over!
I have done everything in this thread:
http://forum.xda-developers.com/htc-one/help/lost-signal-cache-boot-recovery-t2851707/post54949931
gothmog1114 said:
I have had inklings that something was a little off with my installation for a little bit. It has always been like pulling teeth to get a rom installed on my htc one, and for the most part I had to sideload everything I wanted to install.
I ran a snapshot of cyanogen for a while, but my phone refused to update to new versions. I got frustrated and installed the nocturnal GPE rom which worked fine for a few months, but recently would not connect to the networks. I attempted to run the factory reset command from TWRP, but the phone hung for an hour trying to erase the cache. Then when I restarted the phone, instead of seeing the boot screen for the GPE rom I had most recently installed, I saw the cyanogen boot screen.
I have had little luck reinstalling roms since then and also have some problems with the recoveries. I have to install CWM or whatever recovery I dont have installed to even get sideloading to work. I've installed the nocturnal GPE rom again, but when it gets to the screen to select English it just restarts without warning.
Right now I just want to know if it is possible to nuke everything but the bootloader and just start fresh from factory settings. I want the nightmare to be over!
I have done everything in this thread:
http://forum.xda-developers.com/htc-one/help/lost-signal-cache-boot-recovery-t2851707/post54949931
Click to expand...
Click to collapse
Follow this guide.
StormyNight said:
Follow this guide.
Click to expand...
Click to collapse
I tried that. When flashing the firmware, I get (bootloader) read zipped android_info fail. FAILED (remote: 99 unknown fail)
gothmog1114 said:
I tried that. When flashing the firmware, I get (bootloader) read zipped android_info fail. FAILED (remote: 99 unknown fail)
Click to expand...
Click to collapse
Could you screenshot the bootloader for me?
Maybe you've got a whacked recovery. Reflash from fastboot from an md5 verified .img (make sure its m7wls version of TWRP). You should have no problems wiping any partition from within.
StormyNight said:
Could you screenshot the bootloader for me?
Click to expand...
Click to collapse
http://imgur.com/GwCBmpe
gothmog1114 said:
http://imgur.com/GwCBmpe
Click to expand...
Click to collapse
Are you using a Windows 8 computer? If so, try it with Windows 7. If you're using Windows 7, try a different port (preferably a USB 2.0 port).
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Rentom said:
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Click to expand...
Click to collapse
flash any custom kernel to get rid of that message
simms22 said:
flash any custom kernel to get rid of that message
Click to expand...
Click to collapse
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Rentom said:
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Click to expand...
Click to collapse
because google put it there, it is new.
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Yeah I let twrp root it when it asked when I did it two months ago. Was that a bad thing? I thought I read that it was if you were rooting 6.0.1, but I was rooting 6.0 so I decided to see what would happen, and it went smoothly.
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
I see. Makes sense. Alright, thanks. I already did flash it back to stock to update to 6.0.1, so I'm not sure why you told me to flash it back to stock and then install su 2.67.
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Mongo23ny said:
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Click to expand...
Click to collapse
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
simms22 said:
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
Click to expand...
Click to collapse
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Mongo23ny said:
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Click to expand...
Click to collapse
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Tried flashing twrp a couple of times, went back to stock recovery and then twrp. No luck. Also, phone will not boot with custom recovery only with stock. Not sure if I tried 3.0.0.0
simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Do I keep system read only in twrp 3.0?
Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
no, do not keep system read only, ever.
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
Thanks for all your help, did a clean install, fastboot flashed 6.01. I had gotten that corrupt phone message when I rebooted again but I took some security update and that got rid of the message. I flashed twrp 3.0.0.0 and SuperSU 2.67 and got root back. No worries, thx again.
Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
If you are using the systemless root method then yes, you do want to keep system read only.
alryder said:
If you are using the systemless root method then yes, you do want to keep system read only.
Click to expand...
Click to collapse
I kept it in read only, installed SuperSU 2.67 in twrp.