Ok guys, I'm making this thread for all the people that had to flash MI5 stock tar (thanks Josh) in order to have their phone accept the MJ4 firmware. Once the MJ4 firmware is on the phone you may ask how do I go about Rooting my phone and getting TWRP back. At least that is the question I asked myself.
Once I was on MJ4 I attempted to go into Odin and use CF Auto Root. This install did not go through. It froze on me and I was forced to abort. I attempted to flas MI3/MI5 in Odin but those would not go through either. I really thought my phone was bricked. Luckily someone advised I flash TWRP via Odin. Sure enough that got me to boot into my MI5 rom (with my newly installed MJ4 firmware.) However, after manually trying to get into recovery I was taken to stock recovery and not TWRP. This is where I stand right now and I really don't know where to proceed. At this point I'm just happy my phone isn't bricked.
Long story short: CF Auto Root did not work for me on MJ4 firmware. Some have said it worked. I'm not trying again. Please post your experiences concerning this topic so we can all decide which route back to Root is best for those with MJ4 firmware.
I downloaded TWRP ODIN files and ChainFires SU 1.65 flashable zip. The trick is to push TWRP via ODIN ensuring only "auto reboot" is selected. Once you hit start and get to the point where you hear your pc make the usb disconnect sound hold Vol+, Home and Power to boot into recovery. If you do this right TWRP will boot, if not you will have the stock recovery. Once in TWRP flash the SU zip and reboot then profit! Worked like a champ for me
Edit: If at first you don't succeed, try again. It works, just takes practice. And yes I flashed the MI5 tar via ODIN and updated to MJ4.
Sent from my SM-N900P using Tapatalk
I followed your instructions. The only thing I didn't do was flash SU.zip. I simply restored my nandroid.
Thanks for the break down man!
I used restore stock Odin MI5. And then CF auto root. And goo manager to install twrp. Worked without any problems
Sent from my SM-N900P using xda app-developers app
---------- Post added at 11:36 PM ---------- Previous post was at 11:34 PM ----------
Forgot to add that after using MI5 Odin stock got the update for MJ4.
Sent from my SM-N900P using xda app-developers app
MJ4 BOOTLOADER WARNING http://forum.xda-developers.com/showthread.php?t=2503620
KNOX SAFE ROOT INFO http://forum.xda-developers.com/showthread.php?p=46946926#post46946926
mjcollum said:
MJ4 BOOTLOADER WARNING http://forum.xda-developers.com/showthread.php?t=2503620
KNOX SAFE ROOT INFO http://forum.xda-developers.com/showthread.php?p=46946926#post46946926
Click to expand...
Click to collapse
+1
I used the method in your Knox Safe Root link yesterday and I'm good to go. Phone Software, Baseband and Build number are all MJ4, Knox is 0x0, System status is Official, SELinux status is Enforcing. Happy camper!
Does any have a flashable su 1.65 zip I've searched an can't find it. If so thank you your a lifesaver!
Sent from my SM-N900P using XDA Premium 4 mobile app
---------- Post added at 07:33 AM ---------- Previous post was at 07:30 AM ----------
dunjay said:
Does any have a flashable su 1.65 zip I've searched an can't find it. If so thank you your a lifesaver!
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry cancel that more searching found it thanks
Sent from my SM-N900P using XDA Premium 4 mobile app
I odined the MI5 stock tar got the MJ4 update. updated to MJ4 then installed twrp and restored nandroid. now I have MI5 build number grrrr
oxmis said:
I odined the MI5 stock tar got the MJ4 update. updated to MJ4 then installed twrp and restored nandroid. now I have MI5 build number grrrr
Click to expand...
Click to collapse
That's because you restored your Ml5 nandroid. You should still have MJ4 firmware, and Software version though...which are the important bits with the MJ4 update. Unless of course you selected MODEM in the restore and rewrote the M15 version of that too.
If that just bugs you, you can edit your build.prop and change the value for ro.build.display.id to whatever you want!
Gack69 said:
That's because you restored your Ml5 nandroid. You should still have MJ4 firmware, and Software version though...which are the important bits with the MJ4 update. Unless of course you selected MODEM in the restore and rewrote the M15 version of that too.
Click to expand...
Click to collapse
Yeah I know lol. My baseband is mj4 though so im somewhat happy.
Sent from my SM-N900P using Tapatalk
oxmis said:
Yeah I know lol. My baseband is mj4 though so im somewhat happy.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
You should be completely happy. What I'm trying to say...is what you're observing is entirely cosmetic. Your nandroid just restored your old build.prop from your stock Ml5, so it's just a text string you're looking at. You got the firmware update, which was the entire point of the exercise. If the cosmetic detail of that string value is making you less than entirely happy...change it to MJ4
After editing it...you will have to reboot for the changes to display though, most likely.
Gack69 said:
You should be completely happy. What I'm trying to say...is what you're observing is entirely cosmetic. Your nandroid just restored your old build.prop from your stock Ml5, so it's just a text string you're looking at. You got the firmware update, which was the entire point of the exercise. If the cosmetic detail of that string value is making you less than entirely happy...change it to MJ4
After editing it...you will have to reboot for the changes to display though, most likely.
Click to expand...
Click to collapse
Yeah I'm just anal that way lol but how do you manual change it?
Sent from my SM-N900P using Tapatalk
oxmis said:
Yeah I'm just anal that way lol but how do you manual change it?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Any text editor technically. But the easiest by far IMO, is to download ROMToolbox (by JRummy) from the Playstore. Install it, and under the "Performance" section is "build.prop Editor". Tap that button...scroll to that bit that I mention previous. ro.build.display.id TAP it, and tap into the PROPERTY VALUE field and edit to your hearts content Tap OK, when your done, reboot. TADA! WINNING!!
BTW...the PRO version is on sale.. $2.99 Very useful app.
nolimit06 said:
I downloaded TWRP ODIN files and ChainFires SU 1.65 flashable zip. The trick is to push TWRP via ODIN ensuring only "auto reboot" is selected. Once you hit start and get to the point where you hear your pc make the usb disconnect sound hold Vol+, Home and Power to boot into recovery. If you do this right TWRP will boot, if not you will have the stock recovery. Once in TWRP flash the SU zip and reboot then profit! Worked like a champ for me
Edit: If at first you don't succeed, try again. It works, just takes practice. And yes I flashed the MI5 tar via ODIN and updated to MJ4.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I am in the same boat, stuck at the yellow screen, where did you download the stock mj4 tar to flash it with odin?
neonsector said:
I am in the same boat, stuck at the yellow screen, where did you download the stock mj4 tar to flash it with odin?
Click to expand...
Click to collapse
He flashed MI5 via Odin (can be found in Josh Beach's dl section) and then accepted the MJ4 update.
Sent from my SM-N900P using XDA Premium 4 mobile app
So restoring from a nandroid is the only way to root MJ4? I forgot to do a nandroid before doing the update. So I have nothing to restore from.
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 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.
I like many others was having an issue rooting my Note 3 so I figured I'd post a temporary fix until the official Method Comes along Freeza, Twrp Team, CF Root And Others.
WARNING! I am not responsible if you Brick your phone or any damage that may inccur.
Step 1. Download Odin/ CF-Root http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
Step 2. Download Engineering Bootloader N900PVPUCNAB http://forum.xda-developers.com/showpost.php?p=50489993&postcount=1
Step 3 Download Twrp http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
Step 4. Open Odin & (Put the Phone into Download Mode)
Step 5. Install Engineering Bootloader (In the Bootloader Section)
Step 6. Reboot Phone & Put it back into download mode & Install Tar File that Came with Odin
Step 7. Reboot Phone and Put back into download mode and Install the TWRP Download file
Thats it Hope this helps
======================================================================================
IF YOUR PHONE IS STUCK IN A BOOTLOOP FOLLOW THESE INSTRUCTIONS
If you're phone is currently in a bootloop from trying to root earlier in order to get your phone back working all you need to do is pull the battery. Turn the phone on in Download mode and press the Vol Down key to cancel and your phone will boot like normal
Simple enough lol.. very nice!
do we need to use the engineering bootloader?
craign1317 said:
do we need to use the engineering bootloader?
Click to expand...
Click to collapse
No, not at all. Stock bootloader is fine for the aforementioned.
I am not certain, but I believe that this excellent tutorial belongs in another forum, not in the development forum.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Nice, one problem though - the link for the odin download is bad. Link works but the zip file seems to be corrupted. I've tried downloading it about 8 times and it keeps coming up bad. Grabbed odin from another source.
Great post
craign1317 said:
do we need to use the engineering bootloader?
Click to expand...
Click to collapse
Not all the time, Only if you have tried Rooting before and you phone gets stuck in a bootloop
mid3vil said:
Nice, one problem though - the link for the odin download is bad. Link works but the zip file seems to be corrupted. I've tried downloading it about 8 times and it keeps coming up bad. Grabbed odin from another source.
Great post
Click to expand...
Click to collapse
I just clicked on the download and it downloaded just fine for me On a side note make sure you use that specific version.
Will these steps bring me from rooted MJ4 "Jellybomb" to rooted KitKat? Anything I need to do 1st?
---------- Post added at 01:19 PM ---------- Previous post was at 12:37 PM ----------
cmdauria said:
Will these steps bring me from rooted MJ4 "Jellybomb" to rooted KitKat? Anything I need to do 1st?
Click to expand...
Click to collapse
Mainly the question is will this bring me from rooted 4.3 to the point where I can install Freeza's stockish rom through TWRP?
cmdauria said:
Will these steps bring me from rooted MJ4 "Jellybomb" to rooted KitKat? Anything I need to do 1st?
---------- Post added at 01:19 PM ---------- Previous post was at 12:37 PM ----------
Mainly the question is will this bring me from rooted 4.3 to the point where I can install Freeza's stockish rom through TWRP?
Click to expand...
Click to collapse
You need to follow the guidance in the stock tar NAB thread, and hit the OP of the NABD discussion thread in the general forum for the latest info on migrating from MJ4 to stock NAB...
You will need to simply throw that tar file from the dev forum onto PC Odin, no pit file needed, and just flash it. You'll be stock NAB.
You may want to backup all storage, and factory reset your phone whilst in MJ4, prior to flashing, for good measure, but probably unnecessary. That probably part is why I suggest it.
Sent from my SM-N900P using Xparent BlueTapatalk 2
while this method certainly got me twrp, I am not rooted.
Two things, When I got into recovery I get "Seandroid" in red letters, but it still goes into TWRP.
Also, i flashed a .zip of "SuperSU", is that my problem?
When I boot up phone, Supersu says there is no su binary, and root checker app says not rooted.
processorsaurus said:
while this method certainly got me twrp, I am not rooted.
Two things, When I got into recovery I get "Seandroid" in red letters, but it still goes into TWRP.
Also, i flashed a .zip of "SuperSU", is that my problem?
When I boot up phone, Supersu says there is no su binary, and root checker app says not rooted.
Click to expand...
Click to collapse
You shouldn't need to flash SuperSU it should automatically be installed.
Sent from my SM-N900P using xda app-developers app
cmdauria said:
Will these steps bring me from rooted MJ4 "Jellybomb" to rooted KitKat? Anything I need to do 1st?
---------- Post added at 01:19 PM ---------- Previous post was at 12:37 PM ----------
Mainly the question is will this bring me from rooted 4.3 to the point where I can install Freeza's stockish rom through TWRP?
Click to expand...
Click to collapse
You need to install Freezas build of kit kat before you try to root your phone again
Sent from my SM-N900P using xda app-developers app
averymlewis said:
You shouldn't need to flash SuperSU it should automatically be installed.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
I tried everything again, all successful, but still no root...I still show SuperSU installed, how can I get rid of it now?
I installed Superuser app, did binary update, and it says "checking installed version = 1.61:supersu"
Supersu is in app list, but no option to uninstall from Play or application list.
There should be an option in the Super su app itself.
Sent from my SM-N900P using xda app-developers app
caesar_ said:
There should be an option in the Super su app itself.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
I can't get into the app, it just says "there is no su binary installed, this is a problem!" and closes. force stop, clear data/cache doesn't work.
processorsaurus said:
I can't get into the app, it just says "there is no su binary installed, this is a problem!" and closes. force stop, clear data/cache doesn't work.
Click to expand...
Click to collapse
May need a factory reset..
Sent from my SM-N900P using xda app-developers app
caesar_ said:
May need a factory reset..
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Now it says no OS loaded....I am an idiot. :crying:
There probably isn't a stock Kitkat for download is there?
processorsaurus said:
Now it says no OS loaded....I am an idiot. :crying:
There probably isn't a stock Kitkat for download is there?
Click to expand...
Click to collapse
Actually there is.. freeza uploaded the official ota update here in the forums. Just go to recovery and factory reset.. Then go immediately to download mode and flash that tar file via Odin.
Sent from my SM-N900P using xda app-developers app
caesar_ said:
Actually there is.. freeza uploaded the official ota update here in the forums. Just go to recovery and factory reset.. Then go immediately to download mode and flash that tar file via Odin.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
SWEET - thanks for all your help. I have found his odex/deodex thread, is there another I'm not seeing?
EDIT - found it here http://forum.xda-developers.com/showthread.php?t=2655883
processorsaurus said:
SWEET - thanks for all your help. I have found his odex/deodex thread, is there another I'm not seeing?
Click to expand...
Click to collapse
There is a leak and then there is an official.. I chose the official but the choice is yours.
Sent from my SM-N900P using xda app-developers app
Im on the stock OTA kitkat...should i wait for a better method to root and install recovery or will this do? @micmars whats ur input on this?
Hey guys. So thanks to Micmars I was able to break myself out of a terrible boot loop. The only real solution at the time was to use an exe file to push me into the NAB update. My goal was to then to go ahead and push a custom recovery and use SuperSU to root the device, followed by installing NABD. Problem is that it seems that the current stock recovery is unable to flash any of these updates. The broken android comes up when I enter stock recovery. Flashing a custom recovery fails as well.
Here are my goals:
1. Root
2. Flash TWRP
3. Install one of the latest and greatest custom ROM.
I need your help fellas. Any help is greatly appreciated and big shutout to Micmars for saving me from bricking my phone.
Sent from my SM-N900P using xda app-developers app
You will need to root with CF root you can find it in the forums. If you do that you will lose Knox warranty.
Sent from my SM-N900P using xda app-developers app
Put the phone in odin aka download mode. Flash recovery from there. Works fine. Trips knox. But for me I didn't care. Your milage will vary.
Sent From My 0x1 Note 3.i love tep....
wgorham said:
You will need to root with CF root you can find it in the forums. If you do that you will lose Knox warranty.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
I looked at several different stock roms and or recoveries. What exactly is a CF Root? My phone has already tripped Knox so I'm not worried about that.
Sent from my SM-N900P using xda app-developers app
kaos420 said:
Put the phone in odin aka download mode. Flash recovery from there. Works fine. Trips knox. But for me I didn't care. Your milage will vary.
Sent From My 0x1 Note 3.i love tep....
Click to expand...
Click to collapse
Now which recovery are you referring to? Is it the stock? I have tried multiple times with Odin to flash the stock recovery but it won't because it already has the NAB recovery installed and its not letting it do anything else because its saying that the operating system has been modified. so it's basically trying to box with me a bit.
Sent from my SM-N900P using xda app-developers app
KoolCharisma said:
Now which recovery are you referring to? Is it the stock? I have tried multiple times with Odin to flash the stock recovery but it won't because it already has the NAB recovery installed and its not letting it do anything else because its saying that the operating system has been modified. so it's basically trying to box with me a bit.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Why are you trying to flash stock recovery? ?? It already has stock unless you flashed twrp or philz
Go get the NAB tar file and flash back to Stock and then do what you want .... root with chain fire cf auto root for 9005 ... international note 3 ... Then flash twrp the newest is 2.7 ...
Sent from my SM-N900P using Xparent BlueTapatalk 2
KoolCharisma said:
Hey guys. So thanks to Micmars I was able to break myself out of a terrible boot loop. The only real solution at the time was to use an exe file to push me into the NAB update. My goal was to then to go ahead and push a custom recovery and use SuperSU to root the device, followed by installing NABD. Problem is that it seems that the current stock recovery is unable to flash any of these updates. The broken android comes up when I enter stock recovery. Flashing a custom recovery fails as well.
Here are my goals:
1. Root
2. Flash TWRP
3. Install one of the latest and greatest custom ROM.
I need your help fellas. Any help is greatly appreciated and big shutout to Micmars for saving me from bricking my phone.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
To Start,
1. Remove any cases from phone.
2. Put Chainfire latest superuser on your phone,
https://www.dropbox.com/s/lbtuggkhqknm2ik/UPDATE-SuperSU-v1.93.zip
3. Put TWRP 2.7.0.0 for TouchWiz KitKat on your PC,
https://www.dropbox.com/s/ptl8dyomprxxn0l/openrecovery-twrp-2.7.0.0-hltespr-4.4.img.tar
4. Using PC Odin (3.07 is fine), flash TWRP,
https://www.dropbox.com/s/z2n10tjzmxlhaz4/Odin3 v3.07.zip
[Unzip to your PC, run Odin as administrator, shut down your phone, put phone in download mode (volume down + home + power, then volume up to confirm), load TWRP tar into PDA slot, plug phone into PC using same USB port as one you've used before, keep automatically restart checked in Odin, hold phone in palm of your hand, get ready to hold volume up + home, hit start on PC Odin, hit start on PC Odin, when file finishes flashing, hit those buttons quickly, since the recovery file flashes in like 5-10 seconds, your now in recovery.]
5. Inject root,
Tap install from the TWRP, navigate to the location on your phone you put that superuser file, flick the knob, reboot.
You are now rooted with custom recovery.
From here, the world is your own. Lots of roms from which to choose, I recommend looking around the dev forums, you'll find something that's right for you. Might want to start with a TouchWiz rom, just because they are built from stock and they'll function as you'd expect. Try AOSP if you like, but those roms tend to take a bit more diligence on your end. No problem with that, but this will get you started with the least effort.
I hope this helps.
Good luck!
Follow the OP instructions prior to flashing.
Sent from my SM-N900P using Xparent BlueTapatalk 2
KoolCharisma said:
Now which recovery are you referring to? Is it the stock? I have tried multiple times with Odin to flash the stock recovery but it won't because it already has the NAB recovery installed and its not letting it do anything else because its saying that the operating system has been modified. so it's basically trying to box with me a bit.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
So NAB is stock essentially? Why am I constantly having warnings of modification and app crashes constantly.
Further the current recovery is broken. You know, the beat up droid on the ground. It won't allow me to install root. Is it possible I need an older root request?
TWRP 2.07 don't flash through Odin. We'll get it though. Let's keep at it.
Sent from my SM-N900P using xda app-developers app
micmars said:
To Start,
1. Remove any cases from phone.
2. Put Chainfire latest superuser on your phone,
https://www.dropbox.com/s/lbtuggkhqknm2ik/UPDATE-SuperSU-v1.93.zip
3. Put TWRP 2.7.0.0 for TouchWiz KitKat on your PC,
https://www.dropbox.com/s/ptl8dyomprxxn0l/openrecovery-twrp-2.7.0.0-hltespr-4.4.img.tar
4. Using PC Odin (3.07 is fine), flash TWRP,
https://www.dropbox.com/s/z2n10tjzmxlhaz4/Odin3 v3.07.zip
[Unzip to your PC, run Odin as administrator, shut down your phone, put phone in download mode (volume down + home + power, then volume up to confirm), load TWRP tar into PDA slot, plug phone into PC using same USB port as one you've used before, keep automatically restart checked in Odin, hold phone in palm of your hand, get ready to hold volume up + home, hit start on PC Odin, hit start on PC Odin, when file finishes flashing, hit those buttons quickly, since the recovery file flashes in like 5-10 seconds, your now in recovery.]
5. Inject root,
Tap install from the TWRP, navigate to the location on your phone you put that superuser file, flick the knob, reboot.
You are now rooted with custom recovery.
From here, the world is your own. Lots of roms from which to choose, I recommend looking around the dev forums, you'll find something that's right for you. Might want to start with a TouchWiz rom, just because they are built from stock and they'll function as you'd expect. Try AOSP if you like, but those roms tend to take a bit more diligence on your end. No problem with that, but this will get you started with the least effort.
I hope this helps.
Good luck!
Follow the OP instructions prior to flashing.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Micmars! How good to see you again you old chap. Obviously since we last spoke I haven't had much progress. You really helped me getting to this point. We built a whole thread together and saved me $150 in insurance money to get me out of the brick. I don't have a computer on me but I've certainly tried a lot. If stick recovery is simply broken, how do I get of this mess?
I'm confident we'll have that new ROM in no time.
Sent from my SM-N900P using xda app-developers app
This is the message that keeps popping up on my screen. I also have an icon up top with a triang. I feel as though if I were running stock and if I've gone back to the original state of the phone it should
not have this message. I am I correct?
Sent from my SM-N900P using xda app-developers app
Stanard Knox Notifications..
KoolCharisma said:
This is the message that keeps popping up on my screen. I also have an icon up top with a triang. I feel as though if I were running stock and if I've gone back to the original state of the phone it should
not have this message. I am I correct?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Dude, those are standard Knox notifications. If you have successfully rooted your device, just get rid of the damn things. Install freeza's Knox-free Stockish DeOdex or Odex NABD rom and be done with it.
micmars said:
Dude, those are standard Knox notifications. If you have successfully rooted your device, just get rid of the damn things. Install freeza's Knox-free Stockish DeOdex or Odex NABD rom and be done with it.
Click to expand...
Click to collapse
That's just the problem. The stock recovery seems to be broken and I can not actively flash TWRP to the device neither clockworkmod. That's why I'm having the current problem. I can't do anything without having root obviously.
Sent from my SM-N900P using xda app-developers app
KoolCharisma said:
That's just the problem. The stock recovery seems to be broken and I can not actively flash TWRP to the device neither clockworkmod. That's why I'm having the current problem. I can't do anything without having root obviously.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
My friend, I'm at a loss. There's really nothing I can go at this point. Broken stock recovery makes no sense to me, but that doesn't mean it's not possible.
Flashing working recovery that is custom would replace a stock recovery, working or not. At least one could speculate.
You obviously need to install root.
Go hit the qbking77 video on rooting this device and follow the instructions.
Sent from my SM-N900P using Xparent BlueTapatalk 2
G900TUVS1FOL1_G900TTMB1FOL1_G900TUVS1FOL1_HOME.tar
To root:
1. Flash the latest TWRP
2. Flash the latest BETA Systemless Root .zip in TWRP: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
or
Just follow this guide: http://forum.xda-developers.com/tmo...6-5-1-1-pc-t3141404/post61497082#post61497082
I tried this last night with flashfire, had to flash twice, had to reboot after some google play installs and got the T-Mobile bootloop screen, had to flash back to Exodus rom from backup. I miss the touchwiz camera. I then flashed with TWRP and set it up, success! Flashed Hipasian kernel and lost camera....
Do i need to wipe data and cache prior to using Odin to install the full release?
I ask because my first attempt ended in a FAIL message. Secure check fail..
Currently on a rooted stock rom with some mods.
Sent from my SM-G900T3 using XDA Free mobile app
Always Wipe if coming from different rom
mgp53 said:
Do i need to wipe data and cache prior to using Odin to install the full release?
I ask because my first attempt ended in a FAIL message. Secure check fail..
Currently on a rooted stock rom with some mods.
Sent from my SM-G900T3 using XDA Free mobile app
Click to expand...
Click to collapse
I always back up and do a complete wipe so you have something to go back to when coming from different developer roms. Just seems to make things smoother.
hello to all i'm on 5.0 built number OB1 running super su pro-2.49 also do i flash this with odin.?? or flash fire.??
on this step =To root:
2. Flash the latest BETA Systemless Root .zip in TWRP: http://forum.xda-developers.com/show...25&postcount=3
which su do i choose.??? thanks
Anymore feedback on flashfiring this so far? so far only one feedback and he got a bootloop
devoidx said:
Anymore feedback on flashfiring this so far? so far only one feedback and he got a bootloop
Click to expand...
Click to collapse
Worked fine for me. Only issue was I had to use Odin to flash the modem. After the first boot, the baseband was still oj4. DL the stock modem in the post and used odin to install. Works great.
Sent from my SM-T320 using XDA Premium HD app
mgp53 said:
Worked fine for me. Only issue was I had to use Odin to flash the modem. After the first boot, the baseband was still oj4. DL the stock modem in the post and used odin to install. Works great.
Sent from my SM-T320 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! went ahead and did it myself and I also had to Odin the modem but other than that everything runs well.
Is the baseband/bootloader available for CM13 users?
nevermind i found it http://forum.xda-developers.com/tmo...t/how-to-update-to-g900tof6-5-1-1-pc-t3141404
muniz_ri said:
G900TUVS1FOL1_G900TTMB1FOL1_G900TUVS1FOL1_HOME.tar
To root:
1. Flash the latest TWRP
2. Flash the latest BETA Systemless Root .zip in TWRP: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
or
Just follow this guide: http://forum.xda-developers.com/tmo...6-5-1-1-pc-t3141404/post61497082#post61497082
Click to expand...
Click to collapse
Will this trip Knox?
Sent from my SM-G900T using Tapatalk
Playb3yond said:
Will this trip Knox?
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Just flashig the .tar will not trip knox but any root method will.
I'm guessing the only way to not void Knox is to downgrade to 5.0, root. Then use ota's to maintain root?
will this trip knox
Yes it definitely trips Knox. After flashing with Odin CF root rom my base was changed but root was unsuccessful. I tried a few times and put the phone in download mode and there on the screen was*
Knox 0x1 4. Screw me. Are there any wayspecific to reset knox
bronx_guitar said:
Yes it definitely trips Knox. After flashing with Odin CF root rom my base was changed but root was unsuccessful. I tried a few times and put the phone in download mode and there on the screen was*
Knox 0x1 4. Screw me. Are there any wayspecific to reset knox
Click to expand...
Click to collapse
There is no know way (at this point) to reset knox.
tripping knox
vinniej said:
There is no know way (at this point) to reset knox.
Click to expand...
Click to collapse
so i know this means my warranty is voided but i can still have my phone repaired if need be id just have to pay out of pocket then right? is there anyway to flash marshmallow onto my sm-g990t withotu root. i have tried many methods to root. using CF with ODIN, kingroot, towelrroot and nothing works. on on 5.1.1 with all the OTA updates. since flashing back to a stock sm-g990t rom i got the phone right and restored all my data from a back up but its been a lil glitchy. sometime it reboots and all my screens are back to out of box condition. flipboard, all of them. i have delete all those pages, turn off my magazine. redo my folders and shortcuts. any ideas or should i wait till april when i think tmobile rolls out marshmallow? thanx in advance
having some touble
I used odin everytime I chose the ap file it loads then it makes my laptop crash.. Is there another program i could use to run these tar files? Im running 5.1.1 tmobile.