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.
Related
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader
Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"
danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.
Okay will try that. Thanks man.
Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.
Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?
Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader
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!
Wanted to share this to get the ball rolling on this device
https: //www .asus .com /us/Phone/ZenFone-Max-Plus-M1/HelpDesk_Download/
just unlock,but no custom for this device
ill try porting twrp
mfbutan said:
just unlock,but no custom for this device
Click to expand...
Click to collapse
Magisk sytemless root. Unlock bootloader and it works flawless
someone said they got magisk to work,but doesn't it need a custom recovery?
Have you been able to get it to work?i just gave it a shot and it failed, multiple times.
what were you trying?
P2thaizarts said:
Have you been able to get it to work?i just gave it a shot and it failed, multiple times.
Click to expand...
Click to collapse
what were you trying?if you can please locate the boot.img location for our phone and I can try rooting and telling you how I did it.
Dandaivin said:
Magisk sytemless root. Unlock bootloader and it works flawless
someone said they got magisk to work,but doesn't it need a custom recovery?
Click to expand...
Click to collapse
I will try..Thanks
mfbutan said:
I will try..Thanks
Click to expand...
Click to collapse
How'd it go,I was unable to unlock bootloader,haven't tried root as I've heard flashing root with adb will make the phone not boot if bootloader is still locked.
Already try but no luck,i cant unlock..unknown error..
So sad..
same thing happening to me
mfbutan said:
Already try but no luck,i cant unlock..unknown error..
So sad..
Click to expand...
Click to collapse
same thing happenening to me and calling asus doesn't help because they say that the majority of peeopl aren't having this issue.
now it's the no pin error,however i think it worked.
mfbutan said:
Already try but no luck,i cant unlock..unknown error..
So sad..
Click to expand...
Click to collapse
I think Asus fixed their ****,so basically I was able to flash the patched_boot.img now.At first it gave me the network error but every time I always tried again,eventually it gave me the no pin error even thought I had a pin.I tried several times with that too and sometimes it would reboot but not wipe anything,until I took away my pin and it immediately gave the no pin error and I tried again and it rebooted without wiping anything.I contacted asus support over the phone and on zentalk and they told me it was already unlocked.I tried flashing the patched boot image and it went through.I booted into the phone with no problems indicating boot loader was unlocked I think.then surprisingly I checked root with root checker and it came back saying I did have root. I guess they updated the unlock boot loader tool to make it not wipe anything.
Dandaivin said:
I think Asus fixed their ****,so basically I was able to flash the patched_boot.img now.At first it gave me the network error but every time I always tried again,eventually it gave me the no pin error even thought I had a pin.I tried several times with that too and sometimes it would reboot but not wipe anything,until I took away my pin and it immediately gave the no pin error and I tried again and it rebooted without wiping anything.I contacted asus support over the phone and on zentalk and they told me it was already unlocked.I tried flashing the patched boot image and it went through.I booted into the phone with no problems indicating boot loader was unlocked I think.then surprisingly I checked root with root checker and it came back saying I did have root. I guess they updated the unlock boot loader tool to make it not wipe anything.
Click to expand...
Click to collapse
Please post your patched_boot.img if you successfully root our Max Plus sir.. thanks...
can't upload files on xda
Jongkits2011 said:
Please post your patched_boot.img if you successfully root our Max Plus sir.. thanks...
Click to expand...
Click to collapse
It's easy enough to do dowload the firmware from their website,install the magisk manager apk.extract the firmware zip and locate boot.img file.copy it either onto a sdcard or select file transfer on your phone and transfer to your phone.AFter doing so go back in to the magisk manager apk you installed select install->patch boot image file->locate the boot.img file you copied let it patch.After it patches make note where it saves,copy that "patched-boot.img" back to your computer(into the adb folder)and inside adb folder hold shift key+right click then open a comman prompt window.type adb devices.Make sure usb debugging is enable in developer options after pressing build number 7 times.make sure your device is found after hitting enter on adb devices.type adb reboot bootloader.after your phone reboot into fastboot mode(ther'll be a llittle word on the bottom left of your phone screen)main screen will be powered by android rest is black.now type fastboot devices to make sure your device is seen.and then type fasboot flash boot "patched-boot.img".Then you'll be rooted.Make sure you unlock bootloader with their tool first.
any news on how it went for you?
Until now i have no luck to unlock my max plus.. I already ask asus personel but until now its under investigation... Im still waiting.
Successfully root my device zenfone max plus thru magisk manager.
Repair imei!
Hello, does anyone know how to recover the imei of this device? was formatted by sp flash tool and now the imei disappeared does not recognize the chips of the operator and does not access the front camera and the option of front camera, opens the wide angle ... Does anyone have any solution for this?
mbsmatthew said:
Hello, does anyone know how to recover the imei of this device? was formatted by sp flash tool and now the imei disappeared does not recognize the chips of the operator and does not access the front camera and the option of front camera, opens the wide angle ... Does anyone have any solution for this?
Click to expand...
Click to collapse
Someone who managed to route the zenfone max plus m1, could I provide the files in the MDDB folder, so I can retrieve the device's image?
Bootloop
Dandaivin said:
It's easy enough to do dowload the firmware from their website,install the magisk manager apk.extract the firmware zip and locate boot.img file.copy it either onto a sdcard or select file transfer on your phone and transfer to your phone.AFter doing so go back in to the magisk manager apk you installed select install->patch boot image file->locate the boot.img file you copied let it patch.After it patches make note where it saves,copy that "patched-boot.img" back to your computer(into the adb folder)and inside adb folder hold shift key+right click then open a comman prompt window.type adb devices.Make sure usb debugging is enable in developer options after pressing build number 7 times.make sure your device is found after hitting enter on adb devices.type adb reboot bootloader.after your phone reboot into fastboot mode(ther'll be a llittle word on the bottom left of your phone screen)main screen will be powered by android rest is black.now type fastboot devices to make sure your device is seen.and then type fasboot flash boot "patched-boot.img".Then you'll be rooted.Make sure you unlock bootloader with their tool first.
Click to expand...
Click to collapse
I tried this, and now my phone has a bootloop...
I have no backup of the original boot.img.
Flashing the whole FW with SP Flashtool doesn´t work (Brom error), I tried all combinations with Vol. Up & Down...
Does anyone has an idea how to get my phone working again?
It came with FW Version WW-V14.02.1711.22 and a chinese Recovery, I wasn´t able to install updates from the beginning.
ADB is also not working, the device is shown as MTP, I have no connection via ADB.
The only thing which is working is fastboot.
Is there a solution to get it working again with fastboot? Can just flash an other boot.img?
Help
can you explain how you did it please, I have the same
Jongkits2011 said:
Successfully root my device zenfone max plus thru magisk manager.
Click to expand...
Click to collapse
Jongkits2011 said:
Please post your patched_boot.img if you successfully root our Max Plus sir.. thanks...
Click to expand...
Click to collapse
Can you please send me thE patched_booot.img you already used.?
Hi everyone!!
IMPORTANT:NEVER SELECT ERASE OR FORMAT PARTITIONS IN LGUP. IT WILL MESS WITH YOUR IMEI
Im making a new guide to unlock your bootloader/root your device. Its easier to do a little bit risker but if you do it slowly you wont mess up your phone and in the event you do you can always recover it. Remember to FOLLOW ALL THE STEPS or you may end up messing up your phone, The best thing is, you dont need to downgrade to even unlock the bootloader!!
DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR PHONE BRICKS! YOU ARE FOLLOWING THIS GUIDE AND ITS YOUR CHOICE TO DO IT OR NOT TO DO IT AND YOURE THE ONE DOING IT. I JUST WANT TO HELP OTHERS OUT.
If you cant for some reason access fastboot even flashing the v35 file, use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031 it says verizon but i think most of the models of the g7 cant acess fastboot so you can try this.
Requirments:
-A PC
-USB Cable to connect your phone of course
- V35 ABL
--The LG FIrehose file
- QPST/QFIL
-9008 drivers FOLLOW THIS GUIDE!! To install drivers properly IF WINDOWS DOESNT INSTALL THEM AUTOMATICALLY!!
-ADB PLATFORM or someway to access fastboot via cmd
-PATIENCE!!
Steps.
Download the V35 abl,LG Fire house file, download and install qppst and install the 9008 drivers (WUNDOWS 10 should automatically do it for you) If not, download it and install them.
Boot into edl mode via connecting your phone to the pc then turning it off. Hold Vo- and power and keep pushing the vol+ button multiple times when it turns off.
Go into device manager and check if its detected. to check open up device manager and check Ports and it should say Some port 9009 Qualcomm or something like that (IF theres a question mark, exclamation mark or it says qhusb bulk even after you install the drivers, make sure you disable driver signature enforcment on windows and install the drivers again. Theres multiple ways to do it just google on how to disable driver signature enforcment windows 10. Same with windows 7/8,)
Run as administrator qfil and select flat build,.
--Programmer Type: Load the firehose file
-- On the top go to configuration and where it says Device type, make sure you change it to ufs.
-- Click ok to save and exit
At this point qfil should be detecting your port . If not there should be a select port button next to it on top.
Go to Tools then Partition Manager
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
Search for abl_a and right click on it. First do Read Data, it should take only a couple of seconds Then Load Image and load the v35 image. It should say GPT Finished or something like that at the log with no errors.
Reboot holding volume - and power for like 20-30 seconds until the lg logo comes up Then hold the down button to boot into fastboot or it will automatically boot into fastboot depending on what version of android you are on.
Open the folder where your adb tools are, then hold shift +Right Click in the folder and open powershell. Type and enter CMD
Enter: Fastboot oem unlock it should output with OKAY, If it gives you unknown command, try a USB 2.0 port and then turn off your phone and while its booting up enter the command before you boot into fastboot. Once thats done dont close the window yet!!
Once thats done you can now restore your other abl so you can boot back into android. To do that run %appdata% in the search bar or in the run window by holding the windows button and pressing the R button. Then you should be in C:\Users\{YOUR USERNAME}\AppData\Roaming
Open up the Qualcomm folder --> QFIL --> COMPORT#
There should be a ReadData Blah blah.bin in there. Drag and drop that in the folder where your adb tools are
then go back to the window i told you not to close (The powershell/cmd window) then do fastboot flash abl_a (The file name with ReadData) without the ( ).
Now you can turn off the phone vial holding volume - and power and then reboot into android!! You should get a bootloader unlocked or a cannot be checked for courrption message! Congrats your bootloader is unlocked!!
To root: Just back up your boot image via and then find it in %Appdata% put it in your phone then use magisk manager to patch the boot file and then take that boot file and then flash it to boot_a via edl.
I tried my best to write this guide and sorry for my grammatical mistakes. Ill be helping people unlock/root their bootloaders for free during this covid time as well. If you want to donate you can always tell me but its not necessary.
Ill try making a video as soon as i can.
Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks ?
nyolai said:
Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks
Click to expand...
Click to collapse
Should be in theory
nyolai said:
Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks
Click to expand...
Click to collapse
Yes and no. Yes it will unlock the bootloader but the problem with verizon there is no fastboot unless you erase the laf imgs.
Which is why in my guide I use the crossflashed ULM11g it has fastboot and the oem unlock enable button which makes it easier to issue the "fastboot oem unlock" command.
Give it a try and if your not good at doing this with qfil will brick your device. If you run into issues try my guide.
https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031
netookska05 said:
Yes and no. Yes it will unlock the bootloader but the problem with verizon there is no fastboot unless you erase the laf imgs.
Which is why in my guide I use the crossflashed ULM11g it has fastboot and the oem unlock enable button which makes it easier to issue the "fastboot oem unlock" command.
Give it a try and if your not good at doing this with qfil will brick your device. If you run into issues try my guide.
https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031
Click to expand...
Click to collapse
Ill add your link to my thread.
Awesomeslayerg said:
Requirments:
-A PC
-USB Cable to connect your phone of course
- V35 ABL
-The LG FIrehose file
- QPST/QFIL
-9008 drivers
-ADB PLATFORM or someway to access fastboot via cmd
-PATIENCE!!
Click to expand...
Click to collapse
All the links to files redirect to "Unbrick G7" file.
I m stuck in this step
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
always got Shara failed error.
Has windows 10 and tried all possibilities.
The driver not detected automatically so installed manually. Please Help
TigerV said:
I m stuck in this step
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
always got Shara failed error.
Has windows 10 and tried all possibilities.
The driver not detected automatically so installed manually. Please Help
Click to expand...
Click to collapse
Do you have ELF File for the programmer> The one included in the zip file? Sorry i didnt include the ABL Ill update the zip soon Do you get an exclmation mark or something on the ports in devnice manager?
Awesomeslayerg said:
Do you have ELF File for the programmer> The one included in the zip file? Sorry i didnt include the ABL Ill update the zip soon Do you get an exclmation mark or something on the ports in devnice manager?
Click to expand...
Click to collapse
Thanks for your update.
Yes I m using the same ELF file from zip.
The driver not installed automatically so I have installed it manually via device manager and thn no exclamation mark. But somehow its not work. Tried many time but the same issue
Can you please update the link of 9008 driver and guide? Its not working (may be bad link)
TigerV said:
Can you please update the link of 9008 driver and guide? Its not working (may be bad link)
Click to expand...
Click to collapse
Fixed it. Make sure whenever you close qfil or everythime you get that error just reboot into edl mode again.
****.. Unlocked bootloader. Lost Widewine L1. Relocked bootloader again. but Widewine L3 is available. Anyway to get it back to L1. I remember My pixel and Op6 could get back Widewine L1 after relocking bootloader again.
Awesomeslayerg said:
Fixed it. Make sure whenever you close qfil or everythime you get that error just reboot into edl mode again.
Click to expand...
Click to collapse
Thanks somehow I manged for get edl and flashed the image.
Now getting another issue. when I do "Fastboot oem unlock" its say
FAILED (remote: unknown command)
finished. total time: 0.002s
tried will all method with different PC, Different USB and all as mentioned in the main post, but no luck.
TigerV said:
Thanks somehow I manged for get edl and flashed the image.
Now getting another issue. when I do "Fastboot oem unlock" its say
FAILED (remote: unknown command)
finished. total time: 0.002s
tried will all method with different PC, Different USB and all as mentioned in the main post, but no luck.
Click to expand...
Click to collapse
From ecperince just keep doing that. Nut before entering fastboot put the command in and press enter then reboot directly into fastboot. Kerp doing it unt you see the orsnge unlocked bootloader on your g7 screen
Hey op or whomever can help point me in the right direction: when looking at used/refurbished g7's which models should I ask sellers about or steer away from like the LMG710R (I know the LMG710TM is a no go, what about the Sprint unlocked for GSM and what's there code if I want to avoid them?)?
Thanks.
the v35abl file is not avaliable
wente said:
the v35abl file is not avaliable
Click to expand...
Click to collapse
here is the same link from main post (that link has some hyperlink issue)
https://androidfilehost.com/?fid=1899786940962574206
Would this work on LG710N (korean) ??
Once the bootloader is unlocked with this method DRM is lost forever. Even relocking the bootloader will not bring Widewine certification to L1. I am back to stock with locked bootloader. Widewine is at L3.
Awesomeslayerg said:
From ecperince just keep doing that. Nut before entering fastboot put the command in and press enter then reboot directly into fastboot. Kerp doing it unt you see the orsnge unlocked bootloader on your g7 screen
Click to expand...
Click to collapse
have tried many many time and all possible way but no luck
---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------
coolrevi said:
Once the bootloader is unlocked with this method DRM is lost forever. Even relocking the bootloader will not bring Widewine certification to L1. I am back to stock with locked bootloader. Widewine is at L3.
Click to expand...
Click to collapse
re-lock and stock flash also not in bring back to L1? I can not even unlock my boot-loader. stuck at "fastboot oem unlock" and its not working, tried all possible way