Basically what is now my phone is catch and display the image of "WARNING; BOOTLOADER UNLOCKED" and it restarts constantly, only to arrive there and restart again... like a "bootlop"
GOOGLE SEARCH FOR ALL SOLUTION IN FORUMS IN ENGLISH AND SPANISH, no case ...
Apparently my mistake was to install an official ROM on my device MOTOROLA using fastboot way...
It do not recognize charger or usb, I can enter the bootloader menu (which lets you choose factory normal startup, recovery ... you know which one) but by choosing an option that quickly returns to the same pattern discussed above (I select, and automatically jumps screen "warning, bootloader unlocked" and restarted to reach this constantly ..)
Do not recognize the USB or charger by simple selection, because I could not turn off the phone because they did not respond to any command, even if i use physical buttons, and obviusly i dont have acces to digital buttons...... .
However I can go to the "Fastboot" where would the bootloader menu, and there does not even recognize the charger or usb mode ...
is not recognized by selection, not because my port is broken or something, because I notice it because I could not do anything, IT WAS CONSTANTLY RESET DURING HOURS, overheating to the point it ran out of battery and I connect ... and I get the typical image of charging (battery symbol with 0%) and a second later (1% estimate when loading ...) happens again, without notice or other visually perceptible signal it restarts and does Just what i explain in the beginning ....
it doesnt recognize usb or charger... even when restarting or fastboot or bootloader mode menu NOT ACKNOWLEDGE DECIDES NOT RECOGNIZE IT, THE USB PORT ISNT NOT DAMAGED ...
I wonder if anyone could come up with the solution to have had this problem since I see that I'm the first to commit such stupidity to install an official rom via fastboot .....
And I can not find anyone with the same problem as me, nor the solution, even after having googled quite ..
could anyone tell me more or less to do?
not recognize in any way the usb connection, and the charger all ...
so it seems that the phone is broken? I doubt they can give you something that you can only destroy via software, although it is not impossible ... i didnt did so much, i just install something that i shouldnt.. should be any fix for it, and i must not be the first having this problem!
I hope you can help me, since the phone is relatively new and is to me a shame to pay now AR$4500 (1 usd = 8,50 AR$ ) i live in argentina, third world, thats why the price is high... and why i dont talk english so good, but i really really need help...
or in order to have another decent phone i will need to pay a high amount of money... hope you can help me, i know in this forum you can find very smart and helpfull people, youre my last chance
regards from argentina...
Related
Hai people,
Im new here and i got a problem with my HTC Hero. Ive got it rooted to FroydVillain through this site and it worked fine for quite a while. But since thursday my phone flipped.
My trackball keeps lighted on, whatever i do. My battery runs low in like 6 hours...normally i did a whole day with it.
When i plug the usb cable it doesnt connect to my computer, it only starts powering up the battery. If its connected with my usb cable and i remove the battery the trackball starts flickering instead off burning all the time.
I didnt know what was going on, so i tried to do a nand restore in the root menu. After that i still had problems with the trackball and it still doesnt connect to my pc. Then i tried a factory reset in the root menu, but the problems are still there.
It doesnt let me get into the mobile network settings either. It doesnt find my provider and cant change it, so at the moment my whole phone is useless
Im quite new with this whole rooting thing, so i might have messed it up now? I hope some people know a solution for this. Please dont throw to geeky stuff to me, because i might not understand it
My software settings are this according to the phone:
Firmwareversion: 2.1 update1
Smallbandversion: 63.18.55.06PU_6.35.15.11
Kernel-version: 2.6.29-063c4d24 htc-kernel(at)and18-2 #1
Build number: 3.32.405.2 CL 191507 release-keys
Softwarenumber: 3.32.405.2
Browserversion: webkit 3.1
Any help is welcome! Thanks in advance
I have tried to fix it myself cause i didnt get any responds yet, but without succes. I got it to restart again in the original htc version, and get the setup menu where u can set your country, wifi connection etc...
It doesnt recognize my sim card though, and doesnt find a provider because of that. When its finished with the setup menu its at the 'normal' home screen. But as soon as it turns black as the screen saver i cant get the screen on again.
The trackball also still keeps burning.
I went to my local phone repair point, but they dont do androids :S its for nerds he said -_-
Im getting hopeless...plx could some1 tell me what to do. I want a whole reset off the phone...i dont care losing information on it. But because i cant connect it with my computer i have no idea how to flash a rom on it
Hi guys, i just wanted to unlock my phone's bootloader when my computer was suddenly getting 'blue death'. My phone turned off, I tried to turn it on but nothing happened. After that I found some fixing method like SEUS, Flashtool (installed drivers to recognize my phone..), but im still bricked 'cos none of these programs can recognize my phone. When programs say 'turn off phone - hold back key - plug in usb' i get nothing, i mean i know what is flash mode (with the green led) but i cant get into it. I've tried all buttons on the phone (even combos like - power button & back) but noting. When i plug in the charger the led isnt light. Please help me i want my phone back. - and sorry for my english
Same problem: Hard bricked x10 mini pro
I have exactly the same problem as you.
I have had no success in finding a solution, because the phone cannot enter flash mode. There are absolutely no signs of life in the phone even though bootloader unlock was reported as successful.
Any ideas guys? Or can you recommend a decent, trustworthy repairer?
Cheers
the only one here with any inkling of a solution
if i am not mistaken, the only way to solve this problem is to J-tag your phone.
basically, what that means is you take your phone to a repair shop, they take apart your phone and plug in a chip which enables certain debugging features, and they simply re-flash your phone for you.
however, unless you are willing to buy a J-tag board yourself, you need to pay 20+$CAD for this.
After all, they need to make money too..
I was wondering if I've encountered a common failure mode with my Verizon Galaxy S3 and if there are any possible solutions.
A week before it bricked, the phone was acting rather odd, rebooting itself spontaneously and at random; I didn't really think much of it until the following week. Applications on the phone had been running VERY slow and would often crash or hang; in addition, the phone was rebooting itself several times an hour at this point.
The last reboot hung for a while at the "Samsung Galaxy S3" screen before going to the home screen. At this point I realize there may be something serious going on, so I attempt to SSH into it and retrieve important information off it. Unfortunately, it proved to be too late; login attempts failed with "Argument list too long". A few minutes after my ill-fated attempt to save data, the phone crashed in the app launcher and initiated a reboot again; only this time, the Samsung logo never came up. Since then, I have been unable to power it on, enter recovery, or otherwise get any life out of it.
It's long out of warranty so I'm basically wondering what my options are to revive it and possibly get important info off it. Reinserting the battery does not work and neither does plugging it in. All options to enter recovery or any other sort of mode fails; it essentially acts like there's no battery inside and does nothing. Is this a common failure state for S3 units and is there a known solution? Has anyone ever used JTAG to retrieve information off the storage inside?
WildZontar said:
I was wondering if I've encountered a common failure mode with my Verizon Galaxy S3 and if there are any possible solutions.
A week before it bricked, the phone was acting rather odd, rebooting itself spontaneously and at random; I didn't really think much of it until the following week. Applications on the phone had been running VERY slow and would often crash or hang; in addition, the phone was rebooting itself several times an hour at this point.
The last reboot hung for a while at the "Samsung Galaxy S3" screen before going to the home screen. At this point I realize there may be something serious going on, so I attempt to SSH into it and retrieve important information off it. Unfortunately, it proved to be too late; login attempts failed with "Argument list too long". A few minutes after my ill-fated attempt to save data, the phone crashed in the app launcher and initiated a reboot again; only this time, the Samsung logo never came up. Since then, I have been unable to power it on, enter recovery, or otherwise get any life out of it.
It's long out of warranty so I'm basically wondering what my options are to revive it and possibly get important info off it. Reinserting the battery does not work and neither does plugging it in. All options to enter recovery or any other sort of mode fails; it essentially acts like there's no battery inside and does nothing. Is this a common failure state for S3 units and is there a known solution? Has anyone ever used JTAG to retrieve information off the storage inside?
Click to expand...
Click to collapse
Plug it into your computer, or a wall outlet with the battery out. See if it mounts as a strange drive or the led light flashes for a second.
Oh wow. Yes it does have the red light when I plug it into the wall outlet without battery. Haven't tried the PC as I'm leaving for work and my USB wire is in the car but I'll assume that will work when I try it.
WildZontar said:
Oh wow. Yes it does have the red light when I plug it into the wall outlet without battery. Haven't tried the PC as I'm leaving for work and my USB wire is in the car but I'll assume that will work when I try it.
Click to expand...
Click to collapse
At least it isn't completely fried, this method should work:
http://forum.xda-developers.com/showthread.php?t=2581166
Make sure it has no other sign of life first.
If you were on 4.1 then make sure you don't use a 4.3 file and lock your phone. Might have to do some digging around to find them, but they are around here somewhere.
So, something very weird started happening to my phone. Out of nowhere, about 7 hours ago, it would stop charging whenever it was on, charging only when it was off and connected to my laptop. However, I thought it was just something wrong in the dev options, and I went to change whatever was the USB option to "charge phone". With this, I did accidentally forgot to activate the OEM option, and had to reboot not long after. You can probably see where this is going now.
Now I have a phone that bootloops on the FAP Lock message, and whenever I go to download mode to fix it, my PC just doesn't recognize the Phone. I've tried different USB cables, all of them are only recognized when the phone is shut down. So it isn't a hardware problem, because the Phone actually charges when it's shut down, and it isn't a problem with my USB ports or cables, as anything else I use with it works fine. And the worst part is, I need this phone today for a serious bank matter, and I can't afford to lose any data on it either, there's some very personal important stuff from yesterday that wasn't backed up yet. And keep in mind that paying for it to be fixed is the last option for me, as I can't afford it (besides, I fear they might end up getting the phone in factory reset mode, and I can't lose that data as I said).
Any kind of suggestions on how to get either the PC to recognize the phone, or flashing in a different way that doesn't need the PC to recognize the device? Thanks in advance.
Edit: Whenever I try to connect the phone via USB, it doesn't even make the Windows "USB connected" sound, it's just like it isn't there at all. One time, I got it to show, but it was as a "unrecognized usb device", and I haven't been able to replicate it yet.
Dear all,
from the occasional reboot my Zenfone performed every now in a while (which didn't bother me too much) it now reboots so fast that it usually has not yet booted to the point where I could get data off the device before it reboots again.
As always, the backup is too old and I want to extract some data off the device. Most important are a few KBs worth of text notes. Here come some questions:
- It seems to be a hardware fault. Are there educated guesses what may give me a few last moments with the device to extract data? Heat? Freezing?
- Are there professional data recovery companies dealing with smartphones such that they can extract data from the chips without the phone working?
- As it is a Qualcomm device: Would any access via QDLoader work or would it be as unstable as the rest of the phone?
I appreciate any input. And yes, I know that I didn't backup often enough.
Thanks,
weaker
which rom are you on?
Sorry for the late reply.
I'm on stock ROM with Magisk. In the end when it became worse, I let Magisk restore the images but this definitely seems to be hardware-related. I also did no overclocking and I don't use games on the phone so I think that it is also not a thermal issue.
To keep the interested ones updated how it evolved: The situation is now as follows:
I tried to boot into recovery via fastbooting the TWRP (the one I used many times successfully for my phone) after one of the phone bootings was stable for enough seconds so have ADB contact and go to fastboot mode. I hoped to be able to interact more stabily in the recovery. However, the result was that the phone rebooted (I am unsure if the TWRP transfer was finished before that) and then the charging screen appeared and the charging screen remained constantly on, even when pulling the cable. It didn't react to any keypresses in that state.
I let it drain the battery (which was only a few hours as the screen was always on). Then, I plugged the phone in and it booted normally and was stable for 15 minutes or so, which gave me enough time to save the most important data. Phew.
This session however seemed to be the last farewell. The phone started to bootloop and I switched it off*. Now the phone has always a black off screen and doesn't respond to anything: Pressing (and holding) the power button, also in combination with Vol+ or Vol-. Also plugging a cable to charge doesn't create any reaction.
* switching it off worked the following way: The unlocked bootloader shows that one could press the power button to pause the boot. I can't think of why this might be a useful function in a normal situation. However, in my situation I could pause the boot and after some time it would switch off. That way I could at least break the bootloop.
you will have to boot into qloader to be able to recover your phone...
follow step by step exactly what is mentioned in the below link, ypu should be able to recover your phone :
Here’s how to unbrick Asus ZenFone 6 (Asus 6z) from QDLOADER 9008 mode - PiunikaWeb
Is your Asus ZenFone 6 (Asus 6z) hard-bricked? You can use still flash via QDLOADER 9008 mode to give a new life to your dead handset.
piunikaweb.com
Sorry to be the prick here, but next time post this in Q&A section. This one is for posting development (Kernels and ROMs)
OK, no offense taken. I thought that I would need to resort to some TWRP magic to get data off my device.
@MOD: Feel free to move thread where it fits best.
For the sake of completeness:
The phone is back from RMA. According to the sparse documentation they exchanged the mainboard and battery and some connector. Some firmwares are now newer than on the old mainboard (little surprise here). Bootloader unlock worked also on the new phone (some report that this would not work by default after an RMA, for me it did).
So, ASUS did a great job dealing with the issue.