SO sorry this is so long, but the more detail I give the better, right???
I've had this phone only 2 months and managed to get myself into a pickle, but no crying...I KNEW this was possible. Here's what I have, and managed to get...
ZTE Quest 5 (MT6739, government phone,)
Android 9, (Magisk Rooted, more below,)
I did a lot of research, and managed to get a temp root shell and then (from freshly flashed system,) did a dd for all the partitions in .img files, (except userdata, it was huge,) there were 38 of them, I'll list those below. Then I went for the Magisk systemless root solution, which worked very well with the Magisk on the recovery partition. Rebooted 4-5 times to make sure everything was all right, on to the next step...
THEN I installed a couple of Magisk modules...the DeBloater, BusyBox, Termux, and a backup module. I uninstalled the bloat using the Termux (with root) and the DeBloater in the Magisk Manager, Then used the BackUp module which made copies of the same partitions I'd done before...and I still have them. THEN, Rebooted...
The unit rebooted to fastboot....and I wasted 30-45 minutes trying to get it to reboot back to the system, or recovery, or even EDL mode (not sure if it has that though,) BUT it kept going back to fastboot....
SO, I went to work, (I'd unlocked the bootloader while Magisk rooting,) I used the original system.img and fastboot erase system....THEN fastboot flash system.img...good, still no reboot back to system, only fastboot...DAAAAMMIT!!!
SO
Fastboot erase recovery...ok...fastboot flash recovery.img....okay.
STILL nothing, back in fastboot...SO fastboot erase boot...okay...PHONE TURNS OFF, BATTERY DIED!!!!!
I didn't realize that in fastboot mode the unit wasn't charging!
NOW the batter y is chargable, I managed to get something figured out...and the phone turns on, shows the ZTE logo a few seconds and then turns back off....
FOLKS, my wife is beyond P&^*ed! So I GOTTA fix it... Here's the partitions I have dd'ed (I assume the MM backup DD'ed too, but that BU was after the system was modded...)
boot
cache
carrier
dtbo
expdb
flashinfo
frp
gz1
gz2
lk
lk2
loader_ext1
loader_ext2
logo
mcupmfw
md1dsp
md1img
metadata
nvcfg
nvdata
nvram
para
persist
proinfo
protect1
protect2
recovery
Recovery-from-boot.p (don't ask why I did that,)
sec1
seccfg
spmfw
system
tee1
tee2
vendor
ztecfg
I'm not sure how to proceed now, I've been trying in Windows 7 AND Linux tp build a ROM, but this is seeming to be difficult.
Non-A/B, but is supported. It's in the build.prop...
System-as-root?!? Not sure, but when I extracted the boot and recovery images the boot ramdisk was empty, and the recovery ramdisk had a bunch of stuff in it. I've also extraxted the system.img...LOADS od stuff in there to play with, but first...
I NEED help (guidance, and I already have several unpacking/packing and kitchens...but coan get others if they are better suited, nothing I've built so far is recognized by the WwR_MTK tool, (it's supposed to be able to extract a scatter for the SP Flash Tool from a ROM,)
ANY help with getting the scatter would be massively appreciated too!!!
Best case
If you will post your stock recovery.img and lk.img I might be able to help.
I want to port my gionee f205 stock rom to gionee f205 pro stock rom. Both are MT6739 chipsets. But F205 pro stock rom is oreo and the older F205 is Nougat. Now I can't find /system/vendor folder in the new PRO ( I think it is because treble enabled as it came out oreo out of box). It also doesn't have a firmware folder in /system/etc and many files in /etc and /lib are also not found.
1. How should I replace the missing files in new one
2. Should I copy the vendor folder to the vendor.img of the new PRO's stock rom.
3. After I finish porting should I only flash the system.img or the whole stock rom?
Related
Update:
I was able to use this method to root the new ICS update. The thread has been edited accordingly.
----------------------------------------------
I was unable to find a single thread that detailed how to root the stock T-Mobile Springboard firmware and keep the boot and recovery partitions intact to allow future updates, so I have consolidated information from other threads and posts, as well as adding a little myself. Full credit goes to the users and thread OP's referenced in the post links below.
The usual warnings apply: Under no circumstances should anyone do this to their device. You are likely to brick your device and render it completey unusable. In addition, you will void your warantee with T-Mobile. So you will have an out-of-warantee brick instead of a nice, functional tablet. Turn back now while there is still time.
Before you begin, I obviously did this to my device without any problems. My device is running full stock T-Mobile Springboard firmware with the following:
Android version: 4.0.3
Baseband version: 314007
Kernel version: 3.0.8
Build number: S7-303uV100R002C201B035
I do not know if it will work on a device with any other version of the firmware. The following also assumes that you have fastboot and ADB installed and functional on your computer.
In describing how to boot into fastboot and recovery modes below, the description of the volume buttons is how they are while in portrait mode in Honeycomb....as this is where I first used this method. In other words, the volume button closer to the power button is volume up and the other volume button is volume down.
1. Download the CWM Recovery image from this post:
http://forum.xda-developers.com/showpost.php?p=23601045&postcount=7
2. Download CWM-SuperSU-v0.95.zip from this post:
http://forum.xda-developers.com/showpost.php?p=27678611&postcount=22
3. Copy the CWM-SuperSU-v0.95.zip file to an sdcard and put the card in your device.
4. Flash the CWM recovery image to your first recovery partition ONLY:
a.) Boot into fastboot by powering down the device and starting it back up by pressing the
volume up and power buttons at the same time. After the device vibrates, release the
power button but keep holding the volume button until it is booted into fastboot.
b.) Once in fastboot, flash the recovery image:
Code:
fastboot flash recovery recovery5.5.0.4.img
5. Press and hold the power key for 10 seconds to reboot the device. It will boot into the
T-mobile firmware.
6. Power down the device in the usual fashion.
7. Boot into recovery by starting the device back up by pressing the volume down and power
buttons at the same time. After the device vibrates, release the power button but keep
holding the volume button until it is booted into CWM Recovery.
8. Choose 'install zip from sdcard' -> 'choose zip from sdcard', then select the
CWM-SuperSU-v0.95.zip file you put on your sdcard above, then confirm installation.
9. Go back to the main menu and select 'reboot system now'. It will boot into the T-Mobile
firmware.
10. Shut the device down again in the usual fashion, then restart normally and boot into the
T-Mobile firmware again.
11. Now you need to get your stock recovery partition back and get rid of CWM recovery.
There are two copies of the stock recovery- one on each 'recovery' and 'recovery2'. You can
get back to stock recovery by extracting an image from 'recovery2' and flashing it back to
'recovery'. The following (using adb from your computer) will dump the image from recovery2
to your sdcard:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/mnt/sdcard2/recovery.img
12. Take the sd card out of your device and copy this file back to your computer, then flash the
first recovery partition with this image as in step 4b above, but with your new recovery.img file.
You are now rooted and your recovery partitions are returned to stock.
Once you are rooted, if you would like to remove some of the T-Mobile bloatware note that the apk files are not in the usual location (/system/app). I found them tucked away in the following directory:
/data/cust/app
Of course, you will need an app like Root Explorer to get to them and delete them...or you can just use adb. I deleted several of the apk files in that directory, rebooted, and everything is working just fine...with less bloatware.
Also, be aware that any changes you make will be permanent. I tried hard reseting the device through the usual android settings menu security method, and I kept root and all of my deleted bloatware was still gone after it finished and rebooted. There does not appear to be a way to get all of your stock stuff back once you start deleting things...so make backups of files before you delete them in case removing them causes unexpected consequences.
Just to add another bit of information - a list of what I believe are the internal partitions and their locations appears below. I got this from the output from 'cat /proc/partitions' and 'mount', as well as further inspection of the stock recovery image that I extracted from my device. As we don't have a functional CWM Recovery, and I am not sure that I would use any version that was built for the Mediapad (i.e. non-Springboard) for backup and restoring, this list should give Springboard users a way to back up their devices. Using the 'dd' command as in the coding box at the bottom of the OP for each of the paritions should result in a partition image stored out on the sdcard. Fastboot then should be able to flash these 'backed up' images back to the device as in step 4b of the OP...with the correct partition names and backup files substituted of course. I did do this for the recovery partition as I detailed in the OP, but have not tried it for the rest of the partitions.
Code:
/misc emmc /dev/block/mmcblk0p14
/vrcb emmc /dev/block/mmcblk0p16
/recovery emmc /dev/block/mmcblk0p17
/recovery2 emmc /dev/block/mmcblk0p18
/boot emmc /dev/block/mmcblk0p19
/system ext4 /dev/block/mmcblk0p20
/cache ext4 /dev/block/mmcblk0p22
/cust ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p27
/tmpdata ext4 /dev/block/mmcblk0p23
/persist ext4 /dev/block/mmcblk0p21
/tombstones ext4 /dev/block/mmcblk0p24
/firmware ext4 /dev/block/mmcblk0p1
Thanks
Many ty's for this.
Thanks you help me rooted my Springboard. Have you try the MediaPad Phone app can we use the tablet for calling? :good:
Do I have to do step 11 ?
Sent from my SpringBoard using XDA Premium App
---------- Post added at 06:11 PM ---------- Previous post was at 05:49 PM ----------
robkaos said:
Do I have to do step 11 ?
Sent from my SpringBoard using XDA Premium App
Click to expand...
Click to collapse
Also can I do it without PC?
Sent from my SpringBoard using XDA Premium App
Can I use the recovery image from the update that is still on my sd card,what is the difference between the I've springboard .rar, and the su files
Sent from my SpringBoard using XDA Premium App
robkaos said:
Do I have to do step 11 ?
......
Also can I do it without PC?
Click to expand...
Click to collapse
If you do not return your recovery partition to stock, then you will not be able to install future firmware updates from T-Mobile as their updates rely on the stock recovery. So no, you don't have to return your recovery partition to stock, but if you don't you will not be able to install future T-Mobile updates. As far as doing this without a computer - you can use a terminal emulator on your Springboard to create the recovery image from 'recovery2'....the commands should be the same. However, you need to fastboot flash that image back to 'recovery', which you must do from your computer with your device in fastboot mode.
robkaos said:
Can I use the recovery image from the update that is still on my sd card....
Click to expand...
Click to collapse
Yes, if you extract the recovery image from the official T-Mobile update package, you can use this image to flash 'recovery' back to stock when you are done.
Some people have reported that they are unable to boot into CWM recovery if it is flashed only to 'recovery' and not also to 'recovery2'. It is my experience that the device seems to alternate which recovery partition it boots into when you sequentially boot it into recovery mode. When I have CWM on 'recovery' and the stock recovery on 'recovery2', my device will boot into CWM every other time I boot into recovery mode. The other times it boots into the stock recovery. If you can't get CWM recovery to appear when you boot into recovery mode, you could do things a bit different than the instructions. Extract the stock recovery image from the official T-Mobile update package. Store this away on your computer. Then, instead of only flashing 'recovery' with CWM recovery, also flash 'recovery2'. Once you are done rooting the device, use your stored image of the stock recovery to flash 'recovery' and 'recovery2' back to stock.
Originally, I used this method to root Honeycomb. I did not have the T-Mobile update package for Honeycomb and so could not simply extract the stock recovery image from that package. You cannot use the 'dd' command as in step 11 above until you are rooted to dump the image of 'recovery2'. So, without a copy of the update package I could not get an image of my recovery partition without already being rooted. But to root, I have to overwrite my recovery partition with CWM recovery, thereby making it impossible to dump a copy of the stock recovery as I had wiped it out and replaced it with CWM. The solution was to only flash one of the recovery partitions and keep the other one as a backup until the device was rooted and the image could then be extracted.
robkaos said:
...what is the difference between the I've springboard .rar, and the su files
Click to expand...
Click to collapse
Not sure what you are asking here...please clarify.
I haVe found two different root files one su zip and the other is for media pad orange Tahiti ,andspringbord .rar which is the difference?there is not a one click Method like motor defy? My phone wasn't such a problem
Sent from my SpringBoard using XDA Premium App
robkaos said:
I haVe found two different root files one su zip and the other is for media pad orange Tahiti ,andspringbord .rar which is the difference?
Click to expand...
Click to collapse
I don't know about the root files for the Mediapad. I know there is a package that contains the su files and a Windows-based command file that contains a string of adb commands that is supposed to work to root both the Mediapad and the Springboard. I think what you are talking about can be found at either one of these locations:
http://www.modaco.com/topic/354579-...-mediapad-t-mobile-springboard-orange-tahiti/
http://www.gamefront.com/files/22185176/Huawei+MediaPad+ROOT+ICS+Android+4.0.x.rar
I tried to use this, and got a 'premission denied' fail pretty early on. I run Linux on my desktop, so perhaps this works under Windows with the specific Springboard drivers and interface software installed, but it sure does not work in Linux. I came up with my method (or rather consolidated the information for 'my' method from multiple other sources) as a result of having this root method fail for me.
robkaos said:
...there is not a one click Method like motor defy? My phone wasn't such a problem
Click to expand...
Click to collapse
If the files that I linked above work for you, then this is going to be about as close to a 'one-click' method as you can get. Unless you modified it, your Motorola Defy is running Android 2.1 (Eclair). This version of Android can be rooted pretty much just by yelling 'ROOT!' at your phone. There is even an app in the market that can be installed and run on an Android v2.1 device that provides a one-click root without the use of a computer. All of the exploits that were used for these one-click root methods were patched in Android v3+. Pretty much every device needs its own unique root method now, and the only way it is a one-click method is if someone has constructed a command script to execute all of the needed commands for you, as in the linked packages above.
xdajunkman said:
Also, be aware that any changes you make will be permanent. I tried hard reseting the device through the usual android settings menu security method, and I kept root and all of my deleted bloatware was still gone after it finished and rebooted. There does not appear to be a way to get all of your stock stuff back once you start deleting things...so make backups of files before you delete them in case removing them causes unexpected consequences.
Click to expand...
Click to collapse
Just to point out - now that the Springboard ICS update is out, and the zip has been captured and archived - there is a backup of complete stock ICS available. Every single partition is in there including system and cust. So worst case scenario if you bork it by zapping the wrong file in system or cust, you can reflash that partition from the bootloader.
Thanks for the clarification
Sent from my SpringBoard using XDA Premium App
cmstlist said:
Just to point out - now that the Springboard ICS update is out, and the zip has been captured and archived - there is a backup of complete stock ICS available. Every single partition is in there including system and cust. So worst case scenario if you bork it by zapping the wrong file in system or cust, you can reflash that partition from the bootloader.
Click to expand...
Click to collapse
You are, of course, correct. That statement of mine is now outdated...you can delete things to your hearts desire. If you mess something up, just reflash the firmware and start over.
Just finished rooting my MediaPad from t-mobile. I had to install into recovery one and two so now I have no original recovery but I don't really care, I've got the latest Android Ice Cream update beforehand. What usefull apps with root access do I need now? I've got ad free and ROM Toolbox. Was there a phone app that I could use now?
Failed updates and can't recover - PLEASE HELP!
xdajunkman said:
You are, of course, correct. That statement of mine is now outdated...you can delete things to your hearts desire. If you mess something up, just reflash the firmware and start over.
Click to expand...
Click to collapse
Well, unfortunately, I've messed things up. Here's what happened:
1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3
2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.
3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.
4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.
5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.
Any and all help would be immensely appreciated! How can I get back to some sort of working ROM? Please!
Thanks!
knightpawn said:
Well, unfortunately, I've messed things up. Here's what happened:
1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3
2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.
3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.
4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.
5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.
Any and all help would be immensely appreciated! How can I get back to some sort of working ROM? Please!
Thanks!
Click to expand...
Click to collapse
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Any particular locations for the other files via fastboot?
cmstlist said:
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Click to expand...
Click to collapse
Wow! Thanks for the help! I unfortunately, don't have my other computer that has the proper drivers installed to recognize the tablet and to run fastboot on. So, I'll try the fix you are suggesting once I get home today. However, in the meantime, I had some questions with regard to where I should flash the other files.
I understand that recovery.img should go to the recovery and recovery2 partitions.
What about the others? Does boot.img go to a particular partition? Effectively, what would the command line look like? (eg fastboot flash boot boot.img?)
Sorry about the newbie questions. I've installed a number of custom ROMs on phones using CWM, but this is a strange beast.
With regard to your question of whether it boots, well, kind of...it does boot to the T-mobile Springboard screen, then it sits there. I will let it sit for 20-30 minutes and see what happens. Will report back...for sure!
Thanks a ton!
[UPDATE]
So, I had a chance to install the TWRP recovery with the CM10 ROM. I loaded the CM10 ROM with the TWRP which installed successfully. I turned the tablet on and let it sit there for about 10 minutes and sure enough, CM10 runs just fine. However, I did notice that I cannot receive any calls. I am able to make calls, but when someone dials my number, it just goes straight to voicemail.
So, now, I'm wondering, if I can get the stock ICS with International ROM running so that I can try to use this thing as a phone, data and texting tab. I'll try what you suggested when I get home as mentioned earlier.
CM10 has too many problems, why would you want to use it?
cmstlist said:
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Click to expand...
Click to collapse
That worked for me. After playing with vold.fstab I had rendered my Springboard unusable (got the encryption was unsuccessful screen!).
I really wanted to switch the apps installation path to the external sd card but did not succeed.
What am I doing wrong
I have not been able to root my springboard at all. It will go to a black screen that says enter fastboot and it just stays there. When I type to flash the recovery it says it cannot load it. I have adb and fastboot installed...could it be a driver issue? I now know that I am in the correct screen, just can't get this thing rooted. any help would be appreciated thanks.
Well I feel quite stupid. But figured out where I went wrong and for the love of God got my Springboard rooted. *whew*
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Completely Bricked
Me too need a stock rom of ta 1056. Please help if you could manage to provide a helping hand... ?
I had the same issue like yours, looping in twrp. then i tried to flash it with a so called stock rom from net, guess what it went completely bricked and I donnow what to do. ??
mrabudi said:
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Click to expand...
Click to collapse
It's simple. just get the stock recovery (and boot, optional) to flash it with fastboot and go to recovery and wipe it and you'll be ok.
and also using the twrp on this phone is not a great idea to wipe.
if you wanna wipe. please use "fastboot -w" to wipe the phone while bootloader is unlocked. or stock recovery to wipe.
Because twrp built this recovery with only formatting option was ext4 to /data and /cache. So the phone cannot operate properly. Which leads to fake failed decryption notification.
Data partition must need to be formatted under f2fs format.
And finding rom for this phone is pretty easy. Just find some nb0 file for this phone (any variant of this phone should work) and extract it with "nb0 extractor" and then flash it with SP Flash tool by mediatek.
That's my way. I don't know how will you do. But normally you only need the nb0 file and then flash it with OST LA (Nokia's flash tool based off Intel's SUT L1/L3 tool).
My Nokia 1 TA-1047 stuck at Nokia logo screen
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
cuantonhonhoi said:
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
Click to expand...
Click to collapse
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047. Since it's a universal ROM so any variant of the phone can also work) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to look at line with partition "metadata" and then edit "boundary_check" to false.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
kutiz21 said:
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to hide/delete line with partition "metadata" in scatter.txt and you can flash it perfectly.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
Click to expand...
Click to collapse
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
pabloluih said:
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
Click to expand...
Click to collapse
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
kutiz21 said:
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
Click to expand...
Click to collapse
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
That's weird. If you unlocked the bootloader and install adb/fastboot (must be latest version. Older version will not recognize the phone, download platform-tools from google dev site, don't download adb tools off XDA) + Nokia's driver from emulated CD drive (every time you plug the phone to computer with official rom, you'll see it) properly then it should be able to work.
You need to check the fastboot device driver Device Manager (devmgmt.msc) and see if the driver is properly installed yet.
You can only use "fastboot -w" once the bootloader is unlocked. And booting up the phone. It will say the bootloader is in Orange state.
You need to unlock oem bootloader from developer settings when the stock rom is there. And in fastboot too
Here is how you unlock it:
Enable oem unlock from dev settings
Then reboot to fastboot mode (bootloader)
Do this:
"fastboot oem key "serial number string converted to md5, not imei strings" "
"fastboot oem unlock"
Volume up
Then you are actually unlocked the bootloader.
Unlock from developer settings only will not do the trick. It only allows you to have ability unlock the bootloader in fastboot.
If you stuck on the Encryption unsuccessful screen. Try wipe it with stock recovery or "fastboot -w" (if you properly unlocked the bootloader)
If you think you can't do anything anymore. Just flash the ROM provided you above.
If you need the extracted ROM for SP flash tool and the fastboot driver. I can link it to you.
Most of all drivers will automatically install off Windows Update if you're on Windows 10 (except the fastboot driver, and yes. SP flash tool drivers are also provided by Windows 10 too)
Also. You should update the phone to the latest software update when flashing stock rom too. Because newer builds for this phone is compatible-friendly with GSI rom (Treble ROMs like AOSP Android 9 or 8.1 by phhusson)
Updates on Android 9/10
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
Nokia might harden the security of the device so you can't use Magisk on stock rom.
Hey friends,
I want to see if anyone has had this experience and can point me to a fix/resolution. The "main" issue is the Micro USB port is no longer operable, so I CAN NOT just re-flash with SP Tools (I so would have just). I'm keeping the phone charged with a wireless charger. I can boot to TWRP, in fact it bootloops into TWRP. I'm using the "DOOGEE-S60-Android 8.0 (9.2)_TWRP_ROOT_Final" rom, which I was flashing with SP Tools and extracting .imgs from it for testing.
Here's how the issue started; I was updating Magisk Modules and configuring the Hide Props for device emulation (I've done this multiple times looking for a solid working set and had to reflash for the same reasons several times, so I know it started with the Magisk module updating the boot img). At some point during the module updating the boot image seems to get corrupted and I get stuck bootloop into TWRP. This is an MTK device so reflashing with SP Tools and going about business is the normal simple fix..
Since my Micro USB is damaged and I can't flash with SP Tools now, TWRP recovery is the only resolution for this slowly dying device. I simply don't have a lot of experience with this particular issue and this is my first MTK device. I've been able to in TWRP;
1. Factory Reset - No resolution
2. Flash .imgs for boot.img, System.img, tee.img, and recovery.img (built in TWRP recovery for the rom which just resets TWRP, luckily) - No resolution, still bootloops to TWRP
3. chomd 755 adb & fastboot bins to system/bin (for the hell of it so I can terminal to either from within TWRP, can't seem to connect device though)
4. Wiped system completely and restored with with the system.img, by accident actually, and thought TWRP didn't have access enough to write it back, but it does
*edit1; 5. Tried using "dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc" from here. Returned "no such file found". After looking through the file explorer I imagine the file structure maybe different for this device though "dev/block" root is there. Maybe a transfer of different files?
So now I'm coming to see if anyone has any helpful info for recovering the boot to normal system on an MTK device only through TWRP (Which I'm pretty sure I've done multiple times over devices on Snapdragon devices)
Things that do work as current;
1. TWRP
2. External SD for transfering
3. Terminal within TWRP
4. Mounting System R/W
I'm thinking I "could" flash an OTA "Update.zip" for the device in TWRP, but there isn't one. This device only uses FOTA which seems to need the SP Tools type approach.
DemonLoader said:
Hey friends,
I want to see if anyone has had this experience and can point me to a fix/resolution. The "main" issue is the Micro USB port is no longer operable, so I CAN NOT just re-flash with SP Tools (I so would have just). I'm keeping the phone charged with a wireless charger. I can boot to TWRP, in fact it bootloops into TWRP. I'm using the "DOOGEE-S60-Android 8.0 (9.2)_TWRP_ROOT_Final" rom, which I was flashing with SP Tools and extracting .imgs from it for testing.
Here's how the issue started; I was updating Magisk Modules and configuring the Hide Props for device emulation (I've done this multiple times looking for a solid working set and had to reflash for the same reasons several times, so I know it started with the Magisk module updating the boot img). At some point during the module updating the boot image seems to get corrupted and I get stuck bootloop into TWRP. This is an MTK device so reflashing with SP Tools and going about business is the normal simple fix..
Since my Micro USB is damaged and I can't flash with SP Tools now, TWRP recovery is the only resolution for this slowly dying device. I simply don't have a lot of experience with this particular issue and this is my first MTK device. I've been able to in TWRP;
1. Factory Reset - No resolution
2. Flash .imgs for boot.img, System.img, tee.img, and recovery.img (built in TWRP recovery for the rom which just resets TWRP, luckily) - No resolution, still bootloops to TWRP
3. chomd 755 adb & fastboot bins to system/bin (for the hell of it so I can terminal to either from within TWRP, can't seem to connect device though)
4. Wiped system completely and restored with with the system.img, by accident actually, and thought TWRP didn't have access enough to write it back, but it does
*edit1; 5. Tried using "dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc" from here. Returned "no such file found". After looking through the file explorer I imagine the file structure maybe different for this device though "dev/block" root is there. Maybe a transfer of different files?
So now I'm coming to see if anyone has any helpful info for recovering the boot to normal system on an MTK device only through TWRP (Which I'm pretty sure I've done multiple times over devices on Snapdragon devices)
Things that do work as current;
1. TWRP
2. External SD for transfering
3. Terminal within TWRP
4. Mounting System R/W
I'm thinking I "could" flash an OTA "Update.zip" for the device in TWRP, but there isn't one. This device only uses FOTA which seems to need the SP Tools type approach.
Click to expand...
Click to collapse
Any chance of a hardware fix? Replacing the damaged port?
Nephiel said:
Any chance of a hardware fix? Replacing the damaged port?
Click to expand...
Click to collapse
I "would" just simply do that, but the device is older, and since there aren't any factory updates for the OS, it's not really worth the time and effort to buy and solder. It's more fun to find a way through the software at this point..
Why is there no custom rom for Doogee S60? . android 8? 9? 10 ?. where can I find it?
Why is there no custom rom for Doogee S60? . android 8? 9? 10 ?. where can I find it?. Compatible for Doogee S60? custom rom android 8 9 10?
Ulefone Armor X6 - mt6580, 720x1280 5-inch, 2/16 ram/rom Android 9. There is a full rom, ulefone site (Support > Software Download). I use EU version.
Rom is with "-sign.img"s, system/build.prop: "ro.treble.enabled=true", "ro.expect.recovery_id=0xb4248...", boot-sign.img without ramdisk.
Used tools: Linux - IMG-SIGN Extractor (signimg2img), simg2img/img2simg, mount, SP Flash Tool, Carliv Image Kitchen, Windows - Miracle.
Tests for modification:
Fastoboot flashing unlock - ok.
SPFT - before connection - hold volume down - is possible to flash full rom. Single img - error.
Patching recovery-sign.img in magisk, recovery mode. Fastboot flash recovery magisk_patched.img = bootloop.
System-sign.img - unsign, unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via fastboot. Fastboot say "ok". After start - stil stock system, without modification.
For the upper rom exist update ~400mb. Update, dump with Miracle - img's are unsigned.
System.img - unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via Miracle = bootloop.
Also, I make a few ports of TWRP via Carliv Image Kitchen. Always bootloop (I never had trouble with a previous ports, for other phones, especially for this cpu)
Any other ideas? Or links to the right treads. This is my first rom with treble / "-sign.img"s.
Root
Tested on "GQ3085DH1_KSP2E_Ulefone_EEA_20200312_V01（Eu）" (Baseband version MOLY.WR8.W1449.MD.WG.MP.V237.4,2019/10/28 09:26, Kernel version 4.9.117 #2 Mon Oct 28 09:48:24 CST 2019)
Unlocking bootloader and disable verification (fastboot - min. version 1.8, vbmeta.img from stock rom):
fastboot flashing unlock
(volume up)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
On Android - Mtk-easy-su-v1.1.3.apk & MagiskManager-v7.5.1.apk.
Mtk-easy-su:
1. Run on boot
2. Magisk.v20.4.zip (assets-r22) - install
3. "Activate bootless root"
Restart phone. After start, wait to see "Success" on screen (bottom). Magisk work.
After root, if adb is needed:
adb shell
su
mount -o rw,remount /
Do you have made any progress?
Im sitting here on my armor x6 and have the same problems.
ahaff said:
Ulefone Armor X6 - mt6580, 720x1280 5-inch, 2/16 ram/rom Android 9. There is a full rom, ulefone site (Support > Software Download). I use EU version.
Rom is with "-sign.img"s, system/build.prop: "ro.treble.enabled=true", "ro.expect.recovery_id=0xb4248...", boot-sign.img without ramdisk.
Used tools: Linux - IMG-SIGN Extractor (signimg2img), simg2img/img2simg, mount, SP Flash Tool, Carliv Image Kitchen, Windows - Miracle.
Tests for modification:
Fastoboot flashing unlock - ok.
SPFT - before connection - hold volume down - is possible to flash full rom. Single img - error.
Patching recovery-sign.img in magisk, recovery mode. Fastboot flash recovery magisk_patched.img = bootloop.
System-sign.img - unsign, unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via fastboot. Fastboot say "ok". After start - stil stock system, without modification.
For the upper rom exist update ~400mb. Update, dump with Miracle - img's are unsigned.
System.img - unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via Miracle = bootloop.
Also, I make a few ports of TWRP via Carliv Image Kitchen. Always bootloop (I never had trouble with a previous ports, for other phones, especially for this cpu)
Any other ideas? Or links to the right treads. This is my first rom with treble / "-sign.img"s.
Click to expand...
Click to collapse
Yo, can you send me the port of TWRP for this phone please?
Hello Everyone,
I got a new OnePlus Nord N10 5G BE2026 Unlocked the Bootloader, Flashed TWRP Recovery, Advanced wiped everything and formated data. I was going to give Lineage 18.1 GSI Rom a try but when trying to flash system in Fastboot I get partition not found Fastbootd I get no such file or directory.
So I decided I better go back to stock firmware again. I extracted all the files from the stock firmware payload.bin with payload dumper all the files flash fine in Fastboot until I get to the system.img and then I get the partition not found or no such file or directory in Fastbootd. I have tried in both slot A and slot B,
A interesting thing while in TWRP when I connect the phone to a computer the internal storage is greyed out and you can't copy files to it with MTP. I must be missing something somewhere?
System is a dynamic partition (https://source.android.com/devices/tech/ota/dynamic_partitions/implement?hl=en), it cannot be flashed via fastboot using the unpacked system.img
Use https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/
Thanks alot I had tried the MSM Download Tool before and got the Param Error. This time I used the driver from the post and it worked! I guess I won't be trying any GSI roms on this phone because I don't know how to flash System if it is inside the Super.
Wild-Owl said:
Thanks alot I had tried the MSM Download Tool before and got the Param Error. This time I used the driver from the post and it worked! I guess I won't be trying any GSI roms on this phone because I don't know how to flash System if it is inside the Super.
Click to expand...
Click to collapse
Yes, not much development going on with this phone. You should note the TWRP is beta and is not fully functional.