New LEX727's run Android 6.1 out of the box.
Only the "critical partitions" can be unlocked using adb/fastboot. Recovery partition is not "critical" apparently.
No SU in the native 6.1 binaries, so no way to flash non-critical partitions.....i.e.. Recovery.
Bottom line, been at it three days, this thing appears to be root and flash resistant, so far.
Fastboot boot recovery option? Flashing emmc_appsboot partition from a x720?
Did you try the steps in this post?
Post 203 Persistent Bootloader...
Please note that where it says "adb devices" it should really be "fastboot devices"
Wow, THANK YOU SOOOOO MUCH
Worked beautifully, thank you so much.
New best friend.
: )
Related
Hey,
I had problems with the phone and support told me I should flash it. So when I wanted to "flash system.img"
it showed me: Data Transfer Failure (after 48secs)
and when I type in "fastboot devices" now, the name of device now only shows questionmarks: "?????????? fastboot"
And nothing is working now
So when i try to flash system again, windows says "fastboot.exe stopped working"
I am devastated. How can this happen? and what can I do? Please help me
OlivBlum said:
Hey,
I had problems with the phone and support told me I should flash it. So when I wanted to "flash system.img"
it showed me: Data Transfer Failure (after 48secs)
and when I type in "fastboot devices" now, the name of device now only shows questionmarks: "?????????? fastboot"
And nothing is working now
So when i try to flash system again, windows says "fastboot.exe stopped working"
I am devastated. How can this happen? and what can I do? Please help me
Click to expand...
Click to collapse
So you were on cos12.1 and you tried to flash stock images using fastboot? Explain a bit what happened so that i can guide you more accurately..
Anyhow you can always go here http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
And use qfil tool to flash to stock .. read a few posts below to figure out how you should do this and u will end up with zui 1.5 then you can convert to cm or any other rom
Hey thanks for the answer
So I was on COS 12.1 all normal, no root, no unlocked bootloader.
And I wanted to flash COS 12.1 again. So I downloaded the official fastboot image from cyngn . com/support and unzipped it. In there was a system.img file that I tried to flash via "fastboot flash system system.img" Thats when the error occured.
Before that I unlocked the bootloader, started the device, then I flashed the recovery and afterwards the system.
I will now look into the link and see if it helps and report back. Thanks already
OlivBlum said:
Hey thanks for the answer
So I was on COS 12.1 all normal, no root, no unlocked bootloader.
And I wanted to flash COS 12.1 again. So I downloaded the official fastboot image from cyngn . com/support and unzipped it. In there was a system.img file that I tried to flash via "fastboot flash system system.img" Thats when the error occured.
Before that I unlocked the bootloader, started the device, then I flashed the recovery and afterwards the system.
I will now look into the link and see if it helps and report back. Thanks already
Click to expand...
Click to collapse
Before you go to what i suggested
Can you boot into fastboot or recovery ?
If you have whatsapp add me then we can talk it through would be easier than me checking the forum everynow and then ..u'll find my number in private
After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!
CanIHelp said:
After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!
Click to expand...
Click to collapse
https://forum.xda-developers.com/huawei-p9lite/how-to/unified-help-thread-huawei-p9-lite-t3649152
Post 5. Unbricking EMUI 5. Don't take for granted it will work, but considering FRP is locked, this is the only way not needing a unlocked bootloader.
Doesn't work. It's still stuck at the "Your device is booting now..." under the vmall link screen.
Isn't the 3-button method counting on the original recovery being in the recovery partition?
I only have the second recovery working (that eRecovery which only lets you "download and install the latest recovery and system"...and doesn't do anything).
Is there a way to override the frp lock? I saw a couple of tools online claiming to do that, but none worked. I haven't tried DC-Unlocker. If I'm gonna pay for it, might as well go to a service
Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.
Plug your phone on computer.
You see yellow advice? Appears automatically.
Juste after this advice, tip "fastboot reboot bootloader".
After, unlock your bootloader again "fastboot oem unlock YOUR_OEM_CODE"
Ok now shutdown and hold buttons for boot to TWRP recovery, if not appears, flash it on "fastboot flash recovery recovery.img"
Warning command not allowed on fastboot is 90% time du at bootloader unlocked (even if he says it's good)
dariomrk said:
Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.
Click to expand...
Click to collapse
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!
CanIHelp said:
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!
Click to expand...
Click to collapse
No problem mate, nice to hear you did it without problems.
I have lineageos 14.1 with TWRP and want to sell my phone, so I wanted to wipe everything and install stock rom and recovery.
In the TWRP, I made Advanced Wipe and selected everything, but not USB-OTG. After that, I made "format data".
Now, I would like to install stock recovery and stock rom.
However, when I go into the bootloader, the adb does not recognize my phone.
"adb shell" results in: error: device '(null)' not found.
I also cannot simply boot my smartphone, then I am stuck in a bootloop.
How can I fix this?
Can you use fastboot in the bootloader ? If yes just use the command "fastboot flash recovery stock-recovery.img" then "fastboot oem lock" and finally in the recovery go in adb and use the command "adb sideload stockoxygenos.zip"
Puddies said:
I have lineageos 14.1 with TWRP and want to sell my phone, so I wanted to wipe everything and install stock rom and recovery.
In the TWRP, I made Advanced Wipe and selected everything, but not USB-OTG. After that, I made "format data".
Now, I would like to install stock recovery and stock rom.
However, when I go into the bootloader, the adb does not recognize my phone.
"adb shell" results in: error: device '(null)' not found.
I also cannot simply boot my smartphone, then I am stuck in a bootloop.
How can I fix this?
Click to expand...
Click to collapse
very easy
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169/page1
Hello everyone,
It's my first time on a forum like this, I hope i'm doing it right and that you'll be able to help me
So, I followed Samuel Ridosko's tutorial to install Android on lumia 520. I followed every step with success until I ran uefi2lk.cmd.
It happened very fast, i think with success, but the tool closed by its own before I had time to see anything. But what I did notice is that my phone didn't reboot in TWRP. My phone is found under device manager, in Kedacom USB - Android Bootloader Interface. No error message there.
Fastboot does find my phone. I tried to re-install android drivers, and restart the system. But the command "adb devices" still doesn't show anything at all, contrary to fastboot.
I read the comments below the tutorial and tried to flash things manually, like so :
fastboot boot DATA\gptflasher.img
fastboot format system
fastboot format userdata
fastboot format cache
fastboot flash TZ DATA\TZ.img
fastboot flash modem DATA\modem.img
fastboot flash recovery DATA\twrp.img
fastboot oem reboot-recovery
The phone reboots, vibrates, i see the nokia logo and.... nothing more. Still detected in "fastboot devices", not "adb devices".
I can't perform the adb sideload step.
I do have a backup, but since adb doesn't recognize my phone, I have no idea of what to do to fix things.
I tried getting help under the video tutorial, but no one replied, so, i really hope someone here might try to give me a hand ! and sorry if my English is a little odd, I'm french (and new at developer's stuff, i'm actually a webdesigner girl, so it's not easy )
Thank you in advance for taking the time to read and help, and sorry if I posted at the wrong place or anything !
Weird: I was just using it normally, it switched off and now it stays stuck on the Google logo; when entering recovery mode, I get TWRP"s splash screen and it stays there, so I cannot even recover.
Suggestions please??
Note 1: I'm pretty bad with this kind of stuff, need step-by-step instructions.
Note 2: rom is AOSP 7.1.2 but I guess is irrelevant, as even TWRP does not load.
Thanks in advance!!
Can you fastboot boot the TWRP recovery?
Hmmm dont know exactly what that means sorry; I mean I havent tried connecting it to the laptop and using thr ADB toolkit, but I can reset via Power+VolDown to the bootloader menu (? the android layind down and giving the option to StartSystem/ SwitchOff/ Restart/ RecoveryMode), and choosing RecoveyMode it tries to launch TWRP (it even shows the logo) but stays there on the splashscreen, doesn't quite manage to give me the TWRP menus
Someone?
AndDiSa said:
Can you fastboot boot the TWRP recovery?
Click to expand...
Click to collapse
let's see... I set in recovery mode, connect to the PC (does not recognise it), and with "fastboot boot twrp.img" it just sends/writes the file, the tab shows the Google logo with open lock, and then tries to launch Twrp, but as before, it just get stuck in the splashscreen "TeamWin Recovery Project 3.3.1.0" , so just the same.
Command "fastboot flash boot twrp.img" the same
Command "fastboot flash recovery twrp.img" the same
Command "adb devices" returns the list empty
Command "adb reboot recovery" returns "error: no devices / emulators found"
Command "fastboot oem unlock" returns "(bootloader) bootloader is already unlocked"
I tried running a tool called FirstAid (https://forum.xda-developers.com/devdb/project/dl/?id=16684) but does nothing for me
I'm lost, please help
Video and photos of the issue (device, not adb)
video: https://photos.app.goo.gl/GrFrmQhbyQeHVFZN7
Well, looking at your video it seems that there is no bootable ROM installed and also the recovery (for what ever reason) has some issues to start.
The fact, that you are able to boot into bootloader shows that at least it's not completely bricked ... but there's still the chance that the flash memory has some issues.
I would connect the device via usb with a PC and try to do a
fastboot boot <twrp-3.3.1-grouper.img>
to whether in that case the recovery is booting.
If this is successful, the next step would be re-flashing the recovery into the recovery partition and booing into recovery mode from the bootloader.
If this is successful, too, wiping and flashing a new ROM would be the last step.