Novice needs help.
I rooted it two years ago since installed several ROMs. My current ROM is AoCP 7.2.1 KK 4.4.2 (their last version). I have tried to install 4.4.4 ROMs they install fine but gets hung up on the splash screen don't behave right. Using Mr. Cook's ROM cleaner.
Wondering if re-rooting will help. If Yes, do I have un-root and then re-root again? If yes, use ODin?
Thanks.
I doubt that re-rooting will have any helpful effect. Which splash-screen are you referring to? the initial Samsung logo? or the custom firmware logo?
goodjuju said:
Novice needs help.
I rooted it two years ago since installed several ROMs. My current ROM is AoCP 7.2.1 KK 4.4.2 (their last version). I have tried to install 4.4.4 ROMs they install fine but gets hung up on the splash screen don't behave right. Using Mr. Cook's ROM cleaner.
Wondering if re-rooting will help. If Yes, do I have un-root and then re-root again? If yes, use ODin?
Thanks.
Click to expand...
Click to collapse
cyril279 said:
I doubt that re-rooting will have any helpful effect. Which splash-screen are you referring to? the initial Samsung logo? or the custom firmware logo?
Click to expand...
Click to collapse
The Samsung logo. BTW when I reflash AoCP + gApps everything works just fine.
1) What 4.4 firmwares are you having trouble with?
2) What is your process of installation?
goodjuju said:
The Samsung logo. BTW when I reflash AoCP + gApps everything works just fine.
Click to expand...
Click to collapse
cyril279 said:
1) What 4.4 firmwares are you having trouble with?
2) What is your process of installation?
Click to expand...
Click to collapse
1) What 4.4 firmwares are you having trouble with?
AiCP, C-ROM, Slim-Saber (second attempt). First attempt with Slim-Saber the boot image got damaged - you helped me in the Slim-Saber thread. Went back to AoCP 7.2.1 (KK 4.2) all was fine again.
2) What is your process of installation?
Cook's ROM wipe; Install ROM, install gApps.; Boot; if ROM includes CWM restore data from SD card. If TWRP restore from Google. Individually reload the blacklist numbers.
goodjuju said:
[...] if ROM includes CWM restore data from SD card. If TWRP restore from Google.[...]
Click to expand...
Click to collapse
I suspect that the data that you are restoring is boogering up the works. Your current data scenario is setup for AOCP (boots, operates and reboots just fine), and once you flash new firmware, then restore the AOCP data, the firmware doesn't boot correctly?
The best way (IMO) to backup and restore app data is by using titanium backup, or to use titanium backup to extract app data from nandroids.
Your process sounds reasonable up until the restoration of data.
Problem seem to have resolved.
Either the phone was not updating Android or I was being impatient after new ROM. I installed Carbon 4.4 it booted and then went back and re-booted itself and stayed on the Samsung splash screen. It took about 10 minutes before it came back with the Updating Android screen. Now everything seems to be working fine. I could even restore the back-up data from previous ROM. Good thing I got distracted in between and ignored the phone for a while.
Cyril thanks for the advice and patience.
Success
goodjuju said:
Problem seem to have resolved.
Either the phone was not updating Android or I was being impatient after new ROM. I installed Carbon 4.4 it booted and then went back and re-booted itself and stayed on the Samsung splash screen. It took about 10 minutes before it came back with the Updating Android screen. Now everything seems to be working fine. I could even restore the back-up data from previous ROM. Good thing I got distracted in between and ignored the phone for a while.
Cyril thanks for the advice and patience.
Click to expand...
Click to collapse
Never a dull moment with this i777 I had some of the same issues and it does take a while to boot up mine even rebooted itself twice but once its done, Deff! Worth the wait, great Rom and it's even better with https://www.androidfilehost.com/?fid=23610159112653968 Just Rmbr to
Wipe cache/dalvik
Flash Shift
Reboot Recovery
You'll be on the newest kernel and Philz touch.
Then wipe dalvik one more time.
Or what I did was follow cyril279s advice and started all over because I flashed shift kernel after gapps...so
1.rom wipe
2.carbon
3.shift kernel
(Me personally Dalvik again)
4.GApps
(Me personally Dalvik again)
Awesome and you get STweaks
( Me personally again) I installed Xposed before anything else
Related
I've been trying different ROMS and I used SlimROM for awhile until I realized GPS didn't work and my cell connection sucked comapred to TW-based ROMS. Then I tried Hyperdrive which worked at first but every time I would reboot after the first power on after the install, it would stay stuck on the Samsung screen. I reinstalled it time after time (like 6 times) and it would never REboot after the first boot. Every other ROM I've tried installing (Illusion, Synergy, CleanROM) just gets stuck right after the install and they never boot.
I've also noticed that when I try to do a factory wipe after installing anything but SlimROM, I get "error mounting /data" and "error mounting /sdcard/.android_secure".
I've tested installing all of these with the newest verison of TWRP and CWM v6.0.3.2
any ideas?
Factory reset Last option
snowman4839 said:
I've been trying different ROMS and I used SlimROM for awhile until I realized GPS didn't work and my cell connection sucked comapred to TW-based ROMS. Then I tried Hyperdrive which worked at first but every time I would reboot after the first power on after the install, it would stay stuck on the Samsung screen. I reinstalled it time after time (like 6 times) and it would never REboot after the first boot. Every other ROM I've tried installing (Illusion, Synergy, CleanROM) just gets stuck right after the install and they never boot.
I've also noticed that when I try to do a factory wipe after installing anything but SlimROM, I get "error mounting /data" and "error mounting /sdcard/.android_secure".
I've tested installing all of these with the newest verison of TWRP and CWM v6.0.3.2
any ideas?
Click to expand...
Click to collapse
if nothing works, factory-reset but last option.
yeah I just started downloading the stock rom to flash with ODIN in the morning. I just wanted some reason why this would happen so I won't always have have this problem and to know why it only works with some roms over others.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Im having the same problem. I've done a complete ODIN restore to stock like 10 times, while trying Hyperdrive downloaded from 2 sources all with a matching MD5.
I'm on rooted stock right now until someone can figure this out.
I followed the rooting procedure... tried TWRP and Clockwork recoveries... Followed all instructions to the T...
Not sure what else to try... Or what I could be doing wrong... All I can think of now is restoring someones nandroid backup...
Being stuck at the Samsung Galaxy S4 screen sucks...
Zothar said:
Im having the same problem. I've done a complete ODIN restore to stock like 10 times, while trying Hyperdrive downloaded from 2 sources all with a matching MD5.
I'm on rooted stock right now until someone can figure this out.
I followed the rooting procedure... tried TWRP and Clockwork recoveries... Followed all instructions to the T...
Not sure what else to try... Or what I could be doing wrong... All I can think of now is restoring someones nandroid backup...
Being stuck at the Samsung Galaxy S4 screen sucks...
Click to expand...
Click to collapse
I restored to stock using these files http://www.sxtpdevelopers.com/showthread.php?t=237 to flash through ODIN. Rerooted by flashing the older kernel, rooting, installing superSU, then reflashing the newer kernel (normal root procedure). Then I insatlled ROM Manager and gave it root to install CWM recovery. Then I flashed to my same Hyperdrive ROM I was using before and now everything works beautifully. Nothing gets stuck anywhere an no more "cannot mount /data"
Just use that site and restore to stock and everything should work fine.
I'd like to add some confirmation to this. I had similar problems after flashing my first ROM- phone wouldn't reboot a second time, and when I attempted to make nandroids the files would be ridiculously large (~1 TB). I restored to the stock Touchwiz, rerooted normally, and reflashed normally. The strange thing is that I did the rooting and the flashing with the same files I had used the first time, implying something went wrong during the first rooting/flashing process.
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:
I was recently on a rom and today i updated to CM 11, and couldn't make any calls, or texts. I could connect to 4G though which is weird to me... I then went back to beans rom 22 which is 4.1.2 thinking it'll work, but nothing. Can you please help me! Please. I have no idea what baseband i should be on.. thanks
You may have to odin either to a rooted stock rom or a complete odin unrooted stock image to fix it. I had a similar situation and after many attempts I was forced into going back to stock and rerooting and unlocking via adam outlers casual process which is located in the Verizon i605 development section. You will need to know what version you first rooted on and use that odin image to restore. Hoope this helps get yiu in the rigjt direction.
NUKED N2
Just do a factory reset from a touch wiz rom and it wii fix the problem... no need to poison back to stock.
Sent from my SCH-I605 using Tapatalk
I was having this exact same issue and still haven't resolved it. No, restoring to 100% stock does NOT fix the issue.
SJonesGSO said:
I was having this exact same issue and still haven't resolved it. No, restoring to 100% stock does NOT fix the issue.
Click to expand...
Click to collapse
Did you follow and use adam outlers restore thru Odin process back to stock?
NUKED N2
Room?
whos room are you using ? im using sspencer10 and everything is perfect just as a normal 4.4 kitkat very smooth and work 100% perfect u should try it out
If you load a TW ROM, then boot into recovery and wipe everything,then install the TW ROM it should fix it, don't do a restore from a backup as it won't fix it. I have used nephilims latest and it works every time. Also, once you install 4.4 you will probably loses phone and text if you try to install any other rom
Sent from my SCH-I605 using xda app-developers app
I'm in the same boat. Odin'd back to stock Verizon rom, but still no phone or text messaging. LTE works fine though.
After you get your tw rom loaded go into settings and do a factory reset. Do it from settings and not from recovery. You must run through the setup to reprovision your phone do not do a restore and it should fix the problem.
Sent from my SCH-I605 using Tapatalk
N_Jones said:
After you get your tw rom loaded without anything wiringgo into settings and do a factory reset. Do it from settings and not from recovery. You must run through the setup to reprovision your phone do not do a restore and it should fix the problem.
Sent from my SCH-I605 using
Awesome! Thanks man. That worked! I tried so much today but nothing worked. I really appreciate the advice.
Click to expand...
Click to collapse
ran into this issue made attempt to odin back to stock but got stuck at boot now cant communicate phone with computer?any help with next step please!
Hey all, I was wondering if there was an update to this? (Or if anyone else has found something that has worked)
Here is what I have tried so far (and all attempts have failed)...
** All the following attempts at installation used CWM Recovery 6.0.4.3 **
1) Install the ROM (SlimROM 4.4 over 4.3, clean install, wiped cache/data/system/dalvik 3x)
2) Flashed Nandroid of Stock TW ROM (rooted), then installed Slim 4.4 (Clean flash failed, then tried dirty flash, which also failed)
3) Reverted back to stock (The Official VRAMC3), Re-rooted, Installed CWM 6.0.4.3 (Dirty flashed first, which failed. Then did a clean installation, which again failed)
4) Flashed the new MJ9 Modem (with the 4.4 ROM installed), which failed.
Has anyone else had a similar problem, which then fixed it?
Same Issue
N_Jones said:
After you get your tw rom loaded go into settings and do a factory reset. Do it from settings and not from recovery. You must run through the setup to reprovision your phone do not do a restore and it should fix the problem.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Any other advice? This method did not work for me unfortunately.
Any update on this??
The above method did not work for me either.
Hey all, I got it working (the data/network connection that is), with a little effort. Here is what I did in sequence...
1) Reflash the ORIGINAL VRALJB image via ODIN. I used the one found here. You want to make sure you get the one that replaces EVERYTHING, i.e., NOT the alternative restore.
2) I set up my phone and used it normally for about four hours. (This may or may not be necessary, I'm not entirely sure. I also rebooted the phone about five times during that time frame.)
3) I unlocked and rooted the phone via the method outlined here. After that was done, I installed CWM 6.0.4.3 via TWRP (which the unlocking process installs).
4) I then installed CM 11 and the respective Google apps. (I first did a backup, then a factory reset, then cache wipe, then dalvik wipe. The next thing I did was install CM 11, then Gapps.)
5) Restart the phone and success!
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
androidfine16 said:
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
Click to expand...
Click to collapse
I downloaded 5.0. Was NOT satisfied and put KitKat back on. No problems doing that at all but I an NOT rooted.
androidfine16 said:
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
Click to expand...
Click to collapse
I updated via Odin tar file.
About restoring from a nandroid custom recovery backup:
I think/thought I mentioned this in that first thread you linked, but, you cannot in any way restore an old backup onto a new version of android irregardless the device or recovery. Say the system apk, settings apk uses a file named xyz.dat in KitKat, it saves that file to your /data directory. You now go ahead and flash Lollipop which now that same system apk, the settings apk uses a file named yzx.dat, you go and restore your backup restoring the file xyz.dat. Now the settings apk which is a system apk, cannot find this file and runs into a bootloop because not finding the file should never happen but since you went behind its back to remove that file, you confused it majorly.
I use Titanium Backup to restore my apps, best money ever spent.
I personally went back to KitKat, cause, well, I missed xposed more than i thought i would lol. Everything just worked the way I wanted it to with xposed.
I did have to Odin flash a KitKat based ROM in order for it to work though. After that, I restored my full nandroid backup and everything is working again.
My recommendations to you:
1. Take a FULL backup using TWRP or other custom recovery, this includes backing up your system, data, and boot.
2. Flash the Lollipop update using Odin.
3. DO NOT WIPE DATA
4. Reboot.
You should see "android is upgrading" and have a Lollipop build with all your apps still there. i got a few force closes so I ended up wiping my data, but those apps that forced closed were all root apps that were looking for system files that didn't exist anymore.
elesbb said:
I updated via Odin tar file.
About restoring from a nandroid custom recovery backup:
I think/thought I mentioned this in that first thread you linked, but, you cannot in any way restore an old backup onto a new version of android irregardless the device or recovery. Say the system apk, settings apk uses a file named xyz.dat in KitKat, it saves that file to your /data directory. You now go ahead and flash Lollipop which now that same system apk, the settings apk uses a file named yzx.dat, you go and restore your backup restoring the file xyz.dat. Now the settings apk which is a system apk, cannot find this file and runs into a bootloop because not finding the file should never happen but since you went behind its back to remove that file, you confused it majorly.
I use Titanium Backup to restore my apps, best money ever spent.
I personally went back to KitKat, cause, well, I missed xposed more than i thought i would lol. Everything just worked the way I wanted it to with xposed.
I did have to Odin flash a KitKat based ROM in order for it to work though. After that, I restored my full nandroid backup and everything is working again.
My recommendations to you:
1. Take a FULL backup using TWRP or other custom recovery, this includes backing up your system, data, and boot.
2. Flash the Lollipop update using Odin.
3. DO NOT WIPE DATA
4. Reboot.
You should see "android is upgrading" and have a Lollipop build with all your apps still there. i got a few force closes so I ended up wiping my data, but those apps that forced closed were all root apps that were looking for system files that didn't exist anymore.
Click to expand...
Click to collapse
Yeah I avoided lollipop all together. People seem to be having too many problems with it.I installed NK2 via Odin and now rooted/exposed. Runs smooth and I can flash other Roms.
But I do have this one issue. My auto rotation rodent seem to be working I tried everything I can think of. At first boot it works for 10 minutes or 5 sometimes. Than it shuts down completely. Accelerometer isn't working either. No temple run movement or asphalt 8 (sucks). I did sensor firmwate update and ran samsung diagnostic. The sensor seem to be at 0,0 on x and y axis. At first boot they work fine though. Any help please. I even tried different kernel and software Roms to no Vail. And I don't think it's hardware cause it works for brief moments.
Sent from my SM-G900T using XDA Free mobile app
I let the lollipop update happen.. Used the last day and everything seems fine but I can't use Screen mirroring which I use alot.. anyway I downloaded the stock 4.4.2 md5 and odin completely successfully writes it and after it reboots it is stuck at the Tmobile 4gLTE bootscreen.. I've rebooted it and waited a long time.. as well as rewriting. Guess I'll have to download the stock lollipop tar and hope it boots
tri0xinn said:
I let the lollipop update happen.. Used the last day and everything seems fine but I can't use Screen mirroring which I use alot.. anyway I downloaded the stock 4.4.2 md5 and odin completely successfully writes it and after it reboots it is stuck at the Tmobile 4gLTE bootscreen.. I've rebooted it and waited a long time.. as well as rewriting. Guess I'll have to download the stock lollipop tar and hope it boots
Click to expand...
Click to collapse
The 4.4.2 .tar is a "non-wipe" .tar. You need to go into stock recovery and do a factory data reset after flashing.
Did the trick, thanks!
muniz_ri said:
The 4.4.2 .tar is a "non-wipe" .tar. You need to go into stock recovery and do a factory data reset after flashing.
Click to expand...
Click to collapse
Does downgrading like this trips Knox?
Thanks
chiquito3 said:
Does downgrading like this trips Knox?
Thanks
Click to expand...
Click to collapse
I downgraded my wife's phone using the official 4.4.2 firmware from sammobile, and it did NOT trip knox.
Hi,
My phone won’t boot. I see the little greenish circle moving from right to left over the arc. Endlessly. The phone gets warmer.
Samsung S3 i9300
twrp-3.1.0-0
I installed:
lineage-14.1-20170419-nightly-i9300-signed.zip
lineage-14.1-20170426-nightly-i9300-signed.zip
lineage-14.1-20170502-UNOFFICIAL-i9300.zip
every time without error but the phone never boots.
My backup of Android 4.3 restores without problems: phone is working as before.
Two weeks ago I first installed lineage-14.1-20170419-nightly-i9300-signed.zip. Boot successful. Then I saw that I had forgotten to backup my apps with Helium and I had no backup of my contacts. So I restored Android 4.3 and made the backups. After that any install of LineageOS did not lead to a boot-up, only the greenish circle moving from right to left.
I wiped cache, system and data partitions every time before a new attempt.
I tried to find a solution in the many threads but found none.
Am I overlooking something?
Any help appreciated.
Try Completely wiping the partitions and then flashing it using odin.
abhinavp649 said:
Try Completely wiping the partitions and then flashing it using odin.
Click to expand...
Click to collapse
Odin is windows-only. isn't it? I am using xubuntu. Is twrp also ok?
I wiped every time cache, data and system.
BentBit said:
Odin is windows-only. isn't it? I am using xubuntu. Is twrp also ok?
I wiped every time cache, data and system.
Click to expand...
Click to collapse
well, Odin has an alternative variant called jodin for Linux users. cool!! isn't it?
I am just suggesting that if twrp isn't doing it right try using JODIN.
Hi,
I looked at (j)odin; it appeared to be a program originating from Samsung. You can only flash roms which came from Samsung.
I have the latest from Samsung working on my phone: Android 4.3. The newest version 7.1 from LineageOs seems possible to install on my Samsung i9300.
However, I had only the first time I flashed success. See above. Twenty-odd attempts after that all failed although TWRP mentioned that installation was successful.
Please, does anyone know what is wrong with my phone or where I can find more information?
I am at a loss; I searched this forum but cannot find a solution….