This firmware is the unmodified Lollipop (Android 5.0) firmware downloaded through Samsung Kies. In case you need a copy of the firmware so that you don't have to keep downloading it through Kies, I'm providing you with a copy via the link below. It's odin flashable. Use the "AP" or "PDA" button to flash it onto your phone.
1. Download the stock Android 5.0 ROM (Lollipop) - Sprint N900P ONLY! - androidfilehost.com/?fid=24391638059060029
2. Download the official Samsung Kies. - samsung.com/in/support/usefulsoftware/KIES/
3. Download Odin 3 or later. - samsungodindownload.com/download/
4. Open Samsung Kies, and connect your phone. Wait for it to install the needed drivers.
5. Open Odin and make sure that it says it's "Added!"
6. Click the "AP" button and open the downloaded ROM.
7. Wait for it to finish verifying the checksum.
8. Make sure that "Auto Reboot" and "F. Reset Time" are the only boxes checked. (The default)
9. Click "Start" and wait for it to go. (Sometimes it gets stuck when it says "Setup Connection" and then you need to unplug your phone and restart Odin. - BE CAREFUL! Make sure it really is stuck or you'll brick your phone!)
10. [Optional] Flash TWRP (twrp.me) or CWM. (clockworkmod.com) TWRP is more free than CWM in the sense that the CWM ROM Manager has a payware version. If you're feeling generous towards those who spend countless hours each day for fun and to make your life a bit easier, throw them a few bucks. Both are freely available.
WARNING: Odin can brick your phone if you don't know what you're doing. If you break it, just buy another $800 device. I'm providing these instructions and the ROM without any warranty. You do with them what you feel is best.
That this is a zip file, it is not seen my Odin.
THANK YOU THANK YOU THANK YOU! You helped me save what I thought was a dead phone with this!
Is there a mod to change the launcher to 5x4
mac01843 said:
That this is a zip file, it is not seen my Odin.
Click to expand...
Click to collapse
Not sure if you've figured it out yet but you'll have to extract the .tar file from the zip, then Odin will be able to see it, the .tar file that is.
Thank you, thank you, thank you. This totally saved my bacon after a moron at the Sprint Store (and perhaps me for letting him look at it) replaced the SIM and then said that there was nothing they could do for the phone since it had been rooted.. now I have a way to reactivate the phone before switching back to a decent ROM.
This worked like a charm!
Anyone have a mirror?
I get a 404.
Also, will this upgrade my baseband from OC5 to OK2? I am having issues with CM12.1 nightly where I am not getting LTE and I was hoping upgrading the baseband could help. A bit of a noob here so any sort of suggestion would be helpful.
can I keep it unlock?
Can I keep my KITKAT 4.4.2 NOTE 3 Sprint unlocked after updating this stock firmware? I'm newbie and English is not my mother tongue.
Yes you can!
Anyone? On CM as well and would looove to have an Odin flashable Stock ROM
tusker559 said:
I get a 404.
Also, will this upgrade my baseband from OC5 to OK2? I am having issues with CM12.1 nightly where I am not getting LTE and I was hoping upgrading the baseband could help. A bit of a noob here so any sort of suggestion would be helpful.
Click to expand...
Click to collapse
Or maybe point me (us) in the direction of finding something similar?
Anyone else getting invalid MD5 checks in ODIN with this one? Does anyone have an valid download link? Trying to switch back to Stock so I can pull the 6.0 OTA and fix my GPS issues.
Edit:Georgia Mirror is valid
So I used the process, flashed over to stock and had the phone boot up to the Updating 292 Apps then rebooted and now it's sitting on the yellow Sprint boot screen. Blue LED fading in and out with the screen going brighter for a second with a light vibrate at the same time. Has been like that for several minutes now and not sure if I should try to flash again or what. Anyone have any advice?
iletumi said:
So I used the process, flashed over to stock and had the phone boot up to the Updating 292 Apps then rebooted and now it's sitting on the yellow Sprint boot screen. Blue LED fading in and out with the screen going brighter for a second with a light vibrate at the same time. Has been like that for several minutes now and not sure if I should try to flash again or what. Anyone have any advice?
Click to expand...
Click to collapse
Same here. Been waiting about 10 minutes now watching the Sprint screen do the exact same thing.. Giving it another 10 or 15 minutes just to make sure then I guess I'll try again?
Update #1: Tried again and still stuck. I'm at a loss. Pissed at myself for not having a backup since my SD card went down. Anyone with any guidance would save me.
Update #2: Pulled battery. Rebooted into stock recovery and did a factory reset. Phone booted up. Crisis averted.
how did you access the georgia mirror?
404 error on file link.
Nevermind. Tried again and it downloaded.
misterkatanga said:
Same here. Been waiting about 10 minutes now watching the Sprint screen do the exact same thing.. Giving it another 10 or 15 minutes just to make sure then I guess I'll try again?
Update #1: Tried again and still stuck. I'm at a loss. Pissed at myself for not having a backup since my SD card went down. Anyone with any guidance would save me.
Update #2: Pulled battery. Rebooted into stock recovery and did a factory reset. Phone booted up. Crisis averted.
Click to expand...
Click to collapse
Factory reset and it works now! Thank u!!!!
Related
Yesterday, I plugged in my tab to the charger over night. When I unplugged it today, I restarted it and after that it won't boot. The tab only shows the "Samsung galaxy tab 10.1" text for about 20-30 seconds and then it seems to reboot.
The device is rooted and running this rom. It is a 10.1" P7500 3g version.
Although I can still access recovery and bootloader modes, so I've tried wiping cache (normal cache can be cleared, but not dalvik) and data but nothing happens when I try to do it (It justs stays at formatting data forever when I do a full wipe). I've also tried flashing the same firmware and reinstalling the same rom again. I had an old backup of a earlier version of the rom, which I restored to but then I only get the boot screen to load for 2-3 seconds and then it freezes.
What should I do now?
Solved: Read my latest post.
Flash from scratch with Odin. No other choice.
Misledz said:
Flash from scratch with Odin. No other choice.
Click to expand...
Click to collapse
Alright, what files should I flash? Should I get a hold of a original firmware? Thanks for answering btw!
Ah you're welcome
Just get it off samfirmware.com, get HC 3.2 (Don't go for 3.1 as it is rubbish), Get the european firmware as it is the same and the most stable build (Also the first release for most new firmwares, if ICS were to come out, EU would get the firmware first)
GL and feel free to ask what you lack
Flashing guide's are pretty much simple.
Flash the unextracted file (must be in md5 extension) in PDA slot in odin in download mode and voila.
Ah la fresh tablet minion
Misledz said:
Ah you're welcome
Just get it off samfirmware.com, get HC 3.2 (Don't go for 3.1 as it is rubbish), Get the european firmware as it is the same and the most stable build (Also the first release for most new firmwares, if ICS were to come out, EU would get the firmware first)
GL and feel free to ask what you lack
Flashing guide's are pretty much simple.
Flash the unextracted file (must be in md5 extension) in PDA slot in odin in download mode and voila.
Ah la fresh tablet minion
Click to expand...
Click to collapse
I downloaded a 3.2 firmware from samfirmware.com, more specific:
"P7500XWLB1 3.2 2012 February P7500NSELA1 Sweden (Telia)"
It was zipped, i unzipped it and it was one .md5 file and one .dll file. I flashed the .md5 file with Odin in PDA. Odin tells me it is successful, and then the tab shows some scripts saying everything is succesful and then it reboots into the Samsung Galaxy Tab 10.1 text. After that I get a text saying "Manual mode, updating application..." for a while until it reboots into the same procedure again.
Atm I'm downloading another firmware just to be sure, I'll post when I've tried that one aswell. (It's named7500XWLB1 3.2 2012 February P7500OXXLB1 Nordic countries)
Really appreciate your help
Edit: Tried the other firmware without any success.
But have you been able to boot into the tablet properly after flashing? Don't worry about the dll, I don't really know what it's for, actually no one know's since Samsung hasn't even told us what it's used for, and phone's don't read dll's
That manual mode updating is the stock recovery building the CSC and everything (Regional settings)
Which firmware didn't work? You can only use 7500 firmware on a 7500 And don't forget to flash a CWM recovery, just might save your life
Misledz said:
But have you been able to boot into the tablet properly after flashing? Don't worry about the dll, I don't really know what it's for, actually no one know's since Samsung hasn't even told us what it's used for, and phone's don't read dll's
That manual mode updating is the stock recovery building the CSC and everything (Regional settings)
Which firmware didn't work? You can only use 7500 firmware on a 7500 And don't forget to flash a CWM recovery, just might save your life
Click to expand...
Click to collapse
I flashed P7500XWLB1 3.2 2012 February P7500OXXLB1 Nordic countries, and booted it but nothing happened. So I flashed a CWM recovery, and then it boots into Samsungs original-boot animation and then a text says Samsung. And then after a while it reboots again.
I'm at a loss right now, should I try to flash in a different order or flash with the device booting in between?
Ah, you ended up in a bootloop. Sometimes you may need to flash that firmware, then factory reset in recovery to get it to work. Depends if you had something in your previous ROM that conflicts. Or you can save the problem's and flash with a pit file. The overcome thread has a wonderful guide on that
rackadoosing said:
I flashed P7500XWLB1 3.2 2012 February P7500OXXLB1 Nordic countries, and booted it but nothing happened. So I flashed a CWM recovery, and then it boots into Samsungs original-boot animation and then a text says Samsung. And then after a while it reboots again.
I'm at a loss right now, should I try to flash in a different order or flash with the device booting in between?
Click to expand...
Click to collapse
You can try the method described here;
http://forum.xda-developers.com/showpost.php?p=22964943&postcount=4
It will get you back totally to stock, and then you can re-root and reflash.
Hopefully that helps (should fix most problems).
Br,
/primpa
Thanks alot guys!! I followed the "Re-“Stocking” Yer System…"-guide at the bottom of the page you linked, and the tab is now booting correctly. You're my life savers! Thanks again
rackadoosing said:
Thanks alot guys!! I followed the "Re-“Stocking” Yer System…"-guide at the bottom of the page you linked, and the tab is now booting correctly. You're my life savers! Thanks again
Click to expand...
Click to collapse
That method has yet to fail me.
Used to go around suggesting it everywhere but others have used it with success and are stepping in when needed.
Sent from my GT-P7510 using XDA Premium HD app
Hey Guys,
I'm sorry if I'm noobing it up here but I couldn't find a similar thread. I'm running a GT-i9300 (intl)
I just rooted my device yesterday and for the first time I flashed Cyanogenmod 10 on Odin, I followed the instructions as said. Everything flashed perfectly according to Odin.
Here were the instructions:
Noob-proof edition through ODIN:
- Download this : codeworkx.de/download/cyanoge... (have to cut URL)
- Reboot your phone in download mode
- Put the previously downloaded file as PDA
- Don't tick repartition
- Make sure repartition isn't ticked
- Flash it
Unfortunately, when I rebooted it gave me the cyanogenmod boot loop where this ring is circling leaving a trail and it just has cyanogenmod written in the middle for the past 10 minutes.
I am hoping to god I didn't hard brick my phone, I want to know what I did wrong and how do I fix this in the future?
Please help, thank you!
Go into recovery (Power, Home and Vol up for 5-10 seconds) and wipe cache/dalvik cache.
Reboot,
It's not flash for cwm? Otherwise I flashnul in Odin stock rom again and repeated the procedure, see thread.
MattHamed1 said:
Hey Guys,
I'm sorry if I'm noobing it up here but I couldn't find a similar thread. I'm running a GT-i9300 (intl)
I just rooted my device yesterday and for the first time I flashed Cyanogenmod 10 on Odin, I followed the instructions as said. Everything flashed perfectly according to Odin.
Here were the instructions:
Noob-proof edition through ODIN:
- Download this : codeworkx.de/download/cyanoge... (have to cut URL)
- Reboot your phone in download mode
- Put the previously downloaded file as PDA
- Don't tick repartition
- Make sure repartition isn't ticked
- Flash it
Unfortunately, when I rebooted it gave me the cyanogenmod boot loop where this ring is circling leaving a trail and it just has cyanogenmod written in the middle for the past 10 minutes.
I am hoping to god I didn't hard brick my phone, I want to know what I did wrong and how do I fix this in the future?
Please help, thank you!
Click to expand...
Click to collapse
Calm down, you're making it worse by panicing!
You didn't brick your phone
I'll tell you what you did, you flashed a kernel (w. recovery) via Odin. That's good.
You downloaded a zip for CM and flashed it, also very good.
But you forgot to delete cache/ reset device to the factory settings
Boot back into recovery and wipe data, that should work
Hope I could help!
familyguy59 said:
I'll tell you what you did, you flashed a kernel (w. recovery) via Odin.
Click to expand...
Click to collapse
Wrong. Cf-root does not contain a kernel.
Sent from my GT-I9300 using xda premium
My god,
You guys are lifesavers! Thanks so much for helping out the "NOOB" I don't want to make a new thread in regards to this but perhaps someone can lead me in the right direction?
I am going back to the stock ics 4.0.4 firmware w/ touchwiz and I'm just wondering when I do that is there anything else I need to do to "UNVOID" my warranty? I have a 1 year manufacturer from samsung and I have a 1 year by ensquared.com (They don't care if you brick it, they can fix it) but just incase I go with samsung how can I make it look "legit" again, and can I get stock updates from my carrier when they come again or will I have to from now on update by finding the firmware online
Sgs3 flash
Hello, I'am a "Noob" as well.
I would like to jump in on this forum with question on flashing and rooting the SGS3. I am currently working with one that is on the sprint network and would like to flash it to the Verizon prepaid Network. I have been searching since about 12:30 CST. I have downloaded ODIN 3.o.4 and I9300XXBLH1_I9300.......zip file ( I think this is only for unrooting.)
My Questions are if someone could either prepare me or route me to. Where I can get a step by step tutorial ,for beginners, on how to :
_ROOT ( If this is necessary to do before flashing)the SGS3 on 4.0.4
and
--FLASHing SGS3 Sprint to Verizon PP
I really would appreciate all the help I can get I have been watching tutorials and reading forums all afternoon but know one wants to jump right out and say Here is how to flash the sprint SGS3 to Verizon PP Lots of nice stuff on here and youtube on how to root and unroot. but my main concern is how to flash the network. iam looking for something like::
STEP 1...
STEP2..
ETC..
Here is my email [email protected] or I would except insight right form here .
I'm in a bit of a tight situation over here. My mom's phone was having issues, so she wanted me to fix it before I left to visit my grandparents. I found a stock ROM for the phone (GT-i9100 International) and flashed it, but the phone always got stuck on the "Samsung Galaxy SII GT-I9100" boot screen (occasionally it would show the "O2" screen, as it was a ROM for Ireland). I tried a different ROM (can't remember what country it was), and I'm still stuck with the same problem. This time no O2 screen though. I've downloaded my ROMs through sammobile.com and I'm using ODIN v1.83.
The label under the battery reads:
Model: GT-I9100
SSN: -I9100GSMH
What ROM should I use and where can I get it? I found this thread with a link to the ROM for the international version, but Hotfile has been shut down, so I can't download it.
Sorry if I could've found the answer with a few more hours of searching, but I've got less than 24 hours to find a fix and I was hoping that someone else could help me. Thanks a lot!
EDIT: I'm in the U.S., if that matters.
Try AndroidFirmwares.net or Samsung-Updates.com. If it were me in that situation (I.E not my phone), I'd be putting whatever the latest firmware is for the carrier/country.
Any region?
MistahBungle said:
Try AndroidFirmwares.net or Samsung-Updates.com. If it were me in that situation (I.E not my phone), I'd be putting whatever the latest firmware is for the carrier/country.
Click to expand...
Click to collapse
Should any region work to get the phone up and running? I just need to get it back up so that I can root it and flash CM10. Thanks.
Yep absolutely. If your end result is to root the phone & put a custom rom on, use any stock rom you can get your hands on. Though I'd be avoiding 4.0.4, anything other than that should be fine.
MistahBungle said:
Yep absolutely. If your end result is to root the phone & put a custom rom on, use any stock rom you can get your hands on. Though I'd be avoiding 4.0.4, anything other than that should be fine.
Click to expand...
Click to collapse
Is 4.1.2 OK, or should I go for 4.0.3 or below?
Doesn't matter, take your pick.
More info on problem
I tried installing two other ROMs (from androidfirmwares.net), one 4.1.2 and one 2.3.6. The 4.1.2 didn't get me anywhere, but after I flashed 2.3.6 the phone said the assert check failed. GT-i9100 is on the list of what it checked for. (I've never had any luck with the assert checks on any of my Samsung phones: GS Captivate, GSII Skyrocket, or AT&T GSIII. I've always had to remove the check in my update script.) I attached a picture.
EDIT: Since the attachment doesn't seem to be working, here's a Dropbox link.
Pic won't load for me, but it mentions 'recovery error', what exactly are you doing/what's the problem ?
MistahBungle said:
Pic won't load for me, but it mentions 'recovery error', what exactly are you doing/what's the problem ?
Click to expand...
Click to collapse
My process:
Open ODIN v3.09
Plug in the phone, already in download mode.
Click the AP button and load my .tar.md5.
Click Start.
Wait for it to finish, leaving the phone untouched on the table.
I just tried another USB cable, but to no avail. I've also tried unplugging the phone right after it reboots and ODIN says "PASS!", but no luck there either. I just tried another ROM that just finished downloading and it's giving me a similar getprop() error. At the bottom of the output in red it says:
E:Error in /cache/recovery/sec_csc.zip
(Status 7)
Installation aborted.
I don't think there's any way for me to edit the update script, as the tar contains a bunch of filesystem images. Even if it was easy to edit it would ruin the checksum verification.
Check out the picture on Dropbox here.
What are you trying to do in Android recovery ? Given what your stated aim is - get a stock rom on the phone, re-root it, put custom rom on, you shouldn't be using Android (I.E stock) recovery at any stage.
The process should be:-
*Flash stock rom with Odin in download mode (I.E phone off - home/vol down/power, not home/vol up/power)
*Root phone with whatever method
*Flash custom rom with CWRecovery, which you'll get once you root the phone
So....You need to go step by step. Start with flashing the stock rom with Odin, and try to boot the phone normally/make sure that was successful before doing the next two steps. Look for Hopper8's 'Odin troubleshooting' guide if you're having trouble getting a successful Odin flash.
Once you've done that, root the phone & make sure you have CWRecovery working, then flash the custom rom.
The phone boots to the recovery screen after it finishes flashing with ODIN. I put it into download mode, run ODIN, and then it that error screen comes up on the next reboot.
Try flashing the three part firmware linked to in Hopper's thread first (this will wipe the phone). I can't help but think we're missing some info re: what's been done to the phone previously here if the phone is booting into recovery mode after being Odin flashed. It shouldn't do that. After an Odin flash/pass the phone should boot normally, assuming it's not a case of the NAND being corrupted (it probably wouldn't boot into recovery if that was the case/you'd be left with constant bootloop)
I know you've mentioned what's on the sticker on the phone chassis under the battery but are you absolutely 100% sure it's an I9100 ?
MistahBungle said:
I know you've mentioned what's on the sticker on the phone chassis under the battery but are you absolutely 100% sure it's an I9100 ?
Click to expand...
Click to collapse
At the top of the download mode screen it says "PRODUCT NAME: GT-i9100". I don't know any other way to tell besides this and the sticker on the back. There are no carrier markings anywhere, and this phone was purchased because it had an FM radio, which only the international version had.
And assuming by "Hopper's thread" you mean this one, I can't because the files are no longer available.
In that case, you're stuck with the other suggestions to try in his thread & continuing to flash stock roms until you get a properly successful flash I.E phone boots/works normally. There might be something really obvious here being missed, but because we're not there with you/don't have the phone in front of us it might be difficult to work out.
It's working!
Yay, I got it to work! I flashed a custom kernel (jeboo), which allowed me to get into CWM. From there I sideloaded CM10 and now it's up and running! Only I still have a problem with internal storage... (That was the problem I was trying to fix originally.) Would the next thing to try to fix that be flashing a PIT file? If so, any tips for doing that?
I'm going to put off trying to fix that problem and do it when I get back. For now it works as a phone, and that's what's most important to her anyway. Thanks for your help MistahBungle.
Solved!
For anyone else who comes across this thread, I was able to solve my problem permanently by flashing a new PIT file. I found the correct PIT files for the GT-i9100 in this XDA thread. It seemed my partitions had become messed up long ago, as the phone had been showing a 2GB /data partition and only a 2GB internal SD card partition (which should've been closer to 12GB) for some time.
I choose a 4GB data partition (since I was running low on /data space last time). Oddly enough, booting the stock ROM after flashing the PIT only showed a 2GB data partition. Once I flashed CM10 it showed as 4GB though.
For starters (so there isnt misunderstandings )
1) I'm complete noob who's successfully rooted few times with root/custom ROMs, but I'd be very grateful if you can still break down explanations to their simplest (I usually use the site http://galaxys4root.com/ to help me)
2) My device is Samsung Galaxy S4 (Verizon), SCH-i545, Android Jelly Bean 4.2.2. Unfortunately, I'm not even sure what build I have since I have no clue where to find it, but if someone can direct me, I'd be glad post it
3) I originally rooted my phone according to the steps in the link http://forum.xda-developers.com/showthread.php?t=2380325 and it worked fine
I did a factory reset on my phone after failing to "move my downloaded apps to my external sd card with Root Explorer (a root app)". Apps couldn't open and home page lagged/glitched. The reset was successful, but I still had SuperSU from root, and also wanted to update to 4.3 to rid the update message that kept popping up. I used Odin, but that's when trouble started. Every Odin tutorial I went for unrooting S4, said that the first box to the left was supposed to be yellow when the phone connected, but mines stayed blue (see image attachment)
I redownloaded Odin/SAmsung USB Drivers thinking they were out of date, but it didn't do anything. When I tried going into Android Sys Recovery Mode (press volume up/home/power button then release power button) It told me "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I tried downloading Kies and updating, but it didnt even detect my phone. I've tried flashing every stock firmware I've found, but nothing works.
Thing is, I dont even know if I'm soft or hard bricked (or just plain noob ) but I can go into Odin mode just fine, I just have to take out the battery every time and wait a few minutes. However, I cannot go into the sys recovery mode, since all I get is the Kies message. Also, when I just normally turn on my phone, it automatically goes straight to sys recovery.
If anyone can help me resolve this problem, I will be very much appreciated. Thanks for reading the long post! XD
nyankat said:
For starters (so there isnt misunderstandings )
1) I'm complete noob who's successfully rooted few times with root/custom ROMs, but I'd be very grateful if you can still break down explanations to their simplest (I usually use the site http://galaxys4root.com/ to help me)
2) My device is Samsung Galaxy S4 (Verizon), SCH-i545, Android Jelly Bean 4.2.2. Unfortunately, I'm not even sure what build I have since I have no clue where to find it, but if someone can direct me, I'd be glad post it
3) I originally rooted my phone according to the steps in the link http://forum.xda-developers.com/showthread.php?t=2380325 and it worked fine
I did a factory reset on my phone after failing to "move my downloaded apps to my external sd card with Root Explorer (a root app)". Apps couldn't open and home page lagged/glitched. The reset was successful, but I still had SuperSU from root, and also wanted to update to 4.3 to rid the update message that kept popping up. I used Odin, but that's when trouble started. Every Odin tutorial I went for unrooting S4, said that the first box to the left was supposed to be yellow when the phone connected, but mines stayed blue (see image attachment)
I redownloaded Odin/SAmsung USB Drivers thinking they were out of date, but it didn't do anything. When I tried going into Android Sys Recovery Mode (press volume up/home/power button then release power button) It told me "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I tried downloading Kies and updating, but it didnt even detect my phone. I've tried flashing every stock firmware I've found, but nothing works.
Thing is, I dont even know if I'm soft or hard bricked (or just plain noob ) but I can go into Odin mode just fine, I just have to take out the battery every time and wait a few minutes. However, I cannot go into the sys recovery mode, since all I get is the Kies message. Also, when I just normally turn on my phone, it automatically goes straight to sys recovery.
If anyone can help me resolve this problem, I will be very much appreciated. Thanks for reading the long post! XD
Click to expand...
Click to collapse
Looks like you connected in Odin. Flash you stock recovery .tar using PDA ONLY.
Use this link to download the factory image fr the build that your on. You can find out what build your on by going to settings->about phone. Unless you have flashed a modem/radio your current build will be listed under "baseband" it sounds like your on me7 but double check before you download and flash. Fell free to post any other questions. I'll keep an eye out in case you need more help. http://forum.xda-developers.com/showthread.php?t=2301259
[GUIDE] No-Wipe Factory Images (Restore from any soft-brick without wiping data)
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Shaftamle said:
Looks like you connected in Odin. Flash you stock recovery .tar using PDA ONLY.
Use this link to download the factory image fr the build that your on. You can find out what build your on by going to settings->about phone. Unless you have flashed a modem/radio your current build will be listed under "baseband" it sounds like your on me7 but double check before you download and flash. Fell free to post any other questions. I'll keep an eye out in case you need more help. http://forum.xda-developers.com/showthread.php?t=2301259
[GUIDE] No-Wipe Factory Images (Restore from any soft-brick without wiping data)
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Click to expand...
Click to collapse
Oh wow......turns out that I just didn't flash the right .tar file and didn't use PDA. Thanks for helping out! And to think I got so worked up over it....
nyankat said:
Oh wow......turns out that I just didn't flash the right .tar file and didn't use PDA. Thanks for helping out! And to think I got so worked up over it....
Click to expand...
Click to collapse
No problem. Always be extra careful when using Odin. Sounds like you might have got lucky. That's one of the easiest ways to hard brick is flashing wrong file or from non pda., from what I've read.
Glad I could help though.:beer:
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Hi, Followed all the amazing walk through like normal. Not sure what 4.x.x.x I was on, never really check to be honest.
First time this phone has been rooted. (I rooted because I was having problems with the phone, last phone I rooted and was able to fix the problems).
1. Used the download file and instructions by qking...
2. Same with TWRP
3. It rebooted, somehow it screwed up MicroSD card, would no longer read it. Then it rebooted again..
4. Stuck on Sprint screen for last couple hours.
I tried to get back into TWRP and do a factory clean and reset, when it rebooted it, sat at the Sprint Screen for hour or so. Then I searched and a few other people just had to use odin and redo it again and worked fine.
So I did odin again relfashed the file and at reboot it is stuck on Yellow Sprint screen..
That is where im stuck at now is Sprint Screen, thanks in advance!
Swaintan said:
Hi, Followed all the amazing walk through like normal. Not sure what 4.x.x.x I was on, never really check to be honest.
First time this phone has been rooted. (I rooted because I was having problems with the phone, last phone I rooted and was able to fix the problems).
1. Used the download file and instructions by qking...
2. Same with TWRP
3. It rebooted, somehow it screwed up MicroSD card, would no longer read it. Then it rebooted again..
4. Stuck on Sprint screen for last couple hours.
I tried to get back into TWRP and do a factory clean and reset, when it rebooted it, sat at the Sprint Screen for hour or so. Then I searched and a few other people just had to use odin and redo it again and worked fine.
So I did odin again relfashed the file and at reboot it is stuck on Yellow Sprint screen..
That is where im stuck at now is Sprint Screen, thanks in advance!
Click to expand...
Click to collapse
OK first pull battery, now reinsert bat and hold the power, home, and volume down buttons at the same time, then press the volume up button to get into download mode. Don't bother trying to get back to TWRP your past that. While in download mode check the status of the device. Is it Official or custom? Let me know the status.
Now lets flash a fresh stock OS with Odin, to save me a lot of typing go here. http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440
Download the version of odin you want both work fine. Download the version of the KK OS you want to flash, I like NK4. You can follow the steps on my thread listed above to flash an OS with one EXCEPTION!!!
EVEN IF THE DEVICE BOOTS UP AFTER YOU FLASH THE OS THE FIRST TIME, ONCE YOU GET PAST THE SET UP FOR FIRST TIME USE WHICH ( STARTS ABOUT 3-5 MIN AFTER THE SAMSUNG LOGO SCREEN BY THE WAY BE PATIENT ) POWER DOWN THE DEVICE GET BACK INTO DOWNLOAD MODE AND ODIN FLASH THE OS AGAIN !!!
This should get you back to bone stock OS. Once it boots up and get passed first time use set up. Now your ready to root, the way I root is first grab a copy of SuperSU ( latest version is fine its on my thread ) with your PC copy and paste it on the SD card. Next power down completely and boot into download mode, Odin flash a custom recovery TWRP is a good one. The device should boot up after the recovery is flashed on its own, don't try boot up the device yourself to soon, give the recovery a chance to flash completely. Now completely power down the device, hold the power, home, and volume up buttons and boot into recovery. Then flash the SuperSu zip then reboot device you should be off and running . . . .
Here is the first part, im working on the rest now.
Current Binary: Custom
System Status: Custom
Swaintan said:
Here is the first part, im working on the rest now.
Current Binary: Custom
System Status: Custom
Click to expand...
Click to collapse
Ok cool, remember that everything has to fit. Meaning depending on what OS you run i.e. KitKat, Lollipop etc everything should updated to match.
Example : If you run KK NC5 OS then Philz CWM recovery 6.9.12 and later works. TWRP 2.8.3.0 or later works.
If you run Lollipop OC5 then Philz CWM recovery 6.48.4 works. ( link is broken I have a copy if you need it ) TWRP 2.8.6.0 or later works.
As for SuperSU you could go all the way back to v 1.94 and still root the binarys will update automatically. The latest (stable ) version is 2.46 from chainfire.
TY Ill keep you updated, file is taking a long time to download, still sitting at 1 hr to finish up download. Once its downloaded ill continue with the rest of the steps and post updates.
Not been very happy with sprint lately, latest update to my Wifes note 2 screwed her phone way up, only way to fix it was root it. So as soon as I saw mine doing the same thing I hurried to root it, but looks like it was to late. Hopefully this fixes it all, I really do appreciate it.
Swaintan said:
Hi, Followed all the amazing walk through like normal. Not sure what 4.x.x.x I was on, never really check to be honest.
First time this phone has been rooted. (I rooted because I was having problems with the phone, last phone I rooted and was able to fix the problems).
1. Used the download file and instructions by qking...
2. Same with TWRP
3. It rebooted, somehow it screwed up MicroSD card, would no longer read it. Then it rebooted again..
4. Stuck on Sprint screen for last couple hours.
I tried to get back into TWRP and do a factory clean and reset, when it rebooted it, sat at the Sprint Screen for hour or so. Then I searched and a few other people just had to use odin and redo it again and worked fine.
So I did odin again relfashed the file and at reboot it is stuck on Yellow Sprint screen..
That is where im stuck at now is Sprint Screen, thanks in advance!
Click to expand...
Click to collapse
Forgot to say why you flash twice, when the device is corrupted or bootloops. 9 times out of 10 its because something was left behind from the previous OS or something didn't flash in from the new OS. Flashing twice I found through ( trial and error pulling my hair out ) solves this problem.
When I get done with a flashaholic binge and need to get back to a daily user, I always flash back to Stock OS twice, install recovery, and root. Then install a custom OS if want run one this way you always start clean. This way if something doesn't work or stops working you right where to start looking for the problem.
---------- Post added at 07:03 AM ---------- Previous post was at 06:55 AM ----------
Swaintan said:
TY Ill keep you updated, file is taking a long time to download, still sitting at 1 hr to finish up download. Once its downloaded ill continue with the rest of the steps and post updates.
Not been very happy with sprint lately, latest update to my Wifes note 2 screwed her phone way up, only way to fix it was root it. So as soon as I saw mine doing the same thing I hurried to root it, but looks like it was to late. Hopefully this fixes it all, I really do appreciate it.
Click to expand...
Click to collapse
Ya I agree rooting stops the updates. Usually I read up on the update first to see what problems it may be causing. Then decide to unroot and take it, I still run my 4.4.4 NK4 deoexed no knox debloated OS just not a fan of Lollipop to many problems with it, besides there's no themes for it.
You are awesome! Followed your directions and links inside your siggy. So this is where I sit;
I installed (from your siggy)
-SPRINT KK 4.4.4 N900PVPUDNK4
Stock rom : DEODEXED, NO KNOX, and DEBLOATED ( #2 )
Busybox / Zipaligned
Rooted / Superuser
No Knox ( Disabled / Removed )
Volume Mod / 300+ Fonts ( Thanks DevilDog512 )
Custom Kernel ****
-SU 2.46 (it auto updated when I installed)
-TWRP Manager 8.0.1.8
-Recovery TWRP 2.8.7.0
Now I have to start redoing apps etc.. THANK YOU SO MUCH!!!
Edit: Add: Now should be safe to install Wicked Green Theme and get all family n friends to send contact info... that part will be harder then what you had me do, TY again!
Swaintan said:
You are awesome! Followed your directions and links inside your siggy. So this is where I sit;
I installed (from your siggy)
-SPRINT KK 4.4.4 N900PVPUDNK4
Stock rom : DEODEXED, NO KNOX, and DEBLOATED ( #2 )
Busybox / Zipaligned
Rooted / Superuser
No Knox ( Disabled / Removed )
Volume Mod / 300+ Fonts ( Thanks DevilDog512 )
Custom Kernel ****
-SU 2.46 (it auto updated when I installed)
-TWRP Manager 8.0.1.8
-Recovery TWRP 2.8.7.0
Now I have to start redoing apps etc.. THANK YOU SO MUCH!!!
Edit: Add: Now should be safe to install Wicked Green Theme and get all family n friends to send contact info... that part will be harder then what you had me do, TY again!
Click to expand...
Click to collapse
Cool, what stock version KK OS did you flash twice before installed my deodexed 4.4.4 NK4 ?
Not sure, i know i followed each one, so it took me to a site where I had to download it specifically for my phone. My dl history says file name was N900PVPUDNK4_SPR it was the bone stock md5, did that one twice.
Swaintan said:
Not sure, i know i followed each one, so it took me to a site where I had to download it specifically for my phone. My dl history says file name was N900PVPUDNK4_SPR it was the bone stock md5, did that one twice.
Click to expand...
Click to collapse
Cool, that will work fine.