Related
Welcome to Eternity Project!
So... as most of you know I'm working on the Atrix solution from TOO MUCH time.
With the collaboration of people on #moto-atrix I've stated that FUSES on Tegra2 are really OTP, so there isn't any way to CRACK the BL, but we can still BYPASS it.
So... what is it?:
kexec is a "fastreboot" that won't pass through the Moto Bootloader, so with it it's possible to use custom kernels and, with some other development, custom Android systems like CM7 and many others.
Where's the poop?
Okay, that's it: I've successfully compiled and ran kexec on the Atrix 4G, so that kexec works, but it needs a kernel that can boot with kexec. On x86 we can build a relocatable kernel so no problems... but not on ARM and obviously not on Tegra.
The thing that is missing is exactly... _the address of the boot params_!
And now?
I'm only searching for help for completing the project and make a kernel that is bootable from my god-it-is-really-working-kexec. Any devs around?
Downloads:
- Kexec pack V0.01: DOWNLOAD
Kexec pack contains:
- ATAGS for MB860 (ATRIX_atags.tar)
- ATAGS hack module (eternity_procfs.tar)
- kexec module (eternity_kexec.tar)
- kexec tools/binaries (kexec-tools.tar)
- Kernel....that doesn't work. (eternity_kexec_kernel.tar)
So, what does work and what does not?
- ATAGS hacky hack: WORKING
- kexec module: WORKING
- kexec tools/binaries WORKING
- Kernel ToDo
How to run it:
0. FLASH AT&T 1.2.6 SBF PRIOR DOING ANYTHING
1. Extract all the archives
2. Insert the procfs_rw.ko module
3. cat atags > /proc/atags
4. Insert the kexec module
5. Run kexec for loading the kernel and jumping to it.
6. Boot! :|
P.S.: I won't release detailed how-tos because at this state I only need a DEVELOPER that can help me to build the kernel.
Thanks to:
- PAulyHoffman (special thanks!)
- unknown
- Sogarth
- the2dcour
- cranch
- eval-
- and many, many others....!
Awesome, i can verify that this kexec is working and will continue testing until we succeed.
random boot animation I made for eternity project
http://diamantephoto.com/bootanimation_red.zip
Also: 1.2.6 without losing /data, in case you were wondering exactly why I made this
http://forum.xda-developers.com/showthread.php?t=1073439
kexec pack updated. now kexec-tools is included
@kholk: Hai;
so basically this is a port of the unix kexec to run on tegra based devices?
From my understanding the android system uses a boot image that has the ramdisk and kernel combined together and they are dependent on each other... so won't overwriting the kernel at runtime give you us some issues since the core initialization of the system is ran from the ramdisk???
wouldn't be a better idea to tackle this issue too? but then again the only reason we can't flash boot images is because of the bootloader but ofcourse this is definitely a step forward for the tegra users.
now about the kernel, theoretically if we build an aosp tegra kernel from http://android.git.kernel.org/?p=kernel/tegra.git;a=summary shouldn't it work?
I can try building us a kernel if that would work
PS: people let's keep this dev ONLY if you want us to get some progress we need able to read through the thread without useless posts.
edit: also found this https://opensource.motorola.com/sf/frs/do/listReleases/projects.atrix/frs.olympus I'm sure having the source for the kernel we are currently running is also helpful
I know we should keep this dev only but please don't tell me this is for ATT only i already feel shafted enough being a Bell user and that would make it a hell of a lot worse if it was
Ratchet556 said:
I know we should keep this dev only but please don't tell me this is for ATT only i already feel shafted enough being a Bell user and that would make it a hell of a lot worse if it was
Click to expand...
Click to collapse
When a kernel that works will be deployed I'll personally port it to Bell Atrix. This will take only some seconds.
kholk, perhaps we can ask a defy developer (or any of the phones that have kexec working) to help us build the kernel.
it's too bad da_g isn't around, he did a custom kernel but wasn't able to boot it.
I'm not a developer so I am hoping someone can help me understand this process better. From my understanding kexec is used as a reboot method that skips initial bootloader and hardware loading so how will this effect if we turn our phone off or pull the battery? Will the device need to be rebooted after initial startup to reactivate the kexec? Sorry to sound like the newbie that I am, I'm just interested in learning more.
lostinbeta said:
I'm not a developer so I am hoping someone can help me understand this process better. From my understanding kexec is used as a reboot method that skips initial bootloader and hardware loading so how will this effect if we turn our phone off or pull the battery? Will the device need to be rebooted after initial startup to reactivate the kexec? Sorry to sound like the newbie that I am, I'm just interested in learning more.
Click to expand...
Click to collapse
Yeah, I'm also a little confused as to what exactly this means for all of us people who want to just flash Custom ROMs and such? In what ways is this different than just an unlocked bootloader and such?
lostinbeta said:
I'm not a developer so I am hoping someone can help me understand this process better. From my understanding kexec is used as a reboot method that skips initial bootloader and hardware loading so how will this effect if we turn our phone off or pull the battery? Will the device need to be rebooted after initial startup to reactivate the kexec? Sorry to sound like the newbie that I am, I'm just interested in learning more.
Click to expand...
Click to collapse
thebeardedchild said:
Yeah, I'm also a little confused as to what exactly this means for all of us people who want to just flash Custom ROMs and such? In what ways is this different than just an unlocked bootloader and such?
Click to expand...
Click to collapse
Assuming my understanding of kexec is correct, this would survive battery pulls. Basically, a custom rom would need to include two kernels: a Motorola kernel in addition to the custom one. The bootloader would run the Motorola kernel, which should pass any checks the bootloader would make. From there, the kernel would use kexec to load the custom kernel over itself in memory, effectively replacing itself. From there the custom kernel can continue loading the rom.
If the booloader were unlocked, the phone could directly boot the custom kernel. The downside of loading the custom one on top of the Motorola one is that the state of the phone might not be entirely known, so it would need to do more work checking what's been initialized and what hasn't. Its a little more work for the kernel/rom developer, but the end result is the same.
Jotokun said:
Assuming my understanding of kexec is correct, this would survive battery pulls. Basically, a custom rom would need to include two kernels: a Motorola kernel in addition to the custom one. The bootloader would run the Motorola kernel, which should pass any checks the bootloader would make. From there, the kernel would use kexec to load the custom kernel over itself in memory, effectively replacing itself. From there the custom kernel can continue loading the rom.
If the booloader were unlocked, the phone could directly boot the custom kernel. The downside of loading the custom one on top of the Motorola one is that the state of the phone might not be entirely known, so it would need to do more work checking what's been initialized and what hasn't. Its a little more work for the kernel/rom developer, but the end result is the same.
Click to expand...
Click to collapse
I see, thanks for the explanation! So, on the user end, would there be any noticeable differences? This kind of makes it sound like the phone will be doing a lot more work, so could we see performance decrease or perhaps startup lag or something of the sort? Or would this all pretty much function on the surface as if we had flashed a custom ROM on some phone without a locked bootloader?
thebeardedchild said:
I see, thanks for the explanation! So, on the user end, would there be any noticeable differences? This kind of makes it sound like the phone will be doing a lot more work, so could we see performance decrease or perhaps startup lag or something of the sort? Or would this all pretty much function on the surface as if we had flashed a custom ROM on some phone without a locked bootloader?
Click to expand...
Click to collapse
Boot time will be about twice as long. Other then that, everything will run about the same
Yes thank you very much for that explanation... though I do also have the question about stability. By replacing the current kernel in memory with the new modified kernel the phone state may get confused as you mentioned... could this cause instability as a whole or increase risk of kernel panics? Or once everything is loaded and complete does it stabilize with the modified kernel?
Again sorry for the questions. This topic intrigues me and I love learning how stuff works.
thebeardedchild said:
I see, thanks for the explanation! So, on the user end, would there be any noticeable differences? This kind of makes it sound like the phone will be doing a lot more work, so could we see performance decrease or perhaps startup lag or something of the sort? Or would this all pretty much function on the surface as if we had flashed a custom ROM on some phone without a locked bootloader?
Click to expand...
Click to collapse
Only difference would be that it might take slightly longer to boot up. Once the phone is finished booting, there's no difference in terms of performance because by that point the Motorola kernel isnt running, or even loaded.
thebeardedchild said:
Haha yeah I'm checking every like 2 seconds now. What exactly do we wait for then? Someone to just create the custom kernel, and then of course wait for some Custom ROMs to be created? I hope we get CM7!
Click to expand...
Click to collapse
Kexec isn't fully operational yet, still need to find boot params. Then custom kernel.
How easy will this be to install on our phones? will it just be something we need to flash through CWM or will it require some more work then that to install?
Ratchet556 said:
How easy will this be to install on our phones? will it just be something we need to flash through CWM or will it require some more work then that to install?
Click to expand...
Click to collapse
I imagine some of the preliminary stuff may need to be pushed with ADB but devs are always nice and give us very clear guides. And I'm sure either a dev or active member could easily create a batch script.
Even though I'm comfortable with ADB I always make scripts for myself because I regularly wipe me phone and whatnot. Because it's so engaging some people might want to wait until a few normal community members test this out so we can see if there are any glaring challenges with the instructions. Just remember to back things up, read instructions clearly and I'm sure we'll all be fine. We've got SBFs and all that good stuff to cover our asses too.
Would it be possible to bring fastboot off the htc to this? Then we won't have to worry about boot time at all. Even if it did double the boot time...
Sent from my MB860 using XDA App
PixoNova said:
This bypasses the bootloader
Swyped from my Motorola Atrix 4g using XDA Premium App
Click to expand...
Click to collapse
Correct this method has nothing to do with unlocking the bootloader and previous attempts at that proved it maybe impossible.
I am making this thread because I am seeing *far* too many people posting things when they have no idea what they do or when things are coming, or what things are possible with the phone at this point, so please take these answers into consideration when deciding to post either a new thread, or a reply to someone in an existing thread:
(Note: This thread will be continuously updated when more issues need to be addressed)
QUESTION NUMBER 1:
What can our phone do at this point (9/17/2011)?
At this point, our phones can do the following:
-Be rooted
-Use a bootstrap ClockworkMod Recovery
-Make nandroid backups
-Use the 2nd init booting process
QUESTION NUMBER 2:
What is bootstrap recovery?
Bootstrap recovery is an alternative form of recovery which "hijacks" the boot process and instead goes into a recovery mode that loads the ClockworkMod Recovery.
In order to boot into it, you *must* bootstrap it through the app on Android *every time you want to boot into recovery*.
QUESTION NUMBER 3:
What does having bootstrap recovery do for us?
With bootstrap recovery, we can do EVERYTHING that a normal recovery can do for us, *INCLUDING* installing ROMs and making nandroid backups.
QUESTION NUMBER 4:
Now that we have bootstrap recovery, does this mean we can use ROM Manager to install stuff?
No. No, no, no, a thousand times no. This is not an official 2nd init Recovery release from koush and ROM Manager WILL NOT work with the bootstrap version of recovery.
QUESTION NUMBER 5:
What is 2nd init?
2nd init is altering the init files in the system partition to take over the booting process so that we can load whatever we want to on boot. It is a way to get around the locking of the bootloader. This is also what allows CM7 to run on Moto phones with locked bootloaders.
QUESTION NUMBER 6 (this is the important one):
What does it mean when our bootloader is "locked"?
The bootloader being locked means that we are not allowed to flash unsigned images in fastboot or flash custom kernels to our phone that can alter features such as overclocking, or BFS, etc.
HOWEVER: This *does NOT* mean we cannot start making custom ROMs on our phone. The bootloader being locked has *nothing* to do with the system partition and custom ROMs are still completely viable and can be made and now freely distributed.
ALSO: There *are* ways to get around the fact that we cannot flash custom kernels. With 2nd init and kernel modules, we can freely get around the locked bootloader and even achieve features such as overclocking without having to flash a different kernel.
Please read this and understand this before you post.
very useful information here...there seems to be many in these forums that are new-to-root and this explains the current status very well. thanks for this and all of the help you have provided people already.
Sent from my DROID BIONIC using XDA App
I liked this thread since I just picked the bionic up yesterday, like it better than the Droid 3
Sent from my DROID BIONIC using xda premium
If your truly new to root i suggest waiting or reading alot before attempting anything here way to early to be rooting and have no idea what your doing that makes for a perfect bionic paperweight
Sent from my DROID BIONIC using XDA App
Bump-This needs a sticky.
topxshelfxtre said:
If your truly new to root i suggest waiting or reading alot before attempting anything here way to early to be rooting and have no idea what your doing that makes for a perfect bionic paperweight
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
If you know what you're doing, there's not much risk...if you don't, it's a disaster waiting to happen.
Sent from my DROID BIONIC using XDA App
Berzerker7 said:
I am making this thread because I am seeing *far* too many people posting things when they have no idea what they do or when things are coming, or what things are possible with the phone at this point, so please take these answers into consideration when deciding to post either a new thread, or a reply to someone in an existing thread:
......Please read this and understand this before you post.
Click to expand...
Click to collapse
Can you please include Pictures?
Forever root
Where can I find a link to Forever root and cheesecake?
Thankk you
Thanks
Nice write up. As a newbie I can't thank you enough for clearing those topics up in a short and sweet manner. Thanks!
this is the place for stupid questions?
im experienced (rooted droids) but total noob.
what is all the talk about 893 or 5.6something.
its seems totally differenent from ROMs but it looks like some say you need to have this # to use this rom and so forth. It looks also like people are screwing up there data with this stuff.
So...for people who want to Root&Rom is this stuff important? Where is info on what it actually is (893 and other #s)
covering my head and waiting for the smack...
Berzerker7 said:
QUESTION NUMBER 4:
Now that we have bootstrap recovery, does this mean we can use ROM Manager to install stuff?
No. No, no, no, a thousand times no. This is not an official 2nd init Recovery release from koush and ROM Manager WILL NOT work with the bootstrap version of recovery.
Click to expand...
Click to collapse
I was taking a look at the Bootstrap description on the market and it reads:
YOU MUST BE ROOTED TO USE THIS APPLICATION. FOR DROID BIONIC ONLY.
DO NOT DOWNLOAD THIS IF YOU AREN'T COMFORTABLE USING AN SBF!
Droid Bionic Recovery Bootstrap will set your phone up so you can access a custom recovery mode to create full backups of your phone and install new ROMs! Install ROM Manager afterwards for easy ROM installation and backup!
What does the developer mean by the last sentence of his description? Doesn't this conflict with FAQ #4? I'm just trying to make sense of everything before I begin using Roms... Thanks.
Looks like custom roms might finally be here for the xt860 (and possibly me863, read Update4 below for more info). Thanks to Hashcode for all the work he's done for all of us building safestrap, porting cm7 and everything, daywalker04 for uploading the Brazil Retail sbf, Endroid for being the first to try it with a normal bootstrap and now I'm confirming it working with Hashcodes newest safestrap(as well as his old ones, I originally tested w/v0.92 and worked my way up to current). I Just booted cm7 off /preinstall.
As usualy, please keep in mind that neither I or anyone else will take any responsibility for anything that happens to your phone through use of these files.
IF/When you enable and disable safestrap remember to format data/cache, causes bootlooping for me if I don't.
Warning, if you do this the way things are now you will not be able to get back to your bell software!! Only do this is you are absolutely sure you know what you're doing!!!!!!!!
You may have to be on the brazillian retail rom for this to work! You can find it in This Thread. You're looking for Fastboot package for UMTS XT860 Retail Brasil. At this point in time you can't get back to bell stock so again, it's at you're own risk!!
UPDATE: Thanks Rick2 for the recovery fix that allows us to swap between safestrap on the fly. Now when I need data I can get it anywhere. Works with Hashcodes newest safestrap (1.06). Go here to thank him and get the patch!
Update2: I've attached a CWM flashable zip that I've used to successfully get 3g working on Liberty and Mavs Rom, it does not work on cm7 but will hopefully work on other verizon based roms. It pushes the stock libmoto_ril.so(from the brazil retail), a new apns-xml.conf and a slightly edited build.prop(just made it en/US). I've had it cause the phone to fc loop if I installed it on an existing rom and didn't factory reset.
Update3: Watching this thread for info about me863 I think but according to that thread a user has flashed the brazil retail to his me863 and is trying to get data working
Update4: I've reworked the data patch to make it more universal. It should work on me863 providing safestrap runs on your phone. The patch will now copy files from /systemorig so you'll be using matching kernel/libs etc rather than using generic xt860 files. It also makes backups of the original files in the same location (just adds a .bak extension). This new patch IS SAFESTRAP ONLY. Huge huge thanks to Adamogle!!! If it weren't for him I'd still be banging my head up against the wall and no one would be using this patch. You may have to format data/cache, I left it out of the patch so everyone can test (if you phone goes into a force-crash loop then reboot and clear data/cache). Once I get confirmation of this working (or not) on the me863 I'll fix the thread again. I've left the old data patch(renamed as fit) as well in case anyone runs into troubles. Still not a cm7/9 patch, if one comes about it will get it's own thread but it works on all other custom roms based on motorola firmware.
if you see this and you're like "yes, finally some progress on the xt860!! Where do I donate???!?!!" You do that on Hashcodes website, it's ALL his hard work, I just basically wrote you a little story and pooled some files together. He really deserves it, he's working around the clock right now on cm9, seriously around the clock. Of course you can feel free to click the "Thank" button on this post if you like using my data patch
1./ Flash Brazil retail sbf from this thread
2./ root with Zerg from this thread. For some reason v3 kept tossing errors, v2 worked first try.
3./ install safestrap or whatever bootstrap (safestrap from Hashcodes site http://hash-of-codes.blogspot.com/
4./ profit (follow the directions to install a safestrap rom
boot recovery
Enable safestrap in options
Factory reset (formats data & cache)
Mounts > format system
Install your rom
Install my 3gfix
Reboot and profit
)
Again, my patch doesn't work on cm7 at the moment. Sorry Hashcode and everyone but I figured we'd be better off shooting for a known working rom. I'll update the post as I and other users test more roms. Thx thing on a spring for providing the patch "template", every time I threw one together and put it on my phone it turned out to be corrupt somehow so I just removed the files from your data fix and shoved in my own.
does it work with me863?
Thanks Willis I'll try that fix tonight. I'll try some of the other custom roms too see if any work. Probably give safestrap a whirl too
Beamed by invisible waves from my rooted xt860
I gotta say after months of watching customs roms and dev for the xt862 this is pretty exciting. Does wifi data work on cm7? I would assume if the issue is just with apn. I know its not the intended purpose but I may use safestrap as a dual boot, run custom roms at home in safe mode and switch back to Brazil retail when I need 3g
Beamed by invisible waves from my rooted xt860
This is awesome.
Great work guys. As soon as this gets a little more stable I'm going to flash it onto my gf's phone, work around these bugs that came in the stock FW.
Awesome. Been looking forward to this day. Not jumping on the train just yet, but I'm sure that once the 3G bug is ironed out, I'll be flashing.
emprize said:
does it work with me863?
Click to expand...
Click to collapse
Try it out, you can always sbf back to stock if it doesn't work.
Endoroid said:
I gotta say after months of watching customs roms and dev for the xt862 this is pretty exciting. Does wifi data work on cm7? I would assume if the issue is just with apn. I know its not the intended purpose but I may use safestrap as a dual boot, run custom roms at home in safe mode and switch back to Brazil retail when I need 3g
Beamed by invisible waves from my rooted xt860
Click to expand...
Click to collapse
Wifi works, I'm pretty sure it is an apn issue. Think I need to find my old framework-res.
From the bell rom? I have that at home if you need
Beamed by invisible waves from my rooted xt860
Did you try this http://forum.xda-developers.com/showthread.php?p=19981520
Beamed by invisible waves from my rooted xt860
Endoroid said:
Did you try this http://forum.xda-developers.com/showthread.php?p=19981520
Beamed by invisible waves from my rooted xt860
Click to expand...
Click to collapse
Yeah, I tried that and the gsm data patch. I'm having trouble adding/editing apns etc, can't join networks because "Your SIM card does not allow a connection to this network" etc. This is with cm7 and liberty. I have liberty on my safestrap now, running. I can get sms, make calls etc, wifi works. I'll firgure the rest out. If I want to go back to stock for data or something I just turn safestrap off and do an advanced restore of my /data partition to my backup from after installing the brazil retail.
I can't seem to make this work willis, i adb pushed those files to /preinstall but i still get constant FC of com.android.phone the only thing that makes it not do that is removing the sim. i'm confused
Endoroid said:
I can't seem to make this work willis, i adb pushed those files to /preinstall but i still get constant FC of com.android.phone the only thing that makes it not do that is removing the sim. i'm confused
Click to expand...
Click to collapse
I was gonna put together a flashable patch earlier but had some things come up and ended up in a hospital waiting room all night(next time I'll bring my laptop >.<). I'll toss it together asap and update the first post as long as I can flash it/it works. I should have mentioned (this is the confusing part) I pushed those files before enabling safestrap so /preinstall was /system if you get what I mean.
For CM7 to work correctly on GSM, I need to edit the init.mapphone_umts.rc file to setup all of the services the right way.
TBH, I never even looked twice at that file because I thought there wasn't anyone using it.
*blush*
Glad to see the XT860 crowd finally get some fun. )
Thanks Hashcode for putting so much effort into it, it's highly appreciated.
We were feeling a little bit left out.
Well, if you can get a version of CM7 working before I start having to study for exams, would be greatly appreciated.
But, if not, I'm sure I'll just divert time from studying to testing.
Sent from my Nexus S using xda premium
Accophox said:
Well, if you can get a version of CM7 working before I start having to study for exams, would be greatly appreciated.
But, if not, I'm sure I'll just divert time from studying to testing.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Changing your phone's firmware before exams is a bad thing... Trust me, I know Mine are starting next week!
Willis, I wondered if such was the case, I had safe system enabled and tried adb push to both /preinstall and /system as I wasn't sure how adb would recognize them in safe system. I also was pushing while in recovery
Beamed by invisible waves from my rooted xt860
danifunker said:
Changing your phone's firmware before exams is a bad thing... Trust me, I know Mine are starting next week!
Click to expand...
Click to collapse
Which is why I have a trusty nexus s
Sent from my Nexus S using xda premium
Hashcode said:
For CM7 to work correctly on GSM, I need to edit the init.mapphone_umts.rc file to setup all of the services the right way.
TBH, I never even looked twice at that file because I thought there wasn't anyone using it.
*blush*
Glad to see the XT860 crowd finally get some fun. )
Click to expand...
Click to collapse
After the little bit of testing I've done over the last day or two with different custom roms it looks like we're(xt860 and me863 users I image) going to have to have (or really really want) a patch we can flash against any custom rom to get our data and sometimes maybe phone up(or to keep it from crashing). Haven't been able to get 3g up (though the 1 method I did not try was to crash the phone through the dev tools in cm7 as was mentioned in another thread) on any rom yet. Phone/text works right off the bat w/liberty, mavs etc etc.
Narrowed down why Safestrap Recovery would only boot if a USB cable was connected on the XT860; it had to do with a line in the init.rc file executed when booting into recovery:
Code:
write /dev/usb_device_mode msc_adb
As well as a line in the postbootrecovery.sh script which accomplishes essentially the same thing, except via an echo command.
Obviously, we could just comment those lines out, but then we're left without adb in recovery without messy changes each time we want it. So, I whipped up a little script that checks if there is a USB connection and if so, run the previous necessary commands to enable adb and if not, then leave them out. End result: Safestrap Recovery is working like a charm now. No more need to worry about tinkering with my phone without a computer nearby to get into the recovery...
I attached the modified recovery.zip, just replace the original one located at /system/etc/safestrap/recovery.zip with the attached one and you should be good to go.
As the title says, I'd like to root, but with somewhat limited knowledge on the phone and it's processes, and no knowledge of scripting/coding, I want to avoid taking too much risk.
I've been stock with the D3 since I got the phone in 2011, found out we aren't getting ICS, and we aren't getting unlocked by Moto. (pissed off!) >.<
The way I see it I have 2 options, 1) stay stock until my contract is up in march and get a new phone, or 2) Give root a go, and Have ICS ported to me via a Custom Rom, and do more research as I go. (I like being hands-on when it comes to learning).
As to my phone, I am running 906 OTA Stock as it gets .. -_-' I'd like to root using
http://forum.xda-developers.com/showthread.php?t=1686911 <-- ovelayer's method in this thread. (thank you Ovelayer, I can't seem to find that button so I'm just acknowledging you here since I'm new to this kind-of thing).
I just need some clarification
in his thread it says to dl the 1-click .exe, then the Motofail root tool? or is that also a way to root? I got confused with that.
Afterwards, I dl safestrap once I'm rooted? or should I just dl it and put it onto my phone all at once?
Apologies for the noobness. I'd rather be a noob asking questions than a retard who goes ahead and does things and finds out he screwed up too late.
Rooting is done to get superuser permissions within Android so you can install some advanced apps and modify system files which can all be done from within the stock ROM. Rooting then flashing an unofficial ROM is a little more advanced and something I haven't done yet so I can't help you much there. I'm waiting for something a little more stable since my Droid 3 is my main phone. You can read Hash of Codes site (the developer of ICS/JB for the Droid 3) on how to safestrap:
http://blog.hash-of-codes.com/how-to-safestrap/
To root use Motofail. I know it says its for the Droid 4 but the original Droid 3 root exploit was patched with the latest OTA so we have to use the Droid 4 method called Motofail:
http://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/
DróidScìon said:
As the title says, I'd like to root, but with somewhat limited knowledge on the phone and it's processes, and no knowledge of scripting/coding, I want to avoid taking too much risk.
I've been stock with the D3 since I got the phone in 2011, found out we aren't getting ICS, and we aren't getting unlocked by Moto. (pissed off!) >.<
The way I see it I have 2 options, 1) stay stock until my contract is up in march and get a new phone, or 2) Give root a go, and Have ICS ported to me via a Custom Rom, and do more research as I go. (I like being hands-on when it comes to learning).
.
Click to expand...
Click to collapse
My D3 has Maverick as non-safe for daily driver and the latest Hashcode for fun. I find that to be the best combination. Once Hash finishes the camera and JB is working reasonable well, JB will be my DD.
I also have an SGS3, TF300T, and a Spica, all of them rooted.
once rooted, make sure you use safe strap. It makes roms easy to try out before having to settle
Sent from my DROID3 using Tapatalk
Alright, so it appears I have been rooted, and still looks like I'm in .906 OTA. It was pretty easy using Motofail, actually. So, now I have Superuser and Titanium Backup(free, for now) on my D3.
Now, you guys mentioned Safestrap? Can you guys give me a suggestion on which one to use? There appear to be a few of them. 1 is SAFESTRAP v2.10 Recovery (Kexec) and the other is a Tweaked version of Safestrap v1.08e (Non-Kex) which one is better, or a better question, whats the difference between the 2?
DróidScìon said:
Alright, so it appears I have been rooted, and still looks like I'm in .906 OTA. It was pretty easy using Motofail, actually. So, now I have Superuser and Titanium Backup(free, for now) on my D3.
Now, you guys mentioned Safestrap? Can you guys give me a suggestion on which one to use? There appear to be a few of them. 1 is SAFESTRAP v2.10 Recovery (Kexec) and the other is a Tweaked version of Safestrap v1.08e (Non-Kex) which one is better, or a better question, whats the difference between the 2?
Click to expand...
Click to collapse
Safestrap 1.08 is the 'normal' ssafestrap
Safestrap 1.08e/f/g is an advanced safestrap with extra features like touch etc but not by hashcode
Safestrap 2.10 is the latest which allows the new kernel with the kexec ICS/JB to be used.
2.10 It appears to also work fine with normal roms so i'd use that
DróidScìon said:
As to my phone, I am running 906 OTA Stock as it gets .. -_-' I'd like to root using
http://forum.xda-developers.com/showthread.php?t=1686911 <-- ovelayer's method in this thread. (thank you Ovelayer, I can't seem to find that button so I'm just acknowledging you here since I'm new to this kind-of thing).
I just need some clarification
in his thread it says to dl the 1-click .exe, then the Motofail root tool? or is that also a way to root? .
Click to expand...
Click to collapse
If you were stock 906, there was no reason to run the 1-click.exe - that's only for people who rooted their phones and deleted bloatware to get the phone back to stock, or people whose phones are bricked somehow. Coming from stock, just running Motofail was enough to root.
I will concur with everyone here that running rooting, installing and running Safestrap, and installing a custom ROM - and leaving your rooted stock alone - is the best way to go. It will be a lot easier to unroot later on if you want to sell the phone, etc.
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
DróidScìon said:
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
Click to expand...
Click to collapse
It doesn't matter. Choose which has enough space.
DróidScìon said:
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
Click to expand...
Click to collapse
It's asking where to backup TO, like the post above me, choose wherever has space. Backups are about 1GB. You may wish to move it to your computer after if you don't have much space on your device. You can always stick it back on your external sd via card reader if needed, but it's really hard to brick while using safestrap
Also one of the most common errors for noobs on safestrap is, the first time you engage safe mode, you must flash a rom. Since its using a different partition for system, it's currently empty and if you switch to safe and try to boot you will get a black screen as you are booting an empty partition. All gingerbread roms are stable but there are no ics roms that are fully functional, although one is in the works
Sent from my XT860 using xda premium
I saw that, and before I rooted, I did a Factory Reset on the phone and formatted my SD card. So I have 11+gig free on Internal and 15+gigs on External.
Now, I just need to learn to Flash RoMs (probably more to it than just hitting a button that says flash .zip) and find some info on the "must-have" apps for a rooted phone.
Well guys, I've successfully installed CM9 Kexec ICS Sept 5th update from Hashcode on my Droid 3! Now, another big question, How will I restore stuff like contact and account info? I've read somewhere around here that Restoring Data from my google account is a bad idea?? Are there other ways of doing so without Titanium Backup, or should I just go ahead and buy the Pro Key? (currently limited funding)
DróidScìon said:
Well guys, I've successfully installed CM9 Kexec ICS Sept 5th update from Hashcode on my Droid 3! Now, another big question, How will I restore stuff like contact and account info? I've read somewhere around here that Restoring Data from my google account is a bad idea?? Are there other ways of doing so without Titanium Backup, or should I just go ahead and buy the Pro Key? (currently limited funding)
Click to expand...
Click to collapse
If your contacts are on your google account they will show up.
What other account info do you mean?
You should go ahead and restore contacts. just go to Settings>Accounts and Sync>Google, then turn contacts sync on.
Endoroid said:
Also one of the most common errors for noobs on safestrap is, the first time you engage safe mode, you must flash a rom. Since its using a different partition for system, it's currently empty and if you switch to safe and try to boot you will get a black screen as you are booting an empty partition. All gingerbread roms are stable but there are no ics roms that are fully functional, although one is in the works
Click to expand...
Click to collapse
I must have made another noob mistake. Everything went well, up until my first startup with the new OS (cyanogenmod9). It has been at the startup screen for over 15minutes right now. I must say, it is one awesome startup screen, with the blue effects and all, but I would love to get to the desktop/homescreen, haha.
If you guys have any advice I would greatly appreciate it. This is a Droid 3, it was rooted a couple hours ago, I did the safestrap as described, created a backup file, etc. My only guess is I jumped the gun by trying this OS on my Droid3 and it may still be under development? FWIW to you, this is the first I've rooted or modded a smartphone in my life, from 0-full speed in a couple hours is what I was shooting for using everyone elses experience.
thanks
Make sure you wiped the data/user settings in Safestrap. You lose your apps & settings but those items from a previous install can cause that type of boot issue.
Sent from my XT862 using xda app-developers app
Phibernaut said:
Make sure you wiped the data/user settings in Safestrap. You lose your apps & settings but those items from a previous install can cause that type of boot issue.
Sent from my XT862 using xda app-developers app
Click to expand...
Click to collapse
thanks. since my last post I used a more detailed how-to, and wiped 3 different areas for data. Now, i had only a black screen (with power, barely lit) and it never even got to the cool blue screen.
I'm currently in safestrap after pulling my battery again, just trying to figure out how to revert back to my standard OS (rooted) and try a ROM like MavRom since it's suppoedly fully capable and stable. I'd love ICS, but I just want a working phone right now
---------- Post added at 10:25 PM ---------- Previous post was at 10:14 PM ----------
good news is, I did enough steps correctly, that I was able to startup in my unsafe mode, and my normal rooted system is functioning fine. That makes me very happy.
This duel boot thing is pretty cool, reminds me of having bootable thumb drives on my old linux system with different OS's. I hope i can get a seperate OS working, however, that fits my needs for a day to day functional phone, without all of Verizon's crap on it
Once rooted use titanium backup to back up apps and data.
Only restore with the same ROM though, the following is in increasing order of risk
restore app only to exact same ROM+version
restore app+data to same ROM+ver
restore app only to update of same ROM
restore app+data to updated ROM version
play chicken with a bus on a highway
restore apps to different kernel e.g. CM7 backup => restore to CM9
check to see what a gun firing looks like down the barrel
restore app+data to different kernel
restore app+data to an older ROM or kernel
do anything at all with system apps+data if you don't know what you're doing
Granted, it has been a while since I've built CM, and never ported it to a new device, but figure this might give some smarter people a head start or at least provide a place for others to collaborate.
I've not gotten very far past the initial vendor setup per http://wiki.cyanogenmod.org/w/Doc:_porting_intro.
A lot of the work is based off the similar ASUS TF700T, https://github.com/CyanogenMod/android_device_asus_tf700t.
I've not messed with the kernel at all at this point, https://github.com/ouya/ouya_1_1-kernel.
I've uploaded everything so far to github, https://github.com/vinny75/android_device_ouya_ouya_1_1
Packages included with official build:
OUYA Framework, Launcher, and Store
Code:
app\OUYAKeyboard.apk
app\OUYALauncher.apk
app\OUYAOOBE.apk
app\OUYAWallpaper.apk
app\ouya-framework.apk
note: some media files I haven't list
CWiid for Android: http://cvpcs.org/projects/android/cwiid4android and https://github.com/cvpcs/android_external_cwiid[.
Code:
bin\wminput
lib\libcwiid.so
etc\acc_led
etc\acc_ptr
etc\buttons
etc\gamepad
etc\ir_ptr
etc\neverball
etc\nunchuk_acc_ptr
etc\nunchuk_stick2btn
Sixpair for PS3 controllers http://www.blog.kaiserapps.com/2012/10/setting-up-sixaxis-controller-android.html.
Code:
/bin/ps3service
/bin/sixpair
I noticed that the recovery.fstab committed is from the Ouya stock recovery partition. When getting cwm to work properly with the internal sdcard, we ended up having to change the sdcard line.
I made the change and submitted a pull request.
Edit: I saw you merged the change.
Sent from my Nexus 7 using xda premium
mybook4 said:
I noticed that the recovery.fstab committed is from the Ouya stock recovery partition. When getting cwm to work properly with the internal sdcard, we ended up having to change the sdcard line.
I made the change and submitted a pull request.
Edit: I saw you merged the change.
Click to expand...
Click to collapse
Thanks, appreciate the help, hopefully, we'll have a working build soonish
If you need any help with kernel debugging/boot issues, I'll be happy to offer up the assistance of my bus pirate.
I was looking at building CM also, but there was always that step in every tut I looked at for "how to port CM to a new device" that basically said "select your device from the build tree"... well if it was in the device tree it wouldn't really be a "new" device then would it!
Also you may want to look at building 10 instead of 10.1, might have less kernel issues as its 4.1.2 jb... at least so we can get some alternative rom working then go for 10.1 after that.
Good luck!
Vinny75,
What method did you use to create the files?
"Method 1: Use mkvendor.sh to generate skeleton files"
"Method 2: Fork a similar device's git repository"
or "Method 3: create the directories and files manually"
mybook4 said:
Vinny75,
What method did you use to create the files?
"Method 1: Use mkvendor.sh to generate skeleton files"
"Method 2: Fork a similar device's git repository"
or "Method 3: create the directories and files manually"
Click to expand...
Click to collapse
I started out with Method 1 then moved over files and settings from the ASUS TF700T.
professorpoptart said:
If you need any help with kernel debugging/boot issues, I'll be happy to offer up the assistance of my bus pirate.
I was looking at building CM also, but there was always that step in every tut I looked at for "how to port CM to a new device" that basically said "select your device from the build tree"... well if it was in the device tree it wouldn't really be a "new" device then would it!
Also you may want to look at building 10 instead of 10.1, might have less kernel issues as its 4.1.2 jb... at least so we can get some alternative rom working then go for 10.1 after that.
Good luck!
Click to expand...
Click to collapse
Yes, building the new device tree has been... uhm... educational... and I am still learning. If I don't make any headway on 10.1, I might drop back to 10 - at least most of the legwork will be done.
Ok, so I'm in the middle of a build
Have a vendor tree on my git and I forked Vinny75's device tree, modified it some
Also a kernel tree up there, which is required for my device tree (prefer to build the kernel myself =) I've booted a custom-built kernel on it already, so that shouldn't be an issue)
I'm nervous to flash this though. I did a bit of searching but couldn't come up with a way to get back into recovery should this thing not boot. You guys know of anything?
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Sent from my Nexus 7 using xda premium
mybook4 said:
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yea, that's what I'm seeing.
So here's my 'solution'
Since we have fastboot, we can boot a boot.img without having to worry about flashing it.
I've successfully booted my cm boot.img, with ro.secure=0 and ro.adb.secure=0, I can adb reboot it when it fails miserably to boot
Quick and dirty script to unsecure a boot.img:
http://pastie.org/8033076
It assume that unpackbootimg and mkbootimg are in your path, you can get them here: http://invisiblek.org/mkbootfs_tools.zip
Getting closer...
THere's a keyboard solution in the Ouya Questions forum in the thread, [Q] Is My Ouya Dead?
dibblebill said:
THere's a keyboard solution in the Ouya Questions forum in the thread, [Q] Is My Ouya Dead?
Click to expand...
Click to collapse
Yeah, I think that is the same solution posted earlier:
mybook4 said:
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Click to expand...
Click to collapse
THis might be another option too:
tylerwhall said:
I started looking into bootloader-level recovery tonight before messing with the file system too much and potentially getting into a bad state. I couldn't find this information anywhere else.
Bootloader strap
On the back of the board in the center, there is an unpopulated button (U33). When jumped while the power button is pressed, this appears to put the bootloader into USB recovery mode. It enumerates with an nvidia vendor id. Presumably nvflash or tegrarcm could be used to unbrick the device.
I haven't done anything with the bootloader recovery since I haven't yet made a backup. I'm not sure how much of the functionality is allowed given the state of the production fuse, but I would think we could use this to at least get back to a stock state.
Click to expand...
Click to collapse
Some NVidia devices lock access out at the nvflash level unless you've got the manufacturer's key. I believe you get locked out with a 0x4 (nvflash's way of saying "go away").
Using fastboot is probably the quickest, easiest, and safest way to test new kernels.
Sent from my SCH-I535 using xda premium
mybook4 said:
Some NVidia devices lock access out at the nvflash level unless you've got the manufacturer's key. I believe you get locked out with a 0x4 (nvflash's way of saying "go away").
Using fastboot is probably the quickest, easiest, and safest way to test new kernels.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ah he makes it sound like it puts you in USB recovery mode fo you could ADB in to push an update.
Just wanted to say I'm totally stoked on this guys! Can't wait to see what you do with this. Wish I could help, but I'm really not a developer.
i agree with rebel! but when you guys have it readyish ill test flash it and tell you what happens!!
So, OUYA isn't really as interested in being an open console as they suggest.
I'm keeping a track of how many requests we get relating custom firmware, and from what I'm seeing the user base is not as interested in custom firmware as you might think, which is echoed by this thread (we've shipped 60,000+ units, and less than 10 people have commented in the last month in this thread about getting access to recovery mode).
That doesn't mean that we're shooting the idea down, you need to keep in mind that in terms of priorities this is way down the list as you'd expect from any feature where it's being requested by less than one tenth of one percent of the user-base.
I'm sure @Wajeemba is familiar with CM requests that a very small minority of the user-base are very passionate about, so hopefully you can understand why we're not rushing to work on this.
Click to expand...
Click to collapse
Go to this thread and let them know we want support:
http://forums.ouya.tv/discussion/1380/recovery-mode
That's not even slightly surprising. If every user demanded CM10 they still wouldn't comply, because then they'd lose their one means of profit (ouya store), the fact that "nobody is asking for it" is their excuse, and they'll think of another one if that ever changes.
This is why we just need to proceed without them. I'm on week two of who knows how many weeks away from home on work, so my efforts at porting CM have been put on hold. Have you been able to make any progress? I'd totally loan my Ouya to Fattire or Dalingrin, or another whiz porter if they'd be willing to work on it...
sonofskywalker3 said:
That's not even slightly surprising. If every user demanded CM10 they still wouldn't comply, because then they'd lose their one means of profit (ouya store), the fact that "nobody is asking for it" is their excuse, and they'll think of another one if that ever changes.
This is why we just need to proceed without them. I'm on week two of who knows how many weeks away from home on work, so my efforts at porting CM have been put on hold. Have you been able to make any progress? I'd totally loan my Ouya to Fattire or Dalingrin, or another whiz porter if they'd be willing to work on it...
Click to expand...
Click to collapse
I'd check with invisiblek about how to avoid bricking the OUYA. Apparently his is bricked. It's stuck in nvflash mode. I think it was a kernel written with a bad init.rc that did it. not sure though.
Sent from my Nexus 7 using xda premium