So, my G4 Plus got itself bricked out of thin air. I got it last year , unlocked it ages ago, tried some ROMs but decided to go back to stock+ because of pesky camera problems.
Earlier today i was using it normally when it froze and a long vibration started. With no other options I made a hard reboot and it started up again, only it didn't... The boot animation came out all choppy before rebooting itself again. Sometimes it lasted longer, sometimes a bit shorter but it never fully booted up again. Back home I booted into TWRP, flashed cache/dalvik, nothing. It DID get to a full "G" logo, then rebooted itself again. Got a ROM into the SD card, started flashing, froze, reboot again. Tried formatting everything, same thing, froze, reboot.
Just about the only things I can do with it are boot to TWRP and do anything that doesn't involve storage (so pretty much useless) and bootloader.
I also tried just about everything in my power to flash it on ADB/fastboot, but windows itself won't recognize the thing. All sorts of drivers, command lines, windows test mode (for driver certificate shenanigans), nothing worked. I even tried the same on a netbook with win7 since my desktop doesn't have a single USB 2.0 and I heard ADB has trouble with 3.0, nothing again. It doesn't recognize the device at all. They do recognize my girlfriend's G5 by the way, but seem to want nothing to do with my crippled-down-to-bootloader G4+.
I need some help guys, any clues?
Remember:
-Not your everyday bootloop
-Stuck with bootloader and limited usage of TWRP (i can copy files from SD to Internal with no problems)
-Neither Win10 with USB3.0s nor Win7 with USB2.0s recognize the phone at all, at least in this state (every driver out there already installed in every order)
Related
Hey there,
I have a Desire z that was completely stock, no mods, no roms, S-on and all that. One day it had a hissy fit because it was trying to update all my apps via GPRS (didn't have the playstore app yet) and I stopped it. From then on, the phone kept on locking up, freexing, hard rebooting and so on, so I reset it back to Factory and installed playstore first.
Well that was all fine for about a month when the phone suddenly turned itself off, then got stuck in a boot loop for about 30 reboots, then it would work fine, then it would boot loop again and so on. So I entered HBOOT, tried to do a reset from there, and the phone froze...
Now the only thing I can access on the phone is the HBOOT and FASTBOOT menu. I don't have ADB access, so I can't push anything onto it (tried all the drivers I can find, ADB will recognise phone in FASTBOOT but not HBOOT). I have tried the official HTC Gingerbread updater, to no avail (detects phone in fastboot, tries to reboot into hboot, then hangs. Booting phone in HBOOT+USB and running that reports the 120 error, Battery below 30%). I took the rom out of the temp file and put it on the SD card, rebooted the phone, and it starts top update via that, but hangs on the first step (Flashing the bootloader partition)
I have tried soo many things, made about 20 Gold Cards, no idea if any of them were correct or not. I tried running the official HTC update on an XP machine, which is known to not show the 30% battery error, but the drivers wouldn't install.
So, at this point, I have a phone that won;t boot past the HTC logo, Hangs when updating via anything, no root, S-ON, no ADB access, no recovery mods, NADA.
So.. over to you guys...
Hello guys, i'm having a problem ;f
I was on cm12 nightly when i decided to reboot my device after few days of running, strange thing happend and i ended up in bootloop.
I've downloaded 4.4.2/4.4.4/5.0.1 stock images and tried to flash it guided by the instructions in this thread, however i still get a bootloop, even after clean installation, even after wiping cache and doing a factory reset.. I've managed to boot up my device twice since yesterday, after getting stock image to work i pushed cm12 and gapps on my phone and flashed them.
At the first try, i got bootloop again, so i decided to go through the whole process again, many attempts later i've managed to boot up my device again, and again i decided to flash cm12 and gapps, this time my device booted up properly so i wanted to gain root access, in order to do so I flashed UPDATE-SuperSU.zip file and as a result end up in bootloop again.. I have no idea wtf is wrong with my nexus. I am still trying to flash factory image, and i always end up with bootloop.. I'm out of ideas here, HALP! ;(
@update:
I have uninstalled all drivers, and mount my device to another usb port, then with NRT i installed google's drivers, by using nrt i have flashed 5.0.1 factory image, rebooted into recovery and wiped/factory reset, after that i rebooted my device and still no luck - hanging on floating dots for 15 minutes..
Before all of this I tried formatting my cache to FAT and to sdf4 and it didn't help, I literally tried every single instruction i could've found ;/
What's wired is that when i encountered bootloop yesterday and wiped/factory reset i booted fine, after restart it went into bootloop again, so i thought i would wipe/factory reset again i'll be good to go, but.. it didn't help this time oO
things i've already performed:
1. fastboot oem lock/unlock
2. wipe data/cache/factory reset
3. flash factory images of 4.4.2/4.4.4/5.0.2 through NRT/manually
4. converting partition to fat and next to sdf4
5. reinstalling drivers
6. different ports and usb cords
6. i even tried switching motherboard from my old n4 and i still stuck at bootloop *LOL!?*
7. after 6 i thought it may be related to usb port so i switched usb port from my old n4 and it did help but.. until next reboot ;/
from time to time, after flashing it boots up just to make my hopes and then it gets the bootloop after restart ;/
@update2:
It seems it's hardware related issue. I have tearn down my nexus device and left only motherboard with fron/back cameras and audio jack, daughterboard, i even disattached the speaker along with antena. At this point i flashed factory 5.0.1 and it works, i'm in the moment when i plug peace after peace and turn on the device to check if it still works. I'll update when i find out what was the cause of the problem.
@update3
Stupid as it sounds the issue was caused by the vibrator module, while it was disattached, the device was booting up without any problem.
Can anyone PLEASE help??
My partner opted to do a suggested update on her S5, but didn't notice the wifi was off. The phone seemed to have done the update, but shortly after it rebooted itself, then again, then again. The frequency of reboot got quicker and quicker and now it loops between the Galaxy S5 splash screen and the SAMSUNG logo, but doesn't go any further.
I managed to boot the phone into reset mode, cleared the cache and then did a factory reset, but that did nothing to prevent the boot loop.
I then downloaded Odin (ver 10.3.7) and what I believed to be the correct firmware (G900FXXS1CPLV_G900FVFR1CPJ1_G900FXXU1CPIW_HOME.tar.md5).
Having checked the battery was charged, I followed the instructions of connecting the phone via USB, loading the md5 in the AP, checking Auto Reboot and F-Set time in the options and clicking the Odin Start button. I had removed the battery, replaced it and then booted it into the update mode (Power, Home, Volume Down, then volume up) with the screen confirming I was in the right place (....do not unplug.... etc).
The file loaded, (green bar at top of the Odin window on my PC) and Odin reported success. I then disconnected the phone, booted in recovery mode, reset the cache and then did a clear data, factory reset.
The same symptoms prevail, STUCK IN BOOT LOOP!!!!
The only thing different is that if I plug it into the USB on my PC, after a while the phone tries to turn itself on and goes into either a boot loop or freezes on the Galaxy S5 Splash screen or the SAMSUNG Logo.
I am charging another battery (just in case that is in some way to blame) and will try again to replace the firmware, but could I be missing something, do I need to do anything with PIT (I thought this was all taken care of by Odin using the MD5 file) or is there some other test I can perform that will show if the phone is fried???
MANY THANKS for looking!
ur going correct, try to reflash it again through odin and dont disconnect phone until it boots into system, it is taking some good time, so just wait and dont do anything this time like clearing anything or restoring. i hope ull get success.
THANKS - but...
Thanks Rayzen, I will try the whole thing again, but I think there is something more to this than a firmware fault!
There and gone again
OK, so on the 4th attempt I got the phone to take the firmware using Odin, it reported success and the phone rebooted itself (several times) and eventually appeared to boot to a new factory reset.
I put in a SIM card and entered my email and google account details and left it charging over night. This morning when I tried to use it, the screen froze and then it rebooted itself. Hey presto, the phone is back to square one with a boot loop.
ANYONE (please) got any suggestions?
THANKS
No one??
same here, same symptoms, same feeling.
when flash gone right... i feel lucky.. but for half hour only, rebooted and angain in boot loop.
I cannot even boot in recovery. flashed TWRP. from 5 boots in recovery only 1 success.
When trying to wipe phone in TWRP - it hangs.
still trying to install some other (custom) rom. still no success.
hope never dies
same things happened here! now cant get samsung galaxy s5 to boot...............
Are you sure your using right firmware? as it took me a few versions before it booted last time this happened?
Could any please confirm what is the right firmware for samsung galaxy s5 900F
It took another 6 or 7 attempts, left it over night and was about to trash it when it booted.
I then received a 'software update available' message and tried installing it. First attempt put the phone back into boot loop so I reflashed it again using Odin.
That worked immediately the over the network software update installed and now phone is 100%
Very frustrating but I got there!
glad you fixed it! ive tried three different firmwares and still nothing.
trying this one atm
G900FXXU1ANE2_G900FEVR1AND1_G900FXXU1ANE2_HOME.tar
oh and how long do they take to boot when there are sitting at the samsung glowing screen?>
I'm in UK and used what (I had to guess) was the best firmware.
I'll let you know which version it was when I get home tonight.
BUT I had all the problems with a single version and it eventually came good.
I read somewhere that overwriting a different core (from specific providers) with generic firmware, could lead to a world of pain until it gets full replaced... not sure if that's a good description (or has any fact to it) but it seemed to be re-loading and re-loading and re........ for ages, finally cracked it.
well mines booted now!but getting constant errors about samsung push!
If it'still booted, you'very made progress!
Push issues are mentioned elsewhere and can (eventually be sorted) but if you have a booted phone you should be able to get an over the air software update installed from the service provider....?!
I flashed Resurrection Remix a month ago in my 1GB ram variant, and everything was fine until, one day, when I was operating camera in my phone, the phone blacked out, and restarted, and when the screen showed pattern to unlock, and any attempt to unlock the phone would lead to immediate restart, and then after 4-5 attempts, the phone started to restart in frequent short intervals only showing android logo on the screen.
I decided to flash ROM again but this time stock ROM, but this phone has a great history of not entering into recovery mode no matter what I do. It enters only on its will. So, somehow I again flashed TWRP, and then tried flashing stock rom with QPST tool, but, when flashing finished, the phone as usually restarted, but only again to be stuck in boot loop. I again tried to flash it. But this time, after the full installation, the phone became dead. No matter what I do, the phone doesnt even turn on. No vibration, no lighting of screen, and even its not detecting on connecting to the PC.
What could be the problem? Anything related to hardware? Please help.
I suggest you to bring the phone to the service center
vaddadi9953 said:
I flashed Resurrection Remix a month ago in my 1GB ram variant, and everything was fine until, one day, when I was operating camera in my phone, the phone blacked out, and restarted, and when the screen showed pattern to unlock, and any attempt to unlock the phone would lead to immediate restart, and then after 4-5 attempts, the phone started to restart in frequent short intervals only showing android logo on the screen.
I decided to flash ROM again but this time stock ROM, but this phone has a great history of not entering into recovery mode no matter what I do. It enters only on its will. So, somehow I again flashed TWRP, and then tried flashing stock rom with QPST tool, but, when flashing finished, the phone as usually restarted, but only again to be stuck in boot loop. I again tried to flash it. But this time, after the full installation, the phone became dead. No matter what I do, the phone doesnt even turn on. No vibration, no lighting of screen, and even its not detecting on connecting to the PC.
What could be the problem? Anything related to hardware? Please help.
Click to expand...
Click to collapse
I think its hard bricked
https://forum.xda-developers.com/lenovo-a6000/how-to/guide-hard-brick-lenovo-a6000-t3581892
Use this
I used to have a Pixel 5 phone, which unfortunately was run by a truck and now I am stuck with an old Samsung Galaxy S7 Edge phone. I have decided yesterday to install Pixel Experience on it and it all went fine. I have unlocked the OEM, enabled USB debugging, installed the latest version of TWRP with heimdall, and sideloaded the Android 11 Pixel Experience Plus ROM.
I had done a full wipe of the phone before doing it, including the system, etc. I have then recovered from the backup from my Pixel, and it installed all apps. Then I saw that there is a new version of the Pixel Experience, installed it, and plugged it into the charger and I woke up at the Google logo. I disconnected it from the charger and the Google logo was still there, it took me a couple of minutes to switch it off while holding continuously the power button.
I tried to go into recovery or download mode without any success. Then I have connected it to the charger again and I saw the battery indication with lightning inside, but normally it also shows you the battery percentages but this time, it didn't. I have then tried to connect to my PC, thank God this time, it booted straight into recovery. I have tried to sideload again the ROM, and this time, it worked till the end, but then I was unable to slide the slider to unlock it and restart the phone. Then switched it off and tried once again to sideload it, this time the phone died at half of the sideload. I am completely desperate now. Am I doing something wrong?