Related
I have read countless threads on here. So please do not say "search is your friend," or "there are posts" since I read them all, and it did not help.
Here is my setup, I am running Nexus One GingerBread STOCK (without root or anything else), and I do NOT have CWM (if I did, I would have no issue).
I want to root my phone, since that is not possible right now, I want to revert back to froyo, then root, then install Rom Manager/CWM.
I have tried PASSIMG, 'main version' error when using standard way (power + volume down)..
I have tried flashing roms, get authentication error.
I do not want to unlock my bootloader..
Can anyone provide steps (if possible) to revert my nexus one back to stock or earlier version so I can install CWM and used a rooted/modd'd rom?
Thank you in advance!
real1st
you can used PASSIMG for FRG33 down to 2.2 (PASSIMG is flash in HBOOT not in recovery)
Sent from my Nexus One using XDA App (Rooted at stock GRI40)
fastboot oem unlock
~
Mincing words..
I used PASSIMG.zip correctly, by pressing power button and down volume button, it automatically checks for it, and found it. Once it did (the bar in top right) it told me error, main version older!. ..
I do not want to unlock my bootloader..
Any other thoughts?
kenny wong said:
you can used PASSIMG for FRG33 down to 2.2 (PASSIMG is flash in HBOOT not in recovery)
Sent from my Nexus One using XDA App (Rooted at stock GRI40)
Click to expand...
Click to collapse
I do not want to unlock my bootloader.. any other ideas?
real1st said:
Mincing words..
I used PASSIMG.zip correctly, by pressing power button and down volume button, it automatically checks for it, and found it. Once it did (the bar in top right) it told me error, main version older!. ..
I do not want to unlock my bootloader..
Any other thoughts?
Click to expand...
Click to collapse
Same here...
Why don't you want to unlock. It isn't like it is going to hurt anything. And it sounds like you are not going to be able to flash the file because it is a older version. the easy fix is to fastboot oem unlock. HTC still honors the warranty for hardware. Also why are you wanting to go back to 2.2. 2.3 is fine.
~
Couple reasons.. First.. The warranty status (I just received this phone back from replacement).. that is not garunteed, it is subjective, its not across the board, and you can be rejected. Hence the warning when you try to unlock it.
Second, I do not want an unlocked padlock when I use my phone. Was hoping for another way..
Anyone?
real1st
real1st said:
Couple reasons.. First.. The warranty status (I just received this phone back from replacement).. that is not garunteed, it is subjective, its not across the board, and you can be rejected. Hence the warning when you try to unlock it.
Second, I do not want an unlocked padlock when I use my phone. Was hoping for another way..
Anyone?
real1st
Click to expand...
Click to collapse
You have 2 possibilities. Firstly, check your radio version...if you have 5.x, that may be the problem, and you may need to attempt to reflash an older radio first, THEN attempt the passimg.
Secondly, wait for gingerbreak, root via that exploit, and then install clockwork or other recovery to flash an old ROM.
It is 5.x in order to flash gingerbread you had to update your boot/radio.
Is there a step-by-step to do it that way?
Find me an example of HTC not doing warranty repairs because of unlocked bootloader. If your hardware fails they will fix it if its still under warranty
You don't want to see a padlock when you use your phone? So you use your phone during the boot screen?
Stop this nonsense and unlock the bootloader.
Sent from my Nexus One using XDA App
~
Re: Albunday2010
Interesting post. Rather than contribute, you decided to be condescending.
My reasons for not wanting to unlock my bootloader is inconsequential. If you disagree with them, that is your choice, save the post for another thread, that asks for your judgement.
Thank you in advance.
Regards,
real1st
Yeah, albundy, that was kind of uncalled for. I think it's kind of silly, too; but he's asking for help, not condescending remarks.
real1st, you would need to find an older radio image...one of the 4.x's and attempt to flash it in fastboot using the "fastboot flash radio <radioname>.img" command. It MIGHT not let you do that, though...at which point, you may have to just wait for gingerbreak.
He is asking for help when he was already helped. The answer has already been clearly stated in this thread. He doesn't like the answer, but tough, that is what he has to do. There aren't really any other options at this time.
GldRush98 said:
He is asking for help when he was already helped. The answer has already been clearly stated in this thread. He doesn't like the answer, but tough, that is what he has to do. There aren't really any other options at this time.
Click to expand...
Click to collapse
+1
Your only options are passimg, and if that fails with the"main version" error, then unlock the bootloader if you wish...
Flashing different hboot or radio images won't help, and you certainly can't use fastboot to flash them unless you unlock the bootloader...
Sent from my Nexus One using XDA App
B3astofthe3ast said:
fastboot oem unlock
Click to expand...
Click to collapse
not if you like your warranty
Prod1702 said:
Why don't you want to unlock. It isn't like it is going to hurt anything. And it sounds like you are not going to be able to flash the file because it is a older version. the easy fix is to fastboot oem unlock. HTC still honors the warranty for hardware. Also why are you wanting to go back to 2.2. 2.3 is fine.
Click to expand...
Click to collapse
no they dont.
albundy2010 said:
Find me an example of HTC not doing warranty repairs because of unlocked bootloader. If your hardware fails they will fix it if its still under warranty
You don't want to see a padlock when you use your phone? So you use your phone during the boot screen?
Stop this nonsense and unlock the bootloader.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
its not nonsesne if you like your warranty. also, yes they will fix it but at your cost of like 130 bucks.
GldRush98 said:
He is asking for help when he was already helped. The answer has already been clearly stated in this thread. He doesn't like the answer, but tough, that is what he has to do. There aren't really any other options at this time.
Click to expand...
Click to collapse
he will just have to wait for a software loop hole. this is the reason you should not immediately update your phone.
HTC does do warranty repairs on unlocked phones. You people keep bringing this up in thread after thread after thread. If your phone has a hardware issue that they cover under the 1 year warranty they will fix it regardless of the state of the bootloader.
They charge you when your 1 year warranty is up or when you do something stupid that would not be covered under warranty anyways.
All these people need to read the wiki and the forum itself. Just about every day since the OTA came out there have been two threads on the front page of the forum asking the same thing.
I look forward to the day that everybody's warranty has expired. There will still be these threads after a OTA because people don't want to void the warranty or see a padlock on the screen during boot.
At first, sorry for my bad english.
My Question is, if my Display is broken, can i screenshot the bootloader or recovery with commands?
I had the One X and let it fall and my Display worked only sometimes, but i could see what i was doing so i flashed stock recovery and rom and relocked the bootloader so htc repaired it. If this happens again with my htc one, and the display doesnt work, how to know, if i am on the booloader menu, or fastboot and see if it all work? i want to unlock and s-off my device.
Second Question: If my device is s-off, should i go back to s-on or htc doesnt care about it?
1. Fastboot getvar all
2. They don't care
Sent from my iPod touch using Tapatalk
caniix said:
At first, sorry for my bad english.
My Question is, if my Display is broken, can i screenshot the bootloader or recovery with commands?
I had the One X and let it fall and my Display worked only sometimes, but i could see what i was doing so i flashed stock recovery and rom and relocked the bootloader so htc repaired it. If this happens again with my htc one, and the display doesnt work, how to know, if i am on the booloader menu, or fastboot and see if it all work? i want to unlock and s-off my device.
Second Question: If my device is s-off, should i go back to s-on or htc doesnt care about it?
Click to expand...
Click to collapse
the other guy said everything correctly but I want to add that for me they repaired it with s off and they didn't charge me.. but sometimes if you are unlucky they will say that you have to pay... don't listen to them and phone HTC directly etc...
Ok thanks to both of you
Okay guys I've kinda messed up my phone. I'm gunna try and keep this brief , but I need to relock and unroot my phone mainly for warranty purposes. My phone is In a reboot loop, i turn it on and it stays on for about a minute but then it turns off by itself (might be to do with a sunken in lock button I'm not sure). I want to send it back to htc so that they can sort out the lock button, but as it is rooted and unlocked , and simply not working i think my warranty is void.
I've watched various you tube videos and want to use an RUU to restore it , but I'm not too sure which one too use , (does it really matter?) . I am UK orange EE carrier . I've attached my phones details. Can anyone assist me further please , I am hopeless lol . Thank you if you've read this far.
Rsdhillon said:
Okay guys I've kinda messed up my phone. I'm gunna try and keep this brief , but I need to relock and unroot my phone mainly for warranty purposes. My phone is In a reboot loop, i turn it on and it stays on for about a minute but then it turns off by itself (might be to do with a sunken in lock button I'm not sure). I want to send it back to htc so that they can sort out the lock button, but as it is rooted and unlocked , and simply not working i think my warranty is void.
I've watched various you tube videos and want to use an RUU to restore it , but I'm not too sure which one too use , (does it really matter?) . I am UK orange EE carrier . I've attached my phones details. Can anyone assist me further please , I am hopeless lol . Thank you if you've read this far.
Click to expand...
Click to collapse
if your power button is screwed up it's going to be pretty hard to get into the bootloader and recovery. I don't know of any RUU for your carrier (doesn't mean it don't exist just means I don't know about it)
Rsdhillon said:
Okay guys I've kinda messed up my phone. I'm gunna try and keep this brief , but I need to relock and unroot my phone mainly for warranty purposes. My phone is In a reboot loop, i turn it on and it stays on for about a minute but then it turns off by itself (might be to do with a sunken in lock button I'm not sure). I want to send it back to htc so that they can sort out the lock button, but as it is rooted and unlocked , and simply not working i think my warranty is void.
I've watched various you tube videos and want to use an RUU to restore it , but I'm not too sure which one too use , (does it really matter?) . I am UK orange EE carrier . I've attached my phones details. Can anyone assist me further please , I am hopeless lol . Thank you if you've read this far.
Click to expand...
Click to collapse
anyway, forget the warranty even if you ruu the phone. the phone must be locked (not relocked) and tampered flag removed for the warranty to be valid. Setting the bootloader back to locked and removing the tampered flag require s-off, which will be impossible to achieve with a power button stuck (if this is really the case)
If you really think it's that you're better off getting some tiny jewlers screwdrivers and see if you can pop it back up because otherwise your warranty is void
Sent from my HTC One using XDA Premium 4 mobile app
clsA said:
if your power button is screwed up it's going to be pretty hard to get into the bootloader and recovery. I don't know of any RUU for your carrier (doesn't mean it don't exist just means I don't know about it)
Click to expand...
Click to collapse
That's the thing I'm not sure whether my phone constantly rebooting is a hardware problem or a software one. Also say if I was to use an RUU that wasn't 100% like what I needed what would be the risks ?
alray said:
anyway, forget the warranty even if you ruu the phone. the phone must be locked (not relocked) and tampered flag removed for the warranty to be valid. Setting the bootloader back to locked and removing the tampered flag require s-off, which will be impossible to achieve with a power button stuck (if this is really the case)
Click to expand...
Click to collapse
Say I was to send my phone to HTC in its current state do you think they'd send it back or charge me for the repair ?
Also when I hold down the power and volume buttons I can enter the boot loader and use it normally, I'm beginning to think that I don't have a hardware problem at all. Once in the boot loader it all works fine , is there anyway I can do a system restore to set back to default (I know it'll still be rooted) . But I would just like to get my phone functional again.
I'm using TWRP and believe there is a backup file on my phone. But the whole using a backup to restore always confused me.
Say hypothetical I have no button problem at all what would you do ?
Rsdhillon said:
Say I was to send my phone to HTC in its current state do you think they'd send it back or charge me for the repair ?
Also when I hold down the power and volume buttons I can enter the boot loader and use it normally, I'm beginning to think that I don't have a hardware problem at all. Once in the boot loader it all works fine , is there anyway I can do a system restore to set back to default (I know it'll still be rooted) . But I would just like to get my phone functional again.
I'm using TWRP and believe there is a backup file on my phone. But the whole using a backup to restore always confused me.
Say hypothetical I have no button problem at all what would you do ?
Click to expand...
Click to collapse
From the way you explained your first post it sounded like it was bootlooping even in bootloader mode.
If the bootloader is ok, then put TWRP recovery 2.6.3.3 on your phone, push this to your phone sd card and flash it in recovery, during install, select wipe data, flash stock recovery but don't flash stock radio.
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
However, with TAMPERED and UNLOCKED in your bootloader, HTC will charge you for any repairs, the only way you can get rid of those flags is to S-OFF.
Seanie280672 said:
From the way you explained your first post it sounded like it was bootlooping even in bootloader mode.
If the bootloader is ok, then put TWRP recovery 2.6.3.3 on your phone, push this to your phone sd card and flash it in recovery, during install, select wipe data, flash stock recovery but don't flash stock radio.
However, with TAMPERED and UNLOCKED in your bootloader, HTC will charge you for any repairs, the only way you can get rid of those flags is to S-OFF.
Click to expand...
Click to collapse
Thanks for that so that will get me to exactly how I had the phone when it came out the box , but just unlocked and tampered.
Does it have to be that version of twrp?
One thing that always confused me was the wipe data , doesn't that remove everything on the phone ? But does it not matter as we're pushing it onto the phone?
Is the link you posted for an RUU?
Rsdhillon said:
Thanks for that so that will get me to exactly how I had the phone when it came out the box , but just unlocked and tampered.
Does it have to be that version of twrp?
One thing that always confused me was the wipe data , doesn't that remove everything on the phone ? But does it not matter as we're pushing it onto the phone?
Is the link you posted for an RUU?
Click to expand...
Click to collapse
first you mention TWRP 2.6.3.0 update it to 2.6.3.3
if you have a TWRP backup restore it
if you use the guru reset you flash it from twrp
i've got TWRP 2.6.3.3. And i can use it perfectly fine , is it just a case of using the guru reset file to get me back to stock. im abit unsure on how to do this, do i put the zip file onto the phone and then run it in twrp?
Also guys how can i get the zip file onto the phone seeing as using the USB isn't working. Do i need to push it onto the phone? if so how?
I'm using TWRP and believe there is a backup file on my phone. But the whole using a backup to restore always confused me.
Click to expand...
Click to collapse
what happened to the backup option ?
Rsdhillon said:
i've got TWRP 2.6.3.3. And i can use it perfectly fine , is it just a case of using the guru reset file to get me back to stock. im abit unsure on how to do this, do i put the zip file onto the phone and then run it in twrp?
Click to expand...
Click to collapse
The Guru Reset is very simple .. it's a rom you install in TWRP
theirs even a video of it here >> http://www.htc1guru.com/downloads/stock-rom-downloads/
clsA said:
what happened to the backup option ?
The Guru Reset is very simple .. it's a rom you install in TWRP
theirs even a video of it here >>
I could do the backup option yeah, but I do want to unroot it and have it how it was new , mainly for OTA, thanks for the link ill check it out. I'm just worried ill mess up my phone even more, i dont have a lot of experience with androids.
I checked the video , and the guy already had the zip phone on his phones's memory , seeing as i cant use a USB to transfer it how would i get it on there?
Click to expand...
Click to collapse
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Welcome to the club!
necroside007 said:
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Click to expand...
Click to collapse
Why in the world would you relock the bootloader? Against commonsense it would seem. Also, there are threads on here dealing with the update and warning against relocking the boot loader. Those threads also describe efforts to recover from the situation.
wtherrell said:
Why in the world would you relock the bootloader? Against commonsense it would seem. Also, there are threads on here dealing with the update and warning against relocking the boot loader. Those threads also describe efforts to recover from the situation.
Click to expand...
Click to collapse
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
necroside007 said:
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Click to expand...
Click to collapse
freeman_g said:
Welcome to the club!
Click to expand...
Click to collapse
AndrewZorn said:
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
Click to expand...
Click to collapse
If you want to update to the newest OTA you dont need to lock the bootloader back up. The bootloader can remained unlocked when doing this. Its been posted all over XDA about not having to do this. The only time you may want to relock the bootloader is when selling it to someone or trading it in. Thats it.
AndrewZorn said:
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3053497.
Well...I'm not browsing the XDA every day, i only come here for solutions for my problems....
wtherrell said:
http://forum.xda-developers.com/showthread.php?t=3053497.
Click to expand...
Click to collapse
Yeah, posted this morning. What a warning to everyone who did this before.
And saying not to do something that plenty of people want to do (like, returning to stock) isn't very significant.
necroside007 said:
Well...I'm not browsing the XDA every day, i only come here for solutions for my problems....
Click to expand...
Click to collapse
well not to come off rude but number one rule for xda before u post is search, and as you can tell there are multiple threads on this exact same topic.
---------- Post added at 10:56 AM ---------- Previous post was at 10:51 AM ----------
AndrewZorn said:
Yeah, posted this morning. What a warning to everyone who did this before.
And saying not to do something that plenty of people want to do (like, returning to stock) isn't very significant.
Click to expand...
Click to collapse
returning to stock and relocking the bootloader dont go together. You can return to stock and not lock the bootloader. Locking the bootloader has nothing to do with returning a device back to stock. It returns the device back to factory state if u lock it back up. Locking the device back up only should be used for selling the device, or returning the device for repairs. not for taking a ota.
the_rooter said:
Locking the bootloader has nothing to do with returning a device back to stock. It returns the device back to factory state if u lock it back up. Locking the device back up only should be used for selling the device, or returning the device for repairs. not for taking a ota.
Click to expand...
Click to collapse
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
AndrewZorn said:
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
Click to expand...
Click to collapse
There is no downside to a unlocked bootloader. If i remember correctly a locked bootloader is only for oem to protect for warranty issues nothing to do with security that your describing. A locked bootloader or unlocked bootloader tells the oem that this device was unlocked or locked and will tell the consumer (us) that the warranty was void. Number one rule when taking a device back to OEM for repair is return to stock and lock device like I stated above. Security issues has nothing to do with the bootloader. From my understanding its just for the OEM warranty purposes Only!
Edit: what u described above is the same thing I described. Only need to lock device back up for warranty purposes or reselling. Thats it.
AndrewZorn said:
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
Click to expand...
Click to collapse
I posted the warning because people are not being careful. They are locking the bootloader without even checking it works. I've edited the post to say that. But if you're the sort of person that will be flashiogn a lot, a locked bootloader is not a good thing to have now because if you break recovery and cannot boot your device, you are at present - completely screwed. If you want to be stock, that shouldn't be an issue. Just be careful is all we're saying. ...and I cannot help it if my warning comes after some people have made this mistake. If no one made the mistake, I wouldn't have needed to post a warning. Can of peanuts "May contain nuts"... You know, because you know someone somewhere who was allergic to nuts, ate the nuts.
rootSU said:
I posted the warning because people are not being careful. They are locking the bootloader without even checking it works. I've edited the post to say that. But if you're the sort of person that will be flashiogn a lot, a locked bootloader is not a good thing to have now because if you break recovery and cannot boot your device, you are at present - completely screwed. If you want to be stock, that shouldn't be an issue. Just be careful is all we're saying. ...and I cannot help it if my warning comes after some people have made this mistake. If no one made the mistake, I wouldn't have needed to post a warning. Can of peanuts "May contain nuts"... You know, because you know someone somewhere who was allergic to nuts, ate the nuts.
Click to expand...
Click to collapse
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
the_rooter said:
There is no downside to a unlocked bootloader. If i remember correctly a locked bootloader is only for oem to protect for warranty issues nothing to do with security that your describing. A locked bootloader or unlocked bootloader tells the oem that this device was unlocked or locked and will tell the consumer (us) that the warranty was void. Number one rule when taking a device back to OEM for repair is return to stock and lock device like I stated above. Security issues has nothing to do with the bootloader. From my understanding its just for the OEM warranty purposes Only!
Edit: what u described above is the same thing I described. Only need to lock device back up for warranty purposes or reselling. Thats it.
Click to expand...
Click to collapse
I thought that an unlocked bootloader allowed someone without 'normal' access to the files on your phone. That's why the bootloader lock/unlock wipes the device.
You're still completely missing my point with the warranty thing. Suppose my phone's unlocked and my screen breaks. Or my USB port stops working. That big unlocked logo under the Google is going to make getting a replacement really difficult.
By saying there's NO downside to unlocking the bootloader for daily use is absurd. I wanted to go back to as-shipped state for daily use, and locked bootloader is part of that. That's a reasonable goal. I don't care if there's something about the bootloader unlocked that you find valuable. I got tired of the tinkering and decided I just wanted my Nexus 6 to be back the way it was - completely.
AndrewZorn said:
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
Click to expand...
Click to collapse
If guides don't say that at the moment, they definitely should now. I'll look at ours here and ask the OP's to update.
AndrewZorn said:
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
I thought that an unlocked bootloader allowed someone without 'normal' access to the files on your phone. That's why the bootloader lock/unlock wipes the device.
You're still completely missing my point with the warranty thing. Suppose my phone's unlocked and my screen breaks. Or my USB port stops working. That big unlocked logo under the Google is going to make getting a replacement really difficult.
By saying there's NO downside to unlocking the bootloader for daily use is absurd. I wanted to go back to as-shipped state for daily use, and locked bootloader is part of that. That's a reasonable goal.
Click to expand...
Click to collapse
Root access is for the special files. and also i had the same issues u mentioned above and i always found a way to return a device to stock.
1) broken screen- repaired myself
2) broken usb port - repaired myself
I only take in for warranties if it has to do with something that I cant fix myself. This is a risk that all users take in this hobby.
the_rooter said:
Root access is for the special files. and also i had the same issues u mentioned above and i always found a way to return a device to stock.
1) broken screen- repaired myself
2) broken usb port - repaired myself
I only take in for warranties if it has to do with something that I cant fix myself. This is a risk that all users take in this hobby.
Click to expand...
Click to collapse
Alright, so how do I return mine to stock?
Your self-repair solutions are laughable. You're completely missing the point. I'm done arguing this.
AndrewZorn said:
Alright, so how do I return mine to stock?
Your self-repair solutions are laughable. You're completely missing the point. I'm done arguing this.
Click to expand...
Click to collapse
its not laughable. unless u buy an extended warranty the warranty is up after a year so you would have to figure the work yourself. If you are in the boat where u locked it back up and took the ota and bootlooping or whatever. your stuck till there is a solution. if u want to return to stock . Just return to stock but dont lock the bootloader back up, and flash. its that simple.
Edit: we are not arguing. Its just i have my way on repairs and you have yours. its a debate i guess
Edit: this issue has been brought up and is being researched. i was talking about the returning to stock for repairs dont try and put words in my mouth saying i know a fix.
SO, I need a way to root my H/K M8 W/O having to unlock the bootloader.
The reason I say that is that when I attempt to Unlock the bootloader & S-Off with HTCDev, It won't read the PWR button being pressed when I try to select Yes (PWR Button works on everyhtin, except hboot)
So, is there anyway for me to root the phone without needing htcdev?
xBr4v3x said:
SO, I need a way to root my H/K M8 W/O having to unlock the bootloader.
The reason I say that is that when I attempt to Unlock the bootloader & S-Off with HTCDev, It won't read the PWR button being pressed when I try to select Yes (PWR Button works on everyhtin, except hboot)
So, is there anyway for me to root the phone without needing htcdev?
Click to expand...
Click to collapse
Is it a hardware issue? Have you ever flashed any firmware on this, or just the updates? Try to reset the device and try again. As far as I know, you need to unlock the bootloader to change the system, even root.
If the reset does not work, you can always try the sd card method to update the device firmware (RUU) and see if that helps.
If all else fails, take it to sprint and tell them the power button continues to "randomly" fail, if you are worried about their inquiry as to why it does not work in hboot. Or you can say you wanted to reset it. Assuming it might still be under warranty. Or a covered insurance claim.
dopy25 said:
Is it a hardware issue? Have you ever flashed any firmware on this, or just the updates? Try to reset the device and try again. As far as I know, you need to unlock the bootloader to change the system, even root.
If the reset does not work, you can always try the sd card method to update the device firmware (RUU) and see if that helps.
If all else fails, take it to sprint and tell them the power button continues to "randomly" fail, if you are worried about their inquiry as to why it does not work in hboot. Or you can say you wanted to reset it. Assuming it might still be under warranty. Or a covered insurance claim.
Click to expand...
Click to collapse
The Power button works otherwise, just not in hboot. If I long hold press it for 10-15 seconds, it will turn it off, but it won't read it as single press while in hboot at all. The volume button works in hboot, just just the power button.
So, It's a fully functional phone, just won't read power button single press in hboot.
I'd take it to sprint, but I got it off craigslist for a ps3 that had a broken hdmi (The M8 had the charging port problem, so I got it that cheap to fix the charging port then was gonn unlock bl, root, s-off, etc and use it for Vainglory instead of my Droid Turbo, and use it for sprint later on when I later dislike T-Mobile, if ever. lol)
xBr4v3x said:
The Power button works otherwise, just not in hboot. If I long hold press it for 10-15 seconds, it will turn it off, but it won't read it as single press while in hboot at all. The volume button works in hboot, just just the power button.
So, It's a fully functional phone, just won't read power button single press in hboot.
I'd take it to sprint, but I got it off craigslist for a ps3 that had a broken hdmi (The M8 had the charging port problem, so I got it that cheap to fix the charging port then was gonn unlock bl, root, s-off, etc and use it for Vainglory instead of my Droid Turbo, and use it for sprint later on when I later dislike T-Mobile, if ever. lol)
Click to expand...
Click to collapse
So it's not under warranty. Lol. Ok.
Try to RUU the original, perhaps someone else unlocked it and flashed something. You never know. I would definitely try to latest RUU for that version, then try again. Maybe someone else knows a keyboard adb command to automate this?
Also, I think there is a way to root without twrp, but it would be old school. At that point you can install sunshine (maybe even before to force it to root, I think towel root is temp, for sunshine) and it will unlock the BL and give you S-Off.
dopy25 said:
So it's not under warranty. Lol. Ok.
Try to RUU the original, perhaps someone else unlocked it and flashed something. You never know. I would definitely try to latest RUU for that version, then try again. Maybe someone else knows a keyboard adb command to automate this?
Also, I think there is a way to root without twrp, but it would be old school. At that point you can install sunshine (maybe even before to force it to root, I think towel root is temp, for sunshine) and it will unlock the BL and give you S-Off.
Click to expand...
Click to collapse
I ended up getting in touch with jcase and he helped me force it to root and unlock with kingroot and sunshine, took a while since it kept force closing sunshine and I had to re-root each boot, but it looks like I have it working now. Root seems to stay on reboot after messing with it, finally got TWRP installed, now gonna see how flashing goes for roms and sim-unlock.
xBr4v3x said:
I ended up getting in touch with jcase and he helped me force it to root and unlock with kingroot and sunshine, took a while since it kept force closing sunshine and I had to re-root each boot, but it looks like I have it working now. Root seems to stay on reboot after messing with it, finally got TWRP installed, now gonna see how flashing goes for roms and sim-unlock.
Click to expand...
Click to collapse
Glad to hear you got it working!
dopy25 said:
Glad to hear you got it working!
Click to expand...
Click to collapse
If I wasn't active on the Droid Turbo thread, I would prolly be sitting on a half-way useless M8 haha.
I'm also glad that TWRP evolved into what it is now so I don't have to rely on using Power button out of OS.
I still prefer the old CWM though *sigh*