Hello all I need your help please. I followed droidstyles guide on how to go to ics roms (Sect 4) did everything step by step but everytime i try to flas any ics rom it bootloops. I am currently on cm7 that comes with the section 4 and it is working fine . but I download ics rom go to recovery wipe all 3 flash roms and they load but get stuck at boot up . aokp just shows aokp and unicorn over and over , ths just shows cynoagen mod 9 over and over i have let both set for 30 minutes but they never boot up . can some one tell me what im dong wrong . thanks
Try wiping /system (in mounts and storage) and re-installing teamhacksung build 1. Also, you're not three-fingering into recovery, are you?
I read not to do the three finger on ics so im not doing that . I havent tried wiping system i will try that . I also am on teamhacksung build2 download thats the one droidstyle said he had the best luck with . I will let you know if wiping system works. Thanks for your help.
Try Teamhacksung Build 1.
tsmith1296 said:
I read not to do the three finger on ics so im not doing that . I havent tried wiping system i will try that . I also am on teamhacksung build2 download thats the one droidstyle said he had the best luck with . I will let you know if wiping system works. Thanks for your help.
Click to expand...
Click to collapse
actually I always use build 1, but more people seem to have better luck with build 2...also some have success going right from stock to the latest ICS rom. If all else fails you might look into reformatting and possible even replacing your sd card.
Tried the build one and it worked! Thanks guys now running aokp! Love it . Thanks again for your help
Sent from my SCH-I500 using XDA
I am in the same boat. I just flashed to the newest Devil kernal. Rebooted from recovery and it is now stuck with the "samsung" boot loop. Any ideas on how to get into recovery now?
Can you three-finger into recovery? If so, follow section 9 of Droidstyle's guide.
jadams161 said:
I am in the same boat. I just flashed to the newest Devil kernal. Rebooted from recovery and it is now stuck with the "samsung" boot loop. Any ideas on how to get into recovery now?
Click to expand...
Click to collapse
odin cwm4 fixed, three finger into recovery, wipe both caches, flash a older devil kernel or stephens .85 build in the aokp thread.
Can't 3-finger AOKP. I ended up having to ODIN back to stock and start over. Kinda new at this stuff. I loaded AOKP build 40 with devil .81 and it is running now. I am going to flash Devil .90 today and check that out. Just trying to keep the fassy going until my SGS3 comes in.
Thanks for the help guys.
---------- Post added at 10:57 AM ---------- Previous post was at 10:03 AM ----------
Ok, so I just flashed Devil .90 kernal and it installed perfect. Device is fast and so far stable.
jadams161 said:
Can't 3-finger AOKP. I ended up having to ODIN back to stock and start over. Kinda new at this stuff. I loaded AOKP build 40 with devil .81 and it is running now. I am going to flash Devil .90 today and check that out. Just trying to keep the fassy going until my SGS3 comes in.
Thanks for the help guys.
---------- Post added at 10:57 AM ---------- Previous post was at 10:03 AM ----------
Ok, so I just flashed Devil .90 kernal and it installed perfect. Device is fast and so far stable.
Click to expand...
Click to collapse
any reason you decided to disregard my lat post? That would of saved you from needing to go all the way back to stock.
I was already committed to ODIN prior to your response. Just being impatient I guess. Up side is that it gives me practice learning how to ODIN and flash correctly. Thanks tho for the help.
jadams161 said:
I was already committed to ODIN prior to your response. Just being impatient I guess. Up side is that it gives me practice learning how to ODIN and flash correctly. Thanks tho for the help.
Click to expand...
Click to collapse
no problem!!
Related
i would post in the dev forum but it still says that i am a new member even though i have been here for months. I just dont post..no issues before. Ok....so i rooted my evo3d..perfect. I go to install viper 1.3 and it appears to go through as it should. I dodnt get any error messages. Someting is wrong though. It just keeps rebooting to recovery right after white HTC splash screen. I have team win recovery with stock kernel. I wiped EVERYTHING numerous times. Help please. Can someone get this tp viper or repost to the viper dev thread. I really need help
blacjac30 said:
i would post in the dev forum but it still says that i am a new member even though i have been here for months. I just dont post..no issues before. Ok....so i rooted my evo3d..perfect. I go to install viper 1.3 and it appears to go through as it should. I dodnt get any error messages. Someting is wrong though. It just keeps rebooting to recovery right after white HTC splash screen. I have team win recovery with stock kernel. I wiped EVERYTHING numerous times. Help please. Can someone get this tp viper or repost to the viper dev thread. I really need help
Click to expand...
Click to collapse
Your post is pretty vague regarding the circumstances of your problem.
Get the md5 checksum for the ROM, and check it with an md5 checker app. I have been using hashdroid from the market. Or you can get a freeware app for your pc, just Google it.
Alternatively, download the ROM again. And double check the OP's installation instructions.
Sent from my PG86100 using XDA App
Try getting superwipe, or you can go into recovery and format boot, system, data and cache. Unless you have tried this before I'm betting it will solve your problems. Hope this helps. +1 on doublechecking the md5 I never do but it might well b a bad download. I'd still recommend the formatting as this will ensure everything is erased and you are starting fresh.
Transformer Sent
Just download the ROM again. Full wipe and reinstall. You should be fine.
Get a crow-bar, a hammer n some duct tape.... Carefully insert... Nevermind just do what they said.
Sent from 3D A.W.E.S.O.M-O
blacjac30 said:
i would post in the dev forum but it still says that i am a new member even though i have been here for months. I just dont post..no issues before. Ok....so i rooted my evo3d..perfect. I go to install viper 1.3 and it appears to go through as it should. I dodnt get any error messages. Someting is wrong though. It just keeps rebooting to recovery right after white HTC splash screen. I have team win recovery with stock kernel. I wiped EVERYTHING numerous times. Help please. Can someone get this tp viper or repost to the viper dev thread. I really need help
Click to expand...
Click to collapse
I have the same issue, post it in the ViperRom post but basically everyone said never seen it before and suggested all that has been suggested here. I went through all that: re downloading, checking the M5d, even formatting my SD card.
Kept trying till I found out that it is a Kernel issue, my phone doesn't seem to like the stock kernel with that Rom ( the only Rom with the issue), I finally tried showDown Kernel just to test it and that worked, now I am currently using it with natarchy Kernel.
Hopefully this will help you.
try usin CWM recovery i ran viper for awhile no problems in CWM
Adel_2 said:
I have the same issue, post it in the ViperRom post but basically everyone said never seen it before and suggested all that has been suggested here. I went through all that: re downloading, checking the M5d, even formatting my SD card.
Kept trying till I found out that it is a Kernel issue, my phone doesn't seem to like the stock kernel with that Rom ( the only Rom with the issue), I finally tried showDown Kernel just to test it and that worked, now I am currently using it with natarchy Kernel.
Hopefully this will help you.
Click to expand...
Click to collapse
That kind of doesnt make sense cause viper includes its own kernel (stock) so whatever kernel you have will be overwritten with that kernel when you flash viperom.. But good you got it fixed.
aznmode said:
That kind of doesnt make sense cause viper includes its own kernel (stock) so whatever kernel you have will be overwritten with that kernel when you flash viperom.. But good you got it fixed.
Click to expand...
Click to collapse
I overrode the included kernel with another one after flashing the rom.
Another way after it tries to start I pull the battery, push the volume down then power it up to get back to recovery and flash another kernel that works, that is the only way it works for me now.
Sent from my PG86100 using XDA Premium App
Okay I have been trying to get a CM9 rom to boot on my Atrix for about a week now. I am coming from Nottachtrix 1.3.1 on radio 37p with faux GB24 kernel. My bootloader is unlocked and I perform all necessary wipes before install. The furthest I have gotten any of the CM9 roms to boot is the screen that states Android Apps(or something) updateing. It then states starting system and boots back to the booting logo. I have tried fastboot -w. Formating data, cache, system, osh, pre install in mounts storage menu, and clearing both caches before and after install and I get the same results. This only happens with CM9 roms. I cannot get the CNA, Jokers, Turls, or Atrix tablet past the screen stated. I have tried with the latest rom racer from http://forum.xda-developers.com/showthread.php?t=1204500 and both recovery and touch recovery from rom manager and I get the same results. I have posted my issue in the dev section, but decided this was better as I did not want to clutter up the dev forum with my problems. Could it just be my Atrix or would the 37p radio have something to do with the bootlooping issue. Any help would be very much appreciated.
For some odd reason I decided to pull my external SD card before boot, and freaking BOOM BANG POW NO BOOTLOOP!
htcslic said:
Okay I have been trying to get a CM9 rom to boot on my Atrix for about a week now. I am coming from Nottachtrix 1.3.1 on radio 37p with faux GB24 kernel. My bootloader is unlocked and I perform all necessary wipes before install. The furthest I have gotten any of the CM9 roms to boot is the screen that states Android Apps(or something) updateing. It then states starting system and boots back to the booting logo. I have tried fastboot -w. Formating data, cache, system, osh, pre install in mounts storage menu, and clearing both caches before and after install and I get the same results. This only happens with CM9 roms. I cannot get the CNA, Jokers, Turls, or Atrix tablet past the screen stated. I have tried with the latest rom racer from http://forum.xda-developers.com/showthread.php?t=1204500 and both recovery and touch recovery from rom manager and I get the same results. I have posted my issue in the dev section, but decided this was better as I did not want to clutter up the dev forum with my problems. Could it just be my Atrix or would the 37p radio have something to do with the bootlooping issue. Any help would be very much appreciated.
Click to expand...
Click to collapse
Did you flash twice ?
Sent from my MB860 using XDA
I believe the problem is with the radio, I had this issue (on stock radio), then I upgraded to the newest CM9 Kang (0.4.4) and it went away. I then flashed the 37p radio in an attempt to fix a problem I've been having with my WiFi and bluetooth (they both don't work and cause reboots, I assume now it's a hardware problem) and the boot loop came back. I'm gonna try flashing some other radios to see if that works.
Yes flashed twice to no avail. Gonna try the 36p radio and stock to see if that fixes my issue.
Sent from my Wettest Dream Atrix!
giqbal said:
Did you flash twice ?
Sent from my MB860 using XDA
Click to expand...
Click to collapse
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
CaelanT said:
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Trust me, the CM9 kang (not turl's version, haven't tried that) didn't work unless you flashed it twice up to version 0.4.2 (I skipped 0.4.3 and installed 0.4.4 straight without wiping and only flashed once and it worked, so it's possible they fixed the bug). I don't think anyone knows why, but it's been confirmed many times.
CaelanT said:
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
That is what I am hoping, but I have tried every procedure I could find within the forums. Your start to finish is gonna be my last hope.
So I followed the same steps I use for other roms and managed to get this one working http://forum.xda-developers.com/showthread.php?t=1580449
Hey CaelanT any luck on getting me a step by step.
hitmannumber47 said:
Trust me, the CM9 kang (not turl's version, haven't tried that) didn't work unless you flashed it twice up to version 0.4.2 (I skipped 0.4.3 and installed 0.4.4 straight without wiping and only flashed once and it worked, so it's possible they fixed the bug). I don't think anyone knows why, but it's been confirmed many times.
Click to expand...
Click to collapse
Haven't had to do that with jokersax, turl, or CNA versions.
---------- Post added at 12:24 PM ---------- Previous post was at 12:24 PM ----------
htcslic said:
Hey CaelanT any luck on getting me a step by step.
Click to expand...
Click to collapse
Thanks for reminding me. Will get something to you here in a few!
<edit> Check your messages!
Gonna give it a shot soon as I get off work.
EDIT:
Unfortunately that was a no go as well. Followed everything to a tee and tried different kernels. I can only get the AOKP rom to boot, but its is currently without USB storage. Does anyone know a difference in the roms that would cause my Atrix to boot on one and not the other. I can also manage to get the MIUI to boot.
htcslic said:
Gonna give it a shot soon as I get off work.
EDIT:
Unfortunately that was a no go as well. Followed everything to a tee and tried different kernels. I can only get the AOKP rom to boot, but its is currently without USB storage. Does anyone know a difference in the roms that would cause my Atrix to boot on one and not the other. I can also manage to get the MIUI to boot.
Click to expand...
Click to collapse
I think something is going on with the kernel. You may have a bad processor. That's where my train of thought is right now. Sorry I couldn't get you up and running!
CaelanT said:
I think something is going on with the kernel. You may have a bad processor. That's where my train of thought is right now. Sorry I couldn't get you up and running!
Click to expand...
Click to collapse
Thanks for all you help. Finally got it to boot by removing external sd card.
[EDIT] Not sure but I believe the problem I had with m external sd is I still had an ext4 primary partition on it from when I was using Webtop2SD. Copying everything over to pc now and reformating external to see if my assumption is correct.
Looks like the ext4 partition on as was the culprit.
Sent from my Flipping ArtixTab!
After reading the forums (and google) for hours, I'm still at a loss how to recover my i777 phone. I followed the directions to the T at Galaxy2root.c o m. I attempted to upgrade from Gingerbread to JellyBean 4.2.1. I first rooted my phone using Odin3 1.8.5 and Zedomax ROM. I followed the instructions in the link above, clearing the cache, cleared Dalvik cache, factory reset (I did it in the phone, not through CWM which is where I may have messed up.) I did a backup with recovery mode to the sdcard then went through CWM recovery mode and loaded the AOKP's JB build 5.
Everything seemed fine until it got stuck in the JB animation boot screen and stayed there. At this point, I lost access to the CWM's recovery mode menu. At this point, Kies will not recognize my device when it's in Download mode. I flashed the phone with the Siyah 4.0.1 ROM but that caused more damage, being that the phone does not go past the boot animation.
Since I cannot get to recovery mode, how much trouble am I in and how to I fix it? ANY direction will be appreciated.
Guthaes said:
I first rooted my phone using Odin3 1.8.5 and Zedomax ROM.
Click to expand...
Click to collapse
If you had Googled zedomax for the sgs2, you would have seen that that is where your problems began. It's known to cause problems for our device. I'll let the next guy help you out with fixing, as I have no clue.
Sent from my SGH-I777
Guthaes said:
After reading the forums (and google) for hours, I'm still at a loss how to recover my i777 phone. I followed the directions to the T at Galaxy2root.c o m. I attempted to upgrade from Gingerbread to JellyBean 4.2.1. I first rooted my phone using Odin3 1.8.5 and Zedomax ROM. I followed the instructions in the link above, clearing the cache, cleared Dalvik cache, factory reset (I did it in the phone, not through CWM which is where I may have messed up.) I did a backup with recovery mode to the sdcard then went through CWM recovery mode and loaded the AOKP's JB build 5.
Everything seemed fine until it got stuck in the JB animation boot screen and stayed there. At this point, I lost access to the CWM's recovery mode menu. At this point, Kies will not recognize my device when it's in Download mode. I flashed the phone with the Siyah 4.0.1 ROM but that caused more damage, being that the phone does not go past the boot animation.
Since I cannot get to recovery mode, how much trouble am I in and how to I fix it? ANY direction will be appreciated.
Click to expand...
Click to collapse
you might have to go back to stock gingerbread 2.3.5 kk6 with odin http://forum.xda-developers.com/showthread.php?t=1286432 and start from there again
Not to mention you never flashed a rom
Sent from Team Pirate! Using Tapatalk 2
Well that and he flashed a Rom that's not even for our phone. At least I've not seen aokp jellybean 5 anywhere here.or he's got a different phone model and doesn't even have an I777 at all and instead has the I9100 international version or a skyrocket.
Guthaes said:
After reading the forums (and google) for hours, I'm still at a loss how to recover my i777 phone. I followed the directions to the T at Galaxy2root.c o m. I attempted to upgrade from Gingerbread to JellyBean 4.2.1. I first rooted my phone using Odin3 1.8.5 and Zedomax ROM.
Click to expand...
Click to collapse
First up, i am not much of an expert so you can consider me as more or less in your category.
This is your first post here and AFTER you botched things up.
Secondly, you said you read forums for hours.. then you obv didnt read here OR missed this stuff posted about a week back:
brandonarev said:
Broken WiFi? Sounds like someone went to zedomaxs website. If you did, shame on you for using his stuff and expecting help here.
Click to expand...
Click to collapse
That really should have been a pointer.
I hope you ll take this as a big learning lesson and read about things after verification and attempt any rom flashing AFTER asking questions.
Wishing you luck.:good:
Thanks.
I can humbly say that my overconfidence and inexperience with flashing got me into a fix. I took tlopez1973's advice and followed the directions he sent me to. I flashed the ROM with stock Gingerbread 2.3.4, rooted it with Siyah, installed ICS stock and rooted it with siyah 4.0.4. Thanks a ton for the direction. I know now that the fine print is extremely important and definitely will be more diligent in comparing others' procedures when messing with kernals.
Guthaes said:
I can humbly say that my overconfidence and inexperience with flashing got me into a fix. I took tlopez1973's advice and followed the directions he sent me to. I flashed the ROM with stock Gingerbread 2.3.4, rooted it with Siyah, installed ICS stock and rooted it with siyah 4.0.4. Thanks a ton for the direction. I know now that the fine print is extremely important and definitely will be more diligent in comparing others' procedures when messing with kernals.
Click to expand...
Click to collapse
here's the biggest tip anyone here can give you, you're welcome:
If you didn't find it in xda, don't use it.
Glad you got everything working! Read the stickies here and search Google with "xda" after your query and you'll be fine!
Clay
Team Pirate
Sent from my PINK GSwagger2
Hey guys, I need help.
I consider myself fairly adept at handling rooted devices, but I have not been following development for the GS4 for the last several months and have been running the last release of Synergy before their hiatus.
I was going to try out something different. I always enjoyed Beanstown's Jelly 'Beans', and thought I would try Build 7.
Now I am stuck at the Samsug Galaxy Boot Logo and it never goes to the Custom Boot Screen.
WORSE...I managed to break my recovery...so it will not boot their either.
Only mode I can boot to is Download.
Maybe I am just blind but I searched and could not find any Odin flashable recoveries...does anyone have one? Is there a rooted MDK file out there that I can flash via Odin?
Someone please help
Did you do the proper wipes when flashing the new rom? There arent any odin flashable recoveries for the s4. I would probably use the no wipe mdk image to recover (wont lose any user data) since you have no custom recovery to flash something with. Youll have to start over but youll have a working phone at least.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
jbg25 said:
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
Click to expand...
Click to collapse
Yeah looks like you got everything in order. Rom manager or rom toolbox will auto loki the recoveries. No need to update radios when flashing beans either. Itll already have the radios included unless your wanting to flash the mj7 radio seperately then I believe youll be ok doing that. I havent done alot of reading on the newest radios.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
jbg25 said:
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
Click to expand...
Click to collapse
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
beanstown106 said:
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
Click to expand...
Click to collapse
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
jbg25 said:
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
Click to expand...
Click to collapse
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
jbg25 said:
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
Click to expand...
Click to collapse
Go here. Get 2.5.0.2
http://techerrata.com/browse/twrp2/jfltevzw
Instructions
http://teamw.in/project/twrp2/181
At the bottom of the page.
Edit;
Or flash this in recovery
http://forum.xda-developers.com/showthread.php?p=45006486
I would reboot to recovery after flashing to make you got it on the right version.
Then make sure you can still boot back to your rom.
Then go back to recovery
Wipe
Factory reset.
Advanced
Check system, Data, davlik and cache
Wipe
Go back to main screen
Install
Fund your rom to flash.
Sent from my SCH-I545 using xda app-developers app
Me too. I tried the [ROM][TW4.3]STOCK-ROOTED-MJ7-AROMA-LOKI'd ROM with CWMR. Wiped Dalvik. Cache, Ractory Rest/Data. Seemed to install fine but then hung at "Custom". Fortunately I was able to a Nandroid Restore but not sure where this went wrong. Finally got TWRP to install after several failed GooManager attempts over the past month. May CWMR is the problem.
What's up guys, I'm running into an unusual issue here and could really use some guidance. I tried searching around, and the only solution I KNOW will work is to start from scratch, using odin to go back to stock, re-rooting, and then slowly trying to work my way back to where I was before the FUBAR.
So, I was recently using LiquidSmooth 2.9 and went to make the leap to 3.0. Flashed everything, got confirmation that it went through ok, and then I just got stuck at the Samsung Galaxy s4 screen, nothing happens after that. So, I went to restore from the backup that I took earlier and I got a failure to restore.
Not to worry, I figured, I'll just reinstall from the zips for 2.9 that I still had on my SD card. Well, I do that and everything seems to work fine with the flash, but now I'm STILL stuck at the Samsung Galaxy S4 boot screen and STILL, nothing happens after that.
Any suggestions on what to do here? Flash a new kernel? Am I stuck going the long route and having to Odin everything back to stock and then re-root, etc?.
samstheman42 said:
What's up guys, I'm running into an unusual issue here and could really use some guidance. I tried searching around, and the only solution I KNOW will work is to start from scratch, using odin to go back to stock, re-rooting, and then slowly trying to work my way back to where I was before the FUBAR.
So, I was recently using LiquidSmooth 2.9 and went to make the leap to 3.0. Flashed everything, got confirmation that it went through ok, and then I just got stuck at the Samsung Galaxy s4 screen, nothing happens after that. So, I went to restore from the backup that I took earlier and I got a failure to restore.
Not to worry, I figured, I'll just reinstall from the zips for 2.9 that I still had on my SD card. Well, I do that and everything seems to work fine with the flash, but now I'm STILL stuck at the Samsung Galaxy S4 boot screen and STILL, nothing happens after that.
Any suggestions on what to do here? Flash a new kernel? Am I stuck going the long route and having to Odin everything back to stock and then re-root, etc?.
Click to expand...
Click to collapse
Id download the latest liquid file again just in case that file was corrupt somehow.
That's usually been the problem lately from what I've been seeing. You really shouldn't have to Odin.
Also the kernel shouldn't matter but I always flash kts latest kernel with liquid but others don't and have no issues.
Grab that file again
Do a couple wipes in recovery
Flash away
Sent from my SCH-I545 using Tapatalk
---------- Post added at 04:23 PM ---------- Previous post was at 04:21 PM ----------
Also what recovery are you using?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Id download the latest liquid file again just in case that file was corrupt somehow.
That's usually been the problem lately from what I've been seeing. You really shouldn't have to Odin.
Also the kernel shouldn't matter but I always flash kts latest kernel with liquid but others don't and have no issues.
Grab that file again
Do a couple wipes in recovery
Flash away
Sent from my SCH-I545 using Tapatalk
---------- Post added at 04:23 PM ---------- Previous post was at 04:21 PM ----------
Also what recovery are you using?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Using TWRP 2.5.02
samstheman42 said:
Using TWRP 2.5.02
Click to expand...
Click to collapse
Well I've seen others either upgrading their twrp or going with some version of CWM but that's obviously up to you. I'd try to download the latest liquid, which is a unified build, and try it again first..
Sent from my SCH-I545 using Tapatalk