first...upgraded to kitkat 4.4.2 and....sd not working anymore, cant download anything, some apps say sd is required...and on computer i cant write to it either. And gps is crap....so any fixes?
i saw that upgrading to 4.4 fixes all of it but only at&t has it at the moment. What would happen if i installed at&t via odin on a sprinit phone and selected nand erase all option? and why cant u downgrade....with nand erase all, i mean i was not 4.4.2 and the way i upgraded was by installing the recovery rom that was 4.4.2
And I tried editing xml file was not able to open, I tried sd fix from store and a zip via twrp, sd still no work. Am on vision X stock rom, software cn5
Try a different sd ... Maybe you have a bad one ... folder Mount in store works I know ...
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
Try a different sd ... Maybe you have a bad one ... folder Mount in store works I know ...
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
not bad, just after update. I put sd in another phone and works. 8 read this is a kitkat problem
That actually worked said faulty and patch sucess. What about gps...it's working but it's not following along or saying turn
djhulk2 said:
That actually worked said faulty and patch sucess. What about gps...it's working but it's not following along or saying turn
Click to expand...
Click to collapse
Gps is working fine for me ...I would go back to complete stock using Odin and tar file ...mj4 if your on jelly bean or nab nc5 if you're on kit Kat and then check Gps .... Maybe a hardware problem with your phone ...Gps wasn't great on aosp but was fine on stock
Sent from my SM-N900P using Xparent BlueTapatalk 2
I did start with stock mc5, but it did not want to load it...would stay stuck on Samsung logo. So I rooted it and installed that rom and it loaded, but stock doesn't want to anymore
and everything worked before this kitkat update, and here is proof its 100% kitkat
gps problem: http://www.gottabemobile.com/2014/0...e-3-android-4-4-kitkat-release-5-key-details/
sd problem:http://www.androidpit.com/how-to-fix-android-4-4-2-kitkat-problems-galaxy-note-3
djhulk2 said:
I did start with stock mc5, but it did not want to load it...would stay stuck on Samsung logo. So I rooted it and installed that rom and it loaded, but stock doesn't want to anymore
and everything worked before this kitkat update, and here is proof its 100% kitkat
gps problem: http://www.gottabemobile.com/2014/0...e-3-android-4-4-kitkat-release-5-key-details/
sd problem:http://www.androidpit.com/how-to-fix-android-4-4-2-kitkat-problems-galaxy-note-3
Click to expand...
Click to collapse
It will stay on Samsung screen if you don't wipe right when installing a rom .... I always wipe data davlik cache and system .... If I am going to aosp of any kind ....I wipe internal and flash from external sd ...I always wipe internal going from aosp to touch wiz also .... There are to many file differences for me
Sent from my SM-N900P using Xparent BlueTapatalk 2
I did do those wipes but was still stuck. This flash was also via odin
djhulk2 said:
I did do those wipes but was still stuck. This flash was also via odin
Click to expand...
Click to collapse
After flashing in Odin if it passed sometimes you may have to boot into stock recovery and wipe .... If your trying to get it to say official in software for ota it may be necessary to remove sd card prior to flashing with Odin. ..
Sent from my SM-N900P using Xparent BlueTapatalk 2
It's interesting that u say u have no problems, the sd got fixed thanks ti that app mentioned above, but gps works but it does not giude u. The fix for all these problems are said to be in the upgrade 4.4 which only at&t has at the moment
djhulk2 said:
It's interesting that u say u have no problems, the sd got fixed thanks ti that app mentioned above, but gps works but it does not giude u. The fix for all these problems are said to be in the upgrade 4.4 which only at&t has at the moment
Click to expand...
Click to collapse
I use gps every day in Phoenix .... You milage may vary but it works. .. If it don't work for you that is why I would advise you go back to stock to try but if you just want to say no or don't work. ..I tried I have no reason to steer you wrong but oh well
Sent from my SM-N900P using Xparent BlueTapatalk 2
Thanks but, flashing stock is not the solution.
Bump
Related
I got my phone on MI5. I use CF root through odin and I installed TWRP through Odin as well. I played with a couple of ROMs, but wanted to try out MJ4 and some of the new ROMs out for that.
No matter what I try I cant get MJ4. I tried the baseband update from freeza, but that didn't take. I wiped and tried to install, what I thought was stock, a stock image. I even backed up my backups on internal storage and did a complete wipe and back to what I thought was stock
Now when I try to restore a twrp backup, I still end up at the default setup. This is very strange and never had any issues like this with previous phones.
The one thing I noticed about this forum vs previous forums I was in all the time, was lack of sticky threads on how to go completely stock etc
How do i get to stock MI5 so i can install MJ4?
drewbuntu said:
I got my phone on MI5. I use CF root through odin and I installed TWRP through Odin as well. I played with a couple of ROMs, but wanted to try out MJ4 and some of the new ROMs out for that.
No matter what I try I cant get MJ4. I tried the baseband update from freeza, but that didn't take. I wiped and tried to install, what I thought was stock, a stock image. I even backed up my backups on internal storage and did a complete wipe and back to what I thought was stock
Now when I try to restore a twrp backup, I still end up at the default setup. This is very strange and never had any issues like this with previous phones.
The one thing I noticed about this forum vs previous forums I was in all the time, was lack of sticky threads on how to go completely stock etc
How do i get to stock MI5 so i can install MJ4?
Click to expand...
Click to collapse
No need to go to stock mi5.. to get mj4 do this
1] odin the official mj4 file
Can be found at sammobile.com
2] root it via kingoapp.com
Sent from my SM-N900P using Xparent Purple Tapatalk 2
cherylbaker said:
No need to go to stock mi5.. to get mj4 do this
1] odin the official mj4 file
Can be found at sammobile.com
2] root it via kingoapp.com
Sent from my SM-N900P using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
I will try this AGAIN tonight. Re-downloading the Odin file now while at work.
Still a NO-GO
cherylbaker said:
No need to go to stock mi5.. to get mj4 do this
1] odin the official mj4 file
Can be found at sammobile.com
2] root it via kingoapp.com
Sent from my SM-N900P using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
Still a no go. In fact, after flashing that using Odin, my phone is still configured, apps and all. The process completed successfully according to Odin. It only upgraded my build number
I added some screenshots
drewbuntu said:
Still a no go. In fact, after flashing that using Odin, my phone is still configured, apps and all. The process completed successfully according to Odin. It only upgraded my build number
I added some screenshots
Click to expand...
Click to collapse
I would recommend reverting to stock and taking the OTA update if freeza's amazing MJ4 baseband/kernel didn't work for you.
...Or there is that full MJ4 stock .tar you could Odin... Make a titanium backup and TWRP backup (system, boot, data) first of course.
Kompster said:
I would recommend reverting to stock and taking the OTA update if freeza's amazing MJ4 baseband/kernel didn't work for you.
...Or there is that full MJ4 stock .tar you could Odin... Make a titanium backup and TWRP backup (system, boot, data) first of course.
Click to expand...
Click to collapse
where is the stock my tar file for odin? I can't find it and I'm having the same problem.
randyreed1971 said:
where is the stock my tar file for odin? I can't find it and I'm having the same problem.
Click to expand...
Click to collapse
File mirrored by @rpenrod23 here
Source.
Nope!
Kompster said:
File mirrored by @rpenrod23 here
Source.
Click to expand...
Click to collapse
I ran this again, using Odin on the source from here: https://docs.google.com/uc?id=0B-4vmAHRoMi-TGlrellrTi1SWXM&export=download
it was one of the links in your linked back post above. Everything is the same, still only build number incremented
Something is very wrong here.
EDIT: I tried all sorts of things, and no matter what now, I end up with build MJ4 and everything else points to MI5, even if i Odin MI5. I have even tried installing TWRP and wiping the entire thing, flashing MI5 and going for the OTA, but my build still says MJ5 and OTA updates say I am modified.
bump
Is there anyone that can help me?
No matter what I try, my baseband stays at MI5. Even after 3 full wipes and reinstall of stock MI5, the system will not run the auto update, says I am modified.
I have even installed TWRP, wiped system, data etc, installed MI5 stock, wiped 3 times, and then again using stock recovery.
drewbuntu said:
Is there anyone that can help me?
No matter what I try, my baseband stays at MI5. Even after 3 full wipes and reinstall of stock MI5, the system will not run the auto update, says I am modified.
I have even installed TWRP, wiped system, data etc, installed MI5 stock, wiped 3 times, and then again using stock recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2514434
Sent from Sprint Galaxy Note 3 using Tapatalk
insane209 said:
http://forum.xda-developers.com/showthread.php?t=2514434
Sent from Sprint Galaxy Note 3 using Tapatalk
Click to expand...
Click to collapse
Read and tried that method last week, still on MI5.
I'll give it another shot though. I got the backup and restore part down pat, so no harm to try.
drewbuntu said:
Read and tried that method last week, still on MI5.
I'll give it another shot though. I got the backup and restore part down pat, so no harm to try.
Click to expand...
Click to collapse
K
Sent from Sprint Galaxy Note 3 using Tapatalk
So the problem started when I flashed a 4.3 rom last friday. I formatted my internal memory in recovery mode because for some reason I only had 4 gigs of space and had moved everything over to the sd card. Once that was done phone said like 8 gigs available and thought everything was fixed. Well now if I turn off my phone it gets stuck in some kind of bootloop but it's not looping. It's just sits at the Samsung unlock symbol and custom screen. Doesn't loop just sits there. So one day I decided to format the internal memory again and the phone boots up like normal, but I can't power off the phone without going into recovery and formatting the internal memory every time. Any ideas on what is causing it or how I can make the Samsung custom boot stock instead so I can send it out.
I also have tried flashing another 4.3 rom and it doesn't seem to go away either.
I'm not an expert on how they have to make this stuff work with the mdk bootloader but I'm sure it's not hardware related. Have you tried flashing back to a 4.2 rom?
Sent from my SCH-I545 using Tapatalk 2
Downloading one now hopefully it will fix it.
Which recovery are you using? Make sure to wipe data, cache, and dalvik 3x each, then flash your rom
Sent from my SCH-I545 using Tapatalk 2
TWRP and I flashed hyperdrive still no luck still freezing in the same spot and have to actually format to get past it.
Anyone else have any idea on what else I can try?
BlackDynomitr said:
Anyone else have any idea on what else I can try?
Click to expand...
Click to collapse
What version of TWRP are you using?
Sent from my SCH-I545 using Tapatalk
I believe 2.5 I'm guessing only way to check is to go into recovery again.
BlackDynomitr said:
I believe 2.5 I'm guessing only way to check is to go into recovery again.
Click to expand...
Click to collapse
Yep that's the only one I've never had any issues with. TWRP 2.5.0.2
Edit: If your still having issues you could always Odin back with Stock firmware and get a clean start. I know its a pain lol
Sent from my SCH-I545 using Tapatalk
heath2805 said:
Yep that's the only one I've never had any issues with. TWRP 2.5.0.2
Edit: If your still having issues you could always Odin back with Stock firmware and get a clean start. I know its a pain lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Well I think that might work only thing I'm afraid is what if it doesn't turn on.
BlackDynomitr said:
Well I think that might work only thing I'm afraid is what if it doesn't turn on.
Click to expand...
Click to collapse
Well if it doesn't turn on after flashing stock firmware via Odin, you'll know its a hardware issue with it and your warranty should cover a new replacement.
Sent from my SCH-I545 using Tapatalk
I had this issue when I first got my phone. I bought it off Swappa, it was already running TWRP 2.5.0.2, giving me nothing but problems. I switch to Philz Touch and no longer have the issue.
So I have tried every trick under the sun to get my baseband up to MJ4 so I can fully enjoy StrongSteves Odexed Blue. I have been a huge fan of Odexed Blue since the Epic Days.
I am still getting noises in calls and poor wireless signal compared to my friends fully stock MJ4. I have tripped knox and when i try to go to fully stock MI5 for an OTA update, I am told my phone has been modified and cannot receive updates. I can get the build and the firmware to tick up to MJ4 but nothing I try can get the baseband updated. I am on stock kernel.
Can I offer a bounty of around $50 to anyone that can help me?
I will be online for several hours today.
EDIT: Solution is on my reply (#21) on page 3 of this thread.
Do u mean mj4?
Sent from my SM-N900P using XDA Premium 4 mobile app
aFoodStampBaby said:
Do u mean mj4?
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I did. I just fixed it, thanks!
drewbuntu said:
Yes I did. I just fixed it, thanks!
Click to expand...
Click to collapse
You have also tried Odin the full stock MJ4? If not just do that, if you have then maybe try this, Odin MI5, reboot to STOCK recovery and factory reset, then Odin MI5 again then reboot to STOCK recovery factory reset again, boot device then set everything up and wait for update. After update, if it takes, flash CF autoroot in Odin, flash TWRP in Odin then go Blue.
ifly4vamerica said:
You have also tried Odin the full stock MJ4? If not just do that, if you have then maybe try this, Odin MI5, reboot to STOCK recovery and factory reset, then Odin MI5 again then reboot to STOCK recovery factory reset again, boot device then set everything up and wait for update. After update, if it takes, flash CF autoroot in Odin, flash TWRP in Odin then go Blue.
Click to expand...
Click to collapse
I have tried flashing with Odin: N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.tar.md5
Even tried factory reset etc on it several times and flashing again.
I am downloading N900PVPUBMI5_N900PSPTBMI5_SPR.zip and will try your double odin method, even though I am sure I tried this 2 weeks ago.
ifly4vamerica said:
... Odin MI5, reboot to STOCK recovery and factory reset, then Odin MI5 again then reboot to STOCK recovery factory reset again, boot device then set everything up and wait for update. After update, if it takes, flash CF autoroot in Odin, flash TWRP in Odin then go Blue.
Click to expand...
Click to collapse
I tried this. Everything running at MI5 now, but OTA refuses to run still. I attached some screeshots.
As you can see it says "custom" on the "status page" and whatever is triggering that is preventing OTA.
Have you tried using Wanam X posed to fake the system status?
Sent from my SM-N900P using Xparent Skyblue Tapatalk 2
drewbuntu said:
So I have tried every trick under the sun to get my baseband up to MJ4 so I can fully enjoy StrongSteves Odexed Blue. I have been a huge fan of Odexed Blue since the Epic Days.
I am still getting noises in calls and poor wireless signal compared to my friends fully stock MJ4. I have tripped knox and when i try to go to fully stock MI5 for an OTA update, I am told my phone has been modified and cannot receive updates. I can get the build and the firmware to tick up to MJ4 but nothing I try can get the baseband updated. I am on stock kernel.
Can I offer a bounty of around $50 to anyone that can help me?
I will be online for several hours today.
Click to expand...
Click to collapse
So you have the full MJ4 stock rom or just the modem?
Sent from my SM-N900P using XDA Premium 4 mobile app
drewbuntu said:
I tried this. Everything running at MI5 now, but OTA refuses to run still. I attached some screeshots.
As you can see it says "custom" on the "status page" and whatever is triggering that is preventing OTA.
Click to expand...
Click to collapse
Weird even if it was custom it should still flash in Odin when you do the stock MJ4 tar. Not sure what you have going on there. Maybe try a different Odin and stock MJ4 Tar. Good luck.
I've had success with odin3v1.85
Getting Nowhere Fast
mhutton said:
Have you tried using Wanam X posed to fake the system status?
Sent from my SM-N900P using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
@mhutton When I try Wanam eXposed, it allows me to check the box and then requests a reboot, but reboots in custom still.
What I tried to do was set Custom flag off and during reboot, boot into Odin and reflash the stock MI5 and MJ4 and neither work out
luisrod03 said:
So you have the full MJ4 stock rom or just the modem?
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
@luisrod03 I have tried stock full Odin MJ4 and SM-N900P-HLTESPR-MJ4-DeOdex-v2.zip, which is FULL stock rooted deodexed for freeza. Still nothing.
What else can I try to get my baseband up to MJ4? I am almost certain that knox and the custom flag is preventing this, but I am not experienced enough to know how to look at the logs or whatever to prove that.
drewbuntu said:
@mhutton When I try Wanam eXposed, it allows me to check the box and then requests a reboot, but reboots in custom still.
What I tried to do was set Custom flag off and during reboot, boot into Odin and reflash the stock MI5 and MJ4 and neither work out
@luisrod03 I have tried stock full Odin MJ4 and SM-N900P-HLTESPR-MJ4-DeOdex-v2.zip, which is FULL stock rooted deodexed for freeza. Still nothing.
What else can I try to get my baseband up to MJ4? I am almost certain that knox and the custom flag is preventing this, but I am not experienced enough to know how to look at the logs or whatever to prove that.
Click to expand...
Click to collapse
Maybe try going back to MI3, I think it was MI3 anyway, whatever was before MI5. It is important to do the factory reset and wipe data betweeb ODIN flashes though with the STOCK recovery. Last thing to check is that your MJ4 tar actually has the modems in it.
Firmware and Modem only
Full tar
MI3
Guide and links
Also have you tried removing the sd card? Seems I remember some people having trouble with the sd card in the phone steps would be:
remove SD
wipe data, internal sd, davlik and cache in twrp
odin stock (try MJ4 first to avoid the manual update if that doesnt take go back to MI3)
reboot into STOCK recovery and factory reset a couple times
re odin
before phone boots force it to recovery factory reset again
boot normally and see if you have mj4 (or see if you can get the update)
Once you get the update on the internal storage I think it remains flagged as bad until you wipe it so thus the need to pull the sd card and wipe internal memory. (this is just a theory though)
Let us know if this works
Also remember (just in case) some of the files will download as zips so you will need to extract the to flash the. tar.md5 or .tar file in Odin.
ifly4vamerica said:
Maybe try going back to MI3, I think it was MI3 anyway, whatever was before MI5. It is important to do the factory reset and wipe data betweeb ODIN flashes though with the STOCK recovery. Last thing to check is that your MJ4 tar actually has the modems in it.
Firmware and Modem only
Full tar
MI3
Guide and links
Also have you tried removing the sd card? Seems I remember some people having trouble with the sd card in the phone steps would be:
remove SD
wipe data, internal sd, davlik and cache in twrp
odin stock (try MJ4 first to avoid the manual update if that doesnt take go back to MI3)
reboot into STOCK recovery and factory reset a couple times
re odin
before phone boots force it to recovery factory reset again
boot normally and see if you have mj4 (or see if you can get the update)
Once you get the update on the internal storage I think it remains flagged as bad until you wipe it so thus the need to pull the sd card and wipe internal memory. (this is just a theory though)
Let us know if this works
Also remember (just in case) some of the files will download as zips so you will need to extract the to flash the. tar.md5 or .tar file in Odin.
Click to expand...
Click to collapse
Has downgrading from MI5 to MI3 caused issues for anyone? I'm aware of some that had issues with downgrading from MJ4 to MI5.
Sent from my SM-N900P using Xparent BlueTapatalk 2
---------- Post added at 10:28 AM ---------- Previous post was at 10:27 AM ----------
drewbuntu said:
@mhutton When I try Wanam eXposed, it allows me to check the box and then requests a reboot, but reboots in custom still.
What I tried to do was set Custom flag off and during reboot, boot into Odin and reflash the stock MI5 and MJ4 and neither work out
@luisrod03 I have tried stock full Odin MJ4 and SM-N900P-HLTESPR-MJ4-DeOdex-v2.zip, which is FULL stock rooted deodexed for freeza. Still nothing.
What else can I try to get my baseband up to MJ4? I am almost certain that knox and the custom flag is preventing this, but I am not experienced enough to know how to look at the logs or whatever to prove that.
Click to expand...
Click to collapse
Could you post a screenshot of your about phone screen, or are you unable to boot?
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Has downgrading from MI5 to MI3 caused issues for anyone? I'm aware of some that had issues with downgrading from MJ4 to MI5.
Sent from my SM-N900P using Xparent BlueTapatalk 2
---------- Post added at 10:28 AM ---------- Previous post was at 10:27 AM ----------
Could you post a screenshot of your about phone screen, or are you unable to boot?
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I know you can't downgrade from MJ4 to MI5 I tried that a few times and had to restore a nandroid to be able to boot. It wouldn't flash anything even through odin. I did however downgrade a few times from MI5 to MI3 initially. I don't recall having any issues at all.
micmars said:
Has downgrading from MI5 to MI3 caused issues for anyone? I'm aware of some that had issues with downgrading from MJ4 to MI5.
Sent from my SM-N900P using Xparent BlueTapatalk 2
---------- Post added at 10:28 AM ---------- Previous post was at 10:27 AM ----------
Could you post a screenshot of your about phone screen, or are you unable to boot?
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
The mi5 to mi3 downgrade is no problem.
It's how I first got root before tripping knox. (I had a whole thread on it somewhere)
MJ4 to mi5 not possible.
I guess I can read through this thread a bit.
There shouldn't be a situation where flashing the full samsung mj4 file in Odin won't set you straight...
Is it possibly an Odin pc side driver issue.
In theory the Kies program should be able to wipe it to new also though I've never tried.
Sent from my SM-N900P using Tapatalk
mjcollum said:
The mi5 to mi3 downgrade is no problem.
It's how I first got root before tripping knox. (I had a whole thread on it somewhere)
MJ4 to mi5 not possible.
I guess I can read through this thread a bit.
There shouldn't be a situation where flashing the full samsung mj4 file in Odin won't set you straight...
Is it possibly an Odin pc side driver issue.
In theory the Kies program should be able to wipe it to new also though I've never tried.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Thanks for confirming that. I got my phone after taking the MJ4 update right at the Sprint store.
I'm surprised Skunk Ape's stock MJ4 build using Odin hasn't worked. Seems to be the go-to in these situations.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Thanks for confirming that. I got my phone after taking the MJ4 update right at the Sprint store.
I'm surprised Skunk Ape's stock MJ4 build using Odin hasn't worked. Seems to be the go-to in these situations.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yea...
If the stock mj4 full samsung file through Odin doesn't do it ???
It should work every time. No matter what.
Though, I would bet any failures here would be a pc/Odin version/driver issue and not really a phone issue.
Of course I've been wrong before I guess.
Sent from my SM-N900P using Tapatalk
Good point on the MJ4 to MI5 downgrade but I think he is able to get back to MI5 just not able to get it to MJ4 which is strange... You would think if Odin worked to go back to MI5 it would work to go to MJ4.
Note 3 or Gear Sent
ifly4vamerica said:
Good point on the MJ4 to MI5 downgrade but I think he is able to get back to MI5 just not able to get it to MJ4 which is strange... You would think if Odin worked to go back to MI5 it would work to go to MJ4.
Note 3 or Gear Sent
Click to expand...
Click to collapse
Right I should clarify in the hopes it may help.
The issue with going back to mi5 from MJ4 is the bootloader and modems don't downgrade.
So at that point you'd have mj4 baseband stuff but mi5 system.
With mi5 a downgrade puts you at full mi3.
However you should still be able to flash the full samsung mj4 package regardless.
There is currently nothing newer out so no worry there.
Inability to flash a full zip from odin, provided it's a good md5 checked complete zip, is 99.99999999% likely to be an issue with odin , the pc, or drivers. (This is in my experience only so fwiw)
If the phone can get in download mode it shouldn't make any difference what information if any even is written to the necessary partitions. These will all be wiped and re installed anyway.
So...
If his baseband is mi5
There are two real options.
Get mi5 back to completely official. To take ota.
Flash a full mj4. (Usually odin, i don't believe the other packages are updating bootloaders, ect.)
In theory this is super simple.
You would just flash the full samsung mj4 in odin.
That should solve all the problems.
And would leave you with a completely stock phone. (With the exception of knox trip but that is a non issue.)
If for some reason you are not able to flash it with odin, you may give Kies a try. It should also be able to fully wipe and recover to the latest update.
Though in this situation I would probably spend my energy troubleshooting odin.
I'm going to stand behind my bet of it being a odin version or driver issue here.
Though if you are able to flash other things in odin it could also just be a bad file.
I have yet to have a phone that I could get into download mode that was not completely recoverable.
Though I have had issues with specific odin versions and drivers especially on windows 8.
Just my opinion. I'm not sure I even know what I'm talking about. And am probably safe to ignore.
Sent from my SM-N900P using Tapatalk
micmars said:
Has downgrading from MI5 to MI3 caused issues for anyone? I'm aware of some that had issues with downgrading from MJ4 to MI5.
Sent from my SM-N900P using Xparent BlueTapatalk 2
---------- Post added at 10:28 AM ---------- Previous post was at 10:27 AM ----------
Could you post a screenshot of your about phone screen, or are you unable to boot?
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I have been trying to get an MI3 image all day but the downloads fail or get interrupted.
I posted some screenshots in a previous post, and no matter what I try, I end up with version and baseband at MI5 and build at MJ5. I can flip flop build and sometimes version, but not baseband at all.
I have tried the wipe and flash trick 3 times in a row, I have tried Odin version 1.85 and 3.07 and 3.09, none of them complete the job. I have also tried going back to MI5 and then running the MJ5 ROM and then reboot into download and run just the baseband update then wipe, nothing.
Looks like I am about 8 hours + until i have a full MI3 rom.
So I was mj4 rooted .. then went back to stock .. did OTA kit kat update ... rooted using cf auto root since it was updated for 4.4 base now.. took a few seconds on Odin 3.07 showed up as reset on the screen .. phone will reboot but leave it plugged in til it says pass... Mine took a Lil over 2 mins.. anyway I then went to goo manager installed open recovery but when I clicked reboot to recovery.. my phone bootlooped on recovery screen .. I pulled out the battery an put it back in.. an immediately put it into download mode( before it had a chance to bootloop recovery again ) then clicked down to cancel an restart phone.. my question is is there a link to a 4.4 kit kat compatible twrp recovery version that I can install through Odin ... an if so do I put it in the pda section.. Sorry I'm new to note 3 an Odin. .. coming from HTC lol ... thx in advance !
Sent from my SM-N900P using Tapatalk
chico260 said:
So I was mj4 rooted .. then went back to stock .. did OTA kit kat update ... rooted using cf auto root since it was updated for 4.4 base now.. took a few seconds on Odin 3.07 showed up as reset on the screen .. phone will reboot but leave it plugged in til it says pass... Mine took a Lil over 2 mins.. anyway I then went to goo manager installed open recovery but when I clicked reboot to recovery.. my phone bootlooped on recovery screen .. I pulled out the battery an put it back in.. an immediately put it into download mode( before it had a chance to bootloop recovery again ) then clicked down to cancel an restart phone.. my question is is there a link to a 4.4 kit kat compatible twrp recovery version that I can install through Odin ... an if so do I put it in the pda section.. Sorry I'm new to note 3 an Odin. .. coming from HTC lol ... thx in advance !
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Yes, all TWRP and (I believe Philz, though not certain, as I've never used it) tar files can be flashed with PC Odin. Use the latest for KitKat. Go to the original development forum for answers to this important question, as the preferred recovery should be chosen by you.
If you need help flashing, just ask.
Recovery goes in the PDA slot.
Sent from my SM-N900P using Xparent BlueTapatalk 2
chico260 said:
So I was mj4 rooted .. then went back to stock .. did OTA kit kat update ... rooted using cf auto root since it was updated for 4.4 base now.. took a few seconds on Odin 3.07 showed up as reset on the screen .. phone will reboot but leave it plugged in til it says pass... Mine took a Lil over 2 mins.. anyway I then went to goo manager installed open recovery but when I clicked reboot to recovery.. my phone bootlooped on recovery screen .. I pulled out the battery an put it back in.. an immediately put it into download mode( before it had a chance to bootloop recovery again ) then clicked down to cancel an restart phone.. my question is is there a link to a 4.4 kit kat compatible twrp recovery version that I can install through Odin ... an if so do I put it in the pda section.. Sorry I'm new to note 3 an Odin. .. coming from HTC lol ... thx in advance !
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
The OP of this thread has a link to a 4.4 version of TWRP you can flash through Odin. And yes, you put it in the pda section for flashing.
chico260 said:
So I was mj4 rooted .. then went back to stock .. did OTA kit kat update ... rooted using cf auto root since it was updated for 4.4 base now.. took a few seconds on Odin 3.07 showed up as reset on the screen .. phone will reboot but leave it plugged in til it says pass... Mine took a Lil over 2 mins.. anyway I then went to goo manager installed open recovery but when I clicked reboot to recovery.. my phone bootlooped on recovery screen .. I pulled out the battery an put it back in.. an immediately put it into download mode( before it had a chance to bootloop recovery again ) then clicked down to cancel an restart phone.. my question is is there a link to a 4.4 kit kat compatible twrp recovery version that I can install through Odin ... an if so do I put it in the pda section.. Sorry I'm new to note 3 an Odin. .. coming from HTC lol ... thx in advance !
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Haven't tried it personally but here is the link for it http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltespr ......got this from the http://forum.xda-developers.com/showthread.php?t=2596001 Philz recovery thread says it's for Kitkat. i'm still rockin 4.3 atm
DreamingWolf said:
The OP of this thread has a link to a 4.4 version of TWRP you can flash through Odin. And yes, you put it in the pda section for flashing.
Click to expand...
Click to collapse
Used twrp in the op of this thread in the link an flashed with Odin 3.07 .. Good to go now .. thx everyone .. Also everyone is aware that cf auto root for kit kat 4.4 base was updated correct?
Sent from my SM-N900P using Tapatalk
chico260 said:
Used twrp in the op of this thread in the link an flashed with Odin 3.07 .. Good to go now .. thx everyone .. Also everyone is aware that cf auto root for kit kat 4.4 base was updated correct?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Yup.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Deleted
micmars said:
Yup.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Is the latest twrp still 2.6.3.2 for our kit kat version ?
Sent from my SM-N900P using Tapatalk
chico260 said:
Is the latest twrp still 2.6.3.2 for our kit kat version ?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
The TWRP for KitKat I'm using is 2.6.3.2, and was the first working recovery of which I am aware that was specifically designed for Sprint Note 3 KitKat.
That stated, I'm unclear if it is the latest.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
The TWRP for KitKat I'm using is 2.6.3.2, and was the first working recovery of which I am aware that was specifically designed for Sprint Note 3 KitKat.
That stated, I'm unclear if it is the latest.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Also I was wondering. .. coming from HTC evo 4G lte. . We flashed rom zips from internal but I noticed sacs rom (which I'm on said to wipe internal). .. so on samsung we always flash from external?
Sent from my SM-N900P using Tapatalk
chico260 said:
Also I was wondering. .. coming from HTC evo 4G lte. . We flashed rom zips from internal but I noticed sacs rom (which I'm on said to wipe internal). .. so on samsung we always flash from external?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Uhm, nope. I flash everything from internal, but then I blasted out of Jellybean about a month ago, and at that time, updating to the newer operating system required a repartition of the internal memory, so the internal memory was nuked.
At that time, some very explicit instructions were lain out by me as given to me by the dev whom released the leak NA4. From what I've seen, similar instructions are being used by some roms, most likely for similar reasons.
Thus, it's most likely a one-time event for ya.
Once complete, flash away.
I downloaded a new rom today sitting at my desk at work, installed it in 5 minutes, and had it tamed to my tastes pretty quickly...all from internal memory.
My external is for media, my internal is for flashing. I suspect things will be similar for all.
I hope this helps.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Uhm, nope. I flash everything from internal, but then I blasted out of Jellybean about a month ago, and at that time, updating to the newer operating system required a repartition of the internal memory, so the internal memory was nuked.
At that time, some very explicit instructions were lain out by me as given to me by the dev whom released the leak NA4. From what I've seen, similar instructions are being used by some roms, most likely for similar reasons.
Thus, it's most likely a one-time event for ya.
Once complete, flash away.
I downloaded a new rom today sitting at my desk at work, installed it in 5 minutes, and had it tamed to my tastes pretty quickly...all from internal memory.
My external is for media, my internal is for flashing. I suspect things will be similar for all.
I hope this helps.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
So I'm not going to need to wipe internal to flash other things unless prompt to ?
Sent from my SM-N900P using Tapatalk
I'm Unclear on Your Question...
chico260 said:
So I'm not going to need to wipe internal to flash other things unless prompt to ?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I'm unclear on your question. When I upgraded to KitKat for the first time, I blasted my internal data. That was a month ago. Since that time, I have run at least 3 different KitKat roms, all from internal memory. Each install was a single wipe from within TWRP, the standard flick of the knob, which wipes system, data and dalvik. No internal memory card gets wiped, ever. Just the 3 partitions I referenced.
Gotcha I was thinking I was supposed to wipe entire internal storage every time I flashed a rom, but was thinking if that's where the rom zip is.. I'm going to lose it an twrp back ups lol.. i did wipe everything single thing in internal storage including backups before installing sacs though which sucked.. Sorry I'm a Lil slow to this.. thnx man i really really appreciate your dedication an quick response
Sent from my SM-N900P using Tapatalk
micmars said:
I'm unclear on your question. When I upgraded to KitKat for the first time, I blasted my internal data. That was a month ago. Since that time, I have run at least 3 different KitKat roms, all from internal memory. Each install was a single wipe from within TWRP, the standard flick of the knob, which wipes system, data and dalvik. No internal memory card gets wiped, ever. Just the 3 partitions I referenced.
Click to expand...
Click to collapse
chico260 said:
Gotcha I was thinking I was supposed to wipe entire internal storage every time I flashed a rom, but was thinking if that's where the rom zip is.. I'm going to lose it an twrp back ups lol.. i did wipe everything single thing in internal storage including backups before installing sacs though which sucked.. Sorry I'm a Lil slow to this.. thnx man i really really appreciate your dedication an quick response
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Thnx! Again
Sent from my SM-N900P using Tapatalk
micmars said:
My external is for media, my internal is for flashing. I suspect things will be similar for all.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I think much depends on the size of ExtSDCard the person has. I have a 64Gb SanDisk and I keep everything on it from media to flashing files (ROMs, kernels, mods, recoveries, apps). Internal is only used for day to day accumulations from running apps. When it's time to flash a ROM, I move any data I wish to save from internal to external, then wipe internal. I wipe it every single time I flash a ROM. That way I never have to worry about old data borking the new install.
Just my $.02
DreamingWolf said:
I think much depends on the size of ExtSDCard the person has. I have a 64Gb SanDisk and I keep everything on it from media to flashing files (ROMs, kernels, mods, recoveries, apps). Internal is only used for day to day accumulations from running apps. When it's time to flash a ROM, I move any data I wish to save from internal to external, then wipe internal. I wipe it every single time I flash a ROM. That way I never have to worry about old data borking the new install.
Just my $.02
Click to expand...
Click to collapse
Do you wipe everything including storage
Sent from my SM-N900P using Tapatalk
chico260 said:
Do you wipe everything including storage
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Everything - System, Data, Cache, DalvikCache, Do a Factory reset (which is actually redundant because I wipe all the items included in this individually) and wipe (or format depending on which recovery I'm using) the internal SDCard.
Everything I want to keep and/or flash ROM to ROM sits on my external card.
DreamingWolf said:
Everything - System, Data, Cache, DalvikCache, Do a Factory reset (which is actually redundant because I wipe all the items included in this individually) and wipe (or format depending on which recovery I'm using) the internal SDCard.
Everything I want to keep and/or flash ROM to ROM sits on my external card.
Click to expand...
Click to collapse
OK. . I thought you meant in advanced wipe you wipe internal storage option also
Sent from my SM-N900P using Tapatalk
chico260 said:
OK. . I thought you meant in advanced wipe you wipe internal storage option also
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I did mean that. In TWRP you wipe internal storage under the advanced options, in Philz you format the data/data (internal sdcard) under the mounts option.
I wipe EVERYTHING except bootloader, recovery, and extsdcard every time I flash a ROM.
I am trying to flash a Sprint Samsung Note 3 with Cyanogenmod 11. I downloaded the imaged, checked the hash, and put it on the external sdcard. When I use TWRD to flash it, after wiping / factory default, I get the following message : Unable to mount '/usbstorage along with a Success message from TWRD. But when I reboot the phone it gets caught in a recovery loop. I have tried older releases of Cyanogenmod 11 also. Is there something I am missing? I looked online, and found some comments about wiping the data before flashing. But I had done that.
sansari123 said:
I am trying to flash a Sprint Samsung Note 3 with Cyanogenmod 11. I downloaded the imaged, checked the hash, and put it on the external sdcard. When I use TWRD to flash it, after wiping / factory default, I get the following message : Unable to mount '/usbstorage along with a Success message from TWRD. But when I reboot the phone it gets caught in a recovery loop. I have tried older releases of Cyanogenmod 11 also. Is there something I am missing? I looked online, and found some comments about wiping the data before flashing. But I had done that.
Click to expand...
Click to collapse
You flash gapps too ? And wipe data and system before flashing . The unable to mount error means nothing
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
You flash gapps too ? And wipe data and system before flashing . The unable to mount error means nothing
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I found this link about the error. http://forum.xda-developers.com/showthread.php?t=2507403 but the link to the script provided to fix this issue does not work. I have made a comment about it. Hope they can fix it.
Just to double check, I am putting my zip files for Cyanogenmod and Gapps on the sdcard. That is what we are supposed to do right?
sansari123 said:
Yes I did. For some reason it keeps getting stuck in boot loop. So you are saying I should look into something else? The unable to mount message does not mean much?
Click to expand...
Click to collapse
When going from stock to any aosp always wipe system that is what most do wrong
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
When going from stock to any aosp always wipe system that is what most do wrong
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Epix,
I'm not familiar with AOSP Roms on the Note 3, but I know that people were having major issues when upgrading from JellyBean to KitKat TW Roms. They had to Odin flash the stock NAB update first, then they were able to flash NAB (KitKat) Roms. Is this the same procedure for AOSP KitKat Roms?
I haven't seen anything on the various AOSP threads about having to be on NAB or newer (i.e. KitKat) in order to flash their Roms.
topherk said:
Epix,
I'm not familiar with AOSP Roms on the Note 3, but I know that people were having major issues when upgrading from JellyBean to KitKat TW Roms. They had to Odin flash the stock NAB update first, then they were able to flash NAB (KitKat) Roms. Is this the same procedure for AOSP KitKat Roms?
I haven't seen anything on the various AOSP threads about having to be on NAB or newer (i.e. KitKat) in order to flash their Roms.
Click to expand...
Click to collapse
It did not matter what bootloader you were on when flashing aosp roms .... as they were not built to need that .... you could have mj4 and flash 4.4.2 aosp roms just fine ... most times it is not wiping system as touch wiz was on system and it needs wiped to install aosp ....I personally wipe all but external and flash from there .... I hit advanced wipe and wipe data cache davlik system and internal. .. but that is just me
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
It did not matter what bootloader you were on when flashing aosp roms .... as they were not built to need that .... you could have mj4 and flash 4.4.2 aosp roms just fine ... most times it is not wiping system as touch wiz was on system and it needs wiped to install aosp ....I personally wipe all but external and flash from there .... I hit advanced wipe and wipe data cache davlik system and internal. .. but that is just me
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Ah, that's good to know. I wasn't sure if AOSP Roms needed the updated bootloader.
I also do a full wipe in TWRP before flashing a new Rom. I find it prevents a lot of the various issues I've seen with dirty flashers on here.
Thanks for the input!
Epix4G said:
When going from stock to any aosp always wipe system that is what most do wrong
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yea I did a complete wipe of everything. Still got the error. I am now trying another microsd.