Having just bought an S3 (on first charge right now), anything I should be aware of before I start playing? 32gb class 10 sd card on its way so I've a couple of days before I can actually set it up as I want.
Currently using a htc desire, rooted, unlocked, cm7 rom etc..and had an old galaxy spica, so not afraid of odin
thanks
frosty68 said:
Having just bought an S3 (on first charge right now), anything I should be aware of before I start playing? 32gb class 10 sd card on its way so I've a couple of days before I can actually set it up as I want.
Currently using a htc desire, rooted, unlocked, cm7 rom etc..and had an old galaxy spica, so not afraid of odin
thanks
Click to expand...
Click to collapse
You need to start as always by reading the FAQS and Guides and number one is backup your EFS folder .
jje
Well, first things first: congrats, but you should have waited for the S IV to come out.
Second of all, you might want to download Odin and try out some different kernels, see which one you like. I personally am using Siyah Kernel overclocked to 1.8GHz whilst running on two cores (I only unlock all four cores when I need to).
Then check out a decent ROM which works for you. Just like with kernels, try them out, see what you like and (maybe even) stick with it. Again I'll tell you what I'm using (Even though it's pretty obvious, because of my signature) I'm using MIUI Polimorph 3.5c, I think it is.. For me it had amazing battery life and I'm just a MIUI fan, I guess.
All the links are in my signature
Then you should get an xda-developers battery cover. Just for aesthetics
CyanogenModded Very China-like, from my Samsung Galaxy S III
LG Familyguy59/Beatsleigher
Thanks. S IV is a little out of my budget, sadly. Odin installed, rooted and trying to back up the efs using EFS professtional 2.0.33, but it keeps showing an error, "unable to create archive". Seems the phone is writeable some of the time only? EFS created the folder but got no further, when I've tried putting apps on it works for a little whole then looks as though the drive is locked. Perhaps this is related to no sim or sd card installed?
Still, I'll googlesomemore, and play some more. Might stick with stock rom for a week or 2 to see how bloaty it is,and battery life on stock.
Maybe I ought to do it through ADB myself, following the guide
I had a look at a miui rom on my desire....it didn't last long
frosty68 said:
Thanks. S IV is a little out of my budget, sadly. Odin installed, rooted and trying to back up the efs using EFS professtional 2.0.33, but it keeps showing an error, "unable to create archive". Seems the phone is writeable some of the time only? EFS created the folder but got no further, when I've tried putting apps on it works for a little whole then looks as though the drive is locked. Perhaps this is related to no sim or sd card installed?
Still, I'll googlesomemore, and play some more. Might stick with stock rom for a week or 2 to see how bloaty it is,and battery life on stock.
Maybe I ought to do it through ADB myself, following the guide
I had a look at a miui rom on my desire....it didn't last long
Click to expand...
Click to collapse
Check the link to MIUI in my description. I hated it on my cousin's Leo, I almost kicked my Galaxy Nexus against the wall with MIUI and I never dared to install it on my GS II, but on the GS III it works like a charm. But everyone has to figure out there own thing, I guess.
frosty68 said:
Thanks. S IV is a little out of my budget, sadly. Odin installed, rooted and trying to back up the efs using EFS professtional 2.0.33, but it keeps showing an error, "unable to create archive". Seems the phone is writeable some of the time only? EFS created the folder but got no further, when I've tried putting apps on it works for a little whole then looks as though the drive is locked. Perhaps this is related to no sim or sd card installed?
Still, I'll googlesomemore, and play some more. Might stick with stock rom for a week or 2 to see how bloaty it is,and battery life on stock.
Maybe I ought to do it through ADB myself, following the guide
I had a look at a miui rom on my desire....it didn't last long
Click to expand...
Click to collapse
Personally I'd play around with stock for a while and identify any shortcomings with it from your personal point of view before flashing a custom rom, the S3 is the first phone that I've stuck with a stock based rom over CM simply because I miss some of the Samsung stock functionality on straight AOSP roms. If you've got root Philz recovery can back up the EFS for you saving the need for EFS professional, which TBH i have no experience of.
Related
Hi guys,
I've had an S2 for a few months now, and although I've managed to root the phone I'm still pretty green and need help.
I've had an OTA update from Gingerbread to ICS which I only installed as it popped up when I was using the phone.
The battery died earlier than expected and now it's stuck in a bootloop.
I don't want to have to ROM it as frankly I'm still in the "full theory" stage. I've heard of Odin and SamMobile.com, I've seen hours of vids on Youtube but I'm hoping there's another way to get around it. My confidence levels are improving but not there yet.
I have a Titanium backup on the phone from 2.3.4, if I wipe the phone from recovery will it work? Is there anything I can do apart from a new ROM?
If you had my lack of experience with this, what would you do? Thanks.
Can you get into download mode?
If so, you may have to bite the bullet and use Odin to flash the original firmware. You will be able to find it on these forums.
Don't sweat it, just download the Orange ICS ROM and put it in PDA on Odin and flash it, it'll take just a couple of minutes and you are done.
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
FourQ said:
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
Click to expand...
Click to collapse
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Warren.D said:
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nothing confusing about rooting either.
Download one of chainfires cfroot kernels or siyah kernel and flash via Odin.
That's it you're rooted.
----------------------
GTI9100
Hydra H2O 1.2.1
fluxi xx.01_rc5
if ya have a look around the forum, theres plenty of pre-rooted roms to flash via odin that wont increase ya binary counter, nothing hard about that.
Read the links in my signature
Sent from my GT-I9100 using XDA
I'm still reletively new to it
and I've had a couple of bootloops. A bit of a panic and then I figured out what I'd done wrong. As long as you follow instructions to the letter you'll be fine.
Edit: *Relatively, damn it.
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
FourQ said:
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
Click to expand...
Click to collapse
getting a custom rom isn't something you should be afraid of
getting a custom rom (or kernel) can improve your battery life (some of them).. but just be sure that getting a custom rom, it should be for whatever you're running (Gingerbread or ICS) usually, roms are flashable via CWM
take a leap, when you get into bootloop or get some problems along the process, just flash a stock firmware with odin..
@saywhatt
A mate (who's been doing this for years) has installed CWM7. It's odd how the things I liked about Gingerbread were added by Samsung, not Google.
I suspect I'll run with CWM7 for a week or so and decide then. First impressions aren't always correct (especially if you saw my face!) but after a week I should have a pretty good impression of the new ROM. I'm hesitant about ICS as the official version killed the phone but ultimately I may end up there.
It's good to watch the Youtube vids on how to flash stock ROMs with Odin. It's something I may try next week if CWM7 falls from favour.
Ultimately I'm sort of glad it happened. It's given me new confidence to try these things as I know there's a good chance it can all be recovered.
Q
I've never been too afraid of rooting or flashing. My first android device was a cheap piece of rubbish (an LG GTsomething i think), so I built up confidence in rooting and flashing because I didn't care if i damaged my phone.
I would recommend anyone who's not too confident to go out and get a cheap phone, it's a pretty significant investment but if your unsure about what your doing and just want to experiment, it's definitely worth the peace of mind.
...
I'm hesitant about ICS as the official version killed the phone
Click to expand...
Click to collapse
no m8 it didn't, your battery dying while you were updating killed your phone
It had finished a while before that. I was selecting a new font when it died.
You can't stuff up your phone anymore - its already in bootloop, what do you have to lose?
Odin is indeed very easy. Just make sure F.Partition is unchecked. Put the ROM in PDA and flash! Of course, after your phone has been put into download mode and connected to pc via usb and one of the Odin blocks have turned yellow.
Your phone is already rooted? If you made a backup in CWM (NOT Titanium Backup, this won't help you right now, as it's only for apps) you should restore that in CWM. A wipe and factory reset wouldn't help you right bow.
I understand you are a bit skeptic of ICS stock ROM right now, but remember you probably got pushed an early version,.the latest versions are very stable! Though Custom ROM's are the way to go eventually. Try the latest stable Cyanogen ROM.
Sent from my GT-I9100 using Tapatalk 2
@FreeStanler
Good point.
The stock ICS ROM was 4.0.3 if memory serves. It wasn't there for long but I was curious to see which version I'd been upgraded to.
I'm planning to see how this CWM7 ROM sits with me. If I can find out which app is causing this: http://t.co/9GfdXmD I'll probably be happy with it. I need to have a good play about with it to give it a fair chance. May end up with ICS/Stock ICS but for now we'll see how it goes.
Why on earth would you use Cm7 when Cm9 is far better, plus to flash a fw & then root with SuperOneClickRoot, or use the cf root kernel. The whole process takes 5 mins. Honestly M8 there's nothing to worry about. One thing I will say tho, Google Nandroid back up & once you know how to use etc, use it & make it your best friend coz that's the only thing that will fix the bootloop in the future
Sent from my GT-I9100 using xda premium
@blade30p
I didn't. A friend who's been doing this for years did it for me. I was hoping to get something resembling the stock Gingerbread on the phone, instead I got CWM7.
My last HTC Thunderbolt, I had used the [ALL IN ONE] The HTC Thunderbolt Tool! to root my phone. This went well.
I then did a backup of the phone using clockwork mod. Then I flashed leanKernel: minimalistic kernel, which now I realize is a CM7 kernel?
The problem fallowed the kernel flashing. It would boot through the HTC boot image, then through the Thunderbolt logo and straight to a black screen. After that I decided to restore the factory backup before the kernel after wiping data and the system. The problem was after restoring the backup of the original rom the phone bricked. I couldn't get it to boot past the white screen with the HTC screen. Thing is before this phone I had a Nexus S 4G so my first official task on that phone was rooting and flashing custom kernels and roms. At this point I'm not sure if the phone was faulty or if I botched the job somewhere.
If you flashed the wrong kernel for the rom the fix was as easy as wiping cache / dalvik and flashing the correct kernel. As far as you backup you might have a corrupted backup which could be why it bricked. Your SD card may be corrupted too and could be why the backup was corrupted. Maybe try backing the SD card up and reformatting it just to be sure.
Sent from my ADR6400L using Tapatalk 2
Thanks for the response. I thought as much actually. I had already had the phone replaced. It had other issues since the first day I had it. I literally had it 4 days and in those 4 days it would just randomly restart and that was all factory. Lucky for me the Manager of the Verizon store sold us the phones. He just replaced it, but mainly because we had a lot of other issues. I'm actually feeling brave enough to try it again. The only thing that bugs me is the RUU thing. On my old phone it was way simpler.. well.. I had it for a year so it was probably just simpler to me. Either way, I guess the question now is what would be a good kernel for the factory rom? Until I find another rom I want to try? I wanted to hold out for the ICS update but I doubt it will happen after all the reading I've done.
Edit: Yes, I understand that asking for a good kernel for the stock rom is asking for opinions, but that's what I'm looking for.
Imos leankernel for gb sense would be the best. You should still think about reformatting your SD card though.
Sent from my ADR6400L using Tapatalk 2
I checked my SD card's download section and guess what I found. imoseyon_leankernel_v5.1.0GBS.zip This is what I flashed to my last phone. From what I gather this should work with sense 2.1 Android 2.3.4, Software number 2.11.605.19 710RD Now I've got to figure out why this bricked my last phone. I should also mention that I did 2 backups. One with Clockwork mod and another after flashing to EXT4. I tried restoring both in EXT4 and no such luck. Keep in mind, this is an old issue but I'm just baffled as to what happened. The SD card seems fine from what testing I've put it through though.
http://forum.xda-developers.com/showthread.php?t=1260185
the thread I got said kernel from.
You need to use 6.2 for 605.19. That shouldn't have bricked you though. From what you've stated though all I can gather is that the backup is bad.
Sent from my ADR6400L using Tapatalk 2
When you say 6.2 are you talking about a kernel version? If so then I thought 5.1.0 was the most recent, as noted by that thread. Am I missing something?
Well... scratch that question.. I did a quick google and noticed that it's not on these forums. >.>
Edit: Ok. Before I get too far into this. I've rooted, and did a backup with revolutionary CWM. I decided to check out the files in the backup on the phone and some files I can open while others throw back a "Cannot Open File: it does not appear to be a valid archive." with winzip and they also give me an error with 7zip. Should the boot.img file give this error? I can't go off of the MD5 as it was generated by these files.
I could see that happening with a windows computer. I don't know which ones it can open honestly. The only way that you will really be able to tell is from the md5 or just by assuming that is bad because of the first unsuccessful restore.
Sent from my ADR6400L using Tapatalk 2
Yeah, I completely scrapped everything from the last phone's rooting process.
I think I'll do another backup just to be on the safe side.
Edit: thank you for your help. I am now rooted and custom kerneled. I think this is pretty much what I wanted. I'll worry about custom ROMs later on down the road.
Sent from my ADR6400L
I've tried to put a new rom on phone after installing cwm. The 3 different jellybean roms that I've installed will not load up. They all stay on the loadup screen and never finish loading. I never had any problems flashing previous phones with CWM. Anyone's help would be appreciated.
weati said:
I've tried to put a new rom on phone after installing cwm. The 3 different jellybean roms that I've installed will not load up. They all stay on the loadup screen and never finish loading. I never had any problems flashing previous phones with CWM. Anyone's help would be appreciated.
Click to expand...
Click to collapse
Are you following the instructions as stated in the op?
Sent from my SGH-I777 running AOKP
He used Rom Manager. Like a bad bad little boy. Or at least that's what I'd put my money on.
No
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Phalanx7621 said:
He used Rom Manager. Like a bad bad little boy. Or at least that's what I'd put my money on.
Click to expand...
Click to collapse
I have seen this on a few different roms. After the rom hangs on the loading screen go ahead and reboot the phone. If that doesn't work flash a different kernel, and try to boot. If that doesn't work let me suggest Shostock 3. Try that rom. I have never had a problem flashing that.
weati said:
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Click to expand...
Click to collapse
And because this phone isn't other phones, you can't use rom manager with it. It's a nono. And there is a sticky about it. And many threads. And posts. Warning about it.
thanks
Guess I should have tried that before restoring my cwm backup and ordering a different phone. I needed an unlocked phone anyway LOL.
Butchr said:
I have seen this on a few different roms. After the rom hangs on the loading screen go ahead and reboot the phone. If that doesn't work flash a different kernel, and try to boot. If that doesn't work let me suggest Shostock 3. Try that rom. I have never had a problem flashing that.
Click to expand...
Click to collapse
weati said:
Guess I should have tried that before restoring my cwm backup and ordering a different phone. I needed an unlocked phone anyway LOL.
Click to expand...
Click to collapse
Let me get this straight. So you:
1. Decided to flash first and look later, using a method that "worked on other phones."
2. Didn't search the forums or even look at the stickies to find a solution to your problem.
3. Gave up and ordered a different phone rather than taking the 10 minutes it would take to easily get yours up and running?
Wow. Just wow. Tell me this; what phone did you order as a replacement?
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
mattdm said:
Let me get this straight. So you:
1. Decided to flash first and look later, using a method that "worked on other phones."
2. Didn't search the forums or even look at the stickies to find a solution to your problem.
3. Gave up and ordered a different phone rather than taking the 10 minutes it would take to easily get yours up and running?
Wow. Just wow. Tell me this; what phone did you order as a replacement?
Click to expand...
Click to collapse
weati said:
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
Click to expand...
Click to collapse
1. Kies generally only works with stock unrooted phones. Use Odin instead.
2. The phone has no "inability to take a new rom" if you do it the right way.
3. Apparently you don't know pretty well what you're doing.
4. The i9100 works exactly the same way as the i777, and if you try to use Rom Manager on it, you'll end up with the same result: a phone that won't boot.
5. AT&T will unlock an i777 for you if you ask them.
6. Just read the damn stickies, particularly this one and this one.
This thread is full of win.
weati said:
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Click to expand...
Click to collapse
You resolved the problem by buying the unbranded version of the exact same phone?
weati said:
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
Click to expand...
Click to collapse
So u paid 70 dollars to unlock a phone. Great hope it was worth it. Because like others have said they are identical.
Sent from my SGH-I777 running AOKP
I'm gonna go out on a limb here & ask a question that's been on my mind for a while, so bear with me. But first, let me give you some background so there's no confusion & no unnecessary questions asked. I'm by no means a "pro" at modifying my Note 3, I just follow instructions carefully & then implement those directions to achieve results. That's how I rooted my Note 3 but could still care less that I tripped Knox in the end.
I have the 32 GB Sprint Galaxy Note 3 with an 8 GB microSD. It's rooted using Chainfire's method. I also have TWRP for a recovery, but I'm using the stock Sprint ROM that came with it. I have a few root apps installed (Titanium backup, AdAway & Root Explorer) but the rest are what Sprint (& Android) put in there, minus a few that are totally unnecessary for me...(chat apps, picture drawings, step counting & so on) that were removed with Titanuim. It's still on 4.3 Jellybean with PUBMJ4 baseband. I also have the Wi-Fi hotspot fixed through 2 file replacements using Root Explorer.
Now that you know what I have, onto the question...
I see many, many ROMs in other threads that I'd like to try out, but don't know how to go about doing this. Before you jump right in & answer, here's my problem. If I try a ROM but don't like it, or it doesn't suit my needs, how can I go about going back to what I have now in the best (& fewest) steps necessary? In other words, to go back to exactly what ROM I have now, the apps installed, baseband, the whole nine yards. Just like a computer backup, it's a bit-for-bit restore, completely mirroring the hard drive. Understand?
Maybe you could explain to me like I'm seven years old what apps I need, what procedures are taken, the order in which they happen & so on. If I need an app or two to do just this, I have approximately $20 Google Play credit left.
Can a DEV or an experienced person that's done just this help a fellow out? Don't get me wrong, the stock ROM I'm using works for me, but there's ROMs posted that look just awesome! It's all about "personalization", am I right?
Easy, since you have a custom recovery installed (twrp) , you simply do a "nandroid" backup (I personally like to backup to an external SD card, so get a bigger one) before wiping and installing something new. If you like what you got, fine. If you want to go back, wipe and restore! Easy Peasy!
Sorry, being a father means sometimes your time suddenly becomes unavailable. But believe me, it's really easy once you figure out twrp.
I'll let another fine member get more details if you actually need them. ?
Sent from my calculator watch.
So did you figure it all out?
Sent from my SM-N900P using Tapatalk
kingdazy said:
Easy, since you have a custom recovery installed (twrp) , you simply do a "nandroid" backup (I personally like to backup to an external SD card, so get a bigger one) before wiping and installing something new. If you like what you got, fine. If you want to go back, wipe and restore! Easy Peasy!
Sorry, being a father means sometimes your time suddenly becomes unavailable. But believe me, it's really easy once you figure out twrp.
I'll let another fine member get more details if you actually need them. ?
Sent from my calculator watch.
Click to expand...
Click to collapse
Doing a Nandroid backup as we speak! I didn't realize TWRP could do that. (duh! ) I only installed TWRP because I just liked the name of it. TWERP!! (gotta nice sound to it, doesn't it??) Thanks a bunch! :good:
tonyevo52 said:
So did you figure it all out?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I did. I found a Youtube link on how to do a TWRP backup on the Sprint Note 3. Easy Peasy as said above! I'll try some ROMs this weekend (can't promise nuthin' cause it's gonna be 70 degrees this weekend & I'm itchin' to ride my mountainbike along the boardwalk at the Virginia Beach.)
But now that the hard part is outta the way, it's all easy street from here!
Just be sure to Please, oh god Please, read all instructions on any rom you decide to try. Doesn't hurt to read the last 10 pages of each too, get an idea of Current issues that may not be documented in the OP.
And don't get lazy, follow word for word. The only times I f*cked stuff up was when I didn't follow instructions (ie, thought my experience meant I knew best), or just got sloppy.
And, don't forget to wipe! (I wipe 3X, everytime, as a habit. Some people will give you reasons why that's unnecessary, but I can say confidently, if perhaps anecdotally, that I Never have the issues others have with bad flashes, softbricks, FCs, etc.)
Something to get comfortable with, even though you may never need it is ODIN. It's most common use is a utility for flashing stock ROMs and firmwares, great for recovery from bad things. Again, you may never need it, but have it ready in your Pc with a stock ROM file, just in case.
Finally, Titantium Backup can be your best friend, if used properly. It can also be a real pain, so don't become too dependant on it.
FIN
Sent from my calculator watch.
kingdazy said:
Just be sure to Please, oh god Please, read all instructions on any rom you decide to try. Doesn't hurt to read the last 10 pages of each too, get an idea of Current issues that may not be documented in the OP.
And don't get lazy, follow word for word. The only times I f*cked stuff up was when I didn't follow instructions (ie, thought my experience meant I knew best), or just got sloppy.
And, don't forget to wipe! (I wipe 3X, everytime, as a habit. Some people will give you reasons why that's unnecessary, but I can say confidently, if perhaps anecdotally, that I Never have the issues others have with bad flashes, softbricks, FCs, etc.)
Something to get comfortable with, even though you may never need it is ODIN. It's most common use is a utility for flashing stock ROMs and firmwares, great for recovery from bad things. Again, you may never need it, but have it ready in your Pc with a stock ROM file, just in case.
Finally, Titantium Backup can be your best friend, if used properly. It can also be a real pain, so don't become too dependant on it.
FIN
Sent from my calculator watch.
Click to expand...
Click to collapse
No worries! As I said in the OP, I follow directions carefully. I read everything.
Odin is my friend as well. I have it installed on my laptop. That's how I flashed basebands & deodexed stock rooted ROMs on my Galaxy S III. I also have the original stock Sprint ROM for this GN3 "just in case", in a folder sitting on my desktop with a few extra tools. I've never bricked a phone, unless you count using Samsung's online update (can't think of the name at the moment). It said 4.3 was available, so I downloaded it. It flashed, rebooted, but stuck there. Never finished the boot, just gave me an error code. Samsung's own update killed my GS3 & was unrecoverable. Believe me, I tried everything. What was strange, was the ROM was 4.3 but the baseband was the previous version, not the newer one, so the phone just puked. It never updated the baseband so it bricked. Now, I tried (and used) different radios with no problems before the update. Everything worked in harmony. Go figure!
Time for sleep my friend. Gotta work in the morning!
I rooted my sprint Note 3 when I first got it three years ago and flashed it with a custom ROM. I used it for a year and then got a cell phone from work, so I basically stopped using the Note 3 except occasionally. I decided the other day that I wanted to try updating to a newer version of android on the Note 3. It's been a long time since I messed around with rooting, ROMs, and such, and I did not pay close attention to what I was doing and flashed a ROM that was incompatible. When I restarted, I got a Set Warranty Bit Kernel error. I can get the phone into download mode, but I'm unsure of what to do next to get it back to a usable state.
Is there a guide somewhere to walk me through this process?
Thanks!
Solved
Well, I got the phone working again. I basically followed this guide I found. I tried to paste in the link but I'm still too much of a noob. Anyway, it was on android central, and part of the url was how-flash-stock-rom-via-odin-new-interface. Hope that helps someone.
There was one step not covered in that guide - odin kept saying that the md5 value was invalid. I found a youtube video that said to change the extension of the firmware (it was .tar.md5, changed to .tar). After that, it worked and my phone is back.
Is there a guide somewhere to walk me through this process?
Click to expand...
Click to collapse
There's guides everywhere on this site! Just gotta find the right ones lol. Makes it that much better when you finally find em. Next time make a complete backup of your phone first. I like to use TWRP, you can download it directly from the Play Store. I got my Stock Firmware from this archive:
http://samsung-updates.com/device/?id=SM-N900P
Make a backup of that then flash away! It'll be a lot easier/faster to recover with TWRP. What ROM did you flash to yours? Just curious cause every one I've tried had multiple issues to where I wasn't even able to use half my phone smh. Then I root it with CF-Auto:
https://forum.xda-developers.com/showthread.php?t=2466423
Through Odin:
http://odindownload.com/download/#.WYX1A4jyuyJ
Then I make a another separate TWRP backup of my Rooted Stock Phone just in case lol. Lemme know if you run into problems again I'll try to help find it and/or fix it. The more problems I deal with the more I learn! :fingers-crossed:
Might wanna get a USB storage or something too cause ALL these backups take up time and space. (My external SD Card slot hasn't worked for awhile!)... does yours?