Database Develop

[Q] Getting S-OFF with soju

Hey Guys,
I want to make my HTC ONE a Google Play Edtioin, so.I am currently trying to make my HTC ONE (international) S-Off with Soju. i hae USB- Debugging turned on, my Bottloader is unlocked and my phone is rooted.
Everytime i try to run soju i get this Erreor:
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (16/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
Does anyone know how to fix this?

Fabivons said:
Hey Guys,
I want to make my HTC ONE a Google Play Edtioin, so.I am currently trying to make my HTC ONE (international) S-Off with Soju. i hae USB- Debugging turned on, my Bottloader is unlocked and my phone is rooted.
Everytime i try to run soju i get this Erreor:
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (16/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
Does anyone know how to fix this?
Click to expand...
Click to collapse
just do what the output tells you to do!
Go to www.rumrunner.us and use the updated version.

LibertyMarine said:
just do what the output tells you to do!
Go to www.rumrunner.us and use the updated version.
Click to expand...
Click to collapse
Thanks for your reply!
I already have the newest version so that doesn't seem to be the problem :/

Fabivons said:
Thanks for your reply!
I already have the newest version so that doesn't seem to be the problem :/
Click to expand...
Click to collapse
hmm, what OS did you install? Try to install a 4.3 zip from here: http://android-revolution-hd.blogspot.ch/p/android-revolution-hd-mirror-site-var.html
And could you please provide a "fastboot getvar all"?
thanks
P.S.
Just in case you don't know... censor the IMEI and the build number... just everything that is unique on your phone!

LibertyMarine said:
hmm, what OS did you install? Try to install a 4.3 zip from here: http://android-revolution-hd.blogspot.ch/p/android-revolution-hd-mirror-site-var.html
And could you please provide a "fastboot getvar all"?
thanks
P.S.
Just in case you don't know... censor the IMEI and the build number... just everything that is unique on your phone!
Click to expand...
Click to collapse
I recently installed Android Revolution HD 41 and the ElementalX-m7-10.10.1 Kernel.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: /
(bootloader) imei: /
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3941mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Fabivons said:
I recently installed Android Revolution HD 41 and the ElementalX-m7-10.10.1 Kernel.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: /
(bootloader) imei: /
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3941mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
then I think you should try the STOCK 4.3 ROM... this should definitely work. I tested it twice.
http://www.androidrevolution.nl/downloader/download.php?file=One_3.62.401.1_odexed.zip
(Thanks @mike1986.)
Then download the newest version of rumrunner s off:
http://rumrunner.us/rumrunner_downloads/rumrunner_HTC_0.5.0.tgz
BUT carefully listen to the instructions on the site!
http://rumrunner.us/instructions/

Fabivons said:
I recently installed Android Revolution HD 41 and the ElementalX-m7-10.10.1 Kernel.
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
LibertyMarine said:
then I think you should try the STOCK 4.3 ROM... this should definitely work. I tested it twice.
http://www.androidrevolution.nl/downloader/download.php?file=One_3.62.401.1_odexed.zip
(Thanks @mike1986.)
Then download the newest version of rumrunner s off:
http://rumrunner.us/rumrunner_downloads/rumrunner_HTC_0.5.0.tgz
BUT carefully listen to the instructions on the site!
http://rumrunner.us/instructions/
Click to expand...
Click to collapse
Sorry to bug in, but may I recommend ARHD 31.6 (already rooted and unsecured kernel): http://forum.xda-developers.com/showthread.php?t=2183023

nkk71 said:
Sorry to bug in, but may I recommend ARHD 31.6 (already rooted and unsecured kernel): http://forum.xda-developers.com/showthread.php?t=2183023
Click to expand...
Click to collapse
No problem... I tried this one too but none of the ARHD worked for me.. anyways... rumrunner roots and flashed a unsecured kernel..

LibertyMarine said:
No problem... I tried this one too but none of the ARHD worked for me.. anyways... rumrunner roots and flashed a unsecured kernel..
Click to expand...
Click to collapse
When you got s-off, were you using the universal tool, or the firmware specific tools? as far as i can see, the universal tool (unlike the specific versions), need root and unsecured kernel (which the previous fw specific packages did by themselves).

nkk71 said:
When you got s-off, were you using the universal tool, or the firmware specific tools? as far as i can see, the universal tool (unlike the specific versions), need root and unsecured kernel (which the previous fw specific packages did by themselves).
Click to expand...
Click to collapse
I used both... for the new phone I used a universal tool... but I didn't root the phone previously...
Where did you see that? I read again through the whole page and couldn't find a order to install supersu or/and a unsecured kernel...
Maybe we shouldn't discuss this in the thread... we're highjacking this thread^^ Anyways, would be interesting where you got this information form

LibertyMarine said:
I used both... for the new phone I used a universal tool... but I didn't root the phone previously...
Where did you see that? I read again through the whole page and couldn't find a order to install supersu or/and a unsecured kernel...
Maybe we shouldn't discuss this in the thread... we're highjacking this thread^^ Anyways, would be interesting where you got this information form
Click to expand...
Click to collapse
I think it's okay, as long as we don't go forty posts on it; i saw it on while using rumrunner 0.5.0, ........ "ERROR: looks device is not rooted AND lacks an unsecure kernel. su or Fu!!!"
in fact ROM was rooted (odexed), but stock kernel, after installing custom kernel it was ok.

nkk71 said:
I think it's okay, as long as we don't go forty posts on it; i saw it on while using rumrunner 0.5.0, ........ "ERROR: looks device is not rooted AND lacks an unsecure kernel. su or Fu!!!"
in fact ROM was rooted (odexed), but stock kernel, after installing custom kernel it was ok.
Click to expand...
Click to collapse
Hmm... that's weird^^ but to be sure, I'd also do what you recommend... I just didn't have this problem.. don't know why.. the One was just out of the box, unlocked.. not even rooted^^ don't know how this exactly happend. Maybe I was on a previous verison of rumrunner s off... but I am pretty sure it was one of the universal.. I'm gonna dig around in my logfiles.. I stored everything somewhere on my HD...

LibertyMarine said:
Hmm... that's weird^^ but to be sure, I'd also do what you recommend... I just didn't have this problem.. don't know why.. the One was just out of the box, unlocked.. not even rooted^^ don't know how this exactly happend. Maybe I was on a previous verison of rumrunner s off... but I am pretty sure it was one of the universal.. I'm gonna dig around in my logfiles.. I stored everything somewhere on my HD...
Click to expand...
Click to collapse
AFAIK, rooted rom should work, and unsecured kernel is only "preferred".

nkk71 said:
AFAIK, rooted rom should work, and unsecured kernel is only "preferred".
Click to expand...
Click to collapse
sorry, because of a lack of English knowledge, I didn't understand what you meant with this message. Sorry, could you please try to say it with different words ?

LibertyMarine said:
sorry, because of a lack of English knowledge, I didn't understand what you meant with this message. Sorry, could you please try to say it with different words ?
Click to expand...
Click to collapse
yes, sorry: as far as i know (AFAIK), when rumrunner switched from specific to universal, the first thing that was needed was a rooted rom, with an unsecured kernel "preferred, but not necessary",
now (as the number of devices, etc. have been added), rumrunner works best with a ROM compatible with firmware, also rooted and unsecured kernel (ie kernel with write-protection disabled)

nkk71 said:
yes, sorry: as far as i know (AFAIK), when rumrunner switched from specific to universal, the first thing that was needed was a rooted rom, with an unsecured kernel "preferred, but not necessary",
now (as the number of devices, etc. have been added), rumrunner works best with a ROM compatible with firmware, also rooted and unsecured kernel (ie kernel with write-protection disabled)
Click to expand...
Click to collapse
Aha, ok.. thanks! Thank you very much for updating my knowledge!

I'm on stock, rooted, custom recovery and HBoot 1.55... This is what I did....
http://forum.xda-developers.com/showthread.php?t=2606577
Sent from my LG-D803 using xda app-developers app

Thank you so far!
I am going to try it out!
But I have one more question.. is there a fix for the big black menue button which appears in the Google Play Edition?

Fabivons said:
Thank you so far!
I am going to try it out!
But I have one more question.. is there a fix for the big black menue button which appears in the Google Play Edition?
Click to expand...
Click to collapse
oh mate.. what luck that I randomly saw your post... otherwise noone would have seen it.. remember: If you want to have an answer, quote or the other person won't be notified! This is just the way this forum works.. I am sorry.
Yes there is a fix:
Download Xposed Installer and install it on your device. Then install the framework... and search in the store(the one in xposed) for 3dot menu Mod... install it and the 3dot menu is away! To get the 3dot menu working, i can recommand Gravity box which you can use to remap the softkeys(longpress, doublepress)...
Edit:
Xposed doesn't work on ART Engine at the moment! Only dalvik works. Running it on ART will lead into a bootloop... but Xposed know this and disables ART before you run into further errors

Fabivons said:
Thank you so far!
I am going to try it out!
But I have one more question.. is there a fix for the big black menue button which appears in the Google Play Edition?
Click to expand...
Click to collapse
is everything fine?

[Q] Bootloop - Green HTC logo, sometimes Android

Ok, so I have admittedly really screwed up and I'm hoping someone here (or multiple someones) can help me out.
My major screwups:
No nandroid backup.
No s-off
I have Sprint
Current State:
I can get to fastboot, recovery and adb works fine. But no matter which recovery/rom combination I try, I get the same end result. My phone will boot to the "HTC One" screen, then go the green HTC logo/white background screen then reboot. Sometimes it stays active long enough to begin the "Welcome to Android" stuff (pick your language, wifi connection, etc...), but not nearly long enough to get through all the screens.
What I've tried so far:
Multiple recovery options including CWM and TWRP. CWM versions 6.0.4.3, 6.0.4.5 touch. TWRP versions 2.6.3.3, 2.6.3.4, 2.7.0.0.
ROMS: ARHD 31.6 and 62.0 (I know this doesn't work with Sprint), Viper 6.1 and some "stock" rom I found somewhere (filename One_4.19.401.11_odexed.zip).
I don't remember exactly the order, but I know I did TWRP 2.6.3.4 and ARHD 62.0 first. Then did Viper 6.1, then ARHD 31.6. Since then, I've tried every combination of recovery and ROM that I can think of.
Here's getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4205mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
I'm willing to try anything at this point. So suggestions are welcome. You're also welcome to berate me for the above mentioned screwups, but it won't be very helpful.
TIA

Goto_End said:
Ok, so I have admittedly really screwed up and I'm hoping someone here (or multiple someones) can help me out.
Multiple recovery options including CWM and TWRP. CWM versions 6.0.4.3, 6.0.4.5 touch. TWRP versions 2.6.3.3, 2.6.3.4, 2.7.0.0.
TIA
Click to expand...
Click to collapse
Those sound like version numbers for m7_u/ul models, flash proper TWRP for Sprint from here: http://techerrata.com/browse/twrp2/m7wls
(make sure to check MD5 on the download)

nkk71 said:
Those sound like version numbers for m7_u/ul models, flash proper TWRP for Sprint from here: (can't post links yet)
(make sure to check MD5 on the download)
Click to expand...
Click to collapse
Downloaded the 2.6.3.0 from the link you provided (checked md5), flashed recovery. Did an adb push to get the Viper ROM (also checked the md5) back to /sdcard and flashed the ROM. Same results as before.
Additional info:
Sometimes I will get "com.htc.htcdialer is not responding", sometimes not.
The screen will timeout on the green HTC logo screen. If I hit Power to bring it back to life, I have to "pull to unlock" and either the logo screen is still there or it's made it to "Welcome to Android".
I actually got to the Welcome screen this time. Picked the language, wifi network and started with my Google login before it rebooted.
Maybe an incompatible ROM issue? If so, I'm out of ideas as to what to try next.
I've downloaded what I believe to be the RUU for this model phone, but since I can't see the phone in Windows, I haven't even tried the RUU.

Goto_End said:
Sometimes I will get "com.htc.htcdialer is not responding", sometimes not.
...before it rebooted.
Click to expand...
Click to collapse
That's usually caused by the modem not initializing properly, and you could have some corrupt partitions due to using an m7_u/ul and it's time for ruu i guess.
Better head over to the HTC One Sprint forum: http://forum.xda-developers.com/sprint-htc-one should be plenty of help there.
Most of us here are on m7_u/ul so can offer only limited assistance... could be as simple flashing a radio for Sprint... but like I said, I'm not too familiar with Sprint unbrick.
Sorry & Good Luck

There's an awesome Rescue Tutorial over in the Sprint HTC One forum for people like me who flashed a GSM ROM on a CDMA phone. I can't post links yet, or I'd link to it just for posterity.
In essence, the GSM ROMs screw up the partition table. The fix was really easy. Most of the time was spend downloading the correct ROM and waiting for the adb push.

So confused - OTA Updates & Rooted/Modified M7 - please help!

Hi all,
My girlfriend has a HTC One M7, currentley Rooted with an Unlocked bootloader, Bulletproof Kernel, CWM Recovery, S-On (can't get S-OFF no matter what I try) and running the stock 4.4.2 Sense ROM that came with the phone.
She wants to install an OTA update, obviously this won't work with the phone in it's current state. I've got experience with all of this with my Note II, but the M7 is just a whole different can of worms.
What I've tried:
Getting S-OFF (no luck whatsoever with any tools)
Flashing stock recovery and kernel
Flashing stock recovery and kernel and applying the OTA manually via recovery
I've read everything on here and nothing seems to go in. She just wants to be able to install OTA updates, even if it means unrooting her phone permanently as this will happen each time there is an OTA update.
Someone, please guide me in the right direction! Step by step maybe?
Keep in mind there is no way I can't get S-OFF.
Huge thanks to anyone that can help. I'd be eternally in your debt!!

SmokinWaffle said:
My girlfriend has a HTC One M7, currentley Rooted with an Unlocked bootloader, Bulletproof Kernel, CWM Recovery, S-On (can't get S-OFF no matter what I try) and running the stock 4.4.2 Sense ROM that came with the phone.
She wants to install an OTA update, obviously this won't work with the phone in it's current state. I've got experience with all of this with my Note II, but the M7 is just a whole different can of worms.
Click to expand...
Click to collapse
I suppose the phone is trying to apply to ota update and then show a red triangle with an exclamation mark inside?
What I've tried:
Getting S-OFF (no luck whatsoever with any tools) Any error message when trying to S-OFF? You must use the correct tool for your hboot version (probably firewater) + combination of the correct rom + kernel
Flashing stock recovery and kernel --> You must have stock recovery for ota, ota will not install using a custom one.
Flashing stock recovery and kernel and applying the OTA manually via recovery --> appyling the ota manually from stock recovery require s-off
Click to expand...
Click to collapse
I've read everything on here and nothing seems to go in. She just wants to be able to install OTA updates, even if it means unrooting her phone permanently as this will happen each time there is an OTA update
Click to expand...
Click to collapse
.
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
http://forum.xda-developers.com/showpost.php?p=53151895&postcount=23
Keep in mind there is no way I can't get S-OFF.
Click to expand...
Click to collapse
still not sure about this, unless you get the "whelp" message from firewater...
post the output of fastboot getvar all except the imei number and serialno

alray said:
I suppose the phone is trying to apply to ota update and then show a red triangle with an exclamation mark inside?
Click to expand...
Click to collapse
Yep!
alray said:
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
http://forum.xda-developers.com/showpost.php?p=53151895&postcount=23
Click to expand...
Click to collapse
Interesting. I don't have the phone with me at the moment and it's late but I'll try to do the POWERUP + VOL tomorrow at some point, I'll get her to try stock recovery + kernel then do it and see what it's stopping at.
alray said:
still not sure about this, unless you get the "whelp" message from firewater...
Click to expand...
Click to collapse
Didn't get that message, just keeps going indefinetley or stops, and doesn't S-OFF. Tried Firewater, Revone, RumRunner, if there is another then I've almost certainly tried it, followed all the guides including the one that flashed Android Revolution...no idea..
alray said:
post the output of fastboot getvar all except the imei number and serialno
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [I]XXXXXXXXXXXX[/I]
(bootloader) imei: [I]XXXXXXXXXXXXXXX[/I]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Thanks for the prompt reply, really appreciate it and any help you can give.

SmokinWaffle said:
Yep!
Interesting. I don't have the phone with me at the moment and it's late but I'll try to do the POWERUP + VOL tomorrow at some point, I'll get her to try stock recovery + kernel then do it and see what it's stopping at.
Didn't get that message, just keeps going indefinetley or stops, and doesn't S-OFF. Tried Firewater, Revone, RumRunner, if there is another then I've almost certainly tried it, followed all the guides including the one that flashed Android Revolution...no idea..
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [I]XXXXXXXXXXXX[/I]
(bootloader) imei: [I]XXXXXXXXXXXXXXX[/I]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Thanks for the prompt reply, really appreciate it and any help you can give.
Click to expand...
Click to collapse
your version-main? (rom version) Go in settings --> About --> Software info --> Rom version
maybe there is a ruu you could use to restore the phone(4.19.401.9), if it match your version
---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------
you can also flash the stock 5.11.401.10 rom, recovery and firmware available on ARHD website
http://android-revolution-hd.blogspot.ca/p/android-revolution-hd-mirror-site-var.html
http://forum.xda-developers.com/showthread.php?t=2224752

alray said:
your version-main? (rom version) Go in settings --> About --> Software info --> Rom version
maybe there is a ruu you could use to restore the phone(4.19.401.9), if it match your version
---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------
you can also flash the stock 5.11.401.10 rom, recovery and firmware available on ARHD website
http://android-revolution-hd.blogspot.ca/p/android-revolution-hd-mirror-site-var.html
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
4.19.401.11
What exactly is the function of the RUU? I can't seems to get my head around it..
I'm guessing the ARHD steps are to try to get S-OFF?

SmokinWaffle said:
4.19.401.11
What exactly is the function of the RUU? I can't seems to get my head around it..
Click to expand...
Click to collapse
forget the ruu, your phone version is higher than the ruu. flashing a ruu (4.11.401.10) with a lower version than on your phone(4.11.401.11) require s-off.
I'm guessing the ARHD steps are to try to get S-OFF?
Click to expand...
Click to collapse
No, this is the latest stock rom(5.11.401.10) for your phone model (MID: PN0710000 and CID:HTC__001) including android 4.4.2 and sense 6.0
You can flash this stock odexed rom(5.11.401.10) from custom recovery, then flash the stock recovery(5.11.401.10) over the custom one and your phone will be stock and ready to take future ota update. You may also want to update firmware to 5.11.401.10

So after flashing that rom and stock recovery, ota would be ready to roll? Would the kernel matter?
What's the purpose / Difference of firmware and how is it updated? On my note II it was just choose a rom choose a kernel and off you go. This is so much more involved

SmokinWaffle said:
So after flashing that rom and stock recovery, ota would be ready to roll? Would the kernel matter?
Click to expand...
Click to collapse
stock kernel in included in the rom (boot.img) so if you don't flash any other kernel it should be fine.
What's the purpose / Difference of firmware and how is it updated? On my note II it was just choose a rom choose a kernel and off you go. This is so much more involved
Click to expand...
Click to collapse
firmware is all the low level code required for your phone hardware to works with the software (OS)
when speaking about HTC phone, firmware.zip include HBOOT(bootloader), BOOT(kernel), Recovery, Radio and some other stuff. if you want your phone to be 100% stock you need both stock rom + stock firmware to match the same version i.e 5.11.501.10
normally, the firmware is updated at the same time the rom version is updated (from an ota update) If you flash a rom, the rom will be updated but not the firmware.
Updating the firmware manually can be dangerous is you don't know what you are doing and flashing the wrong file. You can update firmware using this command from bootloader (with the correct firmware.zip package in the same folder you have adb and fastboot):
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
also it looks like flashing a 5.x.xxx.x firmware over a 3.x.xxx.x firmware will brick your phone. from what i see, your phone should be on a 4.x.401.x version at the moment, so it theory it should be fine.

Fails on:
>>>setting permissions
set_metadata_recursive: some changes failed
E:Error in /data/media/0/one_5.11.401.10_odexed.zip
(status 7)
Tried 3 different versions of cwm. Bad rom download?
Thinking about it I just re read your above post, could it be because the firmware isn't matched? I read your 'it should be fine' as 'dont update the firmware' not 'its fine to update' which I think is what you meant...
Firmware is 4.19.401.11 however the rom is 5.11.401.10. Can't believe I overlooked this, guess firmware needs to be 5.11.401.10 for the rom to take?

SmokinWaffle said:
Tried 3 different versions of cwm. Bad rom download?
Click to expand...
Click to collapse
No you are using CWM thats the problem. always use TWRP 2.6.3.3

alray said:
No you are using CWM thats the problem. always use TWRP 2.6.3.3
Click to expand...
Click to collapse
Huh?
Is this a requirement of ARHD or....?
Just seems odd
Edit: success!! All seems to work. Thank you. She's overjoyed!!!

Sprint HTC One stuck in Splash Screen

Hi,
I have a Sprint HTC One M7 running stock rom and S-Off(bought it new, thats what i thought then, it is S-off so refurbished maybe). I wanted to upgrade it to sense 6 rom. I did the following procedure:
1. Unlocked bootloader through HTCDev – Success,
2. Based on my readings, flashed recoveries (twrp, philz, cwm) through fastboot – The phone hangs at entering recovery. Hence unable to root.
3. Wasn’t able to get adb working with the rom on. Was always showing HTC one in device manager .Tried various drivers but didn’t work.
Despite this, was able to boot into rom and use as normal. So tried doing the same procedure yesterday. Viola, the Rom is not booting anymore. It stays stuck at the splash screen. I have not wiped anything other than cache so I am sure the rom is still there. I have tried the following steps,
1. Tried installing stock recovery to factory reset – Get a red triangle with ! mark above a phone symbol and stays there. Goes no further.
2. Tried several other recoveries(sprint ones) – When I check adb devices, it detects the phone and says it’s in recovery. Nothing on the phone.
3. Tried going back to stock by flashing RUU(after relocking bootloader) – Error 120 battery below 30% is the message I get. I am sure the battery is above 90% and I it is charging. While charging I noticed the LED at the top changed from Red to Green which I assume means battery is above 90%.
Right now the only thing I am able to access is fastboot. I think when I reboot, it is trying to boot into recovery by default even without me selecting recovery. It is showing recovery after every boot in adb but nothing on the phone. I don’t know where I went wrong in all this.
Can anybody suggest what I can do to bring my HTC back to life. Don’t need sense 6 after all these hassles, just want it working.
Getvar posted below.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.04.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4257mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-35824024
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s

OK. Looks like i did this "fastboot flash boot recovery.img". I know its a stupid mistake but need help recovering. Will i be able to boot into the rom if i flash kernel? If yes, can anybody link me to kernel for 3.04.651.2?
Still have the other problem of not being able to boot into recovery despite flashing it in the correct partition.

killmastern3 said:
OK. Looks like i did this "fastboot flash boot recovery.img". I know its a stupid mistake but need help recovering. Will i be able to boot into the rom if i flash kernel? If yes, can anybody link me to kernel for 3.04.651.2?
Still have the other problem of not being able to boot into recovery despite flashing it in the correct partition.
Click to expand...
Click to collapse
You are also in the wrong section. If you flashed anything from this section that's why you can't boot. You need to be in the sprint htc one section
Sent from my HTCONE using Tapatalk

thicklizard said:
You are also in the wrong section. If you flashed anything from this section that's why you can't boot. You need to be in the sprint htc one section
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Apologies. Will take the query to the correct section. I did flash sprint specific recovery though. Request mods to please close this thread.

killmastern3 said:
Apologies. Will take the query to the correct section. I did flash sprint specific recovery though. Request mods to please close this thread.
Click to expand...
Click to collapse
I just wanted to make sure you flashed sprint specific files. A ruu will get you fixed up there is a thread in the sprint section with a link to the ruu and a how to
Sent from my HTCONE using Tapatalk

thicklizard said:
I just wanted to make sure you flashed sprint specific files. A ruu will get you fixed up there is a thread in the sprint section with a link to the ruu and a how to
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Tried flashing RUU. Get error 120 - low battery. Can i just get the specific kernal and flash it through fastboot?

[Q] Just need stock recovery. No root. No ROM. S-ON

I am computer stupid. More so with phones. This is my brothers old phone. It has TWRP installed. Not rooted. No custom ROM.
All I want to do is get back the stock recovery so I can get this annoying "System update available" message to stop popping up all the time. The update is for software version 6.07.1540.1. Looks like it would upgrade to 4.4.3 as well.
m7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Apr 23 2014,00:42:43.0
That is what the bootloader has on it. It is the developer edition if that changes anything. I am using it currently on Straight Talk.
Android Version is 4.4.2
Sense Version is 6
Software number is 5.11.1540.9
I will provide any other details you may need. I am sorry if this has been covered before, which I am sure it has. I have read thread after thread and haven't learned anything.
Please explain like I am a mentally disabled 3 year old. If it is complicated I will hire you as a private tutor to walk me through it.
Thank you in advance for your help. I do apologize if this question is redundant. I just don't understand the other threads answers out there.

cptplatty said:
I am computer stupid. More so with phones. This is my brothers old phone. It has TWRP installed. Not rooted. No custom ROM.
All I want to do is get back the stock recovery so I can get this annoying "System update available" message to stop popping up all the time. The update is for software version 6.07.1540.1. Looks like it would upgrade to 4.4.3 as well.
m7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Apr 23 2014,00:42:43.0
That is what the bootloader has on it. It is the developer edition if that changes anything. I am using it currently on Straight Talk.
Android Version is 4.4.2
Sense Version is 6
Software number is 5.11.1540.9
I will provide any other details you may need. I am sorry if this has been covered before, which I am sure it has. I have read thread after thread and haven't learned anything.
Please explain like I am a mentally disabled 3 year old. If it is complicated I will hire you as a private tutor to walk me through it.
Thank you in advance for your help. I do apologize if this question is redundant. I just don't understand the other threads answers out there.
Click to expand...
Click to collapse
Ok let's start with some preliminary basics so I can understand exactly what I'm dealing with here
Do you know what adb is, and how to use it?
Do you know what fastboot is and how to use it?
What Operating system do you have on your pc? Windows 8 or 7, Linux, or if your using a Mac, Mac osx?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Ok let's start with some preliminary basics so I can understand exactly what I'm dealing with here
Do you know what adb is, and how to use it?
Do you know what fastboot is and how to use it?
What Operating system do you have on your pc? Windows 8 or 7, Linux, or if your using a Mac, Mac osx?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
no to adb. yes to fastboot. I can make the bootloader say "fastboot usb". I have the fastboot stuff on my windows 8 laptop.
I am using windows 8 on this laptop but have his windows 7 laptop that he used which should still have all the tools needed to put TWRP on there.

cptplatty said:
no to adb. yes to fastboot. I can make the bootloader say "fastboot usb". I have the fastboot stuff on my windows 8 laptop.
I am using windows 8 on this laptop but have his windows 7 laptop that he used which should still have all the tools needed to put TWRP on there.
Click to expand...
Click to collapse
Ok well it's better to use Windows 7, Windows 8 drivers can be problematic and may confuse things.
Do you know if your brother has used ota updates since unlocking the bootloader? The reason I ask is that unlocking the bootloader wipes some important pre-loaded apps from the device. And will cause the update to fail and soft-brick the phone.
Your brother may have known this so it's possible he restored the complete stock Rom previously but it's better to know before hand.
Can you connect fastbootusb then in the fastboot command line type
Code:
fastboot getvar all
Then post the output here. Please Edit out the imei and Serial no from the information before posting.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

I know he intended to put a custom ROM on but never did. All he did was install TWRP. There have been no OTA updates that came out since he did that. This one is the first. He did root through TWRP once but ran into a boot loop and restored through TWRP to before the Root and always has said no when TWRP ask if you want to root.
He is in the military and stayed with me while he was back for a while. I am also calling him in between post and asking him questions.
Here is what you asked for
C:\Users\Eric\Desktop\htc one\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s

cptplatty said:
I know he intended to put a custom ROM on but never did. All he did was install TWRP. There have been no OTA updates that came out since he did that. This one is the first. He did root through TWRP once but ran into a boot loop and restored through TWRP to before the Root and always has said no when TWRP ask if you want to root.
He is in the military and stayed with me while he was back for a while. I am also calling him in between post and asking him questions.
Here is what you asked for
C:\Users\Eric\Desktop\htc one\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Click to expand...
Click to collapse
Ok good thanks. So are you against using a custom Rom? It may be the easiest way to update the phone at this point and will solve the problem of the annoying update notification.
Or would you prefer to keep it stock?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Ok good thanks. So are you against using a custom Rom? It may be the easiest way to update the phone at this point and will solve the problem of the annoying update notification.
Or would you prefer to keep it stock?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
I would like to keep it stock because I plan on selling it on eBay soon. Maybe. Stock phones bring in more cash than custom ROM phones.
Though if it is too difficult to bring to stock, I will ROM it and just keep it. As I understand it, if it's a good ROM it can help keep it up to par with current phones a little longer than a stock ROM would.

How hard will it be to get the stock recovery. Your questions make it seem like it is going to be quite an undertaking.
If that is the case, then yes I will custom ROM it.
Though I would like to know what the process would be for the stock recovery. Just to see if it would be something I could do. It does not have to be a detailed explanation. Just something to get a better idea of.

cptplatty said:
How hard will it be to get the stock recovery. Your questions make it seem like it is going to be quite an undertaking.
If that is the case, then yes I will custom ROM it.
Though I would like to know what the process would be for the stock recovery. Just to see if it would be something I could do. It does not have to be a detailed explanation. Just something to get a better idea of.
Click to expand...
Click to collapse
cptplatty said:
I am computer stupid.
Please explain like I am a mentally disabled 3 year old.
Click to expand...
Click to collapse
That's why all the questions, I'm just trying to understand exactly what you expect the end result to be since the procedures are quite different depending on what you want to end up with.
To be honest getting a stock recovery is easy very easy. But restoring the stock pre-load data is not. You need a complete stock Rom including the pre-loaded apps or the OTA update will soft-brick your phone. Normally not difficult to recover from but in some cases has caused irreversible effects.
Returning to stock for sale or Warranty is whole different ball game. For that you first need to make the device s-off.
Currently it is s-on so you won't be able to set the bootloader back to ****LOCKED**** and you won't be able to remove the ****TAMPERED**** flag on the bootloader screen. There for the buyer or repair center would know that the phone was tampered with at some point.
You can use a reset zip to restore the stock software but the only one I can find for your device is older than your current firmware and again will cause problems when installing ota updates.
Once again because the phone is s-on you cannot downgrade the firmware only HTC signed firmware updates are possible with s-on.
This I'd why I suggested a custom Rom. You can simply flash a custom 4.4.3 Rom and that's that. The ota update notification will be gone and the phone will be running the latest software.
Custom roms generally are better in performance than Stock roms and yes you can normally get custom roms for newer software releases than were ment for the device. Although official support has not ended for the HTC One so there are still updates to come.
If you do want to return to stock to sell the phone your first priority is achieving s-off. Then take a look at this guide. http://forum.xda-developers.com/showthread.php?t=2541082.
The procedure for flashing a recovery weather it is stock or custom is the same and very simple. Download your chosen recovery. (which will be a .img file) put the .img file in your fastboot folder on your pc.
Now connect fastbootusb in the bootloader and in the command line type
Code:
fastboot flash recovery "nameofrecovery".img
fastboot erase cache
Obviously changeing "nameofrecovery".img for the actual name of the recovery file.
Or last and probably best option would be to achieve s-off. Then you can do pretty much whatever you want to it.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good: