[Q]Xposed flashed via Flashify - LG G Flex 2

Has anyone tried this?

Unfortunately flashify still needs a custom recovery to flash zips.
Good thinking though, I really want xposed on my flex 2 too but it looks like we'll just have to wait for a recovery.

you can try this:
http://forum.xda-developers.com/showthread.php?t=2250555

If someone else is willing to try this it would be great to know if it works.
I've already taken back 1 flex 2 because I bricked it, I don't want to risk doing it again with an app that hasn't been updated since 2013.

Yeah, I'll try it once TOTs are available in case I do brick it.
Edit: Anyone know how we can speed up the process to create return to stock files?

Seems flashing with flash gordon app is not possible... Phone reboots like normal and no framework got installed
If you softbrick your device follow the LG Flash Tool Guide... Takes about 10 - 15 mins till you are back on your homescreen with no data lost
http://forum.xda-developers.com/showthread.php?t=2785089

smouker said:
Seems flashing with flash gordon app is not possible... Phone reboots like normal and no framework got installed
If you softbrick your device follow the LG Flash Tool Guide... Takes about 10 - 15 mins till you are back on your homescreen with no data lost
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
Yeah, I found that thread. But there's no firmware for G Flex 2 anywhere. What tot/kdz file do I use?

gtamgs15 said:
Yeah, I found that thread. But there's no firmware for G Flex 2 anywhere. What tot/kdz file do I use?
Click to expand...
Click to collapse
As im from switzerland I found mine here:
http://forum.xda-developers.com/g-flex2/development/kdz-lg-g-flex-2-stock-kdz-t3068441

Does anyone know the commands of flashing xposed via fastboot or ADB?

Ah. I'm from the US, so I have the H950.
Is there a guide somewhere that shows how to dump the system to make a kdz file?
Sent from my LG-H950 using XDA Free mobile app

deBricker said:
Does anyone know the commands of flashing xposed via fastboot or ADB?
Click to expand...
Click to collapse
Open up the zip and see the directory the files are stored in. Then in adb you would use command abd push (drag file here without the parenthesis) /system and hit enter. That would be the command if you were pushing a file to system. If you were pushing to a system app it would be adb push (drag app here) /system/app hit enter. If it was a framework file it would be adb push (drag file here) /system/framework hit enter. Get the drift? For a lib file it would be adb push (drag lib file here) /system/lib hit enter

justinswidebody said:
Open up the zip and see the directory the files are stored in. Then in adb you would use command abd push (drag file here without the parenthesis) /system and hit enter. That would be the command if you were pushing a file to system. If you were pushing to a system app it would be adb push (drag app here) /system/app hit enter. If it was a framework file it would be adb push (drag file here) /system/framework hit enter. Get the drift? For a lib file it would be adb push (drag lib file here) /system/lib hit enter
Click to expand...
Click to collapse
So will this work?

No
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
Boot loops

someone test new xposet v70 ? maybe works .

Related

NS4G Recovery Question

So I just rooted via Pete's instructions, I'm on CWM 3.1.0.1 or something but I see some people are on 4.x.x.x what should I be on? Rom manager only lists the 3.1.0.1 thanks in advance.
DigitalDementia said:
So I just rooted via Pete's instructions, I'm on CWM 3.1.0.1 or something but I see some people are on 4.x.x.x what should I be on? Rom manager only lists the 3.1.0.1 thanks in advance.
Click to expand...
Click to collapse
you should upgrade to the latest, 4.x.x.x.
Im not really finding a link to that CWM version, if I flash one of the kernels will it give me the newest recovery? I know that's how people did it on the fascinate.
Going into the nexus s developement thread and look for cwm 4.x.x.x section posted by j_r0dd. The latest should be 4.0.1.4. Grab that .img file and put it into your C:\AndroidSDK\tools folder or wherever you have it located.
1. Open cmd,
cd C:\whateveryounamedit\tools
2. Boot into bootloader
3. Plug in usb and type: fastboot devices, your devices # should pop up, sometimes if its blank its still connected.
4. Type: fastboot flash recovery nameofrecovery.img
I would give a link, but im on the app.
Sorry.
EDIT: oh and be sure you grab the one for ns4g devices.
Wow thanks for being so helpful! I'll do that ASAP.
Your welcome.
kijp15 said:
Going into the nexus s developement thread and look for cwm 4.x.x.x section posted by j_r0dd. The latest should be 4.0.1.4. Grab that .img file and put it into your C:\AndroidSDK\tools folder or wherever you have it located.
1. Open cmd,
cd C:\whateveryounamedit\tools
2. Boot into bootloader
3. Plug in usb and type: fastboot devices, your devices # should pop up, sometimes if its blank its still connected.
4. Type: fastboot flash recovery nameofrecovery.img
I would give a link, but im on the app.
Sorry.
EDIT: oh and be sure you grab the one for ns4g devices.
Click to expand...
Click to collapse
adb doesn't seem to recognize fastboot as a command? I'm in the bootloader though.
Anyone have a zip of the cwm 4.x.x.x recovery?
Did you install android sdk on your computer? If not, you should do that before you proceed.
EDIT: or did you put adb to your path on your computer
I'm on W7 so I just went to platform-tools and typed cmd in the address bar. However fastboot isn't in platform-tools?
So I went to tools but got another error trying to flash.
Sorry for all the questions I've never had to use fastboot.
Or just put the .img file on the root of your sdcard.
Open terminal
type flash_image recovery /sdcard/nameofrecovery.img
Download android terminal
su
flash_image recovery /sdcard/nameofrecovery.img
Hit enter, it should now read the .img file
After that type reboot recovery to check it. Hope this helps.
kijp15 said:
Download android terminal
su
flash_image recovery /sdcard/nameofrecovery.img
Click to expand...
Click to collapse
If it says no image found?
DigitalDementia said:
If it says no image found?
Click to expand...
Click to collapse
Are you doing correctly?
I've done it a tons of time and it never gave me that msg.
When downloaded it, did it say .txt at the end, if it did change it from
.txt to .img.
And try again.
Positive. I renamed it cwm4.img for ease of use and I type:
su
flash_image recovery /sdcard/cwm4.img
Then it says flash_image: not found
kijp15 said:
When downloaded it, did it say .txt at the end, if it did change it from
.txt to .img.
And try again.
Click to expand...
Click to collapse
Still an image file.
Is your img file in any folders?
If it is your doing something wrong that I don't know about. Ha. If it is take out and out it on the root of your sdcard.
I've just flashed a img wit this same exact process and it went threw.
kijp15 said:
Is your img file in any folders?
If it is your doing something wrong that I don't know about. Ha. If it is take out and out it on the root of your sdcard.
I've just flashed a img wit this same exact process and it went threw.
Click to expand...
Click to collapse
Ugh... frustrating! It's not in a folder, it's right on the root mocking me. Okay just so I know I'm doing it right I do it like this:
su
flash_image recovery /sdcard/cwm4.img
Right? With the spaces between recovery and /sdcard/ ?
Hmmm... that is right.. is your terminal a black or blue background?
If its black your have the wrong terminal.

V20B .bin file :)

There you go
http://www.lgmobiles.com/gsm/download/P920 V20B (Gingerbread Version).zip
To root the bin file (instructions based on the one here)
Requirements: WinHex, a Linux distro (VMs work fine), drivers and flasher.
Instructions
1. Extract and open LGP920AT-00-V20b-ESA-XXX-JAN-10-2012+0_AP.bin in WinHex or any other hex editor.
2. Use WinHex to dump the content from offset B80000 (hexadecimal) to the end (select B80000 as start block and 22ABFFFF as end block and copy it to a new file), and save the dump as system.img.
3. Copy the .img to your Linux distro. Place it in the desktop. Now open terminal, cd to Desktop and enter the following commands one by one:
sudo mkdir temp
sudo mount -o loop system.img temp
Click to expand...
Click to collapse
What this does is mount the img into the temp folder. However, the files are read only. To copy su and superuser.apk, download both file, place them in the Desktop and enter the following commands:
sudo cp superuser.apk temp/app
sudo cp su temp/bin
Click to expand...
Click to collapse
Now, you have to set permissions for su and superuser.apk.
cd temp/app
sudo chmod 0644 superuser.apk
cd
cd Desktop/temp/bin
sudo chmod 6755 su
Click to expand...
Click to collapse
To save the changes, enter this:
sudo umount temp
Click to expand...
Click to collapse
Now, copy image.img back to Windows or whichever environment you prefer.
4. Copy the contents of the img file in WinHex. Go back to the bin file in WinHex and remove any data from offset B80000 onwards. You should be left with offsets 0 to B7FFFF. Right click block B7FFFF, select clipboard data > paste and accept all the prompts. You can now save the .bin file.
5. Now, it's time to flash the .bin. Extract the drivers somewhere and install "LGUnitedMobileDriver_S497CA20_WHQL_ML_Ver_1.0 .exe" and "LGUnitedMobileDriver_S497MA20_WHQL_ML_Ver_1.0.exe". Then, extract the flasher to another location.
6. With the .bin and .fls (found in the zip file containing the .bin as well) in hand, turn your phone off and remove both SD and SIM cards.
MAKE A BACKUP BEFORE PROCEEDING. THIS PROCEDURE WIPES SYSTEM AND APPS. DATA SUCH AS MUSIC AND IMAGES WILL REMAIN INTACT.
Click to expand...
Click to collapse
7. Hold volume up button while inserting the usb cable. When your computer detects the phone, let go of the button.
8. Once the driver installs, run B_SmartFlashTool_Extern.exe, go to the ROM copy D/L tab
9. Select the .bin file under CP bin and the .fls file under AP .bin.
10. Click start. Don't touch anything.
11. Once it's done, close the flasher, unplug your phone and insert the SIM and SD cards and turn it on.
12. Done
Zip file contains both .fls and .bin files.
So it seems roms based on v20B might be in the works
EDIT: Not going to upload, has been superseded by v20E and the Megatron exploit.
Hello! Please laid out links to the program.
http://file.karelia.ru/3jw96r/
LGP920AT-00-V20e (no patched)
Please patch file!
Sent from my LG-P920 using xda premium
he's uploading the v20b bin as we speak, also someone might need to make a thread on "patched firmware" if people are finding more .bin files
I'm 30% through the second zip file, Mediafire only allows maximum 200MB per file so I had to split up the .bin. It should be up in about an hours' time.
SnegovikRZN said:
http://file.karelia.ru/3jw96r/
LGP920AT-00-V20e (no patched)
Click to expand...
Click to collapse
Can somebody patch this bin. I think this is newest ROM 18.01.2012.
dr_jerremy said:
Can somebody patch this bin. I think this is newest ROM 18.01.2012.
Click to expand...
Click to collapse
I'm downloading it now, download speeds are really slow. I'll take a look once it finishes downloading.
pandaball said:
I'm downloading it now, download speeds are really slow. I'll take a look once it finishes downloading.
Click to expand...
Click to collapse
I'm almost done with dowloading,but i dont know how to patch :S..... I will try
EDIT: Bin. V20E 18.01.2012
Follow the updated instructions, they should be concise enough to follow.
In other news, I realised I forgot to set permissions for superuser.apk and su. So, I have to reupload everything due to my mistake. Sorry guys, I can only upload everything tomorrow as it's getting late
@SnegovikRZN If you could create patched ROMs for P920 as you did with the P970 that would be great
pandaball said:
Follow the updated instructions, they should be concise enough to follow.
In other news, I realised I forgot to set permissions for superuser.apk and su. So, I have to reupload everything due to my mistake. Sorry guys, I can only upload everything tomorrow as it's getting late
@SnegovikRZN If you could create patched ROMs for P920 as you did with the P970 that would be great
Click to expand...
Click to collapse
Can I say I'm first?
pandaball said:
Can I say I'm first?
Click to expand...
Click to collapse
i'll bring my thumbdrive over jk
Я не могу создать прошивку для p920, так как там немножко другая структура...
Ohh the ANDROID! string is missing... ok, no problem
in the 20e the entry 22ABFFFF is missing..
Maybe for V20E:
2249FFF0
I can't flash patched rom with Lg flash tool..
Oh I figured out what's the problem
Seem V20B having more options to root it.
hondymondy said:
Seem V20B having more options to root it.
Click to expand...
Click to collapse
Not really, most new roms would be rebased on v20E so I would recommend those

[FIX] No Power Menu, No Lockscreen, Corrupt Efs FIX! Skyrocket and T989

If your phone shuts straight down after pressing the power button and your have no lock screen, read below for solution. Before you do any of this, please note that this was caused by the note radio, aka uclc5, and if u still have it, please remove it! Also causes include a corrupt efs partition. This guide will help to restore key files important to the operation of your phone
There are three methods available. The first and second one are recommended. If you are uncomfortable with adb and command prompt please use method one
UPDATE: This has been confirmed as working on T989!
WARNING!
Method 3 is only to be used if one and two fail, or if you are positive your efs is corrupt!
Original source for solution, with a few method changes by me:
http://forum.xda-developers.com/showthread.php?t=1438451
METHOD ONE
1.) Use busy box installer from the market and re-install even if u have it working
2.) If step one doesn't work, install super su updater, and update it, then try step one again.
3.) Boot into cwm and dark side wipe 3x
4.) Flash rooted 2.3.5 from thread below
5.) Boot into rom and install root explorer
6). Navigate to /efs/imei/
7.) Press menu and select new file
8.) Name it "keystr" exactly as in quotes
9.) Long press keystr and select edit in text editor
10.) Type "ON" and press back, selecting save.
11.) Reboot and make sure keystr file is still present.
12.) Now u have a few options. U can flash ics back using either Odin one click (UCLA4 or UCLD2), but I don't recommend this. Flash one of the ics roms from the development section, we have great devs!
Rooted 2.3.5 zip:
http://d-h.st/ce75z460t847
METHOD TWO
1.) You must have the Samsung drivers installed for the skyrocket, available from here:
http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
2.) Once installed, download the attached zip, its a copy of ADB with the needed file inside
3.) Unzip to any location
4.) Boot phone into cwm
5.) Go into Mounts and Storage, and select "mount /efs". Once done connect usb cable to phone and computer
6.) Open command prompt and navigate to the unzipped adb. Issue the following command "adb devices" it should list phone
7.) Now issue the following command "adb push keystr /efs/imei"
8.) Reboot phone and check presence of keystr file in /efs/imei directory with Root Explorer
METHOD 3
Flash attached EFSFix.zip in cwm and reboot.
A SPECIAL THANKS AND SHOUT OUT TO:
mahausrath and Colombiano80 for providing the efs dumps i needed
cmbrown for being a faithful tester!
No download link at thread for Rooted 2.3.6
---------- Post added at 04:03 PM ---------- Previous post was at 03:32 PM ----------
Found a mirror
http://d-h.st/ce75z460t847
---------- Post added at 04:50 PM ---------- Previous post was at 04:03 PM ----------
Still not working. It wont let me write the file keystr to the directory, just says failed, but I can write other things to it. I'm really really confused please help.
I found the error Confusing
instead of putting "NO" put "ON"
Dwolf16 said:
I found the error Confusing
instead of putting "NO" put "ON"
Click to expand...
Click to collapse
typo, main op edited
This may be just me, but I still can't get this method to work. I can't make a file called keystr. I've tried several times using a multitude of Root exploring programs (EStrong, Root Browser, Root Explorer, Astro, ect.) I make sure it's mounted as write and do the works and it just don't work.
did u try the stuff in the pm I sent?
yea im having the same problem its not saving after shut down..
ConfusingCurve said:
This may be just me, but I still can't get this method to work. I can't make a file called keystr. I've tried several times using a multitude of Root exploring programs (EStrong, Root Browser, Root Explorer, Astro, ect.) I make sure it's mounted as write and do the works and it just don't work.
Click to expand...
Click to collapse
I can't create the file either, any help would be appreciated.
i've updated the op with a new method. since efs won't allow you to write from inside android, i've used adb with the push command.
icenight89 said:
i've updated the op with a new method. since efs won't allow you to write from inside android, i've used adb with the push command.
Click to expand...
Click to collapse
Do we need the android sdk for this?
mimart7 said:
Do we need the android sdk for this?
Click to expand...
Click to collapse
nope, I included EVERYTHING u need
Yo ice nthn is working i did everything that it says plus what you've sent me and still nothing
Still nothing
Dwolf16 said:
Still nothing
Click to expand...
Click to collapse
What's the problem? You can't use adb?
Ok so here's the break down
i flashed the efsfix.zip
i go into mounts and storage, and mount /efs ( a error saying Cant Mount /efs!)
i go to cmd.exe and find the Adb folder that has been unzipped
i detect devices with adb devices
i then adb push keystr /efs/imei
it says
C:\ADB>adb push keystr /efs/imei
0 KB/s (2 bytes in 0.002s)
I then reboot go into root explorer and nothings in efs/imei/ and theres nothing in there but the parent folder
Dwolf16 said:
Ok so here's the break down
i flashed the efsfix.zip
i go into mounts and storage, and mount /efs ( a error saying Cant Mount /efs!)
i go to cmd.exe and find the Adb folder that has been unzipped
i detect devices with adb devices
i then adb push keystr /efs/imei
it says
C:\ADB>adb push keystr /efs/imei
0 KB/s (2 bytes in 0.002s)
I then reboot go into root explorer and nothings in efs/imei/ and theres nothing in there but the parent folder
Click to expand...
Click to collapse
alright, that's it. ur efs partition is corrupt, but I need a dump from a fresh stock untouched phone to make sure its fixed properly. In the mean time, I have made a zip of my efs. So change the instructions and do this.
Make a new folder I'm the same folder as adb.exe and name is efs. Extract the contents of attached zip inside efs folder. When u use adb inside cmd, type "adb push efs /". Then reboot. Report back on if that works or not
ok so i rebooted what should i be looking for? when i was in root explorer nothing changed. When i went back into cwm it's still saying "Can't mount efs!" But in the cmd prompt it showed the "adb push efs /" worked
do u have a keystr right in /efs? does ur lock screen work, or power button? If not ur gonna have to wait til I get an efs dump from someone
icenight89 said:
do u have a keystr right in /efs? does ur lock screen work, or power button? If not ur gonna have to wait til I get an efs dump from someone
Click to expand...
Click to collapse
yea i got nothing....also when i did method one originally i would make the file
keystr
type in "ON"
Saved
and it would work until i rebooted...i just there was a way to save it after boot
The push worked, but there is nothing in the imei directory.

RUU File for RADIO-26.17.14.11_M

Hi,
I have the HTC Inspire 4g with:
Software #: 3.20.502.52 710RD
Android Version 2.3.5
HTC Sense 3.0
Baseband version: 12.69a.60.29u_26.17.14.11_M
I have unlocked the bootloader using htcdev and have successfully rooted the the device but i'm still S-ON. I have tried installing some custom ROMs however after flashing the device did not boot. I understand that I have to flash the boot.img file located in the .zip file of the custome ROM. That I know how to do... My concern is that I want to try out some ROMs but as a precaution I would like to have the stock RUU file for the type device I have should I need to restore it.
I did create a backup of my ROM and have used it previously to restore the phone after installing the custom roms that haven't boot. I just want to know if I flash the boot.img file will a restore bring it back to where it was before the flash or do i need the RUU file to restore stock?
If the later please advice where I can find that particular file as I've searched but can't seem to find the one to use.
Thanks a million.
360fifa
360fifa said:
Hi,
I have the HTC Inspire 4g with:
Software #: 3.20.502.52 710RD
Android Version 2.3.5
HTC Sense 3.0
Baseband version: 12.69a.60.29u_26.17.14.11_M
I have unlocked the bootloader using htcdev and have successfully rooted the the device but i'm still S-ON. I have tried installing some custom ROMs however after flashing the device did not boot. I understand that I have to flash the boot.img file located in the .zip file of the custome ROM. That I know how to do... My concern is that I want to try out some ROMs but as a precaution I would like to have the stock RUU file for the type device I have should I need to restore it.
I did create a backup of my ROM and have used it previously to restore the phone after installing the custom roms that haven't boot. I just want to know if I flash the boot.img file will a restore bring it back to where it was before the flash or do i need the RUU file to restore stock?
If the later please advice where I can find that particular file as I've searched but can't seem to find the one to use.
Thanks a million.
360fifa
Click to expand...
Click to collapse
RUU 3.20.502.52
Thank you kindly for taking the time to respond and also help.
Hi Gizmoe,
is there a rooted and s-off RUU file I could use as well?
Thanks again..
360fifa said:
Hi Gizmoe,
is there a rooted and s-off RUU file I could use as well?
Thanks again..
Click to expand...
Click to collapse
RUU 's can not be modified. You will not lose s off however by running an ruu. After you run ruu just pd98img a recovery and flash away.
Gizmoe said:
RUU 's can not be modified. You will not lose s off however by running an ruu. After you run ruu just pd98img a recovery and flash away.
Click to expand...
Click to collapse
So are you saying that I would need to unlock the bootloader again then following the same steps I have now? I had the impression based off could threads I've read that there's a way to root the device while gaining S-OFF that will allow me to avoid having to manually flash the boot.IMG everytime i install a custom rom. If there's a thread I can read or a guide to follow please provide a link so that I can proceed. Oh, does all the pd98img file the same?
Thanks again.
360fifa
360fifa said:
So are you saying that I would need to unlock the bootloader again then following the same steps I have now? I had the impression based off could threads I've read that there's a way to root the device while gaining S-OFF that will allow me to avoid having to manually flash the boot.IMG everytime i install a custom rom. If there's a thread I can read or a guide to follow please provide a link so that I can proceed. Oh, does all the pd98img file the same?
Thanks again.
360fifa
Click to expand...
Click to collapse
Yeah that's right. Your not s off. Well here is the only method left for the inspire. It may be a bit intimidating but really isn't that hard. Here is link.
http://tau.shadowchild.nl/attn1/?cat=6
Gizmoe said:
Yeah that's right. Your not s off. Well here is the only method left for the inspire. It may be a bit intimidating but really isn't that hard. Here is link.
Click to expand...
Click to collapse
Your're right very intimidating, however I'm willing to try my only concern is what is dd highlighted below "High Level Steps (some detail deliberately NOT included)
htc dev unlock, install cwm recovery and root ONLY
dd the stock boot image to /data/local/tmp and pull it to your pc HD (/dev/block/mmcblk0p22 is boot)
adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img"?
Also i navigated to the folder on my device however it doesn't show any boot.img file. Just a init.rc file. Could you explain just this part of it please?
Thanks again,
360fifa
360fifa said:
Your're right very intimidating, however I'm willing to try my only concern is what is dd highlighted below "High Level Steps (some detail deliberately NOT included)
htc dev unlock, install cwm recovery and root ONLY
dd the stock boot image to /data/local/tmp and pull it to your pc HD (/dev/block/mmcblk0p22 is boot)
adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img"?
Also i navigated to the folder on my device however it doesn't show any boot.img file. Just a init.rc file. Could you explain just this part of it please?
Thanks again,
360fifa
Click to expand...
Click to collapse
DD is copy and convert. It will copy boot files and convert it into boot.img. Use adb shell to do it as shell works within phone directories. Then pull it from pc using adb pull. He is giving you the exact adb commands to do both.
Code:
adb shell
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img
Gizmoe said:
DD is copy and convert. It will copy boot files and convert it into boot.img. Use adb shell to do it as shell works within phone directories. Then pull it from pc using adb pull. He is giving you the exact adb commands to do both.
Code:
adb shell
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img
Click to expand...
Click to collapse
Lol... I figured those were the commands to use, was just wondering what dd stand for.. ( copy and convert ). So let me see if i understand whats happening in the code.
So firstly I need to have the the HTC drivers installed and have the Android SDK on the root of c drive. Basically the same folder used when I unlocked to bootloader. In that folder I have the adb files, should I also add the files listed in the zip file he provided? If so let me explain the code, if no please shed some light.
So adb shell starts the emulator with the device
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot will copy and convert the mmcblk0p22 file if it is found in the /dev/block folder on the device and place it to the /data/local/tmp/ folder and call it boot.img
adb pull /data/local/tmp/boot.img I'm thinking that the computer is going to pull the boot.IMG file from the /data/local/tmp folder however where is it putting it? In the same folder that I started the command prompt from? That is the Android folder on my c drive?
360fifa said:
Lol... I figured those were the commands to use, was just wondering what dd stand for.. ( copy and convert ). So let me see if i understand whats happening in the code.
So firstly I need to have the the HTC drivers installed and have the Android SDK on the root of c drive. Basically the same folder used when I unlocked to bootloader. In that folder I have the adb files, should I also add the files listed in the zip file he provided? If so let me explain the code, if no please shed some light.
So adb shell starts the emulator with the device
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot will copy and convert the mmcblk0p22 file if it is found in the /dev/block folder on the device and place it to the /data/local/tmp/ folder and call it boot.img
adb pull /data/local/tmp/boot.img I'm thinking that the computer is going to pull the boot.IMG file from the /data/local/tmp folder however where is it putting it? In the same folder that I started the command prompt from? That is the Android folder on my c drive?
Click to expand...
Click to collapse
You will want to work out of the platform-tools directory.
Yes adb pull will always pull to your working directory unless another path is specified. Adb shell will need root. So if you type adb shell and don't see a # sign type su to get it. When done in adb shell you will need exit so you can pull to computer. If you had to take two steps to get a # prompt then you will type exit twice.
Gizmoe said:
You will want to work out of the platform-tools directory.
Yes adb pull will always pull to your working directory unless another path is specified. Adb shell will need root. So if you type adb shell and don't see a # sign type su to get it. When done in adb shell you will need exit so you can pull to computer. If you had to take two steps to get a # prompt then you will type exit twice.
Click to expand...
Click to collapse
Kool, thats the directory i'm referring to... I'm sure i'm already rooted. But your saying that when i send the command "adb shell" if I don't see the # sign then i should type su. Are you then saying that if I had to type su twice then I need to hit exit twice to pull to pc?
Oh before I forget should i run ruu before attempting this or remain as is? Also, do I need cmw recovery installed or can i remain on twrp 2.6.0.0?
Thanks again bro..
360fifa
360fifa said:
Kool, thats the directory i'm referring to... I'm sure i'm already rooted. But your saying that when i send the command "adb shell" if I don't see the # sign then i should type su. Are you then saying that if I had to type su twice then I need to hit exit twice to pull to pc?
Oh before I forget should i run ruu or remain as is?
Thanks again bro..
360fifa
Click to expand...
Click to collapse
Yes you would need to type su to see #. Adb shell root access works independently of phone root. It needs root access over adb which without an UN-secure boot img will need the su command. Exit for each level. Once for su and once for shell itself. You want to exit until you are back at Windows directory. Adb shell is at the phones root directory. The dd command is moving files within the phone, while Adb pull would be used to copy from phone to pc. I would not run that ruu if you are going to try and s off. I would run 2.47.502.7. Which I posted a link in the att stock Rom thread.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
http://forum.xda-developers.com/showthread.php?p=50027824
Gizmoe said:
Yes you would need to type su to see #. Adb shell root access works independently of phone root. It needs root access over adb which without an UN-secure boot img will need the su command. Exit for each level. Once for su and once for shell itself. You want to exit until you are back at Windows directory. Adb shell is at the phones root directory. The dd command is moving files within the phone, while Adb pull would be used to copy from phone to pc. I would not run that ruu if you are going to try and s off. I would run 2.47.502.7. Which I posted a link in the att stock Rom thread.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
http://forum.xda-developers.com/showthread.php?p=50027824
Click to expand...
Click to collapse
Do i need to run a ruu or can I proceed as is? If so u recommend running the 2.47.502.7 ruu before going thru the adb commands, y?
Thanks again..
360fifa said:
Do i need to run a ruu or can I proceed as is? If so u recommend running the 2.47.502.7 ruu before going thru the adb commands, y?
Thanks again..
Click to expand...
Click to collapse
Yes go ahead and proceed as is. You should not have any issues. If not successful then try ruu. You may not be able to run the older ruu if your bootloader is newer. Which in that case just run the newer one. I beleive I used this process on a phone with the newer software but the older works for sure.
Gizmoe said:
Yes go ahead and proceed as is. You should not have any issues. If not successful then try ruu. You may not be able to run the older ruu if your bootloader is newer. Which in that case just run the newer one. I beleive I used this process on a phone with the newer software but the older works for sure.
Click to expand...
Click to collapse
Gizmoe you have been very patient and very helpful i thank you a million times. If i encounter any other issues I'll definitely let you know.
Thanks again..
360fifa
360fifa said:
Gizmoe you have been very patient and very helpful i thank you a million times. If i encounter any other issues I'll definitely let you know.
Thanks again..
360fifa
Click to expand...
Click to collapse
I encountered an issue while trying to pull the boot.img file from /data/local/tmp/. The command used was adb pull /data/local/tmp/boot.img I then got a msg saying the adb is not a command, if I remove the adb and send the command with just pull it says pull is not a command.
If I exit su "#" it brings me to $ and if I send the command again it says that I don't have permission. Can you advise what I might be doing wrong? Oh, I got the mmcblk0p22 file to copy and convert into the boot.img file. I was able to see it using ES File explorer on my phone.
Do I need to go in fastboot usb, does unknown sources need to be checked?
Thanks again.
360fifa said:
I encountered an issue while trying to pull the boot.img file from /data/local/tmp/. The command used was adb pull /data/local/tmp/boot.img I then got a msg saying the adb is not a command, if I remove the adb and send the command with just pull it says pull is not a command.
If I exit su "#" it brings me to $ and if I send the command again it says that I don't have permission. Can you advise what I might be doing wrong? Oh, I got the mmcblk0p22 file to copy and convert into the boot.img file. I was able to see it using ES File explorer on my phone.
Do I need to go in fastboot usb, does unknown sources need to be checked?
Thanks again.
Click to expand...
Click to collapse
You need to exit one more time so you can see c prompt with your platform tools folder. Your still in shell therefore still in phone and not actually pulling to your pc. Only the pc uses Adb commands so you have to be at your platform tools folder. If you restart your phone temp empties too so if you can't see boot img anymore that's why.
Gizmoe said:
You need to exit one more time so you can see c prompt with your platform tools folder. Your still in shell therefore still in phone and not actually pulling to your pc. Only the pc uses Adb commands so you have to be at your platform tools folder. If you restart your phone temp empties too so if you can't see boot img anymore that's why.
Click to expand...
Click to collapse
Okay.. I am going to try that now, I swore I did that as well but lets see.
360fifa said:
Okay.. I am going to try that now, I swore I did that as well but lets see.
Click to expand...
Click to collapse
Here's what it said "failed to copy '/data/local/tmp/boot.img' to ' ./boot.img': Permission denied

Root Remix OS for PC

This guide is to root Remix OS for PC
You will need Ubuntu for Rooting (You can download and run it in live CD)
If you are experienced with linux systems don't read whats written in bracket
1. Download and Extract RemixRoot.zip
2. Copy system.img from your pendrive or hdd wherever you have installed Remix Os to this folder (ie RemixRoot folder it should be alongside Readme.txt)
3. Open Terminal (Ctrl+Alt+T)
4. Type
Code:
sudo -i
5. Enter your password (If you are running in live cd then no password)
6. Change directory to RootRemix folder (Goto tmp folder, right click and goto properties and copy location, this is your <dir> replace it in command below )
Code:
cd <dir>
7. If you did it right next line of terminal will end with RemixRoot# followed by blinking cursor
8. Now run rootx.sh script by typing
Code:
sh rootx.sh
9. If everything goes right there wont be any error message and you will get a root.img in your RemixRoot folder
10. Rename it to system.img and copy to your pendrive/hdd replacing previous system.img
11. Reboot and go to RemixOS and update SuperSU binaries
12. That's it! you are now rooted
Thanks to Chainfire & hackarchive
I tried it but i got no system.img, i got r/w access to system (choosen by install) so i tried to symlink it to my system directory and commented out all image mounted related things from script and then tried it.
but after that i cannot boot android anymore, i think the problem is app_process linking to daemonsu, since i set back to original it boots like normal but no superuser access. SuperSU said theres is no superuser installed.
Any suggestion?
Silly question but will I lose root access if I update to the newest version by flashing the new image over the top?
Yes a silly question.... Deserves a silly answer. It will still be underneath, but good luck trying to retrace it!
any other method for rooting, without using ubuntu?
#tested with ubuntu live, and it works like a charms. Thank you..
Sent from my C46G using XDA Premium 4 mobile app
ninharp said:
I tried it but i got no system.img, i got r/w access to system (choosen by install) so i tried to symlink it to my system directory and commented out all image mounted related things from script and then tried it.
but after that i cannot boot android anymore, i think the problem is app_process linking to daemonsu, since i set back to original it boots like normal but no superuser access. SuperSU said theres is no superuser installed.
Any suggestion?
Click to expand...
Click to collapse
same problem here.
Hope same other method can solved
I modified the original script to work with the system folder installation and i removed all app_processX dependend things from script (dunno if it affects the root in any way, cannot find any issue by now) Read the Readme.txt for further installation instructions. The link you find on the reddit sub that GoPal has posted! I cannot post links right now.
Try this
kretex said:
Hope same other method can solved
Click to expand...
Click to collapse
ninharp said:
I tried it but i got no system.img, i got r/w access to system (choosen by install) so i tried to symlink it to my system directory and commented out all image mounted related things from script and then tried it.
but after that i cannot boot android anymore, i think the problem is app_process linking to daemonsu, since i set back to original it boots like normal but no superuser access. SuperSU said theres is no superuser installed.
Any suggestion?
Click to expand...
Click to collapse
You will get root.img file you will have to rename it to system.img
masdeco said:
same problem here.
Click to expand...
Click to collapse
Me too [emoji25]
Envoyé de mon E5333 en utilisant Tapatalk
I've just installed RemixOS 2.0 onto a partition on my Lenovo X200T. I followed the instructions and all was good until I tried to run SuperSU. When it tried to update via the normal method the install failed and asked for a reboot. Any suggestions.
ninharp said:
I modified the original script to work with the system folder installation and i removed all app_processX dependend things from script (dunno if it affects the root in any way, cannot find any issue by now) Read the Readme.txt for further installation instructions. The link you find on the reddit sub that GoPal has posted! I cannot post links right now.
Try this
Click to expand...
Click to collapse
the answer is replace the system folder. this is my methode :
1. copy the system img from the extracted remix iso to somewhere
2. then run the script
3. unpack the system img that already rooted and copy all the content to the system folder of the remix (replace)
4. done. Remix os rooted.
Guys, I installed Remix to ext4 partition (in order to use all free space), so there's no "system.img" on it (but there's "system" folder). How to modify the script or to root Remix other way?
masdeco, thanks for the idea! How do you unpack img file, btw?
4ezahernya said:
Guys, I installed Remix to ext4 partition (in order to use all free space), so there's no "system.img" on it (but there's "system" folder). How to modify the script or to root Remix other way?
masdeco, thanks for the idea! How do you unpack img file, btw?
Click to expand...
Click to collapse
after root the system img then mount it, copy all the content to the system folder of your remix.
since I am a linux user so I use this command :
mount -o loop system.img tmp
this is so cool cool
Works Lenovo Yoga 2 11
Installed to a partition on my HD:
Downloaded RemixOS iso
extracted contents of iso
created temp, data and system folders
ran this tool to root the system.img (now root.img)
renamed root.img back to system.img
mounted system.img to temp folder
copied contents of temp folder to system folder
added entry in grub
now I am triple booting Windows, Linux and RemixOS 2.0 Android with ROOT
Thank You!!!
here is a xdelta3 for patching system.img for those using Remix OS 2 from a USB stick and run windows
GizmoTheGreen said:
here is a xdelta3 for patching system.img for those using Remix OS 2 from a USB stick and run windows
Click to expand...
Click to collapse
can you please explain its usage?
the_poolee said:
can you please explain its usage?
Click to expand...
Click to collapse
me too!
Please
the_poolee said:
can you please explain its usage?
Click to expand...
Click to collapse
dariett said:
me too!
Please
Click to expand...
Click to collapse
it shouldn't be too hard to figure out, put the files in your folder of choice with the system.img from your usb stick, run the batfile. it should create a file named rooted system image, now just replace system.img on your usb stick with that and run...
ofcourse I am assuming your system.img is identical to the one I had, which it should be if it was the 2.0 dev preview which is the only thing you can get today, right?

Categories

Resources