I'm s-off, super cid, and hate W8.1 adb works fine, so does fast boot, but Windows 8.1 won't let me flash anything. It's there a stock Rom (any version) I can flash in recovery? One that will take Sprint ota's and I can still keep s-off and recovery. I could flash stock ruu on w7 and keep root, but no longer have access to anything below 8.1
jpwhre said:
I'm s-off, super cid, and hate W8.1 adb works fine, so does fast boot, but Windows 8.1 won't let me flash anything. It's there a stock Rom (any version) I can flash in recovery? One that will take Sprint ota's and I can still keep s-off and recovery. I could flash stock ruu on w7 and keep root, but no longer have access to anything below 8.1
Click to expand...
Click to collapse
What error do you get when flashing? Also try flashing the ODEX ROM from here. You should be able to take Sprint OTAs I think but I'm not sure.
Related
I want to get back to stock Sense 5 and unroot my device. I was on AOKP and tried using the RUU to restore my device. Unfortunately, I failed to realize I had updated my One to software version 1.31.xxx, and the RUU tool I was using was for 1.29.xxx. So now I have no OS on my phone. I can get to bootloader and TWRP recovery, but neither are really useful to me. At this point I'd be satisfied just flashing any ROM. Pushing via adb isn't working because it won't recognize my device. When I try to start sideload in TWRP I get the error "E: Unable to mount '/data'", so I can't load a ROM that way either...If someone could help me out, I'd be forever grateful.
EDIT: After formatting data I was able to sideload a ROM
none
Did you relock the bootloader first?
Try plugging it into the computer and type ADB reboot recovery, that will take you into recovery. From there you should be able to lock it and run your RUU
musicman625 said:
Did you relock the bootloader first?
Try plugging it into the computer and type ADB reboot recovery, that will take you into recovery. From there you should be able to lock it and run your RUU
Click to expand...
Click to collapse
I was able to get a ROM on my phone. From what I can gather, you can't downgrade from 1.31 to 1.29 with RUU unless you have S-OFF. I guess I'll wait until someone makes a RUU tool for 1.31. What I don't understand though is that viperROM is based off the 1.29 firmware, but the RUU tool I used still says my phone is using 1.31 (thus, why it won't work).
Gnex,,if you s-off using Revone,you can run any RUU and get back to box stock
Sent from my HTCONE using xda premium
I have a Sprint HTC One. I previously unlocked the boot loader and installed clock work mod recovery. I achieved SU and partial Super CID. I tried flashing Viper ROM after relocking the boot loader, which failed. when I went to reboot the phone, I was in boot loader without a system ROM. so I installed the stock ROM and updated firmware. the phone now works. however, I lost su and my custom recovery. I tried to unlock the bootloader , reinstall Viper, but neither will work it fails every time. I am experienced at following instructions on this website, but I lack the knowledge to know exactly what I am doing with each action.
Please help me get either su, custom recovery or the boot loader unlocked. I still have S-off and I am at a loss. Thank you!
patrickgartner said:
I have a Sprint HTC One. I previously unlocked the boot loader and installed clock work mod recovery. I achieved SU and partial Super CID. I tried flashing Viper ROM after relocking the boot loader, which failed. when I went to reboot the phone, I was in boot loader without a system ROM. so I installed the stock ROM and updated firmware. the phone now works. however, I lost su and my custom recovery. I tried to unlock the bootloader , reinstall Viper, but neither will work it fails every time. I am experienced at following instructions on this website, but I lack the knowledge to know exactly what I am doing with each action.
Please help me get either su, custom recovery or the boot loader unlocked. I still have S-off and I am at a loss. Thank you!
Click to expand...
Click to collapse
... simply flash appropriate custom recovery from fastboot. boot into recovery and try to reboot from there and it will ask you if you want to root the device. root it. reboot normally and you will see SU app. open it and update binaries. thats it, you are rooted ...
Failure
Okay, so I appreciate the attention and help, but it fails to install recovery, flash roms, or unlock the bootloader from fastboot. I can flash firmware and run an RUU from my desktop. As well, I can run the Sprint OTA update from the phone, but I have not done that yet. I have hboot 1.55. I have tried to flash things from terminal emulator, but I'm having trouble. I can access and use the phone for Sprint, but the CID says 11111 and won't let me change carriers. Once again, I have S-off.
Thoughts:
Run Sprint update and try to start from scratch, if all else fails, sell it.
Can I flash SU from bootloader? I haven't tried that yet, although I doubt it will work given my other problems.
patrickgartner said:
Okay, so I appreciate the attention and help, but it fails to install recovery, flash roms, or unlock the bootloader from fastboot. I can flash firmware and run an RUU from my desktop. As well, I can run the Sprint OTA update from the phone, but I have not done that yet. I have hboot 1.55. I have tried to flash things from terminal emulator, but I'm having trouble. I can access and use the phone for Sprint, but the CID says 11111 and won't let me change carriers. Once again, I have S-off.
Thoughts:
Run Sprint update and try to start from scratch, if all else fails, sell it.
Can I flash SU from bootloader? I haven't tried that yet, although I doubt it will work given my other problems.
Click to expand...
Click to collapse
... slow down and calm down. i think you are hasting things. dont worry and do whatever you wanna do step by step. its not clear to me what you want to achieve, you wanna switch carriers ? want ota ? want custom rom ? you are s-off but cant flash recovery !!!! please explain exactly what you want and what errors are you getting and doing what
i think you cant have SU from bootloader and certainly terminal emulator doesnt flash recoveries and rom., fastboot does recovery and recovery flashes rom. dont play with your phone like this without proper knowledge. ask whatever doubts you have prior doing anything ...
Straight Talk
You're funny. Yes, I am in a hurry to use my new phone... Ultimately, I want to use it on straight talk. It is S-off, and the boot loader will not unlock, the phone won't flash a recovery and I have lost su. It's the weirdest thing! I haven't had this problem before. Usually you flash stock firmware and ruu and you're back at square one, but not this time.
I would pay you to visit my problem via Teamviewer? Interested?
-Patrick
patrickgartner said:
You're funny. Yes, I am in a hurry to use my new phone... Ultimately, I want to use it on straight talk. It is S-off, and the boot loader will not unlock, the phone won't flash a recovery and I have lost su. It's the weirdest thing! I haven't had this problem before. Usually you flash stock firmware and ruu and you're back at square one, but not this time.
I would pay you to visit my problem via Teamviewer? Interested?
-Patrick
Click to expand...
Click to collapse
... Dear if you wanna network unlock your phone, follow the steps exactly as described.
1. Flash this and only this RUU (first link - http://forum.xda-developers.com/showthread.php?t=2250904 ), no need to relock bootloader if unlocked as you are s-off.
2. Download the recovery for sprint variant and flash it in fastboot mode (fastboot flash recovery recovery.img) (link - http://forum.xda-developers.com/showthread.php?t=2651035).
3. Boot in to recovery and press reboot and then system, it will ask for your permission to root, root it. restart normally and open SU app and update its binaries. phone will reboot itself in recovery and back in normal mode. You will be rooted then. :victory:
then ping me for sim unlock ...
im not really sure what happened...
i was trying to root then s-off today. i got htcdev.com unlocked, was able to flash custom recovery (philz) and flash superuser. when i tried to s-off (firewater) i got the whelp this sucks error (im still not really sure why or what that means)
i tried to then flash a custom rom, and now it wont boot past the htc flash screen with the red text ( this may be because i didnt flash firmware with the rom i tried to install?)
i have tried to flash firmware, and run a ruu and nothing is doing anything...
please please please someone help
What firmware version do you currently have installed? What ROM were you trying to flash?
Take a look at this thread below for info on how to flash the latest RUU. If you have a HK version you'll need the HK RUU. After you run the RUU you'll need to reroot your phone. You'll also need to use the SunShine exploit to gain S-off (the "whelp" message means Firewater won't work on your device). I also recommend Captain Throwback's TWRP 2.8.0.0. recovery.
http://forum.xda-developers.com/showthread.php?t=2880328
im not sure which of these are the firmware...
hboot - 3.16.0.0000
radio - 1.05.20.0321_2
os - 1.54.654.9
Firmware is your radio version. Use the RUU from the link below. Follow the instructions for the manual system update. You'll need to relock your bootloader beforehand using the command "fastboot oem lock" while connected via Fastboot USB mode.
http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/
ohh i forgot about having to relock for ruu
trying that now
I downloaded the ruu, but when I run it it can't find my phone... I think it wants me to be booted into the ROM but I can't boot the only thing I can access is the bootloader
knock.back said:
I downloaded the ruu, but when I run it it can't find my phone... I think it wants me to be booted into the ROM but I can't boot the only thing I can access is the bootloader
Click to expand...
Click to collapse
RUU's are run from the bootloader...make sure it says fastbootusb when connected to your PC.
it did say that
Make sure you have HTC Sync installed on your computer.
I have that installed too... I got it to boot, ended up flashing different recovery then a different rom and that worked... Never got the ruu to work tho... Anyway, thanks for your help
As thread says, now boot looping. Did fastboot reboot at the end of the upgrade and phone tried to reboot then stayed off.
Trying to go into recovery but that blacks out for me as well.
saw this thread pop up in the "similar threads" field as i was creating this post so guess i should give it a go? http://forum.xda-developers.com/showthread.php?t=1936852
basically says to just reinstall a custom recovery and flash a new rom and i'm all set (i think).
you need unlock device again and flash custom recovery
1)Unlock your device
2)flash custom recovery
3)flash rom
Click to expand...
Click to collapse
If that's the case my phone still says i'm unlocked. So yeah, not sure what to do here. Thanks in advance for any help.
My guess is the new kernel/boot.img is not compatible with the rom you are running.
1. You could try a dirty flash of your current rom.(don't wipe anything just flash the rom)
2. Flash a 5.03.651.3 stock rooted rom.
3. Restore a good backup.
4. Run the 5.03.651.3 RUU and start fresh.
BD619 said:
My guess is the new kernel/boot.img is not compatible with the rom you are running.
1. You could try a dirty flash of your current rom.(don't wipe anything just flash the rom)
2. Flash a 5.03.651.3 stock rooted rom.
3. Restore a good backup.
4. Run the 5.03.651.3 RUU and start fresh.
Click to expand...
Click to collapse
Hi, yeah i see.
I went ahead and flashed a TWRP recovery i had labeled as safe and managed to get back into recovery. I'm now on one of my original stock backups which i set right before i went into custom rom mode. So got some functionality back at least.
I will now attempt the RUU process. Please correct me if i'm wrong, but after i complete it, i have to root my phone again? And s-off shouldn't change?
Since you are s-off you don't need to re-lock your bootloader, so all you should need to do after the RUU is re-flash twrp,flash SuperSU if you are going to stay stock rooted or flash a custom rom and you should be good to go.
BD619 said:
Since you are s-off you don't need to re-lock your bootloader, so all you should need to do after the RUU is re-flash twrp,flash SuperSU if you are going to stay stock rooted or flash a custom rom and you should be good to go.
Click to expand...
Click to collapse
awesome, you are the best
thanks again for your help, i would have been in some kind of misery without it lol.
nickhx2 said:
awesome, you are the best
thanks again for your help, i would have been in some kind of misery without it lol.
Click to expand...
Click to collapse
No worries good luck
Hi all,
So let me explain. I was given a HTC One for repair and the person just told me that her child did something wrong in the settings and the phone didn't boot anymore. The phone was on an older stock ROM and didn't get past the HTC One logo. Something was corrupted because the startup sound was cutting off before it had played like it should.
anyways: the phone is S-ON and I have unlocked the bootloader via HTCDev. I can install CWM, CWM Touch and TWRP but can't install any Sense rom because of the antique HBoot 1.56. I can however boot into CM 10.2.1 stable with no problems and ARHD 9.4 but with nou touch. On both ROMs firewather and rumrunner fail (usb debugging is on and root also for adb and apps).
Possible fixes I think off:
-Install an older ARHD version like 42 or 61 or 62 that is compitable with my firmware (but can't find them anywhere);
-install an insecure kernel compatible with CM10.2 (can't find one);
-Somehow just revert back to a Sense rom, wich I can't.
I just want S-off but every s-off tool fails. Is there another way to instal RUU exe or ZIP without S-OFF or at least upgrade the damn antique radio image that belongs in a museum ?
Thanks in advance
soulaiman said:
Hi all,
So let me explain. I was given a HTC One for repair and the person just told me that her child did something wrong in the settings and the phone didn't boot anymore. The phone was on an older stock ROM and didn't get past the HTC One logo. Something was corrupted because the startup sound was cutting off before it had played like it should.
anyways: the phone is S-ON and I have unlocked the bootloader via HTCDev. I can install CWM, CWM Touch and TWRP but can't install any Sense rom because of the antique HBoot 1.56. I can however boot into CM 10.2.1 stable with no problems and ARHD 9.4 but with nou touch. On both ROMs firewather and rumrunner fail (usb debugging is on and root also for adb and apps).
Possible fixes I think off:
-Install an older ARHD version like 42 or 61 or 62 that is compitable with my firmware (but can't find them anywhere);
-install an insecure kernel compatible with CM10.2 (can't find one);
-Somehow just revert back to a Sense rom, wich I can't.
I just want S-off but every s-off tool fails. Is there another way to instal RUU exe or ZIP without S-OFF or at least upgrade the damn antique radio image that belongs in a museum ?
Thanks in advance
Click to expand...
Click to collapse
Hboot 1.56 is not that old the current is 1.57! You can install RUU being S-ON the RUU must be the same or higher version, signed and the bootloader has to be locked/relocked. For Sense ROMs you might try TWRP 2.6.3.3 it seems to work best. ARHD 81 should work with your phone you have to wipe in Aroma before you install it.
I couldn't get ARHD 81 to work, but if someone is in the same situation here is what I did:
1) Relock your bootloader with this command:
fastboot oem lock
2) download this signed radio file : https://www.androidfilehost.com/?w=file-thanks&fid=23622183712460395&mid=70&download_id=t0kvkiiupbv0r5gakftasij7d5&tid=1412801244&hc=731cbdd91c39e4104b17bb47e6236fd9614838fa88b158009a1006be6b2ec5ea
3) Place the file in the same platform-tools directory for ease of use and insert this command:
fastboot oem rebootRUU
4) Once the phone reboots into a black HTC screen enter:
fastboot flash zip <name_of_the_file_here_without_quotes>
5) Normally it should succeed and tell you to immediatly flush, if it fails reattempt to flash the zip and it will succeed.
6) Download your prefered Recovery, mine is CWM but TWRP is even better sometimes and enter:
fastboot reboot-bootloader and then fastboot flash recovery <recovery.img>
6B) EDIT: to be able to flash a recovery IMG with S-On you need to unlock you bootloader again.
fastboot flash unlocktoken Unlocktoken_bin or whatever your unlocktoken is called
Then accept the security warning on your phone with the volume keys and power key.
7) Once succeed enter recovery and flash Maximus HD
8) Once done please enter bootloader again by pressing vol- + power or bij selecting advanced, reboot bootloader in recovery.
9) Because we're S-On, we need to manually flash boot.img
fastboot flash boot boot.img and if you get bootloops fastboot erase cache
Once this is done you should be able to boot into the rom and everything should work. Flashing this has upgraded my hboot to 1.57. Now I will report if I succeed to get S-off.
Well I couldn't find an RUU that was signed and for my version. Also I don't know why but I couldn't get ARHD to work. Maybe I need s-off or another recovery but even with elemental X it didn't boot.
soulaiman said:
Well I couldn't find an RUU that was signed and for my version. Also I don't know why but I couldn't get ARHD to work. Maybe I need s-off or another recovery but even with elemental X it didn't boot.
Click to expand...
Click to collapse
Okay so what I want to suggest you do is for starters go in unlock the bootloader as re locking it before doing anything is pointless when once everything is fixed is when you'd need to do it. Also I recommend that you install the custom recovery first and flash the rom from there rather than trying to flash it using fastboot as then at least we can get a standard recovery message which may be easier to find an answer for, I recommend using the very latest twrp recovery from their site as that should be able to flash all roms but make sure you install a stock sense 6 rom as the phone needs to be on the latest update with the kk radios and obviously that means having an hboot of 1.57 which would allow you to install custom roms that are running on kk otherwise you'll have issues and if you've followed what I suggest and it doesn't work a logcat and even a video of what is actually happening will help a lot to see what's going on but first things first is make sure that phone is on the latest hboot and the latest radio.
Also what version of phone is it? is it a m7ul? I'll send you an ruu link if I know what version we're looking at
dc959 said:
Okay so what I want to suggest you do is for starters go in unlock the bootloader as re locking it before doing anything is pointless when once everything is fixed is when you'd need to do it. Also I recommend that you install the custom recovery first and flash the rom from there rather than trying to flash it using fastboot as then at least we can get a standard recovery message which may be easier to find an answer for, I recommend using the very latest twrp recovery from their site as that should be able to flash all roms but make sure you install a stock sense 6 rom as the phone needs to be on the latest update with the kk radios and obviously that means having an hboot of 1.57 which would allow you to install custom roms that are running on kk otherwise you'll have issues and if you've followed what I suggest and it doesn't work a logcat and even a video of what is actually happening will help a lot to see what's going on but first things first is make sure that phone is on the latest hboot and the latest radio.
Also what version of phone is it? is it a m7ul? I'll send you an ruu link if I know what version we're looking at
Click to expand...
Click to collapse
Thanks for the info and help.
The phone is allready been returned to the owner, it was just a repair job because the phone was out of waranty and nobody in this town could fix it. in fact, some idiot that didn't know what he was doing flashed the wrong hboot version (other phone/model) on it somehow and it was a mess.
I did manage to repair it trough an RUU I found I think or I did install a custom sense 6 rom... I don' remember exactly but it had a mismatching hboot version that's all I remember