Last night after a good night of working with my tablet out on the job I came home and noticed it was running a little sluggish so I rebooted it. It then proceeded to hang on the bootloader screen. I tried flashing into recovery and wiping and reinstalling but it still stays hung up on the bootloader screen. Getting into the recovery boot loader it says the secondary kerlel akb has an issue or something. Is there a way to Odin this thing back to stock? It's not totally bricked I can still get into recovery just can't get it to boot into the second kernel or whatever it means. I can get the exact terminology if someone needs it but I have been bricked worse than this before its just weird it won't fix itself after I re install a new ROM.
Sent from my A100 using Tapatalk
I am on the Skillraz V8 boot loader to be exact, and thats the first screen it gets stuck on..
I just tried flashing a stock un rooted ics zip but it still hangs on the first screen after rebooting after the install, which seemed to take ok... and it doesnt change my recovery or anything back to stock.
In advance, I normally try to fix problems myself thus I dont post much, so I'm sorry if this is in the wrong area. I have already spent about three hours researching and trying to figure this out.
I've gotten sick of the loads of Verizon bloatware slowing down my phone, so I finally pulled the trigger to try safestrap. I'm using the ME7 build so that was the only option.
Safestrap installed without a problem. I flashed Hyperdrive successfully, but the ME7 modules available here would fail to flash even after I checked the MD5. I flashed from another source here successfully.
After all of this, when I boot the phone into that module, it will go to a black screen after the "safestrap enabled" logo. After about a minute, the phone will vibrate, show the Samsung logo, and then go into ODIN download mode.
The only thing I can do now is hold the volume down during start up. This loads a warning about how installing a custom OS will catch your phone on fire with a continue option (which results in the ODIN block), or a Cancel option (that restarts the phone and shows the safestrap logo before going to the black screen etc.) From this I can change the boot default to the stock OS if I choose, but I still cant use Hyperdrive. I have already tried deleting the ROM slot and starting over, but that didnt help.
Thank you so much for the help!
Edit: I tried bonestock and just got a black screen.
Edit 2: I also tried google edition and it would go to a black screen, restart, and loop again.
Hello All
I've managed to make my Nexus 4 quite useless after running the battery all the way down. Initially I was able to revive my completely stock 5.1.1 by flashing TWRP and running fix disk permissions, but after reaching about 70 or 80 percent charge the phone rebooted itself and got stuck at the animation loop again. Strangely I can no longer make either of the bottom two touch menu entries in TWRP click after this to reach fix disk permissions, though the back/home/console output buttons do work. Strangely, fix permissions via CWM 6.0.3.3 does not do the trick. I've since tried loading AOKP 4.4 and 4.3 paired at various times with TWRP or CWM, both of which also get stuck looping part of the boot animation, as well as reflashing both stock 5.1.0 and 5.1.1 which give me the same. What should I try next? Though I have guessed around quite a lot here, I think the TWRP menu touch options failure is the best clue so far.
Thanks
Sam
Hi all,
I got my Wileyfox storm running stock CMOS 13.0 in April and had no problems for about a month. Eventually, I got a pop-up notification with an "Incremental Update" for the phone. I downloaded it and when ready to install, I did so - or at least tried. The update finished and booted into recovery for some reason. At the time I didn't question it and just rebooted the phone from recovery. This led to a boot hang on the "Cyanogen Mod Ready" boot screen.
After searching around for a fix I eventually tried to flash over the stock ROM via Fastboot - which for some reason errored on emmc_appsboot and the phone rebooted itself - with a penguin instead of the Wileyfox boot logo and STILL hangs on the Cyanogen screen. I can also now not boot into fastboot and not boot to fastboot from recovery either (which I CAN still boot to).
Does anyone have any ideas on how to fix this ASAP??? Help would be greatly appreciated!
Many thanks.
I've finally found something that works, unplug the battery for a day or two, then plug in and charge and turn on and might boot properly. Frustrating having to do it every time you get into the bootloop hang and doesn't work every time but still probably salvageable.....I discovered after being bricked for 14 months.
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....?!