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.
Related
(Well, this is embarrassing.)
(yes, I read older threads before making this.)
I recently rooted my admire; I decided to install rom manager and Busybox, however, when rom manager was installed (I figured that I could get flashed roms) When I begun to install CWM recovery 7.0.3 from rom manager, i chose "other". It installed, and it told me to reboot. So, i turned it off and was going to turn it back on. Nothing. Recovery mode, Download mode. Nothing. Phone stays off, never turns back on, as if it was dead. I'm not sure if it did enter DL mode, because I heard that it would still be in download mode, even if the screen was off. My battery still charges(?) when i plug it in. (The battery heats up, no charging screen, or boot.) Any fix?
To recap; Samsung admire. Rooted recently. Root manager installed. Cwm recovery 7.0.3 downloaded. Installed. Tried to reboot. Hard brick.
Biffalothethird said:
(Well, this is embarrassing.)
(yes, I read older threads before making this.)
I recently rooted my admire; I decided to install rom manager and Busybox, however, when rom manager was installed (I figured that I could get flashed roms) When I begun to install CWM recovery 7.0.3 from rom manager, i chose "other". It installed, and it told me to reboot. So, i turned it off and was going to turn it back on. Nothing. Recovery mode, Download mode. Nothing. Phone stays off, never turns back on, as if it was dead. I'm not sure if it did enter DL mode, because I heard that it would still be in download mode, even if the screen was off. My battery still charges(?) when i plug it in. (The battery heats up, no charging screen, or boot.) Any fix?
To recap; Samsung admire. Rooted recently. Root manager installed. Cwm recovery 7.0.3 downloaded. Installed. Tried to reboot. Hard brick.
Click to expand...
Click to collapse
dude i did the same exact thing except when i tried to upload a rom from my sd card,cwm rebooted my admire and it never cut bak on, im been up all nigh
t tryin to unbrick still havent got it to unbrick,but it still charge so dats a plus.
I pulled my vortex out of storage the other day to tinker. It was rooted but fully updated stock 2.2.2
When I booted it up, it stayed on the boot animation 20+ minutes, until the battery ran out. I've tried booting it up again but it keeps bootlooping.
I figured I'd just flash a new ROM onto it, but I never put a custom recovery onto it and the only Vortex Recovery I found was this;
http://androidforums.com/getitnowmarketing/330813-all-one-recovery-thread.html
However, it says I need to do on-device commands and stuff to get it working, which obviously isn't an option.
Is there any other way you guys could think to resurrect my old Vortex? My Droid Charge is my phone now, this thing doesn't get much use anymore, but I'd still like to get it back in a usable form.
EDIT: FYI, already tried everything relevant in this thread: http://forum.xda-developers.com/showthread.php?t=1031596
If you flashed stock rom. Try hard reset.
Home+vol down / vol up+ power.
thank you! that button trick did the job!
EDIT:
well, it worked once, but the phone had been uncharged for a while so the battery died, and now i can't get the trick to work again >_<
is there a way to re-flash stock without a custom recovery?
I had the Photon Q with the SIM mod and CM 9 working for 2 mouth. But yesterday, I were using the cellphone when it reboot itself and get freeze on the unlocked bootloader warning. I try to power it of but y could not, the I let it there until batery drain (about 4 hours)
Now when I boot the cellphone it has an strange behavior. Some times it freeze on the unlocked bootloader warning, other time make a loop boot (show the warning and restart). Also some times it display strange colors on the screen when try to boot and many times it display a randomly sorted grey vertical lines and very few times (one of every 50 times) it boot the ROM but when i touch the screen it goes black.
i can not conect to phone by adb and can not enter recovery, but i can access to the fastboot (in fact the fast boot is working but do not display anything on the screen, i suppouse that the same happend with the recovery. but i can not use it if the screen is black)
I used the fastboot and RSD to flash the stock firmware, the phone return fail on every 4.0.4 ROM but it work with the 4.1.2. After the flash some times thes phone display the morotola and sprint logo and then start the handfree configuration, but when I touch the screen it goes to black again.
I do not know if it is bricked, I think that if i have access to the fastboot i can resurrect the phone. but is very strange the random behavior.
Do you have any idea what should I do?
Thanks.
PS: sorry for my bad english
Re-Strange behaviour
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.
schmandroid said:
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.
Click to expand...
Click to collapse
I tried it, but do not work.
I flash the stock ROM from fastboot and also flash several recoverys, but never boot any ROM and I think that i access to the recoverys but the screen is black then is very dificult to use it. Is strange beacouse some times screen displays perfect the unlocked bootloader warning, but never display anything on the fastboot or the recovery.
Witch part of the software have the video drivers that are used on the recovery and fastboot? I think that maybe is corrupted. how can i flash it again?
Thanks.
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
Hi guys,
New to flashing custom ROMS. Good news - flashed CM12, then LiquidSmooth and I'm learning a lot after having soft bricked my phone a few times. Bad news - After trying to get back to Stock I'm not able to get out of this LG Logo bootloop. The LG logo will flash, screen will go black and the whole process starts again. It doesn’t progress past that. I'm unable to get to TWRP recovery or download mode.
My idiotic move:
Iffy stability with camera and mobile data with CM and LiquidSmooth. Decided to go back to Stock.
I flashed my nandroid backup, which I believe led to a bootloop (can’t remember). Was able to boot to TWRP and get back to CM12. Then I had the genius idea of using AutoREC and selecting the “Go Back to Stock” option. Yes, it’s already sounding like a bad, and nonsensical idea as I say it now. Can't remember exactly what I did next - I either flashed my nandroid backup or did a factory reset through CM settings. Threw me into this bootloop.
The details:
Model - D800 - Am sure of this.
Stock software before flashing CM12 was Lollipop 5.0.2 via OTA.
TWRP Recovery 2.8x something or other. Used AutoRec to flash.
I can interrupt the bootloop and access Factory Hard Reset through Power + Volume Down
Had to go to JB Bootloader in order to Flash ROMs. Errors returned otherwise.
Roadblocks:
No download mode. Holding Volume Up & Inserting USB cable doesn't work. Although am able to get bootloop to include a blank screen with red flashing LED through this method from time to time.
Phone boots up, and goes directly into bootloop when plugging USB cable into phone. This happens both when plugging into a wall charger or into a computer. I think this is probably the biggest pain and is holding up things from progressing. Can turn off phone by holding down power for a few seconds, BUT if the phone is plugged in it will continue to boot on its own.
Phone not recognized by computer & ADB However, was at times able to get Device Manager to recognize the phone as an "Unknown Device" after going to the Factory Hard Reset screen. This is no longer working after trying different drivers. I’ve went through LG Mobile Universal Driver as well as the Koush driver.
Going through Factory Hard Reset via hardware buttons only throws phone back into BootLoop
Can’t boot into TWRP
Any insight or help guys? Thanks in advance. I think getting into Download Mode will be a quiet victory. I’d like to try to use Supersports guide once I get there to go back to stock.