I have a LeEco Le2, Indian version, and I installed a custom ROM (AospExtended with android 8) successfully after following all the recommended procedures like OEM unlock, TWRP flash, backup with TWRP, etc. But due to some cdla issues, i decided to revert back to stock EUI. So when I tried to restore the backup, it failed saying 'cannot mount /system - invalid argument'. So I didn't had any option other than to stay on android 8's ROM. Later I found some stock EUI ROMs available on XDA and other forums (which needed to be installed through stock recovery's update.zip method), so I gave them a try. But most of them failed. Installation completed without giving any error, but the EUI never boots up, it gets stuck at the bootup splash screen and never goes any further even after 2-3 hours. So in my last attempt, I transferred the update.zip file in the root, then flashed stock recovery and installed. Like before, the installation completed without any error messages, but no bootup to EUI. Finally when I tried to flash TWRP to flash custom ROM again, everything failed and I discovered that the bootloader got automatically locked. Now I am stuck and not able to do anything, fastboot oem unlock-go fails saying 'remote: oem unlock is not allowed'. What can I do to either make the EUI work, or unlock the bootloader. ?
Related
I have a Z5C(E5803) that was originally able to unlock the bootloader and let me flash ROMs, specifically the Cyanogen ROM that CTXz has been working on. I ran out of power and got stuck in some kind of nasty bootloop yesterday that prompted me to re-flash boot.img and TWRP.
After I did these things I left it charging for a few hours and it was able to boot into TWRP where I then restored it to a backup of the basic Xperia pre-loaded ROM.
This all worked fine, thought I could boot into TWRP and just flash the Cyanogen zip again. I can get into TWRP just fine but I attempt to flash Cyanogen I get an "ERROR 7"
I have since done several wipes, gotten into the bootloader settings by entering that code in the dialer and have seen that bootloader unlock = no. I distinctly remember bootloder unlocking being allowed the first time I installed CM on my device, what could have caused this?
I was able to use it with fastboot anyway and install CM13 again, maybe this was a bug?
When I tried using oem unlock command with fastboot it said my device was already rooted even though I had just restored from a backup, and then I just proceeded normally from there.
use CM13 official Recovery to FLASH CM13.
also i don't think so twrp3.0.2 is out there for z5c. are you using any other variants Twrp? (YUGA ? )
Hey, I've been using Kangvip rom for the Mate10Pro from this (https://forum.xda-developers.com/mate-10/help/kangvip-rom-t3738379)
It comes rooted with Supersu, and got TWRP up and running.
Now I thought of comming back to the stock version of the phone, and having a problem with that.
First my bootloader is unlocked and FRP is locked, Enable Oem unlocking in Devs Settings is off and greyed out, when trying to flash from the full OTA (from this website)
http://pro-teammt.ru/firmware-database/?firmware_model=bla-l29C432B129&firmware_page=0
Based on my Version BLA-l29C432B129
When I try to flash something, an error appears with Command not allowed, I read that I should relock the bootloader so I did try, but got the error " Root type is risk" so it didn't work.
Same problem in TWRP, everything is SDCARD is encrypted so I can't have a zip or boot image there.
Heard you could system upgrade with inbuilt huawei software, but only allows an external sd card :/
I'd just want to return to stock firmware , stock recovery and unrooted
I will provide as much information as I can!
Kind Regards Felipe
Hello, wanting to root my new zenfone I messed up a bit in the bytes.
The situation I'm in now is that system and boot is kinda messed up, the only way to boot into system or recovery is trough fastboot.
The phone is rooted but no wifi and not proper booting (meaning when I boot normally or ">adb reboot recovery",
I'd be stuck in unlocked bootloader message screen and getting fastboot text on top of it after 5 seconds (yea), as opposed to properly boot into whatever I told it to those 5 seconds passed.
but as I said, I can go to fastboot mode and boot from there into recovery or system (fastboot reboot).
Now the thing is, through TWRP when I try to install stock rom, it will fail saying "Failed to mount '/system' (Structure need cleaning).
I'm out of ideas.
What I wan't to do is go back to stock rom(or custom if there is one) basically get the phone to normal working state and retry to get root access properly after understanding it better... this time.
Edit/Solution : Got everything back to stock + root
What I did is that I extracted a stock system.img with UR-Tool Prime v1, from WW-14.1060.1708.70 stock ROM that I got from asus support page. (after flashing system, wifi worked again)
I also took the boot.img that comes along with the zip.
And finally, got stock recovery back by applying "Full Unroot" option from within SuperSu app.
So once you have extracted your system.img from system.new.dat, do the following:
1 - flash boot.img
2 - flash system.img
3 - if you need to, do full unroot option in SuperSu settings
Don't forget to back everything up.
I used Magisk v16 to get root access.
My S7 Edge (G935F) was rooted, but with a stock Nougat that kept negging me with Knox, so I got to change that Nougat to this Oreo ZTO-G935FXXS3ERLA_G935FZTO3ERKA-20181212.zip one. Everything was great until yesterday when I had the great idea of turning off OEM Unlocking. I didn't know what I was doing. Then I got the Custom Binary Blocked by FRP Lock. So I just reflashed a full ROM (instead of just the AP) and now I have no Recovery and every attempt to flash TWRP (last 5 versions or any other recovery.img) with Odin 3.13 has failed. It loads "recovery.img" then fails. I'm stuck with the "No Command" eternal loop.
I've scoured the Internet and found no solution yet. Please, help me save my only phone. At this point I just want it to function as a phone again.
ZoOMBeE said:
My S7 Edge (G935F) was rooted, but with a stock Nougat that kept negging me with Knox, so I got to change that Nougat to this Oreo ZTO-G935FXXS3ERLA_G935FZTO3ERKA-20181212.zip one. Everything was great until yesterday when I had the great idea of turning off OEM Unlocking. I didn't know what I was doing. Then I got the Custom Binary Blocked by FRP Lock. So I just reflashed a full ROM (instead of just the AP) and now I have no Recovery and every attempt to flash TWRP (last 5 versions or any other recovery.img) with Odin 3.13 has failed. It loads "recovery.img" then fails. I'm stuck with the "No Command" eternal loop.
I've scoured the Internet and found no solution yet. Please, help me save my only phone. At this point I just want it to function as a phone again.
Click to expand...
Click to collapse
Reinstall the Odin, Reinstall Samsung Drivers and try reflashing your ROM
It's a tale as old as time. I have a functioning A3 with TWRP and magisk installed. OTA Jan security update failed. "Installation problem" was all it said. I expected this. I think all my magisk mods are systemless but I did flash a custom kernel in TWRP to get kcal.
Ok I'd gone through this for the December update. I downloaded fastboot ROM and extracted the boot.img. I made sure it was correct. Laurel sprout V10.3.13.0.PFQEUXM. But flashing it with either TWRP or fastboot I got the dreaded error screen on reboot where your options are try again or factory reset. Yes I flashed into the active slot. Even when I chose to factory reset and started fresh, I still got the same error when I tried to update.
I also tried to flash boot+system but also got same corrupted error. I tried using flash_all_except_data_storage but got an antirollback error. I've gone back to a nandroid backup for now but obviously I need to get this sorted out before the Android 10 update.
Any ideas? Thanks
Mi A3 doesn't have anti rollback mechanism as far as I know. If you installed TWRP, you also most probably enabled "allow system modifications" (there is a one time prompt on the first start of TWRP, pretty much everyone just dismisses it without reading). TWRP remembers this setting and for each subsequent boot into TWRP it automatically mounts system as R/W, breaking OTA even if you don't flash anything.
You need to reflash stock fastboot images for boot and system with the same version as you're currently running. If you are getting data corruption error, it usually happens when you flash system image from incorrect region or versions differ too much (you're flashing too old image).
Don't install TWRP (or make sure that you delete its settings first and then do NOT allow system modifications).
As you already performed a factory reset, I'd start from fresh state again - switch to active slot A and reflash whole ROM from fastboot, including data wipe (flash_all.bat if I'm not mistaken, but I don't have it in front of me, so double-check its content that it doesn't lock your bootloader).