Nexus 5 rebooting loop with dead Recovery mode ! any help ?
Welcome Dears
Before 1 week ago, my nexus 5 went into rebooting loop, it was a hardware issue, and after I replace the power button
still the phone rebooting on Google logo every second, when I connect it to the charger, its charging without problem until get a full charged battery, so I think it is not a battery issue, and I can enter the fastboot mode without rebooting, so I think its not a hardware issue now, it was and its goes out !
the problem also when I enter the recovery mode , "No Command" with android logo appears, then I press the Volume Up button then I get the recovery mode command, but unfortunately my PC can't see the phone, so I can't use the "adb sideload" command to flash my MIUI ROM (Version: 5.8.6) again
Code:
adb sideload MIUI.zip
error: device not found
but in the fastboot my PC can connect with Nexus, so I try to flash the CWM/TWRP recovery , I got these replay from the command,
Code:
C:\adb>fastboot flash recovery hammerhead-cwm-6.0.4.4-unofficial.img
< waiting for device >
sending 'recovery' (10498 KB)...
OKAY [ 0.453s]
writing 'recovery'...
OKAY [ 0.847s]
finished. total time: 1.302s
C:\adb>
but unfortunately when I repeat my nexus to recovery mode I didn't get the new flashed recovery ! still stuck on the dead old one !
when I use from recovery mode the "wipe data/factory reset" I got these three line then flashing on "no command" dead recovery logo
Code:
--wiping data. . .
Formatting/data. . .
Formatting/cache . . .
then go into "no command" dead recovery logo flashing until I force it shutdown by power button !
same result by "wipe cache partition" command
my Next step to flash the factory image by fastbood command but this solution will remove all files & pictures & Videos & my notes isn't it ?!
so if that is right ? do you have any other solution to run up my nexus and avoiding these rebooting loop or flash new recovery / custom ROM without loosing my data ?! " I am not afraid of loos any Apps and data of them" I need my sound files, videos, pictures and notes.
Pictures below for more clarify the issue !
I get "No Command" when I enter the Recovery mode, until I press the Volume Up
http://store2.up-00.com/2015-08/1440196110631.jpg
The pictures of Dead Recovery Mode commands
http://store2.up-00.com/2015-08/1440196110722.jpg
Thank you.
try this (maybe you just missed the second command - afaik without the bootloader reboot the flashed recovery won't stick):
Code:
fastboot flash recovery /path/to/recovery.img
fastboot reboot-bootloader
and then try to reboot into recovery on your phone
if this doesn't work:
just download stock image, unpack it, open the flash-all.xxx (bat for windows / sh for linux) and remove the "-w" from the last line.
(this will prevent the script from wiping all of your data.)
then just execute the script.
afterwards you can flash the recovery (see above - and don't forget the reboot-bootloader thingy ^^).
and in custom recovery you can install your zips (custom rom and supersu).
Hi b666m
Thank you for your support & teach me new info & steps
I tried your first idea with the two commands, but unfortunately still the recovery stuck on the old one, I tried with three files of recovery image !
I will try your 2th solution but I have to ask you again and double check if I got it correctly to avoid any missing of my important files & Pictures.
as my OS Windows, you mean I have to open "Flash-all.bat" file and delete the "-W" from the flashing command
"fastboot -w update image-hammerhead-ktu84p.zip"
picture bellow for more clear
{
"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"
}
is it like that ? and that will not delete my files after I double click the flash-all.bat file ?
Thank you again for your support. :good:
The last command which contained "-w"
Code:
"fastboot update image-hammerhead-ktu84p.zip"
will flash the "image-hammerhead-ktu84p.zip" file ,
which is already has a "userdata.img" file inside it , I think this is will formatting the userdata also and write new data isn't it ?
as that is mentioned in this link:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Code:
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
(Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)
is that right ?
Yes that is right. Not to change tactics here... But one use twrp recovery because support for cwm ended over a year ago. If you after going to flash factory images I would unzip and flash them all individually except for the userdata.img which would wipe your sd.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 10:18 PM ---------- Previous post was at 10:16 PM ----------
Follow method two in the how to flash factory images thread you linked. What was suggested before was to open and edit the flash-all.bat script by removing the -w in the script which would wipe. The flash-all has given people issues in the past and by doing each one individually you can see them succeed individually.
Sent from my Nexus 5 using Tapatalk
The best way to solve your problem . it will 100% work I can assure you . download nexus root tool kit on you PC and once downloaded install and then open the application then .. Put your nexus 5 into bootloader if possible and connect the phone to you PC with the OEM USB cable . in the application on the PC you will see unroot and below that an option (soft brick ) chose that and press unroot follow the step and your phone will be fine . I hope I will get a positive feedback from you . enjoying using your nexus 5
Sent from my A0001 using Tapatalk
Dear @jwhyte : Thank you very much for your support and clarify the issue of flashing the userdata.img , I will go with your idea to flash every file individually except the userdata.img file.
Dear @adarshdeep : thank you very much for you support, the nexus root tool kit App was very great, and the "flsh stuck + unroot" with "soft brick" has an a good choosing with "No Wipe Data", but unfortunately my Nexus still in Bootloop after I applied this good idea,
The nexus tool kit succeed to flash the
bootloader, radio, recovery, system and I leaved the Nexus for 30 minutes after I read these info but still same issue
Code:
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
any advice please ?
The new update of my trials also:
I got a connection between my Nexus and My Work PC by ADB sideload mode,
and I applied this command to flash the ROM:
Code:
adb sideload Rom.zip
and the adb uploaded reach the 100%
and the Nexus 5 start to flashing the ROM, but it didn't complete and this is the output messages on the nexus screen:
Code:
Now send the package you want to apply
to the device with "adb sideload <filename>" ...
Restarting adbd ...
Finding update package ...
Opening update package ...
Verifying update package ...
Installing update ...
symlink: some symlinks failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
what is the symlinks failed and (Status 7 Error) ? there is any solution for this error message ?
Thank you for support to recover my Nexus and files, I have tried for one week now, and I am sure I will get the solution with your support :highfive:
unfortinatily when I tried to flash every file as individual, the adb tools replay with FAILED message (FAILED (remote: flash write failure))
even if I used these three commands before
fastboot erase system
fastboot erase cache
fastboot erase boot
the messages replay by adb
Code:
C:\adb>fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.299s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.499s
C:\adb>fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
sending 'radio' (45409 KB)...
OKAY [ 1.617s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 1.797s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
C:\adb>fastboot flash system system.img
erasing 'system'...
OKAY [ 0.119s]
sending 'system' (721400 KB)...
OKAY [ 23.172s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 23.473s
C:\adb>fastboot flash boot boot.img
sending 'boot' (8700 KB)...
OKAY [ 0.387s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.567s
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (9284 KB)...
OKAY [ 0.417s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.591s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.213s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
is that means the mobile is hard break ?!
When I tried to Flash Stuck by the "nexus root tool kit" without wiping data, I got failed in this log for:
bootloader + radio + system, and pass for boot + recovery
Code:
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3119 KB)...
OKAY [ 0.305s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.513s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
sending 'radio' (45425 KB)...
OKAY [ 1.611s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.839s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
sending 'boot' (8980 KB)...
OKAY [ 0.487s]
writing 'boot'...
OKAY [ 0.746s]
finished. total time: 1.241s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
sending 'recovery' (9696 KB)...
OKAY [ 0.506s]
writing 'recovery'...
OKAY [ 0.795s]
finished. total time: 1.307s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
erasing 'system'...
OKAY [ 0.115s]
sending 'system' (1021840 KB)...
OKAY [ 32.279s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 32.587s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.006s
Post-Flash Factory Reset...
downloading 'boot.img'...
OKAY [ 0.420s]
booting...
OKAY [ 0.107s]
finished. total time: 0.537s
You should now see an android on its back with an exclamation point.
This is the 'Pre-screen' to stock android recovery. It requires a button
combination to bring up the menu:
1. While holding down Power, press Volume Up
2. Using the volume buttons highlight 'wipe cache partition'
3. Use the power button to select it.'
4. Wait while it formats 'cache'....
4. Select 'reboot system now'
Press any key to cotinue...
any help to understand why the flashing of bootloader + radio + system were failed ?!
@M_Nexus5. Out of curiosity what happens if you try locking your bootloader in fastboot and rebooting? Does the bootloader stay locked?
fastboot oem lock
fastboot oem device-info
Sent from my Nexus 9 using XDA Free mobile app
Dear @jd1639 : thank you very much for your support, I will try your idea and submit the result here, but if the bootloader be lucked and can't be unlock again we will loos this feature of unlocked bootloader isn't it ?
Now I have a good news I got & copy all my files, :highfive:
I play with some features of Nexus root kit tool and try to flash stock Rom and there were a failed as I mentioned that in my last posts,
I flashed each failed X.img, individually under "Fastboot Flash" menus in "Advanced Utilities" Section,
Then I press Custom recovery Under "Fastboot Boot" in "Advanced Utilities" Section, I think this option is the key because it forced the Nexus to run into TWRP recovey mode :good: "but without flash it, because when I reboot by device to recovery mode again I got the dead old one !!
and this recovery "TWRP" support the "Enable MTP" protocol, so after that I got a connection for my nexus as a storage with my PC and copy All files & Pictures,
I Can copy from the device, but I con't copy from my PC to it.
but there are some Error message in the log of TWRP recovery mode:
Code:
Updating partion details
[COLOR="Red"]E: Unable to mount '/Persist'[/COLOR]
...done
Full SELinux support is present.
[COLOR="Red"]E: Unable to open '/cach/recovery/.version'.[/COLOR]
MTP Enable
also when I tried to flash the slim Rom by install option I got some error message , the TWRP can't flash the Rom here are the messages:
Code:
when I tried to flash a ROM.zip file I got some error messages like this:
Format and Mount System, Mount Data ...
Symlinks and Permissions ...
symlink: some symlinks faild
[COLOR="Red"]E: Error executing updater binary in zip '/sdcard/Zip File sh Update File/Slim-4.4.4.zip[/COLOR]
Error flashing zip 'sdcard/Zip flash Update File/Slim-4.4.4.zip'
Updating partition details...
[COLOR="Red"]E: Unable to mount '/persist'[/COLOR]
...done
also I tried to flash the same my Nexus ROM, (MIUI 4-4-4), but I got same result & Error messages, all Rom already on my sdcard before 4 months maybe.
When I tried "Cache & Dalvik Wipe Complate", I got same error.
Code:
Wiping Dalvik Cach Directories...
Cleaned: /data/dalvik-cach...
-- Dalvik Cach Directories Wipe Complete!
Updating partition details...
[COLOR="Red"]E: Unable to mount '/persist'[/COLOR]
Now may if I flash the stock factory image with wiping all data "its default" solve the problem ?!
or the error message above shown something wrong with device ? or need a certain tool to fix it ?!
or I can fix this issue by "Mount" option in the TWRP Recovery ?! I never used this option !
I will try to flash the stock factory image when I come back to the home.
The big important thing was my files and I got them now by your support, Thaaaanks :fingers-crossed:
the next step, am I get my device back or need to buy new one ?! :cyclops:
Thank you again for your support and I hope the log error messages will give more help to explain the real issue for you.
Well it sounds like you got what you wanted... However from what I've been able to find the errors you are running up against is not good. It sounds like the failed to flash errors and if you boot into twrp which you did and you get mount problems there is a very good chance your sd is fried.
The reason @jd1639 asked about the OEM lock I believe is if it won't stay locked or unlocked it is sd issue.
You can try contacting Google about an RMA however by you replacing there power button they most likely won't accept it.
Good luck glad you got your files.
Sent from my Nexus 5 using Tapatalk
@jd1639 this is the result of the commands, the bootloader is locked now, but return back when I restart the device !
Code:
C:\adbToolsss>fastboot oem lock
...
OKAY [ 0.037s]
finished. total time: 0.037s
C:\adbToolsss>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) off-mode-charge: true
OKAY [ 0.004s]
finished. total time: 0.004s
C:\adbToolsss>
after restarting the device:
Code:
C:\adbToolsss>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) off-mode-charge: true
OKAY [ 0.004s]
finished. total time: 0.005s
C:\adbToolsss>
Dear @ jwhyte , yes it was a good luck when I got a copy of my files, but do you mean that is the error message of "Unable to mount" is the sdcard/storage of devices damaged and can't be fix ?!
about the RMA, my devices already out of warranty, I bought it more than one year ago.
so now go ahead to choose & buy a new device ?
Update:
@D1639
may I got it here in the link of your post
http://forum.xda-developers.com/showpost.php?p=50142493&postcount=14
now the emmc of device is damaged , and I have to buy new device no other solution for this damage whatever software/hardware ?
M_Nexus5 said:
Update:
@D1639
may I got it here in the link of your post
http://forum.xda-developers.com/showpost.php?p=50142493&postcount=14
now the emmc of device is damaged , and I have to buy new device no other solution for this damage whatever software/hardware ?
Click to expand...
Click to collapse
If you can't lock/unlock your bootloader there probably isn't anything you can do. But I'd give this a try, http://forum.xda-developers.com/showthread.php?p=59154061
Sent from my Nexus 5 using XDA Free mobile app
Have a look at this thread: http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Sent from my Nexus 5 using Tapatalk
@jd1639 after I tried that idea still the device into Bootloop, and I checked the EMMC by "BoardDiag" tool, and I got failed , so may as you said nothing can I do with that issue, but I didn't given up yet, I already bought new OnePlus Two,because no more time for new trials, may I have to try new ideas again next week or after that, Thank you very much my dear, you are very helpful.
@efrant thank you for this link, this is a good idea too, I tried it but faced an issue with using & installing Universal Naked driver, some times the Adb tools can't connect with device in recovery mode, I will try it again and again next week when I have a time and using new PC to install the Universal Naked Driver for recovery only to avoid any other drivers for android.
All dears helpers , thank you very much for your helping,
when I have more time next week I will try some of new idea,
if I get any solution I will submit here the link to be a reference for other
who may face same issue,
Thank you again.
M_Nexus5 said:
[snip]
@efrant thank you for this link, this is a good idea too, I tried it but faced an issue with using & installing Universal Naked driver, some times the Adb tools can't connect with device in recovery mode, I will try it again and again next week when I have a time and using new PC to install the Universal Naked Driver for recovery only to avoid any other drivers for android.
Click to expand...
Click to collapse
It seems you are trying to solve too many issues at once.
The first thing you need to do is make sure your drivers are installed properly, which doesn't seem to be the case. You shouldn't have to mess around with any unofficial drivers. Just install the drivers from Google's website: whttp://developer.android.com/tools/extras/oem-usb.html. That is the first thing you need to make sure is done properly.
The next is to make sure you have the latest version of the four files you need (fasboot.exe, adb.exe, & the 2 dll files) to connect with your device.
Only then should you try to troubleshoot / fix your device.
Sent from my Nexus 5 using Tapatalk
You definitely need to fix your persist partition. Your phone will not boot until you do that.
For this to work you need adb to connect to the phone in normal mode (not bootloader).
Installing the naked driver can be problematic, if another driver is already installed. The easiest way is to install it another PC that has not had an Android phone connected to it. You need to disable internet when you connect the phone, and try to cance windows installation of the driver. Then you will have a device with an error in device manager, you right click on it and choose update driver, and choose manual install from the naked driver folder.
If you can't do that, see if you can use the custom recovery to change the phone to connect usb as a camera.
Now open device manager: if you see Android device >Android Composite ADB Interface then adb should work. Try adb devices command. If you see a device you are connected. Then follow bitdomo's guide to fixing the persist partition. You need to be rooted for this to work. You can skip the wifi and BT foe now - you don't need that to boot into the OS. You can do this later.
Once you fix the persist partiton you should be able to boot. Perhaps it will be a good idea to flash stock, but make sure to enable usb debugging, in case you have future problems.
You can see my guide here http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
Related
Hello,
I have a lenovo a396(phone) recently.
It acts wired when dealing with fastboot commands, and looks incredible to root(more info at bottom of this post)
And the Lenovo Customer Service stuff says this phone is not able to flash via fastboot and told me I am only able to flash it via recovery <3e>
Is that even possible???
If yes,
how can I even bypass the 3e signature veriation to flash a custom ROM
EDIT: I have a stock update.zip in my hand!
thank you very much for saving me another one week's spare time
dye
FYI:
fastboot erase cache
erasing 'cache'...
FAILED (remote:unknown partition name)
finished. total time: 0.003s
fastboot erase system
erasing 'system'...
FAILED ( remote:unknown partition name)
finished. total time: 0.003s
fastboot boot zImage initramfs.cpio.gz
___FYI___ the zImage and initrd are unmkbootimg from the boot.img via stock updat.zip
creating boot image...
creating boot image - 10975232 bytes
downloading 'boot.img'...
OKAY [ 0.529s]
booting...
OKAY [ 0.197s]
finished. total time: 0.726s
fastboot oem h
...
[PS: after this three dots, hehe, you doomed to wait forever. cuz the process's status turned into D+ ie, waiting for IO]
Lenovo A397
Android 2.3.5
Kernel 3.10.17
Hardware_ver H201
verA397_S162_140528
if more hardware info requested, please post that
device: VZW motorola droid razr hd xt926 - completely stock, no customizing at all, every update that came to the phone I installed without problem.
About a month ago (~dec 16, 2014 I believe) the phone was lagging and unresponsive so I powered down, restarted, and that is when the problem began. Upon restart the phone got to the red motorola logo and would hang there. holding the power button would power down for a second, then restart.. so I soft reset it to the boot menu where it atleast wasnt heating up drastically. I left it plugged in because there was no way to power down. From there I began researching the xt926 and seeing other people's problems about the phone hanging at boot logo.
I scoured these forums (and numerous others) for problems similar to mine. Since I was able to get into the boot options menu I've tried everything I could find.. rsd lite, rsd flasher, motorola device manager, house of motorola, droid razr utility...
I tried for about 5 days straight and gave up, took it to a local cell repair place and asked what they would do to repair it. They mentioned a few of the things I tried and said that I had went further than they would go. Out of pity (I believe) they gave me an old BB curve which I've been using the last month. I've been shopping around lately for new phones and wanted to give the razr hd one last crack before relenting and getting a new phone (either S5 or HTC one M8).
First question I guess is, is the phone unusable and beyond repair? upon power up, the phone gets to the red motorola logo for about 2 seconds then goes to this presumed fail boot screen.
it lists:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-07-29 03:17:13)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode: USB Connected
Load kernel (boot) failed
Fastboot Reason: Boot Failure
I can restart the phone from here by clicking the power button, it restarts, hits logo screen, then right back here.
I can get to the boot selection screen by holding the volume up button when its restarting.. it'll get to the boot menu and then restart after about 3 seconds of idle time if I dont pick something quickly.. the 5 options at the boot selection are:
Normal Powerup
Recovery
AP Fastboot
Factory
BP Tools
Normal Powerup, Factory, and BP Tools do nothing.. the phone restarts and hits logo screen then boot failure.
AP Fastboot restarts phone and goes to the same boot screen, but instead of the load kernel boot failure stuff it says: Fastboot Reason: Key Pressed. This is the same result as during powerup/restart holding the volume down key.
Recovery restarts, gets to logo screen, then after about 5 seconds gets to the droid dude with the red exclamation triangle over his open chest. From here I can get it into the recovery mode with 5 selections..
reboot system now
apply update from sdcard
apply update from ADB
wipe data/factory reset
wipe cache partition
All of that being said.. do I have any options to get this phone functional?
Your time and effort is greatly appreciated.
Cheers
I'm assuming that you tried the wipe data from recovery option ? And then to be clear did you actually download and install a factory image using RSD?
i would try rsd lite again with all the latest version of the fxz/sbf in case you were using an old one. this thread from @SamuriHL http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083 is the latest for the xt926 make sure you have the moto drivers installed. if you need i can help with teamviwer or hangouts if you want just pm me for details.
as a side note i do not think that your phone is dead just soft bricked.
---------- Post added at 10:21 PM ---------- Previous post was at 10:14 PM ----------
randymancanstand said:
device: VZW motorola droid razr hd xt926 - completely stock, no customizing at all, every update that came to the phone I installed without problem.
Cheers
Click to expand...
Click to collapse
__
I appreciate the input, sorry for the delay in my response.
I'm assuming that you tried the wipe data from recovery option ? And then to be clear did you actually download and install a factory image using RSD?
Click to expand...
Click to collapse
yes, I factory wiped and using rsd lite, droid razr utility, rsd flasher I tried many different images.. through different iterations and combinations. When rsd lite had no effect installing the different images I had, I moved onto a different program. I wasnt exactly sure which image the system required.. I went through the following:
VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC.xml
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
VZW_XT926_4.4.2-KDA20.62-10_1FF.xml
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
I am unsure if they are 'factory' images
i would try rsd lite again with all the latest version of the fxz/sbf in case you were using an old one. this thread from @SamuriHL http://forum.xda-developers.com/droi...46-15-t2873083 is the latest for the xt926 make sure you have the moto drivers installed. if you need i can help with teamviwer or hangouts if you want just pm me for details.
as a side note i do not think that your phone is dead just soft bricked.
Click to expand...
Click to collapse
I am glad to hear that the phone may have a chance yet. I will look into the latest image. I have RSD Lite v6.2.4.. could someone remind me of the basic flash process?
connect the phone to my pc
put the phone into fastboot,
load up rsd lite
load up image in rsd lite
????
profit?
Again, thank you for your time.
edit: I also have motorola mobile driver 6.4.0 installed
RSD Lite v6.2.4
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
When i click start it fails and gives status:
Failed flashing process. 1/17 flash partition "gpt.bin" -> Phone returned FAIL.
Am currently trying house of moto..
randymancanstand said:
RSD Lite v6.2.4
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
When i click start it fails and gives status:
Failed flashing process. 1/17 flash partition "gpt.bin" -> Phone returned FAIL.
Am currently trying house of moto..
Click to expand...
Click to collapse
this may sound to simple but are you unziping the sbf/fxz?
billycar11 said:
this may sound to simple but are you unziping the sbf/fxz?
Click to expand...
Click to collapse
yes definitely
okay maybe your partitions are messed up then i have seen @bweN diorD help people with that before so he may be able to help.
randymancanstand said:
yes definitely
Click to expand...
Click to collapse
flash this in fastboot. use the data wipe batch file.
if the phone doesnt boot fully to the setup screen within 10min after flashing, its likely toast.
edit,
on second thought, dont close the prompt until you see if it boots up or not. if not, copy all the text from inside the prompt and post it here for me to look at.
thanks
The download is going incredibly slow, but when its done I will flash it and report back.
Thanks for the direction
randymancanstand said:
The download is going incredibly slow, but when its done I will flash it and report back.
Thanks for the direction
Click to expand...
Click to collapse
so the download is crawling along.. it has finished prematurely a couple times already. I'll open the .rar and it says its incomplete.
Is this for matt's droid utility? I have a copy of it I got on 12/17/14.. with an fxz labeled:
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_RSD
I'll keep trying the download from the link you provided in the mean time
randymancanstand said:
so the download is crawling along.. it has finished prematurely a couple times already. I'll open the .rar and it says its incomplete.
Is this for matt's droid utility? I have a copy of it I got on 12/17/14.. with an fxz labeled:
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_RSD
I'll keep trying the download from the link you provided in the mean time
Click to expand...
Click to collapse
You need to use the one I just provided.
Not sure what's up with the DL speeds, my account is paid, so that almost never happens.
bweN diorD said:
You need to use the one I just provided.
Not sure what's up with the DL speeds, my account is paid, so that almost never happens.
Click to expand...
Click to collapse
no dice...
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*] Maintained by bweN diorD
[*] Before continuing, ensure your device is in the
[*] "AP Fastboot" mode and connected via USB.
[*] Be VERY aware! This WILL wipe your userdata, including contacts, apps, etc.
[*] I am not responsible if this wipes your internal sdcard, and you should
[*] backup anything worth it to you to your external sdcard and computer before
[*] you choose to continue. You can exit now with the X button on this window.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] This script will also wipe your data (did i mention this will wipe your data
?).
[*] Press any key to continue.
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.340s
sending 'sbl1' (101 KB)...
OKAY [ 0.030s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.160s
sending 'sbl2' (127 KB)...
OKAY [ 0.030s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.160s
sending 'sbl3' (512 KB)...
OKAY [ 0.060s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.350s
sending 'rpm' (140 KB)...
OKAY [ 0.030s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.300s
sending 'tz' (210 KB)...
OKAY [ 0.030s]
writing 'tz'...
Failed to erase partition
Failed to flash partition tz
FAILED (remote failure)
finished. total time: 0.300s
sending 'aboot' (256 KB)...
OKAY [ 0.040s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.310s
sending 'modem' (30720 KB)...
OKAY [ 2.400s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.540s
sending 'fsg' (165 KB)...
OKAY [ 0.030s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.160s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.050s
sending 'logo' (854 KB)...
OKAY [ 0.090s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.220s
sending 'boot' (10240 KB)...
OKAY [ 0.810s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.550s
sending 'recovery' (10240 KB)...
OKAY [ 0.822s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.556s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
sending 'system' (30720 KB)...
OKAY [ 2.400s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 4.010s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.053s
erasing 'cache'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.010s
Hit ENTER to return.
Sorry, but throw it in the trash and move on.
I have seen this exact scenario many times, its not fixable.
bweN diorD said:
Sorry, but throw it in the trash and move on.
I have seen this exact scenario many times, its not fixable.
Click to expand...
Click to collapse
I figured as much.. any idea what could bring this on?
Like I said, no modifications to the phone, it was lagging/hanging so I restarted it.. simply would not boot afterward..
Anyway, thanks for your time and effort. Atleast I know for sure it is done with.
Cheers
randymancanstand said:
I figured as much.. any idea what could bring this on?
Like I said, no modifications to the phone, it was lagging/hanging so I restarted it.. simply would not boot afterward..
Anyway, thanks for your time and effort. Atleast I know for sure it is done with.
Cheers
Click to expand...
Click to collapse
no one seems to know whats causing it. some have mods, some dont. the hole device just seems to become write protected for no reason.
Hello, on March 10th I received a new update on my N5. After update, which finished with no problems as usual, my phone was normally working or about two more hours. In that time no new apps were installed. Then it just shut down, and can't be properly turned on.
It always stuck at Google logo and that is all that it does. I'm able to get to the fastboot mode by holding Power+Volume Up+Volume Down buttons, but I can't get into Recovery Mode option to hard reset it. Nothing show up after selecting that option and Power+Volume Up does nothing. Ok, bad luck, time to flash it nice and clean.
Haha, nice try.
I'm not sure if I had USB debugging on or off, but I think off. Obtained ROM from Google + newest platform tools from SDK and followed all possible manual I could get from Internets, results:
Code:
adb devices
List of devices attached
*nothing*
Code:
adb reboot bootloader
error: no devices found
Drivers are newest from Google, reinstalled several times, device is visible in Windows as Android Bootloader Interface and seem working fine. adb just do not see phone.
Code:
fastboot oem unlock
...
OKAY [ 46.402s]
finished. total time: 46.403s - WORKS!
But rest is just no go:
Code:
fastboot erase boot
erasing 'boot'...
FAILED (remote: failed to erase partition)
finished. total time: 0.219s
Code:
fastboot erase cache
********Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.217s
Code:
fastboot erase recovery
erasing 'recovery'...
FAILED (remote: failed to erase partition)
finished. total time: 0.219s
Code:
fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.218s
I tried several more commands, like to install twrp, but all with same results.
Code:
fastboot flash recovery twrp.img
sending 'recovery' (14314 KB)...
OKAY [ 0.653s] writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.835s
I also tried "fastboot boot twrp.img" and it worked but didn't helped much. Internal storage is showing size 0 MB an when I try to do anything it ends with wall of red text about how it's unable to find partitions or mount images, first line:
Code:
E:Primary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data' is not present!
Also when I reboot bootloader, it get stuck and when I get it back with buttons, it is back in its locked state. So my guess is that eMMC went to Silicon Heaven.
Do you guys have any advices? Or is my phone just fancy mirror now?
When the phone is in fastboot mode, does the bootloader state remain "unlocked" after a reboot?
If the bootloader is unlocked, have you tried relfashing a stock ROM?
audit13 said:
When the phone is in fastboot mode, does the bootloader state remain "unlocked" after a reboot?
If the bootloader is unlocked, have you tried relfashing a stock ROM?
Click to expand...
Click to collapse
Like i wrote, it get back to locked state.
The emmc chip is defective and cannot be fixed. This is clearly indicated when the bootloader relocks itself at reboot.
Thought so, but wanted confirmation . Thank you.
I got a Nexus 5 that won't boot. When you turn it on normally it hangs on the Google logo indefinitely. Recovery mode results in the red triangle logo. The only thing that 'works' is fastboot. But when I plug it into any of my PC's they all say: unknown usb device (device descriptor request failed) in the device manager.
I've tried installing various drivers, but it won't detect my phone in any way. As long as the descriptor isn't known by Windows it cannot install any driver. It will just resort back to the error message. Is there any way for Windows to recognize my device again?
I've tried various PC's and USB cables / ports. It's the device at fault not my other hardware for sure.
I plugged in my Galaxy S6, and it works just fine. Now the funny thing is when I plug back to Nexus 5 it is all the sudden recognized. I flashed the stock firmware back and it hang on the google logo again. Now going to fastboot the device is not recognized again. Recovery mode now also results in a Google logo that is stuck instead of the triangle.
After some retries I can connect in fastboot and the device is recognized as: "android bootloader interface"
Now how can I unbrick it? I am able to flash something to the device, i've tried the Restore_Nexus_5_KTU84P toolkit. It flashes but when it's done the phone reboots into the same brick mode.
When I manually try to flash an .img it says:
FAILED (command write failed (Unknown error))
The bootloader remains unlocked when the phone is rebooted? What OS is on the computer? Tried different USB ports and USB cables?
Tried with Ubuntu and I can flash stable now. But no matter what stock OS I flash (tried 6,5,4.4) after that flashing is done and the phone reboots it stuck on the google logo again. Any options beside throwing it in the bin?
And yeah, the bootloader stays unlocked.
Tried the unbrick method as shown here:
http://forum.xda-developers.com/goo...ck-nexus-5-stucked-qualcomm-hs-t3043301/page1
Flashes fine, also the memory tests pass. But it doesn't change the situation at all.
If when you try to lock or unlock the bootloader and after a reboot the locking or unlocking didn't take that usually means the emmc is bad.
Sent from my Nexus 9 using XDA-Developers mobile app
Are you flashing the userdata.img file too? The file should be flashed last. After flashong, immediately boot into recovery and perform a factory wipe, then reboot.
jd1639 said:
If when you try to lock or unlock the bootloader and after a reboot the locking or unlocking didn't take that usually means the emmc is bad.
Sent from my Nexus 9 using XDA-Developers mobile app
Click to expand...
Click to collapse
Lock / unlock sticks just fine.
audit13 said:
Are you flashing the userdata.img file too? The file should be flashed last. After flashong, immediately boot into recovery and perform a factory wipe, then reboot.
Click to expand...
Click to collapse
I did indeed also manually flash all img files including the userdata.
Code:
sending 'bootloader' (2506 KB)...
OKAY [ 0.317s]
writing 'bootloader'...
OKAY [ 0.462s]
finished. total time: 0.779s
rebooting into bootloader...
OKAY [ 0.061s]
finished. total time: 0.162s
sending 'radio' (42033 KB)...
OKAY [ 2.006s]
writing 'radio'...
OKAY [ 2.892s]
finished. total time: 4.898s
rebooting into bootloader...
OKAY [ 0.077s]
finished. total time: 0.278s
erasing 'system'...
OKAY [ 1.125s]
sending 'system' (692940 KB)...
OKAY [ 31.024s]
writing 'system'...
OKAY [ 47.110s]
finished. total time: 79.259s
sending 'boot' (8620 KB)...
OKAY [ 0.615s]
writing 'boot'...
OKAY [ 0.743s]
finished. total time: 1.358s
sending 'recovery' (9202 KB)...
OKAY [ 0.644s]
writing 'recovery'...
OKAY [ 0.775s]
finished. total time: 1.418s
erasing 'cache'...
OKAY [ 0.531s]
sending 'cache' (13348 KB)...
OKAY [ 0.840s]
writing 'cache'...
OKAY [ 1.075s]
finished. total time: 2.446s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.911s]
finished. total time: 6.911s
erasing 'userdata'...
OKAY [ 6.697s]
sending 'userdata' (137318 KB)...
OKAY [ 6.441s]
writing 'userdata'...
OKAY [ 9.135s]
finished. total time: 22.273s
rebooting...
finished. total time: 0.274s
After flashing I cannot enter recovery, cause every mode except for fastboot results in a stuck Google logo.
aapje1299 said:
Lock / unlock sticks just fine.
I did indeed also manually flash all img files including the userdata.
After flashing I cannot enter recovery, cause every mode except for fastboot results in a stuck Google logo.
Click to expand...
Click to collapse
Let's try something. I'm going to have you try to boot into twrp recovery and if you can do a factory reset from that. At the bootloader you'll use the commands fastboot boot twrp.img. Where twrp.img file be the full file name of the twrp recovery image. If you don't know where to get twrp Google teamwin nexus 5. Download that to your pc. If it boots to twrp go to wipe and wipe the device. Then try rebooting to system.
So you can't enter recovery, even from fastboot mode?
I couldn't
Don't ask me how, but today I flashed it again to show my collegue that it wouldn't work. And after flashing it it came alive all the sudden. I'm a happy man! Everything seems to work except for the camera, but that is probably something else!
--
Hmm, disconnected and reconnected the charger, phone froze. Reboot and now it's stuck on the google logo again. I think this phone is toast
--
Another update
I removed the cover, and all the sudden it booted fine again. The battery was loose inside and there was some duct inside to keep it in place. This phone has been repaired before because the screen was broken. I think something is short circuiting in there. I got it booted now and first I'm going to give it a full charge.
I declared it dead, was able to actually get TeamWin recovery flashed and it worked. Then after some time it was dead again and unable to boot. Also the camera was broken. Thanks for thinking along guys!
My Xperia L is soft bricked and its bootloader is unlocked, so Sony PC Companion can't help. I tried Emma ( flashtool for Xperia) too. But it says "No available services matched the connected device." Service log: "Please refer to update session e0251daa-c222-413f-8f3c-5c77b4d9064b if you need to contact Emma support."
The command "adb devices" shows nothing, but "fastboot devices" is recognising my device when connected in fastboot mode. So, following this thread https://forum.xda-developers.com/xperia-l/help/soft-bricked-device-unlock-help-t3240972, I tried to install cwm recovery, using the command "fastboot flash boot boot.IMG". It shows:
Code:
sending 'boot' (6968 KB)...
OKAY [ 0.233s]
writing 'boot'...
OKAY [ 0.474s]
finished. total time: 0.707s
But nothing seems to install on my phone, as when I try to boot into recovery, the phone just tries to boot up and gets stuck in bootloop.
And if I try "fastboot flash recovery boot.IMG" then I get the following:
Code:
sending 'recovery' (6968 KB)...
OKAY [ 0.242s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.244s
How can I fix my phone? Please help! Any help is appreciated! Thanks!!
ankcash said:
My Xperia L is soft bricked and its bootloader is unlocked, so Sony PC Companion can't help. I tried Emma ( flashtool for Xperia) too. But it says "No available services matched the connected device." Service log: "Please refer to update session e0251daa-c222-413f-8f3c-5c77b4d9064b if you need to contact Emma support."
The command "adb devices" shows nothing, but "fastboot devices" is recognising my device when connected in fastboot mode. So, following this thread https://forum.xda-developers.com/xperia-l/help/soft-bricked-device-unlock-help-t3240972, I tried to install cwm recovery, using the command "fastboot flash boot boot.IMG". It shows:
Code:
sending 'boot' (6968 KB)...
OKAY [ 0.233s]
writing 'boot'...
OKAY [ 0.474s]
finished. total time: 0.707s
But nothing seems to install on my phone, as when I try to boot into recovery, the phone just tries to boot up and gets stuck in bootloop.
And if I try "fastboot flash recovery boot.IMG" then I get the following:
Code:
sending 'recovery' (6968 KB)...
OKAY [ 0.242s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.244s
How can I fix my phone? Please help! Any help is appreciated! Thanks!!
Click to expand...
Click to collapse
Please read this post:
https://forum.xda-developers.com/xperia-l/help/how-to-install-twrp-xperia-l-running-t3659340
Or simply use the below method:
Test again with downloading latest TWRP img and flashing it in fastboot mode using command: fastboot flash boot twrp.img
Then power on your phone and immediately press volume up.
It will directly boot to recovery. Screen may fliker, but no problem, just wipe everything and flash your ROM zip file.