Hi guys can somebody help me? I am trying fo fixed my little sister rn7 non pro version it keep on saying system has been destroyed i can't flash the vbmeta and install any recovery since the phone bootloader is locked is there any ways to fix this? I can't reflashed the stock rom since the bootloader is not unlocked yet.
Related
I'm trying to flash CM 12.1 to my ZE551KL. I have the most recent nightly and the gapps zips. I tried to flash the ROM and kept getting a signature not verified error that I forget the exact wording of. I researched a bit and concluded that I need to unlock the boot loader. So here's where the problem starts. Asus makes a boot loader that will work on my phone but requires firmware 1.16.40.763. My phone won't update past 1.15 something. And that's odd to me since I just got it yesterday.
I tried to use the Asus boot unlocker anyway but nothing happened because my phone won't update to firmware 1.16.40.763. I saw a firmware update to 1.16.40.763 on the Asus website for the Z00T. I have the Z00TD. Will the Z00T firmware brick my phone or work on my phone? My thought it that if it works I can run the boot unlocker that requires 1.16.40.763 and then with the boot loader unlocked I should stop receiving the signature invalid error when I try to flash CM12.1. Does that sound about right? This is my first time flashing CM myself.
Thank you for your help and thoughts.
You should only flash a ROM that's made specifically for your device.
It's actually a good thing for you that it did not flash.
http://wiki.cyanogenmod.org/w/Unofficial_Ports#Asus - Zenfone 2 Laser is not in the cyanogenmod list.
David McDavid said:
I'm trying to flash CM 12.1 to my ZE551KL. I have the most recent nightly and the gapps zips. I tried to flash the ROM and kept getting a signature not verified error that I forget the exact wording of. I researched a bit and concluded that I need to unlock the boot loader. So here's where the problem starts. Asus makes a boot loader that will work on my phone but requires firmware 1.16.40.763. My phone won't update past 1.15 something. And that's odd to me since I just got it yesterday.
I tried to use the Asus boot unlocker anyway but nothing happened because my phone won't update to firmware 1.16.40.763. I saw a firmware update to 1.16.40.763 on the Asus website for the Z00T. I have the Z00TD. Will the Z00T firmware brick my phone or work on my phone? My thought it that if it works I can run the boot unlocker that requires 1.16.40.763 and then with the boot loader unlocked I should stop receiving the signature invalid error when I try to flash CM12.1. Does that sound about right? This is my first time flashing CM myself.
Thank you for your help and thoughts.
Click to expand...
Click to collapse
Where did you download the CM-12 ROM? Are you sure it's for the ZE551KL?
I'm on the same firmware and the bootloader unlock apk does work, though it leaves no indication after the phone restarts. My guess is that you're phone is bootloader unlocked just fine, but you're trying to flash a rom that wasn't built for ZE551KL (Z00TD).
I'm assuming all of you have already rooted your device and was wondering if you can point me to the files needed so that I can root my Z00TD (ZE551KL)..just got this phone yesterday and switched from a lgg3. Have been looking everywhere and can't seem to find the files needed for thiss specific device..thanks
tmjm28 said:
I'm assuming all of you have already rooted your device and was wondering if you can point me to the files needed so that I can root my Z00TD (ZE551KL)..just got this phone yesterday and switched from a lgg3. Have been looking everywhere and can't seem to find the files needed for thiss specific device..thanks
Click to expand...
Click to collapse
HampTheToker wrote up a nice tutorial fro the ZE551KL:
http://forum.xda-developers.com/showpost.php?p=65264766&postcount=7
Ive never seen it before. Ive installed 3 cook ROM and they all have screen freeze bug (inspite they are stable ROMs). Pls help me out of this loop. I just typed about 400 words and it freeze and I have to type this again. Im writting with angry pls help this newbie.
Im using zenfone 5 T00F
This bug cannot be fixed . Its due to booloader.lock your bootloader and get back to stock rom . Or else use custom roms that works with locked bootloader .
Thank you! But.. How to lock bootloader? With fastboot?
You can use any automated script for that . Or manually lock it by flashing the dnx and ifwi files through fastboot .
But after I relock the bootloader, can I flash new ROM? And after relock, does it affect to the ROM which im using?
You are facing screen freeze issue because of your unlocked bootloader. There is no way to fix this issue. Only solution is just revert back to stock firmware. Otherwise there is no option for that.
You can also use any ROM which required locked bootloader. But I don't guaranty you about stability and performance .
No. After relocking the bootloader you will not able to flash the custom ROMs. And also after relocking the bootloader, twrp recovery will also not work.
Custom ROMs, custom kernel, twrp recovery needs unlocked bootloader.
Dear Seniors.
I am facing great hardship because my phone is stuck at boot logo.
No booting in recovery mode to flash another rom.
I did unlock bootloader of it by using tuliptool with success. After that i flashed custom rom in it. after reboot it is happening that.
Please suggest to recover it.
Did you flash twrp after unlocking? Did you make backup of stock ROM? Perhaps find a version of the factory firmware and flash that.
Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.
modorate said:
Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.
Click to expand...
Click to collapse
I found software update notification but when i update an error accruing while update. (This update not compatible with this device"
In easy words......... my recovery.img has been corrupted. I have no idea to get rid of this situation.
I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.
bao_gg said:
I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.
Click to expand...
Click to collapse
Several people myself included have been able to use tuliptool to successfully unlock and root the device.
mine is hard bricked too. but I think it is worse than the case listed on the op.
if you want to hard bricked these are the steps:
follow the procedure to install the Spanish ROM 6.1, than another android m b12, than finally the android seven......use tulip tool and install twpr fine, root ect. amazing ROM.......buuuuut......I lost my IMEI somewhere in this process, and the original FTM which had a small menu changes to another static one, without the menu.
I needed this menu to open the com port to fix the IMEI. than I had the brilliant idea to re-flash android M via twrp (without modifying the zip file to remove the recovery, something I knew so well from the older axon mini).
results:
-lost twpr because the stock ROM wrote over it,
-cannot boot the OS because I flashed android m but the phone had the aboot 7.
-i now have a brick
I need a genious to sujest something to bring it back to life........sh....t...sh...t.....sh...t
any chances I could inject aboot7 via ADB through my dead recovery which somehow the phone recognises? ADB shell still seems to be working
thanks
Since all the roms are gone I was hoping to at least get Flyme nougat, which apparently flyme 8 is based on.
The problem is that flashing Flyme 7 or 8 china all result in a bootloop. The page says I should install 7 stable first, which I did. No difference. I do this with bootloader and recovery removed because I don't want to lose the unlocked bootloader. Does anyone have an idea what the problem is here? I was thinking maybe its me trying to keep the bootloader so I even tried to flash full stock but that didn't work either. I know how to reverse this but Im pretty much out of ideas at that point to get these images work.
did you replace bootloader file with unlocked_bootloader and recovery file with twrp_recovery? this will let you bootloader still unlocked and recovery still TWRP after you flash it.
short story i installed a custom rom. Everything was fine but i was forced to go to stock due to a problem. It looks like i flashed the wrong files i flashed system.img,ramdisk,ramdiskrecovery and kernel.img. I extracted these files from a update that had the same model of my phone but for some reason now my phone is bricked. i was flashing stock firmware but now there's no os installed nothing at all, im a total noob with flashing on huawei phones. I thought this was going to work but no.
My bootloader its unlocked. erecovery doesnt work. i can only access the bootloader mode but my device is not detected while using adb commands. stock recovery works but i only have the following options:''download latest version and recovery'', ''reboot'' and ''shutdown''. is there a solution for this?
Editk guys my problem was fixed.
Same problem
Hello. I have the same problem. How did you fix this.