Related
A friend found a Droid Eris on the side of the road. It would only boot to HBOOT. I am trying to fix the phone.
When I started working on it the bootloader was 1.47.0000 S-ON
I followed this Q and A thread to flash 1.29.2000 S-OFF
I can not get it to boot Amon's recovery. It freezes at the three skateboarding androids. It always boot to fastboot even if I have other buttons held down.
I have tried fastboot erase, flash, and boot.
I know how to use adb and fastboot.
In summary I have never been able to get the phone to boot fully but was able to flash the root rom with S-OFF. Now I need help booting to recovery.
Thanks in advance
This post has both a version of Amon_RA Recovery that can work with a broken trackball, plus instructions on how to flash with fastboot with the S-OFF bootloader (see scenario 4 toward the bottom): http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
Hi, I was running Meanrom 36 s-off....everything was great! Then I flashed Paranoid Androids boot.img with Flash Gui and rebooted (intending to do the ROM next). It now reboots to the Meanrom screen and stops. Won't boot into recovery and wont mount. Any way to just get back to Meanrom???
LazyPanda
Jewel Pvt Ship S-off rl
Cid-Spcs_001
Hboot 1.12.2222
OpenDsp-v25.1.0.32.0405
eMMC-boot
If you have s-off then there is no real need for flashgui, just flash from recovery
Why are you using the kernel workarounds with S-OFF? Just flash the ROMS normally.
Also, this is why people shouldnt use flash image GUI unless they already know how to do it manually from fastboot. Because if something goes wrong they are screwed
these threads are starting to remind me of that time my neighbor gave his son a box of matches....
I didn't realize that when I began. Its been awhile since I've done this and i suck. Cant reboot into recovery now, just reboots normally then gets stuck on the Meanrom boot screen. Matches? I think I've been handed C4!
okay well the most basic BASIC solution would be to try and restore a nandroid backup, you're s-off so thats not a problem, otherwise boot recovery, use a wipe script and install a rom. After you get the phone going again, never ever touch anything like flash gui again, learn basic adb, read up on the features your recovery offers, learn to trouble shoot your phone using adb tools, from within recovery, just by using the rom, or hell check out the irc channels and watch the devs troubleshoot problems themselves. some of them are more then willing to help if they have the time to do so
How can I restore the backup if I can only boot into bootloader? I completely agree. Hell I don't even want to flash another ROM again! I loved Meanrom....
cmm67 said:
How can I restore the backup if I can only boot into bootloader? I completely agree. Hell I don't even want to flash another ROM again! I loved Meanrom....
Click to expand...
Click to collapse
You should be able to boot into the bootloader. Power down the phone by pressing the power button and volume down key for about 15 seconds. The phone will power off and then press and hold down the volume down button and press the power button at the same time for about 5 seconds. Continue to hold the volume key and your bootloader should load. You should then select fastboot and then reboot recovery or recovery can't remember which it shows. The phone will power off and power back on and should boot int recovery. Then you can nandroid provided you nandroid before you flashed the Rom. If you didn't then just flash the Rom again no need to wipe anything Mean Rom wipes davlik already. Then once the Rom is done flashing you should be good.
Sent from my EVO using xda premium
yes, I can reboot into bootloader. When I select recovery it just reboots normally and then gets stuck on the Meanrom boot screen. Never opens recovery
I guess that means you need to fastboot recovery
edit: sorry if it seems I left you hanging, in my area wimax is the only means of internet and to top it off im in a spot that struggles to get wimax despite the fact that all around the outside of my house I can perfect signal
cmm67 said:
yes, I can reboot into bootloader. When I select recovery it just reboots normally and then gets stuck on the Meanrom boot screen. Never opens recovery
Click to expand...
Click to collapse
Reflash the recovery. You can download it from twrp website...the lastest version you should be able to flash recovery via fastboot using
Fastboot flash recovery (recovery file name)
The direction are on the twrp website. The lastest version is 2.2.2.0 .
Flash thay and then reboot the bootloader and then fastboot
Fastboot reboot recovery
It should then load into recovery
Sent from my EVO using xda premium
Thanks! Ended up flashing recovery again in fastboot then could restore my nandroid. I was so lost
Sent from my EVO using xda app-developers app
I really appreciate everyone's help!
Sent from my EVO using xda app-developers app
I am running santod's rooted Stock ICS rom, which has been running excellent, love it very much. Today I went to do a backup in recovery and noticedit will not boot into recovery. I am running the 4EXT recovery as suggested in the rom forum post. Nothing I do seems to be able to boot the recovery. I can't reboot into recovery from the 4EXT app. I boot the phone with the volume down key, and try to enter recovery from there. Still nothing. I get my initial boot logo, then screen goes black, then boot logo again and it proceeds to boot up normally. I have tried re-flashing the recovery from the 4EXT app, I even tried rom manages and using the latest clockwork mod recovery. Nothing gets me into recovery. Also have noticed my phone will not stay powered off when on the charger. If I power off, plug the charger in, after a few seconds phone powers itself on. Could it be related?
I followed the rom installation instructions to the letter.
Installed the 4EXT recovery.
Flashed the ICS radios.
Wiped all my partitions except my SD card.
Flashed rom and have enjoyed for weeks now.
Only other info I know to provide is I installed the debloated/deodexed rom
Did not flash the kernel as I didn't experience boot loops.
Thanks in advance for any assistance folks!
JM1084 said:
I am running santod's rooted Stock ICS rom, which has been running excellent, love it very much. Today I went to do a backup in recovery and noticedit will not boot into recovery. I am running the 4EXT recovery as suggested in the rom forum post. Nothing I do seems to be able to boot the recovery. I can't reboot into recovery from the 4EXT app. I boot the phone with the volume down key, and try to enter recovery from there. Still nothing. I get my initial boot logo, then screen goes black, then boot logo again and it proceeds to boot up normally. I have tried re-flashing the recovery from the 4EXT app, I even tried rom manages and using the latest clockwork mod recovery. Nothing gets me into recovery. Also have noticed my phone will not stay powered off when on the charger. If I power off, plug the charger in, after a few seconds phone powers itself on. Could it be related?
I followed the rom installation instructions to the letter.
Installed the 4EXT recovery.
Flashed the ICS radios.
Wiped all my partitions except my SD card.
Flashed rom and have enjoyed for weeks now.
Only other info I know to provide is I installed the debloated/deodexed rom
Did not flash the kernel as I didn't experience boot loops.
Thanks in advance for any assistance folks!
Click to expand...
Click to collapse
Did you rename or remove the Radio file from the sd card as suggested in the OP of the rom thread?
It will not let you get into Recovery if there is a PG05IMG.zip present on the root of the sd card.
If that's not the case, reflash 4ext from within the Recovery control app.
Just installing the app doesn't install the Recovery.
You must also install the actual Recovery from within the app if you haven't.
santod040 said:
Did you rename or remove the Radio file from the sd card as suggested in the OP of the rom thread?
It will not let you get into Recovery if there is a PG05IMG.zip present on the root of the sd card.
If that's not the case, reflash 4ext from within the Recovery control app.
Just installing the app doesn't install the Recovery.
You must also install the actual Recovery from within the app if you haven't.
Click to expand...
Click to collapse
Yeah, there is no PG05IMG.zip in the sd card root. Also I have tried reinstalling the recovery from the 4EXT recovery control app.
Current verson of recovery installed is 4EXT Recovery Touch v1.0.0.5 RC8.
Tried reflashing that, and also the RC9 test build that is out right now.
Still no go on getting into the recovery.
Thanks.
When you do the volume down and power option with the device off, you need to first press the volume down and then while holding that, then press and also hold the power button, you should feel it vibrate, keeeeeep holding them down, do not let go.
Wait until you see what should be a white hboot screen with menu options, then you may let go.
If you hold power first or don't hold them both down long enough, it will just try to boot normally.
Not that that would explain why you can't get there from within Recovery Control app.
What is your hboot version and how did you root your device?
santod040 said:
When you do the volume down and power option with the device off, you need to first press the volume down and then while holding that, then press and also hold the power button, you should feel it vibrate, keeeeeep holding them down, do not let go.
Wait until you see what should be a white hboot screen with menu options, then you may let go.
If you hold power first or don't hold them both down long enough, it will just try to boot normally.
Not that that would explain why you can't get there from within Recovery Control app.
What is your hboot version and how did you root your device?
Click to expand...
Click to collapse
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
JM1084 said:
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
Click to expand...
Click to collapse
Yes, you can flash Recovery images from hboot, just like you flash a radio.
With it named PG05IMG.zip and placed on the root of the sd card.
HERE is one you can try.
If that doesn't work, I may have something you can try from fastboot to clear the Recovery cache, and maybe that will resolve the issue.
I have only seen one other user have this occur and his device simply ended up getting replaced because he wasn't able to mount to usb for doing fastboot commands either.
santod040 said:
Yes, you can flash Recovery images from hboot, just like you flash a radio.
With it named PG05IMG.zip and placed on the root of the sd card.
HERE is one you can try.
If that doesn't work, I may have something you can try from fastboot to clear the Recovery cache, and maybe that will resolve the issue.
I have only seen one other user have this occur and his device simply ended up getting replaced because he wasn't able to mount to usb for doing fastboot commands either.
Click to expand...
Click to collapse
Still no go flashing that recovery in hboot. What is the process of clearing recovery cache?
On a side note, in talking to my father, his bolt seems to have the same issue. We both were rooted with the same method, and I believe we have the same hboot version. Only difference is he flashed the rom using clockwork recovery.
Edit: I confirmed his hboot is 6.04.1002. same as mine
JM1084 said:
Still no go flashing that recovery in hboot. What is the process of clearing recovery cache?
On a side note, in talking to my father, his bolt seems to have the same issue. We both were rooted with the same method, and I believe we have the same hboot version. Only difference is he flashed the rom using clockwork recovery.
Click to expand...
Click to collapse
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
santod040 said:
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
Click to expand...
Click to collapse
Alrighty, I will give that a shot. I am at work right now and am about to head out of town so I will be unable to try it until sunday. I'll post the results here asap. Thanks again!
Same ROM, same problem,I even tried flashing a different recovery. Rooted using really old one click method a month after thunderbolt release.
Sent from my HTC Thunderbolt
zomgalama said:
Same ROM, same problem,I even tried flashing a different recovery. Rooted using really old one click method a month after thunderbolt release.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
What is your h boot version?
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
Click to expand...
Click to collapse
No Go, my tbolt will not mount in Win7, it just says the device has malfunctioned. Rebooting into the bootloader with USB in will not show anything in Windows, even in fastboot. It makes the device connection sound but no devices show up. Running the CMD file in the zip you linked does nothing, I'm at 10 minutes now where it just says "Waiting for device". Is my device just done for?
JM1084 said:
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
Click to expand...
Click to collapse
I think I had a similar problem once. Boot back into your hboot screen. Then select "factory reset". If you have a 3rd party recovery installed, like it sound like you have (4ext, right?), it will boot you to recovery so you can administer the reset yourself (it doesn't actually wipe anything, just brings you to your recovery's home screen).
Let me know how it goes.
coltspackers said:
I think I had a similar problem once. Boot back into your hboot screen. Then select "factory reset". If you have a 3rd party recovery installed, like it sound like you have (4ext, right?), it will boot you to recovery so you can administer the reset yourself (it doesn't actually wipe anything, just brings you to your recovery's home screen).
Let me know how it goes.
Click to expand...
Click to collapse
Thanks for the info, but this didn't work either. I'm also on 6.04.1002 and rooted mine a week after the T-Bolt shipped manually via adb.
This happened about a month ago also, and I thought it was ext4 but managed to get an older TWRP recovery to work after working on it for about a day and a half without a working phone. At least I have a working phone at this point.
Same ROM, same recovery (4ext), same problem. Rooted by adb a month after launch, hboot 6.04.1002
allo_87 said:
Same ROM, same recovery (4ext), same problem. Rooted by adb a month after launch, hboot 6.04.1002
Click to expand...
Click to collapse
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
santod040 said:
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
Click to expand...
Click to collapse
Excellent advice, thanks man.
Sent from my ADR6400L using Tapatalk 2
My thunderbolt's recovery spin mysteriously started working again yesterday, not sure why.
Doesn't matter though since I switched carriers now:/
Sent from my Sprint LG Optimus G
Still nothing for me. Worse yet is the fact that I can't adb because my usb has not worked properly since "the soup incident"
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
Click to expand...
Click to collapse
After going over the issue with Max and trying several fixes he suggested (he even made me an app that would format my cache), it seems I either need to obtain an RUU and flash the stock software/recovery back on and re-root or try flashing an updated hboot that already has s-off. The thinking is that it is my hboot that is causing the issue. Does anyone know what files I need? I have a couple of things to try at home to see if I can get my usb working again, if not, anything I do will have to be a flashable zip from the bootloader. Thanks!
Hi, I did the update here - http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
And removed twrp. Obviously with my lack of knowledge I
made a mistake. Now I have stock recovery and the nabi freezes on the boot logo.
Any chance someone could help with getting it booting again or getting twrp back on.
gavjbrown said:
Hi, I did the update here -http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
And removed twrp. Obviously with my lack of knowledge I
made a mistake. Now I have stock recovery and the nabi freezes on the boot logo.
Any chance someone could help with getting it booting again or getting twrp back on.
Click to expand...
Click to collapse
If Jellybean is installed, then I think this is what you need to install TWRP for JB onto the Nabi:
http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
Once TWRP is on, your options for recovery are much wider.
gavjbrown said:
Hi, I did the update here -http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
And removed twrp. Obviously with my lack of knowledge I
made a mistake. Now I have stock recovery and the nabi freezes on the boot logo.
Any chance someone could help with getting it booting again or getting twrp back on.
Click to expand...
Click to collapse
Did you do everything else in thread or just that post? i.e. Did you update the bootloader too? http://forum.xda-developers.com/showpost.php?p=50356162&postcount=91
You will need TWRP one way or another. Use the ICS version if you didn't update the bootloader, and JB if you did.
Thanks for the help guys. I didn't realises until after that I needed to update the bootloader too, I'm guessing that's where my troubles start.
Just going to have a look at your links now, I know I could get twrp back on when it doest boot.
Thanks again.
Tried nabilab for ics and jb and both are no longer detecting my nabi.
When the nabi tries to boot the circle around the logo isnt even moving.
Still stuck with the Nabi, if anyone could help I'd really appreciate it. All I can do with it at the moment is boot to stock recovery.
gavjbrown said:
Still stuck with the Nabi, if anyone could help I'd really appreciate it. All I can do with it at the moment is boot to stock recovery.
Click to expand...
Click to collapse
So you installed the 2.2 ROM, but didn't update the bootloader. You have the stock recovery on it right now.
Can you get TWRP back on it?
Can you get into fastboot mode by pressing power and vol down?
aicjofs said:
So you installed the 2.2 ROM, but didn't update the bootloader. You have the stock recovery on it right now.
Can you get TWRP back on it?
Can you get into fastboot mode by pressing power and vol down?
Click to expand...
Click to collapse
Edited -
Yes put 2.2 on it but didn't update the boot loader. Tried to get twrp back on using nabilab buts the tablets no longer being detected .
Yes, I only have stock recovery. When I select fastboot protocol, I then get bootloader, continue, reboot-bootloader, reboot and power off.
gavjbrown said:
Edited -
Yes put 2.2 on it but didn't update the boot loader. Tried to get twrp back on using nabilab buts the tablets no longer being detected .
Yes, I only have stock recovery. When I select fastboot protocol, I then get bootloader, continue, reboot-bootloader, reboot and power off.
Click to expand...
Click to collapse
OK now you need to put TWRP back on it with fastboot when it's in that state.
Look in the TWRP thread, I'm mobile right now, but basically you need to open a command prompt where fastboot is located and then
fastboot flash recovery recovery.img
Thanks so much for getting me out of this mess. Twrp is back on so I should be ok now with a bit of trial and error.
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