Database Develop

[Q] I think I bricked my phone.

So I'm trying to flash a new RUU for GPE HTC One Jelly Bean 4.3. The RUU is suppose to work for unlocked devices; the person who posted the download links had two, with one for unlocked devices and the other for locked devices. I think I messed up somewhere because I had a custom kernel installed via .zip, then booted back to the stock GPE kernel with "fastboot flash boot boot.img"; the system booted up fine but the 3 dot menu was missing so I went back to the customer kernel. The system wouldn't get past the Google screen and now I'm trying to flash the RUU but it won't work. If I do it on my computer via commands, I get "<bootloader> zip info parsing," then "FAILED <remote: 99 unknown fail>". So now I'm in TWRP recovery with the RUU on my SD card; tried flashing it on my phone and it says "Updating partition details...", "E: unable to mount ' /data'", "E: unable to mount internal storage", E: unable to mount ' /data," then lastly "Error flashing zip." I wiped the cache, data, and system; it won't wipe the Dalvik cache and gives me the same error when I do it. Can someone help me?
Edit: When I also try to wipe via "fastboot -w" it comes up with an error saying "FAILED <remote: not allowed>.

You need S-off to ruu to another firmware that's not made for your particular model/carrier.
Once you s-off enter fastboot oem rebootRUU
fastboot flash zip firmware.zip
(Firmware.zip being the actually name of the ruu zip)
It will begin to flash, then fail and say to flush image immediately. Simply press the "up" arrow on keyboard to repeat the exact same command. It will work the second time.
For some reason fastbooting a ruu in that mode always fails the first time, so you have to do it twice without exiting.
Good luck and enjoy
Sent from my HTC One using Tapatalk 2

InflatedTitan said:
You need S-off to ruu to another firmware that's not made for your particular model/carrier.
Once you s-off enter fastboot oem rebootRUU
fastboot flash zip firmware.zip
(Firmware.zip being the actually name of the ruu zip)
It will begin to flash, then fail and say to flush image immediately. Simply press the "up" arrow on keyboard to repeat the exact same command. It will work the second time.
For some reason fastbooting a ruu in that mode always fails the first time, so you have to do it twice without exiting.
Good luck and enjoy
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I think the GPE RUU supports MID: PN0713000 and CID: T-MOB010. http://forum.xda-developers.com/showthread.php?t=2358781
Edit: Oh, never mind; it says S-Off needed...
Any advice on what to do now since my HBoot is 1.54? The HBoot for the latest T-Mobile Sense 5 RUU is 1.44... I'm stuck now...

May be the alcohol but I'm having trouble keeping up lol. You're having questions with the hboot trying to s-off? If you can't s-off, nor ruu BC the firmware doesn't match with the most recent ruu then you may be stuck or hopefully someone with more advanced knowledge can help you a little better
Sent from my HTC One using Tapatalk 2

yorkies88888 said:
I think the GPE RUU supports MID: PN0713000 and CID: T-MOB010. http://forum.xda-developers.com/showthread.php?t=2358781
Edit: Oh, never mind; it says S-Off needed...
Any advice on what to do now since my HBoot is 1.54? The HBoot for the latest T-Mobile Sense 5 RUU is 1.44... I'm stuck now...
Click to expand...
Click to collapse
For some reason Google firmware will flash on certain s-on phones when it shouldn't. First we need to know if this happened.
When booted into the boot loader, is the screen black or white?
Now if there's an RUU available for your cid and mid (an official ruu.exe not an unsigned zip) that is greater than the firmware version currently on the phone, flashing that will fix everything.
If not, head over to original android development and grab a GPE ROM ( you could also use sense or AOSP, but I'm assuming you want GPe) and attempt to flash the ROM in recovery just like you normally would.
AT&T HTC M7ul
Baad Newz's InsertCoin 3.4-2
Flar2's Bulletproof 6.2

CoryTallman said:
For some reason Google firmware will flash on certain s-on phones when it shouldn't. First we need to know if this happened.
When booted into the boot loader, is the screen black or white?
Now if there's an RUU available for your cid and mid (an official ruu.exe not an unsigned zip) that is greater than the firmware version currently on the phone, flashing that will fix everything.
If not, head over to original android development and grab a GPE ROM ( you could also use sense or AOSP, but I'm assuming you want GPe) and attempt to flash the ROM in recovery just like you normally would.
AT&T HTC M7ul
Baad Newz's InsertCoin 3.4-2
Flar2's Bulletproof 6.2
Click to expand...
Click to collapse
So basically I accidentally put security back on BEFORE flashing back to stock so now I'm stuck here. The bootloader screen is black and since I upgraded to HBoot 1.54 via OTA update for stock Jelly Bean when I was S-Off, there is no compatible HBoot for me since the one for T-Mobile is 1.44 currently. My biggest worries right now is that I screwed something up with the partitions or if there's a bigger issue here because it's saying it can't mount the data and SD card, and I can't even wipe the phone via commands. If it's just the CID, MID, and HBoot not matching, then I'm not worried since I can still flash a custom ROM right?

yorkies88888 said:
So basically I accidentally put security back on BEFORE flashing back to stock so now I'm stuck here. The bootloader screen is black and since I upgraded to HBoot 1.54 via OTA update for stock Jelly Bean when I was S-Off, there is no compatible HBoot for me since the one for T-Mobile is 1.44 currently. My biggest worries right now is that I screwed something up with the partitions or if there's a bigger issue here because it's saying it can't mount the data and SD card, and I can't even wipe the phone via commands. If it's just the CID, MID, and HBoot not matching, then I'm not worried since I can still flash a custom ROM right?
Click to expand...
Click to collapse
This is why going back to s-on is almost always a bad idea. You can't flash any unsigned RUUs or firmware packages now, so you can't return your phone to stock.
It sounds like you may have corrupted your sdcard during all this. Try reformatting it from your PC. This will wipe all your data, but if it's corrupted, it's gone anyway. Then you can push a new rom and kernel and flash.

here is the latest signed RUU for TMOB.
http://forum.xda-developers.com/showthread.php?t=2427325

wwjdd44 said:
here is the latest signed RUU for TMOB.
http://forum.xda-developers.com/showthread.php?t=2427325
Click to expand...
Click to collapse
It's of no use to him; he can't run it because he's on 1.54 and s-on.

iElvis said:
This is why going back to s-on is almost always a bad idea. You can't flash any unsigned RUUs or firmware packages now, so you can't return your phone to stock.
It sounds like you may have corrupted your sdcard during all this. Try reformatting it from your PC. This will wipe all your data, but if it's corrupted, it's gone anyway. Then you can push a new rom and kernel and flash.
Click to expand...
Click to collapse
So even if T-Mobile releases an RUU with HBoot 1.54, I can't go back to stock? And how do I reformat it on my PC? CMD? And can you recommend me a ROM that's closest to stock Sense 5? And do I flash the ROM first or the kernel? Sorry about all the questions; I'm just freaking out right now.

yorkies88888 said:
So even if T-Mobile releases an RUU with HBoot 1.54, I can't go back to stock? And how do I reformat it on my PC? CMD? And can you recommend me a ROM that's closest to stock Sense 5? And do I flash the ROM first or the kernel? Sorry about all the questions; I'm just freaking out right now.
Click to expand...
Click to collapse
You still have an unlocked bootloader right?
Then I would just flash a custom recovery and "format sdcard" from there.
Then "adb push Rom.zip /sdcard/" (or sideload) and flash the Rom.
I personally use ARHD 13.x which is very close to stock Sense 5.
ROMs already include a kernel, so no need to flash separately.
Sent from my HTC One using xda app-developers app

nkk71 said:
You still have an unlocked bootloader right?
Then I would just flash a custom recovery and "format sdcard" from there.
Then "adb push Rom.zip /sdcard/" (or sideload) and flash the Rom.
I personally use ARHD 13.x which is very close to stock Sense 5.
ROMs already include a kernel, so no need to flash separately.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, I have an unlocked bootloader but TWRP doesn't seem to have a "format SD card" option.
Edit: And do you know if it's still possible to use the T-Mobile RUU when they come out with Jelly Bean 4.3 update with HBoot 1.54? Or am I just stuck with custom ROMS now?

yorkies88888 said:
Yes, I have an unlocked bootloader but TWRP doesn't seem to have a "format SD card" option.
Click to expand...
Click to collapse
I haven't used TWRP, but I'm sure it's there somewhere. Usually under advanced.
Might be called something else? What format options does TWRP have? Maybe /data/media
Sent from my HTC One using xda app-developers app

nkk71 said:
I haven't used TWRP, but I'm sure it's there somewhere. Usually under advanced.
Might be called something else? What format options does TWRP have? Maybe /data/media
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh, I found it! Thanks! Woot! Do you recommend ARHD 13.x or 21.x?

yorkies88888 said:
Oh, I found it! Thanks! Woot! Do you recommend ARHD 13.x or 21.x?
Click to expand...
Click to collapse
Personal preference. Why don't you try both. 13.x is based on official 4.2.2 and 21.x is based on leaked 4.3 (but still very good)
Just note on 21.0 you have to enter APN settings manually to get mobile data & mms, and there's a bug which won't let you access SIM card contacts.
Sent from my HTC One using xda app-developers app

nkk71 said:
Personal preference. Why don't you try both. 13.x is based on official 4.2.2 and 21.x is based on leaked 4.3 (but still very good)
Just note on 21.0 you have to enter APN settings manually to get mobile data & mms, and there's a bug which won't let you access SIM card contacts.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.

yorkies88888 said:
Edit: And do you know if it's still possible to use the T-Mobile RUU when they come out with Jelly Bean 4.3 update with HBoot 1.54? Or am I just stuck with custom ROMS now?
Click to expand...
Click to collapse
You can't use unsigned RUUs. If T-Mo releases a RUU with 1.54 or later hboot, then yes, you should be able to use it (unless you changed your MID or CID).
yorkies88888 said:
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
Click to expand...
Click to collapse
Yes it is, but you're stuck with the Google bootloader for now, until there is an s-off exploit for 1.54 or T-Mo releases that RUU.

yorkies88888 said:
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
Click to expand...
Click to collapse
It is compatible with 1.54, but I've never tried GPe, so I can't answer that. Don't know if it is firmware, ROM related, or if GPe hboot is different.
Can someone pitch in?
Sent from my HTC One using xda app-developers app

iElvis said:
You can't use unsigned RUUs. If T-Mo releases a RUU with 1.54 or later hboot, then yes, you should be able to use it (unless you changed your MID or CID).
Yes it is, but you're stuck with the Google bootloader for now, until there is an s-off exploit for 1.54 or T-Mo releases that RUU.
Click to expand...
Click to collapse
nkk71 said:
It is compatible with 1.54, but I've never tried GPe, so I can't answer that. Don't know if it is firmware, ROM related, or if GPe hboot is different.
Can someone pitch in?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well it's a good thing I changed my CID back to T-MOB010 before I put security back on then... I had SuperCID so not like it would've mattered... But thanks for the good news! And the GPE ARHD is compatible because it's Jelly Bean 4.3, but would flashing the ARHD 13.x ROM change the bootloader and start-up screen to HTC instead of Google?

yorkies88888 said:
Well it's a good thing I changed my CID back to T-MOB010 before I put security back on then... I had SuperCID so not like it would've mattered... But thanks for the good news! And the GPE ARHD is compatible because it's Jelly Bean 4.3, but would flashing the ARHD 13.x ROM change the bootloader and start-up screen to HTC instead of Google?
Click to expand...
Click to collapse
No. No rom will change your bootloader or splash screen. You need s-off to do that.

[Q] Bootloop - Tryed to RUU to Wrong Version

Ok I wanted to try out CM so I unlocked the bootloader, flashed a custom recovery and CM. I had some connectivity issues so i wanted to go back to stock. Well after locking to bootloader I flashed the 1.29 RUU without knowing I shouldn't (my hBoot was 1.55). Now I am stuck in a bootloop, my recovery is corrupt somehow (says I have no partitions). I have no idea what to do. I have looked through every thread i can find and nothing seems to work.
All I want to do is get this working again. Running stock would be nice but I really don't care at this point.
Any advice?

3.04.651.2 RUU

bigdaddy619 said:
3.04.651.2 RUU
Click to expand...
Click to collapse
That fixed it. I cannot thank you enough. Saved my ass.

KCB5 said:
That fixed it. I cannot thank you enough. Saved my ass.
Click to expand...
Click to collapse
lol no worries enjoy

Point people to the official download for the RUU. Maybe the amount of hits we give HTC will entice them to post more RUU in the future. . .
Sprint HTC One 3.04.651.2 RUU

[Q] Stuck in a loop with GPE

Hello,
I'm having an issue on my device. Whenever I flash it with a GPE rom, I get stuck in a boot loop. This ONLY happens with GPE roms. I can flash a rom with Sense 5.x and it works fine. This only started as of last week. Prior to that, I had flashed a GPE rom back in late December and it ran fine. Is there a fix to this? Or should I just stick to roms with Sense?

Izaku said:
Hello,
I'm having an issue on my device. Whenever I flash it with a GPE rom, I get stuck in a boot loop. This ONLY happens with GPE roms. I can flash a rom with Sense 5.x and it works fine. This only started as of last week. Prior to that, I had flashed a GPE rom back in late December and it ran fine. Is there a fix to this? Or should I just stick to roms with Sense?
Click to expand...
Click to collapse
update your recovery to TWRP 2.6.3.3 for anything related to KitKat

Izaku said:
Hello,
I'm having an issue on my device. Whenever I flash it with a GPE rom, I get stuck in a boot loop. This ONLY happens with GPE roms. I can flash a rom with Sense 5.x and it works fine. This only started as of last week. Prior to that, I had flashed a GPE rom back in late December and it ran fine. Is there a fix to this? Or should I just stick to roms with Sense?
Click to expand...
Click to collapse
Are you S-Off, 4.4 GPE require S-Off (in addition to recovery mentioned by @clsA)

clsA said:
update your recovery to TWRP 2.6.3.3 for anything related to KitKat
Click to expand...
Click to collapse
I've been running TWRP 2.6.3.3 from the get go. That's taken care of.

nkk71 said:
Are you S-Off, 4.4 GPE require S-Off (in addition to recovery mentioned by @clsA)
Click to expand...
Click to collapse
Just checked and realized I have S-On. This should be the problem. Thanks a bunch!

Izaku said:
Just checked and realized I have S-On. This should be the problem. Thanks a bunch!
Click to expand...
Click to collapse
no problem, maybe time to s-off
if you're having trouble with rumrunner, maybe check out @tobesedated recommendations: http://forum.xda-developers.com/showthread.php?t=2606577
and you can hit the thanks button for the posts you found useful

.

.

omarx5656 said:
So, for the past two days, I have been trying to S-Off my HTC One (M7), and it seems I have never been in luck. There was only my last hope with the Insertcoin gpe ROM, and it just opens, I click next in the setup, shuts down, restarts over and over. Basically bricked my phone, I re-installed my last ROM again. I have tried Revone, firewater, moonshine, and rumrunner. All of them didn't work for me. I'm currently running the AICP 4.4.2 ROM. My bootloader is unlocked, I'm rooted, and my hboot is 1.57.0000. I don't see what is the problem with my device. I am trying to get S-Off so I can convert my One into the gpe edition. If you could tell me step by step, thoroughly on how to get S-Off, or even install Insertcoin with S-Off, I will be very grateful. Thanks in advance. PS. Sorry if I posted this in the wrong section, I'm quite new here.
Click to expand...
Click to collapse
why not try flashing cyanogenmod 11 or my rom, its an older version of my rom but people have reported that firewater works with it, you can download it here

.

omarx5656 said:
Well, it didn't work, but something has changed. Usually, I used to get to bottle 12 and then it tells me to restart and try again. this time, it gets to bottle 2 and tells me to retry. Is there something else I'm supposed to do to get it to work? Thanks for your reply btw.
Click to expand...
Click to collapse
What about rumrunner s-off

.

@omarx5656
Flash bulletproof 14.2 kernel and then firewater step by step and you will get s-off quickly

Diabollon said:
@dd98
Flash bulletproof 14.2 kernel and then firewater step by step and you will get s-off quickly
Click to expand...
Click to collapse
just take the boot.img from the bulletproof.zip file and flash it manually, flashing the zip in recovery wont work

dd98 said:
just take the boot.img from the bulletproof.zip file and flash it manually, flashing the zip in recovery wont work
Click to expand...
Click to collapse
You can use flash image gui app from play store for kernel flash

.

The best way is to use your originally 4.4.2 stock and then flash only bulletproof 14.2 for 4.4.2 roms

omarx5656 said:
Sorry but, do I need to have Sense or GPE in order to install it? Last time I've tried installing that kernel on a custom ROM, it bricked my device. So, I'm guessing I will need Sense, but do I need to be fully stock or can I just install another custom ROM with Sense such as the ViperOne?
Click to expand...
Click to collapse
yes its for sense, im not sure about gpe

.

soft brick every time i update stock rom

HTC ONE (M7) Sprint
hboot 1.57
s-on
unlocked
recently used guru reset to go back to stock rom, worked fine until I tried to update the phone and get stuck on boot screen. loaded up twrp again and sideloaded another guru reset... did the same thing, worked until i did an update and gets stuck at boot screen when update is complete.

What kind of update are you talking about?
Sent from my HTC One using Tapatalk

ota android update

OTAs don't work with TWRP.. But I'm really not sure what is going on with your phone. Maybe just flash a ROM that's already up to date?
Sent from my HTC One using Tapatalk

guru reset installs stock rom and recovery. used the latest one available. right now i'm just going to try to get s-off and run a ruu.

Just tried again one more time to see... it seems to take the first update just fine, and only bricks on update 4.06.651.9

Mud3 said:
Just tried again one more time to see... it seems to take the first update just fine, and only bricks on update 4.06.651.9
Click to expand...
Click to collapse
What is your fastboot getvar all (minus serial no and imei)
What guru reset have you been using?

Did you ever fix this, I am having the same problem.

bigpedro36 said:
Did you ever fix this, I am having the same problem.
Click to expand...
Click to collapse
The reason it fails is because the guru reset is too old, it doesn't contain major system files, only radio and recovery plus the Rom zip file, therefore your hboot remains on the latest, probably 1.57, now when the ota comes and tries to update your hboot to 1.56 from the old Rom files that the reset put on there, it fails because you can't back flash an s-on device, s-off is the only answer unless you can find a newer reset Rom.

My HBoot is actually 1.6.. and im having trouble finding anything that will make 1.6 into s-off .

bigpedro36 said:
My HBoot is actually 1.6.. and im having trouble finding anything that will make 1.6 into s-off .
Click to expand...
Click to collapse
Have you tried sunshine s-off ? Not sure if it supports 1.6 yet though but it's worth a try, you only pay if it can s-off your phone after its run some tests. But that's my point, your on the latest hboot and the ota files are assuming you on something like 1.54 (estimate) and trying to update it, fails because you already have a newer hboot.

Seanie280672 said:
Have you tried sunshine s-off ? Not sure if it supports 1.6 yet though but it's worth a try, you only pay if it can s-off your phone after its run some tests. But that's my point, your on the latest hboot and the ota files are assuming you on something like 1.54 (estimate) and trying to update it, fails because you already have a newer hboot.
Click to expand...
Click to collapse
Cool I got S-off now. I'm trying to OTA again and will go from there.

bigpedro36 said:
Cool I got S-off now. I'm trying to OTA again and will go from there.
Click to expand...
Click to collapse
Not sure if the ota will work, you may have to just grab a full Sprint ruu and just run that which will back flash everything.

Seanie280672 said:
Not sure if the ota will work, you may have to just grab a full Sprint ruu and just run that which will back flash everything.
Click to expand...
Click to collapse
The OTA worked.. Thanks a ton.. you explained exactly what the problem was.