Related
Hi guys,
I need help. My kid's Asus TF300T suddenly got stuck at the loading process. I turn it on, and it keeps loading and then reboot itself and kept loading again. This keeps going forever.
The bootloader is unlocked and I had a custom ROM on it, though I don't remember what it is.
I am still able to enter recovery (TWRP 2.4.4.0) while pressing the vol - and Power buttons.
But what else can I do? How do I get the tablet to work again?
Thanks so much.
smokarz said:
Hi guys,
I need help. My kid's Asus TF300T suddenly got stuck at the loading process. I turn it on, and it keeps loading and then reboot itself and kept loading again. This keeps going forever.
The bootloader is unlocked and I had a custom ROM on it, though I don't remember what it is.
I am still able to enter recovery (TWRP 2.4.4.0) while pressing the vol - and Power buttons.
But what else can I do? How do I get the tablet to work again?
Thanks so much.
Click to expand...
Click to collapse
I'm assuming that "loading" means that the boot animation is still working, but not going into Android at the end of it.
You can first try clearing the cache in TWRP: Go to the WIPE category and only select Dalvik Cache and Cache and wipe those. Reboot and see if anything changed.
If that doesn't work, then you can try factory resetting, but this will erase all data not backed up on the tablet. Do NOT wipe data from the fastboot menu. Only factory reset from within TWRP.
cmendonc2 said:
I'm assuming that "loading" means that the boot animation is still working, but not going into Android at the end of it.
You can first try clearing the cache in TWRP: Go to the WIPE category and only select Dalvik Cache and Cache and wipe those. Reboot and see if anything changed.
If that doesn't work, then you can try factory resetting, but this will erase all data not backed up on the tablet. Do NOT wipe data from the fastboot menu. Only factory reset from within TWRP.
Click to expand...
Click to collapse
Yes, that's correct. It's at the boot animation and never get into Android.
I tried to wipe Cache and Dalvnik but that didn't help.
I also just tried Factory Reset, and it did not help either.
Is there anything else I can do? I can try to flash the ROM again, but I just don't remember which ROM I had on it.
smokarz said:
Yes, that's correct. It's at the boot animation and never get into Android.
I tried to wipe Cache and Dalvnik but that didn't help.
I also just tried Factory Reset, and it did not help either.
Is there anything else I can do? I can try to flash the ROM again, but I just don't remember which ROM I had on it.
Click to expand...
Click to collapse
Before you enter TWRP, the bootloader information appears in the top left corner of your screen. Which bootloader version are you on and what does the boot animation say/look like?
It says:
Key driver not found... Booting OS
Android cardhu-user bootloader <1.00 e> released by 'US_epad-10.6.1.8-20130225" A03
Starting Fastboot USB download protocol.
Then I had the option to select RCK - Android - Wipe Data
When I selected RCK, it brings me to TWRP.
The boot animation has the word ANDROID flashing from left to right. It probably was a custom boot animation.
Please let me know if you need anything else.
Thanks
Any suggestions guys?
How can I get this tablet to boot again?
Thanks
smokarz said:
It says:
Key driver not found... Booting OS
Android cardhu-user bootloader <1.00 e> released by 'US_epad-10.6.1.8-20130225" A03
Starting Fastboot USB download protocol.
Then I had the option to select RCK - Android - Wipe Data
When I selected RCK, it brings me to TWRP.
The boot animation has the word ANDROID flashing from left to right. It probably was a custom boot animation.
Please let me know if you need anything else.
Thanks
Click to expand...
Click to collapse
So what I would do is first flash an updated Stock ROM via fastboot: http://forum.xda-developers.com/showthread.php?t=1697227
Flash the "ASUS Transformer Pad TF300T Firmware: V10.6.1.27.5" for your region. Then it will reset.
Then using fastboot, you can follow this guide: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
And you should be up and running with a new CM11 ROM.
cmendonc2 said:
So what I would do is first flash an updated Stock ROM via fastboot: http://forum.xda-developers.com/showthread.php?t=1697227
Flash the "ASUS Transformer Pad TF300T Firmware: V10.6.1.27.5" for your region. Then it will reset.
Then using fastboot, you can follow this guide: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
And you should be up and running with a new CM11 ROM.
Click to expand...
Click to collapse
Thanks cmendonc2,
I really want to make sure I got this right, please let me know if I am missing anything.
1) Install adb/fastboot on my PC
2) Flash Updated Stock Rom via fastboot (which is the latest stock rom and where can I get it?) Do I reboot the tablet after I flashed this?
3) Flash TF300T Firmware: V10.6.1.27.5 via fastboot. I guesss reboot again after I flashed the firmware?
4) Then follow the last link you posted to flash CM11?
smokarz said:
Thanks cmendonc2,
I really want to make sure I got this right, please let me know if I am missing anything.
1) Install adb/fastboot on my PC
2) Flash Updated Stock Rom via fastboot (which is the latest stock rom and where can I get it?) Do I reboot the tablet after I flashed this?
3) Flash TF300T Firmware: V10.6.1.27.5 via fastboot. I guesss reboot again after I flashed the firmware?
4) Then follow the last link you posted to flash CM11?
Click to expand...
Click to collapse
1.) The minimal software from here should work fine: http://forum.xda-developers.com/showthread.php?p=42407269
2.) The Stock ROM is the tf300t firmware: V10.6.1.27.5 from here: http://forum.xda-developers.com/showthread.php?t=1697227 Reboot.
4.) Then follow the guide.
Thanks again,
What are the commands to flash rom and reboot/
smokarz said:
Thanks again,
What are the commands to flash rom and reboot/
Click to expand...
Click to collapse
Extract the blob from the zip file and put it in the fastboot folder:
Code:
fastboot -i 0x0B05 flash system *blob name*
That will take a while and you can watch the progress meter on the device.
Code:
fastboot reboot
will reboot it then.
Thank you. And with fastboot, I don't need to flash the necessary TWRP?
Sent from my HTC One using Tapatalk
smokarz said:
Thank you. And with fastboot, I don't need to flash the necessary TWRP?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Well if you install everything by fastboot, you don't need TWRP. But if something goes wrong and a computer isn't nearby or stops working, having an onboard recovery is essential.
Hopefully, this will be the last question.
Before I use fastboot, should I power up the tablet with the Vol- & Power and then go into RCK mode?
And I don't see a link to download this from that thread.
ASUS Transformer Pad TF300T Firmware: V10.6.1.27.5 Only for US SKU (Android 4.2) - 2013.09.13 update
I downloaded the stock firmware straight from the ASUS website, I hope that was correct.
I ran fastboot, and this is the result of it.
When I did fastboot reboot, the device did not reboot at all and I had to manually power it off.
Now, when I power it on. I am stuck at the ASUS screen, it does even get to the bootloader animation.
Did I do something terribly wrong?
smokarz said:
I downloaded the stock firmware straight from the ASUS website, I hope that was correct.
I ran fastboot, and this is the result of it.
When I did fastboot reboot, the device did not reboot at all and I had to manually power it off.
Now, when I power it on. I am stuck at the ASUS screen, it does even get to the bootloader animation.
Did I do something terribly wrong?
Click to expand...
Click to collapse
Thats weird, the colored text used to be a link to a download in that thread...
What firmware zip did you download? I've never seen that error before. What was the exact name of the file?
cmendonc2 said:
Thats weird, the colored text used to be a link to a download in that thread...
What firmware zip did you download? I've never seen that error before. What was the exact name of the file?
Click to expand...
Click to collapse
I downloaded this file from the ASUS website.
TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip
smokarz said:
I downloaded this file from the ASUS website.
TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip
Click to expand...
Click to collapse
And which file did you extract to flash?
After I extracted, I got this file.
US_epad-user-10.6.1.27.5
And that is the file I used to flash.
smokarz said:
After I extracted, I got this file.
US_epad-user-10.6.1.27.5
And that is the file I used to flash.
Click to expand...
Click to collapse
extract one more layer and get the blob file. Then flash with the blob file.
please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you
Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help
Why do you need to downgrade? Messing with Bootloaders can destroy your phone.
even i want to downgrade... I cant flash custom recovery on 41.1A
poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.
Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...
@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.
kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).
I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk
I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.
How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!
Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?
_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.
_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.
Hi all,
I started out on TWRP version 2.7.1.0, and I wanted to flash the latest TWRP recovery (2.8.7.0), so I used the app that was linked by the TWRP site (TWRP Manager). So I tried to flash the latest update, and then a message pops up telling me to check if this was the right partition. I was careless and I didn't check it, and went ahead and installed it. It said it failed, but next thing I know, every time I tried to reboot(into the system/OS) I just boot right into TWRP (version 2.8.7.0). Then from TWRP (2.8.7.0) I tried to reboot into recovery, and it rebooted into TWRP, except that it was version 2.7.1.0, where I started.
So, when I hit boot into system, I got TWRP (2.8.7.0), and when I hit boot into recovery, I got TWRP 2.7.1.0. I was completely confused, so I wiped the OS, and then booted into fastboot to fastboot flash TWRP(2.8.7.0) in my recovery (It worked). Right now, I'm soft-bricked so I don't have an OS, but I have TWRP(2.8.7.0) as my recovery. Except now, I still get TWRP when I try to boot into system, and fastboot flashing, adb sideloading, and regular TWRP flashing is not working...
Any help is very appreciated, I need my phone to just be working!!! Except, if anyone can help me update it to 5.1 while they're at it, that would be awesome!
akn4497 said:
Hi all,
I started out on TWRP version 2.7.1.0, and I wanted to flash the latest TWRP recovery (2.8.7.0), so I used the app that was linked by the TWRP site (TWRP Manager). So I tried to flash the latest update, and then a message pops up telling me to check if this was the right partition. I was careless and I didn't check it, and went ahead and installed it. It said it failed, but next thing I know, every time I tried to reboot(into the system/OS) I just boot right into TWRP (version 2.8.7.0). Then from TWRP (2.8.7.0) I tried to reboot into recovery, and it rebooted into TWRP, except that it was version 2.7.1.0, where I started.
So, when I hit boot into system, I got TWRP (2.8.7.0), and when I hit boot into recovery, I got TWRP 2.7.1.0. I was completely confused, so I wiped the OS, and then booted into fastboot to fastboot flash TWRP(2.8.7.0) in my recovery (It worked). Right now, I'm soft-bricked so I don't have an OS, but I have TWRP(2.8.7.0) as my recovery. Except now, I still get TWRP when I try to boot into system, and fastboot flashing, adb sideloading, and regular TWRP flashing is not working...
Any help is very appreciated, I need my phone to just be working!!! Except, if anyone can help me update it to 5.1 while they're at it, that would be awesome!
Click to expand...
Click to collapse
I would flash the new RUU.
andybones said:
I would flash the new RUU.
Click to expand...
Click to collapse
Thanks for the reply!
I have already tried to flash the RUU for 4.4.4 but the recovery flash method gave me an error, and the fastboot flash method gave me
FAILED...(remote: not allowed)
I will try again in the morning and let you know how it goes, but I have a feeling it will end the same way.
akn4497 said:
Thanks for the reply!
I have already tried to flash the RUU for 4.4.4 but the recovery flash method gave me an error, and the fastboot flash method gave me
FAILED...(remote: not allowed)
I will try again in the morning and let you know how it goes, but I have a feeling it will end the same way.
Click to expand...
Click to collapse
Why not use the new 5.0.1 RUU?
andybones said:
I would flash the new RUU.
Click to expand...
Click to collapse
andybones said:
Why not use the new 5.0.1 RUU?
Click to expand...
Click to collapse
Yup that's what I meant I'll try 5.0.1 in the morning. Just wondering, will I need the firmware for it? Because I am coming from 4.4.4
akn4497 said:
Yup that's what I meant I'll try 5.0.1 in the morning. Just wondering, will I need the firmware for it? Because I am coming from 4.4.4
Click to expand...
Click to collapse
The firmware is apart of the RUU, did you use cmd
fastboot oem rebootRUU
Then flash RUU? Fastboot flash zip nameofRUU.zip
andybones said:
The firmware is apart of the RUU, did you use cmd
fastboot oem rebootRUU
Then flash RUU?
Click to expand...
Click to collapse
Oh shoot, I feel dumb. I'll let you know, thanks!
The RUU worked! I used the exe and I'm up and running. Thanks!!
akn4497 said:
The RUU worked! I used the exe and I'm up and running. Thanks!!
Click to expand...
Click to collapse
When you go to flash your custom recovery, use fastboot rather than twrp manager. If you MUST use such a shortcut, I might recommend flashify.
cntryby429 said:
When you go to flash your custom recovery, use fastboot rather than twrp manager. If you MUST use such a shortcut, I might recommend flashify.
Click to expand...
Click to collapse
Yeah I think I'll just stick with fastboot flashing recoveries from now on! Thanks
akn4497 said:
Yeah I think I'll just stick with fastboot flashing recoveries from now on! Thanks
Click to expand...
Click to collapse
Glad to hear you're up and running my friend.
HTCDreamOn said:
A word of advice: I strongly recommend temporarily booting any images (be it recoveries or kernels) you are about to flash to your device. This is simply a case of using the command "fastboot boot blahblah.img" whether blahblah.img is a recovery or kernel.
Click to expand...
Click to collapse
We know you can boot to TWRP vice flash to your device by using the command:
Code:
fastboot boot twrp.img
But how do you proceed from here? Are you required to use ADB commands at this point or can you unplug your USB cable and use TWRP as if it was installed, I.E. , back up current ROM, and install new zip.
purplepizza said:
We know you can boot to TWRP vice flash to your device by using the command:
Code:
fastboot boot twrp.img
But how do you proceed from here? Are you required to use ADB commands at this point or can you unplug your USB cable and use TWRP as if it was installed, I.E. , back up current ROM, and install new zip.
Click to expand...
Click to collapse
Sorry if I wasn't clear. Yes you can unplug usb and use as normal, it just means twrp isn't flashed to the device so it won't be there when you reboot.
I just recommend this step because I'm paranoid. Once you've confirmed the image works you should reboot to bootloader and fastboot flash the image, then you'll be able to boot into twrp whenever you want.
HTCDreamOn said:
Sorry if I wasn't clear. Yes you can unplug usb and use as normal, it just means twrp isn't flashed to the device so it won't be there when you reboot.
I just recommend this step because I'm paranoid. Once you've confirmed the image works you should reboot to bootloader and fastboot flash the image, then you'll be able to boot into twrp whenever you want.
Click to expand...
Click to collapse
This is a good step to do, and if the device supports it it should be used... for example the Moto G (if unlocked) fully supports fastboot boot commands, devices like the HTC One M7 do NOT support this anymore...
To the OP, what is really happening here is that TWRP or the boot.img (kernel) is being loaded from USB into RAM and executed normally, instead of the standard /boot partition which is skipped when executing fastboot boot. TWRP (and recovery in general) is really just a specialized micro-sized android distribution and when started via fastboot boot is executed as if it was the boot image. Once the image is transferred into RAM, the boot continues normally per the instructions of TWRP or the boot image, and no further action via USB is required. USB is just the medium to load the image into RAM and nothing more.
fastboot boot - used to manually load a boot image (or recovery) and execute from RAM, it is not flashed to the device, on the next reboot it will return to it's previous state
fastboot flash boot/recovery - used to actually flash the boot image or recovery image to the it's appropriate partition on the device, it does not execute it. On a reboot or factory default this information will stay in the device.
acejavelin said:
This is a good step to do, and if the device supports it it should be used... for example the Moto G (if unlocked) fully supports fastboot boot commands, devices like the HTC One M7 do NOT support this anymore...
To the OP, what is really happening here is that TWRP or the boot.img (kernel) is being loaded from USB into RAM and executed normally, instead of the standard /boot partition which is skipped when executing fastboot boot. TWRP (and recovery in general) is really just a specialized micro-sized android distribution and when started via fastboot boot is executed as if it was the boot image. Once the image is transferred into RAM, the boot continues normally per the instructions of TWRP or the boot image, and no further action via USB is required. USB is just the medium to load the image into RAM and nothing more.
fastboot boot - used to manually load a boot image (or recovery) and execute from RAM, it is not flashed to the device, on the next reboot it will return to it's previous state
fastboot flash boot/recovery - used to actually flash the boot image or recovery image to the it's appropriate partition on the device, it does not execute it. On a reboot or factory default this information will stay in the device.
Click to expand...
Click to collapse
Thanks. So it seems there is no reason to ever flash TWRP unless you don't want the PC dependence to use the TWRP tool.
purplepizza said:
Thanks. So it seems there is no reason to ever flash TWRP unless you don't want the PC dependence to use the TWRP tool.
Click to expand...
Click to collapse
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
I understand what you are saying. The only flash I planned on was SuperSU. I thought when a system upgrade is available, I could simply use SU to unroot and be ready for the update. Would this work?
If I followed your recommendation, could I feasibly, flash TWRP, then when an upgrade is ready, flash nandroid backup (which I assume removes TWRP) then accept system update, then re-flash TWRP. I could restore apps by using TB. Does this make sense? Or does TWRP remain in place after flashing nandroid backup?
purplepizza said:
I understand what you are saying. The only flash I planned on was SuperSU. I thought when a system upgrade is available, I could simply use SU to unroot and be ready for the update. Would this work?
If I followed your recommendation, could I feasibly, flash TWRP, then when an upgrade is ready, flash nandroid backup (which I assume removes TWRP) then accept system update, then re-flash TWRP. I could restore apps by using TB. Does this make sense? Or does TWRP remain in place after flashing nandroid backup?
Click to expand...
Click to collapse
TWRP remains in place after restoring a nandroid (I think, I haven't installed on my Moto G, but in most devices it doesn't backup/restore recovery), but you can easily restore the original recovery via fastboot.
acejavelin said:
TWRP remains in place after restoring a nandroid (I think, I haven't installed on my Moto G, but in most devices it doesn't backup/restore recovery), but you can easily restore the original recovery via fastboot.
Click to expand...
Click to collapse
Just curious, how did you go from 5.1.1 to 6.0?
purplepizza said:
Just curious, how did you go from 5.1.1 to 6.0?
Click to expand...
Click to collapse
OTA... part of soak test on December 22.
acejavelin said:
OTA... part of soak test on December 22.
Click to expand...
Click to collapse
Hey thanks for helping to answer this, your explanation was much better I thought it had something to do with loading into RAM but wasn't sure. I didn't know some devices don't allow fastboot boot commands though, I've always relied on them. Part of the reason I'm avoiding htc now.
@purplepizza I agree with everything acejavelin has said: essentially you really do want to make sure your have twrp flashed.
To answer your nandroid question: It basically just takes an image of the partitions you choose, usually /system, /data, and /boot (where kernel stuff is) which is the least you need to boot back with all your data. It doesn't backup recovery and when you restore it doesn't write anything to recovery, so yes twrp will still be in place. In general you should only ever flash stuff to the recovery partition whilst in fastboot mode (i.e. using fastboot flash recovery recovery.img), I know on some devices you can flash recoveries as zip files in the recovery itself but you shouldn't.
I've seen quite a few people querying about the 6.0 OTA: in short, I wouldn't worry about it because once they start rolling out, people always catch the OTA and post here on xda. You can flash that and it'll return you to stock 6.0 anyway, at which point you can reroot and everything if you want.
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
One more question, when making the first nandroid backup. do you just back up system and data or do you include boot as well?
purplepizza said:
One more question, when making the first nandroid backup. do you just back up system and data or do you include boot as well?
Click to expand...
Click to collapse
My opinion is always backup everything, you can always choose what to restore
Sent from my MotoG3 using Tapatalk
acejavelin said:
My opinion is always backup everything, you can always choose what to restore
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
So what is boot? I know I am kind of going back to my previous question, but if I restore boot, is that the boot loader? I would assume this would not commonly need restored?
And I now assume the bootloader is completely independent from recovery.
purplepizza said:
So what is boot? I know I am kind of going back to my previous question, but if I restore boot, is that the boot loader? I would assume this would not commonly need restored?
And I now assume the bootloader is completely independent from recovery.
Click to expand...
Click to collapse
It is not the bootloader... It is the /boot partition of the phone, basically the kernel and RAM disk. If you screw things up and need to restore, you typically want to restore /boot, /system, and /data, and occasionally /cache (if you want to restore to save time and get an exact duplicate of the previous image, otherwise many people skip /cache and let it rebuild on the first boot which takes 10-15 minutes extra).
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
HTCDreamOn said:
@purplepizza I agree with everything acejavelin has said: essentially you really do want to make sure your have twrp flashed.
Click to expand...
Click to collapse
So I am following your advice. I booted to TWRP, made Nandroid backup.
Rebooted and flashed TWRP, see below:
Code:
sudo fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (7772 KB)...
OKAY [ 10.635s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 10.776s
All seems OK.
Scrolled to recovery, selected recovery. TWRP was there. I then powered down.
After that I held power and volume down, system boots to dead Android with message “No command” Held power then volume up, I see stock boot loader. Is TWRP flashed somewhere or is it gone? So what did I do wrong.
purplepizza said:
So I am following your advice. I booted to TWRP, made Nandroid backup.
Rebooted and flashed TWRP, see below:
Code:
sudo fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (7772 KB)...
OKAY [ 10.635s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 10.776s
All seems OK.
Scrolled to recovery, selected recovery. TWRP was there. I then powered down.
After that I held power and volume down, system boots to dead Android with message “No command” Held power then volume up, I see stock boot loader. Is TWRP flashed somewhere or is it gone? So what did I do wrong.
Click to expand...
Click to collapse
I have no idea, you did it right... selecting recovery from the bootloader should start TWRP, not stock recovery, that should be gone.
acejavelin said:
I have no idea, you did it right... selecting recovery from the bootloader should start TWRP, not stock recovery, that should be gone.
Click to expand...
Click to collapse
Any recommendations how to proceed?
I also need help with my soft bricked moto g3
Moto g3 (xt 1550, Indian dual sim 16 gb version)
I officially upgraded to 6.0.0 via ota and my objective was to root my phone and use xposed modules. I am not interested in any other custom rom (I'd rather keep stock rom just for moto display and ota upgrades) or custom recovery like twrp(I'm afraid it may cause ota upgrades to fail).
I used the method described here in the question- http://android.stackexchange.com/qu...rsu-using-play-store-versus-a-custom-recovery
So I first successfully unlocked my bootloader using the official motorola method.
I then proceeded to use google's backup settings to re-install all the apps that were uninstalled due to unlocking the bootloader. I also put supersu.zip version 2.46 on internal sd card.
I then proceeded to (without rebooting) enter fastboot where i used minimal adb to temporarily boot into twrp version2.8.7 r5 (link - http://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537 ).
Once in twrp, I located and flashed the supersu.zip. It flashed successfully. I procceded to clear dalvik cache and then after clearing cache I tried to reboot my phone using twrp.
However, it did not go beyond the "Warning - Bootloader Unlocked" screen that you get on unlocking a motorola bootloader. I left it for over 10 minutes (usb was still plugged in, I had >80% battery) but it did not proceed.
Long -pressing the power button causes the phone to vibrate and again attempt to boot, stuck at the same initial screen. Adb quite understandably does not work here.
I can press vol down+power and enter fastboot , where adb works fine.
I can enter stock recovery from the fastboot sceen too.
Using adb in fastboot, I am able to boot twrp . In fact, I tried to re-install supersu.zip. I retried version 2.46 and then tried version 2.56. On all occcassions, it was able to successfully flash it, but gets hung on the initial boot screen.
USB Debugging is also enabled, and I have a backp of my sd card data.
I tried taking a backup of the system and apps in twrp (3 gb in total) and tried to reflash it, but it still hangs at the same screen.
Is there any way I can unbrick my device and- (in decreasing order of preference)
1. Keep my stock rom and recovery?
2. Keep stock rom with twrp? (It should not be a problem)
3. Custom rom with custom recovery - perhaps official cm. Least preferred as I want Moto Display and stock/vanilla android.
Also, is SELinux involved anywhere with my phone getting bricked? I also read that a custom kernel is required for rooting 6.0, which I don't have. Supersu Version 2.56 is said to prevent soft bricks if the kernel is incorrect (systemless root), yet even after flashing the newer one it is still bricked. Where am I going wrong? What should I do? Thanks in advance! :good:
purplepizza said:
Any recommendations how to proceed?
Click to expand...
Click to collapse
Try the flash again? Sorry, but I don't really know help... if you are successfully rooted, perhaps try to flash TWRP image with Flashify? (select your file, don't let it auto-grab an image)
acejavelin said:
Try the flash again? Sorry, but I don't really know help... if you are successfully rooted, perhaps try to flash TWRP image with Flashify? (select your file, don't let it auto-grab an image)
Click to expand...
Click to collapse
I have not rooted yet. I guess I can try by booting TWRP then flashing SuperSU.
Can you think of any reasons not to try fastboot again the re-flash TWRP?
I'm trying to boot into TWRP to install it from there ("fastboot flash recovery" doesn't work), but "fastboot boot" just makes my phone boot normally. Anyone know what's going on?
Edit: I'm just dumb and had the wrong image. I extracted the image from the installation zip rather than the separate .img download for fastboot.
Darkscan said:
I'm trying to boot into TWRP to install it from there ("fastboot flash recovery" doesn't work), but "fastboot boot" just makes my phone boot normally. Anyone know what's going on?
Click to expand...
Click to collapse
Issue with TWRP. What are you running?
Blue1k said:
Issue with TWRP. What are you running?
Click to expand...
Click to collapse
Latest versions of stock Android, EDB, and TWRP.
This happened to me, I redownloaded the twrp image, rebooted my phone, tried again and it booted to twrp.
I'm just an idiot. I hadn't done this in a long time, so for some reason I extracted the .img from the .zip, rather than downloading the image labeled fastboot.
On a related note though, do OTAs work with systemless root? Last I checked it was up in the air, but there's been some time now -- could someone link me, perhaps?
Darkscan said:
I'm just an idiot. I hadn't done this in a long time, so for some reason I extracted the .img from the .zip, rather than downloading the image labeled fastboot.
On a related note though, do OTAs work with systemless root? Last I checked it was up in the air, but there's been some time now -- could someone link me, perhaps?
Click to expand...
Click to collapse
it's supposed to work and I don't see why it wouldn't. (I never tried personally) but you will need to have the stock recovery for the OTA to flash.