Hi! I really head your help!! I looked a lot around and followed lots of guides on how to revive my phone, but i've some big issue with it and i really hope that someone here may help me...
The Hard Brick (it won't turn on, it won't charge, it seems like he's totally dead) occurred the other day, i was trying to open googlemaps and the SP was really slow, so i turned it off, and then i wasn't able to turn it on again, at first it was stucked at the screen with the logo (before the splash animation, the logo that you can't normally change) then i managed to turn it on after 2 or 3 times taking off the SD card, but i got a corrupted homescreen, i turned it off again and then, after 2 or 3 times, i got the Hard Brick!!
Probably in my last attempts i created a bounch of errors in the rom that bricked my phone.
Here's what i've done to revive it:
- SPFlashTool 1332.0.187
- official drivers, recovery, rom, etc, from the jiayu.es website.
- removed the battery, manually installed the drivers.
- with spft i loaded the scatter file of the official rom and started the format:
the phone is recognised as Mediatek USB VCOM (Android) (COM3)
i always got the error: S_COM_PORT_OPEN_FAIL (1013)/B] (with every option available)
I tryied to download only the preloader.bin and the recovery.img but i recive the same error.
- someone give me an advice: to remove every old driver for the phone and leave the SPFlashTool to recognise the phone forcing the installation of the drivers. And i really don't get how to do it, the windows update automatically detect the device, if i stop the windows update i simply get an unknown device, the SPFT don't have a chance to recognise it and force the installation of the drivers.
Does anyone of you have a solution, a similar problem, a way to revive my cellphone?
I really can't effort another one XD
FenriX` said:
Hi! I really head your help!! I looked a lot around and followed lots of guides on how to revive my phone, but i've some big issue with it and i really hope that someone here may help me...
The Hard Brick (it won't turn on, it won't charge, it seems like he's totally dead) occurred the other day, i was trying to open googlemaps and the SP was really slow, so i turned it off, and then i wasn't able to turn it on again, at first it was stucked at the screen with the logo (before the splash animation, the logo that you can't normally change) then i managed to turn it on after 2 or 3 times taking off the SD card, but i got a corrupted homescreen, i turned it off again and then, after 2 or 3 times, i got the Hard Brick!!
Probably in my last attempts i created a bounch of errors in the rom that bricked my phone.
Here's what i've done to revive it:
- SPFlashTool 1332.0.187
- official drivers, recovery, rom, etc, from the jiayu.es website.
- removed the battery, manually installed the drivers.
- with spft i loaded the scatter file of the official rom and started the format:
the phone is recognised as Mediatek USB VCOM (Android) (COM3)
i always got the error: S_COM_PORT_OPEN_FAIL (1013)/B] (with every option available)
I tryied to download only the preloader.bin and the recovery.img but i recive the same error.
- someone give me an advice: to remove every old driver for the phone and leave the SPFlashTool to recognise the phone forcing the installation of the drivers. And i really don't get how to do it, the windows update automatically detect the device, if i stop the windows update i simply get an unknown device, the SPFT don't have a chance to recognise it and force the installation of the drivers.
Does anyone of you have a solution, a similar problem, a way to revive my cellphone?
I really can't effort another one XD
Click to expand...
Click to collapse
There is a guide right here
I already tryied to revive my phone with this guide, but with no success...
I was thinking that maybe someone can show me the right driver (with all the package of driver that i find i always have no idea which one i've to install)
And maybe someone already tryied to revive a jiayu g4a and know the name of the right preloader, 'cause apparently what i need to do is to download into the SP the right preloader to revive it...
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
Hi everyone. As I said on a former post, I have an Alcatel 1t 7 tablet; I need its stock recovery image, but even stock firmware is getting impossible to find. I mean, apparently there are firmware for that reference of tablet, but what happens, is that there are several models that share the same physical appearance, but have different hardware, so, they have different firmware, and by that reason, their firmware don't work for my tablet. Anyway...
The fact is, looking that its original firmware is not available on the internet, at least publicly; I'm trying to reflash my tablet by using alcatel's tool called "Alcatel Mobile Upgrade", a tool that I don't guess, would be unknown for many of you. So as I said, I'm trying to reflash it with it (and in the process, restore stock recovery, I hope). So I installed MTK drivers, installed the version recommended for this tablet, followed program's instructions, but when I reach step 2 of 4, the program warns me saying this: "Read terminal information failed. Unplug device, remove the device battery and plug it again - Repeat step 2 and try again".
The issue is, that its battery is internal, not removable; even, is soldered to the board. And I must add, that at first, when I bought this tablet and began to "experiment" with it, I was using SP flash tool, and it was giving me almost the same warning that Alcatel mobile upgrade, but later I discovered what that was a fail of the used sp flash tool version. On a webpage, someone recommended a specific version of sp flash tool to fix that issue; I mean, that I could download firmware to the device without having to "unplug battery"; and It worked.
So first ¿How can upgrade my tablet by using that program?¿What am I doing wrong?¿ Which device must appear under device manager, to it can work?¿mtk usb port, Mediatek DA usb VCOM, Android preloader, or which one? And second, ¿Could be this problem, due to alcatel's mobile upgrade version?
let battery drain to make sure device is powered off. you only have preloader mode for a second - within this time pick up in device manager and install preloader drivers.
if drivers installed correctly, first start flashing, then connect phone. flash tool will keep device in preloader mode for the flashing time period
aIecxs said:
let battery drain to make sure device is powered off. you only have preloader mode for a second - within this time pick up in device manager and install preloader drivers.
if drivers installed correctly, first start flashing, then connect phone. flash tool will keep device in preloader mode for the flashing time period
Click to expand...
Click to collapse
Thank you for replying. Definitely using Alcatel mobile upgrade is not an option, at least to me. I mean, I couldn't make it work in any way. "Fortunately", after an exhaustive search, I could find a post on internet, that recommended for a similar issue, to use Sugar MTK; the publisher shared this program and its credentials, for can use it . So I downloaded and used it, and I could restore my original stock. Now my issue is to port it to TWRP, but now I'm gonna to write a new post about it.
link me to the sugarmtk