Related
Since I saw Chris posted his kernel with a cwm from koush, I decided to check rom manager today to see if there was anything new. And sure enough the touch is now listed and I was able to flash the latest version, 5.0.2.7. Thought I would share.
Sent from my SPH-D710 using xda premium
crawrj said:
Since I saw Chris posted his kernel with a cwm from koush, I decided to check rom manager today to see if there was anything new. And sure enough the touch is now listed and I was able to flash the latest version, 5.0.2.7. Thought I would share.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I can confirm this. 5.0.2.7 is now on my device, updated from 5.0.2.3, and there are now options to backup and restore from either internal or external sd .
On to CM!
odub303 said:
I can confirm this. 5.0.2.7 is now on my device, updated from 5.0.2.3, and there are now options to backup and restore from either internal or external sd .
On to CM!
Click to expand...
Click to collapse
+1
Sent from my Eptouch 4g
Ok this is my first time using rom manager so this might be normal. But I am putting it out there in case people don't know. Looks like you still need a custom kernel for it to work. I tried with stock kernel and it didn't work. Also it looks like you will have two versions of CWM installed. I installed the kernel Chris provided and after installing the rom manager kernel if I choose boot to recovery from rom manager I get the new version, 5.0.2.7. If I try the vup + power I get the recovery on the kernel, which in this case is 5.0.2.6. So with that in mind I would rather just have the kernel with the latest version. Not sure if we can just get a stock kernel with rom manager support and that will fix the double cwm issue.
crawrj said:
Ok this is my first time using rom manager so this might be normal. But I am putting it out there in case people don't know. Looks like you still need a custom kernel for it to work. I tried with stock kernel and it didn't work. Also it looks like you will have two versions of CWM installed. I installed the kernel Chris provided and after installing the rom manager kernel if I choose boot to recovery from rom manager I get the new version, 5.0.2.7. If I try the vup + power I get the recovery on the kernel, which in this case is 5.0.2.6. So with that in mind I would rather just have the kernel with the latest version. Not sure if we can just get a stock kernel with rom manager support and that will fix the double cwm issue.
Click to expand...
Click to collapse
IIRC, we will no longer need CWM built into the kernel, but rather just a CWM redirector to direct to the recovery partition, where it appears that 5.0.2.7 was flashed.
does it take a long time to flash? its been a while since its trying to install
m_reyna_16 said:
does it take a long time to flash? its been a while since its trying to install
Click to expand...
Click to collapse
I think the kernel needs to be made for it... As i think it changes the intramfs
Sent from my SPH-D710 using XDA App
Mine didn't work booted to triangle I am using stock kernel
Sent from my SPH-D710 using Tapatalk
deano0714 said:
I think the kernel needs to be made for it... As i think it changes the intramfs
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
what kernel works on this version then?
digweed4me said:
Mine didn't work booted to triangle I am using stock kernel
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Yes as Deano and I stated it doesn't work on stock kernel. Chris has already updated his stock kernel with the latest version so I switched to it.
m_reyna_16 said:
what kernel works on this version then?
Click to expand...
Click to collapse
Probably any custom kernel but I used Chris41G's stockcwm kernel.
crawrj said:
Probably any custom kernel but I used Chris41G's stockcwm kernel.
Click to expand...
Click to collapse
Nope... Using LoStkernel... And it doesnt work but he is updating it today he said so it sould soon
Sent from my SPH-D710 using XDA App
deano0714 said:
Nope... Using LoStkernel... And it doesnt work but he is updating it today he said so it sould soon
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
yea im using the same kernel, i guess ill wait then
deano0714 said:
Nope... Using LoStkernel... And it doesnt work but he is updating it today he said so it sould soon
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I'm using LostKernel also, and I had no problem installing CWM through Rom Manager. Rebooting to recovery via Rom Manager takes me to 5.0.2.7 (installed from the app), rebooting from Quick Boot or on a regular boot up holding vol up and power takes me to 5.0.2.6 (from LostKernel).
---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------
deano0714 said:
I think the kernel needs to be made for it... As i think it changes the intramfs
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I don't think so. I think Rom Manager flashes CWM to the recovery partition, whereas the kernel is on the boot partition. if you install CWM through Rom Manager, the only way to get to it at the moment is to reboot to recovery from Rom Manager, otherwise you will be booted into the CWM included in the kernel.
odub303 said:
I'm using LostKernel also, and I had no problem installing CWM through Rom Manager. Rebooting to recovery via Rom Manager takes me to 5.0.2.7 (installed from the app), rebooting from Quick Boot or on a regular boot up holding vol up and power takes me to 5.0.2.6 (from LostKernel).
---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------
I don't think so. I think Rom Manager flashes CWM to the recovery partition, whereas the kernel is on the boot partition. if you install CWM through Rom Manager, the only way to get to it at the moment is to reboot to recovery from Rom Manager, otherwise you will be booted into the CWM included in the kernel.
Click to expand...
Click to collapse
Rom manager uses a fake flashing technique so I have read a bunch of times.
The CWM or Team Win recoveries will not stick after rebooting the phone with w OTA update. There is a way of making recovery stick on the rooted OTA update. Does anyone know the correct files to freeze or erase for the new recoveries to stick?????
Is there another way of these recoveries to stick besides flashing a custom Rom??
Vinny
vinnyjr said:
The CWM or Team Win recoveries will not stick after rebooting the phone with w OTA update. There is a way of making recovery stick on the rooted OTA update. Does anyone know the correct files to freeze or erase for the new recoveries to stick?????
Is there another way of these recoveries to stick besides flashing a custom Rom??
Vinny
Click to expand...
Click to collapse
I definitely didn't have that problem. If you have root use google manager to install twrp
Sent from my SGH-T999 using Tapatalk 2
mikeyinid said:
I definitely didn't have that problem. If you have root use google manager to install twrp
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I have root, I have Goo Manager, I'm on a completely stock rooted rom and every time you reboot the new OTA software over writes the custom recovery to the stock Android recovery. If you have a custom rom this will not happen, only on a stock, rooted OTA latest update rom. Others are having the same issue.
Vinny
What methods did you use to install the ota and root?
Have you tried flashing the stock rooted version wildchld released?
Sent from my SGH-T999 using xda app-developers app
I waited for the OTA update then used Odin to flash root, did not reboot after flashing with Odin, pulled battery, then went right to recovery and flashed super user.zip file. I rooted my phone the right way. This is my 2nd SGS3 and didn't have this problem with the 1st one because it had the older build. This is not a problem if you are on a custom build. Only stock, rooted with latest OTA build.
Vinny
Sent from my SGH-T999 using Tapatalk 2
I honestly don't know if it would work but maybe try flashing the insecure stock kernel?
Sent from my SGH-T999 using xda app-developers app
Thanks for the input. (DocHoliday) is my favorite western character. Big western nut.
Vinny
Sent from my SGH-T999 using Tapatalk 2
vinnyjr said:
I have root, I have Goo Manager, I'm on a completely stock rooted rom and every time you reboot the new OTA software over writes the custom recovery to the stock Android recovery. If you have a custom rom this will not happen, only on a stock, rooted OTA latest update rom. Others are having the same issue.
Vinny
Click to expand...
Click to collapse
im stock, rooted on the latest ota and i dont have this issue. never had it on the other build either
vinnyjr said:
Thanks for the input. (DocHoliday) is my favorite western character. Big western nut.
Vinny
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I'm your huckleberry!
Sent from my SGH-T999 using xda app-developers app
mrmako777 said:
im stock, rooted on the latest ota and i dont have this issue. never had it on the other build either
Click to expand...
Click to collapse
yes you do, you just don't know it yet.
Reboot your phone, then boot into recovery.
Sent from the current Heavy Weight Champ GALAXY SIII
Please try this, http://forum.xda-developers.com/showthread.php?t=1821681
Hopefully it works. Mine is fine after update
vinnyjr said:
I have root, I have Goo Manager, I'm on a completely stock rooted rom and every time you reboot the new OTA software over writes the custom recovery to the stock Android recovery. If you have a custom rom this will not happen, only on a stock, rooted OTA latest update rom. Others are having the same issue.
Vinny
Click to expand...
Click to collapse
I'm on the stock rooted rom and this hasn't been a problem for me. I've installed recovery once since I got the phone. And flashed every stock and custom Rom.
Sent from my SGH-T999 using Tapatalk 2
ingenious247 said:
yes you do, you just don't know it yet.
Reboot your phone, then boot into recovery.
Sent from the current Heavy Weight Champ GALAXY SIII
Click to expand...
Click to collapse
Lolol uh, I've done it a hundred times guy, no issues
Sent from my SGH-T999
You're right. You're the only guy in the world who's official stock update doesn't overwrite the recovery upon reboot. They special coded yours to preserve custom recovery.
Please...
I swear sometimes..
Sent from the current Heavy Weight Champ GALAXY SIII
Guys, I have seen this on my GF's GSII (Sprint) as well as on my nexus 7. They are placing a file called recovery-from-boot.p in the /system/ directory that overwrites recovery on every boot. I put a guide a few post up that outlines the issue when I saw it on my GF's phone.
Personally my T-Mobile has been fine, but this scenario I have dealt with before. So don't flame that bad.
The bottom line is that without some custom modding, if you're running the official stock OTA update, stock kernel, etc, standard CWM recovery is not going to stick.
Plain and simple.
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
cybrnook said:
Guys, I have seen this on my GF's GSII (Sprint) as well as on my nexus 7. They are placing a file called recovery-from-boot.p in the /system/ directory that overwrites recovery on every boot. I put a guide a few post up that outlines the issue when I saw it on my GF's phone.
Personally my T-Mobile has been fine, but this scenario I have dealt with before. So don't flame that bad.
Click to expand...
Click to collapse
Yeah, I'm going to try using that guide and report back. thanks
---------- Post added at 11:12 AM ---------- Previous post was at 11:07 AM ----------
Ok, both files were present as described in your guide.
Renamed both to:
recovery-from-boot.bak
install recovery.sh.bak
Reflashed CWM through ROM Manager. Rebooting now, then will try power off & booting into recovery. Hang tight
*Edit: Worked like a charm. Gentlemen, we have the solution. Thanks due (and given) to cybrnook both here and in the guide
sweet.
ingenious247 said:
The bottom line is that without some custom modding, if you're running the official stock OTA update, stock kernel, etc, standard CWM recovery is not going to stick.
Plain and simple.
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
Yeah, I'm going to try using that guide and report back. thanks
Click to expand...
Click to collapse
I would argue, I have a stock rooted rom, stock kernel and I update to the new OTA update via Kies and TWRP has stuck every boot since then. I even tested it again when I saw this thread as it made me unsure.
cybrnook said:
I would argue, I have a stock rooted rom, stock kernel and I update to the new OTA update via Kies and TWRP has stuck every boot since then. I even tested it again when I saw this thread as it made me unsure.
Click to expand...
Click to collapse
Maybe the Kies version is different than the OTA.
Maybe TWRP overwrites or renames/deletes the files causing it.
But you can't argue with my posts, because I said official OTA update, and CWM.
ingenious247 said:
Maybe the Kies version is different than the OTA.
Maybe TWRP overwrites or renames/deletes the files causing it.
But you can't argue with my posts, because I said official OTA update, and CWM.
Click to expand...
Click to collapse
No worries, but for clarification to all the read this thread. The update from Kies is the exact same Official update as the OTA, so if you have not been prompted for the update yet from T-Mo, just install Kies on your PC and plus your phone in, it will prompt you for the update.
I have another guide I made for that:
http://forum.xda-developers.com/showthread.php?t=1842142
For the recovery, installing twrp or CWM wont remove the two files I listed. This is done manually. I know on the sprint side, they made a root Super User package that swiped those off specific to the sprint phone. But I opted away from that for my GF as I Prefer SuperSU and am anal retentive about installing something I don't want and uninstalling it.
---------- Post added at 08:26 PM ---------- Previous post was at 08:24 PM ----------
ingenious247 said:
yes you do, you just don't know it yet.
Reboot your phone, then boot into recovery.
Sent from the current Heavy Weight Champ GALAXY SIII
Click to expand...
Click to collapse
ingenious, it's not present on all phones. Like mine for example, I have been fine since day 1 of owning the phone. But my GF's sprint phone had the persistent install present.
It's strange, some phones don't have it at all, some only have the .p file, and some have both. I have not found the common denominator yet.
ingenious247 said:
You're right. You're the only guy in the world who's official stock update doesn't overwrite the recovery upon reboot. They special coded yours to preserve custom recovery.
Please...
I swear sometimes..
Sent from the current Heavy Weight Champ GALAXY SIII
Click to expand...
Click to collapse
My bad man, I didn't get the memo that you knew everything I guess all the other guys that haven't had this same issue are nuts too...
Sent from my SGH-T999
HELP!!! My brother heard me talking about rooting my phone and installing cool ROM’s so he gave it a shot.. He has a Samsung galaxy s2 epic 4g touch, he loaded some ICS rom that does not have WiFi working, it also does not have USB working? He also didn’t load any recovery making it hard to bring it back to stock.
So I have a Samsung galaxy s2 epic 4g touch with some weird ICS rom, the Wifi does not work, no SDCard access, it has NO USB support.. it does have Bluetooth working so I have been able to move files to it but the rom he installed is not rooted and I can’t install a recovery app…
I can boot into download mode but with no USB support oden will not see the phone
Any advice on how to root the phone or get a recovery app installed from the phone?
I can boot into the default recovery and I have the option to “Apply Update.zip from external storage” but the phone will not see an SD card, I also have an option to “apply update.zip from cache” then I see a lost+fount and recovery directory but I don’t know how to get my update.zip to this folder?
You can try downloading one of agat's ics kernels and flashing it through mobile Odin. You don't need USB for that. If that works then download a rom from xda not some random one you found on the internet, put it in the internal storage and flash from agat's recovery. May not work can't say 100%
Sent from my SPH-D710 using xda app-developers app
can i install mobile Odin with out having root access?
Its not listed on my list of apps for super user so I don't believe so but I am not sure worst that can happen is the app not open
Sent from my SPH-D710 using xda app-developers app
Amore514 said:
can i install mobile Odin with out having root access?
Click to expand...
Click to collapse
Never mind my original post, I missed a sentence in the op..
it does require root access
i can boot into download mode, the OS installed has no USB support so oden does not see the phone.
Amore514 said:
i can boot into download mode, the OS installed has no USB support so oden does not see the phone.
Click to expand...
Click to collapse
Yeah, that's what confuses me. USB support in Odin Download mode of the phone, which I thought was driven by Kernel, not rom, leaves me to wonder if he flashed the international kernel.
Or I thought..
But it's odd you get the rom to boot and all of that is broke..
---------- Post added at 02:43 PM ---------- Previous post was at 02:39 PM ----------
I wonder if you can get to the playstore and download supersu, if that wouldn't be a root method? Total shot in the dark since I haven't followed Chainfires SU thread that close. :edit: Doesn't look like it would work. :/
I for sure can not get access to the play store i can download APK files and move them to this phone via bluetooth but with out root access supersu will not work..
Hmm. So the only options in recovery is externel SD and cache? You may be sol. You can try downloading agats kernel in
Zip format and putting in the internal storage and pray it works. Unless one of the e4gt gurus knows another way
Sent from my SPH-D710 using xda app-developers app
---------- Post added at 09:13 PM ---------- Previous post was at 09:11 PM ----------
Unless you can push recoveries through the bootloader as an img like HTC phones but with recoveries tied to the kernel I doubt it unless its possible to unpack the kernel and just pull the recovery. But that's far beyond me.
Sent from my SPH-D710 using xda app-developers app
what is "agats kernel" and i dont think there is away to flash it with the stick recovery?
Agat is a developer here for the e4gt. You can find his kernels in the kernel repository thread in the Android development sub forum
Sent from my SPH-D710 using xda app-developers app
Ya i just read all about it, looks cool wish i could flash it, lol.
im hoping someone else will chime in with a trick to get the USB to work or how to move the update.zip stock rom i downloaded to the cashe
Amore514 said:
Ya i just read all about it, looks cool wish i could flash it, lol.
im hoping someone else will chime in with a trick to get the USB to work or how to move the update.zip stock rom i downloaded to the cashe
Click to expand...
Click to collapse
They're a tad busy with a leak today, but you may want to reach out to crawrj and see if they have any ideas.
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
geddryis 1,068
helped me. thanks
dfreelan said:
helped me. thanks
Click to expand...
Click to collapse
Please do not reply to "dead" threads to hit the 10 post count.
garwynn said:
Please do not reply to "dead" threads to hit the 10 post count.
Click to expand...
Click to collapse
Lol. Happy new year! :beer:
Transmitted from another galaxy with a Jellybean infused P-5113 full of Unicorn porn.
Just to let everyone know, the Note 2 LTE (including T-Mobile) will be getting official CyanogenMod 10.1 builds!
Here's the link where the builds will be available: http://get.cm/?device=t0lte
And here's the thread in AT&T forum: http://forum.xda-developers.com/showthread.php?t=2105917
Nice! Thanks for the heads up dude.
This solidifies my belief that the Note 2 is undoubtedly the best phone in the world.
Wow just flashed this and my phone will not boot at all. FML...
Fixed. :thumbup:
Sent from my T989 using xda premium
The only reason I've ever used CyanogenMod on my previous device was because of software issues. To date, I can see no reason for even a custom ROM on my Note II let alone a beta ROM.
Hoezack said:
Wow just flashed this and my phone will not boot at all. FML...
Sent from my T989 using xda premium
Click to expand...
Click to collapse
Did you try this?
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
Click to expand...
Click to collapse
AFTER flashing?
Downloaded and tried to flash via CW three different times and installation aborted each time. I wiped data davlik and cache so I have no clue wtf is wrong but I need that 4.2!!!
I really didn't mean for this thread to become a support thread. If you guys are having problems flashing or booting, you didn't follow the instructions. Re-read all the information and try again following the instructions exactly.
xak944 said:
I really didn't mean for this thread to become a support thread. If you guys are having problems flashing or booting, you didn't follow the instructions. Re-read all the information and try again following the instructions exactly.
Click to expand...
Click to collapse
Been rooting and flashing since the G1 and never had installation abort in the middke of a flash but once. I read the directions and did exactly as posted four times now. Idk what the issue is. I am currently on Jedi X rom. Maybe I should flash stock then retry it?
SinisterSincere said:
Been rooting and flashing since the G1 and never had installation abort in the middke of a flash but once. I read the directions and did exactly as posted four times now. Idk what the issue is. I am currently on Jedi X rom. Maybe I should flash stock then retry it?
Click to expand...
Click to collapse
I'm guessing you didn't follow this step:
madmack said:
- Flash the latest official ClockworkMod-Recovery
Click to expand...
Click to collapse
It's been confirmed working with TWRP
xak944 said:
I'm guessing you didn't follow this step:
Click to expand...
Click to collapse
I know you said you didn't want this thread to turn into a support thread but how do you flash the latest recovery? Through odin or fastboot?
thanks
You don't need cwm I flashed perfectly fine with twrp and have no problems at all haven't tried Bluetooth since I don't use it but it States that it's a bug anyway.
Fandroid93 download goomanager and you can install the latest twrp from there. Or download rommanager and should be able to get cwm from there.
skater4690 said:
You don't need cwm I flashed perfectly fine with twrp and have no problems at all haven't tried Bluetooth since I don't use it but it States that it's a bug anyway.
Fandroid93 download goomanager and you can install the latest twrp from there. Or download rommanager and should be able to get cwm from there.
Click to expand...
Click to collapse
Thanks, I hadn't thought about that lol.
SinisterSincere said:
Downloaded and tried to flash via CW three different times and installation aborted each time. I wiped data davlik and cache so I have no clue wtf is wrong but I need that 4.2!!!
Click to expand...
Click to collapse
What version phone do you have? Some Canadian versions require the updater script to be modified to remove the version checks, everything flashes fine after that and works as normal but they forgot to add the version numbers in the check.
Sent from my GT-N7105 using Tapatalk 2
xak944 said:
I'm guessing you didn't follow this step:
Click to expand...
Click to collapse
Nope have the latest cwm but heard alot of people using twrp had luck so gonna flash that.
---------- Post added at 01:12 AM ---------- Previous post was at 01:06 AM ----------
_Dennis_ said:
What version phone do you have? Some Canadian versions require the updater script to be modified to remove the version checks, everything flashes fine after that and works as normal but they forgot to add the version numbers in the check.
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
TMobile version US
SinisterSincere said:
TMobile version US
Click to expand...
Click to collapse
Bad downloads? Try from your computer.
Sent from my GT-N7105 using Tapatalk 2
I've been a long time cm fan until 4.1 TW. That being said I had to try the official nightly and I gotta say it's real cool. 4.2.1 changes with com's twist is very nice. Dare I say it might even be snappier than stock
Sent from my GIANT internet thingy.
This rom does work with T-mobile note 2 right? Just making sure.
pwner325 said:
This rom does work with T-mobile note 2 right? Just making sure.
Click to expand...
Click to collapse
It does... original development thread has cm 10.1 nighties... few days in now... BT and a few other minor kinks
Sent from my SGH-T889 using xda app-developers app
Initially had the cant mount problem with CWM:
New recoveries for new phones that won't mount storage!!
http://forum.xda-developers.com/showthread.php?t=2391616
Starting new thread for the other big problem:
After getting either TRRP or CWM on and mounting and backup/restoring properly flashed stable CM10.1 (and a ton of other releases) along with CARBON cannot boot past the Samsung Galaxy SIII splash screen.
What did Sprint do here to screw us out of ditching their stock build?!?!
Most say its the kernel or something about boot images on the aosp ROMs needs to be modified. They way it looks new s3 users are gonna be waiting for a whilr
Sent from my SPH-L710 using XDA Premium 4 mobile app
Figures I had to replace my freshly shattered screen CM7 Evo 4G right in the middle of a code conundrum
Well hopefully the powers that be can update this thread with the progress so we know when we can rock some badass custom roms.
Noobnl posted an experimental fix to try in the new recoveries thread.
kennyglass123 said:
Noobnl posted an experimental fix to try in the new recoveries thread.
Click to expand...
Click to collapse
I flashed it and instead of hanging on the little blue man my phone hung on the black screen. I tried the nightly that a few others had working and I cant even get that one to boot.
I've been able to get several older ROMS to work fine. So long as they are 4.2.1 ROMs there is a chance it will work. I've been unable to get any 4.2.2 or higher ROM to work.
VMU SPH-L710 GS3
JZO54K.L710VPAMG2
Factory 4.1.2 Phone
Do they flash correctly? in CWM or TWRP? Very weird. It's practice to do Factory Reset, Clear Cache, Clear D Cache, Fix Permissions, then install your Rom.
That is what your doing? Then rebooting into it? and you get stuck on black screen?
youngnex said:
Do they flash correctly? in CWM or TWRP? Very weird. It's practice to do Factory Reset, Clear Cache, Clear D Cache, Fix Permissions, then install your Rom.
That is what your doing? Then rebooting into it? and you get stuck on black screen?
Click to expand...
Click to collapse
Correct. Im very familiar with flashing. No dirty flash. I've tried the CWN (fixed one) and TWRP with no joy. Wont even boot enough for me to get a logcat.
Moped_Ryder said:
Correct. Im very familiar with flashing. No dirty flash. I've tried the CWN (fixed one) and TWRP with no joy. Wont even boot enough for me to get a logcat.
Click to expand...
Click to collapse
I am doing the same things and getting the same result. I am seriously considering selling this s3 and buying an older one.
Any progress?
Just checking to see if any progress was made to get past the hanging blue man samsung screen? I would love to put cyanogen 10.2 on my wifes newer gs3. Thanks again.
The newer s3's have a safeguard in place which will not allow you to mount storage in recovery. You need a modded recovery for the newer devices(several threads) and this will allow you to flash Touchwiz ROMs only AOSP ROMs are still not working on these newer devices.
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 11:57 AM ---------- Previous post was at 11:55 AM ----------
Toeonly said:
I am doing the same things and getting the same result. I am seriously considering selling this s3 and buying an older one.
Click to expand...
Click to collapse
There's devs working on a solution, unfortunately this like this take a long time
Sent from my SPH-L710 using xda app-developers app
IDontKnowMang said:
The newer s3's have a safeguard in place which will not allow you to mount storage in recovery. You need a modded recovery for the newer devices(several threads) and this will allow you to flash Touchwiz ROMs only AOSP ROMs are still not working on these newer devices.
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 11:57 AM ---------- Previous post was at 11:55 AM ----------
There's devs working on a solution, unfortunately this like this take a long time
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Since I am fairly new to rooting and flashing roms, was this a similar problem with aosp roms in the past? if so what kind of time table are we looking at?
ijimkoz said:
Since I am fairly new to rooting and flashing roms, was this a similar problem with aosp roms in the past? if so what kind of time table are we looking at?
Click to expand...
Click to collapse
No, this was only with the S3's purchased within the last 2 to 3 months
cm10.2 now working
you should be able to install the latest nightily and it not get stuck on cid, Thanks to Invisiblek he was able to find the problem from my phone, it works now so please give thanks to Invisiblek and all the others who helped.
killernos said:
you should be able to install the latest nightily and it not get stuck on cid, Thanks to Invisiblek he was able to find the problem from my phone, it works now so please give thanks to Invisiblek and all the others who helped.
Click to expand...
Click to collapse
What what what??!!?
What nightly?
Sent from my SPH-L710 using Tapatalk 4
thznutz87 said:
What what what??!!?
What nightly?
Sent from my SPH-L710 using Tapatalk 4
Click to expand...
Click to collapse
Looks like it was!
Starting from 9/22 nightly
https://github.com/CyanogenMod/andr...mmit/b0cd8e73f2c8a34760e3f88843d6a217bd8032c8
CNexus said:
Looks like it was!
Starting from 9/22 nightly
yep it had something to do with the system not wanting to mount.
Click to expand...
Click to collapse
killernos said:
CNexus said:
Looks like it was!
Starting from 9/22 nightly
yep it had something to do with the system not wanting to mount.
Click to expand...
Click to collapse
Yeah, I saw the commit
Click to expand...
Click to collapse
CNexus said:
killernos said:
Yeah, I saw the commit
Click to expand...
Click to collapse
I can confirm its a fix. Very sweet.
Click to expand...
Click to collapse
It's in the kernel
Sent from my SPH-L710 using Tapatalk 4