Boot-loop with no o/s Zte Grand X Z777 Qualcomm chipset - Android Q&A, Help & Troubleshooting

I rooted my ZTE Grand X Z777 w/Qualcomm chipset... Android is Jelly Bean 4.3 and Cricket Wireless is the vendor, (but I'm an American and I live in Omaha, Nebraska, United States....) I rooted with Kingoroot without doing enough research like a dummy and I lost power before I got a custom recovery installed. I flashed with TWRP and it erased everything on the phone. I need a stock rom that is not MT6572. My imei is (was)... 864642021470202... I see the same MT6572.zip on every site and I've checked at least 100. The thing is... Zte made more than one Grand X Z777. This is the MTK chipset and everyone in America that I've talked to are all looking for the Qualcomm chipset. Jelly Bean 4.3 (not 4.2), and snapdragon 200 or 220. I don't understand why people think that you can flash a Qualcomm chip with an Mtk image, system, boot... Please tell me how if it can be done... It's all wrong and it doesn't work. Nothing works. The driver is Z777 and it's in my C:\Windows\System32\drivers\UMDF\WpdMtpDr.dll and I had to write some code to even get anything done at all. I'm just going to ask XDA because everyone has got it wrong for this phone. Mine was stuck at 0% right after the logo screen trying to load an upgrade from sd card. Wouldn't get reconized by windows unless I held down both volume buttons with power off and plugged it into pc. Adb, fastboot, Ubuntu, would not see it. Error: device not found 'null'... I finally managed to get recovery on it by magically unlocking the bootloader of a device stuck in bootloop and not recognized. Not sure how I did it but I did. I did an md5 check and 6 files were wrong. So I had no radio, imei, no ip address, no mac address.... No way to update but I got usb debugging turned back on and still could not find a stock rom that would work. Now it's back in a bootloop trying to load an update from sd card and the bootloader is locked again... HELP...????..... PLEASE??????????? my email is [email protected] or [email protected].com

chadmaller4444 said:
I rooted my ZTE Grand X Z777 w/Qualcomm chipset... Android is Jelly Bean 4.3 and Cricket Wireless is the vendor, (but I'm an American and I live in Omaha, Nebraska, United States....) I rooted with Kingoroot without doing enough research like a dummy and I lost power before I got a custom recovery installed. I flashed with TWRP and it erased everything on the phone. I need a stock rom that is not MT6572. My imei is (was)... 864642021470202... I see the same MT6572.zip on every site and I've checked at least 100. The thing is... Zte made more than one Grand X Z777. This is the MTK chipset and everyone in America that I've talked to are all looking for the Qualcomm chipset. Jelly Bean 4.3 (not 4.2), and snapdragon 200 or 220. I don't understand why people think that you can flash a Qualcomm chip with an Mtk image, system, boot... Please tell me how if it can be done... It's all wrong and it doesn't work. Nothing works. The driver is Z777 and it's in my C:\Windows\System32\drivers\UMDF\WpdMtpDr.dll and I had to write some code to even get anything done at all. I'm just going to ask XDA because everyone has got it wrong for this phone. Mine was stuck at 0% right after the logo screen trying to load an upgrade from sd card. Wouldn't get reconized by windows unless I held down both volume buttons with power off and plugged it into pc. Adb, fastboot, Ubuntu, would not see it. Error: device not found 'null'... I finally managed to get recovery on it by magically unlocking the bootloader of a device stuck in bootloop and not recognized. Not sure how I did it but I did. I did an md5 check and 6 files were wrong. So I had no radio, imei, no ip address, no mac address.... No way to update but I got usb debugging turned back on and still could not find a stock rom that would work. Now it's back in a bootloop trying to load an update from sd card and the bootloader is locked again... HELP...????..... PLEASE??????????? my email is [email protected] or [email protected]
Click to expand...
Click to collapse
I suggest that you go to this link https://www.zteusa.com/zte-grandx#support and contact the support team (Contact Support) instead.
And no, Mediatek software WILL OBVIOUSLY NOT WORK on qualcomm hardware!
Edit: I found this! https://www.stockrom.net/2017/08/st...nd-x-z777-cricket-android-4-3-jelly-bean.html
Not sure if it's for Qualcomm version or MTK, but you can try it (password for archive is given in the article).

Still searching
Well I still haven't found firmware but I have a bunch of bin files from the automated server QPST. I just found them but now what? And ZTE is no help. They won't even tell me why some Z777's are msm8210 and some msm8610... Found out there's also serious problems with both of those boards. They want me to send it in and pay more than what the phone even costs. It's stuck in recovery mode trying to load an update and there is no menu. Stays at 0%

Related

[Q] Alps S5 octacore, ROM readback and root

Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
gt56 said:
Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
Click to expand...
Click to collapse
Hi
1) First root your device using MTK Chopper (from PC) or framaroot (from android app) . Both work fine for MTK phones
2) Then using MTK droid tools backup your ROM. Here is the guide for that
http://forum.xda-developers.com/showthread.php?t=2730031
3)Then using MTK droid tools , make CWM recovery for your phone and install it . Here is guide for that
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
Hit THANKS if it works
4shreyas said:
Hi
1) First root your device using MTK Chopper (from PC) or framaroot (from android app) . Both work fine for MTK phones
2) Then using MTK droid tools backup your ROM. Here is the guide for that
http://forum.xda-developers.com/showthread.php?t=2730031
3)Then using MTK droid tools , make CWM recovery for your phone and install it . Here is guide for that
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
Hit THANKS if it works
Click to expand...
Click to collapse
I think you mean MOTO Chopper? It doesn't work, same as framaroot. They are old tools, they don't work anymore on the ROMs released after June 2014.
ODIN could work but I have not the sure/right file to download.
Generally speaking, the first thing to do is that of getting a backup of the ROM from the un-rooted phone
The guides that have been reported to work in these cases are:
From XDA:
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
From China Devices:
http://www.china-devices.com/Thread-ROOT-CWM-Readback-your-ROM-with-SP-Flash-Tools#
Hereunder is the link to a success case story:
http://www.china-devices.com/Thread-Rooting-new-octacore-S5
There is no way I know to get the root with one-click-tools, there is no case I could find of anybody being able to root these phones by following other procedures.
If anybody knows better, please send me a link (MTK phones with ROM s released after june 2014 only!!!)
My only problem now is that I cannot get the read back with Flash Tools. I have tried uncountable button-pressing combinations, I have put the phone in recovery, download, fastboot mode, I have tried with and without battery, phone switched off or on - no error, but the read-back doesn't start (however my phone doesn't have the USB connection working when it's off or without battery).
The only way to skip this step is, if I had already a copy of the firmware available, a sure one.
Kindly help me if you can
Hi
Odin doesn't work for MTK mate
Try this latest app . It worked for some latest MTK KK phones
http://www.kingoapp.com/index.htm
Some other KK phones got rooted using vroot and rootgenius
Try your luck
Final option is to read back from SPFT which has 90+ success rate
Link to your stock firmaware: ( Official ROM Kingelon G9000 Version: 20140710_e2706v92_jbla_fhd -> This model number matches with model no in your image)
http://www.needrom.com/download/alps-star-kingelon-g9000-style-s5-touchwiz/
As bizarre as this sounds, I managed to get root on a similar phone (another MTK6592 S5 knockoff) with MTK tools. After exhausting my options, I clicked the ADB button and tried to get root shell regardless (via 'adb root shell', which probably isn't the proper command but it works regardless), which caused some sort of hang. After a minute or so I unplugged my phone, which caused things to start responding again; plugging it back in showed me as having temporary root, and the get root button actually worked the next time I tried it. I have no idea how or why it worked, or if it was a once in a lifetime occurrence, but it can't hurt to try.
Also, if your phone is anything like mine (and is actually running some form of KitKat), good luck getting write support for external SD cards. I couldn't get the system partition to mount (to write changes to the necessary file) via anything but ADB shell.
Problem solved
Good to know, thank ypu.
However in the meantime I solved my problem.
My phone works this way: I have to remove the battery and connect it to the USB cable. Then it goes in "preloader mode" and tries to install a driver called "MT65XX preloader driver". This driver actually emulates a COM port. If data transfer doesn't start, then, after a few seconds, the device goes down and disappear from Windows list. So it is easy to miss it when we install all drivers. I had to dowload it (from Google cloud service in my case), install and ... the Read Back started !!! Now I have completed the procedure and my phone is rooted with the CWD recovery installed.
ALPS S5 phone, real FLASHROM total size, 64GB ext SDcard not working
FEGuy said:
As bizarre as this sounds, I managed to get root on a similar phone (another MTK6592 S5 knockoff) with MTK tools. After exhausting my options, I clicked the ADB button and tried to get root shell regardless (via 'adb root shell', which probably isn't the proper command but it works regardless), which caused some sort of hang. After a minute or so I unplugged my phone, which caused things to start responding again; plugging it back in showed me as having temporary root, and the get root button actually worked the next time I tried it. I have no idea how or why it worked, or if it was a once in a lifetime occurrence, but it can't hurt to try.
Also, if your phone is anything like mine (and is actually running some form of KitKat), good luck getting write support for external SD cards. I couldn't get the system partition to mount (to write changes to the necessary file) via anything but ADB shell.
Click to expand...
Click to collapse
Maybe your phone was using firmware dated before june 2014? These was a bug that was exploited by Framaroot, but now they fixed it.
Is your phone also from ALPS? They sold it to me as capable of installing an external 64GB SDHC card, but I cannot have it working. Did you face any similar issue?
Otherwise 32GB cards work fine. Have you tried Aparted app? I use it for formatting/maintenace. This app makes partitioning, I guess it should work.
Also, if your phone is from ALPS, does it really have the ROM memory that is advertised?
I am facing some interesting issues with my phone on this respect. It was sold as having 16GB internal ROM, of which about 12GB avalible for users. In fact, the settings menu shows 10GB ,( 8GB available) of internal memory, and about 4GB of phone memory. Well, if I am correct, this so called internal memory maps to the directory /data (the one highest level in the root), who corresponds to partirtion mmcblk0p7. This partition actually has a size of 2.3GB instead of 10 !!!. f I install and try to run online Nandroid backup, I cannot have it working on paths directed towards the SDcards, but it works on the path data/media. Well, a backup of about 1.2GB is shown in the setting menu of the phone as a memory consumption of about 5 GB !!!
Then I had also hard time in copying this file from the /data directory to one of the SD cards. Root Browser and Root Explorer didn't work, only ES Manager with root rights worked.
Maybe you can give me some advice in finding some tool or SDK procedure to assess what the real total size of the memory is? Or some suggestion on how to fix the ext 64GB card? I got bad feelings with the guys who sold this phone to me, so I would like to collect some more evidence if possible.
I downloaded some applications for making device inspection. They read the manufacturers' data, so they get cheated - even if, in some cases, they can show the right amount of unused memory still available (quite lower than declared by the phone) . Also I cannot see the real size of the RAM memory used by the CPU .
Need stock ROM for Teca g89 mobile.
Hi experts,
I need stock ROM of TECA G89W ANDROID 4.4 2.4GHz 4GB-RAM +32GB 18MP 5.5-inch GPS SMARTPHONE. I brought this phone 6 months back and unfortunately the software corrupted. I tried with other ROMs and currently bricked my phone. If anyone who might have this phone by fortunate can help me to post the stock rom by read back or any process whatever you wish as you know much than me.
Desperately need the ROM file as I want to have my phone back to working.... Thank you....
need that rom
hello. can you ... or someone else, upload that rom again?
the link is no longer online at needrom, and that was the best rom for my kingelon g9000.
i had made a flash to try another rom, but is wasn't better. when i wanted to download again that ALPS rom it was no longer online!
gt56 said:
Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
Click to expand...
Click to collapse
Hi see if the link helps you to find the mach of your phone model file:///data/data/com.android.browser/files/kingelon_g9000.mht
---------- Post added at 04:58 PM ---------- Previous post was at 04:53 PM ----------
gt56 said:
Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
Click to expand...
Click to collapse
Hi see if the link helps you to find the mach of your phone model file:///data/data/com.android.browser/files/kingelon_g9000.mht , you can root it using v root you will need a pc to root your phone.

Flashed a corrupt preloader on MediaTek device. Should I say RIP or not?

Apparently sometimes it's not the best idea to use the flashing software that the manufacturer of your phone released.
I have a Wiko Lenny(technically a MediaTek MT6572) that has(or had - now it's dead) the habit of simply rebooting into a bootloop every few months. Fixing that was simple; just start SP Flash Tool, format everything then flash the stock ROM back. Last time I did that was around 4 months ago, and since then I have upgraded to Windows 10, and as such, lost the tools I had installed.
Yesterday it went into a bootloop again. I didn't remember exactly what tools I used, so I assumed they were the tools that Wiko supplied a while back with the V10 ROM. Well, they weren't. I still thought I'd give them a try. I mean, it's from the manufacturer's site, so they must work even better that the ones I was using.
I was wrong. The tool flashed the ROM "successfully", but the only thing it actually succeeded to do is corrupt the preloader. For those who don't know, corrupting the preloader basically means the phone won't even power on(not boot, actually power on), won't charge, and the PC won't detect anything if you connect the phone. Practically, it's the hardest brick a phone can get.
The fastest way to fix that is by either using a JTAG connection to flash everything manually, or by entering something called the Mediatek META mode(don't quote me on this one, though - I never heard of it before). JTAG - well I don't have the tools or expertise necessary to do that(although I'd love to learn how to do it - if anyone can point me to a well-written guide or two about that, please do!), and I simply can't get the phone to enter the META mode.
Is JTAG the only way to do it? Is META mode just a myth? Is there a way to save my phone, or should I just say "RIP" and buy a new one(I have the money for a Samsung Galaxy A3, the new one, but I was planning to buy a new computer with that money - is it worth it?)?
TL;DR (It's not that long but anyway...):
I have a Wiko Lenny(Mediatek MT6572) with a corrupted preloader after I flashed it with Wiko's tool. Can I repair it or should I just buy a new phone?
Link to the culprit that killed my phone(AKA Wiko V10 ROM): https://docs.google.com/uc?id=0BzeAvoIC2yhHMTZESUU1Y3hUM0E
Come on people, let's fix this little guy.
EDIT: Please, just tell me what your ideas are... A tip, a crazy idea, some details about MTK devices that could help, anything is appreciated.
Please...
Looks like I'm getting the 10 posts just by begging people to say something... :crying:
I have an MTK phone and its always going wrong and not booting/turning on because I mess with it and break it
I'm sure I flash the backup I made in mtktools with spflash, and plug the phone in with no battery attached, I also have to use windows 7 on a dual boot as windows 10 never played ball properly. You also need the mtk VCOM driver installed, not just adb and normal drivers. If you have all these, and have tried them, then that is the end of my knowledge sadly. Only other thing is going to needrom and seeing if they have a full rom/backup with partition tables/preloader etc.
Also, had to try a few versions of sptools as certain versions didnt work, forget which one I have and which didnt work. And also had to use a samsung USB lead as the stock one didnt work, or the other way round. I just remember it was a ball-ache but did eventually work. Am not on that pc so cant be more helpful, sorry....
robneymcplum said:
I have an MTK phone and its always going wrong and not booting/turning on because I mess with it and break it
I'm sure I flash the backup I made in mtktools with spflash, and plug the phone in with no battery attached, I also have to use windows 7 on a dual boot as windows 10 never played ball properly. You also need the mtk VCOM driver installed, not just adb and normal drivers. If you have all these, and have tried them, then that is the end of my knowledge sadly. Only other thing is going to needrom and seeing if they have a full rom/backup with partition tables/preloader etc.
Also, had to try a few versions of sptools as certain versions didnt work, forget which one I have and which didnt work. And also had to use a samsung USB lead as the stock one didnt work, or the other way round. I just remember it was a ball-ache but did eventually work. Am not on that pc so cant be more helpful, sorry....
Click to expand...
Click to collapse
Thanks for replying. I'm not sure if I have the VCOM drivers, but I'll check. Luckily I also have a Win7 PC besides this one, so I'll try it there too.
You need to repair preloader. Contact me !
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
Please do a nice thing, and tell me how to repair it here. Maybe there will be people in the exact same situation...
Can't fix MIne too !
DragonSky87 said:
Please do a nice thing, and tell me how to repair it here. Maybe there will be people in the exact same situation...
Click to expand...
Click to collapse
I also got an android phone that is INTEX AQUA I5 hd , i was flashing my phone and unfortunatly my pc got off while flashing . And my preloader got currepted .
When i tries to flash my phone it connects to pc as Mediatek Viacom port , but after 3-4 sec it connects as a usb port .
I continuously gots connceted and dissconnected .
and my Sp flash tool shoes error " S_DA_SDMMC_READ_FAILED(3153) "
Can anybody help me with it ? please help me as soon as possible.
You need to flash preloader by Testpoint,after that flash rom.
Dont remember exactly the testpoint but you can try
DragonSky87 said:
Apparently sometimes it's not the best idea to use the flashing software that the manufacturer of your phone released.
I have a Wiko Lenny(technically a MediaTek MT6572) that has(or had - now it's dead) the habit of simply rebooting into a bootloop every few months. Fixing that was simple; just start SP Flash Tool, format everything then flash the stock ROM back. Last time I did that was around 4 months ago, and since then I have upgraded to Windows 10, and as such, lost the tools I had installed.
Yesterday it went into a bootloop again. I didn't remember exactly what tools I used, so I assumed they were the tools that Wiko supplied a while back with the V10 ROM. Well, they weren't. I still thought I'd give them a try. I mean, it's from the manufacturer's site, so they must work even better that the ones I was using.
I was wrong. The tool flashed the ROM "successfully", but the only thing it actually succeeded to do is corrupt the preloader. For those who don't know, corrupting the preloader basically means the phone won't even power on(not boot, actually power on), won't charge, and the PC won't detect anything if you connect the phone. Practically, it's the hardest brick a phone can get.
The fastest way to fix that is by either using a JTAG connection to flash everything manually, or by entering something called the Mediatek META mode(don't quote me on this one, though - I never heard of it before). JTAG - well I don't have the tools or expertise necessary to do that(although I'd love to learn how to do it - if anyone can point me to a well-written guide or two about that, please do!), and I simply can't get the phone to enter the META mode.
Is JTAG the only way to do it? Is META mode just a myth? Is there a way to save my phone, or should I just say "RIP" and buy a new one(I have the money for a Samsung Galaxy A3, the new one, but I was planning to buy a new computer with that money - is it worth it?)?
TL;DR (It's not that long but anyway...):
I have a Wiko Lenny(Mediatek MT6572) with a corrupted preloader after I flashed it with Wiko's tool. Can I repair it or should I just buy a new phone?
Link to the culprit that killed my phone(AKA Wiko V10 ROM): https://docs.google.com/uc?id=0BzeAvoIC2yhHMTZESUU1Y3hUM0E
Click to expand...
Click to collapse
Repair your own device
Soft Brick: Soft brick is the state of android device which occur due to some software problems like boot loops or phone freezing at some point during boot. This only occurs if some software problem occurred in the device mainly during OS upgrade or ROM flashing. If your device is in such state then you are luck there are 99% chances that you can recover your beloved device without needing any professional help or spending hundred of dollars.
Hard Brick Hard brick is the state of android device that occurs when your device won’t boot at all i.e. no boot loop,no recovery and also not charging. This occurs due to trying to flashed firmwere not made for your device or flashed incorrectly. This is more difficult to resolve and often require professional help
in MTK Android there is many Partitions in your phone. like Preloader, Recovery, Bootimg etc….. if somehow Preloader get Corrupted then you phone will not able to DETECT WITH PC !!! in other words you will have phone with BOOT DEAD.
How Preloader get corrupted ?
There could be few reasons but main reason could be that someone or you Flash your complete phone (include Preloader) with wrong files or with wrong ver. Also there could be reason someone Delete Preloader or you Deleted.
How could i know my phone have preloader dead ?
Preloader can be dead if some one Flash it wrong and after flash your mobile will not detect with pc any more. for confirm
1.sp flash tools does not detect your phone anymore and also the computer does not as there is a pop sound when usb is connected to device
2.open device manager
take battery out from phone
insert usb
insert battery
and check is computer detecting any device
If it’s not detect then you have phone which Preloader is dead AKA Boot Dead
How can i repair it ?
requirement
1.screwdriver (by which you can open the screw from handset)
2.bricked device
3.a usb cable
4.a copper wire( for sold test points)
5.a pc with sp flash tool,mtk drivers and stock firmwere for your mobile
now you have to disassemble your phone and take pcb out. check there should be some Golden points. check these points there should be written on them Rx,Tx,GND,Vcc,Vcharge etc… check there should be written “COLO” or “KOLO” or“KCOLO” you have to Sold that point with GND After Sold Attach usb now your phone will detect with USB !! and now ready to Flash.
In some phones “COLO” or “KOLO” or “KCOLO” not written for those type of phones you have to test all points one by one Short Golden point with GND and attach usb cable which point short with gnd can able to detect your phone by pc isForce Preloader Mode Test Point !! Keep in mind Don’t Short Vcc,Vcharge or any other pin which have 4.x Volts also i had tested “Colo” or “Kolo” or “KCOLO” don’t have any kind of volts.
need help
gsm-decode said:
You need to repair preloader. Contact me ![/QUOTE
i have samsung clone A9 MT6580 After reflash phon,e is dead by sptool..i thinkl preloader is damaged..i dont have back up..but ditecting VCOM BUT Always "Sft Enable Dram_Fail (4032)" in format or fullfash in all tools
Click to expand...
Click to collapse
help me i corrupted my pre loader
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
hi sir I try to flash a stock rom downloaded from internet
its a vivo v5 android mobile phone
I tried to flash but I got a few alerts
the selected model does not support model verification
and
if I tried it gives me a brom error
now my phone condition is hard bricked and responding to flash tool
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
HI sir how can I contact you
Hi I also have the same problem - when I flashed the stock rom of my LG K7 X-210 (MT6580__lge__LG-X210__m13g__5.1__ALPS.L1.MP6.V2.19_ARIMA6580.WE.L_P42) with the SP Flash tool when I was in a bootloop, I accidentally forgot to uncheck the preloader option. I flashed it to my phone and from that point onwards it didn't want to start up any more, nor would it react if I tried charging it. So conclusion: the preloader is corrupt...
However, I read online that MTK devices (mine is MT6580) have a 'meta' mode which allows your device to still connect to SP Flash tool even if it is hardbricked (in my case by pressing the volume up button, and then simultaneously plugging it in the computer). It is then recognized as MTK Com port something in device manager.
Luckily I have the same phone (but it's not mine) and I was wondering if it was possible to make a full rom dump from that device and restore it on mine? (a method that is safe for the other device as well)
i have a proble on my new phone since i flash preloader my touch is not working anymore, any solutions ?
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
I need to repair preloader of My Nokia G20.
hello this is very simple.
i solved this problem.
i wrte english very small.
flash atarken yanlış attığın preloader dosyası ile başlat.cihazı bilgisayara bağla.format bittikten hemen sonra doğru preloader dosyasını klasörün içine yapıştır.ama çok hızlı olmalısın.yani uyumsuz preloader dosyası ile cihaza yükleme yaparken tam format esnasında uyumlu olan preloader dosyasını hızlıca yapıştır.
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
Hello, is it too late to write?

Need help with Qualcomm based device MSM 8625 [double-bricked] + total noob!

Dear nice guys of xdadevs,
This is the first time I'm posting and I'd like to request some help from any experts with qualcomm devices.
So the story's like this:
1. I purchased a crappy cheap knock-off local android called Zyrex Onescribe ZA957 (made in Indonesia), it shares similarities with ZTE models like the Zte Blade.
The reason why it was crappy is because it's super slow and it had Android 4.0 ICS installed. Also, whenever I try to shutdown or restart the phone, it would say "Shutting down TABLET". So I immediately knew that it came with a Tablet ROM! This was before I rooted it.
2. It only had like 456mb ram, so I installed Kingroot and successfully got it rooted
3. I then deleted the bloatware with the system uninstaller app downloaded from playstore
4. After a while, the phone just became slower and slower like it was always running out of ram. The boot loading process also took longer and longer as the days progressed, until one time, it just got stuck on the boot logo (bootloop?)
5. So I couldn't figure out what was going on and eventually the phone just decided to stop booting at all, except for making vibrations but no lights or anything else and I couldn't even get to recovery mode by pressing power/vol+ etc.
6. Then I followed instructions to reflash a stock rom and the phone was detected as MSM 9008 or 9006 or something like that. I forgot what program I used to reflash it, but I think I followed the instructions from a website in Indonesian for "tutorial unbrick andromax u".
I also installed the stock rom for that CDMA based phone because it had very similar specs to mine GSM/CDMA dual sim, qualcomm MSM8625 etc.
I knew I had "soft bricked" it at first, but the second time, bang! I've double bricked it and now it's truely bricked! Darnit!
If I try to connect to PC via usb, it's a constant game of cat and mouse where sometimes the PC would detect the phone as "Qualcomm MSM CMDA Technologies" for about 2 seconds, then it disconnects/disappears. Sometimes (after a whole lot of pluggin' & unpluggin', it would stay on the Qualcomm MSM CDMA Technologies as detected in device manager, but listed as "Unknown".
I've installed the drivers for qualcomm BEFORE I attempted to reflash so I know it worked in the past. I've removed the drivers and have reinstalled them, but I still can't get my phone into the 9008/6 mode anymore.
Basically, I want to try reflashing again but I don't know where to go and what to do from here, so any expert help would be strongly appreciated!
Many thanks to the good folks here!
Cheers.

iRulu eXpro X1, model X10 - not booting

Hi all,
Hoping someone might have some knowledge on this Chinese cheap build tablet.
Its an iRulu eXpro X1, model X10. Inside is the Allwinner A83T with 16Gb Rom and 1 Gb RAM.
This was previously with my daughter but we just upgraded her to a Sumsung Tab A, so I thought I'd play with the iRulu (bad mistake lol).
The iRulu was still running kitkat so I rooted it (Kingo Root works fine in anyone else is trying), attempted to install CWM and TWRP. Both failed, every attempt through adb / fastboot gave bootloader: secure mode fail error.
So I them decided to flash the new rom from iRulu's website - using PhoenixUSB.
All was going well, the tablet went into download mode (hold Esc button, plug USB cable in and press power button 10 times in rapid succession.) and the firmware started to download. At 80% PhoneixUSB threw a boot(0) error and stopped.
After this the tablet will not start (nothing on display) nor even show the charging icon on the screen! It does however still enter the download mode so I can try other images. So far I have tried 5 different images (including darkglow10.1_android5.1.img, A83T_N102_N1021L1BC_20151123.img) however all of then error when writing to the bootloader. I have also tried PhoenixCard to write an image in Startup mode - this gave nothing Live Suite makes no difference either, using the images I have.
Unfortunately the serial number has worn off the device so I cant be sure of the exact firmware from iRulu website to install. (I've mailed them for what its worth).
I have opened the device and the pcb is marked INET-N102-REV01 and Zeng-gc2014-12-22. Google has some stuff on it but nothing I understood
Does anyone have any thoughts? I'm concerned that the bootloader is locked / corrupt in some fashion which is stopping the download.
thanks
update: using the x1081 firmware from iRulu and PhoneixCard I have restore functionality. The device thinks its an expro x2 plus and it doesnt recognise the SD card slot (tried multiple cards) but other than that it seems okay
Will try to figure the correct firmware thou - anyone?
thanks
Having the same issue
Hello, I am having the same problems with that tablet, got it from this girl I'm seeing. It was freezing whenever it connected to the internet, I assume was a ROM issue, i flashed an incorrect recovery on it after getting frustrated. Can you please help?

[Device][WIP] RCA DRP2091 / RCT6603W47M7

RCA 10" Touchscreen Tablet PC/DVD Combo Featuring Android 6.0 (Marshmallow)
*No idea why it says PC/DVD as its Android not Windows.
ASIN/Model numbers: ASIN: B077L4VBHK Model: DRP2091
RCA typical RCT number: RCT6603W47M7
Chipset/CPU: MT8127
Ports: 1x Mirco USB (supports ADB! etc. unlike VikingPRO), 1xUSB A, 1xHDMI (mini i believe), 1xMicroSD slot (supports up to 128GB)
Special: 1xDVD/CD Reader/Drive. has unlockable bootloader via fastboot oem unlock
Root Attempts: (Failed: KingoRoot, SRS, KingRoot, RootMaster)
MTK Droid Root & Tools and SP Flash Tools don't seem to work right with this cant create scatter etc. (i assume because of MT8127)
Links:
Walmart/Wally World
Amazon
if any dev could help me root this and get custom recovery would be great.
UPDATE: Thanks to NepoRood (and my testing) theres now CWM recovery (attached to post extract zip and flash img via fastboot flash recovery command.) unfortunately we were still unable to get root access.. if anyone has this device or wants to help root this pm me.
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
darkensx said:
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
Click to expand...
Click to collapse
I found various firmware downloads, but need to know the exact type of firmware you are running.
Example of one I found: rct6603w47m7-android6.0-v23-v2.15.80 (<-- underlined part is what matters)
If you boot into recovery, it should show you the type of firmware you have.
NepoRood said:
I found various firmware downloads, but need to know the exact type of firmware you are running.
Example of one I found: rct6603w47m7-android6.0-v23-v2.15.80 (<-- underlined part is what matters)
If you boot into recovery, it should show you the type of firmware you have.
Click to expand...
Click to collapse
DRP2091-android6.0-v62-v1.19.90-E02
*also says on very bottom of screen "supported API: 3"
**DRP2091 is rct6603w47m7 not sure why there's so many different model/serial numbers referencing the same exact device...
also i managed to dump the whole device via SP tools readback on linux so if anything beyond recovery or boot img are needed i should have it.
darkensx said:
DRP2091-android6.0-v62-v1.19.90-E02
*also says on very bottom of screen "supported API: 3"
**DRP2091 is rct6603w47m7 not sure why there's so many different model/serial numbers referencing the same exact device...
also i managed to dump the whole device via SP tools readback on linux so if anything beyond recovery or boot img are needed i should have it.
Click to expand...
Click to collapse
That version isn't on the site (or any v1.19.x), I'll download the images from the OP in a bit and see what's inside...
NepoRood said:
That version isn't on the site (or any v1.19.x), I'll download the images from the OP in a bit and see what's inside...
Click to expand...
Click to collapse
Had the same issue also I came across a bunch of ota test files on a Chinese site but links were dead and because no ota update is available i can't grab the ota url or file name. So ended up hitting a dead end.
Would it be possible to bypass the activation code screen with cwm or twrp? Or maybe put a different version of android on the tablet, other than marshmallow.?
darkensx said:
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
Click to expand...
Click to collapse
I'm having same problem could someone help me root this tablet explain as easy as possible and slow and clear directions
I have no idea
johnnymack said:
I'm having same problem could someone help me root this tablet explain as easy as possible and slow and clear directions
Click to expand...
Click to collapse
I've got the RCT6603W47M7 tablet, but here in the UK it goes by the name of RCA Neptune 10.1L.
Problem is I have bricked it and I am now trying to recover it using SP Flash Tools. I have tried 2 different stock ROMs, only to have nothing but errors and interruptions during flashing. (errors 2004 and 4008). My tablet is fully charged yet it will randomly disconnect during flashing. I've tried both the MTKAllInOne.bin and DA_SWSEC.bin but I still get the same problem either way.
I've tried different USB ports, different cables and the two download agents that I just mentioned but I am stumped.
I wanted to try the ROM found here https://www.needrom.com/download/rca-rct6603w47m7/
But as I don't have a premium account I cannot access it.
Any ideas? This is very frustrating.
BP9375 said:
I've got the RCT6603W47M7 tablet, but here in the UK it goes by the name of RCA Neptune 10.1L.
Problem is I have bricked it and I am now trying to recover it using SP Flash Tools. I have tried 2 different stock ROMs, only to have nothing but errors and interruptions during flashing. (errors 2004 and 4008). My tablet is fully charged yet it will randomly disconnect during flashing. I've tried both the MTKAllInOne.bin and DA_SWSEC.bin but I still get the same problem either way.
I've tried different USB ports, different cables and the two download agents that I just mentioned but I am stumped.
I wanted to try the ROM found here https://www.needrom.com/download/rca-rct6603w47m7/
But as I don't have a premium account I cannot access it.
Any ideas? This is very frustrating.
Click to expand...
Click to collapse
problem with the cwm recovery if i remember correctly is any thing flashed by it doesnt take the device will just bootloop
i no longer have the device currently i might pickup another at some point... i cant remember if i used the micro usb port to flash or if i had to use a usb male to male cable..
darkensx said:
problem with the cwm recovery if i remember correctly is any thing flashed by it doesnt take the device will just bootloop
i no longer have the device currently i might pickup another at some point... i cant remember if i used the micro usb port to flash or if i had to use a usb male to male cable..
Click to expand...
Click to collapse
Thank you for your reply, I was worried that this discussion was dead. That's frustrating to say the least! Damn! Well, I don't know if this will work but I found another device that is also a MT8127 and has exactly the same spec of this tablet. My point being is that I found a TWRP image for that device, and because it's the same chip set I assume that it'll work for this device too?
If I can get my bricked tablet to even turn on I shall try it. It also makes me wonder that if we were able to root the device, would we be able to access the internal storage by normal means? By using the micro USB ? Either way it'd be great to have it rooted.
I stayed up all night last night trying to flash this tablet and still no luck, it keeps disconnecting half way through.

Categories

Resources