Hi All,
I hope I'm posting in the right place, apologies if not.
I have been running Cyanogenmod on my S4 i9505 since Christmas. A couple of weeks ago, for no apparent reason, the phone started switching itself off so I decided to try and flash back to a stock ROM using Odin and the most recent firmware (5.0.1) from sammobile.com. I'm pretty new to this and don't have much in depth knowledge at all - hence opting for the apparently easy Cyanogenmod rooting option in the first place. The Odin flash 'passed' yet on reboot I got stuck at the Samsung logo and the phone then gets stuck in a boot loop if I switch it off using the power button. I then tried to flash an older firmware (4.2.2) but it has failed twice, leaving me with a 'brick'.
As I said, my technicial knowledge here is very limited but any step by step help to trying to get the phone back up and running would be greatly appreciated. Have I completely ruined the phone past repair, or is there a way round this?
Many thanks in advance
Whenever you upgrade to Android 5.0.1 from an earlier version it takes up to twenty minutes before it fully boots. This is because of the internal change from the Dalvik app compiler to the new ART compiler Android now uses. Android apps come in multiple parts, and on old versions of Android these parts were assembled into a single running image every time you ran the app. This is called "Just In Time" (JIT) compiling. The new ART compiler uses "Ahead Of Time" (AOT) compiling. It assembles all the apps once, rather than repeatedly assembling an app when you run it.
When you upgrade to Android 5.x and future versions of Android, Android will need to spend time compiling every single app on the device before it fully boots. This can take quite a while if you have a lot of apps, and an unfortunate side effect of this is that the device looks like it's stuck in a bootloop.
If you're able to get into Download Mode, your S4 isn't bricked. Install 5.0.1 again, but this time don't touch the device for a while.
Many thanks, a little patience was all that was needed. Re-flashed 5.0.1 and waited for first boot - all sorted!
Related
Two days ago i tried to update my SGS5 (SM-G900F) with Kies to Android 5.0.
The phone has newver been rooted.
That is supposed to pretty straight forward, but after the update i havnt been able to use it.
After each boot it gets me to the logon screen, where i just have enough time to press my code but then it restarts over and over.
So i thougt something might went wrong in the process and used Odin 3.09 to flash the NEE (Nordic/Danish) version from Sammobile manually.
Unfortunately this didnt change a thing and the bootloop is still there.
From the short time where i gain access to my lock screen i see my old lock screen background, but the Font and setup has changed, so i guess it runs Android 5.0 now.
I would appreciate any help to this matter, since i'm growing at bit desperate on this now.
II would prefer not to root it, but if thats the solution then its fine by me.
I should be able to use ADB with the right guide, but havnt used it since the HTC Magic
Well found a solution.
Installed the Team Win Recovery Project and then did a full wipe (VolUp+home+Power under reboot).
So lost everything on the phone, but it works
I was lucky that i did a backup last weekend of images/videos last weekend. Phew....
First post, So hey everyone
So I rooted my phone around 6 months ago with CF Auto Root, everything went fine but i was still on stock ROM. So then i found the Alliance ROM and decided to flash that because it looked cool. I flashed it using FlashFire to ensure I keep root. Everything worked and booted just fine, really smooth and of course it looked awesome. One small problem though, I could not send messages but I could receive them. Probably a SMSC (that was around 3 hours of head ache attempting to fix that) issue or because Straight Talk didn't like my phone using Android 5.0. So then I tried downgrading to Alliance 4.4.2, NOPE. That was the end of my phone :'(
Im now stuck on the Galaxy S5 screen with "Set Warranty Bit: Kernel" in the top right. No idea how to fix it and obviously knox was tripped but that isnt a huge deal to me.
I have tried the following.
1. Tried to reroot (seemed to fix a lot of issues actually)
2. Tried to reflash Alliance ROM android 5.0
3. Multiple cache and system wipes.
4. Installed TWRP through Odin but thats useless because I was dumb and deleted my back up in the system wipe
Im currently downloading stock ROM but my hope for that is fading judging that TWRP even stalls out and the phone reboots right when it attempts to flash. - well this was a bust, there are 4 freaking md5 files. when i go to flash with odin it says it a modem and then fails
What i have access to:
1. Recovery
2. Download
Is my phone already 6ft under or is it hanging on for dear life?
Edit: Should also mention that my galaxy is a SM-G902L (Straight Talks' model???). CF Auto Root for Galaxy SM-900F was used to root. So that is what i based my choice for model when installing Alliance
Ok so recent update, When I go into reboot and do system or whatever, it says there's no OS installed. I guess that would make sense why it doesn't want to boot, because there's nothing to boot into... but why cant i install any OS through odin???
Another Update: So I have no OS, I know how to flash a new OS, such as a custom ROM, but my phone refuses to accept the flash whether through odin or through TWRP.... W.T.F. Did i really look my phone down? And I guess that means that I will need to get the Straight Talk variant of Android 4.4.2 Great If anyone has the a backup and they are on straight talk, please help me out
Thanks for the help!
FIXED!!!
So after around 14-16 total hours of headaches, I have managed to bring my phone out of the grave. I read over the Straight Talk Variant Galaxy S5 thread multiple times and saw people saying that most Verizon ROMs work decently if not perfectly fine with the SM-G902L. So I downloaded M.O.A.R ROM and flashed through TWRP.
Worked like a freaking charm!! She booted right up, into the waterspout boot animation, and after a very long 5 minutes, I got to the welcome and setup screens!! I guess it was just a matter of finding the right ROM. I just find it kind of weird that it would flash Alliance just fine and then not allow it the second time...
Anyway, the very helpful thread that saved my phone
http://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-straight-talk-variant-sm-s902l-t3162340
Good day everyone, i am going to report my delicate and infuriating problem that has been haunting my head for two months
I'll describe my problem in extreme detail, hoping you guys able to identify this disaster.
My android phone is Lenovo A6000 Plus, i've bought it 2 years ago and it's running on latest Lollipop version 5.1.1 I never alter the system files, since i only use my phone for games and communications, and i'm not really into tinkering android's software. so i use my phone like a normal person, do the updates when the settings asked me, update the apps, etc. and this phone running smoothly in my service. i wanted to ask both WISDOM and HELP in this thread.
1. The Bootloop disaster symptoms started on april 2018, when the phone boot SLOWLY AS HELL, seriously.. it took about 1-2 hours to boot, and it also shows the (ANDROID IS UPGRADING 0/132 apps) like wtf? , i haven't update or install any new android apps before this symptom happened. So i leave my phone plugged in and wait it to complete the upgrade; then it worked normally as it should. Unfortunately, it happened EVERYTIME i turn my phone on, EVERY SINGLE TIME.. T_T. so i struggled to avoid my phone from running out from battery as i can. This symptom happened for 3 weeks and it got from bad to worse. I wonder what kind of problem is this?
2. The worse part came when my phone is running at high RAM usage, let's say, i game on my phone alot in my spare time, using the ram up to 1800mb everytime i play game or open chrome browser (Lenovo A6000 plus have 2GB ram). When i close/task manager the apps, my phone launcher wont appear normally as it should (long pressing bottom left button) and it FORCED me to restart the phone and suffer the 1-2 hour LONG BOOT. That's unusual, i cleaned my phone regularly (using cleanmaster) and preserve both of my internal and external storage with 3-4GB free space. I wonder what kind of curse is this?
3. So the bootloop disaster finally got me this May when i turn my phone off and tried to reboot. And... no Android is upgrading 0/132 showed up, i waited for 4 hours and reboot my phone again and again and again. And its finally STRANDED on BOOTLOOP :crying:
Im on panic mode when problem 3 happened, then i searched the almighty Google for help, and found that i can backup my data with TWRP recovery, so i do as it said, followed the guides and BACKED UP all of my data.
For once i felt relieved my data is now saved. Now onto the main problem.
I've had enough of this problem so i format the phone into factory reset, wipe the Dalvik ****s, cache, system and data. All of it. thus, making my phone virgin again.
4. Now im trying to resurrect my phone, and tried my effort by downloading Stock Lollipop 5.1.1 OS again along with its prerequisites. I tried to zip-install it using TWRP but it said that "has not switched carriers and cannot be upgraded" i scratched my head and searched almighty Google again then found that i need to do ####6430### thingy before doing that. umm.. so my phone domain need to be changed, how can i do that with a phone who can't boot? (I'm from Singapore btw). What did i do wrong?? did my phone just turned into useless BRICK? but i've read that bricked phone can't even start the recovery, yet my phone still able to start either with Lollipop stock recovery or TWRP (if i adb fastboot it with adb tools from .cmd), so it's not totally fuc.. uh., BRICKED and i got the chance to fix it.
TL;DR
So, Guys.. i desperately need help. i'm a peon both in work and college, and a dead phone will not make a great company for a person like me.
I searched for enlightments and breakthroughs but always ended up failed resurrecting my phone, can you guys PLEASE :crying: tell/give me a SAFE and WORKING walkthrough to re-install my Lenovo A6000 Plus with Lollipop 5.1.1? And does it running a custom OS like those Cynadrogen thingy is good and worthy enough to speed up my phone? is the chances of getting bricked is unavoidable when running custom OS? I thought its going to be easy like reinstalling Windows, but i was wrong.
FYI, my phone now is UNROOTED and running on TWRP 3.0.2 and i can easily revert it back to Lollipop stock recovery if needed (does it considered rooting if i install custom recovery?) I also need a valid info if my phone would never turn like this again if i resurrect it again.
PLEASE HELP ME PEOPLE
THANK YOU.. ! :highfive:
sevenvoldizm said:
Good day everyone, i am going to report my delicate and infuriating problem that has been haunting my head for two months
I'll describe my problem in extreme detail, hoping you guys able to identify this disaster.
My android phone is Lenovo A6000 Plus, i've bought it 2 years ago and it's running on latest Lollipop version 5.1.1 I never alter the system files, since i only use my phone for games and communications, and i'm not really into tinkering android's software. so i use my phone like a normal person, do the updates when the settings asked me, update the apps, etc. and this phone running smoothly in my service. i wanted to ask both WISDOM and HELP in this thread.
1. The Bootloop disaster symptoms started on april 2018, when the phone boot SLOWLY AS HELL, seriously.. it took about 1-2 hours to boot, and it also shows the (ANDROID IS UPGRADING 0/132 apps) like wtf? , i haven't update or install any new android apps before this symptom happened. So i leave my phone plugged in and wait it to complete the upgrade; then it worked normally as it should. Unfortunately, it happened EVERYTIME i turn my phone on, EVERY SINGLE TIME.. T_T. so i struggled to avoid my phone from running out from battery as i can. This symptom happened for 3 weeks and it got from bad to worse. I wonder what kind of problem is this?
2. The worse part came when my phone is running at high RAM usage, let's say, i game on my phone alot in my spare time, using the ram up to 1800mb everytime i play game or open chrome browser (Lenovo A6000 plus have 2GB ram). When i close/task manager the apps, my phone launcher wont appear normally as it should (long pressing bottom left button) and it FORCED me to restart the phone and suffer the 1-2 hour LONG BOOT. That's unusual, i cleaned my phone regularly (using cleanmaster) and preserve both of my internal and external storage with 3-4GB free space. I wonder what kind of curse is this?
3. So the bootloop disaster finally got me this May when i turn my phone off and tried to reboot. And... no Android is upgrading 0/132 showed up, i waited for 4 hours and reboot my phone again and again and again. And its finally STRANDED on BOOTLOOP :crying:
Im on panic mode when problem 3 happened, then i searched the almighty Google for help, and found that i can backup my data with TWRP recovery, so i do as it said, followed the guides and BACKED UP all of my data.
For once i felt relieved my data is now saved. Now onto the main problem.
I've had enough of this problem so i format the phone into factory reset, wipe the Dalvik ****s, cache, system and data. All of it. thus, making my phone virgin again.
4. Now im trying to resurrect my phone, and tried my effort by downloading Stock Lollipop 5.1.1 OS again along with its prerequisites. I tried to zip-install it using TWRP but it said that "has not switched carriers and cannot be upgraded" i scratched my head and searched almighty Google again then found that i need to do ####6430### thingy before doing that. umm.. so my phone domain need to be changed, how can i do that with a phone who can't boot? (I'm from Singapore btw). What did i do wrong?? did my phone just turned into useless BRICK? but i've read that bricked phone can't even start the recovery, yet my phone still able to start either with Lollipop stock recovery or TWRP (if i adb fastboot it with adb tools from .cmd), so it's not totally fuc.. uh., BRICKED and i got the chance to fix it.
TL;DR
So, Guys.. i desperately need help. i'm a peon both in work and college, and a dead phone will not make a great company for a person like me.
I searched for enlightments and breakthroughs but always ended up failed resurrecting my phone, can you guys PLEASE :crying: tell/give me a SAFE and WORKING walkthrough to re-install my Lenovo A6000 Plus with Lollipop 5.1.1? And does it running a custom OS like those Cynadrogen thingy is good and worthy enough to speed up my phone? is the chances of getting bricked is unavoidable when running custom OS? I thought its going to be easy like reinstalling Windows, but i was wrong.
FYI, my phone now is UNROOTED and running on TWRP 3.0.2 and i can easily revert it back to Lollipop stock recovery if needed (does it considered rooting if i install custom recovery?) I also need a valid info if my phone would never turn like this again if i resurrect it again.
PLEASE HELP ME PEOPLE
THANK YOU.. ! :highfive:
Click to expand...
Click to collapse
When 5.1.1 update arrived?
Okay lets get to the point. Just don't panic. You have the stock rom file, extract a file named 'system.zip'. Now go to TWRP, perform advance wipe (wipe dalvik, data, system and cache partitions) and flash that file from TWRP. You'll be on stock rom with a fresh new experience.
---------- Post added at 10:38 PM ---------- Previous post was at 10:33 PM ----------
Custom ROMs are amazing and far better than the stock lenovo rom. Believe me, no one here is using that crap stock rom. You just need some instructions to flash and your phone will get a new life. We are here to assist you.
I bought a used Samsung tab S2 with a working Lineage 17 already installed.
I tried to install stock ROM using ODIN.
The ODIN process seems to work fine; I get a "PASSED" in green in ODIN, but the tablet will not boot. Immediately after the "PASSED" in ODIN, the tablet displays "updating system", then "erasing" for about 20 seconds, tries to reboot, but hangs at "SAMSUNG" screen and will not boot.
I've tried several stock ROMs from from different sources.
I'm not sure about the Android terminology, but I think I can get into "boot" mode, but not "recovery" mode on the tablet.
I'm not familiar with a lot of the terms with tablets/phones, so learning by doing. However, I've successfully flashed many computers(Windows >Linux), Enigma 2 receivers, (much easier process), stick a USB stick in and go. I'm surprised the process of flashing a new ROM on Android devices is not more simplified, or less involved.
Thanks for any help.
I had this issue once, it was after I enabled 'Update Recovery' in Developer Options on LOS 17.1, it's "update the built in recovery with system updates" thinking it was a good idea but after it updated the first time it would boot-loop or hang, cant remember but it wouldn't get to the OS anymore so I had to re-flash it, but I was getting this problem. I remember it all being a mini nightmare at the time, I believe I had to find a PIT file to repartition it. I don't understand how it got so severely busted but I stayed right away from that option since then and the LOS 17.1 has been really great.
I had a similar type thing years back going from 1 type of OS to another, I didn't realise they used different file systems and I had similar issues when trying to fix my mess. Learning then about how different ROMs can depend on completely different file systems taught me that if things are really bad and you can't even flash a stock rom with Odin, then finding and flashing the PIT file is basically guaranteed to fix the issue. It's super rare that this type of thing happens though, so I tend to forget about crazy experiences like watching my new OS delete itself immediately after installing it, I forget about the techniques and tricks, I tend to swear and panic and chase my tail for a while before eventually working it out.
Hi Everyone,
I have been on a rooted Android 10 build for the past 2 years, but found the battery was starting to drain quickly, so decided to upgrade to the latest version 11.
I have rooted phones many times, however im a bit stummped.
Initially when i rooted by flashing with Odin, my patched AP file, it would boot loop the start screen, however today i have got further and it boots to "android starting", but after 3 hours it hasnt moved from that point. I cant imagine this is normal\expected? I have tried to reflash a few times and wiped\factory reset before hand, using the main CSC instead of home_csc, but still the same result.
Any ideas? Am i missing something?
Cheers!
If anyone wants to reply with a potential fix for others, then please do, however for now i have managed to obtain root using a method someone else did on XDA.
Basically, i managed to install and run TWRP, then flashed a kernel in that. Now have an up to date phone with root.
Thanks for anyone who looks at this however.