When I try to extract it to the proper location as per the GingerBlur instructions, it returns an error message in 7 zip stating:
can not open output file C:\retainroot\GladRootv4.2\*
with the * being replaced by numerous files that it displays the same error message with.
Specifically there's 11 errors and all of those errors state the same thing but with different files.
Those files are:
bin\su
afterupdate.bat
gladroot.bat
unroot.bat
bin\backupsu.sh
bin\restoresu.sh
unroot.sh
Superuser.apk
adb.exe
AdWinApi.dll
AdbWinUsbApi.dll
I'm scared to proceed with the rom-ing unless I get these error messages cleared up.
EDIT: Alright, so it seems I can extract the files to my desktop and then move them to my C drive. Should I proceed?
Related
I have Vista Home Premium 64bit and I did download WinRAR 64 bit edition. Whenever I try to install that there claims to be a corrupt file and I have downloaded it a few times from a few sites.
So I go back to the 32 bit version of WinRAR and that installs fine, but reminds me for better performance to use the 64 bit version.
Now, whenever I extract a ZIP or RAR file the Update.exe is missing or I receive a message about the CRC security not matching. AND if and only if I can get the files extracted when I try to install the ROM the Gtab is constantly stating a "status 7" error. I have tried TNT, VEGAn and 1 other ROM and each will not install.
Is there anyone who would be willing to use Skype or some other means to assist me in getting the tablet back up and running something, even if that's the stock ROM?
I do have Clockwork Mod installed already, that was the only thing that seems to have installed correctly.
Thank you in advance,
Brian
If I undertsand correctly: Youre trying to extract the contents of the "update.zip" file that comes as part of the ROM download?
If so.. you dont extract it, you leave it as "update.zip" in your sdcard directory.
I remember seeing a "pictoral" view of what your filesystem should look like in this xda somewhere. Ill try to find it.
No, I am having problem extracting the ROMs from Zip or Rar, so I went and downloaded Memtest86 just to see if there was a RAM problem. That checked out fine after an hour of testing.
Most every Zip or Rar I try to extract have CRC errors, even if it's unrelated to this site. But part of that causes the Update.zip not to extract at all and I only get the "recovery" folder and Command and the Update.zip had an error and doesn't extract.
I then tried it on a laptop with Win7 and I could extract some files then more errors, then I tried a Win XP laptop and that seemed to extract the files fine.
My latest is now the Gtab is bricked, stuck trying to install recovery that never ends. So I looked up for the USB driver and nvflash and the ROM that goes with that and the Gtab doesn't show up as a removable drive so I can transfer the files on there. I have copied them to SDcard but I can't get that to read the data.
So, at this point the Gtab is looping and I cannot get back into Clockwork or get it to show as a drive using the USB drivers and the -Vol and Power button.
Currently when I just power on the tablet in red text I get:
Magic value mismatch:
:"
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002).
FIXED
PROBLEM FIXED.
I saw another thread stating similar problem, located here http://forum.xda-developers.com/showthread.php?t=1026757 and followed the advice of a few people and now the Gtab is working again. Its stock ROM but the main thing is it's working again.
I am trying to get my viewsonic g tab back to factory. I installed the APX driver ok, and downloaded the applicable files. I try to run the nvflash_gtablet.bat script and it comes up with a file configuration error that the file can't be found. I am running windows 7. Any suggestions?
i have never done nvflash and never got brick and loaded multiple roms and went on dif dev branches
this is for 1.1
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip
and this is for 1.2
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-4349-user.zip
rename the zip file to "update.zip"
hopefully you partioned your tab before nvflashing it. if not then please ignore this.
put update.zip in root of your sd card.
create a folder named "recovery" and place an empty file named command with this text inside
Code:
--update_package=SDCARD:/update.zip
then go into recovery and let it update.
hope i helped somewhat
ps to make files in win 7. i open notepad and paste code then save a command.tmp then i go and delete tmp. it leaves it as a file. and works
Jrome86 said:
I am trying to get my viewsonic g tab back to factory. I installed the APX driver ok, and downloaded the applicable files. I try to run the nvflash_gtablet.bat script and it comes up with a file configuration error that the file can't be found. I am running windows 7. Any suggestions?
Click to expand...
Click to collapse
h i because you didn't have the image files to flash into. This is probably the most common mistake that beginners make.
Go to my website linked in my signature and go to the start here page. You're probably a code yellow.
Ok, this will be a bit of a technical thread, so bear with me. This is so people have an understanding of how to find and look at the update files that get put on a phone. If you are reading thru this, I will assume that you have a basic understanding of ADB and possibly of shell commands like ls and cd
When you go into settings -> About Phone - Software update, your phone does many checks to the file system. One of them is at a file /data/fota/ipth-muc.prop . Most people do not know this directory exists as when you are in ADB you can not do a list command on the /data directory without root. This file is re-created each time you boot your phone. If we do the following command, we can dowload the file to our computer:
ADB pull /data/fota/ipth-muc.prop
If we open the file, it will look a lot like this.
firmware.version=VS920ZV3
max.pkg.size=157286400
This file can also contain additional data. The string we want to add in there is where to download and place update packages. This can be defined as such:
pkg.location=
If this line does not exist, it will default to /cache/fota . Being as we can not cd into /cache or pull/push files there, this is a bad spot to put it. How ever, we can make directories and read/write to them under /data/local . Using this info we can do the following.
ADB shell
mkdir /data/local/temp
exit
From there, we can edit the original ipth-muc.prop file we pulled to look like this:
firmware.version=VS920ZV3
max.pkg.size=157286400
pkg.location=/data/local/temp
If you edit the file, use a true file editor. Notepad will not save it correctly, but Wordpad had no issues. From there we do the following
ADB push ipth-muc.prop /data/fota
Now when we do the update, it will place the downloaded files into our temp directory (note, you must do this after the phone is fully booted, but before you have the phone look for an update). Once the files are done downloading, click remind me later. Then we can go into ADB and pull the files.
ADB pull /data/local/temp
You will get two files. One will be the update "ipth_package.bin" and the manifest files "ipth_package.bin.dd" . The manifest file also contains the link to the original file name as link to it on the host server. The ipth_package.bin file is a simple zip file that can be opened with almost any archiving program.
The zip is signed by LG using their personal key, so modifying it and pushing it back to the phone is not currently possible. We can however see the contents of an update and see what is being change. I hope to use this in the near future to either break the LG key or find a way to find a glitch in a patch being done.
Hi,
I've crosscompiled a couple of useful command line applications (including binutils, gcc, make) to Android -- they work fine if I just move all the files to an Android device, or run them from an SD card etc.
Now I'm wondering what the best way to package them is -- last time I checked, an APK couldn't contain files in /system/bin or the likes, so if I want stuff installed in standard locations, that rules out using an APK (obviously that could be worked around by creating an empty app and just including all related files in the data storage area, and live with the fact that the files aren't where they ideally belong, as long as PATH is set correctly, shouldn't matter too much -- or do any devices mount the data area with the "noexec" bit?).
The other possibility I've considered is just making it a zip file to be installed through custom recoveries - unfortunately I'm running into problems there: trying to use ClockworkMod Recovery 6.0.1.0 on a Galaxy Nexus to install the zip file results in "Installing update..." immediately followed by "Installation aborted." -- that's despite the fact that signature verification works fine when enabled (I've used signing-tools to sign the zip file. Other than the META-INF directory created by signing-tools, the zip file contains system/bin/gcc, system/bin/make and friends). Am I doing anything wrong there?
And, of course, is there a third, even better, way to package command line tools that I'm missing?
Hello.
I have a Lenovo Vibe K5 (A6020L36 model), and as many people, I want root and, if possible, a custom recovery and custom ROM.
So, the first step was find and download a stock ROM and flashing program, this is already done. But the ROM comes with several "system.img" files (system_1.img, system_2.img, and so on until system_39.img), some of them have several megabytes in size, and others have only 8kb. I need to merge them to get one system.img to edit, but all process I tried failed.
First, I tried the command "copy /b system_1.img+system_2.img+etc", and get a system.img about 2Gb in size, but the file is somehow corrupt:
When I extract it with unyaffs, I only get the "app" and "lost+found" folders;
When I navigate the remaining folders with EXT2 Explorer, I can see the remaining folders, but they are empty;
When I try to open with EXT4 Unpacker, it gives an error about 'list index out of bounds';
The same happens if I use the command but ignoring the 8kb files.
When I open only system_1.img in EXT4 Unpacker, it comes with same error. With EXT2 Explorer, I again can see all the folders, but except for 'app' folder, all others are empty. The others system files appears blank in both programs.
Then, I tried to use this tool, but it gives the same error at post #8 (tried with Win10 64bits and Win7 32bits, both as administrator).
The stock recovery don't have an option to make a backup, then I tried to launch a TWRP recovery made by another user, but gives an error 'dtb not found'.
Tried also the adb 'dd' command, wich comes with a 'permission denied' error, because don't have root. The flashing programs (QFIL and others Qualcomm programs) appears to don't have a backup option for system partition, only for nvram stuff.
I stucked now, I can't find a way to generate a single and valid system.img. Any ideas to get it? Attached are some usefull files to look at, I think. I also have the stock boot.img and recovery.img.
Any help will be appreciated. Thanks in advice.
No ideas?
Deleted.