I bought a Cubot GT72 from the net - its basically a chinese knock-off with some very nice specs. And it was working great out of the box; but I had to experiment - right?
Edit: cannot post links; but if you got to www cubot net - you can find the phone easily. The stock ROM is also available.
I fired up MTK-Tools and rooted the phone - no problem there. Then I tried to create a custom CWM and install - that's when things starting going down the drain. It overwrote the recovery and boot partitions - so the phone stopped working. And since then I have been trying various ways to unbrick it.
Luckily, I have another phone with the exact same specs - and was able to download a backup using MTK-Tools and another one using SPFlash.
Problem - the phone is not switching on at all. When I connect it to the computer (after installing the MTK drivers) - nothing happens. When I connect without battery and keep the Up volume pressed - the computer detects an "MTK COM Port", installs it and within 5-10 seconds the port disappears, comes back after 5-10 seconds - and this cycle keeps repeating. I'm not able to connect to the phone using wither MTK-Tools or SPFlash.
When I connect the working phone - it shows up as "MTK VIA COM Port" and I can connect to it using SPFlash.
Have opened the phone and looked for test points - found one that switches on the phone and connects to the computer - but the result is the same as when I connect with the volume up pressed.
Please help - I'm at my wits end.
Drivers
dushyantahuja said:
I bought a Cubot GT72 from the net - its basically a chinese knock-off with some very nice specs. And it was working great out of the box; but I had to experiment - right?
Edit: cannot post links; but if you got to www cubot net - you can find the phone easily. The stock ROM is also available.
I fired up MTK-Tools and rooted the phone - no problem there. Then I tried to create a custom CWM and install - that's when things starting going down the drain. It overwrote the recovery and boot partitions - so the phone stopped working. And since then I have been trying various ways to unbrick it.
Luckily, I have another phone with the exact same specs - and was able to download a backup using MTK-Tools and another one using SPFlash.
Problem - the phone is not switching on at all. When I connect it to the computer (after installing the MTK drivers) - nothing happens. When I connect without battery and keep the Up volume pressed - the computer detects an "MTK COM Port", installs it and within 5-10 seconds the port disappears, comes back after 5-10 seconds - and this cycle keeps repeating. I'm not able to connect to the phone using wither MTK-Tools or SPFlash.
When I connect the working phone - it shows up as "MTK VIA COM Port" and I can connect to it using SPFlash.
Have opened the phone and looked for test points - found one that switches on the phone and connects to the computer - but the result is the same as when I connect with the volume up pressed.
Please help - I'm at my wits end.
Click to expand...
Click to collapse
Ok Google "mt6572 com port drivers" and look for ***.ftdichip.com/Drivers/VCP.***, install the software off that site and see if your computer recognizes the com port, hopefully you'll be able to flash the original rom back to it, let me know how you get on :good:
neosnake991 said:
Ok Google "mt6572 com port drivers" and look for ***.ftdichip.com/Drivers/VCP.***, install the software off that site and see if your computer recognizes the com port, hopefully you'll be able to flash the original rom back to it, let me know how you get on :good:
Click to expand...
Click to collapse
Thanks Neo, The driver is installed - the problem I'm facing is that the phone keeps going offline every 30-40 seconds and hence am unable to flash.
okies
OK thanks for the reply. Its obvious these MTxxxx devices wait for a signal when you plug them in.
1.Try going to the SDK folder and open a command prompt, type fastboot flash boot "boot.img" > point the boot.img to where you have downloaded the original boot.img for the device.
2.When the fastboot gives you the [waiting for device] prompt plug in your phone.
Let me know how you get on, i'm going to be working on a program to flash these phones from windows. :good:
p.s if the above works then flash your original recovery as well
neosnake991 said:
OK thanks for the reply. Its obvious these MTxxxx devices wait for a signal when you plug them in.
1.Try going to the SDK folder and open a command prompt, type fastboot flash boot "boot.img" > point the boot.img to where you have downloaded the original boot.img for the device.
2.When the fastboot gives you the [waiting for device] prompt plug in your phone.
Let me know how you get on, i'm going to be working on a program to flash these phones from windows. :good:
p.s if the above works then flash your original recovery as well
Click to expand...
Click to collapse
Hi Neo - tried. The phone gets detected, but fastboot remains stuck at [waiting for device]. Please see screenshot.
Also, I think the preloader is also gone
Diffrent Drivers
Ok i noticed on there website that there are a different set of drivers, where the ones you have installed emulates a com port the other ones gives you direct access to the USB port, go to adb and type adb devices so that your phone will show up in the device manager, uninstall those drivers and install these ones ftdichip.com/Drivers/D2XX.htm.
Then try and flash the preloader in the usual way, first type flash preloader {name of file} then connect your phone and hopefully you will be able to flash your phone again.
Let me know how you get on again :good:
neosnake991 said:
Ok i noticed on there website that there are a different set of drivers, where the ones you have installed emulates a com port the other ones gives you direct access to the USB port, go to adb and type adb devices so that your phone will show up in the device manager, uninstall those drivers and install these ones ftdichip.com/Drivers/D2XX.htm.
Then try and flash the preloader in the usual way, first type flash preloader {name of file} then connect your phone and hopefully you will be able to flash your phone again.
Let me know how you get on again :good:
Click to expand...
Click to collapse
Apologies for the late reply - tried your method - the phone gets detected as MediaTek DA USB VCOM port - but fastboot or SP flash are unable to detect.
Also, now I have managed to brick the other phone also. Was trying to upgrade the ROM from cubot's website. And even that one is bricked
Really frustrated here.
dushyantahuja said:
Apologies for the late reply - tried your method - the phone gets detected as MediaTek DA USB VCOM port - but fastboot or SP flash are unable to detect.
Also, now I have managed to brick the other phone also. Was trying to upgrade the ROM from cubot's website. And even that one is bricked
Really frustrated here.
Click to expand...
Click to collapse
Also, is there a way I can create a scatter file from the ROM I downloaded using SP Flash?
dushyantahuja said:
Also, is there a way I can create a scatter file from the ROM I downloaded using SP Flash?
Click to expand...
Click to collapse
The full ROM dump has been uploaded here - is there any way I can simply flash the entire dump back into the phone.
http://www.4shared.com/file/wtNcfbRu/ROM_0.html
hi, did you manage to work out anything? i have the exact same problem with my GT72, and i'm out of ideas.
I finally gave up and sent it for repairing. The vendor has been trying to repair it for the last 2 weeks and has given up too. The problem with my phones is that they are not original cubot - the seller on aliexpress is selling fake cubot phones - and we're unable to find the correct files to write to the phone.
Now if only I could find a way to write back the ROM0 file without the scatter files - I had though that would be easy, but am unable to do anything about it
megariffer said:
hi, did you manage to work out anything? i have the exact same problem with my GT72, and i'm out of ideas.
Click to expand...
Click to collapse
dushyantahuja said:
I finally gave up and sent it for repairing. The vendor has been trying to repair it for the last 2 weeks and has given up too. The problem with my phones is that they are not original cubot - the seller on aliexpress is selling fake cubot phones - and we're unable to find the correct files to write to the phone.
Now if only I could find a way to write back the ROM0 file without the scatter files - I had though that would be easy, but am unable to do anything about it
Click to expand...
Click to collapse
maybe i have a fake one, too then. wierd stuff, that is. faking a $60 phone...
anyway, i'm guessing you can only use that ROM_0 file to create a proper preloader.bin for the phone, but you need a working one for that.
you could do that in MTK droid root & tools, but since our phones doens't get detected, we're stumped.
i think having the right preloader could push us to the right direction, but i'm not planning to order a new phone to revive my dead one
anyway, if you make any progress, let us know!
megariffer said:
anyway, i'm guessing you can only use that ROM_0 file to create a proper preloader.bin for the phone, but you need a working one for that.
Click to expand...
Click to collapse
I backed up the ROM_0 file from a working phone (had 2 - broke both); have uploaded it and shared in this thread. So, if you can create the preloader.bin from it - please be my guest.
dushyantahuja said:
I backed up the ROM_0 file from a working phone (had 2 - broke both); have uploaded it and shared in this thread. So, if you can create the preloader.bin from it - please be my guest.
Click to expand...
Click to collapse
i know you uploaded it, but the problem is that i can't do anything with it in MTK droid root & tools, since it only works if there is a working phone connected to the pc.
megariffer said:
i know you uploaded it, but the problem is that i can't do anything with it in MTK droid root & tools, since it only works if there is a working phone connected to the pc.
Click to expand...
Click to collapse
I had even created a scatter file using MTK Droid - the only problem is the scatter doesn't work with the phone. See if it helps you.
dushyantahuja said:
I had even created a scatter file using MTK Droid - the only problem is the scatter doesn't work with the phone. See if it helps you.
Click to expand...
Click to collapse
here's my "progress":
i was able to salvage a preloader.bin from your dump, this was the only one i could get flash tool to start preparing flashing.
i ran into numerous errors after that, but i managed to build a seemingly flashable rom, but it just does not work.
i could format the nand with it, but when i try to flash, it says that the bootlader exceeds partition boundary, whatever that means.
so i'm pretty much stuck at this point, but i'll attach the preloader for you, maybe it will work with your scatter.
the scatter btw did not work for me, since the addresses were wrong (i guess that scatter is for 512MB version, too).
so i built a scatter from scratch with notepad++ it's in the zip, too.
now i just wish there would be someone with a 256MB version able to make a backup with mtk droid and share with us.
megariffer said:
but i'll attach the preloader for you, maybe it will work with your scatter.
Click to expand...
Click to collapse
Thanks - let me try to flash the preloader this weekend and see how things go...
dushyantahuja said:
Thanks - let me try to flash the preloader this weekend and see how things go...
Click to expand...
Click to collapse
how's it going?
arsenal3008 said:
how's it going?
Click to expand...
Click to collapse
Didn't get any time last weekend - will update this weekend.
Wrong firmware.
dushyantahuja said:
Didn't get any time last weekend - will update this weekend.
Click to expand...
Click to collapse
Hi, the same problem, have you figured it out? Thanks for your help ...
Hi everyone,
First of all, I have some basic knowledge but treat me as an absolute noob please
I have a issue with my Huawei Ascend G700-U10. I tried flashing twrp recovery from the phone itself. It was either a wrong one or (I read that that could happen) something with the partition. The result is a boot loop. My PC does recognise the decive, but only for a few seconds. The flash tool does "try" flashing, but as the phone is disconnected too fast, I get an error message. Without much experience, I'd say that the only way I could flash something is making the phone stay connected longer or make the program flash faster. I have no idea how to make the phone stay connected and tried to only flash the stock recovery because I thought it would have to flash less and get it done in those two seconds that the phone stays connected. That didn't work though.
I thought about buying a new phone anyway, so if I can't solve it, it's not dramatic, but a working phone is always better than one that doesn't.
Thanks for your help in advance
Hi, thank you for issued XDA Assist. I think you're right that you need to flash the stock firmware. I'm not sure why usb would keep disconnecting but try different usb ports, the ones in the back of your pc, and cables.
Thread closed.
Hi there,
Today i've received this tablet. All good and dandy until it notified me it has an update so obviously i've gone and do the update. Surprise.. after reboot, update installment and so on the device won't boot anymore at all, and recover mode doesn't work to enter.
I've found official ROM package on their site:
ftp.vonino.org/public/Firmware/Vonino_Tablets/Pluri%20Q8/Orange%20Version/Android%206.0/
Tablet can connect to the PC, but it isn't recognized because "some drivers" missing. How can i install this ROM on the tablet from my pc ?
Thank you.
Hi,
I can't find anything about it on xda or anywhere. You'll need to contact the manufacturer for drivers and instructions on flashing their firmware.
Good luck!
After i tried like almost the entire day i got the tablet in rescue mode or fastboot mode..
I've wiped/data or factory reset and the same happens... it stays in a loop when boot at logo.
I've let it to do so until the battery went dead from 100% and still the same.
I have official ROM but can't install it at all. I think the bootloader is locked?! And it doesnt even unlock it when using some fastboot commands
Also can't install nothing from SD card and when tryin to use ADB the PC can't see the device, but when using fastboot I can work on it.
In rescue mode i've done some root integrity check and at the end of the check some /system files are modified. I believe this is causing the entire problem.
denede said:
After i tried like almost the entire day i got the tablet in rescue mode or fastboot mode..
I've wiped/data or factory reset and the same happens... it stays in a loop when boot at logo.
I've let it to do so until the battery went dead from 100% and still the same.
I have official ROM but can't install it at all. I think the bootloader is locked?! And it doesnt even unlock it when using some fastboot commands
Also can't install nothing from SD card and when tryin to use ADB the PC can't see the device, but when using fastboot I can work on it.
In rescue mode i've done some root integrity check and at the end of the check some /system files are modified. I believe this is causing the entire problem.
Click to expand...
Click to collapse
Typically, on devices I know of, it's fastboot that you would use to flash factory images. So you should be good there. But again, I don't know if that is how your device works too. And it would also typically not matter what's been altered on your device, system wise, you would simply flash the appropriate images with fastboot.
So I'd still say you need to determine the correct procedure to flash the files you got from their site. Perhaps there site has instructions? Or a support number for help of its not working as it should?
I've talked with the support. They gave me a link with an official ROM, a different one that the one that was from the site. But they didn't even told how to use it, LOL.
Have the damn files and don't know what to do with them, OMG.
I've placed the zip archive on SD card and tried to use the option from rescue mode with 'update via sd card". The zip archive is visible but after i select it says Installation aborted :|
I've googled around and maybe my tablet needs to be at over 50% power... but it was plugged into the wall it should've worked.
edit: 100% and no good...
edit2: they sent me another e-mail with a pdf file in which it is explained how to flash their device.
Hi,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.
I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.
So I have 10 years of experience of rooting phones and flashing roms etc and I think this is the first time I really bricked my phone and until now did not find i solution my self.
So how got it bricked: I was on my work, in a bit of a hurry and wanted to update my phone (dirty flash) through TWRP but the installation hanged at the last 1% or such. I let it sit for 30 min. still hangs so decided to abort and do a clean flash but again the update hangs (maybe bad download?) but along the way (probably because I was at work and didn't take the time) I think I ****ed up switching partitions or something and now I have no OS installed on my.
I can boot in to Fastboot mode, TWRP EDL mode and such
But I can't flash an new OS through TWRP because it says the following: Unable to find Partition for path '/system_root' (will post screenshot when I get home from work )
I tried MSM tool but until now I could not get the tool to see my Phone so now I am calling for the help of the XDA Community!
So do you guys have any suggestions wich wil unbrick my phone?
Try running msm from different port on your pc. Preferably a 2.0 usb if you have. Many times makes a difference. Also make sure your adb drivers are updated to latest. Many threads around talk about it.
Extracted boot file from original oneplus rom, flashed that with fastboot and like magic my problem was solved