Hello, I was having issues with my phones (ZTE MAX XL N9560) cellular network, being that although I was having no problems with my phones signal and even had good data connection on my phone I realized I couldn't receive any calls or text messages on the phone, It simply didn't work anymore...The network was good, internet connection was also good but I noticed carrier services such as text messaging were simply not working and to cap it all off, My wireless tethering mobile hotspot was also not working too. I tried tinkering with the network settings even using the android hidden menu *#*#4636#*#* to change the network bands trying to see if it would somehow solve my dilemma but ALL to no avail. So I finally decided to flash the stock rom of the phone in desperate hopes it would be my saving grace but as LUCK would have it the flashing process failed. The QFIL software I was using to flash the stock gave me a FLASH FAIL: FIREHOSE.MBN WAS UNABLE TO LOAD THE IMAGE; AND THAT WAS THE HAMMER ON THE NAIL FOR MY PHONE IT HARD BRICKED. So right now I'm left with a dead phone unable to to power it on, go to FTM mode and even worse it wont boot to EDL mode(Emergency Download Mode) which would have given me hopes to restore the phone. I'm only able to boot it to the ZTE HANDSET DIAGNOSTIC MODE which enables my computer to identify the phone. I've tried using several other qualcomm and zte device flashers and its either I get a FAIL UNABLE TO SWITCH TO EDL MODE or it flat out wont work at all
Can anyone, somebody please help me out with this please ......
THANKS:good:
if you got the right firehouse programmer and you have qfil/qset set up right with your files in the right places...and the correct ROM/firmware....I'm gonna ask you a crazy question ..Doesthe folder that your rom is in probably have the name of the firmware build like when downloaded normally right?? but I was in a similar situation with an alcatel I dug and dug and on Qualcoms dev site and I dont wanna search for it because it would probably take a month to locate the web site said with instructions to change the name of your ROM file to a file name with just 7 numbers not matching... I used 8675309 and it worked...my jaw dropped and I had fastboot
Do a search in here for the ZTE DFU MultiDL A2017X tool.
I bricked my N9560 and it puts it into EDL mode.
Related
I am with ATT and i have had the IMEI registered with them for the phone. I verified the APN but when i connect with ATT it lets me on the 3g network for about 1 minute then drops me completely. I have read hear to use the fix for the ZP0810 so i got the tools and i have the connection the problem comes from when i am following the directions. I cant get it to ever enter the root mode. It says i have root access but all it does is sit the goophone splash screen. the tools i am using come from this spot (http://forum.xda-developers.com/showthread.php?t=2174075) but the database came from another section on here.
I know i am not being very descriptive but i am not a developer and I am more upset about the phone not working it was a present for the wife and it has been a nightmare for me. so any help you can give me would be great.
If i have to buy a new ROM for it i will. I would just need better instructions Tools, Steps and verifications required on my part. I am a mechanic and i know hammers and saws better then ROM's
I appreciate it all in advance if you need more info or pictures or what i am using right now please let me know.
update i have tried the tools given researched them and all but when i go to do the update using the attachement that i have attached and followed the youtube example but i am stuck and truly need some help. I got the tools to run but when i set the tool to connect to smartphone in meta then remove the battery and reinstall and click reconnect i get nothing but the Goophone splash it doesnt progress any further. I have been doing this now for 2 weeks total and have read extensively about how to do it and i feel confident i can do it now if i can figure out what is going on with not going past the splash screen.
I am using window 7 64 bit and i have to run the tools as windows xp sp3 in order to not get a mem error. So any suggestions would be helpful thank you
this is the step that is stopping me from applying the fix
"Then remove the mobile phone battery and reinstall ,click to Reconnect,charger mobile phone through link
to the USB"
hi,
can your phone actually bootup now?
have you tried reflash to diff rom?
i am not in us, so no idea, but reflashing is not difficult. i brick my phone in less than a day and recover it within few hours of reading as well.
Try flashtools
Hi everyone ! I am new to forum, so please forgive me if I post into the wrong category .
I have a very big problem with my phone (LG L3 Optimus E400) . I have installed a lot of custom roms on it and yesterday I realized that the current rom I was using doesn't receive text messages so I decided to try antoher one and I had the "great" idea to Flash v20 Baseband for flashing SlimBeane610 rom. That was very silly. After I flashed the rom, I rebooted my phone and nothing happened, screen is black all the time. When I press the power button the phone vibrates and the back and menu buttons lights up for 1 second like normal log on, then boom, all goes black again and if I don't remove the battery and I press the power button or any combination (like Reset, Emergency mode) doesn't work. I googled everything, I found something on this forum but not very useful. I tried wit adb but my phone isn't on so it can't be recognized. I tried wit KDZ Updater (until the phone was recognized) but I get a error like WParam: 100 and LParam: 500. When I connect it with USB sounds are playing like normal and Mobogenie wants to connect with it but I can't enable USB Debugging so it's pissing me off . If I can enable USB Debuggins from PC somehow, maybe I can connect phone with Mobogenie and make a restore , a backup or flash another rom, it would be easy If I can go into recovery or emergency mode but I can't . If it would exist a software that can erase everything on the phone when the it's turned off ... .I tried with LG TOOLS, LG PC SUITE IV, LG FLASH TOOLS, Android MULTI TOOLS and nothing(i have the latest drivers installed). Can I make something to it using the external_sd (like put a flash into it, connect it through PC via USB cable and try to flash a rom from command prompt but I don't know the paths). This is a very hard problem, I have a bricked L3 and I don't know hot to unbrick, I think isn't only a soft problem, maybe I should do something with its hardware ? If anyone could help I would really appreciate .
Thanks in advance !
PS : I won't be able to follow this conversation until the next week because I am going to "Primitive Age" right now...oh God, I'm only good to smash things . :crying:
PodGom said:
The most important thing is, can you see the LG logo that shows up in normal boot? If you don't, it'd be either a screen problem or a hard brick. Nobody except LG can fix these problems, and you would have to pay LG some money to fix the phone. But if you DO see the LG logo and your phone stops, you can try the below options.
It just may be bricked, and you could try getting into recovery and flash an alternative ROM. But if that doesn't work, tryLG mobile support tools to get it back to its stock firmware. Good Luck!
Click to expand...
Click to collapse
No, I can't see the LG logo . If I could saw the LG screen was very easy to fix it. I think the phone it's really dead and I also think that even an authorized service can't fix it . Do you know an approximately price for fixing this issue ? Thanks .
Hi,
You should definitely ask the experts who own your device for help, Here...
http://forum.xda-developers.com/optimus-l3-l5-l7/help
Good luck!
Thank you. Thread closed.
Hello there everyone, i need some help to put Marshmallow on my Phone. I had tried to install it on a my phone which boot-loader is locked and i got a message saying
"System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. "
I shut down the phone and booted my phone with volume down/home/power key and when its that download mode or something page. I hit continue and i was able to access my phone again. Since then, i cannot boot into recovery mode anymore, it gives me that "System software not authorized by Verizon Wireless has been found on your phone" message and i don't know what to do.
I want to get Marshmallow on my phone, with the ROM for he Samsung UI thing since i don't like plain android. (dunno if that possible, sorry if i sound stupid)
Can someone provide me baby steps to get it. Thanks you alot.
Elisha Fernanades said:
Hello there everyone, i need some help to put Marshmallow on my Phone. I had tried to install it on a my phone which boot-loader is locked and i got a message saying
"System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. "
I shut down the phone and booted my phone with volume down/home/power key and when its that download mode or something page. I hit continue and i was able to access my phone again. Since then, i cannot boot into recovery mode anymore, it gives me that "System software not authorized by Verizon Wireless has been found on your phone" message and i don't know what to do.
I want to get Marshmallow on my phone, with the ROM for he Samsung UI thing since i don't like plain android. (dunno if that possible, sorry if i sound stupid)
Can someone provide me baby steps to get it. Thanks you alot.
Click to expand...
Click to collapse
Hi there, I'd love to help but you did not specify what version of Android you were running prior to getting a bricked device. However a general method would by flashing the stock ROM of the phone via Odin(I'm assuming its a Samsung device). Search for "unlock bricked Samsung SCH-1535" using the search tool. As for the marshmallow UI, this can only be achieved if you've re rooted your device and unlocked your bootloader in other to be able to flash ROMs with marshmallow UI. Alternately you'll have to edit the build.prop file located in the /system folder in the root directory of the device in question. This procedure also will require a rooted device. You can search around for forums that describe how this can be done on your specific device. Goodluck mate:fingers-crossed::fingers-crossed::fingers-crossed:
Ok, i have a doogee x5 pro phone and i tried to root it by flashing twrp recovery using sp flash tools. While flashing i got the error "PMT Changed for the rom it must be download". So i did a small research on internet and i found out that i needed to format everything except bootloader. This succeded. So after that i tried to install the firmware with this succeding to. Unfortunately the time i tried to turn phone on it was dead. SP Flash Tools wont detect it anymore. Please help me cause the phone is not mine and its brand new! I can rate my self as moderate android user. :crying:
i think i have a bigger problem... I downloaded a stock rom for doogee max pro(cause i just realised it wasnt just pro it was max pro) and it didnt seem to be recognised again. Any help would be appreciated. I constantly keep trying to raise it from the deads. Thanks!
Ap0s said:
i think i have a bigger problem... I downloaded a stock rom for doogee max pro(cause i just realised it wasnt just pro it was max pro) and it didnt seem to be recognised again. Any help would be appreciated. I constantly keep trying to raise it from the deads. Thanks!
Click to expand...
Click to collapse
On mtk devices a preloader is independently installed, it should be almost impossible to destroy, I owned a x5 pro and had best success to flash it with sp flash by taking out the battery, press flash button and plug it in...
The second huge issue I see is when you used the specific flash tool format option you very, very likely killed the nvram partition which contained the imei, so you'll have to fix this too by generating a new one and using mtk engineer mode which is well described and to find on Google..
But let's go step by step. Check without battery, or if it's a non replaceable you'll need find the reset button..
i have tried before without battery and i tried just now but nothing. Its very weird it was detected before and now no in same and another machine. I am pretty confused and stressed. Hope i didnt do any physical damage.. :crying:. THANKS!
starting to get pretty stressed omg! and is there a difference between MT6737M and MT6737?
i came to the point im starting to lose my mind... tried everything i could, i have 5 days left to repair this phone and i dont wanna pay 85 euros for this. SP Flash Tools wont detect the phone. Tried almost 5 different scatter files,2 different PCs and different mtk drivers. Im losing my mind already
UPDATE: I almost fixed it! I had flashed wrong preloader so phone wasn't recognized by SP Flash Tool. I fixed preloaded with a little trick from here: link. After that i flashed stock rom downloaded from doogee.cc but phone will not boot resulting in a total black screen. When i hot Power + Vol Up it takes me to another screen:
Select Boot Mode:
Recovery
Bootloader
Normal
Doesn't matter which boot mode i choose i just get a total black screen which means i get nothing. Idk what is happening! Any further help would be appreciated! I constantly try to bring it back working with little success and small improvements.
Last UPDATE: FIXED my phone had no juice left inside so couldnt complete boot proccess. Now its all good running Btw someone must pin this META trick link i send on my previous post cause im sure more people out there have preloader issues!!! Thank you everyone!!
Sam Nakamura said:
On mtk devices a preloader is independently installed, it should be almost impossible to destroy, I owned a x5 pro and had best success to flash it with sp flash by taking out the battery, press flash button and plug it in...
The second huge issue I see is when you used the specific flash tool format option you very, very likely killed the nvram partition which contained the imei, so you'll have to fix this too by generating a new one and using mtk engineer mode which is well described and to find on Google..
But let's go step by step. Check without battery, or if it's a non replaceable you'll need find the reset button..
Click to expand...
Click to collapse
And yes i couldnt flash it with battery only with!
Galaxy S7 SM-G930 RZDA I guess is soft bricked, A buddy brought it to me.
It was originally a USA US CELLULAR Variant. I used my Z3X Box to unlock it, perfect turned out great.
he asked why the USC bootimg and bloatware ETC was still on it. I told him just because u unlock it doesn't mean it'll pop
up AT&T with just the change of a sim.
So then I De-brand it with the combo file-
COMBINATION_FA60_G930AUCU4APL2-VIA ODIN 3.12.3
and again perfect like a brand new phone.
now I'm all self taught learned on my own.
I just like to read before I act and screw something up.
so here's where I'm stuck, he brought it back wanting to know what root,twrp, etc meant.
I told him I know those things and how to do it but be patient give me some time to read into it I heard there is a lot of
complications with s7 at&t model as far as root and twrp and so on. well now he sold it to me cause he couldn't wait and took it else where here the problem.
The Phone only boots to a screen with the message.
SBL Error!
Set CP DEBUG
rdx_init!
skip print_summary_to_lcd..
(With an android img In the center screen with SBL ERROR UPLOAD MODE. beside it.)
With No Download Mode VOL-/HOME/ POWER attempt multiple times and screen goes black and comes straight back to the sbl error upload mode screen.
No Recovery Mode- when I press VOL+/HOME/POWER I get the message.
Set CP DEBUG
IDOQ : G(40), S(12) mA
CPU SERIAL NUM : 0xd43d9324
Fused open loop voltage: 1010mV
Cannot Check RPMB PROVISIONING [-1]
RECOVERY BOOTING....
It also isn't detected by adb drivers on hp laptop win 10 64bit/ or the z3x box its only picked up as a comm port.
shows up as a modem and in devices and printers its listed as MSM8996.
Odin picks it up but will not flash either it stays on setup connection or straight to fail.
Plz and thanks for any help this is my first poist just need a little direction on postings and on this problem I'm beat. thanks again
ok nevermind cant figure out how to add a pic to the post lol help again?
hoss87 said:
Galaxy S7 SM-G930 RZDA I guess is soft bricked, A buddy brought it to me.
It was originally a USA US CELLULAR Variant. I used my Z3X Box to unlock it, perfect turned out great.
he asked why the USC bootimg and bloatware ETC was still on it. I told him just because u unlock it doesn't mean it'll pop
up AT&T with just the change of a sim.
So then I De-brand it with the combo file-
COMBINATION_FA60_G930AUCU4APL2-VIA ODIN 3.12.3
and again perfect like a brand new phone.
now I'm all self taught learned on my own.
I just like to read before I act and screw something up.
so here's where I'm stuck, he brought it back wanting to know what root,twrp, etc meant.
I told him I know those things and how to do it but be patient give me some time to read into it I heard there is a lot of
complications with s7 at&t model as far as root and twrp and so on. well now he sold it to me cause he couldn't wait and took it else where here the problem.
The Phone only boots to a screen with the message.
SBL Error!
Set CP DEBUG
rdx_init!
skip print_summary_to_lcd..
(With an android img In the center screen with SBL ERROR UPLOAD MODE. beside it.)
With No Download Mode VOL-/HOME/ POWER attempt multiple times and screen goes black and comes straight back to the sbl error upload mode screen.
No Recovery Mode- when I press VOL+/HOME/POWER I get the message.
Set CP DEBUG
IDOQ : G(40), S(12) mA
CPU SERIAL NUM : 0xd43d9324
Fused open loop voltage: 1010mV
Cannot Check RPMB PROVISIONING [-1]
RECOVERY BOOTING....
It also isn't detected by adb drivers on hp laptop win 10 64bit/ or the z3x box its only picked up as a comm port.
shows up as a modem and in devices and printers its listed as MSM8996.
Odin picks it up but will not flash either it stays on setup connection or straight to fail.
Plz and thanks for any help this is my first poist just need a little direction on postings and on this problem I'm beat. thanks again
ok nevermind cant figure out how to add a pic to the post lol help again?
Click to expand...
Click to collapse
Did you ever find your fix?
I'm exactly in the same situation. Nothing that I know help me to get out of this sbl error screen. And nothing that I've found online was usefull (and I've searched each day during 1 week in every reachable sites in many different languages). Except this method that I've seen on a couple of forums and I didn't tried it yet:
mathewfb1907 said:
hi bro help pls
If for some reason it doesn't work, then try to create an emergency scdard from an identical model with identical firmware version as your broken one, root it by eng-boot, read out the first 1GB of the "sda" partition, write the dump to a fast class U1/U10 32GB sdcard using Win32Disk, insert the card into the sdcard slot and power it up while holding Vol Down + Home + Power. If everything was done correctly, the phone should boot into download mode, then just flash the latest full stock to fix it.
To create an emergency sdcard for Qualcomm based G930/G935:
adb shell
su
dd if=/dev/block/sda of=/storage/emulated/emergency.bin bs=1024 count=131072
exit
adb pull /storage/emulated/emergency.bin
g930a-v models same sda flash
Click to expand...
Click to collapse
Do you find a solution?