Related
Current Status 7/14
Without the NAND being unlocked, we are unable to re-write to the recovery partition. Other than that everything is working good. Unlocked NAND=One Click Root!
This method is directly based on the new root process for the Eris released on xda.
Original thread can be found here
The following information is taken directly from the thread mentioned above with some small modifications by me for the Incredible.
Big thanks to tereg for the toolkit and the guys who rooted the EVO with a file write/chmod race condition exploit that gave me the idea for this.
jcase noticed that a race isn't actually nessisary to exploit the chmod 777 on the file I've been working with, simplifying the script alot.
I used the files from the adb development pack that Tereg put together. Download them here. You don't need them for this root process as long as you have a working adb install.
You will need adb access. Install the android sdk for your platform (macos, windows, linux) get it for your OS here.
If you don't know how to install the sdk, search xda, there are a ton of howtos for that.
Files to download:
hack-v5-DINC.zip
A ROM file
Android SKD (skip if you have a working adb)
Instructions for linux/OSX.
Have adb in your path, or move the files contained in hack-v5-DINC.zip into your sdk/tools directory so your pushes will work properly.
FOR ALL OS's Make sure your phone has Applications->Development->USB Debugging turned on.
Do NOT have your phone in Disk Drive Mode, have it in Charge Only.
Open a terminal window in your /tools/ directory. Type this at the prompt.
Code:
sh runinlinux.sh
This will take a few minutes, follow the instructions on your screen.
If you get adb: command not found, edit runinlinux.sh and change every
Code:
#/bin/bash
adb push flash_image /data/local/
adb push recovery.img /data/local/
adb push testfile /data/local/
etc...
to
Code:
./adb push flash_image /data/local/
./adb push recovery.img /data/local/
./adb push testfile /data/local/
etc...
Instructions for windows (thanks tereg!)
Download the hack.zip file and extract it to the desktop. So, you have a folder on the desktop called hack. I would recommend moving or copying those files (EDIT: that are contained in the hack folder) to the C:\android-sdk-windows\tools folder. Why? Because the script runs "adb ____" commands, and unless you've set up adb to be able to run anywhere within the command prompt, the script won't run. So, it will universally work if the files in the hack folder are placed in C:\android-sdk-windows\tools
So, open a command prompt by pressing WindowsKey+R, or going to Start-Run (in WinXP) and typing
Code:
cmd
in the text box there and press OK
If you are in Windows Vista/Windows 7, go to the Start Menu, then type in
Code:
cmd
in the search bar in the lower right-hand corner of the start menu and press enter, and locate Command Prompt in the search results, or go to Start -> All Programs -> Accessories -> Command Prompt
Type
Code:
cd C:\android-sdk-windows\tools
and press enter
Now, I recommend pushing the ROM you want to flash to the SD card now.
Code:
adb push ROM.zip /sdcard
Then, type
Code:
runindos.bat
to execute the script.
You might have to run it 2 or 3 times for it to work. If it fails, just reboot the phone normally, then run
Code:
runindos.bat
again once the phone is booted back up and you're ready.
----------(Thanks again tereg!)
It will scan for a long time, give it at least 5 minutes. If it doesn't come back after 5 minutes cntrl +c to stop it, start the process again. MOST PEOPLE HAVE TO RUN THIS AT LEAST TWICE!
If your device reboots into a new screen with options on it, you now have root in recovery mode. At this point you will be flashing your Incredible's brains, so YOUR PHONE WILL BE BLANK AFTER LOADING A NEW ROM! All of your apps/numbers will be gone from the phone.
I suggest a nand backup first.
Download and copy one of these ROM's to your sdcard as update.zip and flash it with flash zip from sdcard by selecting "Install zip from sdcard".
The first boot after loading a new ROM takes quite a while to show any activity to the screen. Give it a good 5 minutes before you start wondering if it's ever going to come back.
---
runinlinux.sh
---
Code:
#/bin/bash
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
adb shell rm /data/local/rights/mid.txt
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
echo "Files copied and permissions set, rebooting HTC Andriod 2.1"
adb reboot
echo "Your phone will now reboot into normal mode, then reboot into recovery mode. If it does not reboot the second time, wait 10 minutes and manually reboot and begin again."
echo "Your phone is now rebooting in Rooted Recovery mode, do a backup and load your ROMs"
adb wait-for-device
adb shell /data/local/flash_image recovery /data/local/recovery.img
adb reboot recovery
---
runindos.bat
---
Code:
@echo off
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
adb shell rm /data/local/rights/mid.txt
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
echo "Files copied and permissions set, rebooting HTC Andriod 2.1"
echo "Your phone will now reboot into normal mode, then reboot into recovery mode. If it does not reboot the second time, wait 10 minutes and manually reboot and begin again."
adb reboot
adb wait-for-device
echo "Your phone is now rebooting in Rooted Recovery mode, do a backup and load your ROMs"
adb shell /data/local/flash_image recovery /data/local/recovery.img
adb reboot recovery
This thread is intended to be an think-tank, similar to the one on the eris forums where I got the idea from. Let the ideas flow!
has this been tested to work on the INC? if not why has this been posted.
outsid0r said:
has this been tested to work on the INC? if not why has this been posted.
Click to expand...
Click to collapse
uhm....do you read?
"This thread is intended to be an think-tank, similar to the one on the eris forums where I got the idea from. Let the ideas flow!"
no. this is not working yet. thats why the title even has {development} in it. the process is almost working, and this is a develpoment thread to work out the issue-which is also in big letters at the top...see where it says
"Without the NAND being unlocked, we are unable to re-write to the recovery partition. Other than that everything is working good. Unlocked NAND=One Click Root!"
So once we solve a much more difficult problem, the less difficult will be easier.
Makes sense.
We already know how to unlock the nand vs the exploit posted last night...also unrevoked will have it done In a few days anyway
Sent from my HTC Incredible using the XDA App
adrynalyne said:
So once we solve a much more difficult problem, the less difficult will be easier.
Makes sense.
Click to expand...
Click to collapse
the difficult problem has already been solved. the unrEVOked team already has the NAND unlocked. now its whether they want to share and make it a true one-click root method, or if they are going to keep it a secret and keep koush's clockworkmod recovery as the only possibility. this tool still uses the clockworkmod recovery, but after a NAND unlock your given the option to change. since koush is working for them too, im starting to think more and more that they are going to keep the monopoly.
im hoping that they will just incorporate their NAND unlock method into this root process. they can even re-lock it after the process is done as they do in their re-flash tool to preserve the monopoly, but a true one-click root is now possible with their co-operation. ive messaged them asking if they want to help out. we will see soon enough, so cross your fingers!
they can even re-lock it after the process is done as they do in their re-flash tool to preserve the monopoly
Click to expand...
Click to collapse
You just lost a ton of respect from me, and I suspect more than a few others. Talk about biting the hand that feeds you.
adrynalyne said:
You just lost a ton of respect from me, and I suspect more than a few others. Talk about biting the hand that feeds you.
Click to expand...
Click to collapse
So I see we have this starting up again....shakes head at OP..
@adrynalyne best to just ignore these people...its not like the winmo days is it man? Le sighe
Good advice, you are right. I will ignore this stuff in the future.
No, not like the winmo days at all. I've never seen so much anomisity and jealousy in a community before like there is for Android.
All I can say is we already intended to release this method, we were making a pretty robust obfuscation for it. But again the community has jumped before thinking and posted the bug for HTC to fix. There might not be any root's left after this one is burnt. Which it now is. Our tool will be released as is soon enough.
We don't care to create a monopoly, we happily work with others that ASK. Those that just jump and tell the world all the secrets we don't want plugged are just stupid, plain and simple.
adrynalyne said:
You just lost a ton of respect from me, and I suspect more than a few others. Talk about biting the hand that feeds you.
Click to expand...
Click to collapse
LOL Whatever, it isnt like respect from you is something anyone cares about. I like someone with the nerve to speak the truth no matter how unpopular it might be.
outsid0r said:
has this been tested to work on the INC? if not why has this been posted.
Click to expand...
Click to collapse
Please read. Think tank! I applaud this dude for trying. More than many others do here!
fader01 said:
LOL Whatever, it isnt like respect from you is something anyone cares about. I like someone with the nerve to speak the truth no matter how untrue it might be.
Click to expand...
Click to collapse
Fixed that for ya.
adrynalyne said:
You just lost a ton of respect from me, and I suspect more than a few others. Talk about biting the hand that feeds you.
Click to expand...
Click to collapse
Shadowmite said:
All I can say is we already intended to release this method, we were making a pretty robust obfuscation for it. But again the community has jumped before thinking and posted the bug for HTC to fix. There might not be any root's left after this one is burnt. Which it now is. Our tool will be released as is soon enough.
We don't care to create a monopoly, we happily work with others that ASK. Those that just jump and tell the world all the secrets we don't want plugged are just stupid, plain and simple.
Click to expand...
Click to collapse
it seems like my comment was taken the wrong way.
for one, clockworkmod recovery is the only one that works on the DINC AFAIK, amon_ras isnt working on here either.
the monopoly is basically a monopoly because of the lack of other available options, not necessarily because its enforced.
i apologize if it came off the wrong way or insulted anyone with the preceding comments.
i meant this thread as a co-operative think-tank, it wasnt my intention to start a big ordeal.
adrynalyne said:
Good advice, you are right. I will ignore this stuff in the future.
No, not like the winmo days at all. I've never seen so much anomisity and jealousy in a community before like there is for Android.
Click to expand...
Click to collapse
@adrynalyne yeah its a real rough community at times, but what ya gonna do right...its hard for me to ignore them at times too
@shadowmite. thanks for your guys hard work....the ignorant ones are everywhere nowadays, hope they don't get you guys down.
Cheers!
Shadowmite said:
All I can say is we already intended to release this method, we were making a pretty robust obfuscation for it. But again the community has jumped before thinking and posted the bug for HTC to fix. There might not be any root's left after this one is burnt. Which it now is. Our tool will be released as is soon enough.
We don't care to create a monopoly, we happily work with others that ASK. Those that just jump and tell the world all the secrets we don't want plugged are just stupid, plain and simple.
Click to expand...
Click to collapse
hmm. well i guess thats what happens when people try to help out the community...maybe next time i just wont do anything... :/
and FYI...i did contact you. i sent you a PM earlier today.
this method has been used on the EVO and hasnt been plugged, and its been in the works on the Eris-also an HTC phone- for quite a long time, and in the same way this is...a co-operative community effort to make the phone the best that it can be.And its still not been plugged.
id worry less about HTC plugging the exploits and more about getting the exploits available to the public.
Correct, you are not the original one leaking the method. But my point is devs capable of finding things like this should be capable of thinking about it being plugged. HTC fixed our recovery hold in the next OTA. Now it's quite possible nand and this root will be patched also. we have NO OTHER WAYS IN... Thats it. besides some VERY complicated exploits we are OUT after the next ota.
I got your pm's, but only after you posted this.
It's a moot point, our one click root is due out in a few minutes. we were going to further lengths to protect the method, but it's out anyway at this point.
Shadowmite said:
Correct, you are not the original one leaking the method. But my point is devs capable of finding things like this should be capable of thinking about it being plugged. HTC fixed our recovery hold in the next OTA. Now it's quite possible nand and this root will be patched also. we have NO OTHER WAYS IN... Thats it. besides some VERY complicated exploits we are OUT after the next ota.
I got your pm's, but only after you posted this.
It's a moot point, our one click root is due out in a few minutes. we were going to further lengths to protect the method, but it's out anyway at this point.
Click to expand...
Click to collapse
well i apologize for the fact that i may/may not have ruined your chances to make a big announcement for your release, but IMO its kinda bs that you keep the info on lockdown. the whole point of android is that its open. a select amount of people shouldnt consider themselves the gatekeepers of important information.
ban_dover said:
well i apologize for the fact that i may/may not have ruined your chances to make a big announcement for your release, but IMO its kinda bs that you keep the info on lockdown. the whole point of android is that its open. a select amount of people shouldnt consider themselves the gatekeepers of important information.
Click to expand...
Click to collapse
From our wiki, which you appearently haven't read:
http://unrevoked.com/rootwiki/doku.php/public/unrevoked2
That doesn't seem fair! Android is about open source.
In some senses, we agree; but at times, a tradeoff needs to be made. Releasing the source code for this, we believe, would compromise the greater ability to unlock devices like these in the future. Given the choice between sacrificing the liberty of running code on our handsets and the liberty of reading the code by which we unlock it, we feel that the millions of handsets are more important. It is unfortunate that we must make such a choice, and we look forward to the day in the future that no such decision need be made.
Click to expand...
Click to collapse
Shadowmite said:
From our wiki, which you appearently haven't read:
Click to expand...
Click to collapse
already read it.
i dont take my opinions from things i read. i take the information and draw my own conclusions. and in this case my conclusion is that, while i can see your point i still disagree.
Hi guys
Well, I had an Atrix for a few days, but had some issues with AT&T and had to return it and deal with some customer service issues before I can re-purchase the device. I didn't let that slow me down though
While I had it, I made a few dumps of the NAND, and have been working on disassembling things. Thanks to the help from a number of great people on IRC (#xda-devs irc.freenode.net) I have been able to successfully change the Bluetooth and Wi-Fi MAC addresses, and discovered a way to write to the flash, bypassing the bootloader security.
The full writeup can be found at pocketnow.com
I will be posting more info about the bootloader bypass as soon as I get it 100% working, right now we are able to write data directly to the NAND, bypassing bootloader security, and also provide a false signature, allowing the device to boot. However there are some remaining issues (a custom kernel that was flashed to the device failed to boot properly) - stay tuned
You the man, thanks for the efforts !
Sweeeet!
Wonderful work!
Excellent, can't wait to see the end result. Hopefully custom kernels and ROMs will be coming soon.
Devs you guys are amazing! Thank you for the hard work that is put into all this! I know the challange is fun for you all, but it really helps us non dev ppl out a lot!
Sent from my MB860 using XDA App
nicely done Da-G.... great work as always glad to see you again and i hope to continue using your work as i did back in old winmo cooking !!!
quick question, is there really a reason why to change the bluetooth/wifi MAC drivers??? are there any benefits or basically just the same exact reasons when you do it on pc's
Main reason to change MAC address is to be able to join Wi-Fi networks that have whitelisting.
You could also use it to simplify device administration on your network.
Beyond that I can also imagine a few black-hat reasons to do it
Atrix is one of the few smartphones that can pull it off easily though, others I am aware of are the LG Optimus One and the SGS series (although it's not so easy on SGS)
There are plenty of other interesting datas in /pds, it is the device provisioning partition (NVRAM) and is equivalent to /efs on the i9000/Captivate (which is the last device I used, so easy for me to compare with)
Careful messing with it though, on the Captivate changing the wrong bit would kill your cellular radio until you restored an EFS backup, I suspect the same danger is here with the Atrix too! And we don't have a quick way to restore a PDS backup yet like with odin on SGS (although I am hot on the heels of a method to do so)
Omfg I'm excited! If this device gets real ROMs an even custom kernels, its going to be an even more amazing device
Sent from my MB860 using XDA Premium App
i'm exited about the bootloader bypass, i thought the firmware would do a complete checksum of it, so if it's partial then we should be able to find out exactly what gets checked.
i'm curious to see if you have been able to find something regarding sim unlock, just like the sgs was holding the lock very easily changeable with a simple hex editor. i bought the code already but maybe other people will get lucky
I've asked for a backup of /pds prior to and after locking over in the general forum, hopefully a few people can send those my way. I suspect a good hard look at that will reveal the location and provide an easy unlock method (I think I located it already, but as /pds is not restored via flashing the leaked SBF, i'm loathe to have someone else try it in fear of brickage)
I'll hammer it out once I get my device back in hand, whenever AT&T decides to allow me to purcahse
Da_G said:
I've asked for a backup of /pds prior and after locking over in the general forum, hopefully a few people can send those my way. I suspect a good hard look at that will reveal the location and provide an easy unlock method (I think I located it already, but as /pds is not restored via flashing the leaked SBF, i'm loathe to have someone else try it in fear of brickage)
I'll hammer it out once I get my device back in hand, whenever AT&T decides to allow me to purcahse
Click to expand...
Click to collapse
i will do it, but i am getting a permission denied.
Code:
C:\Users\fjleon\Desktop\android-sdk-windows\platform-tools>adb shell tar zcvpf /
sdcard-ext/pds-backup.tar.gz /pds/
tar: can't open '/sdcard-ext/pds-backup.tar.gz': Permission denied
i tried adb shell su and accepted super user on the phone, but i still cannot do it
wow bypass= custom roms...... this would be ingenious hope u get it working....
how does rsd lite 5 flashing work??? it seems to create an image and then re sign it.... would backtracking and try to use the same method work?
@franciscojavierleon:
Make sure you don't have usb internal/sd storage mounted when you issue the command, or the sd card will be unaccessible from device
@ahjdmarchi:
I didn't study the program too much yet. I'll look to that if the current method i'm working on proves to be a failure
Da_G said:
@franciscojavierleon:
Make sure you don't have usb internal/sd storage mounted when you issue the command, or the sd card will be unaccessible from device
@ahjdmarchi:
I didn't study the program too much yet. I'll look to that if the current method i'm working on proves to be a failure
Click to expand...
Click to collapse
heres a tattoo that i have on my chest
"failure is not an option" good luck brudda hope all turns well
Da_G said:
@franciscojavierleon:
Make sure you don't have usb internal/sd storage mounted when you issue the command, or the sd card will be unaccessible from device
Click to expand...
Click to collapse
i unmounted it and tried again and still get the same error. i killed root explorer first since i had it open and no dice
@franciscojavierleon:
Try this instead.
Code:
adb shell tar zcvpf /data/local/tmp/pds-backup.tar.gz /pds/
adb pull /data/local/tmp/pds-backup.tar.gz
adb shell rm /data/local/tmp/pds-backup.tar.gz
RadioComm
You really need to take a look at RadioComm if you haven't yet.
The BT MAC address can be edited directly in the NVM on all Motorola devices.
On CDMA chipset devices it is located in seem 01bf record 0001 bytes 0006 and there is also a module and special set of TCI commands for managing this called HOB restore.
There are also flags set in the firmware for whether the HOB is verified during the flash cycle or not.
just an FYI!
@cellzealot:
Checked out RadioComm already, but none of the commands work for Atrix. Have you tried it? Perhaps you have a more updated version?
Edited. Nevermind just saw you needed it before unlock as well. I've got my PDS folder from my unlocked phone if you need it (not sure)
i should get my unlock between today and tomorrow, so with my locked pds backup i will do a diff to see if anything gets changed at all.
Howdy all XDA Folks!
To you, I present ClockworkMod Recovery on the LG Revolution 4G
After many hours of late-night coding and testing by some fearless testers who, without though for their device's safety, allowed me to test building ClockworkMod Recovery despite the fact that I don't actually own this device!
First of all, let me get a few things out of the way:
Credits:
Special thanks to the following people for helping out in one way or another...
Majorpay
birdman
Nemith
Fattire
STACKS (initial testing)
Koush / CyanogenMod team for ClockworkMod
Super special thanks to those who've donated so far!
Click to expand...
Click to collapse
General Information
This is BETA software! There are no guarantees that this won't instabrick your device. That's not to say it hasn't been tested, but if you happen to not follow directions or just have bad luck in general, I can't be blamed for your misfortune.
Click to expand...
Click to collapse
Requirements
To use this, you must:
be rooted
have ADB shell access to your phone; and
be able to follow directions EXACTLY
Click to expand...
Click to collapse
Downloads
To download the first release of ClockworkMod Recovery for the LG Revolution 4G, use the following download links:
[SERVER 1] http://bit.ly/iVa1Kx
[SERVER 2] https://github.com/downloads/thecubed/android_device_lge_revolution/recovery-cwm-pr1.tar.gz
Code:
# md5sum recovery-cwm-pr1.img
a1c61d06fa0f029411cf4cde44639b3f recovery-cwm-pr1.img
Check md5sum before flashing!
Click to expand...
Click to collapse
Instructions
This is what everyone's been waiting for, isn't it?
You sure you don't want to take a jog, or get some fresh air first?
Okay. You're sure. I won't try to change your mind.
I will, however admonish you-- follow these directions EXACTLY.
If you don't, I can't guarantee that your phone will work afterwords.
To begin, download the .tar.gz file from the above links, and extract it somewhere easy, like c:\android (on windows) or ~/android (on linux/OSX)
Let's check the md5sum of the extracted file.
If you're in linux, run
Code:
md5sum recovery-cwm-pr1.img
It should match EXACTLY the md5sum posted under the download link. If it doesn't STOP. You have either not extracted it correctly or the download was bad. Try again until you get the correct md5sum.
If you're on windows, you'll have to find a md5sum application to download.
Once you've got the file extracted correctly, we need to copy it to your phone.
You can either put it on your Internal SD card using the storage mode over usb, or through ADB.
If you choose to do it through ADB, just use
Code:
adb push <path/to>/recovery-cwm-pr1.img /sdcard/
Make SURE that you copy the .img file, not the .tar.gz file!
After you have the recovery copied to your SDcard, it's time to install it on your phone.
ADB shell into your phone.
Once you're adb shell'd into your phone, make sure you have superuser access by typing
Code:
su
and your prompt should change from a "$" to a "#"
Now, let's backup your original recovery image, just in case. Issue
Code:
cat /dev/block/mmcblk0p14 > /sdcard/recovery-original.img
to back up your original recovery image for a rainy day. Keep that safe!
Once we've got that backed up, let's copy over the new recovery image.
Code:
cat /dev/zero > /dev/block/mmcblk0p14
cat /sdcard/recovery-cwm-pr1.img > /dev/block/mmcblk0p14
You'll get an error on the first command, something like "no space left on device". That's okay, we're just clearing out the orignal recovery image.
Now, we MUST check to make sure that our push of recovery worked. Let's run md5sum on it.
Code:
busybox md5sum /dev/block/mmcblk0p14
Should return back the same hash as above in the download section. If it does not, STOP! Post here explaining, and get a developer's attention ASAP.
Lastly, let's make a backup of your MISC partition. This is not required, but is HIGHLY recommended.
Code:
cat /dev/block/mmcblk0p8 > /sdcard/p8-backup.img
This helps us incase somehow your phone gets gunged or weird things happen.
Congrats! You now have ClockworkMod Recovery installed!
Click to expand...
Click to collapse
Accessing Recovery
To access recovery, power off your device and hold VOLUME DOWN and POWER until you see the LG logo.
You will be asked to confirm a 'wipe' of your device. Don't worry! Our custom recovery ignores this.
Your datas will be perfectly safe.
Click to expand...
Click to collapse
Pictures!
Here's a few screenshots from Majorpay's device:
http://i.imgur.com/DYfNK.jpg
http://i.imgur.com/Q7qE4.jpg
Video!
How to access ClockworkMod Recovery Youtube Video: http://www.youtube.com/watch?v=FLb5VJTEDL8
Click to expand...
Click to collapse
Donation Information
I love to develop. I don't do this for money, I do it just for the "thanks".
However, I don't actually own a Revolution-- I'm not even on Verizon!
If I can get enough donations together, I will have my friend purchase the device on contract for $250 at a Verizon retail location.
With that device, I plan on doing quite a lot- creating stock 2.2 roms, attempting to port CyanogenMod7 and a bunch of other awesome things.
Please don't feel obligated to donate, but if you feel like it, you can click the button below to donate any amount you wish to me.
Thank you in advance!
Click to expand...
Click to collapse
Contact Me!
Got an issue with this release? Post here!
Want to contact me privately? PM me on XDA or Rootzwiki
Twitter your thing? Follow me, @tylerfixer on Twitter
Join the official LG Revolution dev IRC channel at freenode on #lgrevolution
I'm IOMonster on IRC!
Click to expand...
Click to collapse
Technical information
Breakdown of the LG software posted by me here: http://www.wiki.rootzwiki.com/wiki/index.php/LG_Revolution_Software_Breakdown
Source will be released as soon as I figure out how to merge all my changes to recovery/minui/graphics.c into my device directory
Click to expand...
Click to collapse
A bunch of thanks for all your hardwork guys...
thats great news, so when and how do we get it!!!!!!!!!!
I'm sleeping now, so most likely tomorrow afternoon
In all honesty, I need to do a few more "sanity checks" to make sure that this is 100% safe to release. Right now it's not.
The sanity checks won't take very long, I just have to sit down and think for a while--but right now my brain's out of "go-juice", so I'm going to head back to bed
Great Job Guys!! Ready to install it.
cubed types in his sleep! Cubed, I re-uploaded the copy of p8 I have on my dev box and ran an md5 between the two locations, so if it's still off, I don't know what to say.
Good afternoon all!
I have a few chores to run today, but as soon as I get back, I will select a few testers on IRC to begin round 2 of testing.
The problem I am facing (very minor issue) is that the MISC: partition image (p8) seems to have shrunk by 1 byte (yep, majorpay- the dump is 1 byte off, everything's shifted by 1 byte to the right).
I'd like to see if this happens reliably on other devices. There is no bricking risk, the only thing I ask is that you have your phone rooted, you have knowledge of the linux command prompt, and are willing to let me teamviewer in to your desktop if something goes awry.
Thanks everyone for your patience and kind words
thecubed said:
Good afternoon all!
I have a few chores to run today, but as soon as I get back, I will select a few testers on IRC to begin round 2 of testing.
The problem I am facing (very minor issue) is that the MISC: partition image (p8) seems to have shrunk by 1 byte (yep, majorpay- the dump is 1 byte off, everything's shifted by 1 byte to the right).
I'd like to see if this happens reliably on other devices. There is no bricking risk, the only thing I ask is that you have your phone rooted, you have knowledge of the linux command prompt, and are willing to let me teamviewer in to your desktop if something goes awry.
Thanks everyone for your patience and kind words
Click to expand...
Click to collapse
Since it didn't happen between Dev and FTP, where do you suppose this happened?
I'm thinking the cat command may have messed with it, I'll try pulling it using dd next time.
I think I'll just grab an image of it within android (FACT_RESET_6), and another from within recovery (FACT_RESET_3) to get a better baseline, since the p8 image we have now is from a while ago, let's see if maybe the original image is bad.
I'm just not sure why the whole image would shrink and suddenly be offset by 1 byte... it's strange to do all that (shifting everything by 1 byte) just for recovery mode...
Clearly it didn't affect the operation last night, so it must have been on the pull. So in need of more testing tonight? (hopefully earlier)
And just to set your mind at ease that we may be cluttering up your release thread, I'll go back and edit on release with "Woots!!!" or something. I probably should have used PM. My bad, just thought of that.
I'm with my friend right now, he's probably going to get this phone either today or tomorrow.
We'll go for another round of testing tonight around 7pm Pacific time.
To all who've donated so far--thank you so very much! I will be getting you guys a customized build with any features you like added (custom colors, background image, you pick) as a thank you.
I'll post here when I get home and am ready to do the final round of testing before public release.
thecubed said:
I'm with my friend right now, he's probably going to get this phone either today or tomorrow.
We'll go for another round of testing tonight around 7pm Pacific time.
To all who've donated so far--thank you so very much! I will be getting you guys a customized build with any features you like added (custom colors, background image, you pick) as a thank you.
I'll post here when I get home and am ready to do the final round of testing before public release.
Click to expand...
Click to collapse
Ready whenever... I'll be hanging out with the daughter until you post in.
I'm back! Head over to IRC whenever you all are ready!
Dont know hiw to get to IRC. Can anyone tell me.Sorry for the noob question.
Sent from my VS910 4G using XDA App
List of fixes for private beta build "recovery-cwm-pr1"
Stuck-in-recovery issue is now fixed, thanks to a strategically added "sleep" command
Cursory test of nandroid backup (not restore) is complete, restore should not brick your device.
CPU governor set to "ondemand" as opposed to "performance" to help alleviate some system stability issues with ADB.
Public release candidate build "recovery-cwm-rc1" will be built here shortly and available for public consumption.
Stick around!
rstout01 said:
Dont know hiw to get to IRC. Can anyone tell me.Sorry for the noob question.
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Head to http://webchat.freenode.net
Set a nickname, and join the channel #lgrevolution and join the fun!
It's released! Wooooo oo oooooooo!!!
EDIT: I will be at the beach tomorrow around 3PM Pacific Time until 8 or 9PM, so if I don't respond, it's because I'm enjoying some well-deserved sunshine
Amazing. I just bought my Revo because of this. You're the man! Enjoy the beach!!
Excellent work! Now I can finally get some much needed rest
Sorry I wasn't able to stick around to do the deodexing. I'll get to that soon. This morning, I didn't wake up on time (4 alarms failed to wake me up), and my daughter almost missed her appointment! Oh well, at least I got 5 1/2 hours of sleep in last night.
Look forward to working again with you in the near future if you're feeling up to it.
My resources are at your disposal if you need a hand. Lets just try to work on getting more human hours into the mix... ha!
(oh, and enjoy your day at the beach!)
I'm back!
If anyone's around, and has questions, I'll be on IRC or you can post here...
http://forum.xda-developers.com/showthread.php?t=1119555
Logically speaking, this application should also work with the Bionic correct?
Just wondering, if its deemed safe in this thread to attempt using, I will try it and post back with results.
---------- Post added at 12:30 AM ---------- Previous post was at 12:08 AM ----------
Okay, so I just backed up everything and tried the app, which won't work due to the fact that it checks the phone model number, Theres a manual guide to get ubuntu running on the atrix, and I'm going to start from scratch there. Probably going to be a couple of days before I do anything since I need a new microhdmi...
I tried the app that comes with it to partition the sdcard but it does a device check then it stops with an error message that the device is not an Olympus (Atrix). Maybe we can get the dev to check on the differences, albeit small, for the Atrix and the Bionic.
Worth a shot. I've been playing around with /osh for a few days but had to reflash to stock due to the lapdock staying on the screensaver.
Hey guys, I am working on the same thing at the moment trying to port over Sogarth's method of unlocking the 10.10 maverick build of Ubuntu on our phones.
http://forum.xda-developers.com/showthread.php?t=1000316
The link here is for his old automated .bat script he made for the Atrix that I believe will work for our phones with a little modification to it to reflect Maverick packages instead of the Jaunty packages for their phones.
Please jump into the irc in my sig because I would like to get this going as well.
I would hop in IRC but I'm about to head out the door.
I'm currently approaching this situation from two directions:
1.) I'm dumping /osh/ (webtop partition) and uploading it to dropbox as soon as I can get a complete dump. (hopefully tonight) and providing it to the original Atrix dev to see if he can hook us up with an app to help do whats needed
2.) I'm also attempting the manual method as soon as I get a new microHDMI cable (I was using a cheap adapter).
You are 100% correct though, you should be able to get that install script working just by changing the packages to reflect the updated Ubuntu. MAKE SURE you backup ANY files before you change them (and preferably a complete backup of /osh/. Since we have SU on our phones we have free reign over the /osh partition, so be careful in there.
OT: I can't wait until we can get on-demand CPU overclocking for this thing... if it clocks as well as past mobile chips... Toggle 1.2-1.4ghz and plug it in the LapDock. You'd have a damned fine netbook...
(Not necessarily talking to any experienced users or noobs, the disclaimer about Linux & SU is for everyone reading this thread - I'm relatively experienced in the Linux world... and I need to be reminded of SU's power sometimes.)
I just realized that their phone's Ubuntu distribution is under the 9.x series versus the 10.x series. A lot of Major changes happened to Ubuntu between 9.x and 10.x that affected the way the operating system talked to devices and booted, they stopped using HAL and moved to a new boot method, I am uncertain whether or not the install script will work or not, though I'm somewhat confident it will, given the nature of webtop (Android does the hardware abstraction, and the booting, we just run a second set of executable's on a different X window session attached to a different display) This should mean that the portions that would normally prevent us from just duplicated the script are omitted from the Ubuntu distribution entirely. As long as we keep a backup we should still be fine.
No worries, just remember to keep FXZ and RSD handy. I've screwed up the /osh partition a couple times but that has saved me from complete disaster so far
Good call on bringing this up. Let me know if you need to test anything for this.
@xaero252
So I modified Sogarth's script to use Maverick build of all the tools it downloads and installs but the problem with the script is that it needs the phone to have the ro.secure=0 so that ADB always launches with root access without manually initiating su each line of code. I am not sure if there is a way around it or if we have to modify the script differently. Anywho, I've upload a copy of the work I've done to the script.
Is it just an sh script? If so and ut doesn't reboot the phone at all you could launch a SU terminal and do "su sh script.sh"
oh i see the issue now... we would have to be able to edit the boot loader for that method... if i'm correct though his android app doesnt use the pc for much... if you change that variable on boot do you think it woukd work?
Hmm, I have an idea, its not as polished as the pc based script, however it should still work presuming you can get a SU terminal to run on the phone ( I happen to have one running right now ) I'm going to see if I can't adapt that to a bash script. probably going to take a while.
Curiously we happen to have a 1.5gb partition for Ubuntu on built in memory, where as the atrix only had a 600 or so mb partition... This is great because we should likely be able to continue to install /, /boot and such to internal memory, and use the sd card (even left as ntfs) for /home...
Couple of things: reading through the script it looks like 100% of the commands he runs could be run on the phone via a bash script run as su. The idea is this: convert the entire script over to bash, copy the script, and the required files to the phone, and execute the script from the phone. The only other concern I can see is the wget package included with the script not being compatible with maverick, which doesn't seem likely.
I'm gonna start working on rewriting the script linux native. My idea is to use a terminal emulator (they are free on the market) and run su script.sh and pray. I need to get a new microHDMI before I do this though, so I can test my results reliably.
xaero252 said:
Is it just an sh script? If so and ut doesn't reboot the phone at all you could launch a SU terminal and do "su sh script.sh"
oh i see the issue now... we would have to be able to edit the boot loader for that method... if i'm correct though his android app doesnt use the pc for much... if you change that variable on boot do you think it woukd work?
Click to expand...
Click to collapse
As far as correcting that, no one has attempted doing custom kernels yet so to do the edit to get root access out of the gate is moot at this point.
Hmm, I have an idea, its not as polished as the pc based script, however it should still work presuming you can get a SU terminal to run on the phone ( I happen to have one running right now ) I'm going to see if I can't adapt that to a bash script. probably going to take a while.
Click to expand...
Click to collapse
Your linux skills are probably 10 folds better than mine but I believe if you convert my modified script, which has all the necessary links to the correct packages for our phone, then it might just work.
Curiously we happen to have a 1.5gb partition for Ubuntu on built in memory, where as the atrix only had a 600 or so mb partition... This is great because we should likely be able to continue to install /, /boot and such to internal memory, and use the sd card (even left as ntfs) for /home...
Couple of things: reading through the script it looks like 100% of the commands he runs could be run on the phone via a bash script run as su. The idea is this: convert the entire script over to bash, copy the script, and the required files to the phone, and execute the script from the phone. The only other concern I can see is the wget package included with the script not being compatible with maverick, which doesn't seem likely.
Click to expand...
Click to collapse
The WGET I packaged in the .zip is the correct for Maverick along with all the files in the \bin directory are corrected to match our phone. If you can convert all this to a bash script, that would be awesome instead having to do each command via ADB Shell. The only problem I had with this is every time I tried to run the DPKG command on the .deb I downloaded manually, it threw up an error saying it could not find the file or destination.
On a side note, you are correct that we have 1.5gb partition opposed to their 700mb so we could honestly forget the part about creating a ubuntu.disk on the /data partition and modify the /osh directly for now until the time we need more space. After that, we can see if Sogarth will incorporate your script into his Webtop2sd app or we could make a 3gb ubuntu.disk on the /data partition since we have plenty of space there.
I'm gonna start working on rewriting the script linux native. My idea is to use a terminal emulator (they are free on the market) and run su script.sh and pray. I need to get a new microHDMI before I do this though, so I can test my results reliably.
Click to expand...
Click to collapse
Make sure you get the adapter as well to trigger Webtop cause at the moment our phone wont do webtop directly over HDMI without the HD Dock, Webtop adapter or Laptop dock. If you want to test the script out for now, hit me with the script and I will test it for ya
just wanted to let all you developers know you kick ass..... i had a jb rooted ahd running batakang rom and loved it until it had an unfortunate meeting with the tire of my fullsize truck this morning....replacement from att store come with stock jb on it ....ive never used linux before and really dont think i can handle the root process for jb (especially after reading the posts from ppl alot smarter than me that were having problems.....looking forward to a simpler method like motofail....thanks again for all of your help and looking forward to making my ahd scream again
jaydheat said:
just wanted to let all you developers know you kick ass..... i had a jb rooted ahd running batakang rom and loved it until it had an unfortunate meeting with the tire of my fullsize truck this morning....replacement from att store come with stock jb on it ....ive never used linux before and really dont think i can handle the root process for jb (especially after reading the posts from ppl alot smarter than me that were having problems.....looking forward to a simpler method like motofail....thanks again for all of your help and looking forward to making my ahd scream again
Click to expand...
Click to collapse
It is a piece of cake trust me. Before I rooted my AHD I had never used Ubuntu or any form of Linux. I download Unbuntu and made the liveCD, and literally copied and pasted every command from the thread into the terminal in Ubuntu, then just followed the instructions on how to connect the phone. Worked first time, no issues. Just grab a cup of coffee, take your time, copy and paste and you will have root in no time,
brett_day said:
It is a piece of cake trust me. Before I rooted my AHD I had never used Ubuntu or any form of Linux. I download Unbuntu and made the liveCD, and literally copied and pasted every command from the thread into the terminal in Ubuntu, then just followed the instructions on how to connect the phone. Worked first time, no issues. Just grab a cup of coffee, take your time, copy and paste and you will have root in no time,
Click to expand...
Click to collapse
The hardest part is probably making the liveCD :laugh:
this is a one-click tool for the "hardest" part..
enjoy!
http://www.linuxliveusb.com/
jaydheat said:
just wanted to let all you developers know you kick ass..... i had a jb rooted ahd running batakang rom and loved it until it had an unfortunate meeting with the tire of my fullsize truck this morning....replacement from att store come with stock jb on it ....ive never used linux before and really dont think i can handle the root process for jb (especially after reading the posts from ppl alot smarter than me that were having problems.....looking forward to a simpler method like motofail....thanks again for all of your help and looking forward to making my ahd scream again
Click to expand...
Click to collapse
I rooted my AHD tonight and it was my first experience ever using Ubuntu. It took me a while to figure it out, but once I got started it was a cake walk. Like someone else said, the hardest part is probably making the LiveCd/usb. I'm not sure why, but I couldn't ever get Ubuntu to work properly in VirtualBox so I ended up just booting my LiveUSB and opening the instructions on my tablet and doing it. It's super easy. Just do exactly what it says.
Oh, and it took me a little while to figure out just how to open a terminal in Ubuntu (ctrl+alt+T). If you're as much of a noob with this as I am knowing how to open a terminal will save you some time right from the get-go.
Good luck!
Google is your friend
any help?
ok so I ran Ubuntu and i cannot get my AHD to connect to the remote server i have entered everything as the instructions said all i get is an error that says that i need to repair my network is there a way to fix this?I really want my root back guys any help ?
EDIT:I have fix this by restarting my router excuse my my questions
very sorry
jelly bean root issues
hey guys just a few questions trying to root my ahd....im using ubuntu 12.04lts live cd
just a few issues
first
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
samba : Depends: samba-common (= 2:3.6.3-2ubuntu2) but 2:3.6.3-2ubuntu2.3 is to be installed
Depends: libwbclient0 (= 2:3.6.3-2ubuntu2) but 2:3.6.3-2ubuntu2.3 is to be installed
Recommends: tdb-tools but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
[email protected]:~$ sudo gedit /etc/samba/smb.conf
this is what i get when i install samba
also when i try to restart it says
[email protected]:~$ sudo restart smbd
restart: Unknown job: smbd
also prolly a stupid question but when i try to do the file manager it says cannot connect to remote host,
ive tried resetting my router and restarting both my phone and computer and nothing works...help
:
So yeah...
I was wondering, if any "recent" version of Ubuntu would work for the root...
Main reason for asking this was because I had a Live USB With 10.04
That and the PC i'm stuck with ATM just can't seem to handle 12.04...
[EDIT]
Never mind, I'm getting Lubuntu...
[EDIT]
I keep getting this error when trying to install samba in my lubuntu (persistent) usb...
Personally, I find these errors to be very annoying, as all I want to do is root my phone...
So, at the moment, I can't install Samba, can't "sudo gedit..."
[email protected]:~$ sudo apt-get install samba
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
samba : Depends: samba-common (= 2:3.6.6-3ubuntu1) but 2:3.6.6-3ubuntu5 is to be installed
Depends: libwbclient0 (= 2:3.6.6-3ubuntu1) but 2:3.6.6-3ubuntu5 is to be installed
E: Unable to correct problems, you have held broken packages.
[email protected]:~$
i got it...
thanks for all your help, you guys roick finally rooted on stock jelly bean btw used ubuntu 12.10 on usb worked great first time no problems
Lubuntu Variant
I noticed for Lubuntu, its a slight variant as opposed to the basic Ubuntu instructions...
Instead of gedit, you can substitute leafpad instead...
"sudo leafpad /etc/samba/smb.conf"
Oh and I think I solved my earlier problem after installing the "sessioninstaller" from the Synaptic Package Manager... (Use the search function.)
My only issue ATM is when I'm in the terminal and I try and use "sudo restart smbd" and it doesn't seem to work.
It merely tells me smbd isn't a process...