I'll start off by giving some background information. I ordered my Nexus 4 back in March and ran stock up until about July/June. Prior to the Nexus I had the HTC G2. I don't know how to root and and use custom ROMs and I have looked at the root guide for the Nexus but it's a huge barrage of information and some terms that I don't know what they are. However, this question doesn't involve rooting. I gave my Nexus 4 to a friend, who also has the Nexus, to root for me and use a custom ROM. In this process however, he did something that he told me to never do (I really don't know why..) and he ended up soft bricking my phone. He did that because my phone was stuck on the "Google" start up screen for over 40 minutes. Basically, he wiped the entire phone, I think. Due to some issues, we are no longer on speaking terms and he was the only person I knew who knows how to deal with rooting and custom ROMs.
Now I don't have the original back up of the stock. My question is, if I ever needed to send my phone back to Google for repairs or anything else, would I be able to somehow get the phone back to it's stock state?
Also, where could I find some resources that aren't a barrage of information? When I go to those threads like the Nexus rooting guide, it's just so much information and I get lost (I don't even quite know what a ROM is, my current interpretation is an operating system). Currently, I think I know how to update the ROM, I'm currently using Paranoid Android.
I apologize if this issue of mine can easily be solved with a search. I have googled this issue numerous times and I could not really find a solid answer.
Fubs261 said:
I'll start off by giving some background information. I ordered my Nexus 4 back in March and ran stock up until about July/June. Prior to the Nexus I had the HTC G2. I don't know how to root and and use custom ROMs and I have looked at the root guide for the Nexus but it's a huge barrage of information and some terms that I don't know what they are. However, this question doesn't involve rooting. I gave my Nexus 4 to a friend, who also has the Nexus, to root for me and use a custom ROM. In this process however, he did something that he told me to never do (I really don't know why..) and he ended up soft bricking my phone. He did that because my phone was stuck on the "Google" start up screen for over 40 minutes. Basically, he wiped the entire phone, I think. Due to some issues, we are no longer on speaking terms and he was the only person I knew who knows how to deal with rooting and custom ROMs.
Now I don't have the original back up of the stock. My question is, if I ever needed to send my phone back to Google for repairs or anything else, would I be able to somehow get the phone back to it's stock state?
Also, where could I find some resources that aren't a barrage of information? When I go to those threads like the Nexus rooting guide, it's just so much information and I get lost (I don't even quite know what a ROM is, my current interpretation is an operating system). Currently, I think I know how to update the ROM, I'm currently using Paranoid Android.
I apologize if this issue of mine can easily be solved with a search. I have googled this issue numerous times and I could not really find a solid answer.
Click to expand...
Click to collapse
Is the phone booting into PA? If not try holding the power button and the volume down at the same time. It should boot into recovery. If it does all you need to do is flash a rom "install a os".
Sent from my Nexus 4 using xda app-developers app
Tunderpimp said:
Is the phone booting into PA? If not try holding the power button and the volume down at the same time. It should boot into recovery. If it does all you need to do is flash a rom "install a os".
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Ohh yes, I should clarify. Currently the phone is working and I have it up to date on Paranoid Android. The only issue I had when updating Paranoid Android was that I could not use the kernel my friend had supplied me with (I think it was the Franco kernel). When I would flash the kernel, it would get stuck on the Google logo screen. I would have to get out of that by re-flashing Paranoid Android again and I've been unsuccessful in flashing any kernels. The main reason I wanted to root my phone was a custom kernel, to help with battery life.
My main question is that I wanted to know if I could ever get it back to stock (as to not void a warranty) if I were to ever need to for any reason.
Fubs261 said:
Ohh yes, I should clarify. Currently the phone is working and I have it up to date on Paranoid Android. The only issue I had when updating Paranoid Android was that I could not use the kernel my friend had supplied me with (I think it was the Franco kernel). When I would flash the kernel, it would get stuck on the Google logo screen. I would have to get out of that by re-flashing Paranoid Android again and I've been unsuccessful in flashing any kernels. The main reason I wanted to root my phone was a custom kernel, to help with battery life.
My main question is that I wanted to know if I could ever get it back to stock (as to not void a warranty) if I were to ever need to for any reason.
Click to expand...
Click to collapse
which franco kernel, was it compatibke with your rom? i mean are you on android 4.3 and the kernel 4.2.2(or vice versa)? when you flashed the kernel, did you flash with the rom then boot up, or did you just flash the kernel alone? did you try redownloading the kernel, maybe a bad download? was it a jss kernel or a jwr kernel?
Fubs261 said:
My main question is that I wanted to know if I could ever get it back to stock (as to not void a warranty) if I were to ever need to for any reason.
Click to expand...
Click to collapse
Yes you can.
Read the guides as slowly as you need to...stopping to research anything you don't understand...
Or just use those no brainer toolkits that teach you nothing.
And stick to stock until you know what's going on within your device when you do these things.
simms22 said:
which franco kernel, was it compatibke with your rom? i mean are you on android 4.3 and the kernel 4.2.2(or vice versa)? when you flashed the kernel, did you flash with the rom then boot up, or did you just flash the kernel alone? did you try redownloading the kernel, maybe a bad download? was it a jss kernel or a jwr kernel?
Click to expand...
Click to collapse
I'm not sure what version it was, I guess that might have been the issue. Would that have caused it to stay on the Google logo screen? I'll make sure to double check for that next time I try to do something.
studacris said:
Yes you can.
Read the guides as slowly as you need to...stopping to research anything you don't understand...
Or just use those no brainer toolkits that teach you nothing.
And stick to stock until you know what's going on within your device when you do these things.
Click to expand...
Click to collapse
Thank you for answering. Could you link a good starter thread for me? I was hesitant to use a custom ROM or even to root my phone. What compelled me to do it was the kernels extending battery life. Because I was so lost and felt overwhelmed, I had my friend help me but now we are no longer on talking terms so I'm lost.
Again, I wish to apologize, I know I should just look this up myself, but with the possibility of bricking/soft-bricking my phone, I want to get as much help as possible. Whatever small nudge, I will take.
Your questions can be answered by reading the stickies thread in the general section. Just follow the instructions to flash back to factory stock:
http://forum.xda-developers.com/showthread.php?t=2010312
If you flash a kernel and the phone won't boot, that kernel or version of the kernel isn't compatible with that rom or particular version of Android.
sent from xda premium app
---------- Post added at 06:09 AM ---------- Previous post was at 06:06 AM ----------
Fubs261 said:
Because I was so lost and felt overwhelmed, I had my friend help me but now we are no longer on talking terms so I'm lost.
Click to expand...
Click to collapse
I hope it's not because he messed up your phone, it's not his fault that you trusted him to do it in the first place. If not, well nevermind.
sent from xda premium app
It's very simple to get it back to stock. You'd just need to find a copy of the stock Rom (which I can assure you is probably on this very website floating around somewhere) and flash it in recovery like you would any other Rom.
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel
---------- Post added at 03:14 AM ---------- Previous post was at 03:12 AM ----------
Also keep in mind, custom roms usually come with custom kernels. So you shouldn't even have to worry about kernel flashing. If you want to preserve battery you should focus more on under clocking and thermal throttling...
You can find guides on here somewhere for that too...
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel
Related
Good evening all,
Basically I'm looking to root my girlfriends fathers U8800, it's currently running android 2.2. He's complained that its got major battery drain so I figure I can find a ROM here that can help that.
I've read there are 3 different types of models for this handset. How do I know which one we've got? If that's relevant?
I've found this thread that seems dead easy to follow, http://forum.xda-developers.com/showthread.php?t=1420728 , am I ok to proceed?
When I've rooted it, do I just flash a rom via CWM like I would with my galaxy s? And will I be caught out with bootloader issues or little things like that?
Thanks in advance.
If the device is the U8800 regular model(not pro or plus) you can follow the guides of the link.
And yes, you can flash a rom from cwm recovery.
Only one suggestion. If you flash the latest stock gingerbread rom(I think is the 522), search for a thread called "get your pink screen back" on developing section. The after 518 versions have the bootloader locked, and on the above thread you will find how to flash the unlocked bootloader from 518 stock rom.
Thanks for that, I'll get on it tomorrow with an operational head. I'll do the pre root checks and make sure I have everything I need in place before I get going.
dancer_69 said:
If you flash the latest stock gingerbread rom(I think is the 522)
Click to expand...
Click to collapse
It's 528
dancer_69 said:
The after 518 versions have the bootloader locked, and on the above thread you will find how to flash the unlocked bootloader from 518 stock rom.
Click to expand...
Click to collapse
*locked pink screen.
Sent from my GT-P1000 using Tapatalk 2
If the device is not yours I suggest you to do nothing. There's no better Rom, in terms of bug free than the original one.
Custom roms always have this or that and will require attention, which I'm sure your fatherin law can live better without these issues and concerns.
This devices have an high consumption and he has to get used to it.
Now if the device was yours meaning you would be using it daily, than i would advise you to install aurora. I don't like it but have to admit that is very good and stable.
:thumbup:
Sent from Odin's device!
Dave759 said:
He's complained that its got major battery drain so I figure I can find a ROM here that can help that.
Click to expand...
Click to collapse
Did you look to see what is causing the battery drain? I have a friend with a stock GT540 that had serious battery drain. Turns out it was the GoSMS program. Deleted the app and now his phone lasts 5 days between charges. Switching a rom won't help if the problem is an app.
1) Get cpu spy and see if it is going to deep sleep
2) If not sleeping, turn off running applications one by one and test via cpu spy to find out which one is causing it not to sleep.
3) Either remove the offending app or use Autorun Manager to modify the receivers (if rooted)
You can fix his problem without changing his rom. If he wants root, superoneclick can root 2.2, I just used it the other day. Also make sure he is on the latest 2.2: b138sp04 or b163. I prefer b163, even though it is the China rom, because I like the Huawei launcher better that stock.
A.C.A.B. said:
If the device is not yours I suggest you to do nothing. There's no better Rom, in terms of bug free than the original one.
Custom roms always have this or that and will require attention, which I'm sure your fatherin law can live better without these issues and concerns.
This devices have an high consumption and he has to get used to it.
Now if the device was yours meaning you would be using it daily, than i would advise you to install aurora. I don't like it but have to admit that is very good and stable.
:thumbup:
Sent from Odin's device!
Click to expand...
Click to collapse
That's not true... official 2.2 is the slowest thing in existence. If he just needs stability then Ezets CM7 is the answer. There are no bugs with it (except wifi tethering) and it's much much faster than stock...
Also he can undervoltage it to preserve battery life more than stock ROM.
Sent from my U8800
You want the best 2.2 you try Void Eridanus. Everything works.
Want the speed, OEX rom it's a Ferrari. Everything works less the mms with data off.
You can also keep the stock Rom, root it and just apply a ffranco kernel. This way you gain the speed.
3 good solutions here.
I'm don't revert to stock Rom for 2 reasons, cam quality and battery life, otherwise i would use stock Rom without a shadow of a doubt.
In terms of stability and all working it's stock 2.2 Rom and this is unquestionable!!!
I have been trying ALL roms and ALL respective versions since July 2011 therefore I do speak by personal extended experience
I repeat once again, in the conditions you mention leave the phone as it is. If you want to do something just root it and that's it.
as a matter of facts i had my phone with so many rooms that i can even say how many but if u want stability i recomend oxygen... if u want stability and good looks use miui 32...
last .32 miui that i used was from miui portugal in english and nothing to say about that...
battery for 2 days and all smoth...
but my phone is weird... he can take almost every rom and be usable...
The issue with miui pt versions it's the cam quality that is horrible. It's just this detail that it's not very good. The rest it's perfect.
Sent from Odin's device!
Hey everyone, back for an update and some other steps. basically, he got frustrated with how the battery so he went out today and bought the newer huawei. Reading eveyones comments here i think its due to the ammount of apps and being on froyo hasn't helped any thing, but anyways its now my new toy to play with. So far, followed the link i posted in the first thread, rooted and installed the latest CWM (v5). I'm now a little confused when it comes to the get the pink screen back, should i follow this thread http://forum.xda-developers.com/showthread.php?t=1457490 now before flashing a new rom or afterwards?
Again thanks for all the help, I'm almost done bothering you all for now
Edit: Reading on some ROM's and the comments above, i should install B518 stock ROM then flash the bootloader fix from the thread posted above then i can install other ROM's? If so where can i get the stock B518 ROM and how do i know which version I'm using? Sorry and thanks again.
First, which rom you have now?
You can find the version from settings -> about phone.
If you have a newer than 518 version you need to change the bootloader with the one from 518. If you have 518 you don't.
Also check which version of kernel you have(is on about phone also)
If you have a 2.6.32 version(which mean that you have froyo rom), you can flash only roms with this kernel version. If you have a 2.6.35 version, you can flash roms with 2.6.35 kernel or 3.0.8(as aurora ICS).
Basically its a stock froyo rom, im looking to get to gingerbread by the end of tonight but currently im stuck on the huawei splash screen after i did a data reset in CWM. Can still get to CWM though.
What rom you want to flash now?
A custom gingerbread based of froyo's kernel 2.6.32 like CM7.2, oxygen or miui, or the official gingerbread?
Im not particularly bothered, something that won't brick the phone and is stable. I'm more worried as to why it wont boot now after a data reset.. any suggestions for that?
You can use adb and logcat function to see where the problem is. Usually when some errors prevent device to complete the boot proccess, this piece of code loops. You need to have some knowledge of programming though, but maybe is something easy.
and now i have blue screen.. what can i do? or have i bricked it?
Where you have blue screen and what you did?
Usually blue screen instead of recovery mode, means that the recovery.img is deleted from .cust_backup/Image folder
basically, i formatted something, reboot and soon as the huawei logo appear a blue scrren rolls down. when i plug the phone into the pc it detects a folder but its empty, the phone is detected as qualcomm now..
Yes, seems that you formated the partition which has the Image folder with all system images. So, now you need to flash an official rom. You can either flash a froyo or a gingerbread rom. You can avoid this only if you previous had take a backup of this folder. In this case just put all files in (empty now) image folder.
I'm honestly not sure where to post this, I found it on another forum (and that post was made about three hours ago). In any case, Samsung appears to have open sourced the stock firmware and kernel for Straight Talk's version of the Galaxy S II.
If you go to http://opensource.samsung.com/ and search of the model number - SGH-S959G - it's the only thing that comes up. The download appears to be just what it says, the uncompiled source code.
I've been looking for stock ever since I bought this phone and since I'm not exactly green when it comes to Linux and using a terminal, I'm tempted to give a crack at compiling this myself. Anybody have any experience with this? It can't be too hard...right? :silly:
(source: http://androidarea51.com/modifications/straight-talk-s2-sgh-s959g-source-code/msg8830/)
IndigoAK said:
I'm honestly not sure where to post this, I found it on another forum (and that post was made about three hours ago). In any case, Samsung appears to have open sourced the stock firmware and kernel for Straight Talk's version of the Galaxy S II.
If you go to http://opensource.samsung.com/ and search of the model number - SGH-S959G - it's the only thing that comes up. The download appears to be just what it says, the uncompiled source code.
I've been looking for stock ever since I bought this phone and since I'm not exactly green when it comes to Linux and using a terminal, I'm tempted to give a crack at compiling this myself. Anybody have any experience with this? It can't be too hard...right? :silly:
Click to expand...
Click to collapse
You won't get the stock firmware by compiling the kernel, mate. Why do you want stock when you already have stock (original) firmware? If you're looking for unbranded, you're unlikely to find it as you have a carrier specific phone.
Force Close said:
You won't get the stock firmware by compiling the kernel, mate. Why do you want stock when you already have stock (original) firmware? If you're looking for unbranded, you're unlikely to find it as you have a carrier specific phone.
Click to expand...
Click to collapse
I'm aware of how this source code works!
IndigoAK I am the one that posted the link on AA51. The file appears to be in tar.gz format like what is used for install through odin. I have not tested it, as I am not a developer, or in need of flashing to factory firmware at this time. I posted it as I seen many people looking for it. I believe it is needed to be able to safely start making modifications for this phone, CWM, Root, custom ROMs, ect., and being able to flash back to stock if something goes wrong. Hopefully with the information out there now it will jump start development.
Edit: After further research the source code files are used to create the firmware, and these cannot be installed through Odin. Feel free to correct me if I'm still wrong.
mr-cook said:
IndigoAK I am the one that posted the link on AA51. The file appears to be in tar.gz format like what is used for install through odin. I have not tested it, as I am not a developer, or in need of flashing to factory firmware at this time. I posted it as I seen many people looking for it. I believe it is needed to be able to safely start making modifications for this phone, CWM, Root, custom ROMs, ect., and being able to flash back to stock if something goes wrong. Hopefully with the information out there now it will jump start development.
Click to expand...
Click to collapse
I probably should have linked to your post. I apologize.
I just thought that posting it here on XDA might get it seen by more people who might know how to put this to use.
Hopefully somebody does put it to use. Due to the way that Straight Talked has gimped this phone, it's going to take the community to really make it worth the price they're charging for it.
I tried to link to the original post on android area 51, but as a new member I am not allowed, yet. I am just trying to get information out there, so thank you for posting it here (as I just now joined). The phone is fairly new and under advertised, but hopefully these posts will stir interest.
I was looking under the battery cover and noticed the FCC id for this phone (SGH-S959G) is A3L SGH I777. Now for everyone smarter than I. Does this mean that the phone is an i777, and would all the mods and ROMs ect. be directly compatible. Also its android 2.3.6. Version s959g UDLG1. Kernel 2.6.35.7. Any thoughts, educated opinions would be appreciated. Thanks.
Sent from my Galaxy Precedent using Tapatalk 2
mr-cook said:
I was looking under the battery cover and noticed the FCC id for this phone (SGH-S959G) is A3L SGH I777. Now for everyone smarter than I. Does this mean that the phone is an i777, and would all the mods and ROMs ect. be directly compatible. Also its android 2.3.6. Version s959g UDLG1. Kernel 2.6.35.7. Any thoughts, educated opinions would be appreciated. Thanks.
Sent from my Galaxy Precedent using Tapatalk 2
Click to expand...
Click to collapse
No.
Everything needs to be modified. The I777 rooting method works for this device, but nobody has been able to get past that as far as I'm aware. I've lost count of the number of times I've had to double reboot my phone trying to install every custom recovery image (and searching around suggests this is the case for a lot of other people) I can get my hands on and I've kept a pretty close eye on custom firmware sites - none of them have added support for this device (probably because you can't install a custom recovery image yet).
Guys I have the same problem, I tried to root my Straight Talk Galaxy SII using the AT&T root but CWM doesn't install and the root breaks the Wifi, Contacts save option, several apps like YouTube. I cannot revert back to the stock ROM due to this issue and I really could use the help.. I'm surprised that DEV teams haven't done much on the phone considering for 45 dollars a month you get really fast 7mb/s speed.
I'm willing to do whatever I can to contribute to a way of finally getting this awesome phone off of a sucky stock rom.
Thanks everyone!
I was just curious if it could be fully flashed to stock i777 GB. As it appears to be the exact same hardware. Completely start over making it the at&t i777.
Sent from my SGH-S959G using Tapatalk 2
mr-cook said:
I was just curious if it could be fully flashed to stock i777 GB. As it appears to be the exact same hardware. Completely start over making it the at&t i777.
Sent from my SGH-S959G using Tapatalk 2
Click to expand...
Click to collapse
No. I tried this.
Also, if your WiFi doesn't work, you probably used the Zedomax kernal. Search XDA for Entropy's kernel and use that instead.
LOOKIN. For Fully Rooted .. Samsung Galaxy s2. Sgh-s959g From Straight Talk. FLASHED a kernel dat when loading. Tells me its a sgh-i9100 ... has a ... ! ...triangle under it...and when I check the info on bout phone. It says sgh-i777.. any links for the best FULLY ROOTED kernels GB?.. PS. Willing to do testing with this phone from straight talk. But has. Att kernel.. one from. Entropy! !! Thanks 
Hi guys, I'm wondering if anyone can shed some light on a few things for me.
I have an ATT SGH i-337 MK2 with SafeStrap 3.71
Today I tried to flash PAC ROM and Dirty Unicorn into ROM Slot-1, and upon reboot when the ROM's logo should appear the whole screen just looked like when a nintendo cartridge isn't working. It was just a few crazy colors with some blocks and lines here and there.
Then I tried AOKP with it's Loki'd Kernel being part of the ROM. The nintendo screen came back again, but then the AOKP logo popped up clear as day for a second. Then went back to the lines and colors.
So could this be a problem with Safestrap compatibility? If so, how can I uninstall it? (I did read the dev's thread, and it just says use .APK and IDK what that means)
Or could it be that I also need to use Loki Doki with the other two? (Didn't see anything about that in PAC or DU threads)
Thanks!
Same issues apon using The Samsung Galaxy S4 for Verizon (jfltevzw) Build MK2 rooted using vRoot (English) and using safestrap. if needed I can upload the safestrap apk or version. If I install any type of AOSP ROM the boot logo is either missng or baby blue with wierd static lines. AOKP is the only AOSP ROM that eventually boots (with static boot logo) but no wireless works, and this is the same wether MK2 and/or MJ7 modules are installed or not. the only rom I can successfuly install and use daily that has no bootloader based issues is Hyperdrive ROM For jfltevzw & jflteatt. Any info would be much apreciated!
Sent from my SCH-I545 using xda app-developers app
^ Interesting. I didn't expect anyone else to have this issue. I never read about it before. I really feel like it has something to do with SafeStrap.
Heath Cliff said:
Hi guys, I'm wondering if anyone can shed some light on a few things for me.
I have an ATT SGH i-337 MK2 with SafeStrap 3.71
Today I tried to flash PAC ROM and Dirty Unicorn into ROM Slot-1, and upon reboot when the ROM's logo should appear the whole screen just looked like when a nintendo cartridge isn't working. It was just a few crazy colors with some blocks and lines here and there.
Then I tried AOKP with it's Loki'd Kernel being part of the ROM. The nintendo screen came back again, but then the AOKP logo popped up clear as day for a second. Then went back to the lines and colors.
So could this be a problem with Safestrap compatibility? If so, how can I uninstall it? (I did read the dev's thread, and it just says use .APK and IDK what that means)
Or could it be that I also need to use Loki Doki with the other two? (Didn't see anything about that in PAC or DU threads)
Thanks!
Click to expand...
Click to collapse
If you would have read 1st, then you would know that you can NOT flash any non TW rom on MK2. This is stated over & over on XDA. Safestrap is NOT the problem it is a Godsend from Hashcode for us to be able to flash custom roms onto our locked boot loader devices. Please read before flashing, bricking & then bashing the developers. Follow the directions posted on how to restore your phone, or better yet make a trip to Best Buy & they'll do it for you. Good Luck.
REEEEEEAAAAADDDD!!!!
It's been very well documented that AOSP does not work with safestrap. Neither does loki. There currently is no way/fix to flash AOSP.
So
1. No AOSP or GPE
2. No loki
3. No flashing custom kernels
Sent from my GT-I9505 using Tapatalk
John The Rhino said:
If you would have read 1st, then you would know that you can NOT flash any non TW rom on MK2. This is stated over & over on XDA. Safestrap is NOT the problem it is a Godsend from Hashcode for us to be able to flash custom roms onto our locked boot loader devices. Please read before flashing, bricking & then bashing the developers. Follow the directions posted on how to restore your phone, or better yet make a trip to Best Buy & they'll do it for you. Good Luck.
Click to expand...
Click to collapse
I did read first. I've been reading this forum for quite a while actually. But there is so much information it's hard to keep it all straight. This ATT stuff is a lot different then my VZW Razr was. That phone was just flash and forget. There are so many different ROM's for this phone now that are 4.3 or KitKat I guess I just didn't realize that, that Android version came with the ROM and was originally something more mod-able stock.
Any way I wasn't bashing SS or Hashcode. I clearly said "compatibility issue" i.e. some programs just don't play well together hence the existence of compatibility mode, virtual machines, and x86 processors. So maybe you should read before bashing novice community members and making yourself look like a big asshole.
And I don't need best buy to fix anything I have a NANDroid, backup on Kies3, and Google+. Besides, I did all of this flashing I on a separate partition so the stock ROM was never altered. Thanks for absolutely nothing at all.
For anyone else that feels like they can move on with me, I would really like to try to install TWRP in place of SS. I'd appreciate any help with how to go about doing that. TIA
Heath Cliff said:
I did read first. I've been reading this forum for quite a while actually. But there is so much information it's hard to keep it all straight. This ATT stuff is a lot different then my VZW Razr was. That phone was just flash and forget. There are so many different ROM's for this phone now that are 4.3 or KitKat I guess I just didn't realize that, that Android version came with the ROM and was originally something more mod-able stock.
Any way I wasn't bashing SS or Hashcode. I clearly said "compatibility issue" i.e. some programs just don't play well together hence the existence of compatibility mode, virtual machines, and x86 processors. So maybe you should read before bashing novice community members and making yourself look like a big asshole.
And I don't need best buy to fix anything I have a NANDroid, backup on Kies3, and Google+. Besides, I did all of this flashing I on a separate partition so the stock ROM was never altered. Thanks for absolutely nothing at all.
For anyone else that feels like they can move on with me, I would really like to try to install TWRP in place of SS. I'd appreciate any help with how to go about doing that. TIA
Click to expand...
Click to collapse
Well stating Safestrap may have a compatibility issue is offensive to the developer, especially since you did not read the instructions or posts from other members who did as you. If you would follow the directions it's perfect. I have 4 different roms on my phone + stock to choose from! How cool is that? I understand the overwhelming urge to flash a rom, as I too have been flashing on my Skyrocket since the factory warranty expired last year, and flashing roms is a breeze on that device. However, this S4 is more complicated since the introduction of the KNOX & the LOCKED boot loader. These phones are expensive so unless you really want a $700.00 brick, read, read some more, then read it all again. Safestrap uses TWRP to flash the roms, but TWRP alone is not compatible with MK2 nor is CWM. If you want to flash roms on your ATT MK2 S4 Safestrap is the only way to do that at this writing.
John The Rhino said:
Well stating Safestrap may have a compatibility issue is offensive to the developer, especially since you did not read the instructions or posts from other members who did as you. If you would follow the directions it's perfect. I have 4 different roms on my phone + stock to choose from! How cool is that? I understand the overwhelming urge to flash a rom, as I too have been flashing on my Skyrocket since the factory warranty expired last year, and flashing roms is a breeze on that device. However, this S4 is more complicated since the introduction of the KNOX & the LOCKED boot loader. These phones are expensive so unless you really want a $700.00 brick, read, read some more, then read it all again. Safestrap uses TWRP to flash the roms, but TWRP alone is not compatible with MK2 nor is CWM. If you want to flash roms on your ATT MK2 S4 Safestrap is the only way to do that at this writing.
Click to expand...
Click to collapse
Okay, well thank you for that. I just see so many ATT S4's in here with other ROMs and Recoverys I thought I could get something to happen. Anyway, sorry for the poor thread and response. I appreciate the plain blunt fact that SS and the ROMs that work with it are my choices for now. And don't worry about me. The worst that I'd probably get is a soft brick and I've recovered from that before Thanks again
Heath Cliff said:
Okay, well thank you for that. I just see so many ATT S4's in here with other ROMs and Recoverys I thought I could get something to happen. Anyway, sorry for the poor thread and response. I appreciate the plain blunt fact that SS and the ROMs that work with it are my choices for now. And don't worry about me. The worst that I'd probably get is a soft brick and I've recovered from that before Thanks again
Click to expand...
Click to collapse
Hey man I totally understand. It's hard to watch all these other roms pop up for the original S4 & we can't flash them. But we no longer have to suffer with only the stock rom option since Hashcode's brilliant Safestrap was released. Once you get use to it, the ability of being able to multi-boot roms really kind of makes up for the locked boot loader. Soon though, we will have 4.4 Kit Kat & then we can start this process of getting off the stock rom all over again. Right? It could be worse, we could have I-phones. We do have a ever growing number of great custom TW based roms available to us here for our device. So try them, you'll be surprised how much better your phone performs. Glad I made sense & forgive my bluntness that's just how us Rhinos roll.
I just acquired a GS4 from ATT today. it is:
Android 4.4.2 (which I upgraded myself)
Baseband V: I337UCUFNC1
I found this thread http://forum.xda-developers.com/showthread.php?t=2663545 But I wanted to make sure there is not anything newer or different since then. I wasn't able to find anything else by searching. I'm trying to root this phone to use CyanogenMod. Unfortunately, my phone is not supported in their list of easy installs.
Can someone verify the steps for me to root and flash Cyan to this model phone before I pull the trigger? Thanks!
burgertime78 said:
I just acquired a GS4 from ATT today. it is:
Android 4.4.2 (which I upgraded myself)
Baseband V: I337UCUFNC1
I found this thread http://forum.xda-developers.com/showthread.php?t=2663545 But I wanted to make sure there is not anything newer or different since then. I wasn't able to find anything else by searching. I'm trying to root this phone to use CyanogenMod. Unfortunately, my phone is not supported in their list of easy installs.
Can someone verify the steps for me to root and flash Cyan to this model phone before I pull the trigger? Thanks!
Click to expand...
Click to collapse
You can't flash anything other than Touch Wiz Roms. That guide and ones like The Ultimate All in one Guide will be a starting place. No custom recoveries either.
Sent from my GT-I9505G using Tapatalk
rugmankc said:
You can't flash anything other than Touch Wiz Roms. That guide and ones like The Ultimate All in one Guide will be a starting place. No custom recoveries either.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
So what's the problem? ATT? too new a hardware version? I have the worst luck with this stuff - if I buy a router to flash a custom firmware like Tomato, it's the ONLY version that isn't supported. crazy.
I'm not sure what a custom recovery is unfortunately. That said, can I root this phone at all? I guess if I can't flash the rom I want to use, can I at least install titanium and freeze all the crapware that I don't want running?
btw - thanks for the response.
burgertime78 said:
So what's the problem? ATT? too new a hardware version? I have the worst luck with this stuff - if I buy a router to flash a custom firmware like Tomato, it's the ONLY version that isn't supported. crazy.
I'm not sure what a custom recovery is unfortunately. That said, can I root this phone at all? I guess if I can't flash the rom I want to use, can I at least install titanium and freeze all the crapware that I don't want running?
btw - thanks for the response.
Click to expand...
Click to collapse
Any build after mdl has the bootloader locked down. If you read thru those two threads OP pages you get an idea. You will also need to get familiar with SafeStrap. I am on the old build and can use an exploit called loki-doki to bypass Sammy's security check and allow kernel to flash.
There may be some new stuff on rooting NC1, but I don't keep up. Basically you had to go back to mk2 to root then go back NC1 and use SafeStrap to flash only TW roms. The SafeStrap thread will explain that. But, it creates slots on the System partition again fooling Sammy. More or less--
Like I said not an expert as I don't have the issue you have with bootloader. But that is the gist of it. Just need to read up so you don't brick--good luck.
rugmankc said:
Any build after mdl has the bootloader locked down. If you read thru those two threads OP pages you get an idea. You will also need to get familiar with SafeStrap. I am on the old build and can use an exploit called loki-doki to bypass Sammy's security check and allow kernel to flash.
There may be some new stuff on rooting NC1, but I don't keep up. Basically you had to go back to mk2 to root then go back NC1 and use SafeStrap to flash only TW roms. The SafeStrap thread will explain that. But, it creates slots on the System partition again fooling Sammy. More or less--
Like I said not an expert as I don't have the issue you have with bootloader. But that is the gist of it. Just need to read up so you don't brick--good luck.
Click to expand...
Click to collapse
DAMN! Thanks!
burgertime78 said:
DAMN! Thanks!
Click to expand...
Click to collapse
Good Luck
There are plenty of folks here to help with specifics like jd and tedusa--:good:
burgertime78 said:
I just acquired a GS4 from ATT today. it is:
Android 4.4.2 (which I upgraded myself)
Baseband V: I337UCUFNC1
I found this thread http://forum.xda-developers.com/showthread.php?t=2663545 But I wanted to make sure there is not anything newer or different since then. I wasn't able to find anything else by searching. I'm trying to root this phone to use CyanogenMod. Unfortunately, my phone is not supported in their list of easy installs.
Can someone verify the steps for me to root and flash Cyan to this model phone before I pull the trigger? Thanks!
Click to expand...
Click to collapse
New way to root is call towelroot. Google it or search for it around here the link is everywhere. It's an apk file made by geohot (same guy that jail broke the iphone and ps3). Once you root you can install safestrap. If you've ever owned an droid device they have something identical called boot strap. Think of it as a dual boot of sorts. Definitely keep your eyes on these threads as well as the sgs5 thread. If an exploit is discovered it'll probably be for the s5 and will be compatible with our s4 (towel root was made for the s5 but works for a whole bunch of devices)
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
burgertime78 said:
DAMN! Thanks!
Click to expand...
Click to collapse
Link: http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3&nocache=1&z=8413408249616623
I was in the same boat as you 2 weeks ago, bought a NC1 and wanted CM, and used this to root. I currently use the Google Edition ROM that has been modified to work on locked bootloader phones, though it does have it's fallbacks. For someone new I'd recommend GoldenEye, just click the link on my signature to download it.
Good luck!
Oh, btw--check out GEOHOT's Towelroot thread in General for NC1. I knew I forgot one. That was the recent method I was thinking of. Not sure which of threads are best for you--depends what you want to do.
---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------
HaHa posted at same time.
You all are AWESOME! Thank you so much! I'll look into this and keep you posted.
rugmankc said:
Oh, btw--check out GEOHOT's Towelroot thread in General for NC1. I knew I forgot one. That was the recent method I was thinking of. Not sure which of threads are best for you--depends what you want to do.
---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------
HaHa posted at same time.
Click to expand...
Click to collapse
I just towelrooted. It worked! I was watching this video http://gs5.wonderhowto.com/how-to/r...nt-even-at-t-verizon-20-seconds-flat-0155617/ and I did it while I Was watching the video. On my device, it did not even reboot - i just said "should be rooted" so I loaded a root checker and sure enough, it is rooted! took all of about 8 seconds.
Now, on to a rom.
I'm confused now. Why can I not use CM? I read about SafeStrap and I understand it's sort of a dual boot setup - I get that. So, in a sense, I'm not really installing FRESH, a new rom - at least not in the sense that you format your hard disk and install a new OS. However, what ARE my choices in roms? I know the whiz touch, and now the golden eye, plus the google modified - but what else? I want something cut down, simple and battery friendly. I'm not a super power user and I don't require much. Actually, battery life is the most important thing to me.
This is my business phone - I use Gmail, SMS, maybe take a few pictures - and I listen to podcasts. very basic user. Advice?
burgertime78 said:
I just towelrooted. It worked! I was watching this video http://gs5.wonderhowto.com/how-to/r...nt-even-at-t-verizon-20-seconds-flat-0155617/ and I did it while I Was watching the video. On my device, it did not even reboot - i just said "should be rooted" so I loaded a root checker and sure enough, it is rooted! took all of about 8 seconds.
Now, on to a rom.
I'm confused now. Why can I not use CM? I read about SafeStrap and I understand it's sort of a dual boot setup - I get that. So, in a sense, I'm not really installing FRESH, a new rom - at least not in the sense that you format your hard disk and install a new OS. However, what ARE my choices in roms? I know the whiz touch, and now the golden eye, plus the google modified - but what else? I want something cut down, simple and battery friendly. I'm not a super power user and I don't require much. Actually, battery life is the most important thing to me.
This is my business phone - I use Gmail, SMS, maybe take a few pictures - and I listen to podcasts. very basic user. Advice?
Click to expand...
Click to collapse
MDL builds have an exploit that allows the kernel to flash. That is loki-doki. Bypasses the Sammy security check to allow this. There is no exploit yet for post MDL builds. Hence you can only flash stock Touch Wiz kernels, thus only roms that have them. So, no aosp based roms. In one of the threads in General that talk about MK2/NC1 etc is a list of roms for you. I forget the technical coding side of SafeStrap. But, it puts roms in System bypassing the bootloader. But, no way of doing that with aosp roms yet.
I am old and don't retain things much anymore if they are not very important to me. So, although I have read up on this stuff, and have a "45 year old" Engineering Degree, I don't need SafeStrap having the MDL bootloader. So, don't remember all that I have read. But, what I said is the basics of it.
Your roms need to have SafeStrap option in the rom thread's OP page. If not listed, it won't work. Having said all that things like Towelroot are new and more options may come along. :good:
Hi, I've been trying to install a custom rom (at this point ANY custom rom) on my friend's phone. I have worked on several phones before, including my own sprint GS3, but this is my first time trying to work around a locked bootloader, and BOY is it a pain, haha. I'm no dev, but I would like to think that I'm pretty competent.
First a few things to note, are that the phone is currently on NI1 (Been too much of a sissy to go to NJ4 in case it screws something up, I don't even know why), it is the 16Gb version, I am using an external sd card to flash everything, and yes I am flashing loki-doki after everything.
So what I've done so far is:
- Try to install TWRP
- Find out that won't work and finally figure out I need safestrap
- Successfully install safestrap after using towelroot by ODIN-ing the NC1 kernel then going back to the NI1 kernel
- Try to flash Resurrection Remix and KToonsez kernel using a new rom-slot, and wind up soft-bricking (stuck on bootloader screen, can get to download mode)
- ODIN NB1 tar then ODIN NI1 update
- Repeat the last few steps several times because I'm too idiotic to realize that it JUST ISN'T GOING TO WORK!
- Finally find a reference to flashing the ATT kernel modules after the rom. That got me past the soft brick and safestrap screen, but I don't even see a boot animation
As of right now my sequence to successfully not soft-bricking (what an accomplishment) is to flash the rom>gapps>ATT kernel module>supersu>loki-doki>wipe dalvik/cache
Now, is it worth it having already spend a good 7 hours, just to get a custom rom? Of course not, it's not my phone and my friend isn't picky. He'd be just fine with rooted TW. However, It kills me that I don't know what's going on, so here I am lol.
TL;DR: Phone has safestrap, is rooted, but any time I flash a rom it gets past the boot loader/safestrap screen and never shows a boot animation, or anything past that. Can anyone help figure out what's going on please?
Thanks in advance.
You can only flash touch wiz based roms with safestrap and you can't flash kernels with safestrap. That's been your problem with soft bricking.
Edit, see this for roms you can flash http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?t=2616221
Thanks guys. I thought I read through the whole thread, but there is so much information, it's pretty scattered, I must have missed the thing about only TW roms working.
Now a few more questions:
1) Is it worth updating to NJ4? The phone is new and doesn't have any app data or anything that would be missed by updating. I see quite a few roms in 4.4.4, but it looks like most of them are AOSP based, which leads me to my next question...
2) Is there a way to get AOSP roms to work? I see all of these AOSP based roms, obviously for this phone, but it would be pointless to make them if they don't work.
Masterjuggler said:
Thanks guys. I thought I read through the whole thread, but there is so much information, it's pretty scattered, I must have missed the thing about only TW roms working.
Now a few more questions:
1) Is it worth updating to NJ4? The phone is new and doesn't have any app data or anything that would be missed by updating. I see quite a few roms in 4.4.4, but it looks like most of them are AOSP based, which leads me to my next question...
2) Is there a way to get AOSP roms to work? I see all of these AOSP based roms, obviously for this phone, but it would be pointless to make them if they don't work.
Click to expand...
Click to collapse
It wouldn't hurt to update to nj4. But it's not going to help you either. Only phones on mdb or mdl bootloader can flash non touch wiz based roms using loki. And you can't go back to those bootloaders
Sent from my Nexus 9 using XDA Free mobile app
Alright then. Hyperdrive looks pretty good, I'll try that along with Ktoonsez kernel. I'll report back later to let you know how it goes. Thanks again!
Masterjuggler said:
Alright then. Hyperdrive looks pretty good, I'll try that along with Ktoonsez kernel. I'll report back later to let you know how it goes. Thanks again!
Click to expand...
Click to collapse
Again, you can't flash a kernel in safestrap
Sent from my Nexus 9 using XDA Free mobile app
Oh, I get it now. That didn't quite register before. So just to confirm, after I flash the rom (which already has its own custom kernel included), I still need to flash the stock ATT kernel, correct?
Flash the rom, super su, and the att module for your base. Hyperdrive is a very good rom, good luck. Also the rom doesn't include a kernel, your original kernel stays put. That's why only tw roms work, because your new rom has to be compatible with the kernel already on your phone.
Just reporting in, I now have the phone up and running using Hyperdrive Rom. Thanks for the help!
I actually had a problem where it would not shut down correctly, but found out it was because I was installing the rom in a rom-slot in safestrap. As soon as I tried the stock rom slot, it worked flawlessly.