hello guys, I'm new in the forum, I have a mobile lower-middle-bought band, his name is Master "smartphone 504-4g", owns the mediatek mt6735 cpu 1 GHz, has 1 GB of RAM, Android 5.1, and 4 GB of rOM.
I tried to extract the rom with MTK droid v2.5.3d tool, but at the end of extraction known that there is only the folder / system saved in the PC, and the program has reported to me the error "No space left on device "thing I was aware through consultation of guides on the internet.
now that I broke the phone after trying to install Xposed (bootloop), how can I enclose all the files in the folder / system I have in the PC, in an IMG to flash file with sp flash tool?
Thanks for help
There are ways to uninstall xPosed Framework if you can get into Recovery:
http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
Check Needrom.com for your specific device ROM, if it is a common device, or even uncommon, there may be a ROM there. I've also backed up using that tool, and left with unusable files. If you know your device info, Kernel and Fingerprint, use that info when searching Needrom, usually it's listed with the available ROMs.
This came up in a search, I don't know if it is your device:
http://iris504qdevelopment.blogspot.com/
X-weApon-X said:
There are ways to uninstall xPosed Framework if you can get into Recovery:
http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
Check Needrom.com for your specific device ROM, if it is a common device, or even uncommon, there may be a ROM there. I've also backed up using that tool, and left with unusable files. If you know your device info, Kernel and Fingerprint, use that info when searching Needrom, usually it's listed with the available ROMs.
This came up in a search, I don't know if it is your device:
http://iris504qdevelopment.blogspot.com/
Click to expand...
Click to collapse
hello, thanks for answering.
I searched in needrom.com for the Rom, inputting the fingerprint, the kernel etc. but could not find anything.
the phone of which you wrote me the link is not what I have.
This is the fingerprint:
Code:
alps/full_x5_g518ql/x5_g518ql:5.1/LMY47D/1456459901:user/test-keys
This is the kernel:
Code:
3.10.65 ([email protected]) (gcc version 4.9.x-google 20140827 (mtk-20150409) (GCC) ) #1 SMP Fri Feb 26 12:20:51 CST 2016
and this is the version of the baseband:
Code:
MOLY.LR9.W1444.MD.LWTG.MP.V42.P7
LMY47D seems to be the version of Lollipop
https://www.google.com/search?q=LMY47D/1456459901&ie=utf-8&oe=utf-8#safe=off&q=LMY47D
Using only that at Needrom, I found only this:
http://www.needrom.com/download/real-android-5-1/
Sorry, usually searching the fingerprint brings up SOMEthing useful. but in this case, there are absolutely no results.
I found references to the Kernel too, but nothing useful.
ok , I had also tried on google but to no avail .
how can I do then to put it back ?
I considered the idea to buy some one the same , but I do not know other ways to extract the ROM and then perform the flash procedure on the broken device .
What do you advise me to do?
Are there any tutorials on this site about using MTK droid tools? Its not just about backing up the system.IMG file, there should be a boot.IMG and a recovery.IMG, and then you have to create Scatter files. But I don't know what I'm supposed to do. I've used other tools, it seems that all it gave me was a system.IMG. its highly likely that this file contains everything, but it appears that there is an extra step that we don't know about.
Your device may simply be uncommon, especially with the lack of usable info available for it. I've looked up fingerprints before and there is usually some info. Which was why i suggested it.
Give me a few days to research this issue. Also, have you tried device Safe Mode? Reboot, hold both volume up+down as it starts, see if you can get it to boot. If it does, remove xPosed.
Also, do you have any recovery that works? Because you can send the xPosed removal zip through ADB and it will remove xposed. Check my first link.
Sent from my 6S Plus using XDA-Developers mobile app
---------- Post added at 06:57 PM ---------- Previous post was at 06:51 PM ----------
I was trying to replace Kingroot with SuperSU late last night and my device was stuck at the boot screen. But I was able to ADB into the device and run a shell and look around, you might be able to copy the Xposed removal tool that way and then run it
Sent from my 6S Plus using XDA-Developers mobile app
I forgot one detail that I have not written in my previous posts. besides the problem of Xposed I made bull**** to install a rom that I thought was compatible with this device, and the ROM is that of Doogee X5 Pro, which is very similar in characteristics to the my device. only after doing the flash with sp flash tool, the phone will not turn on anymore. Now It is only detectable by usb connection without battery and pressing the volume up button. I apologize if I have not written before.
the recovery of my phone I remember is that stock, and I replaced it with the ever TWRP of Doogee x5 pro, but it did not work.
You bricked it. Time for a new device.
it is very unrecoverable @zelendel?
gae1991 said:
it is very unrecoverable @zelendel?
Click to expand...
Click to collapse
Yes it is dead. You messed up flashing something for another device.
I saw on the internet that there is a box to be able to flash the ROM even if the phone is dead. This box is called MTK-box. I have already had experience in the past with the atf-box for Nokia, you say that might work?
I've used ROM's for wrong device on an MT6582 device I had, effectively bricking it. But I was able to find the correct ROM and flash with that, presto, fixed. The problem here, is that we can't FIND the correct ROM.
I highly suggest contacting the seller, was it DHgate? Try to find out. I bought a brand new iPhone 6S+ 1:1 clone from a seller named iBaby888, and I bricked the device while trying to use SuperSU Me. I contacted iBaby and she pointed me to the correct ROM which fortunately had JUST been posted at Needrom by [email protected] I even Bricked it again 2 nights ago, using Vicki Bonick's KR2SU script. Boom, flashed again.
Any device can be reverted to stock I believe, it's just a matter of having the right ROM. Now in the case of using MTK Droid Tools, I think you missed a step:
http://forum.xda-developers.com/showthread.php?t=2730031
5. Start MTK Droid Tools, and connect your phone with the USB cable to the PC. (if Windows install some drivers, then let it install them automatically).
6. Now on the first page of MTK Droid Tools, it should display all infos about the phone when you connect it.
7. If the sqare is Green, then you have root shell and ready, if its not green, press the ROOT button to the right in MTK Droid tools.
8. Click the "IMEI/NVRAM" button and then Backup to backup your IMEI/NVRAM, the backup files will be inside of the MTK Droid Tools folder.
Also you can manually write down your IMEI number just in case it should be lost.
9. Now go to the tap "root, backup, recovery" (in MTK Droid Tools).
10. Click the Backup button, and it will create a complete backup of your ROM. (in the end it will ask, if you want to pack it, just answer no)
11. When it is finished then also click "To prepare blocks for FlashTool", that will convert the backup to be compatible with Spflashtool. (choose the files.md5 inside the backup folder)
12. After the backup is done it will be inside "backup" in the MTK Droid Tools folder. And inside it there will also be a new folder called "!Files_to_FlashTool" Inside there the files for Spflashtool is. So when loading your backup with Spflashtool you must load the scatter file from inside there.
13. Now to install CWM (clockworkmod recovery) In MTK Droidtools, choose "To use boot from phone" and click the "Recovery and Boot" button. It will ask you a lot, just say yes every time, and it will end of sending CWM recovery to the phone and reboot into it on the phone. After you see CWM on the phone you know it is done. You can switch the menu with the volume keys, and the power is the select button.
14. Inside CWM you can also do a complete backup of your phone (remember to have enough space, you can do the backup to the internal storage OR to the SDcard - try "backup" if that fails then choose instead "backup to external sd" or vice versa). I recommed doing that because CWM makes another backup than the one made with MTK Droid Tools. So if you should get problems or loose something, you can always run your CWM backup into your phone and it will be as before.
15. After your done the backup, copy the backup also to a safe place on your PC. Just in case!
Click to expand...
Click to collapse
There may be a way to convert the backup you made.
I used ROMdump on one of my Goophones, and it created 3 files: config.gz, system.info.gz and system.tar. The System.tar file is a large archive. I suppose I have to convert this into somehting that SPFlash can use, but from what I am reading, I think files like this are supposed to be flashed from Recovery. If you can connect while the device is powered off, you may be able to ADB into the device and start a shell, copy the files in and then start s flash. I have only started working with ADB so I'm not clear on it.
I think best bet, contact the Seller of the device, if that wasn't you have the person who ordered the device send a message, ask if they have access to the ROM, sometimes they will offer to send it to you via Skype, iBaby888 offered that for me, but I found the exact Rom I needed on Needrom. If they don't have it, you can ask for the rom over there, make a post identifying the device and just say "need ROM", provide the fingerprint and Kernel if you do that.
gae1991 said:
I saw on the internet that there is a box to be able to flash the ROM even if the phone is dead. This box is called MTK-box. I have already had experience in the past with the atf-box for Nokia, you say that might work?
Click to expand...
Click to collapse
SPFlash and other flashing tools all work that way, even Odin, the device must needs be powered off and in some cases the battery removed. They even have tools to reset the device, if your device does not have a reset button hidden somewhere, the developers of the Flash tools sometimes tell you to disconnect the battery, but in the case of a device not having access to the battery, there is the reset button. Always trip that before each attempt to Flash.
It's basically the same thing, I'm sure OP can flash the device, but we can't find the stock ROM anywhere.
with respect to paragraph 11 forgotten, the program in my case has not created any file called "files.md5", the guide I've read (which is the same that you posted you) I knew I would have to be after the backup, but so was not . In the folder "backup" I only have the folder "/ system" with subfolders "app", "priv-app" etc.
I remember also that the program at the end of the backup asked me if I wanted to compress zip, I clicked "no" and in the right part of the program I read "activities ended in error," I read above and I see the another error "no space left on device", and the guide I've read this error occurs with only the devices with 4 GB of ROM for perform the backup also in the device. anyway thank you for helping me.
my phone id dead
please if you can help me too.
I have an allview phone that has a mediatek mt8735m processor is(dead)does not start,but when I plug it into the usb port of the pc,the your pc recognizes it but does not stay connected
what could I do about it?
Related
As in another thread, I just complete bricked my TS but with help from cheahcl and Lokifish Marz I come back a alive! With more and more people receiving their TS, I feel the need to summarize what I experienced so others wont need to go through all those sh*t. I didn't create any of the tools/step here... All things belongs to the great DEVs of XDA. I just summarize as my personal experiences for your convenience~
<A little background: I am on the 4th list of 1/8/2100>
First of all: Do a backup immediately after you got your TS!
===========================================================
MTK based system is actually very difficult to become brick (almost impossible) as long as YOU HAVE THE F/W SPECIFIC to your TS! The problem is that it seems OMate made changes between each delivery. For Example, the 4th list of 1/8/2100 is different in of the 3rd or earlier 1/8/2100. At least from F/W's point of view. Thus, any F/W that are posted on XDA is NOT guaranteed to compatible with YOUR TS, unless you are lucky!
Since there is NO official/complete deposit of "stock F/W". Once you modified what in your watch, there is no guarantee you will get same version of F/W and it's very possible that your watch will never return to stock!
Part I --- back up the F/W
============================================================
First of all, please get all necessary tools directly from this post "All Tools" http://forum.xda-developers.com/showthread.php?t=2734687 (Do NOT download or install any other things there!)
*if above link doesn't work, I have a mirror in end of this post.
Follow those steps: (modified from link above)
1. Download "All Tools"
2. Install Universal ADB Drivers (included in All Tools) <--If you already have ADB up and running, it's not necessarily, then.
3. Enable USB Debugging on watch
4. Launch MTKDroid Tools
5. Connect watch to PC
6. Please follow the instruction from here: http://www.chinaphonearena.com/foru...up-MTK6592-MTK6589-MTK6577-and-all-MTK-Phones
a. Skip everything above and just starts from "B) Open ADB prompt to begin communication with the phone" .
b. Don't worry about the recovery thing... TS comes with a recovery which is not locked and you can do everything this article said with only stock recovery. (also no busy box is needed, nor su since TS run everything in root!)
c. You could also refer to the video guide below for details
7. After Step D), you will have a backup of your F/W which 100% compatible with your TS!
Part II --- back up the IMEI and NVRAM
============================================================
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
Tools:
============================================================
Currently I mirror "All tools" here https://www.dropbox.com/sh/tsa2jottw...uIEpOyyDiYWFva until it's shutdown by Dropbox for too much traffic. (Any one can provide me a better place?)
I also add a FW backup for "4h list 1/8/2100", which ONLY work with this version of TS. It ONLY works if your original build version is "20140513.103530". If NOT, DON'T TRY IT. It will just waist your time! You had been warned!
After you played with your TS, maybe you will come to an end that your TS is no longer turn on! Fear NOT! It's just the fan part of playing with your TS!
Return to Stock Steps (F/W and IMEI, NVRAM)
======================================
1. If your TS still can start in system, then just simply follow the excellent guild prepared by MasterZen88 at http://forum.xda-developers.com/showthread.php?t=2641261
2. The only difference is you must use the F/W you backup yourself DO NOT DOWNLOAD THE F/W list in that page!
3. If your TS no longer powers on, or cannot enter the system, please do:
a. Disconnect your TS from PC
b. Still follow the steps on above link to prepare your PC to install the MTK USB driver, read in the "Scatter file" from your backup
c. The only difference is Step 11. Since your TS won't power on, you need to pull the battery, than re-install the battery than connect to the PC.
d. After you did this, You should see the MTK SP Flash Tool start flashing your TS!
4. After restore system, please follow http://forum.xda-developers.com/showthread.php?t=2631953 "Restoring Your IMEI After A Full Firmware Flash" to restore your IMEI and NVRAM or you will not able to make phone call!
Trouble Shooting (common error message from SP Flash Tool)
=======================================================
1. "S_FT_ENABLE_DRAM_FAIL (4032)"
Ｔhe F/W you try to flash is NOT compatible with your TS. If the F/W is not backup by yourself, downloaded from XDA or anywhere, there is a 99% chance it won't work on your TS!
Sometimes it also indicate you have a bad connection between TS and PC, maybe a bad cable or cradle...
2. "S_FT_READBACK_FAIL(4009)"
I don't really know what caused this... I experienced twice but I just pull the battery again and it's go like normal
3. "S_COM_PORT_OPEN FAIL(1013)"
a. The MTK USB VCOM driver is not properly installed, or
b. Your connection between PC and TS is not good (bad cable?)
c. Due to previous error, you NEED to pull the battery out of TS and put in the battery than link to PC again! The TS will go offline once any failure during flashing process.
I hope this small guide will save someone from the panic time I had....
How to install Play store and (super)SU?
Installation Play Store
====================================================================
It's really easy... just forget code like *#*#2013.... Doesn't work on newer batch! (I only confirmed this on 4th list of 1/8/2100 developer version)
1. Download Google play here: http://www.xda-developers.com/andro...densities-and-the-rest-of-this-weeks-updates/
2. Make sure on TS you enabled the "Setting/Device/Security/Unknown Sources"
2. transfer the file into the internal SD of TS
3. Use the TS' built in file explorer to locate the apk, than just click the apk to start installation.
4. Profit!
Install (super)SU
====================================================================
Just follow the steps below (I only confirmed this on 4th list of 1/8/2100 developer version) , I saw this somewhere in XDA but forget where... credit to the original poster!
1. Launch MTKDroid Tools (please configure it as the steps in OP)
2. Connect TS to PC
3. Click on "root, backup, recovery" tab
4. Push the SuperSU button then choose which version of SU you want (I use SuperSU)
5. After success installation, go to your TS (TS must have access to internet) and launch SuperSU. SuperSU will prompt to update SU binary
6. Profit!
Great Guide. Following your guide I've backed up all the necessary files to go back to stock for AW-420
:good::good::good::highfive::highfive::highfive:
I have a problem making backups - both the nvram and full system backups fail. I suspect it is not finding an md5 application since files.md5 is zero bytes but the filesystem seems to have been copied OK. (with a fairly clean Win8.1 64 install, just android dev tools installed, this is my gaming machine...)
Code:
--->>> Connect to device <<<---
--- NVRAM Bin Region is write to the file: : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.bin
--- ERROR during copying file between phone and PC : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.tar
tshoulihane said:
I have a problem making backups - both the nvram and full system backups fail. I suspect it is not finding an md5 application since files.md5 is zero bytes but the filesystem seems to have been copied OK. (with a fairly clean Win8.1 64 install, just android dev tools installed, this is my gaming machine...)
Code:
--->>> Connect to device <<<---
--- NVRAM Bin Region is write to the file: : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.bin
--- ERROR during copying file between phone and PC : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.tar
Click to expand...
Click to collapse
Actually I been to this before... However I don't remember what exactly I did to resolve this....
Basically this tool relie on ADB to get access to this watch. It seems your watch is not communicate correctly via ADB. Maybe reinstall the ADB driver from the All in one tool I linked in OP (even your ADB works)
Sent from my HTC_One_max using XDA Premium HD app
New link to "All Tools"?
Since Loki removed his files, is there another link to "All Tools"? Can't download it at link above.
Thanks!
Sorry about that. Bad part is older firmware and root/patch methods are causing serious issues due to Omate changing the hardware yet again.
Lokifish Marz said:
Sorry about that. Bad part is older firmware and root/patch methods are causing serious issues due to Omate changing the hardware yet again.
Click to expand...
Click to collapse
However, the "All Tools" is still working and a valuable piece for everyone here! Could you please at least keep that?
Without the "All tools" I worry when people run into trouble, there would be even harder for them to go back.... (not only need to get correct FW but also need to get correct tools). There are so many version on the internet which is at best too old as not working, at worst infested by something...
Currently I put this "All tools" here https://www.dropbox.com/sh/tsa2jottw6f1f72/AAAgDEcvmo7uIEpOyyDiYWFva until it's shutdown by Dropbox for big traffic.
I also add a FW backup for "4h list 1/8/2100", which ONLY work with this verion of TS. if anyone need it...
(Dear Lokifish, please PM me if you have concern of my hosting of "All tool".)
FYI:
Just as Lokifish Marz said, looks like omate changed hardware for the 4th EU patch of deliveries.
The latest EU batch from the 4th list has the following firmware:
Baseband: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
Kernel: 3.4.5
OUI: 2.1
Build: Omate_TrueSmart_20140513.103530_V2.0
My TS was from the 3rd EU batch which has the following firmware:
Baseband: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
Kernel: 3.4.5
OUI: 2.1
Build: Omate_TrueSmart_20140328.182336_V2.0
Out of curiosity, I was already in Unified Rom, I tried to flash "Build: Omate_TrueSmart_20140513.103530_V2.0" for my TS.
I bricked my device! lucky I had made all the relevant backups, and got my TS back to factory ROM that came from the 3rd list batch.
Then Unified it again.
tshoulihane said:
I have a problem making backups - both the nvram and full system backups fail. I suspect it is not finding an md5 application since files.md5 is zero bytes but the filesystem seems to have been copied OK. (with a fairly clean Win8.1 64 install, just android dev tools installed, this is my gaming machine...)
Code:
--->>> Connect to device <<<---
--- NVRAM Bin Region is write to the file: : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.bin
--- ERROR during copying file between phone and PC : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.tar
Click to expand...
Click to collapse
Did you run the tool as administrator to make the backups?
Stu| said:
Did you run the tool as administrator to make the backups?
Click to expand...
Click to collapse
Yes, tried that. I'm quite happy with my adb access, managed to root my HTC M8, and get shell access on the TS fine (it now has SU working).
I've installed cygwin (overnight!) in the hope that will provide the missing exe that the tool was seeming to want.
lssong99 said:
(Dear Lokifish, please PM me if you have concern of my hosting of "All tool".)
Click to expand...
Click to collapse
It's all good. I'm fine with it. Seeing that folks are now looking at almost 10 different HW versions to deal with, AllTools is going to become really popular.
lssong99 said:
However, the "All Tools" is still working and a valuable piece for everyone here! Could you please at least keep that?
Click to expand...
Click to collapse
I have also uploaded the zip to gdrive as another mirror. https://drive.google.com/file/d/0B099RU3-XRVgVW5HeEpqUXZPMGs/edit?usp=sharing
Fixed my issue. As per the MTKDroidtools log file:
Code:
23/05/14 11:40:34 --- NVRAM Bin Region is write to the file: : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxx
xxxx59988_nvram_140523-114031.bin
23/05/14 11:40:34 /system/bin/sh: tar: not found
23/05/14 11:40:34 --- ERROR during copying file between phone and PC : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmar
t_86xxxxxxxx59988_nvram_140523-114031.tar
the issue was with missing functions running _on_the_watch_ Installed busybox, and good to go. Now, this does leave a problem for anyone wishing to do a backup before making mods.My original backup extracted the system partition (as a dos copy of the filesystem, which must be incomplete for permissions etc) but when done with tar on the device I get proper img files.
I suspect it is possible to manually 'mount -remount,rw /system' then adb push busybox, as it happens I've already installed su so just installed from playstore.
lssong99 said:
1. Download "All Tools"
Click to expand...
Click to collapse
Where is the all tools?
sorry i have find it in GDrive!
xs4all said:
FYI:
Just as Lokifish Marz said, looks like omate changed hardware for the 4th EU patch of deliveries.
The latest EU batch from the 4th list has the following firmware:
Baseband: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
Kernel: 3.4.5
OUI: 2.1
Build: Omate_TrueSmart_20140513.103530_V2.0
My TS was from the 3rd EU batch which has the following firmware:
Baseband: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
Kernel: 3.4.5
OUI: 2.1
Build: Omate_TrueSmart_20140328.182336_V2.0
Out of curiosity, I was already in Unified Rom, I tried to flash "Build: Omate_TrueSmart_20140513.103530_V2.0" for my TS.
I bricked my device! lucky I had made all the relevant backups, and got my TS back to factory ROM that came from the 3rd list batch.
Then Unified it again.
Click to expand...
Click to collapse
My TS was from the 2nd EU batch and it have the same firmware as yours.
There are two backup folders for TrueSmart in the location of "backups"
I just tried to backup my TrueSmart and everything went quite smoothly until I was meant to prepare blocks for Flash Tool. I could find 2 separate backups for TrueSmart with different time stamps on them. I downloaded the AllTools.zip that was hosted in this thread in Google Drive. Is that someone elses backup or what? I have to just choose the later backup, correct?
EDIT: Went with the latest because the earlier already had !FilesForFlashTool folder in it.
How can I actually use SuperSU? When a root request pops up, there aren't any buttons visible except for ask again. I cannot scroll. How do you do this?
soulcrusher said:
How can I actually use SuperSU? When a root request pops up, there aren't any buttons visible except for ask again. I cannot scroll. How do you do this?
Click to expand...
Click to collapse
That happened to me as well. It turned out that if you change the font size in Settings - Display - Font size to Small it will work just fine and show the buttons. Your welcome.
Hello All! I'm sorry, I'm very new to this. Can someone please point me in the direction of instructions that I need to follow in order to root my son's Star Wars Nabi? I'm not sure if it's a nabi 2 or not.. I can't find that anywhere. We just bought it for Christmas. The internal storage is used up and the games won't move to the SD card - so, I figured my only option was to root it. There are so many pages out there with root instructions and I'm not sure which ones to use. Any help would be greatly appreciated.
MrsPurchase15 said:
Hello All! I'm sorry, I'm very new to this. Can someone please point me in the direction of instructions that I need to follow in order to root my son's Star Wars Nabi? I'm not sure if it's a nabi 2 or not.. I can't find that anywhere. We just bought it for Christmas. The internal storage is used up and the games won't move to the SD card - so, I figured my only option was to root it. There are so many pages out there with root instructions and I'm not sure which ones to use. Any help would be greatly appreciated.
Click to expand...
Click to collapse
What is the name of the device in the "about tablet" tab in settings?
It's probably closely related to the nabi2S of i were to guess. You can either try a root method like Kingo root or a TWRP method. Since you are the first person I have seen here with a Star Wars I don't have all the answers.
-If you use Kingo there is no backup to help you if something goes wrong.
-If you use TWRP method there may not even be a version of TWRP that will work, and initially you will not want to install TWRP but run it from ram. So the commands will be a bit different then what you see on the forums. With that method though you will have a backup.
aicjofs said:
What is the name of the device in the "about tablet" tab in settings?
It's probably closely related to the nabi2S of i were to guess. You can either try a root method like Kingo root or a TWRP method. Since you are the first person I have seen here with a Star Wars I don't have all the answers.
-If you use Kingo there is no backup to help you if something goes wrong.
-If you use TWRP method there may not even be a version of TWRP that will work, and initially you will not want to install TWRP but run it from ram. So the commands will be a bit different then what you see on the forums. With that method though you will have a backup.
Click to expand...
Click to collapse
It doesn't have a name :/ It has a model number (SNB02-NV7A), an edition number (SNB02-NV7A-US-SW), android version (4.4.2), a kernel version (3.1.10) and then a build and hard ware number.
I appreciate the advice though. Thank you!
MrsPurchase15 said:
I appreciate the advice though. Thank you!
Click to expand...
Click to collapse
SNB02-NV7A is the model number for the NABI2S. It's likely the Nabi2S TWRP will work for the tablet. To use it though you will likely have to unlock the bootloader and that will erase all your personal data on the tablet. It's the safer method since you will have a backup of your tablet, but will require you to get your hands dirty.
You can read through this http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 and see if it's something you want to try.
Using the above linked thread as the basic outline, in general you would:
-Setup adb/fastboot and the windows driver.
-Unlock the bootloader(wiping all personal data on tablet)
-"fastboot boot" NOT "fastboot flash" the Nabi2S TWRP recovery to the tablet RAM.
- backup the recovery, boot, system, and addon(preload) partitions. Then you can always recovery the tablet if something goes wrong, and help others that need to recover their tablet.
-Download SuperSU and flash from TWRP to obtain root.
I can help with more detailed instructions but if it's something that seems uncomfortable to try then I don't want to type it all out. Again a kingo root or other root method will likely give you root, I personally like having a clean backup before beginning and there is none in existence yet.
Thank you so much! I am absolutely willing to try it. I can't do much worse to it then the state it's already in.
MrsPurchase15 said:
Thank you so much! I am absolutely willing to try it. I can't do much worse to it then the state it's already in.
Click to expand...
Click to collapse
Again the Nabi general information thread is going to be the biggest help in understanding what needs to be done. That information is here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 The procedure below isn't as long as it looks I tried to add some troubleshooting stuff along the way.
Best to have a mircoSD card for this well at least 4GB. Start with the microSD in your computer if possible.
1) First you will need to grab all the files you need:
-Drivers: Refer to drivers section #4 in the General Info Thread. Your choice if you want to try PDAnet, NabiLab, or Universal Naked Drivers. The NabiLab drivers are self installing and work pretty good in a lot of situations but not always. Download which ever one you choose to your computer. I'm going to talk about Nabilab and Universal as first resorts, we will revisit PNAnet if you are having driver issues.
-ADB and Fastboot tools. Here it's best to refer to section #6 in the General Thread. Specifically:
Download and install this package(pay attention to where you install this as you will likely need to put files in there later): http://forum.xda-developers.com/showthread.php?t=2317790
From your start menu select "Minimal ADB and Fastboot" this should open a command prompt where you can type commands
If you didn't pay attention or forgot where you installed the files, at the command prompt that opens type "explorer ." The period is important, explorer <space bar> and a period. So type what is between the quotes.
-TWRP for the NABI2S. Get that file here: TWRP for Nabi2S
After this step you should have downloaded 3 files and the ADB/fastboot files you should have installed. That leaves the remaining 2 files. One should be NABI2S_TWRP271.img, copy that file to the folder where you installed ADB/fastboot(remember you can find that folder by selecting Minimal ADb and Fastboot from your start menu and typing "explorer ." as explained above.) The remaining file is the which ever driver package you picked. If it's universal naked extract the zip file to a place you know. If it's Nabilab drivers go ahead and install them. PDAnet we will try later if these 2 don't work.
2) Boot the Nabi to fastboot with the USB cable plugged in to your computer. Also open device manager on your computer so you can see when the interface comes up. I don't have a Nabi2S so this may be not exactly right. Start with the tablet off. Press and hold the power button AND the vol up buttons at the same time. At some point you should boot up and have a small text menu in the top corner of the screen.(If that doesn't work try power and vol down buttons). One of the menu items will be fastboot protocol. You will want to highlight that text using the volume keys, and then select it using the volume keys.(again I an not sure which is which. Vol - might change which is highlighted, and vol + will select that line, or vice versa, remember which does does what as you will need it later on). Keep trying combinations or timings if it's not working. When it's right your computer will acknowledge a new device plugged in and the device manager screen should show a fastboot or unknown interface.
3) Getting the drivers working. If you chose the Nabilab drivers they should automatically install, and in device manager you should see and item called Android device, and when expanding that entry some bootloader or fastboot interface(When you see this you should be done with this step). The tablet will also switch the text on the screen to say something like "continue", "bootlader", blah, blah. If you went with universal naked drivers this is where you would locate the unknown or fastboot device with the yellow exclamation mark and manually install the driver by pointing them to the folder you extracted(There could be driver signing issues depending on which version of windows you are using. You will have to google "disable windows driver signature enforcement", but basically you will reboot the computer disabling driver signature enforcement. Hopefully if you picked the Nabilab drivers and they work on your computer this step will be pretty painless and not as long as it looks.
4) Unlocking the bootloader. If you have the command window open now great, if not from your start menu select "Minimal ADB and Fastboot" this should open a command prompt. REMEMBER this step will erase all you data on the tablet, game saves, pictures, etc.
Get ready to acknowledge some text on the tablet itself as you have to be pretty quick using the volume keys to highlight and select(Same function as what you noted in step 2). At the command prompt type:
Code:
fastboot oem unlock
OR
Code:
fastboot -i 0x0489 oem unlock
On the tablet some text will pop up asking yes or no do you really want to unlock the bootloader? The selection is made with the volume keys. You should see some confirmation of erasing tablet and completed.
If this step isn't working when you type the command i.e. "waiting for device" the drivers probably still aren't installed correctly. If something failed in this step you may be forced to reboot the tablet and get back in fastboot mode(step2)
5) Install TWRP. With tablet in fastboot mode. Type at the command prompt:
Code:
fastboot boot NABI2S_TWRP271.img
or
Code:
fastboot -i 0x0489 boot NABI2S_TWRP271.img
If you are getting file not found errors the NABI2S TWRP file isn't in the folder. If all goes right the tablet will boot to TWRP. This is where we may have problems as I'm not sure if the NABI2S TWRP can boot the Star Wars Nabi. If it's not booting then we are pretty much done at this point...
6) Getting SuperSU(root). If the tablet booted TWRP. Download this UPDATE-SuperSU-v2.46.zip. Copy that file to your microSD you have inserted in the computer. When that is done safely eject the card from the computer and put it in the tablet.
7) In TWRP select the "mount" tab and check MicroSD(external storage) and the check box should become checked.
8) Make a backup. Select the "backup" tab in TWRP. You will have the options to backup "recovery" "boot" "system" and "preload(or addon)" select all 4 of those. Then select the backup location as MicroSD(external storage). Swipe to backup.
9) Only if step 8 worked install root. Select the TWRP "install" tab. Back out to the highest level, and find external_storage. The UPDATE SUperSU zip should be there. Select it and swipe to install.
10) Only if the step 8 and 9 worked go to the "reboot" tab and reboot. If they didn't work. Press and hold the power key until the tablet shuts off, and we can troubleshoot. If you rebooted the tablet will take a long time to boot initially since you wiped the tablet and it will have to rebuild data. You can then reset up the tablet.
11) Get superSU from Play Store and verify root.
12) If all this work your backup will likely be a benefit to future users so sharing it might be something to consider.
Well.. I followed everything above and it all appeared to work perfectly - however, I still can't access the microSD card to store games. Any ideas?
MrsPurchase15 said:
Well.. I followed everything above and it all appeared to work perfectly - however, I still can't access the microSD card to store games. Any ideas?
Click to expand...
Click to collapse
Are you using an app to do this(like link2sd)? Or just hoping root alone would allow you to do this?
I was hoping the root would allow me but I take it that's wrong, lol.
MrsPurchase15 said:
I was hoping the root would allow me but I take it that's wrong, lol.
Click to expand...
Click to collapse
Haha. Understood. You do need root to do it, but root is needed for the apps that can make it possible. My kids never had the problem when they had their old Nabi2's so I'm not as much help on the "how to" portion but I understand how the apps work. Read through this thread to gain some understanding of what it takes now that you have root. http://forum.xda-developers.com/showthread.php?t=2086338
There is another way also where you stop using internal storage altogether and use an external by editing the ramdisk but it has some limitations as well.
This was awesome i have the same star wars edition and everything works well i even made a backup which i can post and i used the 3.0.1.3 kernel backup to restore the tablet and it still worked
UPDATE: I was able to debrick the phone. Read my later post for details.
----------------------
Hi All,
Thank you all for having amazing community of hackers and developers here. You guys rock.
I started my search for a new rugged rootable phone recently and I settled on Poptel P60. It is a great phone though slightly bigger than what I normally get. Nontheless, the specs are excellent and the price is fair!
I've had a limited success rooting and customizing this phone. The OEM interface is almost bearable but overall the "Customized UI" felt like a downgrade from stock Oreo. It has a very annoying feature of reverting to stock launcher on startup, even when I selected Nova as my default one. The stock launcher is not that great. This, and the lack of ability to use x.flux, Titanium Backup and other root-only apps drove me to try hacking things again.
After emailing the manufacturer they provided the firmware but it is in CPB format. I tried at least 3 different converters for CPB to MTK Scatter and they all either freeze or hang. No luck.
Instead I did a rom readback with SPFlashTool and then cut up the partitions with Wwr. Now I've finally had the recovery partition! I used CarlivImageKitchen to port TWRP from a similar device, Ulefone Armor 5. The chipset and resolution are same. After some trial and error it worked! I had to use USB-OTG for input and external sd card had a weird label, but I was able to install Magisk from the SD card to root, followed by XPosed, full package. It worked! If anyone needs my ported TWRP Recovery for Poptel P60 just ask!
However, the manufacturer UI did complain a lot about the phone being rooted. Eventually, somehow, Magisk stop receiving root requests. They never showed up and timed out! Very strange, because apps that already received root continued working. I tried a lot but could not fix the issue. I was fed up. I wanted to do a manufacturer reset (in hopes of starting from scratch and then attempting to port Lineage or something) but, as I've mentioned, I have not received a firmware compatible with SPFlashTool. I tried to make one from Armor 5. The partitions were almost the same (both are MT6763 devices). One was out of order, and offsets were different and I patched all those. To be clear, I used all the partitions and layout extracted from my rom readback that was cut up by Wwr. I only used the Armor 5 scatter as a reference for file format. I edited the layout to match everythign I saw in Wwr.
This is where the horror begins. I tried flashing (Download Only) with SPFlashTool but got some error saying something changed. "Do you want to do Format & Download instead?". Being an inexperienced idiot that I am, I said yes!
Now, the phone appears bricked. No lights. No screen output. Cannot enter fastboot. Cannot enter recovery. Cannot boot.
I have a feeling the preloader got corrupted. I'm not sure this is the case because I've omitted the preloder from download. At least the first time the phone started acting bricked. The device still shows as Mediatek USB VCOM device and flashing gets initiated but all attempts to flash result in errors. MA checksum mistmatch or something along that order. I've tried a lot of things and I'm stuck! For good or for worse I've tried flashing Ulefone Armor 5 preloader but I'm getting the same error when trying to flash it.
Here is what I have...
- Stock firmware in SPB format. I can't use it and nothing I tried worked for converting it.
- ROM dump made with SPFlashTool
- Wwr was able to extract every partition except preloader. This includes nvram, etc. I'm not sure why it was not able to extract the bootloader.
- TWRP port that worked. Seems not useful if the phone does not start.
- Preloader for Ulefone Armor 5, (same chipset and resolution)
Clearly I am an idiot for using "Format & Download" option. I've found posts later suggesting against it. I am also over my head for trying to tackle a new device by myself, though I have had a marginal success with porting TWRP and installing Magisk.
Now, I feel like idiot and I am stuck! I beg you, XDA developers, if you have any advice (besides not being an idiot in the future), please share!
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
SkylinesHD said:
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
Click to expand...
Click to collapse
That wouldn't work, heh. I bought this phone on eBay and rights now it's currently sold by a handful of sites. It is on warranty but returning it back to China would be complicated. At any rate, I live on the edge outside of warranty!
I was just about ready to give up and feel like the biggest reckless loser on Earth... Days of tinkering around with nothing but a phone brick to show for it. Poptel tech support wouldn't provide me with MTK scatter. All they gave me was this SPB firmware that nobody uses and it crashes every converter I threw at it. Useless.... No fastboot. No recovery. No functional bootloader.
The amazing GOOD NEWS is I have debricked the phone... I used a bootloader from another phone's firmware: Cubot_Power_MT6763_180607_8.1.0. Unlike Ulefone Armor 5's preloader this one worked! It seems like it's the only thing I was missing because the phone starts up and everything seems to work. I must have done a good job with all other partitions but I'll try to watch for signs of anything else broken. Right now it seems fine.
I'm not sure if the bootloader was completely gone, corrupted, or an incorrect one was used. All I know is I was able to download Cubot Power's working bootloader (also MT6763) with SPFlashTool. Nothing like a feeling of unbricking your phone!
I will post more updates if that's ok... I'm hoping to port Lineage on it (I've never tried that before) or at least find a way around the manufacturer's clunky UI. The hardware is great otherwise. If anybody wants a working ported TWRP image or the scatter I used for debricking just ask! I will make a post later if I have more success with customizing the phone. The phone is debricked and I have a scatter and images to fall back on if anything goes wrong. Woot! Thank you everyone who developed these great tools.
I have the same phone been looking for info. there's a thread on 4pda with poptel p60 that has the scatter file and firmware. Any chance you could post the twrp for this phone? having trouble trying to port myself cant figure out port 6763 from the guides available.
4pda.ru/forum/index.php?showtopic=933002
Firemware:
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download
idaman0 said:
Hey man,
Was wondering if you saw my post on your thread. Looking for TWRP for the Poptel P60.
Thanks,
telegram @drmethyl
Click to expand...
Click to collapse
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
https://mega.nz/#!MNVGhaYS!63ovQeowwoP1oE3v6-_ZS8gKx_-mxOh4G4qWcKRbuiQ
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
zeromemory_wtf said:
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
Click to expand...
Click to collapse
sorry man, didn't end up using yours theres a twrp on 4pda now with a mod to flash to keep root. I'll upload for you here if you don;t have an account there.
The patch for the Light-kastomizator v.12 factory firmware.
I decided not to bother with the draining and distribution of modified firmware as a whole, easier to apply the patch, and ... you're done!
If that - the factory firmware v.12 lies with us -HERE, no problem you can return everything back, or (if there is something Kolupaev), first ask her, and then patch.
#
What is done
Будут удалены:
/system/tts
/system/app/QK_LogSystemAbroad_wm_bl
/system/app/QK_Sos
/system/app/QK_PrivacySpace
/system/app/QK_PersonalAssistScreenAbroad_V2
/system/app/BY_3RD_OperaMiniBrowser_OEMBranding
/system/app/BY_3RD_OperaNews_OEMBranding
/system/app/Drive
/system/app/Duo
/system/app/Gmail2
/system/app/GooglePrintRecommendationService
/system/app/LatinImeGoogle
/system/app/Maps
/system/app/Music2
/system/app/PartnerBookmarksProvider
/system/app/Photos
/system/app/YouTube
/system/app/Videos
/system/presetapp/BY_3RD_OperaMiniBrowser
/system/presetapp/BY_3RD_OperaNews
/ system / priv-app / MtkCellBroadcastReceiver
/ system / priv-app / ConfigUpdater
/ system / priv-app / GoogleFeedback
/ system / priv-app / FilesGo
/ system / priv-app / GooglePartnerSetup
/ system / priv-app / QK_MagazineAbroad
/ system / priv-app / Velvet
The system additionally installed:
ES_Provodnik_3.2.5.5 (graphic mode "Panatta-sport")
the SD Maid Pro - system Cleanup (Lite Mod "Breathe of fate" )
Changes:
By default the system is set to Russian language , region and time zone Russia / Moscow. Setupwizard (first assistant settings) is not cut off.
GBoard keyboard replaced by fashion Antonbeard GoogleKeyboard(with a limited access to the Internet is built dictionaries -.. English and Russian)
Google-search is replaced by the latest beta (it is possible to change the style and transparency of the widget)
have been added and changed some default sounds and ringtones, and the default there as a very sadly.
Blocked by advertising the hosts file.
Improved energy efficiency due to shutdown of background update service does not fall asleep GAPPS and downloaders (allowed these services Doze mode).
#
Setting:
1. Throws on micro SD-card this patch.
2. Downloading the last zip-installer " Magisk-v ..... the zip " and also copy it to the SD-card, turn off the phone.
3. Through the SP Flash Tool sewn recovery "TWRP" (the system can not be loaded !!!).
4. Vaypaem userdata (reset to factory settings) through better "factory mode" (volume down inc +) / select "Clear eMMC".
After reset immediately loads in the TWRP (inc + volume up), and from the sd-card in turn apply patches "LiteMod_Poptel_P60_v.12.zip" and "Magisk-v ..... zip". Reboot from the installation refuse twrp-applications.
Done, you have custom firmware!
(If twrp and Ruth is already installed,
After the completion of all the manipulations, it is desirable to flash the stock (factory) rekaveri, then no problem can be used to reset the system from the Android menu and install the firmware update OTA (over the air).
Download: LiteMod_Poptel_P60_v.12.zip
PS. Sberbank + contactless payment working properly, despite the fact that the system has been modified and installed Ruth! :derisive:
Click to expand...
Click to collapse
3.2.3 TWRP by Jemmini for "Poptel P60" ( with the phone port Blackview BV9500): Attached file recovery.img (17,27 MB)
The port used by the kernel to flash Android 8.1.0 version of "POPTEL_V12_20181030"
WARNING !! After installing recovery, subject to permit changes in the system partition, install ROOT is required, otherwise the system will not boot. if not to accept the possibility of changing the system partition and establish the patch-root subsequent restart in overwrite TWRP recovery returned drain-
Attached fileMT6763_Android_scatter.rar(1.28 kb)
#
Getting ROOT
For ROOT set out under TWRP (pre throwing off the memory card), this patch: Attached fileMagisk-v18.0.zip (3,99 MB)
#
Stokovye boot / recovery
from said EEPROM: Attached filestock.rar (22,75 MB)
#
What does not work:
1) Do not see "the internal memory" (can not decipher the "data" section and ask when starting TWRP password).
Solution:
download the patch: Attached filedisable_encryption_P60.zip (133.89 KB)
throw it on the memory card, boot into TWRP, go to the "mount" to put a checkbox on the vendor , then go to the "install" and install the patch.
After installation make data in the "cleaning" cleaning (possibly cleaning does not help but the formatting of data should definitely help)
after data manipulation TWRP be able to work with the data section
2) is not working USB / MTP mode into TWRP
#
Information for those who are "in the tank" :
When TWRP presence in the smartphone in any case and under no circumstances should you do reset through the system.
Resetting takes place only directly through TWRP (standard cleaning sections)
If you run the command via the android in the first place, it can not be executed because it does not understand the TWRP.
and secondly, you get a constant load in TWRP because it has not yet executed the command android you will always be send to recovery /
Solution for "tank": need to install flow-recovery to be completed through a reset command or cancel it.
Another solution I personally do not know
Just do not forget about gratitude : Jemmini,- for the compilation of the TWRP which served as donorUrree,- order TWRP and testing (nothing would have happened without it)Message edited Lomaster_Serg - 6.1.19, 03:02
Click to expand...
Click to collapse
rapidgator.net/file/84ccd2d612ade0256eb927895d4ed37e/LiteMod_Poptel_P60_v.12.zip.html
rapidgator.net/file/c77fec40e349f8083eda14bf7058425c/recovery.img.html
rapidgator.net/file/6621d517cef9aa10abc78b40bcdc8b26/stock.rar.html
rapidgator.net/file/7a7db29c0d35eee169b76698aac6b50b/MT6763_Android_scatter.txt.html
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download
Hello there,
I'm wondering if there's anyone knowledgeable to point me in the right direction. Coronavirus (or I) messed up the build.prop file in a Chinese-made JTY-K107 (MT6580 architecture) tablet and now stuck in a soft-brick state. I cannot use adb push or adb sideload (doesn't detect device probably because I had attached another MT device, a Huawei on the PC before and that is the device I pulled the build.prop from to mess with the bigger tablet and now all seems jumbled driver-wise on my Win 10). In any case, I am able to copy to the SD card an update.zip but factory recovery installation is not possible ("installation aborted" - signing issue?). I tried these two zips inside which the original build.prop files are now nestled. It's maybe the commands/scripts that are at fault or it's some signing issue (that hopefully can be tackled). I don't know. I am very reluctant to think about flashing ROMs at this stage. (Porting MT-architecture ROMs are not exactly easy or risk-free, from what I have seen around other threads/forums.)
The link to the folder with the non-working update zips I pulled from other sites or threads (not knowing how I should go about building these files from scratch on my own):
https://app.box.com/s/7byabibx2j0jfo2zlgmg0oi0ca66vkyn
Thanks very much for any info (or possibly a fix of the zips to make it compatible with MT6580 to install the update).
Cheers,
Zoltán
@zanodor
IMHO a simple factory reset may solve your problems.
jwoegerbauer said:
@zanodor
IMHO a simple factory reset may solve your problems.
Click to expand...
Click to collapse
Today I was thinking, people like overcomplicating things: there must be some easy solution. I actually had done that out of frustration (knowing that I had a Titanium Backup on SD) but the boot issue persists (I tried again but all I see is the Android logo for minutes now).
I thought maybe there was a way to repackage my full Titanium Backup into a zip that could be used in Factory Recovery for a restore solution? I perused the net in vain for that too.
I really don't fancy reinstalling Win 10 to fix the driver issues or trying on one of my Linux machines (I am a noob on those too).
Thanks for the answer, anyway.
In the end I managed to restore the tablet (took me 2-3 days of looking around). I'm only writing this up so others facing adb probs can solve their issues on their MTK-built devices. (Actually probably this will work on any device that is not Samsung or whatever old famous brands.)
The first thing to do was sorting out VCOM drivers. There's a Nigerian-sounding guy whose forum Hovatek I followed for tricks on how to go about it (had to download and install Virtual Serial Port Driver to sort out connection issues in Miracle Box/Thunder). Whenever you have some problem, I suggest you include Hovatek in the search string, cause chances are he has a tool and a tut.
Using Miracle Thunder and acting on Hovatek's instructions I made a copy of my firmware. All I really needed was the sytem.img, of course. My bootloader being fine (messing up your device with build.prop only results in a soft brick), it didn't need fixing. Using Assayyed's Kitchen and Hovatek's tutorial again I unpacked the system.bin I extracted with Miracle (which must be all the time used with virus protection off) after renaming system.bin to sytem.img. I exchanged the build.prop and repacked system but didn't wait for the update.zip to be made, instead I took the img file I wanted in the Kitchen. Then tried SP Flash tool to flash system.img on the device but I had issues with the scatter file. So I downloaded a firmware from Boycracked or whoever and used that scatter (in the meantime I overwrote the system.img with mine). I flashed device, turned on the tablet and voila. I hope this helps peeps out there with similar issues.
WARNING - THESE TOOLS WRITE TO THE DEVICE PARTITIONS DIRECTLY
If you don't know what that means...
THIS CAN REALLY SCREW UP YOUR ---
I HAVE ONLY TESTED THESE ON THE A2020U (NON-5G) - I CANNOT SAY THEY ARE SAFE ON ANY OTHER VERSION OF THE PHONE (YET)(If you want to test it on a specific model you own, send a PM or post and I can tell you to run a few (safe) things from these tools to make them compatible your phone.)
See my next post down for some more "beginner friendly" general tips and tricks for this phone, including some fixes for common problems and a quick guide for installing Magisk!
If you can't afford to brick your phone, these tools aren't made for you.
There aren't really any protections from doing damage. I made them for myself because doing them on a command line constantly is a pain. I'm just sharing them for two reasons:
1) So myself or other people have tools available to make it easier when advising someone on how to fix their phone.
2) For tinkerers who are okay taking the risk that they'll mess something up.
Thanks to @djkuz / @Unjustified Dev for the EDL tool. These scripts really just expand the use of fh_loader commands in that tool. If you are able to read C++ and want to understand fh_loader I suggest searching on google, the source code is available and from that you can better understand what the tool does / what the command line options do. Feel free to ask here too, I'll do my best to share what I know.
Anyway - below I'll go into plenty of detail of what each "tool" does and some helpful information about using them.
I write in a kind of permanent verbose mode, so if you're impatient and need a TL;DR for these... tough. =)
CURRENT VERSION: Version 1.1d
Changelog:
Version 1.1d:
- Fixed reset scripts
Version 1.1c:
- Fixed a typo in backup_GPT ¯\_(ツ)_/¯
Version 1.1b:
- Fixed errors in GPT_Tools - apparently these existed since v1.0 DO NOT USE PREVIOUS VERSIONS
- Removed the v1.1a download (use 1.1b)
Version 1.1a:
- Added script to find the COM port automatically
- Updated all scripts to use the COM port in the file COMPort (created by the above script)
- Added the missing AB Partition manipulation files (accidentally left out of v1.0)
- Added script to run the phone reset EDL command
- Fixed all the filename inconsistency in the XML files - HOPEFULLY. Please post any errors you find. Unfortunately this will make this version incompatible with v1.0 backups without some work - either rename your backup files to match the new format or use the old XML files included.
-- Especially fixed the XML typo of "uefi_sec.mbn" being backed up from both A and B to the same file (overwriting the A copy with B during an ALL backup).
- Added support for installing firmware packages created for this tool. Put them in the Firmware_Package_Restore directory and use the scripts included with them.
Basic Instructions:
1) Download zip (See attachment at the bottom, or here - Download from AndroidFileHost)
2) Unpack zip
3) Move folder to the root directory, or inside any chain of directories that do NOT have spaces in any of the names
4) Right-click on scripts and select "Run with Powershell" to run
5) If running scripts fails due to permissions, see these instructions: https://superuser.com/questions/106360/how-to-enable-execution-of-powershell-scripts
Make a "Complete Backup" (minus userdata):
1) Run Load Programmer
2) Run "backup_all"
3) Check the backup directory and verify the files were backed up and sizes make sense - a full backup should be 10,387,202,048 bytes / 39 files for the critical files and 1,626,697,728 bytes / 64 files for the non-critical (Don't include the port_trace log file when checking size)
Note: You will see a lot of "warnings" before the files begin to download, the program checking if the files already exist.
How to Use These Tools:
Important:
When the scripts run there will be a lot of information dumped to the console. It's not necessary to read all of that BUT - IF YOU DO NOT SEE THE ASCII ART "DONE" AT THE END of running any of these scripts it is likely the script encountered a serious issue. "WARNING" art is normal for some scripts, but "ERROR" means something went wrong.
None of these find the COM port automatically. It is possible (the EDL tool does) but it's just extra work I'm not paid to do =P
You will need to edit each program and change the variable at the top (usually $COMPort = "6") to whatever port number your phone shows up on.
Sorry that's inconvenient, but it should just be once per script - my port number never changes so it wasn't worth implementing automatic port finding.
This is no longer needed after v1.1a.
1. Load Programmer
This is a simple but extremely important tool! You need to run this before running anything else. This script will open a window that runs a command to open a connection to the phone (when it is in EDL / "9008" mode). The window will stay open until you close it. When working on backups I often need to re-connect the programmer, so this makes that easy - just alt-tab to it and hit enter. If you look at the script, it's fairly straightforward - just read the instructions on the screen after running it. The "secret sauce" for this is really the firehose protocol for our chipset that Unjustified Dev provided in the EDL tool.
2. Backup / Restore:
backup_all: This will backup everything on the phone EXCEPT for the huge userdata partition. It will create a backup in two directories, which I'll explain.."critical" / "non-critical": You can see that I have scripts to run these two "types" of backups. Non-critical DOES NOT MEAN NOT IMPORTANT. It means that it is not critical TO ME to back up those files EVERY time I do a backup, because they rarely change. They're EXTREMELY important to have at least one backup of for your phone. The "critical" backup files are files that change often, although some of them are extreme non-critical (cache for example). Use a different name than "critical" if you like, but the point is that only with BOTH backups run (which is what backup_all does) will you have a complete backup.restore_all: This will restore a full (both critical and non-critical) backup set. The backup files have to be in the "restore_critical" and "restore_non-critical" directories respectively. If you didn't make the backup you're trying to restore with this tool CHECK THE FILENAMES, e.g. if you used Unjustified's EDL tool you have to rename the "abl.elf" file his backup generates to "abl_a.elf" for mine. I put _a and _b on every partition that has an a/b version because I got tired of getting them confused. Of course you can always install a backup to either slot.Files moved to the "restore_" directories won't be changed at all by the restore process so you can cut/paste the files from your backup into the directory instead of copying them.
3. A/B Partition Manipulation
These are no more complicated than the backup/restore tools. But they are written to make manipulations of the A/B partitions easier.My main use for these is when I know I have a good, working ROM setup on slot A, I run A2B copy. Then no matter which slot I end up booting I'm sure it will work. (That is, if you have a working, booting slot, copying all the files from that slot to the other slot using this tool will make both slots the same.)Backup/Copy:run_AB-partition-backup: As it says, it will backup both the A/B partition files - WARNING this is NOT a full backup of the phone.run_AB-partition-swap: This will backup all the A/B partition files, then it will write the B files to A and A to B, effectively swapping the partitions and leaving you with a backup in case it screwed up. This backup is ONLY OF THE A/B FILES.. NOT the whole device!run_A2B-partition-copy (and run_B2A-partition-copy): These will do a backup of both A/B partition files, then write the A partition onto the B partition (A2B) or vice versa (B2A), effectively mirroring that partition.
Write/Restore:All the restore scripts try to find their files in the "restore_Partitions" directory - place the files from one of the backups to be restored there.restore_AB-partition-backup: Restore a backup of both the A and B partition files.restore_A-partition-backup (and B): Restore just the backup of one partition to the same partition it was taken from (A to A and B to B).restore_A2B-partition-backup (and B2A): These write from one partition backup to the other partition as the name suggests.
4. GPT Tools
These are some basic tools to directly interact with the partition tables - these are not going to be of any use to 99% of people, so just ignore them if you don't know what they do.run_fixGPT: This issues the --fixgpt command to each of the LUNs. USE AT YOUR OWN RISK. As I understand it, this will use the onboard device configuration information from each LUN (e.g. logical size) and try to rebuild the GPTs. It's similar to running patch XMLs, it can clean up flashing messes. It isn't magic and won't fix everything.Rarely will anyone need it unless they've been messing around with the flash tools recklessly... I certainly don't know anyone who would do something that dumb backup_GPT: Backup all of the header and footer (main/backup) GPTs for all the partitions (lun 0-5). I am not aware of whether any other models of the phone have more LUNs, so be careful if you're using this on a non A2020U phone.restore_GPT: Simply write an entire GPT backup set (both main and backup 0-5) onto the phone. The backups must be in the restore_GPT folder. This DOES NOT BACKUP before it runs so make sure you did your backup.
6. Set Bootable Partition:
Alright this one is important for everyone. There are two scripts here - one for slot A and one for slot B. These just run a simple command, but they will fix a common problem I (and probably others) have - when the ROM active-slot information does NOT match the partition (hard drive) bootable flag, the phone will bootloop EVEN THOUGH EVERYTHING IS GOOD.So when you flash an EDL backup (depending on which files you flash, I believe this happens because of either the bootloader or the GPT files) there is a chance the backup you're flashing was originally from a different slot than the one you're restoring it to. The config thinks it should be on slot A while the hardware thinks slot B should be booting.This will result in a fast ~3 second bootloop as the two disagree and reset.This tool changes which partition is expecting to boot - "1" for slot A and "2" for slot B.This does NOT change the active slot - the phone will continue to boot the same slot it's trying to boot. You just need to make the partition that it is trying to boot has a bootable flag.AFAIK there is no way to change the active slot (the one XBL (I think) is trying to boot), except through fastboot or when the phone fails to load the OS 8 times in a row (note - if it fail to load the OS - if the phone bootloops before "boot" is called it won't ever switch slots on its own).This was a common cause of fast bootloops for me before I figured this fix out.
It does no harm to try this as you can always switch again. If neither one works for you, then it's something wrong with the files you're flashing. If you know which slot the phone is trying to boot (the one it was on last), run the script that matches that slot.
7. Write "Unlocked" Bootloader and FRP:
Just like the original EDL tool, these very simply overwrite your existing (probably stock) bootloader (abl) files with the fastboot enabled version, and/or your FRP with the "unlocked" flag on (see description below). This will allow you to enter the bootloader menu (Vol+/- on booting) and use fastboot to unlock the bootloader.backup_FRP-and-bootloaders: As it says, this will make backups of both the FRP file and current bootloader files (ABLs).run_all: Literally just runs both of the below scripts *shrug*write_UD-bootloader: This automatically backs up both your existing A/B bootloaders before overwriting them (BOTH) with the unlocked/fastboot bootloader.WARNING - an unfortunate fact is that if you're using the stock ROM and you have this bootloader installed, it borks the USB mode so it's stuck in charge only. There's a way to fix it temporarily, I'll post it in my "tips" thread, but you have to do it every time you boot, very annoying. I can't fix it permanently because I don't know how the bootloader file was built!WARNING 2 - Android 10 will NOT BOOT with this bootloader installed. You can still install it, trying to boot will bootloop, but you can get into the bootloader menu and use fastboot - but there are no recoveries I know of that work with Android 10 right now, so there's very limited use to having fastboot right now. Hopefully we can get a port of TWRP 3.4 going for this phone..write_unlock-frp: This is also in the EDL tool, but maybe poorly explained - the FRP file holds the flag you change in the OS Developer Options to designate "allow bootloader unlock". If you FORGOT to switch that flag on and unlock, as I understand it, you get bootlooped. This can fix that for you without having to go through all the work of undoing that mess.WARNING - I have only tested this with a brand new factory reset OS WITHOUT any fingerprint/code set. It may not work if you set one. I warn against using this if you are not ready to lose your data. It's convenient if you just forgot, but if you set a pattern/fingerprint security and encrypted the filesystem overwriting the FRP might remove your ability to decrypt which would force you to factory reset. Again, I haven't tested it for that so it may work, but be careful.If you already screwed up and ran this to set the flag - the script runs a quick backup of your old FRP just in case. So you can try to restore that FRP and pray lol)
8. Specific Files:
This is just a generic program to backup/write(restore) "specific files".I include a "Reference.XML" which has a full <program> line for every partition you might want to write/read on the phone. To use this, you need to copy the lines from the reference XML into "rawprogram-specific-files.xml" for the files you want to read/write.As an example I already set up "rawprogram-specific-files.xml" with the two lines for "abl_a" and "abl_b" in it. So the script will backup or restore those files (provided you put the abl's you want to restore in the restore_files directory).I personally use this template a lot - I have one for ABLs, one for AOPs, one for BOOTs, and so on. If you are trying to fix a specific file(s) it's convenient.
9. Userdata Backup:
I put this last because, to be honest, I'm not sure how good of an idea including this even is.VERY IMPORTANT - DO NOT USE THIS USERDATA TOOL IF YOUR PHONE IS NOT THE 256GB VERSION!!!!!I will need someone with the 128GB version to send me their GPT files if they want me to make an XML that works for them. Because the userdata size for SURE depends on your phone version.Also, I wrote a script that breaks up the file into download slices (and can be written back to the phone in slices, of course) - one, to see if I could do it and if it would work (it does)... and two, so that in the horrible case that something goes wrong during the... nearly 2hrs of transfer time, for my 256gb image ... that I can at least not have to start all over. If something happens, you should be able to remove the entries in the XML for what you already have and start again.Finally - is it even worth doing? Is backing up the userdata even useful?I don't know yet.For an unecrypted pre-A10 phone I do know it works to fully flash ALL the files on the phone + the userdata all at the same time to return the phone to the exact "state" it was backed up in - all the apps and settings and everything, exactly as they were.But A10 is encryption enabled always, and it uses file encryption which sounds even worse for this idea.. and I don't know if the crypto keys change and when. So flashing an entire encrypted partition might just leave you unable to decrypt all, some, or none and you lose everything.OR it might just work - you throw the whole image on there and the decrypt key is the same, boom, easy backup.If anyone tries it, let me know how it goes (or doesn't). I'll update with any results I find.Update 1: I have confirmed that for the 256gb A2020U backing up the full phone and userdata allows you to restore the phone to that exact state. Doesn't matter if it's encrypted, password set or not, etc. If you backup the entire userdata image and reflash it that is where the phone will be. In most cases you also need all the other partitions too, but if they have not changed they don't have to be reflashed. (I confirmed going from encrypted with password -> encrypted with no password -> back up encrypted with password.. This is on Android 10 with its more complicated encryption).Another nice thing to note - of course the image of the phone will be the size of the partition (ie. 256gb for mine, 128gb for others). But if your phone storage is largely empty, you compress the backup using something like 7z once the image has been backed up. It won't take up so much space then. How much less? My 256gb image compressed is 4.5gb. lol.... it makes sense, the phone is new and there's basically no information on the userdata. Many of the pieces of my userdata backup have the same exacty hashes - meaning they are literally just all 0's... 260gb of zeros. Unfortunately you can't get away with just backing up part of the image as data could be anywhere. And over time as the sectors get written to, it will get more difficult to compress.Anyway, if anyone has a 128GB version they want to donate to science (kidding - I just need backups of the GPT) I can make the XML file to use for backing those up too.
Extra Note: All the programs automatically build a log of the console window, so if something goes by too fast just check the log. The fh_loader also creates a log and dumps it somewhat randomly about... lol.. the filename is port_trace.txt. This tends to get deleted and overwritten easily so if you want to keep it, move it when the script finishes,. it does often contain more information than the console shows - it can be useful understanding what's going on.
Extra Note 2: You'll notice a script "Create Hash List" in practically every directory. That's to strongly hint that using that script is super useful. All the files backed up through these tools, by definition, have the exact same size. If you hash your files though, you can tell if they have changed at all. This is extremely useful in troubleshooting problems.
How to install an EDL firmware package:
Note: This tool is specifically made for the firmware packages I posted. It won't work with any other package (although it can, with a little work).
1. Install the EDL tools
2. Run a backup of your phone! Even if it isn't booting.
3. Download a firmware package from this thread: [ROM][STOCK] Stock Firmware Packages (For Expanded EDL Tools)
4. Unpack the firmware archive into the tool directory "Firmware_Package_Restore"
5. Put phone in EDL mode and run Load Programmer
6. Run whichever "Write Firmware vX to Y.ps1" you want (X = firmware version, Y = A or B partition) (If you don't know which partition is currently booting, just install both.)
7. Wait for the install to finish ("done"), then reset the phone with either the power button or the reset tool
8. You might see a few bootloops and then the phone ask you to do a factory reset / system wipe.
9. Done.
PLEASE POST IN THE FIRMWARE THREAD _NOT HERE_ IF YOU RUN INTO ANY ISSUES!
Enjoy!
Also, while I'm here... some other helpful notes for this phone:
-------------------------------
General Information:
As of right now there are a lot of working options for Android 9 and quickly expanding thanks to work @Unjustified Dev did and work @rafyvitto is continuing to do! Check out some of his sGSI ROMs, lots of options!
Thanks to Unjustified LOS 16 is available for Android 9 also, and is the base install for most ROMs. See his threads for that. I may write up an install guide here that's a little more in depth than his.. not today though.
Upgrading to Android 10 with the bootloader unlocked is possible but requires a workaround:
You must unlock on Android 9 then use recovery to side-load the Android 10 update available from ZTE USA (HERE).
This will remove the fastboot enabled bootloader and requires a complete system wipe.
You will retain bootloader unlock.
Once you have updated to A10 you can run OTA updates to get up to the latest version.
Downsides to A10 include - NO RECOVERY (yet), NO CUSTOM ROMs (yet), and if you flash the fastboot enabled bootloader you CAN use fastboot, but you cannot boot- the phone will be in a bootloop until you restore the stock A10 bootloader.
-------------------------------
Resetting the phone manually:
In EDL Loop - Hold power for 20 seconds
In EDL Not-Looped - Hold power for 5 seconds
In System (booted after ZTE logo) - Hold power for 10 seconds
----------------------------------
Entering Modes:
All of these start by using reset above, THEN the button(s) below - in all except one case (EDL), when the phone resets it will vibrate and then show the blue ZTE logo.
When you feel the vibration you want to immediately release the power button and press the mode buttons.
This can be confusing and tricky - most people say "hold power + button" - that is incorrect. Most cases if you hold any button other than power the phone will not finish resetting until you release that button.
What you want to do is right before or as the phone vibrates, then you hold the button. Once the ZTE screen is up it is probably too late if you missed it. So hold power for your reset and be ready to push the button you want when you feel the vibration.
The one exception - EDL mode. For EDL mode you can (and must) hold the key combo just before/during the restart.
Recovery Mode: Vol+ Button
Factory Test Mode: Vol- Button
Bootloader/Fastboot Mode: Vol+/- Button (both) when phone is NOT plugged into USB (if you are too early pressing the combo, even with the USB unplugged, you will get EDL mode)
Emergency Download Mode: Vol+/- Button (both) when phone IS plugged into USB
--------------------------------
EDL Flash Errors (esp. when EDL looped):
There is NO indication the phone is even ON when you are EDL stuck/looped. Other than when you plug into the computer with the right drivers it shows up as a 9008 device (9008 mode is EDL for Qualcomm).
Even when you can see the phone on your computer, it can often "freeze" in EDL if it is left idle for too long (not connected to and being used by a Sahara programmer).
If you try the EDL tool or another flash tool and they give you errors related to the Sahara programmer not loading or no "hello", do this:
Reset the phone - use a clock to count if you need, has to be accurate since there's no indication of when it resets. Press down Vol+/- and the power button, count to 20sec, then release JUST the power button. Keep holding both of the volumes for another 5 sec, then release them. That will get you back into a fresh EDL. You can watch your Device Manager to see the phone disconnect as an indicator when to let go of the power button. If you mess up the timing, wait a bit before trying again so the phone isn't in the middle of rebooting.
Easiest way to tell if you're in EDL is to watch the Device Manager while you do it. Otherwise there is just a lot of guess work, since there's no logo or vibration when you get it right, phone just appears off.
--------------------------------
USB Mode Stuck After Unlocking:
Something about the fastboot/"unlocked" bootloader causes the USB mode when you boot in the OS to be stuck on "Charge Only" mode.
Luckily I found @meow sir 's comment tucked away in this thread, and he knew a way to fix it (thanks!):
1. Open the phone dialer
2. Dial in "*#*#DEBUG#*#*" (debug = 33284)
(Sometimes takes a little bit to open, but a debugger menu will open)
3. Select the 2nd option for USB
4. Pick the only option - this will unset some strange "testing" mode and you can use MPT again.
Unfortunately this fix doesn't stick, you have to do it every time unless you switch back to the stock ABL. =(
--------------------------------
Installing Magisk, Quick Guide:
- You must have your bootloader unlocked already! This works on both A9 and A10.
1. Use this tool to create a full backup! (backup_all)
2. Go into the "critical" directory created by the backup and find the files for boot_a.img and boot_b.img - rename them to boot_a_bak.img and boot_b_bak.img and keep that window open, need them in a second
2. Boot into the OS. Download the Magisk Manager APK from HERE
3. Copy the APK and both of those boot files to your phone, open a file manager and install the APK
4. Open Magisk Manager and click on "Install" for Magisk (upper right)
5. Select "Patch Boot ROM" (or whatever it says.. something like that..)
6. Navigate to boot_a_bak.img and patch it.
7. Go to your Downloads directory (where Magisk dumps the patched file) and rename it to boot_a_magisk
8. Go back to Magisk and repeat those steps for boot_b
9. Copy the two patched Magisk boot files to your computer, into the folder with your "critical" files backup.
10. Rename the Magisk files to "boot_a.img" and "boot_b.img"
11. Move all the files from the "Backup\backup_all-critical-(...)" directory to the "Restore\restore_critical" directory in my tools
12. Finally, reboot into EDL.. almost there!
13. Run "restore_all-critical" (don't forget to run Load Programmer first..)
14. It will restore all you files, kinda a waste of time - if you know how to use the "Specific Files" tool this is a perfect time to use it to flash JUST the boot files. But anyway - this will get it done.
15. When done flashing, reboot the phone and open Magisk Manager to confirm it is installed!
The Magisk team recommend you DO NOT FLASH your stock boot files back to uninstall it, instead they say you should run their uninstaller.zip. However, I am not sure how to uninstall it if you're on A10 since we don't have a recovery that can flash zips? (Unless the stock recovery works for that, I don't think it would..)
I suspect (but have not tried) that on our phone flashing the boot files back over Magisk will not really be a problem since the recovery and ramdisk are all wrapped up into the boot image. But I don't recommend trying it if you value your data! Fair warning.
---------------------------
Alright that's everything. Good luck!
This will be useful for a lot of folks on here, thanks for taking the time to look for a work around.
rafyvitto said:
This will be useful for a lot of folks on here, thanks for taking the time to look for a work around.
Click to expand...
Click to collapse
Glad to be helpful! Usually I lurk the forums getting information I need to unlock/root/etc lol.. but I saw I actually could contribute something to this forum so hopefully it encourages people to get interested in this phone. It's looking pretty sweet now that I'm not spending days fighting with bootloops!
Indeed,on the note of attracting more users. im going to be releasing something for the pixel lovers very soon ?
Thanks Bob!
I'm on A10 with unlocked bootloader. I made all EDL tool backups when on A9 but these were done before correcting the typos as suggested. So I am not confident of successfully flashing back to A9 (preference).
Therefore I will likely flash the magisk-patched boot files to attempt root and report my experience...
Sent from my ZTE A2020U Pro using Tapatalk
big thx, glad to see some life to this almost dev-dead device
Hey thanks for the post. I'm thinking about buying the phone but have a quick question. Can I update to the latest version of Android 9 before unlocking or will the OTA be Android 10. How would I go about updating to the latest version version of Android 9 and not go to Android 10. Can I download the Android 9 OTA from somewhere and flash that one? Thanks in advance for the help!
Crackass said:
Hey thanks for the post. I'm thinking about buying the phone but have a quick question. Can I update to the latest version of Android 9 before unlocking or will the OTA be Android 10. How would I go about updating to the latest version version of Android 9 and not go to Android 10. Can I download the Android 9 OTA from somewhere and flash that one? Thanks in advance for the help!
Click to expand...
Click to collapse
:good: I think your question borderlines on needing its own thread in the Q&A section but I'll answer you anyway...
Currently as long as you are on A9 when you get the phone you can just do OTA updates from firmware version 1.10 to 1.11 to 1.13 (not sure what android security update that is), after 1.13 it goes to A10.
There is an A10 firmware available from ZTE to SD card sideload. Once installed it has to be updated to the latest A10 via a couple OTA updates.
Going directly from A9 to A10 via OTA goes directly to the latest version.
You cannot flash the A9 OTA... because flashing an OTA is an oxymoron... but I guess you mean can you download the A9 firmware and flash them. The answer is... maybe. ZTE does not offer official downloads any A9 firmware for A2002U (USA version), only A10.
They do offer A9 firmware for A2020G (european) and I think other foreign versions (RU, CN). These cannot be interchanged, if you have the US or EU or CN phone you need to use that firmware... from what I have read. I could be wrong, I don't have those phones.
But there is an unofficial stock A9 firmware for the A2020U here on the forums, uploaded by @rafyvitto . That will get you to.. I forget.. 1.11? That can be flashed using the original EDL tool or, with a little modification, the EDL tools in this thread.
Additionally.. if I ever get around to it... I plan to upload all three A9 firmware packages for the US version which can be flashed with the EDL tools in this thread. Not sure if it's really necessary, but I have them.. it's just a matter of figuring out hosting them and spending the time to upload them.
bobthenormal said:
:good: I think your question borderlines on needing its own thread in the Q&A section but I'll answer you anyway...
Currently as long as you are on A9 when you get the phone you can just do OTA updates from firmware version 1.10 to 1.11 to 1.13 (not sure what android security update that is), after 1.13 it goes to A10.
There is an A10 firmware available from ZTE to SD card sideload. Once installed it has to be updated to the latest A10 via a couple OTA updates.
Going directly from A9 to A10 via OTA goes directly to the latest version.
You cannot flash the A9 OTA... because flashing an OTA is an oxymoron... but I guess you mean can you download the A9 firmware and flash them. The answer is... maybe. ZTE does not offer official downloads any A9 firmware for A2002U (USA version), only A10.
They do offer A9 firmware for A2020G (european) and I think other foreign versions (RU, CN). These cannot be interchanged, if you have the US or EU or CN phone you need to use that firmware... from what I have read. I could be wrong, I don't have those phones.
But there is an unofficial stock A9 firmware for the A2020U here on the forums, uploaded by @rafyvitto . That will get you to.. I forget.. 1.11? That can be flashed using the original EDL tool or, with a little modification, the EDL tools in this thread.
Additionally.. if I ever get around to it... I plan to upload all three A9 firmware packages for the US version which can be flashed with the EDL tools in this thread. Not sure if it's really necessary, but I have them.. it's just a matter of figuring out hosting them and spending the time to upload them.
Click to expand...
Click to collapse
Just wanted to chime in, interchanging firmware between each model is possible, you would only need to reflash your model/nonhos/tz partitions to the ones of your variant to have working ril/fod fp/sensors.
Ok Bob I gave it a go and successfully rooted my A2020U running stock A10 v2.09. This is my experience...
Firstly, my A2020U could not connect so I used the @Unjustified Dev Tool ("original tool") to easily determine my com port (i.e. 3). I edited the your scripts accordingly (using Notepad++) and got connected.
I'd rather not fiddle with the hardware buttons to change modes so I used the CLI to "adb reboot edl" to get into EDL mode.
I executed the backup_all.ps1 script.
It echoed several "warnings" indicating that it could not find files. However, the created backup folders did in fact include those files.
I noted that none of the "A" slot files include the "_a" postfix; the "B" slot files did include "_b".
Now I needed to transfer those boot files to my device by first rebooting my device and connecting via MTP.
I noted that the original tool offered a reboot menu option (but sadly only after executing a successful operation). So, not wanting to fiddle, I used the original tool to backup my boot files, then used the menu option to reboot; On my device I then manually selected it to connect via MTP.
After transferring the "boot.img" and "boot_b.img" files to my device, and installing Magisk Manager. I patched them and transferred them back to my PC.
To "flash" (restore) the patched files I decided to cut 'n' paste the two lines regarding them from your Reference.xml file into your rawprogram-specific-files.xml file, replacing your example lines.
I executed your run_write-files.ps1 script and it completed successfully.
Not wanting to fiddle again with the hardware buttons (just so that I can get the reboot option), I backed up the patched files using the original tool and rebooted. Now my device is successfully rooted.
Thank you!
Additional notes and suggestions:
1. Can you please investigate the "false" warnings? See my (redacted) log file attached;
2. It would be great if you could create/duplicate a script within your expanded tool set (or main program) to determine and set the appropriate COMPort (and teach us non-coders the actual commands);
3. Would you also consider investigating and including a reboot device script? (It looks like the original tool calls reset.xml);
4. Note that, at the time of reporting this, the latest versions for the Manager and Magsk are 8.02 (307) and 21.0 (21000) respectively, and that I had to switch the update channel to "beta" for the patched files to pass SafetyNet;
5. Because rooting is a likely use of your tool I am attaching my modified rawprogram-specific-files.xml file which targets the boot files for convenience.
bobthenormal said:
...
Additionally.. if I ever get around to it... I plan to upload all three A9 firmware packages for the US version which can be flashed with the EDL tools in this thread....
Click to expand...
Click to collapse
If this can help me get my A10 device to a state where I can install a custom recovery and cutom ROMs, I would appreciate it!
eKeith said:
Ok Bob I gave it a go and successfully rooted my A2020U running stock A10 v2.09. This is my experience...
Firstly, my A2020U could not connect so I used the @Unjustified Dev Tool ("original tool") to easily determine my com port (i.e. 3). I edited the your scripts accordingly (using Notepad++) and got connected.
I'd rather not fiddle with the hardware buttons to change modes so I used the CLI to "adb reboot edl" to get into EDL mode.
I executed the backup_all.ps1 script.
It echoed several "warnings" indicating that it could not find files. However, the created backup folders did in fact include those files.
I noted that none of the "A" slot files include the "_a" postfix; the "B" slot files did include "_b".
Now I needed to transfer those boot files to my device by first rebooting my device and connecting via MTP.
I noted that the original tool offered a reboot menu option (but sadly only after executing a successful operation). So, not wanting to fiddle, I used the original tool to backup my boot files, then used the menu option to reboot; On my device I then manually selected it to connect via MTP.
After transferring the "boot.img" and "boot_b.img" files to my device, and installing Magisk Manager. I patched them and transferred them back to my PC.
To "flash" (restore) the patched files I decided to cut 'n' paste the two lines regarding them from your Reference.xml file into your rawprogram-specific-files.xml file, replacing your example lines.
I executed your run_write-files.ps1 script and it completed successfully.
Not wanting to fiddle again with the hardware buttons (just so that I can get the reboot option), I backed up the patched files using the original tool and rebooted. Now my device is successfully rooted.
Thank you!
Additional notes and suggestions:
1. Can you please investigate the "false" warnings? See my (redacted) log file attached;
2. It would be great if you could create/duplicate a script within your expanded tool set (or main program) to determine and set the appropriate COMPort (and teach us non-coders the actual commands);
3. Would you also consider investigating and including a reboot device script? (It looks like the original tool calls reset.xml);
4. Note that, at the time of reporting this, the latest versions for the Manager and Magsk are 8.02 (307) and 21.0 (21000) respectively, and that I had to switch the update channel to "beta" for the patched files to pass SafetyNet;
5. Because rooting is a likely use of your tool I am attaching my modified rawprogram-specific-files.xml file which targets the boot files for convenience.
Click to expand...
Click to collapse
Nice! :good:
For the questions..
0. Thanks for the heads up on filenames! I completely missed that the _a files don't have the labels... As you probably noticed all the files are backed up correctly still (no missing/overwritten files), but I removed the _a from all the A slot files. That was my original "fix", so I guess I started building this package before I got annoyed by not having the _a/_b consistency. I'll update the correct XML file and upload it as a new version.
1. Don't worry about those! They're part of using the fh_loader interface. Warnings are usually just fine, ERRORS are bad. I'll add a note to the post when I get a chance so people don't get scared by that.
It's only when you do a backup the program is really only designed in the "writing" sense, for backups you literally run an identical XML to writing but you send a flag that reverses the process. So it weirdly checks if the files it is going to copy (which of course don't exist) exist, and it throws the standard warning, but then it just creates them (of course).
I can't turn those off without lowering the verbosity setting for that tool. I decided to leave it set to high because if someone has a problem and they post their log file (like so!) it's very useful to troubleshoot.
2. I'll think about it / try. Not very hard to program but a little time consuming.
I'll throw a copy of lsusb.exe in the next version. Windows port of the linux command. People can simply run that on a command prompt and it will list all the active COM ports/devices. If you're not familiar with it - you can also find out by clicking on the windows start bar or pressing the windows key and typing in "Device Manager". In the hardware list there is a category for COM ports where it lists them.
3. Yeah that's very easy I'll put one in the next version as well.
4. Helpful to know. Interesting that you needed beta to pass... I didn't think to mention I use the canary builds (not really recommended... the current one crashes when I try to hide Magisk Manager lol)
5. Thanks! Maybe I should make a directory specific to boot backup/write... but I do think anyone not comfortable doing the change you did might not want to be flashing their boot files anyway haha.. things to consider I guess.
As for getting you back from A10, definitely. I'll figure out how to upload them to one of those file sharing sites in a week or two.
In the mean time, with a backup from this tool you're safe (as far as bricking goes, you'll have to system wipe) to try rafy's EDL backup to revert to A9. I'll find the actual post... I should have been less lazy and linked it in my post lol... HERE - rafyvitto's EDL.
If flashing his backup doesn't boot right away try the tool I included to fix the bootable partition. If it still doesn't work after that (maybe mention here what happened) then just restore your backup.
Do you have the 128gb phone by chance?
Thanks much, especially for your detailed clarifications and convenient link!
I have the 8/256GB (P855A03_NA) model.
PS
I want to spend more time on ensuring I have a complete device backup before nuking with another EDL; will dedicate some time this week...
Sent from my ZTE A2020U Pro using Tapatalk
eKeith said:
Thanks much, especially for your detailed clarifications and convenient link!
I have the 8/256GB (P855A03_NA) model.
PS
I want to spend more time on ensuring I have a complete device backup before nuking with another EDL; will dedicate some time this week...
Sent from my ZTE A2020U Pro using Tapatalk
Click to expand...
Click to collapse
Oh nice, with the 256gb model you're good to use the userdata backup program too. Sounds ideal for you since, like me, you want a really bulletproof backup. If you run a full backup and then run the userdata backup you literally have a "phone state" so you can return your phone back to exactly where it was, not have to wipe system or anything.
Of course I'd hate to be wrong so as usual, do at your own risk! Lol. But I am using that method and it has worked great. The downside being over an hour of waiting for the userdata to download or upload... and having to store 256gb (for long term storage you can compress it down to literally a few gb).
I've been kinda busy, but working on getting some of those things from my last post done hopefully this week.
bobthenormal said:
Oh nice, with the 256gb model you're good to use the userdata backup program too. Sounds ideal for you since, like me, you want a really bulletproof backup. If you run a full backup and then run the userdata backup you literally have a "phone state" so you can return your phone back to exactly where it was, not have to wipe system or anything.
Of course I'd hate to be wrong so as usual, do at your own risk! Lol. But I am using that method and it has worked great. The downside being over an hour of waiting for the userdata to download or upload... and having to store 256gb (for long term storage you can compress it down to literally a few gb).
I've been kinda busy, but working on getting some of those things from my last post done hopefully this week.
Click to expand...
Click to collapse
That's great to know! Your user data backup option has simplified my life.
I will wait for your next revision to do a full backup plus user data before nuking.
I am looking forward to moving on from ZTE's A10 to one of Ray's ROMs...
Sent from my PH-1 using Tapatalk
Updated to 1.1a - kind of had to rush on some things so keep an eye out for mistakes, especially in the XML files, and let me know if you find any.
Should have an 1.09 (A9) firmware package up "Soon(TM)", just have to make the xml files then upload the file somewhere.
EDIT: Already needed to update to 1.1b - I found that the GPT_Tools had a big error that probably was there since 1.0 and no one noticed! Backups of the GPT should now actually work...
Thank you @bobthenormal !
Looking forward to your A9 EDL backup...
Sent from my PH-1 using Tapatalk
eKeith said:
Thank you @bobthenormal !
Looking forward to your A9 EDL backup...
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
It's up -- see the new thread.
I didn't have time to test it so make sure you backup but I'm 99,99% sure it will work. I tested it several times in the past, but to make the firmware package I took out all the (I hope) unnecessary files.
There's one thing I'm not sure of - whether you'll need to use the Fix Bootable tool after installing it. IF you need to, then I believe you will have to install it to partition B and then run fix bootable B. (The 1.10 backup was taken originally from the B partition).
If you find that it works without having to do that, let me know... it may not be necessary if wherever that bootable flag is stored didn't get included in the firmware package.
bobthenormal said:
It's up -- see the new thread.
I didn't have time to test it so make sure you backup but I'm 99,99% sure it will work. I tested it several times in the past, but to make the firmware package I took out all the (I hope) unnecessary files.
There's one thing I'm not sure of - whether you'll need to use the Fix Bootable tool after installing it. IF you need to, then I believe you will have to install it to partition B and then run fix bootable B. (The 1.10 backup was taken originally from the B partition).
If you find that it works without having to do that, let me know... it may not be necessary if wherever that bootable flag is stored didn't get included in the firmware package.
Click to expand...
Click to collapse
Thank you @bobthenormal !
I should be able to give it a go this weekend and inform...
Sent from my PH-1 using Tapatalk