This thread is for helping to recover a bricked Tronsmart
Urgent - Bricked!!!
Urgent issue!!!
Yesterday during the day my Tronsmart TS7 (MTK6589) did not want to turn on from sleep (ColorOS), until the everything was ok.
I tried to enter TWRP recovery but it was just showing the teamwin logo, tried to restart and enter OS but also showed only bootlogo.
I used SP Flash tools with my Stock rom to try get it back to life but option Firmware upgrade messed it up, format was done and now GP1 to GP4 partitions show 0 Mb and NAND memory missing while emmc shows 3628 Mb but cannot format and download from SP Flash the /data, /system and /cache, tried to format through new recovery and flashing zip but without success.
I tried also using Download from KVD K7 and Cubot one (bot without flashing preloader), I managed to flash everything except the main three partitions, strangely emmc (internal SD card is OK and writable from Windows).
It seems it is bricked.
Can someone please provide a MTK Droid backup so that I can try to restore the whole phone?
Thanks to everyone.
Domcek said:
Urgent issue!!!
Yesterday during the day my Tronsmart TS7 (MTK6589) did not want to turn on from sleep (ColorOS), until the everything was ok.
Click to expand...
Click to collapse
This is usually caused by the boot.img of a device not matched to your uboot. Use your own Stock boot.img and make the necessary edits in the init.rc for the Color OS
Domcek said:
I tried to enter TWRP recovery but it was just showing the teamwin logo, tried to restart and enter OS but also showed only bootlogo.
Click to expand...
Click to collapse
Not sure why TWRP would not work unless this too was for a different phone/kernel to yours.
Domcek said:
I used SP Flash tools with my Stock rom to try get it back to life but option Firmware upgrade messed it up, format was done and now GP1 to GP4 partitions show 0 Mb and NAND memory missing while emmc shows 3628 Mb but cannot format and download from SP Flash the /data, /system and /cache
Click to expand...
Click to collapse
Rarely will SP Flashtool "mess it up" It seems to me that the firmware upgrade was interrupted or you just selected format only
Once you have formatted the phone you usually have to select all parts including the pre loader to flash your stock rom back to the phone. YOU HAVE TO DO THIS IN DOWNLOAD MODE first not Firmware Upgrade after it flashes the firmware you can then use the Firmware Upgrade option (Recommended) which will sort any messed up partitions
The NAND memory missing is normal and nothing to worry about
Domcek said:
Tried also using Download from KVD K7 and Cubot one (bot without flashing preloader), I managed to flash everything except the main three partitions, strangely emmc (internal SD card is OK and writable from Windows).
Click to expand...
Click to collapse
Domcek said:
It seems it is bricked.
Can someone please provide a MTK Droid backup so that I can try to restore the whole phone?
Thanks to everyone.
Click to expand...
Click to collapse
Use this ROM below to get your phone back to a working condition then start again rooting custom recovery etc.
Stock ROM Here with instructions
Good Luck
Hit Thanks If I Helped
First... Thank you for your response. :victory:
bigrammy said:
This is usually caused by the boot.img of a device not matched to your uboot. Use your own Stock boot.img and make the necessary edits in the init.rc for the Color OS
Not sure why TWRP would not work unless this too was for a different phone/kernel to yours.
Click to expand...
Click to collapse
Well, the TWRP 2603 was on compiled for this phone, previously worked with no problem, after trying to restorea working ROM with SP Flash tools problems with Download of /android, /cache and /userdata appeared and the problem with format of /system, /cache and /data.
I tried with stock and Cubot one (as they are twins) and worked without problems. but the phone was working without problems for 7 days and the screen went off but could not start it anymore from sleep, then the rest of the problems appeared.
Rarely will SP Flashtool "mess it up" It seems to me that the firmware upgrade was interrupted or you just selected[B said:
format only[/B]
Once you have formatted the phone you usually have to select all parts including the pre loader to flash your stock rom back to the phone. YOU HAVE TO DO THIS IN DOWNLOAD MODE first not Firmware Upgrade after it flashes the firmware you can then use the Firmware Upgrade option (Recommended) which will sort any messed up partitions
The NAND memory missing is normal and nothing to worry about
Use this ROM below to get your phone back to a working condition then start again rooting custom recovery etc.
Stock ROM Here with instructions
Good Luck
Hit Thanks If I Helped
Click to expand...
Click to collapse
Well, first my mistake was to select Firmware upgrade and seems that the format messed the partition list.
After that I tried to flash (Download) stock rom (from geekbuying TS7 4 GB) and then Cubot one ROM and KVD K7 (without preloader, twin phones), but I can flash everything exccept the noted 3 partitions (seems like the layout has been lost).
I reinstalled the boot, recovery, etc. from the SP Flash but remained the problematic 3.
It came to my mind that peviously I enlarged /data partition (Meteos 2.5 Gb) and maybe that added to the problem (SP Flash tool shows that the device has 28 GB?!
Upper info 1 GB RAM+8192 Mb DRAM memory. I will attach screenshots.
Domcek said:
First... Thank you for your response. :victory:
Well, the TWRP 2603 was on compiled for this phone, previously worked with no problem, after trying to restore a working ROM with SP Flash tools problems with Download of /android, /cache and /userdata appeared and the problem with format of /system, /cache and /data.
I tried with stock and Cubot one (as they are twins) and worked without problems. but the phone was working without problems for 7 days and the screen went off but could not start it anymore from sleep, then the rest of the problems appeared.
Well, first my mistake was to select Firmware upgrade and seems that the format messed the partition list.
After that I tried to flash (Download) stock rom and then Cubot one ROM and KVD K7 (without preloader, twin phones), but I can flash everything exccept the noted 3 partitions (seems like the layout has been lost).
I reinstalled the boot, recovery, etc. from the SP Flash but remained the problematic 3.
Click to expand...
Click to collapse
It seem's to me that you have changed the PMT file in the ROM restore that you did and this is what broke your TWRP eg: System data cache may now be located in different partitions and twrp can no longer find them or tries to restore it to where it will no longer fit.
Some ports of TWRP are specific as to the dev block they write to eg: Example taken from a typical MTK Recovery: recovery/ rmdisk/ etc/recovery.fstab
Code:
# mount point fstype device [device2]
/boot emmc boot
/cache ext4 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p5
/misc emmc misc
/recovery emmc recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p3
As you can see if you mess the PMT then you break the recovery too. If your recovery was built for a Tronsmart which is Not exactly the same phone as the cubot one BTW they are just similar and have Totally different ROM's and it would seem different PMT's too so you must be careful when flashing with SP Flashtool.
If you have a backup of your Tronsmart with MTK Droidtools or you could even unpack a TWRP backup you just need to find the tronsmart PMT file and restore it via SP Flashtool along with your stock rom and your twrp recovery.
To add the PMT file to the flash just edit the scatter file with notepad ++ from
Code:
__NODL_PMT 0x?00000
to
Code:
PMT 0x?00000
do not change the 0x000000 just leave it at whatever it is in your scatter. Save change and flash as firmware upgrade you should the be good to go
bigrammy said:
It seem's to me that you have changed the PMT file in the ROM restore that you did and this is what broke your TWRP eg: System data cache may now be located in different partitions and twrp can no longer find them or tries to restore it to where it will no longer fit.
Some ports of TWRP are specific as to the dev block they write to eg: Example taken from a typical MTK Recovery: recovery/ rmdisk/ etc/recovery.fstab
Code:
# mount point fstype device [device2]
/boot emmc boot
/cache ext4 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p5
/misc emmc misc
/recovery emmc recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p3
As you can see if you mess the PMT then you break the recovery too. If your recovery was built for a Tronsmart which is Not exactly the same phone as the cubot one BTW they are just similar and have Totally different ROM's and it would seem different PMT's too so you must be careful when flashing with SP Flashtool.
If you have a backup of your Tronsmart with MTK Droidtools or you could even unpack a TWRP backup you just need to find the tronsmart PMT file and restore it via SP Flashtool along with your stock rom and your twrp recovery.
To add the PMT file to the flash just edit the scatter file with notepad ++ from
Code:
__NODL_PMT 0x?00000
to
Code:
PMT 0x?00000
do not change the 0x000000 just leave it at whatever it is in your scatter. Save change and flash as firmware upgrade you should the be good to go
Click to expand...
Click to collapse
Thanks, but... I have a TWRP backup, list attached.
From which file in TWRP I could extract the PMT and insert according to your info, of course on PC (as the log states tar_append_tree(): done with tar_append_file()... I tried rename to tar.gr and tar but without success)?
I am also assured that the partition layout is a problem and these 3 cannot be flashed (but as I am somewhat new to MTK phones and still getting to know them) but I thought that the partition and latter format would be more simple.
Strange is that I can flash every recovery for it (CWM, TWRP,...) and it is fully functional in terms of load, mount (even emmc can be mounted and resized if EBR1/EBR2 is changed).
I tried installing TS7 8G ANDROID/CACHE/USERDATA version and the same from Cubot one, error is:S_FT_ENABLE_DRAM_FAIL (4032) / [EMI] Enable DRAM Failed!
When I try to Download from stock rom the Progress bar stays at 0 % and always stops with message: S_FT_DOWNLOAD_FAIL (4008), while I can flash all other parts (except the 3 noted).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Domcek said:
Thanks, but... I have a TWRP backup, list attached.
From which file in TWRP I could extract the PMT and insert according to your info, of course on PC (as the log states tar_append_tree(): done with tar_append_file()... I tried rename to tar.gr and tar but without success)?
I am also assured that the partition layout is a problem and these 3 cannot be flashed (but as I am somewhat new to MTK phones and still getting to know them) but I thought that the partition and latter format would be more simple.
Strange is that I can flash every recovery for it (CWM, TWRP,...) and it is fully functional in terms of load, mount (even emmc can be mounted and resized if EBR1/EBR2 is changed).
Click to expand...
Click to collapse
Hi,
My mistake I just searched a TWRP backup I have and it seems the PMT file is not backed up the PMT file lives in the same region as the boot.img and uboot so it would need a separate call the same way the boot.img is backed up.
So it's back to the drawing board
Options:
1, Get a Tronsmart PMT file from someone and flash the stock rom with the PMT included.
2, Get the ROM from the link I gave you.
Load it to SP Flashtool and hit firmware upgrade.
You may get a warning or error message something like "PMT has changed use download"
If so just use the download mode and after it's complete then do the same again but this time use the firmware upgrade and fingers crossed it should run without the error. I am kind of working from memory here so I am not 100% sure but I think maybe SP Flashtool rewrites the PMT File during this process.
If all goes well you should now be back to stock and have the correct partitions.
So now flash your twrp recovery and root with MTK DroidTools :fingers-crossed:
Then report back :good:
Edit just noticed your edit LOL
Select all parts I cant make out the image as too small for any detail.
Link for New Flashtool V5.14 Nice UI and a FAQ section which explains any faults/errors and how to solve
bigrammy said:
Hi,
My mistake I just searched a TWRP backup I have and it seems the PMT file is not backed up the PMT file lives in the same region as the boot.img and uboot so it would need a separate call the same way the boot.img is backed up.
So it's back to the drawing board
Options:
1, Get a Tronsmart PMT file from someone and flash the stock rom with the PMT included.
2, Get the ROM from the link I gave you.
Load it to SP Flashtool and hit firmware upgrade.
You may get a warning or error message something like "PMT has changed use download"
If so just use the download mode and after it's complete then do the same again but this time use the firmware upgrade and fingers crossed it should run without the error. I am kind of working from memory here so I am not 100% sure but I think maybe SP Flashtool rewrites the PMT File during this process.
If all goes well you should now be back to stock and have the correct partitions.
So now flash your twrp recovery and root with MTK DroidTools :fingers-crossed:
Then report back :good:
Edit just noticed your edit LOL
Select all parts I cant make out the image as too small for any detail.
Link for New Flashtool V5.14 Nice UI and a FAQ section which explains any faults/errors and how to solve
Click to expand...
Click to collapse
Great, thank you.
I think that acquiring PMT file for Tronsmart TS7 will be a little hard. :crying:
I've tried to experiment with EBR1/EBR2 as the previous partition layout had 2.65 Gb of data and 179 Mb on emmc and it seems that could be related, the message of layout change appeared but still couldn't flash these 3 partitions.
Any good souls with PMT to TS7 maybe?
Thank you in advance
As Cubot One, KVD K7 Blackview JK808 and TS7 are almost identical twins, could I use the one from Cubot one for example?
Domcek said:
Great, thank you.
I think that acquiring PMT file for Tronsmart TS7 will be a little hard. :crying:
I've tried to experiment with EBR1/EBR2 as the previous partition layout had 2.65 Gb of data and 179 Mb on emmc and it seems that could be related, the message of layout change appeared but still couldn't flash these 3 partitions.
Any good souls with PMT to TS7 maybe?
Thank you in advance
As Cubot One, KVD K7 Blackview JK808 and TS7 are almost identical twins, could I use the one from Cubot one for example?
Click to expand...
Click to collapse
I will upload the stock cubot one EBR files. Please flash these along with the rest of the stock ROM via SP FlashTool. Edit the scatter file for the EBR files as described earlier for PMT file.
Fash all in Format + Download mode.
This should then resize your partitions back to stock and re-write the PMT then hopefully everything will be working. :fingers-crossed:
The EBR Files are named EBR1.txt & EBR2.txt for upload purpose just rename to EBR1 & EBR2 removing the .txt
bigrammy said:
I will upload the stock cubot one EBR files. Please flash these along with the rest of the stock ROM via SP FlashTool. Edit the scatter file for the EBR files as described earlier for PMT file.
Fash all in Format + Download mode.
This should then resize your partitions back to stock and re-write the PMT then hopefully everything will be working. :fingers-crossed:
The EBR Files are named EBR1.txt & EBR2.txt for upload purpose just rename to EBR1 & EBR2 removing the .txt
Click to expand...
Click to collapse
Great, thank you.
I am going to try in the next 5 mins. :laugh:
---------- Post added at 03:03 PM ---------- Previous post was at 02:37 PM ----------
Domcek said:
Great, thank you.
I am going to try in the next 5 mins. :laugh:
Click to expand...
Click to collapse
Well, not successull.
Error: S_FT_ENABLE_DRAM_FAIL
Domcek said:
Well, not successull.
Error: S_FT_ENABLE_DRAM_FAIL
Click to expand...
Click to collapse
Ok No problem it seems one or more of the .img files is too large for the partition it's trying to fit into.
Try flash just the EBR files only when completed.
Then try flash the stock rom again in Format + Download mode Use the v5.14 tool as I know this worked on a phone I had once which also had messed up partitions. :good:
Note: You must select all the boxes in the download including the preloader or you will not be able to fully change the partitions otherwise
bigrammy said:
Ok No problem it seems one or more of the .img files is too large for the partition it's trying to fit into.
Try flash just the EBR files only when completed.
Then try flash the stock rom again in Format + Download mode Use the v5.14 tool as I know this worked on a phone I had once which also had messed up partitions. :good:
Note: You must select all the boxes in the download including the preloader or you will not be able to fully change the partitions otherwise
Click to expand...
Click to collapse
Nothing... Format all-Download
S_FT_FORMAT_FAIL
I tried then Firmware upgrade, result:
__NODL_PRO_INFO: Failed to get PMT info.
Domcek said:
Nothing... Format all-Download
S_FT_FORMAT_FAIL
I tried then Firmware upgrade, result:
__NODL_PRO_INFO: Failed to get PMT info.
Click to expand...
Click to collapse
Just try Download only.
Trial and error i am afraid until we can get a successful boot then we can fix things in other ways. :fingers-crossed:
bigrammy said:
Just try Download only.
Trial and error i am afraid until we can get a successful boot then we can fix things in other ways. :fingers-crossed:
Click to expand...
Click to collapse
Tried that, nothing...
Even tried twin ROMS (without preloader) for KVD K7, Cubot one official and HDC One M7, all the same.
Strange is that I can flash all of these preloaders and the result is always the same.
---------- Post added at 08:18 AM ---------- Previous post was at 08:05 AM ----------
Domcek said:
Tried that, nothing...
Even tried twin ROMS (without preloader) for KVD K7, Cubot one official and HDC One M7, all the same.
Strange is that I can flash all of these preloaders and the result is always the same.
Click to expand...
Click to collapse
Seems that now both the batteries are gone, empty.
Domcek said:
Tried that, nothing...
Even tried twin ROMS (without preloader) for KVD K7, Cubot one official and HDC One M7, all the same.
Strange is that I can flash all of these preloaders and the result is always the same.
---------- Post added at 08:18 AM ---------- Previous post was at 08:05 AM ----------
Seems that now both the batteries are gone, empty.
Click to expand...
Click to collapse
Thank you for the info.
But nothing.
I did according to instructions (additionally I tried to get support on 4PDA, thanks to Legiondark), I see the message PMT layout changed but cannot format and cannot download. Tried Download, Format, Firmware upgrade. I got even the PMT and EBR1/EBR2 from Legiondark, but...
USB detectable, when preloader is not flashed it shows MTK USB when I download Preloader on phone it shows Preloader USB VCOM, so it is detectable. I tried to use different ports and install/reinstall drivers.
Yesterday I could not format only android/cache/userdata and today only preloader can be flashed and sometimes the EBR1/2 and PMT files (message recevied at next iteration to user Format all-Download or Firmware upgrade but after trying I get the message F_ST_FORMAT FAIL).
As it was bought from China over internet it seems that it is time to smash it.
Domcek said:
Thank you for the info.
But nothing.
I did according to instructions (additionally I tried to get support on 4PDA, thanks to Legiondark), I see the message PMT layout changed but cannot format and cannot download. Tried Download, Format, Firmware upgrade. I got even the PMT and EBR1/EBR2 from Legiondark, but...
USB detectable, when preloader is not flashed it shows MTK USB when I download Preloader on phone it shows Preloader USB VCOM, so it is detectable. I tried to use different ports and install/reinstall drivers.
Yesterday I could not format only android/cache/userdata and today only preloader can be flashed and sometimes the EBR1/2 and PMT files (message recevied at next iteration to user Format all-Download or Firmware upgrade but after trying I get the message F_ST_FORMAT FAIL).
As it was bought from China over internet it seems that it is time to smash it.
Click to expand...
Click to collapse
:laugh: Yes these phone's can be very frustrating I spent 5 days recovering one of the phones I had after someone had done a bad flash.
What version's SPFlashTool have you tried
Try use these different versions some versions format better some download better again just experiment Here Here and Here
bigrammy said:
:laugh: Yes these phone's can be very frustrating I spent 5 days recovering one of the phones I had after someone had done a bad flash.
What version's SPFlashTool have you tried
Try use these different versions some versions format better some download better again just experiment Here Here and Here
Click to expand...
Click to collapse
yup, frustrating...
the problem is that the preloader can be flashed (only from stock) and I have even tried from similar phones but it does not let to flash a wrong one. I can always flash the stock preloader again and again.
Phone is detectable (MTK USB/Preloader USB) and it reads the information (emmc, read back, test,..) but I cannot format it and I've tried using about 10 Sp flash version 3.x and 2 versions 5.x. :crying: I see that I haven't used the first 2 you added so will, the last (5.x version) I've used, always rund as admin and tried.
Tried to flash it also using 4PDA help (http://4pda.ru/forum/index.php?showtopic=500445&st=540), tried flashing "twin" roms: KVD K7, Cubot One, HDC One M7 (several roms) but all without success, it always hangs on format (never goes past 0%). USB port is OK, drivers on PC are OK (used usbdeview and uninstalled all and reinstalled), USB on phone is firm and not damaged, in short phone is like new,
Yesterday I tried using the testpoint method, found how to jump start it to detect without battery but I it seems that it started to charge the battery prior so that part is not needed.
Possible that the emmc flash got fried by itself? Can I test that somehow?
Domcek said:
yup, frustrating...
the problem is that the preloader can be flashed (only from stock) and I have even tried from similar phones but it does not let to flash a wrong one. I can always flash the stock preloader again and again.
Phone is detectable (MTK USB/Preloader USB) and it reads the information (emmc, read back, test,..) but I cannot format it and I've tried using about 10 Sp flash version 3.x and 2 versions 5.x. :crying: I see that I haven't used the first 2 you added so will, the last (5.x version) I've used, always rund as admin and tried.
Tried to flash it also using 4PDA help (http://4pda.ru/forum/index.php?showtopic=500445&st=540), tried flashing "twin" roms: KVD K7, Cubot One, HDC One M7 (several roms) but all without success, it always hangs on format (never goes past 0%). USB port is OK, drivers on PC are OK (used usbdeview and uninstalled all and reinstalled), USB on phone is firm and not damaged, in short phone is like new,
Yesterday I tried using the testpoint method, found how to jump start it to detect without battery but I it seems that it started to charge the battery prior so that part is not needed.
Possible that the emmc flash got fried by itself? Can I test that somehow?
Click to expand...
Click to collapse
Hi bro,
It's really hard for guys like Legion Dark and myself to diagnose the problems when we do not have the phone in our hands I am kinda running out of ideas here
Normally these suggestions will work and it's really quite hard to brick these phones normally.
Most problems happen when a Kernel/boot.img not meant for your phone gets booted because the kernel can sometimes overwrite important files in the /dev area such as the pmt, ebr, mbr and many other files which are located there. SPFlashTools references files contained in there and if there is a file with info that conflicts with what it expects it will error so it could be something like the fstab file not match what the pmt file says.
Maybe you could try to flash just the stock boot.img then start the phone and leave it for a good while even if it does not fully boot it may rewrite some of the corrupted files :fingers-crossed:
After try to reflash the whole of ROM again and try in all different modes download only, format + download, Firmware Upgrade,
PS: Make sure you use the STOCK ROM I linked earlier 1gbx8gb tronsmart I think the legiondark PMT is modified to 4gb again this will confuse SPflashTool so
Stock ROM all parts selected flash with SPFlashTool.
bigrammy said:
Hi bro,
It's really hard for guys like Legion Dark and myself to diagnose the problems when we do not have the phone in our hands I am kinda running out of ideas here
Normally these suggestions will work and it's really quite hard to brick these phones normally.
Most problems happen when a Kernel/boot.img not meant for your phone gets booted because the kernel can sometimes overwrite important files in the /dev area such as the pmt, ebr, mbr and many other files which are located there. SPFlashTools references files contained in there and if there is a file with info that conflicts with what it expects it will error so it could be something like the fstab file not match what the pmt file says.
Maybe you could try to flash just the stock boot.img then start the phone and leave it for a good while even if it does not fully boot it may rewrite some of the corrupted files :fingers-crossed:
After try to reflash the whole of ROM again and try in all different modes download only, format + download, Firmware Upgrade,
PS: Make sure you use the STOCK ROM I linked earlier 1gbx8gb tronsmart I think the legiondark PMT is modified to 4gb again this will confuse SPflashTool so
Stock ROM all parts selected flash with SPFlashTool.
Click to expand...
Click to collapse
Great, thank you for the all advices given.
I have a somewhat more than basic experience with ROMS, porting, linux and Qualcomm based phones (HTC, Huawei, Samsung,...) and I would not qualify myself as a novice but I must admin these MTKs are something new to me, also as it seems a lot of problems which seem unlogical to me so I am a little lost.
Strange to me is that the box says 4 Gb(it had 620 Mb system, cca 120 mb cache and 1,1 Gb of /data with emmc of approx. 2 Gb) and I see that you note that I should use 8 Gb and not 4 GB PMT and scatter (and of course ROM), more strange is that the SP FLash tool sees it as a 8192 Mb device.
I have tried the 8 Gb stock now and I can't flash the preloader (only 4 Gb Stock is OK) nor and other parts of it: S_FT_ENABLE_DRAM_FAIL (4032) and if I am not mistaken that is an error for the wrong ROM flash?!
Domcek said:
Great, thank you for the all advices given.
I have a somewhat more than basic experience with ROMS, porting, linux and Qualcomm based phones (HTC, Huawei, Samsung,...) and I would not qualify myself as a novice but I must admin these MTKs are something new to me, also as it seems a lot of problems which seem unlogical to me so I am a little lost.
Strange to me is that the box says 4 Gb(it had 620 Mb system, cca 120 mb cache and 1,1 Gb of /data with emmc of approx. 2 Gb) and I see that you note that I should use 8 Gb and not 4 GB PMT and scatter (and of course ROM), more strange is that the SP FLash tool sees it as a 8192 Mb device.
I have tried the 8 Gb stock now and I can't flash the preloader (only 4 Gb Stock is OK) nor and other parts of it: S_FT_ENABLE_DRAM_FAIL (4032) and if I am not mistaken that is an error for the wrong ROM flash?!
Click to expand...
Click to collapse
Hi bro,
I did not realise that Tronsmart did an MT6589 4gb and 8gb version but it seem's they do :silly:
They also do a MT6582 4gb version just to confuse things further :laugh:
Well now I am really confused as all but the newest Cubot One's are MT6589 1gb + 8gb
Did all the problems started when you flashed the ColorOSROM
Was the ColorOS ROM for a Cubot One or Tronsmart and If I it was for Tronsmart was it for 8gb or your 4gb version
I have ported the stock ColorOS for my own phone and I can say that the ColorOS makes quite a lot of entries on kernel init.rc It also shuffled things around so you don't need to partition things manually
What I am trying to say is that if the ColorOS zip contained a heavily modified Kernel Which it would need for ColorOS to work properly and it's not for your exact phone then this maybe the cause of the problems and the reason I never shared my Port of ColorOS as I would of had to manually edited all the different Kernels be be sure they all worked example MT6589 1200mhz 1500mhz and 1500mhz "T" version all slightly different and if they become mixed up then you start getting bugs such as screen not waking up no wifi connection camera issues etc etc :crying:
Hey all.
Easy question I hope! I've been following the guide to unbrick MTK devices, and have managed to get an original factory ROM to flash to the phone, green tick in SP Flash Tools. However, the phone still won't power on at all, save for the light if plugged into usb.
The ROM I've been using is an original factory rom named "ONE-TOUCH-4015X_POP_C1_FULL_STOCK_BACKUP" which is readily available online. I'm not sure what I did to brick it in the first place, but it was within SP flashtool. I May have formatted accidentally.
If someone coudl help I'll try to provide all logs or files requested but please tell me where these could be found as I'm not that good with flash tool.
To confirm the phone won't boot into any mode, recovery is dead, fastboot is dead....
same problem hope somone help us
also share ur backup please
darkglobe87 said:
Hey all.
Easy question I hope! I've been following the guide to unbrick MTK devices, and have managed to get an original factory ROM to flash to the phone, green tick in SP Flash Tools. However, the phone still won't power on at all, save for the light if plugged into usb.
The ROM I've been using is an original factory rom named "ONE-TOUCH-4015X_POP_C1_FULL_STOCK_BACKUP" which is readily available online. I'm not sure what I did to brick it in the first place, but it was within SP flashtool. I May have formatted accidentally.
If someone coudl help I'll try to provide all logs or files requested but please tell me where these could be found as I'm not that good with flash tool.
To confirm the phone won't boot into any mode, recovery is dead, fastboot is dead....
Click to expand...
Click to collapse
Did you ever get the above rom to work? If so what did you do? Or did you find another method to unbrick the phone? Thanks.
Managed to unbrick my 4015 using Mobile Upgrade S 4.3.0 from the Alcatel Website.
http://www.alcatelonetouch.com/global-en/support/download/one_touch_idolx.html
Very simple to use, just install and follow instructions.
darren1 said:
Managed to unbrick my 4015 using Mobile Upgrade S 4.3.0 from the Alcatel Website.
http://www.alcatelonetouch.com/global-en/support/download/one_touch_idolx.html
Very simple to use, just install and follow instructions.
Click to expand...
Click to collapse
no work this version. yes 4015 but no 4015x
Sorry I should have put my phone is a 4015X not 4015. The application does say 4015 which I selected and all went well.
my 4015x no update, it not load, only work flash mode connected to pc and no work mobile upgrade.
4015X Partitions
the 4015x has a different set of partitions to the older (dual sim) 4015
i have a modded rom (kitkat), a modded stock recovery (as stock is also wrong, wont mount data) and a modded cwmrecovery.
i will be posting these soon
i will create a new post for the 4015x version
and will also be asking for other versions of the 4015 users to post me there partition trees and i will repack some recoverys and some roms for you all
note: there are 6 versions that i have seen and they may all have diff tables
hope these will help the pop c1 community
recoverys and rom
Stock Recovery (Fixed)
https://drive.google.com/file/d/0B4ZKFXlQiHioVUExRW1sZkdzSFk/view?usp=sharing
CWMRecovery (Fixed)
https://drive.google.com/file/d/0B4ZKFXlQiHioUTJqOTMtbUNPTEU/view?usp=sharing
kitkat-cm11-modROM.zip (Fixed)
https://drive.google.com/file/d/0B4ZKFXlQiHioUUI3V2Jsd0lTN1k/view?usp=sharing
(I am currently using this rom my self and all seems to be good except vibration, it also thinks its a dual sim but not causing a probb)
Hello!
This thread is quite old but near my case.
I have an Alcatel Pop C1 4015X (cpu MTK6572M) that can't start at all (only the power LED is ON).
I have a backup of this device made with "SP Flash Tool V5.1532.00" but I've error "not enough space" when
I try to restore it.
Same error when I try to restore just one file.
For example, I've tried to restore only the "Stock Recovery" you give above.
I do this:
- I start Flash_Tool v5.1532.00
- I open scatter file from my backup done with the same tool
- I unselect all pieces of the backup except "Recovery" and I browse to the "Stock Recovery" file I've dl
from this thread.
I've got this error : "not enough storage space (1011)"
What could be the problem ?
I makes me totally crazy !
By advance, thanks for your help.
Regards,
Freeman.
Fr33M4n! said:
Hello!
This thread is quite old but near my case.
I have an Alcatel Pop C1 4015X (cpu MTK6572M) that can't start at all (only the power LED is ON).
I have a backup of this device made with "SP Flash Tool V5.1532.00" but I've error "not enough space" when
I try to restore it.
Same error when I try to restore just one file.
For example, I've tried to restore only the "Stock Recovery" you give above.
I do this:
- I start Flash_Tool v5.1532.00
- I open scatter file from my backup done with the same tool
- I unselect all pieces of the backup except "Recovery" and I browse to the "Stock Recovery" file I've dl
from this thread.
I've got this error : "not enough storage space (1011)"
What could be the problem ?
I makes me totally crazy !
By advance, thanks for your help.
Regards,
Freeman.
Click to expand...
Click to collapse
What i did was i used SPFT to flash a backup i found online. Can't post links, just google "ot 4015X Original SPFT ROM", what i used was the algerian rom. Then i flashed the EE stock rom. My own backup didn't flash back correctly either, that's why i used that one i fould online.
4015X unbricked !
Hello,
I found a similar solution here (replace * with . to get a correct http link):
forum*gsmhosting*com/vbb/f317/ot-4015x-firmware-arabic-bulgaria-africa-kenya-1946694/index2.html
It took me hours to find good stock ROMs (bulgarian & arabian then french via OTU) !
You'll have to "play" with pro_info and scatter file...
Good luck to all to unbrick your 4015x !
Regards,
Freeman.
how to partition system storage space of onetouch pop c1?
Hello all,
I'm so dessapointed, i brick my tablet when i want resize but i cant flash with the official firmware (official site " 51cube.com" and "cube-tablet" if you can help me ='(.
Perhaps the firmware is wrong or my manip is wrong, i don't know.
Thx for you help.
Ps : I'm french =)
nofansub said:
Hello all,
I'm so dessapointed, i brick my tablet when i want resize but i cant flash with the official firmware (official site " 51cube.com" and "cube-tablet" if you can help me ='(.
Perhaps the firmware is wrong or my manip is wrong, i don't know.
Thx for you help.
Ps : I'm french =)
Click to expand...
Click to collapse
Hello,
My tablets is good, i flash with the firmware on the site :
h**p://chinagadgetsreviews.com
the link for help.
h**p://chinagadgetsreviews.blogspot.ro/2015/12/download-latest-android-lollipop-51_0.html
Bye
How to?
nofansub said:
Hello,
My tablets is good, i flash with the firmware on the site :
h**p://chinagadgetsreviews.com
the link for help.
h**p://chinagadgetsreviews.blogspot.ro/2015/12/download-latest-android-lollipop-51_0.html
Bye
Click to expand...
Click to collapse
Please can you explain how to use that firmware?
I think it's a recovery firmware for going back to factory defaults when s**t happens.
But I read on some forums that I should backup my IMEI and NVRAM (with MTKDroidTools or something like that...i don't know if there's a specific tool for the Cube T8 Plus) BEFORE trying custom roms, otherwise there will be problems even on restoring stock firmware, right?
Can somebody please make a short-how-to for dummies focalized on this Cube T8 Plus (so poor and confused support on forums yet)?
- Backup before custom rom installation
- Custom rom installation
- Recover to stock firmware
Another question: why that page you linked says "Platform: Mediatek MT6753"
Isn't MT8783?
Thank you very much
my tablet is not bricked now but my serial number and my mac adress is wrong ='(
Use sp tool for save your firmware tablet ( i think).
I have the same problem, after the resizing of partition the tablet is soft bricked and I'm downloading the stock firmware form the above link.
Is there any way to backup the mac address and serial number from softbricked tablet?
...you should have a backup of nvram!
Morgan766 said:
I have the same problem, after the resizing of partition the tablet is soft bricked and I'm downloading the stock firmware form the above link.
Is there any way to backup the mac address and serial number from softbricked tablet?
Click to expand...
Click to collapse
I think it's too late.
I did a backup of nvram with SP Flash Tools BEFORE brick.
When i recovered the tablet after brick, my IMEI was invalid until i flashed my backup of nvram.
Anyone could suggest how and what to backup before trying Root and Resize?
Just backup nvram with sp flash tool
bolija said:
Anyone could suggest how and what to backup before trying Root and Resize?
Click to expand...
Click to collapse
The only unrecoverable partition (for mediatek devices like T8 Plus) is the nvram which contains info about IMEI.
Firmwares/ROMS that we can download from the web never comes with nvram because it's single product related. It's like mac address of wifi cards.
You can find even stock (original) firmwares online, they will bring your tablet back to factory default after a brick.
But if the brick corrupted the nvram, you will NEVER be able to recover it. That means no phone calls and no data connection.
Unless you did a backup of nvram before its corruption.
With SP flash tool you can "read back" from your T8 plus the nvram partition and save it as a file on your pc (file size must be 5MB). Of course you need drivers, SP flash tool and the scatter file. Since i wasn't able to retrieve the scatter file from my T8 plus, I used the scatter included in the stock firmware T8-PLUS_V1.0_20151004.
I am new forum user so I can't post links, but google is enough.
That stock firmware is hosted by baidu, so use browser translation and register an account to get permissions for download.
Remember: in the firmware archive you only need the scatter file! It will tell to SP flash tool where the nvram partition starts and where it ends.
If you will need to restore nvram (e.g. after the unbrick) ,you will have to download to your T8 plus that nvram file with SP flash tool, but before you have to edit the scatter file and set "is_download=true" in the nvram section. Otherwise you will not be able to select nvram in the partitions list from the download tab of SP flash tool.
So the backup will consist in two files:
- nvram file (5MB) (nvram, nvram.img, nvram.bin, extension doesn't matter)
- scatter file with edited "is_download=true" for nvram section
Thanks so much for your help. I think i will be able to backup NVRAM. But im kind of lost on scatter file editing and flash.
Im waiting for Tablet ti arrive