Related
Extracting ROM files from HTC RUU
Official HTC ROM updates are released as RUU (ROM Update Utility), which you run on your (Windows) PC to get the target device updated automatically.
Some of the big brains in the Android community release RUUs re-packaged into signed update files,
which in turn allow for whatever ROM customization you can imagine.
In this how to I will explain how to extract ROM files from a RUU image,
which you can then customize and use to flash your device without the fear of a new bootloader possibly making your device unrootable.
Requirements :
Windows PC,
Microsoft Process Monitor,
File Archiver capable of extracting ZIP files(eg, 7ZIP),
Official HTC RUU for your Android device.
The process of extracting ROM files from a RUU is really straightforward.
The idea behind it is that the self-contained update utility first needs to unpack the update payload into a temporary folder before pushing it onto the device.
This is when we grab the ROM file...
1. download the official RUU
2. start Process Monitor.
3. press CTRL+L
4. change "Architecture" to "Process Name"
5. leave the "is" field as it is
6. in the empty field copy and paste the name of your
RUU file (eg, RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe)
7. click "Add"
8. change "Process Name" to "Path"
9. change "is" to "Contains"
10. in the blank field type "rom.zip" (without quotes)
11. click add
Click "OK" to set the filter and then run the RUU file.
Once the utility starts switch back to Process Monitor and look for an entry in the "Path" column that ends with "\rom.zip".
Right click on that line and select "Jump to..."
this will open a Windows Explorer window in the folder which contains the zipped ROM files
Copy the "rom.zip" file to some other folder, outside of the temp RUU folder tree (eg, desktop)
Once copied, close Process Monitor and the RUU utility.
The copied "rom.zip" file contains the following files:
android-info.txt - list of CIDs this RUU will flash to,
boot.img - root file system image,
hboot (followed by a version string) - boot-loader update,
radio.img - radio driver update,
recovery.img - recovery partition image,
splash1_Hero_320x480.nb0 - boot loader splash image,
system_rel.img - system partition image,
userdata.img - data partition image.
You can now, among many other things, root the ROM
and then flash the updated boot.img and all the other image files on to your device using Recovery
it doesnt work... the process monitor colum is all blank after running RUU... there are no processes listed
munnibhai said:
it doesnt work... the process monitor colum is all blank after running RUU... there are no processes listed
Click to expand...
Click to collapse
you mst be doing something wrong i double checked the method and it still works fine for me..
make sure your environment is set up correctly and run everything as administrator or disadle uac in windows..
thanks for the reply, let me check it again...
i will post back to u
rom.zip corrupted
I followed the directions and like another post in here procmon shows a blank screen. I went to task manager and opened processes and saw when it ran then clicked open file location and found it. I did this twice and both zips are corrupt. (used winzip)
error [D:\android apps\EVO root\EVO\rom.zip]: start of central directory not found; Zip file corrupt.
Possible cause: file transfer error
when I close the RUU all the files in that folder disappear so you have to leave the RUU running while you copy the zip file or it's gone.
At least that's what I saw.
update to last post
I found a zip repair tool and was able to repair and extract the 1.10.653.2 RUU rom capture. I will have to try to run it later. If anyone gets corrupted zip error, Zip Repair pro will repair it.
To get the rom zip without any errors just run the ruu.exe file, when the box with a picture of a phone pops up, click start on pc, type in "run" and click on run then in that box that pops up, type in %temp% and click ok. Another window pops up then just scroll down to the most recent folder and rom.zip will be in there, if not it will be in the next folder.
Hi,
when I try to open the rom.zip I get an error message, it just said it cannot open with 7zip and with windows it says its invalid.
I tried downloading the RUU multiple times but still the same error. I rune the RUU as administrator.
Tried copying it over to different locations and then open it.
RUU_ENRC2B_U_JB_45_O2_UK_1.14.206.13_Radio_3.1204.167.31_release_289474_signed
HTC ONE X+
Thank you
Update:
I used Zip Repair Pro.. however there is no boot.img inside the repaired zip -_-
For those which have problem with making Process Monitor detect RUU temp folder, make sure You add whole file name of RUU including .exe at the end.
Jmcclue's steps, work perfectly, Thank you post #7
htc RUU Rom
Inside 4ndroid said:
Extracting ROM files from HTC RUU
Official HTC ROM updates are released as RUU (ROM Update Utility), which you run on your (Windows) PC to get the target device updated automatically.
Some of the big brains in the Android community release RUUs re-packaged into signed update files,
which in turn allow for whatever ROM customization you can imagine.
In this how to I will explain how to extract ROM files from a RUU image,
which you can then customize and use to flash your device without the fear of a new bootloader possibly making your device unrootable.
Requirements :
Windows PC,
Microsoft Process Monitor,
File Archiver capable of extracting ZIP files(eg, 7ZIP),
Official HTC RUU for your Android device.
The process of extracting ROM files from a RUU is really straightforward.
The idea behind it is that the self-contained update utility first needs to unpack the update payload into a temporary folder before pushing it onto the device.
This is when we grab the ROM file...
1. download the official RUU
2. start Process Monitor.
3. press CTRL+L
4. change "Architecture" to "Process Name"
5. leave the "is" field as it is
6. in the empty field copy and paste the name of your
RUU file (eg, RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe)
7. click "Add"
8. change "Process Name" to "Path"
9. change "is" to "Contains"
10. in the blank field type "rom.zip" (without quotes)
11. click add
Click "OK" to set the filter and then run the RUU file.
Once the utility starts switch back to Process Monitor and look for an entry in the "Path" column that ends with "\rom.zip".
Right click on that line and select "Jump to..."
this will open a Windows Explorer window in the folder which contains the zipped ROM files
Copy the "rom.zip" file to some other folder, outside of the temp RUU folder tree (eg, desktop)
Once copied, close Process Monitor and the RUU utility.
The copied "rom.zip" file contains the following files:
android-info.txt - list of CIDs this RUU will flash to,
boot.img - root file system image,
hboot (followed by a version string) - boot-loader update,
radio.img - radio driver update,
recovery.img - recovery partition image,
splash1_Hero_320x480.nb0 - boot loader splash image,
system_rel.img - system partition image,
userdata.img - data partition image.
You can now, among many other things, root the ROM
and then flash the updated boot.img and all the other image files on to your device using Recovery
Click to expand...
Click to collapse
this is good working 100% thank you :good:
i_4_u89 said:
this is good working 100% thank you :good:
Click to expand...
Click to collapse
no problem and please instead of saying thanks please remember to hit the thanks button on threads first post..
works great, to bad you cant open the zip file
jpwhre said:
works great, to bad you cant open the zip file
Click to expand...
Click to collapse
You can open the zip. Go back a page n try the way i said.
jmcclue said:
You can open the zip. Go back a page n try the way i said.
Click to expand...
Click to collapse
note path is desktop (last post showed from temp folder) and i still get same results. did some searching and aperantly htc now signs their zip files and they can't be opened anymore. having usb issues that causes fastboot force close errors and need to be able to flash boot.img thru flashify app to return it to stock. ran the htcguru reset rom that uses aroma installer to return to stock that lets me take ota's but i get qualcom location force close and other custom roms give me issues forcing me to reset phone to stock every few days with guru installer. flashing recovery in fastboot is a chore as well. I have s-off and can keep it, but doing fastboot oem lock wont relock the bootloader, even though it shows success in cmd line. i can cid and super cid with fastboot.
it leaves me at a point where i really need to pull everything out of the rom.zip file and it wont open.
pic 1, 7zip wont open archive on desktop
pic 2, how i get recovery to flash
pic 3, results from running RUU
i have to reboot device, set comand to reboot bootloader, set command to flash recovery all faster than phone will do all commands to get it to flash, and RUU doesnt work that fast. i know im on sprint with htc one m7, but google search "extract htc zip" "extract rom.zip" both lead to this thread as top result. no other searches will tell me how to open the archive, except one that resulted in "htc signed zips can no longer be opened"
you're more than welcome to give it a go
http://forum.xda-developers.com/showthread.php?t=2795856 Sprint_HTC_One_m7wls_5.05.651.2_RUU.exe
Did HTC change the way they create the exe? I don't find it, the biggest file is data1.cab file that I can't extract.
I'm trying to extract the stock rom for an ATT HTC One Mini (m4) because RUU keeps crashing on me and won't install. I am also rooted with S-off.
If anybody can help me get the stock m4 rom so I can go back to stock, I would really appreciate it.
SyPete said:
Did HTC change the way they create the exe? I don't find it, the biggest file is data1.cab file that I can't extract.
I'm trying to extract the stock rom for an ATT HTC One Mini (m4) because RUU keeps crashing on me and won't install. I am also rooted with S-off.
If anybody can help me get the stock m4 rom so I can go back to stock, I would really appreciate it.
Click to expand...
Click to collapse
No they didn't change it. Some ruu's use a different format requiring the use of a tool called unruu instead of trying to capture the zip file when using the exe (I just learned this today). I've gone ahead and used unruu and the resulting zips have been put in a single tar file. you can download it from here for about 30 days after which ill have to delete the file. also i dont know which zip has what in it.
hi
master how to open Zip firmware !!?
i want to open zip firmware (PM60IMG.zip Desire 400)with 7zip ! but shows below error :
"can not open file PM60IMG.zip az archive "
how to pass this encryption ?
gandolf007 said:
hi
master how to open Zip firmware !!?
i want to open zip firmware (PM60IMG.zip Desire 400)with 7zip ! but shows below error :
"can not open file PM60IMG.zip az archive "
how to pass this encryption ?
Click to expand...
Click to collapse
https://github.com/kmdm/ruuveal/tree/f4936338f19841c75edafbe7e622242105cb39aa
Root your LG G4S (Model H735)
Tested on Andriod 5.1.1.
Thanks goes to @konsolen for sharing the method to open up the port (see appendix in this post) and to @dominik-p for his guide to determine dd parameters (you won't need this to root with the method described, but you can back up your phone if you're worried). And most importantly, thanks to the author of SuperSU for his excellent script updater-binary which worked pretty much out of the box, with only a few workarounds needed (which is what the instructions below do).
First, a few general notes:
The supersu.zip included in this package is version 2.46.
SuperSU can be downloaded here: http://download.chainfire.eu/supersu
If you want to use a new version, just put the zip file in this directory and rename it to "supersu.zip" (delete the old one in this package first of course).
The busybox binary in this package was used successfully to unzip in the LG G4s H735 (Android 5.1.1).
Some time it should maybe be ensured that this is the newest version. Same holds for Send_Command.exe and adb.exe (and attached libraries).
This script uses the "update-binary" script of the SuperSU package to install it on your phone.
The scripts I attached prepare for it to be called (hopefully) successfully.
Instructions to root
Preparation
You MAY want to create a backup of your system beforehand, in case things go wrong.
This is optional, so if you don't want to do this, you may still rely on the .kdz file (see Appendix below) to restore your phone if things go wrong.
You need to calculate the dd parameters and then backup your system partition into a .img file.
There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Keep a copy of your system.img somewhere safe, you can use it to restore
your system if something goes wrong.
Enabling developer options and getting the tools
First, enable developer / debugging mode on your phone:
Navigate to Settings > About Phone > scroll to the bottom > tap Build number seven (7) times.
You'll get a short pop-up in the lower area of your display saying that you're now a developer.
Then, go back and now access the Developer options menu, check 'USB debugging' and click OK on the prompt.
Note: You have to enable USB debugging before plugging your device in to the computer. Unplug device then try to enable USB debugging.
On your computer, install Install and Use ADB (the Android Debug Bridge Utility). Also, download LG Flash Tool.
You can find out how to do both by searching google for it.
Step 1.
Connect your phone via USB (not in download mode yet, just normal).
Then, run Init_Root.bat in order to copy the essential files over to internal storage.
You may do this either by 1) double clicking the file, or 2) executing it from the windows command line.
For Option 2): Open a command line in the folder where you extracted this package. To do this, hold shift while right clicking in the folder opened in the Windows Explorer and select "Open command window here". Then, type
Init_Root.bat
Step 2.
Reboot your phone in download mode and ensure it has opened the port to send commands in download mode.
The port is open if it's displayed on the phone's screen in green letters, like
COMX
(with a number instead of X).
On my LG H735 it was necessary to use "LG Flash Tool 2014" http://lgflashtool.com/ to open the port. So if you don't have the green letters, see instruction pasted below (appendix) on how to open the port.
Step 3.
Open a command line in the folder where you extracted this package. To do this, hold shift while
right clicking in the folder opened in the Windows Explorer and select "Open command window here".
Open a command shell to your phone by typing (replace X with the number displayed on your phone) by typing:
Send_Command \\.\COMX
You should be set to root if the following works:
Typing "ls" returns a long list of file and folder names.
Typing "id" should give you someting like that:
uid=0(root) gid=0(root) context=u:r:recovery:s0
The important bits are the "(root)" uid and gid.
If any of the above is not the case, it will not work, you may search for help in the forum.
Step 4.
Execute the commands below (without the numbering of course).
1. mv /data/local/tmp/busybox /sbin/busybox
2. chmod 755 /sbin/busybox
3. mkdir /tmp
4. mkdir /tmp/supersu
5. /sbin/busybox unzip /data/local/tmp/supersu.zip -d /tmp/supersu
6. mv /data/local/tmp/supersu.zip /tmp/supersu/
7. sh /tmp/supersu/META-INF/com/google/android/update-binary dummy 1 /tmp/supersu/supersu.zip
(Note: Not all commands above may be needed, but this is the conservative approach)
Recommended:
Do sanity checks to see if it's doing its job as expected.
After command 2, type the command ls -l /sbin/busybox to check for sanity.
It must return a line like this (with your own date and time):
-rwxr-xr-x shell shell 1048328 <date> <time> busybox
Command 5 must print several lines containing "inflating" messages, similar to this:
Archive:
inflating: META-INF/MANIFEST.MF
...
Command 7 prints lines like this, and other status messages afterwards:
**************
SuperSU installer
**************
...
Step 5.
Your phone should now be rooted if it all worked ok.
You may now type
LEAVE
to reboot your phone.
Happy rooting!
Troubleshooting
If it doesn't work, for example you phone may be stuck on the boot process displaying the LG logo, then you can use Flash Tool to restore your phone. Use instructions below (how to boot the phone into download mode), but don't pull the USB cable, and just let it run its course. This should restore your phone.
If for some reason this hasn't worked, you may try to "dd" back your system .img which you may have created in the preparation step.
Appendix
How to boot the phone into download mode and open the port
a) Boot the LG G4s in download mode. To do this, first switch it off completely and disconnect USB cable. Then, hold the Volume Up button, and while you keep holding it, plug in the USB cable.
b) Start the LG Flash tool and load the .kdz for your phone. We won't actually complete the flashing, you only need it to start the process, but you should use the kdz for your phone nonetheless.
You can check for your kdz on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
c) Now this is very important: Watch your phone while the .kdz is being flashed by the flash tool.
(the flash tool may complain about error connecting to the update server, but you can ignore this with "ok").
As soon as the green letters show up, UNPLUG THE USB CABLE!
The percentage on your phone has to be 0% still (never mind about percentage in the flash tool, it may not even display it).
Then, kill the Flash Tool with the Windows Task Manager (Ctrl+alt+delete).
When it's closed, you can plug your phone back in.
It's now in download mode with open port.
You may also be interested in optimizing your storage & memory after you have rooted:
http://forum.xda-developers.com/general/general/moving-apps-to-sd-optimize-memory-phone-t3248125
LG-H731 Vigor from Videotron/Virgin Mobile
jen.magnolis said:
Root your LG G4S (Model H735)
Tested on Andriod 5.1.1.
Click to expand...
Click to collapse
Also work on phone listed in title:
LG-H731 (LG G4) Vigor from Videotron/Virgin Mobile
Happy rooting
If you need help, don't hesitate to contact me: [email protected] or here =
Hi
jen.magnolis said:
Root your LG G4S (Model H735)
Tested on Andriod 5.1.1.
Thanks goes to @konsolen for sharing the method to open up the port (see appendix in this post) and to @dominik-p for his guide to determine dd parameters (you won't need this to root with the method described, but you can back up your phone if you're worried). And most importantly, thanks to the author of SuperSU for his excellent script updater-binary which worked pretty much out of the box, with only a few workarounds needed (which is what the instructions below do).
First, a few general notes:
The supersu.zip included in this package is version 2.46.
SuperSU can be downloaded here: http://download.chainfire.eu/supersu
If you want to use a new version, just put the zip file in this directory and rename it to "supersu.zip" (delete the old one in this package first of course).
The busybox binary in this package was used successfully to unzip in the LG G4s H735 (Android 5.1.1).
Some time it should maybe be ensured that this is the newest version. Same holds for Send_Command.exe and adb.exe (and attached libraries).
This script uses the "update-binary" script of the SuperSU package to install it on your phone.
The scripts I attached prepare for it to be called (hopefully) successfully.
Instructions to root
Preparation
You MAY want to create a backup of your system beforehand, in case things go wrong.
This is optional, so if you don't want to do this, you may still rely on the .kdz file (see Appendix below) to restore your phone if things go wrong.
You need to calculate the dd parameters and then backup your system partition into a .img file.
There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Keep a copy of your system.img somewhere safe, you can use it to restore
your system if something goes wrong.
Step 1.
Connect your phone via USB (not in download mode yet, just normal).
Then, run Init_Root.bat in order to copy the essential files over to internal storage.
You may do this either by 1) double clicking the file, or 2) executing it from the windows command line.
For Option 2): Open a command line in the folder where you extracted this package. To do this, hold shift while right clicking in the folder opened in the Windows Explorer and select "Open command window here". Then, type
Init_Root.bat
Step 2.
Reboot your phone in download mode and ensure it has opened the port to send commands in download mode.
The port is open if it's displayed on the phone's screen in green letters, like
COMX
(with a number instead of X).
On my LG H735 it was necessary to use "LG Flash Tool 2014" http://lgflashtool.com/ to open the port. So if you don't have the green letters, see instruction pasted below (appendix) on how to open the port.
Step 3.
Open a command line in the folder where you extracted this package. To do this, hold shift while
right clicking in the folder opened in the Windows Explorer and select "Open command window here".
Open a command shell to your phone by typing (replace X with the number displayed on your phone) by typing:
Send_Command \\.\COMX
You should be set to root if the following works:
Typing "ls" returns a long list of file and folder names.
Typing "id" should give you someting like that:
uid=0(root) gid=0(root) context=u:r:recovery:s0
The important bits are the "(root)" uid and gid.
If any of the above is not the case, it will not work, you may search for help in the forum.
Step 4.
Now you have two options:
#Step 4, Option 1 (recommended to try)
Just run the script and you should be done.
Type:
sh root_lgh735.sh
The script contains all commands I (and other people) used to successfully root the phone.
However we have all used option (2) below, so the script itself has not been tested yet,
though it's very simple (feel free to open it with a text editor to look at it).
You can try to run it, and if it's not doing what's expected you can still go to Option 2
and fix things up.
It will have worked if:
It prints several lines containing "inflating" messages, similar to this:
Archive:
inflating: META-INF/MANIFEST.MF
...
It prints 3 lines like this, and other status messages afterwards:
**************
SuperSU installer
**************
....
If it has done that, reboot your phone and you should be set.
If not, do the commands manually as in Option 2.
Please: If the script worked for you, report it in this thread, so I can simplify these instructions here! Thanks for your help :cyclops:
#Step 4, Option 2:
Execute the commands directly (proven to work on several phones).
Type the commands below (without the numbering of course).
1. mv /data/local/tmp/busybox /sbin/busybox
2. chmod 755 /sbin/busybox
3. mkdir /tmp
4. mkdir /tmp/supersu
5. /sbin/busybox unzip /data/local/tmp/supersu.zip -d /tmp/supersu
6. mv /data/local/tmp/supersu.zip /tmp/supersu/
7. sh /tmp/supersu/META-INF/com/google/android/update-binary dummy 1 /tmp/supersu/supersu.zip
(Note: Not all commands above may be needed, but this is the conservative approach)
Recommended:
Do sanity checks to see if it's doing its job as expected.
After command 2, type the command ls -l /sbin/busybox to check for sanity.
It must return a line like this (with your own date and time):
-rwxr-xr-x shell shell 1048328 <date> <time> busybox
Command 5 must print several lines containing "inflating" messages, similar to this:
Archive:
inflating: META-INF/MANIFEST.MF
...
Command 7 prints lines like this, and other status messages afterwards:
**************
SuperSU installer
**************
...
Step 5.
Your phone should now be rooted if it all worked ok.
You may now type
LEAVE
to reboot your phone.
Happy rooting!
Troubleshooting
If it doesn't work, for example you phone may be stuck on the boot process displaying the LG logo, then you can use Flash Tool to restore your phone. Use instructions below (how to boot the phone into download mode), but don't pull the USB cable, and just let it run its course. This should restore your phone.
If for some reason this hasn't worked, you may try to "dd" back your system .img which you may have created in the preparation step.
Appendix
How to boot the phone into download mode and open the port
a) Boot the LG G4s in download mode. To do this, first switch it off completely and disconnect USB cable. Then, hold the Volume Up button, and while you keep holding it, plug in the USB cable.
b) Start the LG Flash tool and load the .kdz for your phone. We won't actually complete the flashing, you only need it to start the process, but you should use the kdz for your phone nonetheless.
You can check for your kdz on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
c) Now this is very important: Watch your phone while the .kdz is being flashed by the flash tool.
(the flash tool may complain about error connecting to the update server, but you can ignore this with "ok").
As soon as the green letters show up, UNPLUG THE USB CABLE!
The percentage on your phone has to be 0% still (never mind about percentage in the flash tool, it may not even display it).
Then, kill the Flash Tool with the Windows Task Manager (Ctrl+alt+delete).
When it's closed, you can plug your phone back in.
It's now in download mode with open port.
Click to expand...
Click to collapse
Have twpr or cwm recovery to install xposed??
I can confirm is working on LG G4 LG-H735P (Latin America version), thanks!
anyone tried updating? just got a system update notification from my phone lol dk if i should update now or not
Good question! I didn't try it yet. Think it should be ok, but if it isn't, you can just root again I guess
jen.magnolis said:
Good question! I didn't try it yet. Think it should be ok, but if it isn't, you can just root again I guess
Click to expand...
Click to collapse
oh.. it wont like brick or anything? :/
dclarkg said:
I can confirm is working on LG G4 LG-H735P (Latin America version), thanks!
Click to expand...
Click to collapse
I could not root my phone, what kdz file did you use??
Backup problems
Hello,
Coming from a Nexus 4, I bought a G4S last month.
I want to do my first root in order to manage the storage, like jen.magnolis talked about.
In case of a problem (bootloop or brick), I need to be able to restore. I don't really mind about restoring my datas, a factory reset would be enough.
But I don't undestand how i can get the system.img without being rooted ? It seems that I can get a "backup.ab" file using adb. Will it be enough to restore in case of brick ?
I also looked about kdz files, but mine doesn't seem to be available. I have a LGH735 (buyer = FRA, suffix = AFRATS, ...). Will it work if I use the one you provided in your post ?
Thanks for your help !
dclarkg said:
I can confirm is working on LG G4 LG-H735P (Latin America version), thanks!
Click to expand...
Click to collapse
I got the same model phone, but I can't find the .KDZ file for it anywhere. Could you post a link to the one you used please?
Excellent step-by-step guide. Should set an example for other "step-by-step guides" which exclude crucial information ("everybody knows lösfhgaeilurhg has to by typed between these steps here, I shall not mention it" )
Thanks a ton Worked on my LG G4S a.k.a H735 like a charm.
Cheers!
dreamnoob said:
anyone tried updating? just got a system update notification from my phone lol dk if i should update now or not
Click to expand...
Click to collapse
jen.magnolis said:
Good question! I didn't try it yet. Think it should be ok, but if it isn't, you can just root again I guess
Click to expand...
Click to collapse
"phone appears to be rooted, will not be updated" - Hiding root did not help, any simple suggestions but total unrooting?
Wanted to upgrade from 10c to 10d...
Cheers!
Doubts.
Hi everyone!
I just cant find my .kdz file! The phone i want to root its a G4 H735AR, im wondering if there are some compatible .kdz that i can use. Im affraid it might get bricked or something...
BTW i¨ve tried the rootworm.bat method and it didnt work. And when i try to open the COMX port, the lg flash tool always crushes and shuts down.
Works!
ascfzz said:
Hi everyone!
I just cant find my .kdz file! The phone i want to root its a G4 H735AR, im wondering if there are some compatible .kdz that i can use. Im affraid it might get bricked or something...
BTW i¨ve tried the rootworm.bat method and it didnt work. And when i try to open the COMX port, the lg flash tool always crushes and shuts down.
Click to expand...
Click to collapse
So, i made it! It works in the H735AR!! The problem with the flash tool was that i was trying to use it without any KDZ file!! I've used @konsolen .kdz and achieved to open ports, and then continue with the rest of the tutorial without trouble.
Thank you so much! Its a great phone, but with so little internal memory is a waste.
chw9999 said:
"phone appears to be rooted, will not be updated" - Hiding root did not help, any simple suggestions but total unrooting?
Wanted to upgrade from 10c to 10d...
Cheers!
Click to expand...
Click to collapse
ya u just update thru lg bridge.. once updated it will be unroot tho so u have to root it back same method as u did before.. and if you use link2sd it dosent matter after root ur link2sd can just reboot and re-read ur partition without needing to wipe and re-partition
It's working in H736P! Thank you só much!
Enviado de meu LG-H736 usando Tapatalk
For people in Brazil that has H736P, to open ports, is necessary the kdz file to use in LG Flash Tool.
Galera do Brasil, consegui rootear o LG G4 Beat usando esse tutorial porém tive que baixar o arquivo kdz pro H736P pra executar o LG Flash Tool. Cuidado ao usar o LG Flash Tool, assim que aparecer a porta COM na tela do telefone, arranca o cabo USB do computador.
Enviado de meu LG-H736 usando Tapatalk
friend you are from argentina?¿
maxiret said:
friend you are from argentina?¿
Click to expand...
Click to collapse
Brasil.
Enviado de meu LG-H736 usando Tapatalk
Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
Code:
adb devices
iii) now use the command
Code:
adb reboot-bootloader
In fastboot use this command to unlock bootloader
Code:
fastboot oem unlock
Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Code:
expdb
nvdata
nvram
proinfo
protect1
protect2
secro
8) Copy these files in some place where it is safe ( I have copied it to Internal Storage in a folder named PartitionsBackup)..
9) Next, go back to root folder again, and open data/nvram/md/NVRAM/NVD_IMEI and copy the MP0B_001 file to internal storage. Do Not copy this file in the same place as the previous files, but remember where you have copied this file.
These are all the partitions that store the device's IMEI .
10) After copying everything mentioned, Reboot to recovery and flash the desired Custom Rom.
11) Make sure the rom is rooted, and again install FX File Explorer from play store, enable root access as above.
Do Not Forget To Backup Everything Before Doing Anything!
12) Now select the files that you have copied in internal storage (Assuming PartitionsBackup). And copy those files. ( Note: Do Not Copy the MP0B_001 file!)
13) Now open root folder, go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder and paste all the files you have copied, and if asked select Merge/Overwrite files.
14) Reboot.
15) Now go back to internal storage, copy the MP0B_001 file where you have saved it. Go back to root folder and open data/nvram/md/NVRAM/NVD_IMEI and copy the file, select Merge/Overwrite. Now long press the file and select Security, update permissions as Read, Write for both root and radio. Dis-select everything else.
16) Reboot aand Done! Voila ! You should get back the IMEI for your device :victory:
I know its a long post, but it works for Custom ROMs.!
Hope it helps!
Hit Thanks If you feel it works! :highfive:
can you please help me on step 13 because every time i reboot the device the by-name folder contents reset to the original value. my by-name folder backup is 72 mb while when i look in the folder after i reboot it is only 170 bytes
---------- Post added at 06:12 AM ---------- Previous post was at 06:07 AM ----------
also when i wait for a while after rebooting for like 4-6 hours when i looked at my baseband and imei it is not unknown anymore
and my sim is restored but when i reboot again the baseband value and imei is set back to unknown. this happened even before im not following your solution. can it be a hardware issue? would really appreciate any help thx
Cyteezy said:
can you please help me on step 13 because every time i reboot the device the by-name folder contents reset to the original value. my by-name folder backup is 72 mb while when i look in the folder after i reboot it is only 170 bytes
---------- Post added at 06:12 AM ---------- Previous post was at 06:07 AM ----------
also when i wait for a while after rebooting for like 4-6 hours when i looked at my baseband and imei it is not unknown anymore
and my sim is restored but when i reboot again the baseband value and imei is set back to unknown. this happened even before im not following your solution. can it be a hardware issue? would really appreciate any help thx
Click to expand...
Click to collapse
I didn't get you. Do not backup the whole by-name folder. Just copy the files mentioned above. And when you go into the custom ROM, just restore the files copied in the same by-name folder.
No. It might not be a hardware problem.
PraneethMv said:
Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
Code:
adb devices
iii) now use the command
Code:
adb reboot-bootloader
In fastboot use this command to unlock bootloader
Code:
fastboot oem unlock
Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Code:
expdb
nvdata
nvram
proinfo
protect1
protect2
secro
8) Copy these files in some place where it is safe ( I have copied it to Internal Storage in a folder named PartitionsBackup)..
9) Next, go back to root folder again, and open data/nvram/md/NVRAM/NVD_IMEI and copy the MP0B_001 file to internal storage. Do Not copy this file in the same place as the previous files, but remember where you have copied this file.
These are all the partitions that store the device's IMEI .
10) After copying everything mentioned, Reboot to recovery and flash the desired Custom Rom.
11) Make sure the rom is rooted, and again install FX File Explorer from play store, enable root access as above.
Do Not Forget To Backup Everything Before Doing Anything!
12) Now select the files that you have copied in internal storage (Assuming PartitionsBackup). And copy those files. ( Note: Do Not Copy the MP0B_001 file!)
13) Now open root folder, go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder and paste all the files you have copied, and if asked select Merge/Overwrite files.
14) Reboot.
15) Now go back to internal storage, copy the MP0B_001 file where you have saved it. Go back to root folder and open data/nvram/md/NVRAM/NVD_IMEI and copy the file, select Merge/Overwrite. Now long press the file and select Security, update permissions as Read, Write for both root and radio. Dis-select everything else.
16) Reboot aand Done! Voila ! You should get back the IMEI for your device :victory:
I know its a long post, but it works for Custom ROMs.!
Hope it helps!
Hit Thanks If you feel it works! :highfive:
Click to expand...
Click to collapse
Can anyone help me in restoring IMEI in stock ROM?
While flashing using SN writer or maui meta tool it says "Have been in meta mode. Long press power button to normal reboot". After that nothing. It boots back and I still see the INVALID IMEI message.
MisledMew said:
Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
iii) now use the command
In fastboot use this command to unlock bootloader Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Can anyone help me in restoring IMEI in stock ROM?
While flashing using SN writer or maui meta tool it says "Have been in meta mode. Long press power button to normal reboot". After that nothing. It boots back and I still see the INVALID IMEI message.
Click to expand...
Click to collapse
SN write tool can be a little complicated to do. I personally prefer Maui Meta 3G. You can search for guides on SN write tool. There are many....
Facing problem with maui meta 3g
On my mobile it shows its in "Have been in meta mode. Long press power button to normal reboot".
it won't work ahead .... some error like kernel checksum and no permission grant type.. rather i installed drivers of mediatek its not working...
plz help out
Ni$hant said:
On my mobile it shows its in "Have been in meta mode. Long press power button to normal reboot".
it won't work ahead .... some error like kernel checksum and no permission grant type.. rather i installed drivers of mediatek its not working...
plz help out
Click to expand...
Click to collapse
Do you have all drivers installed correctly? ADB, VCOM, USB Drivers?
Also, That message screen is Meta Mode. From that screen only you can do the IMEI process.
Note: This Only works for stock rom. Use this guide.
https://forum.hovatek.com/thread-12328.html
For custom Roms, use my guide.
Device: Lenovo A2016a40 (MY6735M) also known as Lenovo vibe b
Android Version - 6.0 Marshmallow
I can't find any folder named 'nvram' on 'data' directory of root folder
Hey guys, so I have been trying to root and install a custom ROM on my MetrobyTmobile Moto G7 power (XT1955-2 Ocean) Pie 9.0 and the latest updates have been installed.
So i finally figured out how to unlock the bootloader with help from Motorola's unlocking website and unusually long string of numbers and letters to enter into their website. Pho ne is unlocked. I had downloaded the latest versions off all these including:
-TWRP 3.3.1-ocean.img
-Copy AB partiotion file zip
-Open_gapps-x86_64-9.0-stock-20200612
-RR-P-v7.0.2-20191103-ocean-Unofficial-signed
-XT1955-5_OCEAN_TMO_9.0_PCOS29.114-134-14_cid21_subsidy-MPCS_RSU_QCOM_regulatory-DEFAULT_CFC.xml
-ADB minimal 1.4.3
(I also made a backup with the Lenovo rescue and smart assistant
I've tried following directions on several write ups of certain custom ROM installs but when i get to CMD line (DOS) I can kind of get ADB to pull up menus, but I can't get any further. I cant find any detailed step by step with info like where do the downloaded folders of the above programs and Rom's go while still in Windows 10. Nor I can find exact write up of what to type in the CMD line (i am not a coder or went to school for any computer programing.
So I have all the unzipped folders above moved into my C:\ drive with the other main o.s. system folders such as Windows, Program files(x86), Programdata, Users, Perflogs.
Please, anyone who can get me pointed in the right direction, especially with the A+B Partitions and how to type this all into the Command Line, I will be very appreciative. Using cracked apks and MicroG and such just isn't how I want to be using my phones potential with.
This is my first time posting here, I usually am on auto mechanic forums so let me know I i missed something or said to much bla bla. LOL
Thanks!
DerekLindvall said:
Hey guys, so I have been trying to root and install a custom ROM on my MetrobyTmobile Moto G7 power (XT1955-2 Ocean) Pie 9.0 and the latest updates have been installed.
So i finally figured out how to unlock the bootloader with help from Motorola's unlocking website and unusually long string of numbers and letters to enter into their website. Pho ne is unlocked. I had downloaded the latest versions off all these including:
-TWRP 3.3.1-ocean.img
-Copy AB partiotion file zip
-Open_gapps-x86_64-9.0-stock-20200612
-RR-P-v7.0.2-20191103-ocean-Unofficial-signed
-XT1955-5_OCEAN_TMO_9.0_PCOS29.114-134-14_cid21_subsidy-MPCS_RSU_QCOM_regulatory-DEFAULT_CFC.xml
-ADB minimal 1.4.3
(I also made a backup with the Lenovo rescue and smart assistant
I've tried following directions on several write ups of certain custom ROM installs but when i get to CMD line (DOS) I can kind of get ADB to pull up menus, but I can't get any further. I cant find any detailed step by step with info like where do the downloaded folders of the above programs and Rom's go while still in Windows 10. Nor I can find exact write up of what to type in the CMD line (i am not a coder or went to school for any computer programing.
So I have all the unzipped folders above moved into my C:\ drive with the other main o.s. system folders such as Windows, Program files(x86), Programdata, Users, Perflogs.
Please, anyone who can get me pointed in the right direction, especially with the A+B Partitions and how to type this all into the Command Line, I will be very appreciative. Using cracked apks and MicroG and such just isn't how I want to be using my phones potential with.
This is my first time posting here, I usually am on auto mechanic forums so let me know I i missed something or said to much bla bla. LOL
Thanks!
Click to expand...
Click to collapse
To make things easy in windows 10 make sure the driver thing is off first.Then make sure you install adb program to the root of your c drive.Then make sure your a b partion zip is in the adb folder.Then go to computer on ur menue to c drive open up adb folder inside the folder u should see a comand prompt icon or go to search typ cmd and it will bring up windo with c:/adb prompt somi liky that then typ fastboot device it should bring up some numbers.And make sure I have USB debug turned on in phone and have phone in bootloader mode by holding power and volume buttons till a screen comes up use volume bootons to scroll throy to u see restart bootloader .then typ fastboot devices again should get some numbers.now if u got the a b partion zip in your adb folder typ fastboot flash a b partion zip .I renamed mine to shorter name like adpart.zip.on Soo machines u need to just typ abpart then it goes sometimes u have to put the .zip after the abpart then should go.google on how to flash the A B partion zip and also get ur twrp IMG in ur adb folder if things go right the partion zip should flashed with no eorrs then typ fastboot boot recovy or what u saved name is then phone boot up to twrp.to make it easier before u get this far u can put in ext sdcard and u can put ur rom of choice on it .u can I stall twrp but sometimes they touch won't work but I can always boot into twrp from the adb comands.i tryed to make it simple but Google all this before doing anything more and get the comands saved in note pad then u can copy and paste.i try to find the link that details all of of this .there is an tellagram group that might b helpful I use them and here to get mine done
roadkill42 said:
To make things easy in windows 10 make sure the driver thing is off first.Then make sure you install adb program to the root of your c drive.Then make sure your a b partion zip is in the adb folder.Then go to computer on ur menue to c drive open up adb folder inside the folder u should see a comand prompt icon or go to search typ cmd and it will bring up windo with c:/adb prompt somi liky that then typ fastboot device it should bring up some numbers.And make sure I have USB debug turned on in phone and have phone in bootloader mode by holding power and volume buttons till a screen comes up use volume bootons to scroll throy to u see restart bootloader .then typ fastboot devices again should get some numbers.now if u got the a b partion zip in your adb folder typ fastboot flash a b partion zip .I renamed mine to shorter name like adpart.zip.on Soo machines u need to just typ abpart then it goes sometimes u have to put the .zip after the abpart then should go.google on how to flash the A B partion zip and also get ur twrp IMG in ur adb folder if things go right the partion zip should flashed with no eorrs then typ fastboot boot recovy or what u saved name is then phone boot up to twrp.to make it easier before u get this far u can put in ext sdcard and u can put ur rom of choice on it .u can I stall twrp but sometimes they touch won't work but I can always boot into twrp from the adb comands.i tryed to make it simple but Google all this before doing anything more and get the comands saved in note pad then u can copy and paste.i try to find the link that details all of of this .there is an tellagram group that might b helpful I use them and here to get mine done
Click to expand...
Click to collapse
You should use paragraphs or anything like that!
WoKoschekk said:
You should use paragraphs or anything like that!
Click to expand...
Click to collapse
Sorry I'm looking for the format that I did
Adb fastboot was a big problem. Use newest platform tools instead. World of difference with them commands...
1. To extract the image collection from your downloaded rom :
Download Payload Dumper from here (It's a zip file but it's not flashable) to your computer
Extract the zip file to a folder, make it a folder you can use regularly because this is the default tool you would use from now on
Download the rom version you want to root
Unzip the rom to a folder, you will find a file within it called payload.bin
Copy and paste that file into the "payload_input" folder within the Payload Dumper folder you created
Execute the payload_dumper.exe file within Payload Dumper folder, you will not have to specify any options as it always extracts from any payload.bin file in payload_input and outputs the image files to payload_output.
Leave the extraction to be completed, the program will automatically close itself once it's completed
Your extracted .img files will be shown within the payload_output folder
2. If you need to root the boot image you extracted :
Copy the boot.img file from the payload_output folder to a folder on your phone storage (Best to name it appropriately if you will be doing this regularly)
Download and Install the latest Magisk apk from the release site (Accept any prompt to allow install from external source)
Launch the app and then choose Install under the top "Magisk" section
Choose Select and Patch a File then browse to where you copied the boot.img on your storage
Magisk will then apply root to the boot image you specified, Your rooted image file will be output to your phone's Download folder : /sdcard/Download
You don't need to keep the default filename of the rooted image file so you can rename it appropriately for the rom version after you copy it to your computer, just ensure to keep the .img file extension
If you rename the rooted boot image, try not to use spaces in the filename, rather use _ or - as spaces make it more difficult to use in a command window although when you start typing the filename you can use TAB to autocomplete it, always ensure the filename shows .img as the extension and at the end of any commandline
3. If you need to use your rooted boot image to apply root to your phone :
Install the drivers from the mounted drive you should get when connecting the phone to your computer
On Windows you should then have a folder in C:\Program Files (x86)\OnePlus USB Drivers\Android with the platform tools (ADB.exe and Fastboot.exe) you will need, you can obviously copy the content from that folder somewhere else if you wish.
Connect your phone to your computer
Copy your rooted boot image to the folder that has adb.exe and fastboot.exe
Open a command window on your computer by right clicking in that folder and choosing Open command window here
In the command window, Type or copy/paste the command ADB devices and press enter
If you see a prompt on your phone to allow the computer connection then accept it, better still, tell it to allow from now on also.
You should see a string of characters shown in the command window, if you don't see that, then try another cable or re-install your drivers and reboot the computer.
Reboot your phone into Fastboot either by using ADB on your computer ( ADB Reboot Fastboot ) or by enabling Advanced reboot in your developer options in settings and then hold down the power button and use the 3 dot menu on the top right and choosing "Bootloader"
In the command window type Fastboot Boot <filename.img> i.e. Fastboot Boot rooted_boot.img and press enter
You should see a couple of lines in the command window telling you it's copying over to the phone, don't worry it's not being flashed or replacing your existing installed boot image
The phone should then restart and boot using the image from your computer, it will be a slightly slower boot than usual, your existing unlock method should still work
Launch the Magisk app, it should already have root access because the boot image you've used is already rooted
Go to Install under the top Magisk section
Choose Direct Install (Recommended)
Magisk will then apply root access to the boot image on the actual phone
You will be prompted to reboot the phone on the bottom right, do this to complete the process
You don't need the phone connected to your computer anymore as the installed boot image on the phone should now have root access
You can check for root either using any app which requires root or by using an app like Root Checker
Remember to empty the contents of payload_input and payload_output once you have finished, leaving them ready for any future rom versions
4. To retain root access after ROM/OTA update :
Install the update either from Oxygen Updater or from Settings > System > System updates
DO NOT REBOOT when prompted
Go to the Magisk app
Go to Install under the top Magisk section
Choose Install to Inactive Slot (After OTA)
Magisk will apply root to the newly installed boot image for the next version
Reboot when prompted by the Magisk app
The phone should reboot into the updated version with root already applied
Very nice write up! Hopefully many will read this and follow instructions. Too many threads being created with issues because they never bother to read.
Quick question as this is my first OnePlus device.
Will I lose root after a system update and will have to it all over again?
Levi4cyber said:
Quick question as this is my first OnePlus device.
Will I lose root after a system update and will have to it all over again?
Click to expand...
Click to collapse
Just added a new section to my original post for this.
Does flashing magisk change anything in encryption?
Does it wipe anything?
How do I get my ROM to extract the boot img?
Levi4cyber said:
Does flashing magisk change anything in encryption?
Does it wipe anything?
Click to expand...
Click to collapse
No and No
Levi4cyber said:
How do I get my ROM to extract the boot img?
Click to expand...
Click to collapse
Read the first post.
djsubterrain said:
Read the first post.
Click to expand...
Click to collapse
I'm asking where to get my ROM file, in order I should be able to extract the boot img?
A link? Somewhere on my phone?
Levi4cyber said:
I'm asking where to get my ROM file, in order I should be able to extract the boot img?
A link? Somewhere on my phone?
Click to expand...
Click to collapse
It's pinned at the top of the entire forum :
[OnePlus 9 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
They're also posted on OnePlus's site (eventually) :
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Make sure the version matches the one you're using
I updated to latest version 11.2.4.4.LE15AA
Since there's nowhere to download the OTA package and extract the boot img, can I use the boot img of a lower version - 11.2.2.2 ?
Levi4cyber said:
I updated to latest version 11.2.4.4.LE15AA
Since there's nowhere to download the OTA package and extract the boot img, can I use the boot img of a lower version - 11.2.2.2 ?
Click to expand...
Click to collapse
No, definitely not.
Try Oxygen Updater in advanced mode, it should let you download the full rom.
If you were already rooted though, you should've been able to retain it by following the last section in my original post.
If not, then follow the first 2 sections
djsubterrain said:
No, definitely not.
Try Oxygen Updater in advanced mode, it should let you download the full rom
Click to expand...
Click to collapse
Since I'm completely new to OP, is Oxygen updater an app (if yes, is it this; https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater)? Or is it built into the phone?
Levi4cyber said:
Since I'm completely new to OP, is Oxygen updater an app (if yes, is it this; https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater)? Or is it built into the phone?
Click to expand...
Click to collapse
I've linked it, it's not a default app
djsubterrain said:
No, definitely not.
Try Oxygen Updater in advanced mode, it should let you download the full rom.
If you were already rooted though, you should've been able to retain it by following the last section in my original post.
If not, then follow the first 2 sections
Click to expand...
Click to collapse
In the oxygen updater app, if I select "full update" in update method it only gives me version 11.2.2.2., if I select "incremental update", it lets me download 11.2.4.4, and when I unzipped it I have a file payload.bin (it's only 105MB).
Should I use that? Or do I need a full OTA package to extract the boot IMG?
Levi4cyber said:
In the oxygen updater app, if I select "full update" in update method it only gives me version 11.2.2.2., if I select "incremental update", it lets me download 11.2.4.4, and when I unzipped it I have a file payload.bin (it's only 105MB).
Should I use that? Or do I need a full OTA package to extract the boot IMG?
Click to expand...
Click to collapse
Are you choosing the correct OnePlus 9 Pro? It'll show you different variants under the model lookup.
To be honest, If I get the update pushed via OnePlus I always copy/paste it somewhere else cos I think it gets deleted once the upgrade is done.
If you extract the payload.bin and it shows a boot.img then that should suffice. I think it should be around 105MB (I'm on my work PC at the moment so can't check)
Thanks. I'm on the T-Mobile version of the OnePlus 9 Pro, technically my phone is currently on "11.2.2.2.LE5ACB" and the one on OnePlus's support site is "11.2.2.2.LE15AA". I'm not sure the difference but I assume T-Mobile bloatware. Hopefully they didn't do anything else to make the phone work "slightly better" on their network.
I'm not sure if the boot.img I extracted from 11.2.2.2.LE15AA will work with my currently-installed "11.2.2.2.LE5ACB"; any ideas?
Might be better to create a boot.img from my existing version and patch that. Do you know the dd command for me to just create the boot.img from my existing partition? In the past with other phones I've done something like "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/boot.img bs=4096 count=4096 skip=7552" or "dd if=/dev/block/bootdevice/by-name/boot of=boot.img" but I don't know which partition on the OnePlus 9 Pro to image. Any ideas?
--- Update 1 ---
Code:
OnePlus9ProTMO:/ $ ls -l /dev/block/bootdevice/by-name/*boot*
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/boot_a -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/boot_b -> /dev/block/sde43
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vendor_boot_a -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vendor_boot_b -> /dev/block/sde55
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vm-bootsys_a -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vm-bootsys_b -> /dev/block/sde51
Then looking at my active mounts I saw this:
Code:
OnePlus9ProTMO:/ $ mount | egrep "sde16|sde43|sde28|sde55|sde24|sde51"
/dev/block/sde51 on /vendor/vm-system type ext4 (ro,seclabel,nosuid,nodev,relatime)
Which indicates that I'm on the "b" side. So I would want to create a boot.img from `/dev/block/bootdevice/by-name/vendor_boot_b` potentially. So this command "should" work, right?
Code:
dd if=/dev/block/bootdevice/by-name/vendor_boot_b of=/sdcard/Download/stock_boot.img
I might try that instead of the boot.img I extracted from 11.2.2.2.LE5ACB since it doesn't technically line up with the T-Mobile supplied ROM version.
--- Update 2 ---
Yeah, that didn't work.Turns out dd needs to be elevated to do its thing. Got a "Permission denied" when i tried to create the image. So yeah, ironically I need root to run said command and that's why I was trying to run the command, to get the boot.img to root. lol. oh well.
Thank you very detailed.
When I click on the payload_pumper.exe file, the cmd window flashes and nothing else happens.
glitchsys said:
Turns out dd needs to be elevated to do its thing.
Click to expand...
Click to collapse
Try watching this, man, I think this is exactly what you are missing:
Code:
https://www.youtube.com/watch?v=DyUainEJwLM