Related
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
UPDATE
Ok, I figured out how to avoid the RUU 155 error. It seems that HTC for some dumb reason, although for a unlocked developer edition, we still have to lock the bootloader to utilize the RUU. Here are the steps I have done.
Although it is straight forward and easy to do, issues could always arise. I do not take any responsibility if things go wrong. Educate yourself first before attempting anything. If you do not know what you are doing, then don't do it.
Before Starting.
Make sure you have the latest HTC Drivers. You can use hasoon2000 HTC All-In-One Toolkit to complete that. That can be found at HTC One All-In-One Toolkit
Get the appropriate RUU from HTC Dev
1. Lock your bootloader through by booting into hoot and then going into fastboot and issuing the command fasboot oem lock.
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Notice, this will delete all of the files on the system so do this on your own cognition
4. Let the RUU do its thing. If you get an error during the process, such as 152, simply try again. I had it happen once. The phone was stuck on the black HTC screen with four triangles with exclamation points in each corner. If this happens you will not be able to reboot your phone. Simply relaunch RUU and it should reinstall it. If you get error 155 again, then you have not re-locked your bootloader.
3.Once you have successfully reinstalled the rom, you have to register with the HTC Dev to re-unlock your bootloader if that is what you want. The easiest to do this I found was by using the HTC One All-In-One Toolkit. It is a great tool and will help you with majority of things that I have mentioned above, including locking your bootloader. Follow the steps on the toolkit and you'll be all set. The Toolkit can be found here HTC One All-In-One Toolkit
If you found this helpful, click thanks. Also hit thanks to hasoon2000 for creating the toolkit.
Gotta re lock your bootloader
fastboot oem lock
I got relock it even though it came unlocked? How would I unlock it again since I don't have the tokens from HTC development, or is the ruu gonna do that by itself.
Sent from my HTC One using Tapatalk 2
I was having same issues as OP. After using the lock command, the update got longer. The black HTC screen even got as far as a progress bar. Well I now got ERROR 152 saying I should get the correct RUU. I am sure I have the right one, because there is only ONE developer edition RUU file from htcdev.com
Problem now is, I have the black HTC screen with warning signs on each corner.
One thing I saw on a video is you are supposed to restore to the same version? I had updated OTA Z(1.29.1540.16) to the latest which I cant get an RUU for. The RUU available is 1.29.1540.3 no other available. What do I do now? HTC One Dev Edition stuck on black screen with warning signs on all corners.
All I can see now is a scren that says:
***TAMPERED***
***RELOCKED***
bunch of numbers and letters in green and
RUU in orange
schn1tt3r said:
I was having same issues as OP. After using the lock command, the update got longer. The black HTC screen even got as far as a progress bar. Well I now got ERROR 152 saying I should get the correct RUU. I am sure I have the right one, because there is only ONE developer edition RUU file from htcdev.com
Problem now is, I have the black HTC screen with warning signs on each corner.
One thing I saw on a video is you are supposed to restore to the same version? I had updated OTA to the latest which I cant get an RUU for. What do I do now? HTC One Dev Edition stuck on black screen with warning signs on all corners.
Click to expand...
Click to collapse
When I was doing it, the first time I got the 152 error. I simply just redid it and it accepted it on the second try. Trying relaunching RUU that you have and try the install again. That's at least how it worked with me.
Bosnazmaj said:
When I was doing it, the first time I got the 152 error. I simply just redid it and it accepted it on the second try. Trying relaunching RUU that you have and try the install again. That's at least how it worked with me.
Click to expand...
Click to collapse
Did you get that black HTC screen with warning signs on each corner? I am re-running the RUU, hope it works or I just lost $650.
EDIT: You used RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe right? Were you already OTA updated? I wonder why htcdev web says BrightstarUS for the dev edition instead of something else...
EDIT2: Its on that black screen with loading thing again... still exclamation marks on every corner... hope this works or else it won't be a nice first experience with Android coming from iOS lol and I've jailbroken and tinkered on those devices for so long.
---------- Post added at 08:31 PM ---------- Previous post was at 08:21 PM ----------
Yeah 2nd attempt the same error 152. I just lost $650 right?
The green bar goes all the way to the end, it sends it all, but it doesnt reboot. It just gets error. What else can I try? Device isnt even 3 days old.
Did it a third time, after Updating Radio, thats where the error appears.
schn1tt3r said:
Did you get that black HTC screen with warning signs on each corner? I am re-running the RUU, hope it works or I just lost $650.
EDIT: You used RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe right? Were you already OTA updated? I wonder why htcdev web says BrightstarUS for the dev edition instead of something else...
EDIT2: Its on that black screen with loading thing again... still exclamation marks on every corner... hope this works or else it won't be a nice first experience with Android coming from iOS lol and I've jailbroken and tinkered on those devices for so long.
---------- Post added at 08:31 PM ---------- Previous post was at 08:21 PM ----------
Yeah 2nd attempt the same error 152. I just lost $650 right?
The green bar goes all the way to the end, it sends it all, but it doesnt reboot. It just gets error. What else can I try? Device isnt even 3 days old.
Did it a third time, after Updating Radio, thats where the error appears.
Click to expand...
Click to collapse
What was the software version that it came with. Was it with the most recent one? I think 1.29.401.16 one?
Bosnazmaj said:
What was the software version that it came with. Was it with the most recent one? I think 1.29.401.16 one?
Click to expand...
Click to collapse
It came with the .3 and I did OTA to .16
The RUU you can get online from their web is only .3
===============================
Ok so... that black HTC screen accepts "fastboot" commands.
I downloaded the .ZIP version of the Developer Edition OS.
I went in command prompt, I typed
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
****GOT AN ERROR*****
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
.... so again:
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
10 minutes later
fastboot reboot
Oh my was I happy to see the white HTC Startup.
I also have same phone de it shouldnt be tamperd relocked it should be only relocked
Sent from my HTC One using xda app-developers app
I find it funny now far Computer OS's have come and yet we always have to go back to good old DOS Command Prompt to fix things.
BTW, my phone now has bootloader RELOCKED due to the fastboot oem lock command, should I send the phone back just like that or unlock bootloader before sending it back?
I guess to Unlock bootloader again, I have to follow same instructions as if it were an AT&T version right? Did you UNLOCK yours again OP?
U sending it back to HTC?
Sent from my HTC One using Tapatalk 2
Bosnazmaj said:
U sending it back to HTC?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yes, that is the reason I was doing all this restoring. I had ROOTed it to install AdAway. Ads is the only major drawback when compared to iOS (this is my first Android). When you see a gray image on my phone, there are 3 sort of water drops. Like between the touch screen and LCD.
Well, I am exchanging it actually. I like the HTC One a lot. It has a tiny gap, but I dont care about that much, the weird discoloration on the sceen, though, I do mind.
That makes sense.
Sent from my HTC One using Tapatalk 2
Bosnazmaj said:
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
UPDATE
Ok, I figured out how to avoid the RUU 155 error. It seems that HTC for some dumb reason, although for a unlocked developer edition, we still have to lock the bootloader to utilize the RUU. Here are the steps I have done.
Although it is straight forward and easy to do, issues could always arise. I do not take any responsibility if things go wrong. Educate yourself first before attempting anything. If you do not know what you are doing, then don't do it.
Before Starting.
Make sure you have the latest HTC Drivers. You can use hasoon2000 HTC All-In-One Toolkit to complete that. That can be found at HTC One All-In-One Toolkit
Get the appropriate RUU from HTC Dev
1. Lock your bootloader through by booting into hoot and then going into fastboot and issuing the command fasboot oem lock.
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Notice, this will delete all of the files on the system so do this on your own cognition
4. Let the RUU do its thing. If you get an error during the process, such as 152, simply try again. I had it happen once. The phone was stuck on the black HTC screen with four triangles with exclamation points in each corner. If this happens you will not be able to reboot your phone. Simply relaunch RUU and it should reinstall it. If you get error 155 again, then you have not re-locked your bootloader.
3.Once you have successfully reinstalled the rom, you have to register with the HTC Dev to re-unlock your bootloader if that is what you want. The easiest to do this I found was by using the HTC One All-In-One Toolkit. It is a great tool and will help you with majority of things that I have mentioned above, including locking your bootloader. Follow the steps on the toolkit and you'll be all set. The Toolkit can be found here HTC One All-In-One Toolkit
If you found this helpful, click thanks. Also hit thanks to hasoon2000 for creating the toolkit.
Click to expand...
Click to collapse
Thank you. This was very helpful.
Glad I could help
Sent from my HTC One using Tapatalk 2
schn1tt3r said:
It came with the .3 and I did OTA to .16
The RUU you can get online from their web is only .3
===============================
Ok so... that black HTC screen accepts "fastboot" commands.
I downloaded the .ZIP version of the Developer Edition OS.
I went in command prompt, I typed
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
****GOT AN ERROR*****
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
.... so again:
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
10 minutes later
fastboot reboot
Oh my was I happy to see the white HTC Startup.
Click to expand...
Click to collapse
THANK YOU MAN!!!!!!!! You just saved me. I had the same problem except I had OTA .17 and trying to flash .16. My device was all jacked up but it's back to original.
Bosnazmaj said:
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
.........
Click to expand...
Click to collapse
Bosnazmaj - thank you for this wonderful write-up & knowledge. I have a Dev edition myself. Sometime ago, I got into charging issues. Initially, assuming it to be software issues, I thought I'd run the RUU. So, like you, I too figured out that I have to lock my bootloader. Ran the RUU....long story short, found out that I have to give my phone for repairs (turned out to be a hardware issue).
So, the point I am trying to make is that, if we unlock the bootloader, certain apps (like flashlight, sound recorder etc) seems to get deleted. While this, on it's own, might not sound too alarming....the problem is, if these apps are not present, then the OTA does not & will not get applied as the OTA says that these apps have to be present. I am not sure how to unlock the bootloader without losing any apps.
Any knowledge / information on this is MOST appreciated.
Actually I used titanium backup to back those apps that disappear during root before I unlocked anything. Then once I rooted and unlocked I just restored them back with titanium and all was fine. But in reality you don't want to so an ota when you are rooted as you might loose root.
Sent from my HTC One using Tapatalk 2
Can't you re-unlock the phone using following command without going through the HTCDev website mess?
Code:
fastboot oem unlock
Just a heads up. I was able to return to stock using the RUU without locking the bootloader. It took a while to figure it out.
I went from ARHD 31 to A stock rom (m7_stock_dev_1.29.1540.16_signed_052313.zip) found on an old thread, also had to find a stock recovery that would work (i think it was the one liked in the ARHD thread) and used the revone S-off method, then applied the latest RUU from the htc dev site .and it installed and the bootloader remained unlocked.
I had to get this thing ready for someone who bought it. They asked if i could return it to stock with S-off. It was a pain in the but, but got it working
Just flashed Android RevolutionHD on my Sprint HTC One and now I'm stuck looping onto the bootloader. None of the options work and I don't know what to do. Recently bought this phone and hoping to god I didn't just brick it, have never had any problems rooting or flashing in the past so idk if it is bricked, please help.
Jay227 said:
Just flashed Android RevolutionHD on my Sprint HTC One and now I'm stuck looping onto the bootloader. None of the options work and I don't know what to do. Recently bought this phone and hoping to god I didn't just brick it, have never had any problems rooting or flashing in the past so idk if it is bricked, please help.
Click to expand...
Click to collapse
Check this thread here:
http://forum.xda-developers.com/showthread.php?t=2411137
Jay227 said:
Just flashed Android RevolutionHD on my Sprint HTC One and now I'm stuck looping onto the bootloader. None of the options work and I don't know what to do. Recently bought this phone and hoping to god I didn't just brick it, have never had any problems rooting or flashing in the past so idk if it is bricked, please help.
Click to expand...
Click to collapse
For HTC One: International GSM/LTE (UL), International GSM (U), all U.S. carriers (apart from Sprint)
Next time I would suggest you flash only Sprint Roms. You need to RUU http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app
device not found
Every time I go into adb or try to use the hasoon toolkit it tells me device not found. Bootloader is unlocked with s-on and htc drivers are installed. When I try to boot into recovery now it sits at the HTC quite brilliant screen for a few seconds then shuts down.
Just tried re-locking/re-unlocking the bootloader and was successful with that so the drivers are working and it seems to have some connection to adb.
I tried pushing a recovery through adb and it had sit for over 8 hours, went to work and let it sit trying, and still nothing happened. Adb is stuck on sending 'recovery' <7544 KB>... and saying nothing else.
Just tried it again and it worked instantly so now I have a recovery.
Problem solved, major thanks to Indirect for the assist.
Hi so basically my One M8 for Sprint is COMPLETELY BRICKED! The phone cannot be repaired as far as I know because it is not S-Off and I can only boot into boot loader.
Alright so here's the situation, I am going to setup a repair and my options are:
1. I send the phone in and they repair the phone.
2. I pay $20, ship my phone and after DIAGNOSTICS they send me a replacement phone NOT the original one.
3. I pay $30 BUT they ship me the phone first and can charge me full price if they reject my claim without my approval.
What do you guys think would be the best option? and what should I say is the reason I need the repair? Should I just say something like the speakers are not clear or the headphone jack doesn't work?
When I spoke with the rep it sounded like they are more concerned about any hardware defects rather than software but she did say any unauthorized software usage will result in denied repair.
Also, keep in mind the phone will only boot into BOOTLOADER and has the "Tampered" "Relocked" and "Security Warning" banner.
Thankyou.
YungMoola15 said:
Hi so basically my One M8 for Sprint is COMPLETELY BRICKED! The phone cannot be repaired as far as I know because it is not S-Off and I can only boot into boot loader.
Alright so here's the situation, I am going to setup a repair and my options are:
1. I send the phone in and they repair the phone.
2. I pay $20, ship my phone and after DIAGNOSTICS they send me a replacement phone NOT the original one.
3. I pay $30 BUT they ship me the phone first and can charge me full price if they reject my claim without my approval.
What do you guys think would be the best option? and what should I say is the reason I need the repair? Should I just say something like the speakers are not clear or the headphone jack doesn't work?
When I spoke with the rep it sounded like they are more concerned about any hardware defects rather than software but she did say any unauthorized software usage will result in denied repair.
Also, keep in mind the phone will only boot into BOOTLOADER and has the "Tampered" "Relocked" and "Security Warning" banner.
Thankyou.
Click to expand...
Click to collapse
If you can boot into the bootloader your m8 is NOT COMPLETELY BRICKED !..... you can try unlocking the bootloader again, reflashing a custom recovery and a rom.
He will need to pull the boot.img from the Rom since he is not s off.
Your phone is not bricked. By any chance did you do a backup before flashing a new Rom??
Sent from my HTC6525LVW using XDA Premium HD app
rider5512 said:
If you can boot into the bootloader your m8 is NOT COMPLETELY BRICKED !..... you can try unlocking the bootloader again, reflashing a custom recovery and a rom.
Click to expand...
Click to collapse
lucky_strike33 said:
He will need to pull the boot.img from the Rom since he is not s off.
Your phone is not bricked. By any chance did you do a backup before flashing a new Rom??
Sent from my HTC6525LVW using XDA Premium HD app
Click to expand...
Click to collapse
OMG You guys just gave me so much hope. If you one of you guys could please me I am willing to compensate for your time. I was an iPhone user previous to this so I am not too knowledgeable but I can definitely follow directions. I had a M7 a year ago and similar thing happened to it but I was able to fix it with the RUU but not this time.
If you guys could just look over my previous thread to give you an idea of whats going on i would much appreciate it.
http://forum.xda-developers.com/htc...-isnt-sprint-m8-factory-t2819981/post54300608
lucky_strike33 said:
He will need to pull the boot.img from the Rom since he is not s off.
Your phone is not bricked. By any chance did you do a backup before flashing a new Rom??
Sent from my HTC6525LVW using XDA Premium HD app
Click to expand...
Click to collapse
There are no backup. Please help me
YungMoola15 said:
There are no backup. Please help me
Click to expand...
Click to collapse
I believe there is a backup for you to use here : http://forum.xda-developers.com/showthread.php?t=2736048
The problem is you relocked the bootloader (as mentioned in your other post).
Have you try to get unlock_code from HTC ? I don't remember whether you can re-unlock the phone without a proper OS but worth a try.
What's your CID as I can't find it in other post.
YungMoola15 said:
There are no backup. Please help me
Click to expand...
Click to collapse
Go to this link here and find the link to the 1.54.651.10 RUU (do not do this if you updated to the most recent update that added WiFi calling or if you have a Harman/Kardon version. There are links to the HK RUU's at this same link). Follow the instructions listed at that link to run the RUU. Afterwards your phone should be working fine.
This thread here may also be useful to you.
ckpv5 said:
I believe there is a backup for you to use here : http://forum.xda-developers.com/showthread.php?t=2736048
The problem is you relocked the bootloader (as mentioned in your other post).
Have you try to get unlock_code from HTC ? I don't remember whether you can re-unlock the phone without a proper OS but worth a try.
What's your CID as I can't find it in other post.
Click to expand...
Click to collapse
Damn F, the bootloader was unlocked before and also had TWRP recovery. My dumbass unrooted it. Here is the info:
YungMoola15 said:
Damn F, the bootloader was unlocked before and also had TWRP recovery. My dumbass unrooted it. Here is the info:
Click to expand...
Click to collapse
Nothing showing
Magnum_Enforcer said:
Nothing showing
Click to expand...
Click to collapse
Magnum_Enforcer said:
Go to this link here and find the link to the 1.54.651.10 RUU (do not do this if you updated to the most recent update that added WiFi calling or if you have a Harman/Kardon version. There are links to the HK RUU's at this same link). Follow the instructions listed at that link to run the RUU. Afterwards your phone should be working fine.
This thread here may also be useful to you.
Click to expand...
Click to collapse
I am really sorry but I can't post right away because XDA hasn't approved me so I only post 5 minutes between.
Don't I have to S-off for the SD card method?
Here's the pic
YungMoola15 said:
I am really sorry but I can't post right away because XDA hasn't approved me so I only post 5 minutes between.
Don't I have to S-off for the SD card method?
Here's the pic
Click to expand...
Click to collapse
You shouldn't, no. But you can also run it from your PC. Hit the second link in my sig and scroll down to the RUU section. I have instructions posted there on how to run the RUU from your PC.
Magnum_Enforcer said:
You shouldn't, no. But you can also run it from your PC. Hit the second link in my sig and scroll down to the RUU section. I have instructions posted there on how to run the RUU from your PC.
Click to expand...
Click to collapse
Hi i am probably an idiot but is there a RUU for my phone? From the pic I uploaded do you know which ruu version I need? Since I am not S-off it has to be the exact version and the instruction you gave said:
"To run a RUU, simply download the RUU you wish to install to your PC, then connect your phone and PC via USB cable. Once connected, simply double-click the RUU file on your computer to start the installer, then follow the on-screen instructions. Normally, a RUU is run while the phone is booted to the OS but alternatively, can be run while the phone is connected to the computer via Fastboot USB mode. If your device is S-on you will need to relock your bootloader to run a RUU. Use the command "fastboot oem lock" to relock your bootloader (without quotation marks)."
But even after relocking my bootloader and using the 1.54.654.9 RUU .exe I get the error 131 on stage 1/7 Sending Signature. Please see the attached pics. BTW you don't know how much I appreciate your help and you will be compensated.
YungMoola15 said:
Hi i am probably an idiot but is there a RUU for my phone? From the pic I uploaded do you know which ruu version I need? Since I am not S-off it has to be the exact version and the instruction you gave said:
"To run a RUU, simply download the RUU you wish to install to your PC, then connect your phone and PC via USB cable. Once connected, simply double-click the RUU file on your computer to start the installer, then follow the on-screen instructions. Normally, a RUU is run while the phone is booted to the OS but alternatively, can be run while the phone is connected to the computer via Fastboot USB mode. If your device is S-on you will need to relock your bootloader to run a RUU. Use the command "fastboot oem lock" to relock your bootloader (without quotation marks)."
But even after relocking my bootloader and using the 1.54.654.9 RUU .exe I get the error 131 on stage 1/7 Sending Signature. Please see the attached pics. BTW you don't know how much I appreciate your help and you will be compensated.
Click to expand...
Click to collapse
Use the RUU for the 1.54.651.10 update as I previously mentioned. This update is newer than the current software version you have. You can upgrade while S-on, you just can't go backwards (unless you're S-off). The RUU can be found in this post along with installation instructions. Try the install method that's mentioned in the post and then if that doesn't work try the PC method. If using the PC method make sure you see "Fastboot USB" hightlighted in red above the bootloader menu screen prior to running the RUU. This means that your phone and PC are properly connected.
You may also find this guide useful.
Magnum_Enforcer said:
Use the RUU for the 1.54.651.10 update as I previously mentioned. This update is newer than the current software version you have. You can upgrade while S-on, you just can't go backwards (unless you're S-off). The RUU can be found in this post along with installation instructions. Try the install method that's mentioned in the post and then if that doesn't work try the PC method. If using the PC method make sure you see "Fastboot USB" hightlighted in red above the bootloader menu screen prior to running the RUU. This means that your phone and PC are properly connected.
You may also find this guide useful.
Click to expand...
Click to collapse
I am in the process of doing the SD Card method (Transferring the file) I will update you. Thank you so much for helping me I really appreciate it brother.
YungMoola15 said:
I am in the process of doing the SD Card method (Transferring the file) I will update you. Thank you so much for helping me I really appreciate it brother.
Click to expand...
Click to collapse
Glad to help. Use that method and disregard my instructions for using the PC method and you should be good to go.
I had to get some clarification from OMJ regarding that RUU. Just follow his instructions in his thread.
Magnum_Enforcer said:
Glad to help. Use that method and disregard my instructions for using the PC method and you should be good to go.
I had to get some clarification from OMJ regarding that RUU. Just follow his instructions in his thread.
Click to expand...
Click to collapse
DUDE YOU ARE A F$#KING LEGEND! I've had the phone for a week and finally today when I was ready to send it for warranty and list it on eBay you came to the rescue.
YungMoola15 said:
DUDE YOU ARE A F$#KING LEGEND! I've had the phone for a week and finally today when I was ready to send it for warranty and list it on eBay you came to the rescue.
Click to expand...
Click to collapse
Glad to help:good:
YungMoola15 said:
DUDE YOU ARE A F$#KING LEGEND! I've had the phone for a week and finally today when I was ready to send it for warranty and list it on eBay you came to the rescue.
Click to expand...
Click to collapse
You should have solved your problem earlier should you post this in correct device forum :silly:
Get the latest firmware RUU unlock bootloader fastboot reboot RUU make sure rename zip file to firmware.zip put in platform tools folder in sdk......once in bootloader type command fastboot oem rebootRUU .......phone will reboot with black screen and HTC logo.......type fastboot flash firmware firmware.zip let it's do it's thing....once done fastboot reboot should fix temp brick
Sent from my 831C using XDA Premium 4 mobile app
Hello there,
My HTC is not starting up since an firmware update this week (mobile phone provider: Hi/KPN in the Netherlands). I do not know which firm update it was. I have not rooted, unlocked, flashed or made any other kind of customization on my phone. After the firmware update the mobile phone restarted itself and immediately got stuck on the white screen with the text HTC One and beatsaudio. Rebooting the phone has the same results. So I tried the bootloader (HBOOT-1.57.0000) in order to use 'factory reset' and 'recovery', but both options don't do anything.
Can anyone tell me which options I have left in order to repair my HTC One by myself? I would really appreciate your help!
Greetings,
Ivo
CheerZ~NL said:
Hello there,
My HTC is not starting up since an firmware update this week (mobile phone provider: Hi/KPN in the Netherlands). I do not know which firm update it was. I have not rooted, unlocked, flashed or made any other kind of customization on my phone. After the firmware update the mobile phone restarted itself and immediately got stuck on the white screen with the text HTC One and beatsaudio. Rebooting the phone has the same results. So I tried the bootloader (HBOOT-1.57.0000) in order to use 'factory reset' and 'recovery', but both options don't do anything.
Can anyone tell me which options I have left in order to repair my HTC One by myself? I would really appreciate your help!
Greetings,
Ivo
Click to expand...
Click to collapse
is your phone still under warranty?
Do you have adb/fastboot on your computer? if yes post the output of "fastboot getvar all" except your imei and serialno
I have the same problem with a verizon htc one
Cannot find device
I installed Minimal ADB and Fastboot, but it cannot find the device while the mobile phone is switched off or in HBOOT-modus. Probably because debugging is turned off? Is there another way in which I can provide you the information you need?
I have a repair service, but than it will take three weeks before I will see my phone back. That is why I wanted to manually reinstall the software. Is that still possible?
CheerZ~NL said:
I installed Minimal ADB and Fastboot, but it cannot find the device while the mobile switched off or in HBOOT-modus. Probably because debugging is turned off? Is there another way in which I can provide you the information I need?
I have a repair service, but it will take three weeks before I will see my phone back. That is why I wanted to manually reinstall the software. Is that still possible?
Click to expand...
Click to collapse
Usb debugging is only required for adb commands while the phone is booted to Android os.
Fastboot commands should work with the bootloader in fastboot mode regardless of usb debugging. Make sure your drivers are installed correctly and the bootloader is in fastboot mode not hboot mode.
You need to provide the getvar as requested by @alray, or we don't know what software is safe to recommend for you :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
Right, Lets begin....
Originally i followed a guide to root my g6 play,that was by booting a patched twrp, and dm verity and another file beginning with Q, then flash the twrp........... all that was working except dm verity which gave a error (cant remember which one)
i have tried a different number of firmwares (motorola themselves said try jeter and alijeter - as some alijeter firmware are for my model xt1922-2)
now there was a OTA, as far as I can remember, there was 2 ota updates, they went smoothly, but still the BAD KEY message (brought on by the patched dm verity file i think)
after doing this ota, the oem unlocking button was no longer greyed out, so i tried fastboot oem lock but it gives errors about bootloader bad key and more, or invalid android image
whatever happens, i cannot relock the bootloader to remove the message, i cant flash any firmware for my model without one or two errors.......
the only thing that works, to show the bootloader is locked, is fastboot flashing_lock (as my bootloader screen shows flashing_unlocked) this shows, by doing fastboot getvar all and all that, that the bootloader is relocked....but I still have bad key error, and then have to oem unlock again to do anything.....help
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
biggary said:
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
Click to expand...
Click to collapse
Ok so let's put this out there first. I am helping you for free because I generally enjoy being a helping hand! I asked for screenshots, which we still have not gotten. I asked if bootloader was unlocked still to be sure, because I wasn't sure if you had tried to relock it. I think you did try to relock based on your post, but I had to ask twice to get that information out of you. If you truly want help, help those who want to help you help yourself.
That said, I asked for screenshots because I have never heard of a "bad key" error. The way I understood it you were seeing this error in TWRP. After a quick google search I found this image:
https://forums.lenovo.com/lnv/attachments/lnv/230/6043/1/IMG-20170528-WA0015.jpg
I assume this is the same error you see? If so, you can actually ignore it. If you don't want to ignore it, you can try going to bootloader and type this: fastboot oem fb_mode_clear
Also, you can try to see if there is a modified logo.bin for your device and flash it. You could try the G6+ logo.bin possibly:
https://forum.xda-developers.com/moto-g6/themes/bootlogo-remove-message-unlocked-t3789155
PS: I found this info with a quick google search, so I assume you didn't even bother to search?
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
I am having the same issue as you, i am trying so much that i forget about doing root and just want to lock my bootloader again ;-;
The XT1922-2 is an annoying little ****.
biggary said:
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
Click to expand...
Click to collapse
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
w4r3zgod said:
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
Click to expand...
Click to collapse
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
madbat99 said:
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
Click to expand...
Click to collapse
Yea warranty void.
biggary said:
Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
Click to expand...
Click to collapse
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
Click to expand...
Click to collapse
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
Click to expand...
Click to collapse
I found this for another g6. Use the firmware for your model and it may work.
https://forum.xda-developers.com/moto-g6/development/stock-firmware-moto-g6-t3792292/post78432631