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

Root Another JB Update?!

deeleo said:
Sorry if this is a dumb question: In the step where you say "flash the update zip," I'm unclear how to do this after copying the update zip to /cache. In CWM recovery (I'm using 6.0.2.3), I don't see a way to flash a zip from /cache. Am I missing something obvious?
Click to expand...

If you are using cwm you can copy the zip to whatever folder is convenient for you. I flashed mine from my microsd.
 
deeleo said:
Sorry if this is a dumb question: In the step where you say "flash the update zip," I'm unclear how to do this after copying the update zip to /cache. In CWM recovery (I'm using 6.0.2.3), I don't see a way to flash a zip from /cache. Am I missing something obvious?
Click to expand...

Use the tested and latest 6.0.3.6 recovery. I don't know if your recovery will work. You can copy the zip to your sdcard and flash from there.
 
So...I'm gonna do these updates; noticed that madmikess flashed his from his micro sd (I'm assuming he meant ext sd).

Also, that you've updated the kernel over on the other thread...sweet.

My question to you is; should the kernel be done 1st, vise-versa, or does it even matter?
You've probably also seen from one of my other posts that I prefer to augment my phone-ware thru my phone's wifi when and where possible, so that's the route I'll be using here.

Thanks again for ALL the work! :thumbup:

Peace,
Sox
 
soxtober05 said:
So...I'm gonna do these updates; noticed that madmikess flashed his from his micro sd (I'm assuming he meant ext sd).

Also, that you've updated the kernel over on the other thread...sweet.

My question to you is; should the kernel be done 1st, vise-versa, or does it even matter?
You've probably also seen from one of my other posts that I prefer to augment my phone-ware thru my phone's wifi when and where possible, so that's the route I'll be using here.

Thanks again for ALL the work! :thumbup:

Peace,
Sox
Click to expand...

AFAIK, the stock MD6 kernel is needed before flashing MI2 OTA update. After the OTA flashed, you can go back to MiRaGe kernel again. This is what I did.
 
mrg666 said:
AFAIK, the stock MD6 kernel is needed before flashing MI2 OTA update. After the OTA flashed, you can go back to MiRaGe kernel again. This is what I did.
Click to expand...

Yeah, I've been running the md6 since the get-go. So you're advice is the md12 update, then re-do the kernel?

EDIT: sorry I meant the M12
 
soxtober05 said:
Yeah, I've been running the md6 since the get-go. So you're advice is the md12 update, then re-do the kernel?
Click to expand...

I didn't advise anything. Just answered your question about MI2 update :D

Frankly, I am not sure if there is much/any change in MI2 update yet. At least, I didn't see any problems yet and it seems that MI2 is demanding less RAM. Or that is what I want to see as RAM shortage was the most serious problem with MD6, imho. Let's see what will other users say who had problems with freezing lockscreen.

I think it is worth trying MI2 since MD6 is not so great anyway. So, I have advised something now :)
 
So my girlfriend's phone had a custom ROM which kept giving me error 7s (system file mods) when I tried to update it, so I just made a cwm backup of my recently updated phone and erased the md5 sums in it and restored it to her phone. Now she has to deal with all the Fallout themes I have on there lol
It worked as far as updating goes though.
Edit- though it didn't update her baseband. No big deal, everything else is snazzy!
 
mrg666 said:
I didn't advise anything. Just answered your question about MI2 update :D

Frankly, I am not sure if there is much/any change in MI2 update yet. At least, I didn't see any problems yet and it seems that MI2 is demanding less RAM. Or that is what I want to see as RAM shortage was the most serious problem with MD6, imho. Let's see what will other users say who had problems with freezing lockscreen.

I think it is worth trying MI2 since MD6 is not so great anyway. So, I have advised something now :)
Click to expand...

Sorry, point taken. I didn't mean to misconstrue between advise and answer...DOH! :p
 
I have to say that this new update seems to be better than md6. Overall things seem snappier, and so far battery life seems better. Of course I'll need more time to really give it a chance to show if it's better or not. The only thing I'm really hoping for is that this fixes the unresponsive touchscreen issues.
 
We-ellllll....

Managed to get the M12 update done & working; slightly different than posted techniques.
I downloaded the ota from mrg666's link, and also the kernel; put 'em both on my ext sd & tried to flash the update with CWM... no go.
Then I decided to flash zjones' Stock412 odexed ROM that I still had on my SD card. Now I'm at stockJB, AND I still had CWMT 6.0.3.6 working!
Opened the 'install zip from ext SD, and selected the M12 update file. It installed easily enough, but it installed the stock 3e recovery. After a couple of groans and expletives, I gave in and fired up Odin. At first, the MiRaGe 6036 failed thru the push... And I found by experiment that it WOULD NOT PASS WHILE THE AUTO REBOOT BOX WAS UNCHECKED! If it was checked, it passed every time; but when I tired to go that route, I could never get the battery pull timing right, and subsequently the 3e would reinstall.
So my solution was to flash the test8 (6.0.2.3)... because I knew for sure that one would stick with the auto reboot checked; and it did.
So NOW I've got CWM back to stay,WITH the M12 update in tact, but no root...BUT WAIT! On my SD card I also have a SuperSU 1.25 zip file and the original MiRaGe 6.0.3.6 zip (thanks mrg!)...
Flashed both of those files, and VOLIA!... WORKING M12 UPDATE WITH ROOT! COULDN'T HAVE BEEN EASIER!

UGH!
 
I have a really good feeling about the MI2 update, particularly in conjunction with the updated MiRaGe kernel. Already, I'm seeing an app that almost always hangs and crashes on me if I do a particular thing running completely smoothly when I do that thing. :D
 
Woke up this morning and saw there was the update notification on my phone. I told it to install it, it rebooted, a blue screen flashed and then went black and nothing.

I have OOTB Jellybean, and a while back without knowing tried to root, but obviously that doesn't work. But now I have no Stock recovery, I have have whatever that Power + Volume Down boot menu is (Forgot the term you all use for it).

So how do I get stock recovery back so I can actually get this update?

Tried using Odin and the stock recovery provided above, but not the right format for Odin to flash.
 
I think you could use Odin to flash the custom recovery, then use that recovery to flash stock recovery. That is, if I'm understanding you correctly.

But you should be able to use custom recovery to install the update as long as everything else is stock.

If all else fails, Kies can probably get you back to stock even though it's a pain to use.

Pwr + vol up for recovery mode

Pwr + vol down for download mode(for Odin)

By the way, JBOOB is rootable now.
 
sanjuro77 said:
If all else fails, Kies can probably get you back to stock even though it's a pain to use.
Click to expand...

Or if you're me, Kies will also fail. Fortunately, I've found that Kies isn't strictly necessary. zjones posted up a stock JB that I flashed just yesterday, and it's gotten me up and running and helped me get to where I want to be.
 
mrg666 said:
I have just flashed it
is5e.png


MD6 stock ROM and stock boot images are required. Also there should be nothing deleted or modified in the /system directory (having superuser.apk, su binary, and busybox are okay). So you will need to restore /system if you have modified anything. If you are not able to restore your modifications in /system than KIES restore is the only way I can imagine.

Here is the procedure:
- copy the update zip in the previous message to /cache if your phone hasn't downloaded it yet.
- I have built the following flashable zip that will restore original boot image. Go to CWM and flash this. MD6 stock boot image
- reboot into stock recovery or CWM recovery
- flash the update zip
- reboot into MI2

Everything will be restored but apps, data, and settings will be preserved.

I will be working on the recovery and kernel for rooting this again. I will let you know soon

Edit: stock recovery was not really require based on the sanjuro's feedback below. So this post has been updated accordingly.
Click to expand...
I followed the directions (i think i did it correctly) and I get a status 7 error when flashing the MD6 to MD12
can i get some help?
 
PhilBilly881 said:
I followed the directions (i think i did it correctly) and I get a status 7 error when flashing the MD6 to MD12
can i get some help?
Click to expand...


Error 7 means something in the system files has been changed. Are you running a custom Rom? If I recall, you might be running Party Time JB. If so you'll have to flash a stock Rom first before the update will take.

ZJones' cwm-flashable stock Rom will work (use the non deodexed one).
Or Tyler's stock JB backup which can be restored with cwm.
 
sanjuro77 said:
Error 7 means something in the system files has been changed. Are you running a custom Rom? If I recall, you might be running Party Time JB. If so you'll have to flash a stock Rom first before the update will take.

ZJones' cwm-flashable stock Rom will work (use the non deodexed one).
Or Tyler's stock JB backup which can be restored with cwm.
Click to expand...

I did have party time, but flashed Zjone's stock DEODEXED version, thinking it would work. Ill install the non deodexed version and report back.
 
PhilBilly881 said:
I did have party time, but flashed Zjone's stock DEODEXED version, thinking it would work. Ill install the non deodexed version and report back.
Click to expand...

I made the same mistake, but after flashing the stock version, all was golden. While you're at it, after you get the MI2 update, you might want to check out mrg666's MiRaGe kernel. It's excellent.
 
You must log in or register to reply here.
Back
Top Bottom