Database Info

Samsung Transform

The Samsung Transform has the same vulnerability as the Epic (joeykrim-root.sh works to get root).

So how would I go about rooting? Would I use the same process as the EPIC 4g?

if you're good with linux, you can follow the directions in this link forum.sdx-developers.com/epic-development/adb-root-exploit-test
(The mount command is slightly different in step 4.)

I'm running a mac. I tried several guides on the sph-m910 rooting for mac osx but it won't let me push any files to the phone with adb.
Sent from my SPH-M920 using XDA App

Have any of you successfully rooted it using this method?

I have successfully rooted my brother's Transform using the same method I used to root my Epic 4G... same files and everything.

aliendude5300 said:
I have successfully rooted my brother's Transform using the same method I used to root my Epic 4G... same files and everything.
Click to expand...
Click to collapse
Here's a link to the zip file containing the exploit that worked: http://www.filedropper.com/ocr

drivers?
What drivers are you guys using? i cant get any drivers to install...

mark920 said:
What drivers are you guys using? i cant get any drivers to install...
Click to expand...
Click to collapse
From what I am told and understand it must be mounted and run in linux. I will find out as soon as my local store gets one in, I'm first in line.

aliendude5300 said:
I have successfully rooted my brother's Transform using the same method I used to root my Epic 4G... same files and everything.
Click to expand...
Click to collapse
Any link to the method you used?

aliendude5300 said:
Here's a link to the zip file containing the exploit that worked:
I've tried 8 times, cannot get it rooted. Suppose I'll wait just like the rest of us
Click to expand...
Click to collapse

berger1980 said:
aliendude5300 said:
Here's a link to the zip file containing the exploit that worked:
I've tried 8 times, cannot get it rooted. Suppose I'll wait just like the rest of us
Click to expand...
Click to collapse
I tried it as well. I couldn't get it to work either.
Click to expand...
Click to collapse

I got it to work. I tried it under my computer with Windows 7. I had to right click the run.bat and click properties, Click compatibility, Run this program in compatibility mode for Windows XP Service Pack 3. Thanks.

cachorropedorro said:
I got it to work. I tried it under my computer with Windows 7. I had to right click the run.bat and click properties, Click compatibility, Run this program in compatibility mode for Windows XP Service Pack 3. Thanks.
Click to expand...
Click to collapse
I don't mean to be a ****, but what app have you installed that requires root access? I have a specific one, roam manager, that will not run. I believe you may have seen visually that it was rooting it, but it does not do squat.

berger1980 said:
I don't mean to be a ****, but what app have you installed that requires root access? I have a specific one, roam manager, that will not run. I believe you may have seen visually that it was rooting it, but it does not do squat.
Click to expand...
Click to collapse
apps2sd, I need a new kernel for wifi tethering which is the main thing that I want

Rooting Help
Can someone give some detailed instructions on rooting the Samsung Transform???
I agree with cachorropedorro, I'm looking to root for wifi teathering also..... Tried a few methods also.... No luck.

Guys, I've never rooted a phone before and this is my first android. I looked a the Joeyconway version of root.... I'm having a hard time following the command prompts??? Any suggestions?

Is there going to be a transform category? Are there other pages about rooting this new phone??

I was able to root my transform using the ocr joey krimm root method, the drivers for the epic finally worked after restarting the phone, one thing i noticed about the transform was that the ratc script takes longer to work and does not always work. I modified the bat file to have a longer wait after running the ratc file, however that doesnt even work all the time, if you manually run the ratc script and then run the bat it should work thats what i had to do. I also updated the su bin and the busybox version from the current version of the one click root because the files in the ocr.zip have an older su bin that doesnt use superuser.apk and the busybox is not compatible with ti backup.

Mark920,
Can you give some more detailed directions for all of us that are newbees? Like I said in a earlier post, I've never rooted a phone so some of the things you were talking about like ratc script confuses me. Any detailed steps would be awsome.

One click root app!

Hello guys, as you know, the latest one click root that worked on the Transformer was SparkyRoot. Well, with the newest EeePad update (9.2.1.21), it is impossible to root without PC. Well, I have completely cracked the EeePad code. You will be amazed with the options included in my new one click root app. Try it and see for yourself! (Also works on TF201 and SF101 slide) Here is the download link. http://depositfiles.com/files/jp4hcc5ze

That's great to hear. To bad I'm already rooted so I can't try it.
Should make it easy for those needing to root if it work.

Didn't work set cpu and titanium back up didn't work
Sent from my Transformer TF101 using Tapatalk 2

First off..thanks for giving it a go..
Looking forward to hearing some solid reports.
You might want to put a little more detail into your OP..
As your post count is not up and your other threads are still feely new..
I am looking at picking up a new TF B60 next week and if this works as it should,of course will be willing to give it a go..
Sent from my Transformer TF101 using Tapatalk

Yes, there are problems with it. It seems to give partial root access, but not full root. I am working hard to fix the bugs. For some reason, root apps aren't detecting the root, but I was able to edit system files with no problems. The undetected installation for apps works, and transforming the tablet into Linux and MAC work. For some reason, windows is glitching up. Any ideas on how to get apps to detect root?

When i see partial root usually the su is not getting install to system/xbin but it is in system/bin. See that with the OTA root keeper sometimes.

Any movement or progress on this?
Sent from my SGH-I897 using XDA

baseballfanz said:
When i see partial root usually the su is not getting install to system/xbin but it is in system/bin. See that with the OTA root keeper sometimes.
Click to expand...
Click to collapse
Can you move it manually via terminal from bin to xbin? If so does that get you a full root?
Sent from my PG41200 using Xparent Purple Tapatalk 2

bsoplinger said:
Can you move it manually via terminal from bin to xbin? If so does that get you a full root?
Sent from my PG41200 using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
I don't know how this apps work but with OTA Rootkeeper you can copy su from system/bin to system/xbin and that solved it most of the times.

There is still bugs in this app. I am working hard to fix them. The su is in xbin, but still not full access. I heard undetected installation is known to glitch up and corrupt files. Maybe I need to remove undetected installation and do normal installation. But when you do normal installation for superuser (through app) it says "There was a problem parsing the package". Maybe use an alternative package installer?

Have you gotten any further in developing your app?

Yes, I got the windows transformation working. Few apps are detecting root, though. Screenshot apps detect it, and a few root managers work as well. Most arent detecting it, though. Also, syncing files doesnt work...

I have my one-click done, it's in my sig and called PERI.
Uses symlinking as found by wolf to grant root.
I'll be making an on tf app too soon. This is all completely open source and 100% working on the 3 tf101 based tfs. You can take a look at the code if you like, it's very simple.

Yes, I am familiar with PERI. PERI isnt an app, though. My Asus Root Menu is a one-click from the device-No PC required.

The commands can be run On-Tf, and I'm in progress of developing an app to put on the TF right now. Should work with 100% success. Then finally out of beta. If you need any assistance with building yours too I'm willing to help.
EDIT:
--
And dude, you're running into problems I almost GUARANTEE, because you're using andromo. Those 'make apps no coding required' wysiwyg tools are total junk. Code it the old-fashioned way :]
What method are you using too Root? I couldn't find any actual commands that are run by your app, just a bunch of invoke pages to text with nothing really attached too it except some ads stuff.. I apologize if I missed it.
And how in the world did you get linux/mac and windows 7 on there if the apk is only ~276KB A system image installer for the Ubuntu ARM image mabye, but there isn't an image for windows or mac (and both are closed-source).
--
Superuser needs to be flashed via recovery/bootloader/adb in a non-locked environment. This is probably where the problem parsing package error comes from.
--
Has anyone sides the OP gotten this too work even partially?

Yes, it has partially rooted a few people, and some people got full root. I have recieved many pm's about it. How is your app coming along?

[Q] FileMate Clear 7" T720 tablet

Does anyone know if Z4Root will work on this tablet? Thanks!

I've been looking for one for 3 days now, I tryed onclickroot and z4root or something like that,, cant find anything Anyone please help!!

I'm still waiting for my tablet to be delivered...I'm gonna try SuperOneClick (crosses fingers)

I got one of these for my daughter for xmas. I spent a few days trying to root it with no luck. I'm not intimately familiar with android (some unix experience), but I tried all the options I could find for rooting Allwinner a10 devices. At first I ran into problems with adb unable to recognize the device for most one-click methods. I downloaded the android tools and was able to connect with the included adb. After studying the scripts, they all use the "adb root" command to gain root access on the device and copy the necessary files. Unfortunately, this command fails using adb from the tools. At first I thought this was due to my adb version, but after doing some research I think it is actually due to the device kernel. I believe it requires reflashing or some exploit to be able to gain root. I was able to install root explorer and I can browse all the necessary directories but I can't modify or copy the necessary files into them. Busybox told me there was an older version installed, but wouldn't let me install a newer version (again I think due to the permissions). Also, superuser would say it installed but the su binary did not show up on the bin directory. As the necessary directories are all owned by root, I couldn't figure out a way to modify the permissions...

I wound up returning the FileMate and got a Lenovo IdeaTab. Got that rooted in no time.

sorry i never saw this post i've bought 2 of these and i rooted them,
i wish i could get a better build for them though, too many app crashes and the internet connectivity sucks
i used a method by Bin4ry called root with restore, v17 worked any ways i have the zip if you would like it

ferny_dx said:
sorry i never saw this post i've bought 2 of these and i rooted them,
i wish i could get a better build for them though, too many app crashes and the internet connectivity sucks
i used a method by Bin4ry called root with restore, v17 worked any ways i have the zip if you would like it
Click to expand...
Click to collapse
Screw it, here it is for future reference.

How'd you do it!?!?
ferny_dx said:
Screw it, here it is for future reference.
Click to expand...
Click to collapse
FileMate Clear T720
Thank you very much for being the only person ever to have posted in regards to this tablet. I just got mine for christmas and have been trying to get it rooted. I've tried a lot of those one-click methods, and I've even tried this Bin4ary method. but it just hangs up on "daemon started sucessfully*"
Can you please direct me to the filemate drivers (if needed)
also, I have usb debugging endable, allowing 3rd party (not secure) files enabled. and pulling my hair out (enabled).
Thanks again.
Also, I'm running windows 7 and 8, (((maybe i should try win7))) hmm. i'll get back to you on that. Anyhow, any advice would be greatly appreciated, since returning it doesn't sound very fun.

jiberish05 said:
FileMate Clear T720
pulling my hair out (enabled)..
Click to expand...
Click to collapse
I laughed so hard. ok your going to have to install drivers by force,
first off do you happen to have android sdk installed? if you don't there is another way but its going to sound weird,
if you do have the android SDK installed:
1. go to your computer manager (by opening explorer, right click on the "computer" group on the left column and select manager)
2. look for any unrecognized item that appears, ( it will most likely be labeled "Clear" with a faded icon and a "?" sign on top
3. right click and choose "Update drivers", it will give you options, choose "Browse my computer for driver software", another option screen will show,
4. at the bottom of the window there will be an option that says "let me pick from a list of device drivers on my computer"
5. on the screen that appears there should be an option that says "ADB Interface", choose this
6. choose "Google, Inc.">"ADB Testing Interface version x.x.x.x" (I chose version 2.1.0.0)
that should do it next time you plug in the tablet try running ddms or open the cmd and type in "adb devices" (assuming you have adb installed) and it should show.
if this helps just hit the thanks button
[edit] I am running windows 8 btw [/edit]

ADB interface doesn't show up
Thank you very much for getting me farther, however I dont see ADB interface. I'm looking into it right now. I just re-installed the sdk drivers and will keep at it.
BTW, is it even worth doing this? the main reason I want to do it, is so i can connect my ps3 remote via bluetooth, and possibly a little overclocking. Have you had any luck OC it?
Thanks again Much appreciated:good:

jiberish05 said:
Thank you very much for getting me farther, however I dont see ADB interface. I'm looking into it right now. I just re-installed the sdk drivers and will keep at it.
BTW, is it even worth doing this? the main reason I want to do it, is so i can connect my ps3 remote via bluetooth, and possibly a little overclocking. Have you had any luck OC it?
Thanks again Much appreciated:good:
Click to expand...
Click to collapse
open up SDK manager and go to Extras>"Google USB Drivers"
also install everything in the "Android 4.0 (API 14)" section, I have other options installed if this still doesn't work.
its worth it just for the extra stuff that root comes with like titanium backup, but you cant over clock, if you go any higher than 1200 MHz it will lock up and you have to force it to reset.

cyberkeeper1 said:
HERE is the link to root as provided earlier
Click Here to download ADB universal drivers. they should work better than the google USB drivers.
---------- Post added at 12:20 AM ---------- Previous post was at 12:11 AM ----------
this seems kind of spammy. What backs up my claim is that you dont have more than 5 posts...
Click to expand...
Click to collapse
Thanks for the link to my post on android central, the link in that post just comes back the xda thread
Root MANY ANDROID! [Upd: 20.11.2013] - Added Z1 Root
Sent from my XT862 using Tapatalk

Rooted Filemate Clear
I just wanted to confirm I have also rooted the Clear with the Bin4ry v33 exploit using option 1. Although I received the following error:
remote object '/system/bin/ric' does not exist
.
Going to copy files to it's place
Rebooting again, please wait!
Could Not Find C:\Documents and Settings\Graham School\My Documents\Downloads\Ro
ot_with_Restore_by_Bin4ry_v33\ric
Restoring previous Backup! Please select the RESTORE MY DATA option now on your
device!
SuperSu installed and root apps working.

Rooted With Kingo
I just bought one of these cheap to play with and used Kingo to root it. Worked first time, no problem. The only issue I am having is that the SuperSu binaries are failing to update but root is still working. Titanium is working and Root Explorer so I can debloat. Hope that helps is anyone is still trying to use these

Jfender1005 said:
I just bought one of these cheap to play with and used Kingo to root it. Worked first time, lem. The only issue I am having is that the SuperSu binaries are failing to update but root is still working. Titanium is working and Root Explorer so I can debloat. Hope that helps is anyone is still trying to use these
Click to expand...
Click to collapse
please tell me where in the world you got the Kingo root?
As far as being unable to update binaries, try to find a custom recovery and install. From there, you can inject them via su-binary update.zip and bam!

Kingoroot
cyberkeeper1 said:
please tell me where in the world you got the Kingo root?
As far as being unable to update binaries, try to find a custom recovery and install. From there, you can inject them via su-binary update.zip and bam!
Click to expand...
Click to collapse
http://www.kingoapp.com/android-root.htm
That is the link for the Kingo site. The first time I saw it on here there was some question about whether it was safe becase it is not open source and used a Chinese SuperSu app. I felt safe using it on a tablet because I do no banking on it or anything, but the newest posts I have seen are that Kingo is safe. Hope that helps. And if you know where to find a custom recovery that will work with this app please let me know.

[Q] NEC Medias W N-05E root? (dual screen phone)

Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!

bohemianRhapsody said:
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
Click to expand...
Click to collapse
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.

root is easy
bohemianRhapsody said:
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
Click to expand...
Click to collapse
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition

it0 said:
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
Click to expand...
Click to collapse
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?

Lukas_a_1996 said:
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Click to expand...
Click to collapse
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.

it0 said:
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
Click to expand...
Click to collapse
Thanks for the reply . I tried to run the command in impactor but whatever i do i get "Signature bugs unavailable" could it be that i have the wrong ADB drivers installed or is my Impactor setup wrong?
Edit: yeah im running 4.1.2 Build A1001231

You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.

it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
All the adb commands basically work but nothing works with impactor i just get error

it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
Bump!

How to Root Medias N05e
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks

nguyenbuulam said:
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
Click to expand...
Click to collapse
There is a way for temp root N05E, basically u can use pm disable command or other su stuff. But u cannot mount system rw right now.

Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working

How to enter recovery mode?
Despite starting this thread, in the end I never did bother to attempt rooting.
Anyway, unfortunately now the phone refuses to boot. Not triggered by anything obvious, haven't installed any new software recently, etc. Just hung one day and then when I removed and re-inserted the battery, it won't get any further than the "docomo" splash screen. I.e. the OS doesn't appear to be getting bootstrapped at all. The "docomo" splash screen appears and disappears then the phone sits there with both screens powered up but blank.
As it happens, I had ADB Debug enabled in the developer options at the time, so I've tried to see if I can adb shell into the device, but no luck. Not surprised as it's clearly not getting far enough into the boot for that to work.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?

bohemianRhapsody said:
Despite starting this thread, in the end I never did bother to attempt rooting.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
Click to expand...
Click to collapse
In recovery mode, clear cache, etc..
To get there hold volume down and power at the same time,then you'll see the broken android then wait/ press vol down a couple of times to see the menu.

GRbit said:
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
Click to expand...
Click to collapse
did you ever figure out the recovery keys?

hamishhhhs said:
did you ever figure out the recovery keys?
Click to expand...
Click to collapse
No I didn't(
I'm actually sold this phone and lost interest in the topic.

GRbit said:
No I didn't(
I'm actually sold this phone and lost interest in the topic.
Click to expand...
Click to collapse
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far

hamishhhhs said:
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
Click to expand...
Click to collapse
Sorry, but this was too long time ago. Nothing left

GRbit said:
Sorry, but this was too long time ago. Nothing left
Click to expand...
Click to collapse
how would j be able to get the files from my phone?

hamishhhhs said:
how would j be able to get the files from my phone?
Click to expand...
Click to collapse
I dunno man.
I've already described (in the first post you have quoted) what I achieved with this github repo https://github.com/android-rooting-tools/android_run_root_shell . That's all I've got.

Windows RT 8.0 Recovery Environment Jailbreak

This is a version of the 8.0 jailbreak that will run in the recovery environment. This is meant more for developers than end-users.
It does not force a two minute wait at the start, but that is still required.
As always, it was developed for a Surface RT. Vivo tabs, etc..., your mileage may vary. I developed it targeting the Windows RT 8.0 image that MS uploaded after the 8.1 upgrade issues. I don't know if this varies from the stock image, I don't have it anymore.
I'm also curious as to if it'll run on a Surface 2 in the recovery environment. If anyone can test, I'd be grateful.
The trick to getting cdb and whatnot to run was plugging in valid certificate catalogs for cdb (and some other tools).
It also doesn't work with the side volume keys, though it does work with the volume keys on my Type 2 keyboard.

I think you need to add an batch file to download the symbol. The preloaded one may not work on some other tablets.

LolitaPlus said:
I think you need to add an batch file to download the symbol. The preloaded one may not work on some other tablets.
Click to expand...
Click to collapse
There is no Internet in recovery mode. If you can send me aystem32\ntkrnlmp.exe and system32\ci.dll for your recovery I can add them.

netham45 said:
There is no Internet in recovery mode. If you can send me aystem32\ntkrnlmp.exe and system32\ci.dll for your recovery I can add them.
Click to expand...
Click to collapse
However you can run it under normal Windows RT environment, don't you? I know there is no internet so I said it should be in another file.

LolitaPlus said:
However you can run it under normal Windows RT environment, don't you? I know there is no internet so I said it should be in another file.
Click to expand...
Click to collapse
You can't get at the recovery files easily from a full system either.

netham45 said:
It also doesn't work with the side volume keys, though it does work with the volume keys on my Type 2 keyboard.
Click to expand...
Click to collapse
So, seriously, that was my mistake. I only try to use side volume key. And I delete all my work for recovery jailbreak yesterday. Want to cry now. :crying:
Thank for your work, again.
netham45 said:
There is no Internet in recovery mode. If you can send me aystem32\ntkrnlmp.exe and system32\ci.dll for your recovery I can add them.
Click to expand...
Click to collapse
Is there anyway I can done it myself?

LolitaPlus said:
However you can run it under normal Windows RT environment, don't you? I know there is no internet so I said it should be in another file.
Click to expand...
Click to collapse
I get what you're saying, misread your other post. I don't have my device in a bootable state right now, but once I get it fixed up I'll make a .bat you can run to dump the PDBs for the other kernels.

hisoft said:
So, seriously, that was my mistake. I only try to use side volume key. And I delete all my work for recovery jailbreak yesterday. Want to cry now. :crying:
Click to expand...
Click to collapse
That really stinks. Sorry for your loss.
Assuming we have a way to run unsigned code, does anyone have a way to perform raw reads of a block device? I don't think there's any way to do it with managed code, and my development skills only extend a little into that. I figure there should be a way to compile C++ for ARM though. It might help you recover some of what you lost.
Also, it might help us get deleted files off system partitions. A few of us got lucky in getting Vivotab RTs that didn't have signing files deleted. If we could boot from a USB stick and undelete them, then just about everyone could have them...

nice work and a useful way to boot an RT8.1 system into an 8.0RT RE + jailbreak system
I had to get the correct symbols for my Sept 2012 kernel
You have to unlock the os drive if system has a Live account and it is Bitlockered
I usually skip that and run a batch file
manage-bde -unlock c: -recoverypassword xxxxxx-...
WindowsRE RT8.0
doesn't have a full windows environment or full win32 api (obviously) and no network (so far)
but can run many unsigned RT desktop apps
eg
putty
Strangely it can't run RT8.1 standard OS utilities -- must be some version number etc in the header it doesn't like
I might look into a way to dual boot it from HD (rather than booting from a USB) in due course

This is awsome! Been waiting for some update on something about RT jailbreaking even though it's in a RE environment.