UPDATED OP.
link to bootloader warning.
EDITS
Info for people already on mj4.
10/30/13/11:34 US Central
link to bootloader warning.
EDITS
Info for people already on mj4.
10/30/13/11:34 US Central
Also links for kingoapp can now be added OP if you would like. The update hasn't hit yet to allow rebooting using 4 in 1 method but will soon.
Sent From Heaven on my Note 3
---------- Post added at 03:38 PM ---------- Previous post was at 03:31 PM ----------
www.kingoapp.com
https://www.facebook.com/kingoapp
Sent From Heaven on my Note 3
Give me 30 minutes or so I'm running an errand. Then I'll see if can figure something out for you.
walk me through your process again...
And are you still knox 0?
Sent from my SM-N900P using Tapatalk
1) Rooted with CF method.
2) installed TI backup and made a backup
3) xposed framework and wanam to "fake system status"
4) got TWRP, made nandroid backup and flashed the MJ4 file. Seemed to go fine.
The build is updated to MJ4 and the kernel is updated, but the baseband is still on MI5. Calls still popping, etc.
custom
custom
Knox kernel 0x0
knox warranty 0x1
What can I do to get the proper baseband to match the build? (I assume that will fix the call issue?)
Or, should I unroot and backout factory reset, etc. to get the right OTA update?
Thanks
Finally got my system status back to official by factory resetting and flashing MI5 with ODIN again only to get "The latest updates have already been installed" when running the system update so I guess I'll be waiting a little longer for MJ4! Once someone figures out how to update the baseband outside of official updates, I'll probably just trip KNOX and go that route.
Edit: Spoke too soon, just got the update to download
If she's still mi5 just use the first post.Were you on rooted MI5? This seems to be the only option to get back to official. Wanam is useless on my girlfriend's rooted MI5. I really was not looking forward to reflashing and seeing my girlfriend's look of disapproval if she has to redo even on app.
I couldn't get Wanam to show official, I had to wipe and flash MI5 in ODIN twice, then I finally got to official status. I think I'll wait for the TAR to get released next timeIf she's still mi5 just use the first post.
Flashing a vegafied mi5 file and not using the sd files should get you official and the ota. Then run sd files. Shouldn't require a wipe.
Sent from my SM-N900P using Tapatalk
If she's still mi5 just use the first post.
Flashing a vegafied mi5 file and not using the sd files should get you official and the ota. Then run sd files. Shouldn't require a wipe.
Sent from my SM-N900P using Tapatalk
I couldn't get Wanam to show official, I had to wipe and flash MI5 in ODIN twice, then I finally got to official status. I think I'll wait for the TAR to get released next time
I couldn't get Wanam to show official, I had to wipe and flash MI5 in ODIN twice, then I finally got to official status. I think I'll wait for the TAR to get released next time
I really hope it's the former. If it was my phone i wouldn't care but she's got her live wallpaper and icons just the way she likes it. I'd have to hear it, but not the end of the world.
well looks like ill be flipping my knox flag.
thought i had everything done correctly file looked good.
copied over to system..
locks up at sprint logo.
and i guess theres no true adb access in the stock recovery only sideload which doesnt seem to be any use for replacing system files.
unless im missing something i guess ill be installing twrp.
oh well it was bound to happen sooner or later.
ill still be trying to get yall an odex version though.
No no no.. man that bites. Man.. Did you try a battery pull or a factory reset
Sent from my SM-N900P using Xparent Purple Tapatalk 2
HA nevermind. all good.
was able to get adb back by letting it sit at the sprint logo for a minute
odex test version up need a tester