Hi, i had been on cm 11 and it was running 4.4.2. I had already done an OTA update to get on kitkat, so i wasnt wrried about doing another by cm. So i did the update and when my phone rebooted after it just had finished, the phone doesn't want to start. Its been hanging on the samsung galaxy s4 startup screen and refuses to change. I pulled the battery many times out. What should i do?
Hey can someone please help me out, i cant get on my phone at all.I also did a factory reset data wipe on my recovery and it still hasnt worked.
If your phone is stuck at the screen that reads "Samsung Galaxy S4", then it is probably having trouble booting or reading the system partition. Do you remember what Android version you were on prior to installing CM 11?
Vigz said:
If your phone is stuck at the screen that reads "Samsung Galaxy S4", then it is probably having trouble booting or reading the system partition. Do you remember what Android version you were on prior to installing CM 11?
Click to expand...
Click to collapse
uhmm well i was on i think 4.2.2 the one the samsung has stock. And then i put cm11 and it was like 4.3 and then i got an ota update and i got 4.4.2. I just assumed that getting another would be fine. So i got one today and i did it, but yea thats what happened.
solom200 said:
uhmm well i was on i think 4.2.2 the one the samsung has stock. And then i put cm11 and it was like 4.3 and then i got an ota update and i got 4.4.2. I just assumed that getting another would be fine. So i got one today and i did it, but yea thats what happened.
Click to expand...
Click to collapse
Ok, I think you may have to flash back to Samsung's 4.2.2 firmware and flash CM 11 again via custom recovery.
Here is 4.2.2 tar. Flash it with Odin:
http://k0nane.info/rom/M919UVUAMDL_M919TMBAMDL_TMB.zip
After flashing, you may be stuck on a bootloop. Simply, factory reset/wipe data in recovery mode. This will wipe data and internal storage. Once it boots correctly, download the latest CM11 build.
Vigz said:
Ok, I think you may have to flash back to Samsung's 4.2.2 firmware and flash CM 11 again via custom recovery.
Here is 4.2.2 tar. Flash it with Odin:
http://k0nane.info/rom/M919UVUAMDL_M919TMBAMDL_TMB.zip
After flashing, you may be stuck on a bootloop. Simply, factory reset/wipe data in recovery mode. This will wipe data and internal storage. Once it boots correctly, download the latest CM11 build.
Click to expand...
Click to collapse
uhmmmm...also im on a mac. How should i do that, like how should i bring it back to stock on a mac.
solom200 said:
uhmmmm...also im on a mac. How should i do that, like how should i bring it back to stock on a mac.
Click to expand...
Click to collapse
Oh, I am not sure. You can use JOdin3: https://builds.casual-dev.com/jodin3/
It requires Java. A developer was able to get Odin working and even on a web browser. It might not work due to the large file size of the download, though.
Related
Merry Christmas everyone. I tried to resolve this issue my self but was unable to. I had stock 4.3 rooted and flashed MOAR. MD5 matched. Everything seemed ok but when I flashed, it was stuck on "updating apps" for over 20 min. I did a battery pull. My phone started and I was able to go to TWRP recovery. I did a cache wipe and factory reset with plans of reflashing but everything was gone, including my nandroid. I tried to flash stock firmware from http://samsung-updates.com/ it said "failed". I cannot get back into TWRP. Is there any way I can restore to 4.1.2? Or 4.3? I just want to get the phone working again. Ideally I would like to get root back but my main priority is obviously just to get the phone working. Thank you.
jeppuda said:
Merry Christmas everyone. I tried to resolve this issue my self but was unable to. I had stock 4.3 rooted and flashed MOAR. MD5 matched. Everything seemed ok but when I flashed, it was stuck on "updating apps" for over 20 min. I did a battery pull. My phone started and I was able to go to TWRP recovery. I did a cache wipe and factory reset with plans of reflashing but everything was gone, including my nandroid. I tried to flash stock firmwa.
Click to expand...
Click to collapse
I had a similar bad expreience with updating my rooted S3,
to recover your phone try to get md5 recovery room and install it using odin, try to get the one that called recovery (runs stock 4.0.4) then you can update by Kies to 4.3.
If stock means the Samsung update you need to flash the 4.3 firmware. If stock means the de-Knoxed version from here, I would start by flashing a new recovery image then reinstalling the de-Knoxed one.
Can you not get into any recovery at all?
mjkubba said:
I had a similar bad expreience with updating my rooted S3,
to recover your phone try to get md5 recovery room and install it using odin, try to get the one that called recovery (runs stock 4.0.4) then you can update by Kies to 4.3.
Click to expand...
Click to collapse
MD5 recovery room (or rom I googled both)? I could not find it. I'm sorry i have never done this before...could you post the link for it?
Kevets said:
If stock means the Samsung update you need to flash the 4.3 firmware. If stock means the de-Knoxed version from here, I would start by flashing a new recovery image then reinstalling the de-Knoxed one.
Can you not get into any recovery at all?
Click to expand...
Click to collapse
When I press the volume up, home and power button it says "firmware upgrade encountered an issue. Please select recovery mode in kies and try again."
I installed the de-knoxed version..I would like to go back to the de-knoxed version if possible. Is there a way to flash new recovery image through ODIN...again, I'm not very confident in my abilities right now and don't want to flash anything to make it worse. Would it be possible to send me a link with what to flash. Thank you
Sorry I meant rom not room, but youv still can get it from the dev "room" forums. I got it from there.
sorry I cant post links here yet, i dont have the enough posts, but google "unroot sprint galaxy s3" it's one of he first links and once you get the md5 file you can use it with Odin, it's a simple process.
fixed it
Fixed it, got to keep root also. Flashed a new recovery image through ODIN (link for recovery in case anyone else needs it: http://forum.xda-developers.com/showthread.php?p=38079994). Then flashed ROM. Thanks for your help guys.
Hello guys,
I'm running a i9195 LTE version with CM10.2.3 stable and CWM recovery.
I saw that there were new firmwares available for our phone so I decided to update it, without thinking much. I'm already regretting this decision, as after updating with Odin, the phone rebooted and got stuck at the samsung logo.
What should I do now? The Odin flash went fine, I got the pass at the end..
edit: ok, i can access the recovery. So should I re install CWM and then the rom again?
edit2: i got it, so I should have updated the modem instead of the firmware.. next steps?
If you can go to download mode, you should install CWM recovery again and then the CM ROM again.
Next update the modem only!
luisbraz said:
If you can go to download mode, you should install CWM recovery again and then the CM ROM again.
Next update the modem only!
Click to expand...
Click to collapse
Yup, this is what I did, had to factory reset though.. oh well, lesson learned (hopefully).
You can close the thread.
So I had 4.4 stock TouchWiz, then installed TWRP recovery and CM11. Then I wanted back to stock again but TWRP doesn't seem to want to flash anything. It just says Failed. Tried wiping everything, ended up wiping the OS... just trying to get stock back going.
You have the i747 or i747m?
Twrp cannot flash a stock ROM unless that ROM was compiled to be flashed in twrp.
If you have the 4.3 or 4.4.2 bootloader, do not attempt to downgrade the bootloader.
What bootloader is on your phone?
audit13 said:
You have the i747 or i747m?
Twrp cannot flash a stock ROM unless that ROM was compiled to be flashed in twrp.
If you have the 4.3 or 4.4.2 bootloader, do not attempt to downgrade the bootloader.
What bootloader is on your phone?
Click to expand...
Click to collapse
Sorry, i747 AT&T version.
How do I tell which bootloader I have? When I try to boot it looks stock, just stays on the s3 logo. When I boot into download mode it's a Cyanogen guy.
Last working version of ROM I had was TouchWiz-based 4.1. I found on here but I did have CM11 and stock 4.4. before that.
Did you update your phone via OTA to get to 4.4.2? It's important to know so we can give guidance in terms of what can and cannot be flashed to your phone.
What cyanogen guy do you see in download? You mean the green Android dude?
Do this: copy CM10.2 to your external SD card, boot into TWRP and flash the ROM from the external SD card. If the flash is successful but the ROM gets stuck at the boot animation, boot into TWRP and wipe the cache, dalvik, and reboot.
Sorry for such a late reply! Been messing with other stuff lately, not enough time for my phone..
Anyhow,
audit13 said:
Did you update your phone via OTA to get to 4.4.2? It's important to know so we can give guidance in terms of what can and cannot be flashed to your phone.
Click to expand...
Click to collapse
Yes, I did update to 4.4.2 OTA.
When I boot into download it says bootloader rp swrev 3. When I said earlier I thought I had the cyanogen guy when booting into download mode I had it wrong. Download mode is still just the Android guy. I was talking about recovery which I have TWRP, with the Cyanogen guy (?).
When I just try to reboot the phone regularly it gets stuck on the SIII logo.
I tried installing CM10 like you said from my SD card and the install fails.
Any other ideas of what I can try?
Thanks!!
OK I installed CM11 and that's working.
At least I have a working ROM.
Originally the only reason I tried going back to stock from CM11 was so that I could have access to Galaxy Apps for my Gear 2.
I will fool with going back to stock later possibly.
Thanks again for your help, audit13.
GaggleFree said:
OK I installed CM11 and that's working.
At least I have a working ROM.
Originally the only reason I tried going back to stock from CM11 was so that I could have access to Galaxy Apps for my Gear 2.
I will fool with going back to stock later possibly.
Thanks again for your help, audit13.
Click to expand...
Click to collapse
Not related to your original post but if you dig enough you can probably find a form of Galaxy Apps that'll work on CM11! Or you could possibly rip the APK and get it to work.
This may work for you, but I don't own a Gear 2 so I'm not 100% sure.
http://forum.xda-developers.com/showthread.php?t=2593004
Hello crew, I've recently gotten a Note 4 through sprint. I've been rooting devices since the HTC Magic and have had no bricks. I rooted my Note 4 via Odin 1.85. I flashed the latest twrp and It worked great. This morning my phone was frozen and when I pulled the battery, it boot looped. Figured it was a stock kernel issue with xposed installer. I went back into twrp and it refused to mount the system partition. I can't flash a rom, I can't recover from any of the images I created. I went through the unroot process and flashed the stock recovery back with odin. Now it boots but hangs up at the samsung splash screen for a while then loops. Any ideas? Thank you in advance.
Flash twrp again.
Note 4
w7excursion said:
Flash twrp again.
Click to expand...
Click to collapse
Thank you for the fast response. I did. I tried an older version too just in case it was a bug. No luck. When I used Odin to flash the stock recovery and rom back it starts to boot past the black and white Note 4 screen then gets to the samsung splash screen and it just hangs there. I cleared the cache and did a factory reset in the stock recovery.
If its got oel inside your stuck bro
pbedard said:
If its got oel inside your stuck bro
Click to expand...
Click to collapse
OEL? I don't understand why It won't mount the system partition in twrp. I had no initial issues at all. I even flashed a Cyanogenmod nightly. It's still early and wasn't very stable so I went back to a backup I made. worked fine. I was back to rooted stock. Then the next day it froze and here I am.
pbedard said:
If its got oel inside your stuck bro
Click to expand...
Click to collapse
Yep... OE1... Samsung's latest bit of terrorist activity.
Read through the general and help threads... You'll see.
Try notarized rom (search) and then wait for the next official release (5.1.1?) .
jhill110 said:
Yep... OE1... Samsung's latest bit of terrorist activity.
Read through the general and help threads... You'll see.
Try notarized rom (search) and then wait for the next official release (5.1.1?) .
Click to expand...
Click to collapse
Yea bro I'm on of5 now
And any backups to share hmmmm
Ill see what i csn do
tjgr17 said:
OEL? I don't understand why It won't mount the system partition in twrp. I had no initial issues at all. I even flashed a Cyanogenmod nightly. It's still early and wasn't very stable so I went back to a backup I made. worked fine. I was back to rooted stock. Then the next day it froze and here I am.
Click to expand...
Click to collapse
Flash CF Auto Root through Odin and it will put you back on your last rom that booted.
xxSTARBUCKSxx said:
Flash CF Auto Root through Odin and it will put you back on your last rom that booted.
Click to expand...
Click to collapse
Yes, also noticed OP's Odin 1.85 is old.
To OP: CF Auto Root comes bundled with the recommended Odin. I think we're using 3.07 or 3.09 but 3.07 is recommended to uncheck the auto-boot so user can pull USB and battery after flashing custom recovery over OE1 so it sticks.
I also recommend flashing root tar and rebooting as chain fire recommends. "If you don't get to the red Android logo, boot into recovery manually ("adb reboot recovery", or boot while holding Power+VolUp+Home)."
Once booted, see what build you have.
Sent from my SM-N910P using Tapatalk
I need help get past the Tmobile logo at boot.
SM-N900T
Android 4.4.2
N900TUVUENK3
Performed CF-Auto-Root 2.5 years ago. Ran like a champ until last week when phone got boot stuck on white T-mobile logo.
will not start in Safe Mode - press power till Galaxy Note 3 logo shows up, then vol down. does not start in safe mode
Put in Recovery (power, home, vol up), wiped cache, reboot . still boot stuck at T mobile logo
Put in download mode (power, home, vol down), Re-flashed with Odin3-v3.07.exe CF latest SM-N900T (T-Mobile US): CF-Auto-Root-hltetmo-hltetmo-smn900t.zip , extracted to .tar.md5, still boot stuck
Put in Recovery (power, home, vol up), wipe data/factory reset, then reboot. got past Tmobile white boot screen.
Must keep phone on and not reboot otherwise , I will need to wipe data/factory reset each time to boot and get past Tmobile logo
JJEgan said:
Dont know why you are blaming ROOT .
Suggest you ask in your models forum .
I would wipe phone install stock rom and use SuperSu zip as root after flashing custom recovery .
Click to expand...
Click to collapse
The Latest CF-AUTO-ROOT flashed with Odin installed latest SuperSu v2.82 and has stock recovery with stock rom.
Why is phone stuck at boot? Why install custom recovery, I did not need it before? And if so, Which one? Why would SuperSu zip be needed if latest version is already installed?
My TMo Note3 did the exact same thing last week. (I was still on v4.4.2.) After fiddling with it a little bit, I decided to try a factory-reset. That worked, and then after signing into google, all my apps started to re-download and install. Once that completed, I rebooted and again got stuck at the white TMo screen. Eventually I just bit the bullet and flash-updated it to v5. I disabled auto-installing my apps, and carefully installed just the apps I really wanted, rebooting after a few at a time just to see if I could catch whatever was causing it. But after getting all my apps installed, it's working fine now with no reboot issues.
My personal guess (no direct evidence) is that one of the apps was breaking the bootup somehow.
Looks like I am not the only one having this problem. I don't think this would have suddenly happen. I think there must of have been something with a Samsung update that caused the boot to stick at the Tmobile logo. I am thinking I am just going to have to update from 4.4.2 to 5 and trip my knox. Unless someone else has any other ideas.
Thanks for replying. So you upgraded from 4.4.2 to 5.0. How? What does it matter if you trip Knox if phone is already rooted?
I think cfautoroot will always trip the Knox indicator if the phone is running a 4.3 or newer bootloader.
Tried flashing supersu from twrp to get root?
2Code said:
Thanks for replying. So you upgraded from 4.4.2 to 5.0. How? What does it matter if you trip Knox if phone is already rooted?
Click to expand...
Click to collapse
any ideas here?
2Code said:
any ideas here?
Click to expand...
Click to collapse
I used Samsung's Smart Switch PC. One of the "features" is that it will detect the older Android OS on your phone and offer to install the latest - albeit at the cost of a total wipe and re-flash. (Hence why it recommends you use the app to first back up your phone.) I my case, I had nothing to lose since I couldn't get out of the boot-up screen, and I had already done a factory-reset.
I don't know how this will affect the Knox flag. I never tripped that flag, so I can't say if this will reset it or not.
software_samurai said:
I used Samsung's Smart Switch PC. One of the "features" is that it will detect the older Android OS on your phone and offer to install the latest - albeit at the cost of a total wipe and re-flash. (Hence why it recommends you use the app to first back up your phone.) I my case, I had nothing to lose since I couldn't get out of the boot-up screen, and I had already done a factory-reset.
I don't know how this will affect the Knox flag. I never tripped that flag, so I can't say if this will reset it or not.
Click to expand...
Click to collapse
Thanks software_samurai.
so download the pc version, connect phone, and it will wipe and install Android 5.0
Phone was rooted with CF-autoroot , will phone stay rooted after android upgrade from 4.4 2 to 5.0 ? Or will I need to redo CF-autoroot?
Earlier post indicated that autpupdate of apps may be interfering with boot and is cause of boot stuck at Tmobike logo. Post suggests to install apps one at a time and disable autoupdate of apps. Has one app been identified as suspect app? What other steps should I take to prevent recurrance?
TWRP recovery. Do I need to install it to prevent boot stuck issue? How does it help prevent recurrance of boot stuck issue?
2Code said:
so download the pc version, connect phone, and it will wipe and install Android 5.0
Click to expand...
Click to collapse
yes. it will offer the "upgrade" and if you accept, it will wipe and re-flash with the stock OS.
2Code said:
Phone was rooted with CF-autoroot , will phone stay rooted after android upgrade from 4.4 2 to 5.0 ? Or will I need to redo CF-autoroot?
Click to expand...
Click to collapse
this will wipe the phone and install the stock OS, so no, it will not stay rooted after this.
2Code said:
Earlier post indicated that autpupdate of apps may be interfering with boot and is cause of boot stuck at Tmobike logo. Post suggests to install apps one at a time and disable autoupdate of apps. Has one app been identified as suspect app? What other steps should I take to prevent recurrance?
Click to expand...
Click to collapse
that was my attempt at recovering from a factory reset on 4.4.2. my guess was that one of the apps caused the boot-problem, but I can't be sure.
2Code said:
TWRP recovery. Do I need to install it to prevent boot stuck issue?
Click to expand...
Click to collapse
wiping the phone and re-flashing to stock OS is what I did to avoid the boot-problem. I've got no idea about using TWRP since I've never used it.
2Code said:
How does it help prevent recurrance of boot stuck issue?
Click to expand...
Click to collapse
again, wiping and re-flashing to stock OS should totally clear out any software-related problem.
if your phone has some hardware issue, you're out of luck.
software_samurai said:
this will wipe the phone and install the stock OS, so no, it will not stay rooted after this.
Click to expand...
Click to collapse
Many Thanks for replying.
have you rooted with CF-autoroot after using samsung smarts witch pic to install Android 5.0 and stock rom ? How did it go?
2Code said:
have you rooted with CF-autoroot after using samsung smarts witch pic to install Android 5.0 and stock rom ? How did it go?
Click to expand...
Click to collapse
nope. so far I haven't needed root. Android 5.0 has a (rather clunky) way to handle giving specific apps write access to the sdcard, thus eliminating the only reason I would need root.
Curious, Is installing Android 5.0 using Samsung switch PC same as flashing sambile latest SM-900T firmware https://www.sammobile.com/firmwares/galaxy-note3/SM-N900T/TMB/download/N900TUVSFPL1/120222/ ?
2Code said:
Curious, Is installing Android 5.0 using Samsung switch PC same as flashing sambile latest SM-900T firmware https://www.sammobile.com/firmwares/galaxy-note3/SM-N900T/TMB/download/N900TUVSFPL1/120222/ ?
Click to expand...
Click to collapse
Downloaded latest SM-N900T Android 5.0.1 stock Ron & Kernel and flashed with Odin v3.12. Did not wipe out personal data but lost root.
This,took care of the boot stuck at T-Mobile logo
Re-flashed CF-AUTO root to restore root access.
Hope these steps help somebody.