Hey all - before I start I do want to say that I've watched the noob video and I have searched endlessly for days...I'm finding bits and pieces of valuable infomation that have prevented me from making some serious mistakes and I'm eternally grateful for that. I'm also seeing great root guides for my P7510 that I will follow once I am certain that I am in a good spot with my device.
That said....
I want to simply root my P7510 (3.1 updated OTA to 3.2 right out of the box, 2.6.36.3, P7510VLKL2) for now...no custom ROMs just yet, but I do want the ability to do it. So, I followed the guides in various places to obtain the Recovery.tar.md5 for CWM 5.5.0.4 (saw it was recommended to use the latest to flash the 4.1 JB ROM..thought what the hell) and flashed it with Odin 1.85.
Rolling recovery screen. I squinted...hard...and was actually able to take a NANDroid backup which I'm planning to move off of the device and onto my PC for safe keeping. After that however, I determined that trying to read the screen and go further would make my brain blow up and I should try to fix the screen issue first.
Rebooted, no problem. I rooked out major after that thinking "oh, well OK CWM doesn't like me so let's flash TWRP and that will make it all better". Yeah right, that made things WAY fun as I spent 2 hours poking at my rolling screen trying to figure out where the buttons actually are to reboot the device without destroying something.
So I've re-flashed CWM 5.5.0.4 because even while it still rolls, I can at least read it - but I'm gunshy to try anything now because I can't read the thing. I've seen threads about trying to unlock the bootloader but other threads say it isn't necessary. I've seen threads about flashing stock ROMs with Odin but have heard absolute horror stories about people flashing what they thought were stock ROMs and making things worse.
I've searched for this answer everywhere and can't get any help...so, powers that be, if I may draw upon your infinite wisdom, please enlighten me...is it feasible to root my HC3.2 P7510 (purchased in Canada) using the root package that you can find anywhere on an OLDER version of CWM? Will ALL versions of CWM roll my screen like this or just 5.5.0.4? Do I even need 5.5.0.4 if I'm not trying to flash the alpha 4.1 ROM?
Thanks in advance for any help you all can provide in consolidating all the great related info in this forum into one place...
djmatt604 said:
Hey all - before I start I do want to say that I've watched the noob video and I have searched endlessly for days...I'm finding bits and pieces of valuable infomation that have prevented me from making some serious mistakes and I'm eternally grateful for that. I'm also seeing great root guides for my P7510 that I will follow once I am certain that I am in a good spot with my device.
That said....
I want to simply root my P7510 (3.1 updated OTA to 3.2 right out of the box, 2.6.36.3, P7510VLKL2) for now...no custom ROMs just yet, but I do want the ability to do it. So, I followed the guides in various places to obtain the Recovery.tar.md5 for CWM 5.5.0.4 (saw it was recommended to use the latest to flash the 4.1 JB ROM..thought what the hell) and flashed it with Odin 1.85.
Rolling recovery screen. I squinted...hard...and was actually able to take a NANDroid backup which I'm planning to move off of the device and onto my PC for safe keeping. After that however, I determined that trying to read the screen and go further would make my brain blow up and I should try to fix the screen issue first.
Rebooted, no problem. I rooked out major after that thinking "oh, well OK CWM doesn't like me so let's flash TWRP and that will make it all better". Yeah right, that made things WAY fun as I spent 2 hours poking at my rolling screen trying to figure out where the buttons actually are to reboot the device without destroying something.
So I've re-flashed CWM 5.5.0.4 because even while it still rolls, I can at least read it - but I'm gunshy to try anything now because I can't read the thing. I've seen threads about trying to unlock the bootloader but other threads say it isn't necessary. I've seen threads about flashing stock ROMs with Odin but have heard absolute horror stories about people flashing what they thought were stock ROMs and making things worse.
I've searched for this answer everywhere and can't get any help...so, powers that be, if I may draw upon your infinite wisdom, please enlighten me...is it feasible to root my HC3.2 P7510 (purchased in Canada) using the root package that you can find anywhere on an OLDER version of CWM? Will ALL versions of CWM roll my screen like this or just 5.5.0.4? Do I even need 5.5.0.4 if I'm not trying to flash the alpha 4.1 ROM?
Thanks in advance for any help you all can provide in consolidating all the great related info in this forum into one place...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41 <<<< Is this my way out? Again, I've read a lot about bootloaders and this is the closest thing I can find to a straight answer but I want to be ABSOLUTELY positive that it's the correct file....
EDIT: Updated bad URL there.
Related
First off, thanks for taking the time to read my post. I have been trying to root/flash rom since yesterday at 11am now 2:19pm a day later. So before whinning here, I did do my research. Flash is now done, *sigh*
I would like the froyo tazzv26 or 28 rom flashed on my Eris
I've watched yourtube how to videos, unlockr videos, several adroidforums how to posts. they all revert me back here.
My issue is this #1:most of those are old posts(which I've read and been reverted to), and obvious upgrades have been made therefore what thier videos/posts show are not what I'm seeing or reading . Being that this is new to me I feel lost and confused.
Issue#2 I found the rom I wanted, here when I searched Roms for Eris however a link that is next to it sends me to another and another page. Very frustrating.
Favor needed: I've never done this before so can someone please help walk me through the process of being on the ACTUAL page with the download link, and what happens from then. Then let me know what i'm supposed to be seeing on my computer screen once the process starts .** WOW this part is massively missing from all noobie post/videos= FYI for admins and moderators
FYI Eris is already rooted wth 4zroot (instead of HTC1 click since the power up and power button thing didn't work 4 times) I have superuser, quickboot, rom manager, and astro file manager all installed and ready to go.
I'm ready to take your lead
Dulce,
Saw your post over on AF and replied over there, but did really get the gist of your needs until I saw this thread over here on XDA.
Rooting with Z4 root does indeed root you, but this will not allow you to flash or install a custom ROM without having replaced your stock recovery with a custom one, the "one" being Amon_RA (stay away from ClockworkMod at this time for the Eris...the details are probably more than you want or need to know at this time).
The 1-click method that you mentioned previously is what you want and it will install Amon_RA's custom recovery for you.
I would highly advised you to read and understand this thread over on AndroidForums: http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html
You will learn what you need to know from that thread and it will also show you how to install the very same custom recovery as the 1-click method/app. It is clearly more verbose, but the trade-off / benefit is that you will have the best instruction possible regarding rooting your Eris.
Check it out and good luck!
Cheers!
I've rooted my GT 10.1 but I have two questions that I can't find the answer.
1. Has anyone discovered how to unroot back to stock?
2. If rooted, will I be able to get the OTA of touchwiz by checking for updates under settings?
PS I flashed the TouchWiz UX found in this forum. Got to say it is really nice and I can't wait to get the version from Sammy. I then restored a backup using Rom Manager and restored fine except when checking for software updates. It used to say no update available, but today it says failed to connect to servers. Anyone else getting this error?
I guess that is actually 3 questions.
Thanks
1. Unrooting is pretty simple. Just flash the 3.1 OTA in the dev forum, after doing a full wipe. If you feel the need to go back to full stock, you'll also want to nvflash back to the original retail recovery, which you undoubtedly saved when you first rooted.
2. No one knows yet, but rest assured, within a day (less probably) of the update being released, it'll be available here as a rooted flashable ROM. If you learn one thing from your time on XDA, it should be "never accept an OTA update." Let the devs pull it apart and repackage it in a nice root-safe download.
Undoubtedly! (I wish) I wasn't planning to root but while playing with Odin, I thought I was locked at the downloading screen while testing odin. (Didn't hold down the power button long enough to shut off tab) I thought my only solution was to continue and root. No problems rooting, it was easy. I just wanted to make sure I get the TouchWiz update. Now I learned my lesson I will never do an OTA update.
Glad you told me that, otherwise I probably would have screwed up my GT. I don't know how I missed the post about backing up the stock image first. I try to read a lot of posts (heck I even use the search box) before trying something new. Anyway, I'm sure it is posted in the forums somewhere if I need to find it.
Thanks!
pmsrefugee said:
Glad you told me that, otherwise I probably would have screwed up my GT.
Click to expand...
Click to collapse
It's not so much that you'll screw up your device by accepting an OTA, but rather that you might lose root and/or your custom recovery (perhaps permanently). Nevertheless, there are some cases of OTAs screwing up devices when accepted over non-stock installs, so IMHO its always best to wait for a flashable ROM.
pmsrefugee said:
I don't know how I missed the post about backing up the stock image first. I try to read a lot of posts (heck I even use the search box) before trying something new. Anyway, I'm sure it is posted in the forums somewhere if I need to find it.
Thanks!
Click to expand...
Click to collapse
Yes, I believe the stock retail recovery is posted in the CWM recovery download package here: http://forum.xda-developers.com/showthread.php?t=1130574. You'll note that Step 3 is where you were advised to backup your original stock recovery, although the step is (correctly) noted as optional. No big deal, in any event. Glad I could help.
First off, sorry if this has already been covered somewhere and I'm just not finding it.. I've been searching and reading a lot and l am learning a ton, I just cant seem to find an answer for sure..
Note - I am mostly a 'noob'. I have had other sammy phones (a Galaxy S and a Gnex) and have rooted them and put CWM and TWRP on em, and flashed many kinds of custom roms and stuff,, soft bricked em several times,, had to use ODIN to flash em back to stock and start over, followed instructional threads to hack around using ADB and Fastboot commands for different things, etc..Basic playing around with stuff like that. So I sorta know my way around the basics of playing with at least Sammy brand phones.
I recently bought a nice used S4 to play with. I immediately start looking at root instructions and bootloaders and roms,, and ran dead into the brick wall of it already having the ME7 devil on it and thus me being locked out beyond rooting. Since I wanted an S4 specifically for playing with ROMs, I sold that stock ME7 S4 and bought a different one that someone had already put TWRP on and a custom ROM. So now I should be good to go flashing away.
So my question is, if I ever do want to try running a stock ME7 rom sometime, is there one I can flash while playing around flashing trying out different roms that would NOT somehow lock the bootloader? I'm not talking about accepting a Verizon OTA update, I know better than that. I'm talking about manually flashing roms (I am assuming if I flashed a 100% stock Verizon rom it might screw myself and lock the bootloader,, maybe I am mistaken on that assumption idk). I'm seeing the "bonestock me7" rom here on XDA, would that be safe to try for a stock ME7 experience?
ok i'll shut up now,, sorry for the long post.
You're good to go. Just look in the dev section for one to your liking. I've been running BoneStock but there are others including one from andybones which completely stock. Stay clear of any ROM requiring you to Odin as I'd worry about that.
Sent from my SCH-I545 using xda app-developers app
Cool. Thanks much for the help!
Basic operations
sohead said:
First off, sorry if this has already been covered somewhere and I'm just not finding it.. I've been searching and reading a lot and l am learning a ton, I just cant seem to find an answer for sure..
Note - I am mostly a 'noob'. I have had other sammy phones (a Galaxy S and a Gnex) and have rooted them and put CWM and TWRP on em, and flashed many kinds of custom roms and stuff,, soft bricked em several times,, had to use ODIN to flash em back to stock and start over, followed instructional threads to hack around using ADB and Fastboot commands for different things, etc..Basic playing around with stuff like that. So I sorta know my way around the basics of playing with at least Sammy brand phones.
I recently bought a nice used S4 to play with. I immediately start looking at root instructions and bootloaders and roms,, and ran dead into the brick wall of it already having the ME7 devil on it and thus me being locked out beyond rooting. Since I wanted an S4 specifically for playing with ROMs, I sold that stock ME7 S4 and bought a different one that someone had already put TWRP on and a custom ROM. So now I should be good to go flashing away.
So my question is, if I ever do want to try running a stock ME7 rom sometime, is there one I can flash while playing around flashing trying out different roms that would NOT somehow lock the bootloader? I'm not talking about accepting a Verizon OTA update, I know better than that. I'm talking about manually flashing roms (I am assuming if I flashed a 100% stock Verizon rom it might screw myself and lock the bootloader,, maybe I am mistaken on that assumption idk). I'm seeing the "bonestock me7" rom here on XDA, would that be safe to try for a stock ME7 experience?
ok i'll shut up now,, sorry for the long post.
Click to expand...
Click to collapse
Writing the nand memory on this handset is nearly impossible through conventional means, suggest a maintenance jig for the board.
heyazzo said:
Writing the nand memory on this handset is nearly impossible through conventional means, suggest a maintenance jig for the board.
Click to expand...
Click to collapse
Whats the "nand memory"? the area of memory where the recovery/bootloader code is stored? and what do you mean by conventional means? like using CWM or TWRP I assume? what about ODIN? from prior experience ODIN has written over a custom bootloader that I had loaded with a stock one (if I remember right anyway, I think I've lost my custom CWM or TWRP bootloaders by flashing a stock rom via ODIN,, back on the Gnex, I have never tried that with an S4 but assume it would be the same deal). And whats a "maintenance jig"?
lol sorry for so many questions,, warned ya I was a NOOB
No such thing as a dumb question.
sohead said:
Whats the "nand memory"? the area of memory where the recovery/bootloader code is stored? and what do you mean by conventional means? like using CWM or TWRP I assume? what about ODIN? from prior experience ODIN has written over a custom bootloader that I had loaded with a stock one (if I remember right anyway, I think I've lost my custom CWM or TWRP bootloaders by flashing a stock rom via ODIN,, back on the Gnex, I have never tried that with an S4 but assume it would be the same deal). And whats a "maintenance jig"?
lol sorry for so many questions,, warned ya I was a NOOB
Click to expand...
Click to collapse
I was always curious about things that I didn't understand. First, try to understand the security that's already on this device, then decide if an update really did kill one qfuse out of say 10-12 on the board depending on the lifecycle they gave this particular set of commo gear. Search MSM 8960 security, then get back to me via PM, I want to help you any way I can.
Hi all
Recently I upgraded from Samsungs stock 4.1.2 firmware to CyanogenMod 10.2 Stable (based on 4.3.1) using their installer program. Since upgrading the Wifi has been unusable and I have not managed to get the problem resolved through their forums so I have decided to go back to the stock rom.
Now that Samsung have re-released 4.3 for the S3 in the UK (after the one from last month which was pulled for problems) I would like to use this one as it fixes a bluetooth streaming issue I have endured for a long time. I can't find this new firmware for download anywhere so wondered if it is feasible to download say the stock rom 4.1.2 and then upgrade somehow? I have a red line on the bootup screen which shows it has been modified (which triangle away won't remove due to custom rom/bootloader or something like that) so I believe this means I will be blocked from then upgrading from 4.3 OTA but able to do so with Kies?
Being a novice at this I am obviously worried about breaking my phone and I am not sure if having i9300XXEMG4 as a baseband version is an issue among other things after reading the forums. As much as I have read about EFS and the downgrading modem problems, none of it is making sense to me at the moment, even after reading all the documents. Brain freeze maybe!
The cyanogenMod also changed recovery and unlocked the bootloader going by what I have read, is this an issue I need to worry about?
Any advice that can take away some worries and get me on the right path would be muchly appreciated!
You are posting in the wrong forum .
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
JJEgan said:
You are posting in the wrong forum .
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
Click to expand...
Click to collapse
Thank you for your post. I did follow a link in the !!ALL QUESTIONS GO IN THE Q&A FORUM!! OR THEY MAY BE DELETED!! sticky thread which took me to the Q&A forum where I thought I was posting. It is possible a confusion happened during the sign up process.
After reading those threads, two of which I had already read before posting, I have more understanding than I did before. Somehow I missed about the S3 not having a locked bootlader to begin with. I have backup up the EFS using Ktool but also understand it would have been more useful to do before flashing CM 10.2 as I now only have a EFS v2 backup rather than a version 1. What I am unsure of is what is my best action to take at the moment, going by the information I have. I can it is best not to go downgrade to earlier firmwares unless I wanted an added headache of the modem workarounds but do not see the best way to get back to a stock 4.3 firmware still.
I am on Three mobile (H3G) in the UK but don't think my phone is actually locked to them and don't know if that means the BTU is the option I should be choosing. Even so, when I check the firmwares on http://www.sammobile.com/firmwares/2/ I can only see a firmware added last month which I have to assume is the bad 4.3 update that hit the UK and was pulled after the problems it caused. If it was my best option for flashing, even with the problems it caused, how would I then go about getting the extra update that Samsung pushed out to fix the problem?
I saw the Korean factory flash in one of the threads too, not sure if this is too extreme (and potentially more dangerous) than the other options which may be available to me.
Obviously I would like to do this right the first time, rather than stumble backwards fixing all the mistakes I make at the time. So sorry if I am asking what may be simple to some. My knowledge of phones sucks and I wish I hadn't been tempted by the easy looking Cyanogenmod installer now!
Noticed after a few cache and devlik cleans and reboots that the wifi started working on the CM 10.2 mod but only for the main browser and hit and miss with google play. Every over app didn't work on wifi though, but did on cell. I googled all over to see many with similar problems, which suggested manually setting the time and date and static ip settings, clean davlik and updating play apps after deleting their cache.
None of them worked. So to potentially getting away from flashing, does anyone know any other ideas to resolve this? Wifi connects, stock google browser works, Play works flakey. Other installed browsers wont load any pages or connect to the net, such as speed testing app. The only unusual app that also works in a twitter app. Installed an app to see if there was a hidden proxy setting, but it found nothing, Really strange. All the apps work on cell.
Follow the guide in general forum, stickies, to flash back to stock BTU. Network lock is irrelevant to rom.
Choose either 4.1.2 or 4.3 but your baseband must be EMG or later as you now have efs v2.
Don't flash things you don't fully understand, any non Samsung rom has drawbacks you'll have to live with.
In the stickies is a world of information supposed to help you.
boomboomer said:
Follow the guide in general forum, stickies, to flash back to stock BTU. Network lock is irrelevant to rom.
Choose either 4.1.2 or 4.3 but your baseband must be EMG or later as you now have efs v2.
Don't flash things you don't fully understand, any non Samsung rom has drawbacks you'll have to live with.
In the stickies is a world of information supposed to help you.
Click to expand...
Click to collapse
Appreciate you giving me a direction to go. It seems the problem I had finding firmwares the last few days were due to Hotfile going offline and Sammobile rebuilding their index of firmwares. I found through the forums 4.3 BTU I9300XXUGMJ9_I9300OXAGMJ9_BTU.zip which contained a 1.5GB file called I9300XXUGMJ9_I9300OXAGMJ9_I9300XXUGMJ9_HOME.tar.md5 which I think is the correct one which I will try and flash later using the guides. It's not the new fixed 4.3, it's the older broken one but I guess in time I can apply the fix that Samsung are pushing out. This was part of my original question and now i have seen from other posts in the last few days that there is no full copy of the 4.3 anywhere.
The timing of me doing this appears to have been bad for a few of the above reasons, making working it out more difficult to work out for someone who has not done this before.
I can see from your signature and also your post that you think questions such as mine are easily answered in the various threads and through search. Personally I did try all those options first but either my lack of understanding or the overwhelming amount of information meant I was unsure as to what I should actually be doing, let alone which guide to follow. Even googling for BTU or searching xda to try and find what it means was fruitless so trying to put the pieces together is not easy if you have no experience with phones. I have programmed a Pi to do many tasks, built mainframe>SAS gateways and various technical challenges but I still struggle with all the phone flashing info
Many thanks again. Even a few words have been helpful
If you flash the kernel from the Chinese ZCUBMK it will fix all the broken parts of the current uk rom, until the latest ota emerges on xda.
I don't mind helping people who have made a genuine attempt to help themselves, my signature is aimed at the those who flash anything they find then demand someone give them an instant fix.
Your only mistake seems to have been the depth of research before you started, which could have been fatal to your phone -many first time flashes end up with a new motherboard required.
Sent from my GT-I9300 using Tapatalk
If the ota doesn't work in the next few day's I will try that kernel, thanks for that info!
I managed to flash the older official 4.3 firmware just now, so progress has been made A quick check shows me that the power on/lock screen lag problem is present so I assume the other issues will be there too. The red line showing the flash counter has gone and I got no modified phone error when attempting an ota update, as well as device status saying official, so I assume I should be able to upgrade that way when they allow more upgrades on the rollout server.
In case anyone else needs to do the same, this is what I did:
1) Downloaded https://mega.co.nz/#!DVxVgZZb!LIxKGA2Q_KbBH9APo_slOCdZNGJgfn1O6fxOF4C OkHA which I found via a thread titled [Official Firmwares] I9300XXUGMJ9 (Android 4.3) - Ireland (VDI) [04-11-13]
2) Followed the flashing instructions on this page
3) After flashing I got stuck at the Samsung boot screen with the blue light on, even after reseting a few times. So I powered off, held down the home button, volume up and then the power button which took me to the recovery screen where I chose the factory default option. All worked fine after that.
Thanks once again for your help with this boomboomer. A bit of direction was enough to give me the confidence to try it. It's nice to be back to a familiar interface (although it has changed from the 4.1.2 I had before) but the initial setup reminded me of all the bloatware installed. It's a fair bit slower than CyanogenMod was but it all seems to work ok. Once I get the ota update i'll root and freeze some apps to sort that out. Now to install TSF shell
Hey, first post here but I've been reading some threads since 2011.
I have a Samsung Galaxy S4 (I have experience with custom roms and such with the Droid Charge, also Samsung. See a pattern?).
I rooted it a while back, but recently have been experiencing quite a bit of instability so I wanted to try a custom rom (Hyperdrive is the one that I'm looking at but that's kinda irrelevant to this post).
The problem for me is that every guide expects me to be rooted with the custom recovery. I am rooted, and I did have CWM installed to perform the root, but now for some reason recovery boots into stock and I haven't been able to load any custom recoveries. I tried the CWM Rom Manager app to get CWM back, but it didn't seem to work (touch or normal). I have also tried Goo Manager to get TWRP and that was a complete bust.
I noticed one or two other methods involving safe-strap but I cannot for the life of me get safe-strap working on my phone and I've followed a couple guides several times without success.
I need someone to point me in the right direction to get a custom recovery back on my phone. I'm assuming something got screwed up somewhere along the line, so I'm not confident in these other methods but I'm trying to find a guide using Odin. Part of the problem seems to be that the Verizon phones aren't too common so all the guides and downloads are for a different model.
Please help, I'd prefer an Odin method but I'm open to suggestions.
cdroid93 said:
Hey, first post here but I've been reading some threads since 2011.
I have a Samsung Galaxy S4 (I have experience with custom roms and such with the Droid Charge, also Samsung. See a pattern?).
I rooted it a while back, but recently have been experiencing quite a bit of instability so I wanted to try a custom rom (Hyperdrive is the one that I'm looking at but that's kinda irrelevant to this post).
The problem for me is that every guide expects me to be rooted with the custom recovery. I am rooted, and I did have CWM installed to perform the root, but now for some reason recovery boots into stock and I haven't been able to load any custom recoveries. I tried the CWM Rom Manager app to get CWM back, but it didn't seem to work (touch or normal). I have also tried Goo Manager to get TWRP and that was a complete bust.
I noticed one or two other methods involving safe-strap but I cannot for the life of me get safe-strap working on my phone and I've followed a couple guides several times without success.
I need someone to point me in the right direction to get a custom recovery back on my phone. I'm assuming something got screwed up somewhere along the line, so I'm not confident in these other methods but I'm trying to find a guide using Odin. Part of the problem seems to be that the Verizon phones aren't too common so all the guides and downloads are for a different model.
Please help, I'd prefer an Odin method but I'm open to suggestions.
Click to expand...
Click to collapse
If you are on NC5 then Safestrap is your only option. You are going to brick your phone if you just keep throwing recoveries at your phone until one sticks. If you are on MDK then your bootloader is unlocked and you can do what you want. Read the threads, that's what they're there for.
Jesus loves you!
Phone version
liljoe727 said:
If you are on NC5 then Safestrap is your only option. You are going to brick your phone if you just keep throwing recoveries at your phone until one sticks. If you are on MDK then your bootloader is unlocked and you can do what you want. Read the threads, that's what they're there for.
Jesus loves you!
Click to expand...
Click to collapse
I'm actually on ME7. I haven't updated in a very long while because I wanted to root and then stop tinkering. That's not an option for me anymore for the stability reasons. I had over a year of rock solid performance though so it was a good run.
I was searching threads on this forum and others. This one seems to be more reliable than others (and a whole lot friendlier), but I still can't find what I'm looking for.
Maybe you can help me out by pointing out one of the threads that has what I need?
Thanks much.
cdroid93 said:
I'm actually on ME7. I haven't updated in a very long while because I wanted to root and then stop tinkering. That's not an option for me anymore for the stability reasons. I had over a year of rock solid performance though so it was a good run.
I was searching threads on this forum and others. This one seems to be more reliable than others (and a whole lot friendlier), but I still can't find what I'm looking for.
Maybe you can help me out by pointing out one of the threads that has what I need?
Thanks much.
Click to expand...
Click to collapse
MDK, as I understand it, is the only bootloader that has been unlocked thus far. If you are still on ME7 and it's locked anyway, you may be better off just taking the update.
Jesus loves you!
liljoe727 said:
MDK, as I understand it, is the only bootloader that has been unlocked thus far. If you are still on ME7 and it's locked anyway, you may be better off just taking the update.
Jesus loves you!
Click to expand...
Click to collapse
Okay, well obviously I've messed up my phone somehow, I don't think it's possible for me to just go to system settings and update. How do I go about this if that doesn't work?
cdroid93 said:
Okay, well obviously I've messed up my phone somehow, I don't think it's possible for me to just go to system settings and update. How do I go about this if that doesn't work?
Click to expand...
Click to collapse
Well you can update via Samsung Keis, or if you know how to use ODIN you can flash the latest NC5 through ODIN. You'll find everything you'll need from here.
Forgot to say that after you upgrade you can root through towelroot which you can by searching this forum or Google it.
After you install busybox you should be able to install Safestrap, but if you can't, you need to download and install an app calle SElinuxmodechanger and set SElinux to permissive. Then you will be able to install Safestrap. Once you have SS you can only install ROMs on the Stock slot. non of the other slots work.
skeezer308 said:
Well you can update via Samsung Keis, or if you know how to use ODIN you can flash the latest NC5 through ODIN. You'll find everything you'll need from here.
Forgot to say that after you upgrade you can root through towelroot which you can by searching this forum or Google it.
After you install busybox you should be able to install Safestrap, but if you can't, you need to download and install an app calle SElinuxmodechanger and set SElinux to permissive. Then you will be able to install Safestrap. Once you have SS you can only install ROMs on the Stock slot. non of the other slots work.
Click to expand...
Click to collapse
Okay, for starters thank you. This is almost exactly what I needed. I've just got one more issue;
I cannot discern from what I've found on the forums or elsewhere what safestrap is safe for my phone now that I'm on NC5?
Thanks again for this, was a big help.
cdroid93 said:
Okay, for starters thank you. This is almost exactly what I needed. I've just got one more issue;
I cannot discern from what I've found on the forums or elsewhere what safestrap is safe for my phone now that I'm on NC5?
Thanks again for this, was a big help.
Click to expand...
Click to collapse
3.72
Jesus loves you!
Also keep in mind that you can only install TW ROMs or GPE ROMs that are SS friendly. If you try to install Cyanogen or other AOSP ROMs that require custom kernels you run the chance of bricking your phone