Hey everyone,
I am in the process of rooting my axon7 (B10) and need some quick advice
I unlocked the bootloader using this method: https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595
Then went on to install twrp using the axon7toolkit. steps 1 and 2 reported to be working correctly but during the twrp install this came up. (see attached)
okay so recovery flashed successfully, but something went wrong with reboot? why, how, there is no indication that the tool wrote anything to boot.img so I should be fine? Can I just boot to recovery manually and continue normally? Or should I be worried that something went wrong?
the phone is currently still in fastboot mode and responding. however I am super cautious and don't want to brick the phone because I didn't ask so I am keeping it in this state for now.
any help is much appreciated
Checking ADB\Fastboot Connectivity...
ADB device connected!
Rebooting to bootloader...
Checking Fastboot Connectivity...
Fastboot device connected!
Flashing TWRP...
target reported max download size of 536870912 bytes
sending 'recovery' (14452 KB)...
OKAY [ 0.484s]
writing 'recovery'...
OKAY [ 0.113s]
finished. total time: 0.601s
Booting TWRP...
downloading 'boot.img'...
OKAY [ 0.475s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.497s
Tap 'Keep read-only'" on startup!
Checking ADB Recovery Connectivity...
Checking ADB Recovery Connectivity...
Click to expand...
Click to collapse
fleity said:
Hey everyone,
I am in the process of rooting my axon7 (B10) and need some quick advice
I unlocked the bootloader using this method: https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595
Then went on to install twrp using the axon7toolkit. steps 1 and 2 reported to be working correctly but during the twrp install this came up. (see attached)
okay so recovery flashed successfully, but something went wrong with reboot? why, how, there is no indication that the tool wrote anything to boot.img so I should be fine? Can I just boot to recovery manually and continue normally? Or should I be worried that something went wrong?
the phone is currently still in fastboot mode and responding. however I am super cautious and don't want to brick the phone because I didn't ask so I am keeping it in this state for now.
any help is much appreciated
Click to expand...
Click to collapse
Why do you even use axon7toolkit? Use "fastboot flash recovery recovery.img" and you'll be able to avoid using the toolkit. It's finicky as hell.
Otherwise at least use EDL Tool...
Your boot image is untouched. Seemingly axon7toolkit does "fastboot boot recovery.img" which basically sends the recovery to RAM or something and makes the phone boot into that file instead of the actual boot.img.
If you are on Fastboot select "Recovery" from it and hit power. It will enter the recovery directly. This is important because if the phone boots, it will reinstall the stock one.
After you get into TWRP, FLASH MAGISK. This will let you retain TWRP.
Choose an username... said:
Why do you even use axon7toolkit? Use "fastboot flash recovery recovery.img" and you'll be able to avoid using the toolkit. It's finicky as hell.
Otherwise at least use EDL Tool...
Your boot image is untouched. Seemingly axon7toolkit does "fastboot boot recovery.img" which basically sends the recovery to RAM or something and makes the phone boot into that file instead of the actual boot.img.
If you are on Fastboot select "Recovery" from it and hit power. It will enter the recovery directly. This is important because if the phone boots, it will reinstall the stock one.
After you get into TWRP, FLASH MAGISK. This will let you retain TWRP.
Click to expand...
Click to collapse
yeah I don't know why it seemed like a good idea, it's a sticky post in the rom section... It's how I started and then wanted to stick to it somehow.
indeed booting into recovery works like a charm which is already pretty reassuring.
flashed magisk, twrp is not up to date (3.1.1.0), but system boots. thanks a bunch
I guess I'll update / flash the most current version of twrp via fastboot and then go on to flash lineage
again, thank you very much
fleity said:
yeah I don't know why it seemed like a good idea, it's a sticky post in the rom section... It's how I started and then wanted to stick to it somehow.
indeed booting into recovery works like a charm which is already pretty reassuring.
flashed magisk, twrp is not up to date (3.1.1.0), but system boots. thanks a bunch
I guess I'll update / flash the most current version of twrp via fastboot and then go on to flash lineage
again, thank you very much
Click to expand...
Click to collapse
Is your twrp installed as "Keep Read Only" or did you select "Swipe to Allow Modifications"?
After giving flash in the Magisk you gave wipe?
Thanks if you can respond.
Enviado de meu ZTE A2017 usando o Tapatalk
EwertonR19 said:
Is your twrp installed as "Keep Read Only" or did you select "Swipe to Allow Modifications"?
After giving flash in the Magisk you gave wipe?
Thanks if you can respond.
Enviado de meu ZTE A2017 usando o Tapatalk
Click to expand...
Click to collapse
If you're asking because you want to know:
-swipe to allow modifications is okay
-If you want to get rid of encryption, you have to FORMAT data (not wipe). You'll lose the internal storage. After that, flash magisk.
You can just flash it without formatting , but your storage will be encrypted, and you'll lose the internal storage if you ever change ROMs.
I swiped to allow modifications
I backed up everything I needed from the phone. I actually planned for removing everything to get a fresh setup.
Choose an username... said:
If you're asking because you want to know:
-swipe to allow modifications is okay
-If you want to get rid of encryption, you have to FORMAT data (not wipe). You'll lose the internal storage. After that, flash magisk.
You can just flash it without formatting , but your storage will be encrypted, and you'll lose the internal storage if you ever change ROMs.
Click to expand...
Click to collapse
So after installing twrp I format the Data partition and give flash in Magisk, correct?
I am afraid to enter bootloop because I have already done several procedures and in all the same thing happened. I hope everything will work out this time.
EwertonR19 said:
So after installing twrp I format the Data partition and give flash in Magisk, correct?
I am afraid to enter bootloop because I have already done several procedures and in all the same thing happened. I hope everything will work out this time.
Click to expand...
Click to collapse
yes
Related
Exactly as the title says ... after flashing this update, even if unlocked, you can no longer flash a custom recovery.
Fastboot will show a successful flash, e.g. :
mfastboot.exe flash recovery twrp-2.8.6.0-ghost.img
sending 'recovery' (9488 KB)...
OKAY [ 0.849s]
writing 'recovery'...
OKAY [ 0.969s]
finished. total time: 1.819s
Click to expand...
Click to collapse
But when you try to boot recovery, it's stock recovery.
This makes any attempt to flash a rom, regain root, etc. impossible.
And you are booting straight to recovery after flashing via volume down and then volume up to select not the power button?
_litz said:
Exactly as the title says ... after flashing this update, even if unlocked, you can no longer flash a custom recovery.
Fastboot will show a successful flash, e.g. :
But when you try to boot recovery, it's stock recovery.
This makes any attempt to flash a rom, regain root, etc. impossible.
Click to expand...
Click to collapse
After you flash TWRP, at the command prompt type:
fastboot reboot-bootloader
I can't remember where I read it but some people said they had to do that to get the custom recovery to stick.
THEN unplug your device from your computer and reboot into recovery by scrolling down with the volume down button to highlight recovery and then hitting the volume up button to select recovery.
Ok, figured this out ...
(was able to back down to the original 4.4.4 w/rsd-lite and regain TWRP ... to develop this process)
So ... the following can be done to upgrade to this new version, and retain TWRP (plus you have the new recovery later on for 5.1 when it comes along ...)
First, the presumption here is you are unlocked. If you are not, none of this will work.
Also, you will need RSD-Lite installed and operational.
Download :
https://dl.dropboxusercontent.com/u...RIZON_4.4.4_KXA21.12-L1.26-3_cid2_1FF.xml.zip
https://dl.dropboxusercontent.com/u...4.4.4_KXA21.12-L1.26-3/twrp-2.8.6.0-ghost.img
https://dl.dropboxusercontent.com/u/22067374/GHOST_VERIZON_4.4.4_KXA21.12-L1.26-3/servicefile.xml
Unpack the GHOST zip file, and overwrite the "servicefile.xml" in the unpacked folder w/the one you downloaded, then copy the twrp .img in there.
Fire up RSD-Lite, put your phone in fastboot, and apply this update by loading the servicefile.xml as the update.
It will update everything, installing the TWRP instead of the new stock recovery.
Note: you can delete the twrp line in servicefile.xml if you wish to retain your existing custom recovery.
When done, you should reboot, update, and be up and running with the new 4.4.4 and TWRP ... so easy path back to root via TWRP.
_litz said:
Ok, figured this out ...
Click to expand...
Click to collapse
I think all that needs to happen is after you flash TWRP - you don't boot into recovery. Instead, reboot into bootloader mode. This has been a problem from the beginning for some people with their MX13's and not a new thing. I don't think it has anything to do with the update. Some people have to reboot into bootloader after flashing TWRP in order to get it to stick for some reason.
@_litz Please understand that @JulesJam is correct... the proper way to flash a recovery is as follows...
Start the phone to the Fastboot AP/Bootoader menu
using moto's fastboot (aka mfastboot) exectue the following...
mfastboot flash recovery RecoveryYouWishToFlash.img
mfastboot reboot-bootloader
Then use the volume/power keys to enter recovery.
Once in the recovery, it is safe to Reboot the phone normally.
that mfastboot reboot-bootloader step has been crucial for getting the newly flashed recovery (3rd party OR Stock!) to "stick" on the phone.
Flashing with RSDLite is over kill.
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
And you used volume up to enter recovery after flashing twrp? That is the most common problem I see.
_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
That is because you are pressing the power button when you should be pressing the volume up button.
Yep ... ain't my first rodeo ....
It flat out refused to take recovery.
I had to back it back down to the old 4.4.4 version, reflash TWRP, then I simply applied the whole RSD package (sans recovery) to re-upgrade it to the new 4.4.4.
Worked like a charm.
(Plus it gave me a chance to extract the fxz from the moto manager app)
Travisdroidx2 said:
And you used volume up to enter recovery after flashing twrp? That is the most common problem I see.
Click to expand...
Click to collapse
yes, that is what is happening.
See above ... this isn't my first time at this. Was not working as described.
_litz said:
See above ... this isn't my first time at this. Was not working as described.
Click to expand...
Click to collapse
Was not trying to insult your knowledge. That is a very common problem that many do. So I had to ask.
_litz said:
See above ... this isn't my first time at this. Was not working as described.
Click to expand...
Click to collapse
You needed to reboot into bootloader by typing fastboot reboot-bootloader after your flashed TWRP. THEN disconnect your phone from your computer and boot into recovery by using the volume down to highlight recovery and volume up to select recovery.
If you follow those instructions, you will flash TWRP fine. No need to go through that long drawn out process you came up with.
Probably should rename or delete this thread, since its fairly misleading.
Check in the /system partition for a file named recovery-from-boot.p or something similar. If that file is there it will reflash the stock recovery when you reboot, and I've seen it reflash when booting into recovery.
I just used the TWRP manager app from the Play store after reverting to stock recovery and installing the OTA. It worked perfectly the first time.
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
I'm curious as to what is different.. because the other day after flashing stock recovery back on my phone, taking the update to 212.166.3 KXA21.12-L1.26-3 which Verizon just pushed, I used those EXACT STEPS to put TWRP back on my phone and had no problems.
Beats me ... for me, it didn't work ...
So after I got things back onto the old 4.4.4 version, I put together the FXZ with the modified xml file, and simply re-updated, applying both the update, and TWRP, all in one go.
anyone else on old 4.4.4 can do the same thing if they wish, which was why I posted the links and the instructions.
not to bump this thread, but I had zero issues going from stock with 212.55.26 ota update installed and flashing twrp. it just worked like normal.
i would agree with @superkeest seems like this thread should get renamed.
Saw a post in the roms section (for different variant) of a flashable to turn back to stock.
I flashed/rooted a while ago, I did a factory reset and now it boots into TWRP.
Looking to get it back to stock.
Thanks!
Reboot into twrp that's installed on recovery. Flash
this to get download mode back. Use it and LG UP in upgrade mode to flash a kdz to restore literally everything to stock.
Phoenix591 said:
Reboot into twrp that's installed on recovery. Flash
this to get download mode back. Use it and LG UP in upgrade mode to flash a kdz to restore literally everything to stock.
Click to expand...
Click to collapse
Does aboot check laf version?
Alibaba0101 said:
Does aboot check laf version?
Click to expand...
Click to collapse
Yes, but that is laf for the H918 -- so you are good.
-- Brian
Every TWRP I try to flash says:
target reported max download size of 536870912 bytes
sending 'recovery' (22616 KB)...
OKAY [ 1.505s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.528s
It already has TWRP previously flashed in some way, but I cannot get into it. I see the logo flash up from time to time.
Tried Uppercut's LG UP and it will actually connect and give me the chance to flash a KDZ, but the phone will just do a quick restart and f*k everything.
OTA updates fail and say the software isn't verified. Also get the warning screen at bootup that the device has loaded a different operating system.
Any ideas? I just want it back to stock.
runningnak3d said:
Yes, but that is laf for the H918 -- so you are good.
-- Brian
Click to expand...
Click to collapse
How do I boot into TWRP? Feels like a silly question...
"adb reboot recovery" just boots to what looks like regular recovery. However, when I try to update or flash a .KDZ through LG UP, it will restart and flash up the twrp logo and say twrp 3.2.1-3. So I know the fcker is in there somewhere. I want it gone... all of it.
HALP!! Please.
Cookster128 said:
Every TWRP I try to flash says:
target reported max download size of 536870912 bytes
sending 'recovery' (22616 KB)...
OKAY [ 1.505s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.528s
It already has TWRP previously flashed in some way, but I cannot get into it. I see the logo flash up from time to time.
Tried Uppercut's LG UP and it will actually connect and give me the chance to flash a KDZ, but the phone will just do a quick restart and f*k everything.
OTA updates fail and say the software isn't verified. Also get the warning screen at bootup that the device has loaded a different operating system.
Any ideas? I just want it back to stock.
Click to expand...
Click to collapse
OTA updates and unmodified official stock files won't flash via TWRP.
Try flashing a copy of your stock recovery, then try installing the OTA update via stock recovery.
By the way, is that Charlotte NC? I ask because I live in Rockingham.
Sent from my LGL84VL using Tapatalk
Droidriven said:
OTA updates and unmodified official stock files won't flash via TWRP.
Try flashing a copy of your stock recovery, then try installing the OTA update via stock recovery.
By the way, is that Charlotte NC? I ask because I live in Rockingham.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Eh... Charlotte is about two hours from me. I'm at the bottom of the mountain, but I've been to Rockingham a few times. Dad graduated as a RCHS Cougar in '78.
Also, if you didn't already know, I'm the same fool from the noob thread. Glad you found me here. So, when I say it has download mode, I mean when I hit volume up and plug in, it flashes up and says it, then shows the twrp logo, then boots as normal. Calling 'adb reboot download mode' just reboots. You think the bootloader needs to be re-locked?
Cookster128 said:
Eh... Charlotte is about two hours from me. I'm at the bottom of the mountain, but I've been to Rockingham a few times. Dad graduated as a RCHS Cougar in '78.
Also, if you didn't already know, I'm the same fool from the noob thread. Glad you found me here. So, when I say it has download mode, I mean when I hit volume up and plug in, it flashes up and says it, then shows the twrp logo, then boots as normal. Calling 'adb reboot download mode' just reboots. You think the bootloader needs to be re-locked?
Click to expand...
Click to collapse
Yeah, I saw you in the noob thread, I came here looking for the issue you were having.
I'm not certain about the bootloader, I own LG devices, but none of them have fastboot or download mode so I don't have experience troubleshooting flashing issues on LG devices.
Have you tried removing root and any changes you've made to system via the file manager or terminal emulator that is built into TWRP then flashing a copy of stock recovery via TWRP then reboot recovery to allow stock recovery to boot then boot to fastboot and try locking the bootloader then try flashing firmware.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Yeah, I saw you in the noob thread, I came here looking for the issue you were having.
I'm not certain about the bootloader, I own LG devices, but none of them have fastboot or download mode so I don't have experience troubleshooting flashing issues on LG devices.
Have you tried removing root and any changes you've made to system via the file manager or terminal emulator that is built into TWRP then flashing a copy of stock recovery via TWRP then reboot recovery to allow stock recovery to boot then boot to fastboot and try locking the bootloader then try flashing firmware.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I may have got it! Maybe... don't pop the champagne yet. I couldn't get into TWRP at all. It would flash up then just boot regularly. Finally I tried to enter DL mode again but this time I kept holding down the volume up button and pressed every other button like I was entering a secret code on Mortal Kombat. It actually entered TWRP!
Luckily I had already put a laf.zip and H91820f.zip on the SD card. Flashed the ROM first... did nothing except put Magisk on it... don't want. Reboot, flashed laf.zip with my secret MK code, then I had access to the real DL mode! LG UP found it and flash the real ROM. Still working on it to make sure it's all good.
---------- Post added at 07:20 PM ---------- Previous post was at 06:38 PM ----------
Yep, it's good now. Even updated itself to H91820h with no verification snags.
I shall now sell it on eBay for one billion dollars! Muahahaha!
I fixed the problem by just booting into the LG Factory Reset menu, in order to get into TWRP. I hesitated to do that for a while because I had no way to verify TWRP was still on my device. After running out of options, I decided to just go for it. To my (and probably no one elses) surprise, it went straight into TWRP, where I was able to flash H91820s and Magisk 16.0 in the same TWRP session. Rebooted, everything was how it was except on a new version of Android. Root was retained.
Tried to update Magisk on my TMobile H918 from Magisk version 16.x using the app, and selected Direct Installation. The device is now stuck at the fastboot screen, and I cannot boot into recovery from adb.
Is there a way I can repair things? I am unsure exactly what got deleted/corrupted in the process of the update.
EDIT: When I try to boot into TWRP, I get this error:
fastboot: error: cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
and when I try to re-flash TWRP, I get this error:
fastboot flash recovery twrp.img
Sending 'recovery' (28928 KB) OKAY [ 0.764s]
Writing 'recovery' FAILED (remote: 'unknown command')
Finished. Total time: 0.827s
Click to expand...
Click to collapse
Can you get in Twrp with button combo? For me its while boot hold vol down and power then at lg logo release the power for a sec and re hold until the while screen and then select yes twice.
There is also download mode and reflashing twrp that way I believe...
Dont 100% me on that .
Mysticblaze347 said:
Can you get in Twrp with button combo? For me its while boot hold vol down and power then at lg logo release the power for a sec and re hold until the while screen and then select yes twice.
There is also download mode and reflashing twrp that way I believe...
Dont 100% me on that .
Click to expand...
Click to collapse
I tried to boot into recovery, but adb detected no recoveries on the system.
I don't want to do the System Format Yes Twice thing because I believe TWRP is gone. And I am unable to re-flash due to "no such command."
The recovery is unable to be written to the device.
124112 said:
I tried to boot into recovery, but adb detected no recoveries on the system.
I don't want to do the System Format Yes Twice thing because I believe TWRP is gone. And I am unable to re-flash due to "no such command."
The recovery is unable to be written to the device.
Click to expand...
Click to collapse
Is the phone in download mode ?
adb doesn't work in download mode
What does the command fastboot devices return?
Sent from my PH-1 using Tapatalk
Mysticblaze347 said:
Can you get in Twrp with button combo? For me its while boot hold vol down and power then at lg logo release the power for a sec and re hold until the while screen and then select yes twice.
There is also download mode and reflashing twrp that way I believe...
Dont 100% me on that .
Click to expand...
Click to collapse
clsA said:
Is the phone in download mode ?
adb doesn't work in download mode
What does the command fastboot devices return?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I fixed the problem by just booting into the LG Factory Reset menu, in order to get into TWRP. I hesitated to do that for a while because I had no way to verify TWRP was still on my device. After running out of options, I decided to just go for it. To my (and probably no one elses) surprise, it went straight into TWRP, where I was able to flash H91820s and Magisk 16.0 in the same TWRP session. Rebooted, everything was how it was except on a new version of Android. Root was retained.
124112 said:
I fixed the problem by just booting into the LG Factory Reset menu, in order to get into TWRP. I hesitated to do that for a while because I had no way to verify TWRP was still on my device. After running out of options, I decided to just go for it. To my (and probably no one elses) surprise, it went straight into TWRP, where I was able to flash H91820s and Magisk 16.0 in the same TWRP session. Rebooted, everything was how it was except on a new version of Android. Root was retained.
Click to expand...
Click to collapse
Glad it worked...happy new year
I stupidly tried using franco's app to flash cleanKernel on my rooted phone on 9.0.11, it failed of course and now can't boot my phone. I'm able to fastboot boot twrp.img but I'm not sure what is needed next. I've downloaded the full 9.0.11 ota file thinking something in it (or all of it) needs to be flashed from twrp. Afraid to do anything at this point for fear of losing data. Any tips are appreciated.
I've downloaded mauronofrio's rom-stock-fastboot utility but see he says it will clear data. I'm assuming all the .bat files will do this. Any way to avoid clearing internal storage?
soundneedle said:
From bootloader screen, using fastboot boot twrp.zip results in OP going to "Fastboot Mode" screen...and staying there. The zip is pushed to the phone but won't boot into TWRP. This started after I stupidly tried using franco's app to flash cleanKernel on my rooted phone. It failed of course and now can't boot my phone. My phone recently updated itself to 9.0.11, fyi.
Any ideas on how to fix this boot issue? Is it just a matter of flashing something from the full ota 9.0.11 file---some img file or something?
Click to expand...
Click to collapse
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
I was able to recover...thank god. Just used mauronofrio's flash utility. Removed the "-w" flag from the flash-all.bat file and all is good.
Stuck on Fastboot Mode screen once I run fastboot boot twrp.img
bp328i said:
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
Click to expand...
Click to collapse
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Is the twrp.img even being flashed
SimmoMaz said:
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Click to expand...
Click to collapse
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
SimmoMaz said:
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
Click to expand...
Click to collapse
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
TWRP isn't there
lilbrat said:
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
Click to expand...
Click to collapse
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
SimmoMaz said:
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
Click to expand...
Click to collapse
Ok.. are you using the latest TWRP? If you want in the guide section you can you the msmdow like ad tools to reset you phone to stock, and retry again..
THIS. I have the exact same issue. In short, I have the T-mobile version, and was able to unlock successfully. I am using twrp-3.2.3-0, and I have the img and zip in the same folder, same way Techibee does on Youtube. I then type "fastboot boot twrp-3.2.3-0-fajita.img", I get the "OKAY... OKAY... Booting... Finished" response in console. Then, the Fastboot screen appears and never leaves. I have done this 3 times now. I kept tweaking the process, but I'm nervous to keep debugging.
Stuck (
Hello guys,
I wanted to overclock my 6t global. so i had unlocked the bootloader then flashed the twrp. In twrp i firstly reset the os to factory setting and then i flash magisk and smurf kernel. but when i reboot after this my phone is stuck on the phone unlocked message.
ive tried flashing magisk only and then boot, it works. but when i flash smurf kernel i get stuck . why this happening plz help (
Hi xda Community,
I updated to the android 10 a week ago or so. Today i tried to downgrade to 9.0.1.7 cause the beta is way to buggy for me.
My problem is, that I can't use fastboot anymore like it was before. For example, I cannot boot via 'fastboot boot' method into recovery.
Every time I try to boot something I get FAILED (remote: unknown command)
C:\adb>fastboot boot twrp-3.3.1-1-fajita.img
downloading 'boot.img'...
OKAY [ 0.665s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.681s
Does somebody have a fix for this? Due the lack of TWRP, I cannot downgrade or don't now how to downgrade nor to install magisk.
Thanks in advance and have a great new week y'all
Correct me if I'm wrong, but this command will no longer work with Android Q due to Google new partition scheme.
You can check this thread out: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 - it contains fastboot roms of Android P, which you may flash, according to tutorial.
You may also try a local update method with the rollback package (https://www.getdroidtips.com/rollback-android-10-q-pie-oneplus-6-6t/).
Note that this will, unfortunately, wipe your data.
fastboot flash boot twrp.img should do the trick.
Cats_PJs said:
fastboot flash boot twrp.img should do the trick.
Click to expand...
Click to collapse
That will flash the recovery image but it won't be decrypted at all. I tried that and had to wipe my phon.
fogame said:
That will flash the recovery image but it won't be decrypted at all. I tried that and had to wipe my phon.
Click to expand...
Click to collapse
Was just responding to op on the correct command to flash twrp in Android 10.
https://forum.xda-developers.com/showpost.php?p=80639099&postcount=2856
That is the method I followed to upgrade, worked perfectly, it did wipe data. Decryption does work.
Cats_PJs said:
Was just responding to op on the correct command to flash twrp in Android 10.
https://forum.xda-developers.com/showpost.php?p=80639099&postcount=2856
That is the method I followed to upgrade, worked perfectly, it did wipe data. Decryption does work.
Click to expand...
Click to collapse
Lol after spending all day I decided to go back to pie. Now to get play store certified again without locking the bootloader.
Magic Stick said:
Correct me if I'm wrong, but this command will no longer work with Android Q due to Google new partition scheme.
You can check this thread out: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 - it contains fastboot roms of Android P, which you may flash, according to tutorial.
You may also try a local update method with the rollback package (https://www.getdroidtips.com/rollback-android-10-q-pie-oneplus-6-6t/).
Note that this will, unfortunately, wipe data.
Click to expand...
Click to collapse
- Is their a way after this to get magisk working without fastboot boot twrp.img?
Cats_PJs said:
fastboot flash boot twrp.img should do the trick.
Click to expand...
Click to collapse
- Is their a way to only boot up twrp instead of install twrp?
Cats_PJs said:
Was just responding to op on the correct command to flash twrp in Android 10.
https://forum.xda-developers.com/showpost.php?p=80639099&postcount=2856
That is the method I followed to upgrade, worked perfectly, it did wipe data. Decryption does work.
Click to expand...
Click to collapse
Do I get updates for android 10 with this version when it releases?
Thanks in advance y'all
deaddevil2299 said:
- Is their a way after this to get magisk working without fastboot boot twrp.img?
Click to expand...
Click to collapse
Sure, you flash a patched boot img, with fastboot. Look into the Guides and News section you'll find what is needed. Either in 9.0.17 thread ( not renamed yet) or in How to keep twrp and Magisk thread
I don't see the point of having twrp for now, especially with the trick necessary to have decryption working.
It has been said millions time that updates work perfectly with or without twrp, with or without Magisk
Striatum_bdr said:
Sure, you flash a patched boot img, with fastboot. Look into the Guides and News section you'll find what is needed. Either in 9.0.17 thread ( not renamed yet) or in How to keep twrp and Magisk thread
I don't see the point of having twrp for now, especially with the trick necessary to have decryption working.
It has been said millions time that updates work perfectly with or without twrp, with or without Magisk
Click to expand...
Click to collapse
I'm just wondering why their isn't any fastboot version mentioned in my fastboot mode. Looks a bit broken.
I think I wait till their is a stable way to root.
Thanks for the answers