[Q] Any way to access bricked Nexus 10 filesystem in recovery mode? - Nexus 10 Q&A, Help & Troubleshooting

So a google android OS update bricked our Nexus 10 a couple months ago. Now we get a nice dead android on the screen. We can enter recovery mode by holding power + volume up to get into adb sideload, etc.
But the problem is... the system.img has a bad file in it so when we try and sideload to 5.1 from 5.0.2 it refuses due to verification failure.
So how to get this on there?
I've got the system.img manually downloaded but have no idea how to make it into a valid .zip file that adb sideload can upload and the tablet not reject.
Of course... I know how to make a .zip file. That's easy. But it fails verification. That I don't understand.
I know little about android or these devices and I'm using Windows. I know unix but... don't have access to it right now. So I'm stuck in Windows 7.
Oh, and the device is LOCKED. It must stay locked. I can't unlock it--because we'll lose data. I don't want to lose data. That would be bad. It was her device and she's computer illiterate so I have no idea if any of the settings etc. were backed up online.
So how do I access the filesystem to either put a new system.img on by itself or just replace the individual file without using fastboot since the device has to remain locked.
... or unlock it without data loss.
Yes, this sounds complicated. I'm probably screwed. But... maybe there is a way?

Mr_Blastman said:
So a google android OS update bricked our Nexus 10 a couple months ago. Now we get a nice dead android on the screen. We can enter recovery mode by holding power + volume up to get into adb sideload, etc.
But the problem is... the system.img has a bad file in it so when we try and sideload to 5.1 from 5.0.2 it refuses due to verification failure.
So how to get this on there?
I've got the system.img manually downloaded but have no idea how to make it into a valid .zip file that adb sideload can upload and the tablet not reject.
Of course... I know how to make a .zip file. That's easy. But it fails verification. That I don't understand.
I know little about android or these devices and I'm using Windows. I know unix but... don't have access to it right now. So I'm stuck in Windows 7.
Oh, and the device is LOCKED. It must stay locked. I can't unlock it--because we'll lose data. I don't want to lose data. That would be bad. It was her device and she's computer illiterate so I have no idea if any of the settings etc. were backed up online.
So how do I access the filesystem to either put a new system.img on by itself or just replace the individual file without using fastboot since the device has to remain locked.
... or unlock it without data loss.
Yes, this sounds complicated. I'm probably screwed. But... maybe there is a way?
Click to expand...
Click to collapse
That's odd that an OTA just bricked your N10 out of the blue. Don't think I've ever heard of that happening before. Did you just accept the OTA on the device? Or were you trying to update via adb sideload? What version were you on and what version were you upgrading to?
Sorry to hear that, but it does indeed seem like you may be SOL. The only thing I can think of is trying to adb pull the data off the sd card, and then unlocking it to fastboot flash the factory image files (you can always lock it again after flashing). However, I'm not even sure adb pull works with the stock recovery. Also, I believe for adb sideload to work, the file has to be on the root of the sd card on the device. I don't think I've heard of anyone trying to flash a full image file using adb sideload. I've only seen it used to apply OTAs manually or flashing a zip like SuperSU. Not sure how it would work sideloading a full image file.

Mr_Blastman said:
So a google android OS update bricked our Nexus 10 a couple months ago. Now we get a nice dead android on the screen. We can enter recovery mode by holding power + volume up to get into adb sideload, etc.
But the problem is... the system.img has a bad file in it so when we try and sideload to 5.1 from 5.0.2 it refuses due to verification failure.
So how to get this on there?
I've got the system.img manually downloaded but have no idea how to make it into a valid .zip file that adb sideload can upload and the tablet not reject.
Of course... I know how to make a .zip file. That's easy. But it fails verification. That I don't understand.
I know little about android or these devices and I'm using Windows. I know unix but... don't have access to it right now. So I'm stuck in Windows 7.
Oh, and the device is LOCKED. It must stay locked. I can't unlock it--because we'll lose data. I don't want to lose data. That would be bad. It was her device and she's computer illiterate so I have no idea if any of the settings etc. were backed up online.
So how do I access the filesystem to either put a new system.img on by itself or just replace the individual file without using fastboot since the device has to remain locked.
... or unlock it without data loss.
Yes, this sounds complicated. I'm probably screwed. But... maybe there is a way?
Click to expand...
Click to collapse
Issue not fixed ? A proper factory reset( this doesn't remove the data on your internal storage.) followed by any afb sideload should fix your issue ...
Envoyé de mon Nexus 10 en utilisant Tapatalk

Mr_Blastman said:
So a google android OS update bricked our Nexus 10 a couple months ago. Now we get a nice dead android on the screen. We can enter recovery mode by holding power + volume up to get into adb sideload, etc.
But the problem is... the system.img has a bad file in it so when we try and sideload to 5.1 from 5.0.2 it refuses due to verification failure.
So how to get this on there?
I've got the system.img manually downloaded but have no idea how to make it into a valid .zip file that adb sideload can upload and the tablet not reject.
Of course... I know how to make a .zip file. That's easy. But it fails verification. That I don't understand.
I know little about android or these devices and I'm using Windows. I know unix but... don't have access to it right now. So I'm stuck in Windows 7.
Oh, and the device is LOCKED. It must stay locked. I can't unlock it--because we'll lose data. I don't want to lose data. That would be bad. It was her device and she's computer illiterate so I have no idea if any of the settings etc. were backed up online.
So how do I access the filesystem to either put a new system.img on by itself or just replace the individual file without using fastboot since the device has to remain locked.
... or unlock it without data loss.
Yes, this sounds complicated. I'm probably screwed. But... maybe there is a way?
Click to expand...
Click to collapse
First off, your device ISN'T bricked, so stop calling it a brick.
Second, "I've got the system.img manually downloaded but have no idea how to make it into a valid .zip file that adb sideload can upload and the tablet not reject." - You can't, stock recovery will only flash SIGNED (with a valid key, like the one Google has) zips.
Third, "So how do I access the filesystem to either put a new system.img" - Flash new system.img ? needs bootloader unlocked.
Fourth, "or just replace the individual file without using fastboot since the device has to remain locked." - Do you know what file is it? Digressing, you could not modify /system unless it was mounted RW, which isn't possible if the device has NOT been rooted, ever.
So either the device has root ATM or has had root sometime before, for a file under /system/ to be modified.
If the device is still rooted, and you can still boot to Android, you can unlock the bootloader without wiping data, using https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en
If it's not rooted ATM, I believe (don't take my word for it, never used anything else other than fastboot+twrp+supersu flashable zip to root), I believe you can use http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461 to root, unlock bootloader with BootUnlocker, reflash system.img of 5.0.2, relock bootloader. Reboot to recovery, sideload OTA.
Honestly, I think it would be much much easier if you'd just backup all things to cloud yourself, pull /sdcard/ contents to your PC, unlock bootloader, flash LMY48B factory img, relock bootloader.

Related

[Q] Slate 7 Extreme root,flash question

Hi, I am a happy owner of the HP Slate 7 Extreme which is basically the same device as you guys are using.I am still on the 4.2 Jelly bean since HP are not pushing over the air updates with our devices.I want to use the script from the development forum "[Script] [Utility] Nvidia Tegra Note 7 Kitkat Unlock BL, Restore, Recovery, & Root", I want to know if anyone has tried to use it with the Slate Extreme or if it simply should work on the Jelly Bean aswell. Thanks guys.
still have freeze/hang issue..
http://forum.xda-developers.com/showthread.php?t=2663449&page=2
mofared said:
still have freeze/hang issue..
http://forum.xda-developers.com/showthread.php?t=2663449&page=2
Click to expand...
Click to collapse
What about the 4.3+ ?
crazyhacker202 said:
What about the 4.3+ ?
Click to expand...
Click to collapse
i have not test that yet but i believe it should work because i have tested the 4.4.2 and 4.2.2 evga ROM from here using the cwm install from sdcard method..
http://forum.xda-developers.com/showthread.php?t=2627671
The only thing that puzzles me now is i am unable to perform a system recovery from HP update.zip using cwm.
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
So right now i am stuck with 4.2.2 evga ROM all is good and functional.
I have read some post that by updating OTA fix issue in 4.4 but i have no idea on how to get the OTA update.
p/s: This is my first tablet and root attempt...
edit:
i found out that rootjunky has already released the 4.4.2 with 2.3 OTA i will give it a try and feedback later
mofared said:
i have not test that yet but i believe it should work because i have tested the 4.4.2 and 4.2.2 evga ROM from here using the cwm install from sdcard method..
http://forum.xda-developers.com/showthread.php?t=2627671
The only thing that puzzles me now is i am unable to perform a system recovery from HP update.zip using cwm.
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
So right now i am stuck with 4.2.2 evga ROM all is good and functional.
I have read some post that by updating OTA fix issue in 4.4 but i have no idea on how to get the OTA update.
p/s: This is my first tablet and root attempt...
edit:
i found out that rootjunky has already released the 4.4.2 with 2.3 OTA i will give it a try and feedback later
Click to expand...
Click to collapse
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
There was an individual who has received the 4.4.2 update from HP on his Slate Extreme over at the HP forums. I believe he stated he received 20 units donated directly from HP and was wondering why only 1 of them received the update. I believe the reason stated is that he most likely received a non-retail unit by accident. Not sure if he ever dumped the ROM or even knows how. I don't know either otherwise I'd try to contact him to get him to do so.
Re-write recovery partition?
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
I did flash the modified update.zip but CWM doesn't give me the option to re-write the recovery partition. I go straight to "Install from sdcard complete". How is that re-write done?
*Update* All done - Had to select NO to questions on reboot (Replace recovery and root). Thanks so much - back to stock 4.2.2
Belmichel said:
I did flash the modified update.zip but CWM doesn't give me the option to re-write the recovery partition. I go straight to "Install from sdcard complete". How is that re-write done?
*Update* All done - Had to select NO to questions on reboot (Replace recovery and root). Thanks so much - back to stock 4.2.2
Click to expand...
Click to collapse
See my HP Slate 7 Extreme Root post: http://forum.xda-developers.com/showthread.php?t=2850893
What am I supposed to open updater-script with?
---------- Post added at 03:47 AM ---------- Previous post was at 03:31 AM ----------
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
---------- Post added at 04:25 AM ---------- Previous post was at 03:47 AM ----------
I downloaded a script editor and deleted the first three lines of updater script but it still fails to flash.
Finally success!
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
I have the 4450 extreme and one the things that was a little different- is that I had put the update zip on the sd card prior and it did the update on its own... WEIRD but acceptable! rooted and on 4.4.2- thanks man!
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot (previously this): This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk (Previously this): The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip (previously this): A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt (previously this): A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
It Worked! But...
mike-s said:
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot: This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk: The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip: A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt: A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
Click to expand...
Click to collapse
I was able to unlock my bootloader using the above method and it worked. My s7e rebooted and everything was working normally. I loaded the bootloader again to go in and do a cache wipe and my 3 year old bumped into me as I was holding down the volume+ and power buttons. Now I'm stuck in ADX mode (black screen but recognized by my pc, have tried connecting to charger, volume+ and power, volume - and power, nothing works) . I've read that Advent has released adx files for the Vega Note 7 and you can use Tegra Note 7 Super Tools to restore the Nvidia Note 7. I'm wondering if I can use the update.zip file and the nvflash files from Nvidia to restore my tablet from ADX mode.
Any suggestions?
Mike-S, Thanks for the in depth how-to. I tried to sell my Extreme 4450 and the guy that I sold it to said when he received it was in boot loop. I got it back and it is indeed the one I sent him, however, now I have a bricked tab that doesn't even allow fastboot. I have, like others tried calling HP, tried installing per you instruction and finally considered just throwing away or selling. I almost seems like the recovery was wiped... I can get to uploading from SD and have tried using your info to accomplish with no success. Any suggestions? I hate to smash it or try and sell if I can fix it.
Thank you in advance for anyone's help
som1special2 said:
however, now I have a bricked tab that doesn't even allow fastboot. I have, like others tried calling HP, tried installing per you instruction and finally considered just throwing away or selling.
Click to expand...
Click to collapse
Damn, I'm sorry to say that I'm unsure if i'll be able to help much or at all. All i can suggest is look and see if there is any pre-boot subsystem that connects to your pc via usb, similar to the mediatek "preboot mt65xx" which can sort of provide a last gasp chance of recovery.
help with ROM
Hi there,
Need desperate help. I followed the instructions here but ended up with no OS in the s7e. I kept on trying to install a signed ROM via ADB, it reaches 100% senidng but always failed inside TWRP. Not succesful even with CWM. I even tried installing from SD card but no success. Please help, thank you.
Anyone still around here?
Mike S ... not sure you (or anyone else) is paying any attention to this thread anymore (and the HP Slate 7 Extreme at this point is a fairly old device) ... but I can't get any of these methods to work and my S7E (model 4450) is basically useless right now. When cold (i.e. not booted up in prior 30mins or so), I can boot it normally, but within about 10mins, it will "crash" to the all-white HP splash screen and will never recover. Holding the power button just has it go through initial startup, get to the white HP splash screen, and sit there until the battery runs down. I haven't been able to root it yet, so the bootloader still shows "locked". What's ironic is that this device is really all I need -- I don't play high-end games and mostly just stream shows -- but now it's completely unusable. I'm not sure which is easier ... trying to get this to root or just buying something else?
So far, to root, I've tried towelroot and Cydia Impactor, but both of those returned errors as others have reported. I tried following the steps that Mike S put up here, but without my tablet being rooted, adb and fastboot don't even detect my device from the PC (though the PC detects it because I'm able to see it in Windows Explorer and drag files to the storage) ... so it seems like I can't even get to install CWM or anything further.
Maybe the right thing to do is just to dump the paperweight ... it used to work so well but about 6 months ago this stupid HP white screen crash started happening, and since then it's become a regular thing that only takes about 10 mins (at most) before it craps out. I can get to the bootloader and onboard recovery mode, but that doesn't let me load anything.
Not sure where to go next but any advice would be appreciated!
--AJ
MGrad92 said:
Mike S ... not sure you (or anyone else) is paying any attention to this thread anymore (and the HP Slate 7 Extreme at this point is a fairly old device) ... but I can't get any of these methods to work and my S7E (model 4450) is basically useless right now. When cold (i.e. not booted up in prior 30mins or so), I can boot it normally, but within about 10mins, it will "crash" to the all-white HP splash screen and will never recover. Holding the power button just has it go through initial startup, get to the white HP splash screen, and sit there until the battery runs down. I haven't been able to root it yet, so the bootloader still shows "locked". What's ironic is that this device is really all I need -- I don't play high-end games and mostly just stream shows -- but now it's completely unusable. I'm not sure which is easier ... trying to get this to root or just buying something else?
So far, to root, I've tried towelroot and Cydia Impactor, but both of those returned errors as others have reported. I tried following the steps that Mike S put up here, but without my tablet being rooted, adb and fastboot don't even detect my device from the PC (though the PC detects it because I'm able to see it in Windows Explorer and drag files to the storage) ... so it seems like I can't even get to install CWM or anything further.
Maybe the right thing to do is just to dump the paperweight ... it used to work so well but about 6 months ago this stupid HP white screen crash started happening, and since then it's become a regular thing that only takes about 10 mins (at most) before it craps out. I can get to the bootloader and onboard recovery mode, but that doesn't let me load anything.
Not sure where to go next but any advice would be appreciated!
--AJ
Click to expand...
Click to collapse
Get your device drivers right (try androidsdk if it's still not getting recognised) and fastboot the stock system images (fastboot is not root dependent). By the way why were you trying those weird rooting methods ??? Just flash supersu from cwm/twrp and be done with it.
Thanks ... I'll try androidsdk. I actually am a root n00b and so I was trying to figure out the simplest way to go. I guess I guessed wrong! But of course before I can get that working I need the right drivers ... So I'll try that first. I was thinking the drivers were OK since my PC recognized the S7E when Android loaded (before it crashed to the white screen).
Couldn't get androidsdk to work
Hello again... I never could get androidsdk to work. My computer never recognized the tablet to be able to fastboot. *sigh* As much as I hate to give up, I don't know what else to do.... I might try another PC?
Looking for update.zip for S7E
mike-s said:
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot: This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk: The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip: A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt: A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
Click to expand...
Click to collapse
Hey Mike, you wouldn't still happen to have that signed update.zip since you've don't have it on Dropbox anymore?

Help really need here, big issues

Hello to everybody, so i was thinking my nakasi was really dead this time, the last thing i did was flashing a 5.1.1 rom next when i rebooted got stuck on lolipop boot loop so i restarted the tablet
manually to access the recovery, and to my awe, i couldn't no more access the recovery ! (latest twrp) tried again and again nothing, no recovery no bootloader, can't start the OS
always stuck on google logo with the options above, start, bootloader, recovery etc, today i realized i could access the bootloader and fastboot mode (ADB recognize my device when i type fastboot devices)
so i tried flashing stock image and stuff with no luck, tried many stock roms, tried wug's toolkit and the flash all.bat still no luck, i get all kind of error messages here is a screenshot, help is really appreciated if there is anything i can do to save it :
View attachment 3305126
the problem seems to be that i can't write the things i send to the tablet via ADB, tried the NVflash recovery today and got :
View attachment 3306049
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
gaosphappy said:
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
Click to expand...
Click to collapse
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Homurato said:
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Click to expand...
Click to collapse
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
adomol said:
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
Click to expand...
Click to collapse
Hello kind sir, of course at first i tried the 5.1.1 full factory image with the NRT toolkit and got the same writing errors next i tried many bootloaders
(one of them found it here as a 100% working bootloader) the Flatline is the recovery of the NVflash tool where you can access it to unbrick full bricked N7s
if you got blobs.bin of your N7 backed up (clearly not my case)
the flashing writing error i get it with everything i try to flash, recoverys bootloader system etc
when i send them with the flash all command they got sent to the tablet okay, but when writing i get the errors
i don't know but there is a small informations if that can help, before it broke my system was in EXT4 and all the rest in F2FS
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
fwayfarer said:
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
Click to expand...
Click to collapse
I'm still hoping for a software solution since my fastboot works fine, I'll let the motherboard solution my last i guess
Hello some news about the still staggering situations : when the tablet is off and i put the charger i get the battery refiling animation ! so that mean the bootloader isn't broken
and i still can access fastboot mode, even when i push a bootloader i get a signature match message, but the problem is still that the things i push can't be written as i'm still getting a :
FAILED <Remote: <FileWriteFailed>> changed usb cables, changed ports, the last time the tablet was working i had the system on EXT4 and the rest on F2FS, maybe if i can convert everything to EXT4 ?

Help, bootlooped! Locked bootloader.

Hello!
I have the Nexus 6P and I have successfully rooted 16 phones over the past 4 years and never had a problem I couldn't fix. Today I made a mess of my new phone.
I had a perfectly working custom ROM with an unlocked boot loader with TWRP (2.8.7.2) installed. I installed some custom soft keys and got into a boot loop. I went and flashed what I thought was the stock ROM according to the website I was following, and I re locked my boot loader like a fool and was going to eventually unlock it.... turns out I was still boot looped.
I have tried:
sideloading 3 different zips, always get the message "cannot read zip" whatever the zip is
I tried changing the names, doing the full names, doing a stock rooted zipped ROM, nothing works.
I have used SkipSoft and Wugs toolkit and I can't flash ANYTHING or transfer files onto the phone unless the bootloader is unlocked.
I have installed the Google drivers multiple times, ADB devices always works, it seems to not be a driver issue because I can do everything else fine.
I have let the phone sit for 35 minutes in bootloop waiting for it to come back online so I can tick that "OEM unlock" button in the settings menu.
I have also done a dozen other things, the problem is nothing I have done or tried allows me to get any ROM or any file onto the device to flash in TWRP.
Help?
ok shot in the dark here. I had a boot loop until I flashed the flashable vendors zip
I got it in this thread:
http://forum.xda-developers.com/nexus-6p/development/rom-pure-nexus-layers-fi-wifi-calling-t3244563
Give it a whirl if you haven't already.
Found this in the Pure Nexus Project thread, so props to them for providing this.
-MotoNexus- said:
Hello!
I have the Nexus 6P and I have successfully rooted 16 phones over the past 4 years and never had a problem I couldn't fix. Today I made a mess of my new phone.
I had a perfectly working custom ROM with an unlocked boot loader with TWRP (2.8.7.2) installed. I installed some custom soft keys and got into a boot loop. I went and flashed what I thought was the stock ROM according to the website I was following, and I re locked my boot loader like a fool and was going to eventually unlock it.... turns out I was still boot looped.
I have tried:
sideloading 3 different zips, always get the message "cannot read zip" whatever the zip is
I tried changing the names, doing the full names, doing a stock rooted zipped ROM, nothing works.
I have used SkipSoft and Wugs toolkit and I can't flash ANYTHING or transfer files onto the phone unless the bootloader is unlocked.
I have installed the Google drivers multiple times, ADB devices always works, it seems to not be a driver issue because I can do everything else fine.
I have let the phone sit for 35 minutes in bootloop waiting for it to come back online so I can tick that "OEM unlock" button in the settings menu.
I have also done a dozen other things, the problem is nothing I have done or tried allows me to get any ROM or any file onto the device to flash in TWRP.
Help?
Click to expand...
Click to collapse
Thanks, the problem is I can't find a way to sideload anything or move a file over. Everything results in a myriad of errors.
tigercranestyle said:
at worst, you would have to invoke the flash-all command via adb once you extracted the couple of times that you have to. directions are on google's factory image site.
may not be the answer that you were looking for, but it always feels great having a clean device to work with. i mean as it stands, you would have to set everything back up on whatever rom anyway if you somehow got out of the problems you were having. you would spend more time doing that instead of just going the factory image route.
toolkits are fun, but learning your way around them is even more so.
Click to expand...
Click to collapse
I'm gonna check the flash all,I've never done that before. I think that would be all the images in the tgz factory image? Anything to get my phone back yeah, I just need it working again.
-UPDATE- I tried the flash all batch in the system image and I tried the flash all batch command and neither work.
Hey man - crazy story - I literally just got done messing with a toolkit and the EXACT same situation happened to me. Locked bootloader, bootloop, everything. What you need to do is do a complete wipe of everything in TWRP so you can access /data from your PC (unless it isn't messed up currently, and you can decrypt within TWRP, I couldn't...) Then, download Cataclysm (maybe something else will work, idk, but I just did it with cataclysm) and bam - it boots, head to developer options and get the box checked.
Stock images didn't work, nothing did... was scared I had a brick. The saving grace for us is that we both got TWRP installed. No more toolkits for me!
Melamunna said:
Hey man - crazy story - I literally just got done messing with a toolkit and the EXACT same situation happened to me. Locked bootloader, bootloop, everything. What you need to do is do a complete wipe of everything in TWRP so you can access /data from your PC (unless it isn't messed up currently, and you can decrypt within TWRP, I couldn't...) Then, download Cataclysm (maybe something else will work, idk, but I just did it with cataclysm) and bam - it boots, head to developer options and get the box checked.
Stock images didn't work, nothing did... was scared I had a brick. The saving grace for us is that we both got TWRP installed. No more toolkits for me!
Click to expand...
Click to collapse
I have already done the advance wipe and the format data, I just tried again and my computer will not read it as storage with MTP enabled.
Thanks though!
tigercranestyle said:
after extracting the tgz file, it should become a tar file. after extracting that tar file, it should become the six files listed below. these files should be in platform-tools to start from scratch.
bootloader-angler-angler-02.45.img
flash-all.bat
flash-all.sh
flash-base.sh
image-angler-mmb29m.zip
radio-angler-angler-02.50.img
once they are, open command line in that directory (platform-tools) and then "flash-all" should work. if it doesn't make sure you post the error that you're getting on your computer so that others can help.
Click to expand...
Click to collapse
I followed all these steps, I unzipped it and everything and put it in my fastboot folder. I still get the "unknown partition "all" " orrr flash is not recognized as an internal or external command, operable program or batch file. In an attempt with desperation I tried opening every version of the batch file, in the tgz and tar and unzipped AND in the fastboot and it all gives the radio img error.
I still do have my fastboot device connected, to my knowledge that means it can't be a driver problem right?
-MotoNexus- said:
I followed all these steps, I unzipped it and everything and put it in my fastboot folder. I still get the "unknown partition "all" " orrr flash is not recognized as an internal or external command, operable program or batch file. In an attempt with desperation I tried opening every version of the batch file, in the tgz and tar and unzipped AND in the fastboot and it all gives the radio img error.
I still do have my fastboot device connected, to my knowledge that means it can't be a driver problem right?
Click to expand...
Click to collapse
You can't flash anything in fastboot with a locked bootloader. The only way you can get your device to work is by using TWRP to flash a rom.
The flash all command doesn't work because the extracted tar file has A zipped folder inside that has to be extracted also with radio and I think recovery zipped up. You have to extract those two files to put them in the tar file and then you might be able to flash all. But as long as you can fastboot devices you should be able to flash all 6 files and have a brand new device.
tigercranestyle said:
sorry for the late reply. not always here.
1. did you unlock the bootloader again before doing all of this?
2. list the files that are in your platform-tools folder.
3. when you executed the "flash-all" command earlier, you did do it with the dash in between flash and all... right? also, you're doing it without the quotation marks, right?
sorry if they seem silly. just never really know.
Click to expand...
Click to collapse
He can't unlock the bootloader without booting into a rom. He needs to use twrp to flash a full system but I am not sure how to help with that when he can't sideload.
just an unrelated question... why did you lock the bootloader again? what was the purpose?
also, as mentioned... locked bootlader, odds arre USB debugging and OEM unlock are also not checked.... afaik, youre in trouble... hopefully someone else can sav you, im out of ideas
akellar said:
You can't flash anything in fastboot with a locked bootloader. The only way you can get your device to work is by using TWRP to flash a rom.
Click to expand...
Click to collapse
Are you telling me that I'm bricked?
I have no way of transfering files to the devices, it won't read as anything to transfer files and ADB won't sideload anything.
tigercranestyle said:
sorry for the late reply. not always here.
1. did you unlock the bootloader again before doing all of this?
2. list the files that are in your platform-tools folder.
3. when you executed the "flash-all" command earlier, you did do it with the dash in between flash and all... right? also, you're doing it without the quotation marks, right?
sorry if they seem silly. just never really know.
Click to expand...
Click to collapse
Neither am I , I just got back from a trip. I have the fastboot exe adb exe mfastboot exe the ADB api files, and the ROMs I tried to sideload along with all the images I pushed to the device.
Originally I had the bootloader unlocked, like I said I was being a fool blindly following a tutorial to get back to stock and I locked it too soon.
Yeah, I tried flash-all flash all and flash flash-all / flash flash all
dontbeweakvato said:
The flash all command doesn't work because the extracted tar file has A zipped folder inside that has to be extracted also with radio and I think recovery zipped up. You have to extract those two files to put them in the tar file and then you might be able to flash all. But as long as you can fastboot devices you should be able to flash all 6 files and have a brand new device.
Click to expand...
Click to collapse
Okay I unzipped that folder and put all the files in the fastboot folder, I still get the same error. The thing that scares me here is I can use the batch file now and it just gives me an error saying it can't flash because it's bootloader is locked.
Soulfly3 said:
just an unrelated question... why did you lock the bootloader again? what was the purpose?
also, as mentioned... locked bootlader, odds arre USB debugging and OEM unlock are also not checked.... afaik, youre in trouble... hopefully someone else can sav you, im out of ideas
Click to expand...
Click to collapse
They are default unchecked, hence the reason I can't unlock the bootloader again. I said it in my first post, I was being a fool following some guide to get back to stock and ******* up a step.
rift999 said:
He can't unlock the bootloader without booting into a rom. He needs to use twrp to flash a full system but I am not sure how to help with that when he can't sideload.
Click to expand...
Click to collapse
Is there not a way to fix the sideload? Or a way to get my computer to read it as a media devices so I can transfer files or something? It's always worked with previous phones but my computer reads the 6P differently. (even when it was working)
Stop trying to fastboot flash anything, it will not work as I've already started multiple times. The only option you have is to get something moved to storage and flash it from twrp.
akellar said:
Stop trying to fastboot flash anything, it will not work as I've already started multiple times. The only option you have is to get something moved to storage and flash it from twrp.
Click to expand...
Click to collapse
I've tried every driver from Google and Nexus 6P, I can't get it to read the MTP for a file transfer, what would you suggest I do? it doesn't show up as my old phones used to in the computers drives.
I have found 0 success with getting a file on through file transfer or ADB push file.
-MotoNexus- said:
I've tried every driver from Google and Nexus 6P, I can't get it to read the MTP for a file transfer, what would you suggest I do? it doesn't show up as my old phones used to in the computers drives.
I have found 0 success with getting a file on through file transfer or ADB push file.
Click to expand...
Click to collapse
Can't help too much personally, but you might give this a shot:
http://forum.xda-developers.com/showpost.php?p=64317181&postcount=20
Sent from my Nexus 6P using XDA Free mobile app
So I just got it............!!!!! I have spent a total of 16 hours with videos, forums and trial and error. When I was going back the 5th around time messing with drivers I turned my ADB driver into a USB composite because I had no idea I could and instantly I was able to file transfer!!!! Problem solved, I have my ROM on now.
Thank you all for your help! I am so sorry I derped at this, I have been doing this a long time and just got sloppy.

Stuck in fastboot loop-HELP!

I was in the middle of a restore in twrp and the phone shut off in the middle of the restore (while restoring recovery), and had such, my android system will no longer boot, nor can I get into recovery. It simply goes into fastboot mode and that's all. Is there a way to flash twrp (Archlinux?) using fastboot/adb?
Thank you in advance!
533y4 said:
I was in the middle of a restore in twrp and the phone shut off in the middle of the restore (while restoring recovery), and had such, my android system will no longer boot, nor can I get into recovery. It simply goes into fastboot mode and that's all. Is there a way to flash twrp (Archlinux?) using fastboot/adb?
Thank you in advance!
Click to expand...
Click to collapse
Depends on what variant you have. If its a dirtysanta one while in fastboot do
Code:
fastboot flash recovery (twrpimgnamehere).img
and it will install the twrp image you have downloaded. If you are on TMO you need to revert to stock using a KDZ and then re root.
Fastboot commands aren't working on the H918? My model... -_-
What's the difference between recowvery and dirtysanta?
OK. So let me ask this then. If fastboot commands don't seem to do much on the H918, then how does one go about backing up the internal storage before being formatted? Is there like a dd command to copy everything over? Or will the phone still attach storage to the PC when attached, even in fastboot?
In other words, how can I backup my internal storage before reseting to stock?
533y4 said:
Fastboot commands aren't working on the H918? My model... -_-
What's the difference between recowvery and dirtysanta?
Click to expand...
Click to collapse
The difference between recowvery and dirtysanta is multiple things. One thing is the fact that recovery goes after the recovery directly and dirtysanta replaces the bootloader itself. IF you use dirtysanta on a H918 you WILL BRICK. non recoverable. Dirtysantas boatloader is a debug bootloader that has full access to the phone. H918 bootloader only has limited commands available.
The other difference is how the methods goes about actually doing everything. Jcadduonos recowvery attacks recovery uses scripts to start a factory recovery installer/updater but makes it install a temp root instead of a recovery then the device has access to fully install a twrp image. Dirtysanta skips that and attacks the bootloader directly by replacing a higher level function of the phone temporarily that has access to the phones bootloader(for some unknown reason) and replaces it with the debug one. Once the debug one is in the device is able to be rooted like any other device with an unlocked bootloader since it has full access.
533y4 said:
OK. So let me ask this then. If fastboot commands don't seem to do much on the H918, then how does one go about backing up the internal storage before being formatted? Is there like a dd command to copy everything over? Or will the phone still attach storage to the PC when attached, even in fastboot?
In other words, how can I backup my internal storage before reseting to stock?
Click to expand...
Click to collapse
You don't. you can copy everything manually but If you backup the data partition(which has your internal storage inside) it will not be usable on the device after you root. If you do manage to back it up then restore it afterward since the device itself is normally encrypted and is now decrypted the settings and stuff will cause crashes and force closes.
me2151 said:
The difference between recowvery and dirtysanta is multiple things. One thing is the fact that recovery goes after the recovery directly and dirtysanta replaces the bootloader itself. IF you use dirtysanta on a H918 you WILL BRICK. non recoverable. Dirtysantas boatloader is a debug bootloader that has full access to the phone. H918 bootloader only has limited commands available.
The other difference is how the methods goes about actually doing everything. Jcadduonos recowvery attacks recovery uses scripts to start a factory recovery installer/updater but makes it install a temp root instead of a recovery then the device has access to fully install a twrp image. Dirtysanta skips that and attacks the bootloader directly by replacing a higher level function of the phone temporarily that has access to the phones bootloader(for some unknown reason) and replaces it with the debug one. Once the debug one is in the device is able to be rooted like any other device with an unlocked bootloader since it has full access.
You don't. you can copy everything manually but If you backup the data partition(which has your internal storage inside) it will not be usable on the device after you root. If you do manage to back it up then restore it afterward since the device itself is normally encrypted and is now decrypted the settings and stuff will cause crashes and force closes.
Click to expand...
Click to collapse
Very interesting how different the two are and how they work. Very interesting indeed.
As for the data partition, mine is already decrypted as is (was rooted already and tried to install a cm rom to test; ended up glitches during restore). But I have no intentions on restoring an backups. I simply want my photos, saves, books, etc off the actual internal SD storage (not my external SD card, obviously).
My question here I guess is, will the internal storage mount while in fastboot mode the same as if the phone was on normal (adds a new drive (win)/mtp link (unix))?
I just want to copy and paste all the files off the internal storage on to my unix desktop. Then format the whole phone and start fresh again.
*bump*
I have tried to access the SD card while in fastboot mode. Absolutely nothing I do can make the PC see the internal storage on my V20. I have some files for my job on my internal SD card (NOT my external SD card, but the actual built in storage), that I absolutely, positively cannot afford to loose. These files are for my job. If I loose these files, I will loose my job.
Please, can someone tell me how to access the SD card in fastboot mode? It's really really important.
If anyone, at all, has any clue or any ideas on how to access the internal storage or how to restore my v20 without a full reset, then please please please help. Hell, I'll even be willing to donate some money to whoever can figure this out for me. Seriously, it's really that important that I get my files off the internal storage.
Thanks to anyone who can help.
P.s. I have access to Windows and Linux computers.
533y4 said:
*bump*
I have tried to access the SD card while in fastboot mode. Absolutely nothing I do can make the PC see the internal storage on my V20. I have some files for my job on my internal SD card (NOT my external SD card, but the actual built in storage), that I absolutely, positively cannot afford to loose. These files are for my job. If I loose these files, I will loose my job.
Please, can someone tell me how to access the SD card in fastboot mode? It's really really important.
If anyone, at all, has any clue or any ideas on how to access the internal storage or how to restore my v20 without a full reset, then please please please help. Hell, I'll even be willing to donate some money to whoever can figure this out for me. Seriously, it's really that important that I get my files off the internal storage.
Thanks to anyone who can help.
P.s. I have access to Windows and Linux computers.
Click to expand...
Click to collapse
can you let it boot up and will it just hang on the lg logo or is it rebooting into fastboot?
really my only advice would be try letting it hang on lg logo and see if adb is present, furthermore you can get a adb always moded boot.img and push that to the phone using fastboot then see if adb is a option.
If so you can do the adb commands to pull the userdata portion off the device the same way the system dumps are done i believe, but the sad fact is its probably all currupted anyway from your restore you were trying.
The other option is push recovery again to device, and then try a dirty flash of the stock rom, in hopes it can get the system partition back up and running,
furthermore, worst case wipe all and flash the rom, once its back up and running, download diskdigger from playstore and see if it can recovery the deleted stuff, or try the phonedoctor program for windows that runs against your internals and trys to recocvery stuff..
The biggest question is why were you flashing your device without saving stuff thats "soooo important and can cost you your job" ? seems like a oversight on your part really, and a lesson learned. Backup work stuff always, and dont play with roms during work days lol, not to be mean but really, why risk your job and lively hood over some unsaved stuff?
I did actually have a back up on my S6, which I dropped and broke a mere hour before this. So it's not at all an oversight. There were backups in place. And it won't boot at all or I'd had been able to get adb Atleast. ADB won't see the v20 and I tried to flash recovery using fastboot flash recovery recovery.img command. It says unknown.
How can one going about flashing such a boot.img in the H918? Where can one find such things? I assume you mean a kernel of some sort, right?
I truly appreciate the reply. Has I said, it's not like I didn't have backups. I did. It really is an issue of bad luck. : (
i tried this it worked https://forum.xda-developers.com/v20/help/lg-v20-access-to-fastboot-t3557328
Have you tried power on and volume down to go through the factory reset screens.
A bunch of us had this problem and it was because an update downloaded on it's own and the bootloader snoops it out and forces recovery to boot.
Just do the volume down + power button - as soon as you see the lg logo release power only then immediately re-press power and continue holding power and volume down until the factory reset screen pops up. Select yes and yes, (don't worry - if you have twrp recovery it can't reset). It will boot you into TWRP and I'm pretty sure it will delete the update files in fota folder.
In TWRP select reboot - system and it should boot normally like nothing happened.

[ZE552KL] Bizzare issue when flashing TWRP

On my ZF3, I'm on Nougat with the bootloader unlocked and I've confirmed that.
Followed instructions on the XDA ZF3 ROOTING GUIDE thread & ZF3 Toolkit, I can't seem to flash TWRP due to an error.
"
sending 'recovery' (26636 KB)...
OKAY [ 0.912s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.075s
"
I've enabled USB debugging and even restarted, redownloaded drivers, changed USB ports and re did again but still the same error.
Any tips and solution?
Try booting TWRP first, then flashing from within TWRP.
The command is "fastboot boot <path to TWRP image>".
sensi277 said:
Try booting TWRP first, then flashing from within TWRP.
The command is "fastboot boot <path to TWRP image>".
Click to expand...
Click to collapse
Just tried right now, did the command but its stuck at booting. My zf3 didn't boot the .img
Prev was too blurry
Have you been able to flash anything via fastboot from that computer?
Which OS are you using, windows? Firewall disabled? Do you have another computer you can try it on? From what I've read, it's a driver issue causing this and since you've tried reinstalling them, I'd try downloading the USB bootable version of Linux and try again. The commands are the same.
You may be able to flash it through an adb shell too, but I'd try the Linux USB first. On the ze552kl, the recovery partition is #59, so the command would be "dd if=/sdcard/TWRP.bin of=/dev/block/mmcblk0p59".
Edit: I see you posted in the other section you tried other computers so i guess try the DD command. Only thing is, you should back up your original partition first just in case because something is definitely bizarre. Run "dd if=/dev/block/mmcblk0p59 of=/sdcard/recoverybak.bin" first so you can revert if it goes awry.
wang1chung said:
Have you been able to flash anything via fastboot from that computer?
Which OS are you using, windows? Firewall disabled? Do you have another computer you can try it on? From what I've read, it's a driver issue causing this and since you've tried reinstalling them, I'd try downloading the USB bootable version of Linux and try again. The commands are the same.
You may be able to flash it through an adb shell too, but I'd try the Linux USB first. On the ze552kl, the recovery partition is #59, so the command would be "dd if=/sdcard/TWRP.bin of=/dev/block/mmcblk0p59".
Edit: I see you posted in the other section you tried other computers so i guess try the DD command. Only thing is, you should back up your original partition first just in case because something is definitely bizarre. Run "dd if=/dev/block/mmcblk0p59 of=/sdcard/recoverybak.bin" first so you can revert if it goes awry.
Click to expand...
Click to collapse
How do you restore that ".bin" if anything fails? And if it does fail, what's the "problem" that I'll be having to fix?
TiTAN-O-One said:
How do you restore that ".bin" if anything fails? And if it does fail, what's the "problem" that I'll be having to fix?
Click to expand...
Click to collapse
You restore it with the same DD command you used to flash the TWRP recovery bin (dd if=/sdcard/recovery.bin of=/dev/block/mmcblk0p59)
No access to recovery is the problem you'll have.
edit: wait, do you get the warning screen on bootup now since unlocking? The one where you hit the volume keys to get to recovery/bootloader mode?
wang1chung said:
You restore it with the same DD command you used to flash the TWRP recovery bin (dd if=/sdcard/recovery.bin of=/dev/block/mmcblk0p59)
No access to recovery is the problem you'll have.
edit: wait, do you get the warning screen on bootup now since unlocking? The one where you hit the volume keys to get to recovery/bootloader mode?
Click to expand...
Click to collapse
I unlocked my ZF3 via the "0.unlock_ze522kl.bat" way. Some people complained that the official way of unlocking frm the Asus website broke their devices or smth.
Got me a "No such file or directory" when I dd. "Failed to open /sdcard/TWRP.bin"
No warning screen as far as ik. I unlock unofficially. Am I right to say that under the Asus bootloader, a barcode will be seen when it is unlocked?
Im on Nougat officially.
TiTAN-O-One said:
Got me a "No such file or directory" when I dd. "Failed to open /sdcard/TWRP.bin"
No warning screen as far as ik. I unlock unofficially. Am I right to say that under the Asus bootloader, a barcode will be seen when it is unlocked?
Im on Nougat officially.
Click to expand...
Click to collapse
Not sure about the unofficial way but with the official way you get that bootup menu I mentioned along with a warning screen that your phone isn't secure or something. I believe the unofficial way only works on marshmallow, did you use it on nougat?
You have to take the TWRP bin and place it in the root of your sdcard and then try the command.
wang1chung said:
Not sure about the unofficial way but with the official way you get that bootup menu I mentioned along with a warning screen that your phone isn't secure or something. I believe the unofficial way only works on marshmallow, did you use it on nougat?
You have to take the TWRP bin and place it in the root of your sdcard and then try the command.
Click to expand...
Click to collapse
Okay i can confirm the "Bootup and device is insecure" screen is the official way to Unlock your bootloader. I didn't do via that way cos I'm on Nougat. I did the unofficial way cos that's meant for nougat.
As for the TWRP flash, i did everything and still the same. TWRP.bin is at the chosen directory. Just to confirm, its all done under ADB right? And then simply use the dd command right?
TiTAN-O-One said:
Okay i can confirm the "Bootup and device is insecure" screen is the official way to Unlock your bootloader. I didn't do via that way cos I'm on Nougat. I did the unofficial way cos that's meant for nougat.
As for the TWRP flash, i did everything and still the same. TWRP.bin is at the chosen directory. Just to confirm, its all done under ADB right? And then simply use the dd command right?
Click to expand...
Click to collapse
We're talking internal sdcard, right? While in the adb shell, cd to /sdcard and do an ls and verify you can see your TWRP.bin there.....I think it's case sensitive too.
Also, remember I said to back your original one up just in case, so try to do that and verify everything is working.
I was under the impression the unofficial unlock didn't work on nougat and the official did? I thought it was some people doing the unofficial unlock that bricked their phones, which is why I chose the official, lol.
wang1chung said:
We're talking internal sdcard, right? While in the adb shell, cd to /sdcard and do an ls and verify you can see your TWRP.bin there.....I think it's case sensitive too.
Also, remember I said to back your original one up just in case, so try to do that and verify everything is working.
I was under the impression the unofficial unlock didn't work on nougat and the official did? I thought it was some people doing the unofficial unlock that bricked their phones, which is why I chose the official, lol.
Click to expand...
Click to collapse
Right guess what m8. I realised that I didnt and now couldn't unlock my bootloader. Here's what I did for the Unofficial Nougat way of unlocking ZF3 bootloader
Download this Zip file containing a folder called RootZenfone3-master.
Inside this folder contains 4 .bat files that is automated and named orderly so users can easily unlock and root their ZF3.
1st bat file being UnlockzeXXX.bat
2nd bat FlashRecovery.bat
3rd bat GetRoot.bat
Now 1st bat is obvly the bat file to unlock bootloader, ran it, followed the instructions to boot to bootloader etc and waited, only to know that unlocking the bootloader was unsuccessful.
Neermind that, if the bat file wasnt working, you can manually "Fastboot flash all" a file called unlock_ze552kl.raw that i believe contains a partition to unlock the bootloader.
So yes I ran the command but now i have an error that says
"FAILED (remote: Partition flashing is not allowed)"
Same error for both my Linux and Windows machine.
Found a thread here and a user says
"The ASUS Zenfone 3 comes shipped encrypted by default. This is required by Google's Play Services agreement for phone OEMs. You cannot remove decryption on the Zenfone 3 without using a custom ROM"
I had this annoying "reboot and type my pin password" whenever I restart my phone.
Any idea how to remove or decrypt this? I believe this is the issue to all the failed and permission denied errors i guess.
TiTAN-O-One said:
Right guess what m8. I realised that I didnt and now couldn't unlock my bootloader. Here's what I did for the Unofficial Nougat way of unlocking ZF3 bootloader
Download this Zip file containing a folder called RootZenfone3-master.
Inside this folder contains 4 .bat files that is automated and named orderly so users can easily unlock and root their ZF3.
1st bat file being UnlockzeXXX.bat
2nd bat FlashRecovery.bat
3rd bat GetRoot.bat
Now 1st bat is obvly the bat file to unlock bootloader, ran it, followed the instructions to boot to bootloader etc and waited, only to know that unlocking the bootloader was unsuccessful.
Neermind that, if the bat file wasnt working, you can manually "Fastboot flash all" a file called unlock_ze552kl.raw that i believe contains a partition to unlock the bootloader.
So yes I ran the command but now i have an error that says
"FAILED (remote: Partition flashing is not allowed)"
Same error for both my Linux and Windows machine.
Click to expand...
Click to collapse
That "FAILED (remote: Partition flashing is not allowed)" error means you're bootloader isn't unlocked. I believe that is the root cause of your issue.
Use the official unlock, works every time.
The pin at the beginning bootup is a security setting. I believe there was a thread where someone said to disable security lock and then reenable it but chose "no" when it asks to use pin to start device. Give that a shot first and see.
For the official bootloader unlock, is it compatible with Nougat?
Good news, it IS compatible with Nougat. Now my bootloader is unlocked and TWRP is installed successfully. However, i don't seem to get any root access despite flashing the latest supersu.zip nunerous of times. Any ideas why?
TiTAN-O-One said:
Good news, it IS compatible with Nougat. Now my bootloader is unlocked and TWRP is installed successfully. However, i don't seem to get any root access despite flashing the latest supersu.zip nunerous of times. Any ideas why?
Click to expand...
Click to collapse
Do you see the SuperSU icon in your app drawer?
Did you follow this guide and install all four zips?
I had an issue and needed to update busybox, but that was easily done from the playstore.
wang1chung said:
Do you see the SuperSU icon in your app drawer?
Did you follow this guide and install all four zips?
I had an issue and needed to update busybox, but that was easily done from the playstore.
Click to expand...
Click to collapse
Great! Everything is settled and Im unlocked and rooted successfully too. Thanks for the help.
Glad you got it sorted, now make a TWRP backup of all your partitions and go crazy flashing lol

Categories

Resources