Related
Hello all,
I bought this new HTC one m8 few days back, it was in kitkat so i tried the Software update thing, but it keeps searching it for hours then I tried to flash ROMs and then i messed up in TWRP. I accidentally deleted everything without any backup. I tried to flash CM12.1 (not nightly)+ gapps, the logo of cm appears and after that my phone auto reboot and same thing is happening again and again. What i did so far is, i changed my CID, I unlocked my device, tried flashing many ROMs like SkyDragon, and also tried many RUU.zip/RUU.exe files but non of them work. When i tried to open zip files it says cannot open the file/ file maybe damaged or corrupted. I can get into recovery(TWRP 2.8...) I tried to flash through SD but after showing successfully done I get back to this white HTC screen again.
I am seriously in trouble.. please somebody help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SaifAhmed said:
Hello all,
I bought this new HTC one m8 few days back, it was in kitkat so i tried the Software update thing, but it keeps searching it for hours then I tried to flash ROMs and then i messed up in TWRP. I accidentally deleted everything without any backup. I tried to flash CM12.1 (not nightly)+ gapps, the logo of cm appears and after that my phone auto reboot and same thing is happening again and again. What i did so far is, i changed my CID, I unlocked my device, tried flashing many ROMs like SkyDragon, and also tried many RUU.zip/RUU.exe files but non of them work. When i tried to open zip files it says cannot open the file/ file maybe damaged or corrupted. I can get into recovery(TWRP 2.8...) I tried to flash through SD but after showing successfully done I get back to this white HTC screen again.
I am seriously in trouble.. please somebody help.
Click to expand...
Click to collapse
You need to make sure you follow the instructions while flashing a ROM. If you already did check the following:
1. Check if you have custom recovery (TWRP) and custom bootloader (check the thread in development for your device).
2.. Did you flash the right ROM? International (GSM) ROMs are not compatible with Sprint M8. Make sure you are using one from this thread.
3. Most of the time, the ROM zip you have is not completely downloaded. sometime it's error with the download. Whenever you download a ROM/any file make sure the downloaded item matches the MD5 sum.
4. Before flashing a ROM make sure you did a clean wipe. This includes system, data, cache and dalvik cache (but not the data in the sd card - last option shouldn't be checked in twrp). Also for some ROMs you need to be S-OFF. Try installing boot.img using the CMD window.
Let me know if anything mentioned above works for you
Cashreedhar said:
You need to make sure you follow the instructions while flashing a ROM. If you already did check the following:
1. Check if you have custom recovery (TWRP) and custom bootloader (check the thread in development for your device).
2.. Did you flash the right ROM? International (GSM) ROMs are not compatible with Sprint M8. Make sure you are using one from this thread.
3. Most of the time, the ROM zip you have is not completely downloaded. sometime it's error with the download. Whenever you download a ROM/any file make sure the downloaded item matches the MD5 sum.
4. Before flashing a ROM make sure you did a clean wipe. This includes system, data, cache and dalvik cache (but not the data in the sd card - last option shouldn't be checked in twrp). Also for some ROMs you need to be S-OFF. Try installing boot.img using the CMD window.
Let me know if anything mentioned above works for you
Click to expand...
Click to collapse
Thanks bro.. I waited for 1 day then I didnt came back though i fixed it later that day by flashing sprint bad boyz rom and their firmware.. It worked for me
just wanted to point out that the OS showing in the bootloader changes while flashing a zip file in the fastboot. Whatever zip you flashed last, check android-info.txt file. (ofcourse you can flash custom zip files with firmware if you have SOFF only)
Hi All. Complete newbie to the forum here......in search of advice!
I've just got my new OnePlus 3T, so wanted to get it all set up and rooted before switching over from my Galaxy S5.
After reading several guides I followed the below steps:
Completed the OTA update to OOS 4.0.2
Unlocked the boot loader
Flashed TWRP 3.0.3
Booted into Recovery and TWRP asked for the encryption password (which was the same pattern I used in normal mode)
Internal memory was accessible so I proceeded to flash no-verity-opt-encrypt zip and SuperSu.zip. (I couldn't tell if they flashed successfully).
Rebooted
When the phone tries to reboot, I eventually get a screen saying 'Encryption Unsuccessful' and suggests I need to factory Reset.
When I select to reset, it boots back in to TWRP, but there is no request for the encryption pattern this time, and internal memory doesn't seem to mount. (showing as 0mb).
I'm wondering what my next step should be?
Should I try to flash the latest TWRP (3.0.4) via ADB?
Or would I be better off trying to flash back on stock recovery and the stock OOS 4.02 rom, and then wait for a newer TWRP before trying to get root access again?
.......Or will none of the above work?!
All I was really looking to do was root the phone. I'm not planning on changing from the stock OOS rom. I also don't mind if its encrypted or not encrypted.
I have had a look through some of the threads, but cant find examples of this scenario. Any help appreciated!
Which SuperSU file did you flashed?
The-Wexican said:
I proceeded to flash no-verity-opt-encrypt zip and SuperSu.zip.
Click to expand...
Click to collapse
I hope you didn't flash in that exact order. That could possibly be the reason for your issue. Also, you don't need the verity zip if you're flashing SuperSU.
Thanks for the feedback. Below is a link to the guide I followed on the Oneplus forums:
[GUIDE] OnePlus 3T: How to Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup and More !! (It wont let me link the thread as I'm a new user, but Google will show it!
That suggested to flash them in that order, I think.
SuperSU-v2.79-201612051815.zip was the SuperSU I used.
All, just to add, I don't need to recover any data or anything like that. I'm just looking for the best way to get out of this bot loop (of sorts).
I'm kinda thinking that because TWRP Recoveryseems to load OK, I could maybe flash back on the stock recovery and then side load the stock rom?
Any thoughts?
Or is it worth a shot at updating to the latest TWRP first (3.0.4)?
Below is the message I see when I try to boot the phone normally now (not in recovery)........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The-Wexican said:
Below is the message I see when I try to boot the phone normally now (not in recovery)........
Click to expand...
Click to collapse
I did what you did 2 days ago with success.
I recommend you flash back to stock and do the following:
-New devices boot
-Received OTA 7.0, 4.0.2 OOS
-fastboot oem unlock routine
-Flashed TWRP 3.0.4-0 - follow every step of: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391 - read this 5 times, step 11 only requires you pick A) OR B), do not flash both
-Flash UPDATE-SuperSU-v2.79-20161211114519.zip (if you picked Step 11 A), that's what I did).
-Reboot
-Success
stephlal said:
I did what you did 2 days ago with success.
I recommend you flash back to stock and do the following:
-New devices boot
-Received OTA 7.0, 4.0.2 OOS
-fastboot oem unlock routine
-Flashed TWRP 3.0.4-0 - follow every step of: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391 - read this 5 times, step 11 only requires you pick A) OR B), do not flash both
-Flash UPDATE-SuperSU-v2.79-20161211114519.zip (if you picked Step 11 A), that's what I did).
-Reboot
-Success
Click to expand...
Click to collapse
Awesome!
That worked. Thanks for your help!
Now running OP3T with OOS 4.0.2, TWRP recovery, rooted with SuperSU, and I even cleared the DM-Verity nag screen by booting into bootloader and running:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Very happy now!
Hello,
I have this phone (infinix note 4 x572) running oreo 8.1 , build number :X572-H5312CE-O-180531V117
I wish to root it but after a while of searching i'm overly confused and frustrated..
can you please guide me through rooting it?
thanks alot
btw, does local update help in any way ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All the info and installation instructions you need can be found in the release thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And if you encounter problems along the way, take a look at the troubleshooting guide.
https://www.didgeridoohan.com/magisk/Magisk
If you have further questions after that, make sure to be specific about what you need help with. "Guide me through it" is a bit too general and is already covered in the links above.
Didgeridoohan said:
All the info and installation instructions you need can be found in the release thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And if you encounter problems along the way, take a look at the troubleshooting guide.
https://www.didgeridoohan.com/magisk/Magisk
If you have further questions after that, make sure to be specific about what you need help with. "Guide me through it" is a bit too general and is already covered in the links above.
Click to expand...
Click to collapse
thanks, the first prerequisite is the stock boot.img,, i tried backing it up using miracle box but encountered the 'unstable port' problem, what other possible ways i could extract the boot.img from my phone ?
and btw, i remember asking a guy somewhere and he told me that magisk won't root my device, is that true considering it's a less-known manufacturer ?
yazansayed said:
thanks, the first prerequisite is the stock boot.img,, i tried backing it up using miracle box but encountered the 'unstable port' problem, what other possible ways i could extract the boot.img from my phone ?
Click to expand...
Click to collapse
I'd try the TWRP route instead. I found this thread after about 2 minutes of searching on XDA (search words "infinix note 4 x572"):
https://forum.xda-developers.com/android/general/infinix-one-support-root-twrp-firmware-t3695803
It's a really good idea to use the XDA search, because it often works quite good.
If you want to keep the stock recovery on your device, you can actually just boot the TWRP image instead of flashing it. In that case, the command used in that thread:
Code:
fastboot flash recovery recovery.img
should be changed to:
Code:
fastboot boot recovery recovery.img
If that doesn't work, you can actually make quite easily make a backup of your boot image in TWRP and then patch that file in the Manager, to see if that works better.
If things don't work out in TWRP, make sure to provide the recovery log.
---------- Post added at 20:35 ---------- Previous post was at 20:32 ----------
yazansayed said:
and btw, i remember asking a guy somewhere and he told me that magisk won't root my device, is that true considering it's a less-known manufacturer ?
Click to expand...
Click to collapse
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...
Didgeridoohan said:
I'd try the TWRP route instead. I found this thread after about 2 minutes of searching on XDA (search words "infinix note 4 x572"):
https://forum.xda-developers.com/android/general/infinix-one-support-root-twrp-firmware-t3695803
It's a really good idea to use the XDA search, because it often works quite good.
If you want to keep the stock recovery on your device, you can actually just boot the TWRP image instead of flashing it. In that case, the command used in that thread:
Code:
fastboot flash recovery recovery.img
should be changed to:
Code:
fastboot boot recovery recovery.img
If that doesn't work, you can actually make quite easily make a backup of your boot image in TWRP and then patch that file in the Manager, to see if that works better.
If things don't work out in TWRP, make sure to provide the recovery log.
---------- Post added at 20:35 ---------- Previous post was at 20:32 ----------
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...
Click to expand...
Click to collapse
thanks alot for the quick responses, i will try it and reply as fast as possible
okay, i downloaded the twrp recovery image for Note 4, flashed it using Fastboot method successfully,
the problem is when i try to boot into the twrp recovery mode, i tried holding the power menu+ vol.down buttons, it sends me into a black screen with "factory mode" upwards in yellow, no button is working.
i then tried
Code:
adb reboot recovery
the phone reboots and says "No command" under a red triangle.
i then tried to flash the twrp img using sp flash tools, and flashed it successfully but the same errors occur, i can't seem to be able to boot into recovery mode.
i looked up for a solution for the "no command" problem, here's one:
I faced the same problem with nexus 6p. It works when you root immediately after flashing the TWRP. Keep the superSU file in the storage. Get into bootloader. Flash TWRP via fastboot. Without restarting anything, just press volume up/down buttons while in the bootloader to select recovery. TWRP will open. Flash the SuperSU.zip. Then restart the system. Next time, if you open recovery, you won't get the "no command". If you don't flash SuperSU and you try to open recovery later, you will get the "No command".
Click to expand...
Click to collapse
what i understood is that i shouldn't reboot my device using "fastboot reboot" , he says i should get into recovery mode directly without restarting, idk how to do that since there are no option for it on the screen, i just have
Code:
=> FASTBOOT mode...
on the screen !
Didgeridoohan said:
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...
Click to expand...
Click to collapse
unfortunately i never used the sp flash tool before, so i tried flashing a stock rom but the device is now dead with "dram failed" error, i'll try fixing this first
It's tricky trying to help with a device you don't have...
Did you manage to boot to recovery? Usually you use the volume buttons to select the options and then the power button to confirm. You could also just use the fastboot boot option command I wrote earlier. It'll boot straight into TWRP.
There are a few threads for your device around, so if you need help specific to your device, that's the place to go...
everything is fine now,, fixed the device by flashing a rom named (X572-H5312CE-O-180203V55) then used magisk app to patch the included boot.img, flashed the patched boot.img using sp flash tool,, and everything is working fine now,,,
thanks alot
the twrp from the post you provided is for an older firmware, this is why i couldn't get into recovery after i flashed the provided twrp img,, there is no available twrp for the oreo version of the firmware, but i requested one from twrp builder project,, thanks alot, i've learnt alot in the last 24 hours
yazansayed said:
everything is fine now,, fixed the device by flashing a rom named (X572-H5312CE-O-180203V55) then used magisk app to patch the included boot.img, flashed the patched boot.img using sp flash tool,, and everything is working fine now,,,
thanks alot
Click to expand...
Click to collapse
could you upload the boot.img pls (the stock and the patched if possible )
Disclaimer: No guarantees. Follow at your own risk. I am not responsible for bricked phones.
Credits to 4PDA
Prerequisites:
Knowledge of OEM unlocking from Developer options, adb, and fastboot
Knowledge of QPST in case you encounter bootloop, so you can revert to a reliable stock ROM
Unlocked bootloader (from here)
1) Get your bootloader unlocked, if you haven't already.
- Visit https://www.zui.com/iunlock
- Enter the IMEI1 (Second number when you call *#06# with the phone)
- Enter the Device ID from the Bootloader/Fastboot (Hold VOL- and Power, while device is off)
- Enter your email and captcha and set the checkmark to acknowledge voiding your warranty.
- If you get an error saying that your IMEI1 is wrong, put in a sim card and wait a few hours. If it still doesn't work, write an email to [email protected]
- In the developer settings in android, enable usb debugging and oem unlock.
- Flash the sn.img file you receive with fastboot (again, hold vol- and power while the device is off). Command is 'fastboot flash unlock sn.img'. You need compatible usb drivers, qualcom drivers and adb/fastboot to do that. Use google or write me a PM if you have trouble with that.
- execute 'fastboot oem unlock-go'
- This allows you to use fastboot to flash custom system/boot/vendor/vbmeta images
Click to expand...
Click to collapse
@wzsx150's recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img MEGA Google Drive
@wzsx150's TWRP for Android 10 TWRP-3.3.2B-0508-LENOVO_Z5S-10.0-CN-wzsx150-fastboot.7z (extract the IMG file and flash using fastboot)
3) Now you can flash TWRP.
- Download ...
- Flash it from the Bootloader with 'fastboot flash recovery recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img'
- Press VOL UP / VOL DOWN to navigate to recovery.
Click to expand...
Click to collapse
11.3.169: L78071_11.3.169_DEV_FullOTA.zip
11.5.096 Update: ZUI_11.3.169_DEV_TO_ZUI_11.5.096_ST.zip
11.5.111 Update: ZUI_11.5.096_TO_ZUI_11.5.111_ST.zip
Other files, use at your own risk
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Official TWRP for jd2019
In recovery, Format data, then wipe Dalvik/ART Cache, Cache, Data
Reboot to recovery
Install in order, without rebooting, 11.3.169 -> 11.5.096 Update -> 11.5.111 Update.
Install Magisk 20.4
Install TWRP for Android 10 (above) using fastboot if the update replaces stock recovery after rebooting
Edited out from original
Wipe Data and flash Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
In order not to encrypt Data in the future, install Official TWRP immediately after installing updates. Install > Install Image > twrp-3.3.1-0-jd2019.img
Install GApps
Note: I do not know if the 11.5 update relocks the bootloader. It doesn't lock the bootloader.
I had bootloop from OpenGApps. 4PDA post advises to use BiTGApps. You can install Google Play Store from the built-in Lenovo App Center and that's what I did.
Haven't tried disabling dm-verity and forceencrypt.
Good job, my man, I'll check it out tonight and prepare ourselves an updateable package for people coming from any rom to avoid the hassle of going through all of that. As soon as I get it working will release a new TWRP for Android 10.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
carlshark said:
View attachment 5036881
Click to expand...
Click to collapse
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
jacoghi said:
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
Click to expand...
Click to collapse
I've been using the phone on 11.5.111 for a couple of days now.
I flashed both the 3.3.2 TWRP of @wzsx150 and the official TWRP and they seem to be working. I didn't turn off encryption so it seems to work well.
Happy to have helped in a small way. Thank you for your hard work!
links not works
vesdan said:
links not works
Click to expand...
Click to collapse
Thanks for the heads up, apparently the original poster removed the links. Will be uploading the ones I used.
Reuploading done.
Thank you very much
Thanks for the rom my friend.
Can you please upload the latest update cause i am rooted and it cannot be installed via the system.
Also guys ,does anyone knows if i can put the latest android 10 with multilanguage rom ?Thank you for everything ,i appreciate.
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
galardo_2 said:
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
Click to expand...
Click to collapse
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
vesdan said:
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
Click to expand...
Click to collapse
but the qpst app need an aditional content.xml file, where can i get one
Install global via fastboot, all is included or in qfil ROM is all in zip file
vesdan said:
Install global via fastboot, all is included or in qfil ROM is all in zip file
Click to expand...
Click to collapse
I tried and failed again
i tired and failed again
galardo_2 said:
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
Click to expand...
Click to collapse
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
carlshark said:
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
Click to expand...
Click to collapse
after a few atempts (3-4 days) the imei number got accepted, but now i have another problem as you can see, i flashed the gapps and now i have the bootloop and i dont have a clue how to undone it
hello friends I have all the updates installed, but it tells me that there is a new one, where can I download it?
On the other hand, what difference is there between installing by twrp and qfill?
galardo_2 said:
i tired and failed again
Click to expand...
Click to collapse
This is problem with program, drivers sahara. Try fastboot
Hi everybody, i'm having a problem with my phone. I'm going crazy.
I'm trying to flash TWRP but, everytime I try to do that, the process fails.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Even if I try to directly boot twrp.img, i'm not able to access storage (when I try to access storage, UpAlevel is shown and I can't access anything).
I already tried to wipe data or change filesystem (as suggested in various threads). Nothing changed.
Any help would be greatly appreciated.
Twrp:MARS
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
NOSS8 said:
Twrp:MARS
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
Click to expand...
Click to collapse
Hi, NOSS8, thank you so much for your reply! following this I managed to flash twrp recovery. Unluckily, I'm still not able to access storage.
Changing/reverting changes to file system allows me to see storage size; however, I still can't have access to it.
Don't really know what that "Up A Level" means tho
Which rom* and TWRP*(full name)?
NOSS8 said:
Which rom* and TWRP*(full name)?
Click to expand...
Click to collapse
I have this ROM installed: star_global_images_V13.0.6.0.SKAMIXM_20220907.0000.00_12.0_global
about twrp, it's the latest for my device I found on twrp's official website (but I also tried with another earlier version, twrp-3.6.2_11-0-mars, and nothing changed)
FFocardi said:
I have this ROM installed: star_global_images_V13.0.6.0.SKAMIXM_20220907.0000.00_12.0_global
about twrp, it's the latest for my device I found on twrp's official website (but I also tried with another earlier version, twrp-3.6.2_11-0-mars, and nothing changed)
Click to expand...
Click to collapse
Use this TWRP twrp-3.7.0_12-v7.2_A12-mars-skkk
NOSS8 said:
Use this TWRP twrp-3.7.0_12-v7.2_A12-mars-skkk
Click to expand...
Click to collapse
OMG thank you so much! It worked!!
@NOSS8 ... Thanks.... KIndly answer following for Mi phone , as I am a novice ..
1. When to use TWRP and when to use Fastboot ROM for flashing.?
2. If I flash higher version EU ROM v14 in my phone (say 11 ultra), can I lower down to v13? How to do that? Does only flashing by mi tool in fastboot mode be better?
3. If I flashed higher version EU ROM say v14 in a Indian Mi 11 Ultra phone and root it with Magisk, will I be able to get OTA updates regularly or I need to reflash when a new upgraded version comes?
1. When to use TWRP and when to use Fastboot ROM for flashing.?
If the rom is Hybrid, you use one or the other, your choice.
2. If I flash higher version EU ROM v14 in my phone (say 11 ultra), can I lower down to v13? How to do that? Does only flashing by mi tool in fastboot mode be better?
You can downgrade but you will have to format the data (data erased), Miflash erases your data (recommended to downgrade).
3. If I flashed higher version EU ROM say v14 in a Indian Mi 11 Ultra phone and root it with Magisk, will I be able to get OTA updates regularly or I need to reflash when a new upgraded version comes?
You will have more updates with the Weekly than the stable, you will lose the root with each update.
NOSS8 said:
1. When to use TWRP and when to use Fastboot ROM for flashing.?
If the rom is Hybrid, you use one or the other, your choice.
2. If I flash higher version EU ROM v14 in my phone (say 11 ultra), can I lower down to v13? How to do that? Does only flashing by mi tool in fastboot mode be better?
You can downgrade but you will have to format the data (data erased), Miflash erases your data (recommended to downgrade).
3. If I flashed higher version EU ROM say v14 in a Indian Mi 11 Ultra phone and root it with Magisk, will I be able to get OTA updates regularly or I need to reflash when a new upgraded version comes?
You will have more updates with the Weekly than the stable, you will lose the root with each update.
Click to expand...
Click to collapse
Thanks
NOSS8 said:
Use this TWRP twrp-3.7.0_12-v7.2_A12-mars-skkk
Click to expand...
Click to collapse
Why install TWRP "mars" on a "star" device ?
infamas said:
Why install TWRP "mars" on a "star" device ?
Click to expand...
Click to collapse
2 versions of phone 2 versions of TWRP.
Recovery for Xiaomi devices - Browse /star at SourceForge.net
List of relevant recovery in one place
sourceforge.net
sandeep1303 said:
Thanks
Click to expand...
Click to collapse
Have you already tried to remove fingerprints, pins and password? Here a tutorial.
FFocardi said:
Hi, NOSS8, thank you so much for your reply! following this I managed to flash twrp recovery. Unluckily, I'm still not able to access storage.
View attachment 5869405
Changing/reverting changes to file system allows me to see storage size; however, I still can't have access to it.
View attachment 5869407
Don't really know what that "Up A Level" means tho
Click to expand...
Click to collapse
Have you already tried to remove fingerprints, pins and password? Here a tutorial. Go to minute 8:00