Develop Bugs

Unlock bootloader on GT-I9250 without wipe and without root

Hi! After latest OTA update I was left with an unbootable Galaxy Nexus (zygote couldn't start) and I lost root (su needed activitymanager up). So I needed to unlock to revive the phone, but I really didn't want to lose my data. After some exploration I could come up with a way to unlock bootloader without wipe and without root. I have seen several questions about this here and this was deemed impossible, so I decided to share my findings and expect they might help someone. Should work with GSM tuna phones.
Components for success:
— unlocking without wipe via putting a byte in param partition (needs root):
[1] http://forum.xda-developers.com/showthread.php?t=1650830&page=15
— OMAPFlash, a low-level utility for manipulating and flashing chipset (usually used to unbrick phones)
[2] http://forum.gsmhosting.com/vbb/f63...9250-galaxy-nexus-gt-i9100g-gt-i9300-1465412/
Take the two of them and you have a solution. I could successfully flash unlock byte to param partition using OMAPFlash.
A sketch of a guide:
1. Boot windows xp, download OMAPFlash (http://d-h.st/XNv), connect a turned off phone without battery, install drivers for omap device. (Mod edit: I've updated the download link.)
2. Dump a part of param partition. You don't need to dump the whole partition, but I think it is safer if you dump a sector-aligned area (512*n). I used 4KB (8 sectors).
Code:
OMAPFlash -omap 4 -2 -p OMAP4460_TUNA_8G_HS_PRO -t 36000 chip_upload [email protected] 1000 param.img
chip_upload is for downloading data from device memory
[email protected] is the start of params partition (check /sys/block/mmcblk0/mmcblk0p4/start, multiply by sector size 512 and convert to hex)
1000 is to copy 4KB.
Sometimes the process stalls (esp if you try to download larger dumps), just reconnect and retry.
3. Verify that the content is similar to first 4 KB of the dumps of param partitions attached in the thread [2]. For me they matched entirely.
4. Change the byte at offset 124 (0x7C) from 01 to 00.
Code:
echo -ne "\x00" | dd obs=1 count=1 seek=124 of=param.img conv=notrunc
5. Flash it back to the device.
Code:
OMAPFlash -omap 4 -2 -p OMAP4460_TUNA_8G_HS_PRO -t 36000 chip_download [email protected] param.img
Reboot, you are unlocked.
Additional links:
[3] http://forum.gsmhosting.com/vbb/f634/gt-i9250-pinout-enjoooy-1463061/ GT-I9250 JTAG pinout. Not directly releavant to the guide, but I found it while searching for solution, thought that can help someone in future.

Additional reading
The dangers of OTA when you have root, or why I was stuck with an unbootable phone at all
I learned the hard way that OTA may cause unpleasant results if you are trying to preserve root and mess with filesystem.
I was trying to preserve root in a way similar to one used by rootkeeper apps: put a copy of su somewhere in /system and make it immutable. So I went and put my su to /tts (thought that it's unprobable that OTA will do something there), and made it immutable.
And then the update came. As part of the the update process it copied a new version of /system/usr/share/zoneinfo/zoneinfo.version file and the file got 660 perms (package_extract_dir("system", "/system") in the update_script). Then it went on to recursively fix permissions so that the mentioned file would be made readable (set_perm_recursive(0, 0, 0755, 0644, "/system")). But the set_perm_recursive was met by immutable su in tts directory, chmod returned error and the recursive process was stopped before it got to zoneinfo.version file. So the latter file remained unreadable.
Unfortunately during startup zygote preloadsClasses, static constructor in some sqlite class needs DateFormat, and DateFormat reads zoneinfo. And fails cause it's unreadable. Exception, System.exit. Phone boot stuck.
To work my copy of su needs to send a message to ActivityManager service using binder. I wrote a dirty mock for AM but servicemanager didn't accept my fraud, it checked uid. I tried to bypass preloadClasses with overflowing system file descriptors count to prevent zygote from reading preload class list, but somehow it didn't succeed. Thus the only option I had was unlocking bootloader.
So it may end bad if you mess with /system on a stock rom with locked bootloader and want to receive OTA. It may seem natural, but sometimes the changes seem irrelevant, and then a chain of small failures leads you to loss of everything: boot, root, and data.

This is great work! Kudos to you for figuring it out.
By the way, where did you find the syntax for OMAPFlash commands?

efrant said:
This is great work! Kudos to you for figuring it out.
By the way, where did you find the syntax for OMAPFlash commands?
Click to expand...
Click to collapse
There are some docs in OMAPFlash_tuna.zip package. The most interesting is OMAPFlash.txt that lists options and commands and has some examples.
Also I was lucky that there is a complete example for unbricking GT-I9250 in Targets/Projects/tuna. This is where I took the options specific for this device.

nichtverstehen said:
There are some docs in OMAPFlash_tuna.zip package. The most interesting is OMAPFlash.txt that lists options and commands and has some examples.
Also I was lucky that there is a complete example for unbricking GT-I9250 in Targets/Projects/tuna. This is where I took the options specific for this device.
Click to expand...
Click to collapse
Exactly. I haven't needed this yet, but i had looked in those board files, cross examining with omap 4460 manual that can be found on the web. Thanks for sharing.
I was not aware that JTAG method had been found. Great news.
Sent from my i9250

Works!
Awesome - this worked for me! Unlocked, unrooted, TAKJU Galaxy Nexus w/JB 4.2.2. I used OMAPFlash_tuna.zip (download link).
I had issues when the downloaded param.img file was long, so I replaced 1000 with 200 in the commands. Regardless, it still took me probably 5-10 tries on each command to get it working (unplugging and replugging the phone in between), and sometimes it would freeze up and I'd have to restart Windows. If it takes longer than 5 seconds, you should press Ctrl+C and restart that step.
My problem was that one of my volume buttons is messed up, and as a result the fastboot screen doesn't work - Windows doesn't detect a fastboot device, and none of the hardware buttons or the touchscreen works either. As a result I needed to unlock the bootloader without using fastboot (oem unlock), and this did the trick!
Also, on Windows, I downloaded a hex editor (i.e., HxD) to do the editing. My modified param.img (only 512 bytes) is attached as well.
{
"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"
}

Thank you!!! It worked for me too!
The volume buttons on my Galaxy Nexus didn't work and I can't recharge the battery via USB. The USB works only as data connection. Despite all these issues on my phone, it worked for me too!!
I replaced the size in the commands from 1000 to 400 (1024 bytes = 2*512), and I had to put the battery on the phone.

Sweet jesus I cannot express enough gratitude for this post. While I was a little worried about bricking my device, it would up working perfectly.
A couple of confusing points for anyone out there trying to do this:
- The dump / reflash should only take a few seconds each. If it hangs, cancel and re-start the process.
- Install the drivers with the device OFF but plugged in. You will have an OMAP device without a driver in your device manager. Update the device driver and you're good to go.
- I didn't know how to get the dd command to work on windows, so I also went the Hex editor route it it worked flawlessly
- The only snag I ran into was that it did not boot into my flashed CWM after doing an "adb reboot recovery" from the stock rom. It went back to the stock android recovery. From there I did "fastboot boot cwmrecovery.img" and installed my rom and gapps. After that initial boot, it rebooted into recovery just fine! It seems like a weird glitch (maybe just a one-off).
Cheers

techobrien said:
- Install the drivers with the device OFF but plugged in. You will have an OMAP device without a driver in your device manager. Update the device driver and you're good to go.
Click to expand...
Click to collapse
This is a critical step right here. This thread either should be linked on the 101 FAQ if it's not already or stickied.
a maguro wrote this.

techobrien said:
- The only snag I ran into was that it did not boot into my flashed CWM after doing an "adb reboot recovery" from the stock rom. It went back to the stock android recovery. From there I did "fastboot boot cwmrecovery.img" and installed my rom and gapps. After that initial boot, it rebooted into recovery just fine! It seems like a weird glitch (maybe just a one-off).
Cheers
Click to expand...
Click to collapse
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely. It shouldn't exist in custom ROMs, which would explain why after installing a ROM and Gapps you were fine.
This is pretty cool. Nice find OP.

cupfulloflol said:
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely. It shouldn't exist in custom ROMs, which would explain why after installing a ROM and Gapps you were fine.
This is pretty cool. Nice find OP.
Click to expand...
Click to collapse
This post thread have not been getting the attention it deserves..
Beamed from my Maguro.

cupfulloflol said:
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely.
Click to expand...
Click to collapse
Good to know for next time round. The flimsy headphone ribbon cable is the bane of my existence and it seems like a somewhat common problem. I didn't think that the custom rom would touch the bootloader so I was confused, but /system/ makes sense. Thanks for the tip.

Just in case anybody was wondering, this method also worked for my Verizon GNex LTE. I also used a HEX editor.

Hi,
i'm thinking to use this method to unlock my Nexus' bootloader, in order to gain root privileges without wiping the memory.
This because i need to try and undelete files i have lost on my phone, to do this i need the root but i can't use the normal procedure that would wipe forever all the data i need to restore.
As i am new to this kind of operations, i never even rooted my Android phones, i wanted to ask if this procedure can fit my situation, and if there are any risks....
Thank you very much
EDIT: It worked perfectly!!
Thank you very much!!

Did anybody try it on MAGURO device? Does it require any change in the procedure?

Um... The op (and others) did it on a maguro? After all, the title says "on GT-I9250".

Isn't a i9250 a Maguro?
Beamed from my Grouper

Mod edit: removed quote of the OP.
Is WinXP really required for this process or will it work on newer versions of Windows ie Win8?

mielli1 said:
Is WinXP really required for this process or will it work on newer versions of Windows ie Win8?
Click to expand...
Click to collapse
Please do not quote the first post of threads when you reply.
As for your question, if you can get the driver to install on Windows 8, the program will work fine. The driver installs fine in Windows 7 by the way.
Don't forget to disable driver signature verification if you are trying to install drivers in Windows 8.

Windows 8 - stuck at installing drivers
beekay201 said:
This is a critical step right here. This thread either should be linked on the 101 FAQ if it's not already or stickied.
a maguro wrote this.
Click to expand...
Click to collapse
I have a Nexus with a broken volume up button, so am trying this method as a way of unlocking the bootloader and rooting my device.
When I plug the powered off device into the usb port, constantly get the sounds of a device being inserted, and then unplugged (two different beeps.) This continues until I unplug the phone.
Is this the step where I should get a "found new hardware" notification? It is not happening for me, and I'm wondering if this is Windows 8 related.
FYI - I have already disabled driver signature verification.

[ROOT / TWRP][D851 ONLY][OSX/Linux/Windows] Root/TWRP your TMO G3 with PurpleDrake!

Howdy all!
What's this? Read on, dear reader, to discover the magic that is PurpleDrake.
{
"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"
}
What is this?
This is a utility to easily root your LG G3 (specific models only). It's a fairly foolproof script that includes all the dependencies you'll need for getting your phone rooted easily.
This is the FULL version. This means that it will automatically root, and ask you if you want TWRP installed and a custom boot that doesn't trip the root checker!
Click to expand...
Click to collapse
Who made this?
This root is a collaboration between myself (IOMonster), jcase, and autoprime.
Special thanks also to beaups for some initial guidance looking at the vulnerable application.
Thanks to @Shelnutt2 for the security-disabled boot.img
Thanks to @Dees-Troy for the TWRP image!
Click to expand...
Click to collapse
Is my phone compatible?
The new LG G3 models each are slightly different with regards to rooting and unlocking.
To see a matrix of which LG G3 phones are compatible with this root, please see this Google Docs spreadsheet that we've compiled.
When you run this program, your phone will reboot and run a test to see if it's compatible. If the application succeeds, it'll let you know that it's able to permaroot you. If not, it'll fail gracefully and reboot you back to normal Android without having changed anything.
Please note that this version is currently only compatible with the T-Mobile D851 version of the LG G3. For other phones, we suggest you look for the LITE version of PurpleDrake.
Click to expand...
Click to collapse
How do I use this?
WE NOW SUPPORT WINDOWS! YAY ME
To start, for either platform you'll need to scroll down to the download section and get the file.
Ensure that your phone is in ADB mode (PTP Mode for everyone but Verizon. Verizon users need to be in "Internet"/"Ethernet" mode)
Linux Instructions (in a terminal!)
Extract the file you downloaded...
tar xvf ~/Downloads/PurpleDrake-TMO_VERSION.tar.gz
Mark the application as executable, and run it!
cd PurpleDrake-TMO
chmod +x purpledrake_linux.sh
./purpledrake_linux.sh
OSX Instructions (just a bit easier)
Extract the file you downloaded
Double-click on "purpledrake_osx"
Windows Instructions
Extract the file you downloaded
Double-click on "purpledrake_windows"
The application will guide you through all the steps you need.
You will still need to install SuperSU from the market after installing PurpleDrake. This pack does not include one.
If you choose to install the custom boot.img, your phone's root checker will not be tripped and your phone will show as UNROOTED.
After, be sure to check @autoprime's post for how to disable OTA upgrades! here : http://forum.xda-developers.com/showpost.php?p=54254111&postcount=2
Click to expand...
Click to collapse
But, what if I don't want to run your script to root?
Well then, I'd be a little hurt, but you can still do everything the script does manually.
Download the package, and extract it. Open a terminal in the main folder of the archive and run these commands:
Code:
adb reboot --bnr_recovery
adb push ./assets/start_restore /temp/start_restore
adb push ./assets/permaroot.bin /temp/start_restore
adb reboot
That will perma-root you, however there's no protection from doing something stupid or the phone being incompatible. Please be careful!
Click to expand...
Click to collapse
Where do I get this?
WINDOWS/OSX/LINUX VERSION OUT NOW!
- Fixed Windows support
- Fixed OSX ADB issues not detecting phone first try
- Fixed race conditions leading to errors permarooting
- Added 64-bit Linux ADB
Code:
[url]http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-TMO_R03.tar.gz[/url]
Old version here... (OSX/Linux only)
Code:
[url]http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-TMO_R01.tar.gz[/url]
Please DO NOT mirror or re-upload the PurpleDrake software to your own site, or any other file host.
If you need drivers for Windows (thanks @autoprime for having these handy!):
Verizon Drivers: http://downloads.codefi.re/autoprime/LG/LG_G3/LG VZW_United_WHQL_v2.14.1.exe
Everyone Else: http://downloads.codefi.re/autoprim...leDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3.exe
Click to expand...
Click to collapse
Help, it doesn't work!
Post here, let us know what happened and we'll try to help you. DO NOT private message us on XDA or on IRC asking for help. We will not assist privately.
Most questions if not answered here can be answered on #lg-g3 on IRC in Freenode.
Click to expand...
Click to collapse
Thanks so much! How can I show my appreciation?
Since this was a collaboration project, proceeds that are made from this root will be split between amongst us so we can purchase a Sprint test phone to root (as it's currently not rooted).
If you'd like to donate to us, click the "Donate to me" button on the left sidebar under my name, and be sure to enter a comment to let us know that you're donating towards the PurpleDrake project.
Thanks again!
Click to expand...
Click to collapse

FAQ:
Q: I'm running the Windows .bat as administrator and it's closing/not working.
A: There is no need to run the .bat as admin. Just double-click and run.
Q: I get the "Windows cannot find '.\assets\windows\bin\mintty.exe'." error.. watdo?
A: Try just double-clicking on the .bat instead of running as admin.
Also make sure the script is extracted properly first before running.
Q: I [used Flashify and] am stuck in fastboot.. how can I get out?
A: Be cautious using Flashify as it seems it's not working right.. or people are hitting the wrong buttons with it.
HERE are the stock TMO D851 partitions.
Use fastboot to flash recovery(TWRP or stock) and stock boot. This will install TWRP and fix booting into rom.
If on Windows you will need fastboot drivers. Use Google to find fastboot binaries and drivers.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
The commands to flash TWRP manually instead of using flashify is below.
Place TWRP on the root of your internal /sdcard/ using MTP, downloading it directly to phone or using ADB push.
Code:
adb push name_of_file.img /sdcard/
adb shell
su
dd if=/sdcard/name_of_file.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Disable OTA:
Open LG Hidden Menu (3845#*851#) --> WLAN Test --> OTA Setting --> OFF
*Replace "851" with your devices model number, 850, 852, 855 etc...
The first D851 update has been released (10M). Bootloader remained unlocked. It would appear future OTAs will be safe to take AS LONG AS YOUR PHONE IS NOT MODIFIED! If you have flashed TWRP or installed xposed or modified /system then you need to restore any changes made or flash stock firmware (tot/kdz) before taking OTA.
If using a non-tmobile g3 I would be hesitant about taking OTA updates. An OTA may update the boot stack to block Bump!
EFS Backup:
Code:
[FONT="Arial Narrow"][B]Backup EFS after jailbreaking your G3. EFS is split into 2 partitions modemst1 and modemst2.
img files will be on root of internal sdcard. Save the .img files somewhere else besides the sdcard... email, cloud, etc..[/B]
DO NOT FLASH OTHER PEOPLES EFS OR FLASH YOUR OWN BACKUPS ONTO ANOTHER PHONE.
THIS WILL BREAK EFS ON THE PHONE YOU ARE FLASHING TO. EFS BACKUPS ARE FOR THE PHONE THEY CAME FROM ONLY.
I have made a new thread on EFS backup and restore which can be found [URL="http://forum.xda-developers.com/lg-g3/development/efs-lg-g3-efs-backup-restore-t2907329"]HERE[/URL].
[/HIDE]
[B][SIZE="5"]Restoring Stock / Remove root flag:[/SIZE][/B]
[HIDE]
Download the tmo .tot file and use lg flash to restore it to stock. itll format everything on internal sdcard so backup anything u may need off it.
T-Mobile firmware can be found [URL="http://downloads.codefi.re/wolfgart/LG_G3/D851"]here[/URL]. Thanks to [user=608699]@wolfgart[/user] for the files and [user=1157052]@thecubed[/user] for codefire hosting.
*Step by step picture guide - [url]http://imgur.com/W83hMPE[/url]
install the drivers.
put phone into Download Mode (power off. unplug USB. pull battery. put battery back in. press/hold Volume Up then plug in USB cable.)
In Windows Device Manager set the phones serial COM port to #41. (*see picture guide for help)
Install [URL="http://downloads.codefi.re/autoprime/LG/LG_G3/Setup_LGFlashTool_1.8.6.527.zip"][B]LG Flash[/B][/URL]. In "C:\LG\LG Flash" folder delete megalock dll. Replace with .dll below.
new megalock dll - [url]http://bit.ly/1cQADXm[/url] (this site includes a "download manager.. UNCHECK THE BOX before downloading dll file.)
Run LG Flash in the "C:\LG\LG Flash" folder. Select korean factory if asked.
When LG Flash opens you will see a box to select firmware and dll.
Select [URL="http://downloads.codefi.re/autoprime/LG/LG_G3/LGUP_8974.dll"][B]LG Flash .dll[/B][/URL]
Select (.tot)
Hit OK (*see picture guide for help)
Hit yellow start button. If you get Milkyway error click ok. LG Flash will then run a crc check on the tot file. Takes a bit.
After crc check finishes unplug the phone. plug phone back in. it should now be seen in LG Flash and start flashing.
Phone will reboot when finished. You may end up on a screen with s "2"... let it sit there for a minute or two.
If stuck on "2" try unplugging the usb cable from the phone.. wait 10 seconds.. then plug the usb cable back in. now wait 30 seconds and hopefully it changes to a "3"
Once the phone says "3" you can unplug the USB.. remove the battery and plug back in.. boot back up... you are now 100% stock.
[/HIDE]
[B][SIZE="5"]PurpleDrake YouTube Videos:[/SIZE][/B]
[HIDE]
[url]https://www.youtube.com/watch?v=wJtz51KgxjM[/url]
[/HIDE]

And where is the bootloader unlock talked about at the bounty thread or was it just a hoax?
Gesendet von meinem LG-D855

Tectas said:
And where is the bootloader unlock talked about at the bounty thread or was it just a hoax?
Gesendet von meinem LG-D855
Click to expand...
Click to collapse
Hoax? What?
This pack is ONLY for the T-Mobile G3 which has an unlocked bootloader out of the box.
D855 support is NOT included in here. There will be a separate thread when we have an unlock for the bootloaders of the rest of the G3 family.

Tectas said:
And where is the bootloader unlock talked about at the bounty thread or was it just a hoax?
Gesendet von meinem LG-D855
Click to expand...
Click to collapse
There is no boot loader unlock..where ever you read this is misinformed...the T-Mobile variant ships boot loader unlocked, it is the only one so far to be shipping unlocked.

Sweet

thecubed said:
Hoax? What?
This pack is ONLY for the T-Mobile G3 which has an unlocked bootloader out of the box.
D855 support is NOT included in here. There will be a separate thread when we have an unlock for the bootloaders of the rest of the G3 family.
Click to expand...
Click to collapse
I'm aware of that and sry it wasn't meant offensive or to put this one down, autoprime, did imply at the bounty thread, that you as well managed to unlock the bootloader, at least at the beginning, that's what I'm referring to, sry that i said it the wrong way, was a bit disappointed, which for sure isn't your fault or the one of this tool, it's still great progress you made.
Gesendet von meinem LG-D855

I wish the international G3 D855 will be unlocked too
Sent from my LG-D855 using XDA Premium 4 mobile app

Great glad to see this released thank to all that is involved
LGG3 and beyond

All my family is sleep in the room with my Mac will be running asap bright and early. Thank you for your hardwork

Thecubed, autoprime, shelnutt2, jcase, and whoever else....thanks for this. Truly appreciated! Can't wait for Windows support. :Cheers:
Sent from my LG-D851 using XDA Premium 4 mobile app

Plans to support recovery for D855 in the near future?
Need to know to sell or not the G3 ?

What the hell software compatible with a mac that's a 1st whoop whoop well done guys and thanks for the hard work

Yeah great time to be a Mac owner

I have a feeling this treads about to turn in to a "when will this version be supported" topic :/
LGG3 and beyond

Success!
1. THANK YOU!
2. It didn't work the first time around, temproot worked but permaroot did not. Maybe it had to do with the fact that I was reading this forum while it was waiting for my input... I can't see how that would have made a difference but whatever. [[ Edit: It worked the second time running, I just followed the instructions immediately - no problems. /Edit ]]
3. Just a reminder for Linux users ... you have to add udev rules as described here: http://developer.android.com/tools/device.html ... and when you are done with that, also run:
$ sudo service udev restart; sudo killall -9 adb
4. My G3 would only connect to my laptop (Ubuntu 14.04) when it was in PTP mode. MTP or Charge Only did _NOT_ work... Only PTP.
5. THANK YOU AGAIN! You devs rock!
Frank.

Same as the guy above didn't work the first time but worked perfect the second! OSX here.

@ OP
http://forum.xda-developers.com/lg-g3/general/s-carrier-specific-g3-threads-t2818549

I keep getting no such file or directory, going to re download drivers and see

@thecuba not telling you what to do but maybe put this on T-Mobile thread as well http://forum.xda-developers.com/tmobile-lg-g3/development
Hope you don't take it the wrong way

V500 im not able to get into bootloader

Hi,
I just want to unlock bootloader on my g pad and flash custom rom. I did this many times on Nexus devices, also sony.
I installed sdk, next Google drivers and my tablet is detected by computer as adb interface.
But when I type command - adb reboot bootlader
Tablet just reboots. I'm not able to get into fastboot. Plz help. It's v500 version. My software version is v50020d.
Earlier I didn't know that LG locks bootloader and I tried many times to flash custom recovery. One time I had made a mistake and using flashify - I flashed twrp for v510. But LG support tool helped me to repair it. Probably it flashed stock with full wipe becsuse I lost data so everything should be fine now but as You can see - it isn't...
HTC One M8

Also command adb reboot oem-unlock only reboots it
HTC One M8

The v500 has a locked bootloader. You need to root first and then install a older aboot and recovery in order to flash roms. This device like the g2 uses loki to bypass the lg lock.

Ok. I've already rooted my device but every time I try to flash twrp using "loki" method I end with screen like this...
{
"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"
}
HTC One M8

WKD622 said:
Ok. I've already rooted my device but every time I try to flash twrp using "loki" method I end with screen like this...
HTC One M8
Click to expand...
Click to collapse
Okay, so that message providing you wait a bit and see twrp start, means that you have successfully bypassed the locked bootloader...
If it freezes there and nothing happens that would be something different... The second sentence reads differently if Loki has bypassed things. The screen above seems to indicate that Loki is not successfully bypassing (hence my edits to this post) it should say something different in the second line if Loki is successful. My tablet is at home right now so I can't take a picture of a working Loki bypass...
A successful bypass should say something like: Device unlock so boot success!

After this screen twrp turns on.
Edit
Okey... Maybe I've done something wrong. Could you tell me how to flash this recovery in points?
I'm not very familiar with LG...
HTC One M8

WKD622 said:
Twrp turns on.
HTC One M8
Click to expand...
Click to collapse
Excellent, then you have successfully installed twrp and you can get into twrp recovery. Next do a backup to an sdcard (if you have one), download a rom to that card and install it...
---
Does TWRP start can you get into it?

muiriddin said:
Excellent, then you have successfully installed twrp and you can get into twrp recovery. Next do a backup to an sdcard (if you have one), download a rom to that card and install it...
Click to expand...
Click to collapse
I had also done this and flash cm but nothing changed.
Maybe this screen was a result of flashing twrp using flashify.
Yesterday I flashed stock so now I want to begin this process one more time . Could You tell me how to do it?
HTC One M8

----
Yes. But now it come to my mind that this problem with booting was a result of twrp for v510 flashed using flashify and next Loki method. Because maybe at the end twrp was for v500 and it worked but I wasn't able to flash anything because it "thought" that I'm using v510. But next i delete line in updater-script connected with authorization and as a result I flashed cm for my v500 but this boot screen didn't changed.
So as you know next thing I've done was flashing stock and now I want to start from beginnig without problems .
Could you tell me how? :/
HTC One M8

WKD622 said:
Yesterday I flashed stock so now I want to begin this process one more time . Could You tell me how to do it?
HTC One M8
Click to expand...
Click to collapse
Okay, my process from a fresh install of 4.4.2 is:
make sure to download everything you need before you start this process and read through it carefully...
1. Root device using stumproot, thread located here:
http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
Other root approaches potentially will work as well, I use stump since it also works on my phone...
2. Download and use step 3 from idioterror's thread here:
http://forum.xda-developers.com/showthread.php?t=2698267
You will need to modify his batch file to properly work the details for that are in the thread, the download by itself will not work without changing a line in the batch file (if I recall from memory find the query for 50010b and change it to 50010d.)
If that worked the batch file ends with an attempt to reboot into recovery. Unplug the cable after the batch file sends the reboot command so the adb reboot recovery command can properly complete and get you into recovery...
if the tablet boots back into stock try another adb reboot recovery manually(or use flashify to reboot into recovery), again unplug once the reboot starts.
If that does not get you into TWRP but instead gets you into stock recovery you need to do the steps in idioterror's batch file manually go here for details:
http://forum.xda-developers.com/showpost.php?p=56707177&postcount=15
(be really careful with the dd comands if you do this a mistype with them will be very dangerous)).
Once you have this working recovery you need to decide which base you are going to use with your tablet, the 4.2.2. base (for AOSP based roms) or the 4.4.2 base (for recent stock based roms). The recoveries for the 4.2.2. and 4.4.2 are different see the details in this thread:
http://forum.xda-developers.com/showthread.php?t=2551499
You can run AOSP based roms on the 4.4.2 firmware but you will typically need to flash a 4.4.2 replacement kernel like redkernel or mani... See the proper threads in the development section...
If you are going to run AOSP based roms with the standard kernel skip to 3b...
3a. I am running a 4.4.2 firmware base and a redkernel on lollipop myself, make sure to install the latest 2.8.0 recovery for the 4.4.2 firmware base... You can now flash stock based roms, or AOSP roms with a 4.4.2 capable kernel do not do step 3b for stock based roms...
3b. Install the 4.2.2. base (will actually install a different recovery partition and aboot partition, however it will get your firmware back to 4.2.2. which is what almost all of the AOSP roms expect...) thread and download details here:
http://forum.xda-developers.com/showthread.php?t=2719411
That download is huge and takes a while to flash, don't panic, but make sure that the MD5's match since a failed flash for that one can brick the tablet...
4. Enjoy your rooted and rommable tablet!

muiriddin said:
You will need to modify his batch file to properly work the details for that are in the thread, the download by itself will not work without changing a line in the batch file (if I recall from memory find the query for 50010b and change it to 50010d.)
If that worked the batch file ends with an attempt to reboot into recovery. Unplug the cable after the batch file sends the reboot command so the adb reboot recovery command can properly complete and get you into recovery...
if the tablet boots back into stock try another adb reboot recovery manually(or use flashify to reboot into recovery), again unplug once the reboot starts.
If that does not get you into TWRP this step failed and youwill have to manually walk through what the batch file does... Stop and ask me or someone else for further assistance (or open up idioterror's batch file and figure out what it does so you can do it manually (be really careful with the dd comands if you do this a mistype with them will be very dangerous)).
Click to expand...
Click to collapse
You need to know that yesterday back to stock was my second one. 1st time few days ago I edited script as You wrote here form v50020b to d and it didn't boot to recovery. The same result was when it comes to booting to recovery using app like flashify.
So unfortunately I need to do it with the hardest way . I will try. It will be very nice experience.
I belong to crx team as a (very) novice member so I hope Cr3pt will help me looking at instruction You wrote for me if something goes wrong.
Thanks a lot. Probably everything will be okey but there is an option that I will be back here with more questions. :E
Thanks a lot.
HTC One M8

Does it boot into the stock recovery instead with two really strange errors?
WKD622 said:
You need to know that yesterday back to stock was my second one. 1st time few days ago I edited script as You wrote here form v50020b to d and it didn't boot to recovery. The same result was when it comes to booting to recovery using app like flashify.
So unfortunately I need to do it with the hardest way . I will try. It will be very nice experience.
I belong to crx team as a (very) novice member so I hope Cr3pt will help me looking at instruction You wrote for me if something goes wrong.
Thanks a lot. Probably everything will be okey but there is an option that I will come with more questions.
Thanks a lot.
HTC One M8
Click to expand...
Click to collapse

HTC One M8

WKD622 said:
HTC One M8
Click to expand...
Click to collapse
Yeah, idioterror's script is failing, when I had that happen I had to manually do what was in the batch file via an adb shell. I can't write those instructions until later tonight (assuming my little girl sleeps tonight that is)...
Something has changed which causes his script to fail that I haven't tracked down yet (there is a thread on this somewhere in the LG GPAD forums)... It is either the newest LG drivers, or a newer adb.exe install or something that is conflicting with idioterror's script... his approach still works, you just have to manually do it...
One additional thing, when I manually did it, I had already installed busybox so I did not use his tools (dd etc) I used the ones that I had already installed (I use the BusyBox Pro from Stericson in the play store for this, his free version should also work).

Step by Step Aboot/Recovery when the script fails
WARNING: I'm trying to help, I assume that you know how to recover from mistakes by reverting to stock with LG's software if needed. This is the procedure I followed by manually doing what Id10tError had in his batch file... If anything fails below I messed up in translating the instructions. I did not run the dd commands on my tablet to check since I have already done this process. Please be careful... If you find errors I will try and help... the dd command does have the ability to completely destroy your tablet if you use it incorrectly... if you have questions or see a difference between my instructions and the batch file ask and I'll be glad to answer questions. This was translated from idioterror's script, any errors are mine not his.
I assume that you have installed busybox, (this gives you a working dd on the device)
you have rooted your tablet
and you have adb working on your computer.
You could potentially also do this from the tablet itself if you copy the files needed to the proper locations (skip the push part below) and use a terminal directly. I also assume that you have downloaded idioterror's aboot replacement stuff from my earlier instructions. On the computer go to the directory that you opened the zip file and do a directory listing you should see:
the dd lines below may wrap depending upon how you are displaying this...
The directory should contain:
11/12/2014 09:59 PM <DIR> .
11/12/2014 09:59 PM <DIR> ..
05/16/2014 08:48 PM 524,288 aboot.img
05/16/2014 08:48 PM 815,104 adb.exe
05/16/2014 08:48 PM 96,256 AdbWinApi.dll
05/16/2014 08:48 PM 60,928 AdbWinUsbApi.dll
05/16/2014 08:48 PM <DIR> busybox
05/16/2014 08:48 PM 11,001,856 recovery.lok
07/07/2014 04:41 PM 4,156 runme.bat
then type
adb shell
su
mkdir /sdcard/flash_tmp/
exit
exit
adb push ./aboot.img /sdcard/flash_tmp/aboot.img
adb push ./recovery.lok /sdcard/flash_tmp/recovery.lok
adb shell
su
chmod -R 777 /sdcard/flash_tmp
dd if=/sdcard/flash_tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/flash_tmp/recovery.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
rm -rf /sdcard/flash_tmp/
exit
exit
adb reboot recovery
unplug the cable once it starts rebooting and enter TWRP recovery...
It will be dim if you are coming from the 4.4.2 base, go to a dark room if needed so you can see it and flash a newer 4.4.2 recovery next if you are planning on using stock roms, or flash the 4.2.2. base otherwise... see my earlier post for a link to the recovery thread or the 4.2.2 base.

Thanks!
Everything works perfect
HTC One M8

Step 3 of idioterror's thread doesn't work.
You said:
2. Download and use step 3 from idioterror's thread here:
http://forum.xda-developers.com/showthread.php?t=2698267
However, I am unable to download the file from the link.
Do you know of another location where the file can be downloaded?
Thanks in advance!
Morty.

My Internal Storage Fix

This is the Step By Step Guide to how I solved my issue with the Internal Storage on my MTCB Android Head Unit.
These units come stock with a 1 GB internal storage partition and that was not enough for me, so I found a way to double it to 2 GB.
I am using a JOYING RK3188 800x480 head unit which I bought on amazon. This also worked on my Pumpkin C0250 RK3188 1024x600.
It worked for me, it may work for you.
I am not responsible for anything , EVER, ANYWHERE, IT'S NOT MY FAULT!
Seriously though, there are risks involved in this and I cannot be held responsible for what may happen if you choose to do this. YOYO
The tool is credited to WENDAL of Slatedroid. I found it here https://github.com/VeronicaEC/veronicaec.github.io/tree/master/MK808/Rockchip_TOOLS
Step 1: Create a folder called Stock, and unzip the tool into that folder and it will be in a folder called RK3066_IMG_Mod_Tool
This folder will contain a Temp folder as well as some .dll files, an app called "Runme" and a few other things. there are 21 files in all.
The most important of these for me are Temp, and Runme.
Step 2: In the folder STOCK\RK3066_IMG_Mod_Tool I placed a copy of the STOCK Unmodified firmware for my head unit, which is called "update.img" I then renamed this file to "wendal.img" (without the quote marks, because this is what the tool is looking for.)
Step 3: Next, I opened the app called "Runme" and a cmd window labled "Android Firmware Package Tool v1.3" opened on my desktop with instructions. 1-Unpack 2-Pack 3-Exit.
I entered 1 and pressed enter at the prompt to continue. This unpacked my firmware into the "Temp" Folder, then I entered 3 to Exit the tool.
Step 4: Inside the "Temp" folder were now 7 items, one of which is called "parameter" This was the only item I would be dealing with.
There may be other things I could change in here, but this thread is not about that. "parameter"is what I want, and "Temp" is where it is now located.
Step 5: So, now that I have the stock "parameter" file right where I want it I removed it. That's right, I pulled that little bugger right out of "Temp" and threw it away.
Step 6: At this point I needed a replacement for "parameter" and I needed to get it into the folder STOCK\RK3066_IMG_Mod_Tool\Temp
so I stole one from another firmware. I only needed a 2 GB patition for internal storage, and since I had a copy of the Malaysk ROM that was right for my unit, and that firmware had a 2 GB partition, I created another Folder on my desktop called "Malaysk" and unzipped a fresh copy of RK3066_IMG_Mod_Tool into that directory. This helped prevent confusion.
Step 7: Now I took that copy of the Malaysk Rom called "update.img" and placed it in the directory labled "Malaysk\RK3066_IMG_Mod_Tool"
Step 8: Then I changed the name of that img to "wendal.img" (because that is what the UnPack tool wants it to be called)
Step 9: It was time to open "Malaysk\RK3066_IMG_Mod_Tool\Runme" and unpack Malaysk Rom. into "Malaysk\RK3066_IMG_Mod_Tool\Temp" So I opened Malaysk\RK3066_IMG_Mod_Tool\Runme and once again entered 1 to unpack, then I entered 3 to Exit the tool.
Step 10: I opened the folder Malaysk\RK3066_IMG_Mod_Tool\Temp and there I found the new modified "parameter" file. I made a copy of this new parameter file and placed it in the folder STOCK\RK3066_IMG_Mod_Tool\Temp to replace the one I had thrown away.
Step 11: Now I was ready to repack the firmware I had in the STOCK folder. So I opened Runme from STOCK\RK3066_IMG_Mod_Tool and entered 2 for "Pack" to repack the firmware and pressed enter when prompted. This creates a new firmware file called "update_new.img"
Step 12: I copied update_new.img to the SD card for my Head Unit and renamed the img to "update.img" Then I flashed the firmware to my head unit using the method described in the firmware flash section of this forum.
Step 13: As I was reminded by jbleasdale below, whenever one is flashing a Rom to change any partition size on these units, it is necessary to do a factory/data wipe from the recovery menu on your first boot after the flash.

Good find! Many thanks for documenting this so clearly.
I followed these steps on my Joying RK3188 1024x600 unit and it worked well. Nothing appeared to have changed after performing the update at first, however I used the factory/data wipe option from the Recovery menu and I now have a much more usable 2Gb partition.

jbleasdale said:
Good find! Many thanks for documenting this so clearly.
I followed these steps on my Joying RK3188 1024x600 unit and it worked well. Nothing appeared to have changed after performing the update at first, however I used the factory/data wipe option from the Recovery menu and I now have a much more usable 2Gb partition.
Click to expand...
Click to collapse
Thanks for the reminder, I shall add this step to my post. Glad to know it worked for you.

Perfect!!! :good:

Clear and concise instructions, but something isn't working for me?
I've tried replacing the parameter file from Malaysk, which didn't work and then tried DSA and that didn't work either.
In the end, as I had already wiped the system, I thought I'd give DSA ROM a go. It's as good as stock and has a 2GB partition so will be using that for now.
Out of curiosity, I have attached images of the error I encountered when trying to flash with the new parameter file. Any ideas where I went wrong?
{
"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"
}

tariqkhan.co.uk said:
Clear and concise instructions, but something isn't working for me?
I've tried replacing the parameter file from Malaysk, which didn't work and then tried DSA and that didn't work either.
In the end, as I had already wiped the system, I thought I'd give DSA ROM a go. It's as good as stock and has a 2GB partition so will be using that for now.
Out of curiosity, I have attached images of the error I encountered when trying to flash with the new parameter file. Any ideas where I went wrong?
View attachment 3562392
View attachment 3562393
View attachment 3562394
Click to expand...
Click to collapse
I have run into this issue a few times on my Joying unit when I first tried to flash an untouched Stock Rom. If I recall properly,
I had to make 3 or 4 tries before the unit would accept the firmware. DSA has a number of solid firmware solutions for these head units, so it's difficult to go wrong choosing one of those. If anyone else has insight into this issue I would be interested in the solution.
Thank you for your feedback.

rickthecabbie said:
I have run into this issue a few times on my Joying unit when I first tried to flash an untouched Stock Rom. If I recall properly,
I had to make 3 or 4 tries before the unit would accept the firmware. DSA has a number of solid firmware solutions for these head units, so it's difficult to go wrong choosing one of those. If anyone else has insight into this issue I would be interested in the solution.
Thank you for your feedback.
Click to expand...
Click to collapse
It would be even better if someone can detail how to create your own parameter file; this may provide some light onto what actually went wrong?

Nand flash
I gave this a try with my JOYING R3188 x600 with the lastest Beta JOYING rom and used the parameters file from lastest malaysk mod and no luck!
- I did a factory/cache wipe through recovery both before and after flashing and though i have 13gb free internal memory... the NAND FLASH shows as unmounted and that's a problem when trying to download anything because it needs an external "sd" so it calls it to save to (i have an sd, it's the NAND it's looking for)

Motafota said:
I gave this a try with my JOYING R3188 x600 with the lastest Beta JOYING rom and used the parameters file from lastest malaysk mod and no luck!
- I did a factory/cache wipe through recovery both before and after flashing and though i have 13gb free internal memory... the NAND FLASH shows as unmounted and that's a problem when trying to download anything because it needs an external "sd" so it calls it to save to (i have an sd, it's the NAND it's looking for)
Click to expand...
Click to collapse
The problem with using the file from the most recent Malaysk Rom is that it is a FUSE Rom. This is a completely different type of file system.
You can use this technique with the older Malaysk Parameter file as long as it is from a Pre-FUSE Rom. Thanks for sharing your results. :good:

Figured I'd share my parameters file for 3GB of user data and also explain how to create whatever you'd like (if you'd like to go beyond that or something different than the 2GB on Mal's Rom).
If you look at the bottom line of the parameter file (open it in notepad or similar) you will see it defines not only the partition size for each partition (0x00200000 for example is 1GB) but also the start point of the partition @0x00080000 for example is where the user data partition starts).
Now when we increase one partition it has the knock on effect of changing the start point of all of the following ones.
So for example if the user data partition starts at @0x00080000 and is originally 0x00200000 in size, the next partition (metadata) would start at @0x00280000 (the 0x00080000 original start point of the user data partition + the size of the user data partition 0x00200000, 0x00080000 + 0x00200000 = 0x00280000).
The meta data partition is 0x00002000 in size so the next partition would start at 0x00282000 (0x00280000 + 0x00002000) and so on and so forth.
So if we want to change the user data partition to 3GB (0x00600000) we change the size part of the user data to that and then we add on whatever the increase was, so if our original partition size was 0x00200000 we added 0x00400000 to it so the start position for each partition that follows gets increased by 0x00400000
See in bold for the changes in a partial example:
Code:
[email protected](userdata),[email protected](metadata),[email protected](kpanic),[email protected](system),[email protected](oem), [user=2610264]@0x00[/user]444000(user)
becomes
Code:
0x00[B]6[/B][email protected](userdata),[email protected][B]6[/B]80000(metadata),[email protected][B]6[/B]82000(kpanic),[email protected][B]6[/B]84000(system),[email protected][B]8[/B]04000(oem), [user=2610264]@0x00[/user][B]8[/B]44000(user)
has you can see the size of the userdata partition was increased by 0x0040000 (additional 2GB) and then the start point for every partition after was increased by the same 0x00400000, for a 3GB increase you'd use 0x0060000 and so on.

Thank you rickthecabbie and jakejm79! My system now has 4GB in the user data space.

This method does not work, I tried many times but always error !
this method I had found online several months before...
You know another working method ?

pinotuning said:
You know another working method ?
Click to expand...
Click to collapse
Simply flash any "FUSE" ROM...

themissionimpossible said:
Simply flash any "FUSE" ROM...
Click to expand...
Click to collapse
I asked if there is another method !!
no FUSE" ROM

pinotuning said:
I asked if there is another method !!
no FUSE" ROM
Click to expand...
Click to collapse
Probably you're doing something wrong because some time ago for me that method worked perfectly...
Now I'm using a FUSE ROM because for me personally it's a better solution.

themissionimpossible said:
Probably you're doing something wrong because some time ago for me that method worked perfectly...
Now I'm using a FUSE ROM because for me personally it's a better solution.
Click to expand...
Click to collapse
My friend, I have tested this method many times and it does not work !!
Always update fail !!

I solved by another method
regards

pinotuning said:
I solved by another method
regards
Click to expand...
Click to collapse
Perhaps you could write a tutorial for the other method to help people who may not be able to use the one posted in this thread?

rickthecabbie said:
This is the Step By Step Guide to how I solved my issue with the Internal Storage on my MTCB Android Head Unit.
These units come stock with a 1 GB internal storage partition and that was not enough for me, so I found a way to double it to 2 GB.
I am using a JOYING RK3188 800x480 head unit which I bought on amazon. This also worked on my Pumpkin C0250 RK3188 1024x600.
It worked for me, it may work for you.
I am not responsible for anything , EVER, ANYWHERE, IT'S NOT MY FAULT!
Seriously though, there are risks involved in this and I cannot be held responsible for what may happen if you choose to do this. YOYO
The tool is credited to WENDAL of Slatedroid. I found it here https://github.com/VeronicaEC/veronicaec.github.io/tree/master/MK808/Rockchip_TOOLS
Step 1: Create a folder called Stock, and unzip the tool into that folder and it will be in a folder called RK3066_IMG_Mod_Tool
This folder will contain a Temp folder as well as some .dll files, an app called "Runme" and a few other things. there are 21 files in all.
The most important of these for me are Temp, and Runme.
Step 2: In the folder STOCK\RK3066_IMG_Mod_Tool I placed a copy of the STOCK Unmodified firmware for my head unit, which is called "update.img" I then renamed this file to "wendal.img" (without the quote marks, because this is what the tool is looking for.)
Step 3: Next, I opened the app called "Runme" and a cmd window labled "Android Firmware Package Tool v1.3" opened on my desktop with instructions. 1-Unpack 2-Pack 3-Exit.
I entered 1 and pressed enter at the prompt to continue. This unpacked my firmware into the "Temp" Folder, then I entered 3 to Exit the tool.
Step 4: Inside the "Temp" folder were now 7 items, one of which is called "parameter" This was the only item I would be dealing with.
There may be other things I could change in here, but this thread is not about that. "parameter"is what I want, and "Temp" is where it is now located.
Step 5: So, now that I have the stock "parameter" file right where I want it I removed it. That's right, I pulled that little bugger right out of "Temp" and threw it away.
Step 6: At this point I needed a replacement for "parameter" and I needed to get it into the folder STOCK\RK3066_IMG_Mod_Tool\Temp
so I stole one from another firmware. I only needed a 2 GB patition for internal storage, and since I had a copy of the Malaysk ROM that was right for my unit, and that firmware had a 2 GB partition, I created another Folder on my desktop called "Malaysk" and unzipped a fresh copy of RK3066_IMG_Mod_Tool into that directory. This helped prevent confusion.
Step 7: Now I took that copy of the Malaysk Rom called "update.img" and placed it in the directory labled "Malaysk\RK3066_IMG_Mod_Tool"
Step 8: Then I changed the name of that img to "wendal.img" (because that is what the UnPack tool wants it to be called)
Step 9: It was time to open "Malaysk\RK3066_IMG_Mod_Tool\Runme" and unpack Malaysk Rom. into "Malaysk\RK3066_IMG_Mod_Tool\Temp" So I opened Malaysk\RK3066_IMG_Mod_Tool\Runme and once again entered 1 to unpack, then I entered 3 to Exit the tool.
Step 10: I opened the folder Malaysk\RK3066_IMG_Mod_Tool\Temp and there I found the new modified "parameter" file. I made a copy of this new parameter file and placed it in the folder STOCK\RK3066_IMG_Mod_Tool\Temp to replace the one I had thrown away.
Step 11: Now I was ready to repack the firmware I had in the STOCK folder. So I opened Runme from STOCK\RK3066_IMG_Mod_Tool and entered 2 for "Pack" to repack the firmware and pressed enter when prompted. This creates a new firmware file called "update_new.img"
Step 12: I copied update_new.img to the SD card for my Head Unit and renamed the img to "update.img" Then I flashed the firmware to my head unit using the method described in the firmware flash section of this forum.
Step 13: As I was reminded by jbleasdale below, whenever one is flashing a Rom to change any partition size on these units, it is necessary to do a factory/data wipe from the recovery menu on your first boot after the flash.
Click to expand...
Click to collapse
Thanks, Rickthecabbie and the other contributors. I followed the detailed directions and now have 2 GB on Pumpkin RK3188. Not a single hiccup and finished in 30 minutes, most of which was spent downloading the files.

jbleasdale said:
Good find! Many thanks for documenting this so clearly.
I followed these steps on my Joying RK3188 1024x600 unit and it worked well. Nothing appeared to have changed after performing the update at first, however I used the factory/data wipe option from the Recovery menu and I now have a much more usable 2Gb partition.
Click to expand...
Click to collapse
Can someone please let me know if this still works on the joying with 4.4? Also very important, if i do the factory/data wipe option will it erase everything and put me back to stock?? ALso i heard after a whip you cant use easy connect, any help is appreciated cause im at my last wits with this pathetic space, cant update anything.

How To Guide [GUIDE] Change Splash screen for this phone!

NOTE: I am not responsible for any bricked devices. DO THIS AT YOUR OWN RISK!
Click to expand...
Click to collapse
I recently changed my splash screen logo from samsung to a custom one i made in pixlr. Its looks coool. A video is attached below.
REQUIREMENTS:
- ROOTED A32 4G
- usb c cable (to connect to pc)
- windows PC (for zipping and etc.)
- ADB installed on your pc. (For running shell commands) [OR YOU COULD USE SOME TERMINAL EMULATOR]
If your doing this on your phone just follow along, i included seperate commands.
STEPS:
1. Download attached up_param.bin (i extracted this from android 11 firmware. it shld work with fine with 12 they are same. Since downloading whole firmware takes alot of time)
2. Install 7zip if you already didn't from here.
3. Make a working directory anywhere
4. Use 7 zip to extract up_param.bin to a folder.
After extracting this is what you should see
{
"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"
}
These are all the images!
5. modify files as you like. (MAKE SURE THE DIMENSIONS ARE THE SAME. AND DO NOT REMOVE ANY IMAGE IT COULD BRICK)
NOTE: DO NOT TOUCH DOWNLOAD MODE IMAGES. if you f**k them up you will never be able to get into download mode again
You can replace boot_warning.jpg, logo.jpg (main file responsible logo), letter.jpg (the logo that shows for a split second), svb_orange.jpg (boot loader unlock warning)
6. select all images -> right click -> add to archive.
7. set it to tar.
8. set compression method to GNU.
This is what it should look like
9. Click on OK.
10. Now connect your A32 to the PC. (enable USB debugging)
11. Copy over the tar file that was generated by 7zip to anywhere. i am gonna assume we placed it in the internal storage (/sdcard/)
12. Run the following commands.
NOTE: I am editing the original thread since i checked in up param file of my new a13 fw and found new file. Its for if the battery temperature is too high. if you modify the up param from a11 fw and flash that it may not exist and the phone will boot loop if it wants to display the menu...
iM UPLOADING A13 stock up_param HERE FROM A325FXXU2CVK3.
Uploaded as up_param-a13.bin
adb shell (Phone users skip this.)
su
(Grant su permission if the popup comes up).
Then run
ls -l /dev/block/platform/****/by-name
After you get a long output. Search for up_param.
(We all have the same phone but just in case some people with diff samsung mtk phones come here).
now we just have to run 2 more commands and we are done!
Taking backups incase something goes wrong.
(People with different phones replace your up_param partition name here.)
dd if=/dev/block/mmcblk0p35 of=/sdcard/backup-param.bin
Now flashing our new modified up_param with new images
dd if=/sdcard/filename.tar of=/dev/block/mmcblk0p35
WE ARE DONE! now reboot and enjoy the new logo!

CREDITS:
- Orignal post: here.
Also video attached below

Captain_cookie_200 said:
I recently changed my splash screen logo from samsung to a custom one i made in pixlr. Its looks coool. A video is attached below.
REQUIREMENTS:
- ROOTED A32 4G
- usb c cable (to connect to pc)
- windows PC (for zipping and etc.)
- ADB installed on your pc. (For running shell commands) [OR YOU COULD USE SOME TERMINAL EMULATOR]
If your doing this on your phone just follow along, i included seperate commands.
STEPS:
1. Download attached up_param.bin (i extracted this from android 11 firmware. it shld work with fine with 12 they are same. Since downloading whole firmware takes alot of time)
2. Install 7zip if you already didn't from here.
3. Make a working directory anywhere
4. Use 7 zip to extract up_param.bin to a folder.
After extracting this is what you should see
View attachment 5775661
These are all the images!
5. modify files as you like. (MAKE SURE THE DIMENSIONS ARE THE SAME. AND DO NOT REMOVE ANY IMAGE IT COULD BRICK)
NOTE: DO NOT TOUCH DOWNLOAD MODE IMAGES. if you f**k them up you will never be able to get into download mode again
You can replace boot_warning.jpg, logo.jpg (main file responsible logo), letter.jpg (the logo that shows for a split second), svb_orange.jpg (boot loader unlock warning)
6. select all images -> right click -> add to archive.
View attachment 5775663
7. set it to tar.
8. set compression method to GNU.
This is what it should look like
View attachment 5775665
9. Click on OK.
10. Now connect your A32 to the PC. (enable USB debugging)
11. Copy over the tar file that was generated by 7zip to anywhere. i am gonna assume we placed it in the internal storage (/sdcard/)
12. Run the following commands.
adb shell (Phone users skip this.)
su
(Grant su permission if the popup comes up).
Then run
ls -l /dev/block/platform/****/by-name
After you get a long output. Search for up_param.
View attachment 5775673
(We all have the same phone but just in case some people with diff samsung mtk phones come here).
now we just have to run 2 more commands and we are done!
Taking backups incase something goes wrong.
(People with different phones replace your up_param partition name here.)
dd if=/dev/block/mmcblk0p35 of=/sdcard/backup-param.bin
Now flashing our new modified up_param with new images
dd if=/sdcard/filename.tar of=/dev/mmcblk0p35
WE ARE DONE! now reboot and enjoy the new logo!
Click to expand...
Click to collapse
Very good thanks

kilam9900 said:
Very good thanks
Click to expand...
Click to collapse
hehe your welcome. hope it works epikly for you. (if you do it)

Captain_cookie_200 said:
hehe your welcome. hope it works epikly for you. (if you do it)
Click to expand...
Click to collapse
I will do it but I am scare to f**k size so I will do it on PC

kilam9900 said:
I will do it but I am scare to f**k size so I will do it on PC
Click to expand...
Click to collapse
oh lmao. if you do end up breaking your up_param it would still boot fine. but downlaod mode would break until a proper up param file is flashed again.

Captain_cookie_200 said:
oh lmao. if you do end up breaking your up_param it would still boot fine. but downlaod mode would break until a proper up param file is flashed again.
Click to expand...
Click to collapse
I'm reassured

I recommend using dd oflag=direct,sync if=/sdcard/filename.tar of=/dev/block/mmcblk[...] otherwise you may get all sorts of problems, even a bricked phone, especially if you reboot straightaway after flashing. Inside Android all data transfers are cached, it's not the Download tool where everything is synchronous (or at least flushed before reboot).

uluruman said:
I recommend using dd oflag=direct,sync if=/sdcard/filename.tar of=/dev/block/mmcblk[...] otherwise you may get all sorts of problems, even a bricked phone, especially if you reboot straightaway after flashing. Inside Android all data transfers are cached, it's not the Download tool where everything is synchronous (or at least flushed before reboot).
Click to expand...
Click to collapse
i didnt have to deal with anything like that. i did multiple flashes atleast 15 flashes using dd to the up param partition and i did not brick my phone at all. worse you could get is a black screen while booting. and your download mode would not work. but its easy to get it back just flash the up param file again the one that was backed up. although thanks for the info. i did this using recovery. could also be done while booted into android itself

Captain_cookie_200 said:
i didnt have to deal with anything like that. i did multiple flashes atleast 15 flashes using dd to the up param partition and i did not brick my phone at all. worse you could get is a black screen while booting. and your download mode would not work. but its easy to get it back just flash the up param file again the one that was backed up. although thanks for the info. i did this using recovery. could also be done while booted into android itself
Click to expand...
Click to collapse
I ran into this problem when rebooted the phone using the "reboot" shell command right after the "dd". When rebooting from the UI all caches are flushed, of course, but the "reboot" command is a bit crude method I suppose (although in Linux it's always absolutely graceful). Anyway, the logo screen looked absolutely fine, and the system booted okay, but when I tried to enter Download I got the black screen and the boot loop, and no way to either enter Download, Recovery or boot the system. In fact the only thing that still worked was forced reboot (Power + Vol Down). I was able to get out of this situation by connecting the charger and holding Power + Vol Down to force the phone into the off state, then I connected it to the PC and tried entering the Download mode once again, and this time it worked although the graphics was all messed up.

uluruman said:
I ran into this problem when rebooted the phone using the "reboot" shell command right after the "dd". When rebooting from the UI all caches are flushed, of course, but the "reboot" command is a bit crude method I suppose (although in Linux it's always absolutely graceful). Anyway, the logo screen looked absolutely fine, and the system booted okay, but when I tried to enter Download I got the black screen and the boot loop, and no way to either enter Download, Recovery or boot the system. In fact the only thing that still worked was forced reboot (Power + Vol Down). I was able to get out of this situation by connecting the charger and holding Power + Vol Down to force the phone into the off state, then I connected it to the PC and tried entering the Download mode once again, and this time it worked although the graphics was all messed up.
Click to expand...
Click to collapse
did you touch the download mode images in any way? i dont know why this happened for you. i guess i did press the reboot button instead of using the command. since i do it on first fw reflash and i flash a gsi immdiiately afterwards... download shouldnt have died like that tho. i messed with my down load images completely. i competely replaced them with diff new images that are diff sizes too. i dont know why this is happening for you. my download works fine. although it reverts to the old download image somehow once on downloading mode. for confirmations it does show my edited images.

Captain_cookie_200 said:
did you touch the download mode images in any way? i dont know why this happened for you. i guess i did press the reboot button instead of using the command. since i do it on first fw reflash and i flash a gsi immdiiately afterwards... download shouldnt have died like that tho. i messed with my down load images completely. i competely replaced them with diff new images that are diff sizes too. i dont know why this is happening for you. my download works fine. although it reverts to the old download image somehow once on downloading mode. for confirmations it does show my edited images.
Click to expand...
Click to collapse
I suppose your Download still worked fine because the up_param tar archive was complete and not corrupt, and even image files were normal and not chopped in the middle of the data stream. In my case it was the latter, when cache is not flushed the data stream is just cut, and such a simple program as Download obviously cannot handle broken files. The Download tool itself is kept in the separate "debugger" flash memory, I guess it has the default graphics too which can be displayed if no graphics is found in up_param.

uluruman said:
I suppose your Download still worked fine because the up_param tar archive was complete and not corrupt, and even image files were normal and not chopped in the middle of the data stream. In my case it was the latter, when cache is not flushed the data stream is just cut, and such a simple program as Download obviously cannot handle broken files.
Click to expand...
Click to collapse
oh i see. thanks for telling about this. it would help people alot from preventing to brick their phone from bricking

Captain_cookie_200 said:
oh i see. thanks for telling about this. it would help people alot from preventing to brick their phone from bricking
Click to expand...
Click to collapse
Correction: 'dd oflag=direct,sync' does not work in Android shell, the working alternative is 'dd conv=fsync'

Captain_cookie_200 said:
I recently changed my splash screen logo from samsung to a custom one i made in pixlr. Its looks coool. A video is attached below.
REQUIREMENTS:
- ROOTED A32 4G
- usb c cable (to connect to pc)
- windows PC (for zipping and etc.)
- ADB installed on your pc. (For running shell commands) [OR YOU COULD USE SOME TERMINAL EMULATOR]
If your doing this on your phone just follow along, i included seperate commands.
STEPS:
1. Download attached up_param.bin (i extracted this from android 11 firmware. it shld work with fine with 12 they are same. Since downloading whole firmware takes alot of time)
2. Install 7zip if you already didn't from here.
3. Make a working directory anywhere
4. Use 7 zip to extract up_param.bin to a folder.
After extracting this is what you should see
View attachment 5775661
These are all the images!
5. modify files as you like. (MAKE SURE THE DIMENSIONS ARE THE SAME. AND DO NOT REMOVE ANY IMAGE IT COULD BRICK)
NOTE: DO NOT TOUCH DOWNLOAD MODE IMAGES. if you f**k them up you will never be able to get into download mode again
You can replace boot_warning.jpg, logo.jpg (main file responsible logo), letter.jpg (the logo that shows for a split second), svb_orange.jpg (boot loader unlock warning)
6. select all images -> right click -> add to archive.
View attachment 5775663
7. set it to tar.
8. set compression method to GNU.
This is what it should look like
View attachment 5775665
9. Click on OK.
10. Now connect your A32 to the PC. (enable USB debugging)
11. Copy over the tar file that was generated by 7zip to anywhere. i am gonna assume we placed it in the internal storage (/sdcard/)
12. Run the following commands.
NOTE: I am editing the original thread since i checked in up param file of my new a13 fw and found new file. Its for if the battery temperature is too high. if you modify the up param from a11 fw and flash that it may not exist and the phone will boot loop if it wants to display the menu...
iM UPLOADING A13 stock up_param HERE FROM A325FXXU2CVK3.
Uploaded as up_param-a13.bin
adb shell (Phone users skip this.)
su
(Grant su permission if the popup comes up).
Then run
ls -l /dev/block/platform/****/by-name
After you get a long output. Search for up_param.
View attachment 5775673
(We all have the same phone but just in case some people with diff samsung mtk phones come here).
now we just have to run 2 more commands and we are done!
Taking backups incase something goes wrong.
(People with different phones replace your up_param partition name here.)
dd if=/dev/block/mmcblk0p35 of=/sdcard/backup-param.bin
Now flashing our new modified up_param with new images
dd if=/sdcard/filename.tar of=/dev/block/mmcblk0p35
WE ARE DONE! now reboot and enjoy the new logo!
Click to expand...
Click to collapse
NOTE: I am editing the original thread since i checked in up param file of my new a13 fw and found new file. Its for if the battery temperature is too high. if you modify the up param from a11 fw and flash that it may not exist and the phone will boot loop if it wants to display the menu...
iM UPLOADING A13 stock up_param HERE FROM A325FXXU2CVK3.
Uploaded in orignal thread as up_param-a13.bin

I made it and works perfectly, thanks for the tutorial!!

ApiYoshi said:
I made it and works perfectly, thanks for the tutorial!!
Click to expand...
Click to collapse
glad to hear thatt. and your welcome

how to apply this on snapdragon devices
they don't have up_parem.bin file ??

elswerky said:
how to apply this on snapdragon devices
they don't have up_parem.bin file ??
Click to expand...
Click to collapse
they do? check inside bl file of your firmware. Or using the partition list command should show it

Captain_cookie_200 said:
they do? check inside bl file of your firmware. Or using the partition list command should show it
Click to expand...
Click to collapse
Bl file itself doesn't have up_parem.bin file
Unlike exynis devices which have it
And am.nit familiar with partition as you said if you can helping me
Talking about tab S6 w8th android 12 , OneUi 4.1