Related
I've lost the functionality of all my sensors (sensors like auto rotation,gyro,compass,acceleration,hall etc except proximity are not working) in my Redmi Note 4....
I've googled and found that :;
To bring back the sensors back alive , we should flash persist.img file of our specific device......
I've tried to install via fastboot but it is showing an error like this....
When I type :fastboot erase persist persist.img
Its showing:[remote:erase operation on partition persist is not allowed].......
But my bootloader is unlocked.......
Can't do anything with my phone......
Sensors without mobile is like a man without his ..............heart.....
Please share your help guys........
Try TWRP rom and check.
There is a way bring back all sensors alive but you need to sacrifice miui rom, but in custom rom all sensors works well. COLOROS ROM for RN4 sensor fix file can help you.
If you go back to miui, you will face "This device is associated with an existing Mi Account" problem. If you are OK with this, go ahead.
Try to use MiTool to flash fastboot rom
gaab1998 said:
Try to use MiTool to flash fastboot rom
Click to expand...
Click to collapse
I've done this 5 6 times, but nothing helps.
Tried to flash it via edl method (it well reparation n am sure it might fix it for sure, I'll tell you the exact method to put it on edl mode(works every time I tried)
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.
i downloaded the custom recovery for t20 (TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02) from gethub "i cant attach the link because of the forums rules"
then flashed it using fastboot , but then the tablet didn't boot into normal mode but i was getting the boot mode selection when i hold the (power + volume up) which gave me access to recovery mode and fastboot mode
the problem is that this custom recovery had issues with the touch screen and was basically not usable .
so i switched the phone into fastboot and i flashed the patched boot image that was working before but the tablet still didn't boot into normal mode , then i flashed the stock recovery image and now every thing gone .
the tablet has no options to boot into fastboot or recovery anymore.
basically the tablets boots and i get the teclast logo then the image of the broken android with a "no command" on screen and nothing else
i tried holding the volume up and plug in the usb-c cable but i got the same broken droid
holding volume up and power doesn't give the options for boot modes anymore
i would appreciate any help a this moment , thanks
hany20006 said:
i would appreciate any help a this moment , thanks
Click to expand...
Click to collapse
SP Flash tool should help you. Install stock firmware and everything should be restored, a device on MTK isn't so easy to kill. Just check the revision of your device (E1 or E2, on the back cover). I tried this TWRP and already spoke of that control it only with mouse (https://forum.xda-developers.com/showpost.php?p=78710093&postcount=5). I have my own version of the TWRP (3.2.2), there's also a problem with orientation of the screen. But PhilZ recovery works without problems, the management of keys.
ViAlexSt said:
SP Flash tool should help you. Install stock firmware and everything should be restored, a device on MTK isn't so easy to kill. Just check the revision of your device (E1 or E2, on the back cover). I tried this TWRP and already spoke of that control it only with mouse (https://forum.xda-developers.com/showpost.php?p=78710093&postcount=5). I have my own version of the TWRP (3.2.2), there's also a problem with orientation of the screen. But PhilZ recovery works without problems, the management of keys.
Click to expand...
Click to collapse
thanks for the reply my version is E2
i tried flashing the stock but i keep getting an error that the preloader file is not valid . can u upload yours so i can try with it
hany20006 said:
my version is E2
Click to expand...
Click to collapse
Here's firmware T20 (T2E2)-Android7.1.1_V1.02_8F48 specifically for revision E2: Chinese storage or my Y.Disk
If stock firmware doesn't help you, here's my read preload-partition, I have E2 (I hope you know how to restore it in SP Flash Tool using Write Memory option).
Partition address and size:
Code:
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
ViAlexSt said:
Here's firmware T20 (T2E2)-Android7.1.1_V1.02_8F48 specifically for revision E2:
If stock firmware doesn't help you, here's my read preload-partition, I have E2 (I hope you know how to restore it in SP Flash Tool using Write Memory option).
Partition address and size:
Code:
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
Click to expand...
Click to collapse
thank you very much for providing the y.disk link , i spent the whole yesterday searching for a way to download from baidu without luck.
i managed to flash the stock software (using format all +download) and it worked and now the tablet is up and running (unfortunately its chines ) i changed the language but there is bits here and there with chines still i cant complain.
there is no recovery image with this tablet , do u think i should flash the twrp recovery even if it has touch issues.
i cant thank u enough for your help
have a nice day
hany20006 said:
do u think i should flash the twrp recovery even if it has touch issues
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/showpost.php?p=78758523&postcount=7
ViAlexSt said:
See here: https://forum.xda-developers.com/showpost.php?p=78758523&postcount=7
Click to expand...
Click to collapse
yeah i just rooted the device and then flashed the recovery using the Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek (TWRP 3.2.1-0)
the touch screen is till having issues , but i guess i have to use mouse as you said
Hey guys, have either of you had trouble using the flash tool to flash the patched boot image from Magisk? it will not flash no matter what I do. I just get a red bar .... THanks
Draiter said:
Hey guys, have either of you had trouble using the flash tool to flash the patched boot image from Magisk? it will not flash no matter what I do. I just get a red bar .... THanks
Click to expand...
Click to collapse
Those are the notes i made for my self regarding your issue:
at the end we may get an error when flashing the patched-boot.img using sp flash tool
so we need to use fastboot instead
first we need to install ADB and fastboot in the PC (follow link bellow):
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
then power off the device then (hold the volume up+ power ) to enter the BOOT mode (the usb must be disconnected)
then select the fastboot from the menu
then we can use the commands :
#fastboot flash boot c:/patched_boot.img --> make sure the image is in the C folder
if this failed we need to unlock the OEM
#fastboot oem unlock -- > then confirm from the tablet
then try again
#fastboot flash boot C:/patched_boot.img
and when its done we can issue the command for restarting tablet
#fastboot reboot
hany20006 said:
Those are the notes i made for my self regarding your issue:
at the end we may get an error when flashing the patched-boot.img using sp flash tool
so we need to use fastboot instead
first we need to install ADB and fastboot in the PC (follow link bellow):
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
then power off the device then (hold the volume up+ power ) to enter the BOOT mode (the usb must be disconnected)
then select the fastboot from the menu
then we can use the commands :
#fastboot flash boot c:/patched_boot.img --> make sure the image is in the C folder
if this failed we need to unlock the OEM
#fastboot oem unlock -- > then confirm from the tablet
then try again
#fastboot flash boot C:/patched_boot.img
and when its done we can issue the command for restarting tablet
#fastboot reboot
Click to expand...
Click to collapse
Hey thanks for the quick reply, I will give it a go
Sent from my SM-G935F using Tapatalk
Got the boot.img flashed and recovery flashed (Phil's), but cannot do a full backup in recovery, cannot Mount data.
Have you been able to do a full backup?
Sent from my SM-G935F using Tapatalk
Draiter said:
cannot Mount data
Click to expand...
Click to collapse
Standard phenomenon for Nougat/Oreo: to mount a partition /date, must first format it. With loss of user data!
Some TWRP editions don't require this, /data mounted.
Hello.
Thanks ViAlexSt for the help, but I´m still having problems with root
, I try with (MTK) Auto TWRP recovery porter and with MTK Auto Philz recovery porter, with success only with TWRP.
Wiith Philz only get into recovery, when go to the OS the screen freeze with Teclast Logo in red.
With TRWP have an error, not able to mound device.
Is no possible install zip or create a backup.
Any idea??
I have a T20 T2E1
Thanks
I format with SPFlashtool with format+flash option, but not work, no backup, no any wipe.
Still with message Unable to mount parition.
I will try with an older version OF TWRP.
Some screenshots.
Thanks
https://photos.app.goo.gl/qwmLqnhxVk8vRmWA8
https://photos.app.goo.gl/VP5vJCDC7HaDpgaB8
AWLanzarote said:
Still with message Unable to mount parition.
Click to expand...
Click to collapse
Did you manage to do it? It's necessary to format the partition from CWM/TWRP!
Do you need additional explanations?
ViAlexSt said:
Did you manage to do it? It's necessary to format the partition from CWM/TWRP!
Do you need additional explanations?
Click to expand...
Click to collapse
Thank you very much for yor reply.
Yes I try formating with twrp but the same problem, at the end I take the risk and use a downloanble image "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02". The one generated with the porter doesn´t work for my Teclast T20 (T2E1).
With this one "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02.img works at the first".
And after that I was able to install "Magisk-v18.0.zip" and "no-verity-opt-encrypt-6.0.zip".
And finally I get root access, but after a wile I see the propblem with the IMEI wich was Inavild, after try with many options like generate the file MP0B_001, use Uncletools, droid tools, and many other Apps.
Finally today... I found a solution in a Spanisf Forum Dual Sim, Thanks to user "pedrogem" the most easy way to set an IMEI.
https://play.google.com/store/apps/details?id=com.rungetel.ghostphone&showAllReviews=true
Many Thanks..
AWLanzarote said:
Thank you very much for yor reply.
Yes I try formating with twrp but the same problem, at the end I take the risk and use a downloanble image "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02". The one generated with the porter doesn´t work for my Teclast T20 (T2E1).
With this one "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02.img works at the first".
And after that I was able to install "Magisk-v18.0.zip" and "no-verity-opt-encrypt-6.0.zip".
And finally I get root access, but after a wile I see the propblem with the IMEI wich was Inavild, after try with many options like generate the file MP0B_001, use Uncletools, droid tools, and many other Apps.
Finally today... I found a solution in a Spanisf Forum Dual Sim, Thanks to user "pedrogem" the most easy way to set an IMEI.
https://play.google.com/store/apps/details?id=com.rungetel.ghostphone&showAllReviews=true
Many Thanks..
Click to expand...
Click to collapse
Are you able to make a T20 root step by step guide with all the necessary download's (patched boot.img included) ?
would be very appreciate.
regards
toxstoxs said:
Are you able to make a T20 root step by step guide with all the necessary download's (patched boot.img included) ?
would be very appreciate.
regards
Click to expand...
Click to collapse
Hi toxstoxs.
Is already done in this link with all the downloads https://romprovider.com/2019/01/teclast-t20-root-twrp/.
I follow these steps exept the use of adb. In stead, I used SP Flash Tool, the utility included in the the original ROM which you can download from the official Teclast website.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
With SP flash tools, upload the recovry.img "the downloaded TWRP from the link above" and your boot.img "patched on your device with magisk manager from you original"
I use the boot image from the original rom downloaded from Teclast, which I flash previously.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
Just take in mind... touch screeen is not working well in TWRP you should use a mouse, the touch screen is in portrait possition but wou will see the screen in landscape, I do it without a mouse but is not easy, if you can get a mouse will be bether.
Regards.
AWLanzarote said:
Hi toxstoxs.
Is already done in this link with all the downloads https://romprovider.com/2019/01/teclast-t20-root-twrp/.
I follow these steps exept the use of adb. In stead, I used SP Flash Tool, the utility included in the the original ROM which you can download from the official Teclast website.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
With SP flash tools, upload the recovry.img "the downloaded TWRP from the link above" and your boot.img "patched on your device with magisk manager from you original"
I use the boot image from the original rom downloaded from Teclast, which I flash previously.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
Just take in mind... touch screeen is not working well in TWRP you should use a mouse, the touch screen is in portrait possition but wou will see the screen in landscape, I do it without a mouse but is not easy, if you can get a mouse will be bether.
Regards.
Click to expand...
Click to collapse
I went troght that step by step guide but :
1) into Pre requirement steps, i made a NVRAM backup with SP Tool.
step 2 is not so interesting to me as the tablet is new so no personal data are saved.
point 3 : How suppose to make a nandroid backup if no TWRP is intalled???
then.. i suppose that it mean to INSTALL a TWRP and just after make a nandroid backup right?
but...
just after ulock the bootloader and reaching step by step the point 7 and 8 of the guide,
after the command "fastboot boot recovery.img" the device reboot and go in permanent loop.
No way to access the recovery.
is there something that i may check? just once i been able to enter the twrp and the main problem were the impossibilty to access and format the /data partition so, no factory reset were possible and obviously no bbot as well (permanent boot loop).
Im not use adb tools, im only use sp fash tool.
I do it like this.
1 flash the downloaded Rom from Teclast with SP flash tool, to get all fresh.
2 Enable usb debug and oem unlock
3 copy in your device the stock boot.img from the folder firmware from the zip downloaded from Teclast,
4 in your device install the app Majisk manager and use it to patch your original boot.img
5 copy into sd the files magisk.zip, No verity opt encrypt.zip,
6 with sp flash tool flash the patched boot.img and the downloaded TWRP-3.2.3-TwrpBuilder-2019-01-18_20-02"]twrp renamed to recovery.img ”this was the only one trwp which works on my T20”https://github.com/TwrpBuilderTests/android_device_teclast_t20/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-02
7 reboot in recovery with TWRP and install magisk.zip and no verity opt encrypt.zip
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 am having an odd issue... In my Nord 2 the motherboard has been recplaced by OP since I had several issues including a batterydrain that would drain 60% in 8 hours standby without sims and wifi disconnected. Flashing stock (at OnePlus-servicepoint SOMETIMES fixed that - they reflashed stock 4 or 5 times).
Anyway. New motherboard placed at the servicepoint. Stock rom. TWRP, rooted, Magisk 23.0. Nothing else. Freezed some Google-apps with Titanium but nothing else. Google account installed and downloaded just 3 or 4 apps (App Ops, Titanium, Mega und Solid Explorer).
I CAN set-up a PIN-code/PIN-lock for the device (works), but once I want to set a fingerprint the device starts vibrating like hell and it gives an error. Nothing was done since the last return to OnePlus where fingerprint worked. I have the official screenprotector (from OnePlus store, which was on before and it worked perfectly) but nothing else. No case whatsoever.
I am getting so sick of this device. Nothing but trouble, trouble, trouble. Anyone with suggestions? Bwoagh I'd hate to start setting things up over and over again and again and again without knowing the cause. Every time other errors appear. Blegh!
To make sure: TWRP is working correctly and also bootloader works fine!!!
Check your camera to see if it works; If both the camera and fingerprint don't work, that's a symptom the persist partition is corrupted.
The persist partition contains sensor calibration data for the OPN2, and is calibrated and unique to each and every device.
TWRP is known to corrupt the persist image when you try to restore to an TWRP backup; This is a fault with the TWRP software, not the phone.
The fix is to simply use fastboot to flash the persist image manually for a fix; If you have a TWRP backup, locate your "persist_image.emmc.win" file, then boot into fastboot, and use the command "FASTBOOT flash persist persist_image.emmc.win" from your powershell aka usually the same as your ADB terminal
In future, avoid restoring the persist partition using TWRP to avoid the same issue.
Zombnombs said:
TWRP is known to corrupt the persist image when you try to restore to an TWRP backup; This is a fault with the TWRP software, not the phone.
The fix is to simply use fastboot to flash the persist image manually for a fix; If you have a TWRP backup, locate your "persist_image.emmc.win" file, then boot into fastboot, and use the command "FASTBOOT flash persist persist_image.emmc.win" from your powershell aka usually the same as your ADB terminal
In future, avoid restoring the persist partition using TWRP to avoid the same issue.
Click to expand...
Click to collapse
@Zombnombs: first of all, thank you for your reply, this is crucial information. Nevertheless, this SHOULD not be for my device.
Than my device was factory re-flashed in a OnePlus-service-point. Then I updated via OTA, after that installed TWRP but did NOT mess in TWRP, just rooted by flashing Magisk and then I tried to set up the fingerprint... which doesn't work.
What I DID notice so far, is that when a OnePlus Servicepoint flashes back stockrom (with a specific Programm that do not give us), it sometimes leaves recidu of former "****" on the phone. Since I had 5 or 6 factory flashes in 2 months I know what I am talking about. The ROM is factory resetted but last time a TWRP folder SURVIVED for whatever reason even the servicepoint can't explain.
My phone WAS totally corrupted BEFORE the last factory flash, and I ASSUME something "from the past" causes this. Bottomline: set up the phone 4 times already (cost me a day) and it's still not working as it should. Yes. I am close to selling, although I actually like the device.