bought a phone advertised as ulefone u692.
tried to flash cwm to devive , lost recovery.
tried to flash stock firmware to device in hope of fixing afore mentioned problem.
epic fail phone boots but screen is black.
after many attempts and downloading numerous roms and flashing numerous file....finally get it to boot but with several driver issues! many sensors not detected.
what i have found out is the screen is 1920x1080 as opposed to the ulefone u692 which has 1280x720, hence the black screen issue.
everything else says it is right apart from screen resolution.
i do hear cpu info can be faked, how do i check my real cpu info?
would it be possible to add the screen driver to the stock u692 kernel?
thanks.
Hi bro
Please remember , always backup all partitions first on unknown mtk phones.
i wonder your IMEI isn't lost too,
try this tool -> http://forum.xda-developers.com/showthread.php?t=2160490
Don't buy copycats....
Related
I came here after many days trying to fix this phone!
First, I don't know how to work with phones! It was looked due to "Too many tries to unlook it!" and was requesting to connect to one google account to unlook it.
The phone is a generic Spreadtrum SC6820 that has "i9300" writed on the space where the battery goes and its circuit board is marked with the writing L3035_MB_V2.2 and there one stick that reads L3035F-P9600-QUAD-2G-HY-V2.03.B05.
I was unable to find the stock firnware and did not know how to backup it using the ResearchDownload.exe tool available for the Spreadtrum, so I fallowed that very bad tutorial http://forum.xda-developers.com/showthread.php?t=2320640 and I ended with it bricked!
After that, I tried to flash all the roms I could find to see if any would work but all I managed to get is a phone with inverted color scheme, inverted touchscreen, no radio, no BT and no wifi!
If anyone here has the firnware compatible with this phone, please share it, Thanks.
i got the same problam my device has a inverted touchscreen after i flashed its rom using recherche download.please help
Hi !
Today the screen of my Cubot One went black, when I turn it on and off the problem remains, I can still lock the screen.
I downloaded a ROM and I tried installing it with both "Smart Phone Flash Tool" and "SP Flash tool" (Or maybe it is 2 different versions of the same software).
I load the scatter file but when I hit the "download' button nothing happens...
Can you please help me with my problem ?
Edit: Now I get this message: "ENABLE DRAM FAILED!"
rscredin The
up
My phone is experimenting some similar issue
I tried to change the recovery in my cubot one (the grey one), supossedly it has the mt6589t SoC, but every try failed, then I thought to change the firmware (the firmware the phone had was G800_CUBOT_D1_V1.3_"some_number_here"_MJK), with the firmware G800_CUBOT_D1_V0.8_20140124_MJK, i employed the SP tools without problem, the download was succefully, the i put the battery on again, then i switched it on, the telephone started, the screen lites on, but the screen keeps black, it sounds like boots normally, even the unlock screen sound normal, but there is no image in the screen, I've looked for the newer firmware everywhere but I did not found it, somebody could help me, please!!!
The firmware I used to flash the phone succesfully was the cubot one turbo available in the needrom page. Maybe the newer versions of cubot one have a new graphic chip or something different.
The error...
Alastor56 said:
Hi !
Today the screen of my Cubot One went black, when I turn it on and off the problem remains, I can still lock the screen.
I downloaded a ROM and I tried installing it with both "Smart Phone Flash Tool" and "SP Flash tool" (Or maybe it is 2 different versions of the same software).
I load the scatter file but when I hit the "download' button nothing happens...
Can you please help me with my problem ?
Edit: Now I get this message: "ENABLE DRAM FAILED!"
Click to expand...
Click to collapse
The cause of this error is trying to flasn an incorrect ROM image in the device, there are a lot of versions of cubot one, did you tried the roms in needrom_com?
Same prob.
I've same problem. Only black screen (but sounds like boot normally). Did anyone resolve this issue?
any solution found?
abanuelosh said:
The cause of this error is trying to flasn an incorrect ROM image in the device, there are a lot of versions of cubot one, did you tried the roms in needrom_com?
Click to expand...
Click to collapse
hi i have same problem, i install the rom that download of needrom but not work fine, i install the rom succesfull but my screen is black, phone turns on, I can unlock and lock it, volume buttons work, but there is simply no image.
are you have any solution?
Hello,
I have got a samsung galaxy s4 clone set with mtk6572 cpu and lcd driver ic: 1-nt35512_dsi_vdo. after getting it i found it very slow so i tried to do some tricks and it left me with my phone dead.I couldnt turn it on anyhow. then i tried to flash its rom again with my backup. but then my set can turn on but only shows blank screen nothing else.just charge icon showd up if connected to pc or charger. so i thought my backup was faulty so i tried to find relevant rom but i can not find any relevant rom for my phone. Can anybody help me? I am really in a bad situation. I just need to start my phone and see that it is running
I forgot to mention that my device file system is UBIFS
anybody saw this!!!!
I need HELP!!!
sadimahmud said:
Hello,
I have got a samsung galaxy s4 clone set with mtk6572 cpu and lcd driver ic: 1-nt35512_dsi_vdo. after getting it i found it very slow so i tried to do some tricks and it left me with my phone dead.I couldnt turn it on anyhow. then i tried to flash its rom again with my backup. but then my set can turn on but only shows blank screen nothing else.just charge icon showd up if connected to pc or charger. so i thought my backup was faulty so i tried to find relevant rom but i can not find any relevant rom for my phone. Can anybody help me? I am really in a bad situation. I just need to start my phone and see that it is running
Click to expand...
Click to collapse
hi man
i hope you still here
i have the same phone but my phone is GT-I9190
first of all your phone had 512MB Nand flash?
if it is like that
then i can help you
but i will ask you to upload to me the whole rom EXCEPT
system and data images
then i will be able to rebackup my rom and upload it to you
Hello guys,
I have an Star S7189 Phone which I had to return to stock (the owner tried to root but failed and wanted me to get rid of the root), but now that I flashed the stock rom the Display is totally glitchy.
The Device boots fine and I can even flash a custom recovery but even there the screen is glitched. (its basically unusable right now in this state)
I have to return it (working) to the owner.. or he will blame me (understandable)...
I flashed the following rom:
http://www.needrom.com/download/star-s7189s/
because it was the only one I could find that SP-Flashtool would let me flash.. (the other roms are all for MTK6589 but this device seems to be a MTK6582 one - at least thats what SP-Flashtool recognizes it for.
When I ran CPU-Z before all this it said 6589 though.. ?!
---
Usually I manage to fix things, but in this case I'm out of ideas.
When I got the phone it had a newer Firmware Version installed than the one I got now (it was from 2014) but I just cant find any other rom for the MTK6582 model than the one above...
Another weird thing: The sticker under the Battery says Quad 1.6 Ghz - but the MTK6582 is not 1.6 GHz is it?
I really hope anyone can help please !!!!!
I either need another rom or find a way to fix the display... I already thought it might be a hardware issue because even the battery charging screen and the custom recovery screens are affected by the glitches - but it was working alright before.. (with a half assed root which was not working .. or else I wouldnt have tried to flash stock rom anyway...)
HALP!
Additional Infos:
I *think* the rom has the wrong lcd drivers or smth .. because even I can't really "see" them, there seem to be onscreen buttons for menu and back, ALTHOUGH the device has hardware buttons for that - and the old rom didnt have any onscreen buttons showing ....
Please guys, if anyone knows a bit about those MTK china stuff please think of a way how to fix this thing .. I'm really out of ideas..
I have loaded that "MDT Flash Tool" which lets you choose drivers for lcd etc.. but this damn thing does not accept the MTK6582 rom which I need to flash - with MTK6589 roms (which do not work for the device) it opens them fine...
This could be the first soft-brick that I really cant fix ........and its due to lack of files it seems..?
Any way that I could "mod" the rom to get the display working?
Hi all. A friend gives me a Redmi Note 3 (MTK) for replacing the lcd and touch. But, after replacing those parts, the Redmi won't turn on, and goes Bootloop on MI logo. I tried to go in recovery mode, but not work. I downloaded the leatest hennessy stable image (fastboot version) from xiaomi and then I correctly flashed him with SP Flash Tool, but the bootloop seems remaning. I also tried to flash the xiaomi.eu V 7.5.1.0 (Quaze) and the V 7.2.3.0 (JamFlux) without preloader check, but the result is the same: bootloop.
What I can do? I didn't touch anything about software before this problem! I simply follow a guide for replacing the LCD screen (isn't my first time for replacing LCD in smartphones), I unmount anything and then re-mount, but the problem still the bootloop. I don't understand what to do. The phone has locked bootloader (the user didn't made anything with it), but goes in fastboot mode. There's any command to know what is wrong whit this redmi? I'm really furios, this is my first broken smartphone for repairing, but it isn't mine... And i'm in trouble... HELP ME!
antoniosavio96 said:
Hi all. A friend gives me a Redmi Note 3 (MTK) for replacing the lcd and touch. But, after replacing those parts, the Redmi won't turn on, and goes Bootloop on MI logo. I tried to go in recovery mode, but not work. I downloaded the leatest hennessy stable image (fastboot version) from xiaomi and then I correctly flashed him with SP Flash Tool, but the bootloop seems remaning. I also tried to flash the xiaomi.eu V 7.5.1.0 (Quaze) and the V 7.2.3.0 (JamFlux) without preloader check, but the result is the same: bootloop.
What I can do? I didn't touch anything about software before this problem! I simply follow a guide for replacing the LCD screen (isn't my first time for replacing LCD in smartphones), I unmount anything and then re-mount, but the problem still the bootloop. I don't understand what to do. The phone has locked bootloader (the user didn't made anything with it), but goes in fastboot mode. There's any command to know what is wrong whit this redmi? I'm really furios, this is my first broken smartphone for repairing, but it isn't mine... And i'm in trouble... HELP ME!
Click to expand...
Click to collapse
Have you old LCD screen? If yes, try to put it and see if device boot.
andersonaragao said:
Have you old LCD screen? If yes, try to put it and see if device boot.
Click to expand...
Click to collapse
Unfortunately not.. When I dismount this part, the touch was broken and the lcd was KO
antoniosavio96 said:
Unfortunately not.. When I dismount this part, the touch was broken and the lcd was KO
Click to expand...
Click to collapse
sorry but I think only way to see if the problem is in the display is getting another MTK device and try to test this one motherboard in other device with original display.
UPDATE: Tried to change the flex motherboard to usb port cable (seems damaged) but stills on bootloop. I have acces to fastboot, there's someone with a big heart that tells me any hoping question or solution?
Sorry can't really help but AFAIK there is a amount of different components used in our Xiaomi phones. Different lcds, different fingerprint etc etc.... Maybe your new Display is from a different manufacturer and that's why u got a bootloop.. maybe flashing a new rom could help because it uses other software ?!
Same problem. I just disassembled and assembled the phone (I was looking for a way to replace a broken touch). Seems like failed boot checks for device response (glass was broken a month ago but the phone was rebooted recently)