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.
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
Please forgive my stupidity - I'm a longtime Samsung Android user and this Fastboot/adb process is all new to me. Last time I used that was with Original TMOBILE Mototola G1!!
So, this is what I have: I had my device ( ZE551KL ) on LP, Bootloader unlocked with TWRP and rooted. 'Cause I first unlocked the Bootloader with the official ASUS app.
Then I installed the OTA ASUS MM version, but according to everyone, once one install the OTA upgrade, it relocks the Bootloader, correct? How can I test this??
This afternoon I put device in Fastboot mode and did a "fastboot boot twrp-3.0.4.img" and it worked!!!
It boot into TWRP and am busy making a backup now.
My Question: if my bootloader is still locked, how could I boot TWRP?
Can I try and 'Fastboot flash recovery twrp....' and will this work or am I going to brick the device?
Ideas? ( well, rather experienced advice, please)- as I would hate to brick my device.
The TWRP backup I am currently making - is that any good/helpful to anyone that can help us getting this device properly unlocked and rooted?
Thanks
I did try the official ASUS unlock tool on MM....
I forgot to mention that.
I did try the official unlock tool on MM, but the app just failed.
I opened an issue with ASUS regarding this, as their website specify version 1.16 'and later'
Does this mean I am good to flash TWRP??
Am I good to flash TWRP if I get this message??
You are good. I had unlocked the bootloader long time ago, and I have installed MM, they don't relock it back. It would be strange to do that, since once unlocked you lost the warranty... it would be like they will gave you back the warranty!
Dude, your bootloader is unlocked. You're good to go. Fastboot flash that recovery and go to town.
From your description it is clear that you have successfully unlocked your device. Once it is unlocked, you wont be able to lock it back. So there is no way to revert the process and it affects warranty. Now anytime you can flash TWRP with fastboot and install custom ROM. If you want to install Stock rom install stock recovery and use ADB sideload to install Stock ROM. if you have any other doubts visit my youtube channel [TheMobileShots] where i have provided the tutorial to do these things. Have a great day!
Guys please dont flame me i am having a pannic attack and cant think strait. i rooted and flashed twrp with moto g5 plus tool kit, then later used ex kernel, then got update ota notioce...i knew it wouldnt work but was suprised it downloaded and propt to restart..so i did thinking it would say no you cant.. instead stuck in twrp like there is no os! please help. I dont know how to reflash the stock os, my backup didnt work when i restored it, and besides that after trying to restore i ended up wipin g and formatu=ing data and looso=ing it now anyway. i am shaking help please
I have just tried to flash lineage zip and it said succesful but when rebooting it goes strait back to twrp, have i lost my boot img ? what can i possiblu do, i am concerned if i download the 1.6 gig stock rom file from g5 plus kits "factory rom kit" it wont be the propper rom for my region "australia" or wont even have a modem..what can i do.. god why dont i stillhave any xanax
when trying to flash stock rom with toolkit the log says bootloader slot suffix not found and bad key
So i finally drank enough scotch to calm down, and realized the "errors" were not actually preventing the stock rom from flashing... and i now have not only a working rom but a baseband..so my reccomendation goes out to anyone panicked to just flash the downloaded stock rom found in the links of the moto g5 plus toolkit
Never,take otas with custom recovery , the solution is flash whole rom
djzero86 said:
Never,take otas with custom recovery , the solution is flash whole rom
Click to expand...
Click to collapse
Yes.. I truly thought there would be a "wah wah wah" notice being rooted.. But it went straight in to it. Just didn't know where any stock rocks were and wasn't prepared.. And ended in a hyperventilating mess. At least I now have the files
Every day we learn something new, brick this phone is very difficult, all we need is the correct files and some of magic and come back to life ,?
Cheers..
Excuse my bad english...
djzero86 said:
Every day we learn something new, brick this phone is very difficult, all we need is the correct files and some of magic and come back to life ,?
Cheers..
Excuse my bad english...
Click to expand...
Click to collapse
true! My last phone I felt secure and that it was completely unbrickable all because I had all the necessary rescue files and backups. And I had learned from every previous disaster. Thank you for your kind words friend.
Can't get fastboot to recognize device
So I'm kind of in the same boat as you were. I unlocked the bootlader and rooted the phone before giving it to my wife. During that whole process, fastboot had no problems recognizing the phone (obviously). Then my wife tried to update via the OTA which got her stuck in TWRP. I'd like to reflash the stock ROM, but the problem I have is that TWRP won't just flash the zip file ("invalid zip file format"), and I can't use fastboot to do commands line by line since "fastboot devices" doesn't show my phone anymore. I was able to get her going on a custom ROM for now, but I'd like to put her back on the stock ROM so we won't encounter this problem again. I've reinstalled the Motorola driver several times, but no luck. ADB has no problems recognizing the phone when in TWRP recovery. One thing that happened recently was a big update to Windows 10, but I'm not sure if that is the reason for my fastboot issues.
Any advice would be appreciated.
Just a follow up, I tried uninstalling/reinstalling the Motorola driver and ADB on the original computer, but for some reason it still won't "see" the phone in fastboot. I was able to install ADB/Fastboot and the Motorola driver on a separate computer (also Windows 10) to get fastboot to recognize the phone so I could issue commands to reinstall the stock firmware. I noticed, though, that the following commands FAILED when I entered them:
fastboot erase customize
fastboot erase clogo
I'm not sure what those were for, but the phone seems to be working fine on the stock firmware now.
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
Hi
I got my self in quite a pickle here..
so advice or help is very welcomed.
I own a Huawei P10 lite,
with a software version WAS-LX1AC900B049
First off I unlocked the phone, then flashed TWRP recovery, and thus far everything was ok
I wanted to install Lineage 14.1 OS, and I failed because my version of the phone is not supported..
but during attempt installation of Lineage OS , I deleted data, system, dalvik, and cashe..
I did not make a backup!!! (major mistake, I know..)
so effectively I deleted my OS :-/ ..
but it isn’t over jet..
because I could not find a stock rom, namely WAS-LX1AC900B049 version
I thought of debranding my phone to Orange, namely WAS-LX1AC109B110 because stock roms for Orange are available on the net.
so.. using TWRP I replaced oeminfo file..
(this time making a backup of oeminfo)
but once I downloaded Orange stock rom, put it on the
sdcard in /dload folder and entered download mode on the phone, nothing happened, update failed
but.. also changing oeminfo resets the system so I guess that turned off USB debugging..
so now the TWRP is not available because of the system reset, and in the fastboot and rescue mode , adb program from Windows, does not detect device..
so..
it seems I have 3 options..
1. somehow install Orange stock rom
2. make fastboot and rescue mode to work properly so I can reinstall TWRP and go further from there
3. find original stock rom WAS-LX1AC900B049, may be it will work
by the way erecovery does not work, it conects to the wifi, starts serching, and then fails
Help please..
I unbricked the phone
for anyone interested I used adb to unlock the phone in fastboot and rescue mode..
the phone was showing me a message that it was unlocked but it was not
once unlocked previously installed TWRP booted immediately, so from there I installed Lineage 14.1 by HassanMirza01 and it works great
Happy that you fixed your problem but how did adb detected your device as you mentioned it didn't at the first place?
Planning on going back to stock and I think the same trouble would happen for me too.
oH MY GOD!
ultragorki said:
Hi
I got my self in quite a pickle here..
so advice or help is very welcomed.
I own a Huawei P10 lite,
with a software version WAS-LX1AC900B049
First off I unlocked the phone, then flashed TWRP recovery, and thus far everything was ok
I wanted to install Lineage 14.1 OS, and I failed because my version of the phone is not supported..
but during attempt installation of Lineage OS , I deleted data, system, dalvik, and cashe..
I did not make a backup!!! (major mistake, I know..)
so effectively I deleted my OS :-/ ..
but it isn’t over jet..
because I could not find a stock rom, namely WAS-LX1AC900B049 version
I thought of debranding my phone to Orange, namely WAS-LX1AC109B110 because stock roms for Orange are available on the net.
so.. using TWRP I replaced oeminfo file..
(this time making a backup of oeminfo)
but once I downloaded Orange stock rom, put it on the
sdcard in /dload folder and entered download mode on the phone, nothing happened, update failed
but.. also changing oeminfo resets the system so I guess that turned off USB debugging..
so now the TWRP is not available because of the system reset, and in the fastboot and rescue mode , adb program from Windows, does not detect device..
so..
it seems I have 3 options..
1. somehow install Orange stock rom
2. make fastboot and rescue mode to work properly so I can reinstall TWRP and go further from there
3. find original stock rom WAS-LX1AC900B049, may be it will work
by the way erecovery does not work, it conects to the wifi, starts serching, and then fails
Help please..
Click to expand...
Click to collapse
YOU DID AS EXACTELLY AS ME ...HAHAHAHAHAHAHAH and now im still tryiong to find it solutution ...have you found some?