[12/29] Restore for MJ5 --Doesn't trip Knox and optionally provides root--

[marcbsmoove]

Please Help stuck on 7

Hello All. i managed to make to step 7 but keep getting this: " ERROR: Failed to access device. libusb error: -12 "....Can someone please help me to fix this. Thanks to all who reply...

 

[fabiooli]

I'm experiencing the same thing. I used to work for this particular hosting company, and the standard tech support response was "uuuuuhhh.... Web Caches and DNS transversal queues. Check back in 24 hours or 14 Days. Have a good day. Do my survey."

I'm gonna say it's a bandwidth thing, but I used a script to download from dropbox to ftp, if everyone is experiencing the same issue, I'll upload the good old fashioned way.

The same happens here. Tried downloading a dozen times but nothing...

 

[bailey2408]

lol too late, i already did it and kept getting force closes on boot, but i applied the csc and now it works fine.

oh nooooooo!!!! sorry to hear that!! i didn't want to put you in my boat dang it.. i'm not sure but everything i've done still doesnt get heimdall working.. taking a break for a bit from it.. and evil that file for vrcredistx64 wasn't there but went out and found downloaded it from microsoft website and when used heimdall said a .dll file was missing and wouldn't work.. oh well thx again

 

[drakeymcmb]

Whenever i click start in heimdall it says this

Beginning session...
ERROR: Failed to begin session!
Releasing device interface...

Mi_68aablahblahblah is no longer connected
Detected I/O error 87:[The parameter is incorrect.

 

[dviera88]

oh nooooooo!!!! sorry to hear that!! i didn't want to put you in my boat dang it.. i'm not sure but everything i've done still doesnt get heimdall working.. taking a break for a bit from it.. and evil that file for vrcredistx64 wasn't there but went out and found downloaded it from microsoft website and when used heimdall said a .dll file was missing and wouldn't work.. oh well thx again

I think I went through your problem
Install http://www.microsoft.com/en-au/download/confirmation.aspx?id=30679

Before Step 6 go to utilities & click detect then go and put a checkmark on don't reboot
and start hope it helps.

 

[bailey2408]

Whenever i click start in heimdall it says this

Beginning session...
ERROR: Failed to begin session!
Releasing device interface...

Mi_68aablahblahblah is no longer connected
Detected I/O error 87:[The parameter is incorrect.

i'm assuming you can still connect and use odin? i have a replacement coming in mail- evil is there any way your image file could be converted to .tar format that can be used in odin or a way that designgears img could be modified with your workaround so we could use in odin? for whatever reason that seems to be the only way we can interact with our phone.. i'd be willing to test since i've got replacement coming (just can't trip knox if possible)

---------- Post added at 08:32 AM ---------- Previous post was at 08:10 AM ----------

I think I went through your problem
Install http://www.microsoft.com/en-au/download/confirmation.aspx?id=30679

Before Step 6 go to utilities & click detect then go and put a checkmark on don't reboot
and start hope it helps.

thnx will also try this later in day.. are you on windows 7 64 bit? if so shoud i remove all of the vrc files and just use the one you posted above? drakey if your on windows 7 64 bit give this a whirl and lemme know.. i think we are literally at same point of where our phone is

 

[drakeymcmb]

Ir worked yesterday with heimdall 1 time. Then it never worked again.

Sent from my SAMSUNG-SM-N900A using xda app-developers app

 

[[email protected]]

Hello All. i managed to make to step 7 but keep getting this: " ERROR: Failed to access device. libusb error: -12 "....Can someone please help me to fix this. Thanks to all who reply...

I basically had to abuse the crap out of the zadig.exe in the heimdall suite directory. the name of the kies driver for the device looks like "dg_ssudbus" and i believe i ended up using the libusb0 driver (i think i tried them all to be honest, if a driver didn't work i seem to recall that zadig.exe would give you some feedback "driver install failed" etc or "driver install successful") by clicking the "replace driver" button. once i replaced the driver i was able to detect the device through the heimdall frontend under the utilities tab.

when it was time to switch back to odin i just moved to a different usb port out of laziness. once i moved to a different port it rediscovered the device and used the kies driver again.

 

[evilpotatoman]

I think I went through your problem
Install http://www.microsoft.com/en-au/download/confirmation.aspx?id=30679

Before Step 6 go to utilities & click detect then go and put a checkmark on don't reboot
and start hope it helps.

This. Try this. For some reason you may need to click that detect option prior to flashing. I think that's when heimdall sends the hello command

 

[bailey2408]

This. Try this. For some reason you may need to click that detect option prior to flashing. I think that's when heimdall sends the hello command

holy crap!!!! that actually did the trick!! first time heimdall has worked for me.. and just flashed your mi9 image!!! off to the races!!! exactly what i did was fired up zadig, connected phone while in download mode (all i could do), installed the libusb0 driver for msm 8960, fired up heimdall frontend, went to utilities tab, hit detect button, and then went to flash screen and proceeded.. it actually worked- i can't believe it!!!

---------- Post added at 11:03 AM ---------- Previous post was at 11:02 AM ----------

I think I went through your problem
Install http://www.microsoft.com/en-au/download/confirmation.aspx?id=30679

Before Step 6 go to utilities & click detect then go and put a checkmark on don't reboot
and start hope it helps.

this worked!! thank you so much!! drakey give the bottom part a whirl- it should work for you too!!!!!

 

[ahmarchi]

i jsut get stuck on releasing device interface and nothing happens, then the start button is able to get clicked on again.... any help

 

[mikeyhim]

Like I mentioned, everything that MJ5 is about is restrictions. Once we OTA the device, there aren't too many options for us to revert to an earlier set of firmware.

Everything except the MI9_fix.img.ext4 (on your device, this file is the /system folder) I've provided in the OP is MJ5. I am just not sure if it would work. You'd need to "try and see" if the mi9 modem.bin flashes successfully in heimdall.

OK thanks so much. I have flashed MJ5 with this modem.bin by odin. It leads to a bootloop. I flashed back MJ5 modem by Odin and it changes back to original.

Now question is :
Where can I find the other parts like csc,ap of MI9? The links from hotfile in other threads are down.

Just flashing modem.bin didn't change knox

Sent from my IM-A870K using XDA Premium 4 mobile app

 

[bailey2408]

i jsut get stuck on releasing device interface and nothing happens, then the start button is able to get clicked on again.... any help

Read post 90.. that worked for me

 

[drakeymcmb]

holy crap!!!! that actually did the trick!! first time heimdall has worked for me.. and just flashed your mi9 image!!! off to the races!!! exactly what i did was fired up zadig, connected phone while in download mode (all i could do), installed the libusb0 driver for msm 8960, fired up heimdall frontend, went to utilities tab, hit detect button, and then went to flash screen and proceeded.. it actually worked- i can't believe it!!!

---------- Post added at 11:03 AM ---------- Previous post was at 11:02 AM ----------



this worked!! thank you so much!! drakey give the bottom part a whirl- it should work for you too!!!!!

Worked finally!!!!!!!!!!!!!!!!!!!!
Thanks you sooo much!!!
Back to flashing.

 

[ahmarchi]

does the root method used here intall busybox?

 

[drakeymcmb]

yes it does

 

[fabiooli]

Step 8

I passed step 8!
Now when I start the phone on step 9 it's all bugged, really slow and keep giving me the "Direct pen input has stopped" message. I extracted the file on internal memory at the root directory but after restarting the SuperSu is not installed.
Could you guys be more clear on this step? This "pen input has stopped"message is expected?

 

[bailey2408]

I passed step 8!
Now when I start the phone on step 9 it's all bugged, really slow and keep giving me the "Direct pen input has stopped" message. I extracted the file on internal memory at the root directory but after restarting the SuperSu is not installed.
Could you guys be more clear on this step? This "pen input has stopped"message is expected?

Sounds like you need to install the csc file tjat you should have on external sdcard. You have to install it from recovery

 

[evilpotatoman]

I passed step 8!
Now when I start the phone on step 9 it's all bugged, really slow and keep giving me the "Direct pen input has stopped" message. I extracted the file on internal memory at the root directory but after restarting the SuperSu is not installed.
Could you guys be more clear on this step? This "pen input has stopped"message is expected?

You need to boot into recovery to flash the sec_csc.zip file. Also, did you use Odin to reparation during step 2?

 

[ahmarchi]

Also make sure the file u have is 47.8 mb or what ever it is....I had to download it 3 time until I realized it was only downloading it to like 20 mb and stopping

Sent from my SM-N9005 using XDA Premium 4 mobile app

---------- Post added 11th December 2013 at 12:19 AM ---------- Previous post was 10th December 2013 at 11:20 PM ----------

another question, when we already have the mj5 partitions installed.... do we have to odin flash them EVERY time we have to restore, or can we just skip to the heimdall part?