I installed the CM11 for this phone, I know not perfected yet, but it started having issues so I figured I would just go back to non-sense and be done with my CM11 trial.
At first I was just having trouble mounting DATA, then after a few reboots into TWRP 2.8.7.0 -- I lost my CACHE partition as well.
I tried using the RUU, but failed for SECURITY. I can't flash any ROMS (no DATA / CACHE) -- So I am stuck. FASTBOOT works, and I have access via TWRP, but thats it.
Carrier is Virgin Mobile.
Phone is U.S. 32-bit
Been rooted and working since we got root.
Any advice on how to proceed? Can I rebuild partitions from inside TWRP (command line?) can I find something that can be FASTBOOT or installed some other way?
Going back to stock is fine for now, what I am shooting for since it got all buggered up. And no I can't install BACKUPS either. Need partition access first..
Sorry, I think ADB is working, just can't do anything again because of the inability to mount the DATA & CACHE partitions.
The RUU failed by security because you have bootloader unlocked. Try to re-lock bootloader and re-install the RUU. That should work fine.
Been a while since I messed with this model, how do I re-lock bootloader?
****derp.
To re-Lock your bootloader Load phone into FASTBOOT and issue fastboot oem lock from command prompt. Phone will reboot and show RELOCKED.
Reboot phone in fastboot.
In adb, check with "fastboot devices" that your device is connected.
Then, in adb, type:
Code:
fastboot oem lock
And now you will have bootloader relocked.
PS: The phone only will reboot in Bootloader. That's because you don't have any OS installed.
To install the RUU, only plug the phone in fastboot and open the RUU program.
Thanks for help. seems all better now.
Related
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.
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
*UPDATE* - Sorry, forgot to mention that I've idiotically re-locked the bootloader. Unlocking the bootloader would probably get rid of the "signature verify fail" message. I'm unable to flash the recovery because the bootloader is locked and I can't get into the filesystem because the phone needs to go into the OS for that.
When I try to unlock the bootlader by using "fastboot flash unlocktoken Unlock_code.bin" it gives me the error: "cannot open 'Unlock_code.bin'."
I need to be able to access and make changes to the file system by using fastboot commands and I have no idea how to do this.
*UPDATE #2* - I've managed to re-unlock the bootlader (I didn't have the Unlock_code.bin file in the same directory as the current directory in my cmd window). I've re-flashed the recovery successfully. Now when I reboot, it goes into recovery mode (still can't boot into the OS). I'm using ClockWorks for the recovery.
Now I'm unable to root the phone. I'm trying to write SuperSU v1.65 to the phone by using the command: "fastboot flash zip UPDATE-SuperSU-v1.65.zp" and I get the error message: "remote: not allowed."
I can flash the recovery.img and boot.img (can't flash system.img because there's "not enough space"), but I can't flash .zip files
When I try flashing another boot.img, I still get the same thing. The phone goes to the boot screen and can't boot. Then, it reboots and goes automatically into recovery (I can still get into the bootloader and recovery).
Any suggestions to get past these permissions?
bkhosh2 said:
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
Click to expand...
Click to collapse
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
superbellefleche said:
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
Click to expand...
Click to collapse
I'm sorry, but I'm kind of a noob. How exactly do I re-flash a recovery. do I do this using the command: "fastboot flash recovery recovery.img" or should I try "fastboot flash zip filname.zip" (RUU.zip) again?
*UPDATE* - I've tried erasing the cache and re-flashing the recovery and I still get the error message: "signature verify fail."
I'm still waiting for someone to help me. Is anyone going to help me fix my problem or is my HTC One doomed?
If you are on Telus
Download http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
SaHiLzZ said:
If you are on Telus
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
Click to expand...
Click to collapse
I've already tried that. When the bootloader is locked, I get the error: "signature verify fail."
OK.. Unlock bootloader, flash custom recovery, adb push this file: http://www.htc1guru.com/2013/11/guru-reset-3-22-661-1/, and install it from recovery.
SaHiLzZ said:
OK.. Unlock bootloader, flash custom recovery, adb push this file
Click to expand...
Click to collapse
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
bkhosh2 said:
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
Click to expand...
Click to collapse
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
clsA said:
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Click to expand...
Click to collapse
I Installed the TWRP recovery instead of the ClockWorkMod and adb command work! Never using ClockWork ever again!
SaHiLzZ said:
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
Click to expand...
Click to collapse
I Installed TWRP and went into the TWRP recovery and noticed the adb commands work.
That file didn't work, however the Guru file you mentioned earlier did (with the "adb push" command)! Thanks so much for your help! Everything is working perfectly again!
Thanks for posting back. Edit your title to [SOLVED]! and enjoy!
I had a stock Nexus 6 onto which I loaded the MarshMallow previews.
I then decided to go back to 5.1.1 on the basis of the final release using the following:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Once I had entered the final fastboot command I also stupidly entered the command to lock the bootloader prior to rebooting
Some thing went wrong and now the phone sits on the google (while letters on black background) screen on bootup.
What are my options? I can access the bootloader, but its not showing up as a device on the on "adb devices"
Any assistance would be appreciated.
Sorry to say, but you've got a paperweight.
If by some chance you switched out the stock recovery.img with TWRP you're good, but otherwise, nope.
And in bootloader you use fastboot, as in "fastboot devices", not adb.
Boot to bootloader, unlock bootloader via fastboot (not adb!) and then move on from there (flash twrp, custom Rom or factory image).
petermuell said:
Boot to bootloader, unlock bootloader via fastboot (not adb!) and then move on from there (flash twrp, custom Rom or factory image).
Click to expand...
Click to collapse
Problem is that he can't go into settings and tick "OEM Unlocking" (due to phone not booting). Even if it was ticked prior to flashing, I don't think it stays that way after flashing a factory image. I've never tried it myself so this is of course pure speculation. It might be worth a shot.
Didgeridoohan said:
Problem is that he can't go into settings and tick "OEM Unlocking" (due to phone not booting). Even if it was ticked prior to flashing, I don't think it stays that way after flashing a factory image. I've never tried it myself so this is of course pure speculation. It might be worth a shot.
Click to expand...
Click to collapse
Thats a good point. I know when 5.1.0 came out, the OEM unlock option didn't persist after a reboot even, but does since 5.1.1.
My assumption would be it does survive a factory flash, because that data is stored in a partition that isn't touched by flashing a factory image, but like you, I have never tested it.
danarama said:
Thats a good point. I know when 5.1.0 came out, the OEM unlock option didn't persist after a reboot even, but does since 5.1.1.
My assumption would be it does survive a factory flash, because that data is stored in a partition that isn't touched by flashing a factory image, but like you, I have never tested it.
Click to expand...
Click to collapse
Hmm... This got interesting. It should survive a factory flash then.
@mittu1 Did you have OEM unlock allowed prior to locking your bootloader? If so, please, please, please run the command fastboot oem unlock and return with the result.
Yes, if you have stock recovery and can't unlock bootloader (probably because "allow OEM unlock" was not checked, or whatever reason), then you're pretty much stuck. Maybe then try this: http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I think it was intended for people who had downgraded their bootloader accidentally.
There is a zip file for flashing that toggles the "allow OEM unlock" flag (http://forum.xda-developers.com/showpost.php?p=61258590&postcount=352). If you can boot to twrp and flash a zip from the computer, flash that file, then boot to bootloader and unlock BL via fastboot.
I've read somewhere that In the "fastboot format cache" and "fastboot format userdata" work even on locked bootloaders. I haven't tried it personally, is this true?
istperson said:
I've read somewhere that In the "fastboot format cache" and "fastboot format userdata" work even on locked bootloaders. I haven't tried it personally, is this true?
Click to expand...
Click to collapse
If you have a custom recovery (TWRP) you can, after running those commands, flash a rom through TWRP and then proceed to boot up, tick "OEM Unlocking", unlock and do whatever you then intended to do.
Edit: Or use the above mentioned zip to toggle the "OEM Unlock"-thingy...
As i understood the OP the recovery is stock also. But somebody wrote the above, and as last resort it could be tried. And if it's false info, then let's have it clarified.
istperson said:
I've read somewhere that In the "fastboot format cache" and "fastboot format userdata" work even on locked bootloaders. I haven't tried it personally, is this true?
Click to expand...
Click to collapse
They should, but if not, a foctory reset can be done from stock recovery. Select recovery mode, then at the Android press power and then volume up. Then select the factory reset from the menu. See if it boots after that
BUT try fastboot oem unlock first, if you wipe without that and then try to unlock I think it'll fail to unlock
Didgeridoohan said:
Hmm... This got interesting. It should survive a factory flash then.
Click to expand...
Click to collapse
No, it is just my assumption. I am not aware if something in first boot process unchecks that option.
Also, FYI, many of us have noticed that when we bought Nexus 6 and unboxed it, booted straight to bootloader, it would unlock, but after first boot on 5.0, had to enable OEM unlock in settings... so maybe first boot process after a "wipe" resets?
Will try and revert
my phone: Nexus 6 32gb international
marshmallow (MRA58R) with cataclysm rom
twrp custom recovery and elementalx kernel
rooted, unlocked bootloader, no xposed
1. my phone was running fine until it randomly crashed and got stuck in fastboot menu. trying to start does nothing but in bootloader logs it shows this:
Code:
failed to validate boot image ret=-1
trying to reboot recovery gives:
Code:
failed to validate recovery image ret=-1
so i guess time to flash a MRA58R factory image right? however:
2. trying to flash via "flash all" script, manual one by one flash, or using the nexus root toolkit gives:
Code:
<bootloader> failed to flash partition
FAILED <remote failure>
this happens when i try to flash recovery (Stock or twrp) or bootloader or bootimage or system or anything. i have to my knowledge adequate platform tools setup which ive used multiple times before. my sdk tools are updated as well. at this point ill try anything. and i use windows. please help
Osaab said:
my phone: Nexus 6 32gb international
marshmallow (MRA58R) with cataclysm rom
twrp custom recovery and elementalx kernel
rooted, unlocked bootloader, no xposed
1. my phone was running fine until it randomly crashed and got stuck in fastboot menu. trying to start does nothing but in bootloader logs it shows this:
Code:
failed to validate boot image ret=-1
trying to reboot recovery gives:
Code:
failed to validate recovery image ret=-1
so i guess time to flash a MRA58R factory image right? however:
2. trying to flash via "flash all" script, manual one by one flash, or using the nexus root toolkit gives:
Code:
<bootloader> failed to flash partition
FAILED <remote failure>
this happens when i try to flash recovery (Stock or twrp) or bootloader or bootimage or system or anything. i have to my knowledge adequate platform tools setup which ive used multiple times before. my sdk tools are updated as well. at this point ill try anything. and i use windows. please help
Click to expand...
Click to collapse
Is the phone unlocked?
Code:
fastboot oem unlock
Can you erase userdata and cache
Code:
fastboot -w
mywindow said:
Is the phone unlocked?
Code:
fastboot oem unlock
Can you erase userdata and cache
Code:
fastboot -w
Click to expand...
Click to collapse
the phone is unlocked. it shows unlocked status 3 or something. and no -w gives the same error (failed to flash partition).
i was wondering i dont remember if i had "allow oem unlocking" enabled in the dev options and now i cant access it. is there a way that can be a problem?
Osaab said:
the phone is unlocked. it shows unlocked status 3 or something. and no -w gives the same error (failed to flash partition).
i was wondering i dont remember if i had "allow oem unlocking" enabled in the dev options and now i cant access it. is there a way that can be a problem?
Click to expand...
Click to collapse
I doubt it, since you don't need to unlock it a little more.
You should check your USB cable, or try to switch to another port. But if the error still persists, you need to send it to repair.
I am sorry mate, but u might have to send it in for real
Maybe your nand memory is corrupted. Since ur phone just crashed for "no reason" and then got stuck in fastboot, it may be an indicator for that.
Best regards!
Osaab said:
the phone is unlocked. it shows unlocked status 3 or something. and no -w gives the same error (failed to flash partition).
i was wondering i dont remember if i had "allow oem unlocking" enabled in the dev options and now i cant access it. is there a way that can be a problem?
Click to expand...
Click to collapse
I BELIEVE once you tick it and unlock, it does not turn back off (allow OEM unlock)
But as said above, this option only allows the bootloader to accept the unlock command...
Best case is the internal storage got scrambled and your partitions/ partition table is corrupt/missing/gone, worse case and maybe more likely is hardware failure?
Not sure if you can send terminal commands, but next step is either just RMA or searching the internet for a way to manually rebuild partition table from bootloader?
I guess?
Sounds like it messed it self up pretty good somehow, sorry man.
I tried to flash back to recovery, but I used
HTML:
TMO_RETAIL_XT1053_5.1.0-LPAS23.12-15.5-1_CFC.xml
, which I'm pretty sure means I'm gonna have a bad time.
I can't flash the LPA23.12 because I get an error doing fastboot flash partition gpt.bin and it screws up my partitions.
I can flash twrp, but that doesn't help me much. I can get to stock recovery, but that doesn't help me much either.
Things I've tried:
Clearing cache/dalvik
Factory reset
Flashing OTA_XT1053_Rooted.zip with TWRP
Running all the fastboot commands for LPA-23.12-15.5-0
Running all the fastboot commands for LPAS-23.12-15.5-0
Restoring someone elses recovery
I have a Windows 10 VM on my Mac, and while fastboot on Windows sees the phone, I can't get it to show up in RDS Lite 2.6.4. Moto Device Manager and Drivers have been installed.
Any ideas? :crying: