Hi, hoping to get some help here. I did some quick google searching and didn't see anything specific to the pixel.
I used Skipsoft android toolkit to unlock and root my pixel xl. Shortly after I started to have some issues and was forced to do a factory reset which I believe removed root (and I'm not sure if it screwed something up with the bootloader or not) but I've never been able to get to stock recovery. For other reasons I was shipped a replacement pixel and now I need to ship this one back. I needed to revert it back to stock before I send it back. Since it didn't have root, i used Skipsoft toolkit to relock the bootloader. I was presented with a screen on the pixel asking if I wanted to relock the bootload (i had to use vol. buttons to move between yes and no and use power to select).. I selected Yes and hit the volume button. Now my phone won't boot any longer. I can get to the bootloader.. or if I try starting the phone I get a message saying my device is corrupt. It can't be trusted and may not work properly. (if its plugged into my computer or whatever I see a battery charging icon for about 10 seconds then the screen goes blank) if the phone isn't plugged into anything after the corruption notice it just goes to a blank screen.
I'm not a complete noob as I've been around rooting my devices for years but at the same time, I am no expert. Does anyone know or can anyone offer any suggestions how I can get the device back up and running stock?
Thanks in advance for any suggestions or tips!
Will it not boot into recovery from the bootloader menu?
Edit: just realised you said you've relocked the bootloader! Might have been a big nail in the coffin.
Sent from my Pixel XL using Tapatalk
Popped, hopefully Google charges you for your fraudulent warranty claim
ko0ky said:
Hi, hoping to get some help here. I did some quick google searching and didn't see anything specific to the pixel.
I used Skipsoft android toolkit to unlock and root my pixel xl. Shortly after I started to have some issues and was forced to do a factory reset which I believe removed root (and I'm not sure if it screwed something up with the bootloader or not) but I've never been able to get to stock recovery. For other reasons I was shipped a replacement pixel and now I need to ship this one back. I needed to revert it back to stock before I send it back. Since it didn't have root, i used Skipsoft toolkit to relock the bootloader. I was presented with a screen on the pixel asking if I wanted to relock the bootload (i had to use vol. buttons to move between yes and no and use power to select).. I selected Yes and hit the volume button. Now my phone won't boot any longer. I can get to the bootloader.. or if I try starting the phone I get a message saying my device is corrupt. It can't be trusted and may not work properly. (if its plugged into my computer or whatever I see a battery charging icon for about 10 seconds then the screen goes blank) if the phone isn't plugged into anything after the corruption notice it just goes to a blank screen.
I'm not a complete noob as I've been around rooting my devices for years but at the same time, I am no expert. Does anyone know or can anyone offer any suggestions how I can get the device back up and running stock?
Thanks in advance for any suggestions or tips!
Click to expand...
Click to collapse
trying to use the toolkit to download and install google factory stock image and I'm getting the following errors..
Flashing update image..
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609150631
Serial Number........: H*
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boota' (26481 KB)...
OKAY [ 0.842s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.296s
An error occured when flashing the image
DaveHTC200 said:
Will it not boot into recovery from the bootloader menu?
Edit: just realised you said you've relocked the bootloader! Might have been a big nail in the coffin.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
i've managed to use the toolkit to unlock the bootloader again. I can get the phone to boot again to android. But I'd like to revert it back to stock. I cannot get it to boot to recovery though.
cwalker0906 said:
Popped, hopefully Google charges you for your fraudulent warranty claim
Click to expand...
Click to collapse
WTF are you talking about? I'm not the guy who was doing warranty claims. Nice try. RMA isn't WARRANTY mister clueless.
You can try "fastboot set_active _a" prior to running the script again and see if it'll actually write to slot A
Sent from my Pixel XL using Tapatalk
ko0ky said:
WTF are you talking about? I'm not the guy who was doing warranty claims. Nice try. RMA isn't WARRANTY mister clueless.
Click to expand...
Click to collapse
Sure, either way since I'm so clueless...if you read the toolkit thread you would have seen it doesn't work flashing factory images. Multiple people including myself have had this issue, so read and you will find your answers, also if RMA isn't warrant then what is it, you are exchanging a defective device for a new one... warranty lol have a good day buddy
ko0ky said:
Hi, hoping to get some help here. I did some quick google searching and didn't see anything specific to the pixel.
I used Skipsoft android toolkit to unlock and root my pixel xl. Shortly after I started to have some issues and was forced to do a factory reset which I believe removed root (and I'm not sure if it screwed something up with the bootloader or not) but I've never been able to get to stock recovery. For other reasons I was shipped a replacement pixel and now I need to ship this one back. I needed to revert it back to stock before I send it back. Since it didn't have root, i used Skipsoft toolkit to relock the bootloader. I was presented with a screen on the pixel asking if I wanted to relock the bootload (i had to use vol. buttons to move between yes and no and use power to select).. I selected Yes and hit the volume button. Now my phone won't boot any longer. I can get to the bootloader.. or if I try starting the phone I get a message saying my device is corrupt. It can't be trusted and may not work properly. (if its plugged into my computer or whatever I see a battery charging icon for about 10 seconds then the screen goes blank) if the phone isn't plugged into anything after the corruption notice it just goes to a blank screen.
I'm not a complete noob as I've been around rooting my devices for years but at the same time, I am no expert. Does anyone know or can anyone offer any suggestions how I can get the device back up and running stock?
Thanks in advance for any suggestions or tips!
Click to expand...
Click to collapse
Anyone else having this issue I was able to flash my device using directions from this page. (directly from google). https://developers.google.com/android/images You might have to accept their terms before everything gets displayed. I downloaded the image and ran flashall.bat on my windows box - rebooted the device, then got back to bootloader and ran the cmd to lock the bootloader. Everything is STOCK and good to be returned.
cwalker0906 said:
Sure, either way since I'm so clueless...if you read the toolkit thread you would have seen it doesn't work flashing factory images. Multiple people including myself have had this issue, so read and you will find your answers, also if RMA isn't warrant then what is it, you are exchanging a defective device for a new one... warranty lol have a good day buddy
Click to expand...
Click to collapse
He very clearly said that it was being returned for "other" reasons. Not the flashing fiasco.
wtherrell said:
He very clearly said that it was being returned for "other" reasons. Not the flashing fiasco.
Click to expand...
Click to collapse
You are right, I jumped the gun ,all apologies
wtherrell said:
He very clearly said that it was being returned for "other" reasons. Not the flashing fiasco.
Click to expand...
Click to collapse
thanks for being courtesy and helpful! much appreciated!
ko0ky said:
trying to use the toolkit to download and install google factory stock image and I'm getting the following errors..
Flashing update image..
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609150631
Serial Number........: H*
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boota' (26481 KB)...
OKAY [ 0.842s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.296s
An error occured when flashing the image
Click to expand...
Click to collapse
Did you solve this problem, I'm getting the same thing. Stuck in bootloop, but somehow managed to get it started, now stuck in "checking for updates"
dabadoo said:
Did you solve this problem, I'm getting the same thing. Stuck in bootloop, but somehow managed to get it started, now stuck in "checking for updates"
Click to expand...
Click to collapse
To flash use the instructions from the Google page :
https://developers.google.com/android/images
Paolo
The other thing is make sure you're using the latest Fastboot. Old fastboots do not have support for the slot system.
Let this be a huge lesson not to go running to tool kits, the one you used is nice for installing the drivers but ultimately simply using the flash-all.bat is infinitely easier to do at this point if adb/fastboot is configured.
Also don't lock the bootloader if you have modified the system at all =/
Edit: You should probably add your solution to the OP to help anyone else that maybe have done something similar.
I am having a similar issue. All I have done is u lock the bootloader through fastboot. No toolkits involved or anything. Simply plugged in, booted bootloader mode then fastboot OEM unlock and rebooted. I am unlocked but noticed I cannot boot stock recovery. It goes to the dead Android icon and simply says no command below it. No amount of pressing the volume keys or anything changes it. Holding power eventually reboots back to Android. Anyone else experiencing this or have a fix , or better yet a reason for this occurring?
powdered_donuts said:
I am having a similar issue. All I have done is u lock the bootloader through fastboot. No toolkits involved or anything. Simply plugged in, booted bootloader mode then fastboot OEM unlock and rebooted. I am unlocked but noticed I cannot boot stock recovery. It goes to the dead Android icon and simply says no command below it. No amount of pressing the volume keys or anything changes it. Holding power eventually reboots back to Android. Anyone else experiencing this or have a fix , or better yet a reason for this occurring?
Click to expand...
Click to collapse
When on the no command screen, have you pressed and held the power button, then the volume up button?
Never fails for me! Trying to press them together I didn't have any luck.
Sent from my Pixel XL using Tapatalk
DaveHTC200 said:
When on the no command screen, have you pressed and held the power button, then the volume up button?
Never fails for me! Trying to press them together I didn't have any luck.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Maybe I didn't do it in the correct manner, I'll give it a go and report back
Update: successful! Power first then volume then release.
Thanks!!
ko0ky said:
i've managed to use the toolkit to unlock the bootloader again. I can get the phone to boot again to android. But I'd like to revert it back to stock. I cannot get it to boot to recovery though.
Click to expand...
Click to collapse
How did you manage to unlock bootloader and reboot phone trough toolkit, im in the same situation here . the phone is locked on verizon. Thankyou
Related
I was trying out the Android L preview, and decided that I've had my fun and wanted to go back to the ROM I was using. I booted into recovery, and noticed that the stock recovery had been flashed. So, I downloadeed the lasted TWRP and flashed it through fastboot. When I tried to boot into recovery again, it froze at the Google screen. Since I already had everything backed up, I decided to just flash the stock image and try again. This is where the real trouble begins. The flash failed (output below), and now I can't boot into android as well as recovery. I tried a few different images (all from the official site, all marked razor), as well as the Nexus Root Toolkit, and all give me the same error(s).
So, how bad did I mess up?
Code:
C:\Android\razor-ktu84p>fastboot flash bootloader bootloader-flo-flo-04.02.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.135s]
writing 'bootloader'...
FAILED (remote: Signature mismatched!!!)
finished. total time: 1.024s
C:\Android\razor-ktu84p>fastboot -w update image-razor-ktu84p.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
Creating filesystem with parameters:
Size: 13052653568
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3186683
Block groups: 98
Reserved block group size: 783
Created filesystem with 11/798112 inodes and 90699/3186683 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 09f8f0db
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
OKAY [ 0.006s]
sending 'boot' (7050 KB)...
OKAY [ 0.234s]
writing 'boot'...
OKAY [ 0.308s]
sending 'recovery' (7598 KB)...
OKAY [ 0.256s]
writing 'recovery'...
OKAY [ 0.340s]
erasing 'system'...
OKAY [ 0.126s]
sending 'system' (736772 KB)...
OKAY [ 23.632s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 25.676s
That error is usually due to an incompatible fastboot, first try doing a: fastboot erase system
...then try to flash system.img manually again.
Make sure you have the newest fastboot, one that is new as Android L bootloader.
NOTE: DO NOT erase bootloader! This will hardbrick you.
BTW, this is one of the reasons why I use multirom!
mdamaged said:
That error is usually due to an incompatible fastboot, first try doing a: fastboot erase system
...then try to flash system.img manually again.
Make sure you have the newest fastboot, one that is new as Android L bootloader.
NOTE: DO NOT erase bootloader! This will hardbrick you.
BTW, this is one of the reasons why I use multirom!
Click to expand...
Click to collapse
The only img file I have is the bootloader. Is what what you mean?
Also, that seems like a tool I should really have.
StormConjurer said:
The only img file I have is the bootloader. Is what what you mean?
Also, that seems like a tool I should really have.
Click to expand...
Click to collapse
I assume you have the factory image for your old rom, in that package there is a zip file, if you extract it, you will find, among others, a img file named system.img. This is one of the files that is failing to flash.
The bootloader image is failing to flash because it is older than the one that is on there now (the Android L one), so fastboot does not recognize that new Android L bootloader because it expects one of the pre-L bootloaders, so you may have to grab the developers SDK and use that fastboot so it will recognize the newer bootloader.
mdamaged said:
I assume you have the factory image for your old rom, in that package there is a zip file, if you extract it, you will find, among others, a img file named system.img. This is one of the files that is failing to flash.
The bootloader image is failing to flash because it is older than the one that is on there now (the Android L one), so fastboot does not recognize that new Android L bootloader because it expects one of the pre-L bootloaders, so you may have to grab the developers SDK and use that fastboot so it will recognize the newer bootloader.
Click to expand...
Click to collapse
I installed the SDK platform for Android L through the SDK manager, but I'm still getting the exact same error.
I suppose it's also worth mentioning that even if I try to flash the L preview, I still get the same error.
StormConjurer said:
I installed the SDK platform for Android L through the SDK manager, but I'm still getting the exact same error.
I suppose it's also worth mentioning that even if I try to flash the L preview, I still get the same error.
Click to expand...
Click to collapse
Well, have you tried this? http://forum.xda-developers.com/showthread.php?t=2381582
Read the whole OP, you can and should obviously skip the relocking of the bootloader.
Try the Recovery_Nexus7.bat first, if that fails then goto the Dead_Nexus7.bat.
It probably will get you nowhere, but it's worth a shot, obviously if it works, it will wipe everything and put it back to factory.
I solved this simply... By using Nexus Root Toolkit and using Flash Stock and Unroot. Went back to 4.4.4, but you can flash back to any version this way. It will download the ROM you want and flash it with you I having to do basically nothing.
If you are in a boot loop, there's an option for that right under the flash stock and unroot option.
Sorry for the absence. Had a busy few days.
mdamaged said:
Well, have you tried this? http://forum.xda-developers.com/showthread.php?t=2381582
Read the whole OP, you can and should obviously skip the relocking of the bootloader.
Try the Recovery_Nexus7.bat first, if that fails then goto the Dead_Nexus7.bat.
It probably will get you nowhere, but it's worth a shot, obviously if it works, it will wipe everything and put it back to factory.
Click to expand...
Click to collapse
Nope, same results as before.
mhannigan said:
I solved this simply... By using Nexus Root Toolkit and using Flash Stock and Unroot. Went back to 4.4.4, but you can flash back to any version this way. It will download the ROM you want and flash it with you I having to do basically nothing.
If you are in a boot loop, there's an option for that right under the flash stock and unroot option.
Click to expand...
Click to collapse
Like I said in the first post, Nexus Root Toolkit is one of the methods I tried. There's an option to force flash, but I've been trying to avoid that, since it warns of hard bricking the device. I'm quickly running out of options though.
Update: Tried again with force mode turned on. No change in the results.
Hey guys, I'd love anyone's opinion on this as this is the first time something like this has happened to be.
Was using the tablet and noticed that the WiFi wouldn't turn back on. Decided to restart. No more start up and stuck on Google logo indefinitely.
Can get into Bootloader
Computer recognizes the Nexus 7 but thats about it
Cannot get into recovery, frozen screen
Fastboot is unrecognizable
Cannot ADB anything
Tried to use Toolkit to flash OTA Google update to no avail
Code:
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.652s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
sending 'radio' (76038 KB)...
OKAY [ 2.465s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 92.586s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
Creating filesystem with parameters:
Size: 28521246720
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6963195
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1741488 inodes and 153337/6963195 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: DEB-Z00_2.42.0_1204
Serial Number........: 07927f06
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
FAILED
Device version-bootloader is 'FLO-03.14'.
Update requires 'FLO-04.02'.
finished. total time: 0.078s
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.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
Is there anything that can be done or am I SOL?
The tablet is still under warranty but it was running custom ROM with an unlocked bootloader, so I'm totally screwed?
Hi mate. exactly the same happened to me few days ago, in fact I came here to open the same topic.
I tried flashing stock image using Nexus toolkit, see the progress but wouldn't load further the google logo. Tried loading the custom recovery, but when I do so from the tool fastboot on my Nexus freezes.
Tried flashing clockwork recovery and TWRP manually but it stays on stock bootloader screen and if I reboot it goes back to the stock bootloader screen (the one with laying android)
I was rooted with stock 4.4.3
@tecz0r, based on the screenshot and the log you posted, have you tried relocking and unlocking the bootloader? See if it helps.
Maverick-DBZ- said:
@tecz0r, based on the screenshot and the log you posted, have you tried relocking and unlocking the bootloader? See if it helps.
Click to expand...
Click to collapse
Just tried that, was able to lock back. Then tried selecting the recovery mode but that just restarted and then jut stayed with the google logo. Was then able to unlock again with a prompt on the device whether or not I would like to unlock but that did not help.
---------- Post added at 03:04 PM ---------- Previous post was at 02:09 PM ----------
Ok, so I was able to boot with TWPR but for some reason touch screen wouldn't work. When trying to boot with Philz or Clockwork bootloader just freezes
When you use the below command
Code:
fastboot devices
Does your device serial number show up? I'm pretty sure it does, since you're able to re-lock and unlock bootloader. I'm guessing you're using wugfresh toolkit on 64 bit windows.
Try to downgrade to JB 4.3, if this works, you can update to 4.4.3 via OTA.
https://developers.google.com/android/nexus/images#razorg
Download the JB 4.3 image above and extract all files to
C:\Program Files (x86)\WugFresh Development\data
Run the below commends manually in a dos prompt.
Code:
cd C:\Program Files (x86)\WugFresh Development\data
fastboot flash bootloader bootloader-deb-flo-03.14.img
fastboot reboot-bootloader
fastboot flash radio radio-deb-deb-g00_1.23.0_0720.img
fastboot reboot-bootloader
fastboot update image-razorg-JLS36C.zip
Then boot to recovery and factory reset.
Reboot tablet and hope for the best.
Maverick-DBZ- said:
When you use the below command
Code:
fastboot devices
Does your device serial number show up? I'm pretty sure it does, since you're able to re-lock and unlock bootloader. I'm guessing you're using wugfresh toolkit on 64 bit windows.
Try to downgrade to JB 4.3, if this works, you can update to 4.4.3 via OTA.
https://developers.google.com/android/nexus/images#razorg
Download the JB 4.3 image above and extract all files to
C:\Program Files (x86)\WugFresh Development\data
Run the below commends manually in a dos prompt.
Code:
cd C:\Program Files (x86)\WugFresh Development\data
fastboot flash bootloader bootloader-deb-flo-03.14.img
fastboot reboot-bootloader
fastboot flash radio radio-deb-deb-g00_1.23.0_0720.img
fastboot reboot-bootloader
fastboot update image-razorg-JLS36C.zip
Then boot to recovery and factory reset.
Reboot tablet and hope for the best.
Click to expand...
Click to collapse
Thanks for the tip. Happy to say that I was able to RELOCK the bootloader so atleast I have a better chance at Asus honoring the warranty.
Weird thing: couldn't get the bootloader UNLOCKED. It just hangs for about 15 minutes and then says FAILED.
At this point, I simply cannot get the bootloader to write anything or replace current bootloader. Never heard of this issue. No idea how it can be resolved without RMA.
Yeah, looks like it's gone. Good luck with the RMA.
Hey gang!
So I got it to work! yay. tried everything mentioned here, but no luck. Last thing I've tried was manually flashing 4.3. Nothing
Today a guy from the office took it apart and disconnected the battery. Connected it back and booya it's loading.
Surprisingly it loaded 4.3 so flashing was successful but something was preventing it from loading.
Nice to be back, I was kind of getting tired of using my phone for browsing internets from my couch
Interesting, reminds me of a similar problem with the nexus 4 called the red light of death.
Glad it's working fine again.
I flashed system.img and boot.img of Android 6 Factory Image manually and worked so far.After that i want a clean install,so i erased system,userdata and boot Partition and flashed the Factory Image with the included skript.But Android wasn't booting(i waited over 30-35 min.).So did the same again with no success.So i flashed TWRP and flashed CyanogenMod (that worked for me, but TRWP shows Mount Erros with data,cache etc.).But CyanogenMod also stucks in Bootanimation.
Have you tried re-downloading the files? It could be a bad download maybe.
theminikiller said:
Have you tried re-downloading the files? It could be a bad download maybe.
Click to expand...
Click to collapse
Yes.I also tried it with a Lollipop Factory Image.
david.mueller1013 said:
Yes.I also tried it with a Lollipop Factory Image.
Click to expand...
Click to collapse
+1
I have the same problem
Dirty flashed the android 6 flash-all.bat and now I am soft-bricked
Fastboot is activate but fails all actions
If you get an answer please let me know
david.mueller1013 said:
Yes.I also tried it with a Lollipop Factory Image.
Click to expand...
Click to collapse
Goodness your signature is long, who needs that level of detail on all the devices you own, really.
For your problem, boot in bootloader, run the flash-all batch file, when you seed the android boot animation hold power for 10 seconds, boot in recovery mode and do a factory reset to default.
Your recovery problem might be because you need the multi-ROM version of TWRP, I have to use that because if not, TWRP sees no partitions. For my nexus, every time I run the flash-all batch file, I have to do a factory reset to default.
Nic2112 said:
Goodness your signature is long, who needs that level of detail on all the devices you own, really.
Click to expand...
Click to collapse
Now short enough?
Nic2112 said:
For your problem, boot in bootloader, run the flash-all batch file, when you seed the android boot animation hold power for 10 seconds, boot in recovery mode and do a factory reset to default.
Click to expand...
Click to collapse
I tried it, but when i go into Stock Recovery, it shows the lying Android figure with exclamation mark.
Nic2112 said:
Your recovery problem might be because you need the multi-ROM version of TWRP, I have to use that because if not, TWRP sees no partitions. For my nexus, every time I run the flash-all batch file, I have to do a factory reset to default.
Click to expand...
Click to collapse
Unfortunately the MultiROM version is not working,too.The normal version worked well for before(My device wasn't shipped with 5.0.1 or is from best buy or something like that).
david.mueller1013 said:
I tried it, but when i go into Stock Recovery, it shows the lying Android figure with exclamation mark.
Click to expand...
Click to collapse
That's normal, from there press power and Vol Up shortly after, you'll see a menu appear. Just wipe to factory default and reboot.
The first boot takes 3-5 minutes so let that go and you should be back in business.
Nic2112 said:
That's normal, from there press power and Vol Up shortly after, you'll see a menu appear. Just wipe to factory default and reboot.
The first boot takes 3-5 minutes so let that go and you should be back in business.
Click to expand...
Click to collapse
Thank you so much!It worked and booted succesfully , but i don't unterstand the error exacly.
But the main point is, it works again.I had some worse fears like corrupted memory.
How bout editing the thread title adding [solved]...
Nic2112 said:
Goodness your signature is long, who needs that level of detail on all the devices you own, really.
For your problem, boot in bootloader, run the flash-all batch file, when you seed the android boot animation hold power for 10 seconds, boot in recovery mode and do a factory reset to default.
Your recovery problem might be because you need the multi-ROM version of TWRP, I have to use that because if not, TWRP sees no partitions. For my nexus, every time I run the flash-all batch file, I have to do a factory reset to default.
Click to expand...
Click to collapse
Hi
I'm having a similar problem but the flash-all script cant write to my N7 it seems - as below
sending 'bootloader' (3911 KB)...
OKAY [ 0.156s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.602s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.024s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Power + Volume Up just bring me to looping Google screen and I only have access to fastboot screen
I hope you can help me too ?
Thanks
david.mueller1013 said:
Thank you so much!It worked and booted succesfully , but i don't unterstand the error exacly.
But the main point is, it works again.I had some worse fears like corrupted memory.
Click to expand...
Click to collapse
There is no error, some people can dirty flash the image and some can't. I know that when I flash the image, unless I do a factory reset the tablet never boots back. Maybe something that's left behind prevents the boot from completing.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
caolfin said:
Hi
I'm having a similar problem but the flash-all script cant write to my N7 it seems - as below
sending 'bootloader' (3911 KB)...
OKAY [ 0.156s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.602s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.024s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Power + Volume Up just bring me to looping Google screen and I only have access to fastboot screen
I hope you can help me too ?
Thanks
Click to expand...
Click to collapse
Is your tablet already in boot-loader mode when you start? If it is then maybe the bootloader has to be unlocked? I can't say for sure, I don't have a lot of experience messing with the tablet yet. I tried custom ROMS but I'm trying to stick to stock now.
Hi
Yes, the N7 is stuck in bootloader
I have tried many times to lock and unlock the bootloader and currently the last few lines of the bootloader screen are
SIGNING = yes
SECURE BOOT = enabled
LOCK STATE = unlocked
I am assuming that LOCK STATE means bootloader lock state and therefore this should be ok ?!
This is really stumping me now
Nic2112 said:
There is no error, some people can dirty flash the image and some can't. I know that when I flash the image, unless I do a factory reset the tablet never boots back. Maybe something that's left behind prevents the boot from completing.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
Is your tablet already in boot-loader mode when you start? If it is then maybe the bootloader has to be unlocked? I can't say for sure, I don't have a lot of experience messing with the tablet yet. I tried custom ROMS but I'm trying to stick to stock now.
Click to expand...
Click to collapse
Hi, I tried to reset the bootloader and now I cant get it to unlock ggggrrrrr
Comes up with the questions Unlock Bootloader ? and I say yes
I get
C:\adb\razor-lmy47v>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 5.003s
I'm totally stumped now
can someone with LTE (razorg) please do the OTA using the bootloader method (wiping data and system first) and put TWRP back and then make a TWRP backup without booting into the fresh android install so that people who dont have working USB can possibly get the update. it would be much appreciated and theoretically should work.
My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff
nobody?? :'(
Sashtheflash said:
My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff
Click to expand...
Click to collapse
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.
computerslayer said:
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.
Click to expand...
Click to collapse
since my phone cant find an internal memory i cant flash anything... i think partition tables are ****ed up or so. fastboot flash recovery ends in old state locking bootloader via fastboot results in bootloader still open.
Never had a problem like that and im here since the g1
Yikes. I'm afraid I don't have any further advice. Are there any threads around the M9 forums that talk about corrupted partitions?
Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.
Sneakyghost said:
Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.
Click to expand...
Click to collapse
unfortunately my device wont let me boot in recovery again... now it states: Failed to boot to recovery mode Press Volume up to back to menu.
seems my tries to flash single parts of firmware messed this up
Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).
Sneakyghost said:
Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).
Click to expand...
Click to collapse
Im from Germany, too ( Heilbronn) Ok i leave my fingers from it until tomorrow. Thank you a lot for trying !!!
im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?
logy122 said:
im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?
Click to expand...
Click to collapse
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.
Sneakyghost said:
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.
Click to expand...
Click to collapse
im also can open phone and replace emmc |> im only need boot file to write to phone and back to work
Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Gesendet von meinem HTC 10 mit Tapatalk
I don't want to start a new thread. I have a similar problem. I have an HTC one M9 S-OFF Unlocked. I returned my phone to stock after doing a nandrod backup. I realised I had a sms backup in the nandroid that I need so I thought I would install twrp and do a restore the nandroid. I installed twrp and afterward it bootlooped when I went to recovery mode. It goes from white HTC screen to black screen an back. I tried to go to download mode to do a fresh install but it bootloops there as well. It also bootloops if I try to turn it off with it connected to power. I have tried installing different version of twrp but I get the same problem. If I install a stock recovery it says failed to boot to recovery mode and stays on the white HTC screen. Does anyone know of a solution
Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...
bzhmobile said:
Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...
Click to expand...
Click to collapse
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"
Sneakyghost said:
Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Click to expand...
Click to collapse
It was also possible w/Linux on the One XL. I too have never heard of it working on the M7 and later phones, though I've seen the odd post here claiming it is possible. No examples of anyone having done it, however.
copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
djkfree said:
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"
Click to expand...
Click to collapse
bzhmobile said:
copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
Click to expand...
Click to collapse
I get bootloop when I fastboot oem rebootRUU
So,
go to download mod (option in the bootloader ) and apply the fastboot command
htc_fastboot flash zip OPJAIMG.zip
I was using my 5x today, and it froze, then suddenly shut off. After holding the power button for a period of time, I can get the initial "Google" boot logo to appear for a few seconds, but then the screen just goes black again. I can get it to boot into bootloader mode, and from there into stock recovery, but never to the colorful dots to showing that the OS is booting up... every time I try the screen just goes black after a few seconds of the Google logo.
I've seen the bootloop issue before (on a different 5x), and this seems to be a different issue. Before I do anything drastic, do any of you have any suggestions or experience with this type of behavior?
wrkerr said:
I was using my 5x today, and it froze, then suddenly shut off. After holding the power button for a period of time, I can get the initial "Google" boot logo to appear for a few seconds, but then the screen just goes black again. I can get it to boot into bootloader mode, and from there into stock recovery, but never to the colorful dots to showing that the OS is booting up... every time I try the screen just goes black after a few seconds of the Google logo.
I've seen the bootloop issue before (on a different 5x), and this seems to be a different issue. Before I do anything drastic, do any of you have any suggestions or experience with this type of behavior?
Click to expand...
Click to collapse
I just got the same issue with yours 2 hours ago. Did you managed to try if a factory reset could help the phone?
Billys20 said:
I just got the same issue with yours 2 hours ago. Did you managed to try if a factory reset could help the phone?
Click to expand...
Click to collapse
Not yet. There's some data on the phone I need to try to get off before I do that.
Also, after leaving the phone alone for a while, when I came back to it, it did start boot looping, so I guess that is the issue. I tried flashing the modified TWRP image, but I still can't even get it to boot into recovery without looping.
wrkerr said:
Not yet. There's some data on the phone I need to try to get off before I do that.
Also, after leaving the phone alone for a while, when I came back to it, it did start boot looping, so I guess that is the issue. I tried flashing the modified TWRP image, but I still can't even get it to boot into recovery without looping.
Click to expand...
Click to collapse
Same thing here. When I left it for a while I was able to boot to bootloader but when I choose the recovery mode it boots again with the google logo and then turns off. No hope here I guess.
Mine does not care, it does not carry, not the sign of life.:crying:
I might have a similar issue. I posted this in the Lineage OS thread earlier today: "Uhm ... so this just happened: I flashed the latest LOS 15.1 (Apr 30) and Francokernel v56, then tried to reboot into LOS as usual. The phone froze at the LOS boot animation, so I long pressed the power button to shut it down. It eventually did shut down. I then pressed power and volume down to start up the bootloader. The bootloader eventually came up. I then told the bootloader to start into recovery, but I never got there. The screen just stayed black. Now the phone won't respond to whatever I do to it. Holding power and volume down for a long time doesn't do anything; holding power alone for a long time doesn't do anything. Nothing happens whatever I do to the phone. Any suggestions?"
I have discovered by now that the trick with mine is to simply press and hold the power button, rather than power and volume down. That way I am able to get into the phone's bootloader, but that's about it. If I try to boot into recovery — no chance, I only get as far as the Google logo. Has someone tried yet whether flashing the 4 kernel boot.img from this thread — https://forum.xda-developers.com/nexus-5x/general/blod-8-1-0-opm2-171019-029-apr-2018-fix-t3784307 — does anything?
um.z said:
I might have a similar issue. I posted this in the Lineage OS thread earlier today: "Uhm ... so this just happened: I flashed the latest LOS 15.1 (Apr 30) and Francokernel v56, then tried to reboot into LOS as usual. The phone froze at the LOS boot animation, so I long pressed the power button to shut it down. It eventually did shut down. I then pressed power and volume down to start up the bootloader. The bootloader eventually came up. I then told the bootloader to start into recovery, but I never got there. The screen just stayed black. Now the phone won't respond to whatever I do to it. Holding power and volume down for a long time doesn't do anything; holding power alone for a long time doesn't do anything. Nothing happens whatever I do to the phone. Any suggestions?"
I have discovered by now that the trick with mine is to simply press and hold the power button, rather than power and volume down. That way I am able to get into the phone's bootloader, but that's about it. If I try to boot into recovery — no chance, I only get as far as the Google logo. Has someone tried yet whether flashing the 4 kernel boot.img from this thread — https://forum.xda-developers.com/nexus-5x/general/blod-8-1-0-opm2-171019-029-apr-2018-fix-t3784307 — does anything?
Click to expand...
Click to collapse
Here you tried just flashing the stock factory image? Flashing lineage may have messed something up. I bet if you do that everything will be fine.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Here you tried just flashing the stock factory image? Flashing lineage may have messed something up. I bet if you do that everything will be fine.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Tried, but flash-all failed due to the phone switching itself off in the middle of the process. Here's the relevant content from my terminal window.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (4620 KB)...
OKAY [ 0.189s]
writing 'bootloader'...
OKAY [ 0.197s]
finished. total time: 0.387s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'radio' (56630 KB)...
OKAY [ 1.463s]
writing 'radio'...
OKAY [ 0.534s]
finished. total time: 1.997s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (11 MB) to disk... took 0.033s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (17 MB) to disk... took 0.044s
archive does not contain 'recovery.sig'
extracting system.img (1909 MB) to disk... took 10.193s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (185 MB) to disk... took 1.107s
ERROR: usb_write failed with status e00002c0
archive does not contain 'vendor.sig'
ERROR: usb_write failed with status e00002c0
ERROR: usb_write failed with status e00002c0
ERROR: usb_write failed with status e00002c0
ERROR: usb_write failed with status e00002c0
wiping userdata...
ERROR: usb_write failed with status e00002c0
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (Invalid argument))
ERROR: usb_write failed with status e00002c0
--------------------------------------------
ERROR: usb_write failed with status e00002c0
getvar:version-bootloader FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
Where are you getting the factory image? There's stuff that's printed out I've never seen before. Try flashing each partition separately with fastboot.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Where are you getting the factory image? There's stuff that's printed out I've never seen before. Try flashing each partition separately with fastboot.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
From here: https://dl.google.com/dl/android/aosp/bullhead-opm2.171019.029-factory-c7ba966b.zip
I did flash each partition separately in the end, but to no avail. Phone doesn't boot.
Hello same issue here with LineageOS 15.1 (+xposed and ElementalX)
It won't boot anymore after three loop to Google Logo and black screen, I was suspecting hardware issue and now, I see I'm not alone.
I'll try to boot to the bootloader this evening and flash factory images. I hope it'll work.
OMG! What's going on? I'm in Scotland right now with our US Nexus 5X's. Afternoon of the 2nd of May, I was using Hangouts when it just went black. Battery had over 40%. I couldn't even get it to turn on for a while. Then, it started with the unlocked bootloader warning screen then the Google screen-looping those for a while. Occasionally, the colored balls would begin but not finish. Sometimes, it wouldn't do anything--nothing but a black screen. I could get to TWRP via bootloader but any action was impossible as it either locked up or just went black. I left it plugged in overnight and eventually, the OS started (stock April update) again. The phone & OS remained on overnight. This morning, I tried to put the main Fi sim back into it but it locked up (froze) again then started the two-screen loop. I honestly didn't think I'd find people with the same issue--esp just happening. I can't get back to my PC until near the end of May so I can't try very much. I probably have the last OS on my 5X storage since I use Flashfire to update, but I really didn't want to try flashing anything since the black screen issue seems inevitable. I hope someone out there gets to the root of this. So far, hubby's 5X is working. Of course, all of ours were working until they weren't! His is locked and stock. We're both on April update.
Has anyone gotten anywhere with correcting this issue?
FWIW, I just contacted LG support today since I'd read that the warranty had been extended to 30 months. I won't know the final results for a few weeks, but I set up a repair and eventually received a shipping label to Fort Worth, TX. As far as I can tell, these behaviors ARE the BLOD. We also have a 27 mos old 5X that is hardly ever used. It currently has no issue; but then, mine didn't either until is just went black and wouldn't restart.
EDIT: In case anyone is still searching solutions for this issue, my phone is on its way back from LG with a new motherboard. All (including shipping both ways) was covered under the new, 30 mos extended warranty.