Good evening:
My sister in law has an HTC One M7 that has a LOCKED bootloader, is running STOCK, and is S-On. She was using the phone perfectly fine one day, and then all of a sudden it went into this infinite bootloop. This is the Verizon variant of this phone.
The main thing I am trying to accomplish is to save some pictures that she has on her phone of her newborn son (not automatically backed up). After that, I will flash an RUU to get it where it hopefully needs to be.
The info is as follows:
*** Locked***
M7_WLV PVT Ship S-On RH
HBoot-1.61.0000
Radio-1.13.41.1209
OpenDSP-v35.120.274.0718
OS-6.22.605.6
eMMC-boot 2048mb
Nov 30 2015
I have tried the following things from other threads:
1. "Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader."
2. "Try and shut it down and restart it again by holding the power button down for 12 - 15 seconds and see whether that clears it."
3. "Hold down power, volume up and volume down for at least 10 seconds. That should force a clean reboot."
How can I mount the phone to get the pictures or how can I get it to restart just long enough to receive them? Thank you for all your help.
poda13 said:
Good evening:
My sister in law has an HTC One M7 that has a LOCKED bootloader, is running STOCK, and is S-On. She was using the phone perfectly fine one day, and then all of a sudden it went into this infinite bootloop. This is the Verizon variant of this phone.
The main thing I am trying to accomplish is to save some pictures that she has on her phone of her newborn son (not automatically backed up). After that, I will flash an RUU to get it where it hopefully needs to be.
The info is as follows:
*** Locked***
M7_WLV PVT Ship S-On RH
HBoot-1.61.0000
Radio-1.13.41.1209
OpenDSP-v35.120.274.0718
OS-6.22.605.6
eMMC-boot 2048mb
Nov 30 2015
I have tried the following things from other threads:
1. "Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader."
2. "Try and shut it down and restart it again by holding the power button down for 12 - 15 seconds and see whether that clears it."
3. "Hold down power, volume up and volume down for at least 10 seconds. That should force a clean reboot."
How can I mount the phone to get the pictures or how can I get it to restart just long enough to receive them? Thank you for all your help.
Click to expand...
Click to collapse
You could try to go in recovery mode a wipe cache (do not factory reset). Then if the phone is still in a bootloop there is absolutely nothing you can do to backup any file from it. There are only 2 possibility to backup files from your phone, 1st one requires to be booted in the OS which is not possible, 2nd one requires to boot a custom recovery (the bootloader is locked, unlocking it to flash a custom recovery will wipe the phone)
Here is the RUU you'll need: https://www.androidfilehost.com/?fid=24341993505161705
Flash it using htc_fastboot.exe like explained in the RUU collection thread from the general section.
alray said:
You could try to go in recovery mode a wipe cache (do not factory reset). Then if the phone is still in a bootloop there is absolutely nothing you can do to backup any file from it. There are only 2 possibility to backup files from your phone, 1st one requires to be booted in the OS which is not possible, 2nd one requires to boot a custom recovery (the bootloader is locked, unlocking it to flash a custom recovery will wipe the phone)
Here is the RUU you'll need: https://www.androidfilehost.com/?fid=24341993505161705
Flash it using htc_fastboot.exe like explained in the RUU collection thread from the general section.
Click to expand...
Click to collapse
Hi Alray,
Thank you for your ideas on this. When I boot into the bootloader and select to go into recovery, it just takes me back to the bootloader screen. For some reason, I can not get to the screen with the red triangle to get into stock recovery. I was able to figure out the command prompt and fastboot, so I tried "fastboot erase cache", but it said there was an error.
Two key point that I think are good to know, developer options were not enabled on the phone so USB debugging is not on. Also, the fastboot option under settings >> power was still checked. Since i cant get into the system, i can not change those.
So, I cant erase cache via fastboot and I can not get into recovery for some reason. Any other suggestions on how to get into recovery or anything else?
Thanks for your time!
poda13 said:
Hi Alray,
Thank you for your ideas on this. When I boot into the bootloader and select to go into recovery, it just takes me back to the bootloader screen. For some reason, I can not get to the screen with the red triangle to get into stock recovery. I was able to figure out the command prompt and fastboot, so I tried "fastboot erase cache", but it said there was an error.
Two key point that I think are good to know, developer options were not enabled on the phone so USB debugging is not on. Also, the fastboot option under settings >> power was still checked. Since i cant get into the system, i can not change those.
So, I cant erase cache via fastboot and I can not get into recovery for some reason. Any other suggestions on how to get into recovery or anything else?
Thanks for your time!
Click to expand...
Click to collapse
USB debugging status (on/off) doesn't matter when in bootloader and recovery, its only needed to use ADB commands when booted in the OS.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There is nothing else you can try without loosing data on the phone.,,
what was the error when trying fastboot erase cache?
alray said:
USB debugging status (on/off) doesn't matter when in bootloader and recovery, its only needed to use ADB commands when booted in the OS.
There is nothing else you can try without loosing data on the phone.,,
what was the error when trying fastboot erase cache?
Click to expand...
Click to collapse
There was not a specific error given from what I remember, just said that there was an error. I am heading to work so I will try again tonight and will post the specific script that was shown.
alray said:
USB debugging status (on/off) doesn't matter when in bootloader and recovery, its only needed to use ADB commands when booted in the OS.
There is nothing else you can try without loosing data on the phone.,,
what was the error when trying fastboot erase cache?
Click to expand...
Click to collapse
Here is the info that I get when I try to do the fastboot clear cache:
C:\Users\The Goat>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.017s
Any thoughts?
poda13 said:
Any thoughts?
Click to expand...
Click to collapse
Its time to try the RUU I guess
Related
Hey i am stuck in fastboot (going for a week now) and i kinda think it's dead i did that full wipe script and now it won't boot into anything i can do bootloader (my bro told me it can be flashed by there but i don't even know also i can't get into hboot due to the camera button being stubborn) so might as well ask here since he's at my cousins house for now and also how can i flash zip files? like the kind that aren't .img? just for details every time i try to flash via fastboot it either says unknown partition or cannot load blah.img maybe it's something i did wrong? i got adb/fastboot setup with the sdk and stuff but that's as far as i can get .
also i can't use adb (should be obvious by now).
can you access recovery mode? holding home+power?
I can try but don't guarantee success in doing so because of something i did in fastboot by mistake in trying to fix it ( ) unless there's a way of re flashing ra's rom or something there's no way i can get recovery to work again.
edit why don't they have those windows to phone flasher just like the hd2's have them that way i would have had it fixed by now .
Probably you should read a bit in this post.
If you are in fastboot, you can do almost everything with your phone.
1.
Code:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
and your phone is clean.
2.
Code:
fastboot flash recovery <recovery.img>
and you have a working recovery.
3. you can decide how to continue ...
whenever i try to flash it(at last step at the instructions at top), it keeps saying error: cannot load 'Recovery.img' file ,weird , i am using ra's recovery has recovery.img , don't know why it's not letting me flash it
edit even has the original name it won't load
you need to have it in the same directory from where you are calling the fastboot command, i.e.
you are on c:\ -> recovery.img must be located on c:\
otherwise you need to give the full path to your recovery.img, i.e.
Code:
fastboot flash recovery c:\recovery.img
AndDiSa said:
you need to have it in the same directory from where you are calling the fastboot command, i.e.
you are on c:\ -> recovery.img must be located on c:\
otherwise you need to give the full path to your recovery.img, i.e.
Code:
fastboot flash recovery c:\recovery.img
Click to expand...
Click to collapse
Because a button is not good enough here you go
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
for showing me the way also i'v been like this since last week reason i didn't ask in the first place is because i thought it was already answered already and i searched but couldn't find the right answer
but thanks to a guru like you i fixed it .
Edit - testing phone , seems to be doing something at the g1 screen.
Edit 2 - i think it might be ... bricked , hold on.
Edit 3 - got it into recovery lets see from here.
**** it tomorrow i get a new phone anyways time to put this demon to sleep
ok i am not going anywhere can't get lift off .
i have amonra recovery in a zip file if you can flash it via fastboot?
I can try that but if i can get into fast boot (is it the little balltracker thingy and the power button? if so i think my fastboot is broken because it just shows a blue light with no signal of the screen on )
What i have try'ed is that wipe script ohsaka-super-wipe <- and i am trying to get SenseLX v3.1 to run but all my attempts just lead me back to the recovery screen for some weird reason
also don't know if this info will help at all but i got a 16gb sdcard and getting another one soon just hope it's better class
Hold on let me see something
also i flashed my hboot alot of times so maybe it's something with that.
well it's hboot mode but different... hboot is used to flash .img files.. fastboot is the same but diff button to power on and as long as you have fastboot drivers installed you can flash zip files via fastboot, power on device by holding back+power
here's a guide to install adb/fastboot driver on windows vista/7 if thats what you have...
http://forum.xda-developers.com/showthread.php?t=1124916
EDIT: o wait so you do have recovery? you said after trying to install rom it brings you back to recovery?
what radio/spl do you have? you need 2708/2825 & 0013d
here is guide to install radio and spl
http://forum.xda-developers.com/showthread.php?t=1098899
ldrifta said:
well it's hboot mode but different... hboot is used to flash .img files.. fastboot is the same but diff button to power on and as long as you have fastboot drivers installed you can flash zip files via fastboot, power on device by holding back+power
here's a guide to install adb/fastboot driver on windows vista/7 if thats what you have...
http://forum.xda-developers.com/showthread.php?t=1124916
EDIT: o wait so you do have recovery? you said after trying to install rom it brings you back to recovery?
what radio/spl do you have? you need 2708/2825 &1. 0013d
here is guide to install radio and spl
http://forum.xda-developers.com/showthread.php?t=1098899
Click to expand...
Click to collapse
yep i have it, also following guide gonna report back in a few minutes
Edit - i got both hboot0013d-signed.zip and radio-2_22_27_08-signed.zip in my sdcard meaning i might have flashed them already so i don't see why it should be taking me to recovery
edit 2 bad hboot / E:missing bitmap Progress_empty/fill code -1 2x didn't wanna risk the real brick so i didn't install it.
Edit 3 E: - blah blah blah failure at line 3
well its' back to the drawing board for me..
and well fastboot don't work (camera button + power button don't do anything)
Now would'ya look at that it started working to an htc screen doing something alright
it hates me i swear.
lol when you get to the hboot or fastboot screen what does your device say? can you find out what radio and spl you have?
ldrifta said:
lol when you get to the hboot or fastboot screen what does your device say? can you find out what radio and spl you have?
Click to expand...
Click to collapse
Fuucucuc my luck was supposed to get a new phone today
also
NO i can't find out what radio/spl i have i can flash but it will give me a E:/hboot error
well you find out by powering on device in hboot mode, holding camera+power or even try back+power
Dream100 PVT 32b
HSPL.10.95.3000
CPLD - 4
Radio -2.22.28.25
thank you for the info since the camera button was be stubborn
i see i didn't have hboot maybe that's why it's was giving me errors'
----
got it back to default
-----
goddam my luck sucks almost had another one in the hook today (samsung captivate)
Woke up today after using my phone to set an alarm last night...and my phone was shutdown (plugged in).
I tried starting it up, and the phone wouldn't boot past the white HTC startup screen. Since then I've tried booting up several times, including using volume down button, and then clicking fastboot, but the screen just goes black and nothing happens. Effectively I'm stuck at the start-up screen.
My phone is only a couple months old, and is not rooted. Also since I have not attempted anything fancy, I have not yet backed up any of my data, photos, etc. The only advice I've had so far is to do a factory reset, but this would erase important videos, which I really don't want to loose.
Does anyone have suggestions on things to try to either somehow backup my data before a reset, or to fix this issue?
Thanks,
Bill
billiam864 said:
Woke up today after using my phone to set an alarm last night...and my phone was shutdown (plugged in).
I tried starting it up, and the phone wouldn't boot past the white HTC startup screen. Since then I've tried booting up several times, including using volume down button, and then clicking fastboot, but the screen just goes black and nothing happens. Effectively I'm stuck at the start-up screen.
My phone is only a couple months old, and is not rooted. Also since I have not attempted anything fancy, I have not yet backed up any of my data, photos, etc. The only advice I've had so far is to do a factory reset, but this would erase important videos, which I really don't want to loose.
Does anyone have suggestions on things to try to either somehow backup my data before a reset, or to fix this issue?
Thanks,
Bill
Click to expand...
Click to collapse
Maybe you should try to erase cache and reboot?
Code:
fastboot erase cache
fastboot reboot
alray said:
Maybe you should try to erase cache and reboot?
Code:
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I am noob at this. my phone is unrooted, so my bootloader is locked. How do I run the erase cache command as you suggested? I've spent sometime looking for a forum telling me how, but have not found anyting... presumably i need software for my pc and connect the phone to it, or should there be some menu on the phone i can get to, to type in the command?
billiam864 said:
I am noob at this. my phone is unrooted, so my bootloader is locked. How do I run the erase cache command as you suggested? I've spent sometime looking for a forum telling me how, but have not found anyting... presumably i need software for my pc and connect the phone to it, or should there be some menu on the phone i can get to, to type in the command?
Click to expand...
Click to collapse
you will need to have fastboot/adb tools installed on your computer ----> HERE
and you'll need latest HTC drivers installed. This can be done by installing HTC sync software you can find HERE
start with this, ill update this post with more instructions
reboot phone in bootloader mode (hold down POWER + VOL DWN)
you will have a screen similar to this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
select ''FASTBOOT'' (use volume up/down to navigate and power button to select)
then connect phone to computer (better to use a usb port at the back of your computer and don't use any usb hub)
The screen should now display ''FASTBOOT USB''' and the phone should be recognized by your computer.
Now open adb/fastboot tool by clicking on ''Minimal ADB and Fastboot'' icon
it will open a cmd prompt like this:
type these cmds:
Code:
fastboot erase cache [COLOR="Red"]<------- press ''enter''[/COLOR]
fastboot reboot [COLOR="red"]<------- press ''enter''[/COLOR]
now the phone will reboot
check if the phone is now booting properly.
btw no need to unlock the bootloader and root your phone atm
alray said:
you will need to have fastboot/adb tools installed on your computer ----> HERE
and you'll need latest HTC drivers installed. This can be done by installing HTC sync software you can find HERE
start with this, ill update this post with more instructions
reboot phone in bootloader mode (hold down POWER + VOL DWN)
you will have a screen similar to this
select ''FASTBOOT'' (use volume up/down to navigate and power button to select)
then connect phone to computer (better to use a usb port at the back of your computer and don't use any usb hub)
The screen should now display ''FASTBOOT USB''' and the phone should be recognized by your computer.
Now open adb/fastboot tool by clicking on ''Minimal ADB and Fastboot'' icon
it will open a cmd prompt like this:
type these cmds:
Code:
fastboot erase cache [COLOR="Red"]<------- press ''enter''[/COLOR]
fastboot reboot [COLOR="red"]<------- press ''enter''[/COLOR]
now the phone will reboot
check if the phone is now booting properly.
btw no need to unlock the bootloader and root your phone atm
Click to expand...
Click to collapse
Ok,
so i installed the ADB command prompt and the HTC Sync program.
Booted up my phone and got the Fastboot USB indicator...typed in the first command and received an error. (see attached image).
billiam864 said:
Ok,
so i installed the ADB command prompt and the HTC Sync program.
Booted up my phone and got the Fastboot USB indicator...typed in the first command and received an error. (see attached image).
Click to expand...
Click to collapse
the phone is recognised by the computer?
what is the ouput of
Code:
fastboot devices
?
alray said:
the phone is recognised by the computer?
what is the ouput of
Code:
fastboot devices
?
Click to expand...
Click to collapse
My result was: FA38VS902912 fastboot
Seems like the computer sees the Phone...
billiam864 said:
My result was: FA38VS902912 fastboot
Seems like the computer sees the Phone...
Click to expand...
Click to collapse
Yes phone is correctly recognized. Honestly its the first time I see that ''erasing error''.
You might want to try factory reset your phone... but it will wipe all your data.
Your phone is only a couple months old... still under warranty?
Btw factory reset is step #1 when you call htc cus.ser.
alray said:
Yes phone is correctly recognized. Honestly its the first time I see that ''erasing error''.
You might want to try factory reset your phone... but it will wipe all your data.
Your phone is only a couple months old... still under warranty?
Btw factory reset is step #1 when you call htc cus.ser.
Click to expand...
Click to collapse
Okay, well thanks for trying... was really hoping to keep my videos and photos... If you think of anything please repost!
Factory reset should NOT wipe sdcard. But I don't have a htc one to test right bow
sent from my mobile device
billiam864 said:
Okay, well thanks for trying... was really hoping to keep my videos and photos... If you think of anything please repost!
Click to expand...
Click to collapse
yes as @SaHiLzZ said, factory reset won't wipe the internal sdcard partition where your photo and video are stored. It will wipe /data partition where your users settings and app are stored. so you should not lost your media files.
The other options will require unlocking bootloader which will void your warranty. So if your phone is still under warranty better to get it repaired or replaced instead.
alray said:
yes as @SaHiLzZ said, factory reset won't wipe the internal sdcard partition where your photo and video are stored. It will wipe /data partition where your users settings and app are stored. so you should not lost your media files.
The other options will require unlocking bootloader which will void your warranty. So if your phone is still under warranty better to get it repaired or replaced instead.
Click to expand...
Click to collapse
Also unlocking bootloader at HTCDEV will wipe the phone totally / sdcard and all
clsA said:
Also unlocking bootloader at HTCDEV will wipe the phone totally / sdcard and all
Click to expand...
Click to collapse
I hope you all are correct. I spoke with HTC about sending in my phone for repair, and they said that since HTC One phones don't have an external or removal SD card...just internal memory, that all my photos/files/etc will be lost in the factory reset. Perhaps this discrepancy is in the model or type of HTC One?
Thanks,
Hi friends,
I really hope somebody can help me out here..
My mum's Moto G 2014 (stock rom, just like it came out of the box, no tinkering, nothing) started acting weird. It had force-closes all over, nothing worked. So I boot into fastboot mode, select "Factory". The factory reset doesn't work - user data is clearly still there when I boot.
So I try wiping user data and cache with fastboot from the PC (linux). Command runs through, no error message. But the user data is still there when I boot - I still get 100 force-closes, the thing is unusable.
Next I go ahead and unlock the bootloader (which should wipe all data, right)? Again, userdata is still there when I boot.
Then I flash TWRP. But when I boot into fastboot and select "recovery", the screen just goes dark. Same after I flash CWM instead. (And the same, incidentally, as it was with stock recovery - selecting "recovery" just makes the screen go dark).
I am left clueless ... having voided the warranty by unlocking the bootloader. Any pointers?
Thanks, guys.
Power off your phone. When the screen goes black, press and hold the Volume Down button with one finger. Then, while still holding this button, press and hold the Power button with another finger. This will bring up the Bootloader menu, then tap the Volume Down button once to highlight Recovery Mode. From here, simply press the Volume up once, and TWRP recovery should come right up. Touch Wipe and you'll see the Factory Reset.
Tel864 said:
Power off your phone. When the screen goes black, press and hold the Volume Down button with one finger. Then, while still holding this button, press and hold the Power button with another finger. This will bring up the Bootloader menu, then tap the Volume Down button once to highlight Recovery Mode. From here, simply press the Volume up once, and TWRP recovery should come right up. Touch Wipe and you'll see the Factory Reset.
Click to expand...
Click to collapse
But I think as he said, he can't enter the recovery mode.
Did you try to flash a stock rom?
You're right, I missed that part about going dark when choosing recovery.
Lars124 said:
Did you try to flash a stock rom?
Click to expand...
Click to collapse
No - not yet. Where would I get the stock ROMs? I think I've got the XT1068 version of the phone, (Germany, dual-SIM).
Can I just flash the ROM with fastboot from the PC? Without having a custom recovery on the device? (as I said, flashing TWRP or CWM with fastboot didn't work, no error message but no success either).
EDIT: I now managed to get into the stock recovery - I just didn't know I had to press the Vol-Up-Key to confirm (and when the android on its back shows, then hold Power for a few seconds and tap Vol UP to enter the recovery). So I'm in the recovery now. However, selecting "wipe data / factory reset" still doesn't work. I get these error messages:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Doesn't look good, does it?
Thanks so much!
What commands did you enter when in download mode on the phone? What commands on the pc did you enter and what did your phone say in download mode while doing it?
Yes, you flash your stock rom via fastboot and you don't need a custom recovery.
Check this thread and look for your version:
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I think you can take this one:
https://drive.google.com/file/d/0B_OYdZXdfmnbY092bUIxaTkxRjg/view
dazeone said:
What commands did you enter when in download mode on the phone? What commands on the pc did you enter and what did your phone say in download mode while doing it?
Click to expand...
Click to collapse
First I entered
Code:
fastboot erase cache
The PC said:
Code:
erasing 'cache'...
OKAY [ 0.033s]
finished.
The phone said:
Code:
cmd:getvar:partition-type:cache
cmd: erase:cache
Then I hit
Code:
fastboot erase userdata
The PC said:
Code:
erasing 'userdata'...
OKAY [ 0.034s]
finished.
And the phone said:
Code:
cmd:getvar:partition-type:userdata
cmd: erase:userdata
So no error message there (unlike when I start a wipe/reset from the stock recovery). The userdata aren't erased in either case - all the apps are still there (and I'm bombarded with force-closes of all sorts of apps and services every 0.5 seconds)
Lars124 said:
Yes, you flash your stock rom via fastboot and you don't need a custom recovery.
Check this thread and look for your version:
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I think you can take this one:
https://drive.google.com/file/d/0B_OYdZXdfmnbY092bUIxaTkxRjg/view
Click to expand...
Click to collapse
Thanks! I'll definitely try that. But I don't dare get my hopes up after flashing CWM and TWRP didn't work (and factory reset neither). This really starts looking like a brick to me.
That's really strange.
Flash the stock rom and we will see what happens.
Lars124 said:
Yes, you flash your stock rom via fastboot and you don't need a custom recovery.
Check this thread and look for your version:
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I think you can take this one:
https://drive.google.com/file/d/0B_OYdZXdfmnbY092bUIxaTkxRjg/view
Click to expand...
Click to collapse
I downloaded and flashed all parts of the ROM in the order suggested in the .bat file. It turned out as I suspected: No error message (neither in fastboot on the PC nor on the device while flashing), but no change on the device. Even after flashing the stock ROM and erasing userdata and cache at the end of the process, my old apps are still there and nothing appears to have changed. Still getting a ton of force-closes, it's unusable.
It's as if the phone is in read-only mode, I erasing userdata or flashing new ROM doesn't do anything. The only thing I have to go on at this point are the error messages I posted in the photo above (after trying to wipe from the stock recovery:
Code:
Formatting /data
[B]E:
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed[/B]
Formatting /cache
[B]E:
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/cache failed[/B]
loxdp said:
I downloaded and flashed all parts of the ROM in the order suggested in the .bat file. It turned out as I suspected: No error message (neither in fastboot on the PC nor on the device while flashing), but no change on the device. Even after flashing the stock ROM and erasing userdata and cache at the end of the process, my old apps are still there and nothing appears to have changed. Still getting a ton of force-closes, it's unusable.
It's as if the phone is in read-only mode, I erasing userdata or flashing new ROM doesn't do anything. The only thing I have to go on at this point are the error messages I posted in the photo above (after trying to wipe from the stock recovery:
Code:
Formatting /data
[B]E:
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed[/B]
Formatting /cache
[B]E:
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/cache failed[/B]
Click to expand...
Click to collapse
This. I am also having exactly this problem (of endless force quits and inability to flash stock), with precisely the same error message when resetting from recovery. The thread I started '[Q] Custom Recovery Only Works By "fastboot boot"' turns out to have been the wrong title...it seems likely the reason I can't flash a custom recovery (despite unlocked bootloader) is the same reason I can't format partitions either (stock recovery can't, nor can TWRP format /data). Although adb shell can be used for manually formatting partitions, it is serious stuff not to be attempted casually ("instant expert" disease is a leading cause of death so I have not tried it.
Sadly, I can't offer you any help other than to add to link our threads in the hope that something I've discovered may lead a knowledgeable dev to the source of this problem.
Same problem here.
Any write operation fails, while fastboot claims anything was "OKAY".
Only "fastboot -w" gives some hint to the actual problem:
Code:
# fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.077s]
erasing 'cache'...
OKAY [ 0.014s]
finished. total time: 0.091s
However, I was not able to solve it.
I suspect this to be a hardware failure but I did not give up hope completely yet :-\
I have the exact same problem
Has anyone solved it yet?
bump
Thats seems to be my problem too.
With stock recovery and stock rom I didn't manage to wipe cache and user data. I also try it with fastboot but nothing. Nothing clear no erase at all.
Desparate and waiting a solution
Same problem - can't erase, can't flash.
Should ask help from Motorola Support.
Will call to their support and hope they will provide me 2nd level assist, not just advice to use warranty. No official Motorola in my country.
For anyone who would try to get support - chat on site is useless - they will tell you to do Wipe in recovery.
For additional support - call (US) Motorola Support 1-800-734-5870 and try to reach advanced support.
*Motorola chat support advised me to use Talkatone app to make a call, since I'm out of US.
**Get all of available phone docs - IMEI and other stuff.
I can't try their support since MotoG2 is of my girlfriends and is away now.
Support told me to call back only when I will hold the phone in my hands and will have IMEI to provide.
RSD Lite 6.2.4 works with Moto G, earlier versions would not work.
Same stuff - flashed ok but nothing changes.
If we use "mfastboot boot boot.img"
Device shows "updating android applications 1 of 7", then "Starting Android", but then black screen. Again.
But better than was - just black screen without any signs.
Is there any way to boot up different bootloader to get it's fastboot?
Anyone have tried to lock the bootloader, reflash the stock rom from fastboot and unlock again the bootloader?
A similar situation happened to me and this resolve the problem.
Poeta said:
Anyone have tried to lock the bootloader, reflash the stock rom from fastboot and unlock again the bootloader?
A similar situation happened to me and this resolve the problem.
Click to expand...
Click to collapse
When locking bootloader - reboot is required since no commands will work.
But after rebooting everything is still same. Bootloader still UNlocked.
Guys, what you think about this?
http://android-revolution-hd.blogspot.co.uk/2013/10/fix-data-htc-one.html
about partition images
Aaand this
http://android.stackexchange.com/questions/58027/updater-script-for-flashing-raw-partition-image
about dd flashing raw
Darksl1der said:
When locking bootloader - reboot is required since no commands will work.
But after rebooting everything is still same. Bootloader still UNlocked.
Guys, what you think about this?
http://android-revolution-hd.blogspot.co.uk/2013/10/fix-data-htc-one.html
about partition images
Aaand this
http://android.stackexchange.com/questions/58027/updater-script-for-flashing-raw-partition-image
about dd flashing raw
Click to expand...
Click to collapse
It seems to be a motherboard problem... Warranty.
Hi all,
first time poster - looonnng time lurker. Hoping you can help me with my One M7 brick.
Phone had been running slow and sluggish for a few weeks. Yesterday morning, it was particularly slow with apps randomly closing/crashing. Decided to reboot. The phone didn't reboot though; it came back with a white screen and "** TAMPERED *** *** LOCKED****" coming up - a fastboot screen I believe.
I can't get it to boot at all and I've tried accessing it via adb but it isn't detected. 'adb devices' shows nothing however 'fastboot devices' does list the phone. Windroid seems to detect it.
Ordinarily, I would just do a factory reset to see if this helps but my problem is this - I have SMS messages and photos/videos on the phone of my daughter that I really, really, really don't want to lose. They are very precious to me. If it was a case of breaking up the phone then I'd do it in a heartbeat to recover this data.
I've attached some images that I hope may help. A friend has mentioned that some of the lines indicate a problem with encryption on the card which means the data is lost completely - I'm desperately hoping this isn't the case and some kind soul can help.
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
need help to flash factory ruu zip
recently i installed recovery and accidentally deleted system partition..then it wont boot up..
OS- 7. 21 .980. 35
hboot -1.61
can not s-off
mid-PN0714000
cid- HTC__039
there are no ruu zip matches i found..
can anyone suggest me something to back to normal.. thanks..
namal.007 said:
recently i installed recovery and accidentally deleted system partition..then it wont boot up..
OS- 7. 21 .980. 35
hboot -1.61
can not s-off
mid-PN0714000
cid- HTC__039
there are no ruu zip matches i found..
can anyone suggest me something to back to normal.. thanks..
Click to expand...
Click to collapse
flash the 7.19.980.5 RUU, see post #2 of this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
---------- Post added at 09:24 AM ---------- Previous post was at 09:20 AM ----------
MPDi said:
Hi all,
first time poster - looonnng time lurker. Hoping you can help me with my One M7 brick.
Phone had been running slow and sluggish for a few weeks. Yesterday morning, it was particularly slow with apps randomly closing/crashing. Decided to reboot. The phone didn't reboot though; it came back with a white screen and "** TAMPERED *** *** LOCKED****" coming up - a fastboot screen I believe.
I can't get it to boot at all and I've tried accessing it via adb but it isn't detected. 'adb devices' shows nothing however 'fastboot devices' does list the phone. Windroid seems to detect it.
Ordinarily, I would just do a factory reset to see if this helps but my problem is this - I have SMS messages and photos/videos on the phone of my daughter that I really, really, really don't want to lose. They are very precious to me. If it was a case of breaking up the phone then I'd do it in a heartbeat to recover this data.
I've attached some images that I hope may help. A friend has mentioned that some of the lines indicate a problem with encryption on the card which means the data is lost completely - I'm desperately hoping this isn't the case and some kind soul can help.
Thanks
Click to expand...
Click to collapse
If the phone was encrypted then the only way to recover the phone is a factory reset using the stock recovery which will obviously delete all your files. Any other method that could fix the phone will wipe it: unlock the bootloader to flash a new rom will wipe the phone, flashing a ruu will also wipe it. Thats probably either an encryption problem or a failed emmc chip. I don't think there anything to do to recover your data, especially if the phone was encrypted. Sorry at least the phone might be recoverable...
alray said:
flash the 7.19.980.5 RUU, see post #2 of this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
---------- Post added at 09:24 AM ---------- Previous post was at 09:20 AM ----------
If the phone was encrypted then the only way to recover the phone is a factory reset using the stock recovery which will obviously delete all your files. Any other method that could fix the phone will wipe it: unlock the bootloader to flash a new rom will wipe the phone, flashing a ruu will also wipe it. Thats probably either an encryption problem or a failed emmc chip. I don't think there anything to do to recover your data, especially if the phone was encrypted. Sorry at least the phone might be recoverable...
Click to expand...
Click to collapse
Well, after asking a company who said they could do it and then said they'd have to wipe it, I've taken it back.
It seems there's nothing I can do about it; I've even tried using guides on here and elsewhere to return it completely to stock but because I can't get adb working, it's a no go. Factory reset does nothing. Trying to use tools and fastboot to change recovery images and all sorts doesn't work either. Seems to be something relating to 'S-ON' as when it's in RUU boot, if I disconnect and reconnect the USB cable, the screen briefly changes from the HTC screen to the white screen showing "Security Failed!" after trying to flash a new image on.
At a bit of a loss!
MPDi said:
It seems there's nothing I can do about it; I've even tried using guides on here and elsewhere to return it completely to stock but because I can't get adb working, it's a no go.
Click to expand...
Click to collapse
adb commands only works from a booted rom + USB debugging enabled from the developer option menu or from a custom recovery. So there is no problem here.
Factory reset does nothing.
Click to expand...
Click to collapse
What is it doing exactly? You select "factory reset and it boot to the HTC splash sceen? It reboot in bootloader mode? It freeze the phone?
Trying to use tools and fastboot to change recovery images and all sorts doesn't work either.
Click to expand...
Click to collapse
Again you need to be more precise, what doesn't work exactly? There is no fastboot connectivity or there is but the recovery won't flash? Did you unlocked the bootloader?
Seems to be something relating to 'S-ON'
Click to expand...
Click to collapse
No, Its not related to S-ON.
as when it's in RUU boot, if I disconnect and reconnect the USB cable, the screen briefly changes from the HTC screen to the white screen showing "Security Failed!" after trying to flash a new image on.
Click to expand...
Click to collapse
What image exactly and how did you tried to flash it?
alray said:
adb commands only works from a booted rom + USB debugging enabled from the developer option menu or from a custom recovery. So there is no problem here.
What is it doing exactly? You select "factory reset and it boot to the HTC splash sceen? It reboot in bootloader mode? It freeze the phone?
Again you need to be more precise, what doesn't work exactly? There is no fastboot connectivity or there is but the recovery won't flash? Did you unlocked the bootloader?
No, Its not related to S-ON.
What image exactly and how did you tried to flash it?
Click to expand...
Click to collapse
I've taken it back to another shop this morning to have it reset/flashed back to stock. Will just have to try data recovery once I've got it back and see if I can recover anything.
Dear Reader,
As you could see on a video, the device is unlocked using official method ( SMS ), but after when trying to unlock the OEM bootloader it locks itself again.
Why and how to unlock it completely to flash TWRP and Root ?
Thank you.
Best regards,
V7
its already unlocked. try to flash twrp maybe? as you can see the bootloader is already unlocked, then you can flash custom recovery
why are you confused? the settings app already told you its already unlocked
Exodus4 said:
its already unlocked. try to flash twrp maybe? as you can see the bootloader is already unlocked, then you can flash custom recovery
why are you confused? the settings app already told you its already unlocked
Click to expand...
Click to collapse
Thank you for your reply, really.
As you could notice, the trigger sets itself to disabled when menu changes( it doesn't stay at its position ), so I though that the trigger just doesn't work, doesn't it ?
There is only ONE bootloader. You already unlocked it. That trigger is only for enabling lock and unlock from fastboot interface using the code "fastboot oem unlock", which many other android devices use, but probably not for xiaomi ones. That trigger is NOT for unlocking bootloader, or in other words, turning it on DOES NOT unlock the bootloader. There is no such thing as "OEM bootloader". Your bootloader is already unlocked. Go to fastboot and flash TWRP and do whatever you want.
NTLinhHaHa said:
There is only ONE bootloader. You already unlocked it. That trigger is only for enabling lock and unlock from fastboot interface using the code "fastboot oem unlock", which many other android devices use, but probably not for xiaomi ones. That trigger is NOT for unlocking bootloader, or in other words, turning it on DOES NOT unlock the bootloader. There is no such thing as "OEM bootloader". Your bootloader is already unlocked. Go to fastboot and flash TWRP and do whatever you want.
Click to expand...
Click to collapse
Thank you for your reply really.
By the way, I've already tried to flash a custom recovery like TWRP 3.2.1.0, but after rebooting into recovery the old recovery had been shown, even if fastboot tells that everything regarding flashing is OK, so I though it's just locked. Do you know why it loads old stock recovery ?
vv7v7 said:
Thank you for your reply really.
By the way, I've already tried to flash a custom recovery like TWRP 3.2.1.0, but after rebooting into recovery the old recovery had been shown, even if fastboot tells that everything regarding flashing is OK, so I though it's just locked. Do you know why it loads old stock recovery ?
Click to expand...
Click to collapse
Is it really the old recovery, or just a screen with a bunch of yellow buttons? If it's the latter, did you try touching the "recovery" button and THEN the left-side button (there will be a blue and a green button shown)?
After that the phone will boot twrp.
If it's really the old recovery, how did you flash twrp? Through adb? Did you try just booting twrp instead of flashing it? Like "fastboot boot twrp.img" ?
NTLinhHaHa said:
Is it really the old recovery, or just a screen with a bunch of yellow buttons? If it's the latter, did you try touching the "recovery" button and THEN the left-side button (there will be a blue and a green button shown)?
After that the phone will boot twrp.
If it's really the old recovery, how did you flash twrp? Through adb? Did you try just booting twrp instead of flashing it? Like "fastboot boot twrp.img" ?
Click to expand...
Click to collapse
Thank you for your reply really.
Yes, I've used adb and did everything like in this article ( where "Install via ADB" ). So, after that, when clicked on "recovery" ( in menu like you've described above ) it asked me something like "Am I sure to proceed ?", so I accepted this one with a blue button "OK" and it went to "MI-Recovery 3.0" like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
( image's from internet )
vv7v7 said:
Thank you for your reply really.
Yes, I've used adb and did everything like in this article ( where "Install via ADB" ). So, after that, when clicking on "recovery" and accepting with blue button "OK" it goes to "MI-Recovery 3.0" and shows:
( image's from internet )
Click to expand...
Click to collapse
While "installing via ADB", did your phone actually rebooted into Fastboot mode? (the screen showing an android and the word "FASTBOOT" on it)
Try it this way: while the phone is on, reboot the phone via power menu. When the Mi logo appears and the device vibrates a bit, start holding both "Power" button and "Volume down" button (Vol-) until the phone vibrates again. Release both buttons. THEN plug the phone to PC, open adb command prompt window. Assuming the twrp image on your computer is named twrp3210.img, here's the code you need to enter:
Code:
fastboot flash recovery twrp3210.img
After that, go to recovery like you normally do.
That should work.
Remember from now on: Power + Vol- = Fastboot; Power + Vol+ = Recovery. You cannot go to recovery or bootloader from adb in MIUI stock rom.
NTLinhHaHa said:
While "installing via ADB", did your phone actually rebooted into Fastboot mode? (the screen showing an android and the word "FASTBOOT" on it)
Try it this way: while the phone is on, reboot the phone via power menu. When the Mi logo appears and the device vibrates a bit, start holding both "Power" button and "Volume down" button (Vol-) until the phone vibrates again. Release both buttons. THEN plug the phone to PC, open adb command prompt window. Assuming the twrp image on your computer is named twrp3210.img, here's the code you need to enter:
Code:
fastboot flash recovery twrp3210.img
After that, go to recovery like you normally do.
That should work.
Remember from now on: Power + Vol- = Fastboot; Power + Vol+ = Recovery. You cannot go to recovery or bootloader from adb in MIUI stock rom.
Click to expand...
Click to collapse
Thank you.
So, I've done the same as you described:
The "fastboot" text was show with a rabbit like
( image's from internet ), so after I've executed the command:
Code:
fastboot flash recovery twrp3210.img
it shows something like:
( image's from internet ) and after just turned off the phone. Then I've pressed Power + Vol+ and it shows the chinese menu like:
( image's from internet )
vv7v7 said:
Thank you.
So, I've done the same as you described
Click to expand...
Click to collapse
Yes, and then press recovery and then the left-side button.
NTLinhHaHa said:
Yes, and then press recovery and then the left-side button.
Click to expand...
Click to collapse
Thank you.
As you could notice from previous messages
So, after that, when clicked on "recovery" ( in menu like you've described above ) it asked me something like "Am I sure to proceed ?", so I accepted this one with a blue button "OK" and it went to "MI-Recovery 3.0" like:
Click to expand...
Click to collapse
already done this one and got stock recovery.
vv7v7 said:
Thank you.
As you could notice from previous messages already done this one and got stock recovery.
Click to expand...
Click to collapse
How about typing into fastboot:
Code:
fastboot oem device-info
Does the returned message say that you are unlocked?
How about trying a different twrp image?
NTLinhHaHa said:
How about typing into fastboot:
Code:
fastboot oem device-info
Does the returned message say that you are unlocked?
How about trying a different twrp image?
Click to expand...
Click to collapse
Thank you.
The command above gave:
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.005s
I've tried to boot into TWRP with "fastboot boot twrp.img" exactly after flashing "twrp.img", so it booted into TWRP normally, but after reboot into bootloader and choose a recovery it booted into stock rom recovery as before.
Old TWRP versions don't have some features which has 3.2.1.0, so it's rather interesting why this one doesn't boot after flashing and rebooting.
Although, there's a chance that stock rom reflashes recovery each reboot, so that's why. What do you think, is it possible ?
vv7v7 said:
Thank you.
The command above gave:
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.005s
I've tried to boot into TWRP with "fastboot boot twrp.img" exactly after flashing "twrp.img", so it booted into TWRP normally, but after reboot into bootloader and choose a recovery it booted into stock rom recovery as before.
Old TWRP versions don't have some features which has 3.2.1.0, so it's rather interesting why this one doesn't boot after flashing and rebooting.
Although, there's a chance that stock rom reflashes recovery each reboot, so that's why. What do you think, is it possible ?
Click to expand...
Click to collapse
You can totally see from the returned message that your device is unlocked. Yes, and possibly stock rom reflashes recovery each boot. So your way should be to boot twrp.img, wipe System, Data and all caches. install a new rom, and then reboot to fastboot to flash twrp.img into recovery =)))
NTLinhHaHa said:
You can totally see from the returned message that your device is unlocked. Yes, and possibly stock rom reflashes recovery each boot. So your way should be to boot twrp.img, wipe System, Data and all caches. install a new rom, and then reboot to fastboot to flash twrp.img into recovery =)))
Click to expand...
Click to collapse
Thank you.
By the way, in case of leaving stock rom on board and wiping Data and Caches will turn rom to factory reset, but will leave it, is it right ?
vv7v7 said:
Thank you.
By the way, in case of leaving stock rom on board and wiping Data and Caches will turn rom to factory reset, but will leave it, is it right ?
Click to expand...
Click to collapse
Yeah, wipe data + cache = factory reset