Verizon Tab here.
Finally decided to try installing KhasMek's K-leanMod v2 rom.
I started by installing the bootstrap app from the market as per the instructions. The app rebooted the tab. It backed up everything. It said everything was successfull. After that I rebooted in download mode (power +volume down mode)
I then flashed the rom I downloaded from the thread. When I rebooted it just stuck on the samsung logo. I let it sit for 20 minutes and nothing happened. I decided to try to reflash to see if that would work but now I can't get back into download mode. Interestingly I can get into download mode when it is plugged into the wall, but when its connected to the computer it does not work...
Any suggestions?
Thanks
EDIT: It finally decided to connect to the computer and I flashed the CWM, did a factory reset and then flashed the custom rom and it started working again. I think it might have been due to low battery (it was at 3% when it finally came to)? Anyways just glad I dont have an expensive paperweight.
Just discovered a new problem...
When I have the tab plugged into the wall, it wont turn on. It just sits frozen at the battery charge screen. When I unplug it and power it on all is well.
Any idea what that could be?
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....?!
Hello, one week ago I received the Axon 7 mini from Gearbest, since then I haven't used it that much, but yesterday while watching a youtube video it turned off suddenly and when I tried to turn it on it just gotted stuck in the zte logo. After several tries, and trying of wiping the data and doing the factory reset (what gave error messages such as "can't mount"...), I decided to update it to from the sd card using firmware of the russian zte. After that the phone could pass the zte logo and start the configuration screen slowly, but started to rebooting, it took me several trys till I could finish the set up, but the problem was still, then I tried to do the factory reset as well as data wipe now succesfully, but the rebooting and slowness still there, so I can't do anything because I can't finish the setup correctly, and even the only way to turn off the phone without the boot loop is inside the menu of android recovery. I hope you can help me, thanks.
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)
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?