So I just spent the last couple hours trying to root my phone. Only to realize that when I unlocked the bootloader i requested the wrong unlock.bin file. Instead of selecting the htc m8 file, I selected all other supported devices. I don't know if this is the cause of my problem, but since I can't reboot to bootloader, I feel that it is. Is the solution as simple as relocking the bootloader and then unlocking it with the correct unlock.bin file. Or can i just get the correct file and unlock it again. I don't know if any of it will work since the phone won't go into the bootloader. Thought I would as people that know more than me before I brick my phone.
Getting all the stock files from here and then using your cpu to flash everything you should be fine.
jayandare said:
Getting all the stock files from here and then using your cpu to flash everything you should be fine.
Click to expand...
Click to collapse
Ok, Thought I would have to be able to reboot to bootloader in order to flash but I will give that a try. Was there supposed to be a link or did you just mean "from here" as in the xda site?
Tskizzle said:
Ok, Thought I would have to be able to reboot to bootloader in order to flash but I will give that a try. Was there supposed to be a link or did you just mean "from here" as in the xda site?
Click to expand...
Click to collapse
Stock ruu method ,lock bootloader first
manish dubey said:
Stock ruu method ,lock bootloader first
Click to expand...
Click to collapse
Ok thanks. I'll do some searching and figure out how to do that, then try and flash the stock ruu. I'll report back if I have any issues. Thank you again.
Tskizzle said:
Ok thanks. I'll do some searching and figure out how to do that, then try and flash the stock ruu. I'll report back if I have any issues. Thank you again.
Click to expand...
Click to collapse
So I've been reading around and come across some conflicting info. So I finally found the fastboot command to lock the bootloader but some have said to flash the stock ruu first while others say after. Can anyone clear this up for me and let me know if it makes a difference?
S-OFF - no need to relock the bootloader, just run the appropriate RUU
S-ON - relock the bootloader and then run the appropriate RUU
cheers.
Mr Hofs said:
S-OFF - no need to relock the bootloader, just run the appropriate RUU
S-ON - relock the bootloader and then run the appropriate RUU
cheers.
Click to expand...
Click to collapse
Thanks for the help. I think I can handle this now. Is it worth it to go S-off? I'm gonna root once I am back to stock
Tskizzle said:
Thanks for the help. I think I can handle this now. Is it worth it to go S-off? I'm gonna root once I am back to stock
Click to expand...
Click to collapse
Quick reattack on this. I never actually went away from stock. As I couldn't get into the bootloader I never flashed twrp or anything so do I really need to flash the stock RUU? Just trying to figure out for knowledge purposes. Am I basically flashing the RUU to start over from scratch or is it just a precautionary thing?
Related
hey guys so i just got my inc 2 a couple days ago and of course it has the newest update and software which prevents me from downgrading to .97. So i decided to go the HTCdev unlocked BL way. Is there anyway i can flash custom ROMs and still have root access without downgrading to hboot.97?
any help is appreciated THANKS!!
sure can, if boot loader is unlocked, look here:http://forum.xda-developers.com/showthread.php?t=1435228
OK here's a problem though. I cant flash the CWM recovery because i need s-off and i cant get s-off because im unable to downgrade with my new system software. Any way to flash custom roms without CWM?
What about the ext4 touchescreen recovery. I am using it and it is nice. Download the app and then it installs the recovery. Not sure if that will help I have s off so this is new to me. But might be worth a shot.
Aldo101t said:
sure can, if boot loader is unlocked, look here:http://forum.xda-developers.com/showthread.php?t=1435228
Click to expand...
Click to collapse
nvm! successfully rooted! Thanks for the reference man!
Travisdroidx2 said:
What about the ext4 touchescreen recovery. I am using it and it is nice. Download the app and then it installs the recovery. Not sure if that will help I have s off so this is new to me. But might be worth a shot.
Click to expand...
Click to collapse
whats your software number?
Now mine is
tsm m 5.01 ext4
the link above tells you how to flash clockworkmod, you flash the img same as a boot.img
ypu don't need s-off to flash cwmr, follow the directions from above
Aldo101t said:
the link above tells you how to flash clockworkmod, you flash the img same as a boot.img
ypu don't need s-off to flash cwmr, follow the directions from above
Click to expand...
Click to collapse
yeah i am rooted now. i just am trying to figure out how to get s-off with the new 6.1 software
someone has something on that taroot or something like that, check around on the site here.
Aldo101t said:
someone has something on that taroot or something like that, check around on the site here.
Click to expand...
Click to collapse
do you know you this is the post your talking about? http://forum.xda-developers.com/showpost.php?p=26296376&postcount=276
yeah, thats it i think, but i haven't had occasion to use it yet, so i don't know how it works, keep in mind you'll have to relock your bootloader to use it, i think. research it a little before you try
so whats the difference with having s-off compared to s-on?
you won.t have to flash a boot image everytime you install a rom, it also enables you to flash radios. you can't now. but no biggy.
I was trying to return to stock and I was following this guide on my Verizon HTC one
http://forum.xda-developers.com/showthread.php?t=2475216
Everything was going good, Until I flashed the Stock RUU using this command
Fastboot flash zip Rom.zip
As it states in the step by step it will fail just try again that is normal. Well It failed again and I thought that meant go on to the next steps.
SO now I have The Phone locked, S-ON and I cant get it to get past the Fastboot screen.
I tried send a recovery.img to the phone but it wont obviously go.
Man I Need help, ANYONE???
I am thinking I need a boot.img file maybe??
Solved. Thread can be closed or removed.
How did you solve it? I was gonna suggest maybe try running rumrunner again to re-achieve s-off and then just flash a ruu
bootsie99 said:
Solved. Thread can be closed or removed.
Click to expand...
Click to collapse
Murrda said:
How did you solve it? I was gonna suggest maybe try running rumrunner again to re-achieve s-off and then just flash a ruu
Click to expand...
Click to collapse
I had to download an encrypted ruu cause when I would run the above steps with an decrypted ruu it would fail at the signature. I was sweating it big time.
If I install a rom that does not have root will that do the trick? Can someone give me a link please
http://theunlockr.com/2014/06/08/how-to-unroot-the-htc-one-m8-video/
Used something similar myself
Just run whatever ruu you need and send it in...
I've sent in multiple HTC devices that was s-off, still shown unlocked and tampered. Hell I've sent an M7 with android revolution, custom splash and custom boot animation, and GE bootloader still on it. (Bootloader was black). They've never rejected me yet
InflatedTitan said:
Just run whatever ruu you need and send it in...
I've sent in multiple HTC devices that was s-off, still shown unlocked and tampered. Hell I've sent an M7 with android revolution, custom splash and custom boot animation, and GE bootloader still on it. (Bootloader was black). They've never rejected me yet
Click to expand...
Click to collapse
Think you need to read it again. He is S-ON so he can't run any ruu, and not that there are many either ! Have you seem a 2.22.401 ruu for instance ?
Nope.....
@ O.P
For s-on devices i suggest this
Method 1:
Return to the official stock rom via a stock nandroid backup and flash the stock recovery.
The bootloader will say unlocked and you can only get it to say RELOCKED.
Method 2:
Flash a stock rom and recovery and perform sunshine to s-off the device and then return it to full stock and with s-off you can also turn the bootloader to LOCKED.
Brother. Read mine again. I said whatever ruu "you need".
I didn't say any old ruu
However I do thank you for clarifying. I should have made it more clear to use the one specific to his carrier and device.
InflatedTitan said:
Brother. Read mine again. I said whatever ruu "you need".
I didn't say any old ruu
However I do thank you for clarifying. I should have made it more clear to use the one specific to his carrier and device.
Click to expand...
Click to collapse
No problem. I also read fast. But "international" ruu's are very rare......it's easier to find a stock backup than a ruu these days
Mr Hofs said:
No problem. I also read fast. But "international" ruu's are very rare......it's easier to find a stock backup than a ruu these days
Click to expand...
Click to collapse
You the man Mr Hofs. You know your stuff indeed.
InflatedTitan said:
You the man Mr Hofs. You know your stuff indeed.
Click to expand...
Click to collapse
Not always.....i also make many errors
Hey folks.
So I was running CM11 on my Rogers M8 for quite some time, until I decided to flash Sense based roms. Uh-oh, Wifi doesnt work anymore. Decided to do some digging, and realized that it's due to my older firmware which needs to be updated.
I followed the guides, and did the following to prepare:
Flashed stock recovery. I know it worked due to the triangle and explamation mark.
Relocked the bootloader through ADB commands.
Proceeded to ADB "fastboot getvar all" to see my current version.
That's when I saw that right next to the "version-main" it's empty. No numbers. Consequently, I haven't been able to flash any firmwares since it never passes any checks.
I am S-ON (firewater didnt work), CID is ROGER001, and completely exhausted. Please, help me figure this out.
yasha.sinitski said:
Hey folks.
So I was running CM11 on my Rogers M8 for quite some time, until I decided to flash Sense based roms. Uh-oh, Wifi doesnt work anymore. Decided to do some digging, and realized that it's due to my older firmware which needs to be updated.
I followed the guides, and did the following to prepare:
Flashed stock recovery. I know it worked due to the triangle and explamation mark.
Relocked the bootloader through ADB commands.
Proceeded to ADB "fastboot getvar all" to see my current version.
That's when I saw that right next to the "version-main" it's empty. No numbers. Consequently, I haven't been able to flash any firmwares since it never passes any checks.
I am S-ON (firewater didnt work), CID is ROGER001, and completely exhausted. Please, help me figure this out.
Click to expand...
Click to collapse
The Bootloader 3.18. tells you, you have 2.x firmware
So what is stopping me from flashing new firmware each time?
yasha.sinitski said:
So what is stopping me from flashing new firmware each time?
Click to expand...
Click to collapse
Not being SuperCID?
What do you mean each time?
You can flash stock firmware without going back to stock. As long as your MID and CID match.
Just download stock rogers firmware, rename and install it in hboot, or use RUU mode in fastboot.
xunholyx said:
Not being SuperCID?
What do you mean each time?
You can flash stock firmware without going back to stock. As long as your MID and CID match.
Just download stock rogers firmware, rename and install it in hboot, or use RUU mode in fastboot.
Click to expand...
Click to collapse
You see, I tried that. I downloaded stock rogers firmware, and ADB just spits out an error message saying that something doesnt match up. If I recall, it was error 12.
yasha.sinitski said:
You see, I tried that. I downloaded stock rogers firmware, and ADB just spits out an error message saying that something doesnt match up. If I recall, it was error 12.
Click to expand...
Click to collapse
It might be because you have a modified /system partition. Do you use Xposed?
xunholyx said:
It might be because you have a modified /system partition. Do you use Xposed?
Click to expand...
Click to collapse
No. My endgoal is to simply be running Roger's stock rom with full functionality. I just cant figure out how to get to that. I dont care about getting OTAs.
yasha.sinitski said:
No. My endgoal is to simply be running Roger's stock rom with full functionality. I just cant figure out how to get to that. I dont care about getting OTAs.
Click to expand...
Click to collapse
Here are all the files to download to go back to stock rogers. Download and zip them, then use TWRP to flash. Afterwards you will just have to install a stock recovery to be fully stock, but if you don't carte about OTAs, stick with TWRP. That way you can make nandroid backups.
EDIT: I'm mistaken here. You need them unzipped. PM sent.
For others with the same issue of returning to Canadian stock, go to this thread for links and a guide on how to do so.
xunholyx said:
Here are all the files to download to go back to stock rogers. Download and zip them, then use TWRP to flash. Afterwards you will just have to install a stock recovery to be fully stock, but if you don't carte about OTAs, stick with TWRP. That way you can make nandroid backups.
Click to expand...
Click to collapse
Are you going to post links? No matter what you do, I cant thank you enough for your help.
yasha.sinitski said:
Are you going to post links? No matter what you do, I cant thank you enough for your help.
Click to expand...
Click to collapse
Whoops!
Here ya go.
xunholyx said:
Whoops!
Here ya go.
Click to expand...
Click to collapse
Doing all that right now. I'll update how it goes.
yasha.sinitski said:
Doing all that right now. I'll update how it goes.
Click to expand...
Click to collapse
The getvar tell me, you are S-ON.
But you need S-OFF to flash a new firmware.
Otherwise you brick your phone.
That the firmware number is not showing is not critical i think. Its a symtom of some roms.
I flashed the newest firmware to my m7, number was showing. Then i flash Viper 7.0.1 and after that, my number is hidden.
But everything works, so i think its not critical.
Roma80 said:
The getvar tell me, you are S-ON.
But you need S-OFF to flash a new firmware.
Click to expand...
Click to collapse
Not true, you can flash the latest firmware if you're S-ON, the only "catch" is that it MUST be the correct MID and CID(That's in Firmware.zip) else it won't flash.
It's also the only way for an S-ON device to update it's Radio, as it won't be able to manually flash Radio's if it's not S-OFF.
Of course you need to relock your bootloader to do this with S-ON. So get stock recovery also, of course make backups of everything you need backed up as relocking it might erase all data.
BerndM14 said:
Not true, you can flash the latest firmware if you're S-ON, the only "catch" is that it MUST be the correct MID and CID(That's in Firmware.zip) else it won't flash.
It's also the only way for an S-ON device to update it's Radio, as it won't be able to manually flash Radio's if it's not S-OFF.
Of course you need to relock your bootloader to do this with S-ON. So get stock recovery also, of course make backups of everything you need backed up as relocking it might erase all data.
Click to expand...
Click to collapse
Oh okay, good to know.
I read wrong / missunderstood on other thread.
Roma80 said:
Oh okay, good to know.
I read wrong / missunderstood on other thread.
Click to expand...
Click to collapse
Yeah, Mike's guide has some good info. A lot of misinformation out there about some stuff.
He also has an excellent blog with plenty of info/resources if you're bored and what to read up on some stuff. Great site.
Android Revolution HD :good:
So I messed up a bit when relocking my bootloader. I relocked the bootloader, and completely forgot that I had the ElementalX kernel installed. Now I'm at a point where my phone wont boot because it has a custom kernel installed on top of a locked bootloader, and I can't boot the phone to enable OEM unlocking. What the hell do I do here?
Flash the stock images.
flonker said:
Flash the stock images.
Click to expand...
Click to collapse
Doesn't the bootloader need to be unlocked?
harritaco said:
Doesn't the bootloader need to be unlocked?
Click to expand...
Click to collapse
You can still do that. If you want to get back to stock, read through this:
https://developers.google.com/android/images
Just make sure you download the correct images and follow the instructions. Read through everything before you start.
Edit: This is dependent on being able to get into fastboot, which, judging from another thread, might not be possible in your situation. Hopefully you still can boot into fastboot using the key commands.
flonker said:
You can still do that. If you want to get back to stock, read through this:
https://developers.google.com/android/images
Just make sure you download the correct images and follow the instructions. Read through everything before you start.
Edit: This is dependent on being able to get into fastboot, which, judging from another thread, might not be possible in your situation. Hopefully you still can boot into fastboot using the key commands.
Click to expand...
Click to collapse
That is not an option. You need to have the bootloader unlocked in order to flash the images. I can't unlock the bootloader because I can't boot the device. I can get in to fastboot, and watch the charging animation, thats it. I can push commands, then it just comes back at me and tells me that I need to unlock the bootloader.
Running "fastboot continue" let me in. I was able to get the bootloader unlocked again.
harritaco said:
Running "fastboot continue" let me in. I was able to get the bootloader unlocked again.
Click to expand...
Click to collapse
Awesome man. I need to archive this solution as we all have brainfarts sometimes and it's only a matter of time before myself or someone else stumbles. Thanks for sharing your solution.
schwem said:
Awesome man. I need to archive this solution as we all have brainfarts sometimes and it's only a matter of time before myself or someone else stumbles. Thanks for sharing your solution.
Click to expand...
Click to collapse
I definitely can't take credit for it, I saw it on a PSA thread that jcase posted on XDA regarding this topic. I happened to find the post after somebody mentioned him in my reddit post.
https://imgur.com/a/8O93m
harritaco said:
I definitely can't take credit for it, I saw it on a PSA thread that jcase posted on XDA regarding this topic. I happened to find the post after somebody mentioned him in my reddit post.
https://imgur.com/a/8O93m
Click to expand...
Click to collapse
Hey! I'm the guy that mentioned the jcase solution in your Reddit post. Glad you got it fixed.
Anyone have any idea what to do if "fastboot continue" does not work. As I too am stupid and relocked the bootloader. Now all I get is "this device is courpt" when I try to boot it up.
longbowpilot said:
Anyone have any idea what to do if "fastboot continue" does not work. As I too am stupid and relocked the bootloader. Now all I get is "this device is courpt" when I try to boot it up.
Click to expand...
Click to collapse
Did you load into bootloader (vol down + power) and try to run "fastboot -w" (to wipe userdata) then "fastboot continue" and wait 10 min. If you still don't boot power down, go into bootloader again and try "fastboot continue" again.
Sent from my sailfish using XDA Labs
I have tried the "fastboot -w" it says failed and the phone still says courpt. I guess ill just get a replacement. Thanks for the help.
I just want to confirm 100%...flashing stock will not RELOCK bootloader correct? I have a terrible freezing and force closing issue after rooting. I have flashed the stock boot image and tried other kernels but it hasn't helped. So I'm going to flash complete stock but afraid it will RELOCK bootloader
Forgot to mention I have an OTA but the download/install fails every time
Sent from my Pixel XL using XDA-Developers mobile app
Flashing stock will not relock the bootloader.
DIXZ06 said:
Flashing stock will not relock the bootloader.
Click to expand...
Click to collapse
Good to hear. Thank you for confirming
Sent from my Pixel XL using XDA-Developers mobile app
It happened in my case, i forgot to oem unlocking and usb debugging activated.. my rom is 7.1.1, need help, i am stuck in dot loop..
flonker said:
Flash the stock images.
Click to expand...
Click to collapse
This will not work with a locked bootloader. If it did, anyone could flash older firmware and use the bootloader unlock tool. You're screwed once you relock the bootloader with a non stock kernel. Unfortunately for the OP, I suspect he now has a very expensive paper weight.
Mike02z said:
This will not work with a locked bootloader. If it did, anyone could flash older firmware and use the bootloader unlock tool. You're screwed once you relock the bootloader with a non stock kernel. Unfortunately for the OP, I suspect he now has a very expensive paper weight.
Click to expand...
Click to collapse
Op fixed his issue. Read one page back. He got it to boot with fastboot continue.
On a side note. Why the hell is anyone locking their bootloader's.
toknitup420 said:
Op fixed his issue. Read one page back. He got it to boot with fastboot continue.
On a side note. Why the hell is anyone locking their bootloader's.
Click to expand...
Click to collapse
dont understand that too^^
I think there should be a sticky that not to relock the bootloader before reading the proper instructions or please search the xda forums.
Sent from my Pixel XL using XDA-Developers Legacy app