Related
Not completely sure how to explain it.
1. Unlocked Bootloader
2. Flashed or booted TWRP
3. Confused as can be.
At this time I had no clue that there was a simpler system by hasoon.
I just want to get back to stock or whatever so I can just root my phone. I do not want to install custom ROMs, just root.
Can someone link me to a guide to get off TWRP or something?
you still need to do everything you've done. if you don't want to flash a custom rom and just have root then flash this in twrp and then wipe cache and dalvik. UPDATE-SuperSU-v1.25.zip
TWRP is just the recovery and you sorta need it. you don't have to flash a custom rom if you dont want to.
DvineLord said:
just have root then flash this in twrp and then wipe cache and dalvikne.
Click to expand...
Click to collapse
Can you tell me how to get the SU to my phone to flash it?
You shouldn't be scared of custom roms...you're scared because you dont know what's going on...but for just having root download what he linked you to your phone.. boot into twrp click into twrp and press install and find the zip and click on it
swerg said:
Can you tell me how to get the SU to my phone to flash it?
Click to expand...
Click to collapse
you copy it to your sdcard. also since you have twrp installed NEVER do a factory reset from the bootloader only do it in twrp.
a box of kittens said:
download what he linked you to your phone.. boot into twrp click into twrp and press install and find the zip and click on it
Click to expand...
Click to collapse
My problem is getting it downloaded to my phone. I'm kinda stuck on the TWRP screen.
Reboot system...
swerg said:
My problem is getting it downloaded to my phone. I'm kinda stuck on the TWRP screen.
Click to expand...
Click to collapse
have you tried reboot system? while you are in twrp you could mount usb storage then copy supersu to your sdcard and flash it.
only time i ever got stuck in twrp was when i accidentally flashed twrp to boot instead of recovery in which case it will always enter recovery. did you run "fastboot flash boot <twrp>.img" on accident? the proper command is "fastboot flash recovery <twrp>.img". when you flash recovery always good to run "fastboot erase cache".
I went to reboot. System. It started my phone and just went right back to the TWRP screen.
reflash twrp and boot.img to the proper places just incase
Can you give me a link and or a small guide to doing that? I'm kinda clueless when it comes to doing this kinda stuff.
I'm not the brightest with Androids lol.
Frequently Asked Questions
Look it's a STICKY
DvineLord said:
have you tried reboot system? while you are in twrp you could mount usb storage then copy supersu to your sdcard and flash it.
only time i ever got stuck in twrp was when i accidentally flashed twrp to boot instead of recovery in which case it will always enter recovery. did you run "fastboot flash boot <twrp>.img" on accident? the proper command is "fastboot flash recovery <twrp>.img". when you flash recovery always good to run "fastboot erase cache".
Click to expand...
Click to collapse
How would I go about coping supersu to my sdcard? I have my phone hooked up via USB and I have it on mount USB storage but I can't seem to find it.
swerg said:
How would I go about coping supersu to my sdcard? I have my phone hooked up via USB and I have it on mount USB storage but I can't seem to find it.
Click to expand...
Click to collapse
what the frill
I have my phone hooked up to my pc. I can't seem to find where I can copy the SU to my sdcard.
Didn't want to make another thread lol -- quick question! -- Do you need an unlocked bootloader to flash twrp even if I'm s-off?
i believe so
---------- Post added at 10:12 PM ---------- Previous post was at 10:12 PM ----------
swerg said:
I have my phone hooked up to my pc. I can't seem to find where I can copy the SU to my sdcard.
Click to expand...
Click to collapse
did you mount it in twrp?
DvineLord said:
did you mount it in twrp?
Click to expand...
Click to collapse
Yes I mounted it in twrp. It started installing HTC MTP Device but it failed. Is that a required drive?
I HAVE TRIED MULTIPLE ATTEMPTS TO ROOT MY MZ604 BUT NO LUCK. I AM ABLE TO DO THE UNLOCK BOOT LOADER THEN ROOTING IT DOES NOT SEEM TO WORK WITH ANYTHING I HAVE TRIED. IS THERE ANY HELP OR ANY PRE ROOTED ROMS TO DO THE JOB? Can't get twrp or cwm to install!!
HELP!
CL2012 said:
I HAVE TRIED MULTIPLE ATTEMPTS TO ROOT MY MZ604 BUT NO LUCK. I AM ABLE TO DO THE UNLOCK BOOT LOADER THEN ROOTING IT DOES NOT SEEM TO WORK WITH ANYTHING I HAVE TRIED. IS THERE ANY HELP OR ANY PRE ROOTED ROMS TO DO THE JOB? Can't get twrp or cwm to install!!
HELP!
Click to expand...
Click to collapse
Writing is Caps mean you are yelling, Now start from here and read how to root..http://forum.xda-developers.com/showthread.php?t=1468298
Sorry!
tumpy said:
Writing is Caps mean you are yelling, Now start from here and read how to root..http://forum.xda-developers.com/showthread.php?t=1468298
Click to expand...
Click to collapse
hi, i apologise for that i was in a rush and didnt mean to type in caps.
trouble rooting xoom wifi
CL2012 said:
hi, i apologise for that i was in a rush and didnt mean to type in caps.
Click to expand...
Click to collapse
i have tried the way you have given but still no success. the problem seems to be that after i unlock bootloader and try to flash recovery img my external sd card isnt recognised. nothing is working to root my xoom, what is wrong?
CL2012 said:
i have tried the way you have given but still no success. the problem seems to be that after i unlock bootloader and try to flash recovery img my external sd card isnt recognised. nothing is working to root my xoom, what is wrong?
Click to expand...
Click to collapse
Send the recovery img to your xoom with fastboot flash recovery name_of_recovery.img
Then press power and vol up to reboot once at the M count 1 2 3 then press volume down. Then volume up to selext recovery. Once in twrp recovery flash your su.zip (ensure its compatabile with your current os version) and reboot. Then enjoy. When you select reboot twrp will prompt u to delete two files (if your stock) these two files will reinstall stock recovery if they r not deleted or renamed.
You can get the twrp recovery from my sig
trouble rootng xoom wifi!
runandhide05 said:
Send the recovery img to your xoom with fastboot flash recovery name_of_recovery.img
Then press power and vol up to reboot once at the M count 1 2 3 then press volume down. Then volume up to selext recovery. Once in twrp recovery flash your su.zip (ensure its compatabile with your current os version) and reboot. Then enjoy. When you select reboot twrp will prompt u to delete two files (if your stock) these two files will reinstall stock recovery if they r not deleted or renamed.
You can get the twrp recovery from my sig
Click to expand...
Click to collapse
I have tried that but it still still failed. after i unlock the bootloader and try flash recovery img...my sd card isnt recognised to flash CWM or TWRP...why?
CL2012 said:
I have tried that but it still still failed. after i unlock the bootloader and try flash recovery img...my sd card isnt recognised to flash CWM or TWRP...why?
Click to expand...
Click to collapse
Gone over it a hundred times in my thread so before you tell me im wrong, a replace your sd card or b why put the su zip on your sd card? Put it on the internal memory.
Edit... wait your trying to flash the img from your sdcard? Thats not possible
You need to read the OP on my thread on how to install twrp img NOT the zip
trouble rooting xoom wifi
runandhide05 said:
Gone over it a hundred times in my thread so before you tell me im wrong, a replace your sd card or b why put the su zip on your sd card? Put it on the internal memory.
Edit... wait your trying to flash the img from your sdcard? Thats not possible
You need to read the OP on my thread on how to install twrp img NOT the zip
Click to expand...
Click to collapse
hi, i have went thru what u said to do and either way the sd card isnt recognised??
CL2012 said:
hi, i have went thru what u said to do and either way the sd card isnt recognised??
Click to expand...
Click to collapse
So you have twrp booted and your in TWRP recovery yes?
trouble rooting xoom wifi
runandhide05 said:
So you have twrp booted and your in TWRP recovery yes?
Click to expand...
Click to collapse
NO, thats what i am saying...i cant get TWRP to flash or CWM....the bootloader unlocking process i can do...but when it comes to flashing from sd card the sd card isnt recognised. i have been trying various methods and no success for the last 3 days. Its a MZ604 with 4.0.4
CL2012 said:
NO, thats what i am saying...i cant get TWRP to flash or CWM....the bootloader unlocking process i can do...but when it comes to flashing from sd card the sd card isnt recognised. i have been trying various methods and no success for the last 3 days. Its a MZ604 with 4.0.4
Click to expand...
Click to collapse
Ive told you already you can not flash a recovery from stock recovery. You are not reading the op of my thread. Or any other threads on how to do this.
The same method of unlocking the bootloader in fastboot is how you have to flash the recovery unless u already have a custom recovery.
Download the twrp IMG from my op to your computer, save it to your folder where adb.exe and fastboot.exe are.
Boot your tablet into fast boot mode (just like you did when you unlocked the bootloader)
From the folder that adb and fastboot are open cmd prompt
Type
fastboot flash recovery name_of_recovery.img
The tablet should read out that its flashing. In the cmd prompt it should read out that its flashing also.
Once done type
fastboot reboot
Then when the tablet starts to boot you will see the red M count 1 2 3 then press volume down then volume up to select recovery. You are booting into TWRP
runandhide05 said:
Ive told you already you can not flash a recovery from stock recovery. You are not reading the op of my thread. Or any other threads on how to do this.
The same method of unlocking the bootloader in fastboot is how you have to flash the recovery unless u already have a custom recovery.
Download the twrp IMG from my op to your computer, save it to your folder where adb.exe and fastboot.exe are.
Boot your tablet into fast boot mode (just like you did when you unlocked the bootloader)
From the folder that adb and fastboot are open cmd prompt
Type
fastboot flash recovery name_of_recovery.img
The tablet should read out that its flashing. In the cmd prompt it should read out that its flashing also.
Once done type
fastboot reboot
Then when the tablet starts to boot you will see the red M count 1 2 3 then press volume down then volume up to select recovery. You are booting into TWRP
Click to expand...
Click to collapse
That is pretty thorough and explanatory mate. You explained very well with patience
You are such a great asset to all of us. Your knowledge is awesome. Wish I can thank you enough brother.
wesamothman said:
That is pretty thorough and explanatory mate. You explained very well with patience
You are such a great asset to all of us. Your knowledge is awesome. Wish I can thank you enough brother.
Click to expand...
Click to collapse
thanks bud, i try
If you still need help, here is a FAIL proof way... so that there is no mis understanding
watch this
http://www.youtube.com/watch?v=O-7wfZw0wj0&feature=youtu.be
then this
http://www.youtube.com/watch?v=koxgbdQuzOQ
then remember to boot STRAIGHT into recovery after flashing, if you fail to do so the stock rom has two scripts in it that install stock recovery on EVERY BOOT. if you boot to android your custom recovery WILL BE over written
once you boot into TWRP and have finished your flashing and select reboot TWRP will detect the two scripts and prompt you to delete them or your custom recovery will be over written and you will have to re flash ( VIA fastboot like in the first video) again
I tryed to boot CWM recovery for moto G (from this thread) but it didn't boot.
I have an european XT1032 (italian version), there are any fix for this device?
I tested the recovery with the following command:
For the 4.3 version
Code:
fastboot boot CWM43.img
For the 4.4 version
Code:
fastboot boot CWM44.img
but the device prompt the motorola screen and then reboot without boot the custom recovery.
1) is your bootloader unlocked?
2) are you on a stock JB or KK rom?
3) Do you have the same issue with TWRP?
Yes I unlocked the bootloader. I'm on Stock KitKat (4.4.2) and I have the same issue if I try to boot TWRP. I also tried to flash it on device but the issue remains.
Read the OP from the site where you downloaded CWM carefully again and compare it to that what you have quoted here.
With fastboot boot you are trying to flash cwm (recovery) as a kernel:crying:
And even then something is missing in your syntax (flash).
For flashing Kernel use:
fastboot flash boot filename.img
Click to expand...
Click to collapse
For flashing CWM use:
fastboot flash recovery filename.img
Click to expand...
Click to collapse
By the way, here is a good fastboot HowTo.
I already try to flash the recovery on device but it doesn't boot.
so i want to test it before flash on the phone
I already try to flash the recovery on device but it doesn't boot.
so i want to test it before flash on the phone
ecila said:
I already try to flash the recovery on device but it doesn't boot.
so i want to test it before flash on the phone
Click to expand...
Click to collapse
Sorry i don't understand you. You flashed the recovery already? But you want to test it before you flash? Now what?
What did you do exactly?
I think you messed up something while doing this thats why i am suggesting you to go back to Stock first.
Just flash it by typing "fastboot flash recovery recovery.img" and then restart bootloader and press volume down, and then volume up. You should boot into recovery.
mokkami said:
Sorry i don't understand you. You flashed the recovery already? But you want to test it before you flash? Now what?
What did you do exactly?
I think you messed up something while doing this thats why i am suggesting you to go back to Stock first.
Click to expand...
Click to collapse
Before write this post i already tried flash and then boot the custom recovery, but it doesnt boot.
So i restored the stock recovery,and now i want to test recovery (on the fly) without flash it.
You have to flash it. You can not use it "on the fly" to test it.
ecila said:
So i restored the stock recovery,and now i want to test recovery (on the fly) without flash it.
Click to expand...
Click to collapse
I'm really sorry, i just opend the specific Thread again and then i read this.
Then i rememberd this thread. So i'll update my mistake
Rusty! said:
If you want to try it out, use:
Code:
fastboot boot recovery.img
So that the system remains unchanged.
Click to expand...
Click to collapse
So you can use the CWM on the fly.
Hi!
I hope you can help me.
I obviously did something wrong.
Well I did unlock my tablet and got twrp running, also installed the rom but next after the reboot it just doesn't work and i will get this message (see the picture)
After that i am sent back to the interface of twrp.
I just recogniced I have twrp v.2.6.1.0 running - is that the problem?
Hopefully somebody can help me!
greets agepi
agepi91 said:
Hi!
I hope you can help me.
I obviously did something wrong.
Well I did unlock my tablet and got twrp running, also installed the rom but next after the reboot it just doesn't work and i will get this message (see the picture)
After that i am sent back to the interface of twrp.
I just recogniced I have twrp v.2.6.1.0 running - is that the problem?
Hopefully somebody can help me!
greets agepi
Click to expand...
Click to collapse
YOU MUST BE ON THE ASUS STOCK JB 4.2.1 BOOTLOADER VERSION 10.6.1.14.x AND TWRP 2.6.3.2+ OR CWM 6.0.4.6+ BEFORE FLASHING THIS ROM.
This is copied directly from the Developers ROM.
Cheers
agepi91 said:
Hi!
I hope you can help me.
I obviously did something wrong.
Well I did unlock my tablet and got twrp running, also installed the rom but next after the reboot it just doesn't work and i will get this message (see the picture)
After that i am sent back to the interface of twrp.
I just recogniced I have twrp v.2.6.1.0 running - is that the problem?
Hopefully somebody can help me!
greets agepi
Click to expand...
Click to collapse
You didn't use 'Wipe Data' from the bootloader, did you?
Read the OP for CROMBI-KK, compare it to what you did.
Describe in detail what that was.
"Does not work" is not very helpful...
Check if you can get into fastboot.
Sent from my DROID4 using Tapatalk
Well,
I can go to Twrp recovery and fastboot
I did install the rom with everything present I think.. had to select some things and finish the installing
after that I had to reboot and now i just get the image with the penguins.
Can I somehow go back to the original rom? to restart these things?
agepi91 said:
Well,
I can go to Twrp recovery and fastboot
I did install the rom with everything present I think.. had to select some things and finish the installing
after that I had to reboot and now i just get the image with the penguins.
Can I somehow go back to the original rom? to restart these things?
Click to expand...
Click to collapse
If you made a nandroid before flashing this, then yes, you should be able to restore it.
But let's take it from the beginning. Post your bootloader, recovery and rom versions.
As long as you have access to fastboot you can fix this, so don't do anything hasty.
And please be as specific as you can about what you did. We can only help you if we find out where you went wrong.
berndblb said:
If you made a nandroid before flashing this, then yes, you should be able to restore it.
But let's take it from the beginning. Post your bootloader, recovery and rom versions.
As long as you have access to fastboot you can fix this, so don't do anything hasty.
And please be as specific as you can about what you did. We can only help you if we find out where you went wrong.
Click to expand...
Click to collapse
hm ok I will try
well, I didn't make a nandroid backup - my fault :<
are there specific bootloader? I was on JB 4.2.1
I am now on twrp v2.6.3.2 but I was while I did the flashing on twrp v2.6.1
hm I did flash crombi-kk rom from the OP
maybe I did some wipe before in twrp .. i think it was recommended?
so now I can't do any reflash or anything in twrp - everytime I want to do something there is this error:
E: Unable to open '/cache/recovery/.version'
I also can't get access to my external SD
Check if you can get into fastbot.
Long press Power and Volume Down until you see tiny script.
Read it and post the bootloader version: 10.6.1.14.?
berndblb said:
Read it and post the bootloader version: 10.6.1.14.?
Click to expand...
Click to collapse
Well it reads: ww_epad-10.6.1.14.10-20130801
agepi91 said:
Well it reads: ww_epad-10.6.1.14.10-20130801
Click to expand...
Click to collapse
All right, your bootloader is current.
I would recommend that you flash TWRP 2.7 in fastboot, then boot into it, do a Factory Wipe in TWRP (that can take upwards of 60 minutes) and flash the rom again.
Ok.. I tried but I got the answer
failed (data transfer failure (too many links))
hm I think I've got no connection, right?
well and now I get the message:
FAILED ( command write failed( invalid argument))
What do you get with 'fastboot devices'?
Sent from my K00C using Tapatalk
I get 015d2a5068541017 fastboot
agepi91 said:
I get 015d2a5068541017 fastboot
Click to expand...
Click to collapse
Alright, everything good so far.
Now download the TWRP 2.7 blob for the tf700 and put it into the same folder as your fastboot.exe.
Then issue this command:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
if that is successful
Code:
fastboot reboot
Then boot into TWRP via the fastboot menu.
Then you can factory wipe and flash the rom
berndblb said:
Alright, everything good so far.
Now download the TWRP 2.7 blob for the tf700 and put it into the same folder as your fastboot.exe.
Then issue this command:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
if that is successful
Code:
fastboot reboot
Then boot into TWRP via the fastboot menu.
Then you can factory wipe and flash the rom
Click to expand...
Click to collapse
Well I did that but nothing works
I've got now twrp 2.7 and i did that factory wipe but nothing ever happens.. just the usual message
'unable to open 'cache/recovery/.version'
Don't know what I did wrong :<
http://imageshack.com/a/img842/662/kwy9.png
that's the message I everytime get - doesn't matter if it's a wipe or install or something else
in bootlooder at the top there is this message:
>key driver not found... booting 05<
is it possible to formate my complete data, because I think therein lies the problem, exept fastboot on my device and flash a recovery from fastboot?
agepi91 said:
is it possible to formate my complete data, because I think therein lies the problem, exept fastboot on my device and flash a recovery from fastboot?
Click to expand...
Click to collapse
If you want to try that, go to the Wipe menu in TWRP, then to Advanced and choose "format data".
In TWRP this can take 90 minutes! D not interrupt it and make sure the tablet is charged or connected to power.
But this will erase your entire data.
The recovery has it's own partition which you can erase in fastboot:
Code:
fastboot erase recovery
.
Then flash the new recovery. You could also try TWRP 2.6.3.2 if 2.7 doesn't work.
agepi91 said:
is it possible to formate my complete data, because I think therein lies the problem, exept fastboot on my device and flash a recovery from fastboot?
Click to expand...
Click to collapse
Your posted image indicates that simulation mode is active in TWRP - turn if off in TWRP settings.
To format data, it's approximately this: Wipe -> Advanced -> Format -> Data -> confirm
Note that it takes up to 2 hours to format and trim the eMMC.
---------- Post added at 09:15 PM ---------- Previous post was at 09:14 PM ----------
berndblb said:
The recovery has it's own partition which you can erase in fastboot:
Code:
fastboot erase recovery
.
Click to expand...
Click to collapse
...which is usually a stupid idea if you don't know exactly what you are doing.
Well I don't know how but it suddenly worked.. i could reinstall the rom but now it seems i am stuck in a bootloop between the picture of the four penguins and a bootscreen of crombi-kk with loading tiles under it
between these two the tablet is rebooting itself constantly
Go back to recovery and do a wipe only Calvin cache and Cache.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
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?