Hello!
Now I'll start off with what this thread is and all the associated warnings and disclaimers. First off, If you are looking to flash a Viewsonic g Tablet with a custom bootscreen, YOU ARE IN THE RIGHT PLACE.
Now one of my favorite hacks to any device is to customize the bootscreen, it just completes the "hacked device" feel for me. I have found that the info on how to do this is fairly advanced, many people who may want to do this could be turned off by that fact! However, that being said flashing anything with nvflash is very risky and you could lose personal data and/or soft/hard brick your tablet so, if your head is on backwards, or you are just stupid, I'd avoid this anyways
Make a back-up of any personal data anyways!
Also, this guide is mainly for windows users, I am writing this because most of the limited info currently available was for Linux. This may be useful to linux users still, but don't be surprised if you are not finding what you need for a linux problem.
Now the first thing you need to do, if you haven't before, is download two ESSENTIAL tools:
NVFlash (choose the windows one AND the gTablet one): http://db.tt/Wm25t7U
NOTE: I've heard this link can be picky, I've had good luck but beware.
The APX driver for windows: http://www.myadventvega.co.uk/SystemUSB.zip
------------------------------------------
From here you have too extract the windows nvflash into a directory (just do what I did and call it NVFlash, put somewhere like your desktop).
Now extract just the bootloader.bin file from the gtablet nvflash zip file, also put it into that directory.
Now, to put your tablet into APX mode, power it down, then hold down the power and VOLUME - buttons until the current bootscreen comes up and then goes blank (let go at that point). Windows should now detect a new device, the installation will fail, but after that go into Device Manager and right-click on APX then choose Update drivers. Choose to specify a location, then extract the SystemUSB.zip and point it to the folder containing the i386 and amd64 folders. It should install and then you should be good.
Now your tablet is ready to be flashed, which means we are going to define some terms. First off, what I will refer to as the first boot screen is located in partition 6, it defaults to the viewsonic birds and is the first one to show up. What I will refer to as the second boot screen is actually part of the ROM you use and is much trickier to change. It defaults to gTablet in an oval.
To flash the first boot creen locate a 24-bit bitmap file, 1024x600, I use the one below. This is not the actual bmp though, the actual bootscreen is attached to this post. Now once you have a file, place it in your NVFlash directory.
{
"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"
}
Now you need to open a command prompt into your NVFlash directory and run:
Code:
nvflash --bl bootloader.bin --download 6 yourfile.bmp
You should now have a nice new bootscreen, if you have a problem, see the bottom for the FAQ.
To flash the second bootscreen you must not only want this pretty bad, but be ready to lose stuff! The second bootscreen is actually part of the ROM you are using. You can either find a premodified boot.img in this thread:
http://forum.xda-developers.com/showthread.php?t=876488
or make your own using those instructions.
YOU MUST USE THE BOOT.IMG FROM YOUR EXACT ROM, IF IT'S NOT THE EXACT SAME YOU WILL SOFT-BRICK YOUR TABLET!!! QUADRUPLE CHECK THIS!!!!
once you have a boot.img and you've placed it in the NVFlash directory, run this command:
Code:
nvflash --bl bootloader.bin --download 10 boot.img
You may want to keep different images seperate by renaming them or keeping them in a different folder, just remember that you have to flash boot.img, don't change the file name!
To save some time you can use this batch file:
Code:
@echo off
rem If your edit this file, you also accept any responsibility for the damages incurred to your tablet!
:terms
echo ------------------ TERMS OF USE ------------------
echo --- ---
echo --- If you use this batch file, you accept all ---
echo --- responsibility for anything that happens ---
echo --- to your gTablet! ---
echo --- ---
echo --- This process is risky and can cause damage ---
echo --- to your tablet! I don't accept any ---
echo --- responsibility for these damage! ---
echo --- ---
echo --- BASICALLY, USE AT YOUR OWN RISK! ---
echo --- ---
echo --------------------------------------------------
set /p terms=If you agree to these terms type "agree" (no quotes) or else type "decline":
if '%terms%'=='agree' goto top
goto exit
:top
cls
echo Make sure that you have bootloader.bin and nvflash.exe in thie same directory as this file or in PATH!
echo Make sure that your tablet ic connected in APX Mode and ready to be flashed!
echo 1 = Flash initial bootscreen (viewsonic birds is original) (part 6)
echo 2 = Flash secondary bootscreen (gTablet in an oval is original) (part 10)
echo Q = Quit
@set /p ui=Choose one to continue:
if '%ui%'=='1' goto part6
if '%ui%'=='2' goto part10
if '%ui%'=='q' goto exit
if '%ui%'=='Q' goto exit
goto top
:part6
cls
set /p fname6=Enter the file name (relative to this directory):
set /p confirm=Is %fname6% correct? Press y or n, confirm this carefully or you will likely brick your tablet!:
if '%confirm%'=='y' goto flash6
goto part6
:flash6
echo Flashing %fname6% to partition 6 of the connected g Tablet
nvflash --bl bootloader.bin --download 6 %fname6%
pause
goto top
:part10
cls
set /p fname10=Type the location of the proper boot.img (relative to this directory) (this should be a modified version specific to your flashed ROM):
set /p confirm=Is %fname10% the correct location and is this the boot.img for the correct ROM? Press y or n, confirm this carefully or you will likely brick your tablet!:
if '%confirm%'=='y' goto flash10
goto part6
:flash10
echo Flashing %fname10% to partition 10 of the connected g Tablet
nvflash --bl bootloader.bin --download 10 %fname10%
pause
goto top
:exit
exit
Just save this as bootscreen.bat in your NVFlash directory!
And that's about it!
Common errors (FAQ):
Code:
Couldn't find usb device
- Your drivers aren't installed properly or you aren't in APX mode.
Credits (threads I learned this from):
http://forum.xda-developers.com/showthread.php?t=861950
http://forum.xda-developers.com/showthread.php?t=859383
Also the above mentioned thread!
Thanks and have a nice day!
i follow your steps but nothing happen / file not fund error, i put the windows , bootloader bin , and the new image in a folder and run the gtab batch and i just get that error. what im doing wrong .
thanks for any help
patne83 said:
i follow your steps but nothing happen / file not fund error, i put the windows , bootloader bin , and the new image in a folder and run the gtab batch and i just get that error. what im doing wrong .
thanks for any help
Click to expand...
Click to collapse
Well, your explanation of your problem isn't very clear, but I'm assuming you are trying to flash the first boot screen and you are having issues. Please supply some more information or try rereading the steps you're having trouble with.
Related
Hello !
I wrote some scripts for easily pushing and installing files/apks to your android device.
The advantage over "command line" and other scripts like mine :
- Multiple selection allowed (install 100 APKs in one click ! )
- You have a progress bar (shows only the progression between multiples files/ not the state of a single pushing).
- You can choose the destination on your phone with a simple prompt by choosing "Push to ..."
- It's a very simple and lightweight nautilus script...
- You don't have to (in fact, you can't) put the usb in "usb disk" mode, just have debugging enabled.
Examples
To simply install some applications, just select them, right click, go to scripts->ADB->install
{
"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"
}
Progression :
Idem for files :
Progress :
Confirmation :
(So the "Push to ..." allow you to choose a destination. "Push to musique" is just a copy of "Push to sdcard" with the second line of the script changed to copy files to /sdcard/music/ instead of /sdcard/ )
How to install
- Download the scripts :
http://www.itstudents.be/~tom/android/ADB Scripts for Nautilus.tar.gz- Uncompress the files in ~/.gnome2/nautilus_scripts/ADB/
So if your name is mario, you should copy the 3 files to :
/home/mario/.gnome2/nautilus-scripts/ADB/
You are not obliged to make the last folder named ADB, it's just to make "categories" in the Nautilus script menu (like in the screenshots)
Requirements
- A correctly installed ADB
What is a correctly installed ADB?
- The PATH environment variable has to be set, to be able to just type "adb" and not "/path/to/sdk/platform-tools/adb". If it's not done :
Edit the file ~/.bashrc , you can do that by typing in the console
Code:
gedit ~/.bashrc
and add this line changed for yourself at the end of the file
Code:
export PATH=${PATH}:/path/to/android-sdk-linux_86/platform-tools/
Or, if this does'nt work :
Edit the file /etc/environment , you can do that by typing in the console
Code:
gedit /etc/environment
and add this text changed for yourself at the end of the line "PATH:", before the last ["]
Code:
:/path/to/android-sdk-linux_86/platform-tools/
- The rules for udev have to be made to allow any non-root user to access to the device
Method for any HTC device :
Edit with root rights the file /etc/udev/rules.d/51.android.rules by typing in the console :
Code:
gksudo gedit /etc/udev/rules.d/51.android.rules
and add the lines :
Code:
SUBSYSTEM=="usb|usb_device", SYSFS{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
Hope you'll enjoy !
Please correct my english
don't want people to know what you're listening to, eh?
It's cool; I like it.
very useful
thanks man
I've been wanting to do something like this but never had time to. Will definitely test this out!
Sent from my Nexus One using XDA App
Oh epic win thanks for this!
Sent from my HTC Hero using XDA App
Please reupload ADB Scripts for Nautilus.tar.gz somewhere.
Stupid me...
http://www.kmel.be/~tom/android/ADB Scripts for Nautilus.tar.gz
Please note a little "bug", the progress bar progress when a file start transfer. So if you send just one big file, it will be at 100% for a little time...
Easily correctible, but I haven't the time now...
MappaM said:
Stupid me...
http://www.kmel.be/~tom/android/ADB Scripts for Nautilus.tar.gz
Please note a little "bug", the progress bar progress when a file start transfer. So if you send just one big file, it will be at 100% for a little time...
Easily correctible, but I haven't the time now...
Click to expand...
Click to collapse
nice work. very handy
EDIT: actually I may have spoke too soon, these don't seem to be working for me. Ubuntu 10.10
I know my udev and $PATH are all set up correctly. So I'm not sure where these are failing for me..
any thoughts?
EDIT2: OK it was a $PATH issue the ~.bashrc however is only for interactive non login shells adding the adb path to ~.profile and a re-login solved my problem with this script. Or alternatively you could call adb in the script using it's full path.
Thanks MappaM for the great base script!
Here is my version of "Push to Movies":
My solution to the immediately full progress bar was to use the --pulsate option in zenity this works for me because I am likely to only be sending one file anyway and don't need the fine grain feed back of an incremental progress bar. The one that bounces back and forth is what you will see.
echo "15" ; sleep 1
is a hack, you may not need it but for me it lets the pulsate flag work.
zenity bugs reported here
https://bugs.launchpad.net/zenity/+bug/291850
https://bugzilla.gnome.org/show_bug.cgi?id=567663
Code:
#!/bin/sh
#this is MY path, your path will be different . change this path.
android_path="/sdcard/media/video/movies/"
i=1
(
for thing in "[email protected]"
do
# this first echo tricks the pulsate into working you may not need it. try it both with and without it.
echo "15" ; sleep 1
echo $(($i * 100 / $#))
echo "# Pushing \"${thing}\"" ;
adb push "${thing}" $android_path
i=$(($i+1))
done; i=$(($i-1)) ; echo "# $i files pushed." ) | zenity --progress --pulsate --auto-kill --width=300 --text "Copying files..." --title "Pushing files to $android_path"
HOW-TO Fix **ADB is not recognized in the CMD**
Navigate to & Left_Click on Start >
Right_Click on Computer >
Left_Click on Advance System Settings >
Left_Click on Environment Variables >
Left_Click on New ( User Variables ) >
Variables Name: ADB ( Or anything you want )
Variables Value: ;C:\SDK\tools ( Just like this, This is the Path of my adb.exe )
You must put a ; in front of ;C:\ ( adb Path goes here / Variables Value: )
That's it.. You now have set up adb to work Global via cmd prompt on win7
~Eugene
eugene373 said:
HOW-TO Fix **ADB is not recognized in the CMD**
Navigate to & Left_Click on Start >
Right_Click on Computer >
Left_Click on Advance System Settings >
Left_Click on Environment Variables >
Left_Click on New ( User Variables ) >
Variables Name: ADB ( Or anything you want )
Variables Value: ;C:\SDK\tools ( Just like this, This is the Path of my adb.exe )
You must put a ; in front of ;C:\ ( adb Path goes here / Variables Value: )
That's it.. You now have set up adb to work Global via cmd prompt on win7
~Eugene
Click to expand...
Click to collapse
That should help with a lot of the issues I see being posted, not only here but on many Threads. Simple path statement 101
Better: Chose "Path" in "Systemvariables" and put it at the end of this line, i.e. like this: ";C:\android\platform-tools;C:\android\tools". Because then it'll even work if u run the cmd as administrator, which won't work if you do it as described above. Atleast its been the way on my W7 Ultimate 64
{
"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"
}
Hi,
another way (and very useful for other reasons) is to change registry like this:
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Folder\shell\Command Prompt]
@="open cmd here"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Folder\shell\Command Prompt\Command]
@="cmd.exe /k pushd %L"
Afterwards you are - by right-clicking the adb-folder - directly in the right folder.
Don´t know if you have to restart, i´m using it just a long time.
Greets
idephili
or just put the tools folder and adb binarys in C:\Windows or C:\Widnows\System32 ;-)
done
I know this is of topic but thanks Eugene for all of your contributions
Sent from my HTC Sensation 4G using XDA Premium App
Eugene373, I am so happy you're devving on the Sensation! Thanks for the ADB how-to...it really helped! Will you continue to develop and make ROM's for this device?
Alternatively you can also copy the ADB and Fastboot.exe files over to System32 or SysWOW64 folders and they work fine as well.
as google shows up this thread here my two cents...
the mentioned methods don't work for me nor anyone else('s computer) running windows 7 professional 64 bit i know. here's what in fact works perfectly on any computer i tried it on:
copy the path to your adb.exe wherever it is, put a semicolon in front of the path and attach it to the existing entry in the PATH variable. no matter if you add it as an user oder system variable. last one is only to recommend as you're dealing with multiple users which all need to access adb via cmd
is there a way to convert the twrp file backup on my pc to get it back on to my phone to install the backup everytime i try to put it back on my phone via adb it errors out and im stuck at this point ive been at this for over 10 hours just trying to restore my backup i have the backup file on the pc and ive backed it up earlier but now it errors there has to be a way to get this backup back onto my phone in a way that it will recognize it and install it please help lol im familiar with custom roms and the like not a expert but i kinda know what im doing and ive loaded custom roms on many phones in the past with no issues but this one is proving to be a real pain using a note 4 n910t
for more info i was trying to install petbede's rom and i managed to get to the reboot stage and he states it could take anywhere from 7-10 mins on average for it to boot up but mine was going on 20 mins plus and was getting really hot so i pulled the plug and as long as ive been trying to do this in one sitting i just want my backup installed and to be done with it for a few days untill i can muster the courage to try it again but this time i will be backing up on a seperate sd card that i can just pop into the phone to restore from since the pc copy is not playing nice with me
Hi,
I'm releasing a tool for changing the splash image inside the bootloader. It is available in 2 version, GUI & cmd line. The GUI is only for windows while the cmd line is platform independent.
GUI version info:
This tool is written in Python and using pygame library as the image manipulator.
Sorry, there's no mouse button to click, use keyboard to input command.
Sometimes the open file popup window become out of focus,use ALT + TAB to reselect the window.
You can load image that is supported by pygame
(JPG,PNG,GIF(non animated,BMP,PCX,TGA (uncompressed),TIF,LBM (and PBM),PBM (and PGM, PPM),XPM
Image dimension
EEEPAD logo : 300x100, ASUS logo : 300x90, NVIDIA logo : 300x30
GUI version features:
Only for windows
Replace eeepad, asus, nvidia logo
Can load any version of bootloader (build 8.6.5.9 tested)
Extract image from bootloader
Save as blob
GUI version screenshot:
{
"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"
}
GUI version quick guide:
1. Load the bootloader
2. Load the image you want to change.
3. Save the bootloader, and test it via nvflash
4. Save the blob, flash to your device via dd
nvflash test command:
nvflash.exe --bct transformer.bct --setbct --configfile flash.cfg --bl patched_bl.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Click to expand...
Click to collapse
dd flash command:
dd if=blob of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
CMD line version info:
Requires python, python-imaging (PIL).
The script flow is nearly same as the GUI version except it use PIL to load/convert image.
Please browse the source code to get better understanding
CMD line version features:
Platform independent
Replace eeepad, asus, nvidia logo
Can load any version of bootloader (build 8.6.5.9 tested)
Save as blob
CMD line version guide:
Bootsplash patcher for ASUS Transformer TF101 (v1.0 | python | cmd line)
Usage: cmd_patcher.py -b bootloader.bin -e eeepad.bmp -a asus.bmp -n nvidia.bmp
Options:
-h, --help show this help message and exit
-b bootloader.bin Bootloader file
-e eeepad.bmp EEEPAD logo replacement
-a asus.bmp ASUS logo replacement
-n nvidia.bmp NVIDIA logo replacement
-o patched_bl.bin Patched bootloader file (Optional)
-f custom_blob Patched BLOB file (Optional)
Click to expand...
Click to collapse
UPDATE:
Python command line tool is now available.
Disclaimer:
This tool is intended for advanced user/themer. USE AT YOUR OWN RISK!!
REMEMBER : There's always a chance for a messed up bootloader.Please test the bootloader before proceeding to flash the blob.
I'm not liable for any problem arising such as bricked,loosed data..etc.
Click to expand...
Click to collapse
Download:
Get it from here
I'll try it this weekend. thanks for your work.
Moving to Themes & Apps.
I might get the "IRON FIST" but this works great. Thanks for your work.
I have a question I downloaded the Revolution HD 2.2 rom for the TF, then extracted the kernelblob and amended the splash images using this software then used the save command and it created the file named 'blob' , my question is how do i flash it back do i use adb ?
I will appriciate any help
4.0.3
Does anyone know if this will work on ICS?
I tried this with Prime 2.1.1 (HC ROM) and the tool says it's the wrong bootloader (I chose the blob file at the root of the ROM .zip file).
Isn't there anything easier than this to flash a new splash screen? Any help please?
First of all, but not less important...
I'm not responsible for anything that happens with your phone, also, some people experienced some bricks on certain devices, so, just take care where you put paths and data because your phone maybe vulnerable to bricks!
This audio modding guide is intended for experienced users. Mainly, in the Linux handling area, like customizing the kernel and playing with system internal parameters. Please don't play with this, you could overheat and/or damage your smartphone's motherboard if you mess with this menu options.
Requirements:
A rooted LG device.
Stock ROM (includes customized or modded stock)
Universal Init.d
BusyBox
And remember, the curiosity killed the cat, don't be a cat.
System requirements:
Any LG device running ICS (or higher) stock ROM.
Procedure:
First part: setting up the environment
1. Open "Play Store", search for "BusyBox Free" (or open the play store link written above).
{
"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"
}
2. Tap the first result and install it, then open.
3. Now, install BusyBox binaries in your device. Just tap "Install".
4. All done. If you see this, close the app.
5. Now, get back to "Play Store" and search for "Universal Init.d" (or open the play store link written above). Tap the first result.
6. Install it.
7. Open it.
8. Here, move the switch from "Off" to "On".
9. Close the app. The environment set up is done.
Second part: testing device's hardware limits
1. Go to the phone's launcher and tap "Phone".
2. Dial 3845#*<your model's numeric part>#. Mine's LG Optimus L9 (Argentina version), it's model number is P778G, in that case, I should dial 3845#*778#.
3. You'll now see the "Hidden Menu" window. There tap "H/W Device Test".
4. Now pick "Sound Test".
5. Tap "Audio CAL Tool".
6. Pick "SetGain".
7. Tap in the list menu next to "Device Type" and pick "headset".
8. Here, you'll see that there's an item called "HS_DL" and next to it a box where you can type a value. This value should be from 0 to 21. This is you headphone output's gain. Mine's default is 13. The maximum for me is 16, it starts crackling if higher. I suggest you to set it to 16.
9. After setting the value, tap "Ok".
10. Exit the menu.
11. Now, to test your new setting, unplug (if plugged) and plug your headphones again.
Third part: sticking your changes
By default, your device will reset everything as it was before with every reboot. What we gotta do to save those changes? We'll save the files you change when you tap "Ok" to another folder and then retrieve it every time the device boots. How? Here you'll see that:
1. Unplug the USB Cable (if plugged), go to Settings > Developer options and enable "USB Debugging".
2. Plug you device to a computer which has ADB (Android Debugging Bridge) installed. (will work on both Windows and Linux) Don't you know if you have it? Type "adb" at the command line, or "sudo adb" (sudo, just in case) in a Linux Terminal. If you see something similar to the next screenshot, you're okay.
3. Open up a command prompt (or Terminal, in Linux). Type:
Code:
adb shell su -c "cp '/data/audio/gain.table.0 /data/local/'"
4. Open a text editor and create a new file. In Linux, use whatever you like to (includes command line and GUI). In Windows, use Notepad++.
4.1 Only if using Windows:
Right click the bar at the bottom saying "Windows (CR LF)" and pick "Convert to UNIX format".
5. Type (or copy-paste) the next code:
Code:
cp -f /data/local/gain.table.0 /data/audio/
chmod 600 /data/audio/gain.table.0
6. Save the file as 02setaudiogain somewhere in your PC.
7. Go to the folder you saved the file in your PC and then, type those commands:
Code:
adb push 02setaudiogain /sdcard/
adb shell su -c 'mount -o remount,rw /system'
adb shell su -c 'cp /sdcard/02setaudiogain /system/etc/init.d/'
adb shell su -c 'chmod 755 /system/etc/init.d/02setaudiogain'
adb shell su -c 'mount -o remount,ro /system'
8. All done, reboot your device to test . Liked the commands part? Reboot it with this command if you don't like the UI anymore:
Code:
adb shell su -c 'reboot'
Fourth part: troubleshooting
Can't install BusyBox or turn on Universal Init.d?
Check for permission denials at SuperSu's (or your root permission management app) logs.
Device not booting anymore?
Restore a backup over recovery or use LG Mobile Support tool (included in LG PCSuite) to re-flash your device.
Fifth part: how it works
As stated by the logs I took from logcat, what you do when you tap "Ok" in the "Audio CAL Tool" is save some fields to a file called gain.table.0 in /data/audio (/data/audio/gain.table.0)
logcat:
Changes it makes:
Credits:
To @pauliero 's post for the hidden menu code: http://forum.xda-developers.com/showthread.php?t=2126949
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for Realme Mediatek devices only . DON'T DO ANY OF THESE IF YOU HAVE SOMETHING ELSE!
ALWAYS USE DOWNLOAD ONLY MODE OF SP FLASH TOOL.
DON'T TOUCH ANYTHING RELATED TO FORMAT ON SP FLASH TOOL! (IT'S WRITTEN EVERYWHERE, YOU WILL LOSE YOUR IMEIS IF YOU USE FORMAT ALL + DOWNLOAD. YOU ARE SAFE IF YOU USE DOWNLOAD ONLY.)
Windows Method
Requirements:
Device Firmware (Download as per your device model)
Bypass Tools Pack
SP Flash Tool
Install Python from Windows Store
libusb-win32 - Having Issues? Use this.
Get usbdk installer (.msi) from here and install it
MAKING YOUR FIRMWARE READY:
1) Clone this repository : oppo_decrypt
Code:
git clone https://github.com/bkerler/oppo_decrypt
or download the repo zip and extract it
2) Extract the downloaded firmware and move the ofp file to the oppo_decrypt folder
3) In the oppo_decrypt folder open cmd and type these:
Code:
pip3 install -r requirements.txt
(Make sure you have python and pip installed)
4) All the requirements are installed, now it's time to decrypt the ofp:
Code:
python3 ofp_mtk_decrypt.py name_of_file.ofp out
(Replace the ofp name with your actual ofp name)
5) After the decryption now its time to merge superimages (THIS IS ONLY FOR DEVICES WITH DYNAMIC PARTITIONS, IGNORE THIS STEP FOR NON-DYNAMIC DEVICES)
- Install ubuntu from wsl : Guide for that
- Run ubuntu and install simg2img
Code:
sudo apt install simg2img
- Go to the path of your extracted ofp
e.g.
Code:
cd /mnt/d/oppo_decrypt/out
(go to the path of your out folder)
- Check the supermap.csv file
Code:
nano supermap.csv
- check your region and note the superimages names
- Now to merge them :
Code:
simg2img super.0.xxxx.img super.1.xxxx.img super.2.xxxx.img super.img
(Replace the xxxx with the super images' names from your region.)
- After this you will get a Super.img in that out folder
- Now go to scatter file in out folder and edit it (Search Super.img in that and change is_download=false to true)
FLASHING THE FIRMWARE:
1) Extract the bypass zip
2) Go to driver folder, find the .inf file right click and press install.
{
"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"
}
3)Download this file and install it, after installing power off phone and connect to pc while holding Vol+- (don't leave the buttons after connecting) . You might need this driver as well if it's not detected.
Press next, connect your device to PC while holding Vol+- buttons (your device needs to be powered off, and don't leave the buttons) and you will see the mtkdriver down below. Install it.
Choose MediaTek USB Port and install it.
4)Then run the brom.bat under Bypass folder.
5) Now power off the phone and connect the phone while holding volume + and - (Don't leave the buttons until the bypass is done)
6)After the above step Go into Flash Tool folder and open the SPFlash tool go to Options>Option
Click on Connections and select UART and set Baud Rate to 921600
7) after that choose scatter file and also if not set, set your download-agent. You don't need to select auth file as authorization is disabled. Once you do it, it should look like this. ALWAYS MAKE SURE DOWNLOAD ONLY MODE IS SELECTED! DON'T SELECT OTHER MODES!
Make SURE "Download Only" is selected. Don't select ANYTHING ELSE! You will lose your IMEIs, Serial Numbers, Capability of Hardware Attestation etc. if you choose "Format data + Download" make SURE you selected "Download Only".
8) Uncheck oplusreserve2 first. Now, you can start downloading with the button and after that a checkmark will appear. You can reboot your phone and use it like before now! All your userdata will (inevitably) be cleared!
After flashing it should look like this. Download has been complete. Enjoy!
Notes :
After this phone might not boot due to encryption, you can do any of the below procedures to format your data and boot your phone
1. In case you can access recovery by holding volume and power button - Wipe all data from recovery and reboot
2. In case you cannot access recovery, power off phone then enter this command in mtkclient :
Code:
python mtk e metadata,userdata,md_udc
and connect phone while holding both volume buttons. After this just reboot phone
Also note that first boot takes some time, so don't panic leave it for few minutes it'll boot
Credits :
https://github.com/bkerler/ for decryptor and for creating the tool.
Good morning, @pritish1998. Thanks for the effort in producing this well-illustrated and in-depth writeup. Please note, however, that I am removing the reference to Telegram that was previously in your post.
Regarding social networking links, please observe that, as an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we only grant developers the privilege to share references to their social networks in their own development threads, and if thorough support is also provided in that thread. These conditions don't apply to this thread. Additional information is also available here:
Telegram Chat Channels - Way Forward
Thanks for your cooperation.