I have eagerly been waiting for the release of a TWRP image or MSM tool for this device, to no avail
I have seen on one of these posts, found here, a potentially working TWRP image.
Currently it is just the twrp.img without any zip
Directly download it here
As said below, this should be flashable within magisk to install
- I have NOT tested this personally
- I am not advising anybody try this image either
- Password decryption appears to not be functional
- This appears to only function on Android 13
sm8450 A13 Kernel Source Compile Issues
2023/02/16 UPDATE!!!! https://github.com/OnePlusOSS/android_kernel_msm-5.10_oneplus_sm8450/issues/4 if u want test it ---> https://github.com/negroni-development/oneplus-sm8450_t_13.0_10pro referenced by X5Pro based severecold's work.(compiles...
forum.xda-developers.com
It should be able to flash into magisk, but there is no guarantee that flashing into rom can enter the system
PlasmaTornado said:
I have eagerly been waiting for the release of a TWRP image or MSM tool for this device, to no avail
I have seen on one of these posts, found here, a potentially working TWRP image.
Currently it is just the twrp.img without any zip
- I have NOT tested this personally
- I am not advising anybody try this image either
- Password decryption appears to not be functional
- This appears to only function on Android 13
sm8450 A13 Kernel Source Compile Issues
2023/02/16 UPDATE!!!! https://github.com/OnePlusOSS/android_kernel_msm-5.10_oneplus_sm8450/issues/4 if u want test it ---> https://github.com/negroni-development/oneplus-sm8450_t_13.0_10pro referenced by X5Pro based severecold's work.(compiles...
forum.xda-developers.com
Click to expand...
Click to collapse
we need testers
TrajanoX3 said:
we need testers
Click to expand...
Click to collapse
Agreed. I'm sure there are some people willing to give it a shot.
I haven't flashed an image since split partitions has existed, which is a fairly long time now
Even with the OP10, I am still unrooted. TWRP provides just that extra bit of security to me
I tested the twrp. I flashed to A then flashed to B . Put phone to fastboot flashed using the fastboot commands
( fastboot flash recovery_a ) then flashed B using commands ( fastboot flash recovery_b ) . From fastboot went to recovery . Booted up twrp recovery . Change language to English ( second from bottom right ) . Completed backup , reboot phone ok . Then went back into fastboot and reboot to twrp recovery. So its seems to be working ok so far.
Canuck Knarf said:
I tested the twrp. I flashed to A then flashed to B . Put phone to fastboot flashed using the fastboot commands
( fastboot flash recovery_a ) then flashed B using commands ( fastboot flash recovery_b ) . From fastboot went to recovery . Booted up twrp recovery . Change language to English ( second from bottom right ) . Completed backup , reboot phone ok . Then went back into fastboot and reboot to twrp recovery. So its seems to be working ok so far.
Click to expand...
Click to collapse
Fantastic! Can you confirm that it can decrypt without any issues?
Its working good
Canuck Knarf said:
I tested the twrp. I flashed to A then flashed to B . Put phone to fastboot flashed using the fastboot commands
( fastboot flash recovery_a ) then flashed B using commands ( fastboot flash recovery_b ) . From fastboot went to recovery . Booted up twrp recovery . Change language to English ( second from bottom right ) . Completed backup , reboot phone ok . Then went back into fastboot and reboot to twrp recovery. So its seems to be working ok so far.
Click to expand...
Click to collapse
we donate screenshot
heres recovery log from TWRP
Canuck Knarf said:
heres recovery log from TWRP
Click to expand...
Click to collapse
Are you using twrp right now?
TrajanoX3 said:
Are you using twrp right now?
Click to expand...
Click to collapse
Yes
Canuck Knarf said:
Yes
Click to expand...
Click to collapse
Can you send us a screenshot of twrp?
Canuck Knarf said:
Sim
Click to expand...
Click to collapse
Thanks for the screenshots, did you flash magisk through twrp?
Canuck Knarf said:
Yes
Click to expand...
Click to collapse
Magisk installation working probably by twrp?
just installed Magisk
TrajanoX3 said:
we donate screenshot
Click to expand...
Click to collapse
then install and flash partition A and then partition B and relapse to recovery?
Yes
fastboot flash recovery_a then fastboot flash recovery_b then reboot to recovery from fastboot . then change language ...cause its in Chinese
Oh and Twrp works with screen password lock so no need to disable it
Canuck Knarf said:
Oh and Twrp works with screen password lock so no need to disable it
Click to expand...
Click to collapse
how do you operate
Beware, this twrp.img is not bootable. Command fastboot boot twrp.img won't work, you will get bootloop into OP logo. Rebooting into fastboot mode and doing fastboot boot stockboot.img will help.
So it means you can only flash it directly. Confirmed by me and three others.
Related
TWRP Recovery v.3.0 for BLU_VIVO_XL (gionee6753_65u_l1)
based on firmware version BLU_V0030UU_V07_GENERIC_5.1_20160126-1033 / Tue Jan 26 10:33:33 CST 2016 / Android 5.1
How do we go about to install this
jemmini said:
TWRP Recovery v.3.0 for BLU_VIVO_XL (gionee6753_65u_l1)
based on firmware version BLU_V0030UU_V07_GENERIC_5.1_20160126-1033 / Tue Jan 26 10:33:33 CST 2016 / Android 5.1
Click to expand...
Click to collapse
Is this confirmed to work? I tried flashing the TWRP for the Blu Pure XL and the phone boot looped. I was able to unlock the bootloader ADB but after flashing TWRP the phone bootlooped.
ItGuyJax8430 said:
Is this confirmed to work? I tried flashing the TWRP for the Blu Pure XL and the phone boot looped. I was able to unlock the bootloader ADB but after flashing TWRP the phone bootlooped.
Click to expand...
Click to collapse
flash the original recovery (from fastboot mode).
loading recovery and system loading - are two different things...
p.s. recovery was tested.
jemmini said:
flash the original recovery (from fastboot mode).
loading recovery and system loading - are two different things...
p.s. recovery was tested.
Click to expand...
Click to collapse
10-4 ill give the recovery a go. I knew there was a difference, I was just giving extra info on my situation. I just got my replacement phone in today, ill give the recovery a go.
ItGuyJax8430 said:
10-4 ill give the recovery a go. I knew there was a difference, I was just giving extra info on my situation. I just got my replacement phone in today, ill give the recovery a go.
Click to expand...
Click to collapse
give me the boot.img and recovery.img files from your firmware. and the file /proc/emmc from the system
and I'll make TWRP for you...
It works. Thank you jemmini!
Edit: It appears I spoke too soon. Recovery works, but now the phone is in a constant boot loop.
2nd update: By some miracle, I got the phone to stop looping and just stay on recovery by randomly pressing buttons.
During the loop, I get this message.
after unlocking the bootloader you need for the first time to boot the system with the original recovery. and only after that to flash the TWRP...
jemmini, do you have a backup of the stock rom? If so, can you upload it? Thank you.
jemmini said:
after unlocking the bootloader you need for the first time to boot the system with the original recovery. and only after that to flash the TWRP...
Click to expand...
Click to collapse
Can you provide step by step instructions?
I imagine it would be something like this.
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit?
---------- Post added at 07:50 AM ---------- Previous post was at 07:46 AM ----------
xdadev_user11 said:
jemmini, do you have a backup of the stock rom? If so, can you upload it? Thank you.
Click to expand...
Click to collapse
If you have no other option, you can try this.. http:// firmwarefile.com/gionee-s-plus
emowing said:
Can you provide step by step instructions?
Click to expand...
Click to collapse
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
4.1. fastboot oem unlock confirm
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit.
jemmini said:
give me the boot.img and recovery.img files from your firmware. and the file /proc/emmc from the system
and I'll make TWRP for you...
Click to expand...
Click to collapse
I'm planning on trying out TWRP later today. Before I do that, what files should I grab (as a backup) and from where should I grab them? I'm happy to upload them for others, too.
So I will be able to root the phone with this? After unlocking bootloader and flashing twrp I flash supersu?
jemmini said:
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
4.1. fastboot oem unlock confirm
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit.
Click to expand...
Click to collapse
@jemmini I've never heard of the command fastboot oem unlock confirm before. Is this a command to run or do you mean we should do a fastboot getvar all and check the bootloader unlock status for a yes? Sorry for the newbie question. I've never needed to do this with a nexus.
emowing said:
@jemmini I've never heard of the command fastboot oem unlock confirm before. Is this a command to run or do you mean we should do a fastboot getvar all and check the bootloader unlock status for a yes? Sorry for the newbie question. I've never needed to do this with a nexus.
Click to expand...
Click to collapse
The confirmation he means is after you execute the unlock command, on the phone screen asks you to confirm by press volume up. That all.
[del]
xdadev_user11 said:
It works. Thank you jemmini!
Edit: It appears I spoke too soon. Recovery works, but now the phone is in a constant boot loop.
2nd update: By some miracle, I got the phone to stop looping and just stay on recovery by randomly pressing buttons.
Click to expand...
Click to collapse
The same thing happened to me.
After I was able to get into recovery using your steps, I formated ONLY the /data partition and rebooted. The phone then booted up properly after that.
I then downloaded the SuperSU ZIP file and rooted my phone through recovery .
I hope this helps someone.
acotto said:
The same thing happened to me.
After I was able to get into recovery using your steps, I formated ONLY the /data partition and rebooted. The phone then booted up properly after that.
I then downloaded the SuperSU ZIP file and rooted my phone through recovery .
I hope this helps someone.
Click to expand...
Click to collapse
Nice find :good:. I'll try it when I get my phone.. it will be delivered today.
emowing said:
If you have no other option, you can try this.. http:// firmwarefile.com/gionee-s-plus
Click to expand...
Click to collapse
So I unlocked bootloader and also got the bootloop. I flashed this firmware to fix it, but I found out the radio included is not the same as the US version, so now the sim cards don't work.
The firmware image have a file called "MT6753_Android_scatter.txt" which determine what partition to flash. Base on this guide http://www.mtkroms.com/2015/03/how-to-restore-lost-imei-on-any.html, the "secro" partition being replaced may be what caused the issue, so looked like that's what I have unchecked before flashing.
jemmini said:
..
Click to expand...
Click to collapse
I just discovered that you can back the secro and many other partition within TWRP. I don't know if that alone will fix the sim problem. WRONG
Not used to giving guides
TWRP Backup - https://forum.xda-developers.com/oneplus-6t/how-to/dp3-twrp-backup-t-mobile-magisk-t3952304
But you need to download the the QB3 update zip and upack the payload.bin with a payload dumper
Make sure your device is on international and unlocked of course
Boot into Twrp recovery and copy the system.img and vendor.img onto device
Flash both images in respective partitions and on both A and B slot
Wipe data after flashing and reboot into bootloader
From directory of the rest of IMG you've extracted you'll want use fastboot and flash:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Then reboot and done
Don't delete files just yet
Haven't tried but certain you can root this way:
After you've setup your device you can download magisk manager. Select the boot.img on you pc, in your dump folder, and copy it to your device again. In the magisk manager patch the boot image you copied, and copy that onto your PC
Now boot into bootloader and use command
fastboot flash boot magisk_patched.img
Or if that doesn't work try
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
And if device doesn't boot for any reason just flash back the stock boot.img
Enjoy
-About TWRP- (from my knowledge)
DON'T FLASH TWRP
I think recovery is running in boot.img now I'm not sure
But it seems we may need to patch the bootloader to have the recovery in there
Ive unpack both boot IMG from dp3 and Twrp IDK if they're made different but they look different unfortunately I don't understand enough to patch but hopefully that helps idk
So I wouldn't try flashing or booting into recovery it'll just freeze and flashing will mess up the whole device and you'll have to use msmtool again and redo process
ayjays said:
-About TWRP- (from my knowledge)
DON'T FLASH TWRP
I think recovery is running in boot.img now I'm not sure
But it seems we may need to patch the bootloader to have the recovery in there
Ive unpack both boot IMG from dp3 and Twrp IDK if they're made different but they look different unfortunately I don't understand enough to patch but hopefully that helps idk
So I wouldn't try flashing or booting into recovery it'll just freeze and flashing will mess up the whole device and you'll have to use msmtool again and redo process
Click to expand...
Click to collapse
It's not about patching.
Flash stock boot.img to both slots as I'm guessing you aren't sure which one your on.
I'll give u a twrp that works for qb3 also proper instructions.
T-Mobile version downside is we can't flash ota and we can't boot qb3 wth fastboot twrp so flashing the twrp.img now replaces kernel in boot.img.
Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
And I'm aware of checking the active slot with a command but I have trouble switching to the opposite after rebooting because of set_active command maybe I'm doing something wrong
ayjays said:
Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
Click to expand...
Click to collapse
Our recovery is built in boot.img.
Uploading now
---------- Post added at 10:10 PM ---------- Previous post was at 09:42 PM ----------
Boot to fastboot
fastboot getvar all
See which slot is active.
If it's slot a then this
fastboot flash boot_a qb3-twrp.img
If it's slot b then this
fastboot flash boot_b qb3-twrp.img
Once flashed choose boot recovery and once it boots u can flash stock boot.img back then flash magisk 19.4 while in twrp.
U must use USB drive decryption isn't working yet. Or adb sideload.
I've only tested this on T-Mobile version running qb3.
All credits to @mauronofrio I used his source with some modifications
https://www.androidfilehost.com/?fid=6006931924117924335
ayjays said:
Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
And I'm aware of checking the active slot with a command but switching to it after rebooting because I of set_active command maybe I'm doing something wrong
Click to expand...
Click to collapse
Did you try what I posted
twinnfamous said:
It's not about patching.
Flash stock boot.img to both slots as I'm guessing you aren't sure which one your on.
I'll give u a twrp that works for qb3 also proper instructions.
T-Mobile version downside is we can't flash ota and we can't boot qb3 wth fastboot twrp so flashing the twrp.img now replaces kernel in boot.img.
Click to expand...
Click to collapse
twinnfamous said:
Did you try what I posted
Click to expand...
Click to collapse
Not yet, but if you flash the stock boot image after then would there be any point in flashing the patch boot before hand? And, what I was looking for is a more permanent solution. So, that it'll boot and you can go to Twrp whenever without having to use a PC.
If that's the case and it works then nevermind but I remember and if I'm mistaken that, even if you flash the Twrp installer it'll still boot loop after the installation.
If that's still a problem maybe someone more skilled than I, or even you, can patch the stock bootimg themselves. And, eveb get it working for the future time on Q
Maybe unpacking and looking inside the boot.img and Twrp.img, the repacking with the proper adjustments
ayjays said:
Not yet but if you flash the stock boot image after then would there any point in flashing the patch boot before hand. And, what I was looking for is a more permanent solution. So, that it'll boot and you can go to Twrp whenever without having to use a PC.
If that's the case and it works then nevermind but I remember and if I'm mistaken that, even if you flash the Twrp installer it'll still boot loop after the installation.
If that's still a problem maybe someone more skilled than I, or even you, can patch the stock bootimg themselves. And, eveb get it working for the future time on Q
Maybe unpacking and looking inside the boot.img and Twrp.img, the repacking with the proper adjustments
Click to expand...
Click to collapse
I'm aware of the permanent solution your looking for. This is the first step. With magisk installed u can simply use the installer in my android file host by selecting modules push the + sign and find the installer then without rebooting install magisk direct install. Then u can boot to recovery with advanced reboot menu. U can also just do everything in twrp. After u flash twrp.img .
ayjays said:
Not used to giving guides
But you need to download the the QB3 update zip and upack the payload.bin with a payload dumper
Make sure your device is on international and unlocked of course
Boot into Twrp recovery and copy the system.img and vendor.img onto device
Flash both images in respective partitions and on both A and B slot
Wipe data after flashing and reboot into bootloader
From directory of the rest of IMG you've extracted you'll want use fastboot and flash:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Then reboot and done
Don't delete files just yet
Haven't tried but certain you can root this way:
After you've setup your device you can download magisk manager. Select the boot.img on you pc, in your dump folder, and copy it to your device again. In the magisk manager patch the boot image you copied, and copy that onto your PC
Now boot into bootloader and use command
fastboot flash boot magisk_patched.img
Or if that doesn't work try
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
And if device doesn't boot for any reason just flash back the stock boot.img
Enjoy
Click to expand...
Click to collapse
Just like my guide last month on OnePlus forums as I am jacksummers, even if u do this we still have no calling ability whatsoever. SMS is barely working and it still blows for us. I have been trying everything to get the whole thing to not only flash and install but be able to boot with no hardware mismatch... It won't work unless we can resign the firmware with OnePlus signing keys after changing everything to say "single" still. Since we cannot change the phone. There is still something in the phone that comes back as op6tsingle
fullofhell said:
Just like my guide last month on OnePlus forums as I am jacksummers, even if u do this we still have no calling ability whatsoever. SMS is barely working and it still blows for us. I have been trying everything to get the whole thing to not only flash and install but be able to boot with no hardware mismatch... It won't work unless we can resign the firmware with OnePlus signing keys after changing everything to say "single" still. Since we cannot change the phone. There is still something in the phone that comes back as op6tsingle
Click to expand...
Click to collapse
My phone is off rn but I receive calls and texts and I've been receiving calls on my T-Mobile OnePlus 6t since I flashed it... Make sure you're on international version
the only problems i ran in myself so far are app optimzations and when i'd recieved calls and answer my voice would sound weird to them but id hear them perfectly (not my problem lol jk jk)
ayjays said:
My phone is off rn but I receive calls and texts and I've been receiving calls on my T-Mobile OnePlus 6t since I flashed it... Make sure you're on international version
the only problems i ran in myself so far are app optimzations and when i'd recieved calls and answer my voice would sound weird to them but id hear them perfectly (not my problem lol jk jk)
Click to expand...
Click to collapse
Yeah u need to flash every other partition in the bin dump. If it tells u u cannot bc it's a critical partition then ya can't. Once u do so u will have full function and on calls. It's basically everything in the payload.bin but abl,xbl, hyp, and a few others that tell ya they're critical partitions. Once u do that everything works Perfectly.. my main issue was the call issue u described..but do as I suggest and all will work
fullofhell said:
Yeah u need to flash every other partition in the bin dump. If it tells u u cannot bc it's a critical partition then ya can't. Once u do so u will have full function and on calls. It's basically everything in the payload.bin but abl,xbl, hyp, and a few others that tell ya they're critical partitions. Once u do that everything works Perfectly.. my main issue was the call issue u described..but do as I suggest and all will work
Click to expand...
Click to collapse
That's why I said to flash system and vendor in Twrp wipe data then flash the other ones I stated above in fastboot mode everything should be flashed without a problem just follow my guide it's not hard
I'm uploading twrp backup soon with root
DO AT YOUR OWN RISK I WONT BE RESPONSIBLE FOR ANYTHING!!!!!!
EVERYTHING SO FAR WORKS WITH JUST A LIL LAG HERE AND THERE
Tmo oneplus 6t fastboot flash one click Android Q DP3. i test it with and without wiping data. i just put all the files together. just run the flash bat. You need to be on latest beta. i tested myself twice.
root= Download patch q boot.img.
fastboot flash boot img after first boot. then just download canary magisk manager. a quick google search will bring it up
have fun and remember anything goes south you can msm tool back to stock!
flash all: https://drive.google.com/open?id=1D_-B5z-rHGDr6RHjDQA0hz-janrsypdv
patch boot img: https://drive.google.com/open?id=1nbiapy6HZH4VNK4JuEF9KxSIlsBRKgsX
omariscal1019 said:
DO AT YOUR OWN RISK I WONT BE RESPONSIBLE FOR ANYTHING!!!!!!
EVERYTHING SO FAR WORKS WITH JUST A LIL LAG HERE AND THERE
Tmo oneplus 6t fastboot flash one click Android Q DP3. i test it with and without wiping data. i just put all the files together. just run the flash bat. You need to be on latest beta. i tested myself twice.
root= Download patch q boot.img.
fastboot flash boot img after first boot. then just download canary magisk manager. a quick google search will bring it up
have fun and remember anything goes south you can msm tool back to stock!
flash all: https://drive.google.com/open?id=1D_-B5z-rHGDr6RHjDQA0hz-janrsypdv
patch boot img: https://drive.google.com/open?id=1nbiapy6HZH4VNK4JuEF9KxSIlsBRKgsX
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6t/development/dp3-twrp-backup-t-mobile-magisk-t3952304 TWRP backup good job on the not wiping data though
ayjays said:
That's why I said to flash system and vendor in Twrp wipe data then flash the other ones I stated above in fastboot mode everything should be flashed without a problem just follow my guide it's not hard
Click to expand...
Click to collapse
Hi, yes we are saying the same thing.. also note, for me, Calls last for a day, then broken again. Cannot use daily if u need to make phone calls. Testing with TMobile modem.img to see if resolved.
fullofhell said:
Hi, yes we are saying the same thing.. also note, for me, Calls last for a day, then broken again. Cannot use daily if u need to make phone calls. Testing with TMobile modem.img to see if resolved.
Click to expand...
Click to collapse
i made a one click fastboot let me what happens so.ican remove it and add t mo modem
omariscal1019 said:
i made a one click fastboot let me what happens so.ican remove it and add t mo modem
Click to expand...
Click to collapse
Will do buddy. Setting mine up as we speak.. I am down to just my fajita right now, bricked my pixel 3 again as I'm working on an exploit to unlock my locked down version ....
Can you relock bootloader after this? Don't want twrp or root
supaet said:
Can you relock bootloader after this? Don't want twrp or root
Click to expand...
Click to collapse
Not sure try "fastboot oem lock" in the bootloader after
OZIP's FOR RMX2001«Android 10»ㅤㅤ ㅤㅤㅤㅤ ㅤㅤㅤㅤㅤㅤㅤ Click Here
«Android 11»*Team Drive Gone Will Find And Update
Need Help?
Contact Me On Telegram
-GROUP LINK-
Awesome!! Can I dirty flash ui2?
Android 11 update (C12 Global) failed, why?
Not flashing ui 2
Ferbir88 said:
Android 11 update (C12 Global) failed, why?
Click to expand...
Click to collapse
it cant be flashed directly u should flash ozip using custom recovery but after flash , flash patched vbmeta too otherwise u got brick for more info ask in ofiicial realme 6 main telegram group
xdriv3r said:
Not flashing ui 2
Click to expand...
Click to collapse
u cant flash it by stock recovery read other comment reply
unique_sandesh said:
it cant be flashed directly u should flash ozip using custom recovery but after flash , flash patched vbmeta too otherwise u got brick for more info ask in ofiicial realme 6 main telegram group
Click to expand...
Click to collapse
I tried not working (bootloop). I lfashed patched vbmeta. I installed it with custom recovery
Ferbir88 said:
I tried not working (bootloop). I lfashed patched vbmeta. I installed it with custom recovery
Click to expand...
Click to collapse
tell meyour all process sir , and they also need format
unique_sandesh said:
unique_sandesh said:
tell meyour all process sir , and they also need format
First, I flashed stock b.53 firmware with SP flashtool and I update with stock recovery to b.65. For the second time I need root the firmware and patch vbmeta, because missing the custom recovery without this step.( orange fox recovery)For the third Time I flash the c.12 firmware with custom recovery, and reboot to bootloader from recovery than I patch c.12 vbmeta. For the last Time I reboot and the end result bootloop.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
unique_sandesh said:
tell meyour all process sir , and they also need format
Click to expand...
Click to collapse
First, I flashed stock b.53 firmware with SP flashtool and I update with stock recovery to b.65. For the second time I need root the firmware and patch vbmeta, because missing the custom recovery without this step.( orange fox recovery)For the third Time I flash the c.12 firmware with custom recovery, and reboot to bootloader from recovery than I patch c.12 vbmeta. For the last Time I reboot and the end result bootloop
ofc it will not boot untill u format data , u need to format data . give these cmd fastboot -w , fastboot erase userdata
unique_sandesh said:
ofc it will not boot untill u format data , u need to format data . give these cmd fastboot -w , fastboot erase userdata
Click to expand...
Click to collapse
Thank you very much now It works, but I want to ask you: Why can not i enter in recovery Mode? I tried the power on and volume down combination, but the phone enter only fastboot mode with "oplus verification failed" message. If I do a factory reset under the Android, the phone load the recovery, until resetting.
Ferbir88 said:
Thank you very much now It works, but I want to ask you: Why can not i enter in recovery Mode? I tried the power on and volume down combination, but the phone enter only fastboot mode with "oplus verification failed" message. If I do a factory reset under the Android, the phone load the recovery, until resetting.
Click to expand...
Click to collapse
from rmui 2.o we only get in fastboot mode. for recovery give this cmd fastboot reboot recovery, , and ignore that oppo verify failed msg
unique_sandesh said:
from rmui 2.o we only get in fastboot mode. for recovery give this cmd fastboot reboot recovery, , and ignore that oppo verify failed msg
Click to expand...
Click to collapse
Thank you very much!
Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply
Jegwaar said:
Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply
Click to expand...
Click to collapse
were the same situation and i dont know what to do. Please help us.
which is the process 4 install? im on rui 1.0
Kodize said:
which is the process 4 install? im on rui 1.0
Click to expand...
Click to collapse
using custom recovery
Rollback With Custom Recovery
This Method Only For Realme 6/6i(indian)/6s _____________________ RMUI2.0 TO RMUI 1.0____________________________________________ This Method For Downgrading From F2Fs Based Custom Roms ⓿ Flash Latest TWRP (Gofaraway One) ❶ Go to manage partitions And Select...
telegra.ph
Jegwaar said:
Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply
Click to expand...
Click to collapse
keep unlockd your bl and use spft for flashing rui 2 make sure you selected download only in spft while flashing here is the latest decrypted firmware link https://t.me/rmx2001_clouds/7
unique_sandesh said:
keep unlockd your bl and use spft for flashing rui 2 make sure you selected download only in spft while flashing here is the latest decrypted firmware link https://t.me/rmx2001_clouds/7
Click to expand...
Click to collapse
Hi guys, did someone do this ? i'm in the same situation after rolling back to B55 using stock recovery, now stuck on B65, no update coming.
Bootloader is unlocked, when i flash a C18 firmware with SPF phone bootloop in fastboot mode.
Only flashing a B65 firmware with SPF to get phone boot corretly.
I just need to known if this method is tested with the given C19 firmware ?
Many thx.
Need some help just got the new oneplus 10 pro. I unlocked bootloader and tried to flash twrp to it . Now the phone only has fastboot, no recovery nothing, Just keeps rebooting to fastboot. I plug it into charger and turns on and goes rate to fastboot. If i relock bootloader i get this. I will show pic
It is the China NE2210
storage is 12 g - 256g
Probably going to need to flash stock boot.img to boot again. Haven't seen any downloads for stock rom so not sure where you could find it tho.
Which version your device?
I have 7pro, 8t ans 9pro(GLOBAL). I am waiting for release of 10pro in US. I wish i could help. I've just been watching these threads to watch for development
Canuck Knarf said:
Need some help just got the new oneplus 10 pro. I unlocked bootloader and tried to flash twrp to it . Now the phone only has fastboot, no recovery nothing, Just keeps rebooting to fastboot. I plug it into charger and turns on and goes rate to fastboot. If i relock bootloader i get this. I will show pic
Click to expand...
Click to collapse
I have this problem 3 day ago.
What the Color Os ? You neet flash original boot and recovery, if not chenched you must try switch active slot A or B.
Where you find twrp for 10pro, he is not here yet A/B chenge
Thats what im looking for the original boot and recovery.
I bought it from GIZTOP.
OP10PRO-GRO12256
Green
12GB- 256GB
It comes with Colos OS 12
GIZTOP dont have phone files . I have asked them and they said to send back to get repaired
VovaHouse said:
I have this problem 3 day ago.
What the Color Os ? You neet flash original boot and recovery, if not chenched you must try switch active slot A or B.
Where you find twrp for 10pro, he is not here yet A/B chenge
Click to expand...
Click to collapse
I did fastboot set_active a and the same for b ....dosent help
Canuck Knarf said:
I did fastboot set_active a and the same for b ....dosent help
Click to expand...
Click to collapse
i even did fastboot set_active other...it switches to either a or b
VovaHouse said:
I have this problem 3 day ago.
What the Color Os ? You neet flash original boot and recovery, if not chenched you must try switch active slot A or B.
Where you find twrp for 10pro, he is not here yet A/B chenge
Click to expand...
Click to collapse
the problem started because i tried flashing twrp -3.6.0_11-0-lemonadep
Canuck Knarf said:
the problem started because i tried flashing twrp -3.6.0_11-0-lemonadep
Click to expand...
Click to collapse
Of course,lemonade its op 9pro, what you Color os A07 or A08?
You
Canuck Knarf said:
the problem started because i tried flashing twrp -3.6.0_11-0-lemonade
Click to expand...
Click to collapse
You must unlock bootloader and try flash original boot and recovery
Canuck Knarf said:
the problem started because i tried flashing twrp -3.6.0_11-0-lemonadep
Click to expand...
Click to collapse
See this post
Twrp.
Root
Instructions
1. fastboot flashing unlock2.fastboot flashing unlock_critical3.fastboot flash boot boot.img (original)
4.fastboot flash recovery recovery.img (Original).
-as an option
Fastboot flash boot_a boot.img
Fastboot flash boot_b boot.img
Fastboot flash recovery_a recovery.img
Fastboot flash recovery_b recovery.img
(Boot and recovery is color os 12.1 A08)
Recovery Color os 12.1 A08
Thanks buds...I will try
Ok I think it's getting better. I followed your instructions.
It won't do step # 2 even if I change flashing to flash.
1 . I set b active
2. flash boot to b
3. flash recovery to b
4. set a active
5. flash boot to a
6 flash recovery to a
Now if i go back and set b active . then go to power off in fastboot . It just reboot back to fastboot
Now i set a active and power off in fastboot . It goes to oneplus logo ...but keeps rebooting to logo
Canuck Knarf said:
Ok I think it's getting better. I followed your instructions.
It won't do step # 2 even if I change flashing to flash.
1 . I set b active
2. flash boot to b
3. flash recovery to b
4. set a active
5. flash boot to a
6 flash recovery to a
Now if i go back and set b active . then go to power off in fastboot . It just reboot back to fastboot
Now i set a active and power off in fastboot . It goes to oneplus logo ...but keeps rebooting to logo
Click to expand...
Click to collapse
Try fastboot set_active other.
if not, we are waiting for an answer from our friend daxiaamu.
Root OP10 PRO
After going back into fastboot with a still active . I go to recovery in fastboot its back. I can wipe...i can reboot and shut off . But as soon as I plug in charger it just reboots logo
Canuck Knarf said:
Ok I think it's getting better. I followed your instructions.
It won't do step # 2 even if I change flashing to flash.
1 . I set b active
2. flash boot to b
3. flash recovery to b
4. set a active
5. flash boot to a
6 flash recovery to a
Now if i go back and set b active . then go to power off in fastboot . It just reboot back to fastboot
Now i set a active and power off in fastboot . It goes to oneplus logo ...but keeps rebooting to logo
Click to expand...
Click to collapse
Try downloading Color OS A08. End flash system for fastboot. Fastboot flash system system.img.
Color OS 12.1 Color OS 12
You must try payload dumper for extracting
Hello! On the official TWRP website I downloaded the latest version 3.7.0-11 and it turns out that I can't update the weekly ROM because TWRP doesn't show any file. Reading and asking on the internet they gave me a solution but I do not know how safe and reliable it is, they referred me to this link: https://www.123pan.com/s/qHhDVv-nuQJv where they tell me that I have to do, adb, "fastboot boot TWRP.img" with the version (BOOT) 3.7.0_12_Mi11_v7.0_A13-venus-skkk_64135681 .....the question is. How reliable is that file, considering that on the official TWRP website only supports Android 12 and earlier versions? Does anyone with Mi 11 and android 13 TKQ know how to solve this problem? Using ADB Sideload could it be possible to update without losing any data?
Thank you for all!!!
Gor3zno said:
Hello! On the official TWRP website I downloaded the latest version 3.7.0-11 and it turns out that I can't update the weekly ROM because TWRP doesn't show any file. Reading and asking on the internet they gave me a solution but I do not know how safe and reliable it is, they referred me to this link: https://www.123pan.com/s/qHhDVv-nuQJv where they tell me that I have to do, adb, "fastboot boot TWRP.img" with the version (BOOT) 3.7.0_12_Mi11_v7.0_A13-venus-skkk_64135681 .....the question is. How reliable is that file, considering that on the official TWRP website only supports Android 12 and earlier versions? Does anyone with Mi 11 and android 13 TKQ know how to solve this problem? Using ADB Sideload could it be possible to update without losing any data?
Thank you for all!!!
Click to expand...
Click to collapse
If you are on xiaomi.eu_multi_MI11_V14.0.23.1.3.DEV_v14-13.zip
and want to update on the
xiaomi.eu_multi_MI11_V14.0.23.1.9.DEV_v14-13.zip
Start by removing security on the lock screen and reboot then use OTA to download the update and update the phone reboot and the twrp install the rom.
If you want to install the latest TWRP remove security on the lock screen and reboot then flash the TWRP in fastboot mode, assuming it is a TWRP boot.
Command:
fastboot boot twrp.img
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
If REC version
Install with TWRP or fastboot flash recovery_ab twrp.img
Note that the TWRP A13 is already on the rom that you use if weekly A13.
If your system is in A12 use a TWRP A12 to flash A13.
I have Android 13. When I try to download TWRP A13 from https://sourceforge.net/projects/re...wrp-3.7.0_12-v7.0_A13-venus-skkk.img/download I get: 'Software download may not be possible on this device'
When I flash current TWRP I get two sentences, in red (error) 'Unmont data.../.../.twrp'.
Is this command 'fastboot flash recovery_ab twrp.img' new to me, what is the difference with 'fastboot boot twrp.img'?
I don't know what this REC version means?
Gor3zno said:
I have Android 13. When I try to download TWRP A13 from https://sourceforge.net/projects/re...wrp-3.7.0_12-v7.0_A13-venus-skkk.img/download I get: 'Software download may not be possible on this device'
When I flash current TWRP I get two sentences, in red (error) 'Unmont data.../.../.twrp'.
Is this command 'fastboot flash recovery_ab twrp.img' new to me, what is the difference with 'fastboot boot twrp.img'?
I don't know what this REC version means?
Click to expand...
Click to collapse
What is the current TWRP?
If the fastboot boot twrp.img command worked, it's a boot.twrp.
The REC version installs with the TWRP or fastboot flash recovery_ab twrp.img.
To download on Souceforge with the phone.
In the Android browser, press the Menu button and then Settings.
Touch the Advanced options menu.
Touch the User Agent item.
Select the system you want to pass your browser to.
The change is immediate.
What is the version number of your phone?
Go to /settings/my phone/features/model
Example:M2011K2G, M2011K2C
Did you try?
"If you are on xiaomi.eu_multi_MI11_V14.0.23.1.3.DEV_v14-13.zip
and want to update on the
xiaomi.eu_multi_MI11_V14.0.23.1.9.DEV_v14-13.zip
Start by removing security on the lock screen and reboot then use OTA to download the update and update the phone reboot and the twrp install the rom."
I have M2011K2G, xiaomi.eu 14.0.22.12.16 and TWRP 3.7.0-11, the last in the oficial web. Although, according to my research, it seems that this version is not valid for Android 13.
Yes, I removed the fingerprint and the security pattern before.
Gor3zno said:
I have M2011K2G, xiaomi.eu 14.0.22.12.16 and TWRP 3.7.0-11, the last in the oficial web. Although, according to my research, it seems that this version is not valid for Android 13.
Yes, I removed the fingerprint and the security pattern before.
Click to expand...
Click to collapse
Are you sure, I don't see this rom for your device?
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.16.DEV/
You have a Twrp A12 on an A13 system.
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and rebbot on the TWRP at each attempt.
Then flash this TWRP
twrp-3.7.0_12-v7.0_A13-venus-skkk.img
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
and install the rom.
NOSS8 said:
Are you sure, I don't see this rom for your device?
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.16.D
Click to expand...
Click to collapse
Sorry, 22.12.26 is the ROM.
'fastboot flash recovery twrp.img' doesn't work for me, only the boot command.
I didn't try 'fastboot flash recovery_ab twrp.img' but the TWRP I have (3.7.0-11) is apparently not compatible with Android 13 and that's why some say it doesn't work, but I don't understand, it's the latest version on the official TWRP website.
Gor3zno said:
Sorry, 22.12.26 is the ROM.
'fastboot flash recovery twrp.img' doesn't work for me, only the boot command.
I didn't try 'fastboot flash recovery_ab twrp.img' but the TWRP I have (3.7.0-11) is apparently not compatible with Android 13 and that's why some say it doesn't work, but I don't understand, it's the latest version on the official TWRP website.
Click to expand...
Click to collapse
We are talking about these roms, right?
because the TWRP is included in the rom.
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.26.DEV/
NOSS8 said:
We are talking about these roms, right?
because the TWRP is included in the rom.
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.26.DEV/
Click to expand...
Click to collapse
That's strange, when I installed that room, it turns out that the 'main menu' was the normal one, the one that comes without many options.
Gor3zno said:
That's strange, when I installed that room, it turns out that the 'main menu' was the normal one, the one that comes without many options.
Click to expand...
Click to collapse
I have the impression that you are talking to me about the Stock EEA rom for Europe and not the Xiaomi Eu rom custom rom.
NOSS8 said:
Are you sure, I don't see this rom for your device?
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.16.DEV/
You have a Twrp A12 on an A13 system.
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and rebbot on the TWRP at each attempt.
Then flash this TWRP
twrp-3.7.0_12-v7.0_A13-venus-skkk.img
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
and install the rom.
Click to expand...
Click to collapse
So I can't try to flash or boot with A13 version without doing the wioe and without losing all the data?
NOSS8 said:
I have the impression that you are talking to me about the Stock EEA rom for Europe and not the Xiaomi Eu rom custom rom.
Click to expand...
Click to collapse
Ok, now it's clear.
22.12.26 was in Fastboot.zip because no functional TWRP at this time.
try again to install the TWRP A13
twrp-3.7.0_12-v7.0_A13-venus-skkk.img**
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
This is the official TWRP developed by SKK and uploader by Camerado84
Command:
fastboot boot twrp.img**
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
Try several rebooting each time in Fastboot mode.
If after several attempts 5/6 still the same you will have to:
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and reboot on the TWRP at each attempt.
Then flash this TWRP**
Rename it twrp.img**
NOSS8 said:
Ok, now it's clear.
22.12.26 was in Fastboot.zip because no functional TWRP at this time.
try again to install the TWRP A13
twrp-3.7.0_12-v7.0_A13-venus-skkk.img**
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
This is the official TWRP developed by SKK and uploader by Camerado84
Command:
fastboot boot twrp.img**
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
Try several rebooting each time in Fastboot mode.
If after several attempts 5/6 still the same you will have to:
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and reboot on the TWRP at each attempt.
Then flash this TWRP**
Rename it twrp.img**
Click to expand...
Click to collapse
As soon as I have time I'll try it and let you know, thank you
Gor3zno said:
As soon as I have time I'll try it and let you know, thank you
Click to expand...
Click to collapse
To try.
In the Fastboot rom 22.12.26 look in the img folder and replace the recovery.img with the TWRP A13 by renaming it recovery.img.
Important check that the sizes are identical otherwise it will not work.
Then use the Update.bat file.
Then update via OTA.
This will allow you to keep the data.
NOSS8 said:
To try.
In the Fastboot rom 22.12.26 look in the img folder and replace the recovery.img with the TWRP A13 by renaming it recovery.img.
Important check that the sizes are identical otherwise it will not work.
Then use the Update.bat file.
Then update via OTA.
This will allow you to keep the data.
Click to expand...
Click to collapse
There is no recovery.img but the 'boot.img' file happens to weigh exactly the same as the twrpA13skkk file.
Is it possible that boot is the recovery you are referring to?
If so, I should rename the twrpA13skkk.img file to boot.img in this folder.
Although, probably misinformed, I thought that boot is the one in charge of booting the system..... so I'm afraid that changing the file will only boot in TWRP mode without being able to enter system or fastboot.
Gor3zno said:
There is no recovery.img but the 'boot.img' file happens to weigh exactly the same as the twrpA13skkk file.
Is it possible that boot is the recovery you are referring to?
If so, I should rename the twrpA13skkk.img file to boot.img in this folder.
Although, probably misinformed, I thought that boot is the one in charge of booting the system..... so I'm afraid that changing the file will only boot in TWRP mode without being able to enter system or fastboot.
Click to expand...
Click to collapse
Nope, this is a method I used a long time ago and there was a recovery.img.
Stock fastboot rom
NOSS8 said:
Nope, this is a method I used a long time ago and there was a recovery.img.
Click to expand...
Click to collapse
Well, it seems that it is no longer called that.
By installing the twrpA13skkk version you told me, via fastboot, it works perfectly !!!!! I think a lot of people have had the same problem as me because we went to the official TWRP website and the latest version listed there is not compatible with Android 13.
I looked at the cmd command screen and I noticed that after typing 'fastboot boot twr.img' appears writing 'boot.img' so maybe you can change the boot.img file from xiaomi.eu by twrpA13skkk.img (renaming it to boot.img) but as we are not sure we better not move forward on that issue until someone solves that unknown.
If it wasn't for you I wouldn't have found the TWRP version compatible with my device so thank you very much! This is the magic of forums and the internet, now I will be able to help other people thanks to you !!!!!
I have one last doubt, now that I can see the Zip file of the updated Xiaomi eu weekly version, to UPDATE WITHOUT DELETING ANYTHING I simply have to hit 'install' select the ROM and...already?
I ask this because some sites say that you have to do wipe/dalvik and wipe/cache.... in some sites say to do it before installing, in other sites say to do it after installing the ROM, in other sites say to do it before and after and in other sites say that none of this is necessary.
Gor3zno said:
Well, it seems that it is no longer called that.
Click to expand...
Click to collapse
"TWRP website"is obsolete, use my link.
Update via ota then install, the phone reboot on the Twrp and install the rom. No wipe necessary.
Would it be possible to please move this discussion to venus forums? This forum is for alioth, and this discussion could lead to some confusion. Thanks.