Develop Bugs

Downgrading 3.12.405.2 won't work, HELP?

I ****ed up with my rom, Device locked, Bootloader Locked, Getting error while downgrading, Currently software version 3.12.405.2 New Update Totally ****ed up tried all Including AAHK even in aahk also tried no use getting error like you cant downgrade your device " when trying to downgrade it says main version to old..."
in boot loader it's showing OOW Locked
Is there any thing to do with any thing ??
Please help me to clean this ****.
when i am trying to upgrade in recovery mode E:\some cache load error giving some path when i select update from sd card i am getting you dont have permission to do that & device restarting any solution ???

gexis said:
I ****ed up with my rom, Device locked, Bootloader Locked, Getting error while downgrading, Currently software version 3.12.405.2 New Update Totally ****ed up tried all Including AAHK even in aahk also tried no use getting error like you cant downgrade your device " when trying to downgrade it says main version to old..."
in boot loader it's showing OOW Locked
Is there any thing to do with any thing ??
Please help me to clean this ****.
when i am trying to upgrade in recovery mode E:\some cache load error giving some path when i select update from sd card i am getting you dont have permission to do that & device restarting any solution ???
Click to expand...
Click to collapse
can u access fastboot through bootloader

adilrenzu said:
can u access fastboot through bootloader
Click to expand...
Click to collapse
yes but not working i tried the problem is rooting ****ed up no status bar, no ring, No Menu bar. but if any one calls me i can able to answer if i press in menu place menu bar is opening device totally ****ed up in boot loader i am getting "Locked OOW" on top of s-off line in pink color.:crying:

gexis said:
yes but not working i tried the problem is rooting ****ed up no status bar, no ring, No Menu bar. but if any one calls me i can able to answer if i press in menu place menu bar is opening device totally ****ed up in boot loader i am getting "Locked OOW" on top of s-off line in pink color.:crying:
Click to expand...
Click to collapse
ok...just relax...what rom are u running? have u done a full wipe after flashing??
Just let me know and will lend u a hand

glevitan said:
ok...just relax...what rom are u running? have u done a full wipe after flashing??
Just let me know and will lend u a hand
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When i am trying to wipe or factory reset or even i am trying to enter in to recovery mode also i am getting this message cant format cache Boot locked with OOW Please reply

gexis said:
When i am trying to wipe or factory reset or even i am trying to enter in to recovery mode also i am getting this message cant format cache Boot locked with OOW Please reply
Click to expand...
Click to collapse
Are sure that You are s-off? Confirm that in hboot....and tell me if it says unlocked there also..

glevitan said:
Are sure that You are s-off? Confirm that in hboot....and tell me if it says unlocked there also..
Click to expand...
Click to collapse
Sorry for the late reply Trying to s-off downgraded to 1.8.*.* Rom unfortunately my brother updated from HTC.

[Q] HOX Locked! and security warning (I was using viperX)

Well, I have a problem. I am using viperx, with my phone unlocked, obviously. I was listening to music when it suddenly reboot. It runs in bootloader. And... with a message LOCKED and security warning. I dont know what happened. It was in my car holder, I didn´t touch anything... If I reboot, it says for a second "this build is for development purposes only. Do not distribute outside of htc without htc's written permission. Failure to comply may lead to legal action". Then back to the bootloader.
The phone was perfectly cold when it reboots...
A couple of screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help? I suposse I have to unlock it again?

Unlock it again. Use the Unlock_code.bin that you should have in your email.

death__machine said:
Unlock it again. Use the Unlock_code.bin that you should have in your email.
Click to expand...
Click to collapse
Well, I was going to do it, but.. it doesnt boot now... :crying:

racatapum said:
Well, I was going to do it, but.. it doesnt boot now... :crying:
Click to expand...
Click to collapse
after unlock don't forget to flash custom recovery and then fastboot erase cache.

is this the leaked JB hboot?

AgoeZ said:
after unlock don't forget to flash custom recovery and then fastboot erase cache.
Click to expand...
Click to collapse
Yes, but the problem is that the phone doesnt start now...

hamdir said:
is this the leaked JB hboot?
Click to expand...
Click to collapse
No, I didnt upgrade to jb yet...

Cant boot, cant charge it (no leds)...

If phone does not start and you cannot go into HBOOT and it does not get recognized as APX in your computer.
You are ****ed or battery is done.

xmoo said:
If phone does not start and you cannot go into HBOOT and it does not get recognized as APX in your computer.
You are ****ed or battery is done.
Click to expand...
Click to collapse
then.. to the sat?

Timebomb? What build were you on?

There is no way to charge it if it is power off?

webpatrick said:
Timebomb? What build were you on?
Click to expand...
Click to collapse
I was using the last viperx rom...

I would try to charge it using the charging script.
http://forum.xda-developers.com/showthread.php?t=1738274

As your phone doesn't start up / boot at all there might be something completely different that's messed up, I'm guessing it's faulty hardware that has first caused your phones software to go haywire and now the phone simply won't start. You could try the charging-script above but I'd probably go for the warranty, HTC might be a bit tricky about that though.

well his phone says locked and not relocked, the only thing there is the security warning, but i guess he can claim never to have rooted the phone.
i´m not sure about it though

Unlock again.

Well, yesterday night, I left the phone plugged to the wall carger. During the night, It starts (don´t know why) and entered bootloader. Unfortunatelly, I was too slept to try anything...
HTC wont take it to the SAT till monday, so any ideas will be really appreciated!

racatapum said:
Well, yesterday night, I left the phone plugged to the wall carger. During the night, It starts (don´t know why) and entered bootloader. Unfortunatelly, I was too slept to try anything...
HTC wont take it to the SAT till monday, so any ideas will be really appreciated!
Click to expand...
Click to collapse
It reboots again. In fastboot, of course. My pc read it. Tried the battery charger pluggin. It worked, but didt start again. It is off again. What can I do if it starts again? erase cache?

racatapum said:
It reboots again. In fastboot, of course. My pc read it. Tried the battery charger pluggin. It worked, but didt start again. It is off again. What can I do if it starts again? erase cache?
Click to expand...
Click to collapse
Mayby try install ruu for your country
Sent from my HTC One X using xda premium

[Q] Tried to convert to Google edition, now phone boots to this grey 'noise' screen

I tried following the instructions here (http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/)
After being directed to this page (http://forum.xda-developers.com/showthread.php?t=2322820)
I followed the directions on changing the Model ID. After changing the model ID and cell ID, I pushed 2 zip files to the phone (PN0714000.zip and the RUU zip). I reached a point where it booted and a green progress bar showed up. It stopped about 3/4 of the way through. And now it boots to this grey 'noise' screen. i can still run commands via adb. I even flashed a recovery img and rebooted. But no matter what i do, the grey screen is what boots up.
I should say the grey screen shows up instantly. As soon as I turn the phone on it shows up as quickly as that bootloader menu.
Any ideas? Is this the product of a wrong img? I did my best at trying to use the correct model numbers and RUU zip file, but I could have used the wrong one.
Any help would be much appreciated. I spent the day on Google and these forums trying to find answers and attempt fixes. NOthing has worked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

KevinJD said:
I tried following the instructions here (http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/)
After being directed to this page (http://forum.xda-developers.com/showthread.php?t=2322820)
I followed the directions on changing the Model ID. After changing the model ID and cell ID, I pushed 2 zip files to the phone (PN0714000.zip and the RUU zip). I reached a point where it booted and a green progress bar showed up. It stopped about 3/4 of the way through. And now it boots to this grey 'noise' screen. i can still run commands via adb. I even flashed a recovery img and rebooted. But no matter what i do, the grey screen is what boots up.
I should say the grey screen shows up instantly. As soon as I turn the phone on it shows up as quickly as that bootloader menu.
Any ideas? Is this the product of a wrong img? I did my best at trying to use the correct model numbers and RUU zip file, but I could have used the wrong one.
Any help would be much appreciated. I spent the day on Google and these forums trying to find answers and attempt fixes. NOthing has worked.
Click to expand...
Click to collapse
Well, your biggest problem is that all those instructions aren't for a Verizon HTC One.
Can you get into fastboot? I would flash a RUU and just not try to do what you were doing. Follow these instructions since you are S-Off.
http://forum.xda-developers.com/showthread.php?t=2475216
Also, Step 6 says that it's normal.
shadowboy23 said:
Step 6:
When you start your command prompt follow the steps in the picture below. PLEASE BE PATIENT!! After flashing the ENG HBOOT your HTC One will not boot up but you'll just get a gray spotted screen. Your device is not bricked. You can still use adb commands to write the model ID and CID even with a gray screen. WHEN REBOOTING HOLD DOWN POWER BUTTON FOR A FEW SECONDS. You might have to press and hold power button and volume down button when rebooting your phone.
NOTE: When you run the RUU and it says "waiting for bootloader" you will need to restart your phone manually by holding down the power button for a few seconds until it reboots. EACH TIME (does it twice) the RUU says "WAITING FOR BOOTLOADER" you will need to restart the phone manually​
Click to expand...
Click to collapse

Are you in the correct forum first? karn101 is correct this is for the Verizon HTC One. The problem is if you have a Verizon variant we are on a CDMA network. The Google Play Editions are for GSM networks which are AT&T and T-Mobile. I would head over to those forums if that is what your phone is. If not and it is a Verizon variant I would attempt to flash the RUU if you look around through the forums you will be able to find it.

mercer24 said:
Are you in the correct forum first? karn101 is correct this is for the Verizon HTC One. The problem is if you have a Verizon variant we are on a CDMA network. The Google Play Editions are for GSM networks which are AT&T and T-Mobile. I would head over to those forums if that is what your phone is. If not and it is a Verizon variant I would attempt to flash the RUU if you look around through the forums you will be able to find it.
Click to expand...
Click to collapse
I have a Verizon HTC One. Isn't that where I'm at?

karn101 said:
Well, your biggest problem is that all those instructions aren't for a Verizon HTC One.
Can you get into fastboot? I would flash a RUU and just not try to do what you were doing. Follow these instructions since you are S-Off.
http://forum.xda-developers.com/showthread.php?t=2475216
Also, Step 6 says that it's normal.
Click to expand...
Click to collapse
Thanks. I'll look at the thread. (I'll check fastboot when I'm home from work )

KevinJD said:
I have a Verizon HTC One. Isn't that where I'm at?
Click to expand...
Click to collapse
You are. But the thread you linked to is for the GSM version, not the Verizon version.

karn101 said:
You are. But the thread you linked to is for the GSM version, not the Verizon version.
Click to expand...
Click to collapse
Aw man. Could be part of my problem then. I actually tried hard to make sure any links i followed or downloads were for Verizon HTC one.

karn101 said:
Well, your biggest problem is that all those instructions aren't for a Verizon HTC One.
Can you get into fastboot? I would flash a RUU and just not try to do what you were doing. Follow these instructions since you are S-Off.
http://forum.xda-developers.com/showthread.php?t=2475216
Also, Step 6 says that it's normal.
Click to expand...
Click to collapse
Well I just hit one of the first steps and I can't proceed. "Next have your phone booted into the os / rom of choice doesn’t matter I have done this from both CM and Stock/Rooted" I can't boot into anything. Its just stuck at this static screen. I"m not sure whats behind the static. Though I can use the volume keys and go up/down then hit the power, which causes it to reboot. It seems like it's going up and down a menu, like the bootloader screen.

Enjoy your paperweight sir.

Stock HTC One (M8) in boot lock - please help

Hi,
I'm looking for some help with my currently unusable HTC One M8 on EE in the UK. I have done no rooting or making my phone S-OFF to date (and don't have the appetite for it if I'm honest) but it is now stuck in a boot loop and I don't know how to fix it.
On Monday, I accepted an OTA update which seemed to go fine but the reboot then triggered off an update to HTC Lock Screen App. This requested permission to reboot the phone and since then, the phone has been in a constant boot loop. I have tried various options including going into the menu system and selecting 'Recovery' and 'Factory Reset'. None of these options appear to do anything as the screen blanks for a moment and comes back up with the HTC initial screen and then goes into its loop. What does seem odd is that when I go into the recovery area, the menu system is unresponsive to the volume buttons until a series of code lines come up (IMAG1838.jpg)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
which takes some time to cycle through. Once completed, I can then select things like 'FASTBOOT' (IMAG1840.jpg) . Picture IMAG1839.jpg is the only screen I see if i try and reboot/recover anything. I don't know if it means anything to anyone but I also took a pic of the 'IMAGE CRC' (IMAG1841.jpg) .
Can anyone help me resolve this without rooting or voiding my warranty? EE suggested speaking to HTC as they didn't have any ideas or they could send my phone away for repair. This is an option but would rather resolve myself (with help!) if I can.
Although I'm reasonably clued up on general operations of phones, the bare bones of software is a different planet so any assistance will need to be in baby steps and spoon fed (sorry).
Hope the pictures are ok? If not, I can type out the various messages.
Thanks in advance.
Phil

did you Factory Reset while at fastboot mode?

Factory Reboot
aM- said:
did you Factory Reset while at fastboot mode?
Click to expand...
Click to collapse
Hi,
Yes - I did try a factory reset but this didn't resolve the problem and it literally rebooted immediately without appearing to do anything.
Thanks
Phil

PhillipLegg said:
Hi,
I'm looking for some help with my currently unusable HTC One M8 on EE in the UK. I have done no rooting or making my phone S-OFF to date (and don't have the appetite for it if I'm honest) but it is now stuck in a boot loop and I don't know how to fix it.
On Monday, I accepted an OTA update which seemed to go fine but the reboot then triggered off an update to HTC Lock Screen App. This requested permission to reboot the phone and since then, the phone has been in a constant boot loop. I have tried various options including going into the menu system and selecting 'Recovery' and 'Factory Reset'. None of these options appear to do anything as the screen blanks for a moment and comes back up with the HTC initial screen and then goes into its loop. What does seem odd is that when I go into the recovery area, the menu system is unresponsive to the volume buttons until a series of code lines come up (IMAG1838.jpg) View attachment 2966734 which takes some time to cycle through. Once completed, I can then select things like 'FASTBOOT' (IMAG1840.jpg) View attachment 2966736. Picture IMAG1839.jpg View attachment 2966735is the only screen I see if i try and reboot/recover anything. I don't know if it means anything to anyone but I also took a pic of the 'IMAGE CRC' (IMAG1841.jpg) View attachment 2966747.
Can anyone help me resolve this without rooting or voiding my warranty? EE suggested speaking to HTC as they didn't have any ideas or they could send my phone away for repair. This is an option but would rather resolve myself (with help!) if I can.
Although I'm reasonably clued up on general operations of phones, the bare bones of software is a different planet so any assistance will need to be in baby steps and spoon fed (sorry).
Hope the pictures are ok? If not, I can type out the various messages.
Thanks in advance.
Phil
Click to expand...
Click to collapse
Try powering down, then holding power up+power for 20 seconds. This is the equivalent of a battery pull.
Might work, might not. Give it a shot.
Then report back. I/someone might come up with a different solution if it doesn't work for you.

Battery Pull
xunholyx said:
Try powering down, then holding power up+power for 20 seconds. This is the equivalent of a battery pull.
Might work, might not. Give it a shot.
Then report back. I/someone might come up with a different solution if it doesn't work for you.
Click to expand...
Click to collapse
Hi, it was a good idea - but unfortunately this hasn't resolved the problem. Sounds like it's going away for repair unless any other forum users have a stroke of inspiration. It does feel like something has overwritten or corrupted the bootup code somehow!! At least it doesn't feel like anything I've done so warranty is still in place
Thanks for your help.

Can't enter bootloader

Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.

Ok so basically what he is saying is that his phone does NOT even have recovery mode. Where we get the dead android guy he gets this and is thus unable to flash his phone with new recovery or system.
That happened to a friend of mine a long time ago but he threw away his phone ( sold it for cheap ) without trying much.
Are there any ACTUAL solutions ?
Again Power + vol up keys DO NOT bring up recovery mode/fastboot or however you want to call it.

Anyone ?

yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there

debully said:
yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there
Click to expand...
Click to collapse
"moorefied" ?? Can you explain ?

xRanker said:
"moorefied" ?? Can you explain ?
Click to expand...
Click to collapse
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.

debully said:
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.
Click to expand...
Click to collapse
That is mostly because people touch where they are not supposed to ^^
But um thanks for reply.

With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.

debully said:
With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.
Click to expand...
Click to collapse
Not so sure of that, I really think its more user error than anything else, especially when it comes to fastboot. Copy and paste isn't your friend and it seems most people overwrite their boot or fastboot partitions with system files because they use the same command but change the img file name.
Have never had an unrecoverable brick, and those soft bricks I've had were my fault by not reading properly or skipping through steps quickly.

XepouH said:
Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.
Click to expand...
Click to collapse
Find your answer here