well, i just flashed the DFHKT_U_4.5.2-109_DHT-22-23 over DEFYPLUS_U3_4.5.1-134_DFP-137, yes, i know, BIG MISTAKE, the DFP-137 was with other name when i flashed it for the first time, now the phone doesn't boot and charge, its practicably dead, what can i do?
Edit: sorry for the title, I tried to say, it does not load or boot.
Edit2:fixed, just had to turn it on like flash a new sbf, then connect to a pc and start flashing another one.
Uf...
Solution
Bleak3993 said:
well, i just flashed the DFHKT_U_4.5.2-109_DHT-22-23 over DEFYPLUS_U3_4.5.1-134_DFP-137, yes, i know, BIG MISTAKE, the DFP-137 was with other name when i flashed it for the first time, now the phone doesn't boot and charge, its practicably dead, what can i do?
Edit: sorry for the title, I tried to say, it does not load or boot.
Edit2:fixed, just had to turn it on like flash a new sbf, then connect to a pc and start flashing another one.
Uf...
Click to expand...
Click to collapse
Hello, I try to help, in this case you have to get a SFB / original Flash file your operator, hence try to turn the phone into bootloader mode (ON button while the volume button (Vol-+) to same time, hence the contectas to computer with RSD Lite and flash it so
WARNING
MUST BE WITH YOUR OPERATING SYSTEM OPERATOR MOBILE HOME AS PACKAGE CAME AS Failure to do so may become unusable PERMANENTLY (an example is putting on the SFB of another operator, or other model)
If you have questions contact me via Facebook, is in my profile page
If I helped you, give thanks
Please ask all questions in the Q&A section. Thread moved there.
Related
Hello all,
my Motorola Defy does not boot, only white light appears at top when connected to PC through USB cable. This happened after I flashed the device with UK version of .sfb file (mediafire link from http://www.simply-android.com/discussion/593/how-to-unbrick-or-flash-a-defy-firmware.sbf/p1).
Since then, I tried many .sfb files to flash my device but none of them made the phone boot. After second flash, PC wouldn't recognize the device without using MCGyver's battery fix (http://forum.xda-developers.com/showthread.php?p=10600303#post10600303).
I think my problem is described in this thread (http://forum.xda-developers.com/showthread.php?t=938708), although the link to T-mo Froyo ROM is broken.
I appreciate all the help and attention to this problem.
I think you have flashed an eclair-sbf on a froyo-defy.
After flashing your device boots in a black screen?
Choose the right froyo-sbf,
charge your battery before flashing external.
make if possible a factoryreset.
flash this froyo-sbf, its the retail british.
http://sbf.droid-developers.org/umt...JRDNFRYORTGB_P019_A010_HWp3_Service1FF.sbf.gz
Questions go in the Q&A section
Problem solved
Thanks RATTAR, you saved my phone It now boots with red Motorola logo into Android 2.2
Hello!
I read for hour now, bot no luck
I flashed my x10a with flashtool with generic rom.
After flash, as the flashtool says, just turned off and on the phone.
But nothing happened(green led blink one and do a sort vibration, thats all..)
no logo, no sound nothing happens.
I tried to reflash again, but windows says: Cannot recognize the device
In the control panel device manager show "unknown device".
Yes, i have the correct drivers(as you can see i flashed before).
Help me guyz, please, if U can
gyurc said:
Hello!
I read for hour now, bot no luck
I flashed my x10a with flashtool with generic rom.
After flash, as the flashtool says, just turned off and on the phone.
But nothing happened(green led blink one and do a sort vibration, thats all..)
no logo, no sound nothing happens.
I tried to reflash again, but windows says: Cannot recognize the device
In the control panel device manager show "unknown device".
Yes, i have the correct drivers(as you can see i flashed before).
Help me guyz, please, if U can
Click to expand...
Click to collapse
Please post in questions and answer section
And also if your phone can go in flash mode then you can easily flash again
It would be better if you download again cause the previous one might have corrupted
You can find links to download in my signature
Sent from my X10
THeLogiC said:
Please post in questions and answer section
And also if your phone can go in flash mode then you can easily flash again
It would be better if you download again cause the previous one might have corrupted
You can find links to download in my signature
Sent from my X10
Click to expand...
Click to collapse
re posted in q&A
hi all i bought defy about a year ago as a second phone from ebay with cm7 installed.last week i purchase another phone and give my 7 years old daughter. however i reset everything and phone turn old version blur mod then stuck on m logo i download rom and sort the problem.
real problem starts now i try to install cm 9 download all required files wiped the phone and install the rom however it didn't restart stuck on black screen and only white led when connected with usb also didn't connect or recognized by rds lite.I found tread battery wake up from i think was ''mggrager'' or something else finally rds recognized the phone and install another sbf but still stays same as black screen and white.i read so many threats on this side or others and each i installed custom roms without clearing cache
battery replaced with replacement battery also original
all drivers installed
it doesn't respond any buttons or usb connection
rds only with battery jump
please help what to do
I'm having the same problem as you are, i believe... I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport... I take my phone home, not really giving it much importance, and i noticed it would never charge and/or turn on, and that when I connect it to the pc, nothing happened other than the white led coming on.. RSD won't recognized it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
I don't know if i should make a thread of my own.. i think we have the same problem, and i REALLY need my phone back.. so i guess we could just help each other fixing it somehow....
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOLA_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
i already tried several times this method however no luck i am really not sure what to do any more i think only option try to find latest rom or first rom then try again if any luck will update and give the links
pasha543 said:
i already tried several times this method however no luck i am really not sure what to do any more i think only option try to find latest rom or first rom then try again if any luck will update and give the links
Click to expand...
Click to collapse
bump 4 help
Ok...
Somehow i managed to reach a point where my device does not boot when i press the power botton...
Unless i connect it to a usb or a power and then it starts and even goes to the android but loops...
If i disconnect it from the cable it just dies...
Any ideas?
10xs.
mirzanoshin said:
Which model of phone you are using?
Click to expand...
Click to collapse
S4 galaxy i9500
Yes... It happened after i tried to update a firmware to lollilop...
After it happened i tried to fix PIT with a stock rom...
Now it turns on while connected to a usb shows the galxy logo and then reboots...
If disconnected from usb or power it just dies...
I can access download mode and cwm while connected to usb.
At some moments it even reaches the android system and tries booting but then goes to a reboot loop again.
JacobTodoit said:
Ok...
Somehow i managed to reach a point where my device does not boot when i press the power botton...
Unless i connect it to a usb or a power and then it starts and even goes to the android but loops...
If i disconnect it from the cable it just dies...
Any ideas?
10xs.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. Please provide your device make and model so I can guide you to the correct information and help you need.
Thank you.
What problem did the phone have that prompted you to flash the phone?
Did you perform a factory wipe in stock recovery before booting the newly-flashed stock rom for the first time?
The original problem was that all processes started halting...
I did the wipe to lollilop and then installed a rom... That is when tthe device bricked.
Later i downloaded a firmware which was supposed to be stock firmware and tried flashing it but it didn't help.
No matter what i try it keeps looping without the ability to power on without a usb connection being plugged (pc or power).
I am looking for an original firmware which would contain the files for the bbotloader and other in order to flash again...
Will appreciate any help.
The device was bought in Israel.
Did you try flashing a stock ROM with a pit file?
Hi and thank u for your response.
As far as i know it os a galaxy s4,
Gt-I9500 bought on Israel. Was running the cellphone company' stock version 5.0.1 with base version i9500xxuhhog1.
It started doing some problems after it was lost and found.
The cell company bllocked it and we had to replace the imei.
Then every process we tried to work with, halted.
So we decided to flash a new version and new firmware.
We tried moving to lollilop and cm12 but the dvices got to the point where it is now.
I am sure it is something we did with odin...
But not sure what.
Now the situation is as follows.
The device doesn't boot when pressing on the power button.
For booting we need to plug it to a usb power supply or pc and just go to recovery.
From there we choose the option of reboot system and it boots, but keeps looping.
If at any moment we unplug the ub connection it dies.
Following to some advises i tried getting the stock rom online and found a version i9500xxuhog1.
And a pit file.
I applied them to the device, though nothong changed.
10xs for any help.
Jacob
The_Merovingian said:
Greetings,
Thank you for using XDA Assist. Please provide your device make and model so I can guide you to the correct information and help you need.
Thank you.
Click to expand...
Click to collapse
audit13 said:
Did you try flashing a stock ROM with a pit file?
Click to expand...
Click to collapse
Yes... Several times.
With several different firmwares.
So Odin never finished flashing a stock rom?
You may have to use a jtag service to repair the phone.
(or is it hard brick)
Hi,
A2017G
Started with marshmallow,
Unlocked bootloader
attempted to install Slim7
seemed to work but with some possible errors, (wouldn't sync with google... retrospect I should have looked elsewhere before...)
attempted in install stock rom
using
ZTE_A2017GV1.2.0B04_BootStack_by_tron1.zip
ZTE_A2017GV1.2.0B04_Stock_System_by_tron1.zip
which wouldn't boot
So I tried reinstall Slim7
then stock again,
then, like the noob that I am, I removed twrp with
ZTE_A2017GV1.2.0B04_Full_Stock_Reverter_by_tron1.zip
which installs stock recovery
so, now I have a stock rom that won't boot,
an unlocked bootloader
and stock recovery
Not sure what to do from here
thanks in advance for any assistance.
I can abd sideload and update from SD card, but everything I have fails signature verification.
edit: so frustrating trying to find that 1 zip
Dizzee said:
(or is it hard brick)
Hi,
A2017G
Started with marshmallow,
Unlocked bootloader
attempted to install Slim7
seemed to work but with some possible errors, (wouldn't sync with google... retrospect I should have looked elsewhere before...)
attempted in install stock rom
using
ZTE_A2017GV1.2.0B04_BootStack_by_tron1.zip
ZTE_A2017GV1.2.0B04_Stock_System_by_tron1.zip
which wouldn't boot
So I tried reinstall Slim7
then stock again,
then, like the noob that I am, I removed twrp with
ZTE_A2017GV1.2.0B04_Full_Stock_Reverter_by_tron1.zip
which installs stock recovery
so, now I have a stock rom that won't boot,
an unlocked bootloader
and stock recovery
Not sure what to do from here
thanks in advance for any assistance.
Click to expand...
Click to collapse
Just use MiFlash, that one's guaranteed to work. Read my DFU unbrick guide to know how to use it. Just skip the part where you have to disassemble the phone, since you can get to EDL mode by (with the phone off and the USB cable connected to the PC) holding both volume buttons and inserting the USB-C cable to the phone.
I did read your guide, was, hoping to avoid dismantling it...
I tried pressing all 3 buttons.
Am I understanding the procedure correctly:
[phone switched off] + usb-C cable connected to PC only
MiFlash running at this point??
Hold both volume keys in and in insert Cable to Phone
at this point is the phone supposed to switch on?
At no point am I supposed to press the power button?
fyi: I will try different combinations, is great to have a solution, thank you.
Ah.... ok... so, the phone will display nothing, rely on the sound of PC and/or the device manager check and/or hit refresh on miflash
Fyi to anyone, if you have axon7toolkit installed and thus can't install a second version of MiFlash, open up the toolkit and hit 7 (unlock bootloader) to fire up MiFlash... or just go to C:\XiaoMi\XiaoMiFlash
the FULL_EDL file I have produces a couldn't find script Error when loading into MiFlash
so far when attempting to flash all zips
I have started MiFlash with admin
unzipped FULL_EDL file to a folder in root C:\ and ensured there are no spaces in address.
Every time / Every file produces couldn't find script error when loaded into MiFlash
when I attempt to flash the file it says cannot receive hello packet and then times out with an error
Tried disabling anti-virus/firewall, still same error
upgraded MiFlash to 2017.4.24.0 ( older 2016 is included with axon7toolkit), this removes the couldn't find script error, but still not receiving a hello packet, gunna fiddle with the phone as I'm pretty sure the error is coming from there
YES!
rebooted phone, turned off, restarted into EDL, flashed the stock rom from zte site... is in chinese... but it works. Thank you Thank you
so adventure over, after all that I am back to 6.0.1...
Dizzee said:
I did read your guide, was, hoping to avoid dismantling it...
I tried pressing all 3 buttons.
Am I understanding the procedure correctly:
[phone switched off] + usb-C cable connected to PC only
MiFlash running at this point??
Hold both volume keys in and in insert Cable to Phone
at this point is the phone supposed to switch on?
At no point am I supposed to press the power button?
fyi: I will try different combinations, is great to have a solution, thank you.
Ah.... ok... so, the phone will display nothing, rely on the sound of PC and/or the device manager check and/or hit refresh on miflash
Fyi to anyone, if you have axon7toolkit installed and thus can't install a second version of MiFlash, open up the toolkit and hit 7 (unlock bootloader) to fire up MiFlash... or just go to C:\XiaoMi\XiaoMiFlash
the FULL_EDL file I have produces a couldn't find script Error when loading into MiFlash
so far when attempting to flash all zips
I have started MiFlash with admin
unzipped FULL_EDL file to a folder in root C:\ and ensured there are no spaces in address.
Every time / Every file produces couldn't find script error when loaded into MiFlash
when I attempt to flash the file it says cannot receive hello packet and then times out with an error
Tried disabling anti-virus/firewall, still same error
upgraded MiFlash to 2017.4.24.0 ( older 2016 is included with axon7toolkit), this removes the couldn't find script error, but still not receiving a hello packet, gunna fiddle with the phone as I'm pretty sure the error is coming from there
YES!
rebooted phone, turned off, restarted into EDL, flashed the stock rom from zte site... is in chinese... but it works. Thank you Thank you
so adventure over, after all that I am back to 6.0.1...
Click to expand...
Click to collapse
What? It's in chinese?
Can you tell me the name of the file you used? Do you still have cell signal?
Choose an username... said:
What? It's in chinese?
Can you tell me the name of the file you used? Do you still have cell signal?
Click to expand...
Click to collapse
I got it from here: http://www.ztedevice.com/support
selected:- United Kingdom > Mobile Phone > Axon 7
it offers a file "AXON 7(ZTE A2017G) SD card software package(328540B2634ZTE A2017GV1.0.0B11)"
which hints at being compatible with A2017G... but is A2017V and is chinese, although you can change the language in settings there is still plenty here and there, plus chinese bloatware
and No, I didn't get cell signal.
I've gone back to Marshmellow, I will try again, didn't think it would be so different/difficult... Although wow at MiFlash.
FFS!!!! Relocked bootloader and bricked it!!! there should be a warning!
you gotta laugh,
I am a bit livid, I know the guides come with disclaimers, however, you'd think it would be an obvious important warning to make... DO NOT RELOCK YOUR PHONE.
FFS!
Dizzee said:
FFS!!!! Relocked bootloader and bricked it!!! there should be a warning!
you gotta laugh,
I am a bit livid, I know the guides come with disclaimers, however, you'd think it would be an obvious important warning to make... DO NOT RELOCK YOUR PHONE.
FFS!
Click to expand...
Click to collapse
Good lord...
You probably wiped out both IMEIs, now you relock out of the blue... Go to my DFU unbrick guide and stop doing dumb stuff :silly:
Choose an username... said:
Good lord...
You probably wiped out both IMEIs, now you relock out of the blue... Go to my DFU unbrick guide and stop doing dumb stuff :silly:
Click to expand...
Click to collapse
... after I finally got it working again (thanks for the assist), I thought relocking it was just making it secure again. I been rooting/unrooting and swapping out roms since the galaxy s2, who'd think you can't unlock and relock... I do think there should be warnings as it is too easy a mistake to make... lmao stop doing dumb stuff you start first
My phone is insured so I'm not overly fussed, but others will be less fortunate.
hello everywone...i have a troble to...my phone is A2017GV1.2.0B04 like this in post.
I bay this phone whit broken screen, i change the screen and try sim card but the phone is locked Whit google account... When I try my sim to test microphone, the phone it's work OK, but I unlock google account whit add tools and after that my phone don't have a service.
Phone tells no service or turned off airplane mode...what is not true... I can change the 4g/3g/2g connection to only 3g or something else... Wi-Fi and everything else work great but no service... The phone see what operator is on sim but no service... Somebody to help me please and tell me some tutorials how to fix?
I by this phone from Denmark and now I'm in Serbia... Eny help please
Thanks anyway Dragan
---------- Post added at 08:30 PM ---------- Previous post was at 08:27 PM ----------
Mistake,whit adb tools...