After running just about every ROM for this device, I recently flashed my first stock based ROM (cooked 1.8). However since this time I've been unable to flash back to any aosp ROM. I get boot looped on every one. I've tried everything. Yet, I can flash cooked again no problem. I know there's something I'm missing. Any help would be great.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
You have a nandroid backup right? Restore that then flash whatever you want.
Sent from my SGH-I777 using Tapatalk 2
Backup won't boot either. That was my first plan.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Have you tried to format system under mounts and storage after your factory reset, and before you flash your rom and gapps? Just a suggestion. Not sure it will fix you problem or not. It seems as if I had a problem similar to what you are describing after running a Samsung based rom in the past. I believe that was the cure to my issue.
adrock74 said:
Backup won't boot either. That was my first plan.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Search for Siyah kernel v4.3.3 in the forums and install, restart recovery and flash away. Should take care of it.
T
Sent from my SGH-I777 using Tapatalk 2
I always have kept that kernel on standby but that didn't work. I've tried every kernel. Can't believe backups won't even boot. I flashed cook's ROM wipe before his ROM the first time, wonder if that did something.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Try Odin to stock and start from scratch. A lot of work but hey what do you have to lose. :beer:
Sent from my SGH-I777 using xda app-developers app
First find a compatible Kernel for the AOSP ROM your trying to flash. Flash that Kernel.
Second, after the flashing is done, reformat the device; cache, dalkiv cache and system and system settings.
Third, reboot into recovery mode from the recovery menu itself.
Fourth, flash the kernel one more time.
Fifth, flash the AOSP ROM of your choice.
Sixth, reboot back into recovery menu.
Seventh, reformat once more.
Eigth, reboot the device.
As you should know, the first boot up after flashing a ROM takes the longest. Give it like a minute or two.
If this doesn't work, you have to flash a kernel that was compatible with the "cooked" rom you were using. Then from there do a reformat from the recovery menu. Once reformat is done, flash the AOSP kernel, then flash the AOSP ROM right after. Then reformat once more and reboot as normal.
If that doesn't work, flash compatible kernel with the "cooked" ROM your using now and also relay the cooked ROM, and then use Odin to bring it back to stock un-rooted. From there, do as you wish.
Butchr said:
Have you tried to format system under mounts and storage after your factory reset, and before you flash your rom and gapps? Just a suggestion. Not sure it will fix you problem or not. It seems as if I had a problem similar to what you are describing after running a Samsung based rom in the past. I believe that was the cure to my issue.
Click to expand...
Click to collapse
That is exactly what needed to be done. Mr cook actually has another thread with cwm flashable wipe scripts that would have done that. Quite handy :thumbup:
Related
Phone wont sync up email accounts? Stock rom rooted
Sent from my Eris using XDA App
Phone says sync not working try again later :\
Sent from my Eris using XDA App
Also i am getting random htc force closes. Does anyone have a stock rom with root permission? I just restored my first nandroid back up. It seems all the roms i try have issues, maybe its just me :/
Sent from my Eris using XDA App
Have you tried xtrSENSE? It's almost exactly stock. If you Nandroid restore stock you can even flash over stock with just a Dalvik cache wipe and keep all of your apps, settings, etc.
Xtrsence was actually the first rom i ever flashed. It worked great! I tried to flash back to that one but had issues. I have also tried gsb 3.9 and a few others i cant remember.
Sent from my Eris using XDA App
Edit* I dont have a nandroid of stock. Only stock rom with one click root.
Sent from my Eris using XDA App
Well, you can always flash the stock ROM and re-root it.
This is a stock ROM that keeps the custom Recovery: http://forum.xda-developers.com/showthread.php?t=984274 (if you read that first post, it had a link to engtools.zip, which you can then flash to get root on the stock ROM),
The Flashback_21 will bring you back to stock ROM and stock Recovery, which you can then re-root with the 1-click app (the one without the radio is fine): http://forum.xda-developers.com/showthread.php?t=792026
Since you are having data issues, I'd wipe data/factory reset before flashing either one.
Quick question I have been unable to get a rom to install on slot 1 of boot manager i was close but at the end I got error: unable to create new boot.img... So close. I am running 3.14.605.10 firmware, s off, viperrez. I on boot manager I have small image selected, screen force on, and ext4 selected any help would be appreciated. Oh and I tried doing cm9 and also neomax roms on slot 1
Sent from my ADR6425LVW using xda app-developers app
Bump
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Bump
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Same problem here. I don't know what is causing the problem but I read somewhere that a work around for the boot manager problem is to restore nandroids to each slot. Just make a nandroid of your current ROM, wipe device, install new ROM, set it up and make a nandroid of the new ROM. Do this for each ROM you want to use in boot manager. Once that is done restore whatever ROM you want to be the phone ROM using regular recovery. Once that boots open boot manager (follow instructions) and restore each nandroid to adifferent slot. I'm trying now.
motenak said:
Same problem here. I don't know what is causing the problem but I read somewhere that a work around for the boot manager problem is to restore nandroids to each slot. Just make a nandroid of your current ROM, wipe device, install new ROM, set it up and make a nandroid of the new ROM. Do this for each ROM you want to use in boot manager. Once that is done restore whatever ROM you want to be the phone ROM using regular recovery. Once that boots open boot manager (follow instructions) and restore each nandroid to adifferent slot. I'm trying now.
Click to expand...
Click to collapse
Yeah. That was my last resort lol ill try it out also, good luck!
Edit: no dice still get the error building boot.img
Sent from my ADR6425LVW using xda app-developers app
So, I've been on 10.1 for a while, and ever since, I can not Reboot to Recovery using normal options.
The only way I can get in to recovery is to open Rom Manager, flash recovery, then reboot recovery from INSIDE rom manager.
No other way works.
It's kind of annoying. I decided today to flash back to stock using ODIN and start fresh again.
From stock, I install CM7. I can reboot to recovery using CM7 no problem.
From CM7, I install CM10.1 nightly (the latest), and after the phone finally gets in to 10.1, I can no longer reboot to recovery from the reboot menu.
I have to install Rom Manager, then flash recovery from it, then reboot from it.
I have to do this process EVERY time I want to reboot recovery.
Any other way I try, it just reboots normally and not in to recovery.
What gives? Anyone else with this problem?
Thanks.
I just tried to use Terminal Emulator and that fails as well.
su
reboot recovery
It just reboots normal.
Have you tried using any other 4.2.1 ROMs?
Sent from my SGH-T959 using xda app-developers app
No, i haven't.
Well then try like hellybean
Sent from my SGH-T959 using xda app-developers app
You should expect to run into problems when using a "nightly" build ROM. Its practically beta stages, find a ROM that is complete like the poster above mentioned. Cant really recommend any 4.2.ROMS , I stick with froyo ROMS for better performance.
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
You should expect to run into problems when using a "nightly" build ROM. Its practically beta stages, find a ROM that is complete like the poster above mentioned. Cant really recommend any 4.2.ROMS , I stick with froyo ROMS for better performance.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
The reason why I recommended that is because he was on a 4.2 ROM that he was having problems with. Sometimes its painful to go to a lower ROM as far as looks and speed goes therefore I recommended a 4.2 that he could try
Sent from my SGH-T959 using xda app-developers app
No one else using this rom has this problem.
dE.fUsEd said:
No one else using this rom has this problem.
Click to expand...
Click to collapse
Well some phones do actually have random differences. On aokp milestone 6 I had to use a linario build because me and like two other people werwbt getting signal
Sent from my SGH-T959 using xda app-developers app
Still having this problem. Using multiple roms. Now I'm on Baked 4.2.2.
Still can't boot to recovery.
This is annoying as hell.
And the all have the same green leaf for a home screen, so are my ROMS not being written to the right place or what. this is getting confusing. the ROM form about shows the different versions but all are skipping the setup and I have no 3G/LTE connection, only wifi.
Whatever I am doing I seem to be consistent about it
Did you flash gapps?
Sent from my GT-P7500 using XDA Premium HD app
eushaun99 said:
Did you flash gapps?
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
the AOPK had gapps folded in. what is odd is I have now tried AOPK and a CM10 and CM10.1 and they all seem to have the same start screen, come up after the boot like it is already installed, missing any 3G/4G connection. Now I have flashed back to EG01 and run up though iCS several times and it isn't taking the CWM now, says it installs ok but boots into stock recovery. Now I using the older CWM 5504 for the i-905 and it writes somewhere, but apparently not where it should be. I was going to try TWRP but that doens't appear to run on HC/ICS - is it JB only? I have shied away from the newer CWM for a long time because for a while they just seemed to boot-loop the tablet.
Any one have a suggested working version of CWM? This starting from scratch and rolling in all the updates is getting old - which is why I was wondering if there is a way to build my own ODIN set to just flash back to this point without having to go though reroot and install of the recovery (which apparently now I am not able to do - wts! )
Thanks!
Rob (lost) in Katy.
Twrp is compatible with ICS too, if im not mistaken. Go to www.droidbasement.com and download pershoots's version of cwm recovery. That should work just fine. BTW, you did make a full wipe (system, data, cache, dalvik) right? And what's EG01?
Sent from my GT-P7500 using XDA Premium HD app
eushaun99 said:
Twrp is compatible with ICS too, if im not mistaken. Go to www.droidbasement.com and download pershoots's version of cwm recovery. That should work just fine. BTW, you did make a full wipe (system, data, cache, dalvik) right? And what's EG01?
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
I am now one cycle 15 and doing the last update to 4.04. every stinking rom I load goes back to the factory or the ROM starts off and ignores the setup. The really annoying thing is I have had all this setup and working before. Ahhhhhh!
rgranger said:
I am now one cycle 15 and doing the last update to 4.04. every stinking rom I load goes back to the factory or the ROM starts off and ignores the setup. The really annoying thing is I have had all this setup and working before. Ahhhhhh!
Click to expand...
Click to collapse
Ok, i found another recovery laying around that seems to be working. I also found that the bug where you need to delete the script that deletes the new recovery. Once I got that far things started making sense. I guess whatever mod I was on before didn't need it. The next trick will be trynig to decifer how to do an odin backup so that I don't haver to roll though 4/5 upgrades to get here. I know someone is doing it. thanks for the help and a place to bounce ideas. will update if i come up with anything.
Rob
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Markstache said:
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Click to expand...
Click to collapse
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I've done that so many times.
Markstache said:
I've done that so many times.
Click to expand...
Click to collapse
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Yea that's what I said before too but the op said they've done that many times with no luck...
Sent from my SCH-I545 using Tapatalk
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
That's what I would have figured would fix it, because I'm pretty sure that's supposed to wipe /boot, but I found out I cannot flash kernels on my phone for some reason and when having to fix softbricks while experimenting with why it doesn't work and flashing different kernels, I had to do that whole process so many times I can go from softbrick back to where I'm at now in about 20 minutes.
Is your device in factory mode when using touchwiz roms?
jamesd1085 said:
Is your device in factory mode when using touchwiz roms?
Click to expand...
Click to collapse
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
jamesd1085 said:
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
Click to expand...
Click to collapse
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
Definitely don't delete your efs folder. Actually it's good practice to back it up
Sent from my SCH-I545 using Tapatalk
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
No!!!!...you will lose your number and all data capability...just wanted to make sure everything was still mounting properly... I'm at a loss as to what else could be causing your issues
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
I'd find someone like Philz or a TWRP compiler to ask if u haven't already gone that route. I'm sure one of them will know. Hopefully [emoji41]
Sent from my SCH-I545 using Tapatalk
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Markstache said:
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Click to expand...
Click to collapse
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
^^^this should fix you up...but backup everything you can to external SD or computer...when it says full wipe its no joke
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Markstache said:
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Click to expand...
Click to collapse
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As in installing a KT kernel after rooting and having a custom recovery and ROM on my phone. Right now I have three 3/22 nightly cyanogen up and running but as soon as I install kt it trips the Verizon security and on have to flash back to stock kernel to use my phone. Booting into Odin and canceling out to restart does not let me get past the yellow triangle