Related
Shall we have a centralized place for discussion (or better, solutions) related to the bootloop issue happened on HTC One GPe? Apparently I'm not the only one in this situation, and having a single thread will help others to find the solution more easily.
The problems are basically having a soft bricked GPe and only bootloader is accessible. The GPe device is real, S-On, locked or relocked, with stock firmware of OS-3.58.1700.5 and HBOOT 1.54, but without a working rom.
1. flashing the GPe RUU by graffixnyc from this thread won't work because of the signature verification failure, which makes sense since it's not signed by HTC (the firmware.zip flashes through because it's signed by HTC).
2. fastboot oem unlock does not work and shows the following error:
Code:
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.543s]
finished. total time: 0.543s
3. fastboot flash unlocktoken Unlock_code.bin fails silently, i.e. the confirmation screen does not show up on device.
4. trying s-off the device is not feasible without a working rom and unlocked bootloader.
5. fastboot boot <custom_recovery>.img fails for both CWM and TWRP:
Code:
downloading 'boot.img'...
OKAY [ 1.123s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.123s
6. fastboot erase cache and factory reset does not help.
Any other options so we could have a try? @nkk71 @SaHiLzZ
Thank you for creating this thread. The same issue is happening for converted devices with relocked bootloader as well.
I'm out of options as neither fastboot oem unlock nor fastboot flash token unlock.bin are working, and without these not much to do.
SaHiLzZ said:
Thank you for creating this thread. The same issue is happening for converted devices with relocked bootloader as well.
I'm out of options as neither fastboot oem unlock nor fastboot flash token unlock.bin are working, and without these not much to do.
Click to expand...
Click to collapse
It seems like some mechanism has been changed in the latest firmware that prevents the original unlocking method.
This seems to be happening more and more. I'm in the same boat. Tried to update a GPe HTC One and got stuck.
I have contacted HTC support as stated in this thread:
http://forum.xda-developers.com/showthread.php?t=2492469&page=5
They we able to help get his up and running. Hopefully they can help me out to with out the need to pay extra charges.
I will update on the progress, but seeing as we are entering the weekend, it will probably only be next week.
I miss my phone
Thanks for the thread and the clear summary. I have exactly the same issue with my stock Gpe and am anxiously waiting for a solution.
Sent from my Nexus 7 using XDA Premium 4 mobile app
joe7wu said:
It seems like some mechanism has been changed in the latest firmware that prevents the original unlocking method.
Click to expand...
Click to collapse
Create a new unlock_code.bin file using htcdev.com. This worked for me. I tried to use a unlock_code.bin file which i used when using Sense. This older bin-file didn't work so i tried to create a new one. This worked for me and my bootloader is unlocked now.
mderksen said:
Create a new unlock_code.bin file using htcdev.com. This worked for me. I tried to use a unlock_code.bin file which i used when using Sense. This older bin-file didn't work so i tried to create a new one. This worked for me and my bootloader is unlocked now.
Click to expand...
Click to collapse
I think he is talking about the method on the device, not from HTC Dev.
On the device, using "fastboot oem unlock" or the HTC Dev method dosent work.
As stated above the first returns an error and the .bin method shows a success message, but nothing actually happens.
This is my situation anyways.
Any one with locked, not relocked bootloader having the same issue. Wonder how Google will fix this..
+1 I'm having the same problem
Edit: They should make this a sticky thread for as long as the problem exist
I am also having the same issue on my google play edition. S-On. I reflashed a stock recovery image so I could update to stock ROM. Now, I am stuck in a bootloop. I cannot reload any kind of custom recovery (I say that I can't. When I do, the phone will not boot into recovery. It just jumps to the Google screen, attempts to load the OS and then restarts). I AM able to unlock and relock using fastboot oem unlock and lock. I've attempted to reload the firmware and it seems to work (via cmd loading), but the loop process begins again. I attempted to flash a 4.3 firmware I found, but received the blue screen of nothingness when I did.
I'm lost. Possibly only solution is sending back in for repair. I just got the phone and this is annoying as heck..
alcaloide_ said:
+1 I'm having the same problem
Edit: They should make this a sticky thread for as long as the problem exist
Click to expand...
Click to collapse
Yeah, a sticky thread will help a lot. Anyway, I'm still waiting for those people who got in touch with HTC and see how it goes. A bit worried about the fact that I'm in Canada and a friend in US bought this phone for me. Not sure how the custom support will be like in my case.
So, a thought just occurred to me - i haven't updated any of my tools for fastboot since i originally unlocked the system a few months ago.
I am not currently at home, so i cannot check on this, but perhaps this will help others....
The current sdk tools version is 22.3 : http://developer.android.com/sdk/index.html
Could perhaps updating these tools help us re-unlock our phones?
If someone checks and tries this, and then the fastboot oem unlock command, let me know if it is simply a windows software thing.
OK so I emailed HTC, they told me that because the phone was issued from Google, it was Google who was in charge of the warrenty. They gave me the Google customer care number "Google’s US hardware support number: 1.855.836.3987 they are open 24/7." just in case anyone needs it.
I just got off the phone and after talking with them I got the impression that they are aware of the problem but that there is currently nothing that they can do to fix it.
It seemed as though he was hinting at a fix in the future, possibly a flashable zip, but I dont know.
Anyways he had me go into recovery mode, and do a factory reset. I didnt even know I was able to do this. Unfortunately it didn't help.
At the end we had to set up an RMA. They are sending out a phone and then I will need to return mine.
Being currently in Israel they were unable to send it here, so they are going to send it to the US, and they I will send mine back from here.
Kinda sux, I was hoping for a quick fix.
Hope this helps somebody...
AmirH said:
OK so I emailed HTC, they told me that because the phone was issued from Google, it was Google who was in charge of the warrenty. They gave me the Google customer care number "Google’s US hardware support number: 1.855.836.3987 they are open 24/7." just in case anyone needs it.
I just got off the phone and after talking with them I got the impression that they are aware of the problem but that there is currently nothing that they can do to fix it.
It seemed as though he was hinting at a fix in the future, possibly a flashable zip, but I dont know.
Anyways he had me go into recovery mode, and do a factory reset. I didnt even know I was able to do this. Unfortunately it didn't help.
At the end we had to set up an RMA. They are sending out a phone and then I will need to return mine.
Being currently in Israel they were unable to send it here, so they are going to send it to the US, and they I will send mine back from here.
Kinda sux, I was hoping for a quick fix.
Hope this helps somebody...
Click to expand...
Click to collapse
Interesting. I chatted with an HTC rep this morning and I am sending the phone to an HTC repair facility in Houston. I wish Google would just do an exchange. DId they give you a hard time? Should I just call them and ask for an exchange?
They didn't give me a hard time at all. They were actually pretty cool about it.
They tried to help me out, they saw they couldn't, so they said they would send me a new one. I even went as far as telling them that I was playing around with it trying to unlock and flash 4.4(not too specific of course), and that they should just give me a flashable zip to use because I could get it into RUU mode.
I'm not sure if it makes a difference but I bought the phone in August. So i guess the only real question is, is if you still have warranty.
AmirH said:
They didn't give me a hard time at all. They were actually pretty cool about it.
They tried to help me out, they saw they couldn't, so they said they would send me a new one. I even went as far as telling them that I was playing around with it trying to unlock and flash 4.4(not too specific of course), and that they should just give me a flashable zip to use because I could get it into RUU mode.
I'm not sure if it makes a difference but I bought the phone in August. So i guess the only real question is, is if you still have warranty.
Click to expand...
Click to collapse
Thanks! I assume it is a one year warranty? My issue is that I bought it used. I wonder if they will give me a hard time about that.
---------- Post added at 03:48 PM ---------- Previous post was at 03:34 PM ----------
AmirH said:
They didn't give me a hard time at all. They were actually pretty cool about it.
They tried to help me out, they saw they couldn't, so they said they would send me a new one. I even went as far as telling them that I was playing around with it trying to unlock and flash 4.4(not too specific of course), and that they should just give me a flashable zip to use because I could get it into RUU mode.
I'm not sure if it makes a difference but I bought the phone in August. So i guess the only real question is, is if you still have warranty.
Click to expand...
Click to collapse
Well, i just got off the phone with them. I'm glad you had more success than I! The lady said she could not identify a troubleshot and, since I did not buy from them under my account, they couldn't help me.
AmirH said:
OK so I emailed HTC, they told me that because the phone was issued from Google, it was Google who was in charge of the warrenty. They gave me the Google customer care number "Google’s US hardware support number: 1.855.836.3987 they are open 24/7." just in case anyone needs it.
I just got off the phone and after talking with them I got the impression that they are aware of the problem but that there is currently nothing that they can do to fix it.
It seemed as though he was hinting at a fix in the future, possibly a flashable zip, but I dont know.
Anyways he had me go into recovery mode, and do a factory reset. I didnt even know I was able to do this. Unfortunately it didn't help.
At the end we had to set up an RMA. They are sending out a phone and then I will need to return mine.
Being currently in Israel they were unable to send it here, so they are going to send it to the US, and they I will send mine back from here.
Kinda sux, I was hoping for a quick fix.
Click to expand...
Click to collapse
Huh. Interesting. Maybe i just need to call Google. I did try factory reset, but that didn't work. Probably best to do what you did and just ask for a new one to be sent, if they cannot resolve. I did buy it with my google account, so i might be in luck (I probably about when you did, around August).
elisaw99 said:
Huh. Interesting. Maybe i just need to call Google. I did try factory reset, but that didn't work. Probably best to do what you did and just ask for a new one to be sent, if they cannot resolve. I did buy it with my google account, so i might be in luck (I probably about when you did, around August).
Click to expand...
Click to collapse
I would give it a shot
elisaw99 said:
Huh. Interesting. Maybe i just need to call Google. I did try factory reset, but that didn't work. Probably best to do what you did and just ask for a new one to be sent, if they cannot resolve. I did buy it with my google account, so i might be in luck (I probably about when you did, around August).
Click to expand...
Click to collapse
Let us know how it goes! II will be sending mine to HTC tomorrow
I just got off of the phone with Google. Rep indicated that many have been going through this problem. They are sending out a new phone right away and I will send mine back upon receiving the new one. Bought the phone in July from Google Play Store. Great customer service!
Hello,
My 510 x64 phone received a new update from HTC.
OTA_A11_UL_K443_DESIRE_SENSE60_HTC_Europe_1.51.401.2-1.51.401.1_release_4271720d6aeagtsc88zjb1
Is a 30 Mb file that should contain some fixes.
The issue is that the phone re-boots in recovery and at 30 % of the green bar the installation fails. A red download icon shows in the middle of the screen and nothing happens.
In the past i flash some different recovery files but i returned to stock ( stock files that i found online for x64 - 16.0 MB (16,777,216 bytes) )
Can someone please advise if this could be related to my recovery image ?
mzqaddicted said:
Hello,
My 510 x64 phone received a new update from HTC.
OTA_A11_UL_K443_DESIRE_SENSE60_HTC_Europe_1.51.401.2-1.51.401.1_release_4271720d6aeagtsc88zjb1
Is a 30 Mb file that should contain some fixes.
The issue is that the phone re-boots in recovery and at 30 % of the green bar the installation fails. A red download icon shows in the middle of the screen and nothing happens.
In the past i flash some different recovery files but i returned to stock ( stock files that i found online for x64 - 16.0 MB (16,777,216 bytes) )
Can someone please advise if this could be related to my recovery image ?
Click to expand...
Click to collapse
I flashed stock recovery and update installed successfully, you can give me update file?
Uploaded the file
https://drive.google.com/file/d/0B_bbXjxfqWaeMEFjUmE1ZlhFMmM/view?usp=sharing
can you please share your stock boot & recovery files ?
mzqaddicted said:
Uploaded the file
https://drive.google.com/file/d/0B_bbXjxfqWaeMEFjUmE1ZlhFMmM/view?usp=sharing
can you please share your stock boot & recovery files ?
Click to expand...
Click to collapse
With this recovery I flashed update.
https://drive.google.com/open?id=0B3-NJk0QRfxXaG5sWDc1NG5tbzg&authuser=0
EDIT: Try this recovery, is extracted from update.
https://drive.google.com/file/d/0B3-NJk0QRfxXNzBZbFFiRk5HclE/view?usp=sharing
tried both of them and i have the same issue.
https://drive.google.com/file/d/0B_bbXjxfqWaeVXJqZFBIaTZySGc/view?usp=sharing
mzqaddicted said:
tried both of them and i have the same issue.
https://drive.google.com/file/d/0B_bbXjxfqWaeVXJqZFBIaTZySGc/view?usp=sharing
Click to expand...
Click to collapse
Lock bootloader => run this RUU => update
lucyr03 said:
Lock bootloader => run this RUU => update
Click to expand...
Click to collapse
the RUU installer doesn't work.. somehow.. after i accept the licence agreement nothing happens and the installation shield application disappears.
Thried on 2 dif computer, both W7 x64, latest drivers via HTC sync manager
updated Visual C++ Redistributable for Visual Studio 2012 Update 4
mzqaddicted said:
the RUU installer doesn't work.. somehow.. after i accept the licence agreement nothing happens and the installation shield application disappears.
Thried on 2 dif computer, both W7 x64, latest drivers via HTC sync manager
updated Visual C++ Redistributable for Visual Studio 2012 Update 4
Click to expand...
Click to collapse
Work for me, but take more time to open and you have to wait after accept license...
How i can lock bootloader? I am looking instruction and i can't find :/
Ok i find command "fastboot oem lock" lock bootloader. Now I install RUU from link on post lucyr03 but this version is Europe_1.51.401 .1. Today my phone first time find new update to version Europe_1.51.401 .2-1.51.401.2. What is a diffrent of this version?
Misarus said:
How i can lock bootloader? I am looking instruction and i can't find :/
Ok i find command "fastboot oem lock" lock bootloader. Now I install RUU from link on post lucyr03 but this version is Europe_1.51.401 .1. Today my phone first time find new update to version Europe_1.51.401 .2-1.51.401.2. What is a diffrent of this version?
Click to expand...
Click to collapse
Install RUU from my post and update with OTA.
mzqaddicted said:
Hello,
My 510 x64 phone received a new update from HTC.
OTA_A11_UL_K443_DESIRE_SENSE60_HTC_Europe_1.51.401.2-1.51.401.1_release_4271720d6aeagtsc88zjb1
Is a 30 Mb file that should contain some fixes.
The issue is that the phone re-boots in recovery and at 30 % of the green bar the installation fails. A red download icon shows in the middle of the screen and nothing happens.
In the past i flash some different recovery files but i returned to stock ( stock files that i found online for x64 - 16.0 MB (16,777,216 bytes) )
Can someone please advise if this could be related to my recovery image ?
Click to expand...
Click to collapse
I forgot you posted this already. I just received a 30MB update from Boost Mobile on the 32 bit version and it fails the same exact way yours does. I contacted HTC and Boost Mobile and it seems if it doesn't update properly we have to wait for HTC to release it in the form of a RUU, which I believe they will just wait for Lollipop and bundle this little fix in with the Lollipop update. I searched on their site to see if there was anyway we could manually update and it doesn't exist. There are only old ROMs. I tried some tricks to manually update and it failed every time. I am completely stock on the Boost Mobile RUU and I totally deleted everything before the install so there aren't any problems on my end. There is simply a problem with the way they are attempting to update our phones.
Pretty sure you cant update if unlocked and rooted. Has to be like out of the box running. I couldnt but I did update on my wifes locked/unrooted phone no problem. Took 10 minutes. Checking it out, couldnt really see much, if any, difference. 30mb is pretty small.
CSP III said:
Pretty sure you cant update if unlocked and rooted. Has to be like out of the box running. I couldnt but I did update on my wifes locked/unrooted phone no problem. Took 10 minutes. Checking it out, couldnt really see much, if any, difference. 30mb is pretty small.
Click to expand...
Click to collapse
I am on the Boost Mobile stock RUU, locked, and unrooted.
I just noticed the error message in the stock recovery:
htc/sprint_wwe_vm/htc_a11chl:4.4.2/KOT49H/373881.1:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "htc/sprint_wwe_vm/htc_a11chl:4.4.2/KOT49H/373881.2:user/release-keys"
Installation aborted.
Write host_mode:0 done
I did
adb shell
getprop ro.build.fingerprint on my phone and I got:
htc/sprint_wwe_vm/htc_a11chl:4.4.2/KOT49H/433600.1:user/release-keys
This is on the stock Boost RUU, locked, and unrooted.
There are some other items in build.prop that are different than what the update is looking for.
I am going to change them to what is in my phone and try again.
I don't expect it to work, but it can't hurt.
If it doesn't work, I'll try a stock Rom backup from this site, then try the update again.
Sounds good man. Check back in with the results, I'd like to see how it turns out for you. IMO though, I really think the update isn't worth all the hassle but I totally get it if you are/want to just get it to work. I'd probably do the same. good luck.
CSP III said:
Sounds good man. Check back in with the results, I'd like to see how it turns out for you. IMO though, I really think the update isn't worth all the hassle but I totally get it if you are/want to just get it to work. I'd probably do the same. good luck.
Click to expand...
Click to collapse
Thanks. I know it's not really worth the hassle, but I'm learning a lot by messing with it. It's not working, still. I may be wrong but I think they made a mistake with the build.prop when sending the updates to some of our phones. I think some of us just have to wait for Lollipop.
Hello!
I have unlocked my bootloader but it is almost time for me to upgrade my phone. But when I come to sell it, it probably won't go because the bootloader is unlocked, so I want to flash the original boot logo instead of the Warning screen so that the new phone operator won't know the bootloader is unlocked.
Now, everytime I have attempted this using one I have downloaded, but it says "E: downgraded security version for logo"
Then, I tried where someone extracted the stock one, but everytime I try it, it says "E:none signed image detected"
If anyone can help me get around this it would be greatly appreciated.
Thanks in advance,
Paul.
Anyone?
Sent from my Hudl 2 using XDA Free mobile app
Nobody ATM had managed to change the ulogo without any side effects.
This one came close, but is easy to screw up.
The problem is because intel uses signed partitions and with an unlocked bootloader some partitions still can't be flashed and are protected. To get around this we need the key and security version they used for the last ulogo and we don't have it.
Okay, thank you for your reply but I need to have this done within 1 month (facepalm)
Has anything come up since I last posted here?
I don't know if this would now be classed as necro-posting but I need the solution, as expected, my phone never sold so it is now my testing device.
Thanks in advance.
**Warning! This is a potentially hazardous procedure! Do not proceed unless you are willing to deal with the consequences if you do something wrong.** I am not responsible if you brick, blow up, catch on fire, or do any other damage to your phone. Do this at your own RISK! Now that I have that out of the way.
If you feel that you have the necessary skills then proceed. You don't have to wait for someone to make a No Red Text firmware zip, or flashable aboot. It is so easy to create your own no red text aboot zip, or a no-red-text firmware zip. This will work on all M9's and other HTC devices. M8, M7, etc hboot's.
You will need 7zip, and a hex editor. Just open up the firmware zip with 7zip, and extract the signed-aboot. Now open the aboot with a hex editor. In search type the first couple of words of the red text "This Build", and hit enter. That will take you to the line you need to edit to remove that annoying Red Text. On the M9 I believe it will be line 00086F2E or 0008EF3A. Once you have found the lines that appear in red on your screen after you unlocked your bootloader, navigate to the numbers on the left that coincide with the letters. Don't remove any! Type in 20,and watch the letters disappear. Do this for the entire text, and only for that text. The 20 creates a blank space that won't show on the screen. Save it, and put it back in the zip. Flash in download with fastboot. Enjoy. To make a flashable aboot take your modified aboot and android_info.txt from your device, and zip them up together. Then flash in download with fastboot.
You can also do the fake locked mod the same way. Just type in unlocked, in search, and look for the place that has locked, unlocked, and relocked together. Then do the same thing you did for the development warning to the "un" in "unlocked".
Cheers
I Truly Enjoy XDA-Developers. Com with this Fabulous HTC One M9
thanx
thanx its working
thank you.
singhshb said:
thanx its working
Click to expand...
Click to collapse
You're welcome!
daydream3r said:
thank you.
Click to expand...
Click to collapse
batinica said:
This no doubt a noob question but when you say "Just open up the firmware zip with 7zip, and extract the signed-aboot" how do I go about get the zip from my device?
Click to expand...
Click to collapse
You don't get the zip from your device. What you need to do is search for a firmware zip here on XDA and use it. You will probably find someone who has already made a no red text firmware zip and use the ABOOT from it, but where's the fun in that. You could make your own firmware zip, but that's not the purpose of this thread. Search for a thread on XDA to teach you how to make a firmware zip if you are interested in doing that as well.
Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9
help please
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
bakh1 said:
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
Click to expand...
Click to collapse
Sorry my friend but looks like hard brick if it won't power on. there's nothing you can do but jtag.
This is a dangerous thing to do and could destroy your device. You are hex editing the a boot, which is cannot be compromised in any way or you will end up with a paperweight. You see, your bootloader is no longer operational. That's why your phone won't power on. In this case, allowing somebody to do it, that had no clue what they were doing, was extremely risky and foolhardy and looks to have destroyed your device.
bakh1 said:
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
Click to expand...
Click to collapse
I'm sorry to hear that your brother made a mistake editing the ABOOT. Like @Behold_this said you are now going to have to take your phone to a repair shop that has the professional tools to restore your phone to a working condition. If you are with T-Mobile and bought the phone through them you may be able to take it to them and get it replaced. Just don't mention that you modified the ABOOT. Also, if you are a US customer and you haven't used your Uh-Oh protection you can try that. I know that Mo Versi had said rooting your phone would not void the Uh Oh protection, but I don't know about modifying the ABOOT. They're all worth a try. I wish you the best with this. There's always a risk when you modify a device like we do here on XDA. The key is to always follow directions carefully, and if you're not a 100% sure of what you are doing don't do it.
Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9
please help me
i am currently out of us and not going back soon so i gave to local repair shop here they said they cant help me because jtag can only be done on m8 not m9 something like that and my brother said give me one more try he said something about htc unbrick project what should i do please
bakh1 said:
i am currently out of us and not going back soon so i gave to local repair shop here they said they cant help me because jtag can only be done on m8 not m9 something like that and my brother said give me one more try he said something about htc unbrick project what should i do please
Click to expand...
Click to collapse
As far as I know that project was for the M7 and won't work on the M9. Besides that method required for the phone to boot to bootloader or fastboot I believe. Since your phone won't boot at all the only thing I can think to do is go through your carrier or HTC. HTC has repaired or replaced many bricked devices free, but I have heard of a few cases where they would charge. If you don't mind not telling them the complete truth about how it was bricked you could tell them it was in the process of updating when it happened. That has actually happened on the M7. This is the first time I have actually heard first hand of a M9 hard bricking. All of the other ones I have heard about were able to boot to download, htc ftm, or bootloader mode and could be recovered. You have tried to boot to htc ftm by holding the power and volume up buttons continuously?
Using XDA to unleash the power of Android in my S7 Edge, One M9, and S6 Edge Plus
jbfountain said:
**Warning! This is a potentially hazardous procedure! Do not proceed unless you are willing to deal with the consequences if you do something wrong.** I am not responsible if you brick, blow up, catch on fire, or do any other damage to your phone. Do this at your own RISK! Now that I have that out of the way.
If you feel that you have the necessary skills then proceed. You don't have to wait for someone to make a No Red Text firmware zip, or flashable aboot. It is so easy to create your own no red text aboot zip, or a no-red-text firmware zip. This will work on all M9's and other HTC devices. M8, M7, etc hboot's.
You will need 7zip, and a hex editor. Just open up the firmware zip with 7zip, and extract the signed-aboot. Now open the aboot with a hex editor. In search type the first couple of words of the red text "This Build", and hit enter. That will take you to the line you need to edit to remove that annoying Red Text. On the M9 I believe it will be line 00086F2E or 0008EF3A. Once you have found the lines that appear in red on your screen after you unlocked your bootloader, navigate to the numbers on the left that coincide with the letters. Don't remove any! Type in 20,and watch the letters disappear. Do this for the entire text, and only for that text. The 20 creates a blank space that won't show on the screen. Save it, and put it back in the zip. Flash in download with fastboot. Enjoy. To make a flashable aboot take your modified aboot and android_info.txt from your device, and zip them up together. Then flash in download with fastboot.
You can also do the fake locked mod the same way. Just type in unlocked, in search, and look for the place that has locked, unlocked, and relocked together. Then do the same thing you did for the development warning to the "un" in "unlocked".
Cheers
I Truly Enjoy XDA-Developers. Com with this Fabulous HTC One M9
Click to expand...
Click to collapse
I finally found your effort of writing this "recipe".
Thanky for sharing!
Is the "red text" referred to here the notice about the reporting software and that HTC will collect information about what your phone is doing, etc.? If so, will the procedure actually remove the software or stop it from running, or does it just get rid of the notice?
ETA: Is that reporting software an issue to worry about for battery use/privacy/whatever else reasons?
drfarmkid said:
Is the "red text" referred to here the notice about the reporting software and that HTC will collect information about what your phone is doing, etc.? If so, will the procedure actually remove the software or stop it from running, or does it just get rid of the notice?
ETA: Is that reporting software an issue to worry about for battery use/privacy/whatever else reasons?
Click to expand...
Click to collapse
The red text that appears on your phone after unlocking it doesn't have any functionallity. Some just do not want to see it. That's what this is all about. If you don't want to see it use this method. If it doesn't bother you don't do it.
Cheers
Sent from my HTC 10 using XDA Labs
Hello, firstable congratulations to everyone to made an awesome forum, page, etc...
Im from Mexico and I have a HTC one M8 Sprint and I use it on GSM band
a guy sold me with a program named teamwin this program appears when I try to install the new version
I already have the 4.4.3 android version, 6.0 sense and 2.16.651.4 sofware version
and my doubt is can I make any modd to my celphone? I guess that's sounds pretty obviously but I'm new on the topic
I remember I can modd a sony ericsson telephones (like w600) but now Im so noob on the celphone topics.
I like learn new things and I only asking for your help, maybe if you can help me I appreciate that
All the links you can give me will be readed 100% for sure.:good:
So greetings for everyone and again please help me to get this cellphone a new life :laugh:
Hold down power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons and only hold vol down. Don't let go, until you see a white screen with various info on it. This it the bootloader. If the phone simply reboots to OS or Safe Mode, you just had bad timing of the button combo. Repeat the process until you see the bootloader screen.
On the bootloader screen, does it say RELOCKED, UNLOCKED, or LOCKED near the top?
Does it say Software modified, or official?
Does it say s-off or s-on?
redpoint73 said:
Hold down power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons and only hold vol down. Don't let go, until you see a white screen with various info on it. This it the bootloader. If the phone simply reboots to OS or Safe Mode, you just had bad timing of the button combo. Repeat the process until you see the bootloader screen.
On the bootloader screen, does it say RELOCKED, UNLOCKED, or LOCKED near the top?
Does it say Software modified, or official?
Does it say s-off or s-on?
Click to expand...
Click to collapse
It says
Tampered
Unlocked
S-ON
About the OS I don't know, the phone already has SuperU app, also I don't know how it works
Erbat said:
It says
Tampered
Unlocked
S-ON
About the OS I don't know, the phone already has SuperU app, also I don't know how it works
Click to expand...
Click to collapse
You need to update the firmware, to do much of any mods (like current ROMs).
You can do so by either:
1) Finding the proper stock nandroid and stock recovery, then OTA update to latest version.
2) Relock the bootloader, and use latest Sprint RUU (will wipe the phone).
redpoint73 said:
You need to update the firmware, to do much of any mods (like current ROMs).
You can do so by either:
1) Finding the proper stock nandroid and stock recovery, then OTA update to latest version.
2) Relock the bootloader, and use latest Sprint RUU (will wipe the phone).
Click to expand...
Click to collapse
I'm a bit affraid because I don't know if after to do that my phone still works
It's sprint and I use it here in mexico with movistar so I need something else to do this proccedure? I also searching the topics you told me here in the forum
Erbat said:
I'm a bit affraid because I don't know if after to do that my phone still works
Click to expand...
Click to collapse
In your first post, you ask about doing mods. Now you are saying you are afraid to. So I have no idea what your comfort level, what you are willing to accomplish, etc.
As long as you are willing to learn, put in some time reading and understanding, and follow instructions carefully, there isn't much to be afraid of. Any mods to the phone involve some risk. But the risk of permanent damage (a true "brick") are minimal. The worst that is likely to happen, is the phone fails to boot, and you may need to troubleshoot for an hour to 2 to get it back running. But that happens to just about anyone that mods phones, at some time or other. Its just part of the game.
But in the phone's current condition, something needs to be done by you, in order to update the phone in any way; whether it be by official means (RUU or OTA) or custom ROM. Otherwise, it will be stuck on Android 4.4.3 as it is now.
Erbat said:
It's sprint and I use it here in mexico with movistar so I need something else to do this proccedure?
Click to expand...
Click to collapse
Not sure what you are asking, are you wondering if any additional hardware is needed? You will need a computer for either method I stated, plus the sync cable that came with the phone (or other charge/data cable). PC is required for Method #2.
Yes for sure Im reading the past days about the topic and the fears I guess its for my phone became to an expensive brick, but I want to do this, I sent you a PM and I read your answer sorry for do that.
And finally about the last quote, I mean the M8 its originally sprint (on the starts screen says) so I want to know if its possible make the unblock totally to use on any company of the world or the country (Mexico) above than GSM, maybe 3G or in the best way 4G
Erbat said:
And finally about the last quote, I mean the M8 its originally sprint (on the starts screen says) so I want to know if its possible make the unblock totally to use on any company of the world or the country (Mexico) above than GSM, maybe 3G or in the best way 4G
Click to expand...
Click to collapse
So it sounds like you already using the phone on Movistar, just not with 3G or 4G?
There is a mod to unlock bands, which seems to work on your Sprint CDMA version (from what I understand). But it requires s-off ($25 by sunshine app) and is a slightly more complicated mod: http://forum.xda-developers.com/htc-one-m8/general/unlock-bands-qualcomm-device-phone-t2880239
So if you are unsure about doing what I've previously described; the mod to unlock bands is definitely the next level beyond that. Mods done with s-off are more risky, and can actually brick the phone (render it permanently unusable).
Whatever you do, do NOT try to flash another carrier/region versions radio, firmware, RUU, etc. in an attempt to change the band support. You may see some recommendations to that effect. But this does NOT work on the Sprint version, and will probably BRICK your phone.
Sorry I think I don't give my idea correctly, my English is not good.
I wonder if you can make my htc have the most updated software and if it is possible to use other phone network than the GSM because since I buyed (used) has the same software, the same HTC Sense and I could only use the internet GSM mobile network
My phone is
m8_WHL PVT SHIP S-ON *Unlocked*
So I would like to write the correct idea because your help it's usefull for me
really I appreciate your help and therefore not want to lose by confusion or my bad english
then I hope this time to let me know if this is better for your
I'm trying to do my best
Erbat said:
Sorry I think I don't give my idea correctly, my English is not good.
I wonder if you can make my htc have the most updated software and if it is possible to use other phone network than the GSM because since I buyed (used) has the same software, the same HTC Sense and I could only use the internet GSM mobile network
Click to expand...
Click to collapse
Updating the software is a completely separate matter from the phone's band support (3G and LTE bands the phone is compatible with).
I already told you how to update the software, in Post #4 above.
To see if the phone will work with your carrier's 3G or LTE network, you first need to know what 3G and 4G band (or bands) they use for each. Can't really do anything without that basic info. Either research online, or call your carrier and ask them. This is something you should have done before buying the phone; as changing to the proper band support is not always possible.
redpoint73 said:
To see if the phone will work with your carrier's 3G or LTE network, you first need to know what 3G and 4G band (or bands) they use for each. Can't really do anything without that basic info. Either research online, or call your carrier and ask them. This is something you should have done before buying the phone; as changing to the proper band support is not always possible.
Click to expand...
Click to collapse
The band works on 850/1900, while 4G LTE conection use band 4 - LTE AWS frecuency of 1700 MHz and 2100 MHz.
I work today on the software ( the most important for me )
Erbat said:
The band works on 850/1900, while 4G LTE conection use band 4 - LTE AWS frecuency of 1700 MHz and 2100 MHz.
Click to expand...
Click to collapse
Sprint M8 supports 3G bands 850 and 1900.
Are you sure you entered your carrier's APN info correctly?
Did you try the SIM card in another phone, to make sure the SIM works for 3G?
redpoint73 said:
Sprint M8 supports 3G bands 850 and 1900.
Are you sure you entered your carrier's APN info correctly?
Did you try the SIM card in another phone, to make sure the SIM works for 3G?
Click to expand...
Click to collapse
yes I use the right APN settings but when I bought the guy who sold it to me also told me it was unblock for any company here in Mexico but the problem is that you could not upgrade because when the file is downloaded and is installed, the phone enters into recovery mode and can not be or I do not know if it's my mistake, you can not install at all
He say that if I upgrade or modify the phone I can lose part of the unblock of the phonel and it became unusable here in Mexico
I screwed a lot
I don't know what I did wrong on the process of re-stock the phone and now don't start.
only shows the white screen with HTC green logo.
I rememberd when I try to wipe I check all the options and "I swipe to wipe" later when the phone will be reboot
shows me a message about the superU and I install (because already has it)
I was scared and search about this and only found a way to enter on bootloader and says this
*Tampered*
*Relocked*
Well, 6 hours later I have this now:
*Tampered*
**Unlocked**
m8_WHL PVT SHIP S-ON
HBOOT-3.18.0.0000
OS-2.16.651.4
eMMC-boot 2048MB
but when I unlock the bootloader (here's the tutorial of bootloader http://www.htcdev.com/bootloader)
I see the recovery mode once but when I try to do the next step (http://forum.xda-developers.com/showthread.php?t=2755657)
I can not start the recovery mode and I don't do any of progression
Also I can see an message saying me the phone hasn't any OS file so I guess that's the reason I can make it start, only turn on and shows the same white screen with HTC logo, I can entered to Bootloader and FASTBOOT but when I select recovery the phone returns to HBOOT and when I turn off and later turn on happen the same (entered directly to HBOOT screen)
Im a bit concerned about that I hope you can teach me how
*Edited now I can enter to recovery I relocked and unlocked again and I can enter again to recovery and bootloader, please help me to put the files of OS
maybe with a SD card?
Return to stock
Hi Erbat,
first of all it would be nice to get an overview of your device and its versions, you can do this by doing the fastboot command "fastboot getvar all"
The most important version wich you already have is your OS 2.16.651.4, everything what you try to flash to your device if you want to return to stock should match this number or it will mostly fail.
So at this point forget about the Guide with official OTA updates and root access, because its for 4.16.401.10 and you should mainly focus on returning to stock without root to get new updates (easier)
I dont know how much knowledge you already have but just to mention:
Every OS with 2.16.651.4 is for your Sprint version, this means all of the files without 651 will lead in the wrong direction.
Later when you use a RUU ("official" files to return to stock firmware) or a nandroid backup (stock backup created by other users), the files and backups you will find have to match exactly to your OS Version 2.16.651.4 to work.
So at the moment you should focus on returning your device back to stock firmware and OS first, after that you can recieve official OTA updates from HTC :good:
The tutorials/threads you should focus on are mainly these two:
[GUIDE][S-ON] Restore your (European) HTC One M8 back to stock
[tutorial] How to get back on stock with TWRP Stock Nandroid Backups
Edit: You can't use your recovery, because if i understood this right you got TWRP (a custom recovery) before and might have corrupted/deleted it, simply flash the newest version of TWRP 2.8.7.0 with the fastboot command "fastboot flash recovery *NAME-OF_RECOVERY*.img"
TWRP: http://teamw.in/project/twrp2/225/
(If i got anything wrong pls correct me ^^)
KODEC.4 said:
Hi Erbat,
first of all it would be nice to get the an overview of your device and its versions, you can do this by doing the fastboot command "fastboot getvar all"
The most important version wich you already have is your OS 2.16.651.4, everything what you try to flash to your device if you want to return to stock should match this number or it will mostly fail.
So at this point forget about the Guide with official OTA updates and root access, because its for 4.16.401.10 and you should mainly focus on returning to stock without root to get new updates (easier)
I dont know how much knowledge you already have but just to mention:
Every OS with 2.16.651.4 is for your Sprint version, this means all of the files without 651 will lead in the wrong direction.
Later when you use a RUU ("official" files to return to stock firmware) or a nandroid backup (stock backup created by other users), the files and backups you will find have to match exactly to your OS Version 2.16.651.4 to work.
So at the moment you should focus on returning your device back to stock firmware and OS first, after that you can recieve official OTA updates from HTC :good:
The tutorials/threads you should focus on are mainly these two:
[GUIDE][S-ON] Restore your (European) HTC One M8 back to stock
[tutorial] How to get back on stock with TWRP Stock Nandroid Backups
Edit: You can't use your recovery, because if i understood this right you got TWRP (a custom recovery) before and might have corrupted/deleted it, simply flash the newest version of TWRP 2.8.7.0 with the fastboot command "fastboot flash recovery *NAME-OF_RECOVERY*.img"
TWRP: http://teamw.in/project/twrp2/225/
(If i got anything wrong pls correct me ^^)
Click to expand...
Click to collapse
OK I will try to do those things you've post here.
So tonight before I went to sleep the recovery says I don't have OS installed, that's so confusing because I don't know how install it again, I'm pretty noob so I (if you can do it) explain me a lot to do.
Yesterday already learn to use fastboot and the files and those things to do on the computer, I like to learn and more if is for recover my phone :laugh:
Erbat said:
OK I will try to do those things you've post here.
So tonight before I went to sleep the recovery says I don't have OS installed, that's so confusing because I don't know how install it again, I'm pretty noob so I (if you can do it) explain me a lot to do.
Yesterday already learn to use fastboot and the files and those things to do on the computer, I like to learn and more if is for recover my phone :laugh:
Click to expand...
Click to collapse
I know it looks pretty bad for a "noob" if he got no OS on his device and it won't boot anymore, but don't worry as long as you get your phone into fastboot mode you can fix everyting :fingers-crossed:
KODEC.4 said:
I know it looks pretty bad for a "noob" if he got no OS on his device and it won't boot anymore, but don't worry as long as you get your phone into fastboot mode you can fix everyting :fingers-crossed:
Click to expand...
Click to collapse
I can't do anything on cmd, my phone hasn't battery today and when I try to do fastboot getvar all say wating for your device and yesterday obviously don't say this
I need wait to 30%? I guess I have readed this before
Charge it up, restart everything (pc) and try again. You can use "fastboot devices" wich will list all devices connected in fastboot mode (ofc you must choose fastboot in bootloader menu first)
Next could be that you have HTC sync active witch might block something -> uninstall HTC sync
Otherwise you might have driver problems, if so, uninstall htc drivers and sync and reinstall HTC sync to get new drivers. -> uninstall sync only again (maybe reboot)
If all this does not work search for specific fastboot drivers for the M8 and try it with them
Erbat said:
I don't know what I did wrong on the process of re-stock the phone and now don't start.
only shows the white screen with HTC green logo.
I rememberd when I try to wipe I check all the options and "I swipe to wipe" later when the phone will be reboot
Click to expand...
Click to collapse
You should never wipe any of the partitions in the TWRP "Advanced" menu, unless you know exactly that they mean, and what the result will be (those options are called "Advanced" for good reason!). Even if the phone was properly working before, what you did was to wipe the OS (system partition) and make it stop working!
Further, you wiped any backup files and personal data that may have been on internal storage or the removable SD.
Simple rule when modding the phone: Do not experiment or make up your own solutions (will almost always fail and possibly make matter worse); and only do exactly what is directed to you from the proper guides, reputable "helpers", etc.
---------- Post added at 10:30 AM ---------- Previous post was at 10:27 AM ----------
Erbat said:
I screwed a lot
I don't know what I did wrong on the process of re-stock the phone and now don't start.
Click to expand...
Click to collapse
Can't help you, if you don't tell us exactly what you did: step by step, in specific detail, with links to the files you are trying to use, exact file names, etc.
If you don't tell us what you did, we can't see what you did wrong.
---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------
Erbat said:
I see the recovery mode once but when I try to do the next step (http://forum.xda-developers.com/showthread.php?t=2755657)
Click to expand...
Click to collapse
This guide has nothing to do with returning to stock, and is not for your version of the M8.
Nothing good can come of this; for what you are trying to do.
If you didn't know what you were doing, you should have stopped and asked. Learning and reading is good (and I applaud the effort), but don't do anything unless you are sure about it. In your case particular (due to your lack of knowledge/experience) I'd recommend not do anything unless we specifically direct you to. You seem to be going down the wrong roads, and just want to make sure we mitigate that now.
---------- Post added at 10:39 AM ---------- Previous post was at 10:32 AM ----------
Erbat said:
I can't do anything on cmd, my phone hasn't battery today and when I try to do fastboot getvar all say wating for your device and yesterday obviously don't say this
I need wait to 30%? I guess I have readed this before
Click to expand...
Click to collapse
The phone needs to be powered on, and in bootloader-fastboot mode for any fastboot commands to work.
Charge the phone for a few hours, and try again.
We need to get fastboot working, to move forward at all.