Related
After the OTA 3.2.1 update, CWM Recovery would just not install. After flashing the CWM recovery image on stock 3.2.1 and rebooting into recovery, I get the android guy with the exclamation mark. I saw another person in the CWM thread having the same issue.
I did flash CWM before on HC 3.2 successfully, but for some reason it is not working after the last OTA update.
Any thoughts ?
Any luck on this? I'm trying to root my Xoom 3.2.1 and have no idea what to do and looks like the one click tool has been removed...any direction is better than no direction ;-)
Thanks!!
Faslane
I had this same issue yesterday.
Use adb and fastboot to manually install clockwork again...and then if you need to root you can use one click root.
I would give you the code for fastboot command but I'm not home.
Sent from my ADR6350 using xda premium
Do not use one click root-you'll brick it.
Use the Univetsal Xoom Root.
http://forum.xda-developers.com/showthread.php?t=1242241
okantomi said:
Do not use one click root-you'll brick it.
Use the Univetsal Xoom Root.
http://forum.xda-developers.com/showthread.php?t=1242241
Click to expand...
Click to collapse
Thank you okantomi that's what I meant.
Sent from my ADR6350 using xda premium
well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.
Yazan76 said:
well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.
Click to expand...
Click to collapse
That is exactly right.
Yazan76 said:
well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.
Click to expand...
Click to collapse
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks
texasez said:
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks
Click to expand...
Click to collapse
these instructions seem to work
http://forum.xda-developers.com/showpost.php?p=17832798&postcount=78
texasez said:
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks
Click to expand...
Click to collapse
Yes. What I did is backup everything, flash back to stock, wait for my device to download and install the 3.2.1 update, and finally flash the recovery, root my device, and install the tachi kernel. Restored all my applications after making sure that everything is fine.
I know it looks like a long a process but google market applications restore saved me a lot of time.
Yazan76 said:
Yes. What I did is backup everything, flash back to stock, wait for my device to download and install the 3.2.1 update, and finally flash the recovery, root my device, and install the tachi kernel. Restored all my applications after making sure that everything is fine.
I know it looks like a long a process but google market applications restore saved me a lot of time.
Click to expand...
Click to collapse
To save even more time and get back your app data, first back up aps and data in Titanium Backup and make sure the backup is on your external sdcard, just to be safe. Then, after wiping, and once you have rebooted, reinstall TB and then run a batch restore of missing apps and data. It is much faster and better than letting google restore the apps.
.
Yesterday just rooted my xoom but now i have a problem when i try to flash something or do something in recovery doesnt work it say cant open sd or cant mount sd any help
okantomi said:
To save even more time and get back your app data, first back up aps and data in Titanium Backup and make sure the backup is on your external sdcard, just to be safe. Then, after wiping, and once you have rebooted, reinstall TB and then run a batch restore of missing apps and data. It is much faster and better than letting google restore the apps.
Click to expand...
Click to collapse
Even simpler... fastboot flash just boot, system, and recovery stock images. Leave userdata alone. Allow the update. Don't worry about letting it fully boot.. let it.. no harm.. but no root.
Then flash CWM (using fastboot).. boot to recovery.. CWM univ root. Good to go. Or CWM a different kernel
CARLITOZ18 said:
Yesterday just rooted my xoom but now i have a problem when i try to flash something or do something in recovery doesnt work it say cant open sd or cant mount sd any help
Click to expand...
Click to collapse
You need to have an exernal sdcard for the recovery images to work.
Chipster0 said:
... Fastboot flash just boot, system, and recovery stock images.
Click to expand...
Click to collapse
Do you (or anyone else) have any (US VZ 3G MZ600) stock images later than HMJ37? Moto stopped carrying at HRI66 for some reason
Not sure how this happened or if it'll work for anybody else???
I did do a WeShare backup of apps and data prior to starting, just in case TiBu didn't work after the update.
I was planning on just starting over with stock Android 7.0 on my A7 (2017U)..... So I booted into TWRP, formated my data, then followed the steps in this thread, skipping the B29 rollback steps: https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
1) As I mentioned above, I booted into TWRP and did a format
1.5) Wiped everything except Micro SD and USB OTG (this step alone should have nuked all my data?)
2) went to Mount and ticked "read only"
3) Flashed A2017UV1.1.0B15_bootstack_by_DrakenFX.zip
4) Flashed A2017UV1.1.0B15_systemstock_by_DrakenFX.zip
5) Wiped Cashe/Dalvik
6) Rebooted (unplugged my usb cable first, not sure if I needed to or not but it hung the first time when it was plugged in)
I seen a screen that said "Decrypting Data", which scared me....But took about 2 minutes, then booted up and EVERYTHING was stock and right where I left it! All my apps and data was still there, along with the stock apps I had previously removed via TiBu.
I checked for and found the 7.1.1 update - It updated perfectly fine!
I booted into the bootloader, flashed TWRP 3.1 (using my PC fastboot command)
Rebooted into TWRP and flashed su2.79 (and my font) -wiped cashe/Dalvik (again).
Before rebooting, I also did the "reboot disemmcwp" using the TWRP terminal - Not sure if I needed to, but I did?
Rebooted, and I now have rooted, stock 7.1.1 and didn't have to spend 2 hours setting everything back up again!
Not sure you will have the same results as I did... I was frankly really surprised I didn't have to start over (like I planned on doing).
Good luck!
Well, I know what I'm doing after putting the toddler to bed tonight! Thanks for this!
edit: One question, when you format, it was just cache, dalvik and data you choose yea?
Bolandk said:
Well, I know what I'm doing after putting the toddler to bed tonight! Thanks for this!
edit: One question, when you format, it was just cache, dalvik and data you choose yea?
Click to expand...
Click to collapse
Actually, after the format I wiped everything except Micro SD and USB OTG....This step alone should have nuked all my data? So I really don't know how my current apps and data survived a format and a complete wipe? I did do a WeShare backup right before all of this, just in case I didn't get root back and wanted to restore my apps using that app.... I doubt that had anything to do with it.
tele_jas said:
Not sure how this happened or if it'll work for anybody else???
I did do a WeShare backup of apps and data prior to starting, just in case TiBu didn't work after the update.
I was planning on just starting over with stock Android 7.0 on my A7 (2017U)..... So I booted into TWRP, formated my data, then followed the steps in this thread, skipping the B29 rollback steps: https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
1) As I mentioned above, I booted into TWRP and did a format
1.5) Wiped everything except Micro SD and USB OTG (this step alone should have nuked all my data?)
2) went to Mount and ticked "read only"
3) Flashed A2017UV1.1.0B15_bootstack_by_DrakenFX.zip
4) Flashed A2017UV1.1.0B15_systemstock_by_DrakenFX.zip
5) Wiped Cashe/Dalvik
6) Rebooted (unplugged my usb cable first, not sure if I needed to or not but it hung the first time when it was plugged in)
I seen a screen that said "Decrypting Data", which scared me....But took about 2 minutes, then booted up and EVERYTHING was stock and right where I left it! All my apps and data was still there, along with the stock apps I had previously removed via TiBu.
I checked for and found the 7.1.1 update - It updated perfectly fine!
I booted into the bootloader, flashed TWRP 3.1 (using my PC fastboot command)
Rebooted into TWRP and flashed su1.79 (and my font) -wiped cashe/Dalvik (again).
Before rebooting, I also did the "reboot disemmcwp" using the TWRP terminal - Not sure if I needed to, but I did?
Rebooted, and I now have rooted, stock 7.1.1 and didn't have to spend 2 hours setting everything back up again!
Not sure you will have the same results as I did... I was frankly really surprised I didn't have to start over (like I planned on doing).
Good luck!
Click to expand...
Click to collapse
it worked.. but A2017UV1.1.0B15_systemstock_by_DrakenFX.zip did n't booted, so i flashed stock nougot from the BadBoyz rom.. and followed your steps.. it booted to 7.1.1
@tele_jas @`SBR` is it ok to not wipe the Internal Storage ?
Sent from my ZTE A2017U using Tapatalk
khangozzy said:
@tele_jas @`SBR` is it ok to not wipe the Internal Storage ?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I was fairly certain I did, but had a couple tell me that I probably didn't "check" that box in TWRP?? I'd back up your internal storage, just in case?!?!
Someone also said it wasn't necessary to wipe your internal storage, since the base is so close? I guess you could try it without wiping your internal storage? If it's all jacked up, go back and wipe it.
tele_jas said:
Rebooted into TWRP and flashed su1.79 (and my font) -wiped cashe/Dalvik (again).
Before rebooting, I also did the "reboot disemmcwp" using the TWRP terminal - Not sure if I needed to, but I did?
Click to expand...
Click to collapse
Hello, can you post the file that you rooted with?
I'm trying with 2.79 SR3 but I get bootloops and can't boot phone up.
With what supersu did you root?
Thanks!
EDIT: fixed, don't use SR3, use SuperSU-v2.79-201612051815.zip
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
sipe1 said:
Hello, can you post the file that you rooted with?
I'm trying with 2.79 SR3 but I get bootloops and can't boot phone up.
With what supersu did you root?
Thanks!
EDIT: fixed, don't use SR3, use SuperSU-v2.79-201612051815.zip
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Click to expand...
Click to collapse
Yes, v2.79.... Sorry, my fat thumb must have hit the one (1) and I originally posted v1.79...But it's v2.79
tele_jas said:
Yes, v2.79.... Sorry, my fat thumb must have hit the one (1) and I originally posted v1.79...But it's v2.79
Click to expand...
Click to collapse
Still have problem with Super SU binary not installed.
Can you post exact zip that you installed? Can't get root root to work.
sipe1 said:
Still have problem with Super SU binary not installed.
Can you post exact zip that you installed? Can't get root root to work.
Click to expand...
Click to collapse
I pulled it from the link in this post: https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Here is the direct link: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
tele_jas said:
I pulled it from the link in this post: https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Here is the direct link: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Click to expand...
Click to collapse
Thank, problem was in F2FS data.
So no F2FS for data partition, and use SuperSU-v2.79-201612051815.zip https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Hey man i know this is a dumb question but where can i download the weshare app? cannot find it on the us google store :C Thanks bro
J0nhy said:
Hey man i know this is a dumb question but where can i download the weshare app? cannot find it on the us google store :C Thanks bro
Click to expand...
Click to collapse
It was pre-installed on my phone as a stock app - Bottom left corner in the pic attached here, if a pic of the icon helps (I know I sometimes over look apps).
If you don't see it, maybe search for it?? Your launcher may be hiding it?
I thought A2017UV1.1.0B1 is "7.0" not "7.1.1"???
tamahouse02 said:
I thought A2017UV1.1.0B1 is "7.0" not "7.1.1"???
Click to expand...
Click to collapse
If it's, but I was rooted and running several custom mods... So I had to revert back to stock 7.0 and then check for the upgrade (as mentioned in my OP).
tele_jas said:
It was pre-installed on my phone as a stock app - Bottom left corner in the pic attached here, if a pic of the icon helps (I know I sometimes over look apps).
If you don't see it, maybe search for it?? Your launcher may be hiding it?
Click to expand...
Click to collapse
I had that on my phone before upgrading to 7.0 lol im just sticking to titanium backup, thanks man
tele_jas said:
I was fairly certain I did, but had a couple tell me that I probably didn't "check" that box in TWRP?? I'd back up your internal storage, just in case?!?!
Someone also said it wasn't necessary to wipe your internal storage, since the base is so close? I guess you could try it without wiping your internal storage? If it's all jacked up, go back and wipe it.
Click to expand...
Click to collapse
Follow your guide without wiping Internal storage, flash B15 stock system, booted and update OTA, fastbooted twrp, rebooted trwp then flash SuperSU, then restored my B15 data backup.
Everything is fine so far.
Sent from my ZTE A2017U using Tapatalk
So having upgraded to android 8.0 and then creating a backup, I installed TWRP and then SuperSU via TWRP. Now I'm trying to switch to Magisk. Got an error when trying to uninstall SuperSU through the app (uninstall failed), so I flashed SuperSU over with SuperSU unroot.
When I try to install the magisk zip via TWRP, it says that I need to restore the boot.img back to stock. However, when I restore it from the OTA, I get stuck in the infinite bootloop (stuck at Google logo). Luckily I had the backup of the boot.img when the system was working, so I was able to restore that boot.img.
How do I work around this?
did you by any chance had su-hide installed?
wizardwiz said:
did you by any chance had su-hide installed?
Click to expand...
Click to collapse
Nope, the only SU related thing I installed was SuperSU
You might need to flash the full factory image. Out of interest; how come you are switching to Magisk?
dunjamon said:
You might need to flash the full factory image. Out of interest; how come you are switching to Magisk?
Click to expand...
Click to collapse
I feel like Magisk is more supported by the community and just seems more clean/user friendly. Is hiding root with hide-SU just as effective as Magisk?
Koniixii-kun said:
I feel like Magisk is more supported by the community and just seems more clean/user friendly. Is hiding root with hide-SU just as effective as Magisk?
Click to expand...
Click to collapse
I've noticed that around the forum here a lot more people are using Magisk. I ended up switching over on my phone (not on my tablets yet). Day to day I don't really see any difference, but the manager app is definitely more user friendly.
dunjamon said:
I've noticed that around the forum here a lot more people are using Magisk. I ended up switching over on my phone (not on my tablets yet). Day to day I don't really see any difference, but the manager app is definitely more user friendly.
Click to expand...
Click to collapse
How would I go about doing a complete wipe except for the recovery image? Would I do it on TWRP?
Koniixii-kun said:
How would I go about doing a complete wipe except for the recovery image? Would I do it on TWRP?
Click to expand...
Click to collapse
Usually wiping everything except internal storage keeps everything safe (downloads, pictures, documents etc.) However if your on stock recovery don't think you can wipe internal so factory reset should suffice.
I would personally flash the factory image and then flash twrp on top of that. That's what I tend to do with every security update. Probably overkill, but keeps things nice and clean.
Dear XDA,
I screwed up... I think my device is now soft bricked.... :crying:
It all started good on a sunny saturday. I thought this was a good day to try another custom rom. Namely Codename Phoenix.
My device was already rooted so i started with upgrading my TWRP to the latest Blu_Spark TWRP 3.2.1. After flashing the recovery i continued with the ROM. It all went downhill from there....
The install finished and i booted my device. Knowing this could take a while i got into the shower thinking it would finish when i got back. But when i got back it was still booting. Knowing the first boot can take a while so I let it be. After an hour or so it was still stuck on the google logo and the weather and my mood changed for the worse.
I figured something in the process went wrong and tried to boot into recovery. That worked so I thought 'Cool, let's fix it there'. But the recovery was encrypted so i couldn't get to my data. Normally you put in your pincode and it decrypts your phone. This was not the case.... I couldn't put in my pincode so decrypting was out of the question.
Luckily ADB was still working so I downloaded the original Oxygen OS rom and tried to side-load it... This got stuck on 47% for no reason at all. Phone had 100% battery and didn't time-out..
I was really confused, but I let the device do it's thing and maybe things would work out... I was wrong. Everything was worse. Because i tried installing the original firmware it removed the custom recovery....
So now i have a device with no OS and I can't get into recovery. Luckily there is a unbrick tool for OnePlus 5. Following those steps i got stuck on the part that it does not show in my device-manager.
Currently i'm really grumpy and have no idea how to fix this.
I humbly ask for advice. Is this solvable or do i have a wasted OnePlus 5?
Thanks in advance,
Lennard
can you reboot to bootloader?
if yes, you can flash original or custom recovery...
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
[/COLOR]
len.asdf said:
Dear XDA,
I screwed up... I think my device is now soft bricked.... :crying:
It all started good on a sunny saturday. I thought this was a good day to try another custom rom. Namely Codename Phoenix.
My device was already rooted so i started with upgrading my TWRP to the latest Blu_Spark TWRP 3.2.1. After flashing the recovery i continued with the ROM. It all went downhill from there....
The install finished and i booted my device. Knowing this could take a while i got into the shower thinking it would finish when i got back. But when i got back it was still booting. Knowing the first boot can take a while so I let it be. After an hour or so it was still stuck on the google logo and the weather and my mood changed for the worse.
I figured something in the process went wrong and tried to boot into recovery. That worked so I thought 'Cool, let's fix it there'. But the recovery was encrypted so i couldn't get to my data. Normally you put in your pincode and it decrypts your phone. This was not the case.... I couldn't put in my pincode so decrypting was out of the question.
Luckily ADB was still working so I downloaded the original Oxygen OS rom and tried to side-load it... This got stuck on 47% for no reason at all. Phone had 100% battery and didn't time-out..
I was really confused, but I let the device do it's thing and maybe things would work out... I was wrong. Everything was worse. Because i tried installing the original firmware it removed the custom recovery....
So now i have a device with no OS and I can't get into recovery. Luckily there is a unbrick tool for OnePlus 5. Following those steps i got stuck on the part that it does not show in my device-manager.
Currently i'm really grumpy and have no idea how to fix this.
I humbly ask for advice. Is this solvable or do i have a wasted OnePlus 5?
Thanks in advance,
Lennard
Click to expand...
Click to collapse
Don't worry! Your device is safe. At most, you'll be required to wipe your data.
Try using the official twrp recovery here:
https://twrp.me/oneplus/oneplus5.html
If this doesn't work, let me know.
canteo said:
can you reboot to bootloader?
if yes, you can flash original or custom recovery...
Click to expand...
Click to collapse
I can go into fastboot and managed to install TWRP with the comment below!
Zohair.ul.hasan said:
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
[/COLOR]
Don't worry! Your device is safe. At most, you'll be required to wipe your data.
Try using the official twrp recovery here:
https://twrp.me/oneplus/oneplus5.html
If this doesn't work, let me know.
Click to expand...
Click to collapse
Thanks for these words! That's a big relieve
With your link I managed to install TWRP through fastboot. So now i have a custom recovery. The current problem is that my data is encrypted and I cannot decrypt it. There is no option to fill in a password since there is no OS that requires a password. So it's sort of a neverending cycle . Although fastboot, recovery and sideload should work now.
The thing is, previously I tried installing the original firmware and that failed at 47%. So i'm not sure what to do now.
I tried installing 'codeworkx universal twrp 3.2.1-0 recovery' since he seems to have fixed the encrypt issue. But when I tried sideloading the file it says "Zip file is corrupt!". So no succes there yet.
To be precise, this is the threat for Codeworkx Universal TWRP : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
And i downloaded and tried installing: twrp-3.2.1-0-universal-codeworkx-cheeseburger.img
I was thinking about downloading the latest Codename Phoenix ROM, but when I try to download the latest release the file is name "Codename-Phoenix-NOS-8.1-oneplus5t-20180303.zip". That implies it's only for the 5t and not for the 5. So that could be my original problem? That i downloaded the wrong ROM?
That aside.
Should I try to get the download link for CNP and download the latest release for the OP5 and install that.
Or
Should i try to install the original firmware. Reset everything and start over from the beginning (unlocking, rooting, etc..)
Thanks again for all the help
len.asdf said:
I can go into fastboot and managed to install TWRP with the comment below!
Thanks for these words! That's a big relieve
With your link I managed to install TWRP through fastboot. So now i have a custom recovery. The current problem is that my data is encrypted and I cannot decrypt it. There is no option to fill in a password since there is no OS that requires a password. So it's sort of a neverending cycle . Although fastboot, recovery and sideload should work now.
The thing is, previously I tried installing the original firmware and that failed at 47%. So i'm not sure what to do now.
I tried installing 'codeworkx universal twrp 3.2.1-0 recovery' since he seems to have fixed the encrypt issue. But when I tried sideloading the file it says "Zip file is corrupt!". So no succes there yet.
To be precise, this is the threat for Codeworkx Universal TWRP : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
And i downloaded and tried installing: twrp-3.2.1-0-universal-codeworkx-cheeseburger.img
I was thinking about downloading the latest Codename Phoenix ROM, but when I try to download the latest release the file is name "Codename-Phoenix-NOS-8.1-oneplus5t-20180303.zip". That implies it's only for the 5t and not for the 5. So that could be my original problem? That i downloaded the wrong ROM?
That aside.
Should I try to get the download link for CNP and download the latest release for the OP5 and install that.
Or
Should i try to install the original firmware. Reset everything and start over from the beginning (unlocking, rooting, etc..)
Thanks again for all the help
Click to expand...
Click to collapse
Nice to hear that!
To be clear, does the TWRP decrypt you data? When you click install in TWRP, is it a bunch of randomly named files?
I think you should go ahead with installing CNP, you shouldn't have any problems with it now that you've got the correct version.
Good luck!
Zohair.ul.hasan said:
Nice to hear that!
To be clear, does the TWRP decrypt you data? When you click install in TWRP, is it a bunch of randomly named files?
I think you should go ahead with installing CNP, you shouldn't have any problems with it now that you've got the correct version.
Good luck!
Click to expand...
Click to collapse
Yeah it's a bunch of random file names. Like "2TAjnCI8CpHDL38Oh684DuTSgaO".
Alright, i'll let you know if I succeed. Thanks for the help
len.asdf said:
Yeah it's a bunch of random file names. Like "2TAjnCI8CpHDL38Oh684DuTSgaO".
Alright, i'll let you know if I succeed. Thanks for the help
Click to expand...
Click to collapse
Wait! Staying encrypted is a bunch of trouble. I recommend u to follow these steps:
Go to recovery
Select wipe
Select advanced wipe
Clear dalvik and cache
Go back
Select wipe
Click "Format Data"
Type in yes
Go back
Select wipe
Swipe to factory reset
Reboot recovery
Transfer the ROM from PC to phone
Install it
Zohair.ul.hasan said:
Wait! Staying encrypted is a bunch of trouble. I recommend u to follow these steps:
Go to recovery
Select wipe
Select advanced wipe
Clear dalvik and cache
Go back
Select wipe
Click "Format Data"
Type in yes
Go back
Select wipe
Swipe to factory reset
Reboot recovery
Transfer the ROM from PC to phone
Install it
Click to expand...
Click to collapse
Haha thanks! Just in time. Was still downloading the latest CNP .
Whew! Update me after flashing.
Zohair.ul.hasan said:
Whew! Update me after flashing.
Click to expand...
Click to collapse
Hmm, the installation should be a succes. But when i tried to reboot and start up the OS / System it just reboots into TWRP.... ? It's sort of boot looping into recovery.
I tried installing a couple of times with and without wiping dalvik/cache/system.
Could the install file not be complete?
On a side note, my data is not encrypted
len.asdf said:
Hmm, the installation should be a succes. But when i tried to reboot and start up the OS / System it just reboots into TWRP.... ? It's sort of boot looping into recovery.
I tried installing a couple of times with and without wiping dalvik/cache/system.
Could the install file not be complete?
On a side note, my data is not encrypted
Click to expand...
Click to collapse
Did you factory reset by going into wipe>swipe to factory reset?
If not then do that and flash it
Zohair.ul.hasan said:
Did you factory reset by going into wipe>swipe to factory reset?
If not then do that and flash it
Click to expand...
Click to collapse
YES! It work. Many thanks
len.asdf said:
YES! It work. Many thanks
Click to expand...
Click to collapse
Congrats! Please like my replies if you don't mind
Zohair.ul.hasan said:
Congrats! Please like my replies if you don't mind
Click to expand...
Click to collapse
But of course! Already did that. But i'm not sure if it shows or not. Tried clicking multiple times on the thanks button but it doesn't highlight. It should do that right?
len.asdf said:
But of course! Already did that. But i'm not sure if it shows or not. Tried clicking multiple times on the thanks button but it doesn't highlight. It should do that right?
Click to expand...
Click to collapse
Yes it should but that's okay
Zohair.ul.hasan said:
Yes it should but that's okay
Click to expand...
Click to collapse
installed the xda app and there I could give you a 'thanks'
I'm using the tutorial on the LineageOS wiki for the Us996. I've unlocked the bootloader via official means from LG, but when it comes time to send the recovery via fastboot, it successfully sends and writes it, it even let's me boot into it, after pulling the battery, and using the correct button commands. But if I restart and try to enter again I'm greeted by the official erase everything recovery.
Does anyone know what I'm doing wrong? Do I need to flash root to get the recovery to stick?
Take a look at this video. If you have TWRP installed right, and are going to it through a battery pull and the power button volume down combination, then the screen that comes up looks scary and looks like you'll "format" your phone, but as you see in this video, you don't.
baldybill said:
Take a look at this video. If you have TWRP installed right, and are going to it through a battery pull and the power button volume down combination, then the screen that comes up looks scary and looks like you'll "format" your phone, but as you see in this video, you don't.
https://www.youtube.com/watch?v=https://www.youtube.com/watch?v=tDq0qMbgjL4
Click to expand...
Click to collapse
See I've gotten into TWRP, then I reboot system(actual Android not just restarting recovery).the problem is When I power off my phone and tried to get back into TWRP, I clicked yes and yes and it proceeded to wipe my phone. TWRP wasn't there just factory reset lol
lowsnamebrand said:
See I've gotten into TWRP, then I reboot system(actual Android not just restarting recovery).the problem is When I power off my phone and tried to get back into TWRP, I clicked yes and yes and it proceeded to wipe my phone. TWRP wasn't there just factory reset lol
Click to expand...
Click to collapse
Not sure why it isnt happening automatically (it usually does when flashing things like magisk to root) but when you get into twrp or with root rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak. If in twrp first go into the mount page and uncheck the box at the bottom that says something about system read only first, then you can use the file manager.
Or since it sounds like you want to flash lineage, just flash the lineageos zip (and then optionally opengapps and root). Be sure to format data too (wipe->format data->yes). Then if you dont have lineage on an sdcard ready to go you could reboot recovery so that the formatted data is ready then connect to pc and send the zips over by using adb push C:\path\to\lineage.zip /sdcard/
Phoenix591 said:
Not sure why it isnt happening automatically (it usually does when flashing things like magisk to root) but when you get into twrp or with root rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak. If in twrp first go into the mount page and uncheck the box at the bottom that says something about system read only first, then you can use the file manager.
Or since it sounds like you want to flash lineage, just flash the lineageos zip (and then optionally opengapps and root). Be sure to format data too (wipe->format data->yes). Then if you dont have lineage on an sdcard ready to go you could reboot recovery so that the formatted data is ready then connect to pc and send the zips over by using adb push C:\path\to\lineage.zip /sdcard/
Click to expand...
Click to collapse
What I'm thinking about doing is flashing TWRP again, on first boot(of TWRP) backing up my current rom(stock) and trying to boot into recovery again, because if it doesn't stick again, it'll wipe but at least I'll have a backup.
I've noticed a lot of different root files which would you recommend?
lowsnamebrand said:
What I'm thinking about doing is flashing TWRP again, on first boot(of TWRP) backing up my current rom(stock) and trying to boot into recovery again, because if it doesn't stick again, it'll wipe but at least I'll have a backup.
I've noticed a lot of different root files which would you recommend?
Click to expand...
Click to collapse
Sorry for the double post but does the "LG factory reset" stay even after having TWRP installed? Like will I always have to answer yes twice to enter TWRP?
lowsnamebrand said:
Sorry for the double post but does the "LG factory reset" stay even after having TWRP installed? Like will I always have to answer yes twice to enter TWRP?
Click to expand...
Click to collapse
Yes thats always the same.
If you don't flash lineage or something to root stock (I reccommend magisk since the alternative, Supersu, is owned by some Chinese company, and magisk has various modules that do many things) and don't rename /system/recovery-from-boot.p manually (theres a file manager under advanced in twrp) the stock rom will use that file to reflash stock recovery any time it boots.
Phoenix591 said:
Yes thats always the same.
If you don't flash lineage or something to root stock (I reccommend magisk since the alternative, Supersu, is owned by some Chinese company, and magisk has various modules that do many things) and don't rename /system/recovery-from-boot.p manually (theres a file manager under advanced in twrp) the stock rom will use that file to reflash stock recovery any time it boots.
Click to expand...
Click to collapse
Awesome I think my issue is not renaming that file and the stock rom reinstalling stock recovery. I've used SuperSU, never used magisk, is there a stickied release thread for it?
lowsnamebrand said:
Awesome I think my issue is not renaming that file and the stock rom reinstalling stock recovery. I've used SuperSU, never used magisk, is there a stickied release thread for it?
Click to expand...
Click to collapse
Its got more than a thread, has a whole section. Anyway heres the main release thread
Phoenix591 said:
Its got more than a thread, has a whole section. Anyway heres the main release thread
Click to expand...
Click to collapse
You've been a huge help, thank you! I'll report back later tonight, when I can actually work on my phone
So i was able to obtain root aswell as installed twrp, the only issue I had was every rom I tried refused to boot. They just hung at the loading screen, that includes the back up I'd made of stock, is there something I missed?
lowsnamebrand said:
So i was able to obtain root aswell as installed twrp, the only issue I had was every rom I tried refused to boot. They just hung at the loading screen, that includes the back up I'd made of stock, is there something I missed?
Click to expand...
Click to collapse
If you mean the boot animation, the very first time can take a good while, like 20 minutes. Also make sure you've formatted /data if you havnt yet especially going to lineage.
Phoenix591 said:
If you mean the boot animation, the very first time can take a good while, like 20 minutes. Also make sure you've formatted /data if you havnt yet especially going to lineage.
Click to expand...
Click to collapse
Sorry for the late reply, yeah I think I just let the boot animation go for around 5, I'm gonna have to try reflashing it and hoping for the best, I'll be sure to answer back when I get a chance
OK, I know this is an old thread - but I just got a replacement US996 phone; my old standby has a charger plug problem so I decided to get another one and put a rooted stock Oreo ROM on it. However, I'm having the same issue as the OP. Get into fastboot, flash TWRP (I have the 3.3.1-0 version, as the newer 3.3.1-1 version does not have any download mirrors). The flash appears to go just fine, it says the write was completed. However, when I reboot into adb mode and do "adb reboot recovery" I get "no command" and the little droid with his belly hatch open. So obviously TWRP wasn't flashed. The OP says he eventually was able to get it to work and install root. How did you fix the issue?
Do I still need to do the old recowvery shenanigans that we had to do back when the phone first came out?
Thanks!
I believe you MUST use the button combo to reboot into twrp.
See here:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239/post78513963
pistacios said:
I believe you MUST use the button combo to reboot into twrp.
See here:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239/post78513963
Click to expand...
Click to collapse
I've done that. The problem is that TWRP hasn't actually been installed via fastboot flash recovery - it goes through the motions, SAYS it's been installed, but when I do the button combo, it actually does reset my phone rather than booting into TWRP.
---------- Post added at 09:36 AM ---------- Previous post was at 08:55 AM ----------
Disregard the above. Flashed it again (4th time), and it finally took.
The same happened with my wife's US996 now that you mention it. Took a few tries and was a bit frustrating.
When I flashed TWRP on mine it was a "one and done".
Glad you got it sorted.
Thanks - all good. Rooted stock Oreo ROM installed, working great.