Related
Hi all, this is my first post and i hope to take advantage from it.
I've done a lot of research in the android development forums. The first thing i did to my phone was to get it rooted. So far so good, i followed the instructions and everything went ok.
Now i want to install a ROM. Thing is there is a lot of terminology i do not quite understand and i want to know for sure how this process is done correctly. In theory i know how to install a ROM but some disclaimers keeps me from doing it.
The main question here is, my phone has to meet some prerequisites in order to install a ROM? I mean, the android version of my phone, baseband version, kernel version and build number necessarily need to have the same characteristics from the ROM i will be flashing? For example, Team Kang's Juggernaut base band version is T989VKID mine is T989UVKL1, the android version is 2.3.5, mine is 2.3.6 and so on. That basically is it. I do not want to mess up my phone but at the same time i wanna enjoy those great roms.
Thanks in advance and i wish a happy valentine's day to all
Download ROM manager. Pick install from sd card. Wipe data and cache. Pick the ROM you downloaded. Just make sure you only install roms from this forum
Sent from my SGH-T989 using xda premium
The answer to your question is basically no. Roms don't change your baseband. So that doesn't matter. If your on 2.36 and you install a 2.35 ROM you'll just be on 2.35. But in the case of a kickass ROM that would be just fine.
Sent from my SGH-T989 using xda premium
Android_Monsters said:
The answer to your question is basically no. Roms don't change your baseband. So that doesn't matter. If your on 2.36 and you install a 2.35 ROM you'll just be on 2.35. But in the case of a kickass ROM that would be just fine.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
thanks, i appreciate the help. that info was very helpful.
Android_Monsters said:
The answer to your question is basically no. Roms don't change your baseband. So that doesn't matter. If your on 2.36 and you install a 2.35 ROM you'll just be on 2.35. But in the case of a kickass ROM that would be just fine.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
another quiestion, can i perform a nandroid backup on mmy internal sd card abd restore from there without a problem or do i really need to have an external sd?, in case that there is no problem back up to the internal sd, can i later move the back up file in case i get an external sd card? thanks
DarkKnight1 said:
another quiestion, can i perform a nandroid backup on mmy internal sd card abd restore from there without a problem or do i really need to have an external sd?, in case that there is no problem back up to the internal sd, can i later move the back up file in case i get an external sd card? thanks
Click to expand...
Click to collapse
You can do backups from whichever source, it doesnt matter
Sent from my SGH-T989 using Tapatalk
Thank you Dark Knight. I am in the same situation as you. The only difference is that I have yet to root my phone because I haven't gotten a microSD card yet. Would you mind me PMing you with some questions? haha, noob to noob.
DKfilms13 said:
Thank you Dark Knight. I am in the same situation as you. The only difference is that I have yet to root my phone because I haven't gotten a microSD card yet. Would you mind me PMing you with some questions? haha, noob to noob.
Click to expand...
Click to collapse
greetings DKfilms, is good to know that there are some people around here wondering the same questions. And no i don't mind feel free
iLeopard said:
You can do backups from whichever source, it doesnt matter
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
thank you so much for helping, ive been looking to confirm all this info. thanks
Hey i succesfully installed the juggernaut rom thanks for the info again.
Sent from my SGH-T989 using Tapatalk
instead of using rom manager, I would suggest doing everything from the CWM recovery itself. The manual way is always better and you encounter less problems along the way..
i.e. backup/restore isn't complete. didn't wipe everything clean... etc.
Teo032 said:
instead of using rom manager, I would suggest doing everything from the CWM recovery itself. The manual way is always better and you encounter less problems along the way..
i.e. backup/restore isn't complete. didn't wipe everything clean... etc.
Click to expand...
Click to collapse
Yeah that's what I do, besides I hate how rom manager saves backups on my internal memory
Sent from my SGH-T989 using Tapatalk
I could be wrong but I think the last version of CWM wont let you make backups to the internal but you can flash from the internal. But the newest touch version that just came out a few weeks ago does have internal suppoert for backups so you have to flash the latest one. And I would listen to them when they say not to use rom manager there are far too many problems with it. Also the latest version of juggs is 4.1 and that is 2.3.6. I would use that one. Good luck
mojorisin7178 said:
I could be wrong but I think the last version of CWM wont let you make backups to the internal but you can flash from the internal. But the newest touch version that just came out a few weeks ago does have internal suppoert for backups so you have to flash the latest one. And I would listen to them when they say not to use rom manager there are far too many problems with it. Also the latest version of juggs is 4.1 and that is 2.3.6. I would use that one. Good luck
Click to expand...
Click to collapse
I installed the rom without a problem. Im running it right now and im getting used to it. Still got to figure out some of the features but i will get there.
Sent from my SGH-T989 using Tapatalk
DarkKnight1 said:
Hey i succesfully installed the juggernaut rom thanks for the info again.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Just remeber, just because it says galaxy s2 doesnt mean it wont brick your phone. We see this way too often.
Only use roms here and the skyrocket forums NOT the att S2
Sent from my SGH-T989 using xda premium
avarize said:
Just remeber, just because it says galaxy s2 doesnt mean it wont brick your phone. We see this way too often.
Only use roms here and the skyrocket forums NOT the att S2
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Im very aware of that. I once read a post where a guy flashed an I9000 rom into the T989. I only visit this part of the forums so dont worry but thank you anyways for the advice.
Sent from my SGH-T989 using Tapatalk
DarkKnight1 said:
Im very aware of that. I once read a post where a guy flashed an I9000 rom into the T989. I only visit this part of the forums so dont worry but thank you anyways for the advice.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
i give you props for having enough common sense to only visit this part of forums and actually reading b4 flashing...now if only everyone had same level common sense as you
bobby3306 said:
i give you props for having enough common sense to only visit this part of forums and actually reading b4 flashing...now if only everyone had same level common sense as you
Click to expand...
Click to collapse
Yes i hope that newcomers take the time to read everything carefully. Hey i got a question... This is the very first rom i flashed to my phone. If i want to switch from one rom to another, i just cant flash it over the current one right? Phone might brick? What do i need to know before flashing a new rom to my phone. Thanks
Sent from my SGH-T989 using Tapatalk
DarkKnight1 said:
Yes i hope that newcomers take the time to read everything carefully. Hey i got a question... This is the very first rom i flashed to my phone. If i want to switch from one rom to another, i just cant flash it over the current one right? Phone might brick? What do i need to know before flashing a new rom to my phone. Thanks
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
You normally have to do a full wipe b4 installing a different ROM.
Chk out this site (galaxys2root.com) it gives me a lots of EASY TO UNDERSTAND info when i started playing with ROMs.Currently i am on my fifth ROM .
Yes do full wipe, Clear caches and do a nandroid back up first thou and make sure after flashing and re booting to let it sit for 10min
Sent from my SGH-T989 using XDA App
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
I'm not trying to break rules. Unsure if I am. But I have a CDMA HTC one v for virgin mobile and I accidentally went to the HTC one v original development sub forum and downloaded slim bean. Umm every thing is fully functional except WiFi. Thoughts??
Sent from my PK7630000 using xda app-developers app
cjtulowiecki said:
I'm not trying to break rules. Unsure if I am. But I have a CDMA HTC one v for virgin mobile and I accidentally went to the HTC one v original development sub forum and downloaded slim bean. Umm every thing is fully functional except WiFi. Thoughts??
Sent from my PK7630000 using xda app-developers app
Click to expand...
Click to collapse
Questions should go in the Q&A section for future reference, however, since you're here I'll try to help. Did you flash the boot.img that can be found inside the zip before flashing the rom? (or after... I think either way is okay to do) I would try that and see if it works. As long as you downloaded the slimbean for primoc (which is our cdma phones) you should be good It's a great rom
Edit: what I mean by flashing the boot.img is fastboot flash boot boot.img in fastboot usb mode from bootloader, then flash the slimbean rom (.zip file) in recovery
Right. I flashed the boot.IMG in fast boot after I installed the rom. Maybe its just bad luck this time. I'll wipe everything and re flash everything. I just thought since the ROM was in HTC one v original that it was for a different version of the phone.
Sent from my PK7630000 using xda app-developers app
cjtulowiecki said:
Right. I flashed the boot.IMG in fast boot after I installed the rom. Maybe its just bad luck this time. I'll wipe everything and re flash everything. I just thought since the ROM was in HTC one v original that it was for a different version of the phone.
Sent from my PK7630000 using xda app-developers app
Click to expand...
Click to collapse
Maybe it does matter what order you flash things in, but if the title of the thread says CDMA or PrimoC then it's for virgin mobiles one v and last I checked SlimBean had wifi working... so try flashing the boot.img in bootloader first (you may not have to repeat this if you already did it, but just in case it didn't go through or something), then try wiping and reinstalling slimbean (and probably gaps) in recovery
it should work this time, but if not then I'd try supersick kernel (01032013 version should be good)
Hey thanks for the help man. I'll try it out shortly
Sent from my PK7630000 using xda app-developers app
cjtulowiecki said:
Hey thanks for the help man. I'll try it out shortly
Sent from my PK7630000 using xda app-developers app
Click to expand...
Click to collapse
i did read something about getting the boot.img from the op and not using the one in the rom
Nah it just says use whatever the CDMA cm10 kernel is, which in our case the best bet would be probably simon's supersick kernel, but I do think the one in the ROM zip works just fine I'm about to test this out myself, so if you wanna wait ten minutes for me to get back, I'll let you know
---------- Post added at 12:14 PM ---------- Previous post was at 11:46 AM ----------
Alright so to hopefully save you some trouble and lost data, I went ahead and followed the steps you took. no wifi... I followed what I told you, and again got no wifi, but I simply flashed a new kernel (I used simons SuperSick_1-2JB.img) and got wifi to work
sorry for the misunderstanding and leading you astray, and sorry Jared... guess you were right on this one Hope I helped and now I get to enjoy slimbean too haha
Edit: Great... now I'm having issues with not being able to download or update apps... guess I'm gonna try out black jelly since I know Provision is a great rom lol but grr... let me know if you have that problem too?
lilrob1213 said:
Nah it just says use whatever the CDMA cm10 kernel is, which in our case the best bet would be probably simon's supersick kernel, but I do think the one in the ROM zip works just fine I'm about to test this out myself, so if you wanna wait ten minutes for me to get back, I'll let you know
---------- Post added at 12:14 PM ---------- Previous post was at 11:46 AM ----------
Alright so to hopefully save you some trouble and lost data, I went ahead and followed the steps you took. no wifi... I followed what I told you, and again got no wifi, but I simply flashed a new kernel (I used simons SuperSick_1-2JB.img) and got wifi to work
sorry for the misunderstanding and leading you astray, and sorry Jared... guess you were right on this one Hope I helped and now I get to enjoy slimbean too haha
Edit: Great... now I'm having issues with not being able to download or update apps... guess I'm gonna try out black jelly since I know Provision is a great rom lol but grr... let me know if you have that problem too?
Click to expand...
Click to collapse
Black Jelly has some java problems. PACman v19.3 is the most functional so far!
Threads will always be moved without our help. Mods are top goons around here
But anyways, every thing said above yes.
Be sure to always check the broken list too
Sent from my HTC One V using Tapatalk 2
Closed
Wrong section.
Next time please read and respect the rules before posting
So i just wanted to know which people prefer and why. personally i prefer CWM because it was the first recovery i used and it is just easier to navigate in my opinion.
I've tried both on the SGS3. IMO CWM is better on the SGS3, than TWRP.
TEAM MiK
MikROMs Since 3/13/11
I started with cwm touch, and really liked it. Switched to twrp when I installed a custom rom (at their suggestion). Now I really don't have a preference. I keep both zips on my extsd, so I can switch to whatever I want to use...
Sent from my SPH-L710 using xda app-developers app
Shortly after I installed TWRP on my Epic, it hard bricked when installing a ROM. I cannot say for sure it was because of TWRP, but when that happened I've never tried TWRP again, and I haven't had another bricked phone. Coincidence?? Possibly.
TWRP FTW
IBTW it had it issues with The Epic 4G Touch but not anymore that a thing of the past.
Sent from my SPH-L710 using Tapatalk 2
I'm very new to this phone although not to rooting. Neither CWM or TWRP were good on the EVO 4G. As a matter of fact if someone asked for help or had trouble flashing the 1st order of business was to ditch either of those recoveries and install amon_ra.
Consequently I've wanted to ask this question too and I'm gonna keep an eye on this thread.
TWRP. It's the obvious choice. :good:
Cnexus built a recovery switcher that allows you to switch between cwm/cwm touch/twrp. I say install it, and try em all out
I know the first time I used twrp, I had an issue because if you have it set to check mdsum, it will fail if it can't find one. Simple, but it did kinda freak me out.
Sent from my SPH-L710 using xda app-developers app
eisawi99 said:
So i just wanted to know which people prefer and why. personally i prefer CWM because it was the first recovery i used and it is just easier to navigate in my opinion.
Click to expand...
Click to collapse
I thought the same thing for a bit. Then I used TWRP 2.4.40 PR 2.4.2.0 or whatever that one was called, and I am loving it. Works perfectly fine for me. Used a flash able zip too.
------------------------
Sprint Galaxy S3 "Supernexus"
Whiplashh Rom
Look it up.
CWM doesn't let you queue multiple zips as far as I can tell, so I've been using TWRP.
TWRP all the way, plus you can theme it! The one and only thing that annoys me about TWRP is that the clock is always off -__-
Both are great and different roms need either to work right. But in my experience trwp backs up and restores without error. Clockwork never restored properly on any of my phones from og evo, evo lte or my sgs3. But clockwork flashes radio updates better, at least my reception bar level or data connectivity.
Sent from my SPH-L710 using xda premium
socos25 said:
Shortly after I installed TWRP on my Epic, it hard bricked when installing a ROM. I cannot say for sure it was because of TWRP, but when that happened I've never tried TWRP again, and I haven't had another bricked phone. Coincidence?? Possibly.
Click to expand...
Click to collapse
Coincidence, the epic 4G has a bug that caused it to hardbrick when flashing certain roms (memory fault in the kernel or something like that). There was a workaround for this though.
Might as well put my 2 cents in. I have used both recoveries on my devices. I have no personal choice as to one is better than te other issue. I can tell that once cwm was actually fixed and built for the Epic it worked perfectly prior to that when it was first ported over to the OG Epic it was hit or miss, the orange cwm. Oh well my Epic did just fine on both. My Galaxy Nexus works better with TWRP for whatever reason it just does and my S3 prefers CWM again never had an issue with either on those devices but when I use the other recovery on each of those devices they become temperamental and start acting up. I know it's funny but that's what I know of my devices. They are both very good recoveries and they have come a long way since the early days.
Sent from the future via Xparent Green Tapatalk 2
edfunkycold said:
Might as well put my 2 cents in....
Sent from the future via Xparent Green Tapatalk 2
Click to expand...
Click to collapse
So let me ask this: when a rom dev suggests a recovery, is that just because that's what the rom was tested with? Have you had an instance where you've *had* to use a specific recovery (other then one kind working better on a specific phone)?
Thanks
Sent from my SPH-L710 using xda app-developers app
I'm not sure how themeing a recovery is useful? It's not like I'm showing my friends, hey look at this cool recovery. But which ever is fine.
Joe0113 said:
TWRP all the way, plus you can theme it! The one and only thing that annoys me about TWRP is that the clock is always off -__-
Click to expand...
Click to collapse
Sent from my SPH-L710 using xda premium
---------- Post added at 10:26 PM ---------- Previous post was at 10:22 PM ----------
I flashed a lot of Roms on my epic, yes it could be coincidence, but like I said, shortly after flashing TWRP I was warranting my phone because it didn't make it through a flash. I tried everything including once when odining my epic my daughter yanked the plug out. I recovered from that even by removing my battery and plugging it into the computer. After TWRP, I couldn't even do that. And really I have no idea if it was the recovery, but yeah, I chose CWM.
CNexus said:
Coincidence, the epic 4G has a bug that caused it to hardbrick when flashing certain roms (memory fault in the kernel or something like that). There was a workaround for this though.
Click to expand...
Click to collapse
Sent from my SPH-L710 using xda premium
g_money said:
So let me ask this: when a rom dev suggests a recovery, is that just because that's what the rom was tested with? Have you had an instance where you've *had* to use a specific recovery (other then one kind working better on a specific phone)?
Thanks
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No makes no difference, that's because that person has a personal liking for that recovery or like I said his device just responded better to that recovery. Makes no difference roms are not built for specific recoveries. Well not always there was an instance on the OG Epic where in order to flash cm9 the phone had to be re partitioned and a special recovery was necessary and the cm team built the recovery flash into the rom. That's another story for a different thread.
Sent from the future via Xparent Green Tapatalk 2
g_money said:
So let me ask this: when a rom dev suggests a recovery, is that just because that's what the rom was tested with? Have you had an instance where you've *had* to use a specific recovery (other then one kind working better on a specific phone)?
Thanks
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Sometimes recoveries don't like certain roms...doesn't happen often, but it can
I know on my EVO Shift, Sense roms could be flashed ONLY with CWM for some reason, as TWRP wouldn't flash it properly.
CNexus said:
Sometimes recoveries don't like certain roms...doesn't happen often, but it can
I know on my EVO Shift, Sense roms could be flashed ONLY with CWM for some reason, as TWRP wouldn't flash it properly.
Click to expand...
Click to collapse
So betweem you and ed, I should be able to flash a rom with either recovery unless posts show problems flashing with a specific one. And, if I *were* to have problems flashing, I may want to attempt to flash using a different recovery....
If that's the case, I just might pick one recovery, and stick with it!
Sent from my SPH-L710 using xda app-developers app
I started out using CWM but lately I've been using TWRP instead and I like the large buttons and touch interface of it. I'm sticking with it I think.
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