Related
my G1 was rooted when i was in android 1.5 with one click rooting method
then after upgrade to 1.6 i didn't found the root or the Cyanogen recovery and terminal didn't accept SU permission
how to solve that and return to root again????
if you truly lost root, the only thing u can do is re-root your phone. RC29 ect ect.
Why were u using a stock build anyways?
all you must is flash the recovery again, in the patch for 1.6 one click root is "illegal" therfore you must maually flash it through one of many methods which can be found by searching "root,g1,dream,downgrade,etc..."
What do you mean illegal? It was a kernal exploit and was patched in the new linux kernal.
i can not use terminal to flash the recovery again
is there a way to flash RA recovery image again??
You can use fastboot and flash recovery, instrucations in first post of his thread, link in my sig.
shall i download engineering SPL and flash it this is the fastboot u mean?
Well you never said what SPL you have now so I can't say...
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
Radio-2.22.19.26I
when i flash new update.zip i get
E: can't open /cache/recovery/command
Hard SPL: HSPL10.95.3000
Engineering SPL: HBOOT-0.95.3000
Original SPL: HBOOT-0.95.0000
Yes, you do need a new SPL with fastboot enabled.
can u give me the link for that SPL and how to download
thnx 4 ur help
when i install the new SPL they give me
E: no signature (5files)
E: verification failed
installation aborted
See, this "one-click" method should have never been revealed to general public. Now people don't even know how to properly gain and secure root.
OP, here's a suggestion: go read a sticky in the developement section on rooting (rc29, telnet, etc). After that you should have a pretty good understaning of how things work on your phone. If you did that to begin with you would have known that you can't flash any roms without root, can't fastboot, cant flash a different recovery.
I would give you a link to that thread but I really think that you need to learn how search as well.
Good luck
evilkorn said:
What do you mean illegal? It was a kernal exploit and was patched in the new linux kernal.
Click to expand...
Click to collapse
I meant illegal in a loose term meaning they didn't want it to happen like that, so it was closed....sorry for confusing some.
i need help not to start learning from begining
i said i already rooted my phone
borodin1 said:
See, this "one-click" method should have never been revealed to general public. Now people don't even know how to properly gain and secure root.
OP, here's a suggestion: go read a sticky in the developement section on rooting (rc29, telnet, etc). After that you should have a pretty good understaning of how things work on your phone. If you did that to begin with you would have known that you can't flash any roms without root, can't fastboot, cant flash a different recovery.
I would give you a link to that thread but I really think that you need to learn how search as well.
Good luck
Click to expand...
Click to collapse
if u read i root my phone with one click when i was in 1.5 and i test my recovery to be sure that a new recovery image is installed and after update to 1.6 i loose it
ahmed4474 said:
if u read i root my phone with one click when i was in 1.5 and i test my recovery to be sure that a new recovery image is installed and after update to 1.6 i loose it
Click to expand...
Click to collapse
Yeah, if you accept an over the air update, you will loose your custom recovery image, and since you didn't flash a Fastboot enabled SPL, you'll have to downgrade to get root back.
dead2hill said:
I meant illegal in a loose term meaning they didn't want it to happen like that, so it was closed....sorry for confusing some.
Click to expand...
Click to collapse
1 click root was a side effect of a kernel vulnerability, it has nothing do with tmo, htc, or google. It's more of a proof of concept. I won't belabor the point any more.
I agree with borodin1, 99% of the root tutorials say to install hard spl
I flashed 33 and my phone is stock. I need paid apps plus this build is bugging out on me alot. Stuff freezes, its just a bad build. How do I undo this without rooting?
Pretty sure you have to root.
If its like FRF91. Then it wont let you downgrade because it sees FRF91 as an "old version."
Download ere27 as passimg.zip. place in your sdcard root. Boot into recovery. Restore. Let it do its work. Put frf91 into sd card. Boot into recovery and load from zip. Ta da. You are on Frf 91
Sent from my Nexus One using Tapatalk
Or, if you want a shorter and more correct route:
Nexus One Wiki, "Restore", PASSIMG.ZIP method, use FRF91 complete stock image found in one of the threads in Q&A from the last day (or Google).
Don't use FRF91 update, since it's only an update - it's not a complete image.
whatever. Just use a passimg.zip to clean out all the crap. its basically the "do-over" method. Think etch-a-sketch flip and shake.
i tried passimg from http://forum.xda-developers.com/showthread.php?t=717870
it said failure because it was an older version. If i find that ere one will it let me do it? i dont mind going way back and working my way back to froyo, but i dont think i can passimg anything since its considered "older"
search the forum for how to downgrade your hboot- it exists just search for the thread
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=726258
androidjedi said:
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=726258
Click to expand...
Click to collapse
Thank you. Looks like ill have to root for it which im sure ill find if i search how to root 33 so ill wait for a while to see if something else comes up but at least I know there's a way
There is no other way but to root.
Since you're erasing the system you're rooting anyway, why do you care?
The full guide is now in the Wiki, including reverting HBOOT for those that need it.
Jack_R1 said:
There is no other way but to root.
Since you're erasing the system you're rooting anyway, why do you care?
The full guide is now in the Wiki, including reverting HBOOT for those that need it.
Click to expand...
Click to collapse
i dont know, i did 1 click root a few times but every rom i tried- cyan, eno, modac, whatever were great but there was always some bug or something that was annoying enough that i just wanted stock instead. So i dont know how much i like the idea of permanent root, but theres probably a stock rom i can use so its not the end of the world. SDK/Terminal i did all that crap with my g1, personally i found it to be more of a hassle than it was worth. But not having protected apps is not going to cut it so ill cave soon im sure
Again, maybe this time it'll be understood:
There is no "permanent root". The only "permanent" thing is unlocking the bootloader, which you don't have to do - the guide doesn't require it. The system you root will be erased in the PASSIMG method and replaced with a completely stock system of your choice. So, what's exactly stopping you from rooting?
Jack_R1 said:
Again, maybe this time it'll be understood:
There is no "permanent root". The only "permanent" thing is unlocking the bootloader, which you don't have to do - the guide doesn't require it. The system you root will be erased in the PASSIMG method and replaced with a completely stock system of your choice. So, what's exactly stopping you from rooting?
Click to expand...
Click to collapse
the only way to go back from FRG33 is to unlock the bootloader at this stage, the PASSIMG method does not work
When you revert HBOOT, it should work fine. Just the same as it works with Korean FRF91 version, which also has a new HBOOT. People in the FRG33 thread don't know it?
Why people can't understand?At this moment,if you've flashed stock FRG33 rom,using PASSIMG method,you can't root anymore!The only method to roll back to FRF91 is to unlock your bootloader,which is permanent and can't be un-done!
Cheers
Did you see that?
http://androidforums.com/1533396-post14.html
Or is it the only report? (in that case, the guy probably didn't try to run root).
Anyway, being unable to root makes you unable to flash PASSIMG of anything with bootloader lower than 0.35 - but did anyone try PASSIMG with Korean FRF91? It has the same HBOOT as FRG33, so it shouldn't be reported "older".
Jack_R1 said:
When you revert HBOOT, it should work fine. Just the same as it works with Korean FRF91 version, which also has a new HBOOT. People in the FRG33 thread don't know it?
Click to expand...
Click to collapse
Code:
[HOW-TO] Revert HBOOT 0.35.0017 to 0.33.0012
I CAN'T RELOCK THE BOOTLOADER!!!
This only reverts your SPL/HBOOT back to 0.33.0012 after you've installed the Korean FRF91 files and ended up stuck with 0.35.0017 SPL.
Thanks to the guys in the Desire forums and help from the Nexus Q&A, I have reverted my phone to the original HBOOT so I can apply custom roms again.
First you need to root the Korean FRF91 that's on your phone using Paul's instructions for superboot FRF83.
If you are rooted already, skip this step.
http://android.modaco.com/content/go...the-nexus-one/
Code:
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then press and hold the trackball to enter the bootloader
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
Note: If you are using a retail Nexus One, you may need to unlock the bootloader first, as detailed here.
Ok, let's make some order:
1) PASSIMG can flash versions with the same or higher HBOOT version - to check: will the same version flash? I believe so.
The official FRF91 has HBOOT 0.33.0012, the Korean FRF91 has 0.35.0017, and I suppose the FRG33 also has 0.35.0017 - correct?
2) Rooting isn't possible on FRG33 yet. 1 report doesn't count.
So, looking at this:
Using PASSIMG with the Korean FRF91 (complete with HBOOT 0.35.0017) will work over FRG33, if the HBOOT is indeed the same version.
Korean FRF91 is rootable.
Rooting Korean FRF91 allows to downgrade HBOOT, which in order allows to use PASSIMG method to flash official FRF91 with older HBOOT.
So, did anyone try PASSIMG with Korean FRF91?
Jack_R1 said:
Did you see that?
http://androidforums.com/1533396-post14.html
Or is it the only report? (in that case, the guy probably didn't try to run root).
Anyway, being unable to root makes you unable to flash PASSIMG of anything with bootloader lower than 0.35 - but did anyone try PASSIMG with Korean FRF91? It has the same HBOOT as FRG33, so it shouldn't be reported "older".
Click to expand...
Click to collapse
Downloading and testing, thanks for the tip, will report back.
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Hyun is looking for you at revolutionary irc channel.
Sent from my HTC Incredible S using Tapatalk
I know.. I have spoken to him.
jakeyo said:
I know.. I have spoken to him.
Click to expand...
Click to collapse
Any luck? still unable to flash anything?
jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
If you go to the development section of the HTC Incredible 2 forum, attn1 has a script tool that uses the latest Revolutionary/Unreovked exploit to downgrade the ROMand HBOOT to a version that is supported by Revolutionary.
If you look at the script, it is pretty simple. You would just need to use an older Virgin Mobile RUU.zip instead of the Inc2 version. It looks like the 2.12.981.2 would be the one to try.
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Doesnt matter if you need S-ON or S-OFF, as long as you get permissions to access root files.
Someone installed a custom bootloader so I can install custom ROM's, and it just works.... apparently the radios are locked though.
So, another day gone by and my phone is still not working. I can use MiUi, but I ran out of data on my 3g sim and wifi doesnt work, so now I have no internet on it.
katu2006 said:
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Click to expand...
Click to collapse
I'm pretty sure no soff will cause the issues he is experiencing, though he doesn't seem to be listening
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
Yes im a noob that has been using android since 2009..
You seem like a supreme douche.
Weren't you the one who was crying about wanting to go back to his iphone lol
jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
katu2006 said:
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
Click to expand...
Click to collapse
This thread is awesome
no, if I hold down power down and power button I see S-ON and HBOOT 1.16.0000
He typed in commands to give it root permissions, not sure exactly as he remote controlled my computer and typed it in. Then yes, he flashes CWM onto the phone then I installed revolutionary.
Firstly, I went onto the HTC dev site (created an account) and followed the steps to unlock the bootloader. In the end, it was successful, and once it's finished it will wipe the phone (AND WILL STILL SAY s-on)
So then the bootloader is now unlocked, and he did various commands in fastboot. My guess is that he installed CWM from there and it just worked.
at first, cyanogenmod would not boot, so he copied the (boot.img that is working) from MiUi and repled it with cyanogenmod's. The phone booted up and worked. Then he put it back how it was and it now works. Strange, but something must've given it a kick.
I'll repeat myself.
HBOOT 1.16.0000
S-ON
Cyanogenmod &.1 (stable)
Full root access
Need I say more to prove it?
As far as I know, I just cannot flash radios, which actually require the S-OFF....
sorry if I come across as rude, just a long day..
Talk to aftab565 he has the same hboot as you and has arhd running. Sounds like your phone was temp rooted and flashed and I would advise against letting people you don't know take remote access of your pc.
Hopefully it works for him I couldn't help.
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Didn't take my eyes off the screen either.
jakeyo said:
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Click to expand...
Click to collapse
You gotta give props to these guys for donating their time. Every day there's more talk about h-boot 1.16.0000 so I figure if devs want to keep devin there'll be a rev released eventually.
I really appreciate the amount of work hes done, in total I recon he's spent about 6 hours trying to help me getting it to work.
Never left me by myself, he always helped me through every step and was always there if I needed help. I've now got CM7 thanks to him. If he didn't fix it, I would have a useless phone because I couldn't even put on the stock ROM because of my HBOOT im guessing (I did an OTA update to get 1.16.0000 therefore too new to download)
I think SOME of the custom roms do have support for 1.16.0000 and what you only need is the boot file from them to boot up your non-booting ROM then you're all good.
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
2a. You don't need any existing root method to exist, there is no exploit involved in any of this, this will work irrespective of the current status of a root expoit existing or not.
2b. The phone does not have to be listed by HTC as being supproted. Any phone with a suitable hboot can be unlocked.
if this:
Code:
fastboot oem get_identifier_token
returns an identifier code then the phone can be ulocked.
globatron said:
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
Click to expand...
Click to collapse
Get a mod to make a hboot sticky there will be floods of this crap further down the road.
[DISCLAIMER]
I HAVE searched already, and the only result I get is a .12 radio that is NOT signed properly. I don't want this version.
[/DISCLAIMER]
Anyways, I was wondering if anyone could point me into the direction as to where to get an OFFICIAL signed radio, particularly the .12 Korean version. All links I can find to are not properly signed. I was planning to set up BLACKROSE and it requires the .12 radio to be flashed without disabling signature verification. Thanks much.
http://forum.xda-developers.com/wiki/Nexus_One/Radios
Androidity3000 said:
I was planning to set up BLACKROSE and it requires the .12 radio to be flashed without disabling signature verification.
Click to expand...
Click to collapse
Blackrose does not require the 5.12 radio. The only requirements (found in the first post of the development thread) are:
Code:
Windows PC or Linux PC
USB Debugging(ADB) ON
Connect USB before install
HBOOT 0.35.0017
The 5.08 radio (which most N1s are running) tends to be the best radio for people outside of Korea. In fact, it is the one that google released with the Gingerbread OTA update, and I am sure they did a lot of internal testing to determine which radio is the best.
Signed for "fastboot flash" on locked bootloader? Or signed ZIP to flash through recovery?
If you mean bootloader: 5.12 was only released for Korean version, which is different from Google main line (SW-wise only, since it's the same phone). Thus, if it's not accepted by your current bootloader - you won't get it Google-signed anywhere, and you won't be able to flash it through fastboot with locked bootloader, if that's what you're looking for. Last version in Google updates is 5.08.
On the other hand, if you mean signed ZIP for flashing in custom recovery - then it's funny, because ANYONE can sign those ZIPs. Anyone. I can sign it for you with a testkey (that's all that recovery needs). Would that make it more "official"?
In any case, as mentioned before, you don't need it. You need 5.08 and above.
Thanks for the link. I will just use the 5.08 version then. I thought I read that .12 was needed; however, I guess I am mistaken. Glad to know. And yes, I was planning to flash through recovery. Again, thanks much!
In that case, you can flash 5.12 as well. Being signed doesn't make the update.zip official, since all the files for flashing in custom recovery are signed by people, just like myself. 5.12 radio is just as legitimate as 5.08, and both update.zip weren't signed by Google anyway. You do need to verify the md5sum before flashing, though.
I'm overwhelmed by all the shop speak regarding the android OS. Everything's an acronym, and everything sounds vaguely similar to everything else. Stock recovery, stock rom, stock firmware, factory reset, I'm a computer literate person, and I don't know what the difference is between any of these things, I only know that they're serious.
So here's my situation:
I have a Sprint HTC One M8, unlocked with s-off.
I have adb installed on my PC, TWRP and Super SU installed on my phone,
I need to install system updates, first to install KitKat 4.4.4, then immediately after, Lollipop.
When I go to install
my phone boots into TWRP mode
I go to update
select the update zip
swipe to flash
and get "updating partition details... failed"
I gather that I'm supposed to first restore to a stock recovery, and I think I found the correct one here, but the instructions I'm finding are very convoluted. I need to either unlock or lock my bootloader using adb. I need to flash one of the downloads on that page, but I'm not certain which one, how to flash it.
I understand that this isn't a forum for newbies, but that's just the thing, I'm not usually lost when it comes to this stuff, which makes me think many others are probablylost as well.
Can anyone clearly explain the steps I need to take, with a minimum of acronyms, to do whatever you do with a stock recovery to then be able to install Sprint updates?
I posted this question in a different way back in November and had one member keep posting unhelpful answers until the whole thread got hijacked by piggyback questions. I've also found step by step guides that each conflict with one another. One may have 5 steps and the other may have 12, and in one way or another they've always gone off the rails until they no longer seemed to apply to my use case.
If you can help, thank you.
Dr.Zee said:
I'm completely overwhelmed by all the shop speak regarding the android OS. Everything's an acronym, and everything sounds vaguely similar to everything else. Stock recovery, stock rom, stock firmware, factory reset, I don't know what the difference is between any of these things, I only know that they're serious.
So here's my situation:
I have a Sprint HTC One M8, unlocked with s-off.
I have adb installed on my PC, TWRP and Super SU installed on my phone,
I need to install system updates, first to install KitKat 4.4.4, then immediately after, Lollipop.
When I go to install
my phone boots into TWRP mode
I go to update
select the update zip
swipe to flash
and get "updating partition details... failed"
I gather that I'm supposed to first restore to a stock recovery, and I think I found the correct one here, but the instructions I'm finding are very convoluted. I need to either unlock or lock my bootloader using adb. I need to flash one of the downloads on that page, but I'm not certain which one, how to flash it.
I understand that this isn't a forum for newbies, but that's just the thing, I'm not usually lost when it comes to this stuff, which makes me think many others are probablylost as well.
Can anyone clearly explain the steps I need to take, with a minimum of acronyms, to do whatever you do with a stock recovery to then be able to install Sprint updates?
I posted this question in a different way back in November and had one member keep posting unhelpful answers until the whole thread got hijacked by piggyback questions.
If you can help, thank you.
Click to expand...
Click to collapse
First things first, this is a forum for all kinds but there is a Q&A section.
On to the update.
The first thing you need to do is boot to fastboot and type "fastboot oem lock" without quotes and press enter.
The device should be locked and from there you should be able to run the RUU (ROM update utility) that comes directly from htc, no need to do the incremental updates from KK (kitkat) to LP (Lollipop) unless you are looking to do something specific on a certain radio or firmware.
No need to flash stock recovery if you run the RUU, only lock the bootloader.
The RUU files are found on the HTC website or in this thread: http://forum.xda-developers.com/showthread.php?t=2729173 and you should find the directions there, just follow the S-on procedure if you are S-ON, you would know because at this point the only way to obtain S_OFF is to pay 25$ to use the Sunshine app.
This might be able to be moved to the Q&A by a mod and there are plenty of users and devs around here willing to help, just ask questions and try to follow the directions first.
dopy25 said:
First things first, this is a forum for all kinds but there is a Q&A section.
On to the update.
The first thing you need to do is boot to fastboot and type "fastboot oem lock" without quotes and press enter.
The device should be locked and from there you should be able to run the RUU (ROM update utility) that comes directly from htc, no need to do the incremental updates from KK (kitkat) to LP (Lollipop) unless you are looking to do something specific on a certain radio or firmware.
The RUU files are found on the HTC website or in this thread: http://forum.xda-developers.com/showthread.php?t=2729173 and you should find the directions there, just follow the S-on procedure if you are S-ON, you would know because at this point the only way to obtain S_OFF is to pay 25$ to use the Sunshine app.
This might be able to be moved to the Q&A by a mod and there are plenty of users and devs around here willing to help, just ask questions and try to follow the directions first.
Click to expand...
Click to collapse
Thank you very much, I'll run through these steps.
Question, I installed a couple firmware patches after I got s-off. when this is finished, will those be overwritten? Will my phone still be s-off, or would I have to pay to have that done again?
Dr.Zee said:
Thank you very much, I'll run through these steps.
Question, I installed a couple firmware patches after I got s-off. when this is finished, will those be overwritten? Will my phone still be s-off, or would I have to pay to have that done again?
Click to expand...
Click to collapse
So you are S-OFF, OK.
No, the S_OFF is tracked by the device I believe, and would still be able to be used without having to pay again. I have read that many places.
I would not do the full RUU if you are s-off, but the thread I linked has zips to flash firmwares and roms and keep S_OFF. I am still on so I have no experience with S-OFF but I would not lock the bootloader until another s-off user confirms.
dopy25 said:
So you are S-OFF, OK.
No, the S_OFF is tracked by the device I believe, and would still be able to be used without having to pay again. I have read that many places.
I would not do the full RUU if you are s-off, but the thread I linked has zips to flash firmwares and roms and keep S_OFF. I am still on so I have no experience with S-OFF but I would not lock the bootloader until another s-off user confirms.
Click to expand...
Click to collapse
I got a little wreckless and just went ahead and tried it. Everything worked. I'm running Lollipop, I still have S-off, and I just re-rooted through the HTC dev program. The firmware patches I installed were overwritten, but, you can't have everything.
Thank you very much, I'd been dealing with system update messages for months.
Dr.Zee said:
I got a little wreckless and just went ahead and tried it. Everything worked. I'm running Lollipop, I still have S-off, and I just re-rooted through the HTC dev program. The firmware patches I installed were overwritten, but, you can't have everything.
Thank you very much, I'd been dealing with system update messages for months.
Click to expand...
Click to collapse
What do you mean by patches? Just specific bits of firmware? I don't really know of any benefits to having specific bootloader or hboot or radio over another. It used to matter back in the day but I think it is best to have the most updated if you are going to run a newer ROM anyway.
Also, if you are S-OFF you can always downgrade any of them at any time. So if any of the patches you had before gave you any benefits you can always run them again.
Glad you got it taken care of. On any note, if you muck something up you can always run the RUU to get back to stock. HTC did us a huge favor with those.
dopy25 said:
What do you mean by patches? Just specific bits of firmware? I don't really know of any benefits to having specific bootloader or hboot or radio over another. It used to matter back in the day but I think it is best to have the most updated if you are going to run a newer ROM anyway.
Also, if you are S-OFF you can always downgrade any of them at any time. So if any of the patches you had before gave you any benefits you can always run them again.
Glad you got it taken care of. On any note, if you muck something up you can always run the RUU to get back to stock. HTC did us a huge favor with those.
Click to expand...
Click to collapse
It's a patch that adds Harmon Kardon sound. Then I incorrectly remembered an app that enables Snapdragon audio (which is far superior to HK sound) but that's not firmware, you just need a rooted phone to be able to drop it into the system folder.