Here's the problem: I have this XT925 and I wanted to update it to lollipop, so I unlocked the bootloader, rooted it and installed TWRP. I flashed the ROM but when it booted I noticed that Wifi won't turn on and that mobile network showed and error. So I decided to flash stock 4.4.2 ROM to get the correct Modem I needed to flash stock 4.1.2 since stock 4.4.2 hasn't arrived to my country/service provider. I flashed stock 4.1.2 and as soon as it boot up I started the process to flash 4.4.2 without checking the battery level, when I tried to flash kitkat I couldn't because the fastboot said that battery was low, so I tried to boot up but I couldn't since the rom had been wiped, then I tried to boot into recovery (TWRP) to charge it from there but I couldn't since recovery was deleted when I flashed 4.1.2. So I'm stuck into fastboot with no battery, no rom and no recovery. I've read that a factory cable might charge my phone but when I attempted to do one myself I discovered that the micro usb cable I used only had 4 pins instead of the 5 needed, I've been searching all over my house for a micro usb with 5 pins but didn't had any luck, but when I found that there was this website that used to sell some kind of adapter from normal micro usb to factory cable I tried to buy it, only to discover that the site has been taken down and I haven't been able to find something like that since.
I don't want to buy a factory cable since the shipping is very expensive to where I live (Mexico), any ideas on what to do?
You could try opening the phone and manually charging the battery if you can get access to a hobby li-po charger but you need to be careful since I think Moto used a weird chemistry that has a higher voltage then normal. Aside from that - your best bet is a factory cable.
Related
Hey guys,
I have my rooted, custom-ROMmed GS3 here. Was running Eclipse ROM for a while now (several months), decided that I wanted to re-ROM soon, and as I had to boot into recovery earlier today (Google Hangouts caused my phone to freak out and get caught in the bootloop) I figured now was as good of time as any. Did some research, decided to put LiquidSmooth on it, downloaded Liquid-JB-v2.9-OFFICIAL-i9305.zip and gapps-jb-20130301-signed.zip, put them on my external SD, booted into CWM recovery, flashed both on my phone. I did forget to wipe everything. And I think I may have tried to put the international ROM on it. Phone was at 94% battery at the start of this. (Didn't make a backup as my phone was running a backup.) Now, phone won't recognize the power button at all, either just to power on or to try to boot to recovery. It is recognized by my PC in Device Manager as QHSUSB_DLOAD, and plugging it into a charger (wall or USB) without the battery in gives me a red LED.
Help?
Thanks
Figured it out - hard bricked my phone due to a wrong ROM. Fixed it by sending it to brickedmyphone.com , he had it back to me in a week, back to stock, completely working.
my nexus 4 was on temasek's unofficial cm12 build ver 6.1
recovery in use was recovery-philz_touch_6.59.0-mako
i decided to update the rom to build 6.5, so i downloaded the zip to my sdcard,
i had not made a nandroid bkp
after flashing the rom/gapps/superuser, wiping dalvik and cache, things went wrong
after that the phone would only show 'google', then freeze, then go blank, then again show 'google'. this is the first Loop i have encountered where the boot animation never even showed up.
after that in about 8 hrs, i tried all of the foll-
installing the stock images: my phone booted up the first few times i flashed stock images using fastboot, but after three times (because each time it successfully booted i would go back to recovery to try flashing the customromzip) my phone stopped booting up for stock.
it resolutely stayed stuck on the boot ani.
recovery: flashed many times, via sdcard and also via fastboot. no problem with the recovery
zips. absolute fail. nothing can get me past the 'google'
now there's another peculiarity, which makes me wonder if there is hardware damage involved in this softbrick story
after all this flashing my charge came down to 20%, so i tried to charge it (switched off, obviously, since it isn't booting up)
but every time i connect my charger, it boots up,and then shows me google, and freeze and restart..same old cycle
in a last ditch attempt to somehow charge my phone i have brought it to fastboot, and left it connected to my laptop. i don't know if this will work.
please help, also i am now considering using a toolkit, unified android or wugfresh (the latter, i have a previous bad experience with) to get my phone to atleast switch on with something.
should i use the toolkit or just take my brick to the servicecenter to check for damage to hardware
Last night I tried to flash TWRP just because I wanted to go to a custom ROM- alas, the phone now will not go past the google logo. It usually hangs there for 10-ish seconds and then reboots. Occasionally hangs there indefinitely. It's not a power button issue- the button worked just fine before flashing and I've confirmed it still works normally with a multimeter.
I tried to reflash stock using the Google images and "flashall.bat", which says it succeeded- but the phone still loops. I can get into fastboot, but I get the bootloop even in recovery. Running the similar script through Nexus Root Toolkit always fails on flashing the system partition- usually a buffer error due to a sparse header. Can't even seem to get it to do the "fastboot boot TWRP.img" or whatnot. I've flashed KitKat, Lollipop, and MM stock roms to no avail- they all say they succeed, then continue to bootloop.
I've tried just about everything I've seen on here- but not being able to get into recovery hampers efforts like repairing the persist partition.
Help?
When you boot into recovery, the phone reboots itself? If it does, it could be a sign of a failing power button.
When flashing a stock ROM, are you flashing userdata.img and then performing a factory reset/wipe before booting the phone with a stock ROM for the first time?
When I can get into recovery (without a restart), the phone is totally fine.
I think part of the issue is that the battery ran down while I was trying to do the repair- hence it trying to restart and failing. Power button still seems fine (again, confirmed with a multimeter). I left it plugged in to my iPad charger (since that's a 2A charger) overnight and it was still blinking red in the morning. I moved it upstairs and now I can't even make it that far.
Perhaps the battery was just shot by the time I got the "repair" done, hence the boot loops. Is there any way to revive it shy of cutting open the battery + charging manually (with a bench supply) or just replacing the battery altogether? I may try doing a motherboard swap with my working Nexus 5 just to see if it is in fact the battery.
When the phone is powered off and connected to a power source, do you ever see a flashing red LED? You flashed the correct twrp for the hammerhead?
I would try a new battery because it seems like everything is working.
Hi Guys,
So the issue seems to be straightforward and I read many threads about it, but none of them actually solve my problem.
My S6 is locked to Orange Poland (which is currently running 6.0.1 Android). I wanted to flash unbranded Marshmallow rom but that did not go well and in the process of flashing Odin returned an error (Complete(Write) operation failed). That's the way my phone became bricked. I tried to reflash this rom several times (while changing ODIN versions and also I tried single AP as well as 4 files + PIT). None of this worked. So I decided to go back to the branded rom—exactly the same as it was before.
Odin this time didn't show any fail messages and the phone actually started booting up. And here is my problem, it is stuck on the Samsung logo. I tried going to recovery mode, wipe cache and then factory reset but it still cannot go through Samsung logo.
My phone was never rooted. I have up to date samsung usb drivers. I tried SmartSwitch but it fails to recover the phone every time.
Do you kind people have any ideas?
Hi again,
Just a quick update from me. I finally managed to revive my phone. It seems that the bootloop was caused by the low battery (actually 0%, while being connected to PC). Once I charged the phone to 100%, it miraculously booted up and went to the setup wizard. I have no idea if the low battery had an effect on it, but once I charged it, the phone started to work properly.
In the end, I flashed back the stock rom with Orange Poland brand. The rom consisted of 4 files + PIT file. I used Odin3_v3.12.3.
Maybe this will help someone
axapies said:
Hi again,
Just a quick update from me. I finally managed to revive my phone. It seems that the bootloop was caused by the low battery (actually 0%, while being connected to PC). Once I charged the phone to 100%, it miraculously booted up and went to the setup wizard. I have no idea if the low battery had an effect on it, but once I charged it, the phone started to work properly.
In the end, I flashed back the stock rom with Orange Poland brand. The rom consisted of 4 files + PIT file. I used Odin3_v3.12.3.
Maybe this will help someone
Click to expand...
Click to collapse
Thats why you should always charge your phone to at least 70% before doing any flash :good:
Hello there. I own a Z3 model D6603. It is unlocked bootloader and Before it had got the bootloop i had Lineage OS 16 custom rom installed on it (Android 9). I was watching some videos on chrome and then the phone heated a little and then restarted. I thouhgt it was maybe some sort of instability but then it started just bootlooping.
Current Status right now is :
Once connected to pc goes to flash mode.
I can get it to fastboot.
When connected to charger just goes into endless bootloop where only SONY logo appears and then quickly restarts
In attempt to fix it I flashed stock FTF using multiple versions of Flashtool which was fruitless. I also Tried with EMMA but nothing helped still. And then after looking I think it might be damaged TA and I've seen so many say that if that's the case then the phone is bricked forever unless you have had a backup from a previous working state which I actually do. The problem is that I don't know how to flash this TA back since the phone doesn't boot to restore it through ADB. I saw that S1tool works with older devices and doesn't work with Z3 models so I wonder if there is a way to fix this. Thank you for your time.
PS : My power button doesn't work I used to use fastboot to boot it when necessary
Issues of that kind may be a hint for a dead battery, this should be ruled out first. Note: In that case your phone might not boot even if connected to a charger!
After that is ruled out, one should try to install LineageOS 16 or later following the official installation routine from scratch.