Database Develop

Think my One is totally bricked

Hello
First off, thank you in advance. Now to the matter.
My One is completely stuck on bootloader. I tried almost everything but no luck. If i let him do normal boot, it just shows me a black screen and reboots again, over and over. After the update i cannot get acess to fastboot because windows (8.1) tells me that the device is not known. Before the update it was all ok (i had OTA 4.3).
I cannot install a custom recovery, i cannot install anything. Tried to find a RUU.exe for my CID/MID but without luck.
The strange think is that after i update to latest kit kat, i got this (text in red):
{
"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´t do "fastboot getvar all" because i have no acess to fastboot commands.
The only thing i can do is put he phone to charge and pray to the XDA gurus
CID: VODAP102
MODEL: PN07100
SIMLOCK: NO
Anything you need to help me out, just say so and i´ll try and do my best.
Thank you

Zeus_Alex said:
Hello
First off, thank you in advance. Now to the matter.
My One is completely stuck on bootloader. I tried almost everything but no luck. If i let him do normal boot, it just shows me a black screen and reboots again, over and over. After the update i cannot get acess to fastboot because windows (8.1) tells me that the device is not known. Before the update it was all ok (i had OTA 4.3).
I cannot install a custom recovery, i cannot install anything. Tried to find a RUU.exe for my CID/MID but without luck.
The strange think is that after i update to latest kit kat, i got this (text in red):
I can´t do "fastboot getvar all" because i have no acess to fastboot commands.
The only thing i can do is put he phone to charge and pray to the XDA gurus
CID: VODAP102
MODEL: PN07100
SIMLOCK: NO
Anything you need to help me out, just say so and i´ll try and do my best.
Thank you
Click to expand...
Click to collapse
Was this OTA update or did you try and install a file manually?

Zeus_Alex said:
Hello
First off, thank you in advance. Now to the matter.
My One is completely stuck on bootloader. I tried almost everything but no luck. If i let him do normal boot, it just shows me a black screen and reboots again, over and over. After the update i cannot get acess to fastboot because windows (8.1) tells me that the device is not known. Before the update it was all ok (i had OTA 4.3).
I cannot install a custom recovery, i cannot install anything. Tried to find a RUU.exe for my CID/MID but without luck.
The strange think is that after i update to latest kit kat, i got this (text in red):
I can´t do "fastboot getvar all" because i have no acess to fastboot commands.
The only thing i can do is put he phone to charge and pray to the XDA gurus
CID: VODAP102
MODEL: PN07100
SIMLOCK: NO
Anything you need to help me out, just say so and i´ll try and do my best.
Thank you
Click to expand...
Click to collapse
whatever you do don't s-on...
will be easier to recover from.
did you relock your bootloader for any particular reason?
Oh, and don't worry - Win 8 has problems with 'talking' to your device when it's in bootloader mode.
Your phone isn't bricked. Just don't be fiddling about with it until one of the guru's with this type of issue gives you some advice.

If you have another computer or a friend with Windows 7 it won't be hard to fix at all
Sent from my HTC One using XDA Premium 4 mobile app

Zeus_Alex said:
Hello
First off, thank you in advance. Now to the matter.
My One is completely stuck on bootloader. I tried almost everything but no luck. If i let him do normal boot, it just shows me a black screen and reboots again, over and over. After the update i cannot get acess to fastboot because windows (8.1) tells me that the device is not known. Before the update it was all ok (i had OTA 4.3).
I cannot install a custom recovery, i cannot install anything. Tried to find a RUU.exe for my CID/MID but without luck.
The strange think is that after i update to latest kit kat, i got this (text in red):
I can´t do "fastboot getvar all" because i have no acess to fastboot commands.
The only thing i can do is put he phone to charge and pray to the XDA gurus
CID: VODAP102
MODEL: PN07100
SIMLOCK: NO
Anything you need to help me out, just say so and i´ll try and do my best.
Thank you
Click to expand...
Click to collapse
1- the red OS line, is because your firmware flash didnt go through, whether you did it manually or not.
if you do it manually, you do:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <- yes TWICE, if you don't do it twice you'll get the red OS line
fastboot reboot-bootloader
2- your hboot should work with Win8.1, what does it show up as in device manager? anything like this:
3- or just use an Ubuntu Live USB (no need to install, just use Try Ubuntu)

scifitrekkie said:
Was this OTA update or did you try and install a file manually?
Click to expand...
Click to collapse
I did OTA and had a reboot loop.
cr1960 said:
whatever you do don't s-on...
will be easier to recover from.
did you relock your bootloader for any particular reason?
Oh, and don't worry - Win 8 has problems with 'talking' to your device when it's in bootloader mode.
Your phone isn't bricked. Just don't be fiddling about with it until one of the guru's with this type of issue gives you some advice.
Click to expand...
Click to collapse
Thank you. I know Windows 8.1 has problems with fastboot drivers, but before that it was all right.
nateboi81 said:
If you have another computer or a friend with Windows 7 it won't be hard to fix at all
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don´t have. I have a desktop and a laptop, both with Win8
nkk71 said:
1- the red OS line, is because your firmware flash didnt go through, whether you did it manually or not.
if you do it manually, you do:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <- yes TWICE, if you don't do it twice you'll get the red OS line
fastboot reboot-bootloader
2- your hboot should work with Win8.1, what does it show up as in device manager? anything like this:
3- or just use an Ubuntu Live USB (no need to install, just use Try Ubuntu)
Click to expand...
Click to collapse
1. I tried that method before because of the bootloop and did it twice with success. Maybe something went wrong.
2. Thats the strange thing. Hboot 1.55 should indeed work but it doesn´t. And yes, thats exactly what it shows. I tried to enter security mode on win8 and do the unsigned trick, but as soon as i change to modified drivers, my mouse and keyboard stop working, so its a no go.
3. Will test that, but i dont know exactly how to mess good with linux.
And for all of you, thank you for your time. Will update as soon as i find something new.

Zeus_Alex said:
2. Thats the strange thing. Hboot 1.55 should indeed work but it doesn´t. And yes, thats exactly what it shows. I tried to enter security mode on win8 and do the unsigned trick, but as soon as i change to modified drivers, my mouse and keyboard stop working, so its a no go.
Click to expand...
Click to collapse
Please go to my guide http://forum.xda-developers.com/showthread.php?t=2541082
under FAQ #2 to fix it.
If you don't have them (but probably you do), HTC Drivers can be found here: http://forum.xda-developers.com/showthread.php?t=2089508

nkk71 said:
Please go to my guide http://forum.xda-developers.com/showthread.php?t=2541082
under FAQ #2 to fix it.
If you don't have them (but probably you do), HTC Drivers can be found here: http://forum.xda-developers.com/showthread.php?t=2089508
Click to expand...
Click to collapse
I have done the steps in FAQ#2 and this is what it shows and thats what is bothering me.
But still, i´ll go and try to boot up Ubuntu if i can find my usb pendrive
I don´t know what to do later on in ubuntu, so help is apreciated.
Thanks in advance.

Zeus_Alex said:
I have done the steps in FAQ#2 and this is what it shows and thats what is bothering me.
But still, i´ll go and try to boot up Ubuntu if i can find my usb pendrive
I don´t know what to do later on in ubuntu, so help is apreciated.
Thanks in advance.
Click to expand...
Click to collapse
Look in my FAQs, there's instructions there for Ubuntu Live USB + fastboot install
remember in linux, you'll need to use "sudo fastboot ...."

nkk71 said:
Look in my FAQs, there's instructions there for Ubuntu Live USB + fastboot install
remember in linux, you'll need to use "sudo fastboot ...."
Click to expand...
Click to collapse
Installing Ubuntu on my pendrive as i speak.
Later, after i get ADB, what should i do?

Zeus_Alex said:
Installing Ubuntu on my pendrive as i speak.
Later, after i get ADB, what should i do?
Click to expand...
Click to collapse
reflash the firmware, to get it out of "limbo"
sudo fastboot oem rebootRUU
sudo fastboot flash zip <name of firmware>.zip
sudo fastboot flash zip <name of firmware>.zip <- yep TWICE
sudo fastboot reboot-bootloader
then firmware will be back, and you can reinstall custom recovery, and flash ROM

nkk71 said:
reflash the firmware, to get it out of "limbo"
sudo fastboot oem rebootRUU
sudo fastboot flash zip <name of firmware>.zip
sudo fastboot flash zip <name of firmware>.zip <- yep TWICE
sudo fastboot reboot-bootloader
then firmware will be back, and you can reinstall custom recovery, and flash ROM
Click to expand...
Click to collapse
Thank you.
I think i won´t be needing Ubuntu. My laptop has 1 USB 2.0 port and i could make it recognize my One.
Will try those steps now.
Will i be able to go full stock from there?
Update: I did the firmware flash sucessfull. Now whats next?

Zeus_Alex said:
Thank you.
I think i won´t be needing Ubuntu. My laptop has 1 USB 2.0 port and i could make it recognize my One.
Will try those steps now.
Will i be able to go full stock from there?
Update: I did the firmware flash sucessfull. Now whats next?
Click to expand...
Click to collapse
Well where do you want to go?
BTW: i checked your first post (it doesn't say what you want to achieve), but FYI you are S-Off, so no need to LOCK/RELOCK bootloader to flash in ruu mode!!
In aviation terms: "Kindly keep you bootloader unlocked, if you are s-off"

Update 1: Tried to flash TWRP recovery but it tells me "FAILED (remote:not allowed)
So now i am stuck in bootloader because i can´t install a custom recovery.
I want full stock rom.

Zeus_Alex said:
Update 1: Tried to flash TWRP recovery but it tells me "FAILED (remote:not allowed)
Click to expand...
Click to collapse
That's because of locked bootloader.

nkk71 said:
That's because of locked bootloader.
Click to expand...
Click to collapse
How can i install the rom if i can´t do custom recovery? Sorry for all my questions, but i don´t mess with the One alot.
Another brand is ok, but HTC has some crazy stuff around the One.

Zeus_Alex said:
How can i install the rom if i can´t do custom recovery? Sorry for all my questions, but i don´t mess with the One alot.
Another brand is ok, but HTC has some crazy stuff around the One.
Click to expand...
Click to collapse
You can you just have to unlock your bootloader.

nolimit78 said:
You can you just have to unlock your bootloader.
Click to expand...
Click to collapse
Trough HTCDev or any other easy way?

nolimit78 said:
You can you just have to unlock your bootloader.
Click to expand...
Click to collapse
Zeus_Alex said:
How can i install the rom if i can´t do custom recovery? Sorry for all my questions, but i don´t mess with the One alot.
Another brand is ok, but HTC has some crazy stuff around the One.
Click to expand...
Click to collapse
1- like @nolimit78 said, you will have to unlock bootloader (you shouldnt even have locked it in the first place), can you do that? or do you need alternate methods to do that?
2- you still haven't answered my question: what is your goal?

nkk71 said:
1- like @nolimit78 said, you will have to unlock bootloader (you shouldnt even have locked it in the first place), can you do that? or do you need alternate methods to do that?
2- you still haven't answered my question: what is your goal?
Click to expand...
Click to collapse
1. I still have the "Unlock:code.bin" from HTCDev, so yes, it is possible.
2. My goal is to get a full stock rom for my CID (VODAP102) so i can go and do the future OTA´s.

[Q] Help Restoring my HTC ONE back to stock.

I bought a used htc one for at&t and it was running 4.1.2. So I tried OTA and it downloaded the s/w, installed it and upon reboot - went straight to something called teamwin recovery (?) screen. I have to chose reboot button to boot the phone back. So I realized it was rooted and am very new to this whole root thing. I wanted to ota upgrade so I googled and stumbled on the following link with too many other links. Since the following link seemed easy, I tried following:
http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
But at the step 4 I get the following:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S--ON RH
{
"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"
}
Now, how can i get it back to stock rom?
I read a lot of threads here for this very topic but each one takes talks different steps and am concerned being a noob with all these steps that I might brick my phone.
Can somebody please help me with the steps to get back to stock. I apologize if this was already covered in one of the many articles. Thanks.

jsknair said:
I bought a used htc one for at&t and it was running 4.1.2. So I tried OTA and it downloaded the s/w, installed it and upon reboot - went straight to something called teamwin recovery (?) screen. I have to chose reboot button to boot the phone back. So I realized it was rooted and am very new to this whole root thing. I wanted to ota upgrade so I googled and stumbled on the following link with too many other links. Since the following link seemed easy, I tried following:
http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
But at the step 4 I get the following:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S--ON RH
Now, how can i get it back to stock rom?
I read a lot of threads here for this very topic but each one takes talks different steps and am concerned being a noob with all these steps that I might brick my phone.
Can somebody please help me with the steps to get back to stock. I apologize if this was already covered in one of the many articles. Thanks.
Click to expand...
Click to collapse
this should be simple ..do you have a windows PC ? if so what OS version if windows 7 continue, if windows 8.1 just gather the files below and post your answer.
Download this >> http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
and unzip the fastboot.zip below to your desktop
https://www.dropbox.com/s/0wzwt8843zx27nh/Fastboot.zip
from the fastboot folder you just made do shift+right click / command prompt here. now in the command window paste this
fastboot oem lock
you just relocked the bootloader ...now run the RUU file you downloaded above and your phone will be back to Stock.

Thank you very much for the quick reply.
I already downloaded the RUU RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2 as mentioned in the previous link. Should I not use that instead use the one provided by you above?
Just wanted to make sure the steps:
- enable usb debugging on phone
- connect my phone to usb of my windows 7 (with the phone powered on or powered off?)
- from windows 7 command prompt " fastboot oem lock "
- run the RUU file
Please confirm.

jsknair said:
Thank you very much for the quick reply.
I already downloaded the RUU RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2 as mentioned in the previous link. Should I not use that instead use the one provided by you above?
Just wanted to make sure the steps:
- enable usb debugging on phone
- connect my phone to usb of my windows 7 (with the phone powered on or powered off?)
- from windows 7 command prompt " fastboot oem lock "
- run the RUU file
Please confirm.
Click to expand...
Click to collapse
1.26.502.12 is over a year old
flash the one i posted for you it's android 4.3
connect phone to usb when in the bootloader / fastboot usb

Thanks again
I am downloading the RUU.
Do I have to follow the below to do the fastboot?
http://forums.androidcentral.com/ht...restore-back-locked-one-screen-acting-up.html
Reboot your phone to bootloader (power+volume down) and choose fastboot. Plug in your phone and it will change to fastboot USB. Open a command prompt within the fastboot folder and type the following:
fastboot oem lock
The same link I pasted above says to use fastboot oem relock if it is s-on?
"fastboot oem lock" only works if your device is S-OFF and I am assuming yours isn't which is why it didn't work.
Can you please confirm?

jsknair said:
Thanks again
I am downloading the RUU.
Do I have to follow the below to do the fastboot?
http://forums.androidcentral.com/ht...restore-back-locked-one-screen-acting-up.html
Reboot your phone to bootloader (power+volume down) and choose fastboot. Plug in your phone and it will change to fastboot USB. Open a command prompt within the fastboot folder and type the following:
fastboot oem lock
The same link I pasted above says to use fastboot oem relock if it is s-on?
"fastboot oem lock" only works if your device is S-OFF and I am assuming yours isn't which is why it didn't work.
Can you please confirm?
Click to expand...
Click to collapse
which ever works just relock the bootloader and run the RUU

clsA said:
which ever works just relock the bootloader and run the RUU
Click to expand...
Click to collapse
Thanks. I was able to install the RUU you have provided. But the problem is, the camera is all PINK now. It was taking wonderful pictures before but now it's all PINK/PURPLE now. Is there a way I can fix it?

jsknair said:
Thanks. I was able to install the RUU you have provided. But the problem is, the camera is all PINK now. It was taking wonderful pictures before but now it's all PINK/PURPLE now. Is there a way I can fix it?
Click to expand...
Click to collapse
I am still not able to OTA upgrade to kitkat after 48hrs. The bootloader now says relocked. Can I simply enter into fastboot and use the following RUU to get Kitkat?
http://forum.xda-developers.com/showthread.php?t=2428276
Thanks.

My phone is currently running 4.3 with bootloader in 'relocked' state. I am still not getting the OTA update to 4.4 and all my attempts to RUU update to 4.4 fails with htc_fastboot.exe has stopped working error. I will continue to do some more research to get there as the camera is useless in 4.3 at this point. Thanks for all your help and we can close this thread.

Fastboot oem lock only relocks the bootloader. You would have been better downloading and flashing revone to s off and LOCK the bootloader
Can you post a fastboot getvar all please removing imei and serial no?
Sent from my HTC One using xda app-developers app

bricked, broke, something

running RUU on rooted phone gives me failure to connect thru usb. fastboot oem lock relocked my device and RUU tells me i need to be above 30% to flash, and i'm at 70%
fastboot................unlock token fails
device starts at splash screen with red text and wont continue past
restoring last rom successful, but wont boot past red text
push rom to device fastboot flash zip rom.zip just hangs (i have done this many times in past, it will say failed, too big of file and then ends up working any way.
fastboot oem rebootRUU works, but stil wont flash RUU says battery is dead and it's not
tried usb 2.0 and 3.0 with no luck been running rom that is no longer suported and the updated version that worked best has been deleted from server, so i want to go back to stock. i've tried other roms and was not happy so i just want stock back.
current, relocked boot loader, still have TWRP recovery, s-off, custom firmware, and all that works even though i'm (again) relocked boot loader, and i can't unlock it says faild when trying to flash unlock token

jpwhre said:
running RUU on rooted phone gives me failure to connect thru usb. fastboot oem lock relocked my device and RUU tells me i need to be above 30% to flash, and i'm at 70%
fastboot................unlock token fails
device starts at splash screen with red text and wont continue past
restoring last rom successful, but wont boot past red text
push rom to device fastboot flash zip rom.zip just hangs (i have done this many times in past, it will say failed, too big of file and then ends up working any way.
fastboot oem rebootRUU works, but stil wont flash RUU says battery is dead and it's not
tried usb 2.0 and 3.0 with no luck been running rom that is no longer suported and the updated version that worked best has been deleted from server, so i want to go back to stock. i've tried other roms and was not happy so i just want stock back.
current, relocked boot loader, still have TWRP recovery, s-off, custom firmware, and all that works even though i'm (again) relocked boot loader, and i can't unlock it says faild when trying to flash unlock token
Click to expand...
Click to collapse
Backup all of your data to your PC, HTC Backup or Google, then do a factory reset. Now, try to flash the stock firmware first then the RUU from this site.

majmoz said:
Backup all of your data to your PC, HTC Backup or Google, then do a factory reset. Now, try to flash the stock firmware first then the RUU from this site.
Click to expand...
Click to collapse
i can't, bootloader show locked, and splash screen shows unlocked and it doesn't go past splash screen.
{
"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"
}
all fast boot commands work and when phone was running all adb commands worked, problem is i have a locked bootloader ( image above ) and un unlocked bootloader ( image below ) at same time

jpwhre said:
i can't, bootloader show locked, and splash screen shows unlocked and it doesn't go past splash screen.
all fast boot commands work and when phone was running all adb commands worked, problem is i have a locked bootloader ( image above ) and un unlocked bootloader ( image below ) at same time
Click to expand...
Click to collapse
The splash screen has the warning because you have a custom recovery installed not because the bootloader is unlocked. Try to flash the stock firmware with the instructions in the OP. When it flashes, the red warning will go away. Since you are in the bootloader, try to get to factory reset. It may help clear up some of your issues and allow you flash the RUU.

majmoz said:
The splash screen has the warning because you have a custom recovery installed not because the bootloader is unlocked. Try to flash the stock firmware with the instructions in the OP. When it flashes, the red warning will go away. Since you are in the bootloader, try to get to factory reset. It may help clear up some of your issues and allow you flash the RUU.
Click to expand...
Click to collapse
Nothing, i tried flashing TWRP official instead of modified one i've been running from here, i tried flashing 4.3 firmware, i tried flashing 5 firmware ( on modified version of that from OMJ ) and nothing worked
Final attempt was to bypass the htc driver installer i have and install htc sync. Phone started right up after that. Now to restore to stock ( attempt again )

Soft-Brick HTC One M7

Hi all,
first time poster - looonnng time lurker. Hoping you can help me with my One M7 brick.
Phone had been running slow and sluggish for a few weeks. Yesterday morning, it was particularly slow with apps randomly closing/crashing. Decided to reboot. The phone didn't reboot though; it came back with a white screen and "** TAMPERED *** *** LOCKED****" coming up - a fastboot screen I believe.
I can't get it to boot at all and I've tried accessing it via adb but it isn't detected. 'adb devices' shows nothing however 'fastboot devices' does list the phone. Windroid seems to detect it.
Ordinarily, I would just do a factory reset to see if this helps but my problem is this - I have SMS messages and photos/videos on the phone of my daughter that I really, really, really don't want to lose. They are very precious to me. If it was a case of breaking up the phone then I'd do it in a heartbeat to recover this data.
I've attached some images that I hope may help. A friend has mentioned that some of the lines indicate a problem with encryption on the card which means the data is lost completely - I'm desperately hoping this isn't the case and some kind soul can help.
Thanks
{
"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"
}

need help to flash factory ruu zip
recently i installed recovery and accidentally deleted system partition..then it wont boot up..
OS- 7. 21 .980. 35
hboot -1.61
can not s-off
mid-PN0714000
cid- HTC__039
there are no ruu zip matches i found..
can anyone suggest me something to back to normal.. thanks..

namal.007 said:
recently i installed recovery and accidentally deleted system partition..then it wont boot up..
OS- 7. 21 .980. 35
hboot -1.61
can not s-off
mid-PN0714000
cid- HTC__039
there are no ruu zip matches i found..
can anyone suggest me something to back to normal.. thanks..
Click to expand...
Click to collapse
flash the 7.19.980.5 RUU, see post #2 of this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
---------- Post added at 09:24 AM ---------- Previous post was at 09:20 AM ----------
MPDi said:
Hi all,
first time poster - looonnng time lurker. Hoping you can help me with my One M7 brick.
Phone had been running slow and sluggish for a few weeks. Yesterday morning, it was particularly slow with apps randomly closing/crashing. Decided to reboot. The phone didn't reboot though; it came back with a white screen and "** TAMPERED *** *** LOCKED****" coming up - a fastboot screen I believe.
I can't get it to boot at all and I've tried accessing it via adb but it isn't detected. 'adb devices' shows nothing however 'fastboot devices' does list the phone. Windroid seems to detect it.
Ordinarily, I would just do a factory reset to see if this helps but my problem is this - I have SMS messages and photos/videos on the phone of my daughter that I really, really, really don't want to lose. They are very precious to me. If it was a case of breaking up the phone then I'd do it in a heartbeat to recover this data.
I've attached some images that I hope may help. A friend has mentioned that some of the lines indicate a problem with encryption on the card which means the data is lost completely - I'm desperately hoping this isn't the case and some kind soul can help.
Thanks
Click to expand...
Click to collapse
If the phone was encrypted then the only way to recover the phone is a factory reset using the stock recovery which will obviously delete all your files. Any other method that could fix the phone will wipe it: unlock the bootloader to flash a new rom will wipe the phone, flashing a ruu will also wipe it. Thats probably either an encryption problem or a failed emmc chip. I don't think there anything to do to recover your data, especially if the phone was encrypted. Sorry at least the phone might be recoverable...

alray said:
flash the 7.19.980.5 RUU, see post #2 of this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
---------- Post added at 09:24 AM ---------- Previous post was at 09:20 AM ----------
If the phone was encrypted then the only way to recover the phone is a factory reset using the stock recovery which will obviously delete all your files. Any other method that could fix the phone will wipe it: unlock the bootloader to flash a new rom will wipe the phone, flashing a ruu will also wipe it. Thats probably either an encryption problem or a failed emmc chip. I don't think there anything to do to recover your data, especially if the phone was encrypted. Sorry at least the phone might be recoverable...
Click to expand...
Click to collapse
Well, after asking a company who said they could do it and then said they'd have to wipe it, I've taken it back.
It seems there's nothing I can do about it; I've even tried using guides on here and elsewhere to return it completely to stock but because I can't get adb working, it's a no go. Factory reset does nothing. Trying to use tools and fastboot to change recovery images and all sorts doesn't work either. Seems to be something relating to 'S-ON' as when it's in RUU boot, if I disconnect and reconnect the USB cable, the screen briefly changes from the HTC screen to the white screen showing "Security Failed!" after trying to flash a new image on.
At a bit of a loss!

MPDi said:
It seems there's nothing I can do about it; I've even tried using guides on here and elsewhere to return it completely to stock but because I can't get adb working, it's a no go.
Click to expand...
Click to collapse
adb commands only works from a booted rom + USB debugging enabled from the developer option menu or from a custom recovery. So there is no problem here.
Factory reset does nothing.
Click to expand...
Click to collapse
What is it doing exactly? You select "factory reset and it boot to the HTC splash sceen? It reboot in bootloader mode? It freeze the phone?
Trying to use tools and fastboot to change recovery images and all sorts doesn't work either.
Click to expand...
Click to collapse
Again you need to be more precise, what doesn't work exactly? There is no fastboot connectivity or there is but the recovery won't flash? Did you unlocked the bootloader?
Seems to be something relating to 'S-ON'
Click to expand...
Click to collapse
No, Its not related to S-ON.
as when it's in RUU boot, if I disconnect and reconnect the USB cable, the screen briefly changes from the HTC screen to the white screen showing "Security Failed!" after trying to flash a new image on.
Click to expand...
Click to collapse
What image exactly and how did you tried to flash it?

alray said:
adb commands only works from a booted rom + USB debugging enabled from the developer option menu or from a custom recovery. So there is no problem here.
What is it doing exactly? You select "factory reset and it boot to the HTC splash sceen? It reboot in bootloader mode? It freeze the phone?
Again you need to be more precise, what doesn't work exactly? There is no fastboot connectivity or there is but the recovery won't flash? Did you unlocked the bootloader?
No, Its not related to S-ON.
What image exactly and how did you tried to flash it?
Click to expand...
Click to collapse
I've taken it back to another shop this morning to have it reset/flashed back to stock. Will just have to try data recovery once I've got it back and see if I can recover anything.

how to flash NEXUS 6 XT1103 ROM, BOOTLOADER LOCKED, CAN'T GET INTO PHONE, PLEASE HELP

PROBLEM -
I can not get into phone settings or ANYTHING ELSE because it keep SHOWING this error and LOADS NO OS or any icon THING AFTER BOOT
{
"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 tried from adb and it didn't work :-
<<< C:\adb>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.005s
- I have downloaded rom from google for my phone model
- I can not ENABLE OEM unlock because I can not get into phone.
- I have tried wiping CACHE AND FACTORY RESET from recovery but it does not LOAD anything after boot and shows error I posted in image above.

lol!
first off, you posted in the wrong nexus 6 forums, as you arent developing anything(besides a headache). secondly, adb and fastboot are different. fastboot is not an adb command! fastboot is a different tool, like adb but different, and you can only use fastboot while you are in the bootloader. secondly, go back for a little and do a little more reading please, then try again.
edit.. good, this thread got moved to the right place.

"Administr4tor, Account currently disabled on Today, 20:48"
Interesting. Why? Is this thread dead now?

Looks like there is no way to reinstall rom again.
what I am trying to say here is
- I can not get into phone
- I can not enable USB DEBUGGING
- I CAN NOT enable OEM UNLOCK.
tell me yes or no if I can reinstall factory image. is it not simple/

dahawthorne said:
"Administr4tor, Account currently disabled on Today, 20:48"
Interesting. Why? Is this thread dead now?
Click to expand...
Click to collapse
no, its not dead though I was dead for couple days.

Administr4tor said:
Looks like there is no way to reinstall rom again.
what I am trying to say here is
- I can not get into phone
- I can not enable USB DEBUGGING
- I CAN NOT enable OEM UNLOCK.
tell me yes or no if I can reinstall factory image. is it not simple/
Click to expand...
Click to collapse
You're trying to unlock the bootloader, which requires fastboot, using ADB. Do you have fastboot drivers installed? Or you could just unlock the boot loader with nexus root toolkit.

thatkindaguy said:
You're trying to unlock the bootloader, which requires fastboot, using ADB. Do you have fastboot drivers installed? Or you could just unlock the boot loader with nexus root toolkit.
Click to expand...
Click to collapse
Thank you for reply,
- I have adb and fastboot drivers installed from xda when I connect the phone it shows connected, Please check the screenshot.
- I just want to flash stock rom, even if its possible to do it without unlocking bootloader, please let me know.
_ i have already tried NEXUS TOOLKIT and tried to unlock bootloader but it failed to unlock it.
Regards

You can't install a factory image without a locked bootloader. What did you do to make settings force close on boot?

geokhentix said:
You can't install a factory image without a locked bootloader. What did you do to make settings force close on boot?
Click to expand...
Click to collapse
oh, I didn't do anything, I wokeup and charged it after it went dead, and it all happened,
also sometimes I get this error too if I am not getting those "unfortunate error"

Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue

Vivjen said:
Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue
Click to expand...
Click to collapse
Tried that.
Verifying update package. . .
E: failed to verify whole-file signature
E: signature verification failed
Restarting adbd. . .
Installation aborted.

vicks1008 said:
Tried that.
Verifying update package. . .
E: failed to verify whole-file signature
E: signature verification failed
Restarting adbd. . .
Installation aborted.
Click to expand...
Click to collapse
Sure. You have no possibility to push current version installed as OTA update. Try to push beta Android N for example

Vivjen said:
Sure. You have no possibility to push current version installed as OTA update. Try to push beta Android N for example
Click to expand...
Click to collapse
My Nexus 6 is stuck at LMY48M & I tried pushing the latest Marshmallow OTA build MMB29X.

You need to flash OTA with newer bootloader. Not each OTA contain newer version. Anything else will not help. Have you tried to push N?

Why is your Nexus reported in Device Manager as a Samsung device? As someone who owns a Galaxy S4 as well as a Nexus, you cannot use the Samsung driver in place of the Nexus USB driver.
Change your driver to the Google-provided version and try again.

Vivjen said:
You need to flash OTA with newer bootloader. Not each OTA contain newer version. Anything else will not help. Have you tried to push N?
Click to expand...
Click to collapse
I can't even sign up for the Nexus Beta Program. I have to sign up from the Nexus 6.

Nexus root toolkit
this toolkit will do all the work for you. from wugfresh development

vicks1008 said:
I can't even sign up for the Nexus Beta Program. I have to sign up from the Nexus 6.
Click to expand...
Click to collapse
No. Just download OTA from PC and push it to N6 via adb sideload

joseppa87 said:
this toolkit will do all the work for you. from wugfresh development
Click to expand...
Click to collapse
Absolutely. It washed my dishes, took the dog for a walk, and helped me with my homework.

Vivjen said:
Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue
Click to expand...
Click to collapse
sIR, How did you push STOCK OTA and where did you get it from, Can you please tell me steps you followed in details?
Thank you for reading.