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 chaps,
I've just bought a Galaxy tab with plans to port Meego to the device.
I'm new to all the Android stuff, and tbh the myriad methods for doing this/that/the other and the relative lack of explanation of what's actually being done in these various methods/tools is quite confusing (and worrying).
So, if you'll bear with me, I have a few questions which are probably quite basic.
I've rooted my Tab using SuperOneClick, no problems there, I also understand that there is a leaked flashing tool called (Multi)Odin and an open source flashing tool called Heimdall. I understand adb.
So onto the questions:
Before I start messing about, how should I backup my existing firmware image? I see people talking about taking image dumps using dd, or Odin or Heimdall. What is the preferred method? And how should one then restore the device from these backups?
Alternatively is it possible to simply download the firmware directly from Samsung (I see links to later firmware, but really I'd be happy with what I have currently - P1000XXJK5 and FROYO.XWJJ7)?
I'm assuming that the best installation method would be to replace recovery, then I can add my own kernel and have it boot a rootfs mounted on the external SD card for example. Any thoughts?
I've seen one thread about people compiling their own kernels, with panics and the like which are solved by giving the full path to the initramfs extracted from the existing image. Any clues as to why the built version doesn't work? This is not so important as I can have a look at this when I build the Samsung source.
Is anyone looking at the bootloaders? Is there any information anywhere about them (as changing the bootloader to allow selection of the kernel to be booted would make life easier)?
Thanks for your patience!
Ok, so to partly answer myself, I see www dot samfirmware dot com has links to downloads of firmware images.
I'd really prefer to generate my own image of what's currently on the device rather than trusting a download site, but I guess it's better than nothing. Does anyone know how these images were generated anyway?
lardman said:
Ok, so to partly answer myself, I see www dot samfirmware dot com has links to downloads of firmware images.
I'd really prefer to generate my own image of what's currently on the device rather than trusting a download site, but I guess it's better than nothing. Does anyone know how these images were generated anyway?
Click to expand...
Click to collapse
Samfirmware get their images direct from Samsung insiders. They are not dumps.
If you want to dump from your device search "rotobackup" here in the dev forum.
Sent from my GT-P1000 using Tapatalk
alias_neo said:
Samfirmware get their images direct from Saunaing insiders. They are not dumps.
Click to expand...
Click to collapse
Ok that's reassuring.
alias_neo said:
If you want to dump from your device search "rotobackup" here in the dev forum.
Click to expand...
Click to collapse
Great, just what I was looking for, many thanks
So some more questions:
Any limit to the size of the kernel? Presumably just the size of the partition (which after extracting the image for backup seems to be a pretty large 15.4MB)?
What do all the .rc files in the raminitfs do? They are as follows: fota.rc, init.goldfish.rc, init.rc, init.smdkc110.rc, lpm.rc, recovery.rc
The init.rc is the normal init.rc file, so that's fine. Presumably the recovery.rc file is run if the bootloader detects that recovery mode is wanted (holding down keys during boot). The init.goldfish.rc? I guess this is to do with the emulator, though why it would be in a release image I don't know.
I assume that init.smdkc110.rc is automatically run somewhere along the line, though I don't see where it's started.
Any thoughts on lpm.rc and fota.rc? Are multiple .rc files run for the normal and recovery boots?
Thanks
lpm.rc is for low power mode that displays battery charging animation
goldfish is for running the rom under qemu.
backup your rom using rotobackup. compile samsung's kernel from sources, mix up default initramfs with meego's init scripts. pack all Meego stuff into loop mounted disk image. then flash zImage to kernel and your disk image to factoryfs using heimdall. I assume you have experience hacking N8xx/N900 and Maemo or Meego?
factoryfs is around 300MB so I think it should fit Meego and it (and kernel) can be easily restored with heimdall.
Thanks for the comprehensive reply
Yes I do have experience hacking Maemo/Meego, though have never really had to fiddle with init scripts before and this is as good a reason as any to learn.
I'd actually like to dual boot, so am modifying recovery.rc to bring up the Meego system on the external SD card.
Am just fiddling about building extra kernel modules now (needs btrfs for my image for example) and modifying the recovery.rc file.
Hmm, well I was all set to go and flash my new zImage and was looking for the heimdall command line, when I saw this at the top of one of the threads in this part of the forum (http://forum.xda-developers.com/showthread.php?t=870690):
Restoring to factory after using this process (you need using stock images):
heimdall flash --kernel stockzImage --recovery stockzImage --factoryfs factoryfs.rfs
Click to expand...
Click to collapse
Which has made me worry a bit that I've missed a recovery partition with its own kernel and wrongly assumed that the same kernel is used for both recovery and normal running, just with a different .rc file to be interpreted by init.
Any thoughts?
Do we trust the partition sizes reported here: http://forum.xda-developers.com/showpost.php?p=9471190&postcount=14
They seem very small for the kernel partition. I used RotoHammer's dd method to grab the contents of the partitions as a backup, so am assuming the sizes shown above are not correct (or represent something else?)
Going back to RECOVERY and ZIMAGE partitions - the ZIMAGE partition contains a recovery.rc, the question is really whether, even if they use the same zImage in both the ZIMAGE and RECOVERY partitions, the version in the RECOVERY partition is actually booted if recovery mode is selected (by holding the up volume key, etc.)? OTOH it may be that the RECOVERY partition is either empty or unused, has anyone tested specifically to see whether recovery.rc is run from the ZIMAGE partition?
Well I think I can answer my own question there, I flashed my modified kernel (modified recovery.rc) only to the KERNEL partition, and it boots normally if I don't touch anything, and just gets stuck on the first Samsung screen if I boot in recovery mode.
So it's doing something, I just can't tell what. Not sure if any kernel messages are getting lost behind that image, or perhaps they aren't even output to the framebuffer at all. I seem to remember seeing something about disabling the splashscreen so I'll go and have a look for that. Anyone got any other suggestions?
P.S. I also note there's a flash of screen corruption as the device starts up with my new kernel, I don't remember seeing that before. Is this a usual occurance?
I see from the Nexus S port that including adbd in the image seems to be the way to go for early messages, I'll need to generate a new Meego image and have another go later on.
Interesting, I can't see that I've done anything wrong, and my extra init shell script is not started. I am trying to use the "exec" keyword in recovery.rc to start a shell script which will pass control to the Meego rootfs. At the start of my shell script I start adbd (i.e. still within the initramfs), so I should be able to tell if it has started, and it doesn't appear to do so.
Therefore I did some Googling, and I've seen that in some cases the initramfs init does not implement the "exec" keyword (http://forum.samdroid.net/f9/new-init-exec-import-implemented-3280/). This is troublesome for me as it's what I'm trying to use, but at least would explain why I don't seem to leave the init process
I couldn't see the Samsung specific source for init anywhere, has anyone found any? I'm not happy to replace it using the standard Android source as I'm guessing there's code missing which allows the bootloader to tell init how the device was started so that it knows which of the .rc files to run. Has anyone looked into this?
Thanks
Looking at the code in that link it looks pretty straightforward, just a case of parsing the kernel command line (though I might just reverse engineer the existing init first to make sure I'm not missing anything).
Would still be easier to get the actual source code from Samsung, so I've emailed their Open Source group.
lardman said:
P.S. I also note there's a flash of screen corruption as the device starts up with my new kernel, I don't remember seeing that before. Is this a usual occurance?
Click to expand...
Click to collapse
I get it with CM
Does CM use a compressed initramfs? I'm using one of those and wondering if it's something to do with the (admittedly small) extra time required to move to init.
I don't have my Tab with me here, could someone post the output of /proc/cmdline please? You'll need to be root. Thanks.
Well it's booting you'll all be glad to hear.
More details to follow, but from memory the following were required:
Custom kernel to add btrfs support (as the image I'm booting is a btrfs partition on the external SD); kernel patch to allow compile-time cmdline to be added to the end of the bootloader cmdline (to enable console=tty0); replace Android init with init script to perform some basic setup then pivot_root to the Meego partition.
Next steps are to get the Meego system running usefully (which includes getting a terminal as currently I just have a login prompt but no way of inputting anything!) and also seeing whether I can get dual booting working with an Android system standard boot and Meego replacing the recovery boot.
Poor pic, but still: http://people.bath.ac.uk/enpsgp/Tab/PICT0040.JPG
Good stuff. Thanks for keeping us informed.
After you've got the groundwork for this done, how easy would it be to get Ubuntu running?
Try google http://lmgtfy.com/?q=ubuntu+on+galaxy+tab
Sent from my GT-P1000 using XDA App
brilldoctor said:
Try google http://lmgtfy.com/?q=ubuntu+on+galaxy+tab
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
That's using chroot, which I don't want. I want it running natively.
Sent from my Galaxy Tab
***MOD EDIT***
THIS ROM ONLY WORKS ON 4.1.26. Please consider another ROM unless you know what you are doing.
History & IntroThe first version was done with 3 different batch files, it ended up being very hacky and even ended up bricking one phone because the cleanup script didn't properly work.
I have rebuilt it from the ground up as a shell script. The initial temp root and file push is done with a batch file, it then fires off the install script on the phone which reports back to the batch with helpful info about what it is doing and what to expect from the phone as it goes. You no longer have to accept any superuser requests either.
The new script has been used on tons of phones now, everything executed exactly as I expected it to. I really didn't want to post this until we had a stock firmware to restore to, after the first release I have been worried about you guys bricking your devices, but what the hell, here it is anyways.
Come chat with us!FeaturesWorks for rooted and non-rooted devices
Deodexed
Reboot Option
Reboot to Recovery option
Ad Blocking
Removed power options headerChangelogAdeo v0.2: (3/9/2011)
Added Unknown Sources checkbox
Added Preferred install location (internal, sdcard, let system decide)Adeo v0.1: (2/28/2011)
Reboot to Recovery option
Ad Blocking
Only remove app/framework Dalvik-Cache (fixes /data app issues)
Removed power options headerFour simple rulesDo NOT do a factory reset if something goes wrong(soft brick), you will lose adb access and have a pretty brick
Do NOT do this if you are not familiar with ADB, if you softbrick you need to use adb to fix it
DO NOT PULL THE BATTERY, EVER WHILE INSTALLING
BE PATIENTHow to Install
Read the four rules above
Read the four rules above, again
Read the four rules above, again, one more time to make sure you've got it
Download the installer (AdeoInstallerv0.1.7z, AdeoUpdaterv0.2.7z)
Hook up your phone via usb with ADB enabled
run INSTALL.bat from the unzipped files
sit back, relax, wait until it reboots (can take upto 5min, be patient!!)
Read the disclaimer below
Enjoy!
DisclaimerIf you brick your device, I cannot be held responsible. Simply restore with the stock SBF to get you phone working again.Video Walkthru
Nice! First basic rom How would someone restore back to stop if you cant do a factory reset? I know on the captivate I had a nice Odin flash to do that.
Thanks
A custom ROM?
I'm going to have to buy an Atrix!
EDIT: Bought it!
EDIT2: And Adeo'd it. All UI lag is gone! This is awesome!
I am running this in my Atrix now - I believe my phone was the 4th phone to have this install perfectly on with no issues. Designgears, you are the man, once again! Thank you for this!
PM sent DG. I cheated an caught link a few minutes early and wanted say thanks! This is running great with no issues and I'm loving the reboot option...
Installed on mine, worked flawlessly. Thanks!
connexion2005 said:
PM sent DG. I cheated an caught link a few minutes early and wanted say thanks! This is running great with no issues and I'm loving the reboot option...
Click to expand...
Click to collapse
Haha, I understand your PM now... you got my file before I posted this.
psufan5 said:
Nice! First basic rom How would someone restore back to stop if you cant do a factory reset? I know on the captivate I had a nice Odin flash to do that.
Thanks
Click to expand...
Click to collapse
the factory reset is only if you brick.
There is no easy way to get back to stock, I will make a thing just like this installer to do that, actually its done, testing it
designgears said:
Haha, I understand your PM now... you got my file before I posted this.
the factory reset is only if you brick.
Click to expand...
Click to collapse
So if all else fails, the factory reset will bring it back to out of the box shape? Just concerned because Im still debating if I want to keep the phone before my 30 days is up etc. Id like to return it as stock obviously, but I also need to test out custom mods before my decision.
Thanks man.
I am curious, what changes were made for the reboot mod?
Also, thanks for the rom!
psufan5 said:
so if all else fails, the factory reset will bring it back to out of the box shape? Just concerned because im still debating if i want to keep the phone before my 30 days is up etc. Id like to return it as stock obviously, but i also need to test out custom mods before my decision.
Thanks man.
Click to expand...
Click to collapse
no no no, do not factory reset if it bricks!!! Read the op!!!!
shawnbuck said:
I am curious, what changes were made for the reboot mod?
Also, thanks for the rom!
Click to expand...
Click to collapse
smali edits in the framework.jar, android.policy.jar and added an image and sting to framework-res.apk
I saw the no factory reset posts lol... I was just curious what can be done to return the phone back to stock once this is all done with.
Thanks.
psufan5 said:
I saw the no factory reset posts lol... I was just curious what can be done to return the phone back to stock once this is all done with.
Thanks.
Click to expand...
Click to collapse
I designed this script to handle payloads, just need to package up one with a new payload with stock files and upload it.
Installed... Removed Laggyness i was getting with blur UI.
as to refering to the blur UI....
this is my second Atrix.. had to bring my first one back because when i was on tier 3 support the other night they fried the sim card reader with an update which was killing data signal to my phone... that phone had no laggyness whats so ever at all. I got this one today out of the box was having laggyness and slow response to key presses.. this fixed that as of so far.
designgears said:
smali edits in the framework.jar, android.policy.jar and added an image and sting to framework-res.apk
Click to expand...
Click to collapse
Nice, I will give this shot. Although I am already running DeOdexed already but I figured may be you got it running better than mine
I am also going to start editing small things like animations. No sense oh having all this power without some eye candy
Hello designgears,
Did you re-signed the apks? If so, could you share the key files you used? The reason I ask for it, it's because I am playing around with the /system/app apks and was getting errors like:
"Package com.motorola.blur.home has no signatures that match those in shared user"
Awesome job, btw!
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
uskr said:
Hello designgears,
Did you re-signed the apks? If so, could you share the key files you used? The reason I ask for it, it's because I am playing around with the /system/app apks and was getting errors like:
"Package com.motorola.blur.home has no signatures that match those in shared user"
Awesome job, btw!
Click to expand...
Click to collapse
Not sure, I didn't get an errors like that.
airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Try a usb port on the back of your PC
airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Download ADB Wireless from the Market. It'll help solve that one for you.
airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Install the Android SDK
install the MOTO drivers it will also install the moto adb drivers with it.
Install the ADB function drivers into the SDK/tools folder
run...cd to the sdk/tools folder... run... adb devices
should show the device is up which means ADB is enabled
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...
Thanks to Trekfan422991 for cluing me in on the Optimus 3D recovery.
Working:
Nandroid
ADB (after special driver install, need to tweak recovery for it to work with normal drivers)
Mounting USB to computer
Flashing zip files
Dangerous:
Fix Permissions (caused lots of crazy issues, fix by wiping data if you use it)
Sdparted (the sdcards are mount incorrectly, this will probably destroy your device)
I am in the process of making a recovery specifically for our device, it is mostly done and will be posted here when it is ready!
What you are going to need:
ADB (and know how to use it, don't ask in here)
Rooted Phone (again, that will not be covered, don't ask in here)
Optimus 3D recovery image [Download]
If you don't understand something in that list, DO A SEARCH AND LEARN, don't clutter the thread with crap!
Lets get started!
Lets start by getting the recovery.img file on the phone. Open up a cmd prompt and type:
Code:
adb push recovery.img /data
The rest of this will be done on the phone shell. In the cmd prompt type:
Code:
adb shell
We will need to have su access, In the cmd prompt type:
(If you haven't allowed shell su in SuperUser now would be a good time to accept the root request on the phone.)
Code:
su
Now we are going to backup your current recovery to your sdcard. In the cmd prompt type:
(make sure your sdcard is not mounted to your computer)
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
After that is done we are going to flash ClockWorkMod Recovery! In the cmd prompt type:
Code:
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
Congrats! You now have ClockWorkMod Recovery! In the cmd prompt type:
(each line is single command)
Code:
rm /data/recovery.img
reboot
How to enable ADB access: (only if it's not working already)
Download and install: (unzip and install the 2 exe files)
http://www.mediafire.com/?j5m1plnvzb8r0zc
While booted into ClockWorkMod Recovery, go into your device manager, you should see an "LGE Android Composite Device" with a yellow triangle on it.
right click on it, update driver software...
select browse my computer for driver software
select let me pick from a list of device drivers on my computer
click the "Have Disk" button
click the "browse" button
browse to;
for 64bit:
C:\Program Files (x86)\LG Electronics\LG Android Driver\64BitADB
for 32bit:
C:\Program Files\LG Electronics\LG Android Driver
and select lgandadb.inf
click "ok"
From that list select "Android Sooner Single ADB Interface"
click "next"
click "yes" on the popup
Click to expand...
Click to collapse
Awesome Great Work. Did you figure out the Bootloader? Or is there even one should more be the question I suppose. Good thing I am having issues with permissions with this didn't notice the SD Card Mounting issue till just now. That I can't deal with atm.
malickie said:
Awesome Great Work. Did you figure out the Bootloader? Or is there even one should more be the question I suppose.
Click to expand...
Click to collapse
I found a few modes, but no drivers yet so I don't know what they are. Even if we break stuff the kernel and recovery are separate, so technically we should always be albe to get back into recovery to fix stuff.
thankyou DG for getting this started..
so now with my clockworkmod i just made a backup of stock rom... if i say change the framework and I get boot loop.. will this clockwork mod be able to restore the original rom without any problems???
tiny problem... might just be missing something... but after i made my backup and i choose reboot system now... it just goes back to recovery... how do i boot up my phone!!!
sorry if it is obvious... im super tired...
Trekfan422991 said:
tiny problem... might just be missing something... but after i made my backup and i choose reboot system now... it just goes back to recovery... how do i boot up my phone!!!
sorry if it is obvious... im super tired...
Click to expand...
Click to collapse
I got mixed up as to what partition to flash, you just flashed a recovery image over the kernel... its ok tho.
follow my instructions to the su part, then do this.
// this will restore the kernel
dd if=/sdcard/mmcblk0p5.backup of=/dev/block/mmcblk0p5 bs=4096
// this will backup recovery
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
// this will flash cwm
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
OP is fixed!
edit--
and you have no adb access, this is going to get interesting!
haha... i shoulda noticed
____
LET THIS BE A LESSON FOR ALL OF YOU!!!!
THIS IS WHY YOU ALWAYS ALWAYS MAKE BACKUPS!!!!!!
NEVER SKIP THE BACKUP STEP!!!! haha
Trekfan422991 said:
LET THIS BE A LESSON FOR ALL OF YOU!!!!
THIS IS WHY YOU ALWAYS ALWAYS MAKE BACKUPS!!!!!!
NEVER SKIP THE BACKUP STEP!!!! haha
Click to expand...
Click to collapse
LOL! For sure that is why I always say, " Save early, save often, save to multiple locations!" haha.
47r0n1n said:
LOL! For sure that is why I always say, " Save early, save often, save to multiple locations!" haha.
Click to expand...
Click to collapse
sorry just side note:
how you liking your thrill compared to the evo 3d???
designgears said:
What you are going to need:
ADB (and know how to use it, don't ask in here)
Rooted Phone (again, that will not be covered, don't ask in here)
Optimus 3D recovery image [Download]
Click to expand...
Click to collapse
Thanks so much to DG & Trekfan, I've been looking everywhere for CWM!
I cannot find the download link to the recovery - in the quote above from the OP, where it says download, is that supposed to be a download link? I don't know if there's a typo or if I'm just missing something, but the "download" word doesn't link to anything for me. Instead, I thought I'd try searching for it in the optimus 3d forums, but search is down too Does anyone have a link?
Komodo Rogue said:
Thanks so much to DG & Trekfan, I've been looking everywhere for CWM!
I cannot find the download link to the recovery - in the quote above from the OP, where it says download, is that supposed to be a download link? I don't know if there's a typo or if I'm just missing something, but the "download" word doesn't link to anything for me. Instead, I thought I'd try searching for it in the optimus 3d forums, but search is down too Does anyone have a link?
Click to expand...
Click to collapse
I took it down for now, working on some issues.
Woohoo, got Trekfan422991 all fixed!
its true... i tested out my framework mod and it works great!!! look sway better then stock!!!
designgears said:
I took it down for now, working on some issues.
Click to expand...
Click to collapse
Ah, gotcha. I thought I was going crazy Thanks!
Let's rom this baby dg . I assume you also bought this with plans to possibly exchange it when the AT&T Galaxy S II comes out? I'm very impressed by the performance and build quality so far. The main thing it needs is a better theme... yikes!
designgears said:
Dangerous:
Fix Permissions (caused lots of crazy issues, fix by wiping data if you use it)
Sdparted (the sdcards are mount incorrectly, this will probably destroy your device)
Click to expand...
Click to collapse
After CWM is installed and working on our device, would it be safe to fix permission in "ROM Manager," or does that just fix permissions through whichever recovery is currently installed?
I'm guessing someone here knows how ROM manager works in this regard, but if not, I'd be happy to be a guinea pig... after all, I can make/restore backups now! : )
gtg465x said:
Let's rom this baby dg . I assume you also bought this with plans to possibly exchange it when the AT&T Galaxy S II comes out? I'm very impressed by the performance and build quality so far. The main thing it needs is a better theme... yikes!
Click to expand...
Click to collapse
Sorry for being OT but I must agree: if designgears made a Thrill ROM that's Cognition-esque then I'd consider keeping my Thrill, but considering he already has a ROM for the GSII, I imagine he's going to get the AT&T Galaxy S II? Side note, you know you've really earned some serious nerd-cred when other nerds (who you don't even know) speculate what your next cell is going to be
Komodo Rogue said:
Sorry for being OT but I must agree: if designgears made a Thrill ROM that's Cognition-esque then I'd consider keeping my Thrill, but considering he already has a ROM for the GSII, I imagine he's going to get the AT&T Galaxy S II? Side note, you know you've really earned some serious nerd-cred when other nerds (who you don't even know) speculate what your next cell is going to be
Click to expand...
Click to collapse
Not waiting on dg here. Think you missed the "let's" part. Working on a Thrill ROM as we speak. Just got the Thrill about an hour ago and I already dumped the system image, de-odexed it, created an updater-script, added root and busybox, removed bloat, and updated a few apps. Time to start theming, modding framework, and tweaking.
Im also working on a ROM but if we cannot flash zips with CWM then how am I supposed to flash the ROM? Are you going to flash it with Heimdall or something?
gtg465x said:
Not waiting on dg here. Think you missed the "let's" part. Working on a Thrill ROM as we speak. Just got the Thrill about an hour ago and I already dumped the system image, de-odexed it, created an updater-script, added root and busybox, removed bloat, and updated a few apps. Time to start theming, modding framework, and tweaking.
Click to expand...
Click to collapse
Oh, good to hear! Man I really have to sit down and try to learn some more technical stuff sometime, because ROM creation, and not even just the theming aspects, is so appealing to me.
Maybe you can create a thread placeholder and describe what you've done so far? We're really getting OT, sorry all.
timbrendelaz said:
Im also working on a ROM but if we cannot flash zips with CWM then how am I supposed to flash the ROM? Are you going to flash it with Heimdall or something?
Click to expand...
Click to collapse
Oh, I thought you could flash zips through adb after doing the fix? Or no? (((edit: wait, no, I was thinking about pushing .apks through ADB, not flashing .zip files))) Hopefully this is something DG's new recovery might address. If no to both, could you distribute ROMs via nandroid backup files of a fresh ROM installation? It would be incredibly inefficient, but it would work, right?