[Q] - HTC One softbricked, all options found have failed - One (M7) Q&A, Help & Troubleshooting

Hey guys,
So I wasn't paying attention while trying to restore my HTC One to stock. I ended up formatting and erasing all data on the entire phone. It has no OS now. Here's what I am ABLE to do:
Boot into Bootloader and Fastboot
Access TWRP Recovery
HTC Dev Lock and Re-Lock
Here's what I am UNABLE to do:
Sideloading ADB is unavailable due to error messages stating Unable to mount <partition> and every partition is unable to mount.
I have tried to mount the partitions within TWRP, this doesn't work.
Achieve S-Off
I just need to get the phone back to some type of working order so that I can sideload a ROM over or fastboot a fully stock zip. Can anybody help me here? I've seen very similar issues all over the forums, all of the problems they encountered could be fixed by ADB sideloading a ROM, again, I cannot access ADB sideloading.

Sidkain said:
Hey guys,
So I wasn't paying attention while trying to restore my HTC One to stock. I ended up formatting and erasing all data on the entire phone. It has no OS now. Here's what I am ABLE to do:
Boot into Bootloader and Fastboot
Access TWRP Recovery
HTC Dev Lock and Re-Lock
Here's what I am UNABLE to do:
Sideloading ADB is unavailable due to error messages stating Unable to mount <partition> and every partition is unable to mount.
I have tried to mount the partitions within TWRP, this doesn't work.
Achieve S-Off
I just need to get the phone back to some type of working order so that I can sideload a ROM over or fastboot a fully stock zip. Can anybody help me here? I've seen very similar issues all over the forums, all of the problems they encountered could be fixed by ADB sideloading a ROM, again, I cannot access ADB sideloading.
Click to expand...
Click to collapse
U can use a USB OTG cable. Download ARHD(or any rom of ur choice), copy it to a USB. then using the OTG cable, u can flash the rom from TWRP. Once u have a working OS, continue with the RUU process

One other note, I have downloaded two different instances of the shipped ROM for this phone. When trying to "fastboot update update.zip" on either of them, I get the following error message and a failure to update:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt

Sidkain said:
One other note, I have downloaded two different instances of the shipped ROM for this phone. When trying to "fastboot update update.zip" on either of them, I get the following error message and a failure to update:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Click to expand...
Click to collapse
start by posting a "fastboot getvar all" (excluding IMEI and s/n) and what version number of TWRP you're using

your probably just using an outdated twrp version, flash 2.6.3.3 and then retry sideloading

I am in the exact same situation. Phone literally ground to a halt last night, so rebooted it and it got stuck in a boot loop. Phone isn't rooted, it wasn't unlocked at the time (it is now, since I've been trying to fix it for the past day) and I literally have no idea how to fix it. Although I think my situation is worse, I can't access anything else other than the bootloader...
I've tried RUU (which I can't do because I'm not S-Off and I'm on hboot 1.45)
I've tried just flashing a new recovery (but whenever I try to enter the recovery it gets stuck saying 'Entering Recovery' then the phone goes back into the boot loop)
Like literally the only thing I have access to is the bootloader, everything else sends it into a boot loop, hell I can't even format or flash imgs (apart from recovery imgs) without fastboot giving me an error message.
I fear the phone is completely ****ed, and this has come out of completely nowhere. Except now that I've unlocked the bootloader to try and fix it, it says TAMPERED and UNLOCKED which means I WONT GET A REPAIR...

glaringradio said:
I am in the exact same situation. Phone literally ground to a halt last night, so rebooted it and it got stuck in a boot loop. Phone isn't rooted, it wasn't unlocked at the time (it is now, since I've been trying to fix it for the past day) and I literally have no idea how to fix it. Although I think my situation is worse, I can't access anything else other than the bootloader...
I've tried RUU (which I can't do because I'm not S-Off and I'm on hboot 1.45)
I've tried just flashing a new recovery (but whenever I try to enter the recovery it gets stuck saying 'Entering Recovery' then the phone goes back into the boot loop)
Like literally the only thing I have access to is the bootloader, everything else sends it into a boot loop, hell I can't even format or flash imgs (apart from recovery imgs) without fastboot giving me an error message.
I fear the phone is completely ****ed, and this has come out of completely nowhere. Except now that I've unlocked the bootloader to try and fix it, it says TAMPERED and UNLOCKED which means I WONT GET A REPAIR...
Click to expand...
Click to collapse
have you tried to fastboot erase cache after flashing recovery

xnknown said:
have you tried to fastboot erase cache after flashing recovery
Click to expand...
Click to collapse
Yep, it still just hangs on "Entering Recovery" before rebooting and entering the boot loop again...
I'm fearing that this phone is just completely doomed now

glaringradio said:
Yep, it still just hangs on "Entering Recovery" before rebooting and entering the boot loop again...
I'm fearing that this phone is just completely doomed now
Click to expand...
Click to collapse
then you may want to try flashing an older version of twrp

xnknown said:
then you may want to try flashing an older version of twrp
Click to expand...
Click to collapse
I have tried, no matter what version I flash it still does not let me get beyond "Entering Recovery"

glaringradio said:
I have tried, no matter what version I flash it still does not let me get beyond "Entering Recovery"
Click to expand...
Click to collapse
try all three
fastboot erase cache
fastboot erase system
fastboot erase data

glaringradio said:
I have tried, no matter what version I flash it still does not let me get beyond "Entering Recovery"
Click to expand...
Click to collapse
1- are you sure you're using the correct recovery for your phone (e.g. M7_U/UL vs Sprint!!)
2- have you checked MD5 of the download, to make sure it's not corrupt; TWRP site doesn't play nice with download managers, so please check MD5

xnknown said:
try all three
fastboot erase cache
fastboot erase system
fastboot erase data
Click to expand...
Click to collapse
Cache is fine, it erases properly
I get "FAILED (remote: not allowed)" when I try to erase system or data
I have tried flashing every single img from the official TeamWin projects site (the ones that look like openrecovery-twrp-2.6.3.3-m7.img) and absolutely none of them work. They all say "Okay" as if they flash correctly, however when I select to go into recovery from bootloader, it brings up "Entering Recovery" then reboots and goes back into the boot loop

glaringradio said:
Cache is fine, it erases properly
I get "FAILED (remote: not allowed)" when I try to erase system or data
I have tried flashing every single img from the official TeamWin projects site (the ones that look like openrecovery-twrp-2.6.3.3-m7.img) and absolutely none of them work. They all say "Okay" as if they flash correctly, however when I select to go into recovery from bootloader, it brings up "Entering Recovery" then reboots and goes back into the boot loop
Click to expand...
Click to collapse
nkk is right is ur phone a sprint or verizon?

xnknown said:
nkk is right is ur phone a sprint or verizon?
Click to expand...
Click to collapse
It's an international (I'm with the operator 3 in the UK)

glaringradio said:
It's an international (I'm with the operator 3 in the UK)
Click to expand...
Click to collapse
have you checked MD5?

glaringradio said:
It's an international (I'm with the operator 3 in the UK)
Click to expand...
Click to collapse
hmmm that is really wierd lol, the only other thing I can think of is updating your firmware and hboot to the latest and then reflash twrp and erase cache

xnknown said:
hmmm that is really wierd lol, the only other thing I can think of is updating your firmware and hboot to the latest and then reflash twrp and erase cache
Click to expand...
Click to collapse
i hate to be insistent, but has he checked MD5?

nkk71 said:
have you checked MD5?
Click to expand...
Click to collapse
I have, I literally have no idea as to why they aren't working...
xnknown said:
hmmm that is really wierd lol, the only other thing I can think of is updating your firmware and hboot to the latest and then reflash twrp and erase cache
Click to expand...
Click to collapse
My hboot is currently on 1.55, is that not the latest? The phone was on 4.3, and it literally just started boot looping out of absolutely nowhere. This sucks so much and I have no idea how to fix it and can't find anybody who can
When I try to flash a different hboot, I get the error "FAILED (remote: 99 unknown fail)".
Again, MD5s on the TWRP files I downloaded are fine. All I can do is use fastboot to varying degrees of success, and nothing works when I try to use RUU... It's a soft brick, but it's completely and utterly broken and I can't see any way to recover it (and I can't send it for repair since it is now marked as tampered)

glaringradio said:
I have, I literally have no idea as to why they aren't working...
My hboot is currently on 1.55, is that not the latest? The phone was on 4.3, and it literally just started boot looping out of absolutely nowhere. This sucks so much and I have no idea how to fix it and can't find anybody who can
Click to expand...
Click to collapse
and 1 more try: have you checked MD5?

Related

[Q] Possibly bricked? It would be awesome if someone could help

Hi Xda
Forgive me for what you are about to read, as I have carried out some dumb ### noobness:
I was running Sinless 5.1Gpe rom (great rom) anyways I wanted to return to a sense based rom so decided to go for ARHD 40.2 fter reading a number of posts mentioning doing a complete wipe of the phone including SDCARD. I checked the process of pushing via adb and all seemed simple enough.
I initially did a test and it pushed the file, so then i carried out the complete wipe (no OS, no rom on sd card to flash). I then tried to push the rom and it failed. I tried a number of different ways sideload too.
I managed to get the rom to push in the end using the lastest TWRP of which it would not allow me to do rom failed to flash...
Now this is the stupid part, TWRP became unresponsive, and every time I tried to boot into recovery it would kick me out to the spash screen and bootloop. I did the fastboot erase cache without any success.
I managed to switch to CWM but could not mount anything so came across a post about switching to stock....This is the really stupid part. I flashed a stock recovery and also I now have a relocked bootloader.
Is this phone now bricked??
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
I will get there said:
Now this is the stupid part, TWRP became unresponsive, and every time I tried to boot into recovery it would kick me out to the spash screen and bootloop. I did the fastboot erase cache without any success.
I managed to switch to CWM but could not mount anything so came across a post about switching to stock....This is the really stupid part. I flashed a stock recovery and also I now have a relocked bootloader.
Is this phone now bricked??
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
Click to expand...
Click to collapse
How did you unlock the first time? HTCDev or S-OFF?
Can you post the error you get when you try to unlock?
I will get there said:
Hi Xda
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
Click to expand...
Click to collapse
if you have s-off you should flash back a custom recovery:
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY, and adb should be working again,
use this to unlock your phone: http://forum.xda-developers.com/showthread.php?t=2475914
there's also a handy Guru Bootloader Reset (flashable zip): http://forum.xda-developers.com/showthread.php?t=2527194
but it needs either CWM 6.0.3.2+, or TWRP 2.6.3.3+ to work.
or even "revone -u"
I will get there said:
Hi Xda
Forgive me for what you are about to read, as I have carried out some dumb ### noobness:
I was running Sinless 5.1Gpe rom (great rom) anyways I wanted to return to a sense based rom so decided to go for ARHD 40.2 fter reading a number of posts mentioning doing a complete wipe of the phone including SDCARD. I checked the process of pushing via adb and all seemed simple enough.
I initially did a test and it pushed the file, so then i carried out the complete wipe (no OS, no rom on sd card to flash). I then tried to push the rom and it failed. I tried a number of different ways sideload too.
I managed to get the rom to push in the end using the lastest TWRP of which it would not allow me to do rom failed to flash...
Now this is the stupid part, TWRP became unresponsive, and every time I tried to boot into recovery it would kick me out to the spash screen and bootloop. I did the fastboot erase cache without any success.
I managed to switch to CWM but could not mount anything so came across a post about switching to stock....This is the really stupid part. I flashed a stock recovery and also I now have a relocked bootloader.
Is this phone now bricked??
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
Click to expand...
Click to collapse
If you can get to the stock recovery press volume up then power button and quickly release both buttons and you should be in stock recovery. From here you should be able to follow any of the posted steps to flash a RUU back to pure stock.
solbirn said:
How did you unlock the first time? HTCDev or S-OFF?
Can you post the error you get when you try to unlock?
Click to expand...
Click to collapse
Hi thanks for your response, I initially HTCDev then rumrunner to gain s-off.
The error I get is:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Michael\Desktop\Adb And Fastboot>fastboot flash unlocktoken Unlock_code
.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
C:\Users\Michael\Desktop\Adb And Fastboot>
nkk71 said:
if you have s-off you should flash back a custom recovery:
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY, and adb should be working again,
use this to unlock your phone: http://forum.xda-developers.com/showthread.php?t=2475914
there's also a handy Guru Bootloader Reset (flashable zip): http://forum.xda-developers.com/showthread.php?t=2527194
but it needs either CWM 6.0.3.2+, or TWRP 2.6.3.3+ to work.
or even "revone -u"
Click to expand...
Click to collapse
Hey thanks for your response
I cant flash custom recovery the error i get is similar to trying to unlock.(above)
I cannot also use that thread because I cannot access adb (even though my phone recognises fastboot in device manager, when I go to what is now stock recovery is disappears from device manager)
I have no OS so cannot open up emulator for revone.
loughary said:
If you can get to the stock recovery press volume up then power button and quickly release both buttons and you should be in stock recovery. From here you should be able to follow any of the posted steps to flash a RUU back to pure stock.
Click to expand...
Click to collapse
Hey thanks for responding
I can get into stock android recovery(3e) it enters after notifying me that it failed to mount sd card 5 times then finishes with cannot mount sdcard (no such file or directory)
then finally write host_mode:0 done
any further suggestions?
I will get there said:
Hi thanks for your response, I initially HTCDev then rumrunner to gain s-off.
The error I get is:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Michael\Desktop\Adb And Fastboot>fastboot flash unlocktoken Unlock_code
.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
C:\Users\Michael\Desktop\Adb And Fastboot>
Hey thanks for your response
I cant flash custom recovery the error i get is similar to trying to unlock.(above)
I cannot also use that thread because I cannot access adb (even though my phone recognises fastboot in device manager, when I go to what is now stock recovery is disappears from device manager)
I have no OS so cannot open up emulator for revone.
Hey thanks for responding
I can get into stock android recovery(3e) it enters after notifying me that it failed to mount sd card 5 times then finishes with cannot mount sdcard (no such file or directory)
then finally write host_mode:0 done
any further suggestions?
Click to expand...
Click to collapse
You're getting "cannot load"? That just means the filename is wrong, as simple as that. If ur on Windows, check for .img.img (double extension)
Sent from my HTC One using Tapatalk
nkk71 said:
You're getting "cannot load"? That just means the filename is wrong, as simple as that. If ur on Windows, check for .img.img (double extension)
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks @nkk71
I now have an unlocked bootloader
I have also now flashed CWM 6.0.4.5 however I still do not have adb available. The difference now is fastboot is recognised in device manager as before but when I boot into CWM instead of it dissapearing, it moves to 'other devices' one (with yellow exclamation) I know it did this before because of drivers not being installed/recognised but I have htc sync manager installed which in theory has installed the drivers??!
Anything else I can try without adb?
Again many thanks for your assistance, I see you in a number of threads helping people...top bloke!
Further update
I downgraded my hboot back to 1.55 and now TRWP is now functioning, I have now pushed a rom to the phone, however flash fails due to "unable to mount to internal storage"
Is there a fix for this?
Many thanks
I will get there said:
Further update
I downgraded my hboot back to 1.55 and now TRWP is now functioning, I have now pushed a rom to the phone, however flash fails due to "unable to mount to internal storage"
Is there a fix for this?
Many thanks
Click to expand...
Click to collapse
I suggest that you downgrade to Hboot 1.44, keep the bootloader locked and run the 1.28.401.7 RUU to be completely stock. Then its up to you whether you re staying stock or flashing sth custom.
Ivanovic said:
I suggest that you downgrade to Hboot 1.44, keep the bootloader locked and run the 1.28.401.7 RUU to be completely stock. Then its up to you whether you re staying stock or flashing sth custom.
Click to expand...
Click to collapse
Thanks @Ivanovic
I have since moved on a little further, i have now managed to push a rom via sideload, when i then go to flash it says:
Updating partion details....
E:unable to open zip file.
Error flashing zip /sdcard/sideload.zip
updating partition..details
failed
do you know a workaround this, if not could you direct me to a page with both hboot 1.44 and the RUU please
I will get there said:
Thanks @Ivanovic
I have since moved on a little further, i have now managed to push a rom via sideload, when i then go to flash it says:
Updating partion details....
E:unable to open zip file.
Error flashing zip /sdcard/sideload.zip
updating partition..details
failed
do you know a workaround this, if not could you direct me to a page with both hboot 1.44 and the RUU please
Click to expand...
Click to collapse
IF you re flashing a 4.4 ROM then use TWRP 2.6.3.3 or latest CWM
IF you re flashing a 4.3/4.2 ROM then use TWRP 2.6.3.0 or older CWM
Link for the RUU http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
I will get there said:
Thanks @Ivanovic
I have since moved on a little further, i have now managed to push a rom via sideload, when i then go to flash it says:
Updating partion details....
E:unable to open zip file.
Error flashing zip /sdcard/sideload.zip
updating partition..details
failed
do you know a workaround this, if not could you direct me to a page with both hboot 1.44 and the RUU please
Click to expand...
Click to collapse
http://www.htc1guru.com/downloads/ruu-file-downloads/
I had to use the exe version to get it working when I had a similar issue.
Sent from my One using Tapatalk
Yes there is a fix. Install stock recovery. Go to bootloader and select factory reset. It will go to stock recovery and do it's thing and should go into a Bootloop . install custom recovery you should be good
Hi All
Just a quick note, to say all back up and running, thanks for all the respondants who helped.
I wanted add how i got it up and running, so if anyone has similar issues they can use it:
I believe the biggest culprit was the newest Firmware and TWRO 2.3.3.3 in which it did not want to load.
I downgraded by Hboot to firmware 3.xxx and then flashed TWRP 2.3.3.0 and it let me in instead of kicking me out to a bootloop.
I then had access to ADB sideload, which did not work for me in the 1st instance that led me to my problem, This i believe was due to not having the lastest SDK.(upgrade this).
Make sure the Rom you are pushing works well for that downgraded firmware i.e. a solid 4.3 based rom in my case.
Also to note I wiped my external SD card and was unable to mount this to flash, let TWRP sort this by doing a factory reset prior to flashing.
Hope this helps anyone who experienced similar symptoms to me.

Stock RUU need help

Hello. im new here and i ive just bricked my phone , and i wana get back to stock RUU and i dont know whick RUU to download anny sollutions how to check what RUU do i need? Ps.sorry for my bad english. Anny help would be awesome
ubas98 said:
Hello. im new here and i ive just bricked my phone , and i wana get back to stock RUU and i dont know whick RUU to download anny sollutions how to check what RUU do i need? Ps.sorry for my bad english. Anny help would be awesome
Click to expand...
Click to collapse
post the ouput of "fastboot getvar all" except the IMEI and SERIALNO so we can help you determine which RUU you can use if any available for your phone.
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP -v32.120.274.0909
OS-5.16.161.2 eMMC-boot 2048MB
Ive writed everything that i saw on my screen.if i mised anything please tell me
ubas98 said:
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP -v32.120.274.0909
OS-5.16.161.2 eMMC-boot 2048MB
Ive writed everything that i saw on my screen.if i mised anything please tell me
Click to expand...
Click to collapse
that's not your fastboot getvar all, however, the most important part is there which is your OS number, 5.16.161.2 is Vodafone, there is no RUU for your device, do you not have a backup ? how did you brick ?
Seanie280672 said:
that's not your fastboot getvar all, however, the most important part is there which is your OS number, 5.16.161.2 is Vodafone, there is no RUU for your device, do you not have a backup ? how did you brick ?
Click to expand...
Click to collapse
well ive wanted to get to stock so i unlocked my bootloader and tried to install ruu but it failed. and because i locked the bootloader ive somehow bricked my phone one cm11 loading screen. ive unlocked my bootloader and my recovery was all mesed up it couldnt load anny storage so i cant instal other rooms so im stuck here .i have no clue what to do
ubas98 said:
well ive wanted to get to stock so i unlocked my bootloader and tried to install ruu but it failed. and because i locked the bootloader ive somehow bricked my phone one cm11 loading screen. ive unlocked my bootloader and my recovery was all mesed up it couldnt load anny storage so i cant instal other rooms so im stuck here .i have no clue what to do
Click to expand...
Click to collapse
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Seanie280672 said:
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Click to expand...
Click to collapse
well everything worked but when i enter recovery mode it askes me a pasword and i dont know it anny solution?
ubas98 said:
well everything worked but when i enter recovery mode it askes me a pasword and i dont know it anny solution?
Click to expand...
Click to collapse
password ? never seen that before, could you post a photo of it ?
Seanie280672 said:
password ? never seen that before, could you post a photo of it ?
Click to expand...
Click to collapse
http://postimg.org/image/ucolu3a83/ here is the img
ubas98 said:
http://postimg.org/image/ucolu3a83/ here is the img
Click to expand...
Click to collapse
I have never seen that before in all my years of using TWRP, maybe one of the other guys can help you with that
Seanie280672 said:
I have never seen that before in all my years of using TWRP, maybe one of the other guys can help you with that
Click to expand...
Click to collapse
maybe i could use another recovery .if yes anny what is other best recovery?
ubas98 said:
maybe i could use another recovery .if yes anny what is other best recovery?
Click to expand...
Click to collapse
oh somehow the pasword screen went out and now im in the recovery in which folder i could trasfer my rom to the phone?
ubas98 said:
oh somehow the pasword screen went out and now im in the recovery in which folder i could trasfer my rom to the phone?
Click to expand...
Click to collapse
adb push it straight to the sdcard, make sure your phone is plugged into the computer and the rom is in the same folder as adb and fastboot files, then issue this command:
Code:
adb push (name of rom).zip /sdcard/
it will look like its not doing anything but will let you know when its done, then uplug your phone before flashing the rom.
and both TWRP and CWM have their good points, you need CWM to flash AOSP rom's and TWRP to flash sense rom's
Seanie280672 said:
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Click to expand...
Click to collapse
Strangely this is exactly the position I'm in today too.
I wanted to revert to stock after trying cyanogen, relocked the bootloaded and tried to run an RUU. However it stopped with an 'unknown error'. So I tried to push a zip file to it but the adb can't connect to the device and the phone isn't showing up in the device manager (because it's in boot mode?).
I then tried your advice about twrp and tried a different RUU but still get an unknown error and still can't push to the device.
Any ideas of what to try next? My OS is now showing as empty, there was something there previously.
I figured it was time to get some help before I broke things any more.
SGSII_LEDnotify said:
Strangely this is exactly the position I'm in today too.
I wanted to revert to stock after trying cyanogen, relocked the bootloaded and tried to run an RUU. However it stopped with an 'unknown error'. So I tried to push a zip file to it but the adb can't connect to the device and the phone isn't showing up in the device manager (because it's in boot mode?).
I then tried your advice about twrp and tried a different RUU but still get an unknown error and still can't push to the device.
Any ideas of what to try next? My OS is now showing as empty, there was something there previously.
I figured it was time to get some help before I broke things any more.
Click to expand...
Click to collapse
first thing to do is unlock your bootloader again, if you've not already done that, then get TWRP 2.6.3.3 recovery on there, that maybe a problem though as your phone isn't showing in device manager.
So put your phone into the bootloader and see what device manager says then, it should say something if its detecting your phone, even if drivers arnt installed.
also, which HBOOT are you on ? and which Windows OS are you using ?
Seanie280672 said:
first thing to do is unlock your bootloader again, if you've not already done that, then get TWRP 2.6.3.3 recovery on there, that maybe a problem though as your phone isn't showing in device manager.
So put your phone into the bootloader and see what device manager says then, it should say something if its detecting your phone, even if drivers arnt installed.
also, which HBOOT are you on ? and which Windows OS are you using ?
Click to expand...
Click to collapse
I think I've unlocked the bootloader again, fastboot is available and it's showing 'unlocked' at the top. twrp is on there too and I've done the wipe again. The fastboot commands work but pushing doesn't
error: device not found
HBOOT is 1.55.0000 / win7 64 home
Btw Twrp said it couldn't find cache but the wipe was successful.
Thanks for the help.
SGSII_LEDnotify said:
I think I've unlocked the bootloader again, fastboot is available and it's showing 'unlocked' at the top. twrp is on there too and I've done the wipe again. The fastboot commands work but pushing doesn't
error: device not found
HBOOT is 1.55.0000 / win7 64 home
Btw Twrp said it couldn't find cache but the wipe was successful.
Thanks for the help.
Click to expand...
Click to collapse
ok I see what your saying now, what you need to do is boot into TWRP, main screen only, no sub menu's, at that point is your phone still detected in device manager ?
if so then............
put the rom you want to flash in the same folder as adb and fastboot files on your computer, then type:
Code:
adb push (name of rom).zip /sdcard/
you cant push files to your phone using fastboot or whilst its in the bootloader, that's strictly for flashing simple files like Radio's, HBOOTS, recoveries.
Seanie280672 said:
ok I see what your saying now, what you need to do is boot into TWRP, main screen only, no sub menu's, at that point is your phone still detected in device manager ?
if so then............
put the rom you want to flash in the same folder as adb and fastboot files on your computer, then type:
Code:
adb push (name of rom).zip /sdcard/
you cant push files to your phone using fastboot or whilst its in the bootloader, that's strictly for flashing simple files like Radio's, HBOOTS, recoveries.
Click to expand...
Click to collapse
Well at least I've got something in the device manager even if it is a SAMSUNG Android Phone and not my HTC!
The push command hasn't brought up an error, the cursor is just flashing on the next line. It appears to be doing nothing like you said. So I guess I'm playing the waiting game for ten minutes or so. Will there be a notification when it's completed?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
Ok, transfer complete
SGSII_LEDnotify said:
Well at least I've got something in the device manager even if it is a SAMSUNG Android Phone and not my HTC!
The push command hasn't brought up an error, the cursor is just flashing on the next line. It appears to be doing nothing like you said. So I guess I'm playing the waiting game for ten minutes or so. Will there be a notification when it's completed?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
Ok, transfer complete
Click to expand...
Click to collapse
ok, unplug your phone, then goto install and select the rom from the list you just pushed, follow the Aroma options and instructions and also id recommend when given the option, to wipe data.
Seanie280672 said:
ok, unplug your phone, then goto install and select the rom from the list you just pushed, follow the Aroma options and instructions and also id recommend when given the option, to wipe data.
Click to expand...
Click to collapse
I renamed the zip file because there were spaces in the name causing errors, would that cause a failure when trying to install?
skipping MD5 check: no md5 file found
Error flashing zip '/sdcard/****.zip'
updating partition details
failed

HTC one M7 cant restore :(

Hello everyone, im new to these forums (and new to android) so nice to meet you all!
so i got this htc one m7 from a friend, he said he deleted the internal storage and he cant boot up android anymore.
thought might as well give it a try to fix it.
i tried everything in this thread http://forum.xda-developers.com/showthread.php?t=2258809 but it didnt work.
im getting a fail on the last step when it checks signatures.
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
after some surfing on the forums i found out that i need S-OFF... and mine is S-ON but i cant seem to get if off,
the phone bootloader shows this:
**tampered**
**relocked**
m7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
radio-4A22.3263.03
openDSP-v32.120.274.0909
OS-3.63.111.3
eMMC-boot 2048MB
nov27 2013, 19:12:38.0
is there any way to get this phone working again?
thanks
kn!ves said:
Hello everyone, im new to these forums (and new to android) so nice to meet you all!
so i got this htc one m7 from a friend, he said he deleted the internal storage and he cant boot up android anymore.
thought might as well give it a try to fix it.
i tried everything in this thread http://forum.xda-developers.com/showthread.php?t=2258809 but it didnt work.
im getting a fail on the last step when it checks signatures.
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
after some surfing on the forums i found out that i need S-OFF... and mine is S-ON but i cant seem to get if off,
the phone bootloader shows this:
**tampered**
**relocked**
m7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
radio-4A22.3263.03
openDSP-v32.120.274.0909
OS-3.63.111.3
eMMC-boot 2048MB
nov27 2013, 19:12:38.0
is there any way to get this phone working again?
thanks
Click to expand...
Click to collapse
you dont need s-off, however, if you want s-off it would be advised whilst your on a low HBOOT before you update, but thats a different story.
your re-locked, so do you know if it has a custom recovery on it, or a custom rom, or is it 100% stock, to be sure, unlock your bootloader, because if it is running anything custom, it wont boot with a re-locked bootloader, unlock here:
http://www.htcdev.com/bootloader
just follow the instructions and report back when done, it will give you some adb and fastboot files, keep those, you'll need them and will also teach you how to use them if you dont know. :good:
Seanie280672 said:
you dont need s-off, however, if you want s-off it would be advised whilst your on a low HBOOT before you update, but thats a different story.
your re-locked, so do you know if it has a custom recovery on it, or a custom rom, or is it 100% stock, to be sure, unlock your bootloader, because if it is running anything custom, it wont boot with a re-locked bootloader, unlock here:
just follow the instructions and report back when done, it will give you some adb and fastboot files, keep those, you'll need them and will also teach you how to use them if you dont know. :good:
Click to expand...
Click to collapse
The phone was rooted and was still stock rom.
i just did all the steps to unlock the bootloader. ive got the unlock_bin but i dont see any adb and fastboot files?
just tried to flash it again, now i got a different error: FAILED: <remote: 32 header error>
kn!ves said:
The phone was rooted and was still stock rom.
i just did all the steps to unlock the bootloader. ive got the unlock_bin but i dont see any adb and fastboot files?
just tried to flash it again, now i got a different error: FAILED: <remote: 32 header error>
Click to expand...
Click to collapse
how are you trying to flash if you dont have any adb and fastboot files ?
ive attached mine below, just unzip and put your unlock code bin file in the same folder, then try and flash
Seanie280672 said:
how are you trying to flash if you dont have any adb and fastboot files ?
Click to expand...
Click to collapse
just tried these steps again haha http://forum.xda-developers.com/showthread.php?t=2258809
where can i get adb and fastboot files?
thanks
kn!ves said:
just tried these steps again haha http://forum.xda-developers.com/showthread.php?t=2258809
where can i get adb and fastboot files?
thanks
Click to expand...
Click to collapse
attached the files you need above, if you had of continued the unlock process on the HTC site, they would of supplied you with the files and guided you to use them.
Seanie280672 said:
attached the files you need above, if you had of continued the unlock process on the HTC site, they would of supplied you with the files and guided you to use them.
Click to expand...
Click to collapse
i did all the steps to unlock the phone, guess i mised those then. i downloaded your adb and fastboot. those files were already included in my Hasoons AIO Toolkit download.
this probally is a stupid question.... but what do i do now? haha
thanks
kn!ves said:
i did all the steps to unlock the phone, guess i mised those then. i downloaded your adb and fastboot. those files were already included in my Hasoons AIO Toolkit download.
this probally is a stupid question.... but what do i do now? haha
thanks
Click to expand...
Click to collapse
Is your bootloader unlocked now ? does the phone boot ? what do you want to do, custom rom or back to stock ?
Seanie280672 said:
Is your bootloader unlocked now ? does the phone boot ? what do you want to do, custom rom or back to stock ?
Click to expand...
Click to collapse
in the bootloader it now says unlocked. the phone can boot into the bootloader or in Team win recovery project. i just want the phone working again be it stock or custom rom. you know any good custom roms?
thanks
kn!ves said:
in the bootloader it now says unlocked. the phone can boot into the bootloader or in Team win recovery project. i just want the phone working again be it stock or custom rom. you know any good custom roms?
thanks
Click to expand...
Click to collapse
READ THE WHOLE POST BEFORE TRYING ANY OF THIS AS IVE ADDED A BIT TO THE BOTTOM
what you need to do is flash TWRP 2.8.5.0 from here: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
enter recovery and create a simple backup, just something like the boot, then plug your phone into the computer, whilst its still in recovery mode, that recovery supports MTP so your internal storage should open up on your computer, if it doesnt, you have a driver problem, but if it does, then navigate to TWRP/Backup/Phone serial number/todays date and some other details, delete the backup files out of there and place the files inside this zip in there instead, files only not folders: https://www.androidfilehost.com/?fid=23622183712459333
unplug your phone and restore that backup.
once restored, restart your phone and just do a basic setup.
then put this on your internal storage and again boot into recovery mode and flash it: https://www.androidfilehost.com/?fid=23622183712459512
once finished, do a full restart of the phone, your now nearly full stock, one last step, your need to flash the firmware which is here: https://www.androidfilehost.com/?fid=95747613655045066 once downloaded just name it to firmware for ease and put it in the same folder as adb and fastboot on your computer, reboot your phone to the bootloader and lock the bootloader (required to flash firmware as you are s-on), issue these commands.
Code:
fastboot oem lock
fastboot reboot-bootloader[I] (should now say relocked at the top)[/I]
fastboot oem rebootRUU[I] (screen turn black with silver HTC logo)[/I]
fastboot flash zip firmware.zip [I](failed is normal the first time, it will say please flush again) soooooo[/I]
fastboot flash zip firmware.zip
[I]as long as it says successful at the end this time your good to go, if not, report back here before the next command, if all is ok then:[/I]
fastboot reboot-bootloader
fastboot reboot
when you restart your phone will be full stock and you should now be able to update, recommended as your firmware is quite old, however, I would recommend before updating that you try and get s-off, for this you will need to use rumrunner s-off tool, you can find it here plus the instructions: http://rumrunner.us/ (you might want to try this after: "once restored, restart your phone and just do a basic setup." before flashing the firmware and preload data part)
Seanie280672 said:
READ THE WHOLE POST BEFORE TRYING ANY OF THIS AS IVE ADDED A BIT TO THE BOTTOM
what you need to do is flash TWRP 2.8.5.0 from here: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
enter recovery and create a simple backup, just something like the boot, then plug your phone into the computer, whilst its still in recovery mode, that recovery supports MTP so your internal storage should open up on your computer, if it doesnt, you have a driver problem, but if it does, then navigate to TWRP/Backup/Phone serial number/todays date and some other details, delete the backup files out of there and place the files inside this zip in there instead, files only not folders: https://www.androidfilehost.com/?fid=23622183712459333
unplug your phone and restore that backup.
once restored, restart your phone and just do a basic setup.
then put this on your internal storage and again boot into recovery mode and flash it: https://www.androidfilehost.com/?fid=23622183712459512
once finished, do a full restart of the phone, your now nearly full stock, one last step, your need to flash the firmware which is here: https://www.androidfilehost.com/?fid=95747613655045066 once downloaded just name it to firmware for ease and put it in the same folder as adb and fastboot on your computer, reboot your phone to the bootloader and lock the bootloader (required to flash firmware as you are s-on), issue these commands.
Code:
fastboot oem lock
fastboot reboot-bootloader[I] (should now say relocked at the top)[/I]
fastboot oem rebootRUU[I] (screen turn black with silver HTC logo)[/I]
fastboot flash zip firmware.zip [I](failed is normal the first time, it will say please flush again) soooooo[/I]
fastboot flash zip firmware.zip
[I]as long as it says successful at the end this time your good to go, if not, report back here before the next command, if all is ok then:[/I]
fastboot reboot-bootloader
fastboot reboot
when you restart your phone will be full stock and you should now be able to update, recommended as your firmware is quite old, however, I would recommend before updating that you try and get s-off, for this you will need to use rumrunner s-off tool, you can find it here plus the instructions: http://rumrunner.us/ (you might want to try this after: "once restored, restart your phone and just do a basic setup." before flashing the firmware and preload data part)
Click to expand...
Click to collapse
When i try to make a backup i get the error E:unable to mount '/cache'
E:unable to mount '/data'
E:unable to mount internal storage
and also when i connect the phone to my pc it says drivers are correctly installed but i cant see or open the internal storage.
thanks
kn!ves said:
When i try to make a backup i get the error E:unable to mount '/cache'
E:unable to mount '/data'
E:unable to mount internal storage
and also when i connect the phone to my pc it says drivers are correctly installed but i cant see or open the internal storage.
thanks
Click to expand...
Click to collapse
to clear those errors, in TWRP recovery select wipe - format data, this will wipe the entire phone, then reboot back into recovery.
The internal storage popping up on your computer only works when you are booted into recovery (main recovery screen only) and only with TWRP recovery 2.8.5.0 or 2.8.4.0.
Seanie280672 said:
to clear those errors, in TWRP recovery select wipe - format data, this will wipe the entire phone, then reboot back into recovery.
The internal storage popping up on your computer only works when you are booted into recovery (main recovery screen only) and only with TWRP recovery 2.8.5.0 or 2.8.4.0.
Click to expand...
Click to collapse
*after the format i could indeed make a backup
** restoring backup now, took a few tries to get the good TWRP..
how do i flash the M7_UL_preload_4.20.111.21_(flashbar)?
kn!ves said:
*after the format i could indeed make a backup
ok, i have TWRP v2.6.3.0. in my computer the phone show up as drive E: and looks like a cd-drive (cant open it) is there any other way i can copy the backup files from my computer to phone? or should i skipp that part?
thanks
Click to expand...
Click to collapse
How about updating the recovery to the one specified?
kn!ves said:
*after the format i could indeed make a backup
** restoring backup now, took a few tries to get the good TWRP..
how do i flash the M7_UL_preload_4.20.111.21_(flashbar)?
Click to expand...
Click to collapse
Are you using twrp 2.8.5.0 now ?
once you have restored the backup, boot up your phone, do a basic setup, plug your phone into the computer and copy the preload zip file to your internal storage, reboot back to recovery, select install, select the preload zip from the list and swipe to install.
Seanie280672 said:
Are you using twrp 2.8.5.0 now ?
once you have restored the backup, boot up your phone, do a basic setup, plug your phone into the computer and copy the preload zip file to your internal storage, reboot back to recovery, select install, select the preload zip from the list and swipe to install.
Click to expand...
Click to collapse
almost there, flashing firmware now, first time it said failed <remote: 90 hboot pre-update! please flush image again immediatly>
so i did fastboot flash zip firmware.zip again but now it just hangs on sending "zip"
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 10.475s
thanks
EDIT: after unlpugging once it worked. phone is now rebooting
kn!ves said:
almost there, flashing firmware now, first time it said failed <remote: 90 hboot pre-update! please flush image again immediatly>
so i did fastboot flash zip firmware.zip again but now it just hangs on sending "zip"
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 10.475s
thanks
EDIT: after unlpugging once it worked. phone is now rebooting
Click to expand...
Click to collapse
you will be full stock now, connect to your wifi and should beable to get all updates to the latest android.
Hit thanks a couple of times please. :good:
Seanie280672 said:
you will be full stock now, connect to your wifi and should beable to get all updates to the latest android.
Hit thanks a couple of times please. :good:
Click to expand...
Click to collapse
Thank you very mutch for your help and parience
im now turning S-OFF. btw with rumrunner s-off, will i also be able to install cracked apps on it?
thanks.
kn!ves said:
Thank you very mutch for your help and parience
im now turning S-OFF. btw with rumrunner s-off, will i also be able to install cracked apps on it?
thanks.
Click to expand...
Click to collapse
If you get s-off, it wil be way way easier to fix, no need to go through all that stuff again, just change cid, mid and run and RUU.

Factory reset won't finish and keeps trying to erase in a loop.

I did a factory reset from within the settings of the phone, it shows the erasing android and then flickers with and image of an android with triangle. Does this several times and then just stops on the android with red triangle. I can get into stock recovery, tried resetting from there but same thing happens. Also, if I just leave the phone it reboots and then tries to erase and then I get the same loop of it trying and failing.
Any ideas how to fix this? Phone is on the stock 5.0 rom and I have the pure edition.
Thanks
Raistlin1 said:
I did a factory reset from within the settings of the phone, it shows the erasing android and then flickers with and image of an android with triangle. Does this several times and then just stops on the android with red triangle. I can get into stock recovery, tried resetting from there but same thing happens. Also, if I just leave the phone it reboots and then tries to erase and then I get the same loop of it trying and failing.
Any ideas how to fix this? Phone is on the stock 5.0 rom and I have the pure edition.
Thanks
Click to expand...
Click to collapse
I would get into bootloader mode and reflash the system.img.
JulesJam said:
I would get into bootloader mode and reflash the system.img.
Click to expand...
Click to collapse
I am having a hard time trying to flash system.img. I found the system.img for my rom version and tried using ms fast boot v2 but it just hangs in the command window. I have installed the moto drivers and computer recognizes phone when it's in fast boot mode.
I even tried using someone's toolkit to return completely stock u rooted 4.4 but that doesn't work either.
Been reading tons of threads on here but can't seem to get it to flash.
Raistlin1 said:
I am having a hard time trying to flash system.img. I found the system.img for my rom version and tried using ms fast boot v2 but it just hangs in the command window. I have installed the moto drivers and computer recognizes phone when it's in fast boot mode.
Click to expand...
Click to collapse
Are you flashing a single file system.img or sparsechunks? Do you have mfastboot version 2?
Also, you can install Motorola Device Manager on your computer and when your phone is connected in fastboot mode, run MDM and see if it detects it.
JulesJam said:
Are you flashing a single file system.img or sparsechunks? Do you have mfastboot version 2?
Also, you can install Motorola Device Manager on your computer and when your phone is connected in fastboot mode, run MDM and see if it detects it.
Click to expand...
Click to collapse
System img is a single file, I also have a zip that has sparse chunks but haven't tried them. I am pretty sure I downloaded version 2 of mfastboot.
MDM saw my phone and said it had the most recent version.
Raistlin1 said:
System img is a single file, I also have a zip that has sparse chunks but haven't tried them. I am pretty sure I downloaded version 2 of mfastboot.
MDM saw my phone and said it had the most recent version.
Click to expand...
Click to collapse
I would try flashing the sparsechunks if you can't flash the single file image.
JulesJam said:
I would try flashing the sparsechunks if you can't flash the single file image.
Click to expand...
Click to collapse
Tried them using fastboot and only the first sparsechunk worked, they rest gave some error about bootloader.
I then tried in the mfastboot folder I created and it just hangs saying waiting for device, that's why I tried using fastboot.
I am really screwing myself, now while in bootloader and I try to boot or recovery I get failed to validate. Never had these problems flashing my N5, oh well.
Raistlin1 said:
Tried them using fastboot and only the first sparsechunk worked, they rest gave some error about bootloader.
I then tried in the mfastboot folder I created and it just hangs saying waiting for device, that's why I tried using fastboot.
Click to expand...
Click to collapse
How large is your mfastboot? It should be 521KB. If it is smaller than that, you don't have the right one.
What was the bootloader error?
Also now that you have flashed 1 sparsechunk, try MDM again.
You also can try flashing the 4.4.4 system.img if you can find it and then run MDM again b/c it will try to update you.
JulesJam said:
How large is your mfastboot? It should be 521KB. If it is smaller than that, you don't have the right one.
What was the bootloader error?
Also now that you have flashed 1 sparsechunk, try MDM again.
You also can try flashing the 4.4.4 system.img if you can find it and then run MDM again b/c it will try to update you.
Click to expand...
Click to collapse
I am getting bootloader failed to erase partition, failed remote failure.
MDM says phone is on latest version. mfastboot is the size you stated.
Raistlin1 said:
I am getting bootloader failed to erase partition, failed remote failure.
Click to expand...
Click to collapse
This happened to others. One guy had an unlocked bootloader and TWRP installed as recovery and was able to format the data partition through TWRP and that solved the problem for him:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-fastboot-flash-img-failed-t3098727
Can you get into recovery from the bootloader mode? I would get into recovery and wipe cache and then do a wipe data/factory reset and see what happens.
JulesJam said:
This happened to others. One guy had an unlocked bootloader and TWRP installed as recovery and was able to format the data partition through TWRP and that solved the problem for him:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-fastboot-flash-img-failed-t3098727
Can you get into recovery from the bootloader mode? I would get into recovery and wipe cache and then do a wipe data/factory reset and see what happens.
Click to expand...
Click to collapse
I will check out that thread, thanks. I cannot get into recovery from bootloader because it reboots into the erasing android which fails and then I get android with triangle and then I can get into recovery. But wiping cache and factory resetting from there does nothing, it reboots into the erasing android and then it fails to erase again.
Raistlin1 said:
I will check out that thread, thanks. I cannot get into recovery from bootloader because it reboots into the erasing android which fails and then I get android with triangle and then I can get into recovery. But wiping cache and factory resetting from there does nothing, it reboots into the erasing android and then it fails to erase again.
Click to expand...
Click to collapse
Can you reflash stock recovery?
Your bootloader is locked correct?
JulesJam said:
Can you reflash stock recovery?
Your bootloader is locked correct?
Click to expand...
Click to collapse
Reflashing recovery fails like systemail and my bootloader was unlocked prior to all of this happening.
Any way I can flash TWRP in the state I am in?
Raistlin1 said:
Reflashing recovery fails like systemail and my bootloader was unlocked prior to all of this happening.
Any way I can flash TWRP in the state I am in?
Click to expand...
Click to collapse
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
JulesJam said:
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
Click to expand...
Click to collapse
I am spent, going to bed and will pick up again tomorrow. Thanks for helping out.
JulesJam said:
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
Click to expand...
Click to collapse
Tried fastboot boot twrp.img but it won't boot, then tried flashing using fastboot and mfastboot but twrp won't install. Nothing will finish installing, tried flashing everything I can but it keeps failing.
Got the 4.4 image and started with flash partition gpt.bin but got bootloader failed to write primary GPT, bootloader failed to progra partition table, failed remote failure.
On phone I see incomplete boot image for booting, mismatched partition size (recovery). MDM sees my phone and says it is on the current version but I cannot get out of this factory erase looping. Nothing is flashing successfully, I remember seeing something about RSD Lite, will that help me in any way?
Thanks
Raistlin1 said:
Tried fastboot boot twrp.img but it won't boot, then tried flashing using fastboot and mfastboot but twrp won't install. Nothing will finish installing, tried flashing everything I can but it keeps failing.
Got the 4.4 image and started with flash partition gpt.bin but got bootloader failed to write primary GPT, bootloader failed to progra partition table, failed remote failure.
On phone I see incomplete boot image for booting, mismatched partition size (recovery). MDM sees my phone and says it is on the current version but I cannot get out of this factory erase looping. Nothing is flashing successfully, I remember seeing something about RSD Lite, will that help me in any way?
Thanks
Click to expand...
Click to collapse
RSDLite will just use mfastboot to flash. You definitely CANNOT downgrade the partition table - it would leave you with a bootloader partition table version mismatch. So don't attempt that.
You are on the 5.0 bootloader (60.11) correct? If so, did you try flashing the 5.0 partition table (gpt.bin)?
Is your device recognized when you are in recovery and you type in the commad:
adb devices
JulesJam said:
RSDLite will just use mfastboot to flash. You definitely CANNOT downgrade the partition table - it would leave you with a bootloader partition table version mismatch. So don't attempt that.
You are on the 5.0 bootloader (60.11) correct? If so, did you try flashing the 5.0 partition table (gpt.bin)?
Is your device recognized when you are in recovery and you type in the commad:
adb devices
Click to expand...
Click to collapse
As of now I can only get into fastboot mode, I don't believe the phone can even cycle through trying to boot any more. I tried rebooting from fastboot mode but there was an error and it failed.
I tried finding the exact image for 5.0 but I was only able to find the thread that had system, recovery and boot. Do you know a link to find the 5.0 partition table?
Raistlin1 said:
I tried finding the exact image for 5.0 but I was only able to find the thread that had system, recovery and boot. Do you know a link to find the 5.0 partition table?
Click to expand...
Click to collapse
http://www.graffixnyc.com/motox.php
JulesJam said:
http://www.graffixnyc.com/motox.php
Click to expand...
Click to collapse
Downloaded the 5.0 file from there, started flashing those files and it worked up until recovery, then I got the same bootloader message I was getting previously. Tried them over again and they all failed.
When in recovery adb devices starts the daemon and then says list of devices attached but I don't see anything after that.
I think it is fubar`d, going to have to file a warrant claim or use the moto care I purchased.

Can't get twrp working

Hoping I could get some help for this old phone. I've spent over 5 hours trying to get twrp installed and having no success in what should be one of the quickest steps in the whole rooting/flashing game. Reaching out for help before I lose my mind...
I've tried 2 different builds of oreo and 2 different builds of pie (all stock) and for each build I flashed different twrp versions from this link https://androidfilehost.com/?w=files&flid=232371. I even tried the android 9/10 versions on the android 8 builds. No errors in fastboot. If I try using power plus either of the volume keys it just boots right to android. If I try using the fastboot command (fastboot boot recovery.img) it freezes at the Sony logo. Doesn't seem to be an issue with twrp because I couldn't find a single mention of anyone else having this issue in any of the threads I've read while trying to troubleshoot. Any suggestions?
Is your bootloader locked?
betacrypt said:
Is your bootloader locked?
Click to expand...
Click to collapse
Oh, right, I should have mentioned that it's definitely unlocked. I checked in the service menu and I get the warning at startup.
Hmm what android version are you running currently, latest stock pie? It's possible your recovery partition is corrupt somehow.
Open up a terminal for fastboot and try running:
fastboot format recovery
or
fastboot erase recovery
then
fastboot flash recovery twrp-3.3.1-0-lilac-pie-5.img
I used twrp-3.3.1-0-lilac-pie-5.img on my device so I can confirm that one is definitely working.
betacrypt said:
Hmm what android version are you running currently, latest stock pie? It's possible your recovery partition is corrupt somehow.
Open up a terminal for fastboot and try running:
fastboot format recovery
or
fastboot erase recovery
then
fastboot flash recovery twrp-3.3.1-0-lilac-pie-5.img
I used twrp-3.3.1-0-lilac-pie-5.img on my device so I can confirm that one is definitely working.
Click to expand...
Click to collapse
So I managed to get this working. I tried the fastboot erase command but still had no success. Googled "fastboot erase twrp" or something like that and found a thread discussing how twrp was suspected of corrupting someone's data partition and running a "fastboot erase userdata" command to reformat the partition. I didn't think this would help my situation but figured I had nothing to lose at this point. Ran the "erase userdata" command, set up the phone again, but had no success at first.
I re-ran the "erase recovery" command and had no success with twrp 3.3.1. Then I tried 3.2.1 and initially had no success with hardware buttons or the "boot recovery" command. What I did this final time though, which I don't think I did on my previous attempts, was that instead of going back immediately and trying to re-flash twrp after the frozen sony screen, I gave up this time. BUT....I also said "f* it...let me try booting into recovery with the hardware buttons one last time." Lo and behold, I finally got into twrp!
I don't know if running the "erase recovery" command is what was needed, or it was just some quirky glitch where I needed the phone to freeze. Nevertheless, many thanks for responding and prompting me to make the last few attempts. Flashed magisk with no issue afterwards.

Categories

Resources