Database Develop

No OS on phone, can't install a rom

I am hoping someone can help with this, my son completely wiped his Google Edition HTC One. When I asked him what he did he stated that he flashed TWRP and did a full wipe checking all of the boxes under the advanced tab. Then when he tried to flash Cyanogenmod 10.2 it keeps failing. I asked him why he did this and he said his friend told him how cool Cyanogenmod is so naturally he want it to! (By the way my son is 13).
I know very little about this phone but I would like to get the phone back to the way it was before he messed with it as it cost me $650 to buy it. I started reading about RUU files but from what I can tell the RUU will not work with S-ON. And I can't seem to flash any ROM as it keeps failing. Any suggestions would be a big help!

Don't worry this is fixable
First relock your bootloader
Then download a RUU.zip for GPe
boot into fastboot
and type this command (in your pc of course with adb) fastboot oem rebootRUU
A silver htc logo should show
copy the RUU you downloaded to your adb folder and rename to ruu.zip
and type this command fastboot flash zip ruu.zip
this command should be typed twice (ignore the error that shows up)
after the second time it's done
type fastboot reboot
should turn right up
Good luck

Then make him use a flip phone for a week as punishment lol

I had the same. In my case I started ruu for another version (international), of course ruu failed to install but it did fix partitions, after that I was able to sideload rom. I will try to find my topic and provide You with my solution.
This is my BLS/ALS with HTC One, patient is alive and well now, only camera has pink tint...
http://forum.xda-developers.com/showthread.php?t=2322851
Try with CWM instead of TWRP... and finally pass some information about progress.

Thealshear said:
Don't worry this is fixable
First relock your bootloader
Then download a RUU.zip for GPe
boot into fastboot
and type this command (in your pc of course with adb) fastboot oem rebootRUU
A silver htc logo should show
copy the RUU you downloaded to your adb folder and rename to ruu.zip
and type this command fastboot flash zip ruu.zip
this command should be typed twice (ignore the error that shows up)
after the second time it's done
type fastboot reboot
should turn right up
Good luck
Click to expand...
Click to collapse
Will the ruu method work if the phone is S-ON? All of the XDA posts I read state that you need to be S-OFF?

Give it a shot the phone is already bricked what you got to lose

crixley said:
Then make him use a flip phone for a week as punishment lol
Click to expand...
Click to collapse
For now until I can fix the phone he is back to two cans and string!
Sent from my Nexus 5 using Tapatalk

woody970 said:
For now until I can fix the phone he is back to two cans and string!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You can run an ruu but it has to be newer..
See here:
http://forum.gsmhosting.com/vbb/f485/understanding-s-off-super-cid-s-read-b4-u-run-ruu-1505916/

crixley said:
You can run an ruu but it has to be newer..
Any idea where to download the RUU? The build number that was on the phone before all this started was KRT16S.H5 release-keys
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse

woody970 said:
I am hoping someone can help with this, my son completely wiped his Google Edition HTC One. When I asked him what he did he stated that he flashed TWRP and did a full wipe checking all of the boxes under the advanced tab.
Click to expand...
Click to collapse
The good news are that the phone isn't bricked, imho. The bad ones are that you will have to play with ROMs recoveries and RUU's a bit in order to have a working phone back. First of all I would focus to succeed in flashing a ROM in order to boot your phone. Googling I found a user with your same error showed in the pic that solved the issue "checking the signature box then flash a ROM where he got the error then unchecked the same signature box and reflash with success". If this process doesn't work for you, I suggest to flash a different recovery such as CWM and try to flash the ROM through it. Anyway you'll need an unlocked bootloader for the entire process. Let me know if you succeed.
Sent from my HTC One using Tapatalk

Delgra said:
The good news are that the phone isn't bricked, imho. The bad ones are that you will have to play with ROMs recoveries and RUU's a bit in order to have a working phone back. First of all I would focus to succeed in flashing a ROM in order to boot your phone. Googling I found a user with your same error showed in the pic that solved the issue "checking the signature box then flash a ROM where he got the error then unchecked the same signature box and reflash with success". If this process doesn't work for you, I suggest to flash a different recovery such as CWM and try to flash the ROM through it. Anyway you'll need an unlocked bootloader for the entire process. Let me know if you succeed.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
when your son was flashing CM mod was he using the correct version? I don't recall but I tried flashing my ATT HTC one but I am running a WWE firmware so that made me have to flash the GSM version of CM mod. http://www.cmxlog.com/11/m7ul/ Try downloading the latest zip file there and than try mounting to his phone with the USB mount or if you have a USB OTG you can install it from a USB. It shouldn't matter if your S-ON or S-OFF for installing some roms it just helps you avoid taking extra steps to get the ROM to install.
When your flashing with TWRP make sure to do a advanced wipe and check everything that is on there. After you do a advanced wipe do a regular factory reset. I'm hoping that the new CM11 rom will flash for his phone. You can also use ADB sideload to send the zip files over to your phone if you cannot mount the phone. What ADB sideload does is open up a connection from your phones USB and lets you transfer zips over onto the internal SD card basically in DOS command.

I want to thank everyone for there guidance in this. After googling for a couple of days and a few failed attempts with the RUU command I was finally able to restore the phone. I was able to flash a nandroid backup using TWRp from another google edition HTC which brought the phone back to life. Then I flashed a stock recovery and OTA's became available to the phone. The once dead HTC is now back up and running stock 4.4 android. The only issue I with the phone now is that there is a popping sound after a notification comes in that I can't get rid of... Anyone have any ideas?
Sent from my Nexus 5 using Tapatalk

The popping noises seem to come after I updated to kit Kat I don't know but a lot of people might have that issue too.
Sent from my HTC One using Tapatalk

[Q] Stuck at HTC Boot Screen.

I recently got an HTC Raider (Bell) and was following the steps to Root the device and got stuck...
was following this : http://forum.xda-developers.com/showthread.php?t=1416836
the phone was all stock, stock rom, was able to unlock the bootloader via HTC website, did the Wire Trick to S-Off the device but when i got to step 3 "Update the HBOOT (Juopunutbear)" i got an error when trying to "fastboot flash zip jb_hboot.zip" using WCXJB ROOT PACK ... im at work now and cant remember the exact wording of the error, but it Fails (will update tonight with the exact error message).
i read around and people seemed to say that when doing the wire-trick the HBOOT was already being updated and people said it wasnt required, so i went ahead and followed the next steps (Perm-Root) which did work, then i went and tried to load a custom Rom + Gapps and they never worked (either they crashed 5 seconds after boot or just crash at the HTC boot screen and never work)
i can still access Recovery, etc ... i just cant flash any roms, and stupid me i erased my backup on the SDCARD (wiped the SDCARD so i lost my nand backup... i thought the backup was on the internal phone memory)...
any idea ???
thanks for your time, I apreciate it.

Extraze said:
I recently got an HTC Raider (Bell) and was following the steps to Root the device and got stuck...
was following this : http://forum.xda-developers.com/showthread.php?t=1416836
the phone was all stock, stock rom, was able to unlock the bootloader via HTC website, did the Wire Trick to S-Off the device but when i got to step 3 "Update the HBOOT (Juopunutbear)" i got an error when trying to "fastboot flash zip jb_hboot.zip" using WCXJB ROOT PACK ... im at work now and cant remember the exact wording of the error, but it Fails (will update tonight with the exact error message).
i read around and people seemed to say that when doing the wire-trick the HBOOT was already being updated and people said it wasnt required, so i went ahead and followed the next steps (Perm-Root) which did work, then i went and tried to load a custom Rom + Gapps and they never worked (either they crashed 5 seconds after boot or just crash at the HTC boot screen and never work)
i can still access Recovery, etc ... i just cant flash any roms, and stupid me i erased my backup on the SDCARD (wiped the SDCARD so i lost my nand backup... i thought the backup was on the internal phone memory)...
any idea ???
thanks for your time, I apreciate it.
Click to expand...
Click to collapse
So.. the error I get when trying to update the HBOOT (step 3 of the Superguide) is :
sending 'zip' (379KB) ... OKAY
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time : 2.110s.
please help

Extraze said:
I recently got an HTC Raider (Bell) and was following the steps to Root the device and got stuck...
was following this : http://forum.xda-developers.com/showthread.php?t=1416836
the phone was all stock, stock rom, was able to unlock the bootloader via HTC website, did the Wire Trick to S-Off the device but when i got to step 3 "Update the HBOOT (Juopunutbear)" i got an error when trying to "fastboot flash zip jb_hboot.zip" using WCXJB ROOT PACK ... im at work now and cant remember the exact wording of the error, but it Fails (will update tonight with the exact error message).
i read around and people seemed to say that when doing the wire-trick the HBOOT was already being updated and people said it wasnt required, so i went ahead and followed the next steps (Perm-Root) which did work, then i went and tried to load a custom Rom + Gapps and they never worked (either they crashed 5 seconds after boot or just crash at the HTC boot screen and never work)
i can still access Recovery, etc ... i just cant flash any roms, and stupid me i erased my backup on the SDCARD (wiped the SDCARD so i lost my nand backup... i thought the backup was on the internal phone memory)...
any idea ???
thanks for your time, I apreciate it.
Click to expand...
Click to collapse
I answered this yesterday...
Jbhboot.zip is not flashable...
Unzip and apply accordingly...
And please... Read the question and answer thread before starting new
Sent from my Vivid 4G using Tapatalk

rignfool said:
I answered this yesterday...
Jbhboot.zip is not flashable...
Unzip and apply accordingly...
And please... Read the question and answer thread before starting new
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
thanks, but it did flash, and i did read, i read for about 20 hours on this forum, if not more.
here's how i fixed it, hopefuly this can help others...
when i got the "remote: 41 model id check fail" i found a post hidden in here telling to change the phone's CID by typing "fastboot oem writecid 11111111" this worked and i was able to continue with the steps... it did not cure my booting issue, i was still stuck at the white HTC screen... so i locked the device back, got a basic AT&T RUU (my phone was a Bell, so i dont think it matters which one you use) and wiped everything (SD card, cache, data, etc) ...
this solved my non-bootable issue ... so i went at it again, unlocked the phone via HTC's website, re-install a recovery, then the ROM i wanted.
I hope this can save someone a couple of hours of headaches and searches

Bricked htc vivid stuck on white screen
i unlocked the bootloader with unlocker v2 by Fenguepay after that it was partially rooted so after that i rebooted and everything was fine then i tried to flash rom with cm-11-20140628-unofficial-pyramid.zip and gapps it didnt go tru, so i downloaded yet another rom: resurrection remix - kk- v5. 1.2-20140521-holiday.zip and pa gapps modular mini 4.4.2-20131230-signed.zip yet it got stuck on d htc white screen. That was when i used vivid all in one kit v3.0 to relock so i could try flahing factory RUU but no way. i flashed it by entring h boot den got into recovery and wiped cache,davik and data and i also did factory reset before flashing it with the above mentioned roms and gapps. please someone should help me. i have read and read and read till i am now confused. :crying:

[Q] Chronic phone problems. Want to nuke the whole thing and start again.

I have had inklings that something was a little off with my installation for a little bit. It has always been like pulling teeth to get a rom installed on my htc one, and for the most part I had to sideload everything I wanted to install.
I ran a snapshot of cyanogen for a while, but my phone refused to update to new versions. I got frustrated and installed the nocturnal GPE rom which worked fine for a few months, but recently would not connect to the networks. I attempted to run the factory reset command from TWRP, but the phone hung for an hour trying to erase the cache. Then when I restarted the phone, instead of seeing the boot screen for the GPE rom I had most recently installed, I saw the cyanogen boot screen.
I have had little luck reinstalling roms since then and also have some problems with the recoveries. I have to install CWM or whatever recovery I dont have installed to even get sideloading to work. I've installed the nocturnal GPE rom again, but when it gets to the screen to select English it just restarts without warning.
Right now I just want to know if it is possible to nuke everything but the bootloader and just start fresh from factory settings. I want the nightmare to be over!
I have done everything in this thread:
http://forum.xda-developers.com/htc-one/help/lost-signal-cache-boot-recovery-t2851707/post54949931

gothmog1114 said:
I have had inklings that something was a little off with my installation for a little bit. It has always been like pulling teeth to get a rom installed on my htc one, and for the most part I had to sideload everything I wanted to install.
I ran a snapshot of cyanogen for a while, but my phone refused to update to new versions. I got frustrated and installed the nocturnal GPE rom which worked fine for a few months, but recently would not connect to the networks. I attempted to run the factory reset command from TWRP, but the phone hung for an hour trying to erase the cache. Then when I restarted the phone, instead of seeing the boot screen for the GPE rom I had most recently installed, I saw the cyanogen boot screen.
I have had little luck reinstalling roms since then and also have some problems with the recoveries. I have to install CWM or whatever recovery I dont have installed to even get sideloading to work. I've installed the nocturnal GPE rom again, but when it gets to the screen to select English it just restarts without warning.
Right now I just want to know if it is possible to nuke everything but the bootloader and just start fresh from factory settings. I want the nightmare to be over!
I have done everything in this thread:
http://forum.xda-developers.com/htc-one/help/lost-signal-cache-boot-recovery-t2851707/post54949931
Click to expand...
Click to collapse
Follow this guide.

StormyNight said:
Follow this guide.
Click to expand...
Click to collapse
I tried that. When flashing the firmware, I get (bootloader) read zipped android_info fail. FAILED (remote: 99 unknown fail)

gothmog1114 said:
I tried that. When flashing the firmware, I get (bootloader) read zipped android_info fail. FAILED (remote: 99 unknown fail)
Click to expand...
Click to collapse
Could you screenshot the bootloader for me?

Maybe you've got a whacked recovery. Reflash from fastboot from an md5 verified .img (make sure its m7wls version of TWRP). You should have no problems wiping any partition from within.

StormyNight said:
Could you screenshot the bootloader for me?
Click to expand...
Click to collapse
http://imgur.com/GwCBmpe

gothmog1114 said:
http://imgur.com/GwCBmpe
Click to expand...
Click to collapse
Are you using a Windows 8 computer? If so, try it with Windows 7. If you're using Windows 7, try a different port (preferably a USB 2.0 port).

HTC ONE M7 stuck on unlocking screen

Hello
first my problem was:
Quote:
Originally Posted by mara_hr
to cut the long story short, i have formated data on my htc one m7 without making backup (i know)
i have downloaded several roms and am able to read them though usb-otg without problem.
problem occurs when i try to flash them:
Error log:
Skipping MD5 check: no MD5 file found.
assert failed: getpro()
E:Error executing updater binary in zip
Error flashing zip
But when i try to flash android revolution HD 81 - Android revolution 81 , he reads the rom, starts to flash it but screen doesnt respond. volume keys and power keys respond, but you can not say where is the key??
please help
i use TWRP v2.5.0.0
is there any way to update twrp? (latest roms require 2.6 twrp or higher???)
Download the 2.6.3.3 version of TWRP, rename the file to recovery, place the .img file in the folder on your PC where ADB is located and then flash in fastboot with fastboot flash recovery recovery.img. After that command completes, run fastboot erase cache. Then you can copy the ARHD 81 .zip to your phone and flash away.
after that i have tried:
So now you probably have screwed your partitions flashing an incompatible rom and recovery to your phone. Flash a twrp version for Sprint variant and then format data and flash a Custom rom compatible with Sprint phones (M7WLS)
Sprint TWRP here: http://techerrata.com/browse/twrp2/m7wls
Sprint roms here: http://forum.xda-developers.com/spri...ne/development
i have flashed sprint twrp and sprint roms:
Bad Boyz Sprint ONE ROM 4.4.2 Sense 6 v1.0
ROM] Eragon v53Stable&clean|Sense/Aosp/GPE mix, ROM for the HTC One
Sprint_Eragon_V_54.0.0.zip
ViperOne 7.0.1
and they all have same issue.
installation went well. on first boot rom went to lock screen. after unlocking only white screen occurs with green htc logo.
after that dialer app reports crushing
what to do next?
do i need to unlock sprint sim since i live in croatia (europe)?
thanks for help

You should RUU and get everything working the way it should again.
Then flash a rom from the Sprint section.

BD619 said:
You should RUU and get everything working the way it should again.
Then flash a rom from the Sprint section.
Click to expand...
Click to collapse
thx for repling
im a bit of a n00b. can you send me a link or something how to do that? thank you

mara_hr said:
thx for repling
im a bit of a n00b. can you send me a link or something how to do that? thank you
Click to expand...
Click to collapse
android revolution HD 81
Click to expand...
Click to collapse
bruhhh
NOTE: Read the threads, the instructions I'm giving you are just for you to gauge the difficulty of this task, to see if you can do it. Don't follow my instructions! Read the threads!
Read this first.
Then get this firmware.zip and put it in your adb/fastboot folder
source
reboot into fastboot mode with:
adb reboot bootloader
unless you don't have ADB, which you probably don't because you dun goofed when you flashed an Int'l ROM. In which case just press and hold power + vol down and pray.
once you're in fastboot mode, check to see if your device is recognized (may have to do this as root user in linux):
fastboot devices
This should list your device. If nothing comes up, check back here.
Now we're gonna lock your bootloader because RUU fails on unlocked bootloaders (security reasons). Skip this if you're S-Off (you shouldn't be, that's for advanced users).
fastboot oem lock
Now you're gonna go into RUU mode, which lets you modify all partitions of the phone (because you won't be in one):
fastboot oem rebootRUU
Now, we're going to flash the stock image to all the partitions of your device. This is the step that will undo your mistake!
fastboot flash zip firmware_version.zip
NOTE: Change the name of firmware_version.zip to whatever you download from above. If you get an error saying "flush again immdeiately," flash again immediately; just put in the exact same command.
Done. Just finalize with this:
fastboot reboot-bootloader
And then unplug and redo your entire root/ROM process from there.
Hopefully this mini guide will give you an idea of whether you'll need further help. @BD619 is a great fellow to ask.

thank you. you are a life saver. my phone is alive
iv unlocked the bootloader. what do i have to do now install custom rom?

Completely wiped OS during reset :(

Hello, I'm new to these forums and have come to them under some unfortunate circumstances.
I went to update my device (MOTO G 2014) and had an error (cant remember what it said), anyway I rebooted my device and it wouldnt load after the 'BOOT LOADER UNLOCKED' warning screen. I went into TWRP and went to reset my device and wiped the system. (feel like an idiot, then again I am..) So then I downloaded all the USB drivers and Android SDK along with adb+fastboot and attempted to sideload. during the sideload I got this error..
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
EDIT: the error is no showing up at * failed to write data 'protocol fault (no status)
I have swapped USB ports and tried a different USB cable, does anybody have any tips or do I have a paperweight on my hands?
Thanks in advance

Flash stock firmware.
motofirmware.center
Sent from my XT1031

If I understand, right now you have wiped system, and bootloop in Motorola logo.
If you can boot in recovery, then transfer a ROM to an microsd and flash from there.

UPDATE: managed to put 3 ROMs onto my sdcard but only one of them actually allows me to install it, but after I install it I am stuck at the boot screen, guessing I got the wrong ROM for my model, cm doesn't flash, it just says 'Failed!' and so does the most recent one from the website previously linked. Any tips? Model is XT1072. I have been sat at the boot screen for around 15-20 minutes, is it taking so long because of me clearing the dalvik cache?

PJT95 said:
UPDATE: managed to put 3 ROMs onto my sdcard but only one of them actually allows me to install it, but after I install it I am stuck at the boot screen, guessing I got the wrong ROM for my model, cm doesn't flash, it just says 'Failed!' and so does the most recent one from the website previously linked. Any tips? Model is XT1072. I have been sat at the boot screen for around 15-20 minutes, is it taking so long because of me clearing the dalvik cache?
Click to expand...
Click to collapse
Lemme guess u tried to flash "titan" CM and not "thea" one?

LuK1337 said:
Lemme guess u tried to flash "titan" CM and not "thea" one?
Click to expand...
Click to collapse
I have tried both, both are returning the same error
"E: error executing updater binary in zip"
Is this something to do with my TWRP being at v2.7.1.1?

PJT95 said:
I have tried both, both are returning the same error
"E: error executing updater binary in zip"
Is this something to do with my TWRP being at v2.7.1.1?
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3088800
get this recovery.

LuK1337 said:
http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3088800
get this recovery.
Click to expand...
Click to collapse
Thanks for your help and thank you to everyone else who replied to the thread. To anybody else who will maybe see this thread and who are stuck with the same errors, I fixed this by simply flashing the latest recovery using 'fastboot flash recovery [NameOfRecovery].img' then proceeded to install the ROM compatible with my device which I downloaded to my external SD Card.
Again, thanks