Database Users

[Q] nexus 7 wont update, fastboot fails, recovery no go

When i had my nexus 7 i updated to 4.2.1 and then did a factory reset. Upon booting my nexus was back on android 4.1.2(i thought this shouldnt have happened?)
Now the OTA update wont install - i get the dead android with an exclamation mark.
I have downloaded the nexus 7 toolkit to try and unlock the bootloader and flash stock 4.2.1 but i get an error when trying to unlock - FAILED (command write failled (unknown error))
anyone able offer some help please?

ive tried fastboot oem unlock using nexus toolkit and direct through the command line with same results

is this guide any good?
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html

Otherwise you have this GUIDE
Phone:I9100P
Kernel:Dorimanx
ROM:4.2.1 Vanilla RootBox
Tablet:Nexus 7
Kernel:M-Kernel
ROM:4.2.1 AOKP PUB
MOD:JusTunBean

welly_59 said:
When i had my nexus 7 i updated to 4.2.1 and then did a factory reset. Upon booting my nexus was back on android 4.1.2(i thought this shouldnt have happened?)
Now the OTA update wont install - i get the dead android with an exclamation mark.
I have downloaded the nexus 7 toolkit to try and unlock the bootloader and flash stock 4.2.1 but i get an error when trying to unlock - FAILED (command write failled (unknown error))
anyone able offer some help please?
Click to expand...
Click to collapse
It is possible (albeit very slightly) that the file didn't flash correctly, but did corrupt the bootloader just enough to stop it being unlocked/booting into recovery.
If you can't issue the 'fastboot oem unlock' command then it could be for 2 reasons:
1. It is already unlocked (try typing 'fastboot oem lock' and see if it re-locks')
2. The bootloader is slightly corrupt.
Hopefully it is the first one

liamwli said:
It is possible (albeit very slightly) that the file didn't flash correctly, but did corrupt the bootloader just enough to stop it being unlocked/booting into recovery.
If you can't issue the 'fastboot oem unlock' command then it could be for 2 reasons:
1. It is already unlocked (try typing 'fastboot oem lock' and see if it re-locks')
2. The bootloader is slightly corrupt.
Hopefully it is the first one
Click to expand...
Click to collapse
i managed to get it working after erasing everything as in the guide above. I had to keep unplugging the device and trying again though and after a few attempts it worked

when encountering this error i simply cycled through the options (using volume) and said boot into bootloader, familiar windows device dis/connect and then tried the fastboot flash boot boot.img cmd again, worked a treat, currently flashing the system part.
hope this helps!

Blasted kingroot - bricked my phone?

Ahh, hind sight is a wonderful thing.
After trying to use kingroot to get root access, it failed. And a few days later after rebooting.
I'm now stuck at bootup with Start Up Failed.
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
I've now tried lot's of different things, over the last few hours.
RSDLite (show device brings no thing up)
Unlock bootloader (request key, but error regarding OEM unlock not being set - no access to now set it LOL)
Downloaded stock X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip, and tried using various guides on fastboot but keep getting remote failed.
I'm on stock recovery (obviously still locked).
Any thoughts, or hope from anyone?
Obviously, not sure what support Motorola would provide for what is essentially my own fault?

Have you tried manually flashing each bit of the stock firmware/image. That might help. There's a good guide here which I followed to unbrick my device. Just follow the instructions http://theunlockr.com/2015/09/22/how-to-unroot-the-motorola-moto-x-play/

Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926

Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s

sharebubbles said:
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
Click to expand...
Click to collapse
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!

DTLblaze said:
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
Click to expand...
Click to collapse
I run the unlock command, with my unique key but I get ..
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.013s
And since I can't get into the phone, I can't therefore check the "allow OEM unclock"

Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.

DTLblaze said:
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
Click to expand...
Click to collapse
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode

Sickaxis79 said:
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.

sharebubbles said:
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
That really does sound like you bricked the device. If you where on lollipop software you wouldn't have the issue with check bootloader OEM unlock. If it was me I would either contact Motorola or go to a repair shop and have a motd experienced person take a look at it.

Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.

sharebubbles said:
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
Click to expand...
Click to collapse
Strange. This is the tool I used to unlock my bootloader.

drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
I've ben used the latest rom so far why trying to flash (and failing) when I look at recovery I have a LPD23.118-10 number that matches to an earlier 5.1.1 rom (I had been upgraded to 6.0.1 via OTA updates) - do I therefore take that LPD ID to mean that I should actually use the 5.1.1 rom - I'm in the UK, so I'm assuming I'd use the UK one rather than Europe (I'm looking at roms on https://github.com/motoxplay/stock).
Thanks

Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)

sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
And also never try kingroot.

sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
Most in the threads suggesting using rsdlite or manual flash/root and you decided to use kingroot,haha.
Welcome back.

Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
---------- Post added at 05:26 AM ---------- Previous post was at 05:14 AM ----------
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
Tried restoring it, deleted everything and the phone is still on bootloader (LOCKED) and i dont even know how to fix it, I know nothing on how to root, friend suggested it, downloaded it, installed it, didnt work and then i restarted my phone and now its stuck on bootloader screen and the screen has the message "Start up failed: your device didnt start up successfully. Use the software repair assisstant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant." <- Downloaded it, tried it and it was stuck on 6% on repairing, left it over night and it was still on 6%.
ALSO under the message "AP Fastboot Flash Mode(Secure) is there)

Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)

pravin kkr said:
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
Click to expand...
Click to collapse
Download and flash this firmware
https://mega.nz/#!H5YlDCrD!T8tAAW7nHVS-erizRiqg5-Yp_p23hKParMjjHD4diQA credits @kumeipark
Use RSD lite to flash the firmware
http://rsdlite.com/rsd-lite-download/
Moto drivers
http://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/88481
If you have problems installing device drivers using Windows 8.1 or Windows 10 follow this guide
https://www.youtube.com/watch?v=gmw86KplqmU
And don't post your contact no. in public forums for everyone to see.

what is the decryption key for the mega link
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
provide the decryption key

Bricked - Screen Not Turning On

If there is a thread that solves a problem like mine, please point me to it, thanks.
Basically, I had updated my phone to Nougat which resulted in the infamous test-keys build number, instead of the right one (my device is VNS-L31 and it was single-SIM, supposedly.) I was fine with it, but at some point SuperSU auto-updated through the play store and I lost root. So I tried rooting it, but couldn't boot into recovery. Even when I managed to, SuperSU would not flash properly. So I thought I should roll back and do it properly.
I tried the rollback packages through dload from the rollback to MM thread, they wouldn't work. I found another thread that seemed to be describing the 'good way' so I did as it said. Flashed the OEMinfo provided, but then it told me the data partition was damaged. I turned it off and updated through dload, which went to 100%, turned off. And that's that. Screen is not turning on, no tactile feeling from the power button. The only thing that I seem to access is fastboot and only on the pc, the phone shows nothing.
Now I have tried flashing the extracted system, boot and recovery.img from the update zip and even though it says okay, nothing happens. The bootlocker seems to be unlocked still, thankfully I kept the pass!
fastboot oem get-build-number gives 'VNS-C432B120'
Any help would be appreciated.
EDIT: Since flashing the separate images does not seem to work, and fastboot erase system -w results in:
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'system'...
FAILED (remote: Command not allowed)
I think that perhaps the partition table is messed up? Even though as I said the separate images seem to flash fine, without any errors... I tried to flash the whole update.zip or even a couple of ROMs, but it says that there is no android-info.txt. Is there any ROM which includes the android-info.txt or android-product.txt? Or does anyone perhaps know what the .txt should say inside? I have found some threads about HTC phones where they know the content of the .txt file, which is 4 tiny lines mentioning the model ID, main version and such information.

Cannot flash to any partitions

My bootloader is off the rocker right know and I can't seem to get anything done.
Cant access recovery, multiple bootloops, etc. EVEN after flashing stock images from the Dump thread.
Now I cant even do that because nothing wants to flash to the partitions, e.g.
Code:
FAILED (remote: Error flashing partition.)
Code:
c:\tools>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.000s
I'm at a loss here, is there anyway I can fix this?
Thanks guys

jAm-0 said:
My bootloader is off the rocker right know and I can't seem to get anything done.
Cant access recovery, multiple bootloops, etc. EVEN after flashing stock images from the Dump thread.
Now I cant even do that because nothing wants to flash to the partitions, e.g.
I'm at a loss here, is there anyway I can fix this?
Thanks guys
Click to expand...
Click to collapse
I'm sure you've already tried this but, what about the other USB ports? I had this very same issue and it took me about an hour to get my phone to recognize "fastboot -w" again.
If I recall correctly, I had to power off the PC and phone, then downgraded my Minimal ADB and Fastboot and everything started working again surprisingly, commands were recognized and I could wipe and flash with no issues.

Welcome to the club. There are a few of us now. I had this happen when trying to flash TWRP after installing the 8.1 beta. AFAIK there's nothing you can do. I've tried every combination of USB port, cable and OS. Its either a hardware error or somethings ****ed with the bootloader. Essential isn't claiming any responsibility and its just offering a $200 out of warranty replacement to US customers.

General Help - My Nothing is stuck in a boot loop after attempting to root it

I've gotten myself into a bit of a pickle. I just got my Nothing Phone yesterday, and I've already managed to get it stuck in a boot loop. I am still able to access fastboot and my computer still recognises it, so i hope it is still salvageable.
It all started when I stumbled upon this guide, which promised that unlocking and rooting it would be done in minutes. I know next to nothing about rooting phones, but the guide made it seem fairly straightforward. So I gave it a go. Big mistake.
Here's exactly what's happened:
I followed the guide step by step.
At step 2.2 I downloaded the full 1.1.7 (EEA) package from here. Then I extracted the boot image from the downloaded zip by following this guide (still following the main guide).
Flashing it went fine, no errors, but after trying to start it, it just shows the logo for a few seconds and then restarts.
A bunch of googling later, I stumbled upon an xda thread where someone had linked to a website with pre-built images. I tried flashing some of those too, no luck.
Last thing I tried was flashing the "v1.5.3 Fastboot ROM" from that site, but I didn't get far with that at all. It contains a .bat file, but i'm on mac, so tried running the commands one by one. First step was "fastboot set_active b" and that succeeded, but after that it fails with the flashing; "Flashing is not allowed for Critical Partitions". I'm afraid to continue at this point.
If possible I would still like to continue with rooting it, but if it is easier to go back to factory without root I am ok with that too at this point. Can someone please help?

Did you try this? https://forum.xda-developers.com/t/how-to-unbrick-nothing-phone-1-fastboot-bootloop.4501439/

@itsTarec oh god, i think that might just have worked! It does boot now, and i'm going through the setup process. BUT, a few things failed during the flash process:
Code:
(not in order)
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
Writing 'odm_b' FAILED (remote: 'No such file or directory')
Writing 'product_b' FAILED (remote: 'No such file or directory')
Writing 'system_b' FAILED (remote: 'No such file or directory')
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
Should i be worried?

nike1 said:
@itsTarec oh god, i think that might just have worked! It does boot now, and i'm going through the setup process. BUT, a few things failed during the flash process:
Code:
(not in order)
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
Writing 'odm_b' FAILED (remote: 'No such file or directory')
Writing 'product_b' FAILED (remote: 'No such file or directory')
Writing 'system_b' FAILED (remote: 'No such file or directory')
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
Should i be worried?
Click to expand...
Click to collapse
Sorry mate, I have no idea. Keep looking for a solution... I was thinking about rooting my NP1 either but after seeing your thread I'm reluctant

itsTarec said:
Sorry mate, I have no idea. Keep looking for a solution... I was thinking about rooting my NP1 either but after seeing your thread I'm reluctant
Click to expand...
Click to collapse
Yeah, can't recommend it unless you really know what you're doing. It seems to be alright now though, thankfully

nike1 said:
Yeah, can't recommend it unless you really know what you're doing. It seems to be alright now though, thankfully
Click to expand...
Click to collapse
Is your device rooted now? Or did you just fixed the issue?

nike1 said:
I've gotten myself into a bit of a pickle. I just got my Nothing Phone yesterday, and I've already managed to get it stuck in a boot loop. I am still able to access fastboot and my computer still recognises it, so i hope it is still salvageable.
It all started when I stumbled upon this guide, which promised that unlocking and rooting it would be done in minutes. I know next to nothing about rooting phones, but the guide made it seem fairly straightforward. So I gave it a go. Big mistake.
Here's exactly what's happened:
I followed the guide step by step.
At step 2.2 I downloaded the full 1.1.7 (EEA) package from here. Then I extracted the boot image from the downloaded zip by following this guide (still following the main guide).
Flashing it went fine, no errors, but after trying to start it, it just shows the logo for a few seconds and then restarts.
A bunch of googling later, I stumbled upon an xda thread where someone had linked to a website with pre-built images. I tried flashing some of those too, no luck.
Last thing I tried was flashing the "v1.5.3 Fastboot ROM" from that site, but I didn't get far with that at all. It contains a .bat file, but i'm on mac, so tried running the commands one by one. First step was "fastboot set_active b" and that succeeded, but after that it fails with the flashing; "Flashing is not allowed for Critical Partitions". I'm afraid to continue at this point.
If possible I would still like to continue with rooting it, but if it is easier to go back to factory without root I am ok with that too at this point. Can someone please help?
Click to expand...
Click to collapse
When you want to root it is fairly simple, but you need to patch the EXACT boot.img file that your current firmware has. For example, you cannot patch the 1.1.7 boot.img and flash it when you have installed the 1.5.3 firmware.
And for root you need to patch the boot.img with the Magisk app, not just flash it.

lucy1983 said:
When you want to root it is fairly simple, but you need to patch the EXACT boot.img file that your current firmware has. For example, you cannot patch the 1.1.7 boot.img and flash it when you have installed the 1.5.3 firmware.
And for root you need to patch the boot.img with the Magisk app, not just flash it.
Click to expand...
Click to collapse
Aha, I see. That wasn't clear to me. I thought i needed a full package and not just an incremental one, that's why I went for 1.1.7. I did patch it with Magisk though, just the wrong version i guess. But all is well now, the phone's fully working afaict. Thank you for clarifying what went wrong!