Related
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 ...
It took me days trying to make Doogee send me these files. I managed to unbrick my device with this firmware.
So I decided to post it here so anyone can unbrick ther Y100X.
It must be used with SP Flash Tool, here is the link to the thread: Flash Tool
This is the firmware :laugh: (extract with 7zip): --files removed--
For me it worked with the Format All + Download option.
-The firmware is stock and provided by Doogee. I got nothing to do with the making of the files. I also do not get paid for providing these files. I just wanna help others. -
Link sharing is on now. Sorry for forgetting about this.
thanks for el firmware, now how to get the root ... xD. My smartphone is underway yet, cost me $ 70
Root can be achieved through kingroot. But it is an app I personally hate, so I used some KingRoot to SuperSU apps and they worked,so good luck!
Many thanks for the original Firmware :highfive:
I hope there will upgrade to 5.1 or a dream.
Hello
i got trouble with that Y100X, tried to root it with KingoRoot, then i want to replace Kinguser with SuperSu, after that it ended up in Bootloop (showing DooGee logo then reboots). SP Flash Tool won't start (also tried to find Phone with adb but it always reboot to fast and don't connect)
Any thing i can do?
nickless07 said:
Hello
i got trouble with that Y100X, tried to root it with KingoRoot, then i want to replace Kinguser with SuperSu, after that it ended up in Bootloop (showing DooGee logo then reboots). SP Flash Tool won't start (also tried to find Phone with adb but it always reboot to fast and don't connect)
Any thing i can do?
Click to expand...
Click to collapse
Excuse for machine translation.
Took the information from 4pda.ru on this phone.
I quote: "Yesterday did the same thing, got the same) to the office. Site doogee rocked tools for model valencia 2. Including VCOM driver and flasher. The drivers stood on XP vlёt. Ask insertion of a cap according to the instructions of the threads about Flash Tool. Read the instructions and firmware itself took less time than the jump firmware) So do not be scared) is Ruth will not put. How then do not need to.
Briefly: 1 swing tools here https___drive.google.com/file/d/0B-eEVUUoOlT4QzZwZE54LTVFWms/edit?pli=1
2 swing firmware from the link in the header of the topic and its extract 7zip archiver;
3 Turn off the phone, connect it to a computer, manually set VCOM driver from the archive with the tools, disconnect the phone;
4 launch Flash Tool, look for a file scatter in the folder where you unzipped firmware
5 remove the checkbox PRELOADER
6 click DOWNLOAD, connect the cable to the computer off the phone and wait for the flashing 100%
7 disconnect the phone from the computer, and run the long wait until the turn
8 all
I hope that helps
ps in reference to replace ___ :// - new users can not link
ariss77 said:
Excuse for machine translation.
Took the information from 4pda.ru on this phone.
I quote: "Yesterday did the same thing, got the same) to the office. Site doogee rocked tools for model valencia 2. Including VCOM driver and flasher. The drivers stood on XP vlёt. Ask insertion of a cap according to the instructions of the threads about Flash Tool. Read the instructions and firmware itself took less time than the jump firmware) So do not be scared) is Ruth will not put. How then do not need to.
Briefly: 1 swing tools here https___drive.google.com/file/d/0B-eEVUUoOlT4QzZwZE54LTVFWms/edit?pli=1
2 swing firmware from the link in the header of the topic and its extract 7zip archiver;
3 Turn off the phone, connect it to a computer, manually set VCOM driver from the archive with the tools, disconnect the phone;
4 launch Flash Tool, look for a file scatter in the folder where you unzipped firmware
5 remove the checkbox PRELOADER
6 click DOWNLOAD, connect the cable to the computer off the phone and wait for the flashing 100%
7 disconnect the phone from the computer, and run the long wait until the turn
8 all
I hope that helps
ps in reference to replace ___ :// - new users can not link
Click to expand...
Click to collapse
SP Flashtool don't find phone. All drivers installed. Phone goes in fastboot or stock revocery only.
I wish i could get adb shell :crying:
Is there any way to flash system partition in Fastboot or sideload?
thank you
Hi brother
Thank you very much for the ROM, it help me a lot.
nickless07 said:
SP Flashtool don't find phone. All drivers installed. Phone goes in fastboot or stock revocery only.
I wish i could get adb shell :crying:
Is there any way to flash system partition in Fastboot or sideload?
Click to expand...
Click to collapse
Try to flash without the battery, rather than simply turned off the phone.
You my friend are a saviour.
Tried rooting and bricked my phone, Kingroot wouldn't work so tried the Kingo apk which bricked it.
Back to square one now so will wait for a verified root
Thanks :good::good::good::good::good::good::good:
Hi can with this repair an bootlop on the doogee nova y 100x .when i turnt off the phone ??
Sent from my Valencia2_Y100pro using XDA Free mobile app
Got my mother in law a doogee y100x. Apparently Google plus won't install on it. Did anyone face this? Is there a workaround?
Hi.
I had the bootloop problem, and I've solved with this firmware. (Many thanks TheSpecialNoob)
In order to FlashTool detects the phone, needs to be power off, without enter in FlashTool mode.
Select a scatter file, choose "Format All + Download" and press Download.
Thats all.
Custom recovery Doogee Nova Y100X
By the way, someone has managed to stick a custom recovery??? like the CWM or TWRP. If so, could you explain how you did, or upload the recovery.img file for the FlashTool?.
Thank you
zagzag99 said:
Got my mother in law a doogee y100x. Apparently Google plus won't install on it. Did anyone face this? Is there a workaround?
Click to expand...
Click to collapse
It's a problem on all Y100X devices. Doogee must have messed something up in the build.prop I hope they release an official fix.
Carliv Touch Recovery v3.3 for Doogee Nova Y100X
fanjul said:
By the way, someone has managed to stick a custom recovery??? like the CWM or TWRP. If so, could you explain how you did, or upload the recovery.img file for the FlashTool?.
Thank you
Click to expand...
Click to collapse
I auto-answer.
I found a Russian website, which explain how to install a custom recovery (Carliv Touch Recovery v3.3). :good:
I leave the link to the page. http://4pda.ru/forum/index.php?s=&showtopic=669833&view=findpost&p=42555995
If someone is not able to install it , I can try to explain it.
Also I have kept all the necessary files.
Regards
greetings from Spain
Thanks for giving us the original ROM.
I followed your steps and selecting "Format All + Download" I deleted the imeis and as I have read on the internet, also the NVRAM.
As I can do to permanently leave imeis? every time I have restored the ROM to modify and not know if I deleted more things to do a "Format ALL"
Someone I can pass the "NVRAM.bin" to upload it to my phone? Any other suggestions?
[email protected]
Regards
Yeah, I have the same problem. After restoring the stock rom, I have lost NVRAM settings.
Someone who has not restored the phone to stock, can upload the file nva.bin phone.
Thank you
I do not have 10 posts yet, remove underscores from urls. I will edit this when I have 10 posts, I'm sorry for the slight inconvience.
Hi, new here! I recently acquired a Motorola G7 (xt1962-1/river_amz) from my sister. The device did not boot. It mentioned that the device did not start-up successfully, something in relation to slot/a and slot/b, and that I needed to utilize a Software Repair Assistant.
Non-Verizon devices cannot utilize this Software Repair Assistant, I tried and it hung at Processing Device Info. For Non-Verizon devices there's a piece of software called Lenovo MOTO Smart Assistant which can be found: https://support.lenovo.com/us/en/downloads/ds101291
This option did not work for me as the Bootloader did not for some reason allow the device to overwrite some of the content (permission was denied device side.)
The MOTO Smart assistant was good for downloading the devices software. So you do the following:
Download and install the smart assistant software
Click the flash option and then the rescue option
Click moto phone
Select moto g (7th gen)
Select xt1962-1 and then next to target and firmware name there's a download button press that and the firmware will start downloading
You can follow the onscreen instructions for that program, like I said however, it didn't work for me so I'm just going to tell you the steps I went through to get the device working. If you have other solutions, I, as well as the rest of the MOTO G7 users will be happy to hear what worked for you I'm sure.
I tried downloading the files from /moto-g7/development/moto-g7-river-xt1962-1-firmware-29-114-t3913673 on this site and flashing those with some of the below mentioned methods but, no dice.
The default firmware download directory is C:\ProgramData\LMSA\Download\RomFiles btw.
I didn't want to fuss with trying to get RSDlite working on Windows 10. I found that an older PC with a 32-bit install of Windows 7 was far easier to manage, so, that's what I went with.
To follow what I did:
Download RSDlite 6.2.4 from rootjunky's site via: http://rootjunkysdl.com/files/?dir=Android Programs
Download 32-bit drivers from: http://rootjunkysdl.com/files/?dir=Android Drivers/Motorola if LMSA did not install them already
Copy the firmware folder to your desktop or somewhere easy to work from
Ensure your device is in bootloader mode
Open RSDlite and your device should be detected
Select the firmware folder and open flashfile.xml with RSDlite and press start
Let the process finish and don't interupt or you will have to do it all over again
The phone should boot, you will more than likely have to sign into an google account that's already been in use on that device (due to FRP)
You can also use the XML to BAT method, that didn't work for me (remote permission denied/device side)
I hope this helps some people who struggled like I did. Also, sorry if some things are badly worded if at all. I'm autistic and have trouble explaining and expressing things.
Check out my stock resources thread: https://forum.xda-developers.com/moto-g7/development/riveramz-stock-resources-t3917937/
Worked perfectly!
Thanks! I had the same issue (my wife's Moto G7 stuck at the bootloader) and was able to follow your directions, so much appreciated.
The only change I made was to follow the directions at this video (go to youtube/watch?v=njXQYn53SPc) to perform the XML to BAT instead of using RSDlite (since I was on Windows 10).
It worked perfectly and fixed the issue--and the great thing was that by converting the servicefile.xml instead of flashfile.xml, I was able to retain all the data on the phone.
The overall sequence of steps (listed in detail, since this was my first time flashing. Remove underscores from URLs):
Download Lenovo Assistant from your link
In Lenovo Assistant, go to Flash, then Rescue, then select model of phone. Click to download the firmware (but do not actually click the "rescue" button).
Download Google's Platform Tools (to get fastboot and ADB)
Make a folder to hold everything (called "flash")
Copy the downloaded firmware folder from C:\ProgramData\LMSA\Download\RomFiles to flash folder. Copy the fastboot, adb, and adb dll's from the Platform Tools to the firmware folder (per the video).
Copy and edit commands from servicefile.xml to a new servicefile.bat, as described in the video. Place this file in the firmware folder.
Run batch file in command prompt from the firmware folder.
That got the phone running again, with all data intact.
Thank you so much, worked like a charm.
Mine doesn't seem to have any partitions anymore. All my phone does is fast boot mode. And it won't let me flash anything... Please [email protected]
Sent from my Samsung SM-G973U1 using XDA Labs
mattmsr82 said:
Mine doesn't seem to have any partitions anymore. All my phone does is fast boot mode. And it won't let me flash anything... Please [email protected]
Click to expand...
Click to collapse
May need to use a
Loader file or blankflash
See
https://forum.xda-developers.com/moto-g7/help/loader-file-to-unbrick-moto-g7-t3938342.
Sent from my mata using XDA Labs
I followed sd86's guide and used servicefile.xml instead of flashfile.xml, as suggested by chi2.
No problems whatsoever installing RSDlite 6.2.4 on Windows 10 x64 (1909). The drivers were installed by LMSA and I have no idea why you guys said it was difficult.
Just for the record, my phone is a Motorola G7 (xt1962-4), that out of thin air started showing the following message:
start up failed
your device didn't start up successfully.
use the software repair assistant on computer
to repair your device
connect your device to your computer to get
the software repair assistant.
AP fastboot flash mode (secure)
no bootable a/b slot
failed to boot Linus.falling back to fastboot
Fastboot reason: fall-through from normal boot mode
USB connected
Click to expand...
Click to collapse
MrCabana said:
I followed sd86's guide and used servicefile.xml instead of flashfile.xml, as suggested by chi2.
No problems whatsoever installing RSDlite 6.2.4 on Windows 10 x64 (1909). The drivers were installed by LMSA and I have no idea why you guys said it was difficult.
Just for the record, my phone is a Motorola G7 (xt1962-4), that out of thin air started showing the following message:
Click to expand...
Click to collapse
I ended up sending my phone back to Motorola, they they fixed it and sent it back overnight...
Sent from my Samsung SM-G973U1 using XDA Labs
Quote:
Originally Posted by NetrixX13
I had exactly the same problem. The Lineage OS installation instructions are missing an important point.
The Moto G7 has two slots, A and B. However, it seems they only come with a bootloader pre-installed on slot A, slot B seems to be completely blank.
When slot A is active and you flash Lineage OS using TWRP, it writes to slot B and switches to slot B.
When you reboot, you cannot boot anymore, because on slot B there is no bootloader.
To mitigate this issue, you have to flash a "copypartitions" zip before rebooting.
My phone also was in 9008 mode and I revived my Moto G7 using the blankflash method, see here:
https://forum.xda-developers.com/mot...reteu-t4020263
I can also confirm saving my Hard bricked, non booting black screen, no life moto g7 with the above blank flash app from above link. then i used the lenovo recovery program to put the original rom back on the phone downloadable here: https://support.lenovo.com/us/en/downloads/ds101291
if you have a black screen hard brick, no life but windows 10 sees it at an unknown or 9008 device then you can bring your moto g7 back to life again. follow all the above links and youre good!
I don't have a Windows 10 PC...plus, if I screw up my phone, I'll catch hell from the wife...lol
SO...that being said, if someone has an XT1962-6 'River' RETIN phone running Android 10 w/June Sec. Patch....I'd be willing to 'donate' to their paypal for a copy of my phones fw! Anyone interested plz pm me. Thx!
Good day, your post was very useful for me, bring back my phone, Im very grateful, thanks, sorry for my english
switch off your phones and connect usb.
first install drives to your pc by searching where to find device drivers motorola
then download lenovo smart assistant and press rescue
Hi. Im new here too. Well been for a while just my second post and the first time iv actually been able to flash a rom. I have the same problem. No bootable slots. I know exactly what i did wrong. I knew it the moment i hit the reboot button. However, i run zorin 15 on my pc and the levono assistant don't support linux. Anyone know where i can acquire the assistant running linux? Greatly appreciated in advance.
Thank you very much sd86 and chi2 for your research and help
Sadly my phone can't boot after flashing clean OS
I don't want to erase UserData partition, but it seems error is there (as it's only left partition untouched).
As I still would like to keep my data (this is the most important thing on our mobile devices) the only one hope is to unlock bootloader, flash recovery partition (eg. with TWRP) and then perform a backup from recovery software.
I'm the lucky one to get this scarce BRICK problem, my pixel 2 occasionally run into this, can't boot up any more, no bootloader, recovery,
plug into the pc, it always tell qualcomm hs-usb qdloader 9008,
had searched out all the forum, need to use QFIL to flash correct, prog_emmc_firehose_xxxx.mbn, together with rawprogram_XXX.xml.
what is that ? anyone happen to know where to get it ?
any idea is pretty appreciated.
I found this for you: https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868/page1
@misslebulletttttt did you fix your Pixel. If yes, how did you do that?
download > Tool all in one. Update it. update the drivers button at the bottom. now....... choose your phone. now choose flash factory image button.
it go to page where you pick the right firmware for you phone. press the download link. go back to Tool all in one and find the file you just download and then flash it with the button.
Tacis said:
@misslebulletttttt did you fix your Pixel. If yes, how did you do that?
Click to expand...
Click to collapse
sadly, the files that download tool asked was far proprietary, I'm not able to peek it a bit
I'm not saying these will fix or even do anything but I found them and maybe they can help you there Qualcomm usb drivers. I apologize if these are of no use.
I will just post here in case someone has the same issue and might contribute with the files...
Basically an Android device has a few steps of initialization
- power on
- initialize cpu and memory
- load bootloader
- bootloader selects boot mode
- having the boot selected, the kernel and device tree are loaded
- drivers are loaded
- system is loaded
- userdata is decrypted
Ok... So knowing that, when we want to write some partition on the device, we use fastboot. But first, the fastboot must have oem unlocked in settings. Well when unlocking in settings, this write in a protected partition (don't remember which one) which is checked if the fastboot can run some commands.
Well the next step is... Where is fastboot located?
Well, fastboot is located inside the bootloader. So, what?
Imagine that there isn't anything written in the memory... What would the processor do? It would think... Well nothing there... But must access the memory. So the cpu opens a port which is known as the emergency download mode (EDL).
EDL mode can be triggered with adb command or by shorting test points (there's another way, but I won't say it here)
Anyway when in edl mode, the processor talks a defined protocol, which is known as firehose.
So the first file you mentioned:
prog_emmc_firehose_xxxx.mbn
Is the programmer for the specific chipset, in order to make a handshake and allow to write.
Then after the handshake, you need to define how the memory will be partitioned (remember... It is considering a raw memory, with nothing on it). This lead us to the second file:
rawprogram_XXX.xml
This is basically how the memory is partitioned and where the image address is.
Besides those files, you need the img files (which will probably be only the system.img non sparsed i think...) And patch.xml too, probably.
But remember... The programmer needs to be signed and for the chipset... So if anyone has any contact with google... Maybe we can get those in order to unbrick devices... Anyway...
I just wanted to have those files, in case i run into a bad update...
I think we have to contact the carrier according to the bootloader files
misslebulletttttt said:
I'm the lucky one to get this scarce BRICK problem, my pixel 2 occasionally run into this, can't boot up any more, no bootloader, recovery,
plug into the pc, it always tell qualcomm hs-usb qdloader 9008,
had searched out all the forum, need to use QFIL to flash correct, prog_emmc_firehose_xxxx.mbn, together with rawprogram_XXX.xml.
what is that ? anyone happen to know where to get it ?
any idea is pretty appreciated.
Click to expand...
Click to collapse
Hello friend! I have the same problem as you! (Hard bricked Pixel 2 and can't find firmware files for flashing device(via QFIL or QPST)). Do you have any progress on this issue ?
I don`t know where to go with this problem except for this forum
Hi, have you found a solution to this problem? I got a hard brick after the update (
Any update from anyone please?
bmw9651 said:
download > Tool all in one. Update it. update the drivers button at the bottom. now....... choose your phone. now choose flash factory image button.
it go to page where you pick the right firmware for you phone. press the download link. go back to Tool all in one and find the file you just download and then flash it with the button.
Click to expand...
Click to collapse
What does any of that mean? There is no download for a, tool all in one around here.
This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch
KaptinBoxxi said:
This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch
Click to expand...
Click to collapse
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.
JayTM said:
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.
Click to expand...
Click to collapse
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.
KaptinBoxxi said:
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.
Click to expand...
Click to collapse
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.
JayTM said:
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.
Click to expand...
Click to collapse
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to
KaptinBoxxi said:
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to
Click to expand...
Click to collapse
Good luck to you.
I contacted TCL support myself with no luck. They immediately put my case in pending close status.
Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.
JayTM said:
Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.
Click to expand...
Click to collapse
I'll check it out. If its possible to view the code in a tool like dnSpy or extract files from the exe with 7zip, its possible to use with our device, i'm sure as long as the commands are similar
Well you're in luck as it is just a .bat file program simple notepad++ will do.
I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.
Tech101yt said:
I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.
Click to expand...
Click to collapse
Have had the phone for less than 6 months and I'm already having LCD issues. When the display is off, just sitting on a table or something, it'll flash white randomly like its getting an electric signal at random. Its nothing I did. I've never hard dropped the thing. Everywhere I go pretty much is carpeted except work. If manufacturer warranty doesn't cover me, I'll stop recommending the phone to people
I actually switched to an Essential Phone recently. Way better experience, way cheaper too. I have around a dozen of them anyway and have been selling em on swappa (dunno if I'm allowed to say that here, but oh well) lol
@KaptinBoxxi Sounds like you have Ambient Display on for notifications.
mschoolbus said:
@KaptinBoxxi Sounds like you have Ambient Display on for notifications.
Click to expand...
Click to collapse
Nah its turned off. It flashes like a broken LCD would look. All snowy and stuff like an old TV. Its not notifications, just a bad LCD
that sucks... could try reseating the screen's ribbon cable :-/
can anybody share the full update rom about android 11?
top170 said:
can anybody share the full update rom about android 11?
Click to expand...
Click to collapse
I don't believe anyone has Logcatted the update process yet to get the firmware, but on the subject of this post, I do have some updates
I was digging through my Logcat from january and realized I missed something massive. I have yet to figure out the URL structure, but I have all the info for it.
So when you go to the following link, it gives a bunch of errors of missing info
https://g2master-sa-east.tclclouds.com/notify_new.php
For the firmware here on this post at least, each value from my device is
Code:
id = 0156260
curef = T799B-2ALCUS11
vk = 741ace917e3527af81412ca93b0fcce2de04a264
salt = 1611977254070885419
fv = 4DJ1LM10
tv = 4DJBLMB0
op = 1000
status = 999
mode = 2
cltp = 10
type = firmware
formatted from logcat
reportContent= {"id":"0156260","salt":"1611977254070885419","curef":"T799B-2ALCUS11","fv":"4DJ1LM10","tv":"4DJBLMB0","mode":"2","cltp":"10","type":"Firmware","op":"1000","status":"999","vk":"741ace917e3527af81412ca93b0fcce2de04a264"}
no matter what, I get the errors on the web page