[GUIDE] Restoring Stock ROM, Recovery, Unbrick, and Rooting 5.0 on Padfone S - Asus Padfone X and S
I had stuck on ASUS logo, after I do a lot of researches, a lot of trials and errors for 4 hours. I managed to fix them and I wanted to share how I did here.
Easiest way to root lollipop WW-12.2.2.27
use KingRoot from http://www.kingroot.net/down ,It is android app which will run exploit to root the device successfully.
Not Kingoroot Kingoroot was unable to root. Towelroot v1 works only on Kitkat, but not lollipop.
To boot into fastboot mode
adb reboot bootloader
OR turn off device, press and hold power and volume up, until asus logo appear, and stuck at asus logo, that is fastboot mode, to exit fastboot with buttons, press and hold vol down and power button.
To restore stock recovery and ROM after you install TWRP or CWM, or unbrick device
First, note that stock recovery from http://forum.xda-developers.com/showpost.php?p=59055653&postcount=29, does not work for me (maybe everyone else as well).
I flashed it using fastboot flash recovery recovery.img, when I try to boot into recovery using, vol down and power, then select enter recovery, it stucks at asus logo.
First you need to flash TWRP_2.8.7.0.img from http://quarx2k.ru/asus_padfone_s/recovery/
using fastboot flash recovery TWRP_2.8.7.0.img It will show that flashing FAILED (remote: can't flash unsigned image), it fact, it was succeeded, now you can go ahead and boot to recovery.
Note that this version of TWRP, and 2.8.6.0, and CWM cannot successfully flash stock zip ROM, it may show errors, or when you try to boot the device, it will stuck at ASUS logo. But now, we are going to need TWRP_2.8.7.0 to unlock bootloader.
Let's unlock bootloader
simply flash http://quarx2k.ru/asus_padfone_s/CrowLock_RC3.zip with TWRP
You can check bootloader status with fastboot oem device-info
Before unlock :
(bootloader) Device unlocked: false
After unlock
(bootloader) Device unlocked: true
Let's flash stock Kitkat Firmware
You have to unlock bootloader becuase, well it is complicated.
The only TWRP recovery that can successfully flash stock .zip firmware from ASUS is http://datbak.com/links/padfone_s/asus_t00n_twrp_2_7_1_1.img
But this recovery has another bug, if you flash recovery and try to boot to recovery, you will get blank screen, but TWRP is indeed working, you touch the screen and it vibrates back. Anyway you have tofastboot flash recovery asus_t00n_twrp_2_7_1_1.img because it will be needed later for upgrading Kitkat to Lollipop.
If you don't unlock bootloader, you will not be able to boot into recovery directly without flashing to recovery partition Now let's get into fastboot mode, and fastboot boot asus_t00n_twrp_2_7_1_1.img, by booting into this recovery directly via fastboot without flashing it first, you will not get black screen bug of this recovery., if you boot to this recovery from recovery partition, you will get black screen as I told previously.
Now let's flash downgrade to 4.4.2 firmware from http://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone_S/UL-ASUS_T00N-WW-99.99.99.0-user-wipedata.zip with TWRP 2.7.1.1.
This is for only WW SKU, not TW SKU. And all userdata will be wiped.
Browse all firmwares and there is TW SKU downgrade here : https://www.asus.com/Phone/PadFone_S_PF500KL/HelpDesk_Download/
Ok, now reboot to system, and yeah, it finally boots now.
The recovery is still TWRP, not stock one, let's upgrade to lollipop and restore stock recovery using TWRP. Simply place http://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone_S/UL-ASUS_T00N-WW-12.2.2.27-user.zip to root of Internal Memory, unplug usb, press confirmation in notification to begin install lollipop. After device reboot, it will stay blank screen for 5 minutes, don't worry, it is updating to lollipop, after upgrade is done, it will reboot, and recovery will be restored to stock recovery now.
Bootloader is still unlocked.
Another method to root is
fastboot flash recovery asus_t00n_twrp_2_7_1_1.img (recovery is restored to stock now remember)
then flash https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 with TWRP.
To lock bootloader again, boot into fastboot
then fastboot oem reset-dev_info
But I wouldn't recommend you to lock bootloader, you will lose ability to boot to TWRP recovery without replacing stock recovery, unless you are going to send your device to service center and claim warranty.
Files, fastboot and recoveries and bootloader unlock and super su for rooting
asus_t00n_twrp_2_7_1_1.rar https://mega.nz/#!355UmTCb!0Jn-0wlbGHG7lir8u9vq1l8BrR3dsepDdigqfJ9wRPk
twrp_2.8.7.0.rar https://mega.nz/#!GwRRBBjT!8ms39GK62XHairHOrxlmNJCwA-bDeaKA816Cg4lsQr0
Will this work for S Plus model?
It wont, using files from this thread might brick the device.
Sent from my SM-N910C using XDA Free mobile app
Hi im a noob so ill get straight to the point.
You said "Note that this version of TWRP, and 2.8.6.0, and CWM cannot successfully flash stock zip ROM, it may show errors, or when you try to boot the device, it will stuck at ASUS logo."
I have two question as follow:
1. So can i use twrp to flash stock rom or not?
2. Because I'm still at Kit Kat, I dont need to unlock bootloader and flash Kit Kat firmware right?
3. If so, Can I follow the tutorial until flashing the TWRP? but which TWRP that I need to install?
4. All these tutorial to unbrick needs to be done before you brick your phone right? What should i do if i already brick my phone?
Kindly advise.
ChevanLemon said:
Hi im a noob so ill get straight to the point.
You said "Note that this version of TWRP, and 2.8.6.0, and CWM cannot successfully flash stock zip ROM, it may show errors, or when you try to boot the device, it will stuck at ASUS logo."
I have two question as follow:
1. So can i use twrp to flash stock rom or not?
2. Because I'm still at Kit Kat, I dont need to unlock bootloader and flash Kit Kat firmware right?
3. If so, Can I follow the tutorial until flashing the TWRP? but which TWRP that I need to install?
4. All these tutorial to unbrick needs to be done before you brick your phone right? What should i do if i already brick my phone?
Kindly advise.
Click to expand...
Click to collapse
The only TWRP recovery that can successfully flash stock .zip firmware from ASUS is asus_t00n_twrp_2_7_1_1.img
If you are bricked, but you can still access fastboot mode, then you can unbrick and reflash stock firmware to your phone
First of all, Thank you so much for this GUIDE
Here are my doubts, and hoping for confirmation from you. My Padfone S is running well on latest kitkat firmware, rooted with SuperSu and TWRP 2.7.1.1 installed. Now, I wished to upgrade to Lollipop firmware.
Can I use the TWRP 2.7.1.1 to clean install the lollipop firmware instead of the stock recovery because I wished to wipe date, cache as well as SYSTEM before flashing?
My concern is I afraid if wipe the SYSTEM then the TWRP 2.7.1.1 would not be able to flash the Lollipop firmware successfully. Do I need to unlock bootloader in my case?
If I can do so, then can I still use the Flashify to flash TWRP 2.7.1.1 on the lollipop firmware, or I must use "fastboot flash recovery TWRP_2.8.7.0.img" method.
Thanks in advance for your kindly reply.:laugh:
Bootlooped
When I am upgrading my SuperSU and it requires a reboot,it automatically boot looped itself.
What should I do?
Linux4ever85 said:
Will this work for S Plus model?
Click to expand...
Click to collapse
Yes it work. Mine is Asus Padfone S Plus. Got bootloop problem. I have followed ninekaw guide. Thanks Ninekaw. U have save my precious padfone s plus
ninekaw9 said:
I had stuck on ASUS logo, after I do a lot of researches, a lot of trials and errors for 4 hours. I managed to fix them and I wanted to share how I did here.
Easiest way to root lollipop WW-12.2.2.27
use KingRoot from http://www.kingroot.net/down ,It is android app which will run exploit to root the device successfully.
Not Kingoroot Kingoroot was unable to root. Towelroot v1 works only on Kitkat, but not lollipop.
To boot into fastboot mode
adb reboot bootloader
OR turn off device, press and hold power and volume up, until asus logo appear, and stuck at asus logo, that is fastboot mode, to exit fastboot with buttons, press and hold vol down and power button.
To restore stock recovery and ROM after you install TWRP or CWM, or unbrick device
First, note that stock recovery from http://forum.xda-developers.com/showpost.php?p=59055653&postcount=29, does not work for me (maybe everyone else as well).
I flashed it using fastboot flash recovery recovery.img, when I try to boot into recovery using, vol down and power, then select enter recovery, it stucks at asus logo.
First you need to flash TWRP_2.8.7.0.img from http://quarx2k.ru/asus_padfone_s/recovery/
using fastboot flash recovery TWRP_2.8.7.0.img It will show that flashing FAILED (remote: can't flash unsigned image), it fact, it was succeeded, now you can go ahead and boot to recovery.
Note that this version of TWRP, and 2.8.6.0, and CWM cannot successfully flash stock zip ROM, it may show errors, or when you try to boot the device, it will stuck at ASUS logo. But now, we are going to need TWRP_2.8.7.0 to unlock bootloader.
Let's unlock bootloader
simply flash http://quarx2k.ru/asus_padfone_s/CrowLock_RC3.zip with TWRP
You can check bootloader status with fastboot oem device-info
Before unlock :
(bootloader) Device unlocked: false
After unlock
(bootloader) Device unlocked: true
Let's flash stock Kitkat Firmware
You have to unlock bootloader becuase, well it is complicated.
The only TWRP recovery that can successfully flash stock .zip firmware from ASUS is http://datbak.com/links/padfone_s/asus_t00n_twrp_2_7_1_1.img
But this recovery has another bug, if you flash recovery and try to boot to recovery, you will get blank screen, but TWRP is indeed working, you touch the screen and it vibrates back. Anyway you have tofastboot flash recovery asus_t00n_twrp_2_7_1_1.img because it will be needed later for upgrading Kitkat to Lollipop.
If you don't unlock bootloader, you will not be able to boot into recovery directly without flashing to recovery partition Now let's get into fastboot mode, and fastboot boot asus_t00n_twrp_2_7_1_1.img, by booting into this recovery directly via fastboot without flashing it first, you will not get black screen bug of this recovery., if you boot to this recovery from recovery partition, you will get black screen as I told previously.
Now let's flash downgrade to 4.4.2 firmware from http://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone_S/UL-ASUS_T00N-WW-99.99.99.0-user-wipedata.zip with TWRP 2.7.1.1.
This is for only WW SKU, not TW SKU. And all userdata will be wiped.
Browse all firmwares and there is TW SKU downgrade here : https://www.asus.com/Phone/PadFone_S_PF500KL/HelpDesk_Download/
Ok, now reboot to system, and yeah, it finally boots now.
The recovery is still TWRP, not stock one, let's upgrade to lollipop and restore stock recovery using TWRP. Simply place http://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone_S/UL-ASUS_T00N-WW-12.2.2.27-user.zip to root of Internal Memory, unplug usb, press confirmation in notification to begin install lollipop. After device reboot, it will stay blank screen for 5 minutes, don't worry, it is updating to lollipop, after upgrade is done, it will reboot, and recovery will be restored to stock recovery now.
Bootloader is still unlocked.
Another method to root is
fastboot flash recovery asus_t00n_twrp_2_7_1_1.img (recovery is restored to stock now remember)
then flash https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 with TWRP.
To lock bootloader again, boot into fastboot
then fastboot oem reset-dev_info
But I wouldn't recommend you to lock bootloader, you will lose ability to boot to TWRP recovery without replacing stock recovery, unless you are going to send your device to service center and claim warranty.
Click to expand...
Click to collapse
simply flash http://quarx2k.ru/asus_padfone_s/CrowLock_RC3.zip with TWRP --> link dead
Hi thank for your guidance on how restoring stock rom . Im having trouble detecting my phone when in fastboot mode, as you said to boot up into fastboot hold vol up and power and we will stuck at asus logo , but after i connect my pc and using adb cmd fastboot devices it didnt detect any devices and cant proceed to next step when i need to fastboot boot twrp 2.7.1.1
Currently im using twrp 2.8.7.0 , i want to use stockcrom because i need to use my padfone station (since any custom rom is not compatible with padfone station), any suggestions for this problem ? Thanks in advabce
Related
[Q] Stuck On Sony Screen
I have the castor windy version 16gb SGP511. I was previously rooted but not unlocked. I unlocked the boot loader. Installed the twrp image on the pac man thread which i think was dual recovery cause Philz,Cwm came out, so I can install lollipop version of the rom. Made a backup of the stock rom. Followed this instructions - Install the Lollipop ROM + GApps+SuperSU using whatever Recovery you have. - Turn off device completely. - Press <Volume Up> and plug USB cable. - LED should turn blue. - Send command: "fastboot erase recovery" - Send command for Castor_Windy: "fastboot flash recovery TWRP_Castor_Windy.img" - Send command for Castor: "fastboot flash recovery TWRP_Castor.img" - Unplug USB cable. - Device will reboot. - When LED turns pink press <Volume Up> and <Volume Down> several times. - You should now see TWRP I wasnt fast enough so stock rom booted. I used Adb reboot recovery to access recovery and did as the above mentioned. Wiped i tried to install the rom which failed. Rebooted back to system and got stuck in Sony boot up screen. I can access fastboot. Read though the forums I have to find a ftf or a system image file and use a flash tool. What ftf file or system image my I use use which will let me root my device again. Thanks Steve
Kamaleon said: What ftf file or system image my I use use which will let me root my device again. Thanks Steve Click to expand... Click to collapse Try this Xperia downloader tool. Should let you see which versions are which. If you want an easy root, then stay away from the KitKat builds, unless you want to unlock bootloader. http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142 Use Flashtool to flash your downloaded ftf file. Just make sure your device is charged. http://forum.xda-developers.com/showthread.php?t=2335555 I believe flashtool will even install the drivers for your 511
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Kamaleon said: Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already? Click to expand... Click to collapse Well, now this depends. If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again. If you flashed the same version as you had previously installed, then it didn't lock it again.
Moscow Desire said: Well, now this depends. If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again. If you flashed the same version as you had previously installed, then it didn't lock it again. Click to expand... Click to collapse Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Kamaleon said: Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL. Click to expand... Click to collapse You mean the "factory" recovery comes up. Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing. Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff. As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Moscow Desire said: You mean the "factory" recovery comes up. Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing. Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff. As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs. Click to expand... Click to collapse I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Kamaleon said: I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply. Click to expand... Click to collapse Well, here's what I think is going on. 1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there. 2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence. Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with. What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery. Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware. Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery. MD
Moscow Desire said: Well, here's what I think is going on. 1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there. 2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence. Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with. What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery. Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware. Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery. MD Click to expand... Click to collapse I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided 1. Make sure you have CWM installed and a working nandroid backup 2. Download the ROM. 3. Place the ROM on your SD-Card. 4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD 5. Reboot to recovery. 6. Wipe data-factory reset/cache partition/dalvik cache 7. Flash the ROM. Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Kamaleon said: I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided 1. Make sure you have CWM installed and a working nandroid backup 2. Download the ROM. 3. Place the ROM on your SD-Card. 4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD 5. Reboot to recovery. 6. Wipe data-factory reset/cache partition/dalvik cache 7. Flash the ROM. Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help. Click to expand... Click to collapse Well, I'm not sure which route to take. However, I will tell you what I have learned the other day. I have the 521 with unlocked bootloader. Rooted with my own boot.img, flashed SuperSU using "flashboot boot recovery.img" (yeah, sometimes it doesn't show on the display, so it takes a few times). Now, other day I was going to check out the new LyPop pre-rooted. Fastboot flash recovery recovery,img, and it won't boot it to recovery like it should. Like it's not flashed. Tried it a couple times. Now, I didn't install the dual recovery as I'm not sure how that kernel (boot.img) will interact with my current tabs OS. Not to mention I need it for my work until tomorrow. But strangely it sounds like the same issue you have. This weekend I will investigate it. As for me, I will probably flash the Stock ftf lyPop build, and just root it using a modified boot.img. One thing I do know, is flashing a custom recovery to the "recovery" partition, doesn't seem to work like it used to work on other devices. It seems the flashing to the "Fota kernel" partition seems to be the only method that works. This is what happens when you flash that dual recovery, or any recovery that has a boot image using "Fota". Probably explains why you can't get rid of it using "fastboot erase recovery". because it's erasing the wrong partition. Only flashing a full ftf gets rid of it, because the ftf has a new FotaKernel it flashes. Eh, something like that. Will look at it this weekend.
Please Help! I have soft bricked my OnePlus X!!
Hi. I have had the OnePlus X for a very long time, and I have recently bricked . Ok, here it goes :fingers-crossed:. I had a OnePlus X running CM13 with TWRP but a locked bootloader. I decided to try cyanogenmod recovery but soon realized it was terrible. I was unable to flash img. files and the UI was unappealing to me. However at that point I was able to reboot into my ROM (CM13) with no issues. Knowing this, I thought that the only way I could get TWRP back was through a fastboot command (fastboot flash recovery recovery.img). For me to execute that command, I needed to unlock my bootloader first, so I took all the necessary steps in the developer options settings menu. I then booted into fastboot mode and executed this command: fastboot oem unlock. This was my big mistake, as I read up after that you should not unlock bootloader on a custom recovery. After executing this command, it booted me into recovery. I tried many times without success to wipe data and flash a rom zip via external sd card but they never worked. To make things worse, I was unable to boot up the device. Whenever I tried to power on the device, it booted straight into recovery. I am able to boot into fasboot and recovery, but that is pretty much it. Can someone please help me? I am willing to donate.
If you were able to flash the Cyanogen recovery with a locked bootloader you should be able to flash the official OPX recovery as well. You can download that from this link: https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img Then you should be able to unlock the bootloader!
Or if @Tanner1294's doesn't help, flashing stock rom via fastboot will surely help.. PS: Don't ever flash anything on a locked bootloader.
Tried flashing TWRP, but stays stuck on/replace by stock recovery no matter what Itry
No matter how I try to flash the TWRP recovery image to the recovery partition, TWRP gets replaced by the crappy stock recovery!! This is absolutely maddening! Specifically, it seems that no matter what method to use to flash the TWRP recovery, it gets overriden by the stock loader when the phone reboots. My bootloader is UNLOCKED and I've installed a custom rom just fine by using the command fastboot boot twrp.img to boot into the twrp image. This is the only way I'm able to use TWRP at all. I've tried: fastboot flash recovery twrp.img Booting into TWRP, and flashing the image over the recovery partition Flashify to flash the TWRP over the recovery partition from within the rom Trying to flash cyangenmod's recovery from within the rom (was pretty desperate at this point..) I've also tried many different versions of TWRP, I can boot into them just fine but none of them stick when I flash them to the recovery partition. It always says it's successful when I try to flash it, I reboot into recovery, and it boots into the piece of crap EmUI stock recovery screen every time Anyone have any pointers here? It's not the end of the world but it's pretty aggravating having a completely useless recovery if I'm not near a computer,.
Try using Flashify or Flashfire.
Sadly didn't work. It doesn't seem to matter how I flash the recovery, the bootloader replaces it with the stock recovery when it boots. I'll update the OP to clarify, but thank you
I am having same issue have you found a fix
Have you tried starting completely over? Like, downloading the official MM build (b331, C564D003) from Huawei (Assuming you're on L24)? On the new, freshly installed ROM, make sure that USB Debugging is and enable OEM Unlock are on in the developer settings. Then, try flashing this build of TWRP again. Before rebooting, do a Cache/Dalvik Wipe. Boot up into the stock rom, then use 'adb reboot recovery' to see what happens next. It should work...
Hi mate, It'd be easier to help you if you could post a screenshot of your FASTBOOT screen. There will be a line that will say FRP=LOCKED/UNLOCKED something like this. if it is locked, you have to install stock rom & enable OEM unlock from setting. Then relock the boot loader. Then again unlock the boot loader. For myself, I unlocked my BL unofficially, & this problem occurred . I solved it this way... Hope it helps. Cheers!
Problem with recovery installation (Kate) (Official unlock)
Hey! I Have a Kate running latest global developer that i unlocked officially through the mi unlock program. I have been trying to install TWRP ( unoffical twrp, Alka, coffee) through ADB ( fastboot flash recovery twrp.img) for some days now but i wont work!! ADB dont displays any errors and says everything finished but when i try to boot to recovery it's still stock xiaomi recovery?? What might be the problem and how do i fix it? BTW, adb reports that the phone is unlocked (fastboot oem device-info).
Are you trying to boot TWRP straight after flashing it. If your booting the official rom first, then that is restoring stock recovery. After flashing TWRP, manually boot the device with Vol + and Power button. Alternatively boot TWRP with "fastboot boot <twrp.img>" and from TWRP reboot to recovery again so you actually boot the version on the device.
the newest dev rom has "feature" to revert your recovery back to stock when you boot the OS. so be prepared. after you flash your twrp, immediately boot to TWRP and wipe /system to install other OS.
corkiejp said: Are you trying to boot TWRP straight after flashing it. If your booting the official rom first, then that is restoring stock recovery. After flashing TWRP, manually boot the device with Vol + and Power button. Alternatively boot TWRP with "fastboot boot <twrp.img>" and from TWRP reboot to recovery again so you actually boot the version on the device. Click to expand... Click to collapse IvanKurnia said: the newest dev rom has "feature" to revert your recovery back to stock when you boot the OS. so be prepared. after you flash your twrp, immediately boot to TWRP and wipe /system to install other OS. Click to expand... Click to collapse THANKS! That was the problem. Now everything works.
Some info re: Dual Recovery Prior to Flashing TWRP
I'm new to the 7X (L24) so perhaps I'm preaching to the converted, so please correct any errors and/or add more info.... On the L24, I've tried booting TWRP without replacing the stock recovery (using fastboot boot TWRP.img) so that I can first make a backup of the stock recovery. With FRP and bootloader unlocked, I receive something like "remote -- command failed". From the Honor 7 Forum, inside!out said: It's very simply! We have 2 recovery partition. First - Recovery, Second - eRecovery. eRecovery isn't useful.I tested flashing TWRP in second partition. Its work! Click to expand... Click to collapse 18-03-19 update: Got a little braver since others have kindly posted stock recovery and stock ROM for the L24, so I've flashed TWRP (from https://forum.xda-developers.com/honor-7x/how-to/how-to-root-honor-7x-international-t3716056 to recovery2. (Upon booting up TWRP, the title screen shows TWRP 3.1.1.0 OpenKirin edition.) As a result, I found out I was mistaken about the abd reboot commands. adb reboot recovery boots to EMUI stock recovery. fastboot flash recovery2 TWRP.img actually flashes to eRecovery so ... adb reboot erecovery actually boots into TWRP If you've unlocked your bootloader and press Vol-UP when the orange security warning screen appears, you get into the download stock recovery and stock ROM to bring the 7X back to secured state screen. (But currently, it can't find stock firmware.) So right now, stock recovery is in recovery1 and TWRP is in recovery2/eRecovery. For those who can't get OTA updates because they've flash TWRP on recovery1, some kind souls have posted their stock recovery in this forum. (or try to move recovery2 back to recovery1 if you haven't flashed both recoveries.)
iammudd said: I'm new to the 7X (L24) Click to expand... Click to collapse Use our Multi-Tool, your model in Extended Support