Every time I uninstall supersu (using built-in uninstall, deleting sys/xbin, and using the universal unroot tool), on reboot, supersu is reinstalled. I flashed a stock RUU (dottat's) and turned S-ON and relocked bootloader.
I was going to take my phone into Verizon for repair, but at it's current unrootable, modified state, I don't think that will be possible.
Is there any way that I can successfully unroot? Or am I SOL?
ironbesterer said:
Every time I uninstall supersu (using built-in uninstall, deleting sys/xbin, and using the universal unroot tool), on reboot, supersu is reinstalled. I flashed a stock RUU (dottat's) and turned S-ON and relocked bootloader.
I was going to take my phone into Verizon for repair, but at it's current unrootable, modified state, I don't think that will be possible.
Is there any way that I can successfully unroot? Or am I SOL?
Click to expand...
Click to collapse
Did you follow what I told you to do in tigertown's thread? You need to run my s-on RUU exe. The S-on will flash while S-on (obviously) and it does not have SU in /system. You will be 100% stock afterwards.
dottat said:
Did you follow what I told you to do in tigertown's thread? You need to run my s-on RUU exe. The S-on will flash while S-on (obviously) and it does not have SU in /system. You will be 100% stock afterwards.
Click to expand...
Click to collapse
I ran it and I get a signature error.
I get this same error with everything.
ironbesterer said:
I ran it and I get a signature error.
I get this same error with everything.
Click to expand...
Click to collapse
Setup team viewer and pm me the info. We will get this sorted.
Related
I tried following this guide:
thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2849-how-restore-stock-rooted-non-rooted-users.html
I successfully flashed MR1, now when I go to flash the bootloader using the same PG05IMG.zip method it says bypassed. I checked the md5 hash, it checked out okay. What would cause this?
This is for a warranty replacement, I just need the phone to be stock again!
Just find the latest unrooted gingerbread rom that leaked and flash it, it will go back to stock. check here or android police for the download....
Jrocker23 said:
Just find the latest unrooted gingerbread rom that leaked and flash it, it will go back to stock. check here or android police for the download....
Click to expand...
Click to collapse
Thanks, I will give that a shot.
If you originally used the Revolutionary root method, its not just flashing a new hboot, as its a hboot that doesn't allow it to be easily overwritten. This stops you from accidentally flashing a s-on hboot at a time you didn't mean to (most likely through ruu). If you did that, you have to adb some files to your phone to put a stock s-on hboot on. If you did the old downgrade root method, i would try downloaded the files from somewhere other than where you did this time, and try again.
nbdysreal said:
If you originally used the Revolutionary root method, its not just flashing a new hboot, as its a hboot that doesn't allow it to be easily overwritten. This stops you from accidentally flashing a s-on hboot at a time you didn't mean to (most likely through ruu). If you did that, you have to adb some files to your phone to put a stock s-on hboot on. If you did the old downgrade root method, i would try downloaded the files from somewhere other than where you did this time, and try again.
Click to expand...
Click to collapse
This is exactly what I needed to know.
For people in the same boat this is what I did (sorry for the links, apparently I don't have enough posts)
Follow this guide to flash a different hboot:
thunderboltforums.com/forum/htc-thundebolt-hacking-guides/5427-rs-guide-how-return-stock-revolutionary-root.html
Then flash the PG05IMG from here:
droid-life.com/2011/09/27/finally-the-htc-thunderbolt-gingerbread-update-appears-to-be-ready-as-build-2-11-605-3/
so to get back to stock, if you didnt use the rev root method, what exactly do you flash? could someone link me?
shawnn218 said:
so to get back to stock, if you didnt use the rev root method, what exactly do you flash? could someone link me?
Click to expand...
Click to collapse
What I outlined above should get you to stock.
even if i rooted the normal way and not rev?
http://forum.xda-developers.com/showthread.php?t=1310014&highlight=return+to+stock
2/3 of the way down under this section "Putting current stock firmware and s-on back onto the phone"
This will put you back to STOCK / S-0N from the old downgrade root method. If you just want a stock rooted rom, flash one. Unless you are taking it in for service or returning it, there really isn't a need to unroot it just to put a stock rom on.
Ok, i need help here. i'm not sure what is the problem here.
Current Bootloader System
S-Off
hBoot 2.14
Radio 3.18
Super CID - 1111111
Everytime i try to install a ROM, not all of them. i got Install Failed: Status 1. Which i didn't know why.
Previously in previous root i didnt have a problem
Couple days back i decided to tried OTA to 4.1.1 from ATT and this start happening. I relock my bootloader before the OTA and re-unlock before the update following this method. i managed to back to AOSP and some AOKP. but i always had a problem on Viper, very laggy and dialer are almost useless. I cant even flash CleanROM 6.
But, i was thinking. On my bootloader i have Unlocked flag but didnt have Tampered flag, which is i think the issue here. May i get a confirmation on that? and if that the case, may i have the guideline to re-root it this software.
THanks
Try a lower version of twrp if you are using 2.4.3.0
What tez1 said. Though the I believe "failure" is actually just a failure to wipe cache at the end of the flash procedure (at least, that's what it's been for me when I get the error). If you manually wipe cache after install, and then reboot, the flash should have succeeded.
incofstupid said:
But, i was thinking. On my bootloader i have Unlocked flag but didnt have Tampered flag, which is i think the issue here. May i get a confirmation on that?
Click to expand...
Click to collapse
That's not an issue at all. It's what happens when you install new stock system software (like the OTA or a ruu) after you're s-off. S-off stops all security checks, so you don't get that rooted flag anymore.
Problem TWRP... install 2.4.2!
thank you for all the answers i will try it.
EDIT: thanks, you can close this thread. it was the TWRP 2.4.X.X i decided to go back to 2.3.3.1.
Currently running stock rom version 4.0.3. Software number 1.85.502.3. I have root,supercid,unlocked and s off. Using TWRP 2.6.3.0 recovery. I tried to flash Cyanogen 10.1.3 stable but it gave an error message which contained something referring to 2.14 and I remember reading that you may need to update your hboot for newer roms. so i followed this thread http://forum.xda-developers.com/showthread.php?t=2156686 and updated my hboot to 2.14. After that I can flash Cyanogen but when I reboot the phone gets stuck in a boot loop. I've tried wiping cache, davlik, system etc and it doesn't help. Also extracted the boot.img from the rom zip and pushed it to my phone and that didn't help either. What is the problem? Is there anything else I can try?
Updating the hboot is only part of the requirement for flashing the ROM. If you read the usual instructions in the cm ROM thread it actually says you need to run the 3.18 RUU.
Sent from my Evita
timmaaa said:
Updating the hboot is only part of the requirement for flashing the ROM. If you read the usual instructions in the cm ROM thread it actually says you need to run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
Thank you for the reply timmaaa, my brother had the exact same phone and he was running magio rom on it. he used xfactor root exploit and face palm s off. magio rom only requires 2.20 update and I was able to flash cm 10.1 on it and it worked fine. Whats going on there? Anyway so my only option is to run the 3.18 RUU?
I'm not sure what was going on with the other phone, but yes the requirement for either cm10.1 or cm10.2 is to run the 3.18 RUU. You're s-off so the whole process is very easy. Download the RUU, connect your phone in fastboot mode, double click the RUU program on your PC, follow the prompts and that's it. Just make sure no other programs are running and make sure screen saver / hibernation are turned off. It will return your phone to stock but your unlocked bootloader and s-off status will survive the process. You'll just need to flash TWRP recovery again afterwards.
Sent from my Evita
timmaaa said:
I'm not sure what was going on with the other phone, but yes the requirement for either cm10.1 or cm10.2 is to run the 3.18 RUU. You're s-off so the whole process is very easy. Download the RUU, connect your phone in fastboot mode, double click the RUU program on your PC, follow the prompts and that's it. Just make sure no other programs are running and make sure screen saver / hibernation are turned off. It will return your phone to stock but your unlocked bootloader and s-off status will survive the process. You'll just need to flash TWRP recovery again afterwards.
Sent from my Evita
Click to expand...
Click to collapse
just to confirm is this the file i need
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe
lujosh87 said:
just to confirm is this the file i need
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe
Click to expand...
Click to collapse
That's the one
exad said:
That's the one
Click to expand...
Click to collapse
worked like a charm. you are the man. thank you.
timmaaa said:
I'm not sure what was going on with the other phone, but yes the requirement for either cm10.1 or cm10.2 is to run the 3.18 RUU. You're s-off so the whole process is very easy. Download the RUU, connect your phone in fastboot mode, double click the RUU program on your PC, follow the prompts and that's it. Just make sure no other programs are running and make sure screen saver / hibernation are turned off. It will return your phone to stock but your unlocked bootloader and s-off status will survive the process. You'll just need to flash TWRP recovery again afterwards.
Sent from my Evita
Click to expand...
Click to collapse
Thank you too timmaaa.
No problem.
Sent from my Evita
Current Situation(summary):
rooted
unlocked
S-on
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
CID-11111111
Lastest TWRP installed 2.7.1.0
After attempting and failing s-off with Facepalm and Rumrunner as well as trying to get newer roms installed over the 4.2.2 rom
I had the S-on way.... had to do a factory reset because I could only get to the bootloader.
Now I have no ROM installed and can only get to bootloader and recovery. Device does show up under adb sideload and fastboot in the respective modes. cannot mount as a filesystem in TWRP for some reason
Not sure where to proceed from here to acheive s-off and get up to 4.4 aosp roms.
Do I need to update the firmware for any reason? Is there an old exploitable rom and Kernal that I can install that has good success with s-off? I'm just lost and frustrated so I'm asking for help.
bathnapkin said:
Current Situation(summary):
rooted
unlocked
S-on
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
Unsure if superCID or not
Lastest TWRP installed 2.7.1.0
After attempting and failing s-off with Facepalm and Rumrunner as well as trying to get newer roms installed over the 4.2.2 rom
I had the S-on way.... had to do a factory reset because I could only get to the bootloader.
Now I have no ROM installed and can only get to bootloader and recovery. Device does show up under adb sideload and fastboot in the respective modes. cannot mount as a filesystem in TWRP for some reason
Not sure where to proceed from here to acheive s-off and get up to 4.4 aosp roms.
Do I need to update the firmware for any reason? Is there an old exploitable rom and Kernal that I can install that has good success with s-off? I'm just lost and frustrated so I'm asking for help.
Click to expand...
Click to collapse
I was in a similar situation a few days ago. In my case i couldn't boot into Android or recovery mode and the device was stuck in a reboot loop. I run RUU to reset everything to original factory settings. You have to relock your bootloader before you run RUU. It'll reset your root etc and you'll have to start from scratch. This link has the details:
http://forum.xda-developers.com/showthread.php?t=2593037
If you're on Mac or Linux use this one:
http://forum.xda-developers.com/showthread.php?t=1668156
Good luck.
Inn0vative1 said:
I was in a similar situation a few days ago. In my case i couldn't boot into Android or recovery mode and the device was stuck in a reboot loop. I run RUU to reset everything to original factory settings. You have to relock your bootloader before you run RUU. It'll reset your root etc and you'll have to start from scratch. This link has the details:
http://forum.xda-developers.com/showthread.php?t=2593037
If you're on Mac or Linux use this one:
http://forum.xda-developers.com/showthread.php?t=1668156
Good luck.
Click to expand...
Click to collapse
Thanks! this Is what I was hoping would help me. Unfortunately I've discovered I do have super CID "11111111"
currently trying to find a fastboot only script that can S-off me which i'm not sure even exists. Or just a way to revert the cid to whatever the AT&T one is
Inn0vative1 said:
I was in a similar situation a few days ago. In my case i couldn't boot into Android or recovery mode and the device was stuck in a reboot loop. I run RUU to reset everything to original factory settings. You have to relock your bootloader before you run RUU. It'll reset your root etc and you'll have to start from scratch. This link has the details:
http://forum.xda-developers.com/showthread.php?t=2593037
If you're on Mac or Linux use this one:
http://forum.xda-developers.com/showthread.php?t=1668156
Good luck.
Click to expand...
Click to collapse
bathnapkin said:
Thanks! this Is what I was hoping would help me. Unfortunately I've discovered I do have super CID "11111111"
currently trying to find a fastboot only script that can S-off me which i'm not sure even exists. Or just a way to revert the cid to whatever the AT&T one is
Click to expand...
Click to collapse
There's no need to run an RUU at this stage. Just downgrade to TWRP 2.6 and you'll be able to use the 'mount usb storage' feature again to copy a ROM zip across. Use the Kickdroid ROM and try Rumrunner s-off again.
The last thing you wanna do is change your CID back, then you'll be totally screwed. Just do what I said above and you should be fine.
Transmitted via Bacon
timmaaa said:
There's no need to run an RUU at this stage. Just downgrade to TWRP 2.6 and you'll be able to use the 'mount usb storage' feature again to copy a ROM zip across. Use the Kickdroid ROM and try Rumrunner s-off again.
The last thing you wanna do is change your CID back, then you'll be totally screwed. Just do what I said above and you should be fine.
Transmitted via Bacon
Click to expand...
Click to collapse
I managed to relock, run the 2.2 RUU, re-unlock and root again to get an unbricked stock phone. Facepalm didn't work so I'll give kickdroid and rumrunner a go.
EDIT: Kickdroid seems to require a firmware higher than the one I have to work which requires s-off for me to get without bricking. know of any older roms that are unsecure and rumrunner will work on?
Just got frustrated and did the RUU again. but this time I managed to get s-off! don't know what I did different this time but thanks to both of you!
bathnapkin said:
I managed to relock, run the 2.2 RUU, re-unlock and root again to get an unbricked stock phone. Facepalm didn't work so I'll give kickdroid and rumrunner a go.
EDIT: Kickdroid seems to require a firmware higher than the one I have to work which requires s-off for me to get without bricking. know of any older roms that are unsecure and rumrunner will work on?
Just got frustrated and did the RUU again. but this time I managed to get s-off! don't know what I did different this time but thanks to both of you!
Click to expand...
Click to collapse
Kickdroid only needs the newer firmware to stop signal loss problems and random reboots. You could have used it to get s-off. But you got it in the end!
Transmitted via Bacon
For some reason I am unable to install the ROM via RUU OR OTA update (manual or auto). I am getting a Error 132 (signature error). I am S-ON and RELOCKED.
Things I have already done/tried:
Made sure I have the correct RUU (it's the only one available as far as I know and it is for the HTC unlocked US variant).
Made sure my device is RELOCKED and stock recovery installed.
Tried multiple methods - including RUU (tried inside of the OS as well as in download mode/bootloader mode); OTA tried to flash manually inside of stock recovery, tried to download OTA (no update found), tried to flash firmware and OTA in custom recovery as well stock recovery.
Searched the forums relentlessly for answers to the 132 signature error. There doesn't seem to be a consensus answer.
Of note: My 'Software Status' is flagged as "MODIFIED," I'm wondering if that is preventing me from updating the HBOOT via RUU.
Please let me know if you can think of any solutions because I am stumped, and I'm sure the community could use a more definitive answer about the 132 Error as it seems to have been mention several times over the course of quite a few years.
Thanks guys
BrandonBaskin said:
For some reason I am unable to install the ROM via RUU OR OTA update (manual or auto). I am getting a Error 132 (signature error). I am S-ON and RELOCKED.
Things I have already done/tried:
Made sure I have the correct RUU (it's the only one available as far as I know and it is for the HTC unlocked US variant).
Made sure my device is RELOCKED and stock recovery installed.
Tried multiple methods - including RUU (tried inside of the OS as well as in download mode/bootloader mode); OTA tried to flash manually inside of stock recovery, tried to download OTA (no update found), tried to flash firmware and OTA in custom recovery as well stock recovery.
Searched the forums relentlessly for answers to the 132 signature error. There doesn't seem to be a consensus answer.
Of note: My 'Software Status' is flagged as "MODIFIED," I'm wondering if that is preventing me from updating the HBOOT via RUU.
Please let me know if you can think of any solutions because I am stumped, and I'm sure the community could use a more definitive answer about the 132 Error as it seems to have been mention several times over the course of quite a few years.
Thanks guys
Click to expand...
Click to collapse
You need to be S-OFF for flash the Firmware and the 2.18 will not run if you dont have flashed the firmware. If you have an Unlocked USA you need tu run the 1.57 (the last one before 7.0), the status will be OFFICIAL and you can just update whit OTA in setting, information, update like a normal device or flash ota in the recovery stock, but you steel need 1.57.617.60 version and OFFICIAL status.
salvy' said:
You need to be S-OFF for flash the Firmware and the 2.18 will not run if you dont have flashed the firmware. If you have an Unlocked USA you need tu run the 1.57 (the last one before 7.0), the status will be OFFICIAL and you can just update whit OTA in setting, information, update like a normal device or flash ota in the recovery stock, but you steel need 1.57.617.60 version and OFFICIAL status.
Click to expand...
Click to collapse
Hi, thanks for your response. I have run the latest RUU multiple times but it has failed to reset the software status to 'OFFICIAL.' I have even rolled back to the previous RUU, downloaded and installed the OTA for 1.57.617.60 and that too failed to reset the software status to official. Getting S-OFF for me is not currently an option so I'm wondering if there is a practicable alternative.
Thanks again
BrandonBaskin said:
Hi, thanks for your response. I have run the latest RUU multiple times but it has failed to reset the software status to 'OFFICIAL.' I have even rolled back to the previous RUU, downloaded and installed the OTA for 1.57.617.60 and that too failed to reset the software status to official. Getting S-OFF for me is not currently an option so I'm wondering if there is a practicable alternative.
Thanks again
Click to expand...
Click to collapse
Take the ota.zip file and try to install it via the stock recovery, and see what errors you get. That is how I figured out what was wrong with mine ( wrong CID)
MGfusion said:
Take the ota.zip file and try to install it via the stock recovery, and see what errors you get. That is how I figured out what was wrong with mine ( wrong CID)
Click to expand...
Click to collapse
OK. Attempted to flash OTA in recovery and it appeared to be successful, however after rebooting out of recovery there was no OS loaded. Do you know of any way to reset the software status to official - because running the RUU(s) for the current base doesn't seem to work.
Thanks
BrandonBaskin said:
OK. Attempted to flash OTA in recovery and it appeared to be successful, however after rebooting out of recovery there was no OS loaded. Do you know of any way to reset the software status to official - because running the RUU(s) for the current base doesn't seem to work.
Thanks
Click to expand...
Click to collapse
Flash 1.57 ota, and relock boot loader if unlocked. Unlocked boot loader might be what is making the software status say modified
MGfusion said:
Flash 1.57 ota, and relock boot loader if unlocked. Unlocked boot loader might be what is making the software status say modified
Click to expand...
Click to collapse
Bootloader status is: "RELOCKED"
1.57.617.60 RUU is installed
Software Status is still: "MODIFIED"
Could it be that there is no way of resetting this status while S-ON?
BrandonBaskin said:
Bootloader status is: "RELOCKED"
1.57.617.60 RUU is installed
Software Status is still: "MODIFIED"
Could it be that there is no way of resetting this status while S-ON?
Click to expand...
Click to collapse
I'm not sure, I don't understand what could still be "modified"
MGfusion said:
I'm not sure, I don't understand what could still be "modified"
Click to expand...
Click to collapse
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.
BrandonBaskin said:
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.
Click to expand...
Click to collapse
Try installing this zip file with the stock recovery and relocked bootloader. This is how I upgraded to nougat, no problem
https://drive.google.com/file/d/0B53pV_Dn96x1aDJZU2l5MWdmeFk/view
(This is the extracted ota zip file)
MGfusion said:
Try installing this zip file with the stock recovery and relocked bootloader. This is how I upgraded to nougat, no problem
https://drive.google.com/file/d/0B53pV_Dn96x1aDJZU2l5MWdmeFk/view
(This is the extracted ota zip file)
Click to expand...
Click to collapse
Thanks! I will try again with this file. Just curious... do you remember if you "Software Status" was 'MODIFIED'? And are you S-OFF?
BrandonBaskin said:
Thanks! I will try again with this file. Just curious... do you remember if you "Software Status" was 'MODIFIED'? And are you S-OFF?
Click to expand...
Click to collapse
Can't remember if it said modified or not, but I am definitely s-off.
MGfusion said:
Can't remember if it said modified or not, but I am definitely s-off.
Click to expand...
Click to collapse
It may literally be no way to update it with S-ON. It's cool because Sunshine is an option when I get a some extra cash but this seems to be a bit of a programming flaw on HTC's part.
BrandonBaskin said:
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.
Click to expand...
Click to collapse
Try installing the OTA, then flashing ruu. Thats how I did I it.
BrandonBaskin said:
It may literally be no way to update it with S-ON. It's cool because Sunshine is an option when I get a some extra cash but this seems to be a bit of a programming flaw on HTC's part.
Click to expand...
Click to collapse
Oh, you are s-on? I would definitely try sunshine and then install ota or ruu then
The_scam said:
Try installing the OTA, then flashing ruin. Thats how I did I it.
Click to expand...
Click to collapse
Hey, thanks for the response. What is Ruin?
I've got S-OFF, Software Status: Official, Relocked boot loader, CID: BS_US001, Current ROM: 1.57.617.60
I've been getting the same "Error 132: Signature Error" when trying to flash the 2.18.617.1 RUU.
Attempted to flash the most recent RUU I had (1.57.617.41), which was successful. Attempted the 2.18.617.1 RUU again, same issue.
Tried changing the CID to 11111111 and tried flashing the RUU, still getting Error 132.
Tried pushing the 2.18.617.1 OTA via ADB Sideload and got "assert failed: check_cid("00000000", etc...)" error
Changed CID back to BS_US001 and started pushing the OTA updates (1.57.617.52, 1.57.617.60, 2.18.617.1) one by one via ADB Sideload
All of the OTA installs were successful.
Now, only getting the white screen with the HTC logo.
Ran 2.18.617.1 RUU again, ran fine this time.
Still only getting the white screen with the HTC logo.
Not terribly excited about the direction this is going...
kommoncents said:
I've got S-OFF, Software Status: Official, Relocked boot loader, CID: BS_US001, Current ROM: 1.57.617.60
I've been getting the same "Error 132: Signature Error" when trying to flash the 2.18.617.1 RUU.
Attempted to flash the most recent RUU I had (1.57.617.41), which was successful. Attempted the 2.18.617.1 RUU again, same issue.
Tried changing the CID to 11111111 and tried flashing the RUU, still getting Error 132.
Tried pushing the 2.18.617.1 OTA via ADB Sideload and got "assert failed: check_cid("00000000", etc...)" error
Changed CID back to BS_US001 and started pushing the OTA updates (1.57.617.52, 1.57.617.60, 2.18.617.1) one by one via ADB Sideload
All of the OTA installs were successful.
Now, only getting the white screen with the HTC logo.
Ran 2.18.617.1 RUU again, ran fine this time.
Still only getting the white screen with the HTC logo.
Not terribly excited about the direction this is going...
Click to expand...
Click to collapse
download the zip file I had given a link to above and try installing it with the stock system recovery
BrandonBaskin said:
Hey, thanks for the response. What is Ruin?
Click to expand...
Click to collapse
Lol sorry, meant to type ruu. Using my phone and autocorrect ?
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
MGfusion said:
download the zip file I had given a link to above and try installing it with the stock system recovery
Click to expand...
Click to collapse
Try installing the TWRP, look around at the system files. Is anything there? You might have to wipe everything and try the ruu again.
Maybe try rebooting into "fastboot OEM rebootRUU" then once that loads, type "fastboot flash <name of your ruu.zip>" from your computer
The_scam said:
Lol sorry, meant to type ruu. Using my phone and autocorrect
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
Try installing the TWRP, look around at the system files. Is anything there? You might have to wipe everything and try the ruu again.
Maybe try rebooting into "fastboot OEM rebootRUU" then once that loads, type "fastboot flash <name of your ruu.zip>" from your computer
Click to expand...
Click to collapse
lol ohh! ok...I thought it was something like Odin haha
so just so I'm clear:
Flash OTA (in Recovery)?
Then immediately start the RUU?