Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation
WolfHRB said:
Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation
Click to expand...
Click to collapse
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
lewmur said:
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.
Click to expand...
Click to collapse
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
WolfHRB said:
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
Click to expand...
Click to collapse
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible
kevinco1 said:
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible
Click to expand...
Click to collapse
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
What exact GSI and build are you trying to install? There are only a few that are compatible, otherwise you're not gonna have any other luck flashing
I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?
stradfred said:
I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?
Click to expand...
Click to collapse
Make sure you are only trying to flash arm64 builds for this device
Both 19.1-20230418 and 20.0-20230324 do install properly but there's certain bugs that make them unfit to be used as a daily driver.
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218
stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
You left out the step to format data and factory wipe.
lewmur said:
You left out the step to format data and factory wipe.
Click to expand...
Click to collapse
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.
kevinco1 said:
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218
Click to expand...
Click to collapse
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.
stradfred said:
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.
Click to expand...
Click to collapse
TWRP and fastboot can't handle the encrypted data partition. So you need to format it. Current versions of LOS re-encrypt it as soon as you boot to system. And you can't use dm-verity on this model, so you can't disable it.
stradfred said:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.
Click to expand...
Click to collapse
Did you try this build before or after the realization you had left out the steps to wipe and factory reset?
Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.
mrspeccy said:
Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.
Click to expand...
Click to collapse
If you mean you used the "Install" button in TWRP to flash, then that is your mistake. The "Install" button only has the option to flash the "Super" partition and not the "System". You need to use "Fastboot" to flash the system image. I flashed from CWD2 which is even later than CWC1, so that shouldn't be a problem. If it was, then TWRP wouldn't have worked. I'm running LOS 20 20300507 bgN.
No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).
mrspeccy said:
No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).
Click to expand...
Click to collapse
There are only certain LOS builds that work with this device, you're wasting your time if you are blindly flashing random ones.
Refer to earlier posts to confirm which ones do work. And like @lewmur just reported the newest build 20300507 bgN does flash successfully
The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?
mrspeccy said:
The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?
Click to expand...
Click to collapse
You must do a clean flash. The purpose of formatting the data partition is to get rid of the encryption. TWRP can't handle the encryption. And LOS will re-encrypt it the first time you boot to system. As to extracting the kernel from CWA3, I don't advise doing that. It could hard brick the tablet.
Related
Ok guys, this is a sureshot guide for
PROBLEM
* anyone wanting to decrypt their op3 but stuck at 1+ boot screen(Or not able to boot any custom ROMs.) and only able to restore twrp backups
* After using fastboot format userdata twrp and about phone shows only 32gb phone memory(where the hell is my rest of 32gb )
* Fastboot format userdata resulting in Stuck at boot screen or simply an unbrick trick to return to Stock OOS in unencrypted stage
SOLUTION
1. Use method 2 of Mega unbrick guide to restore your phone to stock partitions found here
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
2. After the flashing is complete do not reboot the phone instead reboot directly into bootloader.
3. In fastboot mode flash modded twrp 3.0.2.22 using command ''fastboot flash recovery recovery.img'' found here
http://forum.xda-developers.com/devdb/project/?id=15934#downloads
4. Reboot directly into twrp and using mtp mode copy latest elemental x kernel or bluspark kernel zip for OOS and SYSTEM supersu.zip into the internal storage. System supersu.zip here OR directly proceed to step 8
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
5. Now flash system supersu.zip and directly after that kernel.zip
6. Now again reboot to recovery directly and from twrp boot into system.
7. After boot up you system should be decrypted. You can check in security settings.
8.Reboot recovery and flash required firmware + modem zip found here
http://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
9.wipe data +cache +dalvik +system
10. Flash any rom of your choice and go flashoholic, use multirom or whatever you want.
Pheww. Thanks.
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Ashtrix said:
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Click to expand...
Click to collapse
anything... even multirom works flawless.
I will give this a try, Or will try to Flash the EX then perform parts of this since they support Kexec, to see what works, I have data and lot of apps working them again is a real pita with my schedule...
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
ach3fck said:
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
Click to expand...
Click to collapse
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
nikhilsnigam said:
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
Click to expand...
Click to collapse
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
ach3fck said:
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
Click to expand...
Click to collapse
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
nikhilsnigam said:
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
Click to expand...
Click to collapse
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
ach3fck said:
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
Click to expand...
Click to collapse
your bootloader doesn't get locked
nikhilsnigam said:
your bootloader doesn't get locked
Click to expand...
Click to collapse
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
ach3fck said:
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
Click to expand...
Click to collapse
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
nikhilsnigam said:
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
Click to expand...
Click to collapse
Yeah, i know that, thanks a lot, will try later all of this since i have no time now, will report how it went.Thanks!
This is a simple allow you to learn how to backup and save a copy of your firmware on PC whatever it is like no brand, vodafone etc..
Requirements:
Unlocked bootloader.
Unlocked FRP.
TWRP Recovery, click here.
Steps 1: Disable Encryption
Download the following archive.
Reboot device into fastboot mode and run fastboot flash boot dec_boot.img && fastboot reboot.
Steps 2: Backup Your PRA Firmware
Reboot to fastboot mode.
Run the following command: fastboot flash recovery twrp-3.1.1-2-v2-prague.img && fastboot reboot
Reboot to TWRP -> tab on Backup -> select all partitions -> switch storage to external sd.
Steps 3: Re-enable Encryption
Once done, reboot to fastboot mode.
flash: fastboot flash recovery stock_recovery.img
flash: fastboot flash boot boot.img && fastboot reboot ( always from IMGS archive contents)
** Note **
just follow the steps and will have a fully backup, I tested 100 times while making roms for this device!
regards
One question, in step 3, when I flash stock_recovery.img.. Can I skip that and keep TWRP? For flashing Magisk or modified SuperSU.. Thanks a lot man.. You are the best..
Dr.TheMaster said:
One question, in step 3, when I flash stock_recovery.img.. Can I skip that and keep TWRP? For flashing Magisk or modified SuperSU.. Thanks a lot man.. You are the best..
Click to expand...
Click to collapse
TWRP it's a mandatory to have root permissions, but you can revert to stock recovery once install Magisk or SuperSu.
haky 86 said:
TWRP it's a mandatory to have root permissions, but you can revert to stock recovery once install Magisk or SuperSu.
Click to expand...
Click to collapse
Yeah but I mean can I keep it as TWRP or is it necessary to flash the stock one after rooting?
Dr.TheMaster said:
Yeah but I mean can I keep it as TWRP or is it necessary to flash the stock one after rooting?
Click to expand...
Click to collapse
if you want, you can keep twrp even after rooting.
Hi Haky 86, for my HUAWEI P8 lite 2017, the build number is PRA-LA1C185B167.
I found firmware PRA-LA1C185B176 at below links, do you think they are trustworthy - will they work on my phone ?
forums.easy-firmware.com/showthread.php?182653-PRA-LA1C185B176-zip
easy-firmware.com/home/browse/file-info/id/99327/
haky 86 said:
This is a simple allow you to learn how to backup and save a copy of your firmware on PC whatever it is like no brand, vodafone etc..
Requirements:
Unlocked bootloader.
Unlocked FRP.
TWRP Recovery, click here.
Steps 1: Disable Encryption
Download the following archive.
Reboot device into fastboot mode and run fastboot flash boot dec_boot.img && fastboot reboot.
Steps 2: Backup Your PRA Firmware
Reboot to fastboot mode.
Run the following command: fastboot flash recovery twrp-3.1.1-2-v2-prague.img && fastboot reboot
Reboot to TWRP -> tab on Backup -> select all partitions -> switch storage to external sd.
Steps 3: Re-enable Encryption
Once done, reboot to fastboot mode.
flash: fastboot flash recovery stock_recovery.img
flash: fastboot flash boot boot.img && fastboot reboot ( always from IMGS archive contents)
Click to expand...
Click to collapse
Hello, I followed all the steps, but this error appears and does not finish creating the backup, is there any solution,Thanks?
Hinatasan said:
Hello, I followed all the steps, but this error appears and does not finish creating the backup, is there any solution,Thanks?
Click to expand...
Click to collapse
this was possibile only on PRA-LX1C432B161 firmware, they update encryption on newer firmwares that make backup impossible to save.
haky 86 said:
this was possibile only on PRA-LX1C432B161 firmware, they update encryption on newer firmwares that make backup impossible to save.
Click to expand...
Click to collapse
You think it would be possible what they say in this post, but adapted to our PRA-LX1?
https://forum.xda-developers.com/oneplus-5/help/error-255-twrp-t3739468
Hinatasan said:
You think it would be possible what they say in this post, but adapted to our PRA-LX1?
https://forum.xda-developers.com/oneplus-5/help/error-255-twrp-t3739468
Click to expand...
Click to collapse
Actually I won't fix nothing, I'm working on emui 8.x source to make newer roms (non treble one)
HELP ME
Good evening need some help to back up the firmware of a Huawei B310s Imei: 869242023527367
serial number: F5S8W17901002756
Thank you
Hi everyone, and a happy new year
I need some light please, i don't understand what i'm doing wrong :/
To follow this post, i can't install EU ROM anymore (via TWRP) and i don't know why...
1) i flash the EEA Global via MiFlashTool, all ok
2) i make sure to unlock bootloader, all ok
3) i flash TWRP (official 3.6), all ok
Finally i want to flash 12.5.20.0, or 12.5.17.0 of EU ROM via TWRP/install, the process end up nicelly, no error so reboot, now everytime /data is lost, so it only boot on twrp and nothing is here anymore, need to go back at 1)
That is so frustrating :/
Can anyone enlight me please ?
did you format data after flashing 12.5.20.0
marcel112 said:
did you format data after flashing 12.5.20.0
Click to expand...
Click to collapse
nope, i need to ?
(if i format data, then i'll need to reflash the rom, right ?)
Only fastboot Version available right now bro. Already using it.
If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only
marcel112 said:
If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only
Click to expand...
Click to collapse
Thanks both of you !
Ok, but when i see files like 12.5.20.0 with a twrp flashing procedure labelled Mi11 Ultra, that let me think i can do it that way, it's misleading, at least :/
So, i flashed the latest 12.6 xiaomi eu rom and it worked
New problem, i then try to use twrp to flash magisk, i do fastboot boot twrp.img and then, /data lost again, so impossible to flash magisk :/
I tried both 3.6 official and 3.5.1 unofficial
p.s.: never set security pin/pass or whatever atm, so it's not a problem with the password
why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line
marcel112 said:
why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line
Click to expand...
Click to collapse
Oh my god, i totally forgot this method
Thank you very much, seems to work !
Solved
I have flashed TWRP to recovery (on my unlocked Redmi Note 10 Pro) and can access it no problem. But I have no TWRP folder on my phone and cannot see one when connected to my computer.
I have reflashed to try to fix it, but no change. I found a thread where the suggested terminal commands but I would need to root my phone and I don't think that is something I should be doing. Any suggestions?
31272809 said:
I have flashed TWRP to recovery (on my unlocked Redmi Note 10 Pro) and can access it no problem. But I have no TWRP folder on my phone and cannot see one when connected to my computer.
I have reflashed to try to fix it, but no change. I found a thread where the suggested terminal commands but I would need to root my phone and I don't think that is something I should be doing. Any suggestions?
Click to expand...
Click to collapse
I think you can't access internal storage in case of encryption.
Google about decryption pros cons ... if you're fine with decryption check out dfe in our forum
Laptapper said:
I think you can't access internal storage in case of encryption.
Google about decryption pros cons ... if you're fine with decryption check out dfe in our forum
Click to expand...
Click to collapse
I read about that but I thought I'd see 0MB or weird filenames while looking at the filesystem in TWRP recovery and neither is the case. I did have to enter my password the first time I used TWRP and I have never been asked for it since.
31272809 said:
I read about that but I thought I'd see 0MB or weird filenames while looking at the filesystem in TWRP recovery and neither is the case. I did have to enter my password the first time I used TWRP and I have never been asked for it since.
Click to expand...
Click to collapse
Which recovery you've installed? Try newest orange fox
Laptapper said:
Which recovery you've installed? Try newest orange fox
Click to expand...
Click to collapse
So I had twrp 3.6_11-sweet installed. I just flashed Orange fox (the latest stable version) to recovery, and then I could no longer access recovery - it just restarted to flashboot. I had this problem when I tried to flash the Pixel Experience image too.
So I flashed TWRP to recovery again and everything is back to normal. But the problem is that I can’t use TWRP because there’s no folder installed.
31272809 said:
So I had twrp 3.6_11-sweet installed. I just flashed Orange fox (the latest stable version) to recovery, and then I could no longer access recovery - it just restarted to flashboot. I had this problem when I tried to flash the Pixel Experience image too.
So I flashed TWRP to recovery again and everything is back to normal. But the problem is that I can’t use TWRP because there’s no folder installed.
Click to expand...
Click to collapse
How you exactly flashed recovery?
Orange fox is working quite good....
Laptapper said:
How you exactly flashed recovery?
Orange fox is working quite good....
Click to expand...
Click to collapse
So I put the phone in fastboot mode -> connected to PC with usb -> check connection in cmd (fastboot devices) -> fastboot flash recovery "recovery_orange fox.img" -> power+up
And I get sent back to the fastboot screen
I must be doing something wrong but I have watched videos and read instructions and I don't know what it is.
31272809 said:
So I put the phone in fastboot mode -> connected to PC with usb -> check connection in cmd (fastboot devices) -> fastboot flash recovery "recovery_orange fox.img" -> power+up
And I get sent back to the fastboot screen
I must be doing something wrong but I have watched videos and read instructions and I don't know what it is.
Click to expand...
Click to collapse
Sounds ok
But without the quotes and no spaces, means change the file name like cmd:
fastboot flash recovery orangefox.img
Laptapper said:
Sounds ok
But without the quotes and no spaces, means change the file name like cmd:
fastboot flash recovery orangefox.img
Click to expand...
Click to collapse
I renamed the file but same result - it cycles through back to fastboot instead of recovery.
I don't understand. It's like it only accepts the twrp image, but even that doesn't install right.
31272809 said:
I renamed the file but same result - it cycles through back to fastboot instead of recovery.
I don't understand. It's like it only accepts the twrp image, but even that doesn't install right.
Click to expand...
Click to collapse
Please make a pc screenshot from flashing progress
You've switched on developer option usb debugging?
Laptapper said:
Please make a pc screenshot from flashing progress
You've switched on developer option usb debugging?
Click to expand...
Click to collapse
Here's the screenshot. Inbetween flashing recoveryorangefox.img and twrp.img I have tried to reboot into recovery and I have been sent back to fastboot.
Yes, usb debugging is on in the settings.
31272809 said:
Here's the screenshot. Inbetween flashing recoveryorangefox.img and twrp.img I have tried to reboot into recovery and I have been sent back to fastboot.
Yes, usb debugging is on in the settings.
Click to expand...
Click to collapse
Check out here
How to Enter Recovery Mode ? Volume Up and Power enabling Fastboot
Today I flashed EU RoM 13.0.4 to my Redmi Note 10 pro . Phone is working fine but I installed orange recovery and the process completed successfully on pc . When I press power and volume up it going to Fastboot mode instead of recovery mode. How...
forum.xda-developers.com
And take the files which there are downloadable
Try after flashing to boot via hardware keys and also via adb.
If both not working, I think you have to flash fastboot image via PC miflash and boot it to switch developer usb debugging on and restart to fastboot mode and flash twrp again.....
31272809 said:
Here's the screenshot. Inbetween flashing recoveryorangefox.img and twrp.img I have tried to reboot into recovery and I have been sent back to fastboot.
Yes, usb debugging is on in the settings.
Click to expand...
Click to collapse
One more idea, before starting from scratch:
After flashing twrp disconnecting usb and then rebooting to recovery by pressing power and vol+ until you'll see the logo and feel the vibration
Why don't you test the recovery using fastboot boot? My recommendation is never to flash any recovery before successfully having it started manually once.
My personal approach is, never to install any recovery but only boot it in case it is needed. Disadvantage is that you need to be near a computer if you want to run it.
fastboot flash recovery twrp-3.6.0_11-0-sweet.img
fastboot boot twrp-3.6.0_11-0-sweet.img
Ashle said:
fastboot flash recovery twrp-3.6.0_11-0-sweet.img
fastboot boot twrp-3.6.0_11-0-sweet.img
Click to expand...
Click to collapse
Hi all, there's been some progress but I'd like your advice before continuing. I have my preferred ROM (Pixel Experience, zipped) copied to my SD card and I can see my SD card under Install option on TWRP. My phone data has been formatted (using the twrp Wipe option). Should I try installing from the SD card? I'm nervous since I know missing steps was warned against in the installation instructions.
1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Pixel Experience.zip
4. Reboot System
Ashle said:
1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Pixel Experience.zip
4. Reboot System
Click to expand...
Click to collapse
Is 1 included in 2, or should I do something else as well?
If I'm okay to move to step 3, do I reboot to recovery or reboot into (hopefully) my new ROM?
Copy Pixel Experience.zip to sdcard
reboot to recovery
All over TWRP
1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Install Pixel Experience.zip
4. Reboot System
Ashle said:
Copy Pixel Experience.zip to sdcard
reboot to recovery
All over TWRP
1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Install Pixel Experience.zip
4. Reboot System
Click to expand...
Click to collapse
It didn't work.
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.