Related
Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
LE: I should probably mention my bootloader is unlocked
n1c00_ said:
Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
Click to expand...
Click to collapse
can i use with stock recovery?
thanks.
vbnoob said:
can i use with stock recovery?
thanks.
Click to expand...
Click to collapse
Hi. It's a fastboot command that you run in bootloader mode. And actually the original script runs an OEM unlock command which bypasses your stock recovery.
So it probably doesn't work with stock recovery.
I'm actually on an unlocked bootloader, added that to the OP
ta
n1c00_ said:
Hi. It's a fastboot command that you run in bootloader mode. And actually the original script runs an OEM unlock command which bypasses your stock recovery.
So it probably doesn't work with stock recovery.
I'm actually on an unlocked bootloader, added that to the OP
ta
Click to expand...
Click to collapse
My phone is unlocked bootloader with stock recovery.
Thanks.
vbnoob said:
My phone is unlocked bootloader with stock recovery.
Thanks.
Click to expand...
Click to collapse
Here's what I'd do if I were you
1. I would try it as stated in the OP at first
2. ...if that doesn't work: 'mfastboot oem unlock' (as per original script) followed by 'mfastboot boot *.img'
3. If it still doesn't work I would instal philz recovery - see http://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905 - it does work, mind the ripples
...and if it still doesn't work... Oh well...
n1c00_ said:
Here's what I'd do if I were you
1. I would try it as stated in the OP at first
2. ...if that doesn't work: 'mfastboot oem unlock' (as per original script) followed by 'mfastboot boot *.img'
3. If it still doesn't work I would instal philz recovery - see http://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905 - it does work, mind the ripples
...and if it still doesn't work... Oh well...
Click to expand...
Click to collapse
I am attaching the files that served to me with this I got root in Moto G 2013 5.0.2 Retail Beazil.
I have the stock recovery.
I climb into three parts that weighs 11 megs, Just extract it and put the phone mode fastboot and execute the bat file root-windows.
enjoy it
Then tell me as if I served them.
I think I screwed phone. Being a noob I didn't realise fastboot and Bootloader screens are different. I went and use chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions link
in fastboot. After error failed now it ADB doesn't detect my phone.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>
Any advise to help me? Tried hard method going to bootload still nothing either or at least I think its nothing since this is first attempt I ever tried root my phone. Everytime I plugin in fastboot or even in normal mode the pc does detect it. But it just won't show up in adb.
Decided to try again using leocuervo1983 method for fastboot it stated as fail as well but somehow I got root even though adb still no longer detect my phone.
Edit:
Just found out fastboot doesn't use adb commands or do they? I feel stupid. I Guess there are no issues then even if failed still got root. Fastboot commands works adb doesn't work.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
TAXXXXXXXX fastboot
The easiest method would be to flash the latest version of philz recovery, boot into the recovery and then just reboot from the recovery. You will be asked to disable recovery flash and then install su binaries. Just choose yes for both the options and download and super user app you like (I personally use superSU).
PS: I have tested this method and it works.
pfufle said:
The easiest method would be to flash the latest version of philz recovery, boot into the recovery and then just reboot from the recovery. You will be asked to disable recovery flash and then install su binaries. Just choose yes for both the options and download and super user app you like (I personally use superSU).
PS: I have tested this method and it works.
Click to expand...
Click to collapse
Screen flicker issue is there if i install this on stock asia retail 5.0.2 with unlocked bootloader on stock recovery?
Xicor Yagami said:
Screen flicker issue is there if i install this on stock asia retail 5.0.2 with unlocked bootloader on stock recovery?
Click to expand...
Click to collapse
Yes since the recovery isn't entirely compatible with the new kernel.
pfufle said:
Yes since the recovery isn't entirely compatible with the new kernel.
Click to expand...
Click to collapse
Tried latest TWRP? same results?
Xicor Yagami said:
Tried latest TWRP? same results?
Click to expand...
Click to collapse
yep.
n1c00_ said:
Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
LE: I should probably mention my bootloader is unlocked
Click to expand...
Click to collapse
Thanks a lot! Worked like a charm using mfastboot command.
Works fine
My bootloader was however unlocked...I tried this on CM12....extract the img file from the CF-Auto root File and then flash on the bootloader mode...with mfastboot boot filename.img
The method same as that of kitkat works for lollipop too...you could made some mistake unknowingly somewhere in the middle while following the original procedure
Sent from my Moto G using XDA Free mobile app
is there any method to root moto g?
Any side effects of chainfire method?
leocuervo1983 said:
I am attaching the files that served to me with this I got root in Moto G 2013 5.0.2 Retail Beazil.
I have the stock recovery.
I climb into three parts that weighs 11 megs, Just extract it and put the phone mode fastboot and execute the bat file root-windows.
enjoy it
Then tell me as if I served them.
Click to expand...
Click to collapse
It did'n work for me .... I ran the bat file , and when I pressed a key, it was waiting for the phone and nothing happened.
Edited:
Sorry... I forgot to unlock bootloader first.... worked fine!!! Thanks a lot!!!
after using command fast boot flash recovery boot.img my phn got stuck in blue light...command prompt shows' waiting for device'..how long it will take to flash twrp or am i got stuck!!!pls help me
XDA Visitor said:
after using command fast boot flash recovery boot.img my phn got stuck in blue light...command prompt shows' waiting for device'..how long it will take to flash twrp or am i got stuck!!!pls help me
Click to expand...
Click to collapse
Hello, and welcome to XDA!
Does not sound like anything ill was done, as it did not connect. This could be a cause of one of three things:
Phone is not in the bootloader
Even if in the bootloader, fastboot mode is not activated
PC drivers for fastboot may not be appropriate (or maybe even an outdated fastboot program)
To help you further, can I get the make, model and carrier (if bought through said carrier) of your phone?
Many thanks.
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:
Do you have the Verizon model?
samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03
spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.
The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?
I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?
What if fastboot boot twrpname.img
It's really weird anyway...
enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...
if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.
I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!
Honor 4c chm u-01 b120
locked bootloader
rooted with king root.
Phone still booting but no notwork service. NO SERVICE
Local update file found but cant flash update.app phone only restart.
recovery not comes up.
IMEI null
sorry bad english.
BinMgen said:
Honor 4c chm u-01 b120
locked bootloader
rooted with king root.
Phone still booting but no notwork service.
Local update file found but cant flash update.app phone only reboot.
recovery not working.
IMEI null
sorry bad english.
Click to expand...
Click to collapse
Hi You have made a big mistake by using KingRoot to root your device.
now you have got some serious issues but they can be solved.
First You need to make full wipe of your device currently and need to flash stock firmware.
1.Back up all your important data.
2.wipe current os by formatting.
3.Install the stock ROM version which you got initially.
4.you will get your IMEI number back.
if you are not clear about above or if the above proceess doesnt help help I will suggest another method.
miststudent2011 said:
Hi You have made a big mistake by using KingRoot to root your device.
now you have got some serious issues but they can be solved.
First You need to make full wipe of your device currently and need to flash stock firmware.
1.Back up all your important data.
2.wipe current os by formatting.
3.Install the stock ROM version which you got initially.
4.you will get your IMEI number back.
if you are not clear about above or if the above proceess doesnt help help I will suggest another method.
Click to expand...
Click to collapse
Thanks for your reply!
1 phone cant wipe current os by formatting, be cause recovery menu not comes up.
2 installing stock rom via local update not working phone restating only.
BinMgen said:
Thanks for your reply!
1 phone cant wipe current os by formatting, be cause recovery menu not comes up.
2 installing stock rom via local update not working phone restating only.
Click to expand...
Click to collapse
okay
First go to this link (https://forum.xda-developers.com/honor-4c/how-to/huawei-honor-4c-index-troubleshooting-t3293110) and install ADB / Fastboot and Necessary Drivers and unlock your bootloader(your warranty is void) and check whether your phones being detected by ADB Fastboot
After unlocking I will suggest you next step as per the result you get.
Hi bud .
I hope i can help u with this.kindly follow the instructions properly and u are good to go.
1) install proper usb drivers.
2) open command prompt
3)enable fastboot mode in ur device and connect it pc
4)type this command there.
If u are using mfastboot , then type
mfastboot.exe devices
If u are using fastboot
type
fastboot.devices
5) here ur device will be showed with some numbers. So now put twrp or any other recovery in fastboot folder or the location where u are accessing the fastboot from. Be sure u re named recovery to recovery.img
6)type these command after copying ur twrp to that folder
mfastboot.exe flash recovery recovery.img
mfastboot.exe boot recovery.img
7) Now ur phone will automatically boot to recovery , here u can wipe data.
The bootloop is just because the data partition is still unwiped and no rom will boot . Just format data after booting the recovery .
Thank me if i helped you
--regards--
miststudent2011 said:
okay
First go to this link (https://forum.xda-developers.com/honor-4c/how-to/huawei-honor-4c-index-troubleshooting-t3293110) and install ADB / Fastboot and Necessary Drivers and unlock your bootloader(your warranty is void) and check whether your phones being detected by ADB Fastboot
After unlocking I will suggest you next step as per the result you get.
Click to expand...
Click to collapse
I have try many times but still i get this msg "Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID."is this site working ?.
gopinaidu77 said:
Hi bud .
I hope i can help u with this.kindly follow the instructions properly and u are good to go.
1) install proper usb drivers.
2) open command prompt
3)enable fastboot mode in ur device and connect it pc
4)type this command there.
If u are using mfastboot , then type
mfastboot.exe devices
If u are using fastboot
type
fastboot.devices
5) here ur device will be showed with some numbers. So now put twrp or any other recovery in fastboot folder or the location where u are accessing the fastboot from. Be sure u re named recovery to recovery.img
6)type these command after copying ur twrp to that folder
mfastboot.exe flash recovery recovery.img
mfastboot.exe boot recovery.img
7) Now ur phone will automatically boot to recovery , here u can wipe data.
The bootloop is just because the data partition is still unwiped and no rom will boot . Just format data after booting the recovery .
Thank me if i helped you
--regards--
Click to expand...
Click to collapse
Hi! im working with you but i think something wrong with me, when i put this command "fastboot.devices" the answer is fastboot.devices is not recognized as an internal or external command,operable program or batch file
plz hep where is my problem?
BinMgen said:
Hi! im working with you but i think something wrong with me, when i put this command "fastboot.devices" the answer is fastboot.devices is not recognized as an internal or external command,operable program or batch file
plz hep where is my problem?
Click to expand...
Click to collapse
Hi the command is "adb devices" not "fastboot.devices"
If you are fine with above author help you can proceed if not here is the detailed guide.
Firstly go to this link and download the stock ROM for your device.(the version previous than your current rom)
http://www.carbontesla.com/firmware...-ota-collection/huawei-honor-4c-firmware-ota/
Extract the zip and later extract update.app by using this tool
https://forum.xda-developers.com/showthread.php?t=2433454
Now copy all the files namely recover.img,boot.img,system.img,cust.img into adb folder.
Now go to this link and unlock your bootloader
https://forum.xda-developers.com/honor-4c/how-to/huawei-honor-4c-index-troubleshooting-t3293110
After unlocking now do the following procedure.
1.Enable developer's options in your device.
2.move to adb folder and right click and click on open command prompt here.
3.Now type this command "adb devices" -Displays some id of your device which makes sure your device is connected.(accept prompt on device)
4.type this command " ADB reboot bootloader " or manually boot into fastboot by shutting down your phone and restart by pressing Power+ vol+ buttons.
5.Now you are in fastboot menu.If not try again.
6.now type the following commands
7. "adb devices" -Displays some id of your device which makes sure your device is connected.
8. "fastboot flash recovery recovery.img" - Flashes stock recovery
9. "fastboot flash system system.img" - Replaces your custom rom with stock rom
10. "fastboot flash boot boot.img" - Flashes boot partition which is need to boot stock rom.
11. "fastboot flash cust cust.img"
Now wait for some time and your device will boot into system and your IMEI number is back.
Note:If in steps 8-11 if you can't get success use mfastboot instead of fastboot.
miststudent2011 said:
Hi the command is "adb devices" not "fastboot.devices"
Click to expand...
Click to collapse
faatboot devices is a command too. But he typed it as fastboot.devices
gopinaidu77 said:
Hi bud .
I hope i can help u with this.kindly follow the instructions properly and u are good to go.
1) install proper usb drivers.
2) open command prompt
3)enable fastboot mode in ur device and connect it pc
4)type this command there.
If u are using mfastboot , then type
mfastboot.exe devices
If u are using fastboot
type
fastboot.devices
5) here ur device will be showed with some numbers. So now put twrp or any other recovery in fastboot folder or the location where u are accessing the fastboot from. Be sure u re named recovery to recovery.img
6)type these command after copying ur twrp to that folder
mfastboot.exe flash recovery recovery.img
mfastboot.exe boot recovery.img
7) Now ur phone will automatically boot to recovery , here u can wipe data.
The bootloop is just because the data partition is still unwiped and no rom will boot . Just format data after booting the recovery .
Thank me if i helped you
--regards--
Click to expand...
Click to collapse
Update!
- Now when i put this comand "mfastboot.exe devices" device shown with some numbers.
- When itype "mfastboot.exe flash recovery recovery.img" the answer Failed partition no support flash
plz help!
BinMgen said:
Update!
- Now when i put this comand "mfastboot.exe devices" device shown with some numbers.
- When itype "mfastboot.exe flash recovery recovery.img" the answer Failed partition no support flash
plz help!
Click to expand...
Click to collapse
try my method above
miststudent2011 said:
try my method above
Click to expand...
Click to collapse
The problem of your method unlocking bootloader, i got this msg Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID. when i submit my detail every time i do know what error
BinMgen said:
The problem of your method unlocking bootloader, i got this msg Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID. when i submit my detail every time i do know what error
Click to expand...
Click to collapse
For once in a while KingRoot helped you go to this page
http://huaweip8lite.blogspot.com/2016/03/bootloader-huawei-p8-lite-14-huawei.html?m=1
and follow the guide from step 2
you will get the boot loader unlock code.
or else PM me your details of your device
BinMgen said:
Update!
- Now when i put this comand "mfastboot.exe devices" device shown with some numbers.
- When itype "mfastboot.exe flash recovery recovery.img" the answer Failed partition no support flash
plz help!
Click to expand...
Click to collapse
Ur bootloader is still locked
gopinaidu77 said:
Ur bootloader is still locked
Click to expand...
Click to collapse
Yes!
BinMgen said:
Yes!
Click to expand...
Click to collapse
U need to unlock bootloader inorder to run above command
gopinaidu77 said:
U need to unlock bootloader inorder to run above command
Click to expand...
Click to collapse
I have try many times to submit my detail but every time i got this msg Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID. i don know the error
BinMgen said:
I have try many times to submit my detail but every time i got this msg Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID. i don know the error
Click to expand...
Click to collapse
If u specify a wrong device model ,it will show that error
gopinaidu77 said:
If u specify a wrong device model ,it will show that error
Click to expand...
Click to collapse
It seems Huawei has messed up with their website even though we enter correct details it is showing error.
They really need to solve the problem or else many would be lost.
miststudent2011 said:
It seems Huawei has messed up with their website even though we enter correct details it is showing error.
They really need to solve the problem or else many would be lost.
Click to expand...
Click to collapse
Have u contacted their support?
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
Give the all required information like Brand, model number in your post first.
Huawei honor 5x kiwi L24, I can't really acces the phone so finding some information is impossible. My main issue is when I boot it's failing to verify the Boot.img , recovery.img and system.img . I don't exactly know what all information I can give you
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
-Hope- said:
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
Click to expand...
Click to collapse
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Nixonkai417 said:
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Click to expand...
Click to collapse
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
-Hope- said:
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
Click to expand...
Click to collapse
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Nixonkai417 said:
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Click to expand...
Click to collapse
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
-Hope- said:
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
Click to expand...
Click to collapse
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Nixonkai417 said:
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Click to expand...
Click to collapse
As long as the bootloader says 'phone is unlocked' then its ok
-Hope- said:
As long as the bootloader says 'phone is unlocked' then its ok
Click to expand...
Click to collapse
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Nixonkai417 said:
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Click to expand...
Click to collapse
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
-Hope- said:
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
Click to expand...
Click to collapse
(REMOTE: command not allowed)
I have already sent an email to Huawei support, just waiting on a response to see if they can give me another unlock code. If I'm unable to unlock the boot loader again with the codes, what's my options for unlocling the boot loader without Huawei's help.