Related
I was flashing custom ROMs and accidentally soft-bricked my phone after attempting to go from an alpha Ice Cream Sandwich build to flashing the RUU of the official Sense 3.0 OTA (I know, stupid rookie mistake. I was tired). I tried fixing it, but so far have come up empty handed. The bootloader has just been unlocked through htcdev.com after multiple failed attempts and previously was S-OFF through AlphaRev's Revolutionary (S-ON => Revolutionary S-OFF => S-ON => HTCDEV unlock).
Bootloader reads:
VIVO PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-3822.10.08.28_M
eMMC-boot
Nov 1 2011,20:33:03
When I attempt to boot, it stays on the htc logo screen, then turns off and back on and into recovery.
Does anyone else have this problem or know how to solve it?
I'd like to flash the new RUU.
So far I've tried:
Flashing htc recovery so I can try flashing the RUUs again. No luck
I even modified the android-info.txt inside the RUUs.
I've tried the WWE RUU, the Asia HK RUU and the Asia WWE RUU (the guy from pakistan who posted in the general thread)
Should I be downgrading using a goldcard?
A goldcard is not for downgrading as such, its for flashing another carriers rom. So by all means, try flashing stock RUU with goldcard if you can't locate RUU from your carrier.
You mentioned trying to flash stock recovery but having no luck. With recovery or RUU after that?
Since you are in Canada, you probably have a IncS S710A/PG3212000 model. All of the 3.0x RUUs are for the PG3213000 model, so your only hope is that the unlocked bootloader is going to allow you to flash a modified PG32IMG.zip that has the android-info.txt file changed for modeled PG3212000.
I was able to do this with the 3.08.405.3 WWE RUU, but in my case I have permanent S-OFF via the XTC clip, so the real question is whether the 2.00.0000 unlocked HBOOT will allow you to flash a modified RUU ROM.zip or not. Good luck. You may just have to settle for custom ROMs.
Nonverbose said:
You mentioned trying to flash stock recovery but having no luck. With recovery or RUU after that?
Click to expand...
Click to collapse
I can flash the stock recovery all right by extracting recovery.img from the RUU.zip through fastboot. Sorry, I was unclear. I meant that flashing the RUUs through the bootloader still didn't work even after flashing the recovery. It's mentioned somewhere that you need the htc recovery to flash the RUU, and that it won't work with CWM.
tpbklake said:
Since you are in Canada, you probably have a IncS S710A/PG3212000 model. All of the 3.0x RUUs are for the PG3213000 model, so your only hope is that the unlocked bootloader is going to allow you to flash a modified PG32IMG.zip that has the android-info.txt file changed for modeled PG3212000.
Click to expand...
Click to collapse
Actually, I own a S710e/PG32130 model. I bought it from Taiwan, unlocked.
tpbklake said:
I was able to do this with the 3.08.405.3 WWE RUU, but in my case I have permanent S-OFF via the XTC clip, so the real question is whether the 2.00.0000 unlocked HBOOT will allow you to flash a modified RUU ROM.zip or not. Good luck. You may just have to settle for custom ROMs.
Click to expand...
Click to collapse
I tried the HK one first, because I thought it might be the one that Taiwan receives (Apparently the WWE was for European countries?). Anyways, that worked (sort of, that's how I got this updated Hboot and radio). Then I couldn't boot so I tried the other Asia WWE and the Euro WWE and neither will flash.
If the device is unlocked you can just extract the update zip file and flash it manually. Probably just needs boot.img
fastboot flash boot boot.img
(Although this depends on what exactly is unlocked and with what method,something your posts do not state)
Nonverbose said:
(Although this depends on what exactly is unlocked and with what method,something your posts do not state)
Click to expand...
Click to collapse
I mean I bought it off contract, for the full price of 500 dollars. There are no carrier markings on it either. I bought it from an independent shop, not from a carrier store.
Nonverbose said:
If the device is unlocked you can just extract the update zip file and flash it manually. Probably just needs boot.img
Click to expand...
Click to collapse
Do you mean extract the rom.zip from the RUU.exe, flash the rom.zip as PG32IMG.zip in the bootloader and then fastboot flash boot.img (extracted from PG32IMG.zip)? I've tried that, I'll try it again.
Thanks for the help by the way, and happy new year!
exaltedbladder said:
I mean I bought it off contract, for the full price of 500 dollars. There are no carrier markings on it either. I bought it from an independent shop, not from a carrier store.
Do you mean extract the rom.zip from the RUU.exe, flash the rom.zip as PG32IMG.zip in the bootloader and then fastboot flash boot.img (extracted from PG32IMG.zip)? I've tried that, I'll try it again.
Thanks for the help by the way, and happy new year!
Click to expand...
Click to collapse
Actually just meant the boot.img as there seems to be a common trend of it failing on this phone with symptoms of stopping at splash screen.
On that note when flashing img file in fastboot you need to specify the partition you wish to flash, which is missing in your post, it should read:
fastboot flash(command) boot(partition) boot.img(file)
Minus the brackets of course.
Happy new year to you also
Flashing the boot.img still isn't working. I've tried all three boot.imgs.
EDIT: I've been doing
"fastboot flash boot boot.img"
Flash a custom recovery and boot into it. Wipe cache, dalvik cache and do factory reset. Restart phone and give it 5-10 mins boot time in case its trying to rebuild dalvik cache
@tpbklake can you see what filesystem stock rom is using please
Nonverbose said:
Flash a custom recovery and boot into it. Wipe cache, dalvik cache and do factory reset. Restart phone and give it 5-10 mins boot time in case its trying to rebuild dalvik cache
@tpbklake can you see what filesystem stock rom is using please
Click to expand...
Click to collapse
The stock ROM uses EXT3 for the filesystem.
Nonverbose said:
Flash a custom recovery and boot into it. Wipe cache, dalvik cache and do factory reset. Restart phone and give it 5-10 mins boot time in case its trying to rebuild dalvik cache
Click to expand...
Click to collapse
I used CWM, and it's just like before. It shows the htc screen for around 10 seconds then reboots into recovery.
exaltedbladder said:
I used CWM, and it's just like before. It shows the htc screen for around 10 seconds then reboots into recovery.
Click to expand...
Click to collapse
Flash 4ext recovery so you can confirm that your partitions are formatted to the correct filesystem (ext3) I'm not 100% but I think ics may use ext4
Nonverbose said:
Flash 4ext recovery so you can confirm that your partitions are formatted to the correct filesystem (ext3) I'm not 100% but I think ics may use ext4
Click to expand...
Click to collapse
Yeah, great idea. I had a feeling it was to do with ICS. I'll get right on that.
Whelp, looks like they're all ext3 unfortunately.
exaltedbladder said:
Whelp, looks like they're all ext3 unfortunately.
Click to expand...
Click to collapse
OK, here is a thought after rereading your original post. You currently have HBOOT 2.00.0000 and it has been unlocked via HTCDEV.com, right?
In order to flash a RUU with HBOOT 2.00.0000 in place, it must be in a LOCKED/RELOCKED state. So one suggestion you could try is go into FASTBOOT mode and enter
fastboot oem lock
to relock and then try and run the Sense 3.0 RUU that you attempted in the first post.
tpbklake said:
OK, here is a thought after rereading your original post. You currently have HBOOT 2.00.0000 and it has been unlocked via HTCDEV.com, right?
In order to flash a RUU with HBOOT 2.00.0000 in place, it must be in a LOCKED/RELOCKED state. So one suggestion you could try is go into FASTBOOT mode and enter
fastboot oem lock
to relock and then try and run the Sense 3.0 RUU that you attempted in the first post.
Click to expand...
Click to collapse
Okay, it wasn't locked before. After issuing the command, the bootloader now says
*** RELOCKED ***
*** Security Warning ***
at the top. I tried flashing the PG32IMG.zip, but now it's giving me a CID error. I did getvar all to find out out my cidnum is HTC__621 while in the android-info.txt for the RUU it is HTC__622. Is it enough to edit the android-info.txts or do I need a goldcard or something else to flash the RUU? I'm going to try the other RUUs as well.
EDIT: I just checked all my RUUs. None of them are HTC__621. The closest is HTC__622. Yikes.
exaltedbladder said:
Okay, it wasn't locked before. After issuing the command, the bootloader now says
*** RELOCKED ***
*** Security Warning ***
at the top. I tried flashing the PG32IMG.zip, but now it's giving me a CID error. I did getvar all to find out out my cidnum is HTC__621 while in the android-info.txt for the RUU it is HTC__622. Is it enough to edit the android-info.txts or do I need a goldcard or something else to flash the RUU? I'm going to try the other RUUs as well.
EDIT: I just checked all my RUUs. None of them are HTC__621. The closest is HTC__622. Yikes.
Click to expand...
Click to collapse
Then you will need a goldcard to try and flash.
tpbklake said:
Then you will need a goldcard to try and flash.
Click to expand...
Click to collapse
All the guides I've found require me to install GoldCardHelper from the Android Market or to use adb. My phone doesn't work. Is there any other way to create a goldcard?
exaltedbladder said:
All the guides I've found require me to install GoldCardHelper from the Android Market or to use adb. My phone doesn't work. Is there any other way to create a goldcard?
Click to expand...
Click to collapse
Do you have another phone that you could use?
---------- Post added at 03:46 PM ---------- Previous post was at 03:31 PM ----------
tpbklake said:
Do you have another phone that you could use?
Click to expand...
Click to collapse
OK, so once again reading through this thread, here is what the current status of your phone is:
HBOOT 2.00.0000 RELOCKED
You can boot into HBOOT USB and FASTBOOT USB mode, right? There is currently no RUU for your CID, so a goldcard is needed.
When you were attempting to flash the boot.img files in FASTBOOT mode, the phone was in a LOCKED state, not the UNLOCKED state, right?
Since you can't boot the phone so you can use adb.exe plus the fact that zergRush cannot temp root HBOOT 2.00.0000 anyway, you could try going to HTCDEV.com and follow the unlock bootloader procedure to change HBOOT to UNLOCKED. Then you could retry flashing a boot_signed.img from the PG32IMG.zip file in FASTBOOT mode.
Hey guys,
Right, I have a hardware issue with my phone so need to return it to Three UK.
Currently I have Android Revolution HD 11 on my phone and have updated to 2.17 firmware, s-off.
So I need stock, firmware to be reverted to 1.28.771 and to change my CID to H3G__001 (currently HTC__001). There doesn't appear to be an RUU for three.
First off I'm assuming the H3G nandroid backup in the "[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads" thread doesn't actually touch the firmware so it would remain at 2.17?
So my thinking is this:
Flash the generic europe RUU (do I need to lock my bootloader before doing this)? (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe)
Change CID to H3G__001
Nandroid restore of H3G ROM. (M7 CWM Nandroid Backup / CID H3G__001 / 1.28.771.x )
s-off to lock and remove tamper.
s-on.
OTA update?
Will this work?
Or does anyone have a link to the 1.28.771 firmware?
Thanks for the help.
Ardmanz said:
Hey guys,
Right, I have a hardware issue with my phone so need to return it to Three UK.
Currently I have Android Revolution HD 11 on my phone and have updated to 2.17 firmware, s-off.
So I need stock, firmware to be reverted to 1.28.771 and to change my CID to H3G__001 (currently HTC__001). There doesn't appear to be an RUU for three.
First off I'm assuming the H3G nandroid backup in the "[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads" thread doesn't actually touch the firmware so it would remain at 2.17?
So my thinking is this:
Flash the generic europe RUU (do I need to lock my bootloader before doing this)? (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe)
Change CID to H3G__001
Nandroid restore of H3G ROM. (M7 CWM Nandroid Backup / CID H3G__001 / 1.28.771.x )
s-off to lock and remove tamper.
s-on.
OTA update?
Will this work?
Or does anyone have a link to the 1.28.771 firmware?
Thanks for the help.
Click to expand...
Click to collapse
Any ideas?
You don't have to lock the bootloader and you need s-off to downgrade.
http://forum.xda-developers.com/showpost.php?p=42396455&postcount=20
Rest of the steps...well sounds good but unfortunatelly i'm not expert so dunno
I'm really interested if it works this way for you as i have a VF-uk one, and once i have to go back to stock this info would be really helpful.
Please let we know your progress
Good luck
prodizo said:
You don't have to lock the bootloader and you need s-off to downgrade.
http://forum.xda-developers.com/showpost.php?p=42396455&postcount=20
Rest of the steps...well sounds good but unfortunatelly i'm not expert so dunno
I'm really interested if it works this way for you as i have a VF-uk one, and once i have to go back to stock this info would be really helpful.
Please let we know your progress
Good luck
Click to expand...
Click to collapse
Hey,
Yup this worked perfectly (almost). Reset your CID to your originally carriers before running the nandroid backup or it will be missing your carriers boot screen.
The only thing is the recovery seems to be missing. I'd expect the HTC recovery to load when selecting it from the bootloader but all I get is a red triangle. I obviously need to sort this before sending it back (Monday).
Any ideas?
I haven't s-on'd yet because I want to sort out recovery first. That should be pretty simple though.
I guess I just need a link to stock recovery.img.
Just tried and mine does same. I have stock recovery so thats fine.
Hope you get a nice new one:laugh:
Cheers
Stock recovery will display a red triangle..your all set
Sent from my HTC One using xda app-developers app
Yup. I just realised. Completely 100% back to stock now with s-on.
It's been quite a journey. Hopefully they can repair it quickly so I can get ARHD 11 back on.
Ardmanz said:
Yup. I just realised. Completely 100% back to stock now with s-on.
It's been quite a journey. Hopefully they can repair it quickly so I can get ARHD 11 back on.
Click to expand...
Click to collapse
Ardmanz said:
Yup. I just realised. Completely 100% back to stock now with s-on.
It's been quite a journey. Hopefully they can repair it quickly so I can get ARHD 11 back on.
Click to expand...
Click to collapse
Would you make the step by step?
It would really helpful
If I ain't wrong,
1. Get the RUU's
2. Change CID to HTC_001 before flashing RUU
3. Flash RUU
4. Write original CID
5. Nandroid Restore
6. Re S-ON with Revone
Is that right?
Grand_Goblin said:
Would you make the step by step?
It would really helpful
If I ain't wrong,
1. Get the RUU's
2. Change CID to HTC_001 before flashing RUU
3. Flash RUU
4. Write original CID
5. Nandroid Restore
6. Re S-ON with Revone
Is that right?
Click to expand...
Click to collapse
Yup, those are the exact steps that I took.
Note* make sure you just boot into custom recovery and don't actually flash it when restoring your nandroid backup. Having custom recovery on your device is a dead give away.
Grand_Goblin said:
Would you make the step by step?
It would really helpful
If I ain't wrong,
1. Get the RUU's
2. Change CID to HTC_001 before flashing RUU
3. Flash RUU
4. Write original CID
5. Nandroid Restore
6. Re S-ON with Revone
Is that right?
Click to expand...
Click to collapse
Ardmanz said:
Yup, those are the exact steps that I took.
Note* make sure you just boot into custom recovery and don't actually flash it when restoring your nandroid backup. Having custom recovery on your device is a dead give away.
Click to expand...
Click to collapse
sorry man, but "flash it" refers to?
I don't get it and I don't wanna mess up
Grand_Goblin said:
sorry man, but "flash it" refers to?
I don't get it and I don't wanna mess up
Click to expand...
Click to collapse
Normally you would use the following command to install custom recovery:
Code:
fastboot flash recovery recovery.img
Use this command instead:
Code:
fastboot boot recovery.img
That allows you to boot into custom recovery without actually installing it onto your phone.
Ardmanz said:
Normally you would use the following command to install custom recovery:
Code:
fastboot flash recovery recovery.img
Use this command instead:
Code:
fastboot boot recovery.img
That allows you to boot into custom recovery without actually installing it onto your phone.
Click to expand...
Click to collapse
matursuwun - Thank You so much! (in Javanese)
I just took the sprint update, and I am soft but locked. Originally used revone but can't unlock after update.
I am still soff what are my options. All I want to do is reinstall su.
Anyone?
htc dev
This is why we NEVER take an OTA HTC makes it harder and harder for us to modify our devices with every update
So basically on the HTC one soff does nothing if your also locked? Nothing I can do except HTC dev?
tws101 said:
So basically on the HTC one soff does nothing if your also locked? Nothing I can do except HTC dev?
Click to expand...
Click to collapse
HTC Dev unlock will allow you to flash a recovery, root, and install a custom rom if you so choose. Realize however that most custom roms are based on 1.29 and will likely have camera and wifi issues with the new firmware.
If you're S-OFF, you can RUU back to 1.29 and be a-okay, provided that the Sprint OTA does nothing beneficial that you need. If you're not S-OFF, it is possible to S-OFF via revone 0.21 and ADB. Most will tell you that it cannot be done but I managed it with little effort. Just don't try using it with a terminal app on the device, it probably won't work. ADB shell + revone will S-OFF someone locked on 1.31.x.
Personal experience, the 1.31 firmware and update made my cell reception weak as hell and wifi unusable at times even when I had full signal. It apparently activated HD voice, but I haven't noticed. That's what prompted me to S-OFF 1.31 and downgrade with a RUU.
If I ruu back will I have to clear the phones memory? I assume yes.
Is there anyway to just install superuser?
Is there anyway to unlock?
I am soff. Locked on the new firmware.
tws101 said:
If I ruu back will I have to clear the phones memory? I assume yes.
Is there anyway to just install superuser?
Is there anyway to unlock?
I am soff. Locked on the new firmware.
Click to expand...
Click to collapse
Long as you're S-OFF, you should be able to flash a 1.29 RUU (like I did) and downgrade. If you dev unlock, you can flash a recovery from fastboot and install supersu from there. There's a supersu flashable zip here:http://download.chainfire.eu/315/
So flash this http://forum.xda-developers.com/showthread.php?t=2250904
Then revone will grant me unlock again then I can use twrp to flash su again?
Correct?
I flashed that RUU and still had S-OFF. Even if you, for whatever reason, lose S-OFF - just HTC Dev unlock. You can flash a recovery, install supersu, and be about your day without ever touching S-OFF.
I have not done anything yet but since I am soff can't I flash a zip from fastboot?
Meaning just flash superuser even though I am locked?
If this is possible does anyone have a link to superuser with an androidinfo.txt with it so I can flash it in fastboot?
tws101 said:
I have not done anything yet but since I am soff can't I flash a zip from fastboot?
Meaning just flash superuser even though I am locked?
If this is possible does anyone have a link to superuser with an androidinfo.txt with it so I can flash it in fastboot?
Click to expand...
Click to collapse
Download a recovery,
fastboot flash recovery downloadedimage.img
Then download the supersu zip I linked in one of my last posts. Reboot into the recovery and flash the zip. Mission accomplished.
Even without S-Off, all of this can be done. Even custom roms can be flashed on the One with just HTC Dev unlock. I'm not sure what you mean by s-off but locked. Just make sure you're HTC dev unlocked or S-Off, follow the steps above, and all of your problems will go away.
sshede said:
Download a recovery,
fastboot flash recovery downloadedimage.img
Then download the supersu zip I linked in one of my last posts. Reboot into the recovery and flash the zip. Mission accomplished.
Even without S-Off, all of this can be done. Even custom roms can be flashed on the One with just HTC Dev unlock. I'm not sure what you mean by s-off but locked. Just make sure you're HTC dev unlocked or S-Off, follow the steps above, and all of your problems will go away.
Click to expand...
Click to collapse
I am LOCKED with S-OFF
This command will not work: (Already tried it)
fastboot flash recovery downloadedimage.img
I want to avoid HTC DEV as it clears the phone.
It is my understanding I can use the fastboot flash command if I flash a zip with a android-info.txt file in it. According to the forums that should work since I am S-OFF. Instead of flashing a recovery I was thinking of just flashing SU that way but havn't found an SU pre-prepared to flash that way.
tws101 said:
I am LOCKED with S-OFF
This command will not work: (Already tried it)
fastboot flash recovery downloadedimage.img
I want to avoid HTC DEV as it clears the phone.
It is my understanding I can use the fastboot flash command if I flash a zip with a android-info.txt file in it. According to the forums that should work since I am S-OFF. Instead of flashing a recovery I was thinking of just flashing SU that way but havn't found an SU pre-prepared to flash that way.
Click to expand...
Click to collapse
My understanding is that with a locked bootloader, you're still going to be locked out of changing boot-time code (given that the entire purpose of a locked bootloader is to prevent modifications to onboard software that could compromise secure information), unless you're using a runtime exploit (which is generally for rooting only, and I don't know that there are any such exploits for the Sprint One).
Not sure if this would work but if you used revone try unlock command in step 6 of OP http://forum.xda-developers.com/showthread.php?t=2314582
Sent from my HTCONE using Tapatalk 4
krazyflipj said:
Not sure if this would work but if you used revone try unlock command in step 6 of OP http://forum.xda-developers.com/showthread.php?t=2314582
Sent from my HTCONE using Tapatalk 4
Click to expand...
Click to collapse
That was the very first thing I tried.
After updating via OTA i ran revone with -u and got segment fault. Based on the revone thread it will no longer work once you take that OTA. Everyone is getting the segment fault after OTA.
I figured with an update.zip and using fastboot flash update.zip If the update putting an Android-info.txt file might work. I know fastboot flash recovery rec.img fails.
tws101 said:
I am LOCKED with S-OFF
This command will not work: (Already tried it)
fastboot flash recovery downloadedimage.img
I want to avoid HTC DEV as it clears the phone.
It is my understanding I can use the fastboot flash command if I flash a zip with a android-info.txt file in it. According to the forums that should work since I am S-OFF. Instead of flashing a recovery I was thinking of just flashing SU that way but havn't found an SU pre-prepared to flash that way.
Click to expand...
Click to collapse
Okay, now I understand a bit better. Why not just take the 11 minutes required to back up whats on the phone, then HTC dev unlock?
Just to update everyone Indirect helped me solve this issue.
1. Create txt file named android-info.txt
Data in file 4 lines
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
hbootpreupdate:3
2. Get recovery of your choice and rename it recovery.img
3. Zip files up into zip file name of zip does not matter
4. Run the following fastboot commands
fastboot oem rebootRUU
fastboot flash zip nameofzipfile.zip
fastboot reboot
You now have a recovery of your choice on a LOCKED S-OFF system and can re-flash superuser.
Thank to Indirect!!!
I'd like to return to 4.1.2, but I have updated radio and firmware. Can anyone give me a link to the old firmware? How can I downgrade my firmware, the same way I updated it?
Edit: I finally found the old firmware. You need to be s-off in order to flash it. No need to flash RUU and relock/unlock bootloader
It contains firmware 3.04.651.2 radio and modems and touch panel driver.
Go to fastboot and rename it to Firmware
fastboot oem rebootRUU
fastboot flash zip Firmware
fastboot reboot-bootloader
http://www.mediafire.com/?f1swashpy0gl7hk
First you will need to root, use Revone to gain S-Off with their tutorial in the Development Sections(All Steps Except For "-P" Command) and then you will be able to Downgrade Firmware through an RUU. If you are planning on staying stock then I suggest using Revone to also Lock the bootloader and remove tampered instead of having Relocked and Tampered on there. If not then just use Revone to remove tampered.
EPayne123 said:
First you will need to root, use Revone to gain S-Off with their tutorial in the Development Sections(All Steps Except For "-P" Command) and then you will be able to Downgrade Firmware through an RUU. If you are planning on staying stock then I suggest using Revone to also Lock the bootloader and remove tampered instead of having Relocked and Tampered on there. If not then just use Revone to remove tampered.
Click to expand...
Click to collapse
I am already s-off using revone. I was wondering if I could just flash the old firmware without flashing the whole ruu? After downgrading I will flash a custom rom. My question is where can I find the old firmware( without hboot in order not to loose s-off)?
Sent from my HTCONE using Tapatalk 4
elvisypi said:
I am already s-off using revone. I was wondering if I could just flash the old firmware without flashing the whole ruu? After downgrading I will flash a custom rom. My question is where can I find the old firmware( without hboot in order not to loose s-off)?
Sent from my HTCONE using Tapatalk 4
Click to expand...
Click to collapse
You won't lose S-Off. RUUs do not mess with the Bootloaders Security Flag
I am currently running Viper Rom version 1.8.0 and want to flash the latest version. From what I understand, the best way to do this is to go back to stock and flash version 3.2.1. I do NOT have a stock nandroid backup so was trying to flash with RUU but can't do so unless I am s-off. So I installed Sunshine but it comes up with this: Debug Kernel/Ramdisk - Your device has a debuggable ramdisk (ro.debuggable=1). You need to flash a non-debuggable boot.img, stock would be best. So in order to go back to stock I need to have S-off, but in order to have s-off I need to go back to stock? Somebody please help me with this conundrum.
Bungleboy84 said:
I am currently running Viper Rom version 1.8.0 and want to flash the latest version. From what I understand, the best way to do this is to go back to stock and flash version 3.2.1. I do NOT have a stock nandroid backup so was trying to flash with RUU but can't do so unless I am s-off. So I installed Sunshine but it comes up with this: Debug Kernel/Ramdisk - Your device has a debuggable ramdisk (ro.debuggable=1). You need to flash a non-debuggable boot.img, stock would be best. So in order to go back to stock I need to have S-off, but in order to have s-off I need to go back to stock? Somebody please help me with this conundrum.
Click to expand...
Click to collapse
RUU's do not require s-off.
Bungleboy84 said:
I am currently running Viper Rom version 1.8.0 and want to flash the latest version. From what I understand, the best way to do this is to go back to stock and flash version 3.2.1. I do NOT have a stock nandroid backup so was trying to flash with RUU but can't do so unless I am s-off. So I installed Sunshine but it comes up with this: Debug Kernel/Ramdisk - Your device has a debuggable ramdisk (ro.debuggable=1). You need to flash a non-debuggable boot.img, stock would be best. So in order to go back to stock I need to have S-off, but in order to have s-off I need to go back to stock? Somebody please help me with this conundrum.
Click to expand...
Click to collapse
As stated above you do not have to be S-off to run a RUU. That would defeat the purpose of having a RUU if that were the case, but it's not. You simply have to relock your bootloader while S-on prior to running the RUU.
The command to relock your bootloader is fastboot oem lock.
OK so its relock bootloader then flash ruu will that allow sunshine to s-off?
Mendoza007 said:
OK so its relock bootloader then flash ruu will that allow sunshine to s-off?
Click to expand...
Click to collapse
It's best to run Sunshine from a stock ROM, so yes. Some ROM's contain a modified kernel that causes Sunshine to error out, so stock is your best bet. If you don't want to run the RUU, OMJ has a bunch of stock rooted ROM's in his RUU thread that you should be able to use, also.
Keep in mind that running a RUU will wipe out your internal storage so make sure you back it up before you run it. It will not affect your external SD card, if one is installed.