Related
Hello,
I have problem with my SGS I9000. When I am trying to turn on my phone, I can see only SAMSUNG boot screen blinking again and again. I am NOT able to run recovery mode or download mode (it's strange for me). And what is strange, when phone is turned off and I will plug in battery charger, there is only "spinning" circle.
I know there are threads regarding this problem but other users were able to run download mode, but I am NOT :-(
Thanks to everyone for any answers.
skipper_nb said:
Hello,
I have problem with my SGS I9000. When I am trying to turn on my phone, I can see only SAMSUNG boot screen blinking again and again. I am NOT able to run recovery mode or download mode (it's strange for me). And what is strange, when phone is turned off and I will plug in battery charger, there is only "spinning" circle.
I know there are threads regarding this problem but other users were able to run download mode, but I am NOT :-(
Thanks to everyone for any answers.
Click to expand...
Click to collapse
Have you been able to get into download mode previously? If not it's probably not enabled.
The best approach is probably to make/buy a USB jig. Check ebay.
I was able to run download mode before. Yes, thank you, I already found out how to create jig and I made it.
So pls close this post and sorry.
My galaxy s was hanging on boot (at the big S logo). This wasn't the first time and last time I had tried everything and reflashed. Yet this time odin crashed (windows gave me the 'Odin.exe stopped working' notification) and my phone powered off...
Now it won't give me anything, not download mode, OS or recovery (screen stays black, not even sure if the phone boots at all, hardware buttons also stay off)
Couldn't find anything usefull, any thoughts?
Cheers
Try the JIG to force it into download mode and try again. If odin crashes again, try flashin within windows safe mode. Sometimes it prevents crashing
mrjraider said:
Try the JIG to force it into download mode and try again. If odin crashes again, try flashin within windows safe mode. Sometimes it prevents crashing
Click to expand...
Click to collapse
Will that force the device to boot too? If thats true I will give it a shot this week, hopefully. See if i can get hold of one somewhere.
Thanks for the quick reply
tinyhitman said:
my phone powered off...
Click to expand...
Click to collapse
I Think this is the problem, you may have tried flashing when you had little battery charge and that will cause serious problems as bootloader would have failed.
your only option would be read the My Android Solutions about Problem:- Cannot enter Download or Recovery Mode
xsenman said:
I Think this is the problem, you may have tried flashing when you had little battery charge and that will cause serious problems as bootloader would have failed.
your only option would be read the My Android Solutions about Problem:- Cannot enter Download or Recovery Mode
Click to expand...
Click to collapse
EDIT: I thought it was weird indeed that my phone powered off, since it had a full/near full battery (at least it told me)
Great thread ! Yet unfortunately none of the steps work for me up untill the JIG, I'll have to get hold onto one or make a homemade one (only got a single micro-usb at the moment, so that'll be a sacrifice) Havn't really got a lot of time on my hands but eventually i'll have to give the JIG a shot.
Realize that it seems like the phone isn't powered at all.
EDIT: no "usb device detected" notifications/sounds in windows when plugged in (for adb)
Also: My volt-o-meter told me that my battery outputted 6+ volts... can't seem to reproduce at the time of writing this though....
tinyhitman said:
EDIT: no "usb device detected" notifications/sounds in windows when plugged in (for adb)
Click to expand...
Click to collapse
could be a USB cable failure (guessing) try
2) Problem:- Cannot connect to PC or Unknown Device, getting Code 43 or any other code or NO response when using USB cable in My Android Solutions
did you tried to remove the battery several seconds holding down the powerbutton and put it back again?
btw i also had issues with a galaxy note and a broken usb cable. screen was black because of an empty battery, you should try an other battery maybe a friends one
I'm in a real pickle here...
My phone is bricked and I found all the resources for that already.
However, when I go to flash the firmware on the phone to bring it back to stock it's not allowing me to do it because the battery is at 4%.
I go to charge the phone a it forces itself into bootloops and doesn't charge.
I can get into recovery (CWM--which bricked the phone...likely my fault) but phone doesn't charge there.
I can get into download mode but it doesn't charge there.
WTF is going on!?!?
How can I charge my phone at this point...unfortunately, the battery isn't removable.
Can you flash a custom rom through adb sideload?
datechnerd said:
Can you flash a custom rom through adb sideload?
Click to expand...
Click to collapse
Edit: No, I'm unable to establish an ADB connection in Recovery to do this. I'd actually tried this already with a stock rom. Thanks though.
Flashing the Cyanogen ROM is what bricked the phone. I'm not able to establish an ADB Connection from Recovery (ClockworksMod) so I'm not able to flash anything in Sideload.
Here's the "Boot-Loop":
Power on (vibrate)
LG logo
"Source Booting Unsuccessful"
"Cause: (blank)"
And it just loops like that any time it's plugged in and not in Recovery/Download modes (which also don't charge).
I've tried a factory reset but that didn't change anything. I also tried restoring my original backup image but that doesn't work either.
Currently I'm trying this:
http://forum.xda-developers.com/showthread.php?p=48874488&posted=1#post48874488
This is where I get the failure to flash because of 4% battery.
Only other option I haven't tried yet is to boot into Ubuntu and restore files there and I'm avoiding that for now because I'm at my parents house and don't have burnable DVDs so it's going to be a pain in the ass.
for ubuntu couldn't you do a virtual machine, or live boot from a flashdrive?
datechnerd said:
for ubuntu couldn't you do a virtual machine, or live boot from a flashdrive?
Click to expand...
Click to collapse
I'd do a live CD/USB but they don't have the equipment so I need to go out and buy it (DVD-R is still cheap and so are USB drives) but they're not located very close to any stores
Same issue
Hey man i had the same issue as you and i just plugged it into the wall charger it will charge the phone it will just boot loop a bunch just leave it plugged in for about 30 minutes and try again that worked for me
tim45244 said:
Hey man i had the same issue as you and i just plugged it into the wall charger it will charge the phone it will just boot loop a bunch just leave it plugged in for about 30 minutes and try again that worked for me
Click to expand...
Click to collapse
Thanks a lot. I'll give that a try.
This happened to me too and i dont know what to do if you fixed it help me!
Just an idea. Download an Alternative recovery with charge function. Flash it via ur working recovery from usb otg drive if u have one and reboot to it. Then charge ur phone back to life
Just a thought but maybe you can use an external charger for the battery
had same issue,got bootlopp and baterry dead,can run to download mode but battery dead.everytime gi charge the battery it won't charge just bootloop again.help me too pleaseeee
it wont work for me.i charge it more than an hour but still readed "B0" in download mode thats mean i have 0 battery percent so i can't continueing to flash the phone,please help how to i charge the phone when everythime i charge it on the wall or pc,it will start bootloop again n again without charging the phone.my battery is now at 0% can't do anything
If you can go in cwm, flash twrp from usb and charge your phone in recovery.
Dear friends, anybody has found a solution? I'm on the same situation. If I disassemble my phone, will I be able to charge somehow?
Hi everyone, I know it's been many years but do we have any updates on this? Thank you
Hey guys,
Guess today it was my turn ****ing up.
I apparently have completely bricked my Axon 7 after trying to go from LOS 15.1 to stock oreo beta. The only thing I seem to be able to boot to is DFU mode and for some reason, if I press the Power button + Vol Down I will get stuck on the ZTE Logo and my PC will detect my phone through the ADB interface but every time I try doing something it says my device is unauthorized. Is there any way I can authorize the device whilst being completely bricked?
The only other thing I get is the unlocked bootloader warning screen. If I don't press anything the phone will be stuck there, if I select recovery the phone will simply shut down and anything else will result in a reboot. I have also tried a deep flash cable that that only results on the phone being stuck at the unlocked bootloader screen.
I cannot access the bootloader,
I cannot access EDL mode
I can access ADB, but device shows as unauthorized.
I can access DFU mode.
Any suggestions would be appreciated. I have looked at the Hard brick guide that involves taking the phone apart but that's not something I really want to do.
Thanks in advance.
Edit: My phone gets detected by MiFlash but every time I try flashing I get a cannot receive hello packet and object reference not set to an instance of an object.
ZTE axon 7 EDL tool detects it in ADB mode but says ERROR! NO ANSWER FROM PHONE!. Possibly since its not authorized with ADB.
Ouh....DFU? I think this thing is totally bricked.
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Victor13f said:
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Click to expand...
Click to collapse
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
raystef66 said:
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
Click to expand...
Click to collapse
Thank you for your help . It's a risk you take when flashing phones.
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
stinka318 said:
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
Click to expand...
Click to collapse
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Victor13f said:
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Click to expand...
Click to collapse
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
stinka318 said:
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
Click to expand...
Click to collapse
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Victor13f said:
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Click to expand...
Click to collapse
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Choose an username... said:
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Click to expand...
Click to collapse
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Victor13f said:
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Click to expand...
Click to collapse
In that case you can just pretend that the phone got in that state by itself, it's not too morally correct but some people here pulled it off...
twice now i have gotten an axon 7 into this state. while mine have been a2017u models, i dont know that they are different than yours in that regard.
What worked for me the first time was letting the phone completely die. Being unable to boot into anything, it was somewhat a task to actually make it die, so i kept powering it on (which merely made the red led indicator come on). i did this over and over again over the course of a day at work whenever i noticed it had powered off.
eventually, the phone had no response at all. then, i plugged it up to my laptop, and left it, convinced i had killed it. a dialogue popped up after a minute or two on the phone screen saying to charge the phone by plugging it up. i had no access to fastboot or EDL mode prior. once i got that 'plug in to charge' screen, i switched it to the wall charger, and left it to charge a bit (50-60%) from that state, then, i unplugged it again, and somehow, i managed to get edl mode to work by unplugging it and pressing all three buttons and holding them (typical edl boot).
once there, i reflashed via MiFlash an earlier build. i rolled back using MiFlash as far back as i could. in the process, i lost my imei and serial, which i have yet to successfully recover, but i did get out of DFU pergatory. the imei thing seems to be caused by going back to MM which i did on both of my IMEI-less a2017u boards, but im only guessing. my dd axon 7 is the only one of the three boards with imei and serial, so maybe MM is a bad idea. lol.
The first time i recovered from DFU, i did it inadvertently by letting the phone die and then flashing in EDL mode as well. (i left it for a few weeks as i had given up on it.) after it died completely, and i plugged ut up to the computer and had the same experience, I flashed the beta oreo build for a2017 using miflash. the screen had stopped responding. and i ended up doing a RMA. I now know the screen response thing was bc of a faulty EDL file of B15. (happened again to another of my axon, so i retraced my steps and realized it was when i flashed b15 that it died) . the fix if your screen ever stops responding, but isnt physically damaged? re-flash via EDL a different file. it may take a few tries, but eventually a build will work. for me, it was Marshmallow. I still do not know for certain, but that possibly is what killed my IMEI. but hey, it boots and the screen works.
I genuinely hope posting my idiocy in toying with axon 7s has helped someone out there.
Hello, I turned on my phone this morning as usual however was instead presented into a Factory Test Mode, has happened for the first time. I then long pressed the power button but still no luck, after trying every combination possible I gave up. I charged the phone last night at 100% and turned it off as usual. (On stock rom, Oreo 8.0 not rooted or anything. - A2017GV1.3.0B03 ) Also, don't really want to disassemble or reset my phone. Any help would be much appreiated. Thanks!
owerevoke said:
Hello, I turned on my phone this morning as usual however was instead presented into a Factory Test Mode, has happened for the first time. I then long pressed the power button but still no luck, after trying every combination possible I gave up. I charged the phone last night at 100% and turned it off as usual. (On stock rom, Oreo 8.0 not rooted or anything. - A2017GV1.3.0B03 ) Also, don't really want to disassemble or reset my phone. Any help would be much appreiated. Thanks!
Click to expand...
Click to collapse
what is "long pressed"? You have to hold it for about a minute or so, did you?
If it doesn't work, FTM mode has ADB, so you should be able to hook it up to a PC and issue "adb reboot" from the terminal. If you end up in FTM again then your phone is just borked or something, you can attempt to fix it by using "adb reboot recovery" instead and reflash stuff
Choose an username... said:
what is "long pressed"? You have to hold it for about a minute or so, did you?
If it doesn't work, FTM mode has ADB, so you should be able to hook it up to a PC and issue "adb reboot" from the terminal. If you end up in FTM again then your phone is just borked or something, you can attempt to fix it by using "adb reboot recovery" instead and reflash stuff
Click to expand...
Click to collapse
Thanks, adb reboot solved it! Can't thank you enough!
Same case to me on OreoB03. Power button long pressed didn't respond. I used "minimal_adb_fastboot_1.4.1_portable" and command reboot.
svsavic said:
Same case to me on OreoB03. Power button long pressed didn't respond. I used "minimal_adb_fastboot_1.4.1_portable" and command reboot.
Click to expand...
Click to collapse
Same problem here.
But i do not know how to use ADB tool.
I dowloaded minimal adb fastboot tool and i have now 3 executable (adb, fastboot, MAF32) in a directory but I do not know how to use them in order to reboot my Axon 7.
I would appreciate a step by step guide, made for a very beginner.
Note also that I may not have already the device drivers on my computer.
Find cmd.exe in syistem32, run as administrator, drag adb.exe in cmd window. Write command adb reboot.
Impossible for me.
I am not even able to have the phone recognized since the drivers are not correctly installed and Zadig tools wont help.
I'm really stuck.
Would any Belgian Guys be able to help me having a computer with adb WinUSB drivers correctly installed so that we can reboot my phone with his PC with any adb tool ? Please PM me is so.
Phone is recognized as adb device (w/o driver). Just try this and write command adb reboot or reboot (i don't remember).
It is said that no devices is found.
?
Also had the same FTM problem and can confirm that power button did not work in stock Oreo.
If can't get adb reboot work, one simple way is to discharge the phone - USB type C connection is fully working in FTM mode (u can simply check that). Connect one or few (use simple usb spliter) USB devices (the best way is to connect devices, for example power bank, some bluetooth speaker, which actually suck energy etc.) to your phone in order to charge them and it will fully discharge the phone in a few hours. Then on phone turned off connect power charger, wait about 15-20 minutes to charge and turn on the phone as usual (using only power button for a few seconds).
Hello, i actually thought about this option of waiting for the battery to be discharged but did not dare to take the risk. I finally found someone that will "adb reboot" my phone tomorrow, fingers crossed.
Hi,
OK, let's hope that "adb reboot" option will succeed.
However, personally I see no risks in discharging the battery - when the phone discharges it just safely automatically turns off - no data loss, no need to reflash the ROM etc. I went through this route myself.
I think it could be another bigger risk to keep the screen on (not moving screen) for a longer time - possible burn in of screen etc. But not sure about this risk and don't want to frighten, maybe others have more knowledge on possible screen burn in issues. In my case after discharging the battery no burn in or other screen problems.
I ordered a OTG cable that should arrive tomorrow to discharge the phone if adb reboot does not work. Thank you for ur feedback.
Have you tried this tool to get to EDL and then you can use Miflash to flash back to stock https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
billjim24 said:
Have you tried this tool to get to EDL and then you can use Miflash to flash back to stock https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
Click to expand...
Click to collapse
that's not remotely useful to the situation
please read up before posting lmao
Mine Axon 7 did just that, couldn't turn it off in any way, also on b03 Oreo rom. So I let it discharge completely, and just did a normal power on, and it worked again.
I think that the Oreo Rom is in an awfully bad beta Rom rushed out from a sinking mobile company, that don't give a s... about their customers.
Will never buy ZTE again.
A friend could reboot mine with adb reboot. Problem solved.
I guess adb drivers did not worked well on m'y computer.
Next thing to do : downgrade to Nougat in order to get Daydream. What a shame.
Chinesur said:
A friend could reboot mine with adb reboot. Problem solved.
I guess adb drivers did not worked well on m'y computer.
Next thing to do : downgrade to Nougat in order to get Daydream. What a shame.
Click to expand...
Click to collapse
G B03 has daydream, hasn't it?
No, it doesn't have
Boot in FTM,open axon7toolkit,connect phone to laptop and follow instructions in axon7toolkit.It will reboot in edl and you can flash a firmware