Hi all,
I'm trying to run kaiser-HardSPLv1 on my system but getting an error. Here's my system info:
Windows XP SP2
AT&T Tilt
ActiveSync 4.5
- AT&T Tilt is connected to USB cable and sync icon is green.
- Extracted kaiser-HardSPLv1 to a folder. Two files are in the archive: kaiser-HardSPL.exe and README.txt.
- I followed instructions as per thread and Readme.txt.
However, when I run the utility I get an error stating that prun.exe is not a recognized program (see attached image). I placed prun.exe and also pput.exe in the same directory as extracted files. When I re-run kaiser-HardSPL.exe prun.exe and pput.exe are deleted.
I also ran tried running from the CMD prompt and double-clicking on the program with same results.
Has anyone else ran into this issue? I tried this on two systems and get the same problem.
Appreciate any feedback. Want to get this working to try the HTC ROM.
Thank you in advance.
-Mike
I was able to figure out the issue for this error. Just incase anyone has a similar issue...
In the registry (HKLM\Software\Microsoft\Command Processor) there's a key called "AutoRun". I have a few commands running from there each time a command prompt is executed. The command that caused the issue was "cd \". If the directory is changed the kaiser-HardSPL is not able to extract whatever files necessary to continue the flash process.
It's an extreme situation but I hope this may help someone.
-Mike
prun error
thanks a lot
Related
Sorry for the extreme 'newbiness' of this question but I needs some help here. I just got a Google ION (32B) which I am currently trying to simply Root.
I have gone through all types of instructions and everyone leads to the same steps of applying the Recovery image through Fastboot, but when I do the steps listed after I put the phone in Fastboot, plugged it in, and run:
fastboot boot recovery-new.img
Nothing happens. I get no such file or directory. I check ADB and the phone reads just fine. I have tried on both a Windows machine - which I was able to install the proper drivers for, and in OSX, but neither will read: $fastboot devices.
What could I be missing or doing wrong. I have referred to the Wiki, Essential reading and Newbie resource
Any insight would be greatly appreciated.
Thanks
http://forum.xda-developers.com/showthread.php?t=529062
http://android-dls.com/wiki/index.php?title=Magic_Rooting
fastboot
You will have to download it seperatly.. try here:
http://android-roms.googlecode.com/files/fastboot-win32.zip
Try enable USB debugging and fastboot devices should work.
If not, your drivers may be loaded incorrectly. Installing HTC Sync usually fixes the drivers I've found.
Download recovery-new.img
Put it in the TOOLS directory of the ANDROID SDK and retry your commando.
Yeah I have actually tried all of those things. I am following the root process to a T but still no luck. Perhaps I am doing some wrong in the command line?
have you set the $PATH variable? you get this:
"I get no such file or directory."
Click to expand...
Click to collapse
error-message. my best guess is that you have forgotten to added the path to where your fastboot tool is located.
try changing the directory to where your fastboot tool is located.
*Fixed*
I really appreciate the help guys, I redownloaded the fastboot.exe, and it read the phone right away. Now to start loading ROMs
My Transformer informed me of an OTA update, which I tried to perform. It stuck on the boot screen and wouldn't go any further. I managed to wipe it and get it going again by switching off and pressing power and volume down, so I rebuilt it and it again wanted to do the update - with the same result.
I tried side-loading the update and again, it froze, so I downloaded and ran NVFLASHTF and now I can't get anything on the display whatsoever. All I can do is connect it to my PC and it makes the familiar connection sound and I can get to the SD card, but nothing else.
I need someone to show me what to do step-by-step as if I was completely stupid (which I obviously am!).
Please help if you can.
TIA
the nvflash sticky in the dev section includes a youtube video.
although the most likely reason your nvflash didn't work, is you extracted the files in the wrong place. make sure they are in the same place as the download.bat file.
Sent from my Transformer TF101 using Tapatalk
I have all the nvflash files in the same folder as extracted from the .zip file. I even have Prime 1.6 in the folder.
All I seem to be able to do is press the power button and either Up-vol or down-vol (or both) and the computer disconnects and immediately reconnects. When I run the download.bat file, it seems to run and complete the formatting and then download something and the dos box disappears at that stage. The tablet is showing the following...
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: 027c100040a0b2d7
Click to expand...
Click to collapse
That is the only thing I can get to display - and, of course, it stays like this until I try to reboot again.
copy and paste what you get when you run the batch file into here...once it finishes
Pretty sure the tf should reboot on its own if done right.
Did you also check the md5sum of the downloaded files?
I followed these instructions..worked perfectly
http://tabletroms.com/forums/transf...ock-3-1-stock-3-2-recovery-roms.html#post9968
The Dos box disappears when it finishes so I can't paste it here and yes, I checked the files. In fact, I tried it on three different PCs (W7 64-bit, W7 32-bit and XP Pro 32-bit), all without success.
Have you plugged it straight to power and switch it on?
Yes - no difference.
I think you need nvflash experts help.
Only thing i can think of is the old adb way to transfer a blob file...
Or...
Open a command prompt and go to the directory with the batch file and then run it ..dont double click but just type it in the dos window.. once it finishes it shouldn't close the window and you can see what happens.
maybe try a different usb port, I have 4 ports on the front of my pc but for some reason only ONE port works when i try to nvflash,also have problems if I use a hub or extend the cable in any way
Malandro2011 said:
I think you need nvflash experts help.
Only thing i can think of is the old adb way to transfer a blob file...
Or...
Open a command prompt and go to the directory with the batch file and then run it ..dont double click but just type it in the dos window.. once it finishes it shouldn't close the window and you can see what happens.
Click to expand...
Click to collapse
Ok, the second option got me a little bit of info. Bootloader.bin is installing but it is telling me that the file 'recovery.img' is not found.
you can prevent the dos window from closing by starting the command via command line.
start > run > cmd (enter)
dir c:\where\nvflash\is\located (enter)
download.bat (enter)
OK, it's official - I'm an idiot!
I had downloaded the nvflash version of Prime 1.6 but hadn't extracted the files! I now have a working version of Prime 1.6 and am restoring the data as I type.
Thanks for all your help, especially the suggestion of running download from a dos prompt, which let me see where I was going wrong.
Excellent!
Glad it's all sorted
Ok, I have had multiple Android devices and have never had a problem with any of them with adb however, my computer had done some weird thing and every time I opened SDK Manager, it would open, but then time out and freeze..
SO.
I uninstalled both java development kit, and sdk manager, but now the manager wont open at all.. It just flashes a command prompt and exits out... So I ran the android.bat batch file in a command window, and i got this error
'xcopy' is not recognized as an internal or external command,
operable program or batch file.
ERROR: SWT folder 'lib\x86_64' does not exist.
Please set ANDROID_SWT to point to the folder containing swt.jar for your platform.
If anyone can help me, I would be much appreciated, I just got two new devices this month. I was able to root my SGS2 before, and now I am trying to root my Kindle, and all this is happening... Any help would me much appreciated...
Oh, and I did check my system32 file, and I do have xcopy in my system files
UntamedDeviance said:
'xcopy' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Do you know if "C:\Windows\System32" is in your Environmental Variables Path? My friend had this problem recently, and for some reason it wasn't in there. We added it to the path, and everything works fine now.
EDIT: Here is a link to a tutorial on how to fix this error: http://helpdeskgeek.com/how-to/fix-not-recognized-as-an-internal-or-external-command/
Might try executing the command from a CMD window set to the directory where the files are as a quick test. I agree with checking the Env. paths too.
Hi,
I'm trying to root but getting the message 'adb not recongised as an internal or external command, operable program or batch file'. What does this mean? I've installed fastboot/flashmode and z3 drivers via flahstool. Am on UK Generic .98 firmware.
Thanks
Ok did some googling and found it was to do with the paths in windows. Updated environmental variables as per the below:
http://www.google.co.uk/url?sa=t&rc...0_IbQh9eEAUHHz45h5DM6_g&bvm=bv.87611401,d.cGU
So in mine, I've got SDK tools saved down in C:\Program Files\Tools and have set up my variable as ANDROID_TOOLS pointing to there, then ANDROID_PLATFORM_TOOLS pointing to their location in C:\Program Files\Platform-Tools and then set Path as %Path%%ANDROID_PLATFORM_TOOLS%;%ANDROID_TOOLS%
But when I run the rooting tool I now get 'The system cannot find the path specified' then *daemon not running. starting it now on port 537* then *daemon started succesfully* it begins sending files and then get several 'cannot stat' and 'unable to open' messages before the final:
'Error: Seems your kernel / device is not supported /system/bin/sh: data/local\tmp\getroot: not found
I am now on Global Generic firmware .23.0.a.2.93. Model is D6603, not locked to any carrier, and bootloader is unlockable.
Can someone please help? I need to get rooted ASAP as I'm home visting family before the weekend and said to my dad I'd root his phone before I head back to London.
Thanks.
Never mind - solved and now rooted! Absolutely no idea how - something within the extracted version of giefroot tool was extracted further to somewhere else, ran the tool again and it worked!
I am trying to root my new Pixel 7 Pro, build number TD1A.220804.031, but have run into an issue. Let me explain what I have done and where the issue arose:
I am following the instructions here: https://www.xda-developers.com/how-to-unlock-bootloader-root-magisk-google-pixel-7-pro/. I found the factory image for my phone, downloaded it, then downloaded/installed the Payload Dumper Tool, extracted init_boot.img, copied it to my phone, patched it using Magisk, and copied it back to my computer. Took a bit longer than expected, but no problems.
Via the phone’s setting, I enabled OEM Developer options and then allowed OEM Unlocking. Again, no issues. I then turned the phone off, attached the phone to my computer using a USB cable, and then booted it so that the bootloader menu was visible. In a command window on my PC, I then ran ‘fastboot flashing unlock’. I think this worked (because, when I restarted the phone, I had to go through the whole initialization process again).
The next step is where I ran into the problem. The first time, I put the modified init_boot.img in a new folder on the C: drive, but when I ran ‘fastboot flash init_boot path/to/magisk_patched.img’, I got the error “fastboot: error: cannot load <patched file>: permission denied”. So, then I copied the file to a folder on D:, ran the same command, and got the same error.
I suspect that I missed a step or something equally silly. Any suggestions as to what I should try or any pointers to other rooting guides that might be helpful? Don’t know if this means anything, but when the phone was powered off and plugged into the computer, I tried ‘adb reboot bootloader’ but nothing happened.
When you reboot, do you get the orange triangle with exclamation in it?
it might just be easier to move the magisk_patched.img to the platform-tools folder (the same folder that has adb.exe and fastboot.exe); if you are having "permission" issues from Windows, but you aren't from adb or fastboot, then supposedly having it in the same folder should run it under the same permissions.
Also, make sure that you run CMD as an elevated prompt; search for CMD, right-click, and "Run as administrator" -- this might help with the permission issues as well.
Final suggestion is to be sure to run platform-tools version r33.0.3...
Good luck and hope this helps...
P.S. Also, you might've had better luck and/or it's better organized if you posted in the Pixel 7 Pro (cheetah) forum instead of the Pixel 7 (panther)....
Use Pixel Flasher. Less hassle, more convenience.