Related
I have an unlocked HTC One X, running Stock Rom and CMW recovery. CID 621. (never installed any custom roms, only CMW recovery and unlocking the phone)
I haven't updated my phone in a while since OTA failed due to the recovery. Last night I reverted back to the stock recovery and updated, successfully, OTA version 2.18.751.7.
After updating my One X informs me there's a JB OTA update, 3.14.751.20 but when I try to run it, it reboots, shows the green progress bar for about 30 seconds then shows the red rectangular of failure (rebooting starts up the device normally).
I tried reflashing the stock recovery, tried the recovery from the latest RUU for my CID (RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed) but the OTA update keeps failing.
I also tried disabling SuperSU and used Voodoo Root Keeper to disable root, still the same red rectangular. Tried using the nandroid backup and running through the updates again, but same issue (2.18.751.7 installs correctly, but 3.14.751.20 fails).
Any help would be appreciated!
Thanks,
Maya
mayashoval said:
I have an unlocked HTC One X, running Stock Rom and CMW recovery. CID 621. (never installed any custom roms, only CMW recovery and unlocking the phone)
I haven't updated my phone in a while since OTA failed due to the recovery. Last night I reverted back to the stock recovery and updated, successfully, OTA version 2.18.751.7.
After updating my One X informs me there's a JB OTA update, 3.14.751.20 but when I try to run it, it reboots, shows the green progress bar for about 30 seconds then shows the red rectangular of failure (rebooting starts up the device normally).
I tried reflashing the stock recovery, tried the recovery from the latest RUU for my CID (RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed) but the OTA update keeps failing.
I also tried disabling SuperSU and used Voodoo Root Keeper to disable root, still the same red rectangular. Tried using the nandroid backup and running through the updates again, but same issue (2.18.751.7 installs correctly, but 3.14.751.20 fails).
Any help would be appreciated!
Thanks,
Maya
Click to expand...
Click to collapse
Have you tried relocking your bootloader? 'fastboot oem lock'
Also, maybe try flashing the stock kernel as well?
Did you remove anything?
You might try running an RUU if you can one one new enough, or restoring a backup (there are threads here for both backups and RUU, but look on htcruu.com, the device is endeavoru)
ArmedandDangerous said:
Also, maybe try flashing the stock kernel as well?
Click to expand...
Click to collapse
I'm hesitant about flashing a kernel, as I did not change the original stock one, and it feels too risky.
BenPope said:
Did you remove anything?
You might try running an RUU if you can one one new enough, or restoring a backup (there are threads here for both backups and RUU, but look on htcruu.com, the device is endeavoru)
Click to expand...
Click to collapse
I thought about that, but the most recent RUU for my CID is older than what getvar is telling me (INFOversion-main: 2.18.751.7. latest RUU I found is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed).
As to relock, I went through quite a few similar threads and in all relocking did not make any difference. Also, if that was the case, I don't think the first OTA update would have gone through.
mayashoval said:
I thought about that, but the most recent RUU for my CID is older than what getvar is telling me (INFOversion-main: 2.18.751.7. latest RUU I found is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed).
As to relock, I went through quite a few similar threads and in all relocking did not make any difference. Also, if that was the case, I don't think the first OTA update would have gone through.
Click to expand...
Click to collapse
I think the update to hboot requires it to be locked, your previous update was most likely ok with the hboot it was on.
mayashoval said:
I thought about that
Click to expand...
Click to collapse
Then look for a backup of your ROM version in the backup thread.
BenPope said:
Then look for a backup of your ROM version in the backup thread.
Click to expand...
Click to collapse
Sorry to be a noob but what do you mean? I thought I couldn't use a backup older than the one listed under "main version". Or am I confusing things?
Edit:
Can I install the most recent RUU?
INFOversion-main: 2.18.751.7.
latest RUU is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_ 2.1204.136.21_release_275588_signed.
Update: locking the phone did not help
I locked the phone, but the update still fails at the same location. The green bar expands for about 20 seconds, covering about a quarter of the bar, and the the red triangle appears.
You could always attempt to update the firmware/hboot manually download it here for your cid http://forum.xda-developers.com/showthread.php?t=1957376
Or there is a tool here http://forum.xda-developers.com/showthread.php?t=1924003
sorry for being a noob
gffmac said:
You could always attempt to update the firmware/hboot manually download it here for your cid http://forum.xda-developers.com/showthread.php?t=1957376
Or there is a tool here http://forum.xda-developers.com/showthread.php?t=1924003
Click to expand...
Click to collapse
the tool looks easy enough, but they ask to include the custom JB rom of my choice. I want the Stock update, so what do I do?
The manual update list points to a broken link. I did find it somewhere else. How do I manually update? are these the commands?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
do I need to unlock my phone again? can I use the same Unlock_code.bin I got from HTC last time (saved it) or do I have to go through the process again?
I'm asking all these questions because I don't want to end up with a bricked phone.
mayashoval said:
the tool looks easy enough, but they ask to include the custom JB rom of my choice. I want the Stock update, so what do I do?
The manual update list points to a broken link. I did find it somewhere else. How do I manually update? are these the commands?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
do I need to unlock my phone again? can I use the same Unlock_code.bin I got from HTC last time (saved it) or do I have to go through the process again?
I'm asking all these questions because I don't want to end up with a bricked phone.
Click to expand...
Click to collapse
There are a couple of really good stock looking ROMs on there with enhanced performance. There's one mentioned in my sig, it may also be the easiest route out of your issue using the tool posted above
exocetdj said:
There are a couple of really good stock looking ROMs on there with enhanced performance. There's one mentioned in my sig, it may also be the easiest route out of your issue using the tool posted above
Click to expand...
Click to collapse
Yes I am running to issues... turns out that manually flashing the firmware.zip just got my phone into a bootloop since it turns out you must install a custom rom after it. I did not want to install a custom rom just to get the OTA update to install. now my phone keeps rebooting and I'm waiting for ADHD to download (takes FOREVER! for some reason).
This really sucks. I wanted to stay with stock, and it looks like I can't even go back anymore, can't even restore with a RUU.
mayashoval said:
Yes I am running to issues... turns out that manually flashing the firmware.zip just got my phone into a bootloop since it turns out you must install a custom rom after it. I did not want to install a custom rom just to get the OTA update to install. now my phone keeps rebooting and I'm waiting for ADHD to download (takes FOREVER! for some reason).
This really sucks. I wanted to stay with stock, and it looks like I can't even go back anymore, can't even restore with a RUU.
Click to expand...
Click to collapse
There should be a RUU out for your region soonish but Until then, a stock style custom rom is a brilliant option beleive me
exocetdj said:
There should be a RUU out for your region soonish but Until then, a stock style custom rom is a brilliant option beleive me
Click to expand...
Click to collapse
don't really have a choice now...
downloading maXimus as per your recommendation (and because ADHD will take another 9 hours
You can restore an older backup, it's just like installing a custom ROM.
You might also be able to install a 2.17 RUU on 2.18, I'm not sure the hboot was updated. It's also possible to dissect an RUU and install the bits manually.
You have a few options.
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
plaktoets said:
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
Click to expand...
Click to collapse
Sorry did not find a solution. Ended up installing a custom rom, even though I wanted to keep using the stock one
plaktoets said:
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
Click to expand...
Click to collapse
I hope you did this the other way around......first flash the recovery and the relock the bootloader.....
But if you are on stock rom, kernel and recovery you do not have to relock the bootloader, it updates fine with a unlocked one.
Hey guys, first post here and I couldn't find a good thread title. Hope that's not a problem
Anyways I need a little help with my m8, because I don't know what else to do.
I'll start from the beginning:
It's a One m8, bought from O2 Germany a few months ago. There were no O2 apps installed as I bought it, though.
I unlocked the bootloader, rooted the phone, flashed the TWRP recovery and the Venom m8 ROM. It was S-On over the whole time. Tried to make it S-OFF with the help of firewater but it didn't worked, so I didn't tried it anymore.
I just wanted to flash the newest Venom ROM, but to do so, I had to flash the newest firmware (Kitkat 4.4, have 4.2 right now)
So I relocked the bootloader, because that's what people on the internet said you have to do, to flash the newest stock firmware. After that I wanted to go back to Venom m8.
After relocking the bootloader, I rebooted the phone, and now I'm stuck in there. But in the fastboot mode.
Tried to enter the recovery -> can't access it
Tried to make a factory reset -> didn't worked
Everytime klick on recovery or factory reset, the phone reboots and comes back into fastboot.
Normaly you boot into hboot I think.
At the top of the screen stands:
***TAMPERED***
***RELOCKED***
***Security Warning***
I've seen the first two the whole time, but the third one is new :/
Here are the things I tried until now:
Flashing a stock ROM (it was a OTA_m8_O2___102...) I could try to find the actual link, if that helps.
Flashing a custom recovery (tried TWRP, after that CWM) Yea I already have custom recovery, but I tought it might help somehow.
Erased fastboot cache
None of these things worked. Fastboot is the only thing that works.
So my question now is, if anyone of you guys got any other idea how to solve that problem?
I really would appreciate any help.
If you need some more informations about the phone, just let me know. I guess there's missing some important informations
Sorry for the long text and if I misspelled something
EDIT: I just remembered that the flashing of TWRP or CWM didn't worked. It said FAILED: signature verify fail
Flashing of the Stock ROM worked I guess. There was the silver HTC logo on the phone. Then I flashed it in fastboot mode.
I tried to find this RUU software, but I couldn't find it :/
And "adb" in cmd also not working. It says "device not found"
Have you tried unlocking it again ?
Sent from my HTC One_M8 using XDA Free mobile app
---------- Post added at 12:10 AM ---------- Previous post was at 12:08 AM ----------
Oh, and what are your CID / MID / bootloader version / firmware version / etc. ?
Sent from my HTC One_M8 using XDA Free mobile app
You're bootloader needs to be unlocked, not re-locked. Go to HTC Dev to unlock in again, just like the first time. Then you can flash a recovery.
Like said above, phone HAS to have unlocked bootloader to flash custom ROMs and recovery(which is why you're getting FAILED: signature verify fail). Can't flash custom recovery/ROMs with a locked bootloader.
Go to HTCDev.com and unlock the bootloader like before, then head over to the collection of stock backups thread(in general section) download a nandroid backup for your device and restore it. After that you can flash back the stock recovery(also in the collection thread) and just do the OTA updates until you get to 4.4.4 to use the latest ViperROM.
SunShine don't work with a modifyed custom Rom like ViperS. I flashed ARHD (or stock Rom) and got S-Off with SunShine.
Firewater don't work at all anymore so you have to use SunShine and pay the 25$ it cost.
3fiddy said:
Hey guys, first post here and I couldn't find a good thread title. Hope that's not a problem
Click to expand...
Click to collapse
Its not a bad one. At least better than many thread titles that say things like "Need help". Which of course is obvious, since its a Q&A, help forum! At least you tried to classify your issue!
Although the question of whether its a "soft brick" is not a critical one. IMO the term "soft brick" really doesn't mean anything. It simply means the user just got himself into a jam and doesn't know how to recover. And recovering is usually just a matter of knowing the right simple steps. More important to whether its a "soft brick", is whether the phone is truly bricked or not. And as long as the screen comes on, this phone is virtually never bricked.
RUUs don't exist for Euro versions (only the US versions, as far as I know).
The bootloader needs to be UNLOCKED to flash anything. Either just use the previous unlock bin code and fastboot command, or go through HTCDev.com unlock process again (as previously suggested). Then flash custom recovery, and flash a custom ROM or restore a stock nandroid.
Hey guys, sorry for the late response.
I did what you all said and unlocked the bootloader again. And that was it.
After unlocking it everything works normal.
You guys are the best, I knew this is the right place to come
Even the Venom ROM is on the phone. Everything else is gone, but the ROM is there.
Alright but I still would like to get the newest firmware for the phone. Could you guys give me a little help with this?
What do I have to do first?
I read a lot about how to do this. But as you can see something still went wrong :/
On the phone is currently Android 4.4.2 and ViperOneM8 1.7.0
First thing I have to do is, to grab a Nandroid Backup with the stock ROM, right?
I did this before, but then I read somewhere that the bootloader has to be locked, or relocked to update the newest stock ROM/ the newest firmware.
So if anyone knows how to do this correctly, please let me know.
Also when I flashed the nandroid backup (my own backup from before I flashed venom) I tried to update the firmware, but it wanted to update the latest Venom update.
Is this considered as normal?
Bootloader version (Hboot) is 3.16.0.0... At least I think this is the right one.
@jkolner: Didn't know that firewater doesn't work anymore. How long is this?
@redpoint73: Thanks for the heads-up Also I didn't know that there are no RUUs for the european versions. Good to know that now.
Thank you all for your answers
EDIT: I just tried to enter the recovery and it worked as well.
Oh and when I wrote above that I flashed the stock nandroid backup and the phone wanted to update the latest venom update, I think it was because the rom was still the Venom Rom, right?
Sure it was a nanroid backup, but the ROM was not the stock ROM? Or am I mix-up something there?
3fiddy said:
Alright but I still would like to get the newest firmware for the phone.
I read somewhere that the bootloader has to be locked, or relocked to update the newest stock ROM/ the newest firmware.
Click to expand...
Click to collapse
It sounds like you are trying to return to stock, and install official OTA to update firmware. In that case, unlocked bootloader is OK for OTA (no need to relock). But you need stock ROM and stock recovery.
3fiddy said:
Also when I flashed the nandroid backup (my own backup from before I flashed venom) I tried to update the firmware, but it wanted to update the latest Venom update.
Is this considered as normal?
Oh and when I wrote above that I flashed the stock nandroid backup and the phone wanted to update the latest venom update, I think it was because the rom was still the Venom Rom, right?
Sure it was a nanroid backup, but the ROM was not the stock ROM? Or am I mix-up something there?
Click to expand...
Click to collapse
You are mixing something up. The point of restoring a stock nandroid, is to return to the stock ROM. It sounds like your nandroid is made while on Viper ROM, not stock ROM. Either that, or the nandroid just didn't restore the ROM properly. Make sure "system" is checked on partitions to restore in recovery.
3fiddy said:
Bootloader version (Hboot) is 3.16.0.0... At least I think this is the right one.
Didn't know that firewater doesn't work anymore. How long is this?
Click to expand...
Click to collapse
Its been that way for months now. But your hboot version is old; so firewater might work, might not. Worth a few tries; as firewater is free and doesn't take long. If it still fails, you need to use sunshine to s-off.
redpoint73 said:
It sounds like you are trying to return to stock, and install official OTA to update firmware. In that case, unlocked bootloader is OK for OTA (no need to relock). But you need stock ROM and stock recovery.
Click to expand...
Click to collapse
Exactly this. Alright, then I read something wrong. I thought to flash the stock ROM you have to have a relocked bootloader.
I'll search a stock ROM and recovery. Hoperfully it will work.
redpoint73 said:
You are mixing something up. The point of restoring a stock nandroid, is to return to the stock ROM. It sounds like your nandroid is made while on Viper ROM, not stock ROM. Either that, or the nandroid just didn't restore the ROM properly. Make sure "system" is checked on partitions to restore in recovery.
Click to expand...
Click to collapse
This could be it. I don't know if there was already the Venom ROM in use. Could be.
redpoint73 said:
Its been that way for months now. But your hboot version is old; so firewater might work, might not. Worth a few tries; as firewater is free and doesn't take long. If it still fails, you need to use sunshine to s-off.
Click to expand...
Click to collapse
Okay I'll try it with firewater again.
Thanks for your help
EDIT: After I flashed the Nadroid Backup, do I have to wipe something, like Dalvik or anything?
3fiddy said:
EDIT: After I flashed the Nadroid Backup, do I have to wipe something, like Dalvik or anything?
Click to expand...
Click to collapse
I wipe Dalvik and cache when I flash anything.
Recovery will wipe system as it flashed the ROM. No need to do so manually.
If restoring a nandroid without data partition backed up, you may or may not have to wipe user data. It might not play well with the restored ROM, but it depends on what ROM you are coming from. If error occur, wipe data and restore again.
If you are restoring a nandroid with data partition backup, it will be wiped during restore. No need to do so manually.
Alright I flashed my own stock nandroid backup. Guess I just read something wrong because I thought it will get the latest Venom Update.
Then I downloaded and installed the latest updates. Now the phone has finally Android 4.4.
After everything went good, I flashed the twrp recovery, made a Backup, rooted the phone, did another backup and flashed the latest Venom ROM.
Before flashing something I wiped everything, like you said.
All is good now.
I think now I can totally forget to gain S-OFF with firewater. But I'll save the link to sunshine. Maybe I'll give it a try
Thanks again everyone, couldn't have done it without your help
I have a Htc One M8 ; s-off, hboot 3.16, running 4.4.2. CID is Roger001, unlocked boot
Problem I have is I'm trying to restore the phone to stock because I want to do OTA updates. I followed the guide to return Canadian HTC1m8 to stock - downloaded the nandroid backup, restored it, flashed a stock image through fastboot;
However, now if I try a OTA it just reboots my phone and normally stalls out on the HTC screen. Nothing gets updated . If i try a factory reset, same thing, and it won't boot into bootloader until I wait a while then restart it. My data won't work anymore and TWRP recovery has disappeared. I think my issue is i flashed the wrong recovery .img, I'm a fairly noob. Checked all the related links and can't figure it out.
Any help would be amazing.
Use an ruu For your phone to update your hboot and make your you flash to recovery partition for twrp
htcspark said:
Use an ruu For your phone to update your hboot and make your you flash to recovery partition for twrp
Click to expand...
Click to collapse
I would but
I can't find an ruu that would work, there doesn't seem to be one for rogers...I dunno if any US carriers would work?
htcspark said:
Use an ruu For your phone to update your hboot and make your you flash to recovery partition for twrp
Click to expand...
Click to collapse
I got an update to work, I think I had the wrong stock installed so it wouldn't work properly. Only thing now is my data isn't working, any assistance with that that could be??
Instead of trouble shooting, I would just flash this TWRP backup tested to work on Rogers M8:
http://forum.xda-developers.com/showthread.php?p=58611288
See end of 1st post in above link.
It is already in lollipop. No OTA update needed.
Use latest TWRP recovery, see 2nd post in above link.
New update GPE but fail to update due to E: error..
I think you have to relock the bootloader to get the update but I could be wrong...
Also make sure you're not on superuser CID (11111111)
Can't conclude at all where the error is based on. The provided info is absolutely not enough !
You need stock rom (read never rooted) and stock recovery. Boot loader being unlocked or relocked has for an ota no effect, neither does supercid.
kullum79 said:
I think you have to relock the bootloader to get the update but I could be wrong...
Also make sure you're not on superuser CID (11111111)
Click to expand...
Click to collapse
Wrong on both counts. Neither unlocked bootloader, nor SuperCID will prevent OTA.
As i said
redpoint73 said:
Wrong on both counts. Neither unlocked bootloader, nor SuperCID will prevent OTA.
Click to expand...
Click to collapse
I'm in a similar position.
My M8 was a Rogers once upon a time.
I went through the process of converting it to GPE. It is S-Off, & rooted with the systemless root.
I have TWRP 2.8.7 (iirc - the latest twrp for m8).
I have the same 'an update is available' as OP.
When i tell it to install the phone reboots to recovery and the update fails. I assume this is a TWRP issue.
Not sure what my best approach for getting the update installed is? Can I every to stock Recovery, install the update, and reinstall TWRP? Do I even need TWRP now I'm rooted...?
the_darkwing_duck said:
Not sure what my best approach for getting the update installed is? Can I every to stock Recovery, install the update, and reinstall TWRP? Do I even need TWRP now I'm rooted...?
Click to expand...
Click to collapse
You need stock (never rooted) ROM and matching stock recovery.
Then yes, after you update you will need to reinstall TWRP to root again. OTA update will almost always wipe out root, so its irrelevant that you have root presently. Then root, noting that root on MM is more complicated than past builds: http://forum.xda-developers.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210
Or you can just run the MM RUU (see Development section), keeping in mind that it will wipe the phone (so backup any personal data you want to keep accordingly, before RUU).
Also should be noted, it seems that lots of folks have had to flash MM firmware, then OTA or RUU to Marshmallow, if you get an unexplained Error 155.
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
ruubs said:
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
Click to expand...
Click to collapse
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
computerslayer said:
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
Click to expand...
Click to collapse
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
ruubs said:
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
Click to expand...
Click to collapse
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
computerslayer said:
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
Click to expand...
Click to collapse
The phone status is indeed unlocked.
I didn't know I could flash TWRP or a ROM. I thought I needed S-OFF for that.
I want my phone to be as stock as possible. Can I flash a stock ROM or does it have to be a custom one.
And do i need to flash TWRP in order to flash a ROM?
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
ruubs said:
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
Click to expand...
Click to collapse
That's the route I would take too. The readme thread has a section dedicated to changing your SKU in order to use other RUUs.