Surface RT Downgrade Jailbreak and Exploit. - Windows RT Development and Hacking

With a lot of work scrounging around, I've found all the pieces that fit making a jail-broken OS boot-ready Surface RT. As of Now like 5 or 6 years after it's release, there still doesn't seem to be a OS prepared to run on the Surface RT, but maybe if this thread gets enough popularity someone can get an android OS (Possibly derived from an Asus TF502T) Or a debian style Linux build for it. Credit to @ShapeShifter499 for secure boot unlock, @mamaich for Hard drive repartition instructions, @Screeny for original Downgrade instructions, and @netham45 for jailbreak tool and I have posted links to other threads that will also help once 8.1 is downgraded and jailbroken. Here are all files shared and ready for you:
https://drive.google.com/drive/folders/12VilYYz-gF82qzzs6qOkUXoaKz2us8J9?usp=sharing
And Here goes the instructions for the boot-ready Surface RT
1. Create Recovery usb stick (search for recovery drive in control panel, not the file recovery(you might want that too though))
2. Download Surface RT 8.0 Recovery (Took me forever to find, microsoft has removed it from it's site, i have included)
3. Unzip and Copy the file "install.wim" (located under "sources" from your downloaded 8.0 recovery image) to the root of your 8.1 recovery USB stick
4. Reboot into Recovery with the 8.1 recovery stick.
5. Open Command Prompt
6. Use DiskPart to clean the whole Disk (I had to use the override command)
7. While in Disk part use the following commands- (Minus the rem parts)
convert gpt
rem === 1. Windows RE tools partition ===========
create partition primary size=350
format quick fs=ntfs label="WinRE"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
assign letter="T"
gpt attributes=0x8000000000000001
rem === 2. System partition =====================
create partition efi size=200
rem *** NOTE: For 4KB-per-sector drives, change this value to 260
format quick fs=fat32 label="System"
assign letter="S"
rem === 3. Microsoft Reserved (MSR) partition ===
create partition msr size=128
rem === 4. Windows partition ====================
rem == a. Create Windows partition ===========
create partition primary
rem == b. Create space for recovery image ====
shrink minimum=3600
rem == c. Prepare the Windows partition ======
format quick fs=ntfs label="Windows"
assign letter="W"
rem === 5. Recovery image partition =============
create partition primary
format quick fs=ntfs label="Recovery Image"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
assign letter="R"
gpt attributes=0x8000000000000001
exit
8. While in Command Prompt do the following
Dism /apply-image /imagefile: U:\Install.Wim /index:1 /ApplyDir:W:\
(Make sure to include spaces in the proper places and replace U with your Recovery Drive letter, can be found with Diskpart command 'list vol')
bootrec /fixboot
9. Restart, login and disable automatic updates
10. Disable Bitlocker with administative command prompt with the following
manage-bde -unlock C: -RecoveryPassword YOUR-BITLOCKER-RECOVERY-KEY-HERE (Find your bitlocker code it has changed)
manage-bde -off C:
11. get the secureboot file and run the cmd file as admin. (use volume keys and windows button to select accept when the time comes)
12. After reboot (If stuck in bitlocker bootloop use recovery cmd to do #10) run administrative cmd and use- bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on
13. Use RT_jailbreak in administrative mode to run unsigned apps
14. Use SignTool to Sign any apps you want to continue to run
(optional)
15. use @VNNGYN development tool to continue updates and remove infected updates
I am Soon to test whether i can update directly from final state at #14 to windows 8.1 using the update file and development tool given without ruining anything noticable (Probably safer to run through all updates naturally but I'm impatient), will update with details as soon as I am successful.
---Update---- Microsoft seems to force going through the whole update process so no direct updating to 8.1------
Hopefully people can get the ball rolling with some other OS working fully on this tablet unlike windows 10 iot flop.
Development tool: https://forum.xda-developers.com/wi...ent/windows-8-1-rt-jailbreak-exploit-t3226835
Hacked Desktop Apps: https://forum.xda-developers.com/showthread.php?t=2092348
Compiling guide: https://forum.xda-developers.com/showthread.php?t=2096820
One Desktop app store: https://forum.xda-developers.com/showthread.php?t=2559750
Another Desktop app store: https://forum.xda-developers.com/showthread.php?t=2546221
I apologize if there's anything I missed, these are the same steps I took and where I'm at, once an OS development becomes available I will update a reserved comment.

Create recovery USB stick with attached file “windows 8.0” in the main article, then connect the USB stick into your surface and boot it holding the following keys (Volume Down + Power). Your surface now will boot into recovery from your USB stick and continue troubleshooting and refresh your surface with a new system deleting your files (chose the quick method). After you finish your surface will startup normally with Windows RT 8.0.
You can proceed from number 10. In the main article. Good luck

Reserved

Just as a clarification, this will only work for the original Surface RT. This will not work with the Surface 2

I want to clarify, I DID NOT CREATE THE UNLOCK. I just dug around and recused the needed files for the unlock. Many of them were dead links and lead nowhere. I found them scattered on forum postings, threads, and https://archive.org/ If I had to create this unlock from scratch it would take decades I'd think as currently I don't have the knowledge required for this sort of hacking.

Hi
After the step 8, why restart while then /EFI is always empty ?

I bootloop after doing bootrec /fixboot
and have to start all over again, anything to suggest here?

will Surface RT 8.0 North America restore a Vivotab?
<snip>..... Here are all files shared and ready for you:
drive google com/drive/folders/12VilYYz-gF82qzzs6qOkUXoaKz2us8J9?usp=sharing
.[/QUOTE said:
Is that the w8 rt restore image I can use to repair my asus vivotab w8 rt?
Click to expand...
Click to collapse

Can't get past step 8, Surface RT won't boot properly.
Have tried for 4KB-per-sector drives and won't work either way. Any suggestions?

Dism /apply-image /imagefile: U:\Install.Wim /index:1 /ApplyDir:W:\
There is no space between imagefile and letter usb. Follow as below.
Dism /apply-image /imagefile:U:\Install.Wim /index:1 /ApplyDir:W:\
Change U with your own USB Stick drive letter.

well first of one, thanks a lot for your effort , i couldnt pass after the step 8 , as all the previous guys, i tried with this tutorial and the original one, more easy only with one partition (ntfs), i think that the steps are corrects but the problem is that the efi partition is empty an if you try to put the efi zip that is on google drive this efi doesnt work, i hope some one could explain with more details because the surface tablet is a very good one and the possibility to install another sw is required because microsoft sw in the store is very limited and discontinued.

Hi, I have a Surface RT but its detachable keyboard is broken. Do I need the physical keyboard in this tutorial?
Pls respond

XDA-00 said:
Hi, I have a Surface RT but its detachable keyboard is broken. Do I need the physical keyboard in this tutorial?
Pls respond
Click to expand...
Click to collapse
No, physical keyboard isn´t need

falsate said:
No, physical keyboard isn´t need
Click to expand...
Click to collapse
Thank you.

Deleted

@Thedarkwolf123
Please add these steps to your guide after step 8 :-
Copying the EFIESP.zip files into the system (EFI) partition
Use bootrec /fixboot and then bootrec /rebuildbcd
EXIT and reboot.

XDA-00 said:
@Thedarkwolf123
Please add these steps to your guide after step 8 :-
Copying the EFIESP.zip files into the system (EFI) partition
Use bootrec /fixboot and then bootrec /rebuildbcd
EXIT and reboot.
Click to expand...
Click to collapse
Here are some pics

XDA-00 said:
@Thedarkwolf123
Please add these steps to your guide after step 8 :-
Copying the EFIESP.zip files into the system (EFI) partition
Use bootrec /fixboot and then bootrec /rebuildbcd
EXIT and reboot.
Click to expand...
Click to collapse
how to copy efiesp under cmd

XDA-00 said:
Here are some pics
Click to expand...
Click to collapse
Hey would you mind writing out how you got it to work?
I followed the instructions and added your steps after step 8 but I still keep hitting a bootloop Everytime.

dont put a space after imagefile.. on step 8 on an rt U is drive D
the command line is wrong .the correct way is at the bottom command line .
But.. even when that finishes and the last step is bootrec /fixboot then exit then shut down it still wont boot and this doesnt work
and i doubt anyone has got it to work using these steps as evident in step 8 which is wrong and corrected by me.
its wrong not this
Dism /apply-image /imagefile: U:\Install.Wim /index:1 /ApplyDir:W:\
but this
Dism /apply-image /imagefile:U:\Install.Wim /index:1 /ApplyDir:W:\

XDA-00 said:
Hi, I have a Surface RT but its detachable keyboard is broken. Do I need the physical keyboard in this tutorial?
Pls respond
Click to expand...
Click to collapse
there is an onscreen keyboard but this fix is not working . also step 8 is wrong and everyone gets stuck there . see my post for the correct command line . dont put a space after imagefile:U:\ see they show this with a space after the first : imagefile: U:\ which wont work . no space between :U:\ but even after 100 percent and fixboot it still wont boot .just keeps showing surface then looping

Related

Rooting and ClockworkMod Recovery OS X Guide

Hi all,
Saw there were no guides for ClockworkMod install on Mac. And people cool enough to have the DHD must also surely have Macs Or like hacking about enough to have a hackintosh. So anyways, I made a guide.
Rooting and s-off
I rooted using this thread here
http://forum.xda-developers.com/showthread.php?t=835746
You need to download visionary r12 and a terminal emulator, but its all explained there. Exact same process as for windows users.
Once you are rooted and have s-off, come back here.
ClockworkMod Recovery (Updated guide for [email protected] version)
1. Download the Android SDK for Mac from HERE
Extract it, then move the whole folder to the root of your main drive
e.g for me its full path is "/Snow/android-sdk-mac_x86"
2. Download the HTC fastboot binary from Here
Then extract it and move it to /xxxx/android-sdk-mac_x86/tools/
3. Download the clockwork.img from This thread
And copy it to the tools folder where you put fastboot
4. Connect your DHD to the computer in charge only mode.
5. Open Terminal.app
6. Type
Code:
cd /xxxx/android-sdk-mac_x86/tools/
Where xxxx is the name of your drive
And press enter.
If the drive where your sdk folder is located has a space in its name, you have to add a backslash before the second word.
e.g if your drive is called "Macintosh HD" the path will be:
/Macintosh \HD/android-sdk-mac_x86/tools
Alternatively, if you cant be asked typing into terminal, type cd, then a space, drag the tools folder to the terminal window, make sure it says the right path, then press enter.
7. Type
Code:
./adb devices
And press enter
Check your device is listed correctly y checking its serial number in settings on your phone with the serial number that comes up
8.Type
Code:
./adb reboot bootloader
And press enter
This should reboot your phone to bootloader, with green writing at the top, then fastboot USB in red.
9. Now type
Code:
./fastboot flash recovery clockwork.img
And press enter
If youve done it correctly, it will say
Code:
sending 'recovery' (4914 KB)... OKAY
writing 'recovery'... OKAY
10. Now use the volume buttons to navigate, and power button to select, and navigate to bootloader, then once that loads, to recovery.
Let it load and ClockworkMod will load.
Then click down through the whole menu 3 times until it says 'back menu button enabled"
This means the power button now is the select button.
You now have CM successfully installed, and can reboot, install new roms etc as you please!
No guarantee provided for this guide, if it breaks your device, blows up the computer, gets you sued by google or whatever, I am not responsible and you do all this at your own risk.
Any improvements to the guide, please say in the thread.
I am also working on a script/app to do it all on OS X with one click. Will hopefully be done once this 10 days of coursework and tests is over!
Happy Flashing and thanks to all the devs that made this possible!
Rory
excellent looking forward to the app!
mac OS x needs love from android! devs
Yeah!!!
Useful Guide! Thanks!!
Thanks!
I'm running Ubuntu and the commands are basically the same for Linux systems.
But Linux users will need to add a small file to let the OS see the Device correctly.
Follow step 3 "Setup your system to detect your device." in the guide below:
http://developer.android.com/guide/developing/device.html
Great guide!!!
but on Mac I ceep on getting a signature error??
What am i forgetting?
duanes said:
Great guide!!!
but on Mac I ceep on getting a signature error??
What am i forgetting?
Click to expand...
Click to collapse
Not sure mate, maybe look in the windows threads.
First thing I would suggest is redownload the recovery image.
At what point are you getting the signature error?
excellent i just did it..and my DHD is free!
nandihno said:
excellent i just did it..and my DHD is free!
Click to expand...
Click to collapse
Glad I could help. Will soon be expanding it for flashing kernels and ROMs using fastboot.
Thank you so much for this tutorial is very useful! If Mac users who believe that this method is difficult, can install BootCamp and run Windows natively. I use Windows 7 Ultimate under BootCamp to use the tools for Root, Downgrade, etc... (remember: for use the tools under Windows, runing under "Administrator mode" click right on mouse over the EXE file
Someone with a Mac to use Parallels Desktop or VMWare Fusion for root, to Downgrade, etc with the DHD?
Regards,

Rooting Double Power (DOPO) M7088 Jelly Bean 4.1.1 Tablet

As always Any information I give is free and this information is to be used at your own risk I take no responsibility for your device this is just my experience and i hope it helps someone with the same problem i had
I recently bought the Double Power (DOPO) M7088 Jelly Bean 4.1.1 Tablet from Walmart.com After a few days of searching and many failed Attempts I finally found out how to root this device and would like to share it to those having the same problem.
After doing some digging i descover the Dopo tablets are nothing more than a rebranded generic rock ship tablets so after some searching here is what i found.
Things you will Need.
1.Pdanet+ for android installer (just type in pdanet+ in your search engine of choice)
2.Your device and usb cable
3.The free download of unlockrootpro (Just type unlockroot into your search engine of choice
Steps.
1. Download and install Pdanet+
2 Download and install unlockrootpro free Version
a. you must be connected to the internet for the installer to work.
b. the unlockroot pro will download a file to your computer that is in itself a down loader it is safe but it does try to get you to install some 3rd part software. if you click the close button it will give you the option to skip the 3rd party software and install just the unlockroot software. it does this 2 or 3 times just click close and skip each time.
3. Connect your Tablet up to the PC and allow all the drivers to install.
4. Once connected start unlockrootpro once it is ope click the green root button it should detect your device and bring up a box just click the button and it will install the root.
a. Now i noticed after it installed the root and say rebooting device my device would not reboot. I unplugged my device and then plugged it right back in and the device immediately rebooted
5. Once your table has rebooted download root checker or the app of your choice to verify root access.
I hope this helped anyone with a Dopo m7088
I don't know if this method will work for any of the other Double Power Tablets so i honestly cannot answer any questions other than what i have stated but feel free to try it if you cannot find any other method.
If this method does Work for you please post a coment on your steps and what device you used this method on so that you can help the community.
M7088
Well i have found out that there is a way to ROOT the M7088 from walmart with out internet connection
Download Moborobo in order to load drivers for the M7088
Just download the same software as you would for the PIPO S1 Its all over the net now and also this M7088 has an attitude about rooting so you might have to click root a couple time to force it to but it does work quite well the Chinese software ( ZhuoDaShi ) after its done you will get a message window in Chinese just copy and paste that text into Google translator and it will tell you ROOT is good Ha Ha ha have fun
backslashx said:
As always Any information I give is free and this information is to be used at your own risk I take no responsibility for your device this is just my experience and i hope it helps someone with the same problem i had
I recently bought the Double Power (DOPO) M7088 Jelly Bean 4.1.1 Tablet from Walmart.com After a few days of searching and many failed Attempts I finally found out how to root this device and would like to share it to those having the same problem.
After doing some digging i descover the Dopo tablets are nothing more than a rebranded generic rock ship tablets so after some searching here is what i found.
Things you will Need.
1.Pdanet+ for android installer (just type in pdanet+ in your search engine of choice)
2.Your device and usb cable
3.The free download of unlockrootpro (Just type unlockroot into your search engine of choice
Steps.
1. Download and install Pdanet+
2 Download and install unlockrootpro free Version
a. you must be connected to the internet for the installer to work.
b. the unlockroot pro will download a file to your computer that is in itself a down loader it is safe but it does try to get you to install some 3rd part software. if you click the close button it will give you the option to skip the 3rd party software and install just the unlockroot software. it does this 2 or 3 times just click close and skip each time.
3. Connect your Tablet up to the PC and allow all the drivers to install.
4. Once connected start unlockrootpro once it is ope click the green root button it should detect your device and bring up a box just click the button and it will install the root.
a. Now i noticed after it installed the root and say rebooting device my device would not reboot. I unplugged my device and then plugged it right back in and the device immediately rebooted
5. Once your table has rebooted download root checker or the app of your choice to verify root access.
I hope this helped anyone with a Dopo m7088
I don't know if this method will work for any of the other Double Power Tablets so i honestly cannot answer any questions other than what i have stated but feel free to try it if you cannot find any other method.
If this method does Work for you please post a coment on your steps and what device you used this method on so that you can help the community.
Click to expand...
Click to collapse
Firmware
Hey awesome i may have a chance to try that method out on my tablet soon if i am lucky. I was wondering if anyone or the one that commented on my original post. I need a copy of the firmware for this tablet mine crashed after lending it out to a friend i am afraid he tried to modify it and somehow corrupted the system it is stuck on the dopo start up screen. if there is anyone who can provide a clean copy of this or even maybe dump a copy of theirs for me i would greatly appreciate it.
.
zxhwk said:
Well i have found out that there is a way to ROOT the M7088 from walmart with out internet connection
Download Moborobo in order to load drivers for the M7088
Just download the same software as you would for the PIPO S1 Its all over the net now and also this M7088 has an attitude about rooting so you might have to click root a couple time to force it to but it does work quite well the Chinese software ( ZhuoDaShi ) after its done you will get a message window in Chinese just copy and paste that text into Google translator and it will tell you ROOT is good Ha Ha ha have fun
Click to expand...
Click to collapse
hey this is great news and I thank you !!!
I was wondering if the m7088 caan be upgraded to CM10/4.2.2?
thanks
I don't know if you can install any form of CM on it as of yet. I have successfully I believe Dumped a copy of the system and recovery images from my M7088. Unfortunately my last unit was toast but being under warrantee i sent it back and they replaced it. Soon as I had it i researched how to back up the system just in case. I can provide my copy of the dump or show the process i used to do it.
I don't know if the dump I have is what is exactly a proper form of back up or recovery. I also don't know what is needed to mod it for CM but at least this is a start to anyone who would like to try.
If there is anyone who would like to and would like the Files I have dumped or any help I can provide let me know. I would like to see Cm/4.2.2 working on this device.
Easy way to root any Dopo tablet
I am not responsible for anything. Use this at your on risk.
Download and install Exynos abuse .
Then Uninstall and get any kind of root checker to verify root access.
And that's it.
Worked for me with no problems. NOW My Dopo tablet is faster than when I got it out the box. With minor tweaking apps and my 32 gb external SD card as my internal SD card and you can find the thread on how to do this on xda forums. Running games like NFS MW, Modern Combat 2 and 3,Nba Jam for android.To run good games like these I had to get a system app freezer like titanium backup to freeze a few useless apps. So now these games run very smooth and flawlessly.Good luck.
backslashx said:
I don't know if you can install any form of CM on it as of yet. I have successfully I believe Dumped a copy of the system and recovery images from my M7088. Unfortunately my last unit was toast but being under warrantee i sent it back and they replaced it. Soon as I had it i researched how to back up the system just in case. I can provide my copy of the dump or show the process i used to do it.
I don't know if the dump I have is what is exactly a proper form of back up or recovery. I also don't know what is needed to mod it for CM but at least this is a start to anyone who would like to try.
If there is anyone who would like to and would like the Files I have dumped or any help I can provide let me know. I would like to see Cm/4.2.2 working on this device.
Click to expand...
Click to collapse
I ran across this post and was wondering if you have the original system and recovery images, as I rooted my M7088 and lost my backup files
m7088 firmware
I am looking for a copy of the firmware for my m7008 tablet.
I am trying to fix a problem of it not starting up its stuck on the DOPO screen.
I believe I can re flash it but DOPO will not send me the file they want me to send in.
Any help will be appreciated.
DOPO logo screen-freeze
putertim said:
I am looking for a copy of the firmware for my m7008 tablet.
I am trying to fix a problem of it not starting up its stuck on the DOPO screen.
I believe I can re flash it but DOPO will not send me the file they want me to send in.
Any help will be appreciated.
Click to expand...
Click to collapse
Joining just to make a couple comments here. I find that DOPO logo screen-freeze seems to be common problem.
My story - This passed Christmas 2012 my son purchased a DOPO M7088 for his 12y/o son, and talked me into a like purchase for myself this past March 2013. Here in Jul 2013, the grandson is visiting with his tablet. When it became frozen with the DOPO screen one night - we tried everything that we could think of to restore. Even pointing fingers at him... to what surprise the following morning my tablet froze updating apps. When I tried to restart, reboot, reset... even tried Vol+/PwrUP, Vol-/PwrUP... allowing the power in the battery to drain to a point that the screen would not light up or flash. Then recharging - nothing worked passed the DOPO screen-freeze.
For reference - I have worked in electronics/computers from the late 60s - so I’m not a rookie here.
Fortunately – I purchased insurance with Wal-Mart, their tech-line made same suggestions as I had done to restore the system, and came to the conclusion that they will completely return/refund my purchase.
Strange that within 12hrs two like tablets crash following app updates, where one is for a young man (games) and the other for adult (general usage). The finger pointing had three other fingers pointing back at us. So apologies to the grandson.
My son may root/re-install the grandson’s system when they return home – for myself I’m going to upgrade to a better brand (now that I'm missing the tablet).
Hope this helps others to understand that the DOPO screen-freeze problem may not be their personal tablet problem but a product problem (I.E. firmware). /TDos
Need dump of 7088 rom
backslashx said:
I don't know if you can install any form of CM on it as of yet. I have successfully I believe Dumped a copy of the system and recovery images from my M7088. Unfortunately my last unit was toast but being under warrantee i sent it back and they replaced it. Soon as I had it i researched how to back up the system just in case. I can provide my copy of the dump or show the process i used to do it.
I don't know if the dump I have is what is exactly a proper form of back up or recovery. I also don't know what is needed to mod it for CM but at least this is a start to anyone who would like to try.
If there is anyone who would like to and would like the Files I have dumped or any help I can provide let me know. I would like to see Cm/4.2.2 working on this device.
Click to expand...
Click to collapse
Hello, I have damaged the ROM by a an installed app after rooting. I see you said that you made a dump of the ROM. If possible, can I get a copy of these files as this would help me greatly. I have rkAndroidTool.exe working. If it works out, I will post the procedure.
Thanks
Dump and Flash the dopo M7088 and other RK3066 based ROMs
Any information I give is to be used at your own risk. I take no responsibility for any damage to your device.
Here's my story: I installed an application to change the fonts after I rooted. This damaged the system and created a boot loop. At this point I had not worked out a reliable method to backup and restore the ROM and in the process of trying to fix, I wound up damaging the partitions trying to push a file back into the tablet with adb.
So in my research to restore the ROM, I came across several methods to flash the ROM, but very few methods to dump the complete ROM and I wanted to be able to extract and restore the entire ROM. In another thread, I found scripts to dump the rk3066 chipset. I expanded this idea and modified the scripts to flash the ROM as well. Also, I created an installer script to simplify the process.
These scripts need to use the Ubuntu Linux live DVD to dump and flash the ROM. The advantages of Linux is you can directly connect to the tablet in flash mode without the trouble of having to install drivers or the android SDK.
Download the Linux 12.04 LTS version from the following Link http://www.ubuntu.com/download/desktop .
Once downloaded, burn this ISO file to a DVD using your favorite DVD burning software. Most burning software have the ability to decode ISO files. If needed, here is a free ISO burner. Link: http://download.cnet.com/ImgBurn/3000-2646_4-10847481.html?tag=mncol;2
Download the attached zip file and copy the zip to the USB drive. Do not decompress in windows as we need to do this under linux to preserve the stored permissions.
Boot the PC from the DVD drive. This should start the Linux. You may need to press an “F” key during the BIOS boot to bring up a menu to select which drive to boot from. You should see a purple screen. This is Linux loading. Select the “Try Ubuntu” option and the Linux should boot to the Linux Desktop.
OK, we are in Linux!
Insert the USB drive into the PC wait for the Linux to open a window. It may take a little bit as we are running off a DVD and some resources need to load. Be patient and watch the light to finish blinking on the USB stick! Drag the “ExtractRomRK3066.zip” file in the USB window to the desktop.
Write down the name of the USB in the title bar of the window.
For example, My USB window says: F490-4740 in the title bar. Write this down, then move the USB window to the side.
Double click on the zip file, this opens the zip in a window. Drag the “ExtractRomRK3066“ folder in the zip window to the desktop. When the copy is finished, close the zip window.
Click on the “Dash Home” icon on the top left of the desktop, Type “Terminal” in the search box and select the terminal application icon.
In the Terminal Window type exactly as shown while observing the caps:
cd ~/Desktop/Ex*
Type the command:
ls -l
You should see a file named “install.sh” along with other commands ending with “.sh”.
Type the line as shown below including the “./”:
./install.sh
The required libraries should install to Linux. Don't worry this is only in memory as we are not installing anything to your hard drive. Make sure everything completed without Errors. If you only see warnings, this is OK!
Let's connect the Tablet to the USB port and put into flash mode. With the Tablet power off and the all cables removed, hold the Vol– button and plug in the USB cable. Continue to hold the Vol- button for 5 seconds. Let go of the Vol- button and connect the power cable. We should now be in flash mode.
We can test if we connected to flash mode by typing:
lsusb
You should see a list of USB devices. Within this list you should see a entry that has the ID:
ID: 2207:300a
If you see the ID, great we are connected to the tablet. If not, make sure the tablet is off and do the above Tablet procedure again.
OK we are connected!
Dumping the ROM
Type the following command replacing the “F490-4740” with your USB name we wrote down earlier from the USB title bar and follow the prompts. This will start the dump of the tablet:
sudo ./dumpall.sh /media/F490-4740/output
YAY! We are dumping the ROM!
Now we wait for “done...”, hopefully without any errors.
Double click on the “ output” folder in the USB drive window.
Verify that we have “backup.img”, “boot.img”, “kernel.img”, “misc.img”, “parm.img”, “recovery.img”, “system.img and userdata.img.
Now in the left panel of the USB window. Click on the ^ icon next to the USB drive description. This will unmount the USB drive for removal.
We are done!
Flashing the ROM
To flash a file you will notice other commands with the extension “.sh”. You may use any of these commands to restore all or part of the ROM.
For example:
To flash the below stock rom, extract the zip file to a USB drive and type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall-user.sh /media/F490-4740/dopo7088stock
To flash a backup of all files including the userdata.img, type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall.sh /media/F490-4740/dopo7088stock
To flash just the recovery, do the same as above only with the command:
sudo ./flashrecovery.sh /media/F490-4740/dopo7088stock
To flash just the system, do the same as above only with the command:
sudo ./flashsystem.sh /media/F490-4740/dopo7088stock
The valid command are:
sudo ./dump?.sh
or
sudo ./flash?.sh
replacing ? With:
all, all-user, backup, boot. cache, kernel, kpanic, misc, recovery, system, user, userdata
----------------------
Hope this helps somebody create a full backup.
Thanks.
UPDATE: I got another dopo m7088 tablet, created a backup using the above method and flashed my bricked m7088 tablet. Everything works again. YAY!
Below is the dumped stock rom for the dopo m7088. Hopes this help's sombody unbrick their tablet.
Extract the dopo7088stk.zip to a USB drive and follow the above instructions.
Thanks
Stock Rom Link: https://docs.google.com/file/d/0B8YnQA1FX-_yUU1ERXh1TjNUbnc/edit?usp=sharing
Thanks
I now have my M7088 again. Thank you . Your instructions where 100% right on.
Partition table not correct in stock M7088 ROM!
After I created the dump of the M7088 ROM and I flashed my tablet, I was looking at the parameter file and realized it was wrong from the factory!
There are several problems that may be the reason some people (including me) has had their devices brick for no apparent reason.
Below is the factory partition table. There is a blank space at address 118000 for a length of 11E000 bytes, this is not a problem. However, the "userdata" partition overruns the "kpanic" and "system" partition as well as the "system" partition overruns the "user" partition. This could lead to data corruption in the partitions.
Factory Partition Table: (length @ start)
[email protected](misc), (2000 + 2000 = 4000)
[email protected](kernel), (4000 + 4000 = 8000)
[email protected](boot), (8000 + 8000 = 10000)
[email protected](recovery), (10000 + 8000 = 18000)
[email protected](backup), (18000 + C0000 = D8000)
[email protected](cache), (D8000 + 40000 = 118000)
(ERROR - Space between 118000 and 236000)
[email protected](userdata), (236000 + 400000 = 636000)
(ERROR - 636000 is past 618000 and 61A000)
0x000020[email protected](kpanic), (618000 + 2000 = 61A000)
[email protected](system), (61A000 + 200000 = 81A000)
(ERROR - 81A000 is past 73A000)
[email protected](user) (73A000 -> end)
It looks like someone made a mistake and/or adjusted the partition sizes and never finished the job!
The only way to fix this is to correct the partition table and re-flash the entire device.
Before I corrected the "parameter" and "parm.img" file, I examined other RK3066 roms as well as the dopo TD1010. The TD1010 has a shorter "system" partition so the fixed partition table below is the same as the TD1010 all the way through the "kpanic" partition.
Fixed Partition Table: (length @ start)
[email protected](misc), (2000 + 2000 = 4000)
[email protected](kernel), (4000 + 4000 = 8000)
[email protected](boot), (8000 + 8000 = 10000)
[email protected](recovery), (10000 + 8000 = 18000)
[email protected](backup), (18000 + C0000 = D8000)
[email protected](cache), (D8000 + 40000 = 118000)
[email protected](userdata), (118000 + 400000 = 518000)
[email protected](kpanic), (518000 + 2000 = 51A000)
[email protected](system), (51A000 + 200000 = 71A000)
[email protected](user) (71A000 -> end)
I corrected the stock firmware and repacked it as dopo7088stkfixed.zip. This file can be flashed with the procedure in the earlier post, replacing the original zip package with this one.
Fixed Firmware Link: https://docs.google.com/file/d/0B8YnQA1FX-_yRmhIN1dCT245R2c/edit?usp=sharing
Also, remember to do a full wipe after flashing.
Thanks
---------- Post added at 02:12 PM ---------- Previous post was at 01:51 PM ----------
putertim said:
I now have my M7088 again. Thank you . Your instructions where 100% right on.
Click to expand...
Click to collapse
No problem. Check my above post. I discovered the partition tables from the factory are wrong which could cause data corruption.
Thanks
i keep on getting this error when trying to reflash i follow the steps i dont know what im doing wrong? ..please help.
[can't open input file 'parm.img': No such file or directory
Error: mkkrnlimg could not decode partition table
[email protected]:~/Desktop/ExtractRomRK3066$
bird56duce said:
i keep on getting this error when trying to reflash i follow the steps i dont know what im doing wrong? ..please help.
[can't open input file 'parm.img': No such file or directory
Error: mkkrnlimg could not decode partition table
[email protected]:~/Desktop/ExtractRomRK3066$
Click to expand...
Click to collapse
Sounds like the path to the files is incorrect.
The command "sudo ./flashall-user.sh /media/F490-4740/dopo7088stock" will look for the media in the path specified.
The "sudo ./flashall-user.sh" is the command part of the line.
The path can be interpreted as "/media/" + "The USB Drive Name in the title bar of the window" + "/" + "The Folder the media is in that has the parm.img file."
For example: if you have the files that includes the parm.img file on the USB drive in a folder called "ROM" and the name of the USB drive at the top of the USB drive window is "ABCD-0123", the line would look like:
sudo ./flashall-user.sh /media/ABCD-0123/ROM
Hope this helps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
opening awsfai
mikeopi said:
Sounds like the path to the files is incorrect.
The command "sudo ./flashall-user.sh /media/F490-4740/dopo7088stock" will look for the media in the path specified.
The "sudo ./flashall-user.sh" is the command part of the line.
The path can be interpreted as "/media/" + "The USB Drive Name in the title bar of the window" + "/" + "The Folder the media is in that has the parm.img file."
For example: if you have the files that includes the parm.img file on the USB drive in a folder called "ROM" and the name of the USB drive at the top of the USB drive window is "ABCD-0123", the line would look like:
sudo ./flashall-user.sh /media/ABCD-0123/ROM
Hope this helps.
Click to expand...
Click to collapse
:good: I figured it out. thank you. I have another question what are the proper steps after flashing a new rom? I followed all your steps from dumping to flashing the new fixed rom, but cant get the device out of that stupid DOPO screen. After flashing with the new rom do you unplug it and reboot? BTW its not rooted. thanks
bird56duce said:
:good: I figured it out. thank you. I have another question what are the proper steps after flashing a new rom? I followed all your steps from dumping to flashing the new fixed rom, but cant get the device out of that stupid DOPO screen. After flashing with the new rom do you unplug it and reboot? BTW its not rooted. thanks
Click to expand...
Click to collapse
Hold the power key for about 15 seconds to force a shut down.
After shutting down, do you still get a stuck dopo screen?
If so, try a different USB port on the PC and try the procedure again. Sometime it does not seem to always take.
Make sure you are using the command sudo ./flashall.sh with the fixed rom. For the fixed rom to work, you have to flash all partitions. Then do a factory reset once it is fully booted.
Also, do a wipe. With the power off, hold the vol- and power key. This should bring you into the recovery menu. Do a wipe cache & wipe data/factory reset & reboot.
I have tried your technique at least 4 times and it doesn't work. I can't get through the Linux part with the downloaded file that you offer in your post. I get errors and I cannot go any further.
Either the file that you posted is not good or there is something else going on here. Any idea's? I have also seen other posts saying they cannot get past the errors.
mvalent000 said:
I have tried your technique at least 4 times and it doesn't work. I can't get through the Linux part with the downloaded file that you offer in your post. I get errors and I cannot go any further.
Either the file that you posted is not good or there is something else going on here. Any idea's? I have also seen other posts saying they cannot get past the errors.
Click to expand...
Click to collapse
Please give me more info on what the errors are and what command are they after?
mikeopi said:
Any information I give is to be used at your own risk. I take no responsibility for any damage to your device.
Here's my story: I installed an application to change the fonts after I rooted. This damaged the system and created a boot loop. At this point I had not worked out a reliable method to backup and restore the ROM and in the process of trying to fix, I wound up damaging the partitions trying to push a file back into the tablet with adb.
So in my research to restore the ROM, I came across several methods to flash the ROM, but very few methods to dump the complete ROM and I wanted to be able to extract and restore the entire ROM. In another thread, I found scripts to dump the rk3066 chipset. I expanded this idea and modified the scripts to flash the ROM as well. Also, I created an installer script to simplify the process.
These scripts need to use the Ubuntu Linux live DVD to dump and flash the ROM. The advantages of Linux is you can directly connect to the tablet in flash mode without the trouble of having to install drivers or the android SDK.
Download the Linux 12.04 LTS version from the following Link .
Once downloaded, burn this ISO file to a DVD using your favorite DVD burning software. Most burning software have the ability to decode ISO files. If needed, here is a free ISO burner. Link:
Download the attached zip file and copy the zip to the USB drive. Do not decompress in windows as we need to do this under linux to preserve the stored permissions.
Boot the PC from the DVD drive. This should start the Linux. You may need to press an “F” key during the BIOS boot to bring up a menu to select which drive to boot from. You should see a purple screen. This is Linux loading. Select the “Try Ubuntu” option and the Linux should boot to the Linux Desktop.
OK, we are in Linux!
Insert the USB drive into the PC wait for the Linux to open a window. It may take a little bit as we are running off a DVD and some resources need to load. Be patient and watch the light to finish blinking on the USB stick! Drag the “ExtractRomRK3066.zip” file in the USB window to the desktop.
Write down the name of the USB in the title bar of the window.
For example, My USB window says: F490-4740 in the title bar. Write this down, then move the USB window to the side.
Double click on the zip file, this opens the zip in a window. Drag the “ExtractRomRK3066“ folder in the zip window to the desktop. When the copy is finished, close the zip window.
Click on the “Dash Home” icon on the top left of the desktop, Type “Terminal” in the search box and select the terminal application icon.
In the Terminal Window type exactly as shown while observing the caps:
cd ~/Desktop/Ex*
Type the command:
ls -l
You should see a file named “install.sh” along with other commands ending with “.sh”.
Type the line as shown below including the “./”:
./install.sh
The required libraries should install to Linux. Don't worry this is only in memory as we are not installing anything to your hard drive. Make sure everything completed without Errors. If you only see warnings, this is OK!
Let's connect the Tablet to the USB port and put into flash mode. With the Tablet power off and the all cables removed, hold the Vol– button and plug in the USB cable. Continue to hold the Vol- button for 5 seconds. Let go of the Vol- button and connect the power cable. We should now be in flash mode.
We can test if we connected to flash mode by typing:
lsusb
You should see a list of USB devices. Within this list you should see a entry that has the ID:
ID: 2207:300a
If you see the ID, great we are connected to the tablet. If not, make sure the tablet is off and do the above Tablet procedure again.
OK we are connected!
Dumping the ROM
Type the following command replacing the “F490-4740” with your USB name we wrote down earlier from the USB title bar and follow the prompts. This will start the dump of the tablet:
sudo ./dumpall.sh /media/F490-4740/output
YAY! We are dumping the ROM!
Now we wait for “done...”, hopefully without any errors.
Double click on the “ output” folder in the USB drive window.
Verify that we have “backup.img”, “boot.img”, “kernel.img”, “misc.img”, “parm.img”, “recovery.img”, “system.img and userdata.img.
Now in the left panel of the USB window. Click on the ^ icon next to the USB drive description. This will unmount the USB drive for removal.
We are done!
Flashing the ROM
To flash a file you will notice other commands with the extension “.sh”. You may use any of these commands to restore all or part of the ROM.
For example:
To flash the below stock rom, extract the zip file to a USB drive and type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall-user.sh /media/F490-4740/dopo7088stock
To flash a backup of all files including the userdata.img, type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall.sh /media/F490-4740/dopo7088stock
To flash just the recovery, do the same as above only with the command:
sudo ./flashrecovery.sh /media/F490-4740/dopo7088stock
To flash just the system, do the same as above only with the command:
sudo ./flashsystem.sh /media/F490-4740/dopo7088stock
The valid command are:
sudo ./dump?.sh
or
sudo ./flash?.sh
replacing ? With:
all, all-user, backup, boot. cache, kernel, kpanic, misc, recovery, system, user, userdata
----------------------
Hope this helps somebody create a full backup.
Thanks.
UPDATE: I got another dopo m7088 tablet, created a backup using the above method and flashed my bricked m7088 tablet. Everything works again. YAY!
Below is the dumped stock rom for the dopo m7088. Hopes this help's sombody unbrick their tablet.
Extract the dopo7088stk.zip to a USB drive and follow the above instructions.
Thanks
Stock Rom Link:
Click to expand...
Click to collapse
I have tried this today about 8 times today. 4 with each folder you supplied in every usb port on my computer. I could do it all the way down to the dumping. I couldn't get any of the flashing working and my m7088 tablet is still stuck on the dopo screen. Please help as I would like to have this tablet working for my way home in a week.
I have Linux as a second os on my laptop so the first part was easy.
Thanks for your help so far. Good info

installing pro 2 image files from usb

hi all
i have got the eu pro 2 image files downloaded but i dont klnow how to create a bootable USB stick with these files so i can boot from it on my pro and reinstall from scratch.
Any guides anywhere ???
thanks
paul
Haven't tried it with a recovery image specifically, but I've done this plenty with an install image. There are tools, but I do it semi-manually:
1. Locate suitable flashdrive whose contents you can erase (back them up if needed) and plug it in.
2. Run CMD or Powershell (as Administrator).
3. Run "diskpart" (all commands are given in quotes and should be typed without quotes) and accept the UAC prompt if needed.
4. In diskpart, type "list disk" to see the list of disks, then type "sel dis [#]" (replace [#] with the disk number for the flashdrive).
5. Type "lis par" to see all partitions on the disk (typically only one) then "del par [#]" for each one to delete them.
6. Type "create par primary" to create a new partition spanning the whole flashdrive, then "lis par" to make sure it's selected (star next to it).
7. Type "format quick" to create a file system on the new partition, then "assign" to give it a drive letter.
8. Type "active" to make the new partition the one the OS will attempt to boot from, when booting off that drive.
9. Assuming everything succeeded, you can now exit diskpart ("exit").
10. Either unpack (using a program like 7-Zip) or mount (Win8 can do this automatically, or there's lots of software for older Windows versions) the disk image.
11. Copy the entire contents of the disk image (you can just use Explorer for this part if you mounted it) to the flashdrive.
Congrats, you have a bootable flashdrive containing a Windows installation (or recovery) image.
GoodDayToDie said:
Haven't tried it with a recovery image specifically, but I've done this plenty with an install image. There are tools, but I do it semi-manually:
1. Locate suitable flashdrive whose contents you can erase (back them up if needed) and plug it in.
2. Run CMD or Powershell (as Administrator).
3. Run "diskpart" (all commands are given in quotes and should be typed without quotes) and accept the UAC prompt if needed.
4. In diskpart, type "list disk" to see the list of disks, then type "sel dis [#]" (replace [#] with the disk number for the flashdrive).
5. Type "lis par" to see all partitions on the disk (typically only one) then "del par [#]" for each one to delete them.
6. Type "create par primary" to create a new partition spanning the whole flashdrive, then "lis par" to make sure it's selected (star next to it).
7. Type "format quick" to create a file system on the new partition, then "assign" to give it a drive letter.
8. Type "active" to make the new partition the one the OS will attempt to boot from, when booting off that drive.
9. Assuming everything succeeded, you can now exit diskpart ("exit").
10. Either unpack (using a program like 7-Zip) or mount (Win8 can do this automatically, or there's lots of software for older Windows versions) the disk image.
11. Copy the entire contents of the disk image (you can just use Explorer for this part if you mounted it) to the flashdrive.
Congrats, you have a bootable flashdrive containing a Windows installation (or recovery) image.
Click to expand...
Click to collapse
I've been building windows deployment images for years and I build my boot drives similarly to how you describe. The problem I've had is in getting a uefi bootable drive which I can use to take a drive image before I deploy a new one. In the past I've used tools like Make PE3 to make some useful boot drives but i'm not having nay luck with the newer pe4 or getting an older pe3 image to boot.
Secure boot is off, windows detects the drive and lsit it in the boot menu it just doesn't boot. Any suggestions?
Will_nonya said:
I've been building windows deployment images for years and I build my boot drives similarly to how you describe. The problem I've had is in getting a uefi bootable drive which I can use to take a drive image before I deploy a new one. In the past I've used tools like Make PE3 to make some useful boot drives but i'm not having nay luck with the newer pe4 or getting an older pe3 image to boot.
Secure boot is off, windows detects the drive and lsit it in the boot menu it just doesn't boot. Any suggestions?
Click to expand...
Click to collapse
Try pressing VOL - (I think its -, might be +) as it boots with the flash drive plugged in
lopezk38 said:
Try pressing VOL - (I think its -, might be +) as it boots with the flash drive plugged in
Click to expand...
Click to collapse
Thanks friend but that is not the issue. I can initiate the boot from USB but none of the boot images I've used in the past or that I've create new successfully boot. This problem is limited just to the surface pro.

[Tool] WhatsApp Key/DB Extractor | CRYPT6-12 | NON-ROOT | UPDATED OCTOBER 2016

** Version 4.7 Updated October 2016 - Supports Android 4.0-7.0 **
SUMMARY:
Allows WhatsApp users to extract their cipher key and databases on non-rooted Android devices.
UPDATE: This tool was last updated on October 12th 2016. and confirmed working on Android 4.0-7.0 using WhatsApp version v2.16.304 (latest available).
IMPORTANT: If you wish to extract media files or WhatsApp databases from Google Drive backups then you need: WhatsApp Google Drive Extractor instead.
TUTORIAL:
BRANCH UPDATES:
v4.0 - Fixed issues with Android API 14-17 (4.0-4.2 Jelly Bean).
v4.1 - Added support for Android API 23 (6.0-6.0.1 Marshmallow).
v4.2 - Added support for specifying adb backup passwords.
v4.3 - Added PowerShell version as optional alternative to bat version.
v4.4 - Changed primary mirror for legacy apk.
v4.5 - Fixed issue pushing cipher key to emulated storage.
v4.6 - Updated primary mirror for legacy apk (again).
v4.7 - Added new sanity checks and support for Android API 24 (7.0 Nougat).
PREREQUISITES:
O/S: Windows Vista, Windows 7, Windows 8, Windows 10, Mac OS X or Linux
Java - If not installed: Download Java
ADB (Android Debug Bridge) Drivers
USB Debugging* must be enabled on the target device. Settings -> Developer Options -> (Debugging) USB debugging
Android device with Android 4.0 or higher. I.E. Ice Cream Sandwich, Jelly Bean, KitKat, Lollipop, Marshmallow or Nougat.
*= If you cannot find Developer Options then please go to: Settings -> About phone/device and tap the Build number multiple times.
INSTRUCTIONS:
Extract WhatsApp-Key-DB-Extractor-master.zip maintaining the directory structure.
Click on WhatsAppKeyDBExtract.bat (Windows) or WhatsAppKeyDBExtract.sh (Mac OS X / Linux).
Connect your device via USB, unlock your screen and wait for Full backup to appear.
Enter your backup password or leave blank (if none set) and tap on Back up my data.
Confirm backup password in your command console and then check the "extracted" folder.
TROUBLESHOOTING:
If you have never used USB Debugging before, you may also need to verify the fingerprint.
If you have set a default backup password in your Android settings, then this MUST be the
backup password that you provide when prompted to backup your data. Else it WILL fail!
Linux and Mac OS X users may need to set the script permissions as executable. Depending on the
adb permissions, you may also need to sudo ./WhatsAppKeyDBExtract.sh from your command console.
If you're having issues with WhatsAppKeyDBExtract.bat then right click WhatsAppKeyDBExtract.ps1
and select Run with PowerShell. You may have to enter "y" at first run for script execution policy.
If you get an error saying "AES encryption not allowed" then you need to update your Oracle Java
Cryptography Extension (JCE) to Unlimited Strength Jurisdiction Policy Files.
DOWNLOAD: WhatsApp-Key-DB-Extractor-master.zip
AUTHOR: TripCode
THANKS: dragomerlin for Android Backup Extractor and Abinash Bishoyi for being cool.
alternatives
Yes, this is a normal backup method. There are automatic tools that do the same without using PC, just on device side.
Apart from normal ADB method, you could use ECLIPSE for that, using the memory module, you could transfer files from and in.
If you have physical access to the device, there are many solutions.
regards.
droopyar said:
Yes, this is a normal backup method. There are automatic tools that do the same without using PC, just on device side.
Apart from normal ADB method, you could use ECLIPSE for that, using the memory module, you could transfer files from and in.
If you have physical access to the device, there are many solutions.
regards.
Click to expand...
Click to collapse
The only way to access private application files (such as a WhatsApp's cipher key) without root is the ADB method. You can backup some files on the device without a PC (APK's etc...), but there is currently no way to access private files and folders. All the "My Big Fat Backup" style apps and tools will either require root or ADB. Eclipse also utilizes ADB. Basically, device side backups of application data require root. There are no other alternatives to this. If there was, then Android would be too infeasible and insecure as a viable operating system. Physical access translates into only two solutions. 1.) The ability to root and 2.) The ability to utilize ADB (Eclipse, Bats, Exe's doing nothing more than calling a simple command line). Of course if you are aware of a 3rd method (disregarding the user interface) and is not based on root or ADB then please feel free to share.
Thanks for this tool!
I've just tried to use it, but it installs the java constantly (while java is properly installed on computer as other applications uses it without any problem )
By any chance, do you have any idea how to pass that?
Thanks!!
Mia
PS I got JDK installed and still not working
MiaNet said:
I've just tried to use it, but it installs the java constantly (while java is properly installed on computer as other applications uses it without any problem )
By any chance, do you have any idea how to pass that?
Click to expand...
Click to collapse
The bat file automatically checks for the presence of java.exe on your system. If it's not found then it starts the install. It would appear that for some reason it's not finding Java and hence why you're stuck in this loop. Please find attached a bat file without the Java check. Just put it in the same folder as the original and run this one instead. Let me know how you get on. Java also needs to be callable from the command line. To check this is working you should click on Run... within Windows, type cmd, click OK and type "java -version" (without quotes) and press Enter. This will confirm java is in the command path and print out your JRE build number. I have also updated the release in the OP and removed the Java check, as I have had a couple of similar reports of the loop issue.
Thanks again.
still showing this message attached
TripCode said:
The bat file automatically checks for the presence of java.exe on your system. If it's not found then it starts the install. It would appear that for some reason it's not finding Java and hence why you're stuck in this loop. Please find attached a bat file without the Java check. Just put it in the same folder as the original and run this one instead. Let me know how you get on. Java also needs to be callable from the command line. To check this is working you should click on Run... within Windows, type cmd, click OK and type "java -version" (without quotes) and press Enter. This will confirm java is in the command path and print out your JRE build number. I have also updated the release in the OP and removed the Java check, as I have had a couple of similar reports of the loop issue.
Thanks again.
Click to expand...
Click to collapse
Still showing the attached message
mesho_alaa said:
Still showing the attached message
Click to expand...
Click to collapse
This sounds to me like you need to update your PATH Environment variable with the directory in which java is installed.
Open up a DOS window and type: "where java" (without quotes) to determine possible locations.
If it's located in: "C:\Windows\System32" then the following code should suffice:
Code:
set PATH=%PATH%;C:\Windows\System32
If it's located in: "C:\Program Files\Java\jre7\bin" then:
Code:
set PATH=%PATH%;C:\Program Files\Java\jre7\bin
The above needs to be added to the bat script BEFORE Java is called. You can edit the bat script by opening it with Notepad.
Alternatively, you could permanently update the PATH Environment (probably a better method).
To do this you would: Right click on "Computer" or "My Computer", within Windows Explorer, choose "Properties", click on the "Advanced system settings" and/or the "Advanced" tab, then click on the "Environment Variables" button. Select the "PATH" line, click the "Edit" button, and add the relevant directory to the end of any text that exists for PATH, prefixing the java path with a ";" (semicolon) if this line already contains other string paths. If PATH does not exist then you will need to add it. Sorry this paragraph is a little double-dutch (trying to cater for multiple versions of Windows).
Many thanks! I'll test when home and let you know.
Just to let know, the path command do not fix the prior version with Java check as I first thought this might be the problem.
Thanks!
Mia
Could even be use with ADB from phone to phone? without using the pc? Or I must install the app on the phone and do it offline?
I have find my way! Re-installed Java, manually clicked on java.exe stored in Java folder in Program files (or Program files (x86) ) I've clicked on Javacpl as well and enabled all options, not sure if this is necessary though.
I've then rerun the program without Java check (the Java check one is bugging now) and was able to do the back up.
Thanks!!
Best regards,
Melanie
Cannot tap button
Hi! i've done all the previous steps, but when i unlock the phone, to confirm the backup, i cant tap on "back up my data", it doesnt even grey at hover, just like the button wasn't there...
I can choose not to backup, that button works perfectly, and write the password too, i've tried all the screen, but nothing happends, so i can't backup the phone...
Does anyone think how to solve that? Thanks!
Permission denied
Hi, I followed all instructions and I generated this error.
I would appreciate your help.
Error
mesho_alaa said:
Still showing the attached message
Click to expand...
Click to collapse
I, too am showing the same error.
Curwens said:
Hi! i've done all the previous steps, but when i unlock the phone, to confirm the backup, i cant tap on "back up my data", it doesnt even grey at hover, just like the button wasn't there...
I can choose not to backup, that button works perfectly, and write the password too, i've tried all the screen, but nothing happends, so i can't backup the phone...
Does anyone think how to solve that? Thanks!
Click to expand...
Click to collapse
Try rebooting the device and trying again. If it is still greyed out, the backup feature maybe disabled on the device. Some manufacturers / service providers have specifically disabled usb backups.
kharloz_jc said:
Hi, I followed all instructions and I generated this error.
I would appreciate your help.
Click to expand...
Click to collapse
cardinalaa said:
I, too am showing the same error.
Click to expand...
Click to collapse
It would appear that the key was extracted, but the "copy" wasn't pushed to the sdcard. KitKat? You don't need a copy of the key on your sdcard unless you want to use a supported app. As the key was extracted successfully, you could attempt to copy it by other means.
TripCode said:
This sounds to me like you need to update your PATH Environment variable with the directory in which java is installed.
Open up a DOS window and type: "where java" (without quotes) to determine possible locations.
If it's located in: "C:\Windows\System32" then the following code should suffice:
Code:
set PATH=%PATH%;C:\Windows\System32
If it's located in: "C:\Program Files\Java\jre7\bin" then:
Code:
set PATH=%PATH%;C:\Program Files\Java\jre7\bin
The above needs to be added to the bat script BEFORE Java is called. You can edit the bat script by opening it with Notepad.
Alternatively, you could permanently update the PATH Environment (probably a better method).
To do this you would: Right click on "Computer" or "My Computer", within Windows Explorer, choose "Properties", click on the "Advanced system settings" and/or the "Advanced" tab, then click on the "Environment Variables" button. Select the "PATH" line, click the "Edit" button, and add the relevant directory to the end of any text that exists for PATH, prefixing the java path with a ";" (semicolon) if this line already contains other string paths. If PATH does not exist then you will need to add it. Sorry this paragraph is a little double-dutch (trying to cater for multiple versions of Windows).
Click to expand...
Click to collapse
Hi, I am receiving the "Cannot find the path specified" error. I have tried both changing the script and also the other method, in environment variables. I am curious if this has anything to do with the fact that its an ATT phone (since no one can even root it yet)? No other apps can access my phone, either. I have USB debugging enabled and all prerequisite programs installed. Tried on 2 computers, win7 and win 8.1
I wonder if i it is an error on my part..?
TripCode said:
Try rebooting the device and trying again. If it is still greyed out, the backup feature maybe disabled on the device. Some manufacturers / service providers have specifically disabled usb backups.
It would appear that the key was extracted, but the "copy" wasn't pushed to the sdcard. KitKat? You don't need a copy of the key on your sdcard unless you want to use a supported app. As the key was extracted successfully, you could attempt to copy it by other means.
Click to expand...
Click to collapse
I have reviewed the "Extract" folder and there was the key. I have managed to decrypt it.
Thanks for the help and the tool!
PD: sorry for my bad English, I use translator is haha.
Nothing happens
Hi, first, thanks for this iniciative. A lot of people would apreciate this
I think I did everything as u said, but when I open the WhatsAppKeyExtract,bat and then conect my phone in debuggin mode to PC, nothing happens. Ive waited for 10 minutes and.. nothing happens. Keep showing the initial message: "Please connect your Android device..." and in my phone nothing happens too. Just show a messagem at the upper tab saying: "USB debbugin conected".
Theres any kind of setting to do futher in the debbug options?
Thanks
Update: I had do install de universal adb driver for my phone, and now it starts the download, but now im having problem with java... the messagem says "'java' isnt a recognizable command". I tried all solutions in this post and nothing.. I need heeeelp!
Solution to path problem
Is working perfect. For someone else that can happen the same thing as me. I have to fix something (i am spanish) about:
java is not recognized as an internal or external command, operable program or batch file
Here is the solution:
java .com/en/download/help/path.xml
Or here:
1. Right-Click My Computer and select Properties
2. Then Click The Advanced Tab
3. Then Click Environment Variables
4. Select Path In The Bottom Box and Click Edit
5. Find Where You installed Java (E.g "C:\Program Files\Java\bin)
Its different on each computer
6. Make Sure to add a semicolon after the word bin in the path to seperate it from the other important paths
7. If this doesnt work then you may have to reinstall Java and Try Again
Setting Path on Windows
For Windows XP:
1. Start -> Control Panel -> System -> Advanced
2. Click on Environment Variables, under System Variables, find PATH, and click on it.
3. In the Edit windows, modify PATH by adding the location of the class to the value for PATH. If you do not have the item PATH, you may select to add a new variable and add PATH as the name and the location of the class as the value.
4. Close the window.
5. Reopen Command prompt window, and run your java code.
https://www.dropbox.com/s/nm1goi6m0oob15u/Screenshot 2014-06-15 22.25.27.png
I am getting this error.
using java run time 7 update 60
any ideas?
Thanks!
tzuyang said:
https://www.dropbox.com/s/nm1goi6m0oob15u/Screenshot 2014-06-15 22.25.27.png
I am getting this error.
using java run time 7 update 60
any ideas?
Thanks!
Click to expand...
Click to collapse
Have seen this error before (not related to bat file). You may need to revert to an earlier Java version.

Android X-86 Guide for multi-boot with Windows 10 (dont do what i did)

So it has been a hectic few days for me as I had alas managed to wipe my system reserved partition thinking that installing android x86 as multi-boot would actually boot windows for me. Wrong!!! My first poor encounter was the fact that when I had installed windows it had created the system reserved partition as ntfs... I had not realized this when attempting to install android x-86 as multi-boot. I will tell you the result, when booting it would appear to go to grub, however instead it just booted the first menu on the list without hesitation and gave no menu at all. To remedy this I had to use the windows 10 usb i had created for my initial install. I am still not sure how i managed to get it to boot the first time I think it may have just been dumb luck. When windows booted up i went to Disk Management (right click the windows menu and select from the drop down) where I then proceeded to delete the system reserved partition and reformat it fat32. At this point I was satisfied that android would point the out the windows boot, boy was I wrong. After installing Android x86 (_64 8.1 r3) I finally achieved the grub menu boot correctly. I also noted that when installing android x86 the only way it gave me option to add windows to grub was if i had installed without formatting first. (this can be done a few ways including just reinstalling much the same way you would dirty flash a rom on a phone) or you could use a tool to format the partition such as gparted or a linux live cd/usb. I suggest ext4. Oh wait my nightmare hadn't finished yet... Android x86 install had no problems at all (select partition to install(ext4)... do not format... install grub... yes to windows... yes read write... and then reboot) on reboot windows was in the grub menu and I selected it... oops there is no operating system!!! Well that is unsettling... ( I managed to get back into windows using the install media) and not so sure how. At this point i notice that my system reserved partition was now sda 3) So my next objective was to create a boot record for windows which could have been done easily from windows had I considered using bcdedit tool for windows. But since i knew that the partition was sda 3 I figured I could just point the grub menu to the correct drive... again wrong (there was still no boot mbr on that partition *sigh) Well I found that when i went into command line from the windows repair tool it would say I do not have permission to fixboot... wow nice job microsoft... after doing a bit more research I learned that the newer builds give this error when attempting to fix boot. I found a video on youtube which helped me alot but took quite a while to download the older working repair tool(installation media) but his video was fairly well put together. link here (https://www.youtube.com/watch?v=lRCyb7FzWFY). I followed his guide and this time with the repair tool that he shared in the description of his video, I was able to perform the fixboot (bootrec /fixboot) however one of his commands required the copying of bcd to the system reserved partition. The copy failed, however at this time running all the other bootrec commands seemed to go fine. So I exited command and went to the automatic startup repair, which to my surprise worked perfectly... (after a whopping 30 some hours of pulling my hair out of my head over this mess) And windows began to boot. At this point I gave my thanks to the poster of the video and shared my experience with his video in the comments below.) Now When windows booted up I downloaded the bcdedit tool. Personally I used the multi boot tool from this site (https://www.boyans.net/dual-boot-repair-windows-10.html) and selected repair mbr and boot record. This fixed my boot issue windows would boot normal at reset. However now my android was gone but thats okay.
At this point I just reinstalled the android x86 again over the same ext4 partition without formatting and added the windows to grub. This was perfect however when selecting windows did not boot. To fix this I had to edit the grub menu.lst and change the drive from hd(0,0) to hd(0,2) to point to the fat32 partition which had been somehow displaced to sda3. In order to do this I ran android in debug... when debug is running just hit enter and it give you a prompt... from prompt type without quotes "cd /mbr/grub" when the next prompt comes up you should be in the grub directory where the menu.lst is. Now type without quotes "vi menu.lst" this will take you into a text editor (note you can also change your monitors and resolution permanently in grub menu this way) using the arrow keys navigate to the line you want to edit, in my case the last entry which was windows entry when you get to where you need to edit hit the "i" key this will allow you to now enter and edit the text. After making changes hit "esc" to save changes type ":w!" then hit enter. To exit type ":q!" this will take you back to prompt. Now reboot your system and finally the results I had originally hoped for a multi-boot system with windows 10 and android. Now if you are attempting to do this and are looking for a guide to install I will make this just a little longer to make sure you dontt make the same mistakes I made.
1a) before you attempt to install a dual boot with grub... make sure your system reserved partition is fat32 if it is not you need to change it to fat32. as grub will not boot on ntfs partitions.
1b)you will need to have a blank partition, if you have spare room on the drive you can shrink your volume and create a new one. There are plenty of tools out there to format ext4 even from windows. Make sure you format it before installing. (if you are lazy like me you can format ext 4 from the installation, but there is a chance that you would need to reinstall again and choose not format to get the windows entry in grub)
1c)once your partitions looks the way you need and you have a working fat32 system reserved partition you are ready to move on. ( If you have to change a ntfs partition to fat32 I highly suggest you dont install anything until you have repaired the boot menu and tested it first to make sure it works)
2)create your install media... I prefer to use rufus as it is quick and easy, and I prefer the official android x86 as the 8.1 r3 is stable and works great, you can use whatever image you want though, lord knows i test newer versions as they come out. when you have rufus and the android x86 iso of your choice load rufus select your usb drive and select the iso with the browse button. then just hit start allow it to format and when it is done you can boot into your usb
3)To boot into your usb you may actually need to edit your bios and enable virtualization and make sure safeboot is not enabled, also you need a uefi system for x64 distros so if you have an older legacy bios you will need the x86 version instead or the system wont boot
4)When you finally get it to boot you will find the menu to use it as a live cd or install, select the install.
5a) You will now be asked where to install to. Pick the ext 4 partition you created for it.
5b) Now it will ask you to format choose do not format (again if you hadn't formatted the partition ext4 you may do it now, but you may have to reinstall and not format the next time to add windows to the grub menu)
6) You will now be asked to install grub answer yes, if you do not answer yes you wont be able to get back into your android partition again until you do.
7) Now it will tell you that it found a windows partition and asks you if you want to add an entry, select yes... if you do not you will have to make your own grub entry to get back into windows later or completely delete grub from the partition later.
8) Finally it will ask you if you want to make the system read write... select yes, if you select no i can not guarantee you will be able to install anything inside of the system.
10) The end... Installation finishes but do not click launch... instead click reboot. The reason for this is that I have noticed if you launch at the end of installation the grub somehow manages to disappear and you end up having to completely start over.
Enjoy your android x86 / windows multi-boot system.
make sure your system reserved partition is fat32
Click to expand...
Click to collapse
There is no system reserved partition on my laptop since I have a UEFI laptop.
Should I proceed ?

Categories

Resources