yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Original Development] ohnor:
Latest CASUAL builds not working after VZW update

Hey Adam,

I initially gained root through Framaroot, but the VZW update broke that. I've obtained a TWRP stock recovery for the VZW Note 10.1, but after looking up many links, I still haven't figured out how to use it with odin. There's no .tar file and the largest file is named "system.ext4.win"

I'm not familiar enough with TWRP, just discovered it today.

So I used CASUAL to try and get root back. I tried the following builds:

GalaxyNote10.1-TakeNoteVerizon-CASUAL-R763b--InstaBuild.jar

GalaxyNote10.1-TakeNoteVerizon-CASUAL-R773b--InstaBuild.jar

GalaxyNote10.1-TakeNoteVerizon-CASUAL-R774b--Nightly.jar

R763b--InstaBuild - I couldn't get past the rooting step with framaroot

R773b--InstaBuild - I got the following message a bunch of times before it auto stopped.

"Initialising connection...

Detecting device...

ERROR: Failed to access device. libusb error: -12

'LIBUSB_ERROR_NOT_SUPPORTED'; Attempting to continue

Heimdall v1.4.0"

R774b--Nightly - It put me into download mode and then nothing happened. Also the text in the "Important Information" box never showed up.

I really hope there's a way to get root back after Verizon patched it!

I'll be waiting patiently too! If there's anything that I can test out or help with, I'd gladly help!

Thanks for your work!
[Galaxy Note 10.1 Original Development] AdamOutler:
I run CASUALcore through about 50 separate tests which fail if CASUALcore returns results which are not as expected. A few of these tests include launching CASUAL and automating the GUI. I ran these tests last night, the night before, and the night before that. Last night I ran on Windows as well. The tests are passing.

Log or it didn't happen.
[Galaxy Note 10.1 Original Development] Just about right:
Here you go Adam. Log as requested and hopefully able to get my tablet rooted.
[Galaxy Note 10.1 Original Development] AdamOutler:
Looks like a bad USB cable or port. there is no error correction in Download Mode, so every bit must be perfect. This is different from most USB or Internet communications as they generally have error correction.

Try the latest nightly as well. Go here http://goo.im/devs/AdamOutler/
[Galaxy Note 10.1 Original Development] Just about right:
Roger that. I will try the nightly and then move to another computer that I just reflashed, so it's all new....lol.

Thank you for the prompt response and the continued great support. I will let everyone know how it goes.
[Galaxy Note 10.1 Original Development] Just about right:
Here is the second attempt, although I get the same thing on any build. For some reason the usb driver won't install. Tried on two different computers running windows 7. Can you help me out Adam? This is stressing....lol
[Galaxy Note 10.1 Original Development] Just about right:
Here is another attempt. I finally got the usb issue solved, but now I get a boot upload fail. I have tried the latest nightly, but it won't even start when I click do it.

Will keep pushing forward until I can jailbreak it with your assistance.
[Galaxy Note 10.1 Original Development] AdamOutler:
"C:\Users\JUSTAB~1\AppData\Local\Temp\CASUALJust about right-2013-07-31-14.20.44\SCRIPTS/Galaxy Note 10.1 Verizon Jailbreak\zImage"

interesting... Can you verify this file exists?
[Galaxy Note 10.1 Original Development] Just about right:
Sure does, although I had to back down to SCRIPTS in order to get into the folder of Galaxy Note.
[Galaxy Note 10.1 Original Development] AdamOutler:
OK, but if you launch a command prompt and type "dir pathToTheFileIMentioned" is it found?
[Galaxy Note 10.1 Original Development] Just about right:
After a long fight with the command prompt, I did get it all typed and it is there via CMD using administrator rights. Didn't want to take anything to chance.
[Galaxy Note 10.1 Original Development] ohnor:
CASUAL log

With the most recent update, and the previous one I tried (R744b Nightly)

I click the "Do it!" button and nothing happens except it changes to "Do it" (without the exclamation mark)

Here's my log.

My last log seemed to not have much on it since the "SCRIPTS" box was empty and I'm assuming nothing was run when I clicked "Do it." I clicked the dropdown SCRIPTS menu, but it was blank. So I pulled up the R773b--InstaBuild which is one of the 4 that shows a script. Here it is. Thanks!
[Galaxy Note 10.1 Original Development] olinz:
Not sure what im doing wrong here, have tried on 3 different machines. Im assuming its driver related but im at a brick wall as to how to solve it.

Searching for Download Mode device.

..........Executing Heimdall command.

Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna

http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is

encouraged.

If you appreciate this software and you would like to support future

development please consider donating:

http://www.glassechidna.com.au/donate/

Initialising connection...

Detecting device...

Claiming interface...

Setting up interface...

Initialising protocol...

Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.

Please be patient!

Session begun.

Downloading device's PIT file...

PIT file download successful.

Uploading BOOT

0%libusbx: error [windows_transfer_callback] detected I/O error 1450: [1450] Insufficient system resources exist to complete the requested service.

libusbx: error [windows_transfer_callback] detected I/O error 1450: [1450] Insufficient system resources exist to complete the requested service.

libusbx: error [windows_transfer_callback] detected I/O error 1450: [1450] Insufficient system resources exist to complete the requested service.

libusbx: error [windows_transfer_callback] detected I/O error 1450: [1450] Insufficient system resources exist to complete the requested service.

libusbx: error [windows_transfer_callback] detected I/O error 1450: [1450] Insufficient system resources exist to complete the requested service.

libusbx: error [windows_transfer_callback] detected I/O error 1450: [1450] Insufficient system resources exist to complete the requested service.

ERROR: Failed to send file part packet!

ERROR: BOOT upload failed!

Ending session...

ERROR: Failed to receive session end confirmation!

Releasing device interface...

Heimdall continuable error; Attempting to continue

Heimdall v1.4.0
[Galaxy Note 10.1 Original Development] olinz:
Heres the complete Execute log btw for my post above.
[Galaxy Note 10.1 Original Development] ohnor:
'libusb_error_not_supported'

Here's my log from CASUAL-R796b--Nightly. Thanks.

Edit 1:

I did find this bit about the error I'm receiving (ERROR: Failed to access device. libusb error: -12)

But I'm not familiar enough and don't understand how to accomplish this, but if I manage to figure it out, I'll post back on the results.

If someone else could explain it to me in layman's terms, it'd help a ton.

http://forum.cyanogenmod.com/topic/61639-failed-to-access-device-libusb-error-12/page__hl__libusb

Edit 2:

I found out that the "terminal" is cmd.exe, but I couldn't get the command to bypass permission to the USB working.

Here's the command from the link:

sudo chmod 666 /dev/bus/usb/00?/00? in terminal with 00?'s changed to suit your device

Edit 3:

I believe the sudo command is for Ubuntu users, or at least it's not for windows users.
[Galaxy Note 10.1 Original Development] SRobby:
So, to date, no one has had any luck with changing the recovery after the VZW OTA, correct?
[Galaxy Note 10.1 Original Development] rspong:
I had great luck, I installed version 763b, fromm Goo.im.

It went through great and fixed the Verizon update where I had lost custom recovery.
[Galaxy Note 10.1 Original Development] DarienA:
Instabuild 773b restored my root access. Thank you!
[Galaxy Note 10.1 Original Development] jfvidalc:
Nothing is working for me.
[Galaxy Note 10.1 Original Development] ohnor:
Nothing has worked for me either. I believe if I can get past the USB error, then I will have better luck.
[Galaxy Note 10.1 Original Development] jimh1999:
Does anyone have any info on root or unlock on Verizon Note that has been updated with the latest OTA? My tablet was updated when I got it at the Verizon store.
[Galaxy Note 10.1 Original Development] jfvidalc:
Here's what I've tried:

Disabled Comodo Firewall (made no difference).

Uninstalled Samsung Kies (along with the usb drivers that come with it). CASUAL doesn't recognize the GNote without those Kies usb drivers, so I had to reinstall Kies.

Tried different usb cables.

Tried different usb ports.

The first part of CASUAL works and The GNote goes into "Downloading" mode, but CASUAL then displays the following message prompt asking if I want the usb driver removed when done, and then terminates after a few of those prompts:

[DEBUG]Displaying Yes/No Dialog: CADI message: CASUAL will now install a generic USB driver.

The main error displayed is:

"ERROR: Failed to access device. libusb error: -12" error.
[Galaxy Note 10.1 Original Development] jimh1999:
I get the same result but I am on the latest update and didn't get a chance to root before the tablet was updated.
[Galaxy Note 10.1 Original Development] jfvidalc:
I was rooted before I mistakenly did the last update.

So now I'm trying to get root back, without success.
[Galaxy Note 10.1 Original Development] SRobby:
I seem to be stuck with the lib error as well, only once i got it to recognize the device as the casual driver, but then failed to upload the files to the tablet once in download mode, which at that point casual told me i needed to be in download mode.
[Galaxy Note 10.1 Original Development] AdamOutler:
Are you guys trying the nightlies at goo.im/devs/AdamOutler or the one posted? I have not updated this since the last update because I have no way to update my own device to the latest OTA. I don't have a complete flash.
[Galaxy Note 10.1 Original Development] jimh1999:
I have tried all the nightly updates on the Goo.im site, none work so far. I am on the latest OTA, no root or unlock.
[Galaxy Note 10.1 Original Development] SRobby:
So far I've tried 763b, 773b, 778b, 782b, & 796b. With no success.

Also tried removing any android type driver from my pc, tested at this point, then re-install Samsung drivers, retested, no luck.

Seems to be a driver issue with the casual driver, not really sure.
[Galaxy Note 10.1 Original Development] ohnor:
Same here. I have tried a bunch of the updates, and the nightly ones, stated above with no success. I've also tried removing all android drivers and reinstalling them through Casual with restarting my computer in between, but I still get the libusb 12 error.

Edit:

Added another debug log. So this latest release for some reason wont really even start up. Here's the debug log attached to it.

Man I'm so sad about this stupid update. I'm about to even do a factory restore just to see if it'll get me back to before the VZW update that broke my root. I've tried looking up TWRP, but they don't have anything working for the i925 as of yet and you also need root or an unlocked bootloader before you can use their recovery, (since I have a TWRP stock recovery image, but can't use it). Casual is supposed to root and unlock the bootloader, but due to this libusb error 12 thing I can't even get it to work. I've tried flashing the zImage file through odin that CASUAL comes packaged with, but I don't believe I have the other files to flash it properly.

Adam, is there anything at all we can do outside of CASUAL to bypass this error or just flash the tar/pit files or whichever we need to get back to stock and then use CASUAL from there? Or did the VZW update just prevent us from accessing the tablet all together now?

I also read in another post that the N8010 (I think) is basically the same thing as i925 but not "Verizoned." If this is the case, could we just flash that pit file to return to "stock?"

I'm trying everything I can here, but end up in frustration! Thanks for the help!
[Galaxy Note 10.1 Original Development] BRosenow:
Just does not seem to work . . .

I have attempted this (773b Instabuild) with my Windows8 PC and with my MacBook Pro and get the same failed result every time.

No Joy . . .

Log attached.
[Galaxy Note 10.1 Original Development] SRobby:
Is there some other files that would I can help you out with to get this fixed?

I posted some up a while back, just checking in, and again, thanks for all your work.
[Galaxy Note 10.1 Original Development] BRosenow:
Yea, I really like this device but would like it even more if I could get it rooted. If there is any file I can send you (without root access) I would be happy to.
[Galaxy Note 10.1 Original Development] SRobby:
Too add to it, I am rooted and on the newest version (VRAME2), and i can send you any files that you would need.

I have previously posted the stock kernel and recovery from this build a few pages back.
[Galaxy Note 10.1 Original Development] Kauffman_c:
Has anybody had any luck with the newer versions on goo.im?
[Galaxy Note 10.1 Original Development] BRosenow:
I couldn't even get most of them to run - they would connect and then just sit there. The Instabuilds would run and then error out . . .
[Galaxy Note 10.1 Original Development] needoZ:
I can confirm. Unfortunately with the latest OTA update there is no way to root or unlock the bootloader.
[Galaxy Note 10.1 Original Development] ohnor:
Status update?

I haven't had any luck either. The nightlies just hang at "loading...please wait" and it says my device is removed.

I'm not sure if there is support any longer for our version. It'd be nice to get a status update from Adam on whether or not he's planning on continuing to work on our device or if it really is no longer possible after the OTA update.
[Galaxy Note 10.1 Original Development] needoZ:
I would just be happy with an unlocked bootloader-only version. Once we have that we can install CWM or TWRP and install new ROMs at least.
[Galaxy Note 10.1 Original Development] daredevil061305:
wont let me install frodo with framaroot whats wrong??

how to use this app im on verizon and im trying to obtain root. is this app outdated? im having no luck
[Galaxy Note 10.1 Original Development] ohnor:
Yea it is outdated. It didn't work with the new Verizon update. Lots of us are unable to root out note 10.1 after receiving the update unfortunately. I don't think the developer is continuing to work on this device any longer.
[Galaxy Note 10.1 Original Development] addictivepixels:
Help us Adam! You're our only hope!

This is the droid we're looking for!: good:
[Galaxy Note 10.1 Original Development] sednafx:
+1
[Galaxy Note 10.1 Original Development] BRosenow:
Yea . . . +1
[Galaxy Note 10.1 Original Development] AdamOutler:
We are looking for the next root exploit. If you guys could, try out a few and see if they work.
[Galaxy Note 10.1 Original Development] addictivepixels:
Will do!

So far, I've tried the three available exploits in Framaroot. First two give error 9, last one freezes the app then returns to the home screen. I've also tried this exploit for the S4 on XDA, but received the "Permission Denied" error.

Anything else I can do to help/test, please let me know!
[Galaxy Note 10.1 Original Development] SRobby:
If i can help out with any files or information, I am rooted and on the latest version.
[Galaxy Note 10.1 Original Development] AdamOutler:
Cool. What did you use to get rooted?
[Galaxy Note 10.1 Original Development] BRosenow:
Thank you so much AdamOutler - we appreciate it so much and will help in any way we can.
[Galaxy Note 10.1 Original Development] addictivepixels:
Agreed!
[Galaxy Note 10.1 Original Development] jimh1999:
Casual 845b did not work for me
[Galaxy Note 10.1 Original Development] AdamOutler:
It won't work on the newer firmware. You need to either downgrade or we need a new root exploit.
[Galaxy Note 10.1 Original Development] SRobby:
I used this to originally get rooted & recovery, then i used a root keeper to backup the root, then after the OTA update just restored it.

I lost recovery obviously but i managed to keep root intact.

So i can dump any files that may be helpful. I posted the kernel a few pages back, but if I can help out with anything else just let me know.

post or PM.
[Galaxy Note 10.1 Original Development] jimh1999:
Can you downgrade after you take the OTA update?
[Galaxy Note 10.1 Original Development] ohnor:
Hmm, now here's an idea. I don't know if it'll work or not, but what do you think about trying to use the voodoo OTA rootkeeper app and trying to extract the "protected su" that it has, and then sending us the extracted version and then we try and use the voodoo OTA app to restore root?

Not that I'm aware of. I think that's what we've all been trying to figure out how to do.
[Galaxy Note 10.1 Original Development] sbrissen:
What build is the update? Is it still 4.1?
[Galaxy Note 10.1 Original Development] BRosenow:
Yea, 4.1.2
[Galaxy Note 10.1 Original Development] ohnor:
Someone feel free to correct me if I'm wrong, but I believe if we have a stock image, we would be able to downgrade to that, but no one seems to have the original stock image. Doing a factory reset will not get your device to downgrade either unfortunately.
[Galaxy Note 10.1 Original Development] sbrissen:
I made this a couple days ago, its the stock boot.img and stock system.img (except root). I heimdall'd each piece individually and it booted up fine, just need confirmation on the odin.

https://drive.google.com/uc?id=0B0yjQY6eQJd2Skk0SjdYMmlleFk&export=download
[Galaxy Note 10.1 Original Development] ohnor:
Is this the stock as in before the Verizon OTA update that broke our root or after?
[Galaxy Note 10.1 Original Development] sbrissen:
before and this is prerooted
[Galaxy Note 10.1 Original Development] ohnor:
That's great! I'm in the process of downloading it and I'll give it a shot as soon as I'm able to.

How ever did you manage to have an intact stock? You just never updated past 4.1 (or whatever the original update was?)
[Galaxy Note 10.1 Original Development] sbrissen:
I don't know how many ota's there have been but I believe this is what came on the tab stock. I've had the system files and boot img sitting around for months and just got around to making the odin files. I haven't taken an ota, had the tab for about an hour before I started work on CM :)
[Galaxy Note 10.1 Original Development] ohnor:
Is this what you did with yours to obtain the files? If so great! If not, then I just wanted to put this here in case this helps out more! It's from another thread (http://xdaforums.com/showthread.php?t=2236531&page=3) that we're on trying to find ways to get this all working. :highfive:

So I ran the file as a PDA in Odin and it made it to the end, but then said it failed. =(

Here's the message and screenshot:

<ID:0/004> Added!!

<ID:0/004> Removed!!

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> i925_stock.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> system.img

<ID:0/003> NAND Write Start!!

<ID:0/003> boot.img

<ID:0/003> FAIL!

<OSM> All threads completed. (succeed 0 / failed 1)

And if I should embed the actual picture to make it easier, please let me know. I wasn't able to find rules on embedding photos, but I didn't just in case I'm not supposed to, and just attached it instead.

And my tablet now says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." And it wont leave that screen. Hmm.. What to do now? I tried using Odin in recovery mode about 3 times so far.

edit:

Tried to use heimdall to run the image as a firmware package but it said firmware.xml not detected, so it didn't run.
[Galaxy Note 10.1 Original Development] sbrissen:
Try opening the tar.md5 with a zip program like 7zip and remove the boot.img, then try just flashing the the image with just the system.img in it
[Galaxy Note 10.1 Original Development] AdamOutler:
This exploit no longer works.
[Galaxy Note 10.1 Original Development] ohnor:
It wont allow me to open the file as an archive in 7zip. I tried winrar as well, but that doesn't allow me to delete anything. When I tried to delete it in 7zip it said, "Not Implemented." Also when I open the file from within 7zip I get the attached message.

So in essence I don't know how to remove the boot.img. Kies wont recognize my device as needing an emergency firmware update, so as for now I'm stuck.

I did manage to create a file with just the system.img file, but I got the following error message in Odin:

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> MD5 hash value is invalid

<OSM> i925stock.tar.md5 is invalid.

<OSM> End...

Please help! Thanks!
[Galaxy Note 10.1 Original Development] sbrissen:
try to heimdall the system img and then the bootimg. can you get into recovery?
[Galaxy Note 10.1 Original Development] ohnor:
In Heimdall when I try to load just the system.img by itself as a package it says: "Tar header contained an invalid size"

I recall others stating that our bootloader is locked as well. Though I'm not entirely sure what that means we're limited to.

I can get back into recovery though.

Tried using Kies again after taking my tablet apart and getting the S/N number for the "Firmware upgrade and Initialization" but even after getting the S/N it says that my S/N is still incorrect. I've already put the S/N in as many different ways as I could, including but not limited to all caps, and even adding "HEX" in front of it because some people have said that it's necessary. I've come to the conclusion that there is no firmware update for this device with Kies.
[Galaxy Note 10.1 Original Development] ohnor:
Just brainstorming, but do you think it's possible to hack kies and downgrade to stock via that? I know with the iphone there was a way to downgrade by tricking iTunes into accessing your firmware from a fake server instead of apple's servers.
[Galaxy Note 10.1 Original Development] AdamOutler:
Will someone with the latest version of the firmware, and quite a bit of common sense, see if you can obtain root using the rumrunner method here? http://xdaforums.com/showthread.php?t=2473644

I believe it should allow for root access. But, don't follow the directions, push the exploit to the device and run it.
[Galaxy Note 10.1 Original Development] jimh1999:
I will try it if you can give me a few more instructions.
[Galaxy Note 10.1 Original Development] sednafx:
Same here.
[Galaxy Note 10.1 Original Development] ohnor:
I'm not entirely sure what he means and how to go about doing it, but this is what I tried:

I followed these instructions to take the boot_unsecure.img and turn it into a flashable tar.md5 file and then used Odin to try to get it to work.

http://www.w0lfdroid.com/2013/04/android-how-to-convert-img-recovery-to.html

There's a video for the instructions here:

http://www.youtube.com/watch?v=eRYVl73kG-I

I assume we need to first be in download/odin mode on our device before we can flash it as well.

But if we're supposed to use the soju.exe file, then I'm not sure what mode the device must be in.

Once again, I'm not 100% sure this is what Adam is referring to when he says just don't follow the instructions and push the exploit, but this is what I got from it. Anyone feel free to correct me if I'm wrong!
[Galaxy Note 10.1 Original Development] sednafx:
Did you get this to work?
[Galaxy Note 10.1 Original Development] ohnor:
I don't have a tablet that is in working order to test this out. So, no, I didn't get this to work. I'm not sure if I did it correctly or not too. But I still tried to do this on my messed up tablet and it essentially gave me the error that it was unable to write or read (one or the other, I can't remember) from the device.