Related
Hello guys I got a x920 and was working good until it started doing something similar like Samsung Galaxy S3 Sudden Death.
The phone would randomly get a screen freeze, and the half bottom of the screen got distorted like green and pink lines, then slowly, the pixels were turning to black until the whole screen gets black, but the backlight would remain on.
I had to pull the battery out, and sometimes the phone would work again instantly, some other times, it wouldn't turn on, only after some time, and after a lot of battery pulls.
But last time I got this sudden death, the phone never came back.
I had the stock rom and only root.
My model version is: e2001v21_v89_zlh_hd
Most people with this phone have the e2001_v89_zlh_hd, and most roms on needrom.com are for e2001_v89_zlh_hd, there are a lot of roms for e2001v21_v89_zlh_hd though but I tried everything and I got DRAM Failed.
I use windows 8
SP flash tool v3.1304.0.119, v3.1308.0.125, v3.1316.0.150
And several other roms for both versions.
There is a solution from a French guy about the DRAM failed problem here, but I got the S5 rom downloaded as he stated, and can't get pass the first red bar on SP flash tool.
Do you have any idea what is going on with the 2 versions of the phone? People say that they read on chinese forum that v2.1 (e2001v21_v89_zlh_hd) has got different EMMC. So I guess roms from the e2001_v89_zlh_hd wont work.
I would like to know if you guys have any working rom for my e2001v21_v89_zlh_hd because I really need the phone at the moment. I must get it back to life.
ps (Is windows 8 suitable for flashing? I have installed mtk drviers normally through a weird process enabling manual driver installation through the advanced startup thingy on Windows 8, otherwise it wouldn't let me install the drivers.)
Voliminal_8 said:
Hello guys I got a x920 and was working good until it started doing something similar like Samsung Galaxy S3 Sudden Death.
ps (Is windows 8 suitable for flashing? I have installed mtk drviers normally through a weird process enabling manual driver installation through the advanced startup thingy on Windows 8, otherwise it wouldn't let me install the drivers.)
Click to expand...
Click to collapse
ok, there is no difference for using window 8 , xp, win 7, as long as u have installed the driver correctly.
as u said u can see the red bar, that mean yr driver was installed correctly.
all u need is the right preloader.bin
as i can understand from my past experiance, i think that the later batch of the phone, the manufacturer might use different DRAM or they might have changed the coding of the ram. that is why we see quite often there is complaint of DRAM fail when u try to flash the official rom for the phone. Not for newer model of the phone ( yr phone has two/three batches).
so may be u could ask the http://www.needrom.com/mobile/star-tengda-x920/ - smartdigi to create a preloader.bin from their phone for u , then u replace the preloader.bin in yr rom and flash it.
smartdigi is a team from Greece, and so am I, so yes, I just sent a message.
I hope I'll find a solution.
Voliminal_8 said:
smartdigi is a team from Greece, and so am I, so yes, I just sent a message.
I hope I'll find a solution.
Click to expand...
Click to collapse
i had read tru the needrom wed regarding thier rom, i saw there is a instruction to pass tru the "DRAM fail."
had u tried that before.
they also had rom that match with yr version.
Yes, I downloaded the rom, and still got DRAM failed.
Is there any way to install smartdigi rom through sp flash tool and not sd card?
here's the link http://www.needrom.com/mobile/star-tengda-x920
Yes, I downloaded the rom, and still got DRAM failed.
Is there any way to install smartdigi rom through sp flash tool and not sd card?
here's the link http://www.needrom.com/mobile/star-tengda-x920
Voliminal_8 said:
Yes, I downloaded the rom, and still got DRAM failed.
Is there any way to install smartdigi rom through sp flash tool and not sd card?
here's the link http://www.needrom.com/mobile/star-tengda-x920
Click to expand...
Click to collapse
ok, i just want to know if the procedure as they decribe will work, as i cannot test it, as i don.'t have the phone.
did u manage to get the preloder from them.
if u get the preloader from smartdigi , u stilll get the "DRAM fail" , then i think , may be their phone is an older batch,
for me, if u can read back from from the SP flash tool, (version 3.1316, (i justy learn that there is v3.1328 available)), then definitely u can flash yr phone with this preloader.bin
note
since u can't even go to recovery, then there is no way u can flash the rom with card flash rom from smartdigi, the only way to recover yr phone is tru cable flash rom that mean, u have to pass tru the "DRAM fail"
Well, I found the problem, the drivers installed are MTK USB Port, and not Preloader VCOM drivers.
I use windows 8 x64, I restarted with bypassing the signature thing.
The problem is, when I try to manually select the vcom driver, after the installation it shows up as MTK USB Port, and not as a vcom port.
Any solution?
Voliminal_8 said:
Well, I found the problem, the drivers installed are MTK USB Port, and not Preloader VCOM drivers.
I use windows 8 x64, I restarted with bypassing the signature thing.
The problem is, when I try to manually select the vcom driver, after the installation it shows up as MTK USB Port, and not as a vcom port.
Any solution?
Click to expand...
Click to collapse
no, it does not matter if it is preloader port or vcom port, actually they don,t make difference if u flash the rom.
that mean yr computer is talking to the phone correctly.
now the most important part is the "preloader.bin" file in yr rom must match the dram in yr phone.
that is why u hve to ask who has yr exactly same model of yr phone to create a preloader.bin.
or just try to download the preloader.bin as many as u can.
if u have a friend who has the phone same as as yours, then i can help to create from his phone, or u can create the preloader.bin from his phone
edit,
try to download the latest sp flas tool v3.1324 or v3.1328 ,flash the rom with it.
I tried several roms, with different preloader.bin files, non seems to work.
I tried with all sp flash tool versions, all 3.13904.0.119, 3.1308.0.125, 3.1316.0.150, 3.1328.0.183
Some versions of SP, are not showing up all the files gathered from the scatter file. Some other do.
Well, a smartdigi member, told me to use windows 7, because the mediatek drivers have gone as fas as windows 7 x64.
Voliminal_8 said:
I tried several roms, with different preloader.bin files, non seems to work.
I tried with all sp flash tool versions, all 3.13904.0.119, 3.1308.0.125, 3.1316.0.150, 3.1328.0.183
Some versions of SP, are not showing up all the files gathered from the scatter file. Some other do.
Well, a smartdigi member, told me to use windows 7, because the mediatek drivers have gone as fas as windows 7 x64.
Click to expand...
Click to collapse
ya, u could try with win7.
for me i can flash with win8 also.
i use win 7 at home, win8 at office, no problem.
u could try with win7, i think most likely , u will get the same result.
i had brick my s7589, i unbrick it with the right preloader. after that i tried with the preloader.bin that was originally came with the rom.
this time , it can pass tru the "dram fail", get the purple color, then yellow, then finish with green color. then i try to swith on the phone, but, no response from the phoe. it was bricked again.
then i flash back with the right preloader.bin, the phone back to life again.
did u manage to get preloader.bin from smartdigi?
for me, it is the best solution to unbrick the phone. may be there is some other ways that i don't know
stevenma61 said:
ya, u could try with win7.
for me i can flash with win8 also.
i use win 7 at home, win8 at office, no problem.
u could try with win7, i think most likely , u will get the same result.
i had brick my s7589, i unbrick it with the right preloader. after that i tried with the preloader.bin that was originally came with the rom.
this time , it can pass tru the "dram fail", get the purple color, then yellow, then finish with green color. then i try to swith on the phone, but, no response from the phoe. it was bricked again.
then i flash back with the right preloader.bin, the phone back to life again.
did u manage to get preloader.bin from smartdigi?
for me, it is the best solution to unbrick the phone. may be there is some other ways that i don't know
Click to expand...
Click to collapse
Well... installed windows 7 in another partition.
It was like I never did it, exactly the same result. Everything behaved the same.
I don't know... maybe I have crappy mtk drivers, or I'm doing something wrong while installing them.
Let me describe the steps, and if I'm somewhere wrong you can tell me.
Well, after a clean windows 7 install, I connect the phone to the pc (with or without battery,I think I tried both, didn't see something change) it gets to "other devices" as an "unknown device". right click to update driver software, select the folder with vcom drivers.
It gets recognized as a mtk usb port.
Try to flash like that, same results.
Then I go to update driver again, but this time I click "let me pick from a list of device drivers on my computer." I uncheck show compatible hardware, then I choose MTK Preloader USB VCOM Port.
the device now shows up to the device manager as "MTK Preloader USB VCOM Port".
Try to flash, everything is the same...
I read somewhere, that the normal installation of vcom drivers is kinda different, that it get's shown up as "MTK Preloader USB VCOM Port" right away, and I read that when you install the vcom driver correctly, it connect and disconnects the device every 3 seconds.
Well.. I didn't manage to get the preloader.bin yet, I'll ask for it, but why the official rom on needrom.com preloader.bin is not working with my phone? And why would smatdigi preloader.bin would work for me?
I tried roms that are for e2001v21_v89_zlh_hd but even their preloader wouldn't work for me.
first of all, stop playing with those preloaders. random flashing will brick your motherboard of your computer too, if you flash a wrong BIOS file. clear? okay. the DRAM error occurs if the Rom is mismatching the "signature" of your device. so, before trying to flash it, take another one, in this case, the right one. ( for example: my device (n9770) got few cameras, few board revisions, ddr or ddr2 Ram and so on, only one Rom or a mix of different files will work)so flashing a wrong firmware causes more "damage" or "errors". have you backed up your firmware before rooting?
you need to find a full backup of your device ( most likely a Rom directly from your vendor) including ALL needed partitions for flashtool. ROM's of new devices are hard to find, even for n9770 (mt6577) there are ROM versions from 06-2012 till now. so, if you got a "newer" device, you need to get the correct firmware and flashtool should flash without problems. also, your drivers are working perfectly, otherwise flashtool won't show the red bar wich is checking the device.you may need to check if the "second" driver is installed correctly, because the device will switch from preloader mode to "flash mode". maybe the driver for the preloader is installed correctly, but it can't switch to flash mode.
Chrizzly92 said:
first of all, stop playing with those preloaders. random flashing will brick your motherboard of your computer too, if you flash a wrong BIOS file. clear?
Click to expand...
Click to collapse
Clear bro, but I never really managed to do a flash. Just never. I only get dram failed.
Chrizzly92 said:
okay. the DRAM error occurs if the Rom is mismatching the "signature" of your device. so, before trying to flash it, take another one, in this case, the right one. ( for example: my device (n9770) got few cameras, few board revisions, ddr or ddr2 Ram and so on, only one Rom or a mix of different files will work)so flashing a wrong firmware causes more "damage" or "errors". have you backed up your firmware before rooting?
Click to expand...
Click to collapse
I don't think I did any more harm, since nothing really fot flashed.
Not I don't have a backup :/
Chrizzly92 said:
you need to find a full backup of your device ( most likely a Rom directly from your vendor) including ALL needed partitions for flashtool.
Click to expand...
Click to collapse
I bought it from focalprice, even if they send me any rom, it will be one of the officials found in needrom.com ... So I don't think they'll handle it.
Chrizzly92 said:
also, your drivers are working perfectly, otherwise flashtool won't show the red bar wich is checking the device.you may need to check if the "second" driver is installed correctly, because the device will switch from preloader mode to "flash mode". maybe the driver for the preloader is installed correctly, but it can't switch to flash mode.
Click to expand...
Click to collapse
How can I check that the second drivers is installed correctly?
just open your device manager and check, if the device gets recognized correctly. start a flash and check, if there are any devices gets loaded while trying to flash. if so, install the correct driver. there are some issues with that sometimes.
if this won't work, try using MTD tool. flasing through there should work always, but it got some issues with vcom drivers. you need to assign every vcom port to the mtk device. explaining of this is retty hard since english isn't my motherlanguage, so its best to check google or xda for that.
also, can you start your device into recovery, or is it really "dead"? no bootlogo, nothing?
No the device is hard bricked, no recovery at all. Not anything. :/
I can't use MtkDroidTool, it doesn't detect my device.
hmn, i would suggest its a hardware failure. never saw a device "dying" without flashing before.
btw: i meant SPMultiPortFlashDownloadProject tool, this is a more advanced variant of sp flash tool. just google for it and put a log in here, so i (we) can check whats the matter.
Chrizzly92 said:
hmn, i would suggest its a hardware failure. never saw a device "dying" without flashing before.
btw: i meant SPMultiPortFlashDownloadProject tool, this is a more advanced variant of sp flash tool. just google for it and put a log in here, so i (we) can check whats the matter.
Click to expand...
Click to collapse
I already have this tool and used it with the same results.
Which log do you need? It has 3 but 2 of them are really long, cant fit them in one post.
Voliminal_8 said:
I already have this tool and used it with the same results.
Which log do you need? It has 3 but 2 of them are really long, cant fit them in one post.
Click to expand...
Click to collapse
did u manage to get the preloader from smartdxxx............. ???????
it just takes 5 minutes (the most) to create the preloader from the phone.
take up the battery from the phone, run sp flash tool, connect the phone to computer, 5 sec, the rom_0 is read
put back battery, on the phone, connect the phone to computer, run mtk droik tool, 30 secs later, the preloader is created.
china phones
stevenma61 said:
did u manage to get the preloader from smartdxxx............. ???????
it just takes 5 minutes (the most) to create the preloader from the phone.
take up the battery from the phone, run sp flash tool, connect the phone to computer, 5 sec, the rom_0 is read
put back battery, on the phone, connect the phone to computer, run mtk droik tool, 30 secs later, the preloader is created.
Click to expand...
Click to collapse
been to a lot off repair phones shop and all stead screen x920 done buy a SquareTrade 2 yr warranty £30.99 ins on phones
Hi, i've bricked my phone...someone knows how to unbrick.?
luisfernandoo.nunezfranco said:
Hi, i've bricked my phone...someone knows how to unbrick.?
Click to expand...
Click to collapse
Without any further details, it's going to be difficult to help. It's pretty hard to do so..... What did you do to brick it? Can you get into recovery. Do you have a custom rom? Provide some more details & someone might be able to help you
mightymaki said:
Without any further details, it's going to be difficult to help. It's pretty hard to do so..... What did you do to brick it? Can you get into recovery. Do you have a custom rom? Provide some more details & someone might be able to help you
Click to expand...
Click to collapse
>Hi Friend, i would appreciate yor help, my Nubua Z7 max is bricked after flashing the new(from needrom site) 5.0 stock rom and reflashing the original kitkat stock rom.
I need to repartition the phone storage , when i boot it appears only 4.0 Gbyte storage for programs , but no internal storage.
How can i repartition the internal storage?
Thank you
Simonis said:
>Hi Friend, i would appreciate yor help, my Nubua Z7 max is bricked after flashing the new(from needrom site) 5.0 stock rom and reflashing the original kitkat stock rom.
I need to repartition the phone storage , when i boot it appears only 4.0 Gbyte storage for programs , but no internal storage.
How can i repartition the internal storage?
Thank you
Click to expand...
Click to collapse
There are some instructions on the Z7 mini thread here on XDA. Have a search & follow the instructions
Unbrick Z7 max
mightymaki said:
There are some instructions on the Z7 mini thread here on XDA. Have a search & follow the instructions
Click to expand...
Click to collapse
Thank you but i did not find anything relevant by searching
[email protected] said:
Thank you but i did not find anything relevant by searching
Click to expand...
Click to collapse
You can follow this thread: http://www.androidiani.com/forum/zte-nubia-z7/446548-guida-di-unbrick-z7-max-mini.html
use google translate.
I am going to post a guide in English in about 2 hours. I have bricked mine and I followed the procedure from androidiani.
Guide to unbrick ZTE Nubia Z7 Mini
I have done this procedure on my device without any problem after a repartition failure, but I am not responsible about anything happens to your device (which is already bricked...)
The source is http://www.androidiani.com/forum/zte-nubia-z7/446548-guida-di-unbrick-z7-max-mini-27.html
1) We disable driver signature verification for windows.
- Windows XP https://mega.co.nz/#!30I1yLRD!kLblCqP9_LmiOXjpfzGbFL7m2zqAqKqZ8ciPFWMBDB0
- Windows 7 http://www.sabrent.com/support/knowledgebase.php?article=14
- Windows 8 http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
2) We download the drivers, which we extract in our desktop.
3) We connect the device while switched off to PC via a USB 2.0 port, and we launch Windows device manager. We press simultaneously Vol +/Vol -/Power button for ~5 seconds. We should see our device identified as QHUSB_BULK under Ports section in device manager. If we get prompted to format several drives we cancel all of the actions.
4) We right-click at device QHUSB_BULK > Update Driver > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Have disk > Browse, and we open Nuova cartella folder which we have extracted, containing the drivers.
We choose the driver named Qualcomm HS-USB QDloader 9008 and we install it.
We can see our device now identified with that name in the device manager.
5) We download Nubia Toolstudio , and Z7 mini files.
We extract them inside a folder in our desktop, and we run toolstudio as administrators, disabling our anti-virus, or putting the program to its' exceptions because it will be detected as malware.
In the prompt which will pop-up requiring a password, we enter the e-mail address found at the .txt file.
6) We select eMMC Download, we refresh and we should see our device identified like this.
7) We select browse, and we select the folder nx507J_files containing the Z7 mini files.
8) We select start all, and we wait until the procedure finishes.
The whole process has ended, we unplug our device and we can boot it. We will be with stock rom 1.28
Hi Stratos,
i was able bevor to google translate the italian text an d using the screenshots avaliable there i was able to flash the Nubia 7 MAX
software. BUT no imeis are in the Phone so now i have to find a method to type the IMEI numbers in the Phone dont know how..
I tried to create a flashable zip (as suggested by nano7mobile.blogspot) but did not work maybe becuase i dont know
the IMEI Folder location inside the Phone..
Simos
previously after bricked zte z7 max, can flash with ToolStudio : http://www.needrom.com/download/z7-max-2-13-android-5-beta_eng_chi/ (file: NX505J_CNCommon_V2.13.tar)
voila, phone revive.. thankyou..
Another Problem is Appear..
Imei,Meid, is gone.
i backup imei (blank) with Qpst, generate name: blank_imei.QCN ( ^^)
edit my own file : blank_imei..QCN (with blank imei,meid,esn)
the file is about 141 KB.
i open with hexa editor, feel confuse, don't know where to start, don't know the location of imei,meid,esn.
i don't know where "offset" position to be edit.
i google around,
i think need file : *.QCN from someone z7 max backup, to determine the position of imei,meid,esn. (cmiiw)
can someone help me, provide backup of Z7 Max *.QCN file?
i will Surely change it with hexa editor, edit it with my own imei,meid,esn.
or there is another way to fix this imei-meid-esn problem?
please help...
best regard's
stratos_21 said:
I have done this procedure on my device without any problem after a repartition failure, but I am not responsible about anything happens to your device (which is already bricked...)
The source is http://www.androidiani.com/forum/zte-nubia-z7/446548-guida-di-unbrick-z7-max-mini-27.html
1) We disable driver signature verification for windows.
- Windows XP https://mega.co.nz/#!30I1yLRD!kLblCqP9_LmiOXjpfzGbFL7m2zqAqKqZ8ciPFWMBDB0
- Windows 7 http://www.sabrent.com/support/knowledgebase.php?article=14
- Windows 8 http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
2) We download the drivers, which we extract in our desktop.
3) We connect the device while switched off to PC via a USB 2.0 port, and we launch Windows device manager. We press simultaneously Vol +/Vol -/Power button for ~5 seconds. We should see our device identified as QHUSB_BULK under Ports section in device manager. If we get prompted to format several drives we cancel all of the actions.
4) We right-click at device QHUSB_BULK > Update Driver > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Have disk > Browse, and we open Nuova cartella folder which we have extracted, containing the drivers.
We choose the driver named Qualcomm HS-USB QDloader 9008 and we install it.
We can see our device now identified with that name in the device manager.
5) We download Nubia Toolstudio , and Z7 mini files.
We extract them inside a folder in our desktop, and we run toolstudio as administrators, disabling our anti-virus, or putting the program to its' exceptions because it will be detected as malware.
In the prompt which will pop-up requiring a password, we enter the e-mail address found at the .txt file.
6) We select eMMC Download, we refresh and we should see our device identified like this.
7) We select browse, and we select the folder nx507J_files containing the Z7 mini files.
8) We select start all, and we wait until the procedure finishes.
The whole process has ended, we unplug our device and we can boot it. We will be with stock rom 1.28
Click to expand...
Click to collapse
I bricked it yesterday trying to downgrade from cm12.1 to Official nubia 3.01. Yesterday it showed up as QHUSB_BULK, but now it shows up as android cd rom drive and I can't do anything with it. Currently it will boot into the nubia recovery and it will charge, I can't enable it as mass storage device . I can see that all my files are there through the recovery but I can't gain access to them. Will it let me flash from External USB micro sd card as I am about to go buy one? If I turn it on it goes straight into nubia recovery and when I have it off it charges.
When you said 1.28 did you mean Official 1.82? The 1.82 did not work for me as I had an official 1.82 already downloaded. The file you linked I could not download due to poor connection. I was able to install Nubia 3.01 but I think I lost my imei because it says no sim detected. Fortunately, I do have an efs backup from HC-kTool - will I be able to restore that? Also all of this began as I went straight to V3.01 instead of V2.03, first . And then I went to cm12.1 which was extremely buggy so I try to downgrade to official v3.01 and then to Kitkat 4.4.4 v1.82 when something happened to the pc and phone lost connection during the downgrade.
What should I do next? I currently am on Lollipop 3.01 with no radios, baseband etc. My blue-tooth and wi-fi are working. Should I try to restore my efs.img I backed up with HC-kTool?
next4nextel said:
I bricked it yesterday trying to downgrade from cm12.1 to Official nubia 3.01. Yesterday it showed up as QHUSB_BULK, but now it shows up as android cd rom drive and I can't do anything with it. Currently it will boot into the nubia recovery and it will charge, I can't enable it as mass storage device . I can see that all my files are there through the recovery but I can't gain access to them. Will it let me flash from External USB micro sd card as I am about to go buy one? If I turn it on it goes straight into nubia recovery and when I have it oharges.
Click to expand...
Click to collapse
I'm in a similar situation with mine, self inflicted of course while I was trying to get the phone rooted with 3.01.
Anyway where it is now I can still boot to a point and I still have the Nubia recovery util fully functional. If you go into that and look under 'other' you will see that you have the ability to enable mass storage from there and yes you have the option of updating via SD,internal and OTG via the recovery util.
For me though unless I want to get nasty and do things from scratch it looks like I can only carry out an update using an official Nubia file and not just a recovery nor an earlier or current version of stock firmware which is kind of weird. And yes you have the option of updating via the SD,internal and OTG via the recovery util.
Thanks Parso, fortunately I followed the above steps and I restored to official 5.0. but then I lost my imei and had to sort that out. I actually like the official 5.0 except for 2 bugs one where I can't see the WiFi icon on the status bar unless I'm connected to Wi-Fi. And the other is sometimes when I get a call the screen never lights up and I can't swipe to answer the calls which is really annoying because I have to call them back.
I have the same situation right now.I upgraded my z7max 1.64 to 3.09.then I tried cm12 but there were so many problems with mobile data.
So I decided to change it.It was a big mistake to go back to 1.64 without reading anything.In the end it stopped working after a few trys.
Anyway I managed to enter toolstudio 4.6 and show it at por as com13 .Then I watched steps and flashed 3.09 to phone.It seemed like succesfull but it wasnt.Now it s not reacting and all black screen.
Also when I connected it to computer again at the beginning it was QHUSB_BULK with yellow sign.Then I tried to install Qualcomm CDMA Technologies MSM to set it up.Now it became worse.When I connect my phone it s written "unidentifed device" on device manager.
I guess we re missing one thing.For example this "Qualcomm CDMA Technologies MSM" or qhsusb驱动 folders are for XP, Vista or 7. I m using windows 8 right now and I think these files are not suitible as drivers.
So my phone is dead now.If I can set drivers up I guess I can fix it.But I cant find any other drivers and that s the biggest problem.
Hi everyone,
My feedback, After try CM12.1 i decided to return at android 4.4 and for that i used nubia updated tools and nubia studio.
After flash, no imei and only USA Band.
After restored my NV backup 1 IMEI of 2 come back ?!, After restore my
NV Value (values from opo guide, because NV Calculator give me a bad number ?) all band done USA, ENRO, JAPAN etc ...
BUT the phone lock/unlock (after enter my lock pin) every 5 secondes ?
Please help me, i have no ideas
buzz-27 said:
Hi everyone,
My feedback, After try CM12.1 i decided to return at android 4.4 and for that i used nubia updated tools and nubia studio.
After flash, no imei and only USA Band.
After restored my NV backup 1 IMEI of 2 come back ?!, After restore my
NV Value (values from opo guide, because NV Calculator give me a bad number ?) all band done USA, ENRO, JAPAN etc ...
BUT the phone lock/unlock (after enter my lock pin) every 5 secondes ?
Please help me, i have no ideas
Click to expand...
Click to collapse
For all those who are facing issues unbricking the phone as given above, use these Qualcomm drivers (5th post from top)
http://forum.cyanogenmod.org/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/page__st__40
Point to these drivers from Device manager (QHUSB_BULK). Your device should be identified correctly. Also follow the same steps exactly as given earlier. I managed to unbrick with completely working phone & IMEI.
If anyone is intersted in reading why Qualcomm devices cannot be bricked completely, read the links given below in 2 parts
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/
http://www.androidbrick.com/unbrick...oader-9008-if-you-have-the-right-kind-of-rom/
next4nextel said:
Thanks Parso, fortunately I followed the above steps and I restored to official 5.0. but then I lost my imei and had to sort that out. I actually like the official 5.0 except for 2 bugs one where I can't see the WiFi icon on the status bar unless I'm connected to Wi-Fi. And the other is sometimes when I get a call the screen never lights up and I can't swipe to answer the calls which is really annoying because I have to call them back.
Click to expand...
Click to collapse
Hello,
COuld you please tell me how you solved the problem, cause all imei and meid are:null
Please someone help me fix the imei problem, i have my imei nr's on the box, but i did not do a back-up.
Thank you
zte z7 mini
hi bad rom update and can not get back into recovey have looked at the posts but drivers link down and when i get Nubia Toolstudio i downloade 3 times put needs password ??? any help please i am runing on windows 10 64bit and win 7 32 bit if some can help on here or mail me on [email protected] going mad with this
Hi, this is my first post here. XDA-forums are great and I think here is the place where you would help me to solve the problem with my phone Nubia z7max.
The problem is that after a software (ROM) update in recovery TWRP from the stock 3.22 to Mokee (android 6 ) , the phone remained on logo "Nubia powered by Android". I have read probably everything written about that problem in all possible places that I found around the internet including Chinese NUBIA forum, Androidiani, 4PdA and so on. I followed all the steps which incidentally are the same everywhere for fixing the phone:
http://forum.xda-developers.com/zte-z7/general/unbrick-nubia-z7-mini-t3006268/page2
stratos_21 said:
I have done this procedure on my device without any problem after a repartition failure,
but I am not responsible about anything happens to your device (which is already
bricked...)
The source is http://www.androidiani.com/forum/zte-nubia-z7/446548-guida-di-unbrick-z7-max-mini-27.html
1) We disable driver signature verification for windows.
2) We download the drivers, which we extract in our desktop.
3) We connect the device while switched off to PC via a USB 2.0 port, and we launch Windows device manager. We press simultaneously Vol +/Vol -/Power button for ~5 seconds. We should see our device identified as QHUSB_BULK under Ports section in device manager. If we get prompted to format several drives we cancel all of the actions.
4) We right-click at device QHUSB_BULK > Update Driver > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Have disk > Browse, and we open Nuova cartella folder which we have extracted, containing the drivers.
We choose the driver named Qualcomm HS-USB QDloader 9008 and we install it.
We can see our device now identified with that name in the device manager.
5) We download Z7 mini files.
We extract them inside a folder in our desktop, and we run toolstudio as administrators, disabling our anti-virus, or putting the program to its' exceptions because it will be detected as malware.
In the prompt which will pop-up requiring a password, we enter the e-mail address found at the .txt file.
6) We select eMMC Download, we refresh and we should see our device identified like this.
7) We select browse, and we select the folder nx507J_files containing the Z7 mini files.
8) We select start all, and we wait until the procedure finishes.
The whole process has ended, we unplug our device and we can boot it. We will be with stock rom 1.28
Click to expand...
Click to collapse
The difference in my case is that the procedure for flashing have completed with no errors and the phone restarts and it is in the same condition without any change: the logo "NUBIA powered by Android".
I tried to maybe over 10 different drivers. The phone is detected by the computer as it should be. When downloading the ROM in to the phone with ToolStudio_4.6 or NX505J Nubia Tool V2.1.0, procedure runs without any problems but the result is the same. There is no possibility to enter into recovery, I was TWRP and accordingly have a backup made in TWRP ahead of time when my phone is working normally.
With the combination Vol+, Vol- & Power pressed together for about 7-8 seconds the phone is recognized by the computer as HSUSB_Bulk and a cuple of disc drives with a different volume. Drivers are installed correctly although hardware is 19d2 and the phone is recognized as Qualcomm HS-USB QDLoader 9008 (COM XX).
With the combination Vol+ & Power pressed together for about 7-8 seconds the phone is recognized as Android ADB Interface, on screen are Nubia logo. In this kind I can charge (at least visibly) TWRP through "Z7_Max_All_In_One_Tool_Created_By_Tigreos" (NeedRom), but after that I can not go into Recovery. With the same tool I can install stock recovery too but still can not login to recovery.
The biggest success I've achieved after many attempts, two weeks from now, are to initial animation pictures and melody at startup and phone suddenly goes off.
Pleace Help
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?
Long story short. The phone had a problem with the download mode update. I tried flashing one KZ file (or what the extension is) and Download Mode completely locked up mid update. As in, animation died and the screen was frozen. Pulled out the battery... Download Mode stopped functioning entirely and now I was having this Secure Boot error that was popping up each time I would start the device. Tried a few guides to fix it myself... (long story short, the phone wouldn't boot up, it would just allow me to access all the partitions however, I would have a secure write thingy to pass, so I had 0 access to the phone) and had 0 success with the fixing process.
Today I got mad. Connected the phone again... tried something again, it didn't work. I launched diskpart on CMD. Selected the phone's volume. Typed "Clean" and... here we are. The phone doesn't even have a name anymore (before it had LG G2 Mini regardless of it's state), it just shows up as "Qualcomm HS-USB QDLoader 9008 (COM4)". And from my knowledge... that's a really hardbricked device. Now... I am asking everybody who has more advanced knowledge with this device. Please help me. I know there's programming to do now and several other things here but I beg you... Please guide me and/or help me.
Note: The device doesn't even turn on it's own display. It just connects with that name once it's plugged into the PC. I read a few articles about this... still very clueless as to what I'm supposed to do. @mobiusm Any advice?
Model variant: D620
Does diskpart see the memory chip?
If it does, then I can tell you how you might be able to fix it.
Vagelis1608 said:
Does diskpart see the memory chip?
If it does, then I can tell you how you might be able to fix it.
Click to expand...
Click to collapse
Nope. Sadly, it only gets detected on it's COM port. Diskpart comes back null as well as disk manager doesn't display a storage solution connected.
What OS is your PC on?
Linux might help.
On the l90 forum there is a guide on how to make the phone enter 9008 mode (requires disassembly ofthe phone). It might work for the g2m as well. Just need to check where the Qualcomm test point is.
Good luck!
Vagelis1608 said:
What OS is your PC on?
Linux might help.
Click to expand...
Click to collapse
Windows 8.1 but I also have Ubuntu installed on a VM.
mobiusm said:
On the l90 forum there is a guide on how to make the phone enter 9008 mode (requires disassembly ofthe phone). It might work for the g2m as well. Just need to check where the Qualcomm test point is.
Good luck!
Click to expand...
Click to collapse
The phone is already in 9008 mode tho.
fogoticus said:
Windows 8.1 but I also have Ubuntu installed on a VM.
The phone is already in 9008 mode tho.
Click to expand...
Click to collapse
Does diskpart see the memory chip?
Or it's Linux counterpart (fdisk, I think)?
Vagelis1608 said:
Does diskpart see the memory chip?
Or it's Linux counterpart (fdisk, I think)?
Click to expand...
Click to collapse
Nothing is detected. Other than the name... nothing appears anywhere be it Windows or Linux.
From what I read, it's not dead. It just needs low level code injected, to be partitioned and so forth....
EDIT: Fixed with unbricking service. No other way AFAIK. The error is caused by flashing to US998 20d from V300L 21k. Another user ran into the same error flashing from V300 21 to H930 20. So I guess the takeaway is to be careful when downgrading.
So I think I messed up and now my phone is stuck in UEFI crash (text screen with "LGE crash handler: UEFI crash"). It keeps bootlooping and I can't even turn it off.
QPST says it's in download mode when I plug it in.
Any chance I might be able to fix this?
Picture of the error screen attached
I think you need QFIL to find the emmc prog file, I also experienced the same problem.
sandking707 said:
I think you need QFIL to find the emmc prog file, I also experienced the same problem.
Click to expand...
Click to collapse
I've been messing with QPST but of course there isn't much I can do as-is.
I can use QPST by Port Qualcomm HS USB QDLoader 9008, but I do not have a .mbn file if you have a share file thanks
sandking707 said:
I can use QPST by Port Qualcomm HS USB QDLoader 9008, but I do not have a .mbn file if you have a share file thanks
Click to expand...
Click to collapse
it's a hard brick there is no solution for now (lg g5 .g6.v20.v30 ....) jus twait
im in the same situation on my v300s.:crying:
Read some other threads, there was a mention of a built in fastboot in the PBL but that seems to be untrue.
Maybe this isn't the PBL considering screen is working and there's LG branding.
I've also heard of a recent exploit for SD chipsets, something about the PBL's signature verification. If this works for the firehose, then maybe someone can modify an existing firehose to adapt for the V30, this way a leak won't be necessary. Though if anyone will bother is another matter.
seloka180 said:
it's a hard brick there is no solution for now (lg g5 .g6.v20.v30 ....) jus twait
im in the same situation on my v300s.:crying:
Click to expand...
Click to collapse
edit:
my device solved with jtag in repair shop.
Sent from my LGM-V300S using XDA Labs
So I still haven't managed to fix this, but did some reading. The phone isn't even in 9008 mode so remote repair probably isn't possible. It shows up as a LG AndroidNet device or something. It might be in 9006 mode except with LG's USB ID (1004:6340) and without an interface to the internal storage.
I tried using a tool to communicate in sahara mode but it's outdated so it can only connect to the device and not much else, the commands are mostly invalid. Interestingly when I tried to switch to download mode it requests a 1KB "AMSS" image.
Anyway I'll need a way to enter 9008 mode if I'm to get it repaired. If anyone know of a way I'd appreciate it if you share.
test point lg v30
Duo8 said:
So I still haven't managed to fix this, but did some reading. The phone isn't even in 9008 mode so remote repair probably isn't possible. It shows up as a LG AndroidNet device or something. It might be in 9006 mode except with LG's USB ID (1004:6340) and without an interface to the internal storage.
I tried using a tool to communicate in sahara mode but it's outdated so it can only connect to the device and not much else, the commands are mostly invalid. Interestingly when I tried to switch to download mode it requests a 1KB "AMSS" image.
Anyway I'll need a way to enter 9008 mode if I'm to get it repaired. If anyone know of a way I'd appreciate it if you share.
Click to expand...
Click to collapse
there are two golden points near the ribbion of battery but not the big ones under the ribbion wehen you connect both the phone will go 9008 mode
i am stuck in the very same situation as OP please if anyone has any way or idea on fixing this issues let us know and so others can benefit from it as well
thanks
Sahara mode LG v30, please help!
Hello there,
my lg v30 us998 was 10% battery. I was browsing the web and suddenly it freezed up. I cound´t do nothing until it shut down itself after a few minutes. I plugged in to the charger and the same message showed: UEFI crashed. Sahara mode... Any help please?
Not sure if it is actually possible for me. Still no solution. I was waiting for a more complete reply ...