Related
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Completely Bricked
Me too need a stock rom of ta 1056. Please help if you could manage to provide a helping hand... ?
I had the same issue like yours, looping in twrp. then i tried to flash it with a so called stock rom from net, guess what it went completely bricked and I donnow what to do. ??
mrabudi said:
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Click to expand...
Click to collapse
It's simple. just get the stock recovery (and boot, optional) to flash it with fastboot and go to recovery and wipe it and you'll be ok.
and also using the twrp on this phone is not a great idea to wipe.
if you wanna wipe. please use "fastboot -w" to wipe the phone while bootloader is unlocked. or stock recovery to wipe.
Because twrp built this recovery with only formatting option was ext4 to /data and /cache. So the phone cannot operate properly. Which leads to fake failed decryption notification.
Data partition must need to be formatted under f2fs format.
And finding rom for this phone is pretty easy. Just find some nb0 file for this phone (any variant of this phone should work) and extract it with "nb0 extractor" and then flash it with SP Flash tool by mediatek.
That's my way. I don't know how will you do. But normally you only need the nb0 file and then flash it with OST LA (Nokia's flash tool based off Intel's SUT L1/L3 tool).
My Nokia 1 TA-1047 stuck at Nokia logo screen
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
cuantonhonhoi said:
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
Click to expand...
Click to collapse
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047. Since it's a universal ROM so any variant of the phone can also work) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to look at line with partition "metadata" and then edit "boundary_check" to false.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
kutiz21 said:
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to hide/delete line with partition "metadata" in scatter.txt and you can flash it perfectly.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
Click to expand...
Click to collapse
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
pabloluih said:
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
Click to expand...
Click to collapse
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
kutiz21 said:
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
Click to expand...
Click to collapse
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
That's weird. If you unlocked the bootloader and install adb/fastboot (must be latest version. Older version will not recognize the phone, download platform-tools from google dev site, don't download adb tools off XDA) + Nokia's driver from emulated CD drive (every time you plug the phone to computer with official rom, you'll see it) properly then it should be able to work.
You need to check the fastboot device driver Device Manager (devmgmt.msc) and see if the driver is properly installed yet.
You can only use "fastboot -w" once the bootloader is unlocked. And booting up the phone. It will say the bootloader is in Orange state.
You need to unlock oem bootloader from developer settings when the stock rom is there. And in fastboot too
Here is how you unlock it:
Enable oem unlock from dev settings
Then reboot to fastboot mode (bootloader)
Do this:
"fastboot oem key "serial number string converted to md5, not imei strings" "
"fastboot oem unlock"
Volume up
Then you are actually unlocked the bootloader.
Unlock from developer settings only will not do the trick. It only allows you to have ability unlock the bootloader in fastboot.
If you stuck on the Encryption unsuccessful screen. Try wipe it with stock recovery or "fastboot -w" (if you properly unlocked the bootloader)
If you think you can't do anything anymore. Just flash the ROM provided you above.
If you need the extracted ROM for SP flash tool and the fastboot driver. I can link it to you.
Most of all drivers will automatically install off Windows Update if you're on Windows 10 (except the fastboot driver, and yes. SP flash tool drivers are also provided by Windows 10 too)
Also. You should update the phone to the latest software update when flashing stock rom too. Because newer builds for this phone is compatible-friendly with GSI rom (Treble ROMs like AOSP Android 9 or 8.1 by phhusson)
Updates on Android 9/10
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
Nokia might harden the security of the device so you can't use Magisk on stock rom.
Didn't realize how common this was until I had to look around for a fix. Apparently when flashing a new rom (In this case it was Oxygen OS, Bliss, and Lineage I was trying) It's possible to screw up your Persist partition which govern your sensors. As a result me and a few other people when flashing new roms lose auto-rotate. So I was looking on ways to fix it, but the downloads were too old and broken.
So **** it, I decided to try flashing Miui global from the recovery tool.
So my system image, and recovery image are gone. That leaves me with just Fastboot with unlocked bootloader.
I explained my situation, but here's what I'm really asking. #1 I used to have a Xiaomi account that was authorized to unlock my bootloader. It's been over a year, but before the recovery tool bricked my Mi Pad, it said EDL not authorized. So do you lose your permissions over time? Anyway to get it back.
And #2, does anyone have, know, or would like to provide me backups to vendor, firmware, and/or persist so I can try to fix those? I don't have the time tonight, but even though I don't have a system or recovery, I'm assuming with an unlocked bootloader and fastbook, I can still flash twrp, and work my way from there...
Lastly #3, does anyone know how to bypass EDL not authorized in the recovery tool? This is my preferred way of recovery, since it would reflash all the partitions back to stock and I could just re-mod from there...
I have actually recovered from a destroyed system image, destroyed recovery image, with a locked bootloader. But didn't encounter the EDL issue in my memory, it's been so long I forgot how that happened
Just like to add that I discovered that I still have recovery access, so I could just flash a rom to get back into working order, but that still leaves my sensors not working. So if anyone has a link or backup for Persist partition that would be appreciated
Okay, I know no one replied or helped, but I resolved my own issue, and I'll describe how I messed myself up to get myself better.
1. Flashed a rom via TWRP, this somehow led to rotation not working. Learned rotation sensor data is in Persist partition. Assuming this partition overwritten, corrupted, or likely wiped due to negligence.
2. This led to me trying out Xiaomi recovery tool. I would find out that my account isn't authorized anymore. So flashing tool would always stop flashing when it came to flashing the kernel. Then I created this thread for help. Particularly to acquire a backup of someone's Persist. Help did not arrive
3. This led me to download the Chinese rom (flagship zip) of Miui for Xiaomi Mi Pad 4. This was going to overwrite my recovery and vendor partitions, so I was hoping it would flash my Persist partition as well.
4. System would not boot, softbrick/bootloop. Recovery reverted to stock Chinese. Bootloader still unlocked. Booted into Fastboot
5. ADB terminal, typed:
Code:
fastboot devices
Getting device ID, looking good. Then typed
Code:
fastboot flash recovery rec.img
(I renamed TWRP to rec.img for lazy reasons) ADB says writing flashed recovery successful.
I reboot into recovery. Recovery still Chinese stock ?️?️?
Back to Fastboot, repeat #5, same. Then I type
Code:
fastboot erase recovery
ADB confirms erased recovery, I type:
Code:
fastboot boot recovery
ADB does not detect recovery. So I'm thinking my recovery is gone now... Then I try booting into recovery through Vol Up + Power to make sure recovery had been destroyed... Recovery still Chinese stock ?️?️??
So my assumption was correct that I couldn't overwrite my recovery partition, and my fear was that I needed to enable USB debugging even though my system partition is destroyed
6. I boot back into Fastboot and I type
Code:
fastboot boot rec.img
This boots TWRP without flashing it to your recovery partition... Atleast this works.
7. Attempt to wipe System/Data/Cache/Internal, even though only half those weren't necessary. Could not wipe. Mounted, then repeated... Could not wipe. Assuming this was encryption related, I go back to Wipe and just Slide to format to factory conditions. Finally getting somewhere here.
8. Tired of this hole I dug myself into, I plug in my USB flash drive and flashed TWRP Permanently using TWRP, reboot into recovery to confirm -> looking good -> Flash Lineage + Gapps, with the acceptance that because I didn't have an authorized Xiaomi account anymore, and no one would share a Persist backup, that I was just gonna have to deal with no rotation and rely on an app-crutch
9. Boot into System, rotation working. ?️??️
I didn't think flashing the zippable Chinese rom would actually fix Persist. I originally intend to just use the Chinese Miui and setting up my Mi Pad 4 with my Xiaomi account to somehow re-authorize my account to try the flashing tool again. I did not expect the bootloop, and I damn sure didn't expect ADB telling me I successfully flashed recovery or erased it, only to find out stock recovery kept refusing to go away.
And my final question is:
Can anyone tell me how much usable storage the 32GB Mi Pad 4 should freaking have?!
I always used Micro SD flashed as Internal Storage so I'd always see 80GB free. But now on a fresh install on a new rom I see that I only have 22GB usable storage, on a 32GB device, Lineage less than 1GB, and gapps only 200MB. So all together OS should not exceed 2-3GB unpacked...
WHERE THE HELL IS THE REST OF MY STORAGE?!
I SHOULD HAVE 5 MORE GB, I SHOULD HAVE 26~27GB OF USABLE STORAGE BUT MY SYSTEM SAYS ONLY 22Gb
DOES anyone else have 10GB of storage missing?!
How much should I have?!
Thanks this is good read and may help someone in the future.
There is a persist.zip shared in the Miui 12 port thread.
I have the 64gb version but never took notice of how much remaining storage out of the box. Next time I flash a ROM I'll check and let you know.
scloss84 said:
Thanks this is good read and may help someone in the future.
There is a persist.zip shared in the Miui 12 port thread.
I have the 64gb version but never took notice of how much remaining storage out of the box. Next time I flash a ROM I'll check and let you know.
Click to expand...
Click to collapse
Yeah, I found persist zips but the link was broken.
This is actually the 2nd time I bricked my device, but the 1st time I bricked it, I had just got it around the same time I got the Poco F1, so I had a Xiaomi account, with authorization. So I assumed how I un-bricked my device the 1st time, would fix the brick the 2nd time. I never imagined my account would lose authorization. So flashing the Miui using the Xiaomi recovery tool was useless. So I had to learn/relearn other tricks.
I actually enjoy bricking my devices a little bit for the experience to learn new things. Like this time, I didn't know you could run a recovery on the side through fastboot commands without flashing it. I also didn't know that recovery partition would reject flashes because mi stock recovery was encrypted (or maybe it was a USB debugging thing) , I didn't know Mi Flash authorization could be revoked, and I didn't know what the Persist partition did.
My 1st brick happened because of the Mi recovery tool. No one told me that if you buy a Mi Pad 4 with unlocked bootloader from AliExpress, use the Mi recovery tool, the tool actually intentionally bricks your device and locks your bootloader. The fix for that was opening the mi pad up, shorting some contacts, force the pad into EDL mode, and use a patched bat file and run the tool again and pray it takes. Because I wasn't authorized it wouldn't run the tool.
Thank ****ing God my bootloader was still unlocked this time. I don't think I could have came back
Post 225 in the Miui 12 port thread, the persist.zip is still being shared I checked just now. Not that you really need it if flashing the full rom got your rotation back.
There was 1 time my twrp touch screen became unresponsive after flashing and trying different twrps, and then system touch screen also gone dead, so I can't restore persist even if I wanted to.
One question, lots of tutorials talk about extracting the persist.zip from the fastboot ROM, but I can't find it in the fastboot rom... But the MiFlash tool had never failed me so anything goes wrong I'll just MiFlash it.
I was a Mi A2 user for a while, now I'm moving to Note 9 Pro and I feel a bit lost because of lacking of guides and tools.
I encounter some unexpected issues with disabling phone encryption. In short, I followed the steps I used for my Mi A2, but it seemed only working partially, and I encountered boot loop when upgrading ROM afterwards.
The details are as follow:
I have Note 9 Pro global (joyeuse), originally it was on stock ROM V11.0.5.0.QJZMIXM
After unlocking bootloader, I booted to TWRP with TWRP-3.4.1B-joyeuse-fix.img (from https://xiaomi.eu/community/threads/custom-twrp-3-4-1b-for-redmi-note-9-pro-joyeuse.56896/ ) and flashed Magisk, then Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip (from https://zackptg5.com/android.php#disverfe )
Everything was fine, I could debloat and disable Xiaomi services, and Google Pay was working (with Magisk Hide and MagiskHide Props Config).
But when entering TWRP again, TWRP requested passcode to decrypt data, that's when I realized the phone was not decrypted. Booting to normal mode, phone Settings showed "Encrypted". But because TWRP was able to decrypt with passcode and could backup as normal, so I ignored it.
When V11.0.7.0.QJZMIXM was released, I backed up /data using TWRP and flashed the new ROM using fastboot without erasing data. Then the phone was in boot loop (it showed redmi logo then vibrated then rebooted)
I flashed back V11.0.5.0.QJZMIXM without erasing data, but it still entered boot loop.
I decided to wipe data (using TWRP and using Wipe menu in XIaomi recovery mode), but boot loop still occurred.
I flashed V11.0.7.0.QJZMIXM again, but this time without keeping data (flash_all.bat), but boot loop still occurred.
I accidentally selected flash all & lock bootloader (in MiFlashTool), then phone could boot up normally. But I lost root, and bootloader was relocked.
Additional info: In a rage, I turned on Developer mode and tapped to bind mi account, and now I have to wait 168hrs to unlock bootloader again.
Questions:
What have I done wrong that the phone entered boot loop even after wiping data?
What's the proper way of using TWRP so that I can backup data and can update ROM in the future without going through this mess again?
HRSE said:
I was a Mi A2 user for a while, now I'm moving to Note 9 Pro and I feel a bit lost because of lacking of guides and tools.
I encounter some unexpected issues with disabling phone encryption. In short, I followed the steps I used for my Mi A2, but it seemed only working partially, and I encountered boot loop when upgrading ROM afterwards.
The details are as follow:
I have Note 9 Pro global (joyeuse), originally it was on stock ROM V11.0.5.0.QJZMIXM
After unlocking bootloader, I booted to TWRP with TWRP-3.4.1B-joyeuse-fix.img (from https://xiaomi.eu/community/threads/custom-twrp-3-4-1b-for-redmi-note-9-pro-joyeuse.56896/ ) and flashed Magisk, then Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip (from https://zackptg5.com/android.php#disverfe )
Everything was fine, I could debloat and disable Xiaomi services, and Google Pay was working (with Magisk Hide and MagiskHide Props Config).
But when entering TWRP again, TWRP requested passcode to decrypt data, that's when I realized the phone was not decrypted. Booting to normal mode, phone Settings showed "Encrypted". But because TWRP was able to decrypt with passcode and could backup as normal, so I ignored it.
When V11.0.7.0.QJZMIXM was released, I backed up /data using TWRP and flashed the new ROM using fastboot without erasing data. Then the phone was in boot loop (it showed redmi logo then vibrated then rebooted)
I flashed back V11.0.5.0.QJZMIXM without erasing data, but it still entered boot loop.
I decided to wipe data (using TWRP and using Wipe menu in XIaomi recovery mode), but boot loop still occurred.
I flashed V11.0.7.0.QJZMIXM again, but this time without keeping data (flash_all.bat), but boot loop still occurred.
I accidentally selected flash all & lock bootloader (in MiFlashTool), then phone could boot up normally. But I lost root, and bootloader was re-locked.
Additional info: In a rage, I turned on Developer mode and tapped to bind mi account, and now I have to wait 168hrs to unlock bootloader again.
Questions:
What have I done wrong that the phone entered boot loop even after wiping data?
What's the proper way of using TWRP so that I can backup data and can update ROM in the future without going through this mess again?
Click to expand...
Click to collapse
first of all you are not the only one that faces same problems. So chears mate. Next is the TWRP and the lack of stable/working version since i have done quite few phones now i can tell that the TWRP encryption ignore is not persistent and it works while you don't touch the recovery and not booting it up. Upon the boot it triggers the encryption and although he filesystem is not encrypted it still thinks it is.
Solution for now? wait for the fixed version while this is new phone and may take some time to re-code he recovery (find the damn cause of the encryption trigger).
Anyways. I am still thinking to do the fastboot rom mod, root it while it is not flashed and hen flash it while i don't actually need. I just need to remove all the miui/xiaomi stuff, block the damn ADS and root the phone and those things can be done on a pc i am just figuring out the correct way to do i.
The idea about skipping the TWRP came right after i downloaded mi-flash tool and found out that it uses same fastboot mode to flash everything and the file structure of the rom is not packet or something. Img files can be exacted and re-packed again so everything in the image can be modified.
What i really hate is the fact that there is tons of tools for other phones but somehow Xiaomi was skipped in the device selection...
Downloaded unlock tool, nice but limited to only requesting ad unlocking the phones bootloader. Next thing is the flash tool, it is limited to only flashing. There is xiaomi tool v2 that can also install the twrp, and cause the encryption crap or download and install stock or xiaomi.eu...
What i was looking for was the tool that can take the stock, decompress it and allow you to choose the apps you want to be per-installed, add some functions to it, mod bootscreens, pre-root it and eventually pack and flash the damn thing. While you are skipping the recovery procedure you are way safer than with its crap.
Agree with me?
daigtas said:
first of all you are not the only one that faces same problems. So chears mate. Next is the TWRP and the lack of stable/working version since i have done quite few phones now i can tell that the TWRP encryption ignore is not persistent and it works while you don't touch the recovery and not booting it up. Upon the boot it triggers the encryption and although he filesystem is not encrypted it still thinks it is.
Solution for now? wait for the fixed version while this is new phone and may take some time to re-code he recovery (find the damn cause of the encryption trigger).
Anyways. I am still thinking to do the fastboot rom mod, root it while it is not flashed and hen flash it while i don't actually need. I just need to remove all the miui/xiaomi stuff, block the damn ADS and root the phone and those things can be done on a pc i am just figuring out the correct way to do i.
The idea about skipping the TWRP came right after i downloaded mi-flash tool and found out that it uses same fastboot mode to flash everything and the file structure of the rom is not packet or something. Img files can be exacted and re-packed again so everything in the image can be modified.
What i really hate is the fact that there is tons of tools for other phones but somehow Xiaomi was skipped in the device selection...
Downloaded unlock tool, nice but limited to only requesting ad unlocking the phones bootloader. Next thing is the flash tool, it is limited to only flashing. There is xiaomi tool v2 that can also install the twrp, and cause the encryption crap or download and install stock or xiaomi.eu...
What i was looking for was the tool that can take the stock, decompress it and allow you to choose the apps you want to be per-installed, add some functions to it, mod bootscreens, pre-root it and eventually pack and flash the damn thing. While you are skipping the recovery procedure you are way safer than with its crap.
Agree with me?
Click to expand...
Click to collapse
More than one month, 280 view, 1 comment, no solution, no answer. Everyone out there are competing with each other to create their own ROMs/recovery/kernel images with whatever catchy names they can think of. Nice. But what's the point if the basics are not yet nailed down?
BTW, Telegram channel is flooded with non-contributing chit chat.
My casual observation is that lrtwrp seems to be a common theme for those who have had major issues on Joyeuse.
sir_bazz said:
My casual observation is that lrtwrp seems to be a common theme for those who have had major issues on Joyeuse.
Click to expand...
Click to collapse
For what it's worth, TWRP does not currently have any official builds for curtana OR joyeuse as far as I can tell. The flashing of early, unofficial, pre-alpha ports of TWRP directly onto partitions causing bricks is not that surprising. Xiaomi locking down EDL access is a ****ty move, but still.
Does anyone know if it is possible to get an android 10/11 GSI installed and working on this phone? I have tried numerous times, with GSIs found online, from the official site. Have checked to make sure I'm using one for the correct architecture. I've had varying results.
The different results I've had:
Stuck in bootloop. When in recovery, can't mount system partition.
Stuck on boot screen. Unrecoginized by PC. Can't mount System in Recovery.
Stuck on boot screen. Recognized by PC (makes ding). Can't access the phone. Can't mount System in recovery.
Stuck on boot screen. Unrecognized by PC. CAN mount System in recovery.
I have tried various methods, steps, and combinations of steps. Using TWRP and attempting to flash system with fastboot as well. When I was able to mount System after flashing the GSI, I also tried installing Magisk. It installed, but did not fix the problem. I can't remember everything I tried, but it was over the course of a few days, with multiple attempts per day. Around 5-10 each day. I can not figure out what I'm doing wrong, if it is even my error. It may just not be possible? Or may require steps that I have no knowledge of. If anyone has any advice, or knows if it's not possible with this phone, I would greatly appreciate it.
Edit: Also, I was using SP Flash Tool with the firmware from Cubot website to reinstall stock.
Elrandra said:
Does anyone know if it is possible to get an android 10/11 GSI installed and working on this phone? I have tried numerous times, with GSIs found online, from the official site. Have checked to make sure I'm using one for the correct architecture. I've had varying results.
The different results I've had:
Stuck in bootloop. When in recovery, can't mount system partition.
Stuck on boot screen. Unrecoginized by PC. Can't mount System in Recovery.
Stuck on boot screen. Recognized by PC (makes ding). Can't access the phone. Can't mount System in recovery.
Stuck on boot screen. Unrecognized by PC. CAN mount System in recovery.
I have tried various methods, steps, and combinations of steps. Using TWRP and attempting to flash system with fastboot as well. When I was able to mount System after flashing the GSI, I also tried installing Magisk. It installed, but did not fix the problem. I can't remember everything I tried, but it was over the course of a few days, with multiple attempts per day. Around 5-10 each day. I can not figure out what I'm doing wrong, if it is even my error. It may just not be possible? Or may require steps that I have no knowledge of. If anyone has any advice, or knows if it's not possible with this phone, I would greatly appreciate it.
Edit: Also, I was using SP Flash Tool with the firmware from Cubot website to reinstall stock.
Click to expand...
Click to collapse
TWRP 3.3.1 + Root CUBOT X19
[ROM][CUBOT X19][UNOFFICIAL] Havoc OS 3.11 [10.0][2020-11-30]
Wipe System, Data, Dalvik, Cache OR advanced Wipe without internal storage/micro sd card
Reboot TO TWRP
Wipe System, Data, Dalvik, Cache OR advanced Wipe without internal storage/micro sd card
Reboot TO TWRP
Flash the ROM
Willing to help if you still have an interest in the topic
same, doesnt work for me aswell
A GSI ROM can only get flashed if device supports TREBLE.
To check this you may use that app
Treble Check - Apps on Google Play
Check your device for Project Treble support and more
play.google.com
jwoegerbauer said:
A GSI ROM can only get flashed if device supports TREBLE.
To check this you may use that app
Treble Check - Apps on Google Play
Check your device for Project Treble support and more
play.google.com
Click to expand...
Click to collapse
yes it is treble supported
hi,
if i flash "Havoc-OS-v3.12-20201230-Official-arm64-ab.img" to my cubot x19 it runs fine without any problems.
however if i try to flash the images directly from google (either "https://ci.android.com/builds/branches/aosp-android10-gsi/grid?" or "https://developer.android.com/topic/generic-system-image/releases") the phone gets stuck after displaying the boot screen.
does anyone know how to solve this problem?
kind regards,
xt1622-blue27
xt1622-blue27 said:
hi,
if i flash "Havoc-OS-v3.12-20201230-Official-arm64-ab.img" to my cubot x19 it runs fine without any problems.
however if i try to flash the images directly from google (either "https://ci.android.com/builds/branches/aosp-android10-gsi/grid?" or "https://developer.android.com/topic/generic-system-image/releases") the phone gets stuck after displaying the boot screen.
does anyone know how to solve this problem?
kind regards,
xt1622-blue27
Click to expand...
Click to collapse
These are raw copies
If you want to try Android 11 : https://forum.xda-developers.com/t/...si-flashen-ohne-bootlop.4333513/post-85711061
Figured it out.
Dear all,
I am trying to replace the stock OS on my Lenovo tablet with some more open alternative, like LineageOS. I got as far as installing a modified version of TWRP on it and got root access.
I also found some unofficial gis LOS images but I couldn't install them via TWRP as the SYSTEM partition does not show up when I have to select which partition I want to install the image to. Mounting (ticking) the system partition in TWRP makes no difference. These are the partitions listed:
Boot
Vendor Image
Recovery
Modem (Image)
Persist (Image)
Splash
So I went ahead, and installed it from fastboot like this:
fastboot flash system image.img
Click to expand...
Click to collapse
The command succeeded, but when restarting, the device gets back to fastboot. I can boot into TWRP as well, but no matter what image I try to install, I get the same result.
I wonder what I am doing wrong... A few years back I have converted several phones to LOS and others with no problem. But I have no experience with gis. Maybe that's the problem.
Could someone more experienced help me? maybe I am trying the wrong gis images.
Thanks for any pointers in advance!