Related
Hi all, I'm new here (great place, very informative) and pretty new to the Android scene in general.
As the title said, My AT&T S4 won't boot to recovery after I flashed 4.3 JWR663. Worked fine before and 4.3 is working great, but I can't get to TWRP. When I hold "power + volume up" I get the blue text dialog indicating its going to boot to recovery and the phone just shuts off. I can boot to download mode, but haven't done anything out of fear. I'm not rooted (which is what I'd like to do once this is fixed).
Should I try and re-flash TWRP? Any other suggestions? Feel free to break it down like you're talking to a child. Thanks in advance.
Try flashing it. Get goomanager from the play store. Open it and hit the menu button. Hit install openrecoveryscript.
Sent from my SGH-I337 using xda premium
graydiggy said:
Try flashing it. Get goomanager from the play store. Open it and hit the menu button. Hit install openrecoveryscript.
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
Will that work without root?
Vikingod said:
Will that work without root?
Click to expand...
Click to collapse
You'll need root to flash a recovery with GooManager.
How did you install 4.3? I assume that it's a custom 4.3 as I don't think it has been officially released yet. If it's custom, I'd assume that the ROM had been rooted as well...
theSpam said:
You'll need root to flash a recovery with GooManager.
How did you install 4.3? I assume that it's a custom 4.3 as I don't think it has been officially released yet. If it's custom, I'd assume that the ROM had been rooted as well...
Click to expand...
Click to collapse
I was rooted, but the ROM had it removed and I need to flash Chainfire to get it back. But I can't get into recovery to do so. I think the ROM was done by Jah0n
Is it safe to flash TWRP with Odin now? If so, could you point me to the directions to help me do so. Thanks again for the help.
Found a fix!
My recovery is fine. All I did was power down, try to boot into recovery with "power + volume up + home" and just when the phone vibrated to boot into recovery, I let go of the power button but continued holding the other buttons. It booted into TWRP just fine.
Vikingod said:
Found a fix!
My recovery is fine. All I did was power down, try to boot into recovery with "power + volume up + home" and just when the phone vibrated to boot into recovery, I let go of the power button but continued holding the other buttons. It booted into TWRP just fine.
Click to expand...
Click to collapse
Yep, that's the way you're supposed to get into recovery.
I an able to get in with only power+vol up. Both work for me.
Sent from my SGH-I337 using xda premium
Vikingod said:
Hi all, I'm new here (great place, very informative) and pretty new to the Android scene in general.
As the title said, My AT&T S4 won't boot to recovery after I flashed 4.3 JWR663. Worked fine before and 4.3 is working great, but I can't get to TWRP. When I hold "power + volume up" I get the blue text dialog indicating its going to boot to recovery and the phone just shuts off. I can boot to download mode, but haven't done anything out of fear. I'm not rooted (which is what I'd like to do once this is fixed).
Should I try and re-flash TWRP? Any other suggestions? Feel free to break it down like you're talking to a child. Thanks in advance.
Click to expand...
Click to collapse
Did you try manually booting into recovery with the power and volume button?
quattros said:
Did you try manually booting into recovery with the power and volume button?
Click to expand...
Click to collapse
He fixed his problem a few posts ago...
Sent from my SGH-I337 using xda premium
I have an older phone and after flashing the twrp recovery it won't let me boot into recovery mode at all can someone please give some advice on how I should fix this?
Which phone do you have?
An Alcatel One touch POP D3 4037A
Try using the Alcatel mobile tool to flash back to stock.
TWRP doesn't work
My LG G3 running lineage os 14.1 won't boot into TWRP.
graydiggy said:
He fixed his problem a few posts ago...
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
The blue and black screen start up screen comes up. But it stays like this. This happened since I flashed the lineage ROM. What should I do?
my phone agua rio 4.4.2 kitkat .
After flashing twrp recovery img .
After rebooting it .twrp not installed and it only reboot normal i didnt get to twrp recovery
Need solution pls pls
This thread is about the Samsung Galaxy s4.
Hi there. I'm new of this forum and even of the Android customization scenario. I have a Samsung Galaxy s4 i-9505 with 5.0.1 firmware and build LRX22C.I9505XXUHPK2. I've tried to install TWRP with Odin3 (so without root my phone) and all the procedure goes well. After reboot, I have turned-off my phone and I've tried to enter in the TWRP's recovery mode (using the combo buttons: VolumeUP + Home button + Power button) but the "TEAMWIN" logo didn't appear and the normal "Android Recovery Menu" were visualized.
I need some help to undestand if I did some mistakes during the flashing process. I've used the last versione of TWRP (3.1.1-0 for jfltexx). Any help will be appreciated. Thanks for your attention to this matter.
If you want to root with TWRP, try this for the gt-i9505:
open Odin 3.07 and uncheck everything except r reset time;
download the tar version of twrp for the gt-i9505: https://dl.twrp.me/jfltexx/
download the latest version of supersu.zip and copy it to an sd card or the phone's internal storage: http://www.supersu.com/download;
place the sd card in the phone if twrp has been saved to the sd card from the step above;
connect the phone in download mode and flash twrp in Odin's PDA slot;
when you see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery, install supersu.zip, reboot.
If you just want to install a custom ROM, copy the ROM to the internal or external sd card, install twrp, and install the ROM. Root is not required to install a custom ROM, only a custom recovery.
Warning: whenever you flash anything to a phone, it is always possible for something to go wrong and you must be prepared to deal with any consequences. I have used this method for several note 2, note 3, s3, and s4 phones without any issues. With this being said, I can't guarantee that the above steps will work for your phone or your phone won't be bricked.
I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.
OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
VanGolfer said:
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
Click to expand...
Click to collapse
Why dont you try to revert back stock using a factory image?
chichu_9 said:
Why dont you try to revert back stock using a factory image?
Click to expand...
Click to collapse
I used MDB08M factory instead of MDB08L which originally from the phone, I am not sure this the course of the problem.
The red exclamation usually means either no recovery or incompatible recovery. Did you flash mmb29m recovery for mdb08m rom? If you get stuck too bad you can always enter fastboot and just reflash everything its not that hard to do.
dontbeweakvato said:
The red exclamation usually means either no recovery or incompatible recovery. Did you flash mmb29m recovery for mdb08m rom? If you get stuck too bad you can always enter fastboot and just reflash everything its not that hard to do.
Click to expand...
Click to collapse
Yes, I flashed whole mmb29m factory image over mdb08m. Still can't boot to recovery manu . I'm worried about OTA will fail.
Sent from my Nexus 6P using Tapatalk
VanGolfer said:
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
Click to expand...
Click to collapse
Once you're on that screen, you've held down the power button then pressed and released volume up right?
Sent from my SM-N920T using Tapatalk
VanGolfer said:
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
Click to expand...
Click to collapse
Get into fastboot, then "fastboot flash recovery xxxxxxxx.img" obviously replacing the x's with the file name. Just reflash the recovery for the same factory image you flashed. Very possible that you just need to reflash the recovery image.
spc_hicks09 said:
Get into fastboot, then "fastboot flash recovery xxxxxxxx.img" obviously replacing the x's with the file name. Just reflash the recovery for the same factory image you flashed. Very possible that you just need to reflash the recovery image.
Click to expand...
Click to collapse
Tried but doesn't work.
Sent from my Nexus 6P using Tapatalk
Flash the recovery via fastboot :
fastboot flash recovery xxx.img
fastboot reboot-bootloader
Now, when your phone reboots to bootloader, using the volume keys, find "recovery" and use the power button to confirm.
profit.
he has to press the power button and vol up on that screen to get into recovery just like guy in post 7 said...
factory recovery doesnt boot all the way into it by default, requires a user button input once it gets to that android exclamation screen
kauemelhado said:
Flash the recovery via fastboot :
fastboot flash recovery xxx.img
fastboot reboot-bootloader
Now, when your phone reboots to bootloader, using the volume keys, find "recovery" and use the power button to confirm.
profit.
Click to expand...
Click to collapse
I did this, the red little thing didn't go away
Sent from my Nexus 6P using Tapatalk
VanGolfer said:
I did this, the red little thing didn't go away
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Did you try downloading another recovery file?
That's really strange.
I was having this error when I tried to flash twrp and boot direclty to system (skipping the recovery boot).
Did you try to install twrp?
---------- Post added at 01:53 PM ---------- Previous post was at 01:48 PM ----------
Another thing..
The system boots up normaly?
To solve this, I did the procedure that I just told you + before booting into twrp, I flashed vendor.img..
Dunno if that could cause this issue
kauemelhado said:
Did you try downloading another recovery file?
That's really strange.
I was having this error when I tried to flash twrp and boot direclty to system (skipping the recovery boot).
Did you try to install twrp?
Click to expand...
Click to collapse
When I root I installed TWRP, revert back all to stock after unroot. I have to stay unroot because of the company app. Just want to be easy to update on OTA,
Sent from my Nexus 6P using Tapatalk
VanGolfer said:
When I root I installed TWRP, revert back all to stock after unroot. I have to stay unroot because of the company app. Just want to be easy to update on OTA,
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I know that feel bro, my company also use an app that verifies for root..
I'm rooted, but on 6.0 I had only twrp w/ no root. no problems..
kauemelhado said:
I know that feel bro, my company also use an app that verifies for root..
I'm rooted, but on 6.0 I had only twrp w/ no root. no problems..
Click to expand...
Click to collapse
So you can install twrp without root as I understand. Then do you need to lock your phone after install twrp (unlock before install twrp, right?), and also how do you do the update OTA or upgrade to 6.0.1, etc..? Thx
VanGolfer said:
So you can install twrp without root as I understand. Then do you need to lock your phone after install twrp (unlock before install twrp, right?), and also how do you do the update OTA or upgrade to 6.0.1, etc..? Thx
Click to expand...
Click to collapse
I guess you can't lock your bootloader with Twrp.
Then, to take ota's just simply flash the img files.
;s
I had TWRP 3.0.1 so I downloaded the latest TWRP 3.0.2 IMG file and booted to Recovery and selected the image and then selected Recovery as to where to flash and it flashed no errors so I backed out and went to reboot and selected Recovery and it rebooted to bootloader and when I stroll volume keys to Recovery then power to select it just hangs there I have to do a power long press to get it to reboot back to Android. Any ideas why Recovery will not load now ?
I'm on MHC19l
Stock rooted no mods
System rooted
Sent from my Nexus 6P using Tapatalk
A bad flash, perhaps? Have you checked the MD5 after downloading?
Possible bad download but at this point I can't reflash the recovery until I can fast boot .. I gotta order another Type C to USB to connect the phone to the computer for fast boot grrrrr...
Thx
Sent from my Nexus 6P using Tapatalk
Glad to help! Next time make sure you check MD5 before flashing (even then an occasional bad flash could still cause trouble, but hey, what's the choice here?) You can still boot to Android normally, no?
Sidenote: anyone knows if a micro B to C adaptor would work with fastboot?
Yeah I can still boot to Android fine jus when I select recovery n bootloader it hangs in bootloader. I have to hard reset to get out of bootloader mode lol....
Jus sucks BC now I gotta wait until friday to order a Type C to USB cable to use the computer to fast boot TWRP to recovery.. :/
I jus got this 6P 4 days ago coming from the HTC M9 Developer Edition I decided to go with the 6P over the M10 even though I would have gotten $100 off the M10 for not using my UhOh protection.
But I'm currently Stock w/ root until I figure out or understand this whole Vender thing when flashing Roms.. Jus being very cautious.
With HTC you jus flash the ROM you want but here some say jus flash the ROM and some say flash the Vender matching the ROM.. Lol,..
Sent from my Nexus 6P using Tapatalk
About the vendor img... Not too sure about the whole technical details behind them, but I just flash them every time Google updates them (think monthly security updates), at the very least to get rid of the 'vendor img outdated' popup. You don't need to flash a new vendor img everytime you update/switch ROMs, but only when there's a new vendor.
I usually just flash recovery with flashify. Never had an issue doing it that way. Or fastboot.
Sent from my Nexus 6P using XDA-Developers mobile app
scoot0073 said:
I had TWRP 3.0.1 so I downloaded the latest TWRP 3.0.2 IMG file and booted to Recovery and selected the image and then selected Recovery as to where to flash and it flashed no errors so I backed out and went to reboot and selected Recovery and it rebooted to bootloader and when I stroll volume keys to Recovery then power to select it just hangs there I have to do a power long press to get it to reboot back to Android. Any ideas why Recovery will not load now ?
I'm on MHC19l
Stock rooted no mods
System rooted
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
People have been facing the same issue all around. Even I did, last night after updating to N Preview. Anyhow, the only solution I know right now is to have a decrypted filesystem (disable encryption), for TWRP to boot and work properly.
Yeah disable encryption I believe I read requires booting into recovery and wiping User Data or something alone those line's.
Unless there's a option in Android settings to disable it idk yet as I jus had the phone a few day's.
But so far I happy with my decision to get the 6P over the M10 even if the 6P is 4 or 5 moths old...
Sent from my Nexus 6P using Tapatalk
OK I got the latest TWRP Recovery flash . I used Flashify app and it flashed the recovery and I got a working recovery now..
Sent from my Nexus 6P using Tapatalk
Pain-N-Panic said:
I usually just flash recovery with flashify. Never had an issue doing it that way. Or fastboot.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank u so much that fixed my borked recovery thank you again
Sent from my Nexus 6P using Tapatalk
Two-Click Unlock for Zenfone 2 official Android 6.0
original post in Taiwan Asus Zentalk by @shakalaca
**do it at your risk**
1.Your PC must be adb environment ready.
2.You should know how to get into stock bootloader.( press Power and Volume up together)
files needed:
1. Download unlock.bat and restore.bat from here.
2. Recomended TWRP for verification.(repacked)
steps:
1.Copy unlock.bat and restore.bat on to your PC.
2.Plug your device in PC, click unlock.bat. The program will enter bootloader mode, reboot and then unlock.
3.After it run through unlock, the device will indicate it will reboot in 5 second. **important** PRESS VOLUME UP at the moment to enter bootloader.
4. If you miss step 3, the device will stuck in Asus logo. Don't worry. Just press POWER and VOLUME UP to enter bootloader.
5.When the device is in bootloader, click restore.bat Wait for the reboot and you are done unlock.
6.To verify unlock status, flash the recommended TWRP.
Good luck and all credits to @shakalaca
Is it the same as the unofficial method for bootloader unlock? also is there a way to relock bootloader like flashing it again over MM Beta?
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Flynhx said:
Is it the same as the unofficial method for bootloader unlock? also is there a way to relock bootloader like flashing it again over MM Beta?
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Click to expand...
Click to collapse
Different by the looks , the date gives it away and not a temp twrp-- although i am going to find out in about 10 mins --lets hope this works :highfive:
Not working for me
says flashing droidboot .184
anyone got this to work ?
no recovery after trying this - got stock recovery back from here ok
mega:///#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!ok8SQKII
timbernot said:
Different by the looks , the date gives it away and not a temp twrp-- although i am going to find out in about 10 mins --lets hope this works :highfive:
Not working for me
says flashing droidboot .184
anyone got this to work ?
no recovery after trying this - got stock recovery back from here ok
mega:///#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!ok8SQKII
Click to expand...
Click to collapse
According to @shakalaca, the restore process get back to 6.0 ifwi. After the unlock, the droidboot stay at .184 alright.
What is the status of your device before unlock, rooted or unrooted? Can you flash the twrp provided by him ?
samcjtsai said:
According to @shakalaca, the restore process get back to 6.0 ifwi. After the unlock, the droidboot stay at .184 alright.
What is the status of your device before unlock, rooted or unrooted? Can you flash the twrp provided by him ?
Click to expand...
Click to collapse
my device doesnt get to this part > 3.After it run through unlock, the device will indicate it will reboot in 5 second. **important** PRESS VOLUME UP
but stays on > press any key to finish...... which then closes the window
I flash twrp,says ok but reboots back to bootloader after restarting recovery.
flashed back stock recovery and factory reset for another attempt...lets see
Works good to me. Miss that step where I supposed to pressed vol up button and phone stuck on white splash screen. Force off and then go to bootloader, then execute restore.bat and done. After that root and exposed and then I mess up some another stuff so need to flash 6.0.1 MOFD_SDUPDATE manually from stock recovery. Everything pass smoothly but root and exposed framework disappeared obviously. Root and exposed again no problems
cannot flash custom roms???
Hi everyone,
I successfully unlocked my bootloader from MM beta, I successfully flashed the recommended twrp recovery, I successfully flashed rom and gapps but when I reboot the phone goes back to twrp recovery. Anyone else facing the same issue? Or is it impossible to flash custom roms?
Yousvel said:
Hi everyone,
I successfully unlocked my bootloader from MM beta, I successfully flashed the recommended twrp recovery, I successfully flashed rom and gapps but when I reboot the phone goes back to twrp recovery. Anyone else facing the same issue? Or is it impossible to flash custom roms?
Click to expand...
Click to collapse
ATM this unlock can backup/restore stock rom in recommended twrp, but can't flash CM. Seems its boot.img need to be repacked.
Yousvel said:
Hi everyone,
I successfully unlocked my bootloader from MM beta, I successfully flashed the recommended twrp recovery, I successfully flashed rom and gapps but when I reboot the phone goes back to twrp recovery. Anyone else facing the same issue? Or is it impossible to flash custom roms?
Click to expand...
Click to collapse
Same problem here
samcjtsai said:
ATM this unlock can backup/restore stock rom in recommended twrp, but can't flash CM. Seems its boot.img need to be repacked.
Click to expand...
Click to collapse
how can i flash a stock 5.0 rom from the recommended twrp? I tried to do that but it doesn't work. Do I have to flash a stock 6.0.1 beta rom?
It worked perfectly!Thanx a mill!
Can't flash TWRP although the splash screen became white after unlock.bat -> unlocked
After restore.bat the splash screen went black as usual. Then I flash the recommended TWRP. But when I choose recovery mode in fastboot, it reboot to fastboot. When I adb reboot recovery in Android OS, it reboot to stock recovery. Can anyone help me to solve this problem?
I'm running .69 MM beta, I replaced the .54 fastboot image in the package with .69 one. Does this effect the unlock state?
timbernot said:
Different by the looks , the date gives it away and not a temp twrp-- although i am going to find out in about 10 mins --lets hope this works :highfive:
Not working for me
says flashing droidboot .184
anyone got this to work ?
no recovery after trying this - got stock recovery back from here ok
mega:///#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!ok8SQKII
Click to expand...
Click to collapse
Edit Unlock.bat, find "sleep 3" in the line 24 and change it to "sleep 25" to increase the waiting time to detect back the fastboot after your phone reboots...
This fixed me the issue.... try it...
can i flash supersu to become root after unlock with this method?
ponnuvelpandian said:
Edit Unlock.bat, find "sleep 3" in the line 24 and change it to "sleep 25" to increase the waiting time to detect back the fastboot after your phone reboots...
This fixed me the issue.... try it...
Click to expand...
Click to collapse
Thanks :good: , i`ll keep that in mind when the time comes back on 5 atm
kamyk70 said:
Works good to me. Miss that step where I supposed to pressed vol up button and phone stuck on white splash screen. Force off and then go to bootloader, then execute restore.bat and done. After that root and exposed and then I mess up some another stuff so need to flash 6.0.1 MOFD_SDUPDATE manually from stock recovery. Everything pass smoothly but root and exposed framework disappeared obviously. Root and exposed again no problems
Click to expand...
Click to collapse
How you root your MM beta?, please tell me, i wanna root mine too
Sent from my ASUS_Z008D using XDA-Developers mobile app
Bring twrp zip android 6 please.
Can anyone backup with TWRP and upload?
Factory reset, backup with TWRP, and upload[emoji6]
Gesendet von meinem ASUS_Z00AD mit Tapatalk
KarloHD said:
Bring twrp zip android 6 please.
Can anyone backup with TWRP and upload?
Factory reset, backup with TWRP, and upload[emoji6]
Gesendet von meinem ASUS_Z00AD mit Tapatalk
Click to expand...
Click to collapse
Are you going to post this in EVERY tread?
Sent from my ASUS_Z00A using Tapatalk
Now, if we can unlock stock 6.0, can anyone confirm me if we can directly flash custom roms without downgrading to 5.0
after running restore it worked, however when running unlock.bat, I get permission denied and the device goes tinto bootloader bootloop, and I had the device rooted and bootunlocked already in lollipop, I wonder why that happens?