I have a bricked Hisense A5 (Qualcomm, China) device which stays in a bootloop and I don't know how I can unbrick it.
Facts are:
Device: Hisense A5 (HLTE202N)
Firmware: Stock L1657 6.03.02.00 / Kernel 4.9.112
- I could flash in edl mode successful a stock firmware, but nothing changed after a reboot
- Device stays with "Hisense and powered by Android screen".
- The bootloader can't be unlocked
- teardown device and disabled battery for some minutes and tried to charge it with a wall charger -> bootloop
What I can (like before flashing in edl-mode):
- Entering edl-mode with a xiaomi edl-cable (Qualcomm HS-USB 9008er mode and diagnostic mode 900E after flashing)
- entering fastboot (pressing volume up while rebooting and connecting pc)
What I can't:
-flashing TF-Mode (Firmware on microSD)
-rebooting to system
-shutdown
-recharging wall charger (bootloop)
-not detected as usb-drive for filetransfer
This bootloop mode you can read quite often. The Xiaomi guys can fix this by flashing a fastboot Firmware, but they have an unlocked bootloader
Anybody knows a solution or what I can try to fix this?
Solved:
https://forum.xda-developers.com/showpost.php?p=82726877&postcount=7
JLowe said:
I have a bricked Hisense A5 (Qualcomm, China) device which stays in a bootloop and I don't know how I can unbrick it.
Facts are:
Device: Hisense A5 (HLTE202N)
Firmware: Stock L1657 6.03.02.00 / Kernel 4.9.112
[...]
Anybody knows a solution or what I can try to fix this?
Click to expand...
Click to collapse
Have you already considered trying to use the 6.09.06.00 ROM available via forum.xda-developers.com/showpost.php?p=82583733&postcount=28 ?
defylogic said:
Have you already considered trying to use the 6.09.06.00 ROM available via forum.xda-developers.com/showpost.php?p=82583733&postcount=28 ?
Click to expand...
Click to collapse
Yes, sorry forgot that to mentioned. Good point. That was the first I tried with some other guys in the thread but it doesn't work at all. Tried different microSD and formatting.
Well if the TF Mode not working with 6.0.9 and you have 6.0.3 which is already rooted logic say to try not with 6.0.9 but with 6.0.4 update or better with 6.0.3 but original i.e not rooted. I think something in 6.0.3 is not compatiblle with something in 6.0.9. Simply as that. I remember I say guy in thread for Hisense A5 root which had all update files and WeChat group?
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
gowin132 said:
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
Click to expand...
Click to collapse
Do you have the same files of 6.09.06 version? If yes, please share. I have same problem but my phone has latest OS version.
gowin132 said:
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
Click to expand...
Click to collapse
Great, these files are working flawless in qfil. Could recover the system and then update in Tf-Mode to actual 6.09
These are the original boot, recovery and vbmeta image from 6.09.06.
https://drive.google.com/file/d/1JeUEaBxpH5zu22v-6V_6LAqZzGuXmUhf/view?usp=sharing
Mehedi34 said:
Do you have the same files of 6.09.06 version? If yes, please share. I have same problem but my phone has latest OS version.
Click to expand...
Click to collapse
Do you guys have full firmware with system and other imgs?? Mine seems to still bricked
lillo9546 said:
Do you guys have full firmware with system and other imgs?? Mine seems to still bricked
Click to expand...
Click to collapse
I'm sorry for asking what is probably a silly question, but how exactly do you flash files like boot.img using Qfil ?
I can get into fastboot., but not edl mode.
I know old thread, but am having problems with a bricked A5. After a lot of trial and error, it sometimes gets into Fastboot mode. I can then ask for fastboot device and it responds with a hex number and fastboot.
When I try to flashall new partitions, it fails with:
fastboot: error: ANDROID_PRODUCT_OUT not set or non allowed.
Once I could flash individual partition with:
fastboot flash boot boot_recovery_vbmeta_6.03.02/boot.img
Sending 'boot' (65536 KB) OKAY [ 2.113s]
Writing 'boot'
But then it just sits there and nothing seems to happen.
Anyone has suggestions on what to try, am running out of ideas
.
It would be amazing if anyone could share:
- Stock ROM 6.12 full QFIL backup.
- EFS/QCN backup files.
Thanks
JLowe said:
Great, these files are working flawless in qfil. Could recover the system and then update in Tf-Mode to actual 6.09
Click to expand...
Click to collapse
Hi. I have the same problem as you, but I don't know how to flash those files with qfil. Can you please explain it to me?
Related
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Arseon said:
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Click to expand...
Click to collapse
Go to TWRP and restore your system backup.
kilroystyx said:
Go to TWRP and restore your system backup.
Click to expand...
Click to collapse
But I didn't install a custom recovery. So no TWRP
Arseon said:
But I didn't install a custom recovery. So no TWRP
Click to expand...
Click to collapse
So, then try flash same system partition via fastboot.
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
What your build ?
If this phone with OREO or with NOUGAT / Android 8.x or 7.x ?
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Arseon said:
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Click to expand...
Click to collapse
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
kilroystyx said:
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
Click to expand...
Click to collapse
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Arseon said:
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Click to expand...
Click to collapse
It seems like you are doing well, but have you read the instructions carefully? They recommend when something fail.
https://www.dc-unlocker.com/huawei-phone-flashing-in-fastboot
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
AND very important : do not relock the bootloader !
ONLY if bootloader 'unlockt' you can self-repair !
JamesBott said:
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
Click to expand...
Click to collapse
Mine is ANE-AL00 8.0.0.131(C675). I used ANE-AL00C00B131 (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2370/g1789/v138744/f1/full/filelist.xml ) to flash
JamesBott said:
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
Click to expand...
Click to collapse
Sadly no. Both bootloader and frp are locked.
JamesBott said:
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
Click to expand...
Click to collapse
Since bootloader and frp locked, adb commands are not working. Hence I'm using DCPheonix to flash the file. But without luck. It's still botting to eRecovery only
your phone is C675, you flash C00 : no correct
now is inside your phone a 'mix'
i think, you can no self-repair - sorry
@Arseon, my opinion your system partition is a mess due to xposed installation fail.
The solution for this case is restore system partition, it worked for me in the past.
In some cases we can get lucky install a clean system partition even if it is from other region code, because the main differences between regions are located in the other partitions
But what I learning is that system from C00 region don’t follow this standard because at least is missing google apps.
With DCPheonix did with get lucky and flash all files or just the first 4 and stop in the PACKAGE_TYPE?
same situation
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Edit: I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
alvavaca said:
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Click to expand...
Click to collapse
This thread can help you a lot => HuRUpdater
kilroystyx said:
This thread can help you a lot => HuRUpdater
Click to expand...
Click to collapse
Thks for your help, I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Arseon said:
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
Click to expand...
Click to collapse
In pretty sure you are flashing the wrong firmware, try to push your version with dc-unlocker in fastboot and download the excatly matching firmware. Good luck
well, i have all of this+one more tougher stuff..
Well, I tried to install a custom ROM on my P20 Lite (ane-lx1) via TWRP aand when I failed I ended up into a bootloop, but the thing that got me a headache after a full day of forum research is that when I attempted to install the custom ROM the TWRP wanted a .img file, not a .zip file, so I rebooted after I alreday wiped out everything, I made a backup into the phone, BUT I cant access it because.. the TWRP freezes every time at the TeamWin logo.....the only thing that is accessible now its the fastboot&rescue mode and I'm out of juice and desperated...the bootloader is enabled...i think i preety much killed my phoen and my brain trying to get an android stock experience...i really have to get some sleep,well..thank you for your attention, if you have any suggestions that would pick me up from this mess I would be very greatfull, i'll see what i had left to do as soon as i'm able to...for now, have a good night/day/afternoon, whatever side of the world you're from
Edit:
I left the phone all night into bootloobing and after it got FULLY discharged, I dont know exactly how but the TWRP hasn't popped out, instead after this I was able to get into eRecovery and now it is downloading the 146(C432) version. I guess that I got lucky
Hi! I was trying to root Nokia 1
I flash TWRP through fastboot and it worked! But the problem was I was unable to see my files there.I think because of encryption..
So, I accidentally factory reset my phone through TWRP and then, I was unable to boot into system again..
I was stuck in TWRP
So, I go to fastboot and flash stock_recovery.IMG and after that when I reboot. I am seeing a black screen. I can feel vibration when press home key or home + volume up/down. but screen is black
Please help...
abdul_manan said:
Hi! I was trying to root Nokia 1
I flash TWRP through fastboot and it worked! But the problem was I was unable to see my files there.I think because of encryption..
So, I accidentally factory reset my phone through TWRP and then, I was unable to boot into system again..
I was stuck in TWRP
So, I go to fastboot and flash stock_recovery.IMG and after that when I reboot. I am seeing a black screen. I can feel vibration when press home key or home + volume up/down. but screen is black
Please help...
Click to expand...
Click to collapse
Use micro SD card for twrp. You can't remove encryption just by factory reset. I know how to remove encryption on Nougat but that method doesn't work on Oreo. When you flashed TWRP flash SuperSU (not Magisk) then boot to system, after that boot to twrp recovery again and wipe factory reset and wipe internal storage. You have removed encryption. SuperSU needs to be updated to patch plat and non play file contexts to remove encryption on Oreo. Or someone can make flashable zip to remove encryption.
First find nb0 file for Nokia 1 and try to flash rom with OST.
SkaboXD said:
Use micro SD card for twrp. You can't remove encryption just by factory reset. I know how to remove encryption on Nougat but that method doesn't work on Oreo. When you flashed TWRP flash SuperSU (not Magisk) then boot to system, after that boot to twrp recovery again and wipe factory reset and wipe internal storage. You have removed encryption. SuperSU needs to be updated to patch plat and non play file contexts to remove encryption on Oreo. Or someone can make flashable zip to remove encryption.
First find nb0 file for Nokia 1 and try to flash rom with OST.
Click to expand...
Click to collapse
Thanks for the reply!
Can you please tell me where can I find the nb0 file of Nokia 1 with Android 8.1 Oreo Go edition TA-1047?
abdul_manan said:
Thanks for the reply!
Can you please tell me where can I find the nb0 file of Nokia 1 with Android 8.1 Oreo Go edition TA-1047?
Click to expand...
Click to collapse
currently it's not available, you need to wait someone to upload it.
Nokia1 uses MTK CPU right? If you can get the ota zip of the current update on your phone, you can extract the boot.img file then boot into download mode and type fast boot flash boot <boot.img file>
redweaver said:
Nokia1 uses MTK CPU right? If you can get the ota zip of the current update on your phone, you can extract the boot.img file then boot into download mode and type fast boot flash boot <boot.img file>
Click to expand...
Click to collapse
Can you please explain a little bit more!
How to get ota zip file? (My phone is not working as mentioned above)
Where can I get boot.img?
How to extract and where boot.img?
How to boot into download mode?
abdul_manan said:
Hi! I was trying to root Nokia 1
I flash TWRP through fastboot and it worked! But the problem was I was unable to see my files there.I think because of encryption..
So, I accidentally factory reset my phone through TWRP and then, I was unable to boot into system again..
I was stuck in TWRP
So, I go to fastboot and flash stock_recovery.IMG and after that when I reboot. I am seeing a black screen. I can feel vibration when press home key or home + volume up/down. but screen is black
Please help...
Click to expand...
Click to collapse
I'm having a kind of similar issue. I flashed twrp and now its stuck in a twrp loop. It boots only in twrp and not system. What should I do?
Ludba Amb said:
Can you please explain a little bit more!
How to get ota zip file? (My phone is not working as mentioned above)
Where can I get boot.img?
How to extract and where boot.img?
How to boot into download mode?
Click to expand...
Click to collapse
http://www.mediafire.com/file/0xgn9o0b711wcw0/Nokia_1_TA-1047_MT6735_V8.1.0_180401.zip
Stock Rom for 1047
Download it.
Extract boot.img from that
boot into download mode/recovery
adb reboot recovery
answers to all your questions.... not the answer to fix your problem I think... But have a go.
And last but not least... Please use the search option first or google instead of asking all questions at once.
Or try to get familiar with rooting first...…
good luck buddy.
hello everyone i have nokia 1 oreo go edition i don't have any idea how to root
please help me by sending links for :
1 ) nokia 1 (ta-1047 ) TWRP
2 ) nokia 1 custom rom
3 ) nokia 1 current rom (for security)
(remenber thats only model ta-1047)
seriously i want to root it because there are many issues like multitouch screen problem or missing some system apps and also device getting hot because the memory (ram) is lagging (1gb ram is not enough to run android oreo correctly 2018 )
{PLEASE HELP}
help me please !
can you send me a twrp for nokia 1 ta-1047
i need to root my device to dowoad custom rom
MyTH30 said:
I'm having a kind of similar issue. I flashed twrp and now its stuck in a twrp loop. It boots only in twrp and not system. What should I do?
Click to expand...
Click to collapse
Same here. Seems that the decryption does not work. Better make sure your phone is not encrypted before messing with twrp (3.2.3).
Be careful
Some Nokia 1 are a TA 1060 variant number and if you flash the wrong file you are going to have further problems.
The process to root and get TWRP on the nokias Is complicated enough without everyone suggesting wrong model variants / numbers.
I guarantee someone will download the wrong file for the wrong model and come here crying.
is this the real firmware?
inkepinkje said:
http://www.mediafire.com/file/0xgn9o0b711wcw0/Nokia_1_TA-1047_MT6735_V8.1.0_180401.zip
Stock Rom for 1047
Download it.
Extract boot.img from that
boot into download mode/recovery
adb reboot recovery
answers to all your questions.... not the answer to fix your problem I think... But have a go.
And last but not least... Please use the search option first or google instead of asking all questions at once.
Or try to get familiar with rooting first...…
good luck buddy.
Click to expand...
Click to collapse
hi, i needed to know if this is the real one, they show it's mt6735 instead mt6737m, I've already downloaded a file with the similar name nd it has scatter file of mt6735, that's while in the sp flash tool,i don't see all of the partitions being detected to flash
Hey i am facing the same issue but i didn't flash any other recovery mode my phone Nokia 1 TA-1056 am getting black screen and only feel the vibration when i press power key and when i put my phone on charging then its shows the display and boot into recovery mode directly can anyone help me how i can overcome this issue
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
Long story short, I accidentally formatted everything while trying to flash Stock ROM using SP Flash Tool.
Now I'm having the "Download not completed" error at boot.
I tried solving it by flashing oppo_cutsom which didn't do any good, and after I took it to repairs, they told me I need the original NVRAM & NVDATA
which I can't find anywhere online (at least, not for free -_-).
Can someone please share their Narzo 30A's NVRAM & NVDATA with me?
Thanks in advance
@RealmeNarzo30AUpdates Do a search on Telegram and you will find what you want only for realme Narjo 30a:
Shubham 786 said:
@RealmeNarzo30AUpdates Do a search on Telegram and you will find what you want only for realme Narjo 30a:
Click to expand...
Click to collapse
Thanks, I'll check it out
mouradsme said:
Long story short, I accidentally formatted everything while trying to flash Stock ROM using SP Flash Tool.
Now I'm having the "Download not completed" error at boot.
I tried solving it by flashing oppo_cutsom which didn't do any good, and after I took it to repairs, they told me I need the original NVRAM & NVDATA
which I can't find anywhere online (at least, not for free -_-).
Can someone please share their Narzo 30A's NVRAM & NVDATA with me?
Thanks in advance
Click to expand...
Click to collapse
You can't rip bro
If you done anyhow your imei will be still gone
iamshubh69 said:
You can't rip bro
If you done anyhow your imei will be still gone
Click to expand...
Click to collapse
I managed to get the "Download not completed" fixed, but now I'm in a different kind of bootloop, and I think I need a "verified" version of recovery.img...Where can I find it?
mouradsme said:
I managed to get the "Download not completed" fixed, but now I'm in a different kind of bootloop, and I think I need a "verified" version of recovery.img...Where can I find it?
Click to expand...
Click to collapse
Ask someone on narzo 30a telegram group for stock recovery img it might work
iamshubh69 said:
Ask someone on narzo 30a telegram group for stock recovery img it might work
Click to expand...
Click to collapse
I already did
thank you for taking the time on this
iamshubh69 said:
Ask someone on narzo 30a telegram group for stock recovery img it might work
Click to expand...
Click to collapse
I just managed to install PBRP recovery onto my device, and I accessed it then went straight to Fastboot option (I wanted to flash the stock ROM using realme flash tool), but my PC couldn't detect the device (not Fastboot, nor ADB) although it detects other android phones.
Anyways, since that didn't work - I tried installing PixelExperience (It worked before on my phone, so I thought it would work again but after rebooting the phone didn't even boot).
I then flashed the original dtbo.img, but there's no system,, only the recovery.
Any idea how to fix this?
mouradsme said:
I just managed to install PBRP recovery onto my device, and I accessed it then went straight to Fastboot option (I wanted to flash the stock ROM using realme flash tool), but my PC couldn't detect the device (not Fastboot, nor ADB) although it detects other android phones.
Anyways, since that didn't work - I tried installing PixelExperience (It worked before on my phone, so I thought it would work again but after rebooting the phone didn't even boot).
I then flashed the original dtbo.img, but there's no system,, only the recovery.
Any idea how to fix this?
Click to expand...
Click to collapse
Can you send fast boot mode pic to me it might help
First of all, thanks for guiding me to that group on Telegram (I found the stock recovery there, and I could flash the .ozip thanks to it) but I only managed to make it boot to the yellow RealMe logo, and now it stays there until it reboots on its own. What could I have done wrong? (I did wipe data/reset everything before starting to flash the ROM).
mouradsme said:
First of all, thanks for guiding me to that group on Telegram (I found the stock recovery there, and I could flash the .ozip thanks to it) but I only managed to make it boot to the yellow RealMe logo, and now it stays there until it reboots on its own. What could I have done wrong? (I did wipe data/reset everything before starting to flash the ROM).
Click to expand...
Click to collapse
Try fastboot -w in fastboot mode seems like encryption issue
iamshubh69 said:
Try fastboot -w in fastboot mode seems like encryption issue
Click to expand...
Click to collapse
I have no access to fastboot,
can I use Mtkclient and erase usedata instead?
Edit:
I noticed that after flashing PBRP recovery, and choosing the fastboot option, the devices is detected in fastboot mode (via command "fastboot devices") for like 2 seconds, then it loses connection. Any idea why?
Okay I just revived the phone,
What I was missing for it to boot was the original oppo_custom image,
For those who haven't got a backup, here's the one I used to restore my phone:
Realme_Narzo_30A_oppo_custom.rar
drive.google.com