I have a SM-N900P, rooted stock ROM, CWM recovery, and the hotspot mod. All came from galaxynote3.com if that helps. I was wondering how I would go about updating my phone to 4.4.2. Obviously when I try to update it tells me it can't because of the root. I tried unrooting my phone by flashing the stock firmware but it failed every time, through every USB port. I tried upgrading my phone through Kies but I can't find my S/N.
lilkounchry said:
I have a SM-N900P, rooted stock ROM, CWM recovery, and the hotspot mod. All came from galaxynote3.com if that helps. I was wondering how I would go about updating my phone to 4.4.2. Obviously when I try to update it tells me it can't because of the root. I tried unrooting my phone by flashing the stock firmware but it failed every time, through every USB port. I tried upgrading my phone through Kies but I can't find my S/N.
Click to expand...
Click to collapse
Post #5 will get you all hooked up! DO NOT try to revert back to jellybean once you have flashed NAB through Odin.
http://forum.xda-developers.com/showthread.php?t=2656802
Related
I have the AT&T SGS2. I had installed a few custom software a few months ago, but then I installed a stock 2.3.4 for the AT&T phone. The custom binary count is 1 on the recovery screen.
To upgrade to the official ICS from AT&T, I installed the latest KIES. It successfully detects the firmware update for the device. KIES starts installing and everything goes fine until almost very end. At 91%, installation fails giving the error message something like "Unexpected error. Firmware upgrade encountered an issue. please select recovery mode in kies & try again". I tried several times and same thing happens again. I also tried downloading the stock ICS and install it via ODIN, but same thing happened. It failed at the very end.
What could be happening here? Any advice? Can it be anything to do with the custom binary count? Thanks in advance...
Not sure what might be intefering with kies or Odin. Where did you get the tar that you flashed that failed?
You might try again, with the UCLE5 Stock ICS plus Root tar from the Development forum.
I'm desperately hoping that someone, somewhere can provide a stock firmware for the Bell SGH-I527M that includes knox. Maybe someone from sammobile is reading this and can post it there. I took the OTA update a week ago, then rooted the phone and flashed CWM recovery on it, no problem at all. Everything was running fine.
Yesterday, I thought I'd give the unofficial CM11 ROM a go, so I took a backup and tried flashing CM11 from CWM - failed. So I thought, "No problem, I'll just restore my backup I made ten minutes ago." That, too, failed. I had nothing to go back to since I was trying to do a super-clean flash of CM11 - wipe data/factory reset, format data, format sdcard, all the steps that I've taken a million times flashing different ROMs on different Samsung phones. So I effectively had no OS on the phone, just recovery.
Went to Sammobile and downloaded the only stock firmware they have available for this device for this carrier. Flashed through Odin and on reboot, got the "secure fail kernel - image size too large" error message. Also tried the emergency firmware recovery through Kies and got the same thing.
So basically, I'm completely stuck. The only thing I can get to boot up is download mode. Does anyone know if there is a different firmware I can flash through Odin to get this device up and running again? I'm given to understand that this has something to do with knox security. That since I took the OTA last week, it updated knox security, then when I flashed the stock firmware from sammobile, this is actually an older firmware that does not include knox. I'm hoping that someone has access to the newest stock firmware for this device for Bell with knox that I can flash through Odin to get back up and running.
Any help would be greatly appreciated.
Thanks in advance,
-GB
GladdBag said:
I'm desperately hoping that someone, somewhere can provide a stock firmware for the Bell SGH-I527M that includes knox. Maybe someone from sammobile is reading this and can post it there. I took the OTA update a week ago, then rooted the phone and flashed CWM recovery on it, no problem at all. Everything was running fine.
Yesterday, I thought I'd give the unofficial CM11 ROM a go, so I took a backup and tried flashing CM11 from CWM - failed. So I thought, "No problem, I'll just restore my backup I made ten minutes ago." That, too, failed. I had nothing to go back to since I was trying to do a super-clean flash of CM11 - wipe data/factory reset, format data, format sdcard, all the steps that I've taken a million times flashing different ROMs on different Samsung phones. So I effectively had no OS on the phone, just recovery.
Went to Sammobile and downloaded the only stock firmware they have available for this device for this carrier. Flashed through Odin and on reboot, got the "secure fail kernel - image size too large" error message. Also tried the emergency firmware recovery through Kies and got the same thing.
So basically, I'm completely stuck. The only thing I can get to boot up is download mode. Does anyone know if there is a different firmware I can flash through Odin to get this device up and running again? I'm given to understand that this has something to do with knox security. That since I took the OTA last week, it updated knox security, then when I flashed the stock firmware from sammobile, this is actually an older firmware that does not include knox. I'm hoping that someone has access to the newest stock firmware for this device for Bell with knox that I can flash through Odin to get back up and running.
Any help would be greatly appreciated.
Thanks in advance,
-GB
Click to expand...
Click to collapse
If someone with this new update and root could dump some images i could make an odin tar for yall.
GladdBag said:
I'm desperately hoping that someone, somewhere can provide a stock firmware for the Bell SGH-I527M that includes knox. Maybe someone from sammobile is reading this and can post it there. I took the OTA update a week ago, then rooted the phone and flashed CWM recovery on it, no problem at all. Everything was running fine.
Yesterday, I thought I'd give the unofficial CM11 ROM a go, so I took a backup and tried flashing CM11 from CWM - failed. So I thought, "No problem, I'll just restore my backup I made ten minutes ago." That, too, failed. I had nothing to go back to since I was trying to do a super-clean flash of CM11 - wipe data/factory reset, format data, format sdcard, all the steps that I've taken a million times flashing different ROMs on different Samsung phones. So I effectively had no OS on the phone, just recovery.
Went to Sammobile and downloaded the only stock firmware they have available for this device for this carrier. Flashed through Odin and on reboot, got the "secure fail kernel - image size too large" error message. Also tried the emergency firmware recovery through Kies and got the same thing.
So basically, I'm completely stuck. The only thing I can get to boot up is download mode. Does anyone know if there is a different firmware I can flash through Odin to get this device up and running again? I'm given to understand that this has something to do with knox security. That since I took the OTA last week, it updated knox security, then when I flashed the stock firmware from sammobile, this is actually an older firmware that does not include knox. I'm hoping that someone has access to the newest stock firmware for this device for Bell with knox that I can flash through Odin to get back up and running.
Any help would be greatly appreciated.
Thanks in advance,
-GB
Click to expand...
Click to collapse
im in the same boat lol....any luck bro?
Nubsta said:
im in the same boat lol....any luck bro?
Click to expand...
Click to collapse
See this thread:
http://forum.xda-developers.com/showthread.php?t=2461203
I am a bit of a noob but I have rooted my sprint note 3 which came out successful. I have rooted my galaxy s3 before in the past and flashed many roms without any issues.
Once I rooted my note 3 I ran the stock rom for a week and then decided to kick it up a notch and flashed the bonsai rom, which worked fine until i discovered the camera didn't work. Before I flashed the bonsai rom, I did a backup of the stock rom via cwm. Once I figured out the camera didn't work with the bonsai rom, I reset and wiped the data for my phone and tried to restore the stock rom which i figured it was a boo boo because I got stuck in a bootloop so I reflashed the bonsai rom back on my phone until I got back home to my pc. At that point, I decided to unroot and return the phone back to stock. I used odin and followed unrooting instructions to a tee and I had an official stock firmware, but odin failed and I think I may have soft bricked my phone. In a panic, I downloaded a "rooted stock" rom and flashed that...after a few bootloops, I updated my cwm recovery and superuser app...and my phone has been working fine every since (whew). I really want to unroot, then re-root and just run the stock rom without flashing any more custom roms, however I am afraid of bricking it again.
I have the stock official firmware N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.tar.md 5 which to my understanding is android 4.3. I do understand that 4.4 is out. I was wondering is it ok to flash the 4.3 using odin to return my phone back to stock?? I've been spooked ever since my soft brick encounter. Any info will be helpful. Btw, sorry for the long story. I figured I should give all the details. That would help me get to the bottom of it all
Thanks in Advance!
LadyDroid81 said:
I am a bit of a noob but I have rooted my sprint note 3 which came out successful. I have rooted my galaxy s3 before in the past and flashed many roms without any issues.
Once I rooted my note 3 I ran the stock rom for a week and then decided to kick it up a notch and flashed the bonsai rom, which worked fine until i discovered the camera didn't work. Before I flashed the bonsai rom, I did a backup of the stock rom via cwm. Once I figured out the camera didn't work with the bonsai rom, I reset and wiped the data for my phone and tried to restore the stock rom which i figured it was a boo boo because I got stuck in a bootloop so I reflashed the bonsai rom back on my phone until I got back home to my pc. At that point, I decided to unroot and return the phone back to stock. I used odin and followed unrooting instructions to a tee and I had an official stock firmware, but odin failed and I think I may have soft bricked my phone. In a panic, I downloaded a "rooted stock" rom and flashed that...after a few bootloops, I updated my cwm recovery and superuser app...and my phone has been working fine every since (whew). I really want to unroot, then re-root and just run the stock rom without flashing any more custom roms, however I am afraid of bricking it again.
I have the stock official firmware N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.tar.md 5 which to my understanding is android 4.3. I do understand that 4.4 is out. I was wondering is it ok to flash the 4.3 using odin to return my phone back to stock?? I've been spooked ever since my soft brick encounter. Any info will be helpful. Btw, sorry for the long story. I figured I should give all the details. That would help me get to the bottom of it all
Thanks in Advance!
Click to expand...
Click to collapse
Depends on what version you are running, but sounds like you are on mj4 still... http://forum.xda-developers.com/showthread.php?t=2657828 this one is mj4 (4.3), if you are on 4.4 you need to go to the Android development forum and use whatever version you are on, just look for rwilcos one click.
tonyevo52 said:
Depends on what version you are running, but sounds like you are on mj4 still... http://forum.xda-developers.com/showthread.php?t=2657828 this one is mj4 (4.3), if you are on 4.4 you need to go to the Android development forum and use whatever version you are on, just look for rwilcos one click.
Click to expand...
Click to collapse
Yes...I am still on 4.3.
LadyDroid81 said:
Yes...I am still on 4.3.
Click to expand...
Click to collapse
Follow the instructions from this thread and you will be fully unrooted http://forum.xda-developers.com/showthread.php?t=2657828:good:
Hey everybody,
First time poster here. So I have an AT&T Galaxy S4 I337 that I have been running Cyanogenmod on for quite a while now. Well, after getting bored and wanting to revert to the original firmware, I went through the process of a factory reset to stock through Odin. Everything went smoothly, all that's left is to update to 4.4.2 Kitkat and to root my phone once again. I went into settings and began the OTA update thinking it would install 4.4.2. After about 20 minutes of updating and downloading, my phone finally finished rebooting, but when I checked to see what version of android I was running, it was still 4.2.2. Kies also says that I'm running the latest firmware. Why won't my phone or Kies pick up the new Kitkat update? Does it have something to do with the fact that I flashed a custom ROM before? I could really use some help!
Thanks!
ViridianFlea said:
Hey everybody,
First time poster here. So I have an AT&T Galaxy S4 I337 that I have been running Cyanogenmod on for quite a while now. Well, after getting bored and wanting to revert to the original firmware, I went through the process of a factory reset to stock through Odin. Everything went smoothly, all that's left is to update to 4.4.2 Kitkat and to root my phone once again. I went into settings and began the OTA update thinking it would install 4.4.2. After about 20 minutes of updating and downloading, my phone finally finished rebooting, but when I checked to see what version of android I was running, it was still 4.2.2. Kies also says that I'm running the latest firmware. Why won't my phone or Kies pick up the new Kitkat update? Does it have something to do with the fact that I flashed a custom ROM before? I could really use some help!
Thanks!
Click to expand...
Click to collapse
You can't update directly from 4.2.2 to 4.4.2. You're missing out on a couple of updates in between. But, it doesn't look like you've read a head too much. You can't root 4.4.2 directly. The current method for rooting it involves downgrading back to 4.3, rooting, installing the Safestrap recovery, and using that to install a stock rooted rom. Since you are already on 4.2.2 and can use a custom recovery, it is recommended to install a stock or custom rom and the accompanying modem. Once you go past 4.3, there is no return due to the Knox bootloader deal.
I'm currently running a Verizon galaxy note 2 with jedi X20. I am rooted and have twrp 2.7 installed. Im currently trying to flash I605VRUEMJ9 So I can start installing 4.3 TW roms. however when I flash MJ9 in odin. everything runs fine until odin causes it to restart and it just puts me into recovery. every time so im guessing it never has a chance to finish. It still shows im running 4.1.2. Any ideas would be greatly appreciated.
Timb0king said:
I'm currently running a Verizon galaxy note 2 with jedi X20. I am rooted and have twrp 2.7 installed. Im currently trying to flash I605VRUEMJ9 So I can start installing 4.3 TW roms. however when I flash MJ9 in odin. everything runs fine until odin causes it to restart and it just puts me into recovery. every time so im guessing it never has a chance to finish. It still shows im running 4.1.2. Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
If you're not flashing the pit file with it, try that to see if it will work.
Edit: ... You probably know this, but don't flash the entire 4.3 stock MJ9 ROM or you'll permanently lock your bootloader. Just Odin flash the MJ9 firmware only.
If it keeps failing, you might consider ODIN'ing back to 4.1.2 stock VRAMC3, then running Casual again, then updating your recovery. That would at least give you a clean slate to start with... You might also try a different version of one of the latest recoveries. Hope you got it working.
Good luck!
mattnmag said:
If you're not flashing the pit file with it, try that to see if it will work.
Edit: ... You probably know this, but don't flash the entire 4.3 stock MJ9 ROM or you'll permanently lock your bootloader. Just Odin flash the MJ9 firmware only.
If it keeps failing, you might consider ODIN'ing back to 4.1.2 stock VRAMC3, then running Casual again, then updating your recovery. That would at least give you a clean slate to start with... You might also try a different version of one of the latest recoveries. Hope you got it working.
Good luck!
Click to expand...
Click to collapse
Just as an FYI I got it figured out. Turns put it was flashing mj9 and worked but i still had a 4.1.2 rom installed. all I did was use twrp to install meanbeans reborn and now my phone is running 4.3 mj9. Thanks for the help.