Related
Just got a GSIII today and have been trying some JB ROMS out, but so far I have not been able to get WiFi working at all with any of them.
I have tried Vanilla RootBox, LiquidJB and SuperNexus but whilst I can see my WiFi AP on all of them and can enter my password all I get is the "Connecting..." message for ages before it gives up?
WiFi works fine on the stock ROM, and there are no obvious settings on the WiFi router itself which would be causing this.
Any advice appreciated!
You need to flash back to stock ICS then flash jelly beam buddy
Sent from my GT-I9300 using xda premium
speedyjay said:
You need to flash back to stock ICS then flash jelly beam buddy
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thanks, I just spotted a couple of threads mentioning this.
Couple of questions, when you say flash back to stock does that mean through CWM Recovery, or some other way? Does it have to be a straight flash to a downloaded stock ROM or am I able to just "restore" the backup I made?
Thanks again!
Flash back using odin....i can provide a link if you like
Sent from my GT-I9300 using xda premium
speedyjay said:
Flash back using odin....i can provide a link if you like
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Cool, so I've got Odin (I believe that's what I used to root the phone?) Is there a specific .zip I need to flash back to? Also do I need to boot back in to the stock ROM or just stick JB straight back on again?
Please note, when you have flashed back to ics you need to then set up phone and connect to Wi-Fi once, then proceed to flash jb
slaphead20 said:
Please note, when you have flashed back to ics you need to then set up phone and connect to Wi-Fi once, then proceed to flash jb
Click to expand...
Click to collapse
Excellent. Do I need to download a specific "Stock ICS" ROM to do this? Any pointers as to where I can find this?
Thanks for the help people
I seem to remember I just flashed an old wannamlite Rom in cwm
http://forum.xda-developers.com/showthread.php?t=1646610
These ones. (4.0.4)
Or try http://fus.nanzen.se/
This is if you want to find the original firmware your phone came with.
I'm still not having much luck with this.
Should I be wiping before I flash back to ICS, and then again before back to JB?
I think a wipe before flashing ICS is enough.
But watch the youtube video on the first post on :
http://forum.xda-developers.com/showthread.php?t=1646610
It pretty much explains every part of returning to stock ICS. From there it is just reflashing JB with odin and wifi should work.
Hmm, still not having much luck. I've installed my JB ROM, wiped, gone back to stock ICS using the ROM from the link provided above in ODNI.
But now when I try to reboot in to recovery to re-flash my JB ROM I seem to get a different version of recovery from what I had before and it fails during verification when I try to flash the .zip.
Any advice welcome!
I'm having the same problem here.
BUT, even flasing stock ICS and flasing a custom JB ROM after that does not solve the issue.
Here is what I did in what order. Maybe I'm missing some essential point or whatever:
- full wipe in cwm recovery
- flash stock ICS via Odin (I9300XXBLH3_I9300DBTBLH4_I9300XXLH1_HOME.tar)
- reboot and test WiFi. WiFi works fine! Firmware is 4.0.4
- flash CF-Root-SGS3-v6.4 to gain root again
- boot into CWM Recovery, format /preload (to get rid of apps installing themselves on boot)
- another full wipe
- install zip from sdcard (tried AOKP JB build 4 for i9300 and ParanoidAndroid v2.22)
same old ****! WiFi not conecting!
I would apeciatie any help to solve this problem for me. Aparently reverting to stock ICS has solved this for others but I dont get what I'm donig wrong her...
try some router side adjustments
Jenuall said:
Hmm, still not having much luck. I've installed my JB ROM, wiped, gone back to stock ICS using the ROM from the link provided above in ODNI.
But now when I try to reboot in to recovery to re-flash my JB ROM I seem to get a different version of recovery from what I had before and it fails during verification when I try to flash the .zip.
Any advice welcome!
Click to expand...
Click to collapse
you need to root again flashing 'CF-Root' via Odin to get CWM recovery. I guess.
try some router side adjustments
Click to expand...
Click to collapse
that does not seem right. My phone connects just fine with any ICS based ROM. It even conects with JB ROM Android Revolution HD.
BitzlSchnitzl said:
you need to root again flashing 'CF-Root' via Odin to get CWM recovery. I guess.
Click to expand...
Click to collapse
Okay so I Re-rooted with CF-Root through ODIN and have got CWM recover back, but now when I re-flash JB I still get the same problems, try to connect to WiFi and it just sits there saying "Connecting..." and then gives up!
Is there a specific set of steps for doing this? I connected to WiFi whilst back on the Stock ICS ROM (LG8) and that worked fine, I have tried various combinations of wiping/not wiping at each stage in between JB->ICS->JB with no luck. Do I need a particular Stock ROM to go back to, do I have to use a specific version of ODIN/CF-Root/CWM?
Very annoying as everything else about the Jelly Bean ROMS seems perfect!
Has anyone worked out why JB ROMS are doing this?
I have the same problem
It seems to work for some people to go back to ICS and then flash JB ROMs, but somehow it does not work for us..
I'm trying an old stock ICS now and the will flash cm10. lets see if that helps
I've downloaded a selection of stock and custom ICS roms to try with the process, hopefully something will do the trick!
Also I don't think changing router settings can have anything to do with this as it works fine for every other device I own, including a different handset running JB. However out of curiosity I spent last night playing with all the settings to see if anything would help. It didn't
U said u flashed back to stock.... In that case u lost cwm then ur gonna hafto re flash cwm
Sent from my SGH-I747M using xda premium
Good news! I found a solution!!
use newest siyah kernel and wifi should connect
I need to return my Note back to stock. I rooted my Note back in Feb. the night I got it so I never did the official ICS update through OTA or Kies. Do I have to return back to GB that I started with or can I get by with flashing a stock ICS ROM, counter reset, and finaly Odin flash the stock recovery?
I appriciate any info ya'll guys are willing to provide.
ICS is the new stock... flash it.
BlackZenith said:
ICS is the new stock... flash it.
Click to expand...
Click to collapse
Thanks! I have read several posts of people going all the way back to GB then doing the update to ICS through Kies. That seemed a little redundant and figured I'd ask lol. I assume all I need to do then is to flash the stock ICS rom, reset counter and then stock recovery (odin). Thanks again.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I think I misunderstood you. I thought you were asking which OS to use in order to be stock... not how to accomplish getting stock ICS on your phone. In any case I think if you are stock GB or stock ICS, Kies will work. But if you are running a custom/deodex version of GB/ICS, Kies will not work. That's probably what everyone was trying to tell you. So if you are running a custom ROM, you are going to need to flash a stock version of GB/ICS before Kies will work.
BlackZenith said:
I think I misunderstood you. I thought you were asking which OS to use in order to be stock... not how to accomplish getting stock ICS on your phone. In any case I think if you are stock GB or stock ICS, Kies will work. But if you are running a custom/deodex version of GB/ICS, Kies will not work. That's probably what everyone was trying to tell you. So if you are running a custom ROM, you are going to need to flash a stock version of GB/ICS before Kies will work.
Click to expand...
Click to collapse
I gotcha. Actually been running JB for a while. Started of with GB which is when I rooted. Just didn't know if I had to go back to that or if I could just flash a stock 4.0.4 ROM before I retuned it for warranty (USB port issue). Bottom half of my screen doesn't register touch while charging.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
But does your USB issue affect the use of Odin? Be my first concern.
I don't believe it would. I can connect and is recognized on the computer and I can transfer files between phone and PC. I just have to unplug the cable from the phone in order for the screen to recognize touches around the lower half of screen
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Should be good to go then. I would Odin flash stock GB, reset and double check the flash counter. Check for Kies connectivity and pending ICS update availability. Throw a bunch of random apps on to give an appearance of use. Return for warranty all while pretending Android is a great mystery to you, even though we know that's not the case. Best of luck.
Resolved! I went ahead and took the following steps.
Flashed the stock rar file (GB) through Odin
Flashed cwm touch recovery through Odin
Flashed stock (GB) modern through touch recovery
Flashed reset counter through touch recovery
Used ADB to install stock recovery (did not trip counter this way).
Now completely stock (GB), I connected to kies and updated to stock official ICS 4.0.4.
All set to return it for warranty!!!
Thanks for helping out guys!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Hers my dilema, i had 4.1.1 rooted and unlocked and decided to return to stock so I could update to 4.1.2. all went well downgrading to stock but when I got the OTA the phone bootlooped. I could not access the recovery menu to wipe cache (as suggested in a few other post) so I ended up having the download the newest image and flash it to my phone. That worked after using the 16Gb pit file that is here in the forum (it kept failing before trying the pit file). THE QUESTION I have is, how do I root with casual without bootlooping? I tried after getting 4.1.2 installed and it went back into the bootloop. Any help would be greatly appreciated.
big.daddy said:
Hers my dilema, i had 4.1.1 rooted and unlocked and decided to return to stock so I could update to 4.1.2. all went well downgrading to stock but when I got the OTA the phone bootlooped. I could not access the recovery menu to wipe cache (as suggested in a few other post) so I ended up having the download the newest image and flash it to my phone. That worked after using the 16Gb pit file that is here in the forum (it kept failing before trying the pit file). THE QUESTION I have is, how do I root with casual without bootlooping? I tried after getting 4.1.2 installed and it went back into the bootloop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
OK, how exactly did you get 4.1.2 on your phone? You say that using the very latest version of CASUAL still causes bootloops when trying to unlock?
The obvious thing here is YOU NEVER SHOULD HAVE WENT TO ACCEPT THE OTA.
As it is this is a question better answered by AdamOutler or Droidstyle.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
OK, how exactly did you get 4.1.2 on your phone? You say that using the very latest version of CASUAL still causes bootloops when trying to unlock?
The obvious thing here is YOU NEVER SHOULD HAVE WENT TO ACCEPT THE OTA.
As it is this is a question better answered by AdamOutler or Droidstyle.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I flashed a stock image that I downloaded from stockimages(or something like that) with odin. That got the phone back up and running with 4.1.2. Once I did that, I figured I was back to stock (no root and no unlock) so I tried to run casual to re-root and unlock and ended up in a boot loop. Since then, I have gotten back to root and unlock but from now on I guess I have to update via the TWRP. Thanks for the obvious suggestion but I figured that since i had flashed back to stock it was ok to accept the ota.......I was assuming that I could get full access by running casual. From now on, I will leave well enough alone.
big.daddy said:
I flashed a stock image that I downloaded from stockimages(or something like that) with odin. That got the phone back up and running with 4.1.2. Once I did that, I figured I was back to stock (no root and no unlock) so I tried to run casual to re-root and unlock and ended up in a boot loop. Since then, I have gotten back to root and unlock but from now on I guess I have to update via the TWRP. Thanks for the obvious suggestion but I figured that since i had flashed back to stock it was ok to accept the ota.......I was assuming that I could get full access by running casual. From now on, I will leave well enough alone.
Click to expand...
Click to collapse
The more updates Verizon pushes the tighter they luck the phone down trying to deal up all the holes our exploits could use, in turn that makes the exploits more risky and more prone to cause potential trouble.
It is best to just leave everything alone once you get rooted and unlocked and just flash the updates via TWRP/CWM, there is no real reason or advantage to updating the normal way. It does nothing different than flashing the ROM in recovery and has no advantages and a huge amount of risk.
It may be that the Odin flashable ROM you got was missing something or was wonky in some way since it didn't come from XDA. It shouldn't have reacted that way if you were using the most up to date version of CASUAL.
Sent from my SCH-I605 using XDA Premium HD app
big.daddy said:
I flashed a stock image that I downloaded from stockimages(or something like that) with odin. That got the phone back up and running with 4.1.2. Once I did that, I figured I was back to stock (no root and no unlock) so I tried to run casual to re-root and unlock and ended up in a boot loop. Since then, I have gotten back to root and unlock but from now on I guess I have to update via the TWRP. Thanks for the obvious suggestion but I figured that since i had flashed back to stock it was ok to accept the ota.......I was assuming that I could get full access by running casual. From now on, I will leave well enough alone.
Click to expand...
Click to collapse
Big.daddy can I ask what you used to get back from the bootloop to where your at now? Sorry to bother you but I screwed up somewhere, once again
chiefsfan69 said:
Big.daddy can I ask what you used to get back from the bootloop to where your at now? Sorry to bother you but I screwed up somewhere, once again
Click to expand...
Click to collapse
I used Odin to get the phone back to stock (vramc3). I tried it on two computers and eventually got it to rum when using the 16 GB .pit file that can be found on this forum. That got me back to stock. I then used casual to re-root and unlock. The thing I have learned is that once twrp is intalled, I only need to download a ROM based on the Verizon stock (unless you want custom) and flash it through twrp. NOT WHAT I INITIALLY DID. I flashed back to stock and accepted an ota which didn't work out well. Took me 5 hours of downloading and trying to get the phone flashed. Good luck. The first thing I would try is downloading the beanstown vzw stock ROM and flash it with the .pit file.
big.daddy said:
I used Odin to get the phone back to stock (vramc3). I tried it on two computers and eventually got it to rum when using the 16 GB .pit file that can be found on this forum. That got me back to stock. I then used casual to re-root and unlock. The thing I have learned is that once twrp is intalled, I only need to download a ROM based on the Verizon stock (unless you want custom) and flash it through twrp. NOT WHAT I INITIALLY DID. I flashed back to stock and accepted an ota which didn't work out well. Took me 5 hours of downloading and trying to get the phone flashed. Good luck. The first thing I would try is downloading the beanstown vzw stock ROM and flash it with the .pit file.
Click to expand...
Click to collapse
Thanks man, **** I just went through all this bs and finally got mine last night but then I tried to do casual and something went wrong and now I am back in the loop and I don't know if i should just flash the same I did just last night to get it back or what? Thank you though I really appreciate your help
I would try casual agai if you can get into download mode (power + vol dn+ home). If that doesn't work I'd try reflashing. Good luck.
big.daddy said:
I would try casual agai if you can get into download mode (power + vol dn+ home). If that doesn't work I'd try reflashing. Good luck.
Click to expand...
Click to collapse
I can get in download mode but the problem seems to be the adb, and since i can't get in the phone to turn it on casual never picks up the device, for all I know?
chiefsfan69 said:
I can get in download mode but the problem seems to be the adb, and since i can't get in the phone to turn it on casual never picks up the device, for all I know?
Click to expand...
Click to collapse
Reflash with Odin
big.daddy said:
Reflash with Odin
Click to expand...
Click to collapse
Hold on, reflash casual in odin?
chiefsfan69 said:
Hold on, reflash casual in odin?
Click to expand...
Click to collapse
No, do what you did last time in Odin again.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
No, do what you did last time in Odin again.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I have been trying, this time around it hasnt passed a single flash, on anything?
chiefsfan69 said:
I have been trying, this time around it hasnt passed a single flash, on anything?
Click to expand...
Click to collapse
Check the drivers to make sure the CASUAL driver isn't the one in use.
Sent from my SCH-I605 using XDA Premium HD app
You may also want to try a different computer...... Different USB ports too. I will work it takes a little patience.
Hello, I am new to the forum, but I am not new to rooting. I switched from the Droid Razr Maxx to the Galaxy S4, and so far I have loved my GS4. I am updated fully to android 4.2.2 baseband I545VRUAME7. I was able to root my phone using the SD Card method as published on Saturday, July 27 2013. Upon rooting my phone I attempted to install custom recovery in order to install the Eclipse S4GE v1.4 ROM made by nitroglycerine33. I downloaded Goomanager and installed TWRP. Upon telling TWRP to flash the custom ROM it rebooted the phone, as usual. After reboot i was put into Odin. I tried this process 4 times with no avail, continuously booting into Odin. After trying TWRP, I tried Clockworkmod and the same happened to me. I am unable to get anything other than Odin, and I really hate TouchWiz and want to switch to this ROM. Thanks for any help.
DaringVirus52 said:
Hello, I am new to the forum, but I am not new to rooting. I switched from the Droid Razr Maxx to the Galaxy S4, and so far I have loved my GS4. I am updated fully to android 4.2.2 baseband I545VRUAME7. I was able to root my phone using the SD Card method as published on Saturday, July 27 2013. Upon rooting my phone I attempted to install custom recovery in order to install the Eclipse S4GE v1.4 ROM made by nitroglycerine33. I downloaded Goomanager and installed TWRP. Upon telling TWRP to flash the custom ROM it rebooted the phone, as usual. After reboot i was put into Odin. I tried this process 4 times with no avail, continuously booting into Odin. After trying TWRP, I tried Clockworkmod and the same happened to me. I am unable to get anything other than Odin, and I really hate TouchWiz and want to switch to this ROM. Thanks for any help.
Click to expand...
Click to collapse
You cant flash roms on the new update, you can only root.
With rooted ME7, we do not have the capability (yet!) to install custom roms or recoveries. See the thread on the bounty about this.
resurektz said:
You cant flash roms on the new update, you can only root.
Click to expand...
Click to collapse
Why is that, and is there a way to downgrade the Baseband now that I am rooted, as I said before I do not like TouchWiz.
DaringVirus52 said:
Why is that, and is there a way to downgrade the Baseband now that I am rooted, as I said before I do not like TouchWiz.
Click to expand...
Click to collapse
What's your build number? If it ends with ME7 the best you can do is root (for now).
Is there a way to downgrade, or a reason as to why we cannot install custom ROMs?
Me7 blocks older versions of the firmware so no downgrading. You cant install a custom recovery because me7 patched the loki exploit. Once on the me7 ota youre stuck, for now atleast.
Sent from my SCH-I545 using Tapatalk 2
Thanks, keep me updated as to when we can install custom ROMs.
No problem.
Sent from my SCH-I545 using Tapatalk 2
DaringVirus52 said:
Hello, I am new to the forum, but I am not new to rooting. I switched from the Droid Razr Maxx to the Galaxy S4, and so far I have loved my GS4. I am updated fully to android 4.2.2 baseband I545VRUAME7. I was able to root my phone using the SD Card method as published on Saturday, July 27 2013. Upon rooting my phone I attempted to install custom recovery in order to install the Eclipse S4GE v1.4 ROM made by nitroglycerine33. I downloaded Goomanager and installed TWRP. Upon telling TWRP to flash the custom ROM it rebooted the phone, as usual. After reboot i was put into Odin. I tried this process 4 times with no avail, continuously booting into Odin. After trying TWRP, I tried Clockworkmod and the same happened to me. I am unable to get anything other than Odin, and I really hate TouchWiz and want to switch to this ROM. Thanks for any help.
Click to expand...
Click to collapse
You, my friend, are SOL for now
I got tired of waiting & ordered a Dev edition w/unlocked bootloader.
Sent from my Galaxy Nexus using Tapatalk 2
wtherrell said:
You, my friend, are SOL for now
I got tired of waiting & ordered a Dev edition w/unlocked bootloader.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
im still surprised nobody has been able to port the dev edition bootloader over and figure out how to unlock it.
but yes OP, you are screwed. start liking TW
dansan382 said:
im still surprised nobody has been able to port the dev edition bootloader over and figure out how to unlock it.
but yes OP, you are screwed. start liking TW
Click to expand...
Click to collapse
To port it over, the stock bootloader must first be unlocked. You can't overwrite the locked bootloader
najaboy said:
To port it over, the stock bootloader must first be unlocked. You can't overwrite the locked bootloader
Click to expand...
Click to collapse
obviously.. what i should have wrote was,
surprised nobody is able to compare and contrast the 2 bootloaders, find out whats different and examine a way to release that block. which im pretty sure what they have been trying.
basically it should be the same bootloader, one locked and one unlocked. find out how the lock is there and whats different
Is there any way to get out of the Odin mode when you attempt to reboot to recovery on ME7 using TWRP? Is it possible to flash back to the stock ROM?
You cant flash a custom recovery on the me7 ota. Turn your phone off and use the odin/download mode key combo. When it asks if u want continue decline and your phone will boot normally. Me7 images flashable via odin are in the dev section.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
You cant flash a custom recovery on the me7 ota. Turn your phone off and use the odin/download mode key combo. When it asks if u want continue decline and your phone will boot normally. Me7 images flashable via odin are in the dev section.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Got it thanks a ton! I'll read up in the dev section. I really wish there were step by steps for noobies out there that are a bit more clear. I've googled and seen so many links to forums and threads. I thought I found a pretty straight forward method, but that one didn't work. I'm not giving up!
Regards,
Tony
blkst2x said:
Is there any way to get out of the Odin mode when you attempt to reboot to recovery on ME7 using TWRP? Is it possible to flash back to the stock ROM?
Click to expand...
Click to collapse
You're not using TWRP if you updated to ME7. You have the stock recovery and are on the stock rom. There is no going back to MDK.
Sent from my Nexus 7 using Tapatalk 4
najaboy said:
You're not using TWRP if you updated to ME7. You have the stock recovery and are on the stock rom. There is no going back to MDK.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Unfortunately I have figured that one out. So, is there any way to install one of the ROMs posted by Dubbsy? I was under the impression that these worked with ME7, but I must be very wrong in that assumption. Forgive my ignorance. I'm just really sick of TouchWiz and I can't wait to get a clean Android install on this device.
No you cant install any rom as of yet on me7. The me7 roms in the dev section are an me7 base with mdk files so you can retain ability to flash a custom recovery and flash other roms. As for your pm shut your phone all the way off and then hold volume down + power. Release power when it vibrates keep holding vol down and itll ask for you to confirm or deny booting to download mode. If you deny it your phone should boot normally. Everytime you boot I believe itll do this so youll eventually need to use one of the me7 odin images. There is no wipe versions in the dev section so you wont lose any apps and data associated with them.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
No you cant install any rom as of yet on me7. The me7 roms in the dev section are an me7 base with mdk files so you can retain ability to flash a custom recovery and flash other roms. As for your pm shut your phone all the way off and then hold volume down + power. Release power when it vibrates keep holding vol down and itll ask for you to confirm or deny booting to download mode. If you deny it your phone should boot normally. Everytime you boot I believe itll do this so youll eventually need to use one of the me7 odin images. There is no wipe versions in the dev section so you wont lose any apps and data associated with them.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
after doing that procedure once, it let's me boot up fine. Powering off, then on, reboot, or batter pull..they all work fine now. How would I install one of the ME7 Odin images? Is there a doc on how to do that using Odin?
Got a s4 today, followed the root guide here, using mdk pre release kernel. Did not unlock the boot loader. Loaded hyperdrive and after loading everything did the reboot. left me at the black samsung screen with an unlocked padlock and custom underneath. i can get into recovery and download. but no matter what i do will not progress screens (even tried full cache, dalvic, system, and data wipe and reloaded Hyperdrive. same results)
Should i re flash back to stock and try the entire process over again? if so, links please
also, what did i do to soft brick my phone? for future avoidance
and whats the difference between mdk and me7?
You probably got a bad download of the rom. Its a good idea to verify the md5 after its been downloaded. Once you can get a good download of the rom you dont need to odin back you can flash the rom in recovery and youll be good to go. The me7 ota is the newest firmware, has a few nice changes but it also has a non exploitable boot loader so you cant run a custom recovery on it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
You probably got a bad download of the rom. Its a good idea to verify the md5 after its been downloaded. Once you can get a good download of the rom you dont need to odin back you can flash the rom in recovery and youll be good to go. The me7 ota is the newest firmware, has a few nice changes but it also has a non exploitable boot loader so you cant run a custom recovery on it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
To clarify, your suggesting re downloading rls8, and try flashing that. Then, if that doesn't work, re flash the stock kernel (basically go through the Odin root guide again?)
Thanks!
Redownload rls8 verify the md5 checksum to make sure its not another bad download and then flash. As long as you can get into custom recovery of your choice and the download is good theres no reaaon it shouldnt work.
Sent from my SCH-I545 using Tapatalk 2
correct md5sum, same results.
both odin'd kernels have no effect, same boot problem. anyone know a fix?
Hopefully someone will. Same problem. Putting my phone back to stock rooted MDK works. The minute I try to flash Hyperdrive 8 and 8.1, it boots fine, then hangs on a restart.
Atleast, Will verizon exchange the phone seeing this?
Your mistake, why should Verizon replace something you caused.
Did you make a nandroid of the stock Rom prior to flashing?
Sent from my SCH-I545 using Tapatalk 4
Addiso said:
Your mistake, why should Verizon replace something you caused.
Did you make a nandroid of the stock Rom prior to flashing?
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
and yet no one has yet been able to pinpoint what mistake i made in installing a rom i've used for 12 months (s3) and installing a new version on a new phone while following every instruction to the letter, suddenly ****s on me. so please, enlighten me, what mistake did i make?
You didn't make a mistake. Chances are, you just used the wrong recovery. I spent 7 hours last night trying to fix my phone. I factory reset this morning to the stock MDK and re-rooted and figured out how to use ADB to install the Clockwork Mod Recovery. It's difficult to get started and figure out how to install and use it, but there are resources out there that will help you figure it out. I reinstalled the new 8.1 Hyperdrive with CWM recovery and was delighted when the ROM actually rebooted without fuss. It did hang on the Custom unlock screen long enough to make me nervous though. Figure out ADB and add CWM. It will work.
Edit for your steps: Reinstall the stock MDK with Odin. Reroot as per the instructions in the MDK root thread. Instead of TWRP, use CWM Recovery (which isn't nearly as easy), then reinstall the latest Hyperdrive (or whatever you were trying to install).