Screen Fuzzy after GPE Conversion. - One (M7) Q&A, Help & Troubleshooting

Hello everyone,
I was following the conversion to Google Play Edition on this website
http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
After changing my modelid and cid, I typed "fastboot OEM rebootRUU" and now every time I turn on my phone I get this screen. (See attached). Even if I try to boot into recovery, this screen still appears.
I doubt there's a way to fix this but any thoughts would be helpful.
Thank you.

Due to the nature of a LCD panel that static is technically not a natural occurrence as it is on a crt panel, I suspect you flashed a bad recovery or someone's joke, try changing recoverys
Sent from my HTC One using XDA Premium 4 mobile app

MiniDolan said:
Hello everyone,
I was following the conversion to Google Play Edition on this website
http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
After changing my modelid and cid, I typed "fastboot OEM rebootRUU" and now every time I turn on my phone I get this screen. (See attached). Even if I try to boot into recovery, this screen still appears.
I doubt there's a way to fix this but any thoughts would be helpful.
Thank you.
Click to expand...
Click to collapse
How did you changed your MID? Which method did you used? It looks like you have flashed the eng hboot. in that case, the screen you see is normal, you must run the ruu to restore the hboot and then you'll get rid of that screen. This method of changing MID is NOT recommended like said in the first post of the thread you have used to do the change MID. There is now much safer and easier way to do this from custom recovery. Flashing the eng bootloader could brick your phone.
reboot your phone to that gray screen and then launch the gpe ruu.exe. Each time the ruu says "waiting for bootloader" reboot the phone manually by holding the power button. When the ruu flash is complete, your phone should work normally. Next time, don't use this method to change MID.
---------- Post added at 02:10 PM ---------- Previous post was at 01:58 PM ----------
THC Butterz said:
you flashed a bad recovery or someone's joke
Click to expand...
Click to collapse
In 99% of the cases, this screen is caused by flashing the engineering bootloader to change the MID.

alray said:
How did you changed your MID? Which method did you used? It looks like you have flashed the eng hboot. in that case, the screen you see is normal, you must run the ruu to restore the hboot and then you'll get rid of that screen. This method of changing MID is NOT recommended like said in the first post of the thread you have used to do the change MID. There is now much safer and easier way to do this from custom recovery. Flashing the eng bootloader could brick your phone.
reboot your phone to that gray screen and then launch the gpe ruu.exe. Each time the ruu says "waiting for bootloader" reboot the phone manually by holding the power button. When the ruu flash is complete, your phone should work normally. Next time, don't use this method to change MID.
---------- Post added at 02:10 PM ---------- Previous post was at 01:58 PM ----------
In 99% of the cases, this screen is caused by flashing the engineering bootloader to change the MID.
Click to expand...
Click to collapse
Thanks for the response, to change the MID, I did flash the eng hboot.
Yeah, it looks like it is normal. I tried running the ruu but my computer won't detect the phone at all. I've read that this is because I'm running Windows 8.1 and there's an issue with the drivers.
I'll have to revert to WIndows 7 and do it
Thanks!

MiniDolan said:
Thanks for the response, to change the MID, I did flash the eng hboot.
Yeah, it looks like it is normal. I tried running the ruu but my computer won't detect the phone at all. I've read that this is because I'm running Windows 8.1 and there's an issue with the drivers.
I'll have to revert to WIndows 7 and do it
Thanks!
Click to expand...
Click to collapse
yes unfortunately you can't use this method with 8.1 like warned at post 2, 434 and 439 and you should not use this method at all like warned at post #1:
MOD EDIT
Seems this guide, if not properly followed will cause a (soft)brick. Also there are more up to date guides.
[how to]change your MID without the eng bootloader
[TOOL] MID change without ENG HBOOT | Aroma GUI
In the interests of all users the guide is hidden, below.
If you wish to follow it go ahead. If you brick your handset, you were warned.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=42542785&postcount=2
http://forum.xda-developers.com/showpost.php?p=48111207&postcount=434
http://forum.xda-developers.com/showpost.php?p=48137630&postcount=439
If you don't want to downgrade your windows version, use a ubuntu live cd. You can use fastboot from ubuntu (linux) on your computer without installing the OS.
Next time you want to change MID, use this tool from a custom recovery, its easier, faster and safer: http://forum.xda-developers.com/showthread.php?t=2535365

Related

[Q] Will a Goldcard let me install any RUU?

My question is: will a goldcard let me install any other RUU with a version 2.17? Or do i need to get S-OFF so i can change my CID?
Background - First time posting here - please forgive any breaches in etiquette. I bought an HTC One 802w (China Unicom variant - CID HTCCN703) but when i opened it up I saw it doesn't have google apps - so i thought i have to root it. I unlocked the bootloader and rooted successfully (first time i've done this), then installed CWM and a mod to change blinkfeed to english language sources.
All was well until i installed a mod to give me Advance Power Menu - without reading the instructions carefully enough http://forum.xda-developers.com/showthread.php?t=2190384
Now my device won't get past a boot screen - "android" in very small letters with a moving highlight like it's made of shiny metal). I have USB debugging on and FastBoot mode on as well.
I have the stock recovery and firmware files for 1.12.1402.2, but recently upgraded to Android 4.2.2 so now my software main version is 2.17.1402.2 I've been reading like crazy about this and have created a goldcard using flashgc. My plan was to get another RUU file for another carrier - preferably not a chinese one (can't read Chinese)
I've been trying to use revone to gain S-OFF while in CWM recovery mode but to no avail so far - getting error = 1 all the time.
Goldcards only work if you have an actual SD card you can hack with a hex editor. With S-Off you can change to any CID, and you don't need to be rooted or have an unlocked bootloader to attempt an S-Off. Revone works only when your phone is booted.
What you can do now is probably flash over your current ROM with something like ARHD, get it working at least then use revone to S-Off. Then do whatever you want
ArmedandDangerous said:
Goldcards only work if you have an actual SD card you can hack with a hex editor. With S-Off you can change to any CID, and you don't need to be rooted or have an unlocked bootloader to attempt an S-Off. Revone works only when your phone is booted.
What you can do now is probably flash over your current ROM with something like ARHD, get it working at least then use revone to S-Off. Then do whatever you want
Click to expand...
Click to collapse
Hey - thanks for the quick reply. I've tried to flash the firmware to my SD card using ADB, but it failed. I suspected because the firmware is for version 1.12.1402.2 but my phone is now 2.17.1402.2. Would that cause a failure?
What I'd do is download any RUU (preferably 1.29), go S-OFF and SuperCID so I can install it without having to worry about CID and MID mismatches.
Revone's method to S-OFF: http://forum.xda-developers.com/showthread.php?t=2314582
SuperCID: http://forum.xda-developers.com/showthread.php?t=2317536
or
http://forum.xda-developers.com/showthread.php?t=2315319
The second one is much, much easier and you don't have to be booted into the phone or anything, just bootloader.
Setup ADB using this: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Make sure you have HTC Sync Manager installed on your computer for the proper drivers.
---------- Post added at 05:03 PM ---------- Previous post was at 05:02 PM ----------
au_jericho said:
Hey - thanks for the quick reply. I've tried to flash the firmware to my SD card using ADB, but it failed. I suspected because the firmware is for version 1.12.1402.2 but my phone is now 2.17.1402.2. Would that cause a failure?
Click to expand...
Click to collapse
What do you mean by tried to flash it? Did you try sideloading or pushing it in recovery? And which recovery do you have installed?
au_jericho said:
Hey - thanks for the quick reply. I've tried to flash the firmware to my SD card using ADB, but it failed. I suspected because the firmware is for version 1.12.1402.2 but my phone is now 2.17.1402.2. Would that cause a failure?
Click to expand...
Click to collapse
You can sideload a whole ROM zip through recovery, then install that from recovery itself. Once you have a working phone, proceed to S-Off, change your CID then flash a RUU if you want

[Q] HTC ONE m7 NO OS

ok, firstly yes im a noob but not a noob legend, so i have a basic understanding of what im doing.
Now i tried to Flash a Viper rom on my HTC ONE M7 with CWM and i realize that this was a horrible mistake on my part
i cant mount sdcard to put on a different rom nor anything to tht effect.
im from Jamaica and my carrier is Digicel.
im on
this is my bootloader screen
****TAMPERED ******
***** UNLOCKED****
M7_UL PVT SHIP S-ON RH
HBOOT - 1.56.0000
RADIO-4A.25.3263.21
OpenDsp-v32.120.274.0909
OS-4.19.401.11
eMMC-boot 2048MB
Feb 26, 2014. 12:32:09.0
i cant access adb
it always gives an error and says no devices found
Please guys help me get my M7 Up
Look for the all in one toolkit and adb sideload.
You May need the new drivers it has.
Sent from my HTC One_M8 using Tapatalk
Try to return the device to stock. So the first thing you want to do is install the HTC drivers on your computer. Next find the RUU (rom) for your device here: http://www.htc1guru.com/downloads/ruu-file-downloads/
Next thing is you want to boot into the bootloader menu and connect the usb. It should be in fastboot mode now. Now since you have S-On you will have to relock the bootloader before you are able to flash the RUU. I'm not 100% sure how to relock the bootloader but google is your friend. Once bootloader has been locked you need to boot the device in fastboot mode once again. once there you will have to run the following commands in command prompt.
use cd to change the directory to where you downloaded the RUU zip. ie if its on your desktop then it should be (assuming its windows):
cd C:\Users\"your Username here"\Desktop
next you want to run
fastboot oem rebootRUU
then once the htc logo pops up run
fastboot flash zip "the name of the RUU zip file".zip
The first time you run the previous command you should get an error like this:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Once you get this error run the previous command immediately. The RUU should now just flash the phone back to stock and you should be good to go!
Re: Htc one m7 no os
how do i know which RUU will work , how will i know the compatibility, my fone is unbranded so no Sprint, At&t, none o that shows when i usually turn my phone on
Nvoy said:
how do i know which RUU will work , how will i know the compatibility, my fone is unbranded so no Sprint, At&t, none o that shows when i usually turn my phone on
Click to expand...
Click to collapse
you can change the CID to 11111111(SuperCID) and MID to PN0710000, that way any RUU would work. These forums should help
http://forum.xda-developers.com/showthread.php?t=2182823
http://forum.xda-developers.com/showthread.php?t=2305490
sometimes my m7 can not be detected by my computer so giving commands to it is impossible.
then i restart my computer and its all ok.
you should try that
FAILED (remote: 12 signature verify fail)
that is the error i got when i tried flashing the ruu "RUU Zip M7 HTC Google Edition_3.06.1700.10"
Did you change your cid as in the previous post? To flash the Google play edition ROM you will need a the super cid or the Google one
Sent from my One using xda app-developers app
---------- Post added at 11:20 AM ---------- Previous post was at 11:18 AM ----------
Nvoy said:
how do i know which RUU will work , how will i know the compatibility, my fone is unbranded so no Sprint, At&t, none o that shows when i usually turn my phone on
Click to expand...
Click to collapse
Since your phone is unbranded I would go with the developer sense ROM. This might also need the cid change as well, but the developer ROM is the brightstar US one
Sent from my One using xda app-developers app
when i try to change my CID it gave me a usb error :| sigh
Nvoy said:
when i try to change my CID it gave me a usb error :| sigh
Click to expand...
Click to collapse
you are in a conundrum at the moment. In order for you to change the CID you need S-off. So that would be the first step. Find a way to get s-off then everything should just work smoothly
*****Edit*****
Don't know why i didnt mention this before, but the google play edition rom needs s-off to work which is why it didnt work. So like i mentioned before try to install the brightstar US developer RUU. Also what is your CID ATM? You might need to install an RUU specific to your CID
---------- Post added at 12:51 PM ---------- Previous post was at 12:46 PM ----------
you can get your CID by booting into fastboot and running this:
fastboot getvar cid
The biggest thing you need right now is to get back to a running rom. From there you can root, get S-off and then run any sort of rom you want. With S-on you are severely limited.
---------- Post added at 01:10 PM ---------- Previous post was at 12:51 PM ----------
on second thought lets try and get you back up and running with viper rom as that seems easier at this point. As long as your bootloader is unlocked i think we should be able to do it. Do you by any chance have a USB OTG cable? It will help immensely if you have one.
The first thing you should do is get twrp custom recovery. from here:
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.7.0.0-m7.img
next you want to flash this recovery using fastboot
so navigate using cd to where you dowloaded the file as before
then type in command line
fastboot flash recovery "NameOfRecovery".img
after this you should now have TWRP recovery installed. Next you will want to boot into recovery and if you do not have a USB OTG cable then follow the instructions in this video to load the viperrom zip file onto the phone
https://www.youtube.com/watch?v=CivvxcM1PCY
Once the file is on your phone. You will want to do a data wipe/factory reset in recovery. Now you can finally flash the rom and will hopefully get you back up and running.
Guys,
take it easy a bit, flashing RUUs, changing CIDs, Kindle Fire sideload youtube etc. is rushing things a little, especially with S-On!! ... and S-Off can wait.
especially without a "fastboot getvar all"
at OP, please start by
1- posting a "fastboot getvar all" (excluding IMEI and s/n)
2- what recovery you are running (name and version)
3- what does Windows Device Manager show (while in custom recovery) -> "Unknown Device" or "Android USB .. -> My HTC" (if it's the former then check my guide FAQ #2... disregard the guide only check the FAQ!!)
lol guess what guys, i jus got my device to accept the sideload command...i unplugged my device and plugged it back in and now it wont pick up sighhhhhhhhhhhhhh!!!!!!!!!!!!!!!!!
ok so im back in adb devices trying to push the rom, i reached as far as this command "adb push Rom.zip.zip /data/media"
but it says Permission Denied..why?
THANKS A BUNCH GUYS FOR UR HELP, I finally succeeded in doing it , i done it by sideload and nailed tht ****!!!!!!!!!!but cudnt do it without u guys insight, patience and help thanks
Not a problem. Glad to be of some help.
Sent from my One using xda app-developers app

Cannot obtain s-off after accepting 1.54.651.8 software update

Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
might be your hardware, i am soff with 651.8
Sent from my 831C using XDA Free mobile app
koolcat7 said:
Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
Click to expand...
Click to collapse
You could try it multiple times. Reboot the phone, computer, change USB ports, etc.. Who knows, maybe it'll work.
I know the M8 I got S-Off on took the 1.54.651.8 OTA before I even bothered to actually mess with it (unlock bootloader, root, and S-Off) and it was perfectly able to do all of those things.
koolcat7 said:
Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
Click to expand...
Click to collapse
If Firewater says it won't work on your device, then you can't get S-OFF for the time being. There's nothing you can do about that.
Don't flash anything above 1.54.651.8 without being S-Off
koolcat7 said:
Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
Click to expand...
Click to collapse
I'm running into the same problem and I need it badly.
If you do flash .13 without S-off you basically will have no way to flash the firmware and could be without audio from the stock music app.
Wow it's been a long night. This is a learning process for me. I've never come to a new phone so quickly so I'm getting used to the fact that development takes time and I need to be patient. I pretty much soft bricked my phone last night. Ended up deleting my system partition and had to pull some tricks to even get back into a bootable rom. I took one of the TWRP stock restores and reverted all the way back to 1.12.651.17. Then I fastboot flashed the stock recovery from 1.54.651.8 and took the OTA update so now I am completely back to stock....FEW...avoided a trip to the sprint store. I now understand that since I don't have S-OFF yet, I should flash any software versions over .8. In order to have a fully working .13, I'm sure the firmware is required as well (most likely the reason why my audio wasn't working for some of the ROMs). However, I'm still stuck with the issue in the picture below. I need to get S-OFF so I can flash the firmware 1.54.651.8, including the Hboot, Is it possible to flash an Hboot.img without being S-OFF?
#firewater is the IRC channel for the S-OFF by the way.
Also why is my radio and open dsp showing invalid-ver-info?
Anybody please help?
And something is really messed up because now my vibration won't work. No idea what is going on I just badly need s-off.
@mhuffer
So what is your current issue? It sounds like you have a working 1.54.651.8 setup, which, without S-OFF, is the most up-to-date. You might not be able to run the Harman Kardon ROM, as that may require the HK firmware, but besides that is everything working (outside of the invalid entries showing in HBOOT)?
Captain_Throwback said:
@mhuffer
So what is your current issue? It sounds like you have a working 1.54.651.8 setup, which, without S-OFF, is the most up-to-date. You might not be able to run the Harman Kardon ROM, as that may require the HK firmware, but besides that is everything working (outside of the invalid entries showing in HBOOT)?
Click to expand...
Click to collapse
Well it seems like my Hboot isn't recognizing my radios and somthing tells me the firmware is borked somehow because my vibration feedback isn't working. I am currently on 1.54.651.8, rooted, dev unlocked, fully stock. You can see from the picture my Hboot doesn't look right. My vibration was working fine yesterday but i cannot pin point when it stopped working. I'm guessing when I accidentally deleted the system partition through TWRP 2.7.0.7. I am currently running your version of TWRP (2.7.0.7). I'm also in the firewater IRC asking for help. I think my best bet would be to get s-off somehow and hboot the framework from 1.54.651.8 with unmodified hboot so I can get back to stock (if this is possible). At some point in all my confusion last night I did change my CID version to 11111111 and try to run the RUU for the HK version (.13) this might be where it all went wrong. I have my phone up and running and everything is working except for vibration and the Hboot looks out of whack.
mjhuffer said:
Well it seems like my Hboot isn't recognizing my radios and somthing tells me the firmware is borked somehow because my vibration feedback isn't working. I am currently on 1.54.651.8, rooted, dev unlocked, fully stock. You can see from the picture my Hboot doesn't look right. My vibration was working fine yesterday but i cannot pin point when it stopped working. I'm guessing when I accidentally deleted the system partition through TWRP 2.7.0.7. I am currently running your version of TWRP (2.7.0.7). I'm also in the firewater IRC asking for help. I think my best bet would be to get s-off somehow and hboot the framework from 1.54.651.8 with unmodified hboot so I can get back to stock (if this is possible). At some point in all my confusion last night I did change my CID version to 11111111 and try to run the RUU for the HK version (.13) this might be where it all went wrong. I have my phone up and running and everything is working except for vibration and the Hboot looks out of whack.
Click to expand...
Click to collapse
Well if you're not S-OFF, you couldn't have changed your CID. And if you ran the OTA to get where you are now, then you're firmware is already stock.
You can try flashing the stock firmware from the 1.54.651.8 OTA again and see if that normalizes your device.
Captain_Throwback said:
Well if you're not S-OFF, you couldn't have changed your CID. And if you ran the OTA to get where you are now, then you're firmware is already stock.
You can try flashing the stock firmware from the 1.54.651.8 OTA again and see if that normalizes your device.
Click to expand...
Click to collapse
How do I flash it without being S-off? Can I run it with S-On? I think I really just need a way to revert my Hboot to stock. I was hoping somebody had an RUU available that would just wipe everything and start from scratch.
---------- Post added at 12:56 PM ---------- Previous post was at 12:51 PM ----------
Captain_Throwback said:
Well if you're not S-OFF, you couldn't have changed your CID. And if you ran the OTA to get where you are now, then you're firmware is already stock.
You can try flashing the stock firmware from the 1.54.651.8 OTA again and see if that normalizes your device.
Click to expand...
Click to collapse
I need someway to revert my Hboot while being S-ON. I was hoping somebody that had some knowledge could make and RUU with the proper CID to revert EVERYTHING back to stock. I mean I want to start from the bottom up. I don't know if this is possible without HTC releasing anything.
mjhuffer said:
How do I flash it without being S-off? Can I run it with S-On? I think I really just need a way to revert my Hboot to stock. I was hoping somebody had an RUU available that would just wipe everything and start from scratch.
---------- Post added at 12:56 PM ---------- Previous post was at 12:51 PM ----------
I need someway to revert my Hboot while being S-ON. I was hoping somebody that had some knowledge could make and RUU with the proper CID to revert EVERYTHING back to stock. I mean I want to start from the bottom up. I don't know if this is possible without HTC releasing anything.
Click to expand...
Click to collapse
No one can make a RUU it has to be leaked from HTC.
Sent from my 831C using Tapatalk
Konfuzion said:
No one can make a RUU it has to be leaked from HTC.
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
I figured that, is there any way to create a flashable zip with signed everything except for the recovery so I can possibly push it through TWRP. You have to understand I want to try everything possibly before returning this phone to sprint. I have a feeling they will want to ship it off to HTC if the vibration doesn't work.
mjhuffer said:
I figured that, is there any way to create a flashable zip with signed everything except for the recovery so I can possibly push it through TWRP. You have to understand I want to try everything possibly before returning this phone to sprint. I have a feeling they will want to ship it off to HTC if the vibration doesn't work.
Click to expand...
Click to collapse
You don't need to be S-OFF to flash the signed firmware.zip through HBOOT, which is why I suggested it.
---------- Post added at 01:54 PM ---------- Previous post was at 01:40 PM ----------
https://www.dropbox.com/s/cm6m61o78r0poe6/firmware.zip
Relock Bootloader, then fastboot oem rebootRUU, then fastboot flash zip firmware.zip.
Then you can unlock again if you want and flash custom recovery. But you can at least see if the firmware zip gets everything working properly again.
skizzled said:
You could try it multiple times. Reboot the phone, computer, change USB ports, etc.. Who knows, maybe it'll work.
I know the M8 I got S-Off on took the 1.54.651.8 OTA before I even bothered to actually mess with it (unlock bootloader, root, and S-Off) and it was perfectly able to do all of those things.
Click to expand...
Click to collapse
I never got a message of "You are out of luck" on my failed attempts. But....
First phone took me like 3 tries. Windows 7 x64
Second phone took like 4 failed attempts Windows 8.1 x64 (same computer) (timing out with over 2 minutes of dots......) using the exact same version of firewater as previous phone.
I was not sure if it was a Windows 8 issue.
Then I tried downloading the latest firewater and it was different from what I downloaded a month ago and worked the first time.
I agree. Try multiple times. Try with phone on WIFI vs Mobile Data. SO that Data is available quickly after adb reboot.
Try rebooting computer and try even another computer another USB port. Some computers have internal "USB Hubs". Try front vs Back etc.
I was able to do it on Windows 8.1 x64. I install latest HTC Sync. Then uninstall everything but the drivers.
I also had flashed Bad Boys 1.1 (Unlocked with S-ON) to get my rooted OS instead of manually rooting it. Then Factory Reset it. Turned on WIFI then did S-OFF.
Most rooted ROMs remove a lot of baggage that might interfere with rooting.
I'm still running all stock firmware though except for Recovery.
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
koolcat7 said:
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
Click to expand...
Click to collapse
It doesn't matter how many times you try. It won't work. Read the message.
koolcat7 said:
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
Click to expand...
Click to collapse
Ouch, pretty blunt message.
You don't need S-OFF to get wifi tether. All you need is HTC Unlock and Root.
S-OFF mainly allows you to flash firmware. You can only flash complete and signed firmware without S-OFF.
And each time you do, you'll have to reflash recovery.
I believe you can install several ROMs with S-ON that support Wifi Tether.
I ran "Wifi Tether Router" from Google Play ($1.99) with S-ON (HTC Unlock/Root) before S-OFF was available.
koolcat7 said:
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
Click to expand...
Click to collapse
The Captain is right. I got on the IRC this morning and talked to the firewater guys. They didn't really say why but they were at least a good amount of help. I can't say I blame them for not releasing any information on why. I just wish I knew about bootloader exploits.
Also, I'm on windows 7 pro 64-bit. I have a laptop with win 8 64-bit, but am afraid to try on that PC due to ALL its USB ports are 3.0 (and firewater says to avoid 3.0 ports).
Captain_Throwback said:
You don't need to be S-OFF to flash the signed firmware.zip through HBOOT, which is why I suggested it.
---------- Post added at 01:54 PM ---------- Previous post was at 01:40 PM ----------
https://www.dropbox.com/s/cm6m61o78r0poe6/firmware.zip
Relock Bootloader, then fastboot oem rebootRUU, then fastboot flash zip firmware.zip.
Then you can unlock again if you want and flash custom recovery. But you can at least see if the firmware zip gets everything working properly again.
Click to expand...
Click to collapse
Does this firmware.zip possibly have the hboot and boot.img included? If not could you please make me one with it. It worked but the Hboot still says Tampered Relocked and my Radio and Open DSP say Invalid_Ver_Info and I still don't have vibration.
mjhuffer said:
Does this firmware.zip possibly have the hboot and boot.img included?
Click to expand...
Click to collapse
Yes.

Roms with Aroma Installer never work. Suggestions?

My HTC One has all the necessary prerequisites for flashing Roms. I'm not sure how to check s-off though, but I think that's the case. I can flash Roms that do not use Aroma, but if the ROM contains Aroma there is no use. They all freeze at a certain point, I believe around some part that has to do with the System. For example, Maximus HD freezes at 1% when formatting something. Any help would be appreciated. I have looked a lot for the last few days, and can't seem to find an answer.
ronii1123 said:
My HTC One has all the necessary prerequisites for flashing Roms. I'm not sure how to check s-off though, but I think that's the case. I can flash Roms that do not use Aroma, but if the ROM contains Aroma there is no use. They all freeze at a certain point, I believe around some part that has to do with the System. For example, Maximus HD freezes at 1% when formatting something. Any help would be appreciated. I have looked a lot for the last few days, and can't seem to find an answer.
Click to expand...
Click to collapse
Okay so I'm assuming that you're flashing a kk rom here. Are you on the latest recovery and also on a kk base with the latest radios and hboot already on the device? Also make sure you're flashing the right rom for you're device. What device do you have? And also send the link to the rom you're trying to flash just so I can double check that it's correct as if it's freezing at 1% then all I can think that is the problem is you're either trying to flash a kk custom rom on a jb rom without updated firmware and radios or your recovery is out of date or the 3rd reason could simply be you're trying to flash the wrong rom for your phone.
dc959 said:
Okay so I'm assuming that you're flashing a kk rom here. Are you on the latest recovery and also on a kk base with the latest radios and hboot already on the device? Also make sure you're flashing the right rom for you're device. What device do you have? And also send the link to the rom you're trying to flash just so I can double check that it's correct as if it's freezing at 1% then all I can think that is the problem is you're either trying to flash a kk custom rom on a jb rom without updated firmware and radios or your recovery is out of date or the 3rd reason could simply be you're trying to flash the wrong rom for your phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2189373
That is the rom, It's Maximus HD. My hboot is 1.54, I'm not sure if my phone has the latest radios, but I have the latest TWRP recovery. 2.8.0.2 I think? I have the HTC One M7 for AT&T., but it says HTC One UL in the same screen I found the hboot. I believe the phone was converted to the GPE edition since it says GOOGL1 on the hboot screen. (I bought this second hand)
EDIT: I just want to add that Android Revolution HD yields the same results, but at 10%. And my phone is currently on a stock build of Sens 6 4.4.3, but the rom before it was GPE.
ronii1123 said:
http://forum.xda-developers.com/showthread.php?t=2189373
That is the rom, It's Maximus HD. My hboot is 1.54, I'm not sure if my phone has the latest radios, but I have the latest TWRP recovery. 2.8.0.2 I think? I have the HTC One M7 for AT&T., but it says HTC One UL in the same screen I found the hboot. I believe the phone was converted to the GPE edition since it says GOOGL1 on the hboot screen. (I bought this second hand)
EDIT: I just want to add that Android Revolution HD yields the same results, but at 10%. And my phone is currently on a stock build of Sens 6 4.4.3, but the rom before it was GPE.
Click to expand...
Click to collapse
If you go into your bootloader you'll see under the **unlocked** message you'll see something that has the phone model and then ship and after ship it will say either s-on or s-off and for the ROM you're trying to flash you have to be s-off thankfully you're on hboot 1.54 so you can use rumrunner to gain s-off if you're not so check that
dc959 said:
If you go into your bootloader you'll see under the **unlocked** message you'll see something that has the phone model and then ship and after ship it will say either s-on or s-off and for the ROM you're trying to flash you have to be s-off thankfully you're on hboot 1.54 so you can use rumrunner to gain s-off if you're not so check that
Click to expand...
Click to collapse
Looks like I am S-Off already. This is strange. It's the only device that has reacted this way to Aroma. I will say that I decide to flash Elemental X today, and that uses Aroma. That worked no problem.
ronii1123 said:
Looks like I am S-Off already. This is strange. It's the only device that has reacted this way to Aroma. I will say that I decide to flash Elemental X today, and that uses Aroma. That worked no problem.
Click to expand...
Click to collapse
Have you checked the md5 of the ROM to make sure that it isn't just a bad download or something which you would just need to re download it again?
dc959 said:
Have you checked the md5 of the ROM to make sure that it isn't just a bad download or something which you would just need to re download it again?
Click to expand...
Click to collapse
Redownloaded, same issue. My CID says CID-GOOGL1, could that be the issue? I heard that the CID is supposed to be something like 1111111 or something like that.
After every attempt, when I restore a backup, I see the text "E: Unable to mount ' /cache' " in red
ronii1123 said:
Redownloaded, same issue. My CID says CID-GOOGL1, could that be the issue? I heard that the CID is supposed to be something like 1111111 or something like that.
Click to expand...
Click to collapse
Yea that's actually what I was just about to say haha I just had to grab the links to the CID's so you can find the one for your phone as it's a converted gpe phone not a factory one which means you simply just need to go to the link I'll post here and find the RUU that is for at&t and the CID will be listed under the download link then you just need to change it.
Link for CID: http://www.htc1guru.com/downloads/ruu-file-downloads/
Once you've found your CID listed in the link which I'll have a look myself to see if I can find it for you but you need to then go into terminal or cmd and type in:
adb reboot bootloader
adb oem writecid CWS__001
fastboot erase cache
fastboot reboot
I changed the code so that it has the correct CID for you so just type in what I've typed there and you'll be back to normal and it should all flash fine
---------- Post added at 05:00 PM ---------- Previous post was at 04:39 PM ----------
ronii1123 said:
Redownloaded, same issue. My CID says CID-GOOGL1, could that be the issue? I heard that the CID is supposed to be something like 1111111 or something like that.
After every attempt, when I restore a backup, I see the text "E: Unable to mount ' /cache' " in red
Click to expand...
Click to collapse
I always receive the red text saying it can't mount cache so don't worry it's not going to stop you from flashing that's just an issue that I have no idea what's causing it but cache is a temporary file anyway so it isn't going to affect installing a ROM well at least it hasn't for me
dc959 said:
Yea that's actually what I was just about to say haha I just had to grab the links to the CID's so you can find the one for your phone as it's a converted gpe phone not a factory one which means you simply just need to go to the link I'll post here and find the RUU that is for at&t and the CID will be listed under the download link then you just need to change it.
Link for CID: http://www.htc1guru.com/downloads/ruu-file-downloads/
Once you've found your CID listed in the link which I'll have a look myself to see if I can find it for you but you need to then go into terminal or cmd and type in:
adb reboot bootloader
adb oem writecid CWS__001
fastboot erase cache
fastboot reboot
I changed the code so that it has the correct CID for you so just type in what I've typed there and you'll be back to normal and it should all flash fine
---------- Post added at 05:00 PM ---------- Previous post was at 04:39 PM ----------
I always receive the red text saying it can't mount cache so don't worry it's not going to stop you from flashing that's just an issue that I have no idea what's causing it but cache is a temporary file anyway so it isn't going to affect installing a ROM well at least it hasn't for me
Click to expand...
Click to collapse
Alright I'll give that a shot, thanks! I'll let you know of my results.

Htc one m7 sprint stuck at Grey screen while trying to change cid

I was trying to change the cid of my m7 but after flashing some files it just stuck on this Grey screen.. the tutorial i was following said that i can use adb commands on this screen but i cant because this phone is recognised as malfunctioning now (after that adb command) in my pc with windows 10.. i don't know much abt these stuff but it would be really helpful if i can revive this phone.
If u need any info just le me know..ill post it asap.
RIPhones said:
I was trying to change the cid of my m7 but after flashing some files it just stuck on this Grey screen.. the tutorial i was following said that i can use adb commands on this screen but i cant because this phone is recognised as malfunctioning now (after that adb command) in my pc with windows 10.. i don't know much abt these stuff but it would be really helpful if i can revive this phone.
If u need any info just le me know..ill post it asap.
Click to expand...
Click to collapse
Flashing files to change CID? CID can be changed using "fastboot oem writecid <your_desired_cid>", no file flashing required.
Are you talking about MID change? Hope you did not followed the crappy guide making users flash an eng bootloader?
And why are you trying to change your CID (or MID) on a Sprint phone?
alray said:
Flashing files to change CID? CID can be changed using "fastboot oem writecid <your_desired_cid>", no file flashing required.
Are you talking about MID change? Hope you did not followed the crappy guide making users flash an eng bootloader?
And why are you trying to change your CID (or MID) on a Sprint phone?
Click to expand...
Click to collapse
yes i was following that "crappy guide" as i was trying to change mid because i was unable to flash Stock RUU using adb ..it was showing some error.
PS. i don't have any recovery installed.
RIPhones said:
yes i was following that "crappy guide" as i was trying to change mid because i was unable to flash Stock RUU using adb ..it was showing some error.
PS. i don't have any recovery installed.
Click to expand...
Click to collapse
There are much more up-to-date and safer guides to change your MID. Did you read to moderator comment (in red) before reading the guide? The last pages of the thread? The guide you just followed made you flash an engineering bootloader made for the Droid DNA, not even designed for the M7 (hence the gray screen). This bootloader version is 1.39 which mean it will not allow you to connect (use fastboot) with any Windows 8 or 10 computer. So from now you must use a Win 7, XP, Linux or Mac machine to be able to use fastboot commands.
If your goal was to restore the original Sprint MID and CID on your phone that's ok. If you are trying to change your MID/CID to something else than Sprint, this is totally useless since only Sprint RUU will flash correctly on a Sprint phone (no conversion possible for this variant).
What was the error when flashing the RUU?
The first step out of this will be to flash twrp recovery (the wls version) so you can revert your MID back to Sprint and flash an old sprint RUU or firmware.zip.
alray said:
There are much more up-to-date and safer guides to change your MID. Did you read to moderator comment (in red) before reading the guide? The last pages of the thread? The guide you just followed made you flash an engineering bootloader made for the Droid DNA, not even designed for the M7 (hence the gray screen). This bootloader version is 1.39 which mean it will not allow you to connect (use fastboot) with any Windows 8 or 10 computer. So from now you must use a Win 7, XP, Linux or Mac machine to be able to use fastboot commands.
If your goal was to restore the original Sprint MID and CID on your phone that's ok. If you are trying to change your MID/CID to something else than Sprint, this is totally useless since only Sprint RUU will flash correctly on a Sprint phone (no conversion possible for this variant).
What was the error when flashing the RUU?
The first step out of this will be to flash twrp recovery (the wls version) so you can revert your MID back to Sprint and flash an old sprint RUU or firmware.zip.
Click to expand...
Click to collapse
i can't remember that error as it was done a week ago but when i was trying to flash twrp it was just was failing. ill get back to u once i install ubuntu on my system and try with that.. but what should i do first after connecting it to a linux machine? should i try to install recovery ?? please help me out here.
RIPhones said:
i can't remember that error as it was done a week ago but when i was trying to flash twrp it was just was failing. ill get back to u once i install ubuntu on my system and try with that.. but what should i do first after connecting it to a linux machine? should i try to install recovery ?? please help me out here.
Click to expand...
Click to collapse
you'll first need to flash back a Sprint bootloader. Then flash twrp and revert your MID and CID back to sprint using twrp's terminal and finally flash a sprint RUU.

Categories

Resources