• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root New plan!

You don't have to create threads for all of your 'plans'. Just do what we all do and leave it in your head. I suggest Google Keep if you are having trouble with that.
 
davidmargolin said:
You don't have to create threads for all of your 'plans'. Just do what we all do and leave it in your head. I suggest Google Keep if you are having trouble with that.
Click to expand...

All right. There's always the possibility, though, of someone saying, "Hey, I tried that, and my advice is to [zig] where you might think you ought to [zag]" or "Yeah, I tried that, and it did wonders" or sometimes even "Whoa, I advise against that because [reasons]."

But sure.
 
I like the idea of publicly documenting this. If anyone else catches whatever your device caught, they would know how to fix it right away!
 
rbheromax said:
I like the idea of publicly documenting this. If anyone else catches whatever your device caught, they would know how to fix it right away!
Click to expand...

Assuming it addresses the cause of the problem. Right now, plugging in headphones is an exercise in pointlessness. Everything else is dandy!

Thanks.
 
Okay, I think it should have been flash ROM, then flash kernel, because my kernel version now says 3.0.31-1175366 se.infra@SEP-129 #1 Tue Apr 30 02:46:07 KST 2013
 
yeah because when u flash that rom, it comes with its own kernel thus overwriting whichever one u wanted lol
 
After KIES reset, do the MI2 OTA update before doing anything else. After the OTA update do the followings,

- test if your problems are resolved first
- root and flash CWM recovery with ODIN,
- replace the kernel if you want

Don't do deodexed ROM flash since it will revert back to an older build than MI2.
 
mrg666 said:
After KIES reset, do the MI2 OTA update before doing anything else. After the OTA update do the followings,

- test if your problems are resolved first
- root and flash CWM recovery with ODIN,
- replace the kernel if you want

Don't do deodexed ROM flash since it will revert back to an older build than MI2.
Click to expand...

I did everything else, but Kies failed. I got notified of the OTA update after I'd done my factory reset, and the OTA failed.

Thanks.
 
shyFluttershy said:
I did everything else, but Kies failed. I got notified of the OTA update after I'd done my factory reset, and the OTA failed.

Thanks.
Click to expand...

I thought you were done with the KIES reset after you have mentioned about the stock kernel in your post. How did you get there?

Do you mean you have flashed the MI2 OTA by "did everything else"? That is great then.
 
mrg666 said:
I thought you were done with the KIES reset after you have mentioned about the stock kernel in your post. How did you get there?
Click to expand...

I'd already downloaded the zips to my SD card. When Kies failed, I threw my hands in the air (verbally expressing my consternation in a most unladylike manner) and just flashed the other things, then factory reset.

So now I'm de-odexed, MiRaGe'd, not rooted, and still running on MD6. I've given up on Kies, unless I can flash some stock things first to make it happy, because apparently having custom stuff can make Kies fail.

Thanks.
 
Well, test what you have there to see if the lockscreen problems are resolved. If not you should try MI2 OTA. But that deodexed ROM is blocking your way to MI2 big time. Why did you do that?
 
mrg666 said:
Well, test what you have there to see if the lockscreen problems are resolved. If not you should try MI2 OTA. But that deodexed ROM is blocking your way to MI2 big time. Why did you do that?
Click to expand...

Because I didn't know it would be a roadblock and I thought it would help streamline my system. I'm downloading the stock JB now, but it will take a while.

Thanks.
 
shyFluttershy said:
Because I didn't know it would be a roadblock and I thought it would help streamline my system. I'm downloading the stock JB now, but it will take a while.

Thanks.
Click to expand...

I used zjones' odexed rom; that's what I had on my extsd card. I'm up & running the M12 now, but it took me some time-and probably in a slightly more unconventional way. I doc.'d it on the other thread , if you venture a giggle...post #36...:rofl:
 
soxtober05 said:
I used zjones' odexed rom; that's what I had on my extsd card. I'm up & running the M12 now, but it took me some time-and probably in a slightly more unconventional way. I doc.'d it on the other thread , if you venture a giggle...post #36...:rofl:
Click to expand...

Yeah, I just flashed that and factory reset. Now I guess all I can do is wait for the OTA. :boring: :bebored:

Thanks.
 
shyFluttershy said:
I just tried that. Could you please tell me precisely which one that is and how to get there on the off chance I accidentally fiddled with the wrong one?

Thanks.
Click to expand...


Google Services Framework

Clear data option

Reboot phone

Then go to phone settings/about device/system updates/ check for updates
 
sanjuro77 said:
Google Services Framework

Clear data option

Reboot phone

Then go to phone settings/about device/system updates/ check for updates
Click to expand...

Well, I had indeed cleared the wrong app's data. It's still not pushing the update, though. (I do love how it initially said "Last checked for update 12/31/1969.")

Thanks.
 
I got the update prompt by clearing the data from Google Services Framework, then going directly to Check For Updates without first rebooting the phone.

I have the MI2 update!

[HIGH]
Baseband version
M950VPBMI2

Build number
JZO54K.M950VPBMI2
[/HIGH]

Hallelujah! :party:

Now to re-flash MiRaGe.
 
You must log in or register to reply here.
Back
Top Bottom