My friends given me a S9+ clone with some major issues so I figured rooting or reflashing ROM would fix those, but every single ROM I tried doesn't work and just some up with and error shown in an attached image. Phones currently soft bricked and won't turn on. From what I learned this is a firmware compatibility issue but the problem is I cannot find one compatible with this clone. I managed to snap a picture while the phone was still running, revealing the firmware details. It would be very helpful If theres anyone who could provide me a link with a possibly compatible firmware.
Flippy485 said:
My friends given me a S9+ clone with some major issues so I figured rooting or reflashing ROM would fix those, but every single ROM I tried doesn't work and just some up with and error shown in an attached image. Phones currently soft bricked and won't turn on. From what I learned this is a firmware compatibility issue but the problem is I cannot find one compatible with this clone. I managed to snap a picture while the phone was still running, revealing the firmware details. It would be very helpful If theres anyone who could provide me a link with a possibly compatible firmware.
Click to expand...
Click to collapse
Unfortunately you're probably out of luck, the best you probably could have done is just use the phone as it was. I had something similar, it was an S7 edge clone, also running a mediatek processor. If you're lucky you might find a Chinese forum with some firmware on it.
Edit: where did you get the firmwares that you tried flashing?
YrrchSebor said:
Unfortunately you're probably out of luck, the best you probably could have done is just use the phone as it was. I had something similar, it was an S7 edge clone, also running a mediatek processor. If you're lucky you might find a Chinese forum with some firmware on it.
Edit: where did you get the firmwares that you tried flashing?
Click to expand...
Click to collapse
Believe me I didn't want to mess with the phone that much but you couldn't download anything on it, even from the play store and calls were broken too. So this was meant to be the last chance for this guy. I got the firmwares from general googling. Here's the list of few I tried:
MT6580__alps__boway6580_weg_gm_l__boway6580_weg_gm_l__5.1__ALPS.L1.MP6.V2.19_BOWAY6580.WEG.GM.L_P8
MT6580__samsung__SM-G960U__hero2qltechn__7.0__ALPS.L1.MP6.V2.19_HCT6580.WEG.A.L_P55
samsung s9+___MT6580__samsung__SM-G960F__dream2qltesq__7.0__alps-mp-m0.mp1-V2.34_hexing6580.we.m_P15
There's probably 3 more I tried and deleted.
Flippy485 said:
Believe me I didn't want to mess with the phone that much but you couldn't download anything on it, even from the play store and calls were broken too. So this was meant to be the last chance for this guy. I got the firmwares from general googling. Here's the list of few I tried:
MT6580__alps__boway6580_weg_gm_l__boway6580_weg_gm_l__5.1__ALPS.L1.MP6.V2.19_BOWAY6580.WEG.GM.L_P8
MT6580__samsung__SM-G960U__hero2qltechn__7.0__ALPS.L1.MP6.V2.19_HCT6580.WEG.A.L_P55
samsung s9+___MT6580__samsung__SM-G960F__dream2qltesq__7.0__alps-mp-m0.mp1-V2.34_hexing6580.we.m_P15
There's probably 3 more I tried and deleted.
Click to expand...
Click to collapse
I see, wow. Good job trying anyway. Do you think it could have been an issue with lacking the radio bands to work with your carrier?
YrrchSebor said:
I see, wow. Good job trying anyway. Do you think it could have been an issue with lacking the radio bands to work with your carrier?
Click to expand...
Click to collapse
Actually no. I could hear the other person, but from thier side they could only hear static noise. I tested microphones and they worked so who know's what's the issue.
So after a lot of suffering I actually got further and I can now download stuff to the phone. One firmware in particular can be flashed but the "userdata" partition cannot I just get the "not enough space" error. I'm no expert but this partition may contain some crucial config files. So when I boot the phone I only see vertical lines. Right now I'm trying to modify the android scatter file but I feel like a child while doing this.
Flippy485 said:
So after a lot of suffering I actually got further and I can now download stuff to the phone. One firmware in particular can be flashed but the "userdata" partition cannot I just get the "not enough space" error. I'm no expert but this partition may contain some crucial config files. So when I boot the phone I only see vertical lines. Right now I'm trying to modify the android scatter file but I feel like a child while doing this.
Click to expand...
Click to collapse
Way to go! What is that phone flash tool you're using?
YrrchSebor said:
Way to go! What is that phone flash tool you're using?
Click to expand...
Click to collapse
SP Flash Tool for MTK devices.
Hello. I read your topic about the software, fake samsung s9 + clone. I have a very similar situation. My friend's parents gave it to me to do something and I tried flashtool to upload the same software and now the phone is dead. The computer detects this phone ... Do you have any suggestions on what you could do?
I had same problem and fixed it Just change the proloder
If u don't have prooader I have 10 prooader files for s9+ clone diffrent models
Just change proloaer
Then windows should show mtk proader vcom driver on device manager
I will uploads files when I go to work
mosirezaei said:
If u don't have prooader I have 10 prooader files for s9+ clone diffrent models
Just change proloaer
Then windows should show mtk proader vcom driver on device manager
I will uploads files when I go to work
Click to expand...
Click to collapse
hello I need those preloader files to save the phone
I suffer the same, if I can get information about it, how did it work?
Same problem with my same model of S9+ Clone
Dear
I have same model of Samsung Clone S9+ and also have same problem. I flashed my phone with wrong firmware and my phone has only white screen. i changed an other firmware then it totally dead and dont turn ON then I use an other then there are some vertical lines. Can you help me??
Do you find correct firmware for your phone?
Thanks
I know this is not going to help get your phones going.. But serious, if you do not want to experience these types of issue.. By all means do not a clone phone.. If you can not afford the real deal. Then buy something within your budget, or save up until you can purchase it...
cic108 said:
Same problem with my same model of S9+ Clone
Dear
I have same model of Samsung Clone S9+ and also have same problem. I flashed my phone with wrong firmware and my phone has only white screen. i changed an other firmware then it totally dead and dont turn ON then I use an other then there are some vertical lines. Can you help me??
Do you find correct firmware for your phone?
Thanks
Click to expand...
Click to collapse
MT6580_S9+ - Google Drive
drive.google.com
more than 12 firmwares
Try searching on needrom but most likely it will be paid firmware, good luck
kirichen said:
MT6580_S9+ - Google Drive
drive.google.com
more than 12 firmwares
Click to expand...
Click to collapse
here is the proloader files i uploaded on Gdrive
Related
i just bought a chinese htm xs5292 runnin 4.1.1 i want to root and upgrade to 4.3 any help on how to do this would be greatly appreciated, here are the specs
manufacturer - htm
model - x5292
android version - 4.1.1
kernel - x5292 dual core
software - mt5617-c913-en-vo5
hardware - c913-v1.02
i'm a first timer at this so please speak like you would to a child (even though i'm 35)
many thanks in advance
paul
paul0909 said:
i just bought a chinese htm xs5292 runnin 4.1.1 i want to root and upgrade to 4.3 any help on how to do this would be greatly appreciated, here are the specs
manufacturer - htm
model - x5292
android version - 4.1.1
kernel - x5292 dual core
software - mt5617-c913-en-vo5
hardware - c913-v1.02
i'm a first timer at this so please speak like you would to a child (even though i'm 35)
many thanks in advance
paul
Click to expand...
Click to collapse
I can help you get rooted. First you will need to install drivers on your PC so your device can communicate with the root program. Then try this:
http://forum.xda-developers.com/showpost.php?p=43163569&postcount=7
If that dont work, let me know. You can always use MTK Droid Tools and SP flash tool to pull your stock recovery and port it into a custom recovery that will allow you to flash a simple root.zip
Hope this helps!
usb drivers
thanks Klown80, that looks like it should work, but first i need to install my usb drivers, i have loked at a ton of sites and they all didnt work, i need spreadtrum usb drivers, but can't figure out wich ones, a few said they all worked on any spreadtrum phone, but either im installing them incorrectly, or they simply didnt work,
again, thanks for any help in advance
paul
paul0909 said:
thanks Klown80, that looks like it should work, but first i need to install my usb drivers, i have loked at a ton of sites and they all didnt work, i need spreadtrum usb drivers, but can't figure out wich ones, a few said they all worked on any spreadtrum phone, but either im installing them incorrectly, or they simply didnt work,
again, thanks for any help in advance
paul
Click to expand...
Click to collapse
Try using this, it installs drivers for many different phones, it may not be the actual manufacturers drivers for your specific device but it will help get your phone talking to your PC:
http://www.snappea.com/
Also - Make sure you are going into settings and turning USB debugging on. You can usually find this under Settings > Developer Options.
snapea
Again, thanks Klown, but no joy, i tried serveral times and after 15 - 20 mins of "fobulating" (is that even a real word ) my phone it said "failed to processs phones data" i tried restarting both devices etc and a couple of other thing suggested but no joy.
Any other ideas, as always thanks in advance.
Paul
oh ps, i also tried to connect to snapea via wifi, but got the same message
paul0909 said:
Again, thanks Klown, but no joy, i tried serveral times and after 15 - 20 mins of "fobulating" (is that even a real word ) my phone it said "failed to processs phones data" i tried restarting both devices etc and a couple of other thing suggested but no joy.
Any other ideas, as always thanks in advance.
Paul
oh ps, i also tried to connect to snapea via wifi, but got the same message
Click to expand...
Click to collapse
Try these drivers
https://www.dropbox.com/sh/oaslz8xuxk7ag50/VRzHnZvA-b
finally
\it worked, can't thank you enough, one more bothersome question, now i have my phone rooted how do i safely, and i emphasise safely upgrade from 4.1.1 to 4.3
I have looked into it a bit myself, and am in half a mind to give it a go, but the warnings about bricking my phone always puts me off, so once again, thanks in advance for any help given, and many thanks for the help so far.
Paul
paul0909 said:
\it worked, can't thank you enough, one more bothersome question, now i have my phone rooted how do i safely, and i emphasise safely upgrade from 4.1.1 to 4.3
I have looked into it a bit myself, and am in half a mind to give it a go, but the warnings about bricking my phone always puts me off, so once again, thanks in advance for any help given, and many thanks for the help so far.
Paul
Click to expand...
Click to collapse
Go here and download MTK Droid Tools from first post:
http://forum.xda-developers.com/showthread.php?t=2160490&styleid=18
Run the program and connect your phone to PC, this tool will tell you lots of info about your phone but the main function is to possibly back up your stock firmware (This is good to have if you plan on trying to flash anything to the phone, this way you will have your stock files to fall back on in case something you flash to the phone does not work.) Once you have MTK Droid Tools running and phone connected, what does it say next to Hardware on the phone info tab please?
I am not sure off top of my head about updating to a higher version of Android but this back up step is REALLY important. It is hard if not impossible to find stock firmware floating around on the net for these chinese clone devices. IF you have stock files backed up you can flash almost anything you want knowing you have a way to restore your phone to working order. IF you look around here on XDA you will see tons of posts by people looking for the stock firmware for their clone phone after soft bricking it playing around. Sadly there is not much help for them unless they find someone with the EXACT same phone and are willing to share their back up (if the next person made one theirselves that is!)
hardware
Klown80 said:
Go here and download MTK Droid Tools from first post:
http://forum.xda-developers.com/showthread.php?t=2160490&styleid=18
Run the program and connect your phone to PC, this tool will tell you lots of info about your phone but the main function is to possibly back up your stock firmware (This is good to have if you plan on trying to flash anything to the phone, this way you will have your stock files to fall back on in case something you flash to the phone does not work.) Once you have MTK Droid Tools running and phone connected, what does it say next to Hardware on the phone info tab please?
I am not sure off top of my head about updating to a higher version of Android but this back up step is REALLY important. It is hard if not impossible to find stock firmware floating around on the net for these chinese clone devices. IF you have stock files backed up you can flash almost anything you want knowing you have a way to restore your phone to working order. IF you look around here on XDA you will see tons of posts by people looking for the stock firmware for their clone phone after soft bricking it playing around. Sadly there is not much help for them unless they find someone with the EXACT same phone and are willing to share their back up (if the next person made one theirselves that is!)
Click to expand...
Click to collapse
Thanks again, while i go to the link and follow the next steps i thought i'd put up the hardware version you asked for
hardware - c913-v1.02
Paul
edit
even though my pc now recognises the fact that tere is a spreadtrum phone in my devices list and i managed to root it ok, when i load up mtk droid tools it says "the device isn't revealed, connect or reconnect a cable"
needless to say i tried reconnecting and it didn't change i downloaded the adb drivers from the link under the mtk link but have no idea what to do with them,
appologies for my ignorance in all of this, but like i said in my first post, i have no idea what i'm doing with all this, thanks
paul
pps the hardware version i posted was from the info on my phone
Hi fellow xda'rs,
I recently bought a Android TV Stick from Geek(app) from china.
I thought I had found a bargain as its specs were:-
2GB RAM
Quad Core CPU
16GB Storage
I managed to snap this up for £24 which I thought was a bargain but when I got the device delivered and was using it I thought it was a little on the slow side so I began to think it was a clone as its default OS theme was not the same as the usual CX919's aswell.
So I wanted to flash the device with a new ROM specifically the Finless 1.6b ROM.
So after following the instructions to installing the ROM using the software provided with the ROM download I managed to install the drivers and get the software to recognize the device. I then wiped the NAND and attempted to install the ROM but it failed .
Now the device does not boot at all and is not recognized by the PC. Windows just states the device is not recognized and has malfunctioned
So I cannot flash any other or what I believer I have found to be the original ROM for the clone device.
The board states its a GXT_D16_LP_V1.8 150310
I have seen that there are tutorials on putting the device into Mask Flash mode by shorting pins but as this is for the genuine CX919 my board is totally different and does not have the pins available to short I think.
In short could anyone help me to put this device into Mask Flash mode and tell me what id need to do and what pins to short please?
I have attached a couple of pictures of the device and board.
lowery91 said:
hi fellow xda'rs,
i recently bought a android tv stick from geek(app) from china.
I thought i had found a bargain as its specs were:-
2gb ram
quad core cpu
16gb storage
i managed to snap this up for £24 which i thought was a bargain but when i got the device delivered and was using it i thought it was a little on the slow side so i began to think it was a clone as its default os theme was not the same as the usual cx919's aswell.
So i wanted to flash the device with a new rom specifically the finless 1.6b rom.
So after following the instructions to installing the rom using the software provided with the rom download i managed to install the drivers and get the software to recognize the device. I then wiped the nand and attempted to install the rom but it failed .
Now the device does not boot at all and is not recognized by the pc. Windows just states the device is not recognized and has malfunctioned
so i cannot flash any other or what i believer i have found to be the original rom for the clone device.
The board states its a gxt_d16_lp_v1.8 150310
i have seen that there are tutorials on putting the device into mask flash mode by shorting pins but as this is for the genuine cx919 my board is totally different and does not have the pins available to short i think.
In short could anyone help me to put this device into mask flash mode and tell me what id need to do and what pins to short please?
I have attached a couple of pictures of the device and board.
Click to expand...
Click to collapse
problem solved! :d
i found the mask flash mode pins to short by trial and error and luckily enough after 1 hour i solved it and got the pc to flash it back to its original rom. If anyone has the same device or issues and would like to know how to solve this i will be happy to help
I would be interested. I have a very similar clone (was supposed to be mk809iv). I have the same board although possibly different chipset.
I haven't bricked it (yet) but will probably do so if I can't find a way to root it. I think it may have come pre-rooted as super su was preinstalled but it has never worked (possibly because the app updated but not the binary?). I have since tried to update the binary and killed the root access completely.
Questions:
Is the ROM you used pre-rooted or rootable (if you've tried)?
Which pins need shorting? I have a button on the side that may be doing the same thing.
OT. How do I upload images or can I not as a new member?
Thanks in advance
any guide? i have the same device or where to download rom?
If your still looking, i might be able to help with a rom, root, and guide.
Thank you but managed to get root the same day you posted. I may still give it a go when my new tv box turns up though if you dont mind posting the info?
For anyone else interested in how I gained root:
1. Search for, download and install kingroot 4.6.5 (this is the version I used, only the latest version is available from official site and cannot be sure next steps will work with it)
2. Run kingroot and follow steps to gain root (dongle may reboot)
3. BUY super sume from play store.
4. Run super sume and follow steps to replace kingroot with super su.
what pins did you short
I am having problems flashing my hdmi stick . I can't get it to flash mode. which pins did you shorted?
can you email me a picture of it? [email protected] thanks
Lowery91 said:
problem solved! :d
i found the mask flash mode pins to short by trial and error and luckily enough after 1 hour i solved it and got the pc to flash it back to its original rom. If anyone has the same device or issues and would like to know how to solve this i will be happy to help
Click to expand...
Click to collapse
Hello,
Having some problems with this stick .Messed up trying to flash a non rooted rom and now I only get a blue icon in rkbatch tool ( after short pin 5-6 ) and nothing happens. Download boot fail errors for a year...
Can someone help me please?
Is it the same model? What version of rkflash tool are you using. And what version are you trying to flash. In my case I didn't need to short any pins.
spade2be said:
Is it the same model? What version of rkflash tool are you using. And what version are you trying to flash. In my case I didn't need to short any pins.
Click to expand...
Click to collapse
I've used several batchtools from 1.5 ( doesn't see my device at all ) to 1.8, different roms ( neomod, finless, stock cx919 roms )hoping one would give me something. All different bootloaders 1.24, 2.08, 2.13,...
I'm going to check mine out. It's been a minute since I used it. But I got the rock chip tool and the img file. I'll zip it up and pm you the link asap.
spade2be said:
I'm going to check mine out. It's been a minute since I used it. But I got the rock chip tool and the img file. I'll zip it up and pm you the link asap.
Click to expand...
Click to collapse
Thnx a million for your help. I've gone bonkers over this hahaha
Lowery91 said:
problem solved! :d
i found the mask flash mode pins to short by trial and error and luckily enough after 1 hour i solved it and got the pc to flash it back to its original rom. If anyone has the same device or issues and would like to know how to solve this i will be happy to help
Click to expand...
Click to collapse
what pins did you short
I am having problems flashing my hdmi stick . I can't get it to flash mode. which pins did you shorted?
can you email me a picture of it? [email protected] thanks
Guys, the phone went into brick mode simply while charging. Please help me with links or ideas on how to find / create a debricking .zip or folder to flash this Qualcomm Snapdragon 400 - 8930AB device.
Why would a service get use of my money when I know it is possible to reanimate this small evil by myself? People keep talking on russian forums about using tools like xPRG ... HEX/ MBN files... Miflash for Qualcomm... QPST software.. and stuff like this... but they are very general in explaning things... Help me!
Thanks!
Same problem here please help anyone
Mango Polo said:
Guys, the phone went into brick mode simply while charging. Please help me with links or ideas on how to find / create a debricking .zip or folder to flash this Qualcomm Snapdragon 400 - 8930AB device.
Why would a service get use of my money when I know it is possible to reanimate this small evil by myself? People keep talking on russian forums about using tools like xPRG ... HEX/ MBN files... Miflash for Qualcomm... QPST software.. and stuff like this... but they are very general in explaning things... Help me!
Thanks!
Click to expand...
Click to collapse
Take care
I hope this is not necroposting, but what do you mean for brick? Explain, is it hardware or software? And how is it going now?
L-K said:
I hope this is not necroposting, but what do you mean for brick? Explain, is it hardware or software? And how is it going now?
Click to expand...
Click to collapse
Necroposting at its finest, but i thought i would write here, so the thread creator might find something useful.
Here is my problem, samsung galaxy express 2 aka sm g3815, gone bricked while charging, i had custom recovery installed, although i do not seem to be able to remember the version, and root, flashed with Odin, everything worked perfectly for...almost a year, i guess. One day, my lil hero died. :crying: My computer seems to detect something plugged in, saying that it some QHUSB_DLOAD device. On some research I understood the Qualcomm reverted or switched to some sort of fail-safe state where it requires files to be written back in the device(correct me if im wrong). It`s been in deep coma for a few months now, everyone said "just buy a new phone and save yourself the hassle". Nope, my mind is set on repairing my hero. On other threads i found out it is possible to revive a phone in this state, using a class 10 or above microSD card and writing a debrick image. Problem was, i searched the seas of gold for the darn debrick image, none found. Until a few days ago, one of my workmates has a Galaxy Express 2, and said he can hand it to me so that i can copy what i need from it after the holidays. Both phones run on 4.4.2, his phone is all stock rom, no cwm or twrp, no root no nothing. It is coming in my hands in a few days. Does anyone have the patience to clearly write what must i do to get my hero working again? It`s been sucky here without it, currently stuck with a samsung Star 3 i reflashed myself, but that lil thing ain`t no Android. I have two class 10 microSD cards, one 8 Gb, one 16 Gb,with backup done, and i saw on other threads that i need to use the 8 gb one, since the phone`s internal was 8 gb. Anyway, sorry for the long novel, it`s my style tho, give as much info as you can so the people helping you know what they`re messing with haha feel free to ask for any extra information. If we ever meet, I`ll buy you a beer or two.....dozens
Cheers!
I am currently in communication with Alcatel's U.S. support (which may be outsourced, who knows?), and they have made it clear there is no OTU (OneTouchUpdate) available for the AT&T Alcatel Allura 5056O device. Their current advice is limited to performing a factory reset via the GUI, which of course isn't possible for a softbricked phone.
This means that as of this writing, there is no known way to restore this device from a softbrick.
I am explaining carefully the issue I and and a number of others here on XDA have experienced with this phone to Support, specifically asking for some method to reload the stock ROM, and will report any constructive suggestions they may have. But the OTU I made available at:
https://www.multcloud.com/share/0377ab37-15ed-4bcd-be3b-dbe8c7eb2cc8
...that lists the 5056 simply will not work on the 5056O.
Received this from the Contact Center:
The firmware is information that would only be available at the repair center. We would recommend you to perform a factory reset...
Click to expand...
Click to collapse
Still trying, but it isn't looking very good for those of us with softbricked 5056Os...
Yup I wanted to root the phone, so I did but then it bootlooped and it's bricked lol.
Haven't heard anything else from Alcatel's Customer "Support," so I've resent my questions to see if I can get some answers out of someone. There are enough of us affected by this issue that I'm not going to let them off quite so easily...
More bad news; the most recent reply from Alcatel CS:
At this moment it would be to send in the device into the repair center to get it repaired for you.
Click to expand...
Click to collapse
Clearly they are going to be less than helpful for those of us with the 5056O. Unless some kind soul here who has this phone is willing to image and post a copy of the Allura ROM, or someone knows a tech working for Alcatel who can supply the ROM, those of us with soft-bricked phones are completely screwed.
Am getting same info from Twitter CS...the ROM is only available inside their repair center.
(*sigh*) So unless someone else manages to liberate this device's ROM, guess we all might as well throw the devices in a drawer and move along. Just remember that the next time you're phone shopping, and bypass the Alcatel/TCL offerings.
Friends here I leave a link for you to download a copy I made to the Alcatel Allura 5056O, I did it through the flashfire application, I think if some advanced developer could work it, it would solve the problem we have. Https://mega.nz/#!01NDVR5K!rPPYEd87ndmg5Q9jmQ3qWjm1qGD3Rm7ge83yIsezSSQ
Excuse my bad English, I'm from Venezuela.
sanpuyon said:
Friends here I leave a link for you to download a copy I made to the Alcatel Allura 5056O
Click to expand...
Click to collapse
That is excellent, thank you very much!
Now let me make sure I understand; is this a copy of a softbricked ROM, or a functional one? Is it rooted or non-rooted?
CharlieSummers said:
That is excellent, thank you very much!
Now let me make sure I understand; is this a copy of a softbricked ROM, or a functional one? Is it rooted or non-rooted?
Click to expand...
Click to collapse
It is a copy of a functional rom, has root access and has modifications that I did before the device would damage me, but I have all my data in it.
sanpuyon said:
It is a copy of a functional rom, has root access and has modifications that I did before the device would damage me, but I have all my data in it.
Click to expand...
Click to collapse
So, if we can figure out how the Alcatel OTUs push the ROM to the phone, we might be able to get a softbricked phone to the point of performing a system reset...
Time to start reading up on how...
CharlieSummers said:
So, if we can figure out how the Alcatel OTUs push the ROM to the phone, we might be able to get a softbricked phone to the point of performing a system reset...
Time to start reading up on how...
Click to expand...
Click to collapse
The problem with my phone is that I made a modification to the build prop and upon restart I just showed the logo and then black screen, connect it to the adb and try to carry a custom recovery of a 6040A alcatel I had before and the result was that too Delete the recovery stock, now the phone when I connect it to adb appears to me as unauthorized, so I have not been able to repair it
sanpuyon said:
now the phone when I connect it to adb appears to me as unauthorized, so I have not been able to repair it
Click to expand...
Click to collapse
Keep trying. I've noticed that my 5056O does the same thing, but if I keep trying (restarting the phone, plugging in-and-out, etc.) I can eventually get adb devices to show it as "device" at which point I can acquire a shell, which can be SU'd.
Not guaranteeing this will work for you, but it has worked for me quite a few times so far. Beginning to think this phone is just magic, not science.
Just a quick bump to remind folks there are a bunch of soft-bricked 5056O phones out here in desperate search for a ROM...
Another bump to see if anyone has additional information on 5056O ROMs...hope springs eternal!
Still nothing, eh?
Hoping for someone with info on how to unbrick an Alcatel OneTouch Allura (5056O) - a stock ROM and means for recovery would be great!
Dear friends, after suffering for more than a year with my damaged phone, find a solution, I hope you can also solve it.
Here is a guide and the link to download the tool.
In the completely off phone will press the volume up and down keys at the same time and connect it to the pc so enter the download mode
1) Download the tool from this link https://mega.nz/#!NpkhnCoT!q5LxwJdWfIjcIY2tl99eGbhvRtrSY8bk-GQcDji7Rhs
2) Then unzip it install it on the pc
3) They execute it and they place the user and the password that he left in the attached note, when the update comes out they tell him not to
4) They look for the model of the team and they give to the option of flash and enjoy the magic
The only bad thing is that in the process the network release is lost
sanpuyon said:
Dear friends, after suffering for more than a year with my damaged phone, find a solution, I hope you can also solve it.
Click to expand...
Click to collapse
Um, last time I checked, the 5056O didn't have available ROMs outside AT&T. Is this the phone you repaired?
Also, latest version of SUGAR I found is v11.6.9R, which I placed in the MultCloud shared folder at https://www.multcloud.com/share/0377ab37-15ed-4bcd-be3b-dbe8c7eb2cc8 in the Misc folder. Same credentials as listed in the older README:
Region: All
Username: SU_IN.Panasonic
Password: KoD8naL2
Dongle authorization: unchecked
sanpuyon said:
The only bad thing is that in the process the network release is lost
Click to expand...
Click to collapse
My fault being unfamiliar with this stuff, but can you explain what was lost?
Oh, and I don't suppose this got you any closer to installing a custom recovery to root the phone?
does anyone have a link to the stock firmware? for an ALcatel onetouch Allura 5056O, I've been browsing the thread and seen none of the links provided for the stock firmware are all dead.
Better late than never: https://www.androidfilehost.com/?fid=10620683726822061932
I had hat on a HDD from a while back and never had a way to use it until I found edl. I'm currently flashing it now and I have no idea if it's gonna work or not. I don't think it will but who knows.
Also, its probably gonna take a few days or more to flash...
Edit: It failed at some point just a few hours in. Maybe it was just my device because I have disassembled it in the past looking for test points. I wish everyone else good luck.
Hi, noob here!
I have a Coolpad Torino S (a cheap Chinese Android 5.1 phone) I was using to tether a few devices to the internet. A few days ago it started behaving oddly, so I restarted it. As expected, it restarted and brought up the manufacturer logo splash screen. It then went to a black screen and vibrated non-stop.
It has a non-removable battery, so I held down power until it switched off, but all it did was bring up the logo again (without turning off) and then vibrated relentlessly.
After a bit of trial and error, I managed to get into recovery. I wiped the cache and restarted - endless vibration.
I returned to recovery and factory reset the phone, then restarted - endless vibration.
I've never seen this behaviour from a phone before. I realise I've probably killed it, but I wonder if reflashing the firmware might stop this vibration issue (as it does seem like a software problem). The problem I face is that there does not seem to be a single stock or custom ROM anywhere on the web for this device. One Russian website claims to have the stock ROM, so I downloaded it, but the RAR file is password protected (with no hint as to what the password might be), and so utterly useless.
I'd appreciate any advice on how I might fix the phone or find a ROM!
The model number is E561 (bizarrely, there is a near-identical Coolpad phone - the Coolpad Fancy - that shares the same model number despite having different hardware in several key areas, so I don't know whether using that ROM is a risk worth taking).
Hi , here is right firmware for your device:
https://files.fm/u/5auxsp2g
How to flash examle :
https://www.youtube.com/watch?v=b_yyilVsn5I
Good luck ...
Teddy Lo said:
Hi , here is right firmware for your device:
Good luck ...
Click to expand...
Click to collapse
Thanks a lot! However, that appears to be for the Coolpad Fancy rather than the Torino S (same model number, different spec). The ROM in the link is for a phone with (apparently) half the storage capacity (8GB vs 16GB in the Torino S) and a different version of Bluetooth (4.0 vs 4.1 LE in the Torino S). I think I read somewhere else that the Fancy has a lower res video on the camera too.
Will it be safe to flash onto the wrong phone? Obviously it can't get much worse than its current state, but at least it's vaguely responding when I turn it on etc at the moment...
tesbreag said:
Thanks a lot! However, that appears to be for the Coolpad Fancy rather than the Torino S (same model number, different spec). The ROM in the link is for a phone with (apparently) half the storage capacity (8GB vs 16GB in the Torino S) and a different version of Bluetooth (4.0 vs 4.1 LE in the Torino S). I think I read somewhere else that the Fancy has a lower res video on the camera too.
Will it be safe to flash onto the wrong phone? Obviously it can't get much worse than its current state, but at least it's vaguely responding when I turn it on etc at the moment...
Click to expand...
Click to collapse
Hi , don't flash firmware for Fancy , I will upload on the internet correct firmware for Torino soon , sorry I didn't checked that first firmware is for Fancy . Stay updated
Teddy Lo said:
Hi , don't flash firmware for Fancy , I will upload on the internet correct firmware for Torino soon , sorry I didn't checked that first firmware is for Fancy . Stay updated
Click to expand...
Click to collapse
Hi again. Thanks for the clarification!
Just to confuse things more, my phone is the Coolpad Torino S. There is another phone called the Coolpad Torino which again is a different phone entirely (much bigger screen and very different hardware than the Torino S).
It is quite easy to find ROMs for the Fancy and (IIRC) the Torino. It's the Torino S that is impossible to find. so if you can help with that I'd be very grateful!
tesbreag said:
Hi again. Thanks for the clarification!
Just to confuse things more, my phone is the Coolpad Torino S. There is another phone called the Coolpad Torino which again is a different phone entirely (much bigger screen and very different hardware than the Torino S).
It is quite easy to find ROMs for the Fancy and (IIRC) the Torino. It's the Torino S that is impossible to find. so if you can help with that I'd be very grateful!
Click to expand...
Click to collapse
This firmware is for Torino S verion like in this video! If you don't know what is what send your device to repair center.
https://www.youtube.com/watch?v=VH8Shjl6_hs
Teddy Lo said:
This firmware is for Torino S verion like in this video! If you don't know what is what send your device to repair center.
https://www.youtube.com/watch?v=VH8Shjl6_hs
Click to expand...
Click to collapse
Thanks for the reply. I don't know if I said something wrong and if I did I apologise - it was never my intention. This whole Coolpad situation is very confusing, that was my only point (three phones, 2 with almost identical names and 2 with identical model numbers, all completely different!)
I did see that video before but based on the images I assumed it was for a manual update to a working phone (as it goes into settings etc). I will look into this solution if you think it is indeed the appropriate file?
Coolpad seem to offer zero support, so even if I wanted to send it to a repair centre, it would be impossible!
Thanks again!
tesbreag said:
Thanks for the reply. I don't know if I said something wrong and if I did I apologise - it was never my intention. This whole Coolpad situation is very confusing, that was my only point (three phones, 2 with almost identical names and 2 with identical model numbers, all completely different!)
I did see that video before but based on the images I assumed it was for a manual update to a working phone (as it goes into settings etc). I will look into this solution if you think it is indeed the appropriate file?
Coolpad seem to offer zero support, so even if I wanted to send it to a repair centre, it would be impossible!
Thanks again!
Click to expand...
Click to collapse
Hi , no problem dude just I wanted to help you to solve your problem with your device . That is truth that unknown device like yours is complicated with support and the only available firmware for your device was that what I send you.
This flash file is for your device Coolpad Torino S E561 (SK3-U00) Dual SIM also you have same new device with same firmware SK3-U00 . Google a little bit this and you will see the new devices has the same firmware version . I know it is shame for support but what can I say to you about is to don't buy unknown devices and if you thinking about buying like those devices do little research about their support and what problems can you face with that device .
I wish you all the best with your unbricking device .
With Respekt
Teddy Lo said:
Hi , no problem dude just I wanted to help you to solve your problem with your device . That is truth that unknown device like yours is complicated with support and the only available firmware for your device was that what I send you.
This flash file is for your device Coolpad Torino S E561 (SK3-U00) Dual SIM also you have same new device with same firmware SK3-U00 . Google a little bit this and you will see the new devices has the same firmware version . I know it is shame for support but what can I say to you about is to don't buy unknown devices and if you thinking about buying like those devices do little research about their support and what problems can you face with that device .
I wish you all the best with your unbricking device .
With Respekt
Click to expand...
Click to collapse
Thanks for all your help so far. I've downloaded and extracted the firmware file, and YGDP v4.03 as recommended.
One more question... would the Coolpad driver in the Fancy file you linked before be the same for the Torino S? I'm guessing the drivers are the standard Qualcomm USB drivers, right?
tesbreag said:
Thanks for all your help so far. I've downloaded and extracted the firmware file, and YGDP v4.03 as recommended.
One more question... would the Coolpad driver in the Fancy file you linked before be the same for the Torino S? I'm guessing the drivers are the standard Qualcomm USB drivers, right?
Click to expand...
Click to collapse
Probably it will work if not use this one:
https://drive.google.com/uc?id=1M4HjlqcwcTUJNRKufa5Vr4oejVTUE24D&export=download
Good luck , and let me know if you fixed
Teddy Lo said:
Probably it will work if not use this one:
https://drive.google.com/uc?id=1M4HjlqcwcTUJNRKufa5Vr4oejVTUE24D&export=download
Good luck , and let me know if you fixed
Click to expand...
Click to collapse
After a great deal of messing around with different versions of YGDP and various CoolPad drivers, I finally got to the point where YGDP was able to find and transfer data to my phone.
10 minutes later, the phone rebooted and now it seems to be fully working!
Many thanks for your help!
An update on this, a year and a pandemic on. The phone has died again, and this time YGDP won't bring it back.
It is failing with a flash write error, so I can only assume this is now a hardware fault, unless any XDA geniuses can suggest anything further to try? YGDP gives the following errors:
Code:
12:32:38 CELL0: Start to download emmc_appsboot.mbn file ...
12:32:38 CELL0: transmit emmc_appsboot.mbn file size info OK
12:32:39 CELL0: Fail to transmit emmc_appsboot.mbn file Flag code
12:32:39 CELL0: Res:flash write failure
12:32:39 CELL0: Fail to transmit emmc_appsboot.mbn file data !
12:32:39 CELL0: Lock bootloader ...
12:32:39 CELL0: Download failed,please try again!!
12:32:39 CELL0: Total download time elapsed: 0 min : 2 sec
12:32:39 CELL0: Downloading all files: Failed!
I can still get into Recovery (which also flashes up a litany of cache read/mount errors), and have tried wiping caches and factory resetting multiple times.
Any final suggestions before I consign it to the scrapheap?
Hey same issue here, can you please explain how you managed to get it to recovery?
coolpad e502