[Q] Custom Recovery and Rom Question - Verizon Samsung Galaxy S 4

I'm sure this has been asked but I just wanted to verify I had my information correct, I have rooted and put custom roms on a gs3 in the past so I have little experience but don't want to brick my gs4 and it seems it may be a slightly difference process.
Essentially I want to get CM10 on my Verizon GS4
I found these root directions here http://forum.xda-developers.com/showthread.php?t=2290798
They seem pretty straight forward. I would assume I follow these directions and install TWRP or clockwork mod after its rooted then just flash my roms, however I saw something about Loki on another thread and getting around the bootloader. Do I have to do anything special involving that or once I am rooted can I just install the custom recovery from the app store and start installing roms...
Also how do I check if I have the update that just came out that prevents flashing roms.
Sorry if this was asked but I didn't see my specific question anywhere and I would really appreciate the help.
Also would you recommend going with the google edition or CM10?

Questions and Help issues go in Q&A and Help section
Thread moved

Im fairly certain TWRP is pre-loki'd now, so you wont have to worry about it.
In about phone, look under baseband version, If it doesn't say i545VRUAMDK then you have the new update that isnt rootable yet.
And for your last question, i havent tried either of them yet (I'm on hyperdrive).

Related

SGS2 - Root / Kernel / ROM?

Hi All.
I last rooted a HTC Desire well over a year (or 2) ago and I am now looking into rooting my Samsung Galaxy S2 - I9100, from Optus in Australia.
Although well versed, I am finding myself in noob land trying to read and firgure out what is the correct way to alter my phone.
Firstly I apologise for posting something that I am sure is answered out here. So please just point me to the right place and close this thread if so.
I can see that the standard boot loader (hope I refer to that correctly) appears to allow you to install another OS (ROM).
This appears to be called ODIN.
Am I able to load new ROMs by using the default ODIN on the phone, or do I need to load something like ClockworkMod?
I am intending to download and install the generic stock ROM (non-carrier) version before looking into other variants.
I am assuming to load other ROMs, like say Cyanogen 9, I would have to go through the root process.
Aside from rooting, I am reading posts that refer to updating the kernel. What is the kernel and why do I need to change it?
Thanks in advance for any assistance.

[Q] First time unlocking bootloader, root and install custom ROM

The short story (MODS please move this to correct forum if required)
How do I:
Unlock the bootloader
Root the TF201
Install CWM or TWRP
Install a custom ROM
I have a TF201 on JB 4.1.1 build no: 10.4.2.15
It has never been rooted or bootload unlocked
The Long Story
Hi all
I am sure the above question has been asked about a thousand times but here goes (MODS move this thread to correct thread if in the wrong place)
I have owned an Asus TF201 since about March, bought brand new from ebuyer.com, as i was new to android back then i didn't dare root it or unlock the bootloader in case i voided my warranty etc.
Since then my Prime has received all its updates via OTA and the current build is 10.4.2.15 on JB 4.1.1, it has never been rooted or bootload unlocked, it is in pristine unmodified condition.
In the mean time i got a Samsung Galaxy S3 and having played around with that got brave, i rooted it using CF Root method which automatically installed CMW Recovery and then proceeded to flash the Wanamlite ROM and have been happy with it since.
I am now looking to install a custom ROM on my PRIME it but have come across the fact that its not as easy or straight forward as the S3
Firstly, as its never been bootloader unlocked, rooted or modified in anyway shape or form it might be a bit tougher.
I have stumbled upon the fact that to install a custom rom, i need TWRP or CWM (or both (not sure)) installed which needs it to be rooted and in order to root i need to unlock the bootloader.
I have googled high and low on XDA, youtube and while they all point to an official Asus Bootloader unlocker, the Asus website claims that this is for ICS only (i'm on JB now in case you missed it), also a lot of the info out there is out of date since Asus has made changes.
So my question is as follows:
How do i unlock the bootloader? Everyone keeps mentioning an official Asus unlocker but its says for ICS ONLY and how do i run it
How do i root? - is there something like CF Root which was for the SGS3
Once i have the above do i then use TWRP or CWM or both to install a custom ROM?
I am aware that unlocking the bootloader voids warranty, i am aware that installing a custom ROM increases the binary counter, i am ware that bricking is possible (but lets try and minimize that), i am aware of those as i was warned about them from general research on wanting to do this and from modifying my S3.
Basically to use a custom rom on this device you download the unlocker tool from Asus (Says ICS only but works on JB, know from experience. Did it myself). It is an application and all you do is connect to the internet and run it. Once unlocked you can flash TWRP/root your device. Use either the guide on their website or go on youtube and look at some videos. There are step by step guides that show it all on video. Once you have TWRP you can head over to the dev section for the TF201 and download one of the custom roms (Hairybean 1.4 is supposed to drop soon, I'd suggest that one) and use the in-thread guide to flash it.
My #1 tip to you is read. read, and read it again. Understand it all and then proceed. Asking questions before you flash is better than doing it wrong and posting in the thread saying you bricked your prime then the OP/devs have to help you through the unbrick process. Questions are almost always answered quickly and in a friendly manner. Hope I helped
I think what he is asking for... is a full step by step guide... from a full stock JB locked TF201.... and I think It would be nice for all...
See U.
Istarth said:
I think what he is asking for... is a full step by step guide... from a full stock JB locked TF201.... and I think It would be nice for all...
See U.
Click to expand...
Click to collapse
This is exactly what i mean, all the information is fragmented all over, not just on XDA but also on other Android /TF201 forums, in some places its clearer in others a bit obscure or vague or worse out of date since them Asus c**ks keep changing stuff
The Galaxy S3 Dev forums are far clearer and have step by step guides on how to do this, personally i hate watching them youtube videos whilst they are trying to help and plus points for the effort they put in, a lot of the people doing it just waffle in them and i still prefer the old fashion of step by step guides.
I learned how to go from stock S3 to Wanamlite ROM all in one evening and it was quick and painless.
But thanks for your help regarding using the Asus official tool for ICS works for JB, might now try it tomorrow or the day after.
I started a guide thread.
Sent from my Zio using xda app-developers app
Wow that guide would be awesome. I'm in the same situation as Shizbazki and I find it hard to get all the info to one and do it.
http://forum.xda-developers.com/showthread.php?t=1998359
Link to my guide thread in the general forum. If anybody has any questions you can PM me or comment there and it'll likely be answered quickly. I'll gladly guide anyone through this process if they need other information.
NM. thanks, McJesus.

[Q] A beginner's plunge with follow-up questions

Hi all, I'm enjoying reading lots in this forum in order to learn how to unleash my S3. One massive thank you to all who make this community such a great and rich resource. Thanks!
After reading a bunch, I took the XDA plunge. Here's what I've recently done (maybe this will help someone who's considering taking the plunge too. I was surprised at how easy everything was). I rooted my i9300 by flashing CF-AutoRoot via Odin. I then downloaded GooManager from the Market. It installed an open recovery script for me, TWRP. Next, I rebooted to TWRP recovery mode and did a backup and then a factory reset. I flashed temasek's build (v20) of Android 4.3/10.2 with the latest gapps zip (20130813). Then came the moment of truth. I was nervous when my phone took a bit longer to boot. The sweet Cyanogenmod logo just kept swirling. Finally, it booted and I was in love.
I have just a few questions about my phone now.
First, is the TWRP backup I did adequate to get me out of serious trouble if something goes wrong flashing updates? The backup ended up being over 2gb!
Secondly, have I done anything to the kernel? If not, should I?
Thirdly, have I done all that rooting and custom roms have to offer? Do I now just update my rom when new builds come out and continue enjoying my phone? If so, that's great. Just wondering what if anything I could do next, apart from trying other custom roms.
Lastly, what's the proper way to get help troubleshooting glitches/bug with the custom rom I'm using since I'm not yet able to post in its development forum thread? For example, my bluetooth won't turn off and in some apps the screen flickers or doesn't seem to render the window properly.
Thanks in advance.
oceo said:
Hi all, I'm enjoying reading lots in this forum in order to learn how to unleash my S3. One massive thank you to all who make this community such a great and rich resource. Thanks!
After reading a bunch, I took the XDA plunge. Here's what I've recently done (maybe this well help someone who's considering taking the plunge too). I rooted my i9300 by flashing CF-AutoRoot via Odin. I then downloaded GooManager from the Market. It installed an open recovery script for me, TWRP. Next, I rebooted to TWRP recovery mode and did a backup and then a factory reset. I flashed temasek's build (v20) of Android 4.3/10.2 with the latest gapps zip (20130813). Then came the moment of truth. I was nervous when my phone took a bit longer to boot. The sweet Cyanogenmod logo just kept swirling. Finally, it booted and I was in love.
I have just a few questions about my phone now.
First, is the TWRP backup I did adequate to get me out of serious trouble if something goes wrong flashing updates? The backup ended up being over 2gb!
Secondly, have I done anything to the kernel? If not, should I?
Thirdly, have I done all that rooting and custom roms have to offer? Do I now just update my rom when new builds come out and continue enjoying my phone? If so, that's great. Just wondering what if anything I could do next, apart from trying other custom roms.
Lastly, what's the proper way to get help troubleshooting glitches/bug with the custom rom I'm using since I'm not yet able to post in its development forum thread? For example, my bluetooth won't turn off and in some apps the screen flickers or doesn't seem to render the window properly.
Thanks in advance.
Click to expand...
Click to collapse
1. A backup is always adequate on almost all situations and that size is acceptable since most of my backups are around 1.41 gb but I recommend that you also backup your efs since it's one of the most important things to backup on our devices. More info here: http://forum.xda-developers.com/showthread.php?t=1308546
2. As far as I know any cyanogenmod based firmware installs it's own custom kernel however this is highly reversible as soon as you flash a stock firmware again.
3. Well the possibility of having a rooted phone are endless. In xda you'll find vast amount of tweaks, roms, kernels etc that you can flash on your device. Even I still keep on flashing things (with precautions of course) whenever i find something interesting.
4. Until you can post that thread just keep posting your question here in the Q & A but search the topic you have in mind first since it's most likely been asked before, just to keep the forum clean as much as possible.
oceo said:
Hi all, I'm enjoying reading lots in this forum in order to learn how to unleash my S3. One massive thank you to all who make this community such a great and rich resource. Thanks!
After reading a bunch, I took the XDA plunge. Here's what I've recently done (maybe this will help someone who's considering taking the plunge too. I was surprised at how easy everything was). I
I have just a few questions about my phone now.
First, is the TWRP backup I did adequate to get me out of serious trouble if something goes wrong flashing updates? The backup ended up being over 2gb!
No its not It has note backed up EFS .
Secondly, have I done anything to the kernel? If not, should I?
Your choice .
Thirdly, have I done all that rooting and custom roms have to offer? Do I now just update my rom when new builds come out and continue enjoying my phone? If so, that's great. Just wondering what if anything I could do next, apart from trying other custom roms.
Your choice as to try other roms or mods .
Lastly, what's the proper way to get help troubleshooting glitches/bug with the custom rom I'm using since I'm not yet able to post in its development forum thread? For example, my bluetooth won't turn off and in some apps the screen flickers or doesn't seem to render the window properly.
Some roms have a Q&A thread or discussion thread . Usually problems are posted in the rom thread .
Click to expand...
Click to collapse
Thanks for the replies. I booted into recovery and used TWRP to do an EFS backup. Super easy.

[Q] Looking for info/advice on what to do next

I got my GS4 back in the summer and I promptly rooted and I believe I even was able to unlock the bootloader. I then flashed Eclipse S4 TW edition (based on MDK) and its been so rock solid I haven't had a reason to touch is since. I'm been staring at my android 4.2.2 version and have been thinking no reason to upgrade. If it isn't broke don't fix it right? Well I'm starting to feel the flashing itch so I decided to jump back on XDA and see whats out there.
I'm trying to get a grasp on what all has changes since the last time I flashed my phone. It looks like there has been a few new builds to drop since I flashed. I'm confused on the details though. With my current state can I flash anything I want using the custom recovery or are there restrictions that I must follow. I have seen posts about using SafeStrap for flashing. I remember SafeStrap from my Razr days as a solution for phones with locked bootloaders. Does one of the OTA's relock the bootloader and make it impossible to unlock or are the SafeStrap posts for people that got the phones after me which already came with a locked bootloader?
Any reason why not to upgrade to the newest builds? I can't find any details on what is different between the builds but I have to imagine there is some new stuff that I might want to play with.
Lastly, can anyone suggest a good solid ROM to similar to Eclipse TW that is based on a newer build?
I appreciate any help you guys can give me. Being away this long and coming back is slightly overwhelming and who has time to navigate through every page of every thread for the past 6 months or so.
I would suggest to read some of the threads....custom Roms for 4.3 and 4.4 are a bit slow in coming. If you are mdk...no need for safestrap....you can still keep your phone rooted and loki'd..and move to 4.3 base
powered by hashcode safestrap hyperdrive 10.2
trevoryour said:
I got my GS4 back in the summer and I promptly rooted and I believe I even was able to unlock the bootloader. I then flashed Eclipse S4 TW edition (based on MDK) and its been so rock solid I haven't had a reason to touch is since. I'm been staring at my android 4.2.2 version and have been thinking no reason to upgrade. If it isn't broke don't fix it right? Well I'm starting to feel the flashing itch so I decided to jump back on XDA and see whats out there.
I'm trying to get a grasp on what all has changes since the last time I flashed my phone. It looks like there has been a few new builds to drop since I flashed. I'm confused on the details though. With my current state can I flash anything I want using the custom recovery or are there restrictions that I must follow. I have seen posts about using SafeStrap for flashing. I remember SafeStrap from my Razr days as a solution for phones with locked bootloaders. Does one of the OTA's relock the bootloader and make it impossible to unlock or are the SafeStrap posts for people that got the phones after me which already came with a locked bootloader?
Any reason why not to upgrade to the newest builds? I can't find any details on what is different between the builds but I have to imagine there is some new stuff that I might want to play with.
Lastly, can anyone suggest a good solid ROM to similar to Eclipse TW that is based on a newer build?
I appreciate any help you guys can give me. Being away this long and coming back is slightly overwhelming and who has time to navigate through every page of every thread for the past 6 months or so.
Click to expand...
Click to collapse
Ok, So heres what you missed. After the MDK release they(Verizon/Samsung) patched the loki bootloader hack so thats why anybody whos not on the MDK release has an locked bootloader. That is where safestrap comes in. Safestrap is a custom recovery that was developed by Hascode, in order to provide those with a locked bootloader a way to get in on the rom action, while keeping there stock rom untouched.
Now that said i would advise you to update but not through the stock "Check Update" tab (as that will lock your phones bootloader). Instead you should just flash a rom that is built with the new update as the base (E.X. Hyperdrive 11). This will allow you to get the new update without locking your bootloader.
Now for roms, i believe there is an updated Eclipse TW Rom & Eclipse AOSP ROM on the Dev's site ( dont know the link but will post it once i find it).

New to S4

So I just got handed an S4 from a co-worker, I just spent an hour looking up info on root and stuff to load custom roms (looking mainly for CM11). My main problem seems to be all the shortened terms and everything associated with this phone, root vs unlocked bootloader vs etc, MK2?? NC5??. I can't seem to find any "newb" friendly breakdown of all of this. This isn't my first hacked device by far (I got an old DiNC and a ReZound for my last 2), but definitely the most confusing one. So here's the info I got on my phone: Galaxy S4, Verizon, SCH-I545, Android 4.4.2, VRUFNC5, hardware version: I545.06.
Can anyone point me in the right directions to understand better, and get me to my final destination of Custom rom? Or at least get me to understand this better?
I did search the first 5 pages of every section to see if there was a "newb-friendly" sticky but didn't seem to go anywhere fast, just made me more confused.
tong6998 said:
So I just got handed an S4 from a co-worker, I just spent an hour looking up info on root and stuff to load custom roms (looking mainly for CM11). My main problem seems to be all the shortened terms and everything associated with this phone, root vs unlocked bootloader vs etc, MK2?? NC5??. I can't seem to find any "newb" friendly breakdown of all of this. This isn't my first hacked device by far (I got an old DiNC and a ReZound for my last 2), but definitely the most confusing one. So here's the info I got on my phone: Galaxy S4, Verizon, SCH-I545, Android 4.4.2, VRUFNC5, hardware version: I545.06.
Can anyone point me in the right directions to understand better, and get me to my final destination of Custom rom? Or at least get me to understand this better?
I did search the first 5 pages of every section to see if there was a "newb-friendly" sticky but didn't seem to go anywhere fast, just made me more confused.
Click to expand...
Click to collapse
The problem with a simple "newb friendly" page is that every update to the phone changes what you need to do to root and what you can run.
For your NC5 phone, you need to use Towelroot to root it. That gets you root, but you're stuck with the stock bootloader. That means that you can't directly run a custom ROM. You can use Safestrap to allocate space for an alternative ROM, which is almost the same as a fully unlocked phone. The big thing you lose is that you can't run arbitrary ROMs, just what's compatible with the stock kernel. No CM, no AOSP.
So, read up on Towelroot and Safestrap. Once you have those down, you should be n the way.
Yeah, I got towel root already installed, supersu running and added to system and Knox disabled. Where should I be looking at roms that I can run under safestrap? Or should I say which section of the forums? Thank you for your response btw.
tong6998 said:
Yeah, I got towel root already installed, supersu running and added to system and Knox disabled. Where should I be looking at roms that I can run under safestrap? Or should I say which section of the forums? Thank you for your response btw.
Click to expand...
Click to collapse
Usually, roms that are compatible with safestrap are labeled as such. Since nc5 doesn't allow custom kernels, you will stuck with touchwiz kernels, so usually the roms will look like the stock samsung experience or a themed version. If you want an aosp themed safestrap rom, get eclipse rom. If you want a 99% gpe s4 rom download the gpe edition safestrap rom( it has some bugs though).
Usually roms are located at the "Android development" section of the forum. The gpe rom thread is in the general section.
tong6998 said:
Yeah, I got towel root already installed, supersu running and added to system and Knox disabled. Where should I be looking at roms that I can run under safestrap? Or should I say which section of the forums? Thank you for your response btw.
Click to expand...
Click to collapse
The thing to keep in mind, is that safestrap loads too late to be able to replace the kernel. This is the limiting factor, your stuck on the stock kernel... Different versions of android and different versions of kernels may have slightly different functions/parameters coded into the kernel, so calling a newer function or calling a function with parameters that no longer match the new style will fail.... so if the rom wasn't directly designed for the stock kernel of the same version your using it likely won't work.
In practice that means you need a rom based on TW, that is the same version (NC5) as you are currently using. Not sure but there are likely a few changes the Rom make needs to add for safe strap compatibility... Basically when you look at the Rom's thread it will list a baseband (NC5) and say its safestrap compatible.
Thanks to all of you, that clears up a lot of confusion I had. Now where do I find out (or how do I decifer) if I'm MJ7/MK2/ME7/MI1? Or am I correct in assuming I'm NOT (all the builds I see for safestrap mention those only no NC5.

Categories

Resources