I was able to downgrade the phone to NB1 and root it with Towelroot, and used Safestrap in order to get recovery on the device.
After that, I booted into recovery and installed the GPE 5.0.1 ROM.: http://galaxys4root.com/t-mobile-galaxy-s4-roms/gpe-android-5-0-1-lollipop-rom-for-galaxy-s4/
Now the phone will not go past the S4 splash page, reboots and then goes into the stock recovery. Ive tried factory reset, clearing cache and removing the battery.
Any help is appreciated. I bought this phone for my fiance and am wanting to give it to her soon as a present.
Thank you so much in advance.
I think the problem is that you downgraded.
GDReaper said:
I think the problem is that you downgraded.
Click to expand...
Click to collapse
I couldnt install towelroot on the 4.4.4 version it came with since it said device wasnt supported.
I was following these instructions: http://www.droidviews.com/root-att-galaxy-s4-sgh-i337-android-4-4-4-kitkat-firmware-i337ucufnj4/
It states to downgrade, then root, then go back to the 4.4.4. I thought after the steps I took, I could go straight to a custom ROM.
Thanks
I used CF-Auto-Root to root my device. Since towelroot didn't work for me either.
Maybe the rom did not flash right. Try flashing again.
problem in installing lollipop rom india to samsung i9500
I have installed the newly released lollipop rom to my samsung i9500 through odin. it was successfully flashed but the phone cant restart, it stuck with samsung written on the screen and blue light on...what i should do???
Related
Phone: Samsung Galaxy S4 ATT I337UCUAMDL
Model Number in settings on 4.4 ROM = GT-I9505G
As the title says, I installed dandroid's newest 4.4 ROM from WICKED v5 4.2.2 and lost root. So I attempted to update my CWM Recovery from Odus 1x to the newest using Odin which failed do to write protected I suppose all though others says that doesnt effect their installs.
Where I'm at:
Cannot boot into recovery, says booting recovery the just reboots and enters Dandroid's ROM w/o root.
I'm now lost and have been reading the forums for hours. Currently downloading STOCK Samsung firmware for my device I337UCUAMDL_I337ATTAMDL_ATT.zip
CASUAL failed.
What do I need to do to get back to WORKING custom recovery w/ rooted dandriod 4.4 kitkat rom. Should I use Odin and flash stock rom then motochopper to root and try to reinstall working CWM recovery?
Please advise best course of action. My phone had been working properly with every ROM I tried before update to 4.4 ROM and attempted CWM recovery update (thinking that would fix my root issue). Thanks all!
If you have a nandroid, and I hope you do, just restore that in your custom recovery. If you don't, then you're going to have to return to stock with odin
Tried motochopper on the phone as it sits and it fails as well.
I have a stock backup but the problem is I no longer have access to any recovery. Guess I'm just gonna have to flash the stock firmware with Odin when its finished downloading and start over.
Just finished Odin flash back to samsung factory firmware. Phone stuck at att world logo on bootup, still can't access recovery. Any ideas?
GSXRspike said:
Just finished Odin flash back to samsung factory firmware. Phone stuck at att world logo on bootup, still can't access recovery. Any ideas?
Click to expand...
Click to collapse
If you flashed Odin successfully you can get into recovery.
Finally got into recovery it rebooted 3 times but just holding the req. buttons finally got me in.
Back on factory firmware and rooted w/ cwm recovery all back in place properly worrking.
I would like to use the Dandroid 4.4 ROM with this device. When I install am I going to lose root again and if so, how I do I get it back on this device since the model in the settings is going to change from I337 to I9505G after installing this ROM?
Figured it all out last night, re-flashed Dandroid's latest ROM which still caused me to loose root, then flashed SuperSU 1.51 instead of 1.80 and regained root. All is right in the world now.
GSXRspike said:
Figured it all out last night, re-flashed Dandroid's latest ROM which still caused me to loose root, then flashed SuperSU 1.51 instead of 1.80 and regained root. All is right in the world now.
Click to expand...
Click to collapse
Hey, if you dont mind me asking where did you get the 1.51 zip to flash? I'm having a similar issues with same ROM where i lost root but have recovery access.
Thanks
Update: Found the file. Flashed it. Root is back. Have you let market update it automatically? If so did you lose root afterwords?
Hi there,
Long time lurker on the forums here, and have been browsing around the whole day to find a solution to my problems without luck .
Yeasterday I received my Galaxy Note 3 (N900T), but I had very poor reception, I thought this was because the N900T was appearantly a US model which I wasn't aware of, but since hardware was the same I decided a custom rom might fix things up.
I installed the latest CM 11 nightly and appropriate google apps but without any luck (reception still bad)
Then I decided to install the origional 4.4.2 firmware for T-mobile N900T, now the reception and everything works just fine, but I get a bunch of errors that google app x (youtube, playstore etc) have stopped working, so I get alot of these pop-ups and can't use the playstore.
I thought: Ok I just need to install the latest Gapps for the 4.4.2 version, there's where the problem comes in. When I booted into recovery it would boot into the standard android recovery and not CWM recovery. I couldn't do anything in the normal recovery mode to install gapps. So I managed to download the rom manager through my browser and just installed that without the playstore, after this i installed the recovery, found out my root was undone after the patch.
I then downloaded the chainfire thingy and flashed it with odin, which all worked fine and I managed to root my phone again. When opening SuperSU it says there was some 'KNOX thingies remaining which I said ok take away. After this I installed the CWM recovery, and said: Launch ClockworkMod recovery so I could install the new version of Gapps there. However: This is where it gets stuck in a loop trying to launch the bootloader, and I was unable to get into the bootloader. The only way to stop the bootloader loop was to take out the battery, boot into download mode and cancel the download mode after which my phone would continue to boot normally.
After this I tried to flash the 4.3 version of android with odin, and even reflashing the current 4.4.2 version, but I can't flash any roms with odin anymore as it gives me the Fail! Auth. error everytime in odin.
If anybody could help me that would be greatly appreciated!
Just to clarify:
I am still working on this, I downloaded Goomanager and installed TWRP recovery, but no luck, my phone will simply get stuck in a loop when i try to boot it into recovery. I can still startup my phone normally, but it's quite useless without gapps.
Thanks in advance for any assistance, I really feel lost on this one :/
Maybe its too late but I wonder if it would have helped if you install another kernel when you had CM11. Maybe that would have had solve the problems with the reception? I'm a total noob at this, so I don't know, its just something that I thought of.
grafgever said:
Just to clarify:
I am still working on this, I downloaded Goomanager and installed TWRP recovery, but no luck, my phone will simply get stuck in a loop when i try to boot it into recovery. I can still startup my phone normally, but it's quite useless without gapps.
Thanks in advance for any assistance, I really feel lost on this one :/
Click to expand...
Click to collapse
Not sure but when i upgraded my N9006 to KitKat and tried to root it using cf-auto-root for my phone it went into a boot loop. I ended up using the one designed for N9005 as it specifically stated it was made for the 4.4 boot loader. I'm guessing the other ones are for 4.3?
locn said:
Not sure but when i upgraded my N9006 to KitKat and tried to root it using cf-auto-root for my phone it went into a boot loop. I ended up using the one designed for N9005 as it specifically stated it was made for the 4.4 boot loader. I'm guessing the other ones are for 4.3?
Click to expand...
Click to collapse
I managed to flash the philz recovery with odin, I got the phone working now, except when I make a call I'll loose all mobile network signal afterwards. Unsure how to solve this. Could I flash a European stock firmware to my n900t?
So its been a while since I tried flashing and rooting....HTC Evo while.
My Problem: Tried installing custom recovery (TWRP), when it rebooted it is stuck on Samsung logo screen.
Tried through Odin flashing the stock firmware nothing...
My S4 is older from earlier 2013, but I`ve done all the OTA updates.
Any ideas or suggestions?
Agent Droid said:
So its been a while since I tried flashing and rooting....HTC Evo while.
My Problem: Tried installing custom recovery (TWRP), when it rebooted it is stuck on Samsung logo screen.
Tried through Odin flashing the stock firmware nothing...
My S4 is older from earlier 2013, but I`ve done all the OTA updates.
Any ideas or suggestions?
Click to expand...
Click to collapse
Don't think you can revert back to older than NAE if that was your last ota. Flash stock NAE. Did you use cfautoroot? Guess knowing exactly what you did before the problem might help narrow it down
pontif said:
Don't think you can revert back to older than NAE if that was your last ota. Flash stock NAE. Did you use cfautoroot? Guess knowing exactly what you did before the problem might help narrow it down
Click to expand...
Click to collapse
I finally got it fixed and going. I did use CFAUTOROOT, which seemed to work okay, gave me the super user app. It was the recovery i keep having problems, when i tried to flash a rom it just gets stuck in bootloop.
Ok so I'd like to put AllianceROM on my international version SM-G900F H3G UK model.
To do so, my plan is to downgrade lollipop to 4.4.2 stock, root with TowelRoot, then install the ROM through Mobile Odin Pro (to preserve the KNOX counter). I've just tried to flash 4.4.2 onto the phone, but I cannot get it to start at all after it's flashed. The phone just hangs on the Three (H3G) boot animation.
I'm hoping that I've just got confused with the Sammobile site and that I've just flashed the wrong 4.4.2 firmware (so far tried flashing ANG2 and ANE2). Something I should have checked earlier but I just thought they were updated versions of the same ROM).
If I can't successfully boot into 4.4.2, I'd like to try flashing lollipop to retrieve some files I forgot to backup (another silly mistake). I'm not sure whether I can take files off it through the ADB sideload or whatever but if I have to lose all my data then I'm not too bothered.
What's the best way to go about my situation?
Any help would be greatly appreciated.
Boot to recovery and factory reset
*Detection* said:
Boot to recovery and factory reset
Click to expand...
Click to collapse
Right, thanks man. After flashing lollipop, I can now boot up and back up stuff. I'll flash 4.2.2 again and factory reset.
Hello all,
I am looking for some advice, on getting my AT&T Samsung Galaxy S4 working again. I will keep this as short as I can:
I originally had 4.3 rooted with the MK2 firmware, and used Odin to flash my phone to 4.4 NB1, using the ROM in the Guide to Stock/Updating/Rooting thread.
This worked fine, and I was able to boot and use the phone, but my root access was gone.
I tried Towelroot, Kingo, etc... to no success.
I then followed http://forum.xda-developers.com/showthread.php?t=2692825 thread to semi downgrade to MK2 and was able to obtain root again. I also installed Safestrap recovery.
At this point I could not successfully boot back into the phone, though I could access Safestrap.
I flashed the stock kernel for NB1 again, but still could not boot.
I then flashed the stock NB1 ROM again.
After this, the phone would show the android icon and a progress bar, then restart, reach the Samsung load screen, start the AT&T load screen and then boot loop.
Once I reached this point, I could no longer access recovery, only download mode.
In my attempts since then. I've found if I stop the phone from ever getting to the Samsung load screen after flashing the stock ROM, I can then access recovery. As soon as I let it boot, I cannot access recovery.
I've flashed the stock ROM multiple times at this point, gotten into recovery and wiped the devices then rebooted multiple times.
I just don't know what else I can do.
Does anyone have any ideas? A place to look? Any help appreciated!