Related
Dear Sir,
I have followed all the steps but still not rooted my htc desire 820 dual sim
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064..............this link I have followed.....
but didn't sucess.......
plz....help...Sir
HTC Desire 820 can be easily rooted with few simple steps.
I am not responsible for your warranty loss or device not functioning properly.
Steps
1] Unlock Bootloader if you don't know how to do it visit this page
2] Download TWRP Recovery from here
3] Download Super Su from Here and transfer it to your device
4] Reboot to Fastbboot mode using Volume Down and Power Key
5] Connect Phone to PC
6] Extract files from Recovery.zip in one location and simply click on flash-recovery.bat
7] After Step 6 is finished Using volume keys navigate and select recovery option and go to recovery
8] After rebooting in recovery select Install zip > and selecting supersu.zip transferred in first step to obtain root access.
9] Reboot
Very much urgent.......plz. reply...........
subinoy.bose said:
Dear Sir,
I have followed all the steps but still not rooted my htc desire 820 dual sim
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064..............this link I have followed.....
but didn't sucess.......
plz....help...Sir
HTC Desire 820 can be easily rooted with few simple steps.
I am not responsible for your warranty loss or device not functioning properly.
Steps
1] Unlock Bootloader if you don't know how to do it visit this page
2] Download TWRP Recovery from here
3] Download Super Su from Here and transfer it to your device
4] Reboot to Fastbboot mode using Volume Down and Power Key
5] Connect Phone to PC
6] Extract files from Recovery.zip in one location and simply click on flash-recovery.bat
7] After Step 6 is finished Using volume keys navigate and select recovery option and go to recovery
8] After rebooting in recovery select Install zip > and selecting supersu.zip transferred in first step to obtain root access.
9] Reboot
Very much urgent.......plz. reply...........
Click to expand...
Click to collapse
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Please let us know what is the exact message your getting are you not able to get to Recovery ???
I have been able to successfully root my device by following the steps outlined did not face any challenges hence wanted to check.
Same Probleam here pls help me
I AM SUFFERING FROM SAME PROBLEAM.
i am using desire 820q.
bootloader unlocked.
but when i enter in recovery then that says entering recovery then come back.
pls help me...
problem with htc 820q root
mukulatri said:
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Click to expand...
Click to collapse
I'm following this instruction and could not root my device,
My HTC 820q is unlock but when I want read SuperU.zip from Sd card at fastboot>recovery my mobile goes to restart and procedures been uncompleted.
Please help me, is this instruction only for HTC 820?
How we can root HTC 820q?
tah3r said:
I'm following this instruction and could not root my device,
My HTC 820q is unlock but when I want read SuperU.zip from Sd card at fastboot>recovery my mobile goes to restart and procedures been uncompleted.
Please help me, is this instruction only for HTC 820?
How we can root HTC 820q?
Click to expand...
Click to collapse
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064
mukulatri said:
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Click to expand...
Click to collapse
Well I have the same issue, recovery looks installed after pressing power button to launch it goes to a screen and go back almost instantly on fastboot screen. I also tried last version of framaroot, does not help either... just get a failed message
尚雷諾 said:
Well I have the same issue, recovery looks installed after pressing power button to launch it goes to a screen and go back almost instantly on fastboot screen. I also tried last version of framaroot, does not help either... just get a failed message
Click to expand...
Click to collapse
Hi there, let's go step by step without "shortcuts" that are typically working on PC/WIn.
1. Unlock bootloader of your phone at HTCdev[dot]com [replace 'dot' with . - sorry for confusion I haven't earned reputation to post external links yet]. All necessary tools (fastboot) will be provided to download during process as well as necessary instructions. You need Windows/Linux or OS X computer to complete this step.
2. Download custom recovery .img file and save it to same directory you have fastboot files (e.g. from step 1) on you computer
3. Start phone in fastboot mode (mind fast boot option in Power settings must be unchecked if you using VolDown [-] start option (not necessary if you use adb reboot bootloader). Battery must be charged over 10% (I suggest 30% to stay secure); connect to computer (phone shall display Fastboot USB)
4. Navigate command/terminal window on your computer to location of recovery image file from step 2 (fastboot files must be there or have a correct path specified).
5. On computer terminal window run command: fastboot flash recovery filename_of_recovery.img . Red section must be exact custom recovery file name.
6. You'll get some communication in terminal. If completed OK will be among them, if failure, there will be FAIL with description of reason (e.g. low_power). If only "waitng for device" dislays, check connection with phone.
7. Navigate phone to HBOOT, then select recovery. If recovery don't start, check step 1 and restart from step 3. If only icon with red ! appears, it means you have stock recovery installed. Please verify from step 1.
8. Once custom recovery is installed and working, use it to flash SuperSU or any other superuser app (must be flashable .zip to be applied). Install just 1 root application, to avoid problems. At this point, you may consider flashing busybox also if you plan extensive file modification, but it's not necessary for root. For any sake, clear cache befor restart.
9. Restart the phone - you shall view SuperSU application or any other superuses app you've flashed i step 8.
Hope now works.
T0ark said:
Hi there, let's go step by step without "shortcuts" that are typically working on PC/WIn.
1. Unlock bootloader of your phone at HTCdev[dot]com [replace 'dot' with . - sorry for confusion I haven't earned reputation to post external links yet]. All necessary tools (fastboot) will be provided to download during process as well as necessary instructions. You need Windows/Linux or OS X computer to complete this step.
2. Download custom recovery .img file and save it to same directory you have fastboot files (e.g. from step 1) on you computer
3. Start phone in fastboot mode (mind fast boot option in Power settings must be unchecked if you using VolDown [-] start option (not necessary if you use adb reboot bootloader). Battery must be charged over 10% (I suggest 30% to stay secure); connect to computer (phone shall display Fastboot USB)
4. Navigate command/terminal window on your computer to location of recovery image file from step 2 (fastboot files must be there or have a correct path specified).
5. On computer terminal window run command: fastboot flash recovery filename_of_recovery.img . Red section must be exact custom recovery file name.
6. You'll get some communication in terminal. If completed OK will be among them, if failure, there will be FAIL with description of reason (e.g. low_power). If only "waitng for device" dislays, check connection with phone.
7. Navigate phone to HBOOT, then select recovery. If recovery don't start, check step 1 and restart from step 3. If only icon with red ! appears, it means you have stock recovery installed. Please verify from step 1.
8. Once custom recovery is installed and working, use it to flash SuperSU or any other superuser app (must be flashable .zip to be applied). Install just 1 root application, to avoid problems. At this point, you may consider flashing busybox also if you plan extensive file modification, but it's not necessary for root. For any sake, clear cache befor restart.
9. Restart the phone - you shall view SuperSU application or any other superuses app you've flashed i step 8.
Hope now works.
Click to expand...
Click to collapse
Thanks for your answer, I have to say I properly unlocked the phone so I do not think there is a way I messed up with this step as when I start bootloader it clearly shows on the top of the screen ''UNLOCKED".
When I flashed recovery on my phone I had no errors prompted or any message of failure. The process went well until a success notification.
Now when I start my phone into bootloader I repeat, I clearly see that recovery has been installed but when I attempt to start it then I'll be almost instantly brought back to the bootloader screen... now I started to wonder if... if an update of android could cause this kind of issue? The point is my phone is using android 4.4.4 and not the factory version 4.4.2. I remember having updated my android version which was perhaps a mistake as this phone is not very old and I was planning to root it in the next days... Now I'm not expert just try to figure it out.
I tried different system to auto root via different apps, some using the PC some using directly the phone, I never get any success...
尚雷諾 said:
Thanks for your answer, I have to say I properly unlocked the phone so I do not think there is a way I messed up with this step as when I start bootloader it clearly shows on the top of the screen ''UNLOCKED".
When I flashed recovery on my phone I had no errors prompted or any message of failure. The process went well until a success notification.
Now when I start my phone into bootloader I repeat, I clearly see that recovery has been installed but when I attempt to start it then I'll be almost instantly brought back to the bootloader screen... now I started to wonder if... if an update of android could cause this kind of issue? The point is my phone is using android 4.4.4 and not the factory version 4.4.2. I remember having updated my android version which was perhaps a mistake as this phone is not very old and I was planning to root it in the next days... Now I'm not expert just try to figure it out.
I tried different system to auto root via different apps, some using the PC some using directly the phone, I never get any success...
Click to expand...
Click to collapse
Ok, please try twrp from Original Android Development tread (it works for me, mind, I'd question it's stability) or Philz recovery (sorry, I found only Chinese, but it's for verivication only: h...ps://drive.google.com/file/d/0BygOvRquk4z8S05kRC1XMXdSbXM/view?usp=sharing - please adjust tt in address - rookie rules).
I'd suggest test running from Fastboot: fastboot boot custom_recovery.img - replace with actual file name from directory you're running terminal.
This shall verify if it's problem with recovery file or any remaining protection...
T0ark said:
Ok, please try twrp from Original Android Development tread (it works for me, mind, I'd question it's stability) or Philz recovery (sorry, I found only Chinese, but it's for verivication only: h...ps://drive.google.com/file/d/0BygOvRquk4z8S05kRC1XMXdSbXM/view?usp=sharing - please adjust tt in address - rookie rules).
I'd suggest test running from Fastboot: fastboot boot custom_recovery.img - replace with actual file name from directory you're running terminal.
This shall verify if it's problem with recovery file or any remaining protection...
Click to expand...
Click to collapse
Does having S-ON bother? I was also wondering about that but all tutorials I found no one mentions anything about the S-ON or S-OFF thing.
But I do have a S-ON under UNLOCKED
what is stock recovery.img name
i dont know what is the real stock recovery.img name.
htc desire 820q dualsim
I can't root my htc desire 820q by this method, is any alternative way?
I just root my phone with same procedure but my phone still show s-on..... How can i s-off my phone.....
Hello everyone, I've been trying to unbrick my ZenFone 2 ZE550ML for at least 5 hours...
(first, the small history...)
I've a french ASUS ZenFone 2 ZE550ML (Z008D) with 2 Go of RAM running latest Lollipop official ROM (I never unlocked bootloader or rooted it)
I suscribed to Asus beta tester program on ZenTalk forum, so I received the Marshmallow upgrade via official OTA last night.
Everything updated normally, I had enough space, update has been completed, I saw the ASUS logo on dark background because it's not unlocked, I saw the message "Optimizing apps..."(ART compiling)... and I successfully booted to Marshmallow... but just one time.
What happened is that my ZenFone 2 is... really... slow... and... with... Marshmallow... it... had... the... same.... slowness... than... with... Lollipop :silly:
And, after playing around with Marshmallow around ten minutes (apps were updating through Play Store), my phone hung, only because of slowness. I could make it sleep (screen turning on/off, that's all, no lock screen), and I could just access to shutdown/reboot menu if I press 3 seconds the Power button. But it was frozen, like it often did in Lollipop.
I waited 15 minutes, because I thought turning off while updating apps like Google Play Services was not a brilliant idea. After 15 minutes of waiting, still frozen, but even more frozen : no power menu, and orange LED was still ON even after disconnecting the charger. I decided to reset my ZenFone 2 by pressing power button 10 seconds.
And... I rebooted it => vibration, then immediately USB logo (when POWER or POWER+UP VOLUME). Nothing more after that. No LED while charging (if I plug it to a charger, it boot loop with USB logo). It's very frustrating because... I saw ASUS logo just before optimization, and I stopped it AFTER update, not during :crying:
(now what I tried)
Today I tried to apply this guide : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
I managed to install every driver, I downloaded every file/image I could...
Because of USB logo, my device is always recognized as a Moorefield device with known driver
Following the guide, I sent to my phone the basic 4-coulour bootloader using xFSTK, no problem
Here is the problem now : I've a working fastboot menu, fastboot is recognized by my computer, BUT almost every fastboot command fails, because my serial number was set to 0123456789ABCDEF :crying:
-> Fastboot error is systematically : FAILED (remote: flash_cmds error! (this happens after successfully downloading to phone, but it's not applying)
and, I tried "fastboot erase cache" :
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
I never had any software mess in my phone :crying:
So I don't know what to do, because I would like to flash only splashscreen, recovery and boot if possible, I don't want to lose data
I'm actually downloading a RAW for WW_ZE550ML_2.20.40.149 that I'll sideload with Asus Flash Tool (without wiping data) if it's the only way to do
Where can I find working images for fastboot that can be flashed on a generic serial number?
Thanks for your answers
Edit 1 : OH WAIT... The fastboot screen on my ZenFone 2 Z008 says :
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
WTF ASUS ?!?!?!?!
The ONLY things I did are : OTA update to Marshmallow (I never had OTA issues before) and sending through xFSTK the FW DNx, IFWI and OS Images FOR ZE550ML given in the guide... What happened?! Please please please, can somebody give me the right files? Thank you ^^
(sorry for eventual bad english, I'm a tired french)
Have you tried to re flash fastboot (fastboot flash droidboot.img)?
About the serial number, I think 0123..DEF is normal because I mine is like yours, too. But everything is fine.
fanfan54 said:
Hello everyone, I've been trying to unbrick my ZenFone 2 ZE550ML for at least 5 hours...
(first, the small history...)
I've a french ASUS ZenFone 2 ZE550ML (Z008D) with 2 Go of RAM running latest Lollipop official ROM (I never unlocked bootloader or rooted it)
I suscribed to Asus beta tester program on ZenTalk forum, so I received the Marshmallow upgrade via official OTA last night.
Everything updated normally, I had enough space, update has been completed, I saw the ASUS logo on dark background because it's not unlocked, I saw the message "Optimizing apps..."(ART compiling)... and I successfully booted to Marshmallow... but just one time.
What happened is that my ZenFone 2 is... really... slow... and... with... Marshmallow... it... had... the... same.... slowness... than... with... Lollipop :silly:
And, after playing around with Marshmallow around ten minutes (apps were updating through Play Store), my phone hung, only because of slowness. I could make it sleep (screen turning on/off, that's all, no lock screen), and I could just access to shutdown/reboot menu if I press 3 seconds the Power button. But it was frozen, like it often did in Lollipop.
I waited 15 minutes, because I thought turning off while updating apps like Google Play Services was not a brilliant idea. After 15 minutes of waiting, still frozen, but even more frozen : no power menu, and orange LED was still ON even after disconnecting the charger. I decided to reset my ZenFone 2 by pressing power button 10 seconds.
And... I rebooted it => vibration, then immediately USB logo (when POWER or POWER+UP VOLUME). Nothing more after that. No LED while charging (if I plug it to a charger, it boot loop with USB logo). It's very frustrating because... I saw ASUS logo just before optimization, and I stopped it AFTER update, not during :crying:
(now what I tried)
Today I tried to apply this guide : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
I managed to install every driver, I downloaded every file/image I could...
Because of USB logo, my device is always recognized as a Moorefield device with known driver
Following the guide, I sent to my phone the basic 4-coulour bootloader using xFSTK, no problem
Here is the problem now : I've a working fastboot menu, fastboot is recognized by my computer, BUT almost every fastboot command fails, because my serial number was set to 0123456789ABCDEF :crying:
-> Fastboot error is systematically : FAILED (remote: flash_cmds error! (this happens after successfully downloading to phone, but it's not applying)
and, I tried "fastboot erase cache" :
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
I never had any software mess in my phone :crying:
So I don't know what to do, because I would like to flash only splashscreen, recovery and boot if possible, I don't want to lose data
I'm actually downloading a RAW for WW_ZE550ML_2.20.40.149 that I'll sideload with Asus Flash Tool (without wiping data) if it's the only way to do
Where can I find working images for fastboot that can be flashed on a generic serial number?
Thanks for your answers
Edit 1 : OH WAIT... The fastboot screen on my ZenFone 2 Z008 says :
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
WTF ASUS ?!?!?!?!
The ONLY things I did are : OTA update to Marshmallow (I never had OTA issues before) and sending through xFSTK the FW DNx, IFWI and OS Images FOR ZE550ML given in the guide... What happened?! Please please please, can somebody give me the right files? Thank you ^^
(sorry for eventual bad english, I'm a tired french)
Click to expand...
Click to collapse
After flashing Z008 with xFSTK IAW the procedure you tried, the product name in fastboot screen is shown as ASUS_Z00A. After flashing with Asus flashtool, the fastboot screen says correct product number Z008 and corect serial number. :good:
I tried to flash boot.img, droidboot.img, system.img and recovery.img because I did not want to lose my data. Unfortunately, my Z008 did not accept the fastboot commands just like you, so I wiped my data. :crying:
It seems that this guy has succeeded to unbrick Z00A without losing his data. I have not tried this procedure in my Z008 using Z008 raw file yet, so I don't know if this is effective for Z008.
http://forum.xda-developers.com/showpost.php?p=67474121&postcount=210
Serial number restored by Asus Flash Tool, now I can flash with fastboot
Hakataben said:
After flashing Z008 with xFSTK IAW the procedure you tried, the product name in fastboot screen is shown as ASUS_Z00A. After flashing with Asus flashtool, the fastboot screen says correct product number Z008 and corect serial number. :good:
I tried to flash boot.img, droidboot.img, system.img and recovery.img because I did not want to lose my data. Unfortunately, my Z008 did not accept the fastboot commands just like you, so I wiped my data. :crying:
It seems that this guy has succeeded to unbrick Z00A without losing his data. I have not tried this procedure in my Z008 using Z008 raw file yet, so I don't know if this is effective for Z008.
http://forum.xda-developers.com/showpost.php?p=67474121&postcount=210
Click to expand...
Click to collapse
Hello,
Thanks for your answers
I let going Asus Flash Tool for 6 hours, I saw in the Task Manager and on my Zenfone that it used fastboot2 to erase partitions.
Phone said O.K
But it's stuck for 6 hours on a500cgfastboot (these files are here : C:\Program Files (x86)\ASUS\ASUS Flash Tool\Google)
So I think I'll have to reboot phone and PC and retry (I checked integrity of the raw with 7-zip (the raw file is actually a zip file which is unzipped in the folder %USERPROFILE%\.fbrawtempdir) but I'll re-download it...)
Maybe serial number just changed...
Edit after reboot : SO COOL
I discovered that a500cgfastboot was stuck because................................... by erasing some partions, fastboot2 restored the right serial number (I had to restart fastboot to see back my legit serial number)... and it restored product name to Z008
And because a500cgfastboot (and other command ran by Asus Flash Tool) have the old serial 0123456789ABCDEF for argument, a500cgfastboot was no longer finding my phone
I'll retry downloading my img files with fastboot... But I saw Asus Flash Tool cleaned system partition too, but I'll try...
Edit after flashing with fastboot
With the right serial number, everything flashed perfectly with fastboot (but there's one problem : in the Mega folder, there is not the system image for Marshmallow)
so, without system image, my phone boots (ASUS logo, etc...) BUT nothing happens after logo because fastboot2 wiped system :crying: :crying:
I have still access to Fastboot, like before bricking (POWER + VOL UP) (but I can't figure out how to enter in recovery, I've just the droid bot with exclamation mark)
(it's unbricked but no system)
fanfan54 said:
Hello,
Thanks for your answers
I let going Asus Flash Tool for 6 hours, I saw in the Task Manager and on my Zenfone that it used fastboot2 to erase partitions.
Phone said O.K
But it's stuck for 6 hours on a500cgfastboot (these files are here : C:\Program Files (x86)\ASUS\ASUS Flash Tool\Google)
So I think I'll have to reboot phone and PC and retry (I checked integrity of the raw with 7-zip (the raw file is actually a zip file which is unzipped in the folder %USERPROFILE%\.fbrawtempdir) but I'll re-download it...)
Maybe serial number just changed...
Edit after reboot : SO COOL
I discovered that a500cgfastboot was stuck because................................... by erasing some partions, fastboot2 restored the right serial number (I had to restart fastboot to see back my legit serial number)... and it restored product name to Z008
And because a500cgfastboot (and other command ran by Asus Flash Tool) have the old serial 0123456789ABCDEF for argument, a500cgfastboot was no longer finding my phone
I'll retry downloading my img files with fastboot... But I saw Asus Flash Tool cleaned system partition too, but I'll try...
Edit after flashing with fastboot
With the right serial number, everything flashed perfectly with fastboot (but there's one problem : in the Mega folder, there is not the system image for Marshmallow)
so, without system image, my phone boots (ASUS logo, etc...) BUT nothing happens after logo because fastboot2 wiped system :crying: :crying:
I have still access to Fastboot, like before bricking (POWER + VOL UP) (but I can't figure out how to enter in recovery, I've just the droid bot with exclamation mark)
(it's unbricked but no system)
Click to expand...
Click to collapse
If you want to use Marshmallow, I recommend to flash pre-rooted lollipop first, then to flash marshmallow. In your situation, you should unbrick your Z008 at first. After that, you can change system to Marshmallow easily.
Pre-rooted Z008 systems are here. http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
In my case, I needed to have rooted and bootloader-unlocked again to enter in recovery.
Yay!
ASUS Flash Tool flashed the 2.20.40.149 successfully
It's saying "Optimizing app 45 of 119", but I think I had 179 when upgrading to Marshmallow...
And my Android was in french before. But I think I'll be able to fix this
I'll check soon if I've still all my data and apps...
(also, I tried to film everything, if it works I could eventually upload a video tutorial )
Thanks
Another problem... Edit 1
Android boots, I haven't any installation "Welcome" popup because I did not reset it, but as a consequence it crashes at start :
"Unfortunately, android.process.media stopped"
"Unfortunately, android.process.acore stopped"
And it reboots
Maybe it's because these are Marshmallow apps... Will I have to reset it?
Or where can I find system.img for Marshmallow?
Edit 2 Just managed to access to recovery menu
Definitely solved
Solved without losing any data (except settings of some non-system apps)
Hello,
I found on ZenTalk (this thread : http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=78184&pid=392686) a working link to Latest Marshmallow sideload zip for ZE550ML OR ZE551ML. It was the right file, finally.
ZF2/ZE550ML/Z008/Android 6.0.1/WW-4.21.40.54 ~ download --> here.
ZF2/ZE551ML/Z00A/Android 6.0.1/WW-4.21.40.61 ~ download --> here.
Click to expand...
Click to collapse
I sideloaded this file using adb and recovery mode, it worked PER-FECT-LY : my phone just rebooted without any problem, like before the problem. And with latest Marshmallow obviously : I immediately received messages, could access to my pictures, apps, with the same settings than before, in French (just one thing: settings for some non-system apps are reset)
Here is guide of everything I did to unbrick a Marshmallow ZE550ML stuck on USB logo with no bootloader :
(Note: I recommend you to charge your ZenFone for a few hours as soon as you'll get fastboot menu at step 1, so it will not shutdown... Even if it's not turning on the orange LED, it's charging )
(Note also that these are the steps I had to do in order to unbrick MY phone without losing data and installing Marshmallow. For your phone some steps might be unnecessary, if you're lucky... I know this is a very long guide but I had to do this in MY case)
1. Flash basic bootloader with xFSTK Downloader to boot fastboot
I had, first, to switch to advanced startup with support for unsigned drivers (video tutorial here),
install Asus USB drivers (link to Asus USB drivers here - note: video tutorial to install drivers from inf (repeat for every device available : ADB Interface, Bootloader Interface, etc...) )
and IntelSocUSB driver (link to IntelSocUSB driver 1.2.0 - Note: Before finishing IntelSocUSB setup it will ask you to configure a device : you'll have to connect your ZenFone 2 using an USB cable to your computer, while it's displaying USB logo, and WAIT FOR DETECTION IN Device Manager as "Moorefield device" under "Intel Soc" section),
to flash a fastboot bootloader (link to xFSTK_ZE550ML-sal358-amtech.vn for ZE550ML / link to xFSTK_ZE551ML-sal358-amtech.vn for ZE551ML) using xFSTK Downloader (link to xFSTK Downloader 1.7.0) [B
(guides for everything in this step 1: english version - same in vietnamese with screenshots and valid links - detailed PDF for xFSTK with screenshots).[/B] => phone boots on fastboot
2. Flash a lollipop ROM (or Marshmallow raw if you find it) with Asus Flash Tool to repair fastboot info (like serial number) and access recovery if you want to install Marshmallow from a zip
In order to get a working recovery menu (because I found a zip for Marshmallow but no raw, I'll have to install a recovery),
I had to install Asus Flash Tool (link to Asus Flash Tool 1.14 - Note: archive password is www.asus-zenfone.com ),
flash a Lollipop raw (link to WW_ZE550ML_2.20.40.149.raw) on my ZenFone 2 ZE550ML using Asus Flash Tool (Model: ZE550ML - wipe data : no)
(guides for everything in this step 2: english version - same in vietnamese with screenshots and valid links)
BUT because Asus Flash Tool will wipe everything except user data and change your serial number from 0123456789ABCDEF to your legit serial number, flashing will NOT work and process will be ENDLESS because serial number has changed so phone is not found and you're not warned of that by Asus Flash Tool.
After 20 minutes of "OKAY" status displayed in green text on your phone, after 20 minutes of "a500cgfastboot.exe" running in task manager,
I think you can safely unplug USB cable, abort Asus Flash Tool by closing this software, killing "a500cgfastboot.exe",
rebooting phone (notice serial number change in fastboot info on phone's screen) and flash again with same settings but the new serial number (different of 0123456789ABCDEF).
This flash should work, after an hour or less you'll see in Asus Flash Tool that it's finished.
3. Flash Marshmallow zip with adb sideload
Finally, you'll have to shut down your phone,
boot in recovery mode (guide is here),
connect it to computer, select "apply update from adb",
install adb (link to ADB Installer 1.4.3 - Note: install it system-wide but don't install Android USB drivers) on your computer,
download zip OTA for Marshmallow (link to UL-Z008-WW-4.21.40.54-user.zip for ZE550ML / link to UL-Z00A-WW-4.21.40.61-user.zip for ZE551ML),
open a command prompt in the folder where you downloaded files (using "File > Open command prompt > Open command prompt" in the Windows Explorer's ribbon), then type :
Code:
adb devices
to verify that your phone is detected (you should see your serial number in cmd),
then type the following command to flash Marshmallow stock (zip is NOT pre-rooted if you want to root you'll have to do it after) :
ZE550ML
Code:
adb sideload UL-Z008-WW-4.21.40.54-user.zip
ZE551ML
Code:
adb sideload UL-Z00A-WW-4.21.40.61-user.zip
It may take a while decompressing then sending to phone. Then select "wipe cache partition" in your recovery menu,
wait until you see again the menu (so, wait until end of wiping cache), and select "reboot").
Now pray, and your device should magically boot the latest beautiful stock Marshmallow ROM from Asus, with all your data, exactly like before you bricked it.
It worked for me, but with the right new images it should work perfectly for you...
Enjoy this small guide, I hope you'll appreciate hard googling work
Thank you all, my problem is solved
fanfan54 said:
Solved without losing any data (except settings of some non-system apps)
Hello,
I found on ZenTalk (this thread : http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=78184&pid=392686) a working link to Latest Marshmallow sideload zip for ZE550ML OR ZE551ML. It was the right file, finally.
I sideloaded this file using adb and recovery mode, it worked PER-FECT-LY : my phone just rebooted without any problem, like before the problem. And with latest Marshmallow obviously : I immediately received messages, could access to my pictures, apps, with the same settings than before, in French (just one thing: settings for some non-system apps are reset)
Here is guide of everything I did to unbrick a Marshmallow ZE550ML stuck on USB logo with no bootloader :
(Note: I recommend you to charge your ZenFone for a few hours as soon as you'll get fastboot menu at step 1, so it will not shutdown... Even if it's not turning on the orange LED, it's charging )
(Note also that these are the steps I had to do in order to unbrick MY phone without losing data and installing Marshmallow. For your phone some steps might be unnecessary, if you're lucky... I know this is a very long guide but I had to do this in MY case)
1. Flash basic bootloader with xFSTK Downloader to boot fastboot
I had, first, to switch to advanced startup with support for unsigned drivers (video tutorial here),
install Asus USB drivers (link to Asus USB drivers here - note: video tutorial to install drivers from inf (repeat for every device available : ADB Interface, Bootloader Interface, etc...) )
and IntelSocUSB driver (link to IntelSocUSB driver 1.2.0 - Note: Before finishing IntelSocUSB setup it will ask you to configure a device : you'll have to connect your ZenFone 2 using an USB cable to your computer, while it's displaying USB logo, and WAIT FOR DETECTION IN Device Manager as "Moorefield device" under "Intel Soc" section),
to flash a fastboot bootloader (link to xFSTK_ZE550ML-sal358-amtech.vn for ZE550ML / link to xFSTK_ZE551ML-sal358-amtech.vn for ZE551ML) using xFSTK Downloader (link to xFSTK Downloader 1.7.0) [B
(guides for everything in this step 1: english version - same in vietnamese with screenshots and valid links - detailed PDF for xFSTK with screenshots).[/B] => phone boots on fastboot
2. Flash a lollipop ROM (or Marshmallow raw if you find it) with Asus Flash Tool to repair fastboot info (like serial number) and access recovery if you want to install Marshmallow from a zip
In order to get a working recovery menu (because I found a zip for Marshmallow but no raw, I'll have to install a recovery),
I had to install Asus Flash Tool (link to Asus Flash Tool 1.14 - Note: archive password is www.asus-zenfone.com ),
flash a Lollipop raw (link to WW_ZE550ML_2.20.40.149.raw) on my ZenFone 2 ZE550ML using Asus Flash Tool (Model: ZE550ML - wipe data : no)
(guides for everything in this step 2: english version - same in vietnamese with screenshots and valid links)
BUT because Asus Flash Tool will wipe everything except user data and change your serial number from 0123456789ABCDEF to your legit serial number, flashing will NOT work and process will be ENDLESS because serial number has changed so phone is not found and you're not warned of that by Asus Flash Tool.
After 20 minutes of "OKAY" status displayed in green text on your phone, after 20 minutes of "a500cgfastboot.exe" running in task manager,
I think you can safely unplug USB cable, abort Asus Flash Tool by closing this software, killing "a500cgfastboot.exe",
rebooting phone (notice serial number change in fastboot info on phone's screen) and flash again with same settings but the new serial number (different of 0123456789ABCDEF).
This flash should work, after an hour or less you'll see in Asus Flash Tool that it's finished.
3. Flash Marshmallow zip with adb sideload
Finally, you'll have to shut down your phone,
boot in recovery mode (guide is here),
connect it to computer, select "apply update from adb",
install adb (link to ADB Installer 1.4.3 - Note: install it system-wide but don't install Android USB drivers) on your computer,
download zip OTA for Marshmallow (link to UL-Z008-WW-4.21.40.54-user.zip for ZE550ML / link to UL-Z00A-WW-4.21.40.61-user.zip for ZE551ML),
open a command prompt in the folder where you downloaded files (using "File > Open command prompt > Open command prompt" in the Windows Explorer's ribbon), then type :
Code:
adb devices
to verify that your phone is detected (you should see your serial number in cmd),
then type the following command to flash Marshmallow stock (zip is NOT pre-rooted if you want to root you'll have to do it after) :
ZE550ML
Code:
adb sideload UL-Z008-WW-4.21.40.54-user.zip
ZE551ML
Code:
adb sideload UL-Z00A-WW-4.21.40.61-user.zip
It may take a while decompressing then sending to phone. Then select "wipe cache partition" in your recovery menu,
wait until you see again the menu (so, wait until end of wiping cache), and select "reboot").
Now pray, and your device should magically boot the latest beautiful stock Marshmallow ROM from Asus, with all your data, exactly like before you bricked it.
It worked for me, but with the right new images it should work perfectly for you...
Enjoy this small guide, I hope you'll appreciate hard googling work
Thank you all, my problem is solved
Click to expand...
Click to collapse
Man, Today you saved my life and my phone's life . I had exact same problem like yours and I have tried everything to bring my phone back to life last a few days. Today I just noticed your post and it solved my problem perfectly. Thanks man ,really appreciate it ..
muhammed cy said:
Man, Today you saved my life and my phone's life . I had exact same problem like yours and I have tried everything to bring my phone back to life last a few days. Today I just noticed your post and it solved my problem perfectly. Thanks man ,really appreciate it ..
Click to expand...
Click to collapse
Hello,
Thanks for your great feedback muhammed!
Have a nice day!
help me
fanfan54 said:
Hello,
Thanks for your great feedback muhammed!
Have a nice day!
Click to expand...
Click to collapse
please share to my email link WW_ZE550ML_2.20.40.149.raw
[email protected]
tanks before
iwakpauz said:
please share to my email link WW_ZE550ML_2.20.40.149.raw
[email protected]
tanks before
Click to expand...
Click to collapse
Hello, I already sent it to you by email. Here is the link : https://yadi.sk/d/XAUyR8eRtuKdA
Hello,
Sorry for reviving this thread, but I found myself in the same situation. I followed every step, and it works flawlessly. However, after flashing the stock Marshmallow ROM, unlocking the bootloader, flashing TWRP and reinstalling the stock ROM through there, it always bricks my phone (it's the ZE551ML, by the way), so I can't root my device at all. I wonder if anyone has any way of solving this?
I also found that, after unlocking the bootloader, the serial number appears as 0123456789ABCDEF again. I'm pretty much stuck on the stock ROM at this point, with no way of rooting it at all. I can't flash SuperSU through the stock recovery either, it gives me the "signature verification failed" error.
Thanks a lot in advance.
ayuinaba said:
Hello,
Sorry for reviving this thread, but I found myself in the same situation. I followed every step, and it works flawlessly. However, after flashing the stock Marshmallow ROM, unlocking the bootloader, flashing TWRP and reinstalling the stock ROM through there, it always bricks my phone (it's the ZE551ML, by the way), so I can't root my device at all. I wonder if anyone has any way of solving this?
I also found that, after unlocking the bootloader, the serial number appears as 0123456789ABCDEF again. I'm pretty much stuck on the stock ROM at this point, with no way of rooting it at all. I can't flash SuperSU through the stock recovery either, it gives me the "signature verification failed" error.
Thanks a lot in advance.
Click to expand...
Click to collapse
Hello , Firstly , although not clear when you say > "flashing TWRP and reinstalling the stock ROM through there"
1) You can only back up stock rom and restore from TWRP - you cannot flash stock rom from TWRP .
2) Were you bricked and used xFSTK at some point and did you correct serial before upgrading to M ?
signature failed is normal after unlocking bootloader :good:
timbernot said:
Hello , Firstly , although not clear when you say > "flashing TWRP and reinstalling the stock ROM through there"
1) You can only back up stock rom and restore from TWRP - you cannot flash stock rom from TWRP .
2) Were you bricked and used xFSTK at some point and did you correct serial before upgrading to M ?
signature failed is normal after unlocking bootloader :good:
Click to expand...
Click to collapse
Hello, and thank you for the reply!
I'm rather new to this, so I apologize for the possible incorrect terms... I'll try to describe everything as detailed as possible:
My device got bricked, and I sought a solution for it, thus arriving at this thread.
I did every step the OP described to unbrick the device, using xFSTK, *except* rebooting the device after the first flash with ASUS Flash Tool (because when I did, it'd become unresponsive, so I used the flash tool a second time without rebooting and it recovered my serial number).
Next, I went to recovery and installed the Lollipop .zip through adb sideload.
Afterwards, I installed the Marshmallow .zip through adb sideload again.
It's working great this way, but I wanted to root it, so I rebooted into bootloader, and tried to "fastboot boot twrp.img" with no success.
After reading a few more threads, I figured I had to unlock the bootloader before being able to boot into twrp, so I used the bootloader unlocker.
After unlocking it, I was unable to boot into anything but the bootloader (which I presume is normal), so I tried to boot into twrp through fastboot with no success - I had to use "fastboot flash recovery twrp.img" for it to work.
I went into recovery mode, and twrp launched. Since I presumed I had to install Marshmallow from there, due to unlocking the bootloader, I did - through "install .zip".
And after doing that and rebooting the system, it became unresponsive again, - bricked: black screen, only vibrates - thus returning to its initial state.
ayuinaba said:
Hello, and thank you for the reply!
I'm rather new to this, so I apologize for the possible incorrect terms... I'll try to describe everything as detailed as possible:
My device got bricked, and I sought a solution for it, thus arriving at this thread.
I did every step the OP described to unbrick the device, using xFSTK, *except* rebooting the device after the first flash with ASUS Flash Tool (because when I did, it'd become unresponsive, so I used the flash tool a second time without rebooting and it recovered my serial number).
Next, I went to recovery and installed the Lollipop .zip through adb sideload.
Afterwards, I installed the Marshmallow .zip through adb sideload again.
It's working great this way, but I wanted to root it, so I rebooted into bootloader, and tried to "fastboot boot twrp.img" with no success.
After reading a few more threads, I figured I had to unlock the bootloader before being able to boot into twrp, so I used the bootloader unlocker.
After unlocking it, I was unable to boot into anything but the bootloader (which I presume is normal), so I tried to boot into twrp through fastboot with no success - I had to use "fastboot flash recovery twrp.img" for it to work.
I went into recovery mode, and twrp launched. Since I presumed I had to install Marshmallow from there, due to unlocking the bootloader, I did - through "install .zip".
And after doing that and rebooting the system, it became unresponsive again, - bricked: black screen, only vibrates - thus returning to its initial state.
Click to expand...
Click to collapse
Hi again , yes you did everything right up to a point .
You will have to use xFSTK again , flash in aft after till you see ` RESULT = OK ` after a couple of minutes into flash (serial will be incorrect here) ...
Close aft - force close it - keep phone connected through-out -- do not dislodge data cable--- set everything back up in aft again -- then press vol+ once --- your serial will be corrected -- start the flash and let it finish , it will boot into the system related to the raw you flashed.
upgrade like before BUT when in M , use giovix`s Modder tool to unlock bootloader flash, twrp and root etc.
You will be fine ,just remember to back-up stock rom in TWRP first before installing custom LineageOS ,so you can use` return to stock option ` in modder tool after restoring your stock back-up -- to install future updates :good:
timbernot said:
Hi again , yes you did everything right up to a point .
You will have to use xFSTK again , flash in aft after till you see ` RESULT = OK ` after a couple of minutes into flash (serial will be incorrect here) ...
Close aft - force close it - keep phone connected through-out -- do not dislodge data cable--- set everything back up in aft again -- then press vol+ once --- your serial will be corrected -- start the flash and let it finish , it will boot into the system related to the raw you flashed.
upgrade like before BUT when in M , use giovix`s Modder tool to unlock bootloader flash, twrp and root etc.
You will be fine ,just remember to back-up stock rom in TWRP first before installing custom LineageOS ,so you can use` return to stock option ` in modder tool after restoring your stock back-up -- to install future updates :good:
Click to expand...
Click to collapse
Did everything as you told me, but now whenever I "reboot to system", it boots into recovery every time... :\
To clarify, I used the command "fastboot flash recovery twrp_z00a_v24_repack.img", and then installed the latest .zip of SuperSU in TWRP (Install -> SuperSU.zip).
EDIT: Sorry, I mistook Giovix's bootloader unlocker for their full modder tool, I'll be trying that now.
EDIT 2: You saved my butt! Thank you so much for your help, I managed to succeed in everything, finally!
ayuinaba said:
Did everything as you told me, but now whenever I "reboot to system", it boots into recovery every time... :\
To clarify, I used the command "fastboot flash recovery twrp_z00a_v24_repack.img", and then installed the latest .zip of SuperSU in TWRP (Install -> SuperSU.zip).
EDIT: Sorry, I mistook Giovix's bootloader unlocker for their full modder tool, I'll be trying that now.
EDIT 2: You saved my butt! Thank you so much for your help, I managed to succeed in everything, finally!
Click to expand...
Click to collapse
Marvelous stuff. ,its been a pleasure helping you
Happy flashing
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
PS, should see the lengths some people go to restore serial
Why ? Lol When it
Only takes 3 mins max this way
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..
mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.
Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:
Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are
Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising
IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"
I had to fix a couple of bricked selfie phones (z00ud and z00udb but i assume this works on any selfie zd551kl model), that were probably bricked by autoflashing wrong firmware, so after spending a few days going thru many different tutorials, this is my tested method on how to fix them (or if you wanna get a cheap phone from taobao and turn it into a decent one), obviously it wasn't extensively tested, so take it as is . Some steps MIGHT be unnecessary but i didn't want to skip them as i was just glad i found a way how to get the phones to completely stable, latest firmware from useless paperweight.
A. if fone doesnt accept any firmware,or bricked,bootlooped etc. flash basic CN firmware, regardless is recovery WW or CN
- Instructions:
1. go to phone recovery (PWR button + VolDwn, release PWR on logo)
2. on phone select adb bootloader, it switches to fastboot mode (or hold PWR button + VolUp, release PWR on logo)
3. on PC unzip archive and start the autoflash .bat file
4. start the phone
files: archive (Asus Zenfone Selfie Z00UDB ZD551KL 3+16 here )
B. upgrade CN/WW firmare to latest version
- Instructions:
1. on PC install adb drivers
2. go to phone recovery (PWR button + VolDwn, release PWR on logo)
3. on phone select adb sideload
4. on PC, copy firmwares into adb folder
5. on PC go to adb folder and start cmd in that folder (shift+Rclk)
6. type adb devices to check connection, then adb sideload firmwarename.zip
7. start the phone
8. repeat all steps until latest CN/WW firmware is installed
files: adb drivers adb-setup-1.4.3 here , firmwares here(UL-Z00T-CN-1.13.40.661-user,UL-Z00T-CN-1.14.40.695-user,UL-Z00T-CN-1.15.40.1548-user)
C.swap CN firmware for WW, upgrade to Android 6
- Instructions: (also someone elses crappy YT video instructions here )
1. on PC install vc x86 and x64 redist packages for 2010,2012,2013 to prevent .ddl missing errors when running flashtool
1. on PC install asus flash tool
3. on fone turn on usb debugging in developer settings (click on about>sw info>build number)
4. turn off fone then start it in fastboot mode (hold PWR button + VolUp, release PWR on logo)
5. connect the fone to PC, start the autoflash .bat file from the firmware folder (CSC_ZD550KL_1_2_0_70_fac_eng_20150905_secure)
6. disconnect usb, wait for fone to reboot, then disconnect the battery on boot logo (remove back cover in advance)
7. return the battery, and start the fone again in fastboot mode, check for extra info on screen
8. on PC start the flashtool, connect the fone in fastboot mode, check if connected, select the model (ZD551KL), select wipe data
9. on PC, browse to firmware (WW_ZD551KL_1.15.40.1582-bsp-user-20160510203701-secured-release) in flashtool, click start, chose Yes for both options (wipe and image promt), wait until flashing is over
10. disconnect and start the fone
11. connect the fone to PC, copy the firmware (UL-Z00T-WW-21.40.0.1692-user) to internal memory or SD card and wait for the fone to recognize the package and auto-update to Android 6
12. connect the fone to PC, copy any newer firmware to internal memory or SD card (no need to copy next iteration or 2156 build, you can go to for ex. 2214 build right away) wait for the fone to recognize the package and auto-update to newer build of Android 6
files: vc redist packages here , firmwares (WW_ZD551KL_1.15.40.1582-bsp-user-20160510203701-secured-release here,CSC_ZD550KL_1_2_0_70_fac_eng_20150905_secure here), Android 6 firmwares here
Are those steps A,B and C and we should follow everything or methods and just follow only 1? I have a Z00UD Asus Model phone, should I still use the firmware Z00UDB from step A? Thank you!!
jasonch said:
Are those steps A,B and C and we should follow everything or methods and just follow only 1? I have a Z00UD Asus Model phone, should I still use the firmware Z00UDB from step A? Thank you!!
Click to expand...
Click to collapse
Depending on your issues, you should pick the step you need, in case nothing works on your phone start with step A, otherwise start with the step that is appropriate for your problem.
Thanks for this guide. Tried this but get stuck at FRP of ASUS. Google mail was on previous owner. Any solutions?
can flash .zip via TWRP?
dhonxean said:
Thanks for this guide. Tried this but get stuck at FRP of ASUS. Google mail was on previous owner. Any solutions?
Click to expand...
Click to collapse
not sure i understand, are you saying your phone is locked with the account from the previous owner ? if so then just do a factory reset from recovery and setup with your own account.
witopanjoel said:
can flash .zip via TWRP?
Click to expand...
Click to collapse
What zip exactly, some should be done like in the tutorial, others can be flashed from recovery
I use the bootloader from your archive on a Z00UD and it is bricked (will remain on Asus screen)...
Do you have a Z00UD bootloader?
may phone is bricked itry this and now my phone is in boot loop..
z00ud ZD551KL
firmwares are not already available on the websites, do you have any other website that has those files?
asus z00ud, soft bricked by wrong flash, now not turning on, display black, only vibrate when plug in charger or press the power button. Please help.
My asus zenfone selfie model become asus zenfone go. How do i fix this? Any help please.
Need Asus Zenfone Selfie Z00UD Hard Brick/Dead Boot Repair Solution
Z00UD Flash After set dead show Qualcomm HS-USB QDLoader 9008 How To Solve? Help Me
READ EVERYTHING CAREFULLY!
1.Your phone warranty will be void after this tutorial!
2.Any small mistake and your phone is bricked/bootlooped!
3.All of your data will be lost so back it up somewhere
Click to expand...
Click to collapse
(Fixed the tutorial my bad.)
Click to expand...
Click to collapse
Hey Guys Im Back! Thank you for the support and how it blew up. I have tested this on Android 10 UI 2.0 and it works better then ever!
Also installed lineage os : https://forum.xda-developers.com/galaxy-a10/development/rom-lineage-os-a10-a105f-t4078093
So i tried using afaneh92's tutorial which will be linked here : https://forum.xda-developers.com/galaxy-a10/how-to/magisk-root-galaxy-a10-series-t3963822
Which lead to me bootlooping or softbricking and my storage was reduced from 32 gb to 16Gb so i decided to work on my own method!
Credits go to afaneh92 for the Twrp!
BEFORE YOU START YOU SHOULD HAVE
1.Samsung Drivers installed
2.Odin Installed
3.7zip Installed
4.A data transfer cable
5.A Proper working brain
If you have all of those lets start!
A: Phone settings
1.Go in settings>about phone>software information>build number tap that 5 times until it says "You are a developer now" then you will have Developer options unlocked
2.Then go in developer functions and find OEM unlocking tick that on scroll down until you see Usb Debugging and tick that also Disable Auto Updates option
B: Download TWRP and 2 other important files
1.Dial *#1234# and it will show the AP and some others, focus on AP paste it on google and get the download for it
2.After downloaded move the AP to your download folder in your android device
3.You will get a magisk_patched.tar after its been offically converted
4.Get the twrp for a10
Download the twrp file here : https://mega.nz/#!OU1WhSDZ!vQz5K1wpqBhg0hCD59aziaHPxFlUsT_2WG8SgT8p6iY
5.After you got everything open the .tar archive and extract vbmeta.img, boot.img and you should already have recovery.img on your Desktop
6.Grab all the 3 .img files and archive them into a .tar using 7zip, Now continue to step C,
C :Unlocking The Bootloader and Getting Into Download Mode (THE PART WHERE YOU RESET YOUR PHONE)
1.Turn Off your phone
1.2.Put your data cable into your PC(dont connect your phone to it yet)
1.3.Hold Volume Up and Down then insert the cable into your phone
1.4.When you see a bluescreen let go
1.5.Hold vol up until you see another screen then let go for 1 second and hold vol up again
2.Your device will reset itself and reboot
2.1.After the device has booted in into the setup take the cable out after Turn off your phone
2.2.Hold Vol Up and Down again and connect the cable
2.3.Let go when a blue screen appears then press vol up until you are in download mode
D: Flashing TWRP
1.Open Odin
2.Press on AP then find Desktop.tar and press open
3.Press start and let it do its thing
4.After your Phone has rebooted you oficially have TWRP installed
5.If you want to know hoe to root go to step E
E: Installing Magisk
Since magisk is counted as the best rooting option rn i will be using it in this tutorial(Sorry supersu fans)
1.Install Magisk Manager
2.Press on Install (first one) then press install again and after that press Install Zip Only
3.Then go into Twrp by doing the steps below
3.1.Turn off your device
3.2.Hold vol up and power button untill you see TWRP logo
4.Press install
4.1.Find magisk-v20.4(20400).zip
4.2Swipe right on the bottom to flash it then press reboot system now.
5.Now you have TWRP,Root and Magisk Congratulations!
What happens if something goes wrong.
1.SV Error Device 1 library 0 - You installed the wrong firmware look for the right firmware.To check go in recovery mode and look at the A105XXXXXX and then look for a download. Remider AP->AP BL->BL CP->CP HOME_CSC->CSC
2.vbmeta.img error - you have the wrong vbmeta.img file. Redownload the original firmware and take out the right vbmeta.img next time you try flashing. Reminder AP->AP BL->BL CP->CP HOME_CSC->CSC
3.A blue screen telling you to use samsung switch emergency update. That wont work so just flash the original firmware and try flashing twrp again.
4.When i try to boot in it gets me into TWRP - Thats just because that your data is corrupted and to fix it while in TWRP mode press wipe then swipe after its done press Reboot To System. That should be a fix
5.My internal storage is just full of weird numbers and I can't download anything on it! Go in TWRP then wipe,press advanced wipe, click on internal storage and data, swipe. That should fix the error
6.Boootlooping or Bricked! Installed corrupted firmware or the recovery was f-ed up. Then install the right firmware and redo the steps!
If you have issues during the process send it in the comment ill try to respond as fast as i can!
i notice thread title says exynos only.. u do know they are all exynos including a102u and a102u1 right?
Oh. Alright thanks for telling me.
Press on app? I have nothing in odin saying that, do you mean ap?
Edit: guess not....i'm bricked, stuck on galaxy logo, device not recognized by pc, holoding power button wont force reboot, nothing lol.
Edit2: can force reboot holding volume down and power but instantly stuck on logo again, cannot power off or enter download, nothing...bricked. Followed this guide to the letter. I assumed when you said app in odin you meant ap since there is no app button. My bootloader unlocked then I went to flash in odin the tar i made with patched boot and vbmeta, along with recovery linked. I used matching firmware to what my A10 has also. Would not mind if i could get back into download mode, but that looks impossible now.
Edit3: Managed to get download mode but had to be so quick...hopefully I can reflash stock now.
Cupcake 1.5 said:
Press on app? I have nothing in odin saying that, do you mean ap?
Edit: guess not....i'm bricked, stuck on galaxy logo, device not recognized by pc, holoding power button wont force reboot, nothing lol.
Edit2: can force reboot holding volume down and power but instantly stuck on logo again, cannot power off or enter download, nothing...bricked. Followed this guide to the letter. I assumed when you said app in odin you meant ap since there is no app button. My bootloader unlocked then I went to flash in odin the tar i made with patched boot and vbmeta, along with recovery linked. I used matching firmware to what my A10 has also. Would not mind if i could get back into download mode, but that looks impossible now.
Edit3: Managed to get download mode but had to be so quick...hopefully I can reflash stock now.
Click to expand...
Click to collapse
Im sorry for that and yes i meant AP.
If you wanted to reboot you had to hold vol up vol down and power at the same time and you sure that you unlocked the bootloader and used the right firmware?
Also tell me the AP and from which source have you downloaded it :laugh:
cmz6996 said:
Im sorry for that and yes i meant AP.
If you wanted to reboot you had to hold vol up vol down and power at the same time and you sure that you unlocked the bootloader and used the right firmware?
Also tell me the AP and from which source have you downloaded it :laugh:
Click to expand...
Click to collapse
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.
Cupcake 1.5 said:
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.
Click to expand...
Click to collapse
Oh! Im happy to hear that!
Cupcake 1.5 said:
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.
Click to expand...
Click to collapse
Could you also tell me from where have you downloaded the corrupted firmware so i can warn the others?
cmz6996 said:
Could you also tell me from where have you downloaded the corrupted firmware so i can warn the others?
Click to expand...
Click to collapse
The corruption was my side, I was using a download manager, but when I downloaded through chrome it was all good. As I said, schoolboy error on my part for not checking md5. I used sammobile site for the firmware.
Cupcake 1.5 said:
The corruption was my side, I was using a download manager, but when I downloaded through chrome it was all good. As I said, schoolboy error on my part for not checking md5. I used sammobile site for the firmware.
Click to expand...
Click to collapse
Alr thanks.
Can you upload it to Mediafire? Mega marks a "temporal error"...
Kyua said:
Can you upload it to Mediafire? Mega marks a "temporal error"...
Click to expand...
Click to collapse
At me it works?
Works on a105m?
Axeggus said:
Works on a105m?
Click to expand...
Click to collapse
Yes
i receive message that i running samsumg not official firmware after odin install recovery.tar
not work
cmz6996 said:
So i tried using afaneh92's tutorial which will be linked here : https://forum.xda-developers.com/galaxy-a10/how-to/magisk-root-galaxy-a10-series-t3963822
Which lead to me bootlooping or softbricking and my storage was reduced from 32 gb to 16Gb so i decided to work on my own method!
Credits go to afaneh92 for the Twrp!
BEFORE YOU START YOU SHOULD HAVE
1.Samsung Drivers installed
2.Odin Installed
3.7zip Installed
4.A data transfer cable
5.A Proper working brain
If you have all of those lets start!
A: Phone settings
1.Go in settings>about phone>software information>build number tap that 5 times until it says "You are a developer now" then you will have Developer options unlocked
2.Then go in developer functions and find OEM unlocking tick that on scroll down until you see Usb Debugging and tick that also Disable Auto Updates option
B: Download Your firmware and TWRP
1.Go in your calls app and dial *#1234# Then You will receive some details about your AP, CP etc. look at the AP then download the firmware by searching it on google and (download it from sites like sammobile etc)
2.After you got your firmware connect your device to your pc after its connected send the entire firmware to the device in the Downloads folder
2.1. Install Magisk Manager
3.After you're in magisk manager press on install (first one) then press install again then press Select and Patch a File
3.1.Chose the firmware you saved on the Downloads folder
3.2.After you tap on it it should've already started modifying it
4.After it finished go back to your pc and move the magisk_patched.tar back to your desktop (It should be located in Downloads)
5.From the magisk_patched.tar extract boot.img and vbmeta.img to your desktop
5.1.Download the twrp file here : https://mega.nz/#!OU1WhSDZ!vQz5K1wpqBhg0hCD59aziaHPxFlUsT_2WG8SgT8p6iY
5.2.After recovery.img(TWRP) has been downloaded move it to your desktop
5.3.Select all those three items(vbmeta.img,recovery.img,boot.img) right click then Find 7Zip then press add to archive
5.4.Rename the Archive name to recovery.tar and make sure the archive format is .tar
6.After the Archive has been downloaded follow the steps in C
C :Unlocking The Bootloader and Getting Into Download Mode (THE PART WHERE YOU RESET YOUR PHONE)
1.Turn Off your phone
1.2.Put your data cable into your PC(dont connect your phone to it yet)
1.3.Hold Volume Up and Down then insert the cable into your phone
1.4.When you see a bluescreen let go
1.5.Hold vol up until you see another screen then let go for 1 second and hold vol up again
2.Your device will reset itself and reboot
2.1.After the device has booted in into the setup take the cable out after Turn off your phone
2.2.Hold Vol Up and Down again and connect the cable
2.3.Let go when a blue screen appears then press vol up until you are in download mode
D: Flashing TWRP
1.Open Odin
2.Press on AP then find recovery.tar and press open
3.Press start and let it do its thing
4.After your Phone has rebooted you oficially have TWRP installed
5.If you want to know hoe to root go to step E
E: Installing Magisk
Since magisk is counted as the best rooting option rn i will be using it in this tutorial(Sorry supersu fans)
1.Install Magisk Manager
2.Press on Install (first one) then press install again and after that press Install Zip Only
3.Then go into Twrp by doing the steps below
3.1.Turn off your device
3.2.Hold vol up and power button untill you see TWRP logo
4.Press install
4.1.Find magisk-v20.4(20400).zip
4.2Swipe right on the bottom to flash it then press reboot system now.
5.Now you have TWRP,Root and Magisk Congratulations!
What happens if something goes wrong.
1.SV Error Device 1 library 0 - You installed the wrong firmware look for the right firmware.To check go in recovery mode and look at the A105XXXXXX and then look for a download. Remider AP->AP BL->BL CP->CP HOME_CSC->CSC
2.vbmeta.img error - you have the wrong vbmeta.img file. Redownload the original firmware and take out the right vbmeta.img next time you try flashing. Reminder AP->AP BL->BL CP->CP HOME_CSC->CSC
3.A blue screen telling you to use samsung switch emergency update. That wont work so just flash the original firmware and try flashing twrp again.
4.When i try to boot in it gets me into TWRP - Thats just because that your data is corrupted and to fix it while in TWRP mode press wipe then swipe after its done press Reboot To System. That should be a fix
5.My internal storage is just full of weird numbers and I can't download anything on it! Go in TWRP then wipe,press advanced wipe, click on internal storage and data, swipe. That should fix the error
6.Boootlooping or Bricked! Installed corrupted firmware or the recovery was f-ed up. Then install the right firmware and redo the steps!
If you have issues during the process send it in the comment ill try to respond as fast as i can!
Click to expand...
Click to collapse
hi guy... very good guide but it not work for my galaxy a10 ....i only have unlock the bootloader... if i try to get patched recovery ... it not work.... i have device blocked black screen for samsung software... or i cant go recovery mode it say me a error of vbmeta)
andrea2o18 said:
hi guy... very good guide but it not work for my galaxy a10 ....i only have unlock the bootloader... if i try to get patched recovery ... it not work.... i have device blocked black screen for samsung software... or i cant go recovery mode it say me a error of vbmeta)
Click to expand...
Click to collapse
You installed the wrong fir.ware check your right firmware.
BlueFolks said:
i receive message that i running samsumg not official firmware after odin install recovery.tar
Click to expand...
Click to collapse
Be cause you modified the firmware ignore that message
have you fixed the storage reduced to 16gb problem?
I have a Samsung galaxy sm-a10. I've tried everything here, even combination files. The error I ALWAYS get is 'failed flashing ROM... OEM lock'
Of course I have unlocked OEM in developer options, but still I get this error in the bootloader.
Any ideas?