Related
Decided to rewrite this as the problem is different now, not as bad, but a lot weirder! I can't get my head round whats up
Description of Problem
Right, so simplistically, the phone boots up, and you can use it (sort of) for about 30 seconds, before it reboots. Whilst its on, you can open apps, but there is definite issues with menu's not opening and you cant set a wallpaper, but its almost fully working. Then without any warning it just reboots, and does the same thing again.
I'm just confused at how it can boot up and almost fully work before rebooting. Failing to boot at all or bootlooping at the start animation, I can understand that, but not this.
Video of the Problem
What Caused the Issue
Its been a week or so since it first died, so I cant fully remember exact things that happened (I appreciate this will not be helpful!)
I had converted the phone to a google edition version using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2358781
Changed the MID and CID, flashed the bootloader, recovery and RUU and the whole thing worked great.
Then I got my Xperia Z, so wanted it back to stock to be sold. Problem is I locked the bootloader and went S-ON before flashing the stock bootloader because i'm an idiot! Then obviously it wouldn't boot due to locked bootloader and custom recovery, so I tried to flash stock RUU, failed naturally due to upgraded bootloader, so I unlocked the bootloader again, flashed stock, and now this happens
Things I've Tried
Factory Reset
Flashed Stock Roms (1.28 / 2.17 / 2.24 and google edition) via both flashable zip and CWM backups - flashing in fastboot doesnt work because of signature error
Revone to re S-OFF (On HBOOT 1.54 so get a -6 error)
Maybe some other things?
Does anyone have any ideas? Any help is appreciated at the moment, don't want to wait for S-OFF on 1.54 or a 2.24 RUU as that could mean a brick on my shelf for a while.
Can't you use revone to unlock? Or did you do s-on as well?
Edit: didn't mean to thank you there - this app is killing me..
Have you tried downgrading your firmware to give you the old 1.44 bootloader?
Sent from my HTC One using xda premium
redbull123 said:
Can't you use revone to unlock? Or did you do s-on as well?
Edit: didn't mean to thank you there - this app is killing me..
Have you tried downgrading your firmware to give you the old 1.44 bootloader?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
After hours of playing round I managed to get it to unlock the bootloader, so I should be fine, no idea what changed to make it work, but now it does. Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?
dh2311 said:
Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?
Click to expand...
Click to collapse
You can't downgrade when you're s-on.
iElvis said:
You can't downgrade when you're s-on.
Click to expand...
Click to collapse
Thats what I thought, hence why I got a bit concerned earlier. Phones not fixed yet, stuck in a bootloop but my internet is slow for downloading firmwares
If you're unlocked, you should be able to flash a new recovery, and from there a new rom. You've probably mucked up something with the OS, so hopefully a wipe and flash should do the trick.
dh2311 said:
After hours of playing round I managed to get it to unlock the bootloader, so I should be fine, no idea what changed to make it work, but now it does. Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?
Click to expand...
Click to collapse
You can't - I thought you were s-off since I didn't read in your post that you went back to s-on, that's what I was asking..
Sent from my HTC One using xda premium
iElvis said:
If you're unlocked, you should be able to flash a new recovery, and from there a new rom. You've probably mucked up something with the OS, so hopefully a wipe and flash should do the trick.
Click to expand...
Click to collapse
The partition tables are ******, dont know why, sd card partition is unreadable and an ADB sideload still causes bootloops, this phone is really messed up and i dont know what i did
Usually I can figure the problem out. No idea now. Going to try and get the SD card back and restore an RUU from a CWM backup, then RUU it and should be fixed!
Luckily I have my trusty Xperia Z to use whilst I sort this out!
dh2311 said:
The partition tables are ******, dont know why, sd card partition is unreadable and an ADB sideload still causes bootloops, this phone is really messed up and i dont know what i did
Usually I can figure the problem out. No idea now. Going to try and get the SD card back and restore an RUU from a CWM backup, then RUU it and should be fixed!
Luckily I have my trusty Xperia Z to use whilst I sort this out!
Click to expand...
Click to collapse
Did you try formatting your sdcard partition from your computer? That sounds like the issue. Likely you corrupted something with all those changes. Remember revone is a hack, so it;s not 100% reliable.
iElvis said:
Did you try formatting your sdcard partition from your computer? That sounds like the issue. Likely you corrupted something with all those changes. Remember revone is a hack, so it;s not 100% reliable.
Click to expand...
Click to collapse
Genius! Dont know how i didnt think of that. Now i have an accessible SD card, just still bootlooping, itll work with the 1.28 backup and then the RUU will correct everything I've messed up
Okay, this needs a bump since this problem is weird now. The phone boots, with a number of roms, but after about 15 seconds, crashes and reboots every single time, no matter what ROM.
I have wiped system, data, cache everything, and it still does this!
Any ideas? an RUU is out of the question since i am on 2.17 and there is no RUU
dh2311 said:
Okay, this needs a bump since this problem is weird now. The phone boots, with a number of roms, but after about 15 seconds, crashes and reboots every single time, no matter what ROM.
I have wiped system, data, cache everything, and it still does this!
Any ideas? an RUU is out of the question since i am on 2.17 and there is no RUU
Click to expand...
Click to collapse
Sounds like a kernel or firmware conflict. Try flashing 2.24 and see if that helps.
Edit: n/m, just saw you're s-on. I think the problem is that you've got an incompatible mix of firmwares from trying to convert to GE. You need to get s-off again somehow.
iElvis said:
Sounds like a kernel or firmware conflict. Try flashing 2.24 and see if that helps.
Click to expand...
Click to collapse
Thats what I thought, tried 1.28, 2.17 and 2.24 with still no success. It doesnt make sense to me.Trying flashing CM10 as i saw someone else suggest
EDIT: same problem! :'(
dh2311 said:
Thats what I thought, tried 1.28, 2.17 and 2.24 with still no success. It doesnt make sense to me.Trying flashing CM10 as i saw someone else suggest
Click to expand...
Click to collapse
Are you flashing firmware or just roms?
iElvis said:
Are you flashing firmware or just roms?
Click to expand...
Click to collapse
I cant flash RUU's becuase of my firmware version (2.17) flashed 1.28 via a CWM backup and the other 2 via ARHD stock odexed roms, best I think i can get becuase theres no 2.17 or 2.24 RUU that I know of
dh2311 said:
I cant flash RUU's becuase of my firmware version (2.17) flashed 1.28 via a CWM backup and the other 2 via ARHD stock odexed roms, best I think i can get becuase theres no 2.17 or 2.24 RUU that I know of
Click to expand...
Click to collapse
I don't mean RUUs, I mean one of the custom firmware packages that you flash in fastboot. But you need to be s-off to do that. You did something like this when you converted to GE.
This is one of the risks of going s-off, unfortunately. It lets you do stuff to your phone that can really screw it up.
iElvis said:
I don't mean RUUs, I mean one of the custom firmware packages that you flash in fastboot. But you need to be s-off to do that. You did something like this when you converted to GE.
This is one of the risks of going s-off, unfortunately. It lets you do stuff to your phone that can really screw it up.
Click to expand...
Click to collapse
Going back to S-ON was my mistake, if this phone was still S-OFF I'd have been able to fix it. But i still cant explain why it bootloops? All I did was change the MID and CID, which are now back to stock (HTC_001) and (PN07100) but it still has the Google edition bootloader, surely if that was the issue then it wouldnt boot past the bootloader, so where does the issue lie?
dh2311 said:
Going back to S-ON was my mistake, if this phone was still S-OFF I'd have been able to fix it. But i still cant explain why it bootloops? All I did was change the MID and CID, which are now back to stock (HTC_001) and (PN07100) but it still has the Google edition bootloader, surely if that was the issue then it wouldnt boot past the bootloader, so where does the issue lie?
Click to expand...
Click to collapse
It could be any number of things. You changed a lot going to GE, and with S-on, the phone is now doing all its usual security checks. Something somewhere got bollixed up. It could be the GE firmware is conflicting with your CID or MID.
One way or another, you've got to get back to s-off.
iElvis said:
It could be any number of things. You changed a lot going to GE, and with S-on, the phone is now doing all its usual security checks. Something somewhere got bollixed up. It could be the GE firmware is conflicting with your CID or MID.
One way or another, you've got to get back to s-off.
Click to expand...
Click to collapse
Thats the solution. Or a 2.24 RUU from HTC could also do it. But revone requires a booting phone, which mine cant do, doesnt work out of recovery unfortunately. and moonshine is only for older versions. Tempted to just put this phone on a shelf and wait for an RUU. Carry on using my Xperia Z
Dont know if this will be of any help for sorting the issue, but this is all the hboot info from getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <removed for safety>
(bootloader) imei: <removed for safety>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Definitely cant seem to get this to work, upon booting i get lots of force closes like the messaging app and contacts storage. That a clue for anyone?
Or if anyone knows how to S-Off without a working F/W that would be a help but I doubt it can be done
Hi,
Right... um where do i start.
Won a HTC one from work. I work for Orange/EE UK and HTC was faulty. Basically major chunks of corrupted code in the stock ROM.
So i rooted it pulled the whole thing apart (software speaking) fully cleaned out the phone and started from scratch with Android HD Revolution.
Noticed the other day 4.3 was now available so i flashed new rom but it was bugging my phone out so did a full wipe and went to re-install 4.2.2 and the thing got stuck in bootloop wouldnt even get past the boot loader.
So i formatted the whole thing and started from scratch but now my twrp wont respond. touchscreen will not work. Also flashed cmw to find that the internal sdcard will not mount and is not writing any info to it even when i adb push files to it there just not actually writing to the memory.
The last creepy thing. HBOOT has blank OS tried a getvar version-main command and its blank.
Am i right in thinking that this thing is basically broke beyond repair now or is there anything ive missed. BTW im on hboot 1.54 so no s-off and my CID is ORG001 so doesnt look like theres any RUU files either.
Help would be muchos appreciated.
Thanks
Kris
1.54 s-off
you are in luck,the " fone fun shop" have just managed to achieve s-off on 1.54 boot loader.give them a call and they will sort it for you.
doohdah said:
you are in luck,the " fone fun shop" have just managed to achieve s-off on 1.54 boot loader.give them a call and they will sort it for you.
Click to expand...
Click to collapse
Are they uk or us based? And is this the java card method?
The good thing about being s-on is that it's virtually impossible to brick your phone just flashing stuff.
It sounds like you may have corrupted your sdcard partition and more. Reformat using your PC, then reflash twrp, and try adb pushing the rom again. It should just be a matter of getting the storage partition properly restored and the right software onto the phone.
Please reply
klashnikoff said:
Hi,
Right... um where do i start.
Won a HTC one from work. I work for Orange/EE UK and HTC was faulty. Basically major chunks of corrupted code in the stock ROM.
So i rooted it pulled the whole thing apart (software speaking) fully cleaned out the phone and started from scratch with Android HD Revolution.
Noticed the other day 4.3 was now available so i flashed new rom but it was bugging my phone out so did a full wipe and went to re-install 4.2.2 and the thing got stuck in bootloop wouldnt even get past the boot loader.
So i formatted the whole thing and started from scratch but now my twrp wont respond. touchscreen will not work. Also flashed cmw to find that the internal sdcard will not mount and is not writing any info to it even when i adb push files to it there just not actually writing to the memory.
The last creepy thing. HBOOT has blank OS tried a getvar version-main command and its blank.
Am i right in thinking that this thing is basically broke beyond repair now or is there anything ive missed. BTW im on hboot 1.54 so no s-off and my CID is ORG001 so doesnt look like theres any RUU files either.
Help would be muchos appreciated.
Thanks
Kris
Click to expand...
Click to collapse
Hi Kris,
I had the same problem, my on phone setting show the firmware version correctly but my bootloader shows a blank for the OS field, can you please update me if you were able to solve this issue.?
Thanks a bunch mate!
thenesh55 said:
Hi Kris,
I had the same problem, my on phone setting show the firmware version correctly but my bootloader shows a blank for the OS field, can you please update me if you were able to solve this issue.?
Thanks a bunch mate!
Click to expand...
Click to collapse
As long as you have fastboot all is not lost!
Sent from my HTC One using Tapatalk
instigator008 said:
As long as you have fastboot all is not lost!
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yeah fast boot is working but when I m trying to use the rumrunner to s-off it stops after 8 pouring messages and nothing happens now am on ATT Dev version 3.22.1540.1 , but bootloader shows a Blank , and hboot is 1.54 , can you please suggest me , what can I do from here on, can I use revone, to s-off? or flash something else to make this thing work,
Thanks for your Time.
Can you get into recovery? If not flash twrp. You'll need an unlocked bootloader to flash a custom recovery.
Sent from my HTC One using Tapatalk
instigator008 said:
Can you get into recovery? If not flash twrp. You'll need an unlocked bootloader to flash a custom recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yes I can boot into recovery, I installed CWM. My bootloader is unlocked too..
all I am trying to do is get back to stock rom of a device with cid : htc__001 and get s-off from there to go back to my stock att.
I changed my sid to GOOGl001 to install GE and then changed the rom and cid,and S-oned it, Trying to get to some rom where I can get S-off from rumrunner.
Any help would be great,
Thanks for your time..
I appreciate your help
thenesh55 said:
Yes I can boot into recovery, I installed CWM. My bootloader is unlocked too..
all I am trying to do is get back to stock rom of a device with cid : htc__001 and get s-off from there to go back to my stock att.
I changed my sid to GOOGl001 to install GE and then changed the rom and cid,and S-oned it, Trying to get to some rom where I can get S-off from rumrunner.
Any help would be great,
Thanks for your time..
I appreciate your help
Click to expand...
Click to collapse
Flash a custom Rom with a stock kernel. I s-off'd with Android Revolution 30. Just make sure your firmware version (mainver) matches up with the rumrunner version you downloaded.
Sent from my HTC One using Tapatalk
instigator008 said:
Flash a custom Rom with a stock kernel. I s-off'd with Android Revolution 30. Just make sure your firmware version (mainver) matches up with the rumrunner version you downloaded.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, I flashed one with 2.24.400.1 os and now my phone get var shows this :
INFOversion: 0.5
INFOversion-bootloader: 1.54.0000
INFOversion-baseband: 4A.20.3263.16
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: HT35DW904679
INFOimei: 35xxxxxxxxxxx94
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 4149mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-94cf81a8fd
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.047s
can you please suggest me what Could do from here on??
Have you seen such issue in the past?
Thanks a lot for your reply
Strange. Have you tried flashing a ruu?
Sent from my HTC One using Tapatalk
---------- Post added at 09:58 PM ---------- Previous post was at 09:54 PM ----------
You could try this tool to write your mainver: http://forum.xda-developers.com/showthread.php?t=2344671
Sent from my HTC One using Tapatalk
instigator008 said:
Strange. Have you tried flashing a ruu?
Sent from my HTC One using Tapatalk
---------- Post added at 09:58 PM ---------- Previous post was at 09:54 PM ----------
You could try this tool to write your mainver: http://forum.xda-developers.com/showthread.php?t=2344671
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply, Its really helpful, I was able to rewrite the osvar, but now am running into a strage issue, i wrote 2.24.400.1 and its letting me install 2.24.400.8 , when i tried to upgrade from 2.24.400.1 it shows a error mesage saying the device is corrupted something like that and tells me to contact htc.but dont't update anything on the phone. after this I tried rumrunner and it didn't work either
any suggestion that could help me at this point??
could it be like i corrupted my some part of boot loader??
Thanks for your time , I really appreciate it.
thenesh55 said:
Thanks for your reply, Its really helpful, I was able to rewrite the osvar, but now am running into a strage issue, i wrote 2.24.400.1 and its letting me install 2.24.400.8 , when i tried to upgrade from 2.24.400.1 it shows a error mesage saying the device is corrupted something like that and tells me to contact htc.but dont't update anything on the phone. after this I tried rumrunner and it didn't work either
any suggestion that could help me at this point??
could it be like i corrupted my some part of boot loader??
Thanks for your time , I really appreciate it.
Click to expand...
Click to collapse
Pretty sure that technique of "downgrading" firmware version is only meant to enable the use of RUU to restore to stock. Use the program to write back your the version your firmware actually matches, then try reflashing.
I know Orange does not have an RUU but you might want to try using this nandroid backup
instigator008 said:
Flash a custom Rom with a stock kernel. I s-off'd with Android Revolution 30. Just make sure your firmware version (mainver) matches up with the rumrunner version you downloaded.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
thenesh55 said:
Hi Kris,
I had the same problem, my on phone setting show the firmware version correctly but my bootloader shows a blank for the OS field, can you please update me if you were able to solve this issue.?
Thanks a bunch mate!
Click to expand...
Click to collapse
Hey boss sorry for late reply never really got a notifcation email from this.
Nope im no further forward.
Still got no firmware or OS installed on the phone. Well according to the HBOOT anyways yet im running insertcoin 6.01.
Hey Investigator how do i know what firmware i need to install?? My phone getvar mainver is blank. I can flash a million roms it still brings back nothing. :/ strange i know..
Thanks
Kris
Here This might help
klashnikoff said:
Hey boss sorry for late reply never really got a notifcation email from this.
Nope im no further forward.
Still got no firmware or OS installed on the phone. Well according to the HBOOT anyways yet im running insertcoin 6.01.
Hey Investigator how do i know what firmware i need to install?? My phone getvar mainver is blank. I can flash a million roms it still brings back nothing. :/ strange i know..
Thanks
Kris
Click to expand...
Click to collapse
Hi Kris,
Checkthis out..
Before Entering the value,
Find your Phones model no, based on that change ur OS version
http://forum.xda-developers.com/showthread.php?t=2344671.
I did this but when ever I change my OS, its not being updated, The only solution I can think of is to somehow get My S-off, I am looking for some one who can do it with a java card or by some other means.
Please let me know guys if Any one knows how to s-off with on a ATT GSM phone with a java card or by other means.
I was s-off before and screwed it up.
Thanks for any replies.
thenesh55 said:
Hi Kris,
Checkthis out..
Before Entering the value,
Find your Phones model no, based on that change ur OS version
http://forum.xda-developers.com/showthread.php?t=2344671.
I did this but when ever I change my OS, its not being updated, The only solution I can think of is to somehow get My S-off, I am looking for some one who can do it with a java card or by some other means.
Please let me know guys if Any one knows how to s-off with on a ATT GSM phone with a java card or by other means.
I was s-off before and screwed it up.
Thanks for any replies.
Click to expand...
Click to collapse
Hey boss,
Well misctool only writes a variable that RUU's read from to verify your not downgrading it doesnt actually write firmware.
Plus flashing a rom will not flash firmware either.
I dont know whether your having the same problem as me but my issues came from a dirty flash which softbricked my phone. Because of this i formatted the SDcard erasimg a partition the the OSver is wrote to.
The firmware is still there just no visible because of the erase. Im currently in the process of downloading every single rumrunner firmware and flashing them till i get one to work.
Kris
ANy fix yet?
I'm having the exact same problem. Bootloader shows OS- 'Blank space'
Tried different sprint Ruu's but always gets Error 155 because of No os i guess.
Amitfuriousgamer said:
I'm having the exact same problem. Bootloader shows OS- 'Blank space'
Tried different sprint Ruu's but always gets Error 155 because of No os i guess.
Click to expand...
Click to collapse
it has nothing to do with the no - OS ... you just need to flash the firmware then the RUU
And your s-off no need to relock the bootloader like that
Amitfuriousgamer said:
I'm having the exact same problem. Bootloader shows OS- 'Blank space'
Tried different sprint Ruu's but always gets Error 155 because of No os i guess.
Click to expand...
Click to collapse
Error 155 means image error, your using the wrong RUU, as your s-off, you can flash any Sprint RUU you just need firmware first.
Missing OS number in the bootloader is a common problem due to flashing a custom recovery, its not a problem and doesn't effect the phone in anyway.
I have a HTC One on the EE network in the UK and I am still currently on Android 4.3 and Sense 5.5, they haven't bothered to release Android 4.4 yet and I have no hope that they will release Sense 6.
So, I would like to know how to go about changing my EE branded phone into an Unlocked International Version so that I can receive OTA updates direct from HTC.
Current CID: ORANG001
Current Hboot: 1.55
Current Software Number: 3.63.61.1
Radio: 4A.21.3263.04
Locked Bootloader with S-On
I would very much appreciate any help you can give.
Thank-You
rh92 said:
I have a HTC One on the EE network in the UK and I am still currently on Android 4.3 and Sense 5.5, they haven't bothered to release Android 4.4 yet and I have no hope that they will release Sense 6.
So, I would like to know how to go about changing my EE branded phone into an Unlocked International Version so that I can receive OTA updates direct from HTC.
Current CID: ORANG001
Current Hboot: 1.55
Current Software Number: 3.63.61.1
Radio: 4A.21.3263.04
Locked Bootloader with S-On
I would very much appreciate any help you can give.
Thank-You
Click to expand...
Click to collapse
first of all you need to unlock your bootloader and s-off your phone, debrand is not possible with s=on
the you would need to change your cid to something like HTC__001 or developer edition cid, one fastboot command required to do this.
and then run the correct RUU for those cid's and your done.
its quite easy to do, the hardest part is getting s-off, however you may be ok on 1.55 hboot, try rumrunner, read the instructions and download the required file here: http://rumrunner.us/
Seanie280672 said:
first of all you need to unlock your bootloader and s-off your phone, debrand is not possible with s=on
the you would need to change your cid to something like HTC__001 or developer edition cid, one fastboot command required to do this.
and then run the correct RUU for those cid's and your done.
its quite easy to do, the hardest part is getting s-off, however you may be ok on 1.55 hboot, try rumrunner, read the instructions and download the required file here: http://rumrunner.us/
Click to expand...
Click to collapse
Do I need custom recovery? If so which is best.
And do I need to have a custom ROM installed to gain s-off or can s-off be achieved on my current EE branded ROM?
Thanks
rh92 said:
Do I need custom recovery? If so which is best.
And do I need to have a custom ROM installed to gain s-off or can s-off be achieved on my current EE branded ROM?
Thanks
Click to expand...
Click to collapse
nope its not required for either, you should be able to s-off on stock rom, if you get an error or for some reason it fails, then you MAY have to flash a custom recovery and custom rom / kernel.
The RUU's will put you back to fully stock anyway in the end.
Seanie280672 said:
nope its not required for either, you should be able to s-off on stock rom, if you get an error or for some reason it fails, then you MAY have to flash a custom recovery and custom rom / kernel.
The RUU's will put you back to fully stock anyway in the end.
Click to expand...
Click to collapse
If the s-off does cause an error or it fails, can this cause my device to get bricked?
And by fully stock do you mean that the RUU turns s-on and locks my boot loader? (just in case I need to send my phone in for repair).
Thanks
rh92 said:
If the s-off does cause an error or it fails, can this cause my device to get bricked?
And by fully stock do you mean that the RUU turns s-on and locks my boot loader? (just in case I need to send my phone in for repair).
Thanks
Click to expand...
Click to collapse
no your phone wont brick
and no the ruu wont turn your phone s-on, you will need to lock your bootloader before running the RUU, but that's one simple command too, but only after s-off.
all you need right now is to make sure you have the drivers installed and that your device is detected in windows both when booted into a rom and on the bootloader screen.
Seanie280672 said:
no your phone wont brick
and no the ruu wont turn your phone s-on, you will need to lock your bootloader before running the RUU, but that's one simple command too, but only after s-off.
all you need right now is to make sure you have the drivers installed and that your device is detected in windows both when booted into a rom and on the bootloader screen.
Click to expand...
Click to collapse
After installing the RUU how would I get s-on?
Thanks
rh92 said:
After installing the RUU how would I get s-on?
Thanks
Click to expand...
Click to collapse
don't s-on, never s-on simple as that.
Seanie280672 said:
don't s-on, never s-on simple as that.
Click to expand...
Click to collapse
Ok, I was just asking in case I needed to send my phone in for repair in the future.
rh92 said:
Ok, I was just asking in case I needed to send my phone in for repair in the future.
Click to expand...
Click to collapse
not really something they will check to be honest, but if you s-on and you've played about with your phone down the line, like flashed a modified firmware or hboot, you will get an instant brick, if your hboot version is too high you will get the tampered flag back, or if you make a mistake along the way and the fix requires s-off, it will be very difficult to get again.
Seanie280672 said:
not really something they will check to be honest, but if you s-on and you've played about with your phone down the line, like flashed a modified firmware or hboot, you will get an instant brick, if your hboot version is too high you will get the tampered flag back, or if you make a mistake along the way and the fix requires s-off, it will be very difficult to get again.
Click to expand...
Click to collapse
So, is the following step by step list correct.
1. Unlock boot loader
2. Get s-off via rumrunner
3. Change CID
4. Lock boot loader
5. Run RUU
And, I am currently on 4.3 and Sense 5.5, so can I go straight to the sense 6 and Android 4.4 RUU, or do I have to install the sense 5.5 and Android 4.4 RUU first.
Thanks
rh92 said:
So, is the following step by step list correct.
1. Unlock boot loader
2. Get s-off via rumrunner
3. Change CID
4. Lock boot loader
5. Run RUU
And, I am currently on 4.3 and Sense 5.5, so can I go straight to the sense 6 and Android 4.4 RUU, or do I have to install the sense 5.5 and Android 4.4 RUU first.
Thanks
Click to expand...
Click to collapse
yup that's the correct order, and you will have to use this RUU as its the only full RUU available, everything else is just OTA's
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Seanie280672 said:
yup that's the correct order, and you will have to use this RUU as its the only full RUU available, everything else is just OTA's
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Click to expand...
Click to collapse
And after installing this RUU I can just download Sense 6 via OTA.
rh92 said:
And after installing this RUU I can just download Sense 6 via OTA.
Click to expand...
Click to collapse
yes, just accept the ota's one at a time.
Seanie280672 said:
yes, just accept the ota's one at a time.
Click to expand...
Click to collapse
Thanks for your help
I have an PN07200, how can I get sense 6, which will be the best RUU and CID?.... Thanks!
Enviado desde mi HTC One X+ mediante Tapatalk
is it possible to re-apply the branding?
i.e.
RUU
change cid
OTA with brand change
gwaitsi said:
is it possible to re-apply the branding?
i.e.
RUU
change cid
OTA with brand change
Click to expand...
Click to collapse
yup, change your cid to its original one, and find your service providers RUU and flash it.
Hi all,
I'm considering downgrading my HBOOT from 1.55 to 1.44 in order to restore the 'fastboot boot' command (a bug that HTC admit to). What concerns me is whether a particular HBOOT version is compatible only with a certain range of firmware releases and so whether I risk bricking or bootlooping from a downgrade.
Another, related question. Is it safe to use, for example, an international HBOOT (*.*.401.*, likely from PN0710000) on my Rogers phone (*.*.631.*, PN0712000)?
Anyone know whether these kinds of dependency exist, or whether HBOOT and the contents of other partitions are completely independent of one another and no crosschecking is performed? It seems to me that HBOOT 1.44 is the real sweet spot given the simplicity of revone and the ability to boot from an image that's not on the device itself.
Full disclosure: I'm running an M7_UL on Rogers (PN0712000 and CID ROGER001), S-OFF, bootloader unlocked, no root with currently stock 3.22.631.1 firmware and ROM.
Thanks folks,
Ian
dr_diem said:
Hi all,
I'm considering downgrading my HBOOT from 1.55 to 1.44 in order to restore the 'fastboot boot' command (a bug that HTC admit to).
Click to expand...
Click to collapse
fastboot boot recovery.img was intentionally removed in higher hboot, not a bug.
What concerns me is whether a particular HBOOT version is compatible only with a certain range of firmware releases and so whether I risk bricking or bootlooping from a downgrade.
Click to expand...
Click to collapse
Not 100% sure but I have downgraded to 1.44 many time and it did not caused any issue.
Another, related question. Is it safe to use, for example, an international HBOOT (*.*.401.*, likely from PN0710000) on my Rogers phone (*.*.631.*, PN0712000)?
Click to expand...
Click to collapse
I used .401 1.44 hboot on a pn071200 dev edition .1540 and it did not caused any issue.
I don't really understand why you want to flash 1.44 back when you have s-off...? downgrade to 1.44 only if and when its needed.
Many thanks for the rapid and informative response alray!
alray said:
fastboot boot recovery.img was intentionally removed in higher hboot, not a bug.
Click to expand...
Click to collapse
Really?! All the more annoying
alray said:
Not 100% sure but a downgraded to 1.44 many time and it did not cause any issue.
Click to expand...
Click to collapse
That's really promising - thanks!
alray said:
I used .401 1.44 hboot on a pn071200 dev edition .1540 and it did not caused any issue.
Click to expand...
Click to collapse
That's the mustard right there! I don't know if anyone knows the definitive answer on all this, but my gut tells me that (for GSM single-SIM handsets at least) the further down the software->firmware chain you go the more generic the code becomes. Your findings seem to support that theory.
alray said:
I don't really understand why you want to flash 1.44 back when you have s-off...? downgrade to 1.44 only if and when its needed.
Click to expand...
Click to collapse
Yeah, it's because I would like to back up my stock recovery before rooting, so I want to boot a custom recovery via fastboot and use it to take a nandroid of the stock recovery. Again I don't know if stock recoveries are tied to a particular firmware or ROM release (any idea on that one?), but I'm trying to play safe!
In general I find there aren't too many Rogers images out there (HBOOT, firmware, OTA, RUU...) which makes the rooting dance that bit more tricky for us. I tried to grab the OTA file when I recently went stock to go 1.29.631.17 -> 3.22.631.1 but of course one needs to root in order to access /temp to go get the file and I didn't want to root before I took a vanilla backup - catch 22! I don't suppose you have a 3.22.631.1 stock recovery lying around do you? It'd save me a whole load of trouble
Cheers,
Ian
dr_diem said:
Yeah, it's because I would like to back up my stock recovery before rooting
Click to expand...
Click to collapse
stock recovery can be extracted from the ota package in the firmware.zip file.
so I want to boot a custom recovery via fastboot and use it to take a nandroid of the stock recovery.
Click to expand...
Click to collapse
You can't make a nandroid backup of the recovery image but you can pull it using "dd" commands
Again I don't know if stock recoveries are tied to a particular firmware or ROM release
Click to expand...
Click to collapse
yes, use the recovery that match the version of your phone firmware/software.
I don't suppose you have a 3.22.631.1 stock recovery lying around do you? It'd save me
Click to expand...
Click to collapse
no sorry
There is a recovery collection here: http://forum.xda-developers.com/showthread.php?t=2545227
but there is no 3.22.631.1 which is an old version btw...
---------- Post added at 03:45 PM ---------- Previous post was at 03:39 PM ----------
dr_diem said:
.
Click to expand...
Click to collapse
you might want to take a look at what I have done: http://forum.xda-developers.com/showpost.php?p=54167697&postcount=1095
look under "for reference, here is how the recovery was pulled:"
alray said:
stock recovery can be extracted from the ota package in the firmware.zip file.
Click to expand...
Click to collapse
Yeah it is unfortunate that I failed to obtain that
alray said:
You can't make a nandroid backup of the recovery image but you can pull it using "dd" commands
Click to expand...
Click to collapse
Oh? Bummer In order to dd from the hboot partition I thought I'd need to be rooted though? And wouldn't I need a custom recovery in order to root? Or am I wrong and I can dd from fastboot or adb without root? If I can then this'd be an ideal solution and I wouldn't need the HBOOT downgrade after all
Huge thanks for the edit and pointer to how to dd without root!
alray said:
yes, use the recovery that match the version of your phone firmware/software.
Click to expand...
Click to collapse
Understood, thanks.
alray said:
There is a recovery collection here: http://forum.xda-developers.com/showthread.php?t=2545227
Click to expand...
Click to collapse
Yes I've combed my way through every repository I can find, but like I say ROGER_001 is a poorly-served CID I guess if I was really pushed I could go SuperCID and use the TELUS one I see there!
alray said:
but there is no 3.22.631.1 which is an old version btw...
Click to expand...
Click to collapse
Yeah the reason I'm so keen to have a complete path to downgrade to stock 4.3 is because I'm not convinced I ever want to go beyond 4.3. 4.4 makes Google Search become the shell, which is a line I'm not sure I want to cross :laugh:
Ian
dr_diem said:
Oh? Bummer In order to dd from the hboot partition I thought I'd need to be rooted though? And wouldn't I need a custom recovery in order to root? Or am I wrong and I can dd from fastboot or adb without root? If I can then this'd be an ideal solution and I wouldn't need the HBOOT downgrade after all
Click to expand...
Click to collapse
Yes you'll need either root or to downgrade hboot to 1.44, boot a custom recovery (fastboot boot), use dd from the custom recovery shell to pull the stock recovery from mmcblk0p34 partition. look in my previous (edited) post. I have posted a link explaining how to do it.
That's stormin' alray! Now I finally have a viable route forwards.
Big thanks,
Ian
dr_diem said:
That's stormin' alray! Now I finally have a viable route forwards.
Big thanks,
Ian
Click to expand...
Click to collapse
just make sure to type the dd commands correctly, it could brick your phone if you make a mistake using dd commands...
alray said:
just make sure to type the dd commands correctly, it could brick your phone if you make a mistake using dd commands...
Click to expand...
Click to collapse
Hah, yeah, touch wood I've never yet bricked any device using dd, but I'm clear how powerful/dangerous it is as commands go
Okay so I just want to finish up this thread for those who might use it as reference later.
I followed alray's excellent advice and downgraded HBOOT to 1.44 (using a 1.29.401.12 file from here) - I've been running if for a few days now and all seems fine. The phone was slower to shut down for the first few reboots - it would hang on the 'HTC logo' page for around 10 seconds or so - but now even that has gone away and it behaves fine in every way. So then, complete success running HBOOT 1.44 sourced from a 1.29.401.12 RUU on a handset running 3.22.631.1 firmware and stock ROM, that originally came with HBOOT 1.55.
FWIW I also successfully copied out the stock recovery by fastboot booting a custom recovery and using dd.
Ian
dr_diem said:
Okay so I just want to finish up this thread for those who might use it as reference later.
I followed alray's excellent advice and downgraded HBOOT to 1.44 (using a 1.29.401.12 file from here) - I've been running if for a few days now and all seems fine. The phone was slower to shut down for the first few reboots - it would hang on the 'HTC logo' page for around 10 seconds or so - but now even that has gone away and it behaves fine in every way. So then, complete success running HBOOT 1.44 sourced from a 1.29.401.12 RUU on a handset running 3.22.631.1 firmware and stock ROM, that originally came with HBOOT 1.55.
FWIW I also successfully copied out the stock recovery by fastboot booting a custom recovery and using dd.
Ian
Click to expand...
Click to collapse
glad to know it worked fine! happy flashing
Hello Everyone,
I have read multiple guides from here and want to emphasize what a great community this place seems to be!
I am a proud owner of an HTC One M7 with Miui installed.
I have CWM Recovery installed and am S-ON.
I have the tint problem of the camera and intend to bring it to the seller for a repair. This requires me to go back to the stock HTC Sense ROM.
Below is the output of the fastboot getvar all command:
c:\fastboot>fastboot.exe getvar all
(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: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4317mV
(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.052s
Click to expand...
Click to collapse
I don't know how to choose the correct RUU. The only thing which comes close to what I have in terms of software version is this:
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
Should I use it?
Also, most of the guides start with the assumption that your phone is S-OFF (not really sure what that means exactly, but that's a different conversation).
Does that mean I can skip the steps for getting it back to S-ON from those guides and continue onward or I should get it first to S-OFF, do whatever needs to be done and then get it back to S-ON and continue with the RUU?
Thanks a lot, guys!
Best,
Wisher
WisherBG said:
Hello Everyone,
I have read multiple guides from here and want to emphasize what a great community this place seems to be!
I am a proud owner of an HTC One M7 with Miui installed.
I have CWM Recovery installed and am S-ON.
I have the tint problem of the camera and intend to bring it to the seller for a repair. This requires me to go back to the stock HTC Sense ROM.
Below is the output of the fastboot getvar all command:
I don't know how to choose the correct RUU. The only thing which comes close to what I have in terms of software version is this:
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
Should I use it?
Also, most of the guides start with the assumption that your phone is S-OFF (not really sure what that means exactly, but that's a different conversation).
Does that mean I can skip the steps for getting it back to S-ON from those guides and continue onward or I should get it first to S-OFF, do whatever needs to be done and then get it back to S-ON and continue with the RUU?
Thanks a lot, guys!
Best,
Wisher
Click to expand...
Click to collapse
That RUU will work for you, but it won't do any good for reinstating your warranty. You need to be s-off to return to 100% stock.
As you will need to set the bootloader back to ***LOCKED*** which requires s-off. With s-on the best you will get is ***RELOCKED*** and that's a sure sign the device was tampered with.
WisherBG said:
Hello Everyone,
I am a proud owner of an HTC One M7 with Miui installed.
I have CWM Recovery installed and am S-ON.
I don't know how to choose the correct RUU. The only thing which comes close to what I have in terms of software version is this:
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
Should I use it?
Thanks a lot, guys!
Best,
Wisher
Click to expand...
Click to collapse
Danny201281 said:
That RUU will work for you, but it won't do any good for reinstating your warranty. You need to be s-off to return to 100% stock.
Click to expand...
Click to collapse
this ruu won't work for you it's version is low you need same or higher version
Stock Reset Rom can help you but not 100%
S Off is only option
yatindroid said:
this ruu won't work for you it's version is low you need same or higher version
Stock Reset Rom can help you but not 100%
S Off is only option
Click to expand...
Click to collapse
Good catch I didn't spot he was on .11 not .9 :good:
Thanks for your replies.
So how do I go about getting a newer RUU?
I am currently trying to get S-OFF with rumrunner... hopefully it will work.
If I get it to be S-OFF, what should I do from that point on?
The unbranded EU Lollipop RUU (in ZIP form) is here:
http://forum.xda-developers.com/htc-one/general/htc-one-m7-european-signed-ruu-t3048384
EddyOS said:
The unbranded EU Lollipop RUU (in ZIP form) is here:
http://forum.xda-developers.com/htc-one/general/htc-one-m7-european-signed-ruu-t3048384
Click to expand...
Click to collapse
If you use that ruu you won't be able to get s-off, there is no working method to s-off hboot 1.60. You'd be better off finding a stock Rom to flash and get s-off with rumrunner. Once you update past hboot 1.57 you will have to pay $25 for sunshine to s-off and as I mentioned if you go to hboot 1.60 you will ha e to wait for a new exploit that will work with that version. No doubt that will also be an updated version of Sunshine
What's wrong with paying for S-OFF? Gotta show the Devs some love
So the current option is to find a stock 401.11 ROM?
Any ideas where to look for one?
I have found the original/stock OTA zip file for the 401.11 update from an article by Android Revolution HD.
Also the 401.11 stock firmware zip from the android revolution collection.
(sorry, I'm too new of a user and can't post the actual links but they can be found by googling "4.19.401.11 ruu" and seeing the android revolution blogspot article)
Am I correct in thinking that I should do the following:
1. Flash with this firmware (since it is the stock one).
2. Install the OTA zip with fastboot (I think there is a tutorial on how to do this). Will this work the same as installing a RUU?
3. Run rumrunner while still on hboot 1.56
4. Go to S-OFF
5. Return everything to stock
6. Apply latest OTA (lolipop etc.)
7. Pay the price if I want to have S-OFF later.
Best,
Wisher
WisherBG said:
So the current option is to find a stock 401.11 ROM?
Any ideas where to look for one?
I have found the original/stock OTA zip file for the 401.11 update from an article by Android Revolution HD.
Also the 401.11 stock firmware zip from the android revolution collection.
(sorry, I'm too new of a user and can't post the actual links but they can be found by googling "4.19.401.11 ruu" and seeing the android revolution blogspot article)
Am I correct in thinking that I should do the following:
1. Flash with this firmware (since it is the stock one).
2. Install the OTA zip with fastboot (I think there is a tutorial on how to do this). Will this work the same as installing a RUU?
3. Run rumrunner while still on hboot 1.56
4. Go to S-OFF
5. Return everything to stock
6. Apply latest OTA (lolipop etc.)
7. Pay the price if I want to have S-OFF later.
Best,
Wisher
Click to expand...
Click to collapse
No RUU, flash this inside TWRP recovery just like you would with a custom rom, only this will make your phone stock.
https://www.androidfilehost.com/?fid=23501681358545524
you cant manually flash OTA's whilst s-on, also you shouldnt need to flash firmware that you are already on.
Seanie280672 said:
No RUU, flash this inside TWRP recovery just like you would with a custom rom, only this will make your phone stock.
YOUR LINK (removed due to too new a user)
you cant manually flash OTA's whilst s-on, also you shouldnt need to flash firmware that you are already on.
Click to expand...
Click to collapse
Ok, I will be flashing with this guru reset file.
Then I should go S-OFF and follow the guide to get everything back to stock (no **UNLOCKED**, no TAMPERED, etc.).
Correct?
WisherBG said:
Ok, I will be flashing with this guru reset file.
Then I should go S-OFF and follow the guide to get everything back to stock (no **UNLOCKED**, no TAMPERED, etc.).
Correct?
Click to expand...
Click to collapse
get s-off as long as you can, do not accept any updates.
after s-off you will need to flash HBOOT 1.44 and a very early RUU, then get rid of the flags and s-on before updating.
removing the flags and then going s-on with anything higher than HBOOT 1.54 and the flags come back on the next reboot.
Seanie280672 said:
get s-off as long as you can, do not accept any updates.
after s-off you will need to flash HBOOT 1.44 and a very early RUU, then get rid of the flags and s-on before updating.
removing the flags and then going s-on with anything higher than HBOOT 1.54 and the flags come back on the next reboot.
Click to expand...
Click to collapse
Ok, thanks! I will see what I can do with the help of the guides in this forum.
Any helpful links will be highly appreciated.
Best,
Wisher
WisherBG said:
Ok, thanks! I will see what I can do with the help of the guides in this forum.
Any helpful links will be highly appreciated.
Best,
Wisher
Click to expand...
Click to collapse
just report back here once your s-off and all the guys will be more than happy to help you :good:
Seanie280672 said:
after s-off you will need to flash HBOOT 1.44 and a very early RUU, then get rid of the flags and s-on before updating.
removing the flags and then going s-on with anything higher than HBOOT 1.54 and the flags come back on the next reboot.
Click to expand...
Click to collapse
Important Thanks
Got the following with rumrunner:
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
Click to expand...
Click to collapse
However I can do "adb shell" and then "su" brings me to be a super user.
What is different to what the situation was when I was with MIUI is that now when I type "adb shell" I am not automatically root (don't have # but $ at the console). When I do "su", the $ changes to #, which basically means that I am root.
I guess rumrunner has a requirement that you are root by default when logging via adb shell.
Any idea on a fix?
Best,
Wisher
EddyOS said:
What's wrong with paying for S-OFF? Gotta show the Devs some love
Click to expand...
Click to collapse
There's nothing wrong with paying for s-off. I have purchased Sunshine myself when necessary, and made regular donations to other devs. but it's only fair to inform people of there options before you land them with a $25 solution not everyone has money to spare for that sort of thing. :good:
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
WisherBG said:
So the current option is to find a stock 401.11 ROM?
Any ideas where to look for one?
I have found the original/stock OTA zip file for the 401.11 update from an article by Android Revolution HD.
Also the 401.11 stock firmware zip from the android revolution collection.
(sorry, I'm too new of a user and can't post the actual links but they can be found by googling "4.19.401.11 ruu" and seeing the android revolution blogspot article)
Am I correct in thinking that I should do the following:
1. Flash with this firmware (since it is the stock one).
2. Install the OTA zip with fastboot (I think there is a tutorial on how to do this). Will this work the same as installing a RUU?
3. Run rumrunner while still on hboot 1.56
4. Go to S-OFF
5. Return everything to stock
6. Apply latest OTA (lolipop etc.)
7. Pay the price if I want to have S-OFF later.
Best,
Wisher
Click to expand...
Click to collapse
You should try rumrunner with the Rom @Seanie280672 posted to gain s-off. Not guaranteed to work as HTC started patching firmware at this point but if you need 100% stock it's your best chance to s-off without Sunshine.
If rumrunner won't work Sunshine is still cheaper than paying for the repair, and when you get your device back you can use Sunshine again for free, as long as it is the same device and not a replacement :good:
Seanie280672 said:
No RUU, flash this inside TWRP recovery just like you would with a custom rom, only this will make your phone stock.
https://www.androidfilehost.com/?fid=23501681358545524
you cant manually flash OTA's whilst s-on, also you shouldnt need to flash firmware that you are already on.
Click to expand...
Click to collapse
---------- Post added at 09:34 PM ---------- Previous post was at 09:31 PM ----------
WisherBG said:
Got the following with rumrunner:
However I can do "adb shell" and then "su" brings me to be a super user.
What is different to what the situation was when I was with MIUI is that now when I type "adb shell" I am not automatically root (don't have # but $ at the console). When I do "su", the $ changes to #, which basically means that I am root.
I guess rumrunner has a requirement that you are root by default when logging via adb shell.
Any idea on a fix?
Best,
Wisher
Click to expand...
Click to collapse
Did you select the option to install root when you flashed the rom?
Danny201281 said:
There's nothing wrong with paying for s-off. I have purchased Sunshine myself when necessary, and made regular donations to other devs. but it's only fair to inform people of there options before you land them with a $25 solution not everyone has money to spare for that sort of thing. :good:
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
You should try rumrunner with the Rom @Seanie280672 posted to gain s-off. Not guaranteed to work as HTC started patching firmware at this point but if you need 100% stock it's your best chance to s-off without Sunshine.
If rumrunner won't work Sunshine is still cheaper than paying for the repair, and when you get your device back you can use Sunshine again for free, as long as it is the same device and not a replacement :good:
Did you select the option to install root when you flashed the rom?
Click to expand...
Click to collapse
Thanks for the info.
I did select to have the phone rooter.
However, I remembered that I forgot to switch fastboot off while testing rumrunner with the ROM from @Seanie280672.
I have now disabled this and am trying again. If it doesn't work, will reinstall the ROM again with CWM and *make sure* to have super user privileges (although I do have the Superuser app installed now just after flashing.)
I also remember that I had some super user issues when I was trying to install MIUI and had to install some zip via CWM. I still have that zip so will try with it.
Again, thank you VERY VERY much for helping me out!
Best,
Wisher
WisherBG said:
Thanks for the info.
I did select to have the phone rooter.
However, I remembered that I forgot to switch fastboot off while testing rumrunner with the ROM from @Seanie280672.
I have now disabled this and am trying again. If it doesn't work, will reinstall the ROM again with CWM and *make sure* to have super user privileges (although I do have the Superuser app installed now just after flashing.)
I also remember that I had some super user issues when I was trying to install MIUI and had to install some zip via CWM. I still have that zip so will try with it.
Again, thank you VERY VERY much for helping me out!
Best,
Wisher
Click to expand...
Click to collapse
your better off using TWRP recovery to flash the rom, there should be an option to root during the installer, but if there isnt then TWRP will ask you if you would like to root before leaving recovery.
Seanie280672 said:
your better off using TWRP recovery to flash the rom, there should be an option to root during the installer, but if there isnt then TWRP will ask you if you would like to root before leaving recovery.
Click to expand...
Click to collapse
Did it via CWM, made sure to select to root the phone. Still, I can do "su" when in the phone shell via adb, but it won't be directly with root access after "adb shell".
Now will try with TWRP (since installing the guru reset rom also resets the recovery to the HTC stock) and report back.
Good thing is I still have the MIUI backed up to use with CWM.
I will write soon.
Best,
Wisher