Related
Please help urgently! So I just S-OFF'd my phone (right after unlocking my bootloader via htcdev) and I was excited to finally manually flash a 5.1 update to my EE UK One m9. I sort of made it a European version by changing one of its update numbers to [BLANK].401.[BLANK]. I then spent the whole night booting my phone into download mode and using fastboot commands: "htc_fastboot flash zip...".
Each zip was the previous update to the other, I.e. I was already on 1.32.401.6, so I used fastboot to get to 1.32.401.8 as the cmd. prompt said that it was successfully installed on my phone (p.s. I didn't have an sd card big enough to exfat 32 and put the update zips on it). I then repeated the steps again, but then fastboot flashed "2.10.401.", this was the update that would hopefully bring my phone to 5.1 . The cmd. prompt said that it was a success so I booted my phone up as normal, but I went to the settings to check software information and it was still on 1.32.401.6! It then said an update was ready to install so I just installed it as normal. Once it went into the bootloader it flashed it without any problems and tried to boot back up again. It then lit up a blue screen for 10 seconds and then went into the black HTC RUU screen with the grey htc logo. My phone has now, for the last hour, been stuck in this infinite loop of blue screen, vibrate, ruu screen and REPEAT. I've tried pressing vol. down and power as well as up to get into other modes like download mode, but it doesn't work. I CAN'T EVEN TURN IT OFF! I HAVE TO WAIT FOR IT TO RUN OUT OF BATTERY! MORE IMPORTANTLY, ADB DOESNT RECOGNISE IT, NOR DOES FASTBOOT!!!! SO I CAN'T EVEN FLASH A STOCK RECOVERY, SYSTEM IMG, ETC! PLEASE IF ANYONE CAN, HELP ME. I REALLY DON'T WANT TO HAVE TO BUY A NEW ONE AND PAY S-OFF AGAIN!
Louis118 said:
Please help urgently! So I just S-OFF'd my phone and I was excited to finally manually flash a 5.1 update to my EE UK One m9. I sort of made it a European version by changing one of its update numbers to [BLANK].401.[BLANK]. I then spent the whole night booting my phone into download mode and using fastboot commands: "htc_fastboot flash zip...".
Each zip was the previous update to the other, I.e. I was already on 1.32.401.6, so I used fastboot to get to 1.32.401.8 as the cmd. prompt said that it was successfully installed on my phone (p.s. I didn't have an sd card big enough to exfat 32 and put the update zips on it). I then repeated the steps again, but then fastboot flashed "2.10.401.", this was the update that would hopefully bring my phone to 5.1 . The cmd. prompt said that it was a success so I booted my phone up as normal, but I went to the settings to check software information and it was still on 1.32.401.6! It then said an update was ready to install so I just installed it as normal. Once it went into the bootloader it flashed it without any problems and tried to boot back up again. It then lit up a blue screen for 10 seconds and then went into the black HTC RUU screen with the grey htc logo. My phone has now, for the last hour, been stuck in this infinite loop of blue screen, vibrate, ruu screen and REPEAT. I've tried pressing vol. down and power as well as up to get into other modes like download mode, but it doesn't work. I CAN'T EVEN TURN IT OFF! I HAVE TO WAIT FOR IT TO RUN OUT OF BATTERY! MORE IMPORTANTLY, ADB DOESNT RECOGNISE IT, NOR DOES FASTBOOT!!!! SO I CAN'T EVEN FLASH A STOCK RECOVERY, SYSTEM IMG, ETC! PLEASE IF ANYONE CAN, HELP ME. I REALLY DON'T WANT TO HAVE TO BUY A NEW ONE AND PAY S-OFF AGAIN!
Click to expand...
Click to collapse
hold power and vol up and vol down all at the same time will get you to bootloader, we hope
Aldo101t said:
hold power and vol up and vol down all at the same time will get you to bootloader, we hope
Click to expand...
Click to collapse
That helped thanks, but I still can't boot into anything else... I'm pretty sure I can't install anything through fastboot without download or run mode...
Louis118 said:
That helped thanks, but I still can't boot into anything else... I'm pretty sure I can't install anything through fastboot without download or run mode...
Click to expand...
Click to collapse
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Aldo101t said:
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Click to expand...
Click to collapse
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Aldo101t said:
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Click to expand...
Click to collapse
what you should do is if you can restore a backup, put a 5.1 rom on your sd card and after you flash the latest firmware 2.10.401.xx. then boot to recovery and install the 5.1 rom.
---------- Post added at 07:43 PM ---------- Previous post was at 07:41 PM ----------
Louis118 said:
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Click to expand...
Click to collapse
you still have TWRP INSTALLED, do you have a backup.
Aldo101t said:
what you should do is if you can restore a backup, put a 5.1 rom on your sd card and after you flash the latest firmware 2.10.401.xx. then boot to recovery and install the 5.1 rom.
---------- Post added at 07:43 PM ---------- Previous post was at 07:41 PM ----------
you still have TWRP INSTALLED, do you have a backup.
Click to expand...
Click to collapse
How do you expect me to boot into it? I told you, pressing any other mode besides power off, causes the blue screen loop
Louis118 said:
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Click to expand...
Click to collapse
try powering it off then go back to bootloader and try to get to recovery again
Aldo101t said:
try powering it off then go back to bootloader and try to get to recovery again
Click to expand...
Click to collapse
Nope, still does the blue loop.
Louis118 said:
Nope, still does the blue loop.
Click to expand...
Click to collapse
well, that's the sh^ts, I don't know at this point.maybe someone else can chime in here that can help.
I've seen this before, and there is no fix that I'm aware of. You've corrupted something important in your firmware, probably by flashing all those firmware packages.
You made several mistakes here, the first in thinking you needed to flash every firmware for your phone. All you needed was the last one. The other mistake was confusing your OS version with your firmware version. You were still on 1.32 base but your firmware was updated.
The last mistake, and the one that probably did the damage, was trying to take an OTA after all that. You were stock enough for it to run, but since your firmware was already updated, the OTA broke something.
As far as I know, the only thing you can do is return it to HTC for service.
Sent from my HTC One M9 using Tapatalk
iElvis said:
I've seen this before, and there is no fix that I'm aware of. You've corrupted something important in your firmware, probably by flashing all those firmware packages.
You made several mistakes here, the first in thinking you needed to flash every firmware for your phone. All you needed was the last one. The other mistake was confusing your OS version with your firmware version. You were still on 1.32 base but your firmware was updated.
The last mistake, and the one that probably did the damage, was trying to take an OTA after all that. You were stock enough for it to run, but since your firmware was already updated, the OTA broke something.
As far as I know, the only thing you can do is return it to HTC for service.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help anyway. Also, I got this under contract from EE, so do I have UH OH protection automatically from htc? Or will it cost me to get it serviced?
Louis118 said:
Thanks for trying to help anyway. Also, I got this under contract from EE, so do I have UH OH protection automatically from htc? Or will it cost me to get it serviced?
Click to expand...
Click to collapse
Uh Oh protection isn't available in the UK.
As you unlocked your bootloader and got S-OFF, they will almost certainly charge you for repairs as this isn't a hardware issue and was actually caused by you flashing your phone.
Sent from my HTC One M9 using Tapatalk
Questions............
Did u install any recovery like twrp?
Did you root?
Post pictures of bootloader/try to post any other screen you may be able to enter
LLegion said:
Questions............
Did u install any recovery like twrp?
Did you root?
Post pictures of bootloader/try to post any other screen you may be able to enter
Click to expand...
Click to collapse
I'm able to enter the boot loader menu (with the options to reboot, power down, download mode and bootloader). Unfortunately, clicking any of the options (apart from power down) causes the blue screen boot loop to continue.
This wasn't really Crazy you now All You have to do is go to the bootloader menu and from there Ashley you can actually flash the Recovery ebusiness Leave me and if you don't believe me godaddy redirect link to the Team Win recovery project Website Just follow the instructions to flash recovery as they say
---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------
You can flash recovery from bootloader menu i did that way when by mistake did erease all my internal card including system.img.....i was lost my phone didnt boot line yours also getting the bluescreen and voilaaa!!! I did flash on bootloader menu but download the 2.8.7.1 beta here the proof link....https://twrp.me/devices/htconem9.html
LLegion said:
This wasn't really Crazy you now All You have to do is go to the bootloader menu and from there Ashley you can actually flash the Recovery ebusiness Leave me and if you don't believe me godaddy redirect link to the Team Win recovery project Website Just follow the instructions to flash recovery as they say
---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------
You can flash recovery from bootloader menu i did that way when by mistake did erease all my internal card including system.img.....i was lost my phone didnt boot line yours also getting the bluescreen and voilaaa!!! I did flash on bootloader menu but download the 2.8.7.1 beta here the proof link....https://twrp.me/devices/htconem9.html
Click to expand...
Click to collapse
I flashed the recovery file successfully (according to the command window) but when I click the "reboot recovery mode" option it brings up the red development text and then goes back into the bluescreen loop.
Louis118 said:
I flashed the recovery file successfully (according to the command window) but when I click the "reboot recovery mode" option it brings up the red development text and then goes back into the bluescreen loop.
Click to expand...
Click to collapse
You said before that fastboot wasn't working. It's working now? Does it show up in fastboot devices?
If so, you might try running a RUU from bootloader.
The trixk is to flash and just after reboot press power and down vol to wnter immediatly into rexovery twrp just as it says in the link...just do it and will go into twrp once you have entered justflash any nandroid or flash a zip ruu from sd card in a sexond boot
I'm not able to enter RUU mode...
This is my first post and I am writing it after a Christmas night with the fam, so please expect errors.
This phone has given me problems even before it arrived to my door Christmas eve. My city received too much snow for the mailman to deliver my package to my door, making it more difficult for me to obtain my device on time. Once I received my device it was great, fingerprint sensor was extremely convenient, took great pictures for Christmas, call quality was good, among other little things. Getting to the point of this thread. I got a notification to update my phone to the latest software, because we eating, I tried to set it for later. The "later" button did not work. after 2 hours and the annoying notification, I decided to download the update and install it. These are my steps:
Pluggled in the charger
Downloaded update
let the phone do its thing overnight
I woked up
"Google logo" bootloop
I can't access the recovery partition, it shows the green android logo with the string "no command"
When I manually boot the device using the bootloader:
"Your device is corrupt. It cant be trusted and may not work property
visit this link on another device
g.co/ABH
press power to continue "
please need help, It has been only 12 hours with the device, and I do not have a C to USB adapter to flash anything to the device.
Does bootloader allow you to use adb commands still?
hopesrequiem said:
Does bootloader allow you to use adb commands still?
Click to expand...
Click to collapse
I do not have a USB type C adapter, so I can not use any adb commands with the device.
The "No Commands" happens when I use the volume button to access recovery, as if there was no recovery partition installed
Call Google.
bobby janow said:
Call Google.
Click to expand...
Click to collapse
I would have tried, but the nexus 5 is the only device on the house.
I managed to find a type C cable at my local store (probs the only thing open today) I am going to try to flash a factory image using google's official method.
Any tips would be welcome.
I just checked and my recovery says no commands, I think it always does. To actually get the recovery commands to come up, when you're in recovery, press and hold the power button and then press volume up straightaway. The recovery menu will then come up and I suggest wiping your cache and rebooting. If that fails then u can also factory reset from there.
Sent from my Nexus 5X using Tapatalk
I was not able to flash anything yet.
Hayth said:
I just checked and my recovery says no commands, I think it always does. To actually get the recovery commands to come up, when you're in recovery, press and hold the power button and then press volume up straightaway. The recovery menu will then come up and I suggest wiping your cache and rebooting. If that fails then u can also factory reset from there.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply, when I used your method, a new screen showed up, downloading mode.
Firmware Update
Do not unplug the USB connection until the process is complete.
0%
I tried to adb and fastboot to access the recovery and wipe the cache but no luck.
LeGrassy said:
I was not able to flash anything yet.
Thanks for your reply, when I used your method, a new screen showed up, downloading mode.
Firmware Update
Do not unplug the USB connection until the process is complete.
0%
I tried to adb and fastboot to access the recovery and wipe the cache but no luck.
Click to expand...
Click to collapse
Huh, that is strange.. Sorry to hear it didn't work. Sounds like somethings definitely not quite right, I'd definitely go down the flashing stock images route.. I'm not sure how you can go about unlocking the bootloader though if you haven't already. Now we have the choose the allow oem unlock option in developer options u need to be able to start the phone :/
Sent from my Nexus 5X using Tapatalk
Ok, I uninstall and re-installed all the drivers with SDK tools and I that fixed my fastboot problems.
Now I have to unlock my device, but I can't load the OS, I have the factory image, downloaded from the google developer website.
I have the bullhead LGH790 16GB variant, and downloaded the (MMB29K) 6.01 Marshmallow
The issues as mentioned before is that the OS does not load so I cannot unlock my bootloader.
Is there any way to unlock it to flash a stock rom throught ADB, Fastboot, bootloader, etc?
LeGrassy said:
Ok, I uninstall and re-installed all the drivers with SDK tools and I that fixed my fastboot problems.
Now I have to unlock my device, but I can't load the OS, I have the factory image, downloaded from the google developer website.
I have the bullhead LGH790 16GB variant, and downloaded the (MMB29K) 6.01 Marshmallow
The issues as mentioned before is that the OS does not load so I cannot unlock my bootloader.
Is there any way to unlock it to flash a stock rom throught ADB, Fastboot, bootloader, etc?
Click to expand...
Click to collapse
That my friend is a very good question. I'm curious to hear the solution myself.
Maybe you can try this, adb flash stock recovery, and then load up the recovery like how I mentioned earlier. Then adb sideload this rom, it's completely stock but in zip format. I don't think it flashes the bootloader radio etc but I don't think they've changed since 6.0. If for any reason they have or u wanna flash the stock images thru fastboot to make sure everything's up to date, then u can go about unlocking the bootloader and reflashing the stock image to make sure uv got the right bootloader, radio etc : http://forum.xda-developers.com/showthread.php?t=3267096
Sent from my Nexus 5X using Tapatalk
I think the question is how do I unlock the bootloader if I can't enable developer options since I can't boot into the stock rom? The bootloader command says you can't unlock, thus really you can't do anything like flashing even a stock .img file. How do you bypass that? How are you able to do anything if you can't boot even into stock rom?
I'm not 100% sure if adb sideload needs an unlocked bootloader or not. I know that flashing an OTA thru stock recovery (update via adb) doesn't need an unlocked bootloader, so could be worth trying that if this doesn't work? Obviously gotta make sure you use the right OTA file
Edit: Actually, now that I think about it I think you need a custom recovery to adb sideload. So the only other thing I can think of is trying to flash the same OTA via stock recovery, OTA files can be downloaded here: http://www.droid-life.com/2015/12/09/download-android-6-0-1-marshmallow-updates-for-nexus-devices/
If your stock recovery isn't working properly though and it still just goes into download mode then I'm outta ideas might have to be an RMA to google
Sent from my Nexus 5X using Tapatalk
I extracted all the files from the .tgz I got from the google's website, and tried to flash the recovery ... but I can't really do it.
HTML:
target reported max download size of 536870912 bytes
sending 'recovery' (12509 KB)...
OKAY [ 0.479s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.502s
I am in the phone with google, and their are transferring me to LG, they will probably want me to return the device.
What a Christmas gift I received. The epic hold music is not helping me feel better either
LeGrassy said:
I extracted all the files from the .tgz I got from the google's website, and tried to flash the recovery ... but I can't really do it.
HTML:
target reported max download size of 536870912 bytessending 'recovery' (12509 KB)...OKAY [ 0.479s]writing 'recovery'...FAILED (remote: device is locked. Cannot flash images)finished. total time: 0.502s
I am in the phone with google, and their are transferring me to LG, they will probably want me to return the device.
What a Christmas gift I received. The epic hold music is not helping me feel better either
Click to expand...
Click to collapse
Christmas music?
RMA in process
Edit: "Christmas music? ", it was the classical music you see in the movies when the evil guy is killing innocent people.
Thanks for everybody who replied, you guys were helpful in one way or another.
LG's manufactures warranty said that my problem needed to repaired, the process will take 7-9 business days, if they cannot fix it they would send me a new phone.
Mods; if needed feel free to close this threat. Thanks
There has to be a way to recover from this. All the guides say to do this or that after you boot into rom and allow unlock bootloader. What if you can't get into the rom. Come on guys someone knows what to do. IRC perhaps? All you need to do is unlock the effin' bootloader and you're golden.
---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------
LeGrassy said:
Edit: "Christmas music? ", it was the classical music you see in the movies when the evil guy is killing innocent people.
<snip lol>
the process will take 7-9 business days
Mods; if needed feel free to close this threat. Thanks
Click to expand...
Click to collapse
BS 7-9 business days is ridic. No!
bobby janow said:
There has to be a way to recover from this. All the guides say to do this or that after you boot into rom and allow unlock bootloader. What if you can't get into the rom. Come on guys someone knows what to do. IRC perhaps? All you need to do is unlock the effin' bootloader and you're golden.
---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------
BS 7-9 business days is ridic. No!
Click to expand...
Click to collapse
I'm not BSing she said that they would give me a printing label so I can send it, once they receive the device they will take 7-9 days to repair it and then they would ship. I even made a joke to the customer rep, that in 7-9 days I could find a solution and charge them for my service.
She did not laugh
bobby janow said:
There has to be a way to recover from this. All the guides say to do this or that after you boot into rom and allow unlock bootloader. What if you can't get into the rom. Come on guys someone knows what to do. IRC perhaps? All you need to do is unlock the effin' bootloader and you're golden.
---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------
BS 7-9 business days is ridic. No!
Click to expand...
Click to collapse
yep, all you have to do is unlock the BL, too bad there is no way to do it in this condition. its fairly common knowledge.
bweN diorD said:
yep, all you have to do is unlock the BL, too bad there is no way to do it in this condition. its fairly common knowledge.
Click to expand...
Click to collapse
I did not know that. Very useful information, thanks.
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it. Today I wanted to recover it back to stock (When I got it out of the box) I did a command using fastboot which was along the lines of fastboot boot boot.img but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
PLEASE HELP ME
Issue Solved - 22/01/16
ChiefMustardo said:
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it.
Click to expand...
Click to collapse
Hard to help, if we don't know exactly what you did. Try to explain in detail (or as best you can) the exact steps (including file names, version numbers, etc.) of what you performed.
ChiefMustardo said:
I did a command using fastboot which was along the lines of fastboot boot boot.img
Click to expand...
Click to collapse
Again, hard to tell what the issue is, if we don't know exactly what you did.
Are you sure you didn't do fastboot flash? I don't think you would do anything permanent with the command fastboot boot.
What exactly were you trying to boot/flash with this command? What was the file name, where did you get it from, and what was the exact intent?
Did you get this idea from a thread or guide?
ChiefMustardo said:
but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
Click to expand...
Click to collapse
If you hold power + vol up for a long time (30 seconds or more) does the phone reboot? Then what, black screen again?
Do Power + vol up again. The moment the screen goes dark (but before the HTC logo screen with the red text warning) let go of those buttons, and only hold power down; and don't let go until you see the bootloader screen. If this fails, try again, you probably just got the timing wrong (started pressing vol down too late, or let go of it too early).
Once in bootloader, select fastboot (if not in that mode already) using vol keys, then confirm with power button. Connect to computer and do: fastboot getvar all
Post the getvar output (delete IMEI and serial numbers before you post).
Again, i am really sorry but i do not understand what i did. It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Here is the info:
ChiefMustardo said:
Again, i am really sorry but i do not understand what i did.
Click to expand...
Click to collapse
I seriously doubt that you can't remember any of the steps you did to try to root it.
Just sounds like you are too lazy to type. So why should I put forth more effort than you; when you are the one that wants help?
Describe as best you can, that is all I ask.
ChiefMustardo said:
It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Click to expand...
Click to collapse
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
And you really can't remember if you got this idea from a thread? You had to come up with it somehow.
What were you even trying to do here? What did you think the command would do?
Again, either you are just being lazy, evasive, or got hit on the head to cause amnesia; if you can't answer the questions.
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect. I already new how to unlock the boot-loader because I owned a HTC desire 510. I went back onto my phone it has twrp installed but I use root checker and it says that proper root access is not granted and I have tried to use SuperSU but I got the binary issue so I gave up. It was working fine but today I decided I wanted to revert it back to stock again but did something which completely messed it up.
Also, i decided i wanted to restore it because if it broke and i needed it to be repaired it would void my warranty. I was thinking when i reset the RUU it would make it stock again but it did not.
Now, that's more like it!
ChiefMustardo said:
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect.
Click to expand...
Click to collapse
An Android app, or PC program?
Either way, one-click type root apps don't work on HTC devices. PC based toolkits worked at one time, but were never updated to support the recent software builds (outdated TWRP versions fail on Lollipop, and outdated SuperSU versions fail).
ChiefMustardo said:
S I decided I wanted to revert it back to stock again but did something which completely messed it up.
Click to expand...
Click to collapse
What did you think you were doing with the fastboot command (fastboot boot boot.img)?
One thing I can say for sure: Don't try mods, fastboot commands, etc. unless you know exactly what you are doing (such as following reputable instructions to the letter). The command you did just isn't right. You either got it from a bad source, or you decided to improvise or experiment (really bad idea). You made the issue much worse than it was to begin with (probably just needed to flash the updated SuperSU zip, maybe also update TWRP).
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
You also didn't answer the question:
redpoint73 said:
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
Click to expand...
Click to collapse
It was a computer application and i thought the command would reboot it with a different kernal/firmware thing. But yeah i followed the instructions like an idiot and messed up my phone and no i don't anymore because i deleted it
ChiefMustardo said:
i thought the command would reboot it with a different kernal/firmware thing.
Click to expand...
Click to collapse
Fastboot boot means you are trying to remote boot something without flashing it. A boot.img isn't bootable. I've only seen this done with recovery.img
I think you meant to do: fastboot flash boot boot.img
The one different word makes a huge difference. The action is to flash, not boot. The "boot" is the location of where to flash to.
Also, even if you properly flashed boot.img, this is just the kernel, and wouldn't change much. To return to stock, you want to flash a full ROM. And kernel, ROM and firmware are not interchangeable terms, so don't for a second think they are.
Ok. Is it possible though to revert it back to stock and if yes, do you think you can help me?
Do the fastboot command: fastboot oem lock. Then download the 4.16.401.10 RUU from the following thread, and run it from PC: http://forum.xda-developers.com/showthread.php?t=2701376
Your alternative is to restore the proper stock TWRP backup. While the relevant files are on that same link, you'll find clearer instruction on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
It now says Relocked then underneath security warning. Is that good?
ChiefMustardo said:
It now says Relocked then underneath security warning. Is that good?
Click to expand...
Click to collapse
The security warning just means you altered something in the stock software (root, kernel, etc.). It doesn't matter, as the RUU will write all partitions to factory condition.
Will i have to re unlock the boot-loader for the RUU.exe to work?
ChiefMustardo said:
Will i have to re unlock the boot-loader for the RUU.exe to work?
Click to expand...
Click to collapse
NO. Its required to be LOCKED or RELOCKED to run RUU.
Its the only reason I told you to relock it.
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
ChiefMustardo said:
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
Click to expand...
Click to collapse
What does your PC screen say? Is the RUU stuck sending?
You probably just need to disconnect the phone and start again. RUU just gets stuck sometimes. It shouldn't take any more than 5 or 10 minutes.
Yeah it says updating 0 out of 7 sending ........................
ChiefMustardo said:
Yeah it says sending 0 out of 7
Click to expand...
Click to collapse
It should be safe to just disconnect the phone and start over with the RUU again.
This is what comes up
It send that 1 had been sent then it said error
My Pixel XL is now dead. Won't turn on when pressing or long pressing or long pressing the power button for 5 minutes.
Long pressing the volume down and power button leads to vibration feedback but the screen is black, can't even get to the bootloader.
Last thing before it bricked is browsing through my photos, my phone suddenly froze as usual. And then it powered off automatically. After that, I can't get into the system, neither the bootloader.
Anybody know how to fix hard bricked Pixel?
Thx.
Queentus said:
My Pixel XL is now dead. Won't turn on when pressing or long pressing or long pressing the power button for 5 minutes.
Long pressing the volume down and power button leads to vibration feedback but the screen is black, can't even get to the bootloader.
Last thing before it bricked is browsing through my photos, my phone suddenly froze as usual. And then it powered off automatically. After that, I can't get into the system, neither the bootloader.
Anybody know how to fix hard bricked Pixel?
Thx.
Click to expand...
Click to collapse
try this one here
if not, call harware support for a possible rma
reyscott said:
try this one here
if not, call harware support for a possible rma
Click to expand...
Click to collapse
Won't work cause I can't even get to the bootloader. Thx anyway.
call google support to initiate RMA.
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
CZ Eddie said:
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
Click to expand...
Click to collapse
Thanks for the reply.
My Pixel is already on it's way to RMA.
My Pixel XL shut down this morning. After several attempts to restart, it hung on the Google splash screen. I got into bootloader and tried to reflash OPR3 with flash-all.bat. It got a little ways but quit with “remote: flash write failure”. I got into bootloader again and tried the reflash again. It got the same error earlier in the process and ever since, no button combinations will get it to turn on and I get no lights or battery image when plugged in.
When I plug it into my computer, I get the connection beep from the computer, but no evidence of a connection in Device Manager or in remove media. Since my computer recognizes the phone somehow, is there a way to retrieve data from my phone? I have seen many references to programs that can do this, but I am skeptical. My warranty replacement has been ordered, but I'd like to get whatever I can before it gets here.
Same thing happened to me last night. RMA is on its way, but this month old Pixel XL is dead.
CZ Eddie said:
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
Click to expand...
Click to collapse
do you have an advanced guide to fix it? I have pixel past warranty that has the same problem
JimSmith94 said:
My Pixel XL shut down this morning. After several attempts to restart, it hung on the Google splash screen. I got into bootloader and tried to reflash OPR3 with flash-all.bat. It got a little ways but quit with “remote: flash write failure”. I got into bootloader again and tried the reflash again. It got the same error earlier in the process and ever since, no button combinations will get it to turn on and I get no lights or battery image when plugged in.
When I plug it into my computer, I get the connection beep from the computer, but no evidence of a connection in Device Manager or in remove media. Since my computer recognizes the phone somehow, is there a way to retrieve data from my phone? I have seen many references to programs that can do this, but I am skeptical. My warranty replacement has been ordered, but I'd like to get whatever I can before it gets here.
Click to expand...
Click to collapse
There are 2 things you can try 1.) Go-to you folder where you have adb & fastboot. Download factory zip and unzip into adb & fastboot folder. Plug phone into PC. Open a cmd window that's NOT the administrator one try adb devices, then fastboot reboot bootloader. Click once to advance in cmd, then double click flash-all.bat and let it run through the install process. It will stop a few time, but just ignore, may even spit out an error, just ignore and let it keep installing, it may keep doing this stop and start thing,let it run. It will eventually boot up. It will wipe phone and you will have to do a new phone install. Then you can go into bootloader mode and fastboot twrp and twrp installer and go back and install super su go back and install suhide 109.
When installing TWRP I would recommend the previous version of December 1, I think and not the Dec. 15 version. Same with twrp installer.
The other thing you can try is to (if you can turn phone off) hold down power button for 5 seconds then press volume UP , that should put you in the Android on it's back and say No Command. Then you can use the options given you.
Good luck
fiverings said:
There are 2 things you can try 1.) Go-to you folder where you have adb & fastboot. Download factory zip and unzip into adb & fastboot folder. Plug phone into PC. Open a cmd window that's NOT the administrator one try adb devices, then fastboot reboot bootloader. Click once to advance in cmd, then double click flash-all.bat and let it run through the install process. It will stop a few time, but just ignore, may even spit out an error, just ignore and let it keep installing, it may keep doing this stop and start thing,let it run. It will eventually boot up. It will wipe phone and you will have to do a new phone install. Then you can go into bootloader mode and fastboot twrp and twrp installer and go back and install super su go back and install suhide 109.
When installing TWRP I would recommend the previous version of December 1, I think and not the Dec. 15 version. Same with twrp installer.
The other thing you can try is to (if you can turn phone off) hold down power button for 5 seconds then press volume UP , that should put you in the Android on it's back and say No Command. Then you can use the options given you.
Good luck
Click to expand...
Click to collapse
My post was over three months ago and as I said, I got a refurb replacement, which I have since sold and have a Pixel 2 XL. Guess I should have said that although my computer recognized it, adb didn't. That's why I was asking if there was any other way to retrieve the data. I ended up using a week old backup so it wasn't too bad.
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
---------- Post added at 07:30 PM ---------- Previous post was at 06:53 PM ----------
perfectswanson said:
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
Click to expand...
Click to collapse
I was able to get it to boot into twrp. Should be OK from here. Thank you.
perfectswanson said:
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
---------- Post added at 07:30 PM ---------- Previous post was at 06:53 PM ----------
I was able to get it to boot into twrp. Should be OK from here. Thank you.
Click to expand...
Click to collapse
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
I'm sorry I should have responded sooner. I don't remember much, but I had a feeling that it was still running because it was warm so I left it alone for a couple hours to see if it would die and then I could try to boot it again it's exactly what I did but what was funny was that it still had battery life when I turned it back on I hope you had some some luck.
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
Son of a gun. I did it again! Today. I followed a guide telling me to uninstall magisk with twrp before flashing 9.0. Now I have the same problem again. Goddamn TWRP. It told me no OS installed. Then I realized I forgot to put the magisk uninstaller file on my Verizion Pixel XL. Last time I just let my phone sit for a few hours or so, and it boot again. Not sure if it needs to run out of power, so it can boot again or what. Do you remember what you did when it happened to you?
perfectswanson said:
Son of a gun. I did it again! Today. I followed a guide telling me to uninstall magisk with twrp before flashing 9.0. Now I have the same problem again. Goddamn TWRP. It told me no OS installed. Then I realized I forgot to put the magisk uninstaller file on my Verizion Pixel XL. Last time I just let my phone sit for a few hours or so, and it boot again. Not sure if it needs to run out of power, so it can boot again or what. Do you remember what you did when it happened to you?
Click to expand...
Click to collapse
I couldnt switch it on at all. I'm planning to take it to Ubreakifix store, I guess they are the official google pixel repair people.
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
nikinnikin said:
I couldnt switch it on at all. I'm planning to take it to Ubreakifix store, I guess they are the official google pixel repair people.
Click to expand...
Click to collapse
You gotta be kidding me. Last time I left the phone alone, and my hunch was that it would run out of power, and then you can atleast get into the bootloader. I fixed it before. I wish I could get a hold of software those guys use to repartition, or however they do it. We have Pixel 3 leaks, but no repair software. All I did was install TWRP, and it said no OS installed. It just kept booting up into TWRP. Then I switched slots to see if that would change it, but I think that might have been what screwed it up.
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
What version of TWRP did you use?
---------- Post added at 01:50 PM ---------- Previous post was at 01:37 PM ----------
I just got back into the bootloader. After a dozen times I just held down and power for like five seconds. Should I try recovery and try to remove Magisk, or should I just try to flash 9.0?
---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------
What I did this time that was different, and I don't know if this is what helped or what, but this time I plugged in headphones and held power and vol down.
Putting the headphones in worked, or maybe it was just a fluke, but it worked on the first try. I got into Bootloader, "fastboot boot twrp.img", then I flashed the magisk uninstaller zip, the booted back to bootloader, and did flash-all.bat. It said it failed on the vendor partition, but everything still works.
How do you access EDL mode on this device? Fastboot oem blankflash does not work. It only returns a denied message. If your wondering why I need access to this mode it's so I can fix my baseband. I read somewhere here on xda that doing so may help me get the original baseband back.
Also require access to EDL mode, but can't find a way.
I have the same question...
Deep flash cables don't seem to work, although I just learned that I need to check the "ports" section of Windows device manager and not simply expect it to pop up like a new device normally would.
My G7 Play isn't bricked.
Not rooted, and no TWRP installed either.
I need to figure out a way to make a full disk image without destroying the data already present.
The options theoretically possible seem to be:
1. Root via exploit - I'm currently exploring the viability of privilege escalation from Ubuntu installed in Termux
2. Unlock the bootloader without formatting anything - Guides do exist for other phones, but I only get one chance to get this avenue right.
3. Enter EDL mode and backup the entire disk using Qualcomm's own software. - The easiest way (on paper), but the method to put this phone in EDL mode continues to elude me.
I'm aware of the typical three ways to get a Qualcomm device in EDL mode without bricking it...
Deep flash cable - doesn't seem to work, but I'll try again with freshly aquired knowledge.
ADB/fastboot command - I've tried all of them native to my device, and a few that were added from guides about other devices
JTAG "pins" - much more like pads than pins...
Can't find diddly about 'em.
Don't know if they exist on a G7 Play, or which two to short to each other if they are even there.
Anyone have a potential solution that i may have overlooked?
Not sure if this is what you need or not but here's s link for a PDF file that's chock fill of nerd stuff (schematics/pinouts/etc) regarding the g7 play (-4 variant, I think)
The term JTAG hits like 13 times so it might hey you in the right direction at least.
[Google drive]/file/d/15aZddF1RALQyjJ9hUI4nTYLewYSa9ERY/view?usp=drivesdk
(I've been a member forever but this is my first post. Not sure if I can post links or not so just replace the above with drive.goog...etc...)
If you have any problems with the link PM me and we'll sort it out.
Good luck.
travis.mcgaw said:
Not sure if this is what you need or not but here's s link for a PDF file that's chock fill of nerd stuff (schematics/pinouts/etc) regarding the g7 play (-4 variant, I think)
The term JTAG hits like 13 times so it might hey you in the right direction at least.
[Google drive]/file/d/15aZddF1RALQyjJ9hUI4nTYLewYSa9ERY/view?usp=drivesdk
(I've been a member forever but this is my first post. Not sure if I can post links or not so just replace the above with drive.goog...etc...)
If you have any problems with the link PM me and we'll sort it out.
Good luck.
Click to expand...
Click to collapse
You need 10 posts to share links
Clickable link
https://drive.google.com/file/d/15aZddF1RALQyjJ9hUI4nTYLewYSa9ERY/view
Sent from my ali using XDA Labs
How to over think the simple things?
Thanks for the input gentlemen,
I'll hang on to the literature for future reference.
Turns out that I was wayyyyyyyy over thinking it.
Motorola's adb and fastboot commands (particularly on Qualcomm socs) is highly contextual.
When the documentation said 'adb reboot edl' that's what it meant.
Not from the booted os though.....
From recovery (SMH).
Simple as that for anyone else who's trying to take a full disk image without unlocking their bootloader
I think I'll still pursue a root exploit via termux though.
It could help a lot of folks out who don't have a solid root solution (Samsung users).
I'm too close to just forget about it anyway.
Seems to be working out like the old adb temp root, but with the possibility of automating the process into something less cumbersome.
Select slot_b from TWRP, then reboot into fastboot. You'll brick and go into EDL. I just did it last night on accident.
ok so i have the xt1952-t variant i have no stock recovery ive flashed in fastboot stock android 10 rom (XT1952-T_CHANNEL_RV_9.0_PCYS29.148-154-8_cid21_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml) everything flashed fine but it wont boot it says no baseband and ro.full build is blank. everytime it says unable to read non-hlos and kicks me back to fastboot. also bootloader is locked still i have my unique key but without being able to boot to os i cant toggle oem unlock..... this has been so frustrating. I believe i need to blank flash the device but cant get to edl.... can somebody tell my noob @$$ how to fix this thing? its my friends device i think he issued an erase all command. ive tried oem config fsg-id tmo and oem config carrier tmo both say ok but nothing fixes it.....please sos. Thanks in advance.
EDIT* Got it to boot to stock recovery after all thanks
---------- Post added at 09:36 AM ---------- Previous post was at 09:12 AM ----------
when you say "adb reboot edl" from recovery do you mean adb sideload? didnt work for me help please?
chrisdsj said:
ok so i have the xt1952-t variant i have no stock recovery ive flashed in fastboot stock android 10 rom (XT1952-T_CHANNEL_RV_9.0_PCYS29.148-154-8_cid21_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml) everything flashed fine but it wont boot it says no baseband and ro.full build is blank. everytime it says unable to read non-hlos and kicks me back to fastboot. also bootloader is locked still i have my unique key but without being able to boot to os i cant toggle oem unlock..... this has been so frustrating. I believe i need to blank flash the device but cant get to edl.... can somebody tell my noob @$$ how to fix this thing? its my friends device i think he issued an erase all command. ive tried oem config fsg-id tmo and oem config carrier tmo both say ok but nothing fixes it.....please sos. Thanks in advance.
EDIT* Got it to boot to stock recovery after all thanks
---------- Post added at 09:36 AM ---------- Previous post was at 09:12 AM ----------
when you say "adb reboot edl" from recovery do you mean adb sideload? didnt work for me help please?
Click to expand...
Click to collapse
How did you get??
dmferrer89 said:
How did you get??
Click to expand...
Click to collapse
I honestly dont remember bro. ive moved a few times and i dont have that phone anymore, i did successfully fix it though. im working on xt2131-1 now.
LeeSylva said:
How to over think the simple things?
Thanks for the input gentlemen,
I'll hang on to the literature for future reference.
Turns out that I was wayyyyyyyy over thinking it.
Motorola's adb and fastboot commands (particularly on Qualcomm socs) is highly contextual.
When the documentation said 'adb reboot edl' that's what it meant.
Not from the booted os though.....
From recovery (SMH).
Simple as that for anyone else who's trying to take a full disk image without unlocking their bootloader
I think I'll still pursue a root exploit via termux though.
It could help a lot of folks out who don't have a solid root solution (Samsung users).
I'm too close to just forget about it anyway.
Seems to be working out like the old adb temp root, but with the possibility of automating the process into something less cumbersome.
Click to expand...
Click to collapse
You can't reboot to EDL from recovery using the phones interface nor ADB if in sideload mode etc. This just isn't possible.
There are a lot of custom made ADB versions out there other than the stock platform tools. These other ones contain special commands for various brands that support them. I do know these will work but unfortunately only testpoints, bricking, or like smoeone said possibly changing configuration of boot are the only ways to get into EDL I can think of.
I never could get motorolas into EDL switching between slots and such with TWRP.
Spaceminer said:
Select slot_b from TWRP, then reboot into fastboot. You'll brick and go into EDL. I just did it last night on accident.
Click to expand...
Click to collapse
Seriously? That's odd. What build? I could never achieve this (didn't try intentionaly either) . Every time I would do as you explain for testing purposes my phone would simply reboot to TWRP or back to slot a. This is with majority of motorolas i have with slots and with no configuration changed by me.
fastboot oem blankflash