Related
Hi,
I was at work Sunday night when the phone offers me an update, not wanting to lose my data I re-growth that has Tuesday morning during my last round (which takes me roughly 25/30 minutes ). So I run the update and go round when I come back I have the phone on the screen of blocked boot ...
Considering I'm looking since yesterday, I have already tried many tutorials that did not work.
I tried everything flashed like to start from zero but nothing worked. I have every time a message like: failed can't install image not signed OR dtb not found ...
I have access at fastboot and nothing else.
There's way to save this phone I for 3 months or it is good to wedge a table ?
Thx in advance
edit :
ok, i do this
http://www.asus-zenfone.com/2015/10/how-to-root-asus-zenfone-2-laser-ze500kl.html
and this
http://forum.xda-developers.com/showpost.php?p=66894780&postcount=5
and i have now acces to recovery mode
Edit 2 :
http://www.asuszenfoneblog.com/2015/04/how-to-flash-asus-zenfone-2-via-adb.html with the firware Version V13.10.7.1(Andriod M) https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
but after reboot i have the message : ERROR : Can't load invalid boot image !
i lose th recovery and i can't flash the boot ( remote dtb not found ) ...
edit 3 :
the phone has restarts with the original firmware but I have so manipulated that I do not know what I did
I remember using the following links : http://www.asus-zenfone.com/2015/09/how-to-flash-asus-zenfone-2-laser.html ans the stock rom for 550KL
when I reinstall the rom of origin, such would not boot and I had to boot the mod_boot.img picture (Flashtool boot mod_boot.img), which launches the phone and now more problem. It remains to remove the root which should be easier than the rest.
@Genux888 This link takes to ZE500KL's firmware downloads https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
Your phone model is ZE550KL but you first attempted to flash MM ROM of ZE500KL
Thats why you got error: invalid boot.img and you lost recovery.
I don't know where you got mod_boot.img from. Neverthless, here's the simplest fix-
1. Download ZE550KL's Stock_boot_recovery.zip
This zip contains stock signed recovery.img and boot.img. Extract it and copy both .img files to the folder where you have adb and fastboot files.
Download correct firmware for your ZE550KL of the correct SKU. You can find your SKU on your phone's box.
WW SKU : Download ZE550KL's firmware v1.17.40.1531 for WW SKU only
Let me know if your phone's SKU is not WW
Copy the firmware zip (UL-Z00L-WW-1.17.40.1531-user.zip) to your external sd card.
2. Connect your phone to computer and Reboot phone to fastboot mode.
3. Now run the following commands
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot oem reboot-recovery
3. Third command should reboot your phone to recovery mode.
Now, in recovery mode-
A) select "wipe cache partition" then select yes
B) select "apply update from sdcard" then select "UL-Z00L-WW-1.17.40.1531-user.zip" and finally select "yes"
stuck at verifying update package
MITHI-N said:
stuck at verifying update package
Click to expand...
Click to collapse
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.
sziraqui said:
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.
Click to expand...
Click to collapse
Hi can you put a link to OTA, I tried searching for it but could only get the full firmware from the asus website.
sziraqui said:
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.
Click to expand...
Click to collapse
Removed, putback battery & followed all steps, successfully installed 1531 rom
Then upgraded to Asus Marshmellow, Everything working.
But when I try to clear data & cache from new recovery I get couple of errors stating unable to mount /asdf & few other things
MITHI-N said:
Removed, putback battery & followed all steps, successfully installed 1531 rom
Then upgraded to Asus Marshmellow, Everything working.
But when I try to clear data & cache from new recovery I get couple of errors stating unable to mount /asdf & few other things
Click to expand...
Click to collapse
I did the following-
Input: "Wipe cache partition"
Output: E: unable to mount /asdf (invalid argument)
Input : "mount /system"
Input: "wipe cache partition"
Output: Cache wipe complete
E: unable to mount /asdf
E: Can't open /asdf/recovery/last_log
This shows that I am able to wipe cache after mounting /system (though it doesnt make sense)
I didn't wipe data as I don't want to setup my device again. You may try if wiping data works after mounting /system. Alternatively, you can flash stock 1.15's recovery (download from post #2)
and flash in fastboot mode using
Code:
fastboot flash recovery recovery.img
(assuming you recovery.img file is present in the folder where you have fastboot files)
And, here on XDA, we hit "thanks" good button if a post was helpful to us.
Sorry to reply so late but I managed to unlock my phone has put version 5.0, the update to 6.0, UNLOCK the boot, root the phone and install the TWRP may close 2 or 3 hours after my last post.
thank you.
i really like it when people post all the steps taken and links in their problem posts.
this is great.
(no, that is NOT sarcasm)
The best solution out there for zoold 550kl
This is the best answer for the rooted asus zenfone 2 550kl for upgrading to marshmellow stock .Thank you...
Help
@sziraqui My phone is in a bootloop and I honestly know pretty much nothing as to how to fix it.. I know it's the ZE551KL, but that's pretty much it. Is there any way youcan help me out? thanks in advance
Stock recovery for MM?
Anyone have stock recovery for MM upgrade from LP?
Problem Not Solved
I am Also facing same type of problem but the difference is :
- I am only able to enter fastboot mode only when i am connecting my phone to pc via datacable.
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..
I've seen you've tried a lot.
I'd suggest you try this... As long as you can send your phone to fastboot and can pc/add your way through you'll be able to unbrick it. This takes a bit of time as you'll be dealing with two huge downloads (system.img and stock rom) but it should do the trick.
Follow the guide here:
https://www.asus.com/zentalk/thread-80274-1-1.html
---------- Post added at 12:59 AM ---------- Previous post was at 12:54 AM ----------
utkarshdev20 said:
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..
Click to expand...
Click to collapse
The guide at https://www.asus.com/zentalk/thread-80274-1-1.html talks about flashing boot.img first then a huge (1.7GB) system.img second then recovery.img last.
So it could mean the boot.img and system.img needs to be dealt with first before you have any chances of getting your recovery to work.
Follow the steps closely, I've been able to fix a brick with it twice.
NO way to boot into Recovery or Fastboot!!!!!!!!!!!!!
Phone got bricked!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
When connected to PC(Windows), I only get 8 local disk partitons (ext4) asking to format!!!!!!!!!!!
And one with image partition(BOOT)
What to do now to regain access to either fastboot or to recovery!!!!!!!!!!!!!!!!!
PLEASE Reply!!!!!!!!!!!!!!!!!!
utkarshdev20 said:
I am Also facing same type of problem but the difference is :
- I am only able to enter fastboot mode only when i am connecting my phone to pc via datacable.
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..
Click to expand...
Click to collapse
I can help you but first i neef some info about your phone..how it got bricked?was your phone rooted?
First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out
Sahaj4 said:
First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out
Click to expand...
Click to collapse
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk
Jyoti_re said:
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk
Click to expand...
Click to collapse
Heyy.. Thanks a lot Jyoti_re! It worked out perfectly..
I have done till step 3.. The phone booted into 3.0.2
The sensors are not working. I will flash the presist.img as you said in step 4
However, i have encountered a problem. My OP2 is a 64 GB version. But now the internal storage shows 7gb free out of 9.66 GB.. Earlier it used to show 54GB instead of 9.66..
What should i do?
Thanks again
Yes u must have to flash persist.img via firstboot mode by typing [ fastboot flash persist ] for sensor correctly working.
Install es file explorar from play store and check which folder taking More space
don't forget to press thanks if I helped u.
Thanks a lot Jyoti! /
Yeah i got it.. Flashed the persist img.
i searched through the forums.. somehow my device got the 16gb version img.. i dont know how..
i had to flash userdata64G.img as well
Now it all works perfectly.. sensors are working.. data storage is back at 54gb..
Thanks a lot! I had been stuck on this bootloop since 3 days..
and i pressed the thanks button.. i will press it 100 times over if possible Thanks again! Cheers!
Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!
Sahaj4 said:
Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!
Click to expand...
Click to collapse
Flash this SuperSU
https://drive.google.com/file/d/0B0OiN2evbEPuZk1KSk1hYUpEazA/view?usp=drivesdk
don't forget to press thanks if I helped u.
OP2 stuck in bootloop on upgrading from 2.0.2 to 3.0.2
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...
ciroportugues said:
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...
Click to expand...
Click to collapse
Have u enabled OEM unlocking in developer option ??
No i forgot to enable...
No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
Jyoti_re said:
Have u enabled OEM unlocking in developer option ??
Click to expand...
Click to collapse
No iforgot to enable...
What can i do now?
ciroportugues said:
No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
No iforgot to enable...
What can i do now?
Click to expand...
Click to collapse
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Jyoti_re said:
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.
ciroportugues said:
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.
Click to expand...
Click to collapse
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.
ciroportugues said:
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.
Click to expand...
Click to collapse
What does the Device Manager show when you connect your phone? By what name is it identified?
Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).
---------- Post added at 10:06 PM ---------- Previous post was at 09:37 PM ----------
Sahaj4 said:
What does the Device Manager show when you connect your phone? By what name is it identified?
Click to expand...
Click to collapse
Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).
When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings
Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Sahaj4 said:
When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings
Click to expand...
Click to collapse
Tried this commands but the sistem reboots and stucka on powered by android
ciroportugues said:
Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Tried this commands but the sistem reboots and stucks on powered by android
Click to expand...
Click to collapse
Hi. want to know if you anymore command to help me? thanks for help
ciroportugues said:
Hi. want to know if you anymore command to help me? thanks for help
Click to expand...
Click to collapse
I don't know much.. only as much as i have tried..
try running the command
fastboot oem device-info
if your device is unlocked, you are lucky! then there are many options
but if your device is locked.. then as far as i know, msm tool is your only saviour
try using this guide to unbrick your phone
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Hello,
I need help about my yureka plus on android (YU5510A),
I bought yureka plus yesterday and it comes on stock android 4.4.4 (Kitkat), I try to install custom rom and connect my phone to my laptop with help of YUWARE and try to unlock the bootloader in fastboot mode, it shows the successful message, but phone cant restart, I restart it manually, but it stuck on Yureka logo, trying again for flashing TWRP, same thing happen.
My phone (YU5510A) stuck on yureka plus logo.
So please help me.
Best Regards
Sadique A
sadique2804 said:
Hello,
I need help about my yureka plus on android (YU5510A),
I bought yureka plus yesterday and it comes on stock android 4.4.4 (Kitkat), I try to install custom rom and connect my phone to my laptop with help of YUWARE and try to unlock the bootloader in fastboot mode, it shows the successful message, but phone cant restart, I restart it manually, but it stuck on Yureka logo, trying again for flashing TWRP, same thing happen.
My phone (YU5510A) stuck on yureka plus logo.
So please help me.
Best Regards
Sadique A
Click to expand...
Click to collapse
your device is soft bricked from where i see,
download the drives first for your device link :- https://androidmtk.com/download-yu-usb-driver
download adb platform tools:- https://dl.google.com/android/reposi...st-windows.zip
download recovery:- https://dl.twrp.me/tomato/
download the fast-boot firmware:- http://builds.cyngn.com/factory/tomato/cm-12.1-YOG4PAS8A4-tomato-signed-fastboot-a7a306cebd.zip
download factory image maker :- https://drive.google.com/open?id=0BxGRG9YXw62rUWNLMjdNaGt1a2s
method 1
extract the fast boot firmware and factory image maker in same folder. then follow these steps.
put your phone in fast-boot mode and type fastboot -i 0x1ebf oem unlock (will unlock your bootloader)
and now find flash_all.bat file in the folder where you extracted all files and run as admin. let the process finish you would be back at stock firmware with no boot loops.
if you don't want to go to factory image then
method 2
boot your phone in fastboot and type
fastboot -i 0x1ebf oem lock (to lock your bootloader)
fastboot -i 0x1ebf oem unlock (to unlock your boot loader) as you used yuware or something that might created problem in bootloader so follow both.
fastboot -i 0x1ebf flash recovery name_of_recovery.img
and let it flash recovery then boot into recovery go to advance wipe format data type yes and swipe, install any custom rom and flash gapps done.
if you face still boot loops follow method 1 and flash roms later.
P.s while in fast-boot remove sim cards and memory cards from your phone and then run any commands.
and while flashing any roms please do remove sim cards.
Bhavesh_khatri said:
your device is soft bricked from where i see,
download the drives first for your device link :- https://androidmtk.com/download-yu-usb-driver
download adb platform tools:- https://dl.google.com/android/reposi...st-windows.zip
download recovery:- https://dl.twrp.me/tomato/
download the fast-boot firmware:- http://builds.cyngn.com/factory/tomato/cm-12.1-YOG4PAS8A4-tomato-signed-fastboot-a7a306cebd.zip
download factory image maker :- https://drive.google.com/open?id=0BxGRG9YXw62rUWNLMjdNaGt1a2s
method 1
extract the fast boot firmware and factory image maker in same folder. then follow these steps.
put your phone in fast-boot mode and type fastboot -i 0x1ebf oem unlock (will unlock your bootloader)
and now find flash_all.bat file in the folder where you extracted all files and run as admin. let the process finish you would be back at stock firmware with no boot loops.
if you don't want to go to factory image then
method 2
boot your phone in fastboot and type
fastboot -i 0x1ebf oem lock (to lock your bootloader)
fastboot -i 0x1ebf oem unlock (to unlock your boot loader) as you used yuware or something that might created problem in bootloader so follow both.
fastboot -i 0x1ebf flash recovery name_of_recovery.img
and let it flash recovery then boot into recovery go to advance wipe format data type yes and swipe, install any custom rom and flash gapps done.
if you face still boot loops follow method 1 and flash roms later.
P.s while in fast-boot remove sim cards and memory cards from your phone and then run any commands.
and while flashing any roms please do remove sim cards.
Click to expand...
Click to collapse
Need custom recovery
TWRP 3.0.2 not supported by YU5510A
sadique2804 said:
Need custom recovery
TWRP 3.0.2 not supported by YU5510A
Click to expand...
Click to collapse
TWRP is custom recovery itself, using it on my device since year, works fine you might have flashed wrong twrp. Try rom the link provided and remove every thing from phone before flashing twrp.
Bhavesh_khatri said:
TWRP is custom recovery itself, using it on my device since year, works fine you might have flashed wrong twrp. Try rom the link provided and remove every thing from phone before flashing twrp.
Click to expand...
Click to collapse
I know TWRP is custom recovery
But in my phone (YU5510A, Stock Android 4.4.4) it is not supported.
Whenever I am trying to install, it corrupt the recovery and the firmware of my phone.
After installing TWRP 3.0.2.0 (downloaded from official website under tomato section) my phone cant boot, it stuck on YU logo.
If you have the link please share.
sadique2804 said:
I know TWRP is custom recovery
But in my phone (YU5510A, Stock Android 4.4.4) it is not supported.
Whenever I am trying to install, it corrupt the recovery and the firmware of my phone.
After installing TWRP 3.0.2.0 (downloaded from official website under tomato section) my phone cant boot, it stuck on YU logo.
If you have the link please share.
Click to expand...
Click to collapse
Like i said your device is soft bricked try methods i suggested, but recovery should work fine press vol up+ vol down+power button to boot into recovery you would be able to use TWRP. if not try to flash recovery again as i said yuware might have introduced some bugs install as i suggested. your device stuck at boot loop has nothing to do with recovery not working.
---------- Post added at 08:03 PM ---------- Previous post was at 07:50 PM ----------
Try to flash older versions here is 2.8.4.0 if you on kit-kat or any,
https://dl.twrp.me/tomato/twrp-2.8.4.0-tomato.img
https://dl.twrp.me/tomato/twrp-2.8.5.0-tomato.img
https://dl.twrp.me/tomato/twrp-2.8.6.0-tomato.img
type
fastboot -i 0x1ebf flash recovery twrp-2.8.4.0-tomato.img
remove simcards and memory cards while flashing. hope this helps.
I flashed cm12.1 officially signed, and it worked and i recovered my device, but i want to flashed custom rom and it needs a custom recovery.
That's the problem, and I tried 2.8.7 and 2.8.6 and 2.8.5.
Currently I am on official cm12.1 with cm recovery.
I m also facing same problem.
---------- Post added at 08:26 PM ---------- Previous post was at 08:26 PM ----------
sadique2804 said:
I flashed cm12.1 officially signed, and it worked and i recovered my device, but i want to flashed custom rom and it needs a custom recovery.
That's the problem, and I tried 2.8.7 and 2.8.6 and 2.8.5.
Currently I am on official cm12.1 with cm recovery.
Click to expand...
Click to collapse
Your problem solved bro?
sadique2804 said:
I know TWRP is custom recovery
But in my phone (YU5510A, Stock Android 4.4.4) it is not supported.
Whenever I am trying to install, it corrupt the recovery and the firmware of my phone.
After installing TWRP 3.0.2.0 (downloaded from official website under tomato section) my phone cant boot, it stuck on YU logo.
If you have the link please share.
Click to expand...
Click to collapse
TRY TO UNLOCK BOOTLOADER FIRST.
Twrp won't install properly if the bootloader is locked.
IF THIS HELPS CLICK THANKS :good:
Hangs twrp
My phone got hanged at twrp yureka plus yu5510A stock lollipop plz help
ray pember said:
My phone got hanged at twrp yureka plus yu5510A stock lollipop plz help
Click to expand...
Click to collapse
Flash latest version of twrp using adb
Here is the link
https://dl.twrp.me/tomato/twrp-3.1.1-0-tomato.img.html
My device 5510a I install twrp but touch not working properly so plz help me....next what I do
sadique2804 said:
Hello,
I need help about my yureka plus on android (YU5510A),
I bought yureka plus yesterday and it comes on stock android 4.4.4 (Kitkat), I try to install custom rom and connect my phone to my laptop with help of YUWARE and try to unlock the bootloader in fastboot mode, it shows the successful message, but phone cant restart, I restart it manually, but it stuck on Yureka logo, trying again for flashing TWRP, same thing happen.
My phone (YU5510A) stuck on yureka plus logo.
So please help me.
Best Regards
Sadique A
Click to expand...
Click to collapse
hello for yureka i have some files I hope u don't try fastboot cause yureka have limited rom memory i have some files i encountered the worst case . i went to local vendor he did it for 3dollar. nd yes i read some yureka have a different board in the differnet country so files are bit messed up feel free to message i have somefiles try the luck or better search other thread developers are not doing a lot nowadays i was trying ubuntu but somehow sad life
Hii I have yu yureka plus (yu5510a) the phone is starting and stuck at YU logo after that blue screen appears and phone can't go ahead .
And When i connect the phone with pc it can't detected and an error shows in phone that "do not disconnect the data cable" & in bottom left "your phone is not secure" please help
After installing magisk via TWRP I loaded magisk manager and updated to 18.0. It asked me if I wanted to reboot but upon reboot I'm stuck in fastboot mode,. Fastboot reboot just takes me back to fastboot mode.
I can boot to recovery but once again if I select reboot to system it goes to fastboot mode.
Any idea?
I have same problem, any suggestions?
I've got the same exact problem...one difference is it happened on FulmicsROM, i dont know what to do now, help guys please
Same here. I tried to flash boot.img from *.zip and TRWP. No change. I can't boot into TRWP too, only in fastboot.
I had the same issue. You have to flash the stock boot image or your current rom build from twrp. You get to twrp with holding power and volume down while starting. Release the power button for a second at the lg logo then press it again. Confirm with yes but be aware that just works if you have a custom bootloader (like twrp) . If not you gonna erase your system.
You can still flash TWRP directly from fastboot with fastboot flash recovery twrp.img (or fastboot flash boot twrp.img, if you still can't boot to recovery) and boot it after flashing, just to be sure not to overwrite the whole system.
Everybody who posted today (2nd or 3rd Jan 2020) just updated their Magisk to v20.2, and ran into the 'only fastboot' error upon reboot? Did you folks update Magisk within Android or in TWRP?
---------- Post added at 11:03 AM ---------- Previous post was at 10:54 AM ----------
tremalnaik said:
You can still flash TWRP directly from fastboot with fastboot flash recovery twrp.img (or fastboot flash boot twrp.img, if you still can't boot to recovery) and boot it after flashing, just to be sure not to overwrite the whole system.
Click to expand...
Click to collapse
not for me on a G5, could neither boot recovery (without flashing) nor flash recovery using fastboot, the downloading or sending part are both ok, but the booting or writing recovery part result in 'FAILED (remote: unknown command)'
this is the first time after more than 2yrs with the G5 that i ran into this problem while updating Magisk; all in all a very vexing problem (initially it was also due to me having a hard time trying to enter recovery, couldnt get the timing right).
on a side note, the V30 updated uneventfully.
perhaps, from a layman's point of view, with the advancement of Android OS, it is now harder to have a one size fits all root solution, thus it is better not to update Magisk if it is working well and if the new version does not offer any or much improvement over the previous for older OS.
I had the magisk 20.2 fastboot only issue this morning on my G6 (H872). I used the hardware button factory reset steps to get me into TWRP as I had that installed for my recovery already. From there I reflashed magisk uninstaller, followed by magisk 20.1. hopefully that helps others here.
potatohead said:
Everybody who posted today (2nd or 3rd Jan 2020) just updated their Magisk to v20.2, and ran into the 'only fastboot' error upon reboot? Did you folks update Magisk within Android or in TWRP?
---------- Post added at 11:03 AM ---------- Previous post was at 10:54 AM ----------
Click to expand...
Click to collapse
I am stuck in fastboot. Tried to update Magisk via the internal update function. Did not work for the first time.
Finally installed new ROM.....
You have to follow the steps in the following post:
https://forum.xda-developers.com/showpost.php?p=81378123&postcount=13
Unfortunately, I haven't followed those instructions, and I have unbricked my phone using LGUP (from this thread https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222) and the H87020h_00_OPEN_EU_OP_0110.kdz file I had on my PC. I have lost all my Data though...
Got the same problem with my H870 today. With TWRP already installed i try to uninstall Magisk with the "Magisk-uninstaller-20200102.zip" and flash Magisk-v20.1 . This didn't work for me
Now i dirty-flashed the 30B Stock (https://forum.xda-developers.com/lg-g6/development/rom-lg-h870-eu-30b-rom-t4007979) over my older 20G an everything works more or less. The system is pretty slow and i got some problems with Titanium not beeing able to uninstall some bloatware-apps because it couldn't find the correspoding APKs. After reinstalling Titanium i couldn't start it.
Most likely i have to do another fresh install after i have done some backups...
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty could be void if you tamper with any part of your device / software.
* Same statement for XDA.
Needed tools : Backup your phone before following any steps
1. Minimal adb and fastboot
2. official TWRP 3.3 for jasmine_sprout Download img file from twrp website
3. latest magisk manager 19.2 zip file from magisk manager website
First step : Boot loader unlock
1) Tap on build number more than 7 times and unlock developer option in about phone.
2) turn on OEM Unlocking and USB debugging
Now open command windows in adb shell folder and connect your device to computer.
type : 1) adb devies (this should show your device after giving permission in your phone : conformation that your device is
connected)
2) adb reboot bootloader
3) fastboot devices ( conformation that your phone is coonected in fastboot mode)
4) fastboot oem unlock
( after that you need to follow according steps in your phone and grant to unlock phone)
keep in mind this will reset your phone. Afteer reboot again turn on developer options and usb debugging
5) fastboot flashing unlock_critical
( the warning and steps you need to follow again in your phone like in step 4)
this will again reset your phone.Afteer reboot again turn on developer options and usb debugging
Congratulations your bootloader is Unlocked now.
STEP 2. Flashing TWRP and Magisk Install
before that keep in mind As Mi A2 follows A/B boot partition system so DONT DIRECT FLASH TWRP FROM
FASTBOOT.
" Dont forget to turn on developer options and usb debugging "
open command window in adb shell folder and boot your phone in bootloader mode as told earlier and connect to computer.
Copy twrp-3.3.0-0-jasmine_sprout.img to minimal adb and fastboot folder. you can rename it to your convenient name
type : 1) fastboot boot twrp-3.3.0-0-jasmine_sprout.img
or if you renamed it
fastboot boot YourRenameName.img
this will temporarily boot twrp in your Device. As twrp is booted you will be able to see your phone connected in computer
(file transfer mode)
Copy and paste both magiskmanager.zip (current latest stable is 19.2 ) into phone
Flash your downloaded version of Magiskmanager.zip
Reboot your Phone.
Congratulations If nothing goes sideways Your phone is Magisk Rooted.
If you want to flash something using TWRP now is the time Otherwise as Mi A2 has A/B slot form and no Recovery Partition You Cannot flash TWRP permanently.
But You can always boot TWRP from adb and use it.
ROM flashing help
Can't flash ROM after using this method
Torque422 said:
Can't flash ROM after using this method
Click to expand...
Click to collapse
You May be facing some highly lag issues too. In that case flash stock rom using mi flash tool. In my steps i said that flash twrp.zip file after booting it. But flashing twrp.zip doesnt do anything. if you want to use TWRP you need to boot TWRP everytime from adb.
Also After flashing stock rom i am pretty sure that you will be able to flash custom rom.
follow this guide for flashing custom ROMs
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Failed
No such a directory problem, please help
Please elaborate more about the problem ? @shahidrok
shahidrok said:
No such a directory problem, please help
Click to expand...
Click to collapse
---------- Post added at 03:16 PM ---------- Previous post was at 03:08 PM ----------
TYPHOON9055 said:
You May be facing some highly lag issues too. In that case flash stock rom using mi flash tool. In my steps i said that flash twrp.zip file after booting it. But flashing twrp.zip doesnt do anything. if you want to use TWRP you need to boot TWRP everytime from adb.
Also After flashing stock rom i am pretty sure that you will be able to flash custom rom.
follow this guide for flashing custom ROMs
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thanks ?, i have successfully installed havoc rom, i read that link many times But this time i read more carefully, I have installed everything now?
Do you know, If we can install nethunter in our mi a2 @TYPHOON9055
Hve done everything but when i try to reboot to twrp it gets stuck on twrp logo,dont know what im doing wrong.
Twrp only working when flashing via adb, and when I try to boot into twrp recovery it gets stuck twrp logo. Flashed magisk patched but unable to flash any magisk module or if I try to flash and reboot device it always get stucks in bootloop.. unable to find the problem.. a little help would be highly appreciated. Thanks
I get error 1 during flashing
Amnvlad said:
Twrp only working when flashing via adb, and when I try to boot into twrp recovery it gets stuck twrp logo. Flashed magisk patched but unable to flash any magisk module or if I try to flash and reboot device it always get stucks in bootloop.. unable to find the problem.. a little help would be highly appreciated. Thanks
Click to expand...
Click to collapse
Reflash the latest twrp again through fastboot , And flash only .img file of twrp
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Alucard said:
I get error 1 during flashing
Click to expand...
Click to collapse
Follow the flashing custom rom guide, i flashed successfully, Havoc rom is fantastic ?
Torque422 said:
Reflash the latest twrp again through fastboot , And flash only .img file of twrp
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Follow the flashing custom rom guide, i flashed successfully, Havoc rom is fantastic
Click to expand...
Click to collapse
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
Available custom roms are for Oreo versions if you have updated ur device to pie , it won't work.
Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
I was on stock pie + may update (10.0.9)
Follow this way , unlock the bootloader via fastboot oem unlock, fastboot flashing unlock it will reboot here, goto developer settings Enable usb debugging
Then do this fastboot flashing unlock_critical It will again reboot
Now, install the magisk app And download the patched boot image from internet Whatever your build no is, mine was 10.0.9 so i downloaded version 10.0.9_boot.img
Open the magisk app, click on install , select and patch a file, Then choose this downloaded patched image, it will flash it successfully, if it don't Then you have mistaken something..
After this there will be a patched.img in download folder Which is just created by magisk, copy this img to pc, Through fastboot Flash it "fastboot boot patched.img"
Now, flash TwrpImage3.3.img through fastboot
When you boot in , Copy and paste your rom, gapps
Now flash twrpVersion3.2.img via fastboot
Clear system,data,caches, Flash the rom in slot B
Now flash the twrp3.2.zip through installed twrp, click on recovery And it will boot to twrp
Now Flash the gapps in slot a (i used nano)
Now flash magisk.zip through twrp
Reboot , That's it!
(Twrp 3.2 is stable for flashing rom and gapps , Just for first time When we coming from stock
Twrp 3.3 latest Gives us MTP transfer, The difference is this in using both of these)
Installation of magisk is the last process, it is part of rom, First installed ur desired rom and then magisk
You said, You installed twrp, as i mentioned above You forgot to do some steps as about patched boot + installation of magisk through patched file etc..
Though you can try to search on google for your next step
patched supported magisk Version x.x.x for mi a2
If you got the file, You are lucky.. otherwise flash the stock rom with mi flash tool
And Start from unlocking bootloader
Magisk Module available.
Torque422 said:
Please elaborate more about the problem ? @shahidrok
---------- Post added at 03:16 PM ---------- Previous post was at 03:08 PM ----------
Thanks , i have successfully installed havoc rom, i read that link many times But this time i read more carefully, I have installed everything now
Do you know, If we can install nethunter in our mi a2 @TYPHOON9055
Click to expand...
Click to collapse
There is a magisk module available for installing kali nethunter in this device. i never tried installing it but it should work fine. Read proper descriptions before installing it though.
Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
the adb recognized my phone but fastboot do not, help me out please
Andrew.kathy said:
the adb recognized my phone but fastboot do not, help me out please
Click to expand...
Click to collapse
Probably a problem with drivers, check and reinstall drivers
Can i use this method to flash magisk on Mi 9T pro?
I can't boot into twrp
The command u said to enter fastboot boot twrp.img it says booting and then the bootloader message and then shut downs
Topper8118 said:
The command u said to enter fastboot boot twrp.img it says booting and then the bootloader message and then shut downs
Click to expand...
Click to collapse
Checklist:
- there is file of <compatible TWRP recovery> in ADB/Fastboot directory with the name you are typing in fastboot command
- ADB drivers installed correctly (both "adb devices -l" and "fastboot devices" return valid results in corresponding phone states)
- only one phone (namely MiA2) is connected to PC
- phone fully unlocked (OEM debugging enabled and PC was previously approved for ADB in phone)
- USB port on MB of PC is USB-2.x or USB-3.x-compatible-with-Mi-A2<which is not true in general>
Several guys says that command "fastboot oem unlock" is old and now we have to write "fastboot flashing unlock" instead, then "critical".
Which is the best way now?
Thank you
HTCDevil said:
Several guys says that command "fastboot oem unlock" is old and now we have to write "fastboot flashing unlock" instead, then "critical".
Which is the best way now?
Thank you
Click to expand...
Click to collapse
fastboot flashing unlock
fastboot flashing unlock_critical