Database Info

[Q] Bricked one

os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?

brooklynchildxbc said:
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
Click to expand...
Click to collapse
Push a custom rom via adb and flash in recovery or flash stock images via fastboot

acuicultor said:
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
Click to expand...
Click to collapse
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.

brooklynchildxbc said:
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
Click to expand...
Click to collapse
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?

boober78 said:
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
Click to expand...
Click to collapse
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back

brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
No problem. I'm glad I could help
Sent from my One using Tapatalk

brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
Don't give up.... I was in the same position like you for a couple days....and now is fix by my self..... If you unlock your bootloader try to lock back (fastboot oem lock) now try to flash via fastboot Philz Recovery ( try until is rebooting himself into recovery) .... After that put on a memory stick the new system .... You may need to mount the USB flash drive ..... That's exactly what I have done....Good Luck ...

It is damn near IMPOSSIBLE to actualy, truly "brick" these devices. There are way too many safeguards in place.
Be careful before announcing that you are "bricked". Bootlooping (which is what your device was doing) is not "bricked". As long as you have fastboot, you can always reflash recovery, and then use recovery to reflash your custom ROM (or you can bypass all of that and reflash the factory images from fastboot).
Don't panic, you know more than you think you know. Just don't get freaked out, and read. You'll be fine.

Can't boot into recovery. any idea if this can be fixed?

I tried to root my Opo, but it started to go wrong after i flashed it. It went to reboot into TWRP, but all that happened was it crashed. the 1+ logo comes on and then the screen goes blank. This Happens all the time when I try a "fastboot oem unlock", factory reset, or a boot recovery.. the fastboot does work, but the device is also locked and i can't do a recovery due to this. I tried to do the root tutorial on youtube by C4ETech.. help please!

@nickizm, when you boot to fastboot and enter the command "fastboot devices", can you see your device listed on the screen?

Thanks for the reply.. The fastboot work fines apart from when I try to unlock the devices and it reboots into recovery, it crashes and doesn't unlock.. the rest of the phone works fine apart from the recovery... my bootloader is also locked and I can't unlock it due to crashing
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screem enabled: false

I can't be certain but I'm pretty sure I read a similar issue to this a few days ago that was caused by not having the latest fastboot software, the user resolved it by downloading the latest android sdk and trying again.
Worth a shot.
Hope it helps.
Powered by Bacon

I had trouble when I first tried to root. Twrp wouldn't install. I ran some command which loaded it up but didn't install it on the phone, I was the able to root my phone.
Make sure you have latest oneplus one drivers. Have you tried using oneplus one toolkit to install recovery?
Sent from my Oneplus One using XDA Free mobile app.

I've tried to install a recovery, but my device is locked. If i do a "fastboot oem unlock" is just crashes on me when it going into recovery. I also get the same crash when I do a factory data reset or if I reboot into recovery. I think it's definitely something to do with the recovery, but since my device is locked i'm not sure what to do?... cheers again

nickizm said:
I've tried to install a recovery, but my device is locked. If i do a "fastboot oem unlock" is just crashes on me when it going into recovery. I also get the same crash when I do a factory data reset or if I reboot into recovery. I think it's definitely something to do with the recovery, but since my device is locked i'm not sure what to do?... cheers again
Click to expand...
Click to collapse
Did you try with the latest android sdk?
Powered by Bacon

I'm sure I did.. It wasn't that old.. I can try again, but the problem is I won't be able to unlock my phone??
is this the right link? http://developer.android.com/sdk/installing/index.html?pkg=studio

New drivers, exactly the same

Have you tried using a toolkit to do the unlock for you? People usually advise against using toolkits to do it for you as it prevents you gaining the experience of doing it yourself, but since it's not working when doing it yourself I don't see any harm in trying a toolkit.
You can find several options at the bottom of @timmaaa's resources roll-up thread here

Rkr87 said:
Have you tried using a toolkit to do the unlock for you? People usually advise against using toolkits to do it for you as it prevents you gaining the experience of doing it yourself, but since it's not working when doing it yourself I don't see any harm in trying a toolkit.
You can find several options at the bottom of @timmaaa's resources roll-up thread here
Click to expand...
Click to collapse
Yea i have also tried the tool kit V2
My problem is that the recovery is damaged in some way and my device is locked. i can't "fastboot oem unlock" as it just crashes when it goes to reboot.. is there a way to unlock my device with another method or can the recovery be repaired some how? i'm such noob

patstar5 said:
I had trouble when I first tried to root. Twrp wouldn't install. I ran some command which loaded it up but didn't install it on the phone, I was the able to root my phone.
Make sure you have latest oneplus one drivers. Have you tried using oneplus one toolkit to install recovery?
Sent from my Oneplus One using XDA Free mobile app.
Click to expand...
Click to collapse
Ye i tried that as well.. can't unlock the device as it just crashes when it goes to reboot into recovery

I think you might be out of luck, unless someone here more knowledgeable than I can help.
If you have a recovery image (not zip) you can try running the following command (make sure the img file is in the same directory as your adb/fastboot files and rename it "recovery");
Code:
fastboot boot recovery.img
What this allows you to do is boot into the TWRP recovery without having it installed on your phone, but I think I read somewhere that this command no longer works.
EDIT: If the above command will let you boot into TWRP, you'll want to read the guide here and flash the script.

Rkr87 said:
I think you might be out of luck, unless someone here more knowledgeable than I can help.
If you have a recovery image (not zip) you can try running the following command (make sure the img file is in the same directory as your adb/fastboot files and rename it "recovery");
Code:
fastboot boot recovery.img
What this allows you to do is boot into the TWRP recovery without having it installed on your phone, but I think I read somewhere that this command no longer works.
EDIT: If the above command will let you boot into TWRP, you'll want to read the guide here and flash the script.
Click to expand...
Click to collapse
I've tried that as well, but as my device is locked it won't allow it.. I'm stuck in limbo for now unless there is a way to unlock my device or repair the recovery? thanks for trying anyways

nickizm said:
I've tried that as well, but as my device is locked it won't allow it.. I'm stuck in limbo for now unless there is a way to unlock my device or repair the recovery? thanks for trying anyways
Click to expand...
Click to collapse
One last effort, after a bit of reading I've seen a few people with your issue have resolved it by flashing ColorOS (Chinese Stock ROM) and then going back to a custom rom once everything is fixed.
You can find a guide on how to do this here

Rkr87 said:
One last effort, after a bit of reading I've seen a few people with your issue have resolved it by flashing ColorOS (Chinese Stock ROM) and then going back to a custom rom once everything is fixed.
You can find a guide on how to do this here
Click to expand...
Click to collapse
Cheers mate! I just had a quick flick through it and it looks promising? the only problem seems to be with drivers in windows 7 which i am also using.. I'll see if I can do it via linux or i'll have to install xp on my old laptop or something.. I'll save this for tomorrow tho as it's late and will let you know how I get on with it. thanks for the help

nickizm said:
Cheers mate! I just had a quick flick through it and it looks promising? the only problem seems to be with drivers in windows 7 which i am also using.. I'll see if I can do it via linux or i'll have to install xp on my old laptop or something.. I'll save this for tomorrow tho as it's late and will let you know how I get on with it. thanks for the help
Click to expand...
Click to collapse
No worries! Let me know how it goes good luck!

Rkr87 said:
No worries! Let me know how it goes good luck!
Click to expand...
Click to collapse
Definitely! cheers again

nickizm said:
I tried to root my Opo, but it started to go wrong after i flashed it. It went to reboot into TWRP, but all that happened was it crashed. the 1+ logo comes on and then the screen goes blank. This Happens all the time when I try a "fastboot oem unlock", factory reset, or a boot recovery.. the fastboot does work, but the device is also locked and i can't do a recovery due to this. I tried to do the root tutorial on youtube by C4ETech.. help please!
Click to expand...
Click to collapse
can you give a little detail about
"device is also locked and i can't do a recovery due to this"
you did fastboot oem unlock. so saved data is wiped. but you should be able to boot into android system,
if so, enable "developer options" by clicking "settings" --> "about phone" --> "Build Number" click it 7 times,
then go into settings developer options and enable USB debugging.
then, use not fastboot, but adb to boot into recovery.
adb reboot recovery
Click to expand...
Click to collapse
there you can got into recovery.

Gh05tShie1d said:
can you give a little detail about
"device is also locked and i can't do a recovery due to this"
you did fastboot oem unlock. so saved data is wiped. but you should be able to boot into android system,
if so, enable "developer options" by clicking "settings" --> "about phone" --> "Build Number" click it 7 times,
then go into settings developer options and enable USB debugging.
then, use not fastboot, but adb to boot into recovery.
there you can got into recovery.
Click to expand...
Click to collapse
That doesn't work as my device crashes when it goes into recovery..
eg: "fastboot oem unlock", factory reset, or a boot recovery all crash as my recovery isn't working. When my device goes to reboot in recovery the 1+ logo comes up, fades out to like a blueish from the white 1+ logo and crashes.. so basically it's looked and I can't get into recovery.. thanks for trying

Soft bricked shield tablet PLEASE HELP!

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

Trying to flash TRWP Moto Z recovery - not working

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!

ASUS Zenfone Max Plus M1 ZB570TL Bootloader Unlock Tool out now!!

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.?