Database Info

****ROOT EVO After July 1 OTA Update

I tried every method, read every thread in every forum in an effort to root my EVO. Nothing worked. I was driving myself mad and spending tons of time. I Eventually I came across a post which directed me to XDA Developers Thread ---==={ROOT GUIDE}===--- | 1.47.651.1 ROOT, post 579 by SharkUW . I have used this on my own phone and I don't see a reason why it wouldn't work. I modified some of the instructions to make it clearer. The instructions may not be exact, and there is some seat-of-the-pants involved, but I got it to work. Use it at your own risk.
Prerequisites (follow in order)
Android-SDK developers program. I loaded it to C:
JAVA SE Development (use correct bit – 32 or 64). loaded in C:
Microsoft .NET Framework V 4.0
Reboot your phone and do a factory reset. Erase everything
Set phone to Charge Only and USB debugging
Open the stock browser and sign-in with your PCS phone number. Leave running.
Shutdown the phone, then restart
Make sure ADB is functional on your computer. You should be able to "adb shell" (confirming adb is working, exit shell if you're in it).
Extract the Do_root.zip (link below) and place all these files into the SAME folder as adb.exe. I have not included the appropriate PC36IMG.zip. Get it here. http://forum.xda-developers.com/showthread.php?t=701835 Leave the name as "eng-PC36IMG.zip". Place that in the SAME directory as well as the .zip.
Open a command prompt on your computer. point directory to Android-SDK directory\tools and a list will come up… click on "root.bat” and click RUN.
If it hangs for more than 30 seconds with the browser ****, CTRL+C, yes to kill the bat and just run it again.
Follow the directions. Your phone is going to reboot. It is then going to do a little **** and reboot into the boot loader. Keep track of the Command screen and wait because some steps take a while and there is no way of telling if it’s working. Nothing lasted more than 5 minutes. Eventually it will be in a "bootloader" and ask if you want to reboot. Say Yes with a Volume UP.
The .bat is now done. You have root. (not sure if next part is true) You now need a custom recovery to flash a proper ROM beyond the scope of this guide.
In original instructions but I’ve found the following Recovery step and code is not necessary: Now take the last step and flash the recovery.img that will already be on the root of your sdcard. To do this, after the PC36IMG flash:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
To check for root do ADB Shell and should get #.
If you're all advancedy you can put on a different recovery image.
IMPORTANT If you get a message here about "not writing bad block", flash it again until you get 0 errors. I don't know how common it is, but personally my recovery has issues with flashing. Do NOT let that be a bad flash.
Attached Files
do_root.zip (4.07 MB, 49 views)
________________________________________
Last edited by SharkUW; 7th July 2010 at 01:06 AM.

Going to try it tomorrow and hope it works. Thanks

Where are the attached files?

Can't find the do_root.zip file. Seems there is no attachment, please re-post. Thanks.

I tried to attach the do_root.zip file and a link to Toast 2 file. If that doesn't work, go to the referenced post #579 here: http://forum.xda-developers.com/showthread.php?t=718889&page=58.

Have you tried this SimpleRoot? I just did it, and it worked flawlessly.

Vivix729 said:
Have you tried this SimpleRoot? I just did it, and it worked flawlessly.
Click to expand...
Click to collapse
Simpleroot ftw.

mattrb said:
Simpleroot ftw.
Click to expand...
Click to collapse
QFT. I did simple root (I still setup adb and ensured it was working first) and then flashed the rooted Stock 1.47 ROM in about 40 min. I think most people that are running into issues with Simpleroot do not have adb setup properly or they did something inadvertently and need to clear out the files/cache and need to start over from scratch.

gmanvbva said:
QFT. I did simple root (I still setup adb and ensured it was working first) and then flashed the rooted Stock 1.47 ROM in about 40 min. I think most people that are running into issues with Simpleroot do not have adb setup properly or they did something inadvertently and need to clear out the files/cache and need to start over from scratch.
Click to expand...
Click to collapse
I did simple root and it worked fine too. I don't think the issue is adb being setup since he has an adb file in his download.

Update from a few days ago.
Just got a new SDHC card and simpleroot worked. The SDHC that came with my phone died. I placed a spare in there that was a 2gd regular micro and Hboot would not ready the IMG for nothing.
If simple root is not working then it's the Sh!tty card acting up.
Happy ending for me.

I just got my phone yesterday did the ota simpleroot and seems like it worked fine
but now i dont know what to do next
to get custom roms or froyo 2.2 or anything lol

Awesome post |OP|.
My desktop is Windows 7 x64 and doesn't play nicely with the standard tools.
I was forced to adapt your root.bat script to an OSX friendly BASH script.
The only requirement is that you download the android SDK from developer.android.com/sdk/index.html (apparently, I'm too new to post links).
The steps I took to get root:
Unzip the android SDK
follow |OP|'s instructions, unzipping the contens of do_root into [sdk-root]/tools/
unzip the attached bash script to the [sdk-root]/tools/
run my bash script from the [sdk-root] folder instead of root.bat - type "./root.sh" without the double-quotes
Grab a copy of Froyo while your phone is being rooted

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

[How-To] Update devices via the OTA .zip

Hello everyone,
rhcp was able to locate a method with which to do updates the standard way HTC does them. If you are, for instance, on 1.73 and have the 1.85 OTA .zip file (the one sent from HTC, not a CWM .zip file), you can use this method to place it in the right location and start an update.
Disclaimer:
I do not take responsibility if something goes wrong. PLEASE do this at your own risk.
Please do not use this to go to 1.85 as you may lose root. This is more FYI for future OTA updates or after 1.85 is rooted.
Requirements:
You must have ROOT before doing this. You'll be accessing a location that is not writable without root.
You must have the official OTA file. If someone can help with this portion I can post it here for all users to use if they wish.
Follow these steps to pull the OTA update:
When it shows "downloading" and the OTA completes, if you have root, please do the following:
Code:
adb shell
cd /cache
ls -l
Locate the file ending with .zip here. May look extremely long and should resemble something like OTA_Evita_U_Cingular.........zip
Quit out of adb shell
Code:
adb pull /cache/<file name of the OTA package.zip>
Post that package.zip file on a file share and send me the link and I will add it to the OP.
To update using the OTA file, follow these steps:
Code:
adb push <file name of the OTA package.zip> /mnt/sdcard/
adb shell
su
cp <file name of the OTA package.zip> /cache/update.zip
cd /cache/
mkdir recovery
cd recovery
echo “–update_package=/cache/update.zip” > command
adb reboot recovery
This will cause your device to update using the OTA method that HTC uses to push updates.
If this helped you...PLEASE donate to rhcp, which happens to have had to pay for a new One S due to bricking the first time figuring this out. His donate link is here.
Toss me a Thanks if you think this guide was helpful .

h8rift said:
Hello everyone,
rhcp was able to locate a method with which to do updates the standard way HTC does them. If you are, for instance, on 1.73 and have the 1.85 OTA .zip file (the one sent from HTC, not a CWM .zip file), you can use this method to place it in the right location and start an update.
Disclaimer:
I do not take responsibility if something goes wrong. PLEASE do this at your own risk.
Requirements:
You must have ROOT before doing this. You'll be accessing a location that is not writable without root.
You must have the official OTA file. If someone can help with this portion I can post it here for all users to use if they wish.
Follow these steps to pull the OTA update:
When it shows "downloading" and the OTA completes, if you have root, please do the following:
Code:
adb shell
cd /cache
ls -l
Locate the file ending with .zip here. May look extremely long and should resemble something like OTA_Evita_U_Cingular.........zip
Quit out of adb shell
Code:
adb pull /cache/<file name of the OTA package.zip>
Post that package.zip file on a file share and send me the link and I will add it to the OP.
To update using the OTA file, follow these steps:
Code:
adb push <file name of the OTA package.zip> /mnt/sdcard/
adb shell
su
cp <file name of the OTA package.zip> /cache/update.zip
cd /cache/
mkdir recovery
cd recovery
echo “–update_package=/cache/update.zip” > command
adb reboot recovery
This will cause your device to update using the OTA method that HTC uses to push updates.
If this helped you...PLEASE donate to rhcp, which happens to have had to pay for a new One S due to bricking the first time figuring this out. His donate link is here.
Toss me a Thanks if you think this guide was helpful .
Click to expand...
Click to collapse
nice but this update didnt fix anything anyway. wifi still sucks.

djfrost40 said:
nice but this update didnt fix anything anyway. wifi still sucks.
Click to expand...
Click to collapse
Lol. Be it as it may....this is still a handy method for us to use with future OTA updates.

h8rift said:
Lol. Be it as it may....this is still a handy method for us to use with future OTA updates.
Click to expand...
Click to collapse
I think ATT and HTC just need to issue a refund to all of the unfortunate folks that fell for this phone hook line and sinker...LOL, I tried the update, and wifi is still bad maybe even worse... I just boxed mine up and went back to my HTC Vivid.

djfrost40 said:
I think ATT and HTC just need to issue a refund to all of the unfortunate folks that fell for this phone hook line and sinker...LOL, I tried the update, and wifi is still bad maybe even worse... I just boxed mine up and went back to my HTC Vivid.
Click to expand...
Click to collapse
Sorry to hear that djfrost40. I have literally had zero issues with this phone. No issues mentioned here (besides HTC's software-tweaked multi-tasking) have been evident on my phone. Hope your Vivid treats you well.

h8rift said:
Sorry to hear that djfrost40. I have literally had zero issues with this phone. No issues mentioned here (besides HTC's software-tweaked multi-tasking) have been evident on my phone. Hope your Vivid treats you well.
Click to expand...
Click to collapse
Wow was starting to think I was the only one because like you I have had zero problems with my phone never had to replace it and the multi tasking doesn't really effect me all that much
Sent from My Nocturnalized Beast

The only issue I have is getting my OC to work 100%. Aside from that, I love the phone to death!

This method does not seem to work for me. I have no trouble following the steps but the phone just boots into recovery and nothing else. Also I think there are a couple of "exits" missing from the list of commands right after the creation of the command file, maybe they are implied.
Has anyone else verified this works for them? I am on a rooted, TWRP and still at 1.73. I also tried this method with CWM recovery installed but no luck.

anika200 said:
This method does not seem to work for me. I have no trouble following the steps but the phone just boots into recovery and nothing else. Also I think there are a couple of "exits" missing from the list of commands right after the creation of the command file, maybe they are implied.
Has anyone else verified this works for them? I am on a rooted, TWRP and still at 1.73. I also tried this method with CWM recovery installed but no luck.
Click to expand...
Click to collapse
If you have twrp, why have you flashed a custom Rom?
Sent from my HTC One X using Tapatalk 2

kleeman7 said:
If you have twrp, why have you flashed a custom Rom?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Yeah, kinda does'nt make sense. Actually I am liking the original HTC sense and also I am not sure which rom to try out.

Update.zip for root??
Is it possible to make an update.zip that we could flash via stock recovery to push su bianary? Just a thought.

kizzle4 said:
Is it possible to make an update.zip that we could flash via stock recovery to push su bianary? Just a thought.
Click to expand...
Click to collapse
Nope, unless you work for HTC and know how to get the key to sign the update zip
Sent from my HTC One XL using Tapatalk 2

What about update zip from say an international version?

kizzle4 said:
What about update zip from say an international version?
Click to expand...
Click to collapse
It will fail once it reads the build prop and realizes that this isn't an international one x, and if it does flash you would have a nice paperweight
Besides what does this accomplish? You can't modify ANY zip file from HTC without breaking the signature. Which makes this method useless
Sent from my HTC One XL using Tapatalk 2

In order for a thread to exist in the development section, it must contain a link to downloadable content. Because this is more of a guide, I'm moving this to general.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.

What steps in the OP modify if there's not enough space on the cache partition to hold the update.zip? Is it safe to run the following steps in that case:
Code:
adb push <file name of the OTA package.zip> /mnt/sdcard/
adb shell
su
cd /mnt/sdcard/
mv <file name of the OTA package.zip> update.zip
cd /cache/recovery
echo "-update_package=/mnt/sdcard/update.zip" > command

AlxMAX said:
What steps in the OP modify if there's not enough space on the cache partition to hold the update.zip? Is it safe to run the following steps in that case:
Code:
adb push <file name of the OTA package.zip> /mnt/sdcard/
adb shell
su
cd /mnt/sdcard/
mv <file name of the OTA package.zip> update.zip
cd /cache/recovery
echo “–update_package=/mnt/sdcard/update.zip” > command
Click to expand...
Click to collapse
Wondering this too... or even using a larger partition like /data that has 1GB free. :-/

Can someone dd the radio partition for me and link to it?
Wanna make the zips =)
FYI: use this adb command and then pull the img of your sd card -
Code:
C:\adb>adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/radio.img

taylor.fowler said:
Can someone dd the radio partition for me and link to it?
Wanna make the zips =)
FYI: use this adb command and then pull the img of your sd card -
Code:
C:\adb>adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/radio.img
Click to expand...
Click to collapse
"removed from dropbox" stock radio from new at&t ota, download taylor.fowler cwm flashable

Cm10.x and sense zips coming soon!
Sent from my One X using xda app-developers app

[wip] atrix2 webtop ubuntu ICS 4.0.4 OTA

Thanks to jimbridgman, I was able get this far...
I purchased a couple of lapdocks for $50 each to use with my raspberry pi. I needed cables from China to use the rpi on the lapdock, so while waiting for said cables, I bought a used atrix 2 [AT&T branded] to play with. When I got it, it already had the OTA 4.0.4 update on it. I *really* wanted ubuntu to run on this and was sad to learn this wasn't possible.
So I've been fooling around with this thing and here's what i've got so far.
Things you may want to have [or already have!]:
MotorolaDeviceManager_2.3.4
ICS_root(superuser_3.1.3_and_su_binary_3.1.1)_
InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
RSD Lite v5.6
webtop_unlock.tar
ADB
Linux box [I have Ubuntu installed in an Oracle based VM]​
If you hose the phone you'll need to put it into fastboot mode [hold power and volume down] and run RSD Lite to restore/reflash it. After the flash completes, root it with the ICS_root(superuser_3.1.3_and_su_binary_3.1.1)'s root.bat. If you aren't aware that this will erase everything on your phone, you may want to get some more reading in.
So the atrix2 4.0.4 AT&T OTA *seems* to store the WebTop/Ubuntu environment on /dev/block/mmcblk1p24; it has a symbolic link called "webtop" in /dev/block.
So what I've tried so far...
pull the webtop image and copy to sdcard
"dd if=/dev/block/mmcblk1p24 of=/sdcard/webtop.img"
The "webtop.img" to your desktop and back it up. AFAICT, this is your WebTop partition and if you hose this file, with no backup, you've permanently hosed WebTop on the phone. This file is 1.3gigs
Copying this file takes about 12 minutes on my computer​
mount the "webtop.img" file in linux using [after creating the folder "wt" in tmp]
sudo mount webtop.img /tmp/wt -o loop​
edit with "sudo nautilus"
browse to /tmp/wt
rename etc/toymoyo to "old-toymoyo"
editing "start-oshwt-1.sh" and "start-oshwt-2.sh" [located in /tmp/wt/usr/local/bin/"]
Here I have progressively commented out every line starting with "sfalv"​ rename "mountsecurityfs.sh" in "etc/init.d" to "mountsecurityfs.old" and create a blank "mountsecurityfs.sh" file
extract the contents of mbm.rar to respective directories​
unmount "webtop.img" with
sudo umount /tmp/wt​
push your edited version to the phone
copy "webtop.img" back to the sdcard [overwrite/replace]. Before you do this, make sure you have a clean copy of "webtop.img" somewhere
adb shell | su | dd if=/sdcard/webtop.img of=/dev/block/mmcblk1p24
Replacing this file/partition takes about 12 minutes on my computer​
Sadly, this has had no effect so far. My WAG is that this version of WebTop/ ICS 4.0.4 does some copying from tmp folders to replace the stuff I've changed. Basically, at this point I'm trying just to crash WebTop.

ill13 said:
I purchased a couple of lapdocks for $50 each to use with my raspberry pi. I needed cables from China to use the rpi on the lapdock, so while waiting for said cables, I bought a used atrix 2 [AT&T branded] to play with. When I got it, it already had the OTA 4.0.4 update on it. I *really* wanted ubuntu to run on this and was sad to learn this wasn't possible.
So I've been fooling around with this thing and here's what i've got so far.
Things you may want to have [or already have!]:
MotorolaDeviceManager_2.3.4
ICS_root(superuser_3.1.3_and_su_binary_3.1.1)_
InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
RSD Lite v5.6
webtop_unlock.tar
ADB
Linux box [I have Ubuntu installed in an Oracle based VM]​
If you hose the phone you'll need to put it into fastboot mode [hold power and volume down] and run RSD Lite to restore/reflash it. After the flash completes, root it with the ICS_root(superuser_3.1.3_and_su_binary_3.1.1)'s root.bat. If you aren't aware that this will erase everything on your phone, you may want to get some more reading in.
So the atrix2 4.0.4 AT&T OTA *seems* to store the WebTop/Ubuntu environment on /dev/block/mmcblk1p24; it has a symbolic link called "webtop" in /dev/block.
So what I've tried so far...
pull the webtop image and copy to sdcard
"dd if=/dev/block/mmcblk1p24 of=/sdcard/webtop.img"
The "webtop.img" to your desktop and back it up. AFAICT, this is your WebTop partition and if you hose this file, with no backup, you've permanently hosed WebTop on the phone. This file is 1.3gigs
Copying this file takes about 12 minutes on my computer​
mount the "webtop.img" file in linux using [after creating the folder "wt" in tmp]
sudo mount webtop.img /tmp/wt -o loop​
edit with "sudo nautilus"
browse to /tmp/wt
rename etc/toymoyo to "old-toymoyo"
editing "start-oshwt-1.sh" and "start-oshwt-2.sh" [located in /tmp/wt/usr/local/bin/"]
Here I have progressively commented out every line starting with "sfalv"​ rename "mountsecurityfs.sh" in "etc/init.d" to "mountsecurityfs.old" and create a blank "mountsecurityfs.sh" file
extract the contents of mbm.rar to respective directories​
unmount "webtop.img" with
sudo umount /tmp/wt​
push your edited version to the phone
copy "webtop.img" back to the sdcard [overwrite/replace]. Before you do this, make sure you have a clean copy of "webtop.img" somewhere
adb shell | su | dd if=/sdcard/webtop.img of=/dev/block/mmcblk1p24
Replacing this file/partition takes about 12 minutes on my computer​
Sadly, this has had no effect so far. My WAG is that this version of WebTop/ ICS 4.0.4 does some copying from tmp folders to replace the stuff I've changed. Basically, at this point I'm trying just to crash WebTop.
Click to expand...
Click to collapse
I thought I read somewhere that webtop for ICS was nothing more than an apk. That's the problem of hacking it up, it's not running like it was in GB

Ugh, well, if WebTop is nothing but an apk, then that explains why i cant seem to crash it
So, I've extracted the system image from dev/block and mounted it with
sudo mount -t ext4 system.img /tmp/atrix -o loop​
I'll poke in there...but if this all for naught, I may have to ditch this phone and go for a nexus

ill13 said:
I purchased a couple of lapdocks for $50 each to use with my raspberry pi. I needed cables from China to use the rpi on the lapdock, so while waiting for said cables, I bought a used atrix 2 [AT&T branded] to play with. When I got it, it already had the OTA 4.0.4 update on it. I *really* wanted ubuntu to run on this and was sad to learn this wasn't possible.
So I've been fooling around with this thing and here's what i've got so far.
Things you may want to have [or already have!]:
MotorolaDeviceManager_2.3.4
ICS_root(superuser_3.1.3_and_su_binary_3.1.1)_
InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
RSD Lite v5.6
webtop_unlock.tar
ADB
Linux box [I have Ubuntu installed in an Oracle based VM]​
If you hose the phone you'll need to put it into fastboot mode [hold power and volume down] and run RSD Lite to restore/reflash it. After the flash completes, root it with the ICS_root(superuser_3.1.3_and_su_binary_3.1.1)'s root.bat. If you aren't aware that this will erase everything on your phone, you may want to get some more reading in.
So the atrix2 4.0.4 AT&T OTA *seems* to store the WebTop/Ubuntu environment on /dev/block/mmcblk1p24; it has a symbolic link called "webtop" in /dev/block.
So what I've tried so far...
pull the webtop image and copy to sdcard
"dd if=/dev/block/mmcblk1p24 of=/sdcard/webtop.img"
The "webtop.img" to your desktop and back it up. AFAICT, this is your WebTop partition and if you hose this file, with no backup, you've permanently hosed WebTop on the phone. This file is 1.3gigs
Copying this file takes about 12 minutes on my computer​
mount the "webtop.img" file in linux using [after creating the folder "wt" in tmp]
sudo mount webtop.img /tmp/wt -o loop​
edit with "sudo nautilus"
browse to /tmp/wt
rename etc/toymoyo to "old-toymoyo"
editing "start-oshwt-1.sh" and "start-oshwt-2.sh" [located in /tmp/wt/usr/local/bin/"]
Here I have progressively commented out every line starting with "sfalv"​ rename "mountsecurityfs.sh" in "etc/init.d" to "mountsecurityfs.old" and create a blank "mountsecurityfs.sh" file
extract the contents of mbm.rar to respective directories​
unmount "webtop.img" with
sudo umount /tmp/wt​
push your edited version to the phone
copy "webtop.img" back to the sdcard [overwrite/replace]. Before you do this, make sure you have a clean copy of "webtop.img" somewhere
adb shell | su | dd if=/sdcard/webtop.img of=/dev/block/mmcblk1p24
Replacing this file/partition takes about 12 minutes on my computer​
Sadly, this has had no effect so far. My WAG is that this version of WebTop/ ICS 4.0.4 does some copying from tmp folders to replace the stuff I've changed. Basically, at this point I'm trying just to crash WebTop.
Click to expand...
Click to collapse
Fist off this very very familiar, and little credit where credit is due would have been nice in your OP. See my link below.
The real issue is that with moto getting rid of support for webtop and the lapdocks, they took out the important parts of the kernel from the boot.img, so the major parts like the ubuntu.sh that is in / on the android side is not there, and since the bootloader is locked, we cannot make any changes to the / partition to add the unbutu.sh script back. You are more than welcome to try and use my webtop hack script (which I notice you call out my webtop_unlock.tar, without crediting me) to move the image to your sdcard, so that you do not have to use an image file that was dd'd I have a way to copy it and then edit the mount.sh script in /system/bin to mount it on every boot, but again you will need to find a way to get the unbutu.sh script and the kernel modules to work, that is where I had to stop with hacking webtop.
P.S. here is my webtop hack instructions. All my files are linked in there, the script works, and many people have used it. The issue will be getting the unbuntu.sh script and putting it in the right place and getting the dock apk files from GB that call the ubuntu.sh script when docked to work in ICS.
http://forum.xda-developers.com/showthread.php?t=1375042

jimbridgman,
Yeah, I used your instructions to get to where I am! However, since I am stuck on OTA 4.0.4 I don't have a lot of hope...
Currently downloading the InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip to try what you just said about replacing apks and the ubuntu.sh script...
since this phone isn't my daily driver, I suppose I could brick it and not worry too much...Although webtop 3 is usable for me, I'd just rather have a full desktop
Ahhh...on the old roms, "grfs.img" is the ubuntu webtop...

ill13 said:
jimbridgman,
Yeah, I used your instructions to get to where I am! However, since I am stuck on OTA 4.0.4 I don't have a lot of hope...
Currently downloading the InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip to try what you just said about replacing apks and the ubuntu.sh script...
since this phone isn't my daily driver, I suppose I could brick it and not worry too much...Although webtop 3 is usable for me, I'd just rather have a full desktop
Ahhh...on the old roms, "grfs.img" is the ubuntu webtop...
Click to expand...
Click to collapse
Again though, it even states in the forum rules, that you are to give credit, when you use other peoples work, and you did not do that in your post, just remember that next time, because I could go to the MODS and have the thread removed, since your technically you were using my work without permission. Read the rules again just so you know. Others may not be so nice, I have seen people banned for similar things.

added thanks to first post...

This work on Jely Bean too?

Jim, so does this mean that without an unlocked bootloader, Ubuntu webtop won't be possible on ICS? I suppose the only other way to do it would be by loading the modules via 2ND-init?

snowplow said:
Jim, so does this mean that without an unlocked bootloader, Ubuntu webtop won't be possible on ICS? I suppose the only other way to do it would be by loading the modules via 2ND-init?
Click to expand...
Click to collapse
probably not, since the unbuntu.sh was in / on the android side, and that is in the boot image, and unless you have good source for the MB865, then there is a nil chance.

Jim
I've got a build date of Friday August 31, this means that there is no going back to GB?
Sent from my MB865 using XDA Premium HD app

jimbridgman said:
Again though, it even states in the forum rules, that you are to give credit, when you use other peoples work, and you did not do that in your post, just remember that next time, because I could go to the MODS and have the thread removed, since your technically you were using my work without permission. Read the rules again just so you know. Others may not be so nice, I have seen people banned for similar things.
Click to expand...
Click to collapse
Hey Jim, old pal!
How's work on the new ROM going?
Would love to give it a spin with my lapdock.

awe man I wish this was working...
Alperon said:
Hey Jim, old pal!
How's work on the new ROM going?
Would love to give it a spin with my lapdock.
Click to expand...
Click to collapse

Fire hd8 2017 root, debrick

Tested only on 2017 hd8
This post is outdated please refer to: https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-8-2017-douglas-t3962846
1 - Open your fire hd 8 7th gen, now you need to access the pads under the board(be very careful there is a lot of glue), specifically we need the pad TP28 which is the clk signal of the emmc
2 - Get yourself a wire (I recommend one with only one conductor in the plastic shroud) or something conductive
3 - Now on a linux machine/vm (if you use a vm, do usb passthrough) go in the amonet folder and do:
Code:
sudo ./bootrom-step.sh
4 - When you see:
Code:
[2019-02-07 14:35:59.478924] Waiting for bootrom
short TP28 to ground (there is a big pad near TP28, its ground so you can use it) and plug the usb
5 - If the operation is successful you should be prompted to remove the short and press enter
6 - Wait until the script end if it's succesfull you will see:
Code:
[2019-02-07 12:11:05.621357] Reboot to unlocked fastboot
in case of any error probably you should start again from step 4
7 - now the device should reboot and go automatically in fastboot mode (if not, try unplug and plug back the usb), you can reflash any partition ex:
Code:
sudo fastboot flash <partition-name> <image-file.img>
The boot partition need to be flashed on the device in order to recover from the first part of the guide so:
Code:
sudo fastboot flash boot boot.img
You can extract boot.img from the ota archive
Becouse there is no system partition check on th 7th gen you can flash a modified system.img (a rooted one)
i will link the ota where i've extracted the .img (sorry i can't upload mine becouse my up speed is trash, 512kbit/s)
8 - Now, again on al linux machine/vm go in the folder amonet-res and run again:
Code:
sudo ./bootrom-step.sh
the steps are the same as from 3 to 6
9 - your table should reboot into FireOS
Recover from flashing the 8th gen exploit
in step 7, when you get into fastboot mode do:
Code:
sudo fastboot flash boot boot.img
with the boot.img from an ota then proceed with the other step
Ready to flash rooted system
Instead of make your own modified system image, you can flash this (thanks to @JJ2017) https://mega.nz/#F!G7pn3SCS!TWhEmzSFNctoil626IbF3A
download both boot and system from the mega link then, once you get in the fastboot mode in step 7, run from the directory where the downloaded system.img and boot.img are:
Code:
sudo fastboot flash system system.img
sudo fastboot flash boot boot.img
This method require you to install the SuperSu app (download an apk from a site like APKmirror)
Make your own system.img
Download this : https://raw.githubusercontent.com/xpirt/sdat2img/master/sdat2img.py
(assuming debian or ubuntu distro) install android-tools-fsutils
1 - get yourself an ota archive
2 - extract it
3 - put sdat2img.py in the same directory as the extracted ota
4 - do
Code:
python2 sdat2img.py system.transfer.list system.new.dat system.img
5 - now do
Code:
mkdir system && sudo mount system.img system
6 - now you can modify the image and for example install SuperSU (Install SuperSu on system.img section of the thread)
7 - unmount the image
8 - do
Code:
img2simg system.img system-a.img
9 - in fastboot mode do:
Code:
sudo fastboot flash system system-a.img
sudo fastboot flash boot boot.img
run the commands in the same folder as the .img
Install SuperSu on system.img
Coming soon. for now you can refer to Building the system image section of this post (thanks to @cybersaga) https://forum.xda-developers.com/showpost.php?p=78864228&postcount=31
Or try this script for creating a rooted system.img (thanks to @SirausKen) https://forum.xda-developers.com/showpost.php?p=78868608&postcount=39
My terminal output while i'm flashing rooted system.img
https://pastebin.com/hn2Rhk87
Thanks
- xyz' for the amonet exploit chain
- <br > for the emmc pinout
- xpirt for sdat2img

looks like I got something to try this evening.
Thanks!

NFSP G35 said:
looks like I got something to try this evening.
Thanks!
Click to expand...
Click to collapse
Please post your results

Ok, I'm gathering the required stuff to try this out.
I'm going to go through your method exactly, but I'm curious... (and this is probably a stupid question that's already been answered somewhere else) why can't we flash TWRP?

Is it just me, or is the process of manually applying SuperSU to the system image a huge pain?
Got to put it on pause for tonight. Any tips or suggestions are welcome though!

NFSP G35 said:
Is it just me, or is the process of manually applying SuperSU to the system image a huge pain?
Got to put it on pause for tonight. Any tips or suggestions are welcome though!
Click to expand...
Click to collapse
Yeah I feel like step 6 could be expanded into, like, 5 steps. I'm not sure how that's done either.

Can confirm working....
Awesome work @t0x1cSH.... after many an hour.... yes, your method successfully root Fire HD8 (2017)
Pretty much followed your guide - managed the 'SU' injection with help from the method description @ <br /> Hardmod Root (https://forum.xda-developers.com/hd...ot-hardmod-root-amazon-fire-hd-8-7th-t3851617)
Actually, not too difficult compared to the Hardmod - when fully written up this will be a game-changer
Many thanks: :good::good::good:
BTW: used Fire OS 5.3.6.4 (most recent)

I'll probably give it a try this weekend. Where did you get the OTA update from?
Update: Nevermind, I found it: https://www.amazon.ca/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=202144610

I'm not great at Linux commands. Would anyone be kind enough to tell me how to modify the system image to include root?

I'll try this weekend as well.

niggabyte said:
I'm not great at Linux commands. Would anyone be kind enough to tell me how to modify the system image to include root?
Click to expand...
Click to collapse
See the previous post (or more to the point, see the section "Writing SuperSU" in <br />'s thread...
JJ2017 said:
... managed the 'SU' injection with help from the method description @ <br /> Hardmod Root (https://forum.xda-developers.com/hd...ot-hardmod-root-amazon-fire-hd-8-7th-t3851617)
Click to expand...
Click to collapse
Also, thanks @JJ2017 for pointing out that thread had the steps for manually patching in SuperSU.
I thought I remembered seeing it before, but couldn't remember where and majorly failed at finding it (meanwhile it's hiding out right under my nose LOL) Probably just too tired.
Anyone who does this successfully could share their patched system.img (preferably just a stock-rooted)

NFSP G35 said:
See the previous post (or more to the point, see the section "Writing SuperSU" in <br />'s thread...
Click to expand...
Click to collapse
Rather embarrassingly, I don't know what commands are required in terminal for copying, moving, and applying permissions to files...

niggabyte said:
I'm not great at Linux commands. Would anyone be kind enough to tell me how to modify the system image to include root?
Click to expand...
Click to collapse
niggabyte said:
Rather embarrassingly, I don't know what commands are required in terminal for copying, moving, and applying permissions to files...
Click to expand...
Click to collapse
No problem. Linux can be intimidating at first... Believe me, I've been there!
Fortunately, it's not hard to come up to speed and quite a rewarding experience.
Grab yourself a Linux cheat-sheet: https://www.google.com/search?q=linux+cheat+sheet&tbm=isch
I believe cp and chmod are mainly what you'll need.

NFSP G35 said:
See the previous post (or more to the point, see the section "Writing SuperSU" in <br />'s thread...
Also, thanks @JJ2017 for pointing out that thread had the steps for manually patching in SuperSU.
I thought I remembered seeing it before, but couldn't remember where and majorly failed at finding it (meanwhile it's hiding out right under my nose LOL) Probably just too tired.
Anyone who does this successfully could share their patched system.img (preferably just a stock-rooted)
Click to expand...
Click to collapse
I was about to ask the same thing, if someone want to share their rooted and preferably stock system images (like a MEGA link) i will put them on the main thread (with credits of course)
With my internet connection, upload my system.img will take forever

JJ2017 said:
BTW: used Fire OS 5.3.6.4 (most recent)
Click to expand...
Click to collapse
Their site says that 5.6.3.0 is the most recent: https://www.amazon.ca/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=202144610
Are we looking at the same thing?
I'm wondering because I just went through this process and now the tablet won't boot. It's stuck at the "fire" logo.
So where did you get your OTA file?

cybersaga said:
Their site says that 5.6.3.0 is the most recent: https://www.amazon.ca/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=202144610
Are we looking at the same thing?
I'm wondering because I just went through this process and now the tablet won't boot. It's stuck at the "fire" logo.
So where did you get your OTA file?
Click to expand...
Click to collapse
my guess is that you probably created a wrong symbolic link for app_process, the command should be something like:
Code:
ln -s system/xbin/daemonsu bin/app_process

t0x1cSH said:
my guess is that you probably created a wrong symbolic link for app_process, should be something like:
Code:
ln -s system/xbin/daemonsu bin/app_process
Click to expand...
Click to collapse
I did create that. I kept track of all the commands I typed. But I remounted the image to check and it's there:
Code:
[email protected]:~/Desktop# ls -l system/bin/app_process
lrwxrwxrwx 1 root root 13 Feb 8 17:09 system/bin/app_process -> xbin/daemonsu

cybersaga said:
I did create that. I kept track of all the commands I typed. But I remounted the image to check and it's there:
Code:
[email protected]:~/Desktop# ls -l system/bin/app_process
lrwxrwxrwx 1 root root 13 Feb 8 17:09 system/bin/app_process -> xbin/daemonsu
Click to expand...
Click to collapse
Should be (straight from the device)

t0x1cSH said:
Should be (straight from the device)
Click to expand...
Click to collapse
That makes a whole lot of sense! I'll try again.
---------- Post added at 06:47 PM ---------- Previous post was at 06:10 PM ----------
Hrm... now it's stuck at the Amazon logo. That's a step back.
I'll retrace my steps.

cybersaga said:
That makes a whole lot of sense! I'll try again.
---------- Post added at 06:47 PM ---------- Previous post was at 06:10 PM ----------
Hrm... now it's stuck at the Amazon logo. That's a step back.
I'll retrace my steps.
Click to expand...
Click to collapse
try to clear the cache from the recovery (power + volume down) and remember to flash boot.img from the recovery, if you forgot it the tablet will hang on the amazon logo