Develop Bugs

Custom splash image

I have attached all the files needed to do this on windows, mac, and linux at the end of this post. The creation of these apps, goes to the respective people, including Koush, JF, Infernix, and alansj.
Want to get rid of that t-mobile boot image?
Disconnect, over at Gotontheinter.net, has figured out how to do it using the new unlocked bootloader from the g1 dev phone. Below is a quote from the source. ( http://www.gotontheinter.net/node/9 )
"So you want to join the party and flash your own boot image, but its a weird undocumented format and you don't want to spend all year researching it in the source. Well, I'm here to help.
It is actually very simple. Start with an image you want to use, make sure it is 320x480 with 8bpp color. (In my examples, I'll use splash.png: PNG image data, 320 x 480, 8-bit/color RGBA, non-interlaced
Just make sure you have ImageMagick installed, and the utilities from the source build. (Specifically, rgb2565.)
$ convert -depth 8 splash.png rgb:splash.raw
# Make sure it is 460800 bytes long!
$ rgb2565 < splash.raw > splash.raw565
# Triple-check size before flashing! 307200 bytes
$ fastboot flash splash1 splash.raw565
$ fastboot reboot
Lets break it down. the convert turns it from a png (or any supported image format) into a raw 8-bits-per-color no-alpha data file. This file should be 460800 bytes - no more, no less.
Next, rgb2565 converts that file to a raw 565 16bit file (for the framebuffer on the G1.) This file is exactly 307200 bytes long - if its not, you messed up somewhere.
Finally, you use fastboot to flash the splash image and reboot. Instead of the B&W T-mobile logo, now you will see your custom splash screen. Congrats! "
Thanks to Infernix for the following extended how to:
1. find an image you like
2. edit it with your favourite editing suite and scale it to 320x480
3. after scaling it, convert the colorspace to 256 colors (8-bit)
4. Save it as a PNG without alpha channel/transparency.
5. Use the convert tool from the ImageMagick toolkit (use cygwin, or a linux box): convert -depth 8 splash.png rgb:splash.raw
6. Check that the splash.raw file is exactly 460800 bytes!
7. Compile the android tool called rgb2565 (gcc -O2 -Wall -Wno-unused-parameter -o rgb2565 to565.c)
8. Run the conversion command: rgb2565 < splash.raw > splash.raw565
9. Check that splash.raw565 is 307200 bytes. if it isn't, DO NOT FLASH IT ON YOUR PHONE. double-check your steps, something went wrong.
10. Boot your phone in SPL mode (hold camera +power).
11. After SPL shows, plug in USB connector/cord/whateva and push trackball or hit back. SPL restarts and now shows FASTBOOT.
12. If on windows, you need to install http://dl.google.com/android/android_usb_windows.zip
13. Compile android (see http://source.android.com/download) and make sure the fastboot binary (mydroid/out/host/*/bin/fastboot) is compiled (* being your OS)
14. use fastboot devices to check whether if your phone is showing up. if it isn't, try it as root (user might not have permission to access the usb device).
15. Double check that splash.raw565 is 307200 bytes. if it isn't, DO NOT FLASH IT ON YOUR PHONE.
16. Flash the splash image: fastboot flash splash1 splash.raw565
17. Reboot your phone to check: fastboot reboot
The instructions below are for users trying to flash their own boot image using windows.
The instructions below are also JF's work and not my own:
Instructions:
(note: you have to check the USB device in Computer Manager when the phone is in fastboot mode. The computer sees the phone in fastboot mode as a different device than the phone in normal mode)
Download the file and extract it in the same folder as adb. (if you don't have adb yet, it's included in the android SDK for windows. go download it!)
Take out the usb cable and boot up your phone into the SPL (back + power). You have to have the dev bootloader for this to work (white background with 3 skateboarding androids).
Plug in the usb cable, and make sure the display on the phone changes from "Serial0" to "FASTBOOT". If it doesn't, try pressing the back button.
If it asks you to install drivers, then go ahead and use the same usb drivers that you used to get adb working. You can skip the rest of the instructions. Fastboot should be working for you now.
If it doesn't ask you to install a driver, you need to figure out if the correct driver is loaded already.
Right click on My Computer, and click Manage, then go to the device manager
If you see an "ADB Interface" category at/near the top, with "HTC Dream" under it, then you're good to go. Fastboot should be working for you.
If you don't see an "ADB Interface" category, then it's likely that windows loaded the USB Mass Storage driver for it automatically. In the device manager, go down to "Universal Serial Bus Controllers", and see if you have at least one "USB Mass Storage device". If you have multiple ones, you'll need to go through each to find the correct one.
To find the correct one, right click on the USB Mass Storage device and click Properties. Go to the Details tab. In the combo box at the top that says "Device Instance Id", bring up the pull down and choose "Compatible Ids". If that is the correct device, then you will see 3 entries:
* USB\Class_ff&SubClass_42&Prot_03
* USB\Class_ff&SubClass_42
* USB\Class_ff
Once you find the correct device, go to the driver tab, and click "Update Driver". Choose "No, not this time", then "Install from a list or specific location", then "Don't search, I will choose the driver to install", and then choose the same usb driver that you used to get adb to work.
After that's done, you should be good to go. Open a command prompt and type fastboot devices and it should list the phone.
Here is a very good set of instructions for applying this to your phone if you haven't gotten it already: http://forum.xda-developers.com/showthread.php?t=467064
Additional Information
-
-
another way to convert to 565 raw, but from ANY format, is to use ffmpeg like so:
ffmpeg -i input.png -f rawvideo -pix_fmt rgb565 output.565
where input.png could be jpg, gif, tiff, etc. whatever you want.
-
-
credits for this goes to
Clone137
Heres some info about FFmpeg and where you can download it: FFmpeg
Stericson

“It won't work,” droned Marvin, “I have an exceptionally large mind.”

It's possible to modify the code to show a different startup animation: for example, the cylon strobing eye animation that was present up till Android V0.9.
Check out \frameworks\base\libs\surfaceflinger\BootAnimation.cpp. Just need to redeploy the one surfaceflinger file to see the changes.

Stericson, You ROCK!

I'm getting hung up at this line
fastboot flash splash1 g1-splash.rle
it says g1-splash.rle not found. what'd i miss? everything else has worked like a charm thus far.

Correction in instructions:
$ rgb2565 < splash.raw > splash.raw565
# Triple-check size before flashing! 307200 bytes
$ fastboot flash splash1 splash.raw565
$ fastboot reboot

Stericson said:
This file should be 460800 bytes - no more, no less.
Click to expand...
Click to collapse
460800 shall be the size of the file, and the number of bytes in the file shall be 460800. 460801 shalt not the size of the file be, neither shall the size be 460799, excepting that thou then append a byte to 460800.
460802... is right out.
Once the file size 460800, being the 460800th byte be reached, flasheth thou thy boot image onto the G1, who, being naughty in my sight, shall display it.
(note: please read the instructions, and don't actually flash a file that's 460800 bytes long. I had to take some artistic liberties here )

Ok, now the terminal just hangs on
< waiting for device >
Is the phone supposed to be in recovery? I've tried that, but have had the same results. I have the /system mounted and the phone is on a jailbroken RC30 (1.2). And it also is running the Dev 1 bootloader. Any helpful hints?
[edit]
when i do an 'adb devices', the phone is listed...

can I do this using windows? I made an image, with paint shop pro, and used convert to convert it to the raw format and it turned out to be 403,200 bytes, is that wrong? What did I do? Also, can I use rgb2565 on Windows? or do I have to run this in linux? Lastly, when using fastboot, do I boot my phone into the dev bootloader and connect to it via adb shell and then type that command?
Any help would be great!

OK let me extend the howto:
1. find an image you like
2. edit it with your favourite editing suite and scale it to 320x480
3. after scaling it, convert the colorspace to 256 colors (8-bit)
4. Save it as a PNG without alpha channel/transparency.
5. Use the convert tool from the ImageMagick toolkit (use cygwin, or a linux box): convert -depth 8 splash.png rgb:splash.raw
6. Check that the splash.raw file is exactly 460800 bytes!
7. Compile the android tool called rgb2565 (gcc -O2 -Wall -Wno-unused-parameter -o rgb2565 to565.c)
8. Run the conversion command: rgb2565 < splash.raw > splash.raw565
9. Check that splash.raw565 is 307200 bytes. if it isn't, DO NOT FLASH IT ON YOUR PHONE. double-check your steps, something went wrong.
10. Boot your phone in SPL mode (hold camera +power).
11. After SPL shows, plug in USB connector/cord/whateva and push trackball or hit back. SPL restarts and now shows FASTBOOT.
12. If on windows, you need to install http://dl.google.com/android/android_usb_windows.zip
13. Compile android (see http://source.android.com/download) and make sure the fastboot binary (mydroid/out/host/*/bin/fastboot) is compiled (* being your OS)
14. use fastboot devices to check whether if your phone is showing up. if it isn't, try it as root (user might not have permission to access the usb device).
15. Double check that splash.raw565 is 307200 bytes. if it isn't, DO NOT FLASH IT ON YOUR PHONE.
16. Flash the splash image: fastboot flash splash1 splash.raw565
17. Reboot your phone to check: fastboot reboot
This list together with instructions at http://www.gotontheinter.net/node/9 should get you going.
The tools mentioned here are commandline tools.
I have attached static versions of the tools mentioned for linux x86 to this thread. However I can't guarantee that they will work for you. they should, though.

A quick note: you can save directly to raw format from gimp or photoshop (allowing you to skip the imagemagick step). It just has to be 8-bit (which has been the default when I tried it).
Also, I attached rgb20565 and fastboot compiled for OS X 10.5.

Could someone upload the compiled binaries for Windows for those lazy people out there (me included)?

Here is the compiled binary for rgb2565
I don't have the compiled binary for fastboot, hopefully someone else will post it for you guys...I found it easier, way easier, to do this on a linux box.

After a bit of tinkering, i finally got it. The biggest problem i was having was that after i booted into the SPL, THEN i was supposed to connect the USB cable... i had it plugged in and then tried to boot SPL and nothing happened. Everything is great now. Big thanks

Thanks Stericson for the compiled rgb2565 file(for windows)
Can someone please upload the fastboot binary? I don't know how to compile it myself....Thanks a lot in advance for everyones previous hardwork on this and forthcoming.

to build the file yourself go to the root android source directory (mine is linux, but it looks like this "/home/ryan/android_source"), your's might look something like "C:/Source Codes/android/" or whatever. Once you navigate to that directory (via the command prompt... just go to start > run > and type in 'cmd' and hit enter, then use the 'cd' command to get there... e.g., "cd C:/Source Codes/android/"), once there, simply type 'make' and hit enter and it will start building everything, it might take a few minutes to complete. Then just go into the 'out' directory, then it's under "host/windows-x86/bin" (i'm not sure about the windows-x86 part, it might just be windows or something like it, i'm just assuming based on mine), once in that folder you'll have the fastboot as well as all of the other binary files ready to go. Then you can just type fastboot w/e w/e and it'll work just fine.
Here's my updated bootloader logo:
It's kind of difficult to see, my camera sucks... it's my fraternity letters with the crest in the background. Here's the image i used for it:

big head white robot guy
Id like to have the big head robot one in the first of this post, mind sharing the properly pressed,flipped,shook,stirred and what not, Id just like to dump the tmob splash, really anybody who has tried tested images attach them here, if you don't mind sharing...
just figured I'd ask as I didnt see any posted anywhere I don't always do so well at looking for stuff, at least thats what my wife is always b1tchen in my ear...
bhang

Ok, I'm sure I can do that, but now how do I get the android source onto my windows installation? Do I use cygwin? How, if so?
Thanks so much....
BTW, I've tried googling this, and still am, with no luck, thusfar.

Here's what I finally settled on.
Take 2...

Awesome, thanks for the help!
You mentioned that disconnect figured out how to do it with a dev bootloader - does this mean my rooted rc30 phone should be upgraded to a dev phone bootloader for it to work? Or will I be able to perform it on my modified rc30 v1.2 setup?
thanks
edit: nm, figured it out thanks! here's a pic:

[Q] How to root SM-T113 ?

Hello, i have one question.
I have a Samsung Galaxy Tab 3 7.0 ( SM-T113 ) i can't find any rom and root package for my pad.
Maybe someone can help me?

I support this request. The T113 is a new device. I was thinking of getting me a cheap t110, but the t113 is also cheap. If it would be possible to root this I would take it.

Rooting SM-T113
Hello everybody
I struggled to root my Samsung Galaxy Tab 3 Lite
(SM-T113). So I decided to shared my experience and writing this tuto.
Of course, this is "a non standart" device, and elements for rooting
SM-T110 or SM-T210 didn't work. Android version of this device is 4.4.4
Methodology and tries :
I have proccured myself the Samsung official firmware (here). This image
allow me to get back during beetwen the experimentations. I tried several
experimentation and restore the device after each fail.
Installing with Odin the Clockworkmod (CWM) for SM-T110 , for SM-T210, and
SM-T211. (Has preconnised here) Each time, when loading the CWM, I got a little
(1 ascii character) exclamation mark at the top-left of the screen. The device
didn't boot on recovery
Installing with Odin the (TWRP) for SM-T110. Same symptom
Installing philz_touch : against the message with only the red exclamation
mark.
I conclude of checked of some signature before executing recovery.
Using Kingo root application : software try to root during 20 minutes and
finaly fail.
Using Towel root application : The device isn't reconized
Conclusion: Security breach for rooting have been fixed in this version of android
I have downloaded UPDATE-SuperSU-v2.46 for android. The idea is to push this
application by the standart android update way. (native recovery).
Sending the zip archive 'as is' => failure to check the whole archive
Re-sign the archive with the autosign tools => failure to check footer of archive
Rewriting the update-script (see here) and (here) and auto-sign the archive
: failure to check footer
I am procured myself some pre-rooted image. Odin fail to import them. (and I
have no succed to use heimdall for linux on my debian)
I have try to improve the official samsung Image by adding root manually , using
simg2img and make_ext4fs. Odin fail at the same point
It's remaining me two way : Or I try to generated a correct update file, or I
try to understood why odin fail to import prerrooted system and my custom
image. I choosed the second option.
The offical update is splited by several blocks, each block having is own
header. A master header provide global information about the image (number of
blocks, size, ...). I have putting some spies in simg2img and
observate the headers of official update and of my custom uptate. Result is
surprising : It is missing 4 bytes by headers. in custom update. According to
samsung orginal update, missing values seem to be constant. I suppose it's a 'magic
number', checked by the device to be sure the 'good' update is applied. So I
modifed this headers in make_ext4fs for adding the missing constants. My custom update is now
accepted by my devices, and I got root (!)
I will now describe how to generate and import this update.
DISCLMAIMER
I or Xda-developers are not responsable of any damage one your device, in particular if you bricked it
You waranty will probably void
Rooting device may lead to some dysfonctionnement, or may open some security breach. You are the only responsable.
1. What do you need :
Your device, and a cable to connect it to your PC
A Windows distribution, with Odin (www (dot) samsungodindownload (dot) com/) and the samsung drivers (www (dot) samsung (dot) com/us/support/owners/product/SM-T110NYKAXAR#")
A Linux distribution, with the appropriate compilation package (build-essential), and with git.
A way to transfers big files beetwen your Linux and your Windows.
The Official samsung update (best-tech-reviews (dot) com/update-sm-t113-t113xxu0aoa4-android-4-4-4-2152 or rapidgator (dot) net/file/7140bfdc421eea86eda5a5cbca00216e)
The UPDATE-SuperSU-v2.46 in zip format (download (dot) chainfire (dot) eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1") (or root program for your android)
Method assume you never installed root on your device
2. Generate the update
Uncompress the Samsung official image.
Code:
unzip image_official.zip
tar -xf image.tar.md5
Uncompress and make_ext4fs and simg2img (here)
Code:
cd ..
git clone https:// github.com/YuLaw/ext4-utils.git
cd ext4_utils
Download and applied the patch (see attachment)
Code:
patch -p1 < ../patch_ext4_utils.diff
Build ext4_utils
Code:
make
Extract the image
Code:
cd ..
unzip DBT-T113XXU0AOA4-20150121104149.zip
tar -xf T113XXU0AOA4_T113OXA0AOA4_HOME.tar.md5
ext4_utils/simg2img system.img system.img.raw
Mount the image
Code:
mkdir mount_point
sudo mount -o loop,rw system.img.raw mount_point
unzip the UPDATE-SuperSU-v2.46
Code:
mkdir UPDATE-SuperSU-v2.46
mv UPDATE-SuperSU-v2.46.zip UPDATE-SuperSU-v2.46/
cd UPDATE-SuperSU-v2.46/
unzip UPDATE-SuperSU-v2.46.zip
cd ..
Now, copy common file and armv7 one the mount_point. If you use an other
device, replace the armv7 repository by the appropriate repository according
to your device processor. You can refer to the
UPDATE-SuperSU-v2.46/com/google/android/update-binary to find them.
Code:
sudo cp UPDATE-SuperSU-v2.46/armv7/{su,supolicy} mount_point/xbin
sudo cp UPDATE-SuperSU-v2.46/armv7/su mount_point/xbin/daemonsu/
sudo cp UPDATE-SuperSU-v2.46/armv7/libsupol.so mount_point/lib
sudo mkdir mount_point/etc/init.d
sudo cp UPDATE-SuperSU-v2.46/common/99SuperSUDaemon mount_point/etc/init.d
sudo cp UPDATE-SuperSU-v2.46/common/Superuser.apk mount_point/app
sudo mv mount_point_app/etc/install-recovery.sh mount_point/etc/install-recovery.bak
sudo cp UPDATE-SuperSU-v2.46/common/install-recovery.sh mount_point/etc
sudo chmod 0755 mount_point/xbin/daemonsu
sudo chmod 06755 mount_point/xbin/su
sudo chmod 0755 mount_point/xbin/supolicy
sudo chmod 0644 mount_point/lib/libsupol.so
sudo chmod 0755 mount_point/etc/install-recovery.sh
sudo chmod 0744 mount_point/etc/init.d/99SuperSUDaemon
sudo chmod 0644 mount_point/app/Superuser.apk
We will regenerate the file system. Do not umount them. If patch on
ext4_utils is not applied, you shall applied it now.
Code:
mkdir output
sudo ext4_utils/make_ext4fs -s -a system -l 1500M output/system.img mount_point
cd output
tar -cf system.img system.img.tar
md5sum -t system.img.tar >> system.img.tar
mv system.img.tar system.img.tar.md5
You can now transfert this file to your windows operating system.
3. Android prepartion
You must ensure your device is allowed to install apk from untrusted source. See
in option/application or in developper menu option
Connect the android to you pc.
Boot your android device into downloading mode. On SM-T113 Samsung galaxy Tab3 lite,
press power, volume down and pad when booting.
Run odin, ensure Repartion is NOT checked, and select the AP (PDA) button. (The
only checked case is autoreboot and F.Reset time) Load the previously generated
file and click start.
Your android device may now reboot and install the root application.
Congratulation, you have now rooted your device. You can clean up the downloaded files.
4. One of these step fail, what I can do to come back. :crying:
You may import with odin the official samsung firmware or proceed to a factory return from the recovery.
5. May I eat my devices if I can't root it ?
Samsung user manual say to not do it.

samsung tab 3 sm-t113 root
Thank for the update about for the root. But I don't have Linux and I don't know how to use Linux too. It's there a way without Linux

If you don't have linux, you can try using Cygwin. This is a linux like environment running on Windows.
or if you find my solution is too complicated, I do it for you.
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
https://drive.google.com/file/d/0Bwao3SgtdOPPYm9XNF8wQXEyWjg/view?usp=sharing
unzip file and upload it to you device with Odin
Nb: This file will remain on my google drive until I need space or until I decide to remove it. (in a long time)

grizzlyfute said:
If you don't have linux, you can try using Cygwin. This is a linux like environment running on Windows.
or if you find my solution is too complicated, I do it for you.
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
unzip file and upload it to you device with Odin
Nb: This file will remain on my google drive until I need space or until I decide to remove it. (in a long time)
Click to expand...
Click to collapse
Thank you for your great work!!
Do you think the package will work also with Tab3 lite SM-T116? (Sm-t116 should have only the 3g module more than sm-t113)

Root Worked
Thanks for the your great effort grizzlyfute.
Worked perfectly and finally got my device rooted

beodev said:
Do you think the package will work also with Tab3 lite SM-T116? (Sm-t116 should have only the 3g module more than sm-t113)
Click to expand...
Click to collapse
No. Package will erase the system partition, including configuration file (/system/etc), and probably some drivers. Importing the SM-T113 package will probably put the 3G module out of service.
I suggest you to procure an 'official firmware' for your device (see in Settings/about for the exact version) and follow procedure in post#3.

grizzlyfute said:
No. Package will erase the system partition, including configuration file (/system/etc), and probably some drivers. Importing the SM-T113 package will probably put the 3G module out of service.
I suggest you to procure an 'official firmware' for your device (see in Settings/about for the exact version) and follow procedure in post#3.
Click to expand...
Click to collapse
I tried to follow your linux-instructions (by using cygwin, with an official sm-t116 firmware), but something go wrong (i think cygwin doesn't know batch commands like "sudo", or "su" etc..).
I put your md5 file to my sm-t116: the results is that the device is rooted, but no network connection works (Wi-Fi too) .
I jump back to the original firmware, maybe in the future someone will develop the firmware for the sm-t116 version.
Thank you for the Help

Thanks buddy! It works! :good:
Just got my t113 today and now rooted. Awesome!

Light at end of tunnel
grizzlyfute said:
...
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
https://drive.google.com/file/d/0Bwao3SgtdOPPYm9XNF8wQXEyWjg/view?usp=sharing
unzip file and upload it to you device with Odin
...
Click to expand...
Click to collapse
FABULOUS!!! And thank you! And have i said fabulous? And thank you??? And this, only for giving me rooting hope!
I am a proud user of a gt-i9100 for a few years, rooted/unlocked/custom rom(ehndroix), so, all the 9 miles, but, that´s the phone... And since i am not very proficient when it comes to using odin, and if you don´t write all the steps, i am like a fish out of water (can´t breathe or swim) and i am afraid to do some wrong step.
So, when you say upload it to your device, which will be the parameters in ODIN?
Edit: I confirm, it works, i was afraid of doing something wrong and brick the thingy, but its working fine, thanks to odin and pda and this developpers work!:victory:
!! Thanks !!

I followed these instructions step-by-step on my SM-T113, but for some reason the device would always fail to receive the image I'd built (Odin would just sit there saying NAND Write Start! for a while, then fail. So I tried downloading your precompiled version... and what do you know, it worked straight away.
Thanks a ton, HUGE help!

(q)how to root tab sm-t116nu ?
please help me

cjmac said:
I followed these instructions step-by-step on my SM-T113, but for some reason the device would always fail to receive the image I'd built (Odin would just sit there saying NAND Write Start! for a while, then fail. So I tried downloading your precompiled version... and what do you know, it worked straight away.
Thanks a ton, HUGE help!
Click to expand...
Click to collapse
Sorry for the delay.
I encountered the same problems before I make the patch. Cause of the problem is the file generated by ext4_utils tools is not immediately compatible with the sm-t113 device. I have to add constants in the encapsulation headers for the device to accept the file. You can see details in the patch provided.
To determine theses constants, I put some spies in simg2img and extracts the official firmware. It is not exclude these values change in function of the device.
For the sm-t116, I suggest to open an other thread. I think the works can be picked up and adapted.

wifi issues?
Thanks for your work!
I have successfully rooted my tablet, but its now not connecting to a weak wifi signal it was previuosly connecting to. In fact, it previuosly rratd the same signal as "fair".
Is this connected in any way to the rooting package, and can be resolved somehow?

Hello, thanks for your help! now, i have my Samsung SM-T113 rooted.
but, there any way to put the cmw?
I want to make a backup image and not as .... thanks

Anyone know if this way working in model SM-T113NU ?

Samsung official image ?
grizzlyfute said:
2. Generate the update
Uncompress the Samsung official image.
Click to expand...
Click to collapse
I don't understand what is the "Samsung official image" :
i don't see it neither in the 1. What do you need : list , nor in attached files
I thought it could be "The Official samsung update ", but its name is not "image_official.zip" I see in the first line of code, and moreover I see "unzip DBT-T113XXU0AOA4-20150121104149.zip" in the following lines.

any chance to make more easy the way to get root? btw I have the variant SM-T133NU 4.4.4 KK please!

Minimalistk0 said:
any chance to make more easy the way to get root? btw I have the variant SM-T133NU 4.4.4 KK please!
Click to expand...
Click to collapse
I second that! Rooted custom rom highly appreciated! I'd even pay some bucks

Working method to root the LG G4S (Model H735 / "LG G4 Beat")

Root your LG G4S (Model H735)
Tested on Andriod 5.1.1.
Thanks goes to @konsolen for sharing the method to open up the port (see appendix in this post) and to @dominik-p for his guide to determine dd parameters (you won't need this to root with the method described, but you can back up your phone if you're worried). And most importantly, thanks to the author of SuperSU for his excellent script updater-binary which worked pretty much out of the box, with only a few workarounds needed (which is what the instructions below do).
First, a few general notes:
The supersu.zip included in this package is version 2.46.
SuperSU can be downloaded here: http://download.chainfire.eu/supersu
If you want to use a new version, just put the zip file in this directory and rename it to "supersu.zip" (delete the old one in this package first of course).
The busybox binary in this package was used successfully to unzip in the LG G4s H735 (Android 5.1.1).
Some time it should maybe be ensured that this is the newest version. Same holds for Send_Command.exe and adb.exe (and attached libraries).
This script uses the "update-binary" script of the SuperSU package to install it on your phone.
The scripts I attached prepare for it to be called (hopefully) successfully.
Instructions to root
Preparation
You MAY want to create a backup of your system beforehand, in case things go wrong.
This is optional, so if you don't want to do this, you may still rely on the .kdz file (see Appendix below) to restore your phone if things go wrong.
You need to calculate the dd parameters and then backup your system partition into a .img file.
There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Keep a copy of your system.img somewhere safe, you can use it to restore
your system if something goes wrong.
Enabling developer options and getting the tools
First, enable developer / debugging mode on your phone:
Navigate to Settings > About Phone > scroll to the bottom > tap Build number seven (7) times.
You'll get a short pop-up in the lower area of your display saying that you're now a developer.
Then, go back and now access the Developer options menu, check 'USB debugging' and click OK on the prompt.
Note: You have to enable USB debugging before plugging your device in to the computer. Unplug device then try to enable USB debugging.
On your computer, install Install and Use ADB (the Android Debug Bridge Utility). Also, download LG Flash Tool.
You can find out how to do both by searching google for it.
Step 1.
Connect your phone via USB (not in download mode yet, just normal).
Then, run Init_Root.bat in order to copy the essential files over to internal storage.
You may do this either by 1) double clicking the file, or 2) executing it from the windows command line.
For Option 2): Open a command line in the folder where you extracted this package. To do this, hold shift while right clicking in the folder opened in the Windows Explorer and select "Open command window here". Then, type
Init_Root.bat
Step 2.
Reboot your phone in download mode and ensure it has opened the port to send commands in download mode.
The port is open if it's displayed on the phone's screen in green letters, like
COMX
(with a number instead of X).
On my LG H735 it was necessary to use "LG Flash Tool 2014" http://lgflashtool.com/ to open the port. So if you don't have the green letters, see instruction pasted below (appendix) on how to open the port.
Step 3.
Open a command line in the folder where you extracted this package. To do this, hold shift while
right clicking in the folder opened in the Windows Explorer and select "Open command window here".
Open a command shell to your phone by typing (replace X with the number displayed on your phone) by typing:
Send_Command \\.\COMX
You should be set to root if the following works:
Typing "ls" returns a long list of file and folder names.
Typing "id" should give you someting like that:
uid=0(root) gid=0(root) context=u:r:recovery:s0
The important bits are the "(root)" uid and gid.
If any of the above is not the case, it will not work, you may search for help in the forum.
Step 4.
Execute the commands below (without the numbering of course).
1. mv /data/local/tmp/busybox /sbin/busybox
2. chmod 755 /sbin/busybox
3. mkdir /tmp
4. mkdir /tmp/supersu
5. /sbin/busybox unzip /data/local/tmp/supersu.zip -d /tmp/supersu
6. mv /data/local/tmp/supersu.zip /tmp/supersu/
7. sh /tmp/supersu/META-INF/com/google/android/update-binary dummy 1 /tmp/supersu/supersu.zip
(Note: Not all commands above may be needed, but this is the conservative approach)
Recommended:
Do sanity checks to see if it's doing its job as expected.
After command 2, type the command ls -l /sbin/busybox to check for sanity.
It must return a line like this (with your own date and time):
-rwxr-xr-x shell shell 1048328 <date> <time> busybox
Command 5 must print several lines containing "inflating" messages, similar to this:
Archive:
inflating: META-INF/MANIFEST.MF
...
Command 7 prints lines like this, and other status messages afterwards:
**************
SuperSU installer
**************
...
Step 5.
Your phone should now be rooted if it all worked ok.
You may now type
LEAVE
to reboot your phone.
Happy rooting!
Troubleshooting
If it doesn't work, for example you phone may be stuck on the boot process displaying the LG logo, then you can use Flash Tool to restore your phone. Use instructions below (how to boot the phone into download mode), but don't pull the USB cable, and just let it run its course. This should restore your phone.
If for some reason this hasn't worked, you may try to "dd" back your system .img which you may have created in the preparation step.
Appendix
How to boot the phone into download mode and open the port
a) Boot the LG G4s in download mode. To do this, first switch it off completely and disconnect USB cable. Then, hold the Volume Up button, and while you keep holding it, plug in the USB cable.
b) Start the LG Flash tool and load the .kdz for your phone. We won't actually complete the flashing, you only need it to start the process, but you should use the kdz for your phone nonetheless.
You can check for your kdz on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
c) Now this is very important: Watch your phone while the .kdz is being flashed by the flash tool.
(the flash tool may complain about error connecting to the update server, but you can ignore this with "ok").
As soon as the green letters show up, UNPLUG THE USB CABLE!
The percentage on your phone has to be 0% still (never mind about percentage in the flash tool, it may not even display it).
Then, kill the Flash Tool with the Windows Task Manager (Ctrl+alt+delete).
When it's closed, you can plug your phone back in.
It's now in download mode with open port.

You may also be interested in optimizing your storage & memory after you have rooted:
http://forum.xda-developers.com/general/general/moving-apps-to-sd-optimize-memory-phone-t3248125

LG-H731 Vigor from Videotron/Virgin Mobile
jen.magnolis said:
Root your LG G4S (Model H735)
Tested on Andriod 5.1.1.
Click to expand...
Click to collapse
Also work on phone listed in title:
LG-H731 (LG G4) Vigor from Videotron/Virgin Mobile
Happy rooting
If you need help, don't hesitate to contact me: [email protected] or here =

Hi
jen.magnolis said:
Root your LG G4S (Model H735)
Tested on Andriod 5.1.1.
Thanks goes to @konsolen for sharing the method to open up the port (see appendix in this post) and to @dominik-p for his guide to determine dd parameters (you won't need this to root with the method described, but you can back up your phone if you're worried). And most importantly, thanks to the author of SuperSU for his excellent script updater-binary which worked pretty much out of the box, with only a few workarounds needed (which is what the instructions below do).
First, a few general notes:
The supersu.zip included in this package is version 2.46.
SuperSU can be downloaded here: http://download.chainfire.eu/supersu
If you want to use a new version, just put the zip file in this directory and rename it to "supersu.zip" (delete the old one in this package first of course).
The busybox binary in this package was used successfully to unzip in the LG G4s H735 (Android 5.1.1).
Some time it should maybe be ensured that this is the newest version. Same holds for Send_Command.exe and adb.exe (and attached libraries).
This script uses the "update-binary" script of the SuperSU package to install it on your phone.
The scripts I attached prepare for it to be called (hopefully) successfully.
Instructions to root
Preparation
You MAY want to create a backup of your system beforehand, in case things go wrong.
This is optional, so if you don't want to do this, you may still rely on the .kdz file (see Appendix below) to restore your phone if things go wrong.
You need to calculate the dd parameters and then backup your system partition into a .img file.
There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Keep a copy of your system.img somewhere safe, you can use it to restore
your system if something goes wrong.
Step 1.
Connect your phone via USB (not in download mode yet, just normal).
Then, run Init_Root.bat in order to copy the essential files over to internal storage.
You may do this either by 1) double clicking the file, or 2) executing it from the windows command line.
For Option 2): Open a command line in the folder where you extracted this package. To do this, hold shift while right clicking in the folder opened in the Windows Explorer and select "Open command window here". Then, type
Init_Root.bat
Step 2.
Reboot your phone in download mode and ensure it has opened the port to send commands in download mode.
The port is open if it's displayed on the phone's screen in green letters, like
COMX
(with a number instead of X).
On my LG H735 it was necessary to use "LG Flash Tool 2014" http://lgflashtool.com/ to open the port. So if you don't have the green letters, see instruction pasted below (appendix) on how to open the port.
Step 3.
Open a command line in the folder where you extracted this package. To do this, hold shift while
right clicking in the folder opened in the Windows Explorer and select "Open command window here".
Open a command shell to your phone by typing (replace X with the number displayed on your phone) by typing:
Send_Command \\.\COMX
You should be set to root if the following works:
Typing "ls" returns a long list of file and folder names.
Typing "id" should give you someting like that:
uid=0(root) gid=0(root) context=u:r:recovery:s0
The important bits are the "(root)" uid and gid.
If any of the above is not the case, it will not work, you may search for help in the forum.
Step 4.
Now you have two options:
#Step 4, Option 1 (recommended to try)
Just run the script and you should be done.
Type:
sh root_lgh735.sh
The script contains all commands I (and other people) used to successfully root the phone.
However we have all used option (2) below, so the script itself has not been tested yet,
though it's very simple (feel free to open it with a text editor to look at it).
You can try to run it, and if it's not doing what's expected you can still go to Option 2
and fix things up.
It will have worked if:
It prints several lines containing "inflating" messages, similar to this:
Archive:
inflating: META-INF/MANIFEST.MF
...
It prints 3 lines like this, and other status messages afterwards:
**************
SuperSU installer
**************
....
If it has done that, reboot your phone and you should be set.
If not, do the commands manually as in Option 2.
Please: If the script worked for you, report it in this thread, so I can simplify these instructions here! Thanks for your help :cyclops:
#Step 4, Option 2:
Execute the commands directly (proven to work on several phones).
Type the commands below (without the numbering of course).
1. mv /data/local/tmp/busybox /sbin/busybox
2. chmod 755 /sbin/busybox
3. mkdir /tmp
4. mkdir /tmp/supersu
5. /sbin/busybox unzip /data/local/tmp/supersu.zip -d /tmp/supersu
6. mv /data/local/tmp/supersu.zip /tmp/supersu/
7. sh /tmp/supersu/META-INF/com/google/android/update-binary dummy 1 /tmp/supersu/supersu.zip
(Note: Not all commands above may be needed, but this is the conservative approach)
Recommended:
Do sanity checks to see if it's doing its job as expected.
After command 2, type the command ls -l /sbin/busybox to check for sanity.
It must return a line like this (with your own date and time):
-rwxr-xr-x shell shell 1048328 <date> <time> busybox
Command 5 must print several lines containing "inflating" messages, similar to this:
Archive:
inflating: META-INF/MANIFEST.MF
...
Command 7 prints lines like this, and other status messages afterwards:
**************
SuperSU installer
**************
...
Step 5.
Your phone should now be rooted if it all worked ok.
You may now type
LEAVE
to reboot your phone.
Happy rooting!
Troubleshooting
If it doesn't work, for example you phone may be stuck on the boot process displaying the LG logo, then you can use Flash Tool to restore your phone. Use instructions below (how to boot the phone into download mode), but don't pull the USB cable, and just let it run its course. This should restore your phone.
If for some reason this hasn't worked, you may try to "dd" back your system .img which you may have created in the preparation step.
Appendix
How to boot the phone into download mode and open the port
a) Boot the LG G4s in download mode. To do this, first switch it off completely and disconnect USB cable. Then, hold the Volume Up button, and while you keep holding it, plug in the USB cable.
b) Start the LG Flash tool and load the .kdz for your phone. We won't actually complete the flashing, you only need it to start the process, but you should use the kdz for your phone nonetheless.
You can check for your kdz on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
c) Now this is very important: Watch your phone while the .kdz is being flashed by the flash tool.
(the flash tool may complain about error connecting to the update server, but you can ignore this with "ok").
As soon as the green letters show up, UNPLUG THE USB CABLE!
The percentage on your phone has to be 0% still (never mind about percentage in the flash tool, it may not even display it).
Then, kill the Flash Tool with the Windows Task Manager (Ctrl+alt+delete).
When it's closed, you can plug your phone back in.
It's now in download mode with open port.
Click to expand...
Click to collapse
Have twpr or cwm recovery to install xposed??

I can confirm is working on LG G4 LG-H735P (Latin America version), thanks!

anyone tried updating? just got a system update notification from my phone lol dk if i should update now or not

Good question! I didn't try it yet. Think it should be ok, but if it isn't, you can just root again I guess

jen.magnolis said:
Good question! I didn't try it yet. Think it should be ok, but if it isn't, you can just root again I guess
Click to expand...
Click to collapse
oh.. it wont like brick or anything? :/

dclarkg said:
I can confirm is working on LG G4 LG-H735P (Latin America version), thanks!
Click to expand...
Click to collapse
I could not root my phone, what kdz file did you use??

Backup problems
Hello,
Coming from a Nexus 4, I bought a G4S last month.
I want to do my first root in order to manage the storage, like jen.magnolis talked about.
In case of a problem (bootloop or brick), I need to be able to restore. I don't really mind about restoring my datas, a factory reset would be enough.
But I don't undestand how i can get the system.img without being rooted ? It seems that I can get a "backup.ab" file using adb. Will it be enough to restore in case of brick ?
I also looked about kdz files, but mine doesn't seem to be available. I have a LGH735 (buyer = FRA, suffix = AFRATS, ...). Will it work if I use the one you provided in your post ?
Thanks for your help !

dclarkg said:
I can confirm is working on LG G4 LG-H735P (Latin America version), thanks!
Click to expand...
Click to collapse
I got the same model phone, but I can't find the .KDZ file for it anywhere. Could you post a link to the one you used please?

Excellent step-by-step guide. Should set an example for other "step-by-step guides" which exclude crucial information ("everybody knows lösfhgaeilurhg has to by typed between these steps here, I shall not mention it" )
Thanks a ton Worked on my LG G4S a.k.a H735 like a charm.
Cheers!

dreamnoob said:
anyone tried updating? just got a system update notification from my phone lol dk if i should update now or not
Click to expand...
Click to collapse
jen.magnolis said:
Good question! I didn't try it yet. Think it should be ok, but if it isn't, you can just root again I guess
Click to expand...
Click to collapse
"phone appears to be rooted, will not be updated" - Hiding root did not help, any simple suggestions but total unrooting?
Wanted to upgrade from 10c to 10d...
Cheers!

Doubts.
Hi everyone!
I just cant find my .kdz file! The phone i want to root its a G4 H735AR, im wondering if there are some compatible .kdz that i can use. Im affraid it might get bricked or something...
BTW i¨ve tried the rootworm.bat method and it didnt work. And when i try to open the COMX port, the lg flash tool always crushes and shuts down.

Works!
ascfzz said:
Hi everyone!
I just cant find my .kdz file! The phone i want to root its a G4 H735AR, im wondering if there are some compatible .kdz that i can use. Im affraid it might get bricked or something...
BTW i¨ve tried the rootworm.bat method and it didnt work. And when i try to open the COMX port, the lg flash tool always crushes and shuts down.
Click to expand...
Click to collapse
So, i made it! It works in the H735AR!! The problem with the flash tool was that i was trying to use it without any KDZ file!! I've used @konsolen .kdz and achieved to open ports, and then continue with the rest of the tutorial without trouble.
Thank you so much! Its a great phone, but with so little internal memory is a waste.

chw9999 said:
"phone appears to be rooted, will not be updated" - Hiding root did not help, any simple suggestions but total unrooting?
Wanted to upgrade from 10c to 10d...
Cheers!
Click to expand...
Click to collapse
ya u just update thru lg bridge.. once updated it will be unroot tho so u have to root it back same method as u did before.. and if you use link2sd it dosent matter after root ur link2sd can just reboot and re-read ur partition without needing to wipe and re-partition

It's working in H736P! Thank you só much!
Enviado de meu LG-H736 usando Tapatalk

For people in Brazil that has H736P, to open ports, is necessary the kdz file to use in LG Flash Tool.
Galera do Brasil, consegui rootear o LG G4 Beat usando esse tutorial porém tive que baixar o arquivo kdz pro H736P pra executar o LG Flash Tool. Cuidado ao usar o LG Flash Tool, assim que aparecer a porta COM na tela do telefone, arranca o cabo USB do computador.
Enviado de meu LG-H736 usando Tapatalk

friend you are from argentina?¿

maxiret said:
friend you are from argentina?¿
Click to expand...
Click to collapse
Brasil.
Enviado de meu LG-H736 usando Tapatalk

Installing LineageOS on my old Samsung Galaxy S6

I'm trying to install LineageOS on my old Samsung Galaxy S6 on which I have enabled developer options and USB debugging. I am not an expert in this but have at least made a little progress but I'm not confident and the remaining steps
The following describes the steps I have done so far on my old SONY VAIO laptop with Manjaro Linux installed....
https://wiki.lineageos.org/adb_fastboot_guide.html # Installed adb and fastboot
"platform-tools_r28.0.2-linux.zip" # download, extract & configure # done
Setting up "adb" # done, I can see "List of devices" when phone connected
Was able to boot phone into recovery mode, "Android Recovery" text only menu is displayed. I was not able to select and "Reboot to bootloader".
Was able to boot phone into "Download-mode" showing "ODIN MODE" top LH of text only screen
I have also installed following sofware on my laptop...
Code:
$ sudo pacman -Syu android-udev # installed OK
$ pamac build heimdall # installed OK
$ sudo heimdall print-pit # this produced a long list of partitions, then
# phone reboots to standard home screen.
$ sudo pacman -Syu android-tools # I decided to install this from stardard repos
# I wasn't sure if this was required or not.
I tried to root my phone following these instructions...
https://www.all-things-android.com/content/how-root-samsung-mobile-device
... and I was able to complete each step successfully until step 22.
... I just didn't get "Flash completed successfully!" message next to the progress bar at Step 22 of instructions.
I did get following message in the Status text area....
Code:
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Beginning session...
Releasing device interface...
Not sure what went wrong here to be honest.
NOTE: Phone is still not rooted yet. so is this a problem going forward?
I'm trying to follow the instructions laid out on...
https://wiki.lineageos.org/devices/zerofltexx/
when I click on the first link...
Installation
How to install LineageOS on the Samsung Galaxy S6
I get to this page....
Install LineageOS on zerofltexx
https://wiki.lineageos.org/devices/zerofltexx/install
TABLE OF CONTENTS
1. Basic requirements # DONE
2. Preparing for installation # DONE
3. Installing a custom recovery using heimdall # I'M STUCK HERE
4. Installing LineageOS from recovery
5. Get assistance
"Installing a custom recovery using heimdall" states the following instructions....
Download a custom recovery - you can download TWRP. https://dl.twrp.me/zeroflte/ Simply download the latest recovery file, named something like twrp-x.x.x-x-zerofltexx.img.
NOTE: I found "twrp-3.2.3-0-zeroflte.img" 24.8M 2018-08-04 13:04:34 EDT
which is different from "twrp-x.x.x-x-zerofltexx.img"
Power off the your device and connect the USB adapter to the computer (but not to the device, yet).
Boot into download mode: With the device powered off, hold Volume Down + Home + Power.
Accept the disclaimer, then insert the USB cable into the device.
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window in the directory the recovery image is located, and type:
heimdall flash --RECOVERY twrp-x.x.x-x-zerofltexx.img --no-reboot
$ heimdall flash --RECOVERY twrp-3.2.3-0-zeroflte.img --no-reboot
NOTE: I haven't done this step yet because the next step is...
Installing LineageOS from recovery
Build a LineageOS install package.
which links to https://wiki.lineageos.org/devices/zerofltexx/build
where it talks about "Build LineageOS and LineageOS Recovery"
this looks very complicated for my limited knowledge of both Linux and Android flashing etc.
My questions:
1. Are my steps so far OK, anything missing?
2. Is there an easier way to do this, can I download a package already built, if so, where to go?
3. Phone is still not rooted yet. so is this a problem going forward?
4. Have I installed the correct software packages so far?
Any help / guidance would be appreciated. Thanks.

I think you need heimdall 1.4.3

kurtn said:
I think you need heimdall 1.4.3
Click to expand...
Click to collapse
Thanks for feedback @Kurtin. I can't see heimdall 1.4.3 in the Manjaro AUR repository, I only see heimdall 1.4.2
I'm not sure how to install a package unless it's in the repository.

fracmo2000 said:
Thanks for feedback @Kurtin. I can't see heimdall 1.4.3 in the Manjaro AUR repository, I only see heimdall 1.4.2
I'm not sure how to install a package unless it's in the repository.
Click to expand...
Click to collapse
That's why I asked for it in MX Linux test repo.

kurtn said:
That's why I asked for it in MX Linux test repo.
Click to expand...
Click to collapse
I can't seem to find any links for testing iso. Could you advise link? Thanks

fracmo2000 said:
I can't seem to find any links for testing iso. Could you advise link? Thanks
Click to expand...
Click to collapse
Sorry, I don't know how to handle that in manjaro. Maybe you should try Odin on a windows PC instead.

Do it the EASY way .....
Suggestion - this is SO MUCH EASIER if you use Odin instead. ASSUMING you have a working Odin setup .....
Tick the box to turn off auto re-boot in Odin.
Flash TWRP.
Do the fast shuffle of fingers necessary to do the initial re-boot into TWRP - vol.down+power to reset the phone and then IMMEDIATELY when the screen goes to black vol.up+power+home to boot recovery. Make sure you hold the three keys down or you won't boot into TWRP.
Once you get TWRP in place, you are good to go. If you re-boot into stock recovery it means your fingers were slow or you didn't hold all three keys down. Repeat with faster or more patient fingers as necessary.
Which S6 variant ? If you have the 920F version, for instance, this is as easy as it gets. Some versions of the S6 are a bit more problematic, and it may be difficult or even impossible if you have a Chinese, HK, or USA Qualcomm model (AT&T, etc...) , but for the others, easy as pie as long as you have the correct TWRP file to flash. Check twice, flash once .....
Speaking of Pie, there is a very functional version of Lineage 16 for the S6. Not 100% perfect but getting there and completely useable (for me, anyway) as a daily driver.

[Tutorial] Install Windows 10 for ARM32 on your Surface 2

Hi guys, following the recent release of a Windows 10 ARM32 install tutorial in Chinese to install it on the Surface RT 1 and Surface RT 2, I've decided to come and try my luck by using google translate to follow the procedure and then decided to refine it and to make it into this tutorial for the Surface 2 (The procedure for the Surface 1 should not be much different aside from the files you have to use but as I don't have one, I haven't tried out the files for it...).
Download: https://yadi.sk/d/mnCUeGKWm1XTXA
Requires:
- The files available in the Yandex Repo
- A recovery USB Disk for Surface 2: Surface2_BMR_20.2.19.0.zip (https://support.microsoft.com/en-hk/help/4023512/surface-creating-and-using-a-usb-recovery-drive)
- A keyboard
1. Copy the following files from the yandex repo to the root directory of your recovery disk:
- Disabling_UAC.reg
- SecureBootPatch.zip (extract it)
- APPX1.rar (extract it)
- surface2_win10_zh_cn_new.wim
- Microsoft.NET.Native.Framework.1.1.appx
- Microsoft.NET.Native.Runtime.1.1.appx
- Camera_fix.reg
2. Boot into Recovery mode (insert the recovery disk, hold the "vol dow" button then press the "power" button and release the "vol down" button when the surface logo appears)
Open a command prompt and type the following commands:
- diskpart
- list disk
- sel disk 0
- list part
- sel part 4
- for quick fs = ntfs override
- exit
- dism /apply-image /imagefile:d:\sources\install.wim /applydir:c: /index:1
3. Reboot the device and Disable UAC, then run "Disabling_UAC.reg" as admin and reboot the device once again
Once the device has rebooted open regedit and go to "HKEY_LOCAL_MACHINE\BCD00000000" select "BCD00000000", click on file and select "unload hive"
Once this is done extract "SecureBootPatch.zip" and open the "SecureBootPatch" folder to run "InstallPolicy.cmd" as admin and then reboot the device once again (l If the secure boot debug policy interface appears after restarting, it means normal. Select accept and install to install)
Open a command prompt as admin and enter the following command to enable test mode :
- bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on
4. Now we can start serious business and install Windows 10 on the device, to do so, we'll start by rebooting the device in recovery mode (Check the lower right corner to indicate that secureboot is not configured correctly and it will succeed)
Once in recovery mode open a command prompt and type the following commands:
- diskpart
- list disk
- sel disk 0
- list part
- sel part 4
- for quick fs = ntfs override
- exit
- dism /apply-image /imagefile:d:\surface2_win10_zh_cn_new.wim /applydir:c: /index:1
5. Plugin your keyboard and reboot the device, you should get an error message related to the boot configuration, at this moment press shift+f10 and open regedit
Go to the following registry entry: HKEY_Local machine/SYSTEM/Setup/Status/ChildCompletion and then select the "setup.exe" entry, modify it to "3", exit regedit and commandline and click "Ok" on the error dialog box, the device should reboot(don't reboot the device in any other way), and configure correctly now
Configure the system the way you want it
Once on the desktop open a powershell command prompt and type in the following commands:
- slmgr.vbs /upk
- slmgr /ipk NPPR9-FWDCX-D2C8J-H872K-2YT43
- slmgr /skms kms.03k.org
- slmgr /ato
- slmgr /skms zhang.yt
Your device is now activated
6. We must then proceed to install the runtime environment and store app
Select the APPX1 folder and copy it to the Desktop, open it and select "APPX.ps1",and choose "Run with powershell", once done press "enter" reboot the system, go back to where you were and do the same with "AppxBundle.ps1"
Then Select "Microsoft.windowsStore.appxbundle" and install it (this will install a chinese version of the Microsoft Store (better than nothing I guess? Maybe someone can provide and english version?)
Finally install the following files from the root of your recovery disk:
- Microsoft.NET.Native.Framework.1.1.appx
- Microsoft.NET.Native.Runtime.1.1.appx
7. Now all we need is a few tweaks to remove usability quirks and then your device will work like a shine :
7.1. You might have noticed than when you boot your device you get a message telling you that the licence is about to expire and that you also get a paging file error popping up at every login, this kinda ruins the experience, so we're gonna get rid of those.
- To remove the licensing popup first it go to " C:\Windows\System32" and take ownership of "LicensingUI.exe", then rename it to "LicensingUI-old.exe"
- To remove the paging file popup just manually set the page cache to 16 MB min and 512 MB max.
(Thanks to betanu701 for indicating us these tricks)
7.2. We're also gonna get totally rid of the Chinese language pack to favor any language you might want, this will also change the Store language to whatever language pack you put in.
- Go to Settings>Time & language>Region & language, and then set the whatever language pack you want as the default and remove the Chinese one (that's of course if you don't speak Chinese ^^)
(Thanks to ShotSkydiver for this trick)
7.3. We'll also make the camera work simply by applying the "Camera_fix.reg" registry entry as admin.
Your device is now ready to use.
Bonus: You can download and install the following apps from our fellow community member _CNR_, you'll get a bunch of stock apps that'll work for this build like mail, maps, solitaire...etc and Office 2013, here's the link : https://mega.nz/#F!ivwlHKaZ!hFwEHZnyw_nNTe4b3TN4wA
Quirks: at the moment I am getting a paging file error at every login along with an expired version warning, if anyone knows how to get rid of those two things, that'd be very helpful, I'd update the tutorial and mention your help in here of course...
(Edit: the quirks have been ironed out thanks to fellow community members)
I think this is only the beginning, we can probably improve this, first of all, we need an english store app (done), we'll also need to get rid of the error and warnings at every bootup(done), then we'll need to compile some apps and update existing ones and then list them, I hope the community on this forum will be helpful for these tasks :angel: For the time being enjoy what you get

Will this work in Asus winRT?
Enviado desde mi G8441 mediante Tapatalk

notass said:
Will this work in Asus winRT?
Enviado desde mi G8441 mediante Tapatalk
Click to expand...
Click to collapse
No, there are two images available, one made for the Surface 1 and one for the Surface 2, maybe it could work if you make a custom image from the leaked build but certainly not that way...

Hey !
I do have a problem with the "bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on" step... it don't work for me I don't understand why..

Are there any difference in the procedure for the Surface RT, other then using the corresponding W10 image?

Kiba85 said:
Are there any difference in the procedure for the Surface RT, other then using the corresponding W10 image?
Click to expand...
Click to collapse
No difference, if you try, tell me if you can install the secure boot patch and if the command "bcdedit ....." works for you. Because i'm stuck at this step

First off, thanks for the guide; it worked perfectly for my Surface 2! Also, I stumbled across a simple way to get the Store to display in English rather than Chinese: just go into Settings, then Time & language, then Region & language, and then set the English language pack as the default (optionally you can also remove the Chinese language pack as well). From there, open the Store, and it'll be in English!

AlGaib said:
Once this is done extract "SecureBootPatch.zip" and open the "SecureBootPatch" folder to run "InstallPolicy.cmd" as admin and then reboot the device once again (l If the secure boot debug policy interface appears after restarting, it means normal. Select accept and install to install)
Open a command prompt as admin and enter the following command to enable test mode :
- bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on
Now we can start serious business and install Windows 10 on the device, to do so, we'll start by rebooting the device in recovery mode (Check the lower right corner to indicate that secureboot is not configured correctly and it will succeed)
Click to expand...
Click to collapse
I would like to give a little warning to people following this guide - don't try to see what happens if you flash the Win10 WIM without having secure boot disabled. I just did that, and my Surface 2 is now bricked. If you want to be super sure that SecureBoot is off, run this cmdlet in PowerShell: Confirm-SecureBootUEFI
If it returns True, SecureBoot is still enabled.
I have an official Windows RT 8.1 recovery stick from Microsoft (but I also tried to make my own stick from the provided ZIP), but when I try to boot into Recovery (Volume Down + Power), I get the following error:
"A required device isn't connected or can't be accessed.
Error code: 0xc000000f"
When I just turn on the Surface, the boot fails, because the Windows 10 installation I flashed fails the SecureBoot test:
"The digital signature for this file couldn't be verified.
File:\Windows\system32\winload.efi
Error code: 0xc0000428"
Bloody hell, I was looking forward to having a more functional Surface and I ended up with a bricked one. Not sure what else can be done, when it refuses to boot even from official recovery stick :crying:

AlGaib said:
Following the recent release of a Windows 10 ARM32 install tutorial in chinese, I've used google translate to follow the procedure and then refined it, here is my tutorial for the Surface 2...
Download: https://yadi.sk/d/mnCUeGKWm1XTXA
Requires:
- The files available in the Yandex Repo
- A recovery USB Disk for Surface 2: Surface2_BMR_20.2.19.0.zip (https://support.microsoft.com/en-hk/help/4023512/surface-creating-and-using-a-usb-recovery-drive)
- A keyboard
Copy the following files from the yandex repo to the root directory of your recovery disk:
- Disabling_UAC.reg
- SecureBootPatch.zip (extract it)
- APPX1.rar (extract it)
- surface2_win10_zh_cn_new.wim
- Microsoft.NET.Native.Framework.1.1.appx
- Microsoft.NET.Native.Runtime.1.1.appx
Boot into Recovery mode (insert the recovery disk, hold the "vol dow" button then press the "power" button and release the "vol down" button when the surface logo appears)
Open a command prompt and type the following commands:
- diskpart
- list disk
- sel disk 0
- list part
- sel part 4
- for quick fs = ntfs override
- exit
- dism /apply-image /imagefile:d:\sources\install.wim /applydir:c: /index:1
Reboot the device and Disable UAC, then run "Disabling_UAC.reg" as admin and reboot the device once again
Once the device has rebooted open regedit and go to "HKEY_LOCAL_MACHINE\BCD00000000" select "BCD00000000", click on file and select "unload hive"
Once this is done extract "SecureBootPatch.zip" and open the "SecureBootPatch" folder to run "InstallPolicy.cmd" as admin and then reboot the device once again (l If the secure boot debug policy interface appears after restarting, it means normal. Select accept and install to install)
Open a command prompt as admin and enter the following command to enable test mode :
- bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on
Now we can start serious business and install Windows 10 on the device, to do so, we'll start by rebooting the device in recovery mode (Check the lower right corner to indicate that secureboot is not configured correctly and it will succeed)
Once in recovery mode open a command prompt and type the following commands:
- diskpart
- list disk
- sel disk 0
- list part
- sel part 4
- for quick fs = ntfs override
- exit
- dism /apply-image /imagefile:d:\surface2_win10_zh_cn_new.wim /applydir:c: /index:1
Plugin your keyboard and reboot the device, you should get an error message related to the boot configuration, at this moment press shift+f10 and open regedit
Go to the following registry entry: HKEY_Local machine/SYSTEM/Setup/Status/ChildCompletion and then select the "setup.exe" entry, modify it to "3", exit regedit and commandline and click "Ok" on the error dialog box, the device should reboot(don't reboot the device in any other way), and configure correctly now
Configure the system the way you want it
Once on the desktop open a powershell command prompt and type in the following commands:
- slmgr.vbs /upk
- slmgr /ipk NPPR9-FWDCX-D2C8J-H872K-2YT43
- slmgr /skms kms.03k.org
- slmgr /ato
- slmgr /skms zhang.yt
Your device is now activated
We must then proceed to install the runtime environment and store app
Select the APPX1 folder and copy it to the Desktop, open it and select "APPX.ps1",and choose "Run with powershell", once done press "enter" reboot the system, go back to where you were and do the same with "AppxBundle.ps1"
Then Select "Microsoft.windowsStore.appxbundle" and install it (this will install a chinese version of the Microsoft Store (better than nothing I guess? Mybae someone can provide and english version?)
Finally install the following files from the root of your recovery disk:
- Microsoft.NET.Native.Framework.1.1.appx
- Microsoft.NET.Native.Runtime.1.1.appx
Your device is now ready to use.
Quirks : at the moment I getting a paging file error at every login along with an expired version warning, if anyone knows how to get rid of those two things, that'd be very helpful, I'd update the tutorial and mention your help in here of course...
I think this is only the beginning, we can probably improve this, first of all, we need an english store app, we'll also need to get rid of the error and warnings at every bootup, then we'll need to compile some apps and update existing ones and then list them, I hope the community on this forum will be helpful for these tasks :angel: For the time being enjoy what you get
Click to expand...
Click to collapse
To get the Store in english: Start > Settings > Language > Region & Language > Remove chinese
To get rid of the popup (old Windows version): C:\Windows\System32\LogonUI.exe > Right Click > Properties > Security > Advanced > Owner...Change > Add your username > Check Names. Close all popups and rename the file to whatever you want

Do i have to Downgrade to 8.0?

I have a problem. I cant disable Secure Boot. Therefore this command doesn't work:
bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on
I already launched SecureBootPatch 100 times. I get the screen on boot where I need to press Agree.
I completely restored with USB recovery Windows 8 RT. Non success
this doesn't change anything. Secureboot stays on.

Avonlady said:
I would like to give a little warning to people following this guide - don't try to see what happens if you flash the Win10 WIM without having secure boot disabled. I just did that, and my Surface 2 is now bricked. If you want to be super sure that SecureBoot is off, run this cmdlet in PowerShell: Confirm-SecureBootUEFI
If it returns True, SecureBoot is still enabled.
I have an official Windows RT 8.1 recovery stick from Microsoft (but I also tried to make my own stick from the provided ZIP), but when I try to boot into Recovery (Volume Down + Power), I get the following error:
"A required device isn't connected or can't be accessed.
Error code: 0xc000000f"
When I just turn on the Surface, the boot fails, because the Windows 10 installation I flashed fails the SecureBoot test:
"The digital signature for this file couldn't be verified.
File:\Windows\system32\winload.efi
Error code: 0xc0000428"
Bloody hell, I was looking forward to having a more functional Surface and I ended up with a bricked one. Not sure what else can be done, when it refuses to boot even from official recovery stick :crying:
Click to expand...
Click to collapse
Hmmm... are the flash drives formatted to Fat32? I don’t really understand how applying an image could cause this much damage...
Do you get any options when you try to boot into 10? If you can find a way to get to the command line, you can restore a Windows RT image from the restore disk

Evandarkfire said:
I don’t really understand how applying an image could cause this much damage...
Click to expand...
Click to collapse
It's quite simple, really. The sole purpose of SecureBoot is to prevent booting of non-signed operating systems. Like this leaked Windows 10. And since I removed the recovery partition (containing command prompt, etc.), the device is now toast. And yes, the recovery sticks are FAT32.

Avonlady said:
It's quite simple, really. The sole purpose of SecureBoot is to prevent booting of non-signed operating systems. Like this leaked Windows 10. And since I removed the recovery partition (containing command prompt, etc.), the device is now toast. And yes, the recovery sticks are FAT32.
Click to expand...
Click to collapse
Are you sure you booted from usb stick? You should still be able to boot from usb. I broke my efs partition, but could still boot from usb stick and recover everything.

I have to ask and I'm sorry for sounding like a noob..... but will this tutorial work for a Microsoft surface 2 running 8.1rt? I saw theres another post that says windows rt but I'm confused...... also when one of the requirements is a keyboard does that mean a USB keyboard or can the type keyboard work?

Fix quirks
Quirks : at the moment I getting a paging file error at every login along with an expired version warning, if anyone knows how to get rid of those two things, that'd be very helpful, I'd update the tutorial and mention your help in here of course...
Click to expand...
Click to collapse
To solve the 2 quirks. For the page caching. Manually set the page cache to min 16 MB and max 512 MB.
For the Build is about the expire. Go to C:\Windows\System32. Find the file LicensingUI.exe. Take complete ownership. Then rename it to LicensingUI-old.exe (or anything).
That will prevent the popups from showing up

Anybody have a working adblocker for the included version of Edge? Also does anybody where to get one of the old UWP arm32 versions of Kodi? They've all been removed from the official servers. Other than that it's amazing, so much better than 8.1!

Avonlady said:
I would like to give a little warning to people following this guide - don't try to see what happens if you flash the Win10 WIM without having secure boot disabled. I just did that, and my Surface 2 is now bricked. If you want to be super sure that SecureBoot is off, run this cmdlet in PowerShell: Confirm-SecureBootUEFI
If it returns True, SecureBoot is still enabled.
I have an official Windows RT 8.1 recovery stick from Microsoft (but I also tried to make my own stick from the provided ZIP), but when I try to boot into Recovery (Volume Down + Power), I get the following error:
"A required device isn't connected or can't be accessed.
Error code: 0xc000000f"
When I just turn on the Surface, the boot fails, because the Windows 10 installation I flashed fails the SecureBoot test:
"The digital signature for this file couldn't be verified.
File:\Windows\system32\winload.efi
Error code: 0xc0000428"
Bloody hell, I was looking forward to having a more functional Surface and I ended up with a bricked one. Not sure what else can be done, when it refuses to boot even from official recovery stick :crying:
Click to expand...
Click to collapse
When I first attempted to flash win10 on my device I did not follow completely the chinese tutorial and therefore I had not disabled secureboot, the Tablet wouldn't boot but I could easily just reflash win8.1 from a recovery drive, your issue sure sounds weird my friend... I'm sadly not knowledgeable enough to help you solve this
Cnnrduncan said:
Anybody have a working adblocker for the included version of Edge? Also does anybody where to get one of the old UWP arm32 versions of Kodi? They've all been removed from the official servers. Other than that it's amazing, so much better than 8.1!
Click to expand...
Click to collapse
I'd love to find a working adblocker too, I really don't understand why ublock won't work, this kindof thing should be platform agnostic, how weird... Also we need to start a thread with a collection of usable software...
Edit: I've updated the tutorial and thanked the users who indicated us how to iron the quirks out, Win10 ARM32 bits on the surface 2 is now as usable as it can get, we just need to make a collection of useful apps and list them (find some and compile others) and everything will be as great as it can be...

Will this work if my surface 2 is running 8.1rt?
---------- Post added at 03:00 AM ---------- Previous post was at 02:57 AM ----------
AlGaib said:
When I first attempted to flash win10 on my device I did not follow completely the chinese tutorial and therefore I had not disabled secureboot, the Tablet wouldn't boot but I could easily just reflash win8.1 from a recovery drive, your issue sure sounds weird my friend... I'm sadly not knowledgeable enough to help you solve this
I'd love to find a working adblocker too, I really don't understand why ublock won't work, this kindof thing should be platform agnostic, how weird... Also we need to start a thread with a collection of usable software...
Edit: I've updated the tutorial and thanked the users who indicated us how to iron the quirks out, Win10 ARM32 bits on the surface 2 is now as usable as it can get, we just need to make a collection of useful apps and list them (find some and compile others) and everything will be as great as it can be...
Click to expand...
Click to collapse
Would there. E any possible way of making a video tutorial????
---------- Post added at 03:01 AM ---------- Previous post was at 03:00 AM ----------
AlGaib said:
When I first attempted to flash win10 on my device I did not follow completely the chinese tutorial and therefore I had not disabled secureboot, the Tablet wouldn't boot but I could easily just reflash win8.1 from a recovery drive, your issue sure sounds weird my friend... I'm sadly not knowledgeable enough to help you solve this
I'd love to find a working adblocker too, I really don't understand why ublock won't work, this kindof thing should be platform agnostic, how weird... Also we need to start a thread with a collection of usable software...
Edit: I've updated the tutorial and thanked the users who indicated us how to iron the quirks out, Win10 ARM32 bits on the surface 2 is now as usable as it can get, we just need to make a collection of useful apps and list them (find some and compile others) and everything will be as great as it can be...
Click to expand...
Click to collapse
Would there. E any possible way of making a video tutorial????

trollingwhovian said:
Will this work if my surface 2 is running 8.1rt?
---------- Post added at 03:00 AM ---------- Previous post was at 02:57 AM ----------
Would there. E any possible way of making a video tutorial????
---------- Post added at 03:01 AM ---------- Previous post was at 03:00 AM ----------
Would there. E any possible way of making a video tutorial????
Click to expand...
Click to collapse
I don't have time or the ressources to do that, sorry, also I don't wanna redo the whole thing again on my device just to make a video tutorial, the text one is good enough...