Related
Update 2 after some fiddling I found that after flashing Pico Capps hdxposed is needed to make the play store work on this build http://forum.xda-developers.com/showthread.php?t=2618158
Update 1 New lolipop ota, this appears to be based on lolipop 5.1 and as such requires xposed unofficial by romracer if you want to use xposed Xposed for 5.0 would not flash for me. Same upgrade steps as before just this one instead of the bottom one and change your xposed package
https://mega.nz/#!i5RRCKQZ!NC291mcIo-2yzr23j8Vg_mLZ11ECql4lL_xen6xwXuM
update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin
siegesoldier said:
this is the developer preview, sorry if the title is a little misleading. Thanks to http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Use at your own risk.
https://www.dropbox.com/s/38i2lqq5p...review_ariel-20.5.2.0_user_520033250.bin?dl=0
Hopefully someone can figure out how to make this thing boot when flashed from TWRP
Click to expand...
Click to collapse
Important update, the instructions below are not to be followed !!! They are historical ...
Same drill as in here :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Replace the original META-INF/com/google/android/updater-script with the one from the zip below. Remove "images" directory. This will ensure that your bootloader stays 4.5.3 and unlocked. When TWRP asks to add root, say yes.
If for some reason you lose TWRP (recovery), reflash it from within 5.0. Since you have root, no biggie. I'll play with this a bit too, but later.
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
siegesoldier said:
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
Click to expand...
Click to collapse
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip).
The trick is that you install Lollipop, install root, and install the new bootloader separately. It should boot OK and you should have root in 5, but you'll lose TWRP (it won't be able to boot since the bootloader will probably be signed). To get TWRP back you'll need to downgrade to 4.5.3
bibikalka said:
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip
Click to expand...
Click to collapse
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
siegesoldier said:
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
Click to expand...
Click to collapse
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Upon reflection, there is a chance you have a bit of a soft brick. If the factory reset option does not come up, it may end up a little tricky to fix things. I wonder if you'd be able to connect via adb before it reboots.
bibikalka said:
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Click to expand...
Click to collapse
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
siegesoldier said:
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
Click to expand...
Click to collapse
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
I think TWRP just blocked it from updating. Oh well, if the ports at home don't work, I was eventually going to get it replaced anyway since I had a blue discoloration on my screen. Glad to be of some moderate use to the community instead of a leecher for once. May the next person have some luck!
bibikalka said:
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
Click to expand...
Click to collapse
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
siegesoldier said:
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
Click to expand...
Click to collapse
So no adb anymore? I am not sure how SuperSu comes in, there gotta be su program somewhere.
Anyway, the great news is that JMZ is going to be back soon. That's going to boost our tinkering capabilities by 300%
siegesoldier said:
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Click to expand...
Click to collapse
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
bibikalka said:
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
Click to expand...
Click to collapse
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
siegesoldier said:
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
Click to expand...
Click to collapse
Interesting, at what stage of the update did this happen? 5.2.0 file system is slightly packaged and is pain in the neck to peak into, but in 4.5.3 the recovery is updated via a pretty specific command install-recovery.sh , and I cannot find any references to this in updater-script. So I wonder at what stage will this be run. Also, there is no direct image for recovery, one has to reconstruct it as the commands below do. A bit messy ...
install-recovery.sh
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Edit: It kind of looks like /system/etc/install-recovery.sh will be run at every boot. So I wonder if TWRP just renames it to something and calls it "protection". I guess one can double check the file system after 5.2.0 update while still in TWRP, and see what happened to recovery files.
Help
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
hawkazn said:
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
Click to expand...
Click to collapse
Last time this procedure ended up with a soft brick. Are you sure you want to pursue this route?
Help
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
hawkazn said:
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
Click to expand...
Click to collapse
Meaning exactly what? It'd be possible to replace the camera app, one for another. Do you think some other system stuff is involved such as some sort of settings?
You'll have to find a way to mount the big 5.2.0 system update file as a filesystem, then you could read what's in there, including the camera stuff.
TWRP help
So I downloaded the zip file for 5.0 and it flashed and asked to install super user. I had to download the apk for supersu and then update it.
But the problem is that I lost my twrp. I push the volume + and power and it just reboots. I also lost my play store. Any thoughts how to get twrp back on?
Just got a brand new 2017 Shield. Got in to fast boot using "adb reboot bootloader" as I don't have a game controller and I was unable to get a usb keyboard or any other controller to work. Booted to latest TWRP and installed SuperSU. Now it doesn't boot. I'm just getting a bunch of warnings and errors regarding being unlocked and the system being modified. Then, I just get a black screen. Did I just screw up? Is there new update that I installed with DM verity enabled and this is causing it to stop booting?
Either way, it does not boot far enough for me to get in via ADB and I can't get back in to fastboot. Any other things I can try to get into fastboot? Assuming I can, what's the latest image I will need to reflash back to stock?
Any assistance/guidance appreciated. Thanks. :fingers-crossed:
Update: I was able to find a KB that works to get in to fastboot mode. So that's working. Is the latest development image from NVidia going to work for me?
Update2: So I just went for it since I got inpatient waiting for responses. Back up and running after flashing the latest developer image. Now to get SuperSU or Magisk working?
Final Update: It looks like I used a slightly older SuperSU (2.79) installer which I'm guessing broke DM verity (or something worse). After installing TWRP (permanently), I sideloaded the new SuperSU (2.82 SR3) zip and everything worked just peachy.
joojoobee666 said:
Just got a brand new 2017 Shield. Got in to fast boot using "adb reboot bootloader" as I don't have a game controller and I was unable to get a usb keyboard or any other controller to work. Booted to latest TWRP and installed SuperSU. Now it doesn't boot. I'm just getting a bunch of warnings and errors regarding being unlocked and the system being modified. Then, I just get a black screen. Did I just screw up? Is there new update that I installed with DM verity enabled and this is causing it to stop booting?
Either way, it does not boot far enough for me to get in via ADB and I can't get back in to fastboot. Any other things I can try to get into fastboot? Assuming I can, what's the latest image I will need to reflash back to stock?
Any assistance/guidance appreciated. Thanks. :fingers-crossed:
Update: I was able to find a KB that works to get in to fastboot mode. So that's working. Is the latest development image from NVidia going to work for me?
Update2: So I just went for it since I got inpatient waiting for responses. Back up and running after flashing the latest developer image. Now to get SuperSU or Magisk working?
Final Update: It looks like I used a slightly older SuperSU (2.79) installer which I'm guessing broke DM verity (or something worse). After installing TWRP (permanently), I sideloaded the new SuperSU (2.82 SR3) zip and everything worked just peachy.
Click to expand...
Click to collapse
Ummm sooner or later you will probably run into problems by installing twrp permanently, really all you had to do was fastboot twrp and install the newer supersu
jionny said:
Ummm sooner or later you will probably run into problems by installing twrp permanently, really all you had to do was fastboot twrp and install the newer supersu
Click to expand...
Click to collapse
What kind of issues do you expect I will have? So far it's been fine, multiple reboots and what not as I was getting everything setup. Worse case scenario I just need to fastboot recovery and or boot?
joojoobee666 said:
What kind of issues do you expect I will have? So far it's been fine, multiple reboots and what not as I was getting everything setup. Worse case scenario I just need to fastboot recovery and or boot?
Click to expand...
Click to collapse
Look around the nvidia shield tv forum and you will see multiple people have problems when they update when they permanent install. its one reason why you don't see any tutorials of permanent install of twrp all tutorials instruct fastboot install
jionny said:
Look around the nvidia shield tv forum and you will see multiple people have problems when they update when they permanent install. its one reason why you don't see any tutorials of permanent install of twrp all tutorials instruct fastboot install
Click to expand...
Click to collapse
Ok, thanks for the info. I did see some people that were saying they had issues but nothing I saw was really clear initially. However, after some further research I see the main issue is if an update tried to apply with TWRP installed, things can go hay-wire. I'll go ahead and remove. Just sucks that I can't remotely use TWRP. Some of my devices are nowhere near a PC. I just feel naked without it installed.
Edit: I downgraded to the latest image from NVidia, installed the latest OTA and re-rooted again, sans TWRP.
So I was messing with my phone because I just got it rooted, I was excited; my last phone that was rooted was my Xperia C and that was years ago. I messed with Magisk modules and somehow came across a video on how to uninstall a module whereas I was just deleting them in the Magisk App. I tried the uninstall mod. I used TWRP Recovery but then the uninstall mod did not install. Now I am stuck with the android one logo. Please I need help .
Update! I was still trying to wipe the data. I don't know why it went through now it doesn't even go to the android one logo
Update no. 2! so i tried flashing it and it worked, I completely forgot about the MiFlashingTool, I was hesitant to actually flash with TRWP just because after I unlocked OEM on my device I can't seem to transfer files anymore in my phone (but probably it's because of the drivers). So I flashed it and rooted it again. I kinda am pretty knowledgeable about it too now. All's well that ends well.
Good to hear you were able to recover your phone. Always remember to do a full backup in TWRP before experimenting, in case something goes wrong
Tepig said:
Good to hear you were able to recover your phone. Always remember to do a full backup in TWRP before experimenting, in case something goes wrong
Click to expand...
Click to collapse
how to do a full back up in TWRP ? and what if i use the "Hot Boot" TWRP ?
#newbiehere
iSEKAI said:
how to do a full back up in TWRP ? and what if i use the "Hot Boot" TWRP ?
#newbiehere
Click to expand...
Click to collapse
Look at backup in twrp ? full means tick all the boxes. And hotboot means that you don't have a sticking twrp. However you still can backup on a MicroSD card.
henk_j said:
Look at backup in twrp ? full means tick all the boxes. And hotboot means that you don't have a sticking twrp. However you still can backup on a MicroSD card.
Click to expand...
Click to collapse
hmm.. so having twrp installed is really neccesary here .. ?
can i installed twrp recovery on my mi a1 running last pie OS ?
and if it can , will it make me unable to receive OTA update?
i know i can just flash the new update via twrp but the were kinda huge difference.. i mean OTA update were only around 250MB on the last patch feb 5th
but if we wanna flash it via twrp (i hotboot it back then) the file was above 1GB ?
NooDoAh said:
So I was messing with my phone because I just got it rooted, I was excited; my last phone that was rooted was my Xperia C and that was years ago. I messed with Magisk modules and somehow came across a video on how to uninstall a module whereas I was just deleting them in the Magisk App. I tried the uninstall mod. I used TWRP Recovery but then the uninstall mod did not install. Now I am stuck with the android one logo. Please I need help .
Update! I was still trying to wipe the data. I don't know why it went through now it doesn't even go to the android one logo
Update no. 2! so i tried flashing it and it worked, I completely forgot about the MiFlashingTool, I was hesitant to actually flash with TRWP just because after I unlocked OEM on my device I can't seem to transfer files anymore in my phone (but probably it's because of the drivers). So I flashed it and rooted it again. I kinda am pretty knowledgeable about it too now. All's well that ends well.
Click to expand...
Click to collapse
you can try installing twrp and flash magisk install via twrp.you can try installing twrp and flash magisk uninstall via twrp.
Dear all,
first of all I would like to be sorry if I'm saying something worng. I'm not so expert about Android world.
I've got a OnePlus 6T that I've rooted with the help of a friend some months ago.
Not it's a lot that I keep see the notification abount the OS update and I keep skipping it but it's bothering me so... I searched for a guide and I found this (https://oneplus.gadgethacks.com/how...thout-losing-root-no-computer-needed-0192638/) (I hope I can post it also if it's from another website).
It seems so simple, I've downloaded the OTA update, the TWRP and the Magisk. My issue is that whene I reboot to the recovery I'm not booting into TWRP but I suppose into the OnePlus recovery instead.
I searched angain and found this other guide (https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953) that is more complete but I can't understand if it's the proper guide I need to follow to update my device keeping it rooted and most of all without loosing any data.
Thanks,
Riki
The first guide you linked to is wrong. Do not follow that. That is why you don't have TWRP anymore. The second guide you linked to on XDA is correct. Follow the TWRP guide. Once you have TWRP reinstalled.
You must download the zip from the second link you posted here at XDA.
Flash the Zip in TWRP. This flash the update to the opposite slot. It also wipes out TWRP and replaces it with the stock recovery.
Now you must reinstall TWRP. Flash the TWRP installer. This will flash TWRP to both slots.
Now reboot to recovery. This will reboot to the new slot where you update was just flashed.
This is when you install Magisk to the updated slot. You MUST do this.
Now reboot to system after you installed Magisk.
Now you have updated without losing any data.
The guide in the second link says to use the Magisk uninstaller. I've personally never done this. This is probably for people who use all sorts of weird add-ons and such. I don't know. Never uninstalled Magisk, never had a problem. That's all I can say. You can try it, or you can follow the official instructions.
OhioYJ said:
The first guide you linked to is wrong. Do not follow that. That is why you don't have TWRP anymore. The second guide you linked to on XDA is correct. Follow the TWRP guide. Once you have TWRP reinstalled.
You must download the zip from the second link you posted here at XDA.
Flash the Zip in TWRP. This flash the update to the opposite slot. It also wipes out TWRP and replaces it with the stock recovery.
Now you must reinstall TWRP. Flash the TWRP installer. This will flash TWRP to both slots.
Now reboot to recovery. This will reboot to the new slot where you update was just flashed.
This is when you install Magisk to the updated slot. You MUST do this.
Now reboot to system after you installed Magisk.
Now you have updated without losing any data.
The guide in the second link says to use the Magisk uninstaller. I've personally never done this. This is probably for people who use all sorts of weird add-ons and such. I don't know. Never uninstalled Magisk, never had a problem. That's all I can say. You can try it, or you can follow the official instructions.
Click to expand...
Click to collapse
Thanks OhioYJ,
so, before I can follow the TWRP guide, I must reinstall it. Could you please give me a link to a guide on how to do it?
Thanks again,
Riki
RikiBez said:
Thanks OhioYJ,
so, before I can follow the TWRP guide, I must reinstall it. Could you please give me a link to a guide on how to do it?
Click to expand...
Click to collapse
[Guide] OnePlus 6T [Fajita]: Unlock | Flash TWRP | Root | Nandroid & EFS Backup !!
Thanks to Funk Wizard again. Don't forget the section about backing up your modem, this is always important in case something really goes wrong. You'll probably never need it, but if you ever do you'll be really glad you have it.
OhioYJ said:
[Guide] OnePlus 6T [Fajita]: Unlock | Flash TWRP | Root | Nandroid & EFS Backup !!
Thanks to Funk Wizard again. Don't forget the section about backing up your modem, this is always important in case something really goes wrong. You'll probably never need it, but if you ever do you'll be really glad you have it.
Click to expand...
Click to collapse
I followed the guide but I get stucked into a loot without been able to boot into TWRP. I'm only able to enter the recovery mode and the fastboot mode but when I launch the command from Windows it finish with no error but the phone still stuck on the fastboot logo or the oneplus logo. After many tryes now I've got only this and also errors on PC:
Old_video_link_removed
EDIT: At the moment I'm not event able to enter the recovery mode, I keep restarting it and it will only boot to the fastmode.
RikiBez said:
I followed the guide but I get stucked into a loot without been able to boot into TWRP. I'm only able to enter the recovery mode and the fastboot mode but when I launch the command from Windows it finish with no error but the phone still stuck on the fastboot logo or the oneplus logo. After many tryes now I've got only this and also errors on PC:
https://youtu.be/7Re-p7Z1yhc
EDIT: At the moment I'm not event able to enter the recovery mode, I keep restarting it and it will only boot to the fastmode.
Click to expand...
Click to collapse
It's booting into recovery, but the OnePlus recovery. That is what the menu that is asking you to select a language is. When you enter the command fastboot boot trwp.img you don't get any sort of error? Or the phone doesn't respond?
OhioYJ said:
It's booting into recovery, but the OnePlus recovery. That is what the menu that is asking you to select a language is. When you enter the command fastboot boot trwp.img you don't get any sort of error? Or the phone doesn't respond?
Click to expand...
Click to collapse
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
RikiBez said:
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
Click to expand...
Click to collapse
Is fastboot installed? Are you typing the commands correctly?
Sent from my OnePlus 6T using XDA-Developers Legacy app
RikiBez said:
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
Click to expand...
Click to collapse
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
CazeW said:
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
Click to expand...
Click to collapse
If I want to clean flash my 9.0.13 rooted TWRP. What do I need to uninstall or wipe? Im on 9.0.13 currently
Sent from my OnePlus 6T using XDA-Developers Legacy app
i7vSa7vi7y said:
Is fastboot installed? Are you typing the commands correctly?
Sent from my OnePlus 6T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Fastboot was working until I reinstalled adb and OnePlus drivers.
CazeW said:
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
Click to expand...
Click to collapse
I didn’t know any other way. That’s why I asked how to do it. Anyway I’m running the command from the right folder. Maybe something broke on my laptop.
Yesterday evening I tried from a new laptop windows 10, installed adb and OnePlus driver for the first time and I was able to run the commands without the error not finding the command but:
Fastboot boot twrp.image returned me an error
If I run fastboot flash boot twrp.image it does not give me error but the phone does not response. It only boot to the boot loader.
RikiBez said:
I didn’t know any other way. That’s why I asked how to do it. Anyway I’m running the command from the right folder. Maybe something broke on my laptop.
Yesterday evening I tried from a new laptop windows 10, installed adb and OnePlus driver for the first time and I was able to run the commands without the error not finding the command but:
Fastboot boot twrp.image returned me an error
If I run fastboot flash boot twrp.image it does not give me error but the phone does not response. It only boot to the boot loader.
Click to expand...
Click to collapse
Try uninstalling adb. Delete the whole folder and install it again. Try updating your netframework on your PC and the latest C++
Sent from my OnePlus 6T using XDA-Developers Legacy app
I'm creating a new tread about the issue and the state where I am because now I can't update or keep data, I just need to recover the phone to a normal state.
RikiBez said:
I'm creating a new tread about the issue and the state where I am because now I can't update or keep data, I just need to recover the phone to a normal state.
Click to expand...
Click to collapse
Use the msm tool for that
Sent from my OnePlus 6T using XDA-Developers Legacy app
Flashing the fastboot rom would probably have gotten you back in and maybe with your data in tact. Now fair warning I'm a Linux user anyways, but really fastboot and adb are so much easier in Linux. For people that have issues, it sometimes is easier just to make a bootable USB / CD of Linux Mint or Ubuntu and then from Synaptic or the Package manager install adb and fastboot. No drivers or anything else to install, everything will just work.
Last time I got stuck in fastboot I just used the fastboot ROM to get back to bootable.
OhioYJ said:
Flashing the fastboot rom would probably have gotten you back in and maybe with your data in tact. Now fair warning I'm a Linux user anyways, but really fastboot and adb are so much easier in Linux. For people that have issues, it sometimes is easier just to make a bootable USB / CD of Linux Mint or Ubuntu and then from Synaptic or the Package manager install adb and fastboot. No drivers or anything else to install, everything will just work.
Last time I got stuck in fastboot I just used the fastboot ROM to get back to bootable.
Click to expand...
Click to collapse
Those fastboot roms have sure saved me from raging before
I would also recommend using migrate, it's in the play store and it backs up all your data and then puts it in a flashable zip
i7vSa7vi7y said:
If I want to clean flash my 9.0.13 rooted TWRP. What do I need to uninstall or wipe? Im on 9.0.13 currently
Sent from my OnePlus 6T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Do a factory reset from TWRP and flash the full ROM.
One best method...and the method that works 100% tested for upgrading a rooted OOS to new OOS version without any loss of data, without any issues.
I'll mention the guide that I have used to upgrade from 9.0.12 rooted to 9.0.13 rooted. Without any loss of data
Download latest OOS full ROM
Boot to TWRP
Flash OOS 9.0.13
Flash TWRP installer zip
Reboot system
Phone will boot.
Now go back to recovery mode
Flash Magisk if u want root again
Done
No confusion. No data loss. Not being stuck. Sweet and Simple.
sanjeev7 said:
One best method...and the method that works 100% tested for upgrading a rooted OOS to new OOS version without any loss of data, without any issues.
I'll mention the guide that I have used to upgrade from 9.0.12 rooted to 9.0.13 rooted. Without any loss of data
Download latest OOS full ROM
Boot to TWRP
Flash OOS 9.0.13
Flash TWRP installer zip
Reboot system
Phone will boot.
Now go back to recovery mode
Flash Magisk if u want root again
Done
No confusion. No data loss. Not being stuck. Sweet and Simple.
Click to expand...
Click to collapse
So I don't have to wipe my system data or anything. I heard some people had the problem of getting stuck or that there was a red warning screen that popped up when booting, and I'm not talking about the bootloader message. I'm currently on 9.0.11. Also should I download the latest version of TWRP or should I use the one I'm using currently. Don't wanna mess anything up. Another guide I read said I should flash the oos rom, then TWRP, than magisk
Heya everyone,
I've got my 6T with Android 10 rooted that it's giving me some troubles. I made some mistakes when I updated to android 10 so now I would like someone to help me doing these steps the proper way.
I would like to:
Reset the whole phone with a fresh install of Android like factory, if possibile already updated to the Android 10.3.0 (i've already downloaded the full OTA and Ive got ADB installed and working),
then I'll want to install TWRP and Magisk from scratch too and at the end I'll install apps and I'll restore datas (only those needed like pictures or google drive/whatsapp backups).
I'm not sure which steps do I have to follow to do this without breaking something during the process.
Thanks
All is written here and still valid, read first posts carefully.
Use latest .30 twrp version and latest Magisk zip
https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789
Striatum_bdr said:
All is written here and still valid, read first posts carefully.
Use latest .30 twrp version and latest Magisk zip
https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789
Click to expand...
Click to collapse
Thanks. I'll follow the guide.
Before rooting how could I factory reset everything and update the phone. I would like to be sure that everything done in the past will be cleared.
Thanks
Sent from my ONEPLUS A6013 using Tapatalk
RikiBez said:
Thanks. I'll follow the guide.
Before rooting how could I factory reset everything and update the phone. I would like to be sure that everything done in the past will be cleared.
Thanks
Click to expand...
Click to collapse
Unlocking the bootloader is a factory reset. If already done, reboot in recovery and do it from there
Striatum_bdr said:
Unlocking the bootloader is a factory reset. If already done, reboot in recovery and do it from there
Click to expand...
Click to collapse
Do you mean from the TWRP recovery? I checked it but I don't know from which menu to do it.
Or is it possible and better to do it from ADB? If yes which command do I need to use?
RikiBez said:
Do you mean from the TWRP recovery? I checked it but I don't know from which menu to do it.
Or is it possible and better to do it from ADB? If yes which command do I need to use?
Click to expand...
Click to collapse
There is a factory reset function in phone settings > system
If not enough
https://twrp.me/faq/whattowipe.html
Please use Google that's exactly what I do to answer you
Striatum_bdr said:
There is a factory reset function in phone settings > system
If not enough
https://twrp.me/faq/whattowipe.html
Please use Google that's exactly what I do to answer you
Click to expand...
Click to collapse
I used Google and searched the forum. I read some guides but I made the thread cause I would like to have an help from someone that knows what I need to do step by step cause I don't want to fail.
Sent from my ONEPLUS A6013 using Tapatalk
[deleted]
Follow this thread to rollback to pie..
This will wipe your data and do the reset that you want..
From there you can update to latest 10.3.0 and install twrp and magisk afterwards...
https://forum.xda-developers.com/on...owngrade-oos-android-10-t4000645/post80843523
An important question is. Do you need TWRP? Because you don't need TWRP for root. If you want root, i suggest just flashing the patched boot.img.
You can factory reset from any recovery by wiping everything.
bokkoman said:
An important question is. Do you need TWRP? Because you don't need TWRP for root. If you want root, i suggest just flashing the patched boot.img.
You can factory reset from any recovery by wiping everything.
Click to expand...
Click to collapse
I'm not really sure for what I need TWRP but I always used to install it with Magisk.
Sent from my ONEPLUS A6013 using Tapatalk
Steps that I followed to solve
I would like to thanks @Striatum_bdr and @cultofluna for their tips.
I solved doing this:
I saved camera pictures, downloads folder and anything else I need by dragging and dropping from phone to PC. I also made backups of Whatsapp, Nova Launcher and other tools I would to restore.
I downloaded the rollback and folloed the instructions from here: https://forum.xda-developers.com/on...owngrade-oos-android-10-t4000645/post80843523
After that I started the phone skipping most of the requests
Updated it a couple of times until I was on Android 10.3.0
Then I followed the standard rooting guide for the OnePlus 6T: https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789 using files from this new post related to Android 10: https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
When I finished I had a fully rooted Android 10.3.0 with TWRP on both slots.
At the end I made a factory reset from the system setting to clear the my answers to the questions that I skipped at the beginning and I configured it as I wish.
I downloaded apps and restored files and backups from PC and cloud drives
List of files that I've used:
https://drive.google.com/file/d/1L7EZGx5mgeQYXO19Vsp9FWu9GXhF45Qs/view (PC)
https://drive.google.com/file/d/1-uWQn-oHu_ROuDVCzIyrExoRbsSBYTtU/view (PC)
https://www.androidfilehost.com/?fid=4349826312261677894 (PC)
https://www.androidfilehost.com/?fid=4349826312261677893 (Phone)
https://github.com/topjohnwu/Magisk/releases/download/v20.1/Magisk-v20.1.zip (Phone)
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk (Phone)
I guess the easiest way would to just go to recovery, wipe everything (after backup first of course).
Then adb sideload your ROM (in this example OOS 10.3.0) in recovery and let it install.
Reboot your phone and go thru first steps.
Go to fastboot and flash patched boot.img (magisk patched, look for the boot corresponding to your ROM) to gain root and reboot again.
Now you're all set.
No need for TWRP or anything. Just update the normal way and install magisk through magisk manager to inactive slot before you reboot after update.