NEW Root method for Motorola Android Phones - Android Software/Hacking General [Developers Only]

Hi! I just created this thread to let you know that thanks to user dettofatto and me, there's a new root method for Motorola Android Phones (I don't know if it will work for other brands).
NOTE: I tried this method with Gingerbread, I don't know if this will work with other versions.
The method is far from easy, but it works if none of the existing exploits and tricks don't.
Ok, there are some simple-like steps to root your phones:
1. If you have an unrooted gingerbread, ask for a rooted gingerbread userdata partition image (aka CG37) with a modified local.prop file and USB debugging enabled.
The value that you need to modify is ro.sys.atvc_allow_all_adb from 0 to 1.
IMPORTANT: The best you can do is to double wipe the phone and then modify local.prop an allow USB debugging, so the data partition doesn't have any of your personal information.
Then you can create a userdata partition image by typing this in the shell (with root access)
Code:
dd if=/dev/block/userdata of=/sdcard/CG37.smg
or
Code:
busybox dd if=/dev/block/userdata of=/sdcard/CG37.smg
and let it do its work.
2. Once you got your CG37.smg in the SD card, you will have to boot into linux (so you can use sbf_flash).
3. When you are in linux, you need to extract the folder contained in the zip that you can download here mediafire.com/?n100jj66130lgra
4. Then you need to copy the CG37.smg and your original SBF (the non rooted one) to that folder.
5. Now you'll have to start a terminal with root permissions, and move to the folder by typing
Code:
cd <folder>
(where folder is the folder I just mentioned, without the <>, you can drag the folder to the terminal if you don't want to type its address)
4. Then you need to resize that partition to 200 Mb, since sbf_flash won't allow you to flash a big image (approx. 1,1 Gb). You have to type this
Code:
efsck -f CG37.smg
resize2fs CG37.smg 200M
5. Then you need to type
Code:
chmod +x sbf_flash
and then you need to start your phone into bootloader and connect it to the computer, then you type
Code:
./sbf_flash -r --userdata CG37.smg ORIGINAL.sbf
(where ORIGINAL corresponds to the name of your SBF)
and let it its work.
5. Once the phone started up, you now need to run this command
Code:
bash finishroot.sh
And let it finish the work.
6. Now you have your phone rooted. You can just reboot into recovery mode and do a double wipe, because the files that we needed are now in system partition.

Great!!

can't unzip attached!!

It seems xda forum doesn't allow me to add attached files or links. So look at the step 3, the link is there.

didn't upload the sbf_flash, the one i use it stuck in waiting for devices. can't enter bootloader mode, when press @ doesn't appear the menu option. any ideas?

Prometeo88 said:
didn't upload the sbf_flash, the one i use it stuck in waiting for devices. can't enter bootloader mode, when press @ doesn't appear the menu option. any ideas?
Click to expand...
Click to collapse
Done! I uploaded the zip file again with the sbf_flash included, the one I used to flash my phone

Do you actually need the full userdata (I mean userdata as initialized after first boot following a wipe)? Or is having an essentially empty userdata with just the adb directive in local.prop all that's needed? Or does local.prop get ignored if you trigger some "first boot after wipe" tripwires? XT720 is eclair/yaffs2 so some details would be different but the concept is good. I'm just wondering about the "how could you get a rooted userdata" chicken/egg problem if no other rooting method already existed for the phone...

It's gone! Thank you!
I suggest you to reboot in standard recovery... and do it a double wipe..

help...
Anyone ca poste the CG37.smg
I have an unrooted milestone 2 and I can't fine any other motorola to create the file.....

giannihsd said:
Anyone ca poste the CG37.smg
I have an unrooted milestone 2 and I can't fine any other motorola to create the file.....
Click to expand...
Click to collapse
I suggest you to ask for it in the Milestone 2 Forum. Thanks.

rodrigojfuentes said:
I suggest you to ask for it in the Milestone 2 Forum. Thanks.
Click to expand...
Click to collapse
I've just created a thread there, let's hope someone helps us
Do you think we could use the CG37 from other (similar) devices?
For example, as far as i know, the milestone 2 is very similar to the defy and the Pro looks similar too.
We just need it to boot, so we can push the needed files to system.
Have you uploaded your CG37 somewhere, so i can test in on my MS2?

nicofff said:
I've just created a thread there, let's hope someone helps us
Do you think we could use the CG37 from other (similar) devices?
For example, as far as i know, the milestone 2 is very similar to the defy and the Pro looks similar too.
We just need it to boot, so we can push the needed files to system.
Have you uploaded your CG37 somewhere, so i can test in on my MS2?
Click to expand...
Click to collapse
Try it! http://www.mediafire.com/?aweayb68szubuci

Any word on if this will work on DX 621?
I posted on DXF to see if one of the people who took it will try.

Could it be possible to re-upload the required files? The mediafire link in the OP says it has been removed for violation... I was going to try this method for a DX 621, despite having the 604 root method, it would be nice to actually have the 621 kernel.

Hey there!
I really like this development, even though I don't own a Motorola phone. But I thought this deserved a spot on the Portal:
http://www.xda-developers.com/android/universal-gingerbread-root-for-motorola-devices/
I hope you like my write up

PoorCollegeGuy said:
Hey there!
I really like this development, even though I don't own a Motorola phone. But I thought this deserved a spot on the Portal:
http://www.xda-developers.com/android/universal-gingerbread-root-for-motorola-devices/
I hope you like my write up
Click to expand...
Click to collapse
Good job, keep it up
Nice review of my tool also
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5

Skreelink said:
rodrigojfuentes said:
3. When you are in linux, you need to extract the folder contained in the zip that you can download here mediafire.com/?n100jj66130lgra
Click to expand...
Click to collapse
Could it be possible to re-upload the required files? The mediafire link in the OP says it has been removed for violation... I was going to try this method for a DX 621, despite having the 604 root method, it would be nice to actually have the 621 kernel.
Click to expand...
Click to collapse
system.zip

File removed for violation ... ??

I am working on this for the DX right now, there's an issue with making the .smg via dd, as the data partition on the DX is 8GBs. Most microSD cards are FAT32, which doesn't support an 8GB file (4GB max filesize). I got around this by piping dd through gzip and moving the file off for testing.
You can follow my progress on this over on rootzwiki; rootzwiki.com/topic/19318-important-information-regarding-621-system-update/page__st__320#entry635557

omyg said:
system.zip
Click to expand...
Click to collapse
PoorCollegeGuy said:
Hey there!
I really like this development, even though I don't own a Motorola phone. But I thought this deserved a spot on the Portal:
http://www.xda-developers.com/android/universal-gingerbread-root-for-motorola-devices/
I hope you like my write up
Click to expand...
Click to collapse
Thank you very much guys!

Related

[MOD][12/03/09] ADB Remount, Superuser, and Busybox

I'd been trying to figure out how to set up a few simple things in my rooted, post-MR, but otherwise stock CDMA Hero. Namely, ADB Remount permissions (/default.prop file), set up Superuser to properly manage permissions for apps that require root, and install Busybox. Ideally, I wanted to set these up manually. Turns out it's not as simple as one might hope. ADB Remount, for example, requires that you modify and repackage the boot.img/recovery.img.
So, what I've got here is a minimal update.zip file you can apply to your phone via the recovery console. Nothing crazy, it's just MoDaCo's ROM 1.1, but with everything taken out except for the aforementioned items. Once you patch your phone, just these items will be configured and your phone will still look, run, etc. the same as before. Also, a2sd will be copied to your /system/bin directory, but it's something that had to stay in the file for some reason, otherwise the phone wouldn't boot. Probably a setting Paul built into the boot.img.
In any case, here it is. It's working well for me. Hope it helps some of you out too.
****
Thanks goes to Paul of course (MoDaCo) camalot (Droid Explorer) and dagnasty for telling me about the auto-sign plugin that's available in Droid Explorer.
Instructions for manually installing Busybox over here:
http://forum.xda-developers.com/showthread.php?t=591303
****
I responded on ppcgeeks:
mercado79 said:
IAlso, a2sd will be copied to your /system/bin directory, but it's something that had to stay in the file for some reason, otherwise the phone wouldn't boot. Probably a setting Paul built into the boot.img.
Click to expand...
Click to collapse
Yup. It's a script that was added to the boot.img-ramdisk that copies all of your apps to your sd when apps2sd's requirements are met.
So if the sdcard is not partitioned correctly then ap2sd will not run, yes?
Smacky55 said:
So if the sdcard is not partitioned correctly then ap2sd will not run, yes?
Click to expand...
Click to collapse
"Correctly" is relative. If there is no EXT partition on the sdcard, then the ROM won't try to move your applications to it. But the script runs regardless.
Sorry, meant if sdcard isn't partitioned at all. Thanks for the answer.
flipzmode told me in another thread that even though this script is included, that doesn't mean that the update.zip i posted will enable apps2sd for anyone. there's more required in order to get it to work (i stripped most everything out).
A few simple questions. re -stock 1.56... rom
1) in the zip system folder, its refers to /xbin ; does that require that /system/xbin be pre-existent, or will it create it ?
2) busybox is in /system/bin on mine. Do I need to remove it?
a) if so then due to the "busybox --install -s /system/bin"
command , how do i remove the current symbolic busybox entry points?
b)have $PATH changes been applied to overwrite the current export
3) empty init.sh file?
4) google meta references?
I think I may understand the need to get bootstrap-"root" permissions established, is there another way as well?
Thanks for dealing with these noobie questions.
Thanks for this. worked out great.
willy900wonka said:
A few simple questions. re -stock 1.56... rom
1) in the zip system folder, its refers to /xbin ; does that require that /system/xbin be pre-existent, or will it create it ?
2) busybox is in /system/bin on mine. Do I need to remove it?
a) if so then due to the "busybox --install -s /system/bin"
command , how do i remove the current symbolic busybox entry points?
b)have $PATH changes been applied to overwrite the current export
3) empty init.sh file?
4) google meta references?
I think I may understand the need to get bootstrap-"root" permissions established, is there another way as well?
Thanks for dealing with these noobie questions.
Click to expand...
Click to collapse
sorry willy man. not sure what i can tell you. i'm pretty close to being a newbie myself. i never fully understood what the script was doing. i simply took the original modaco update and compared it to another script paul had posted on his forums last fall.
if you unzip the file, you should be able to see everything that's going on. the file structure is super simple, so modify it to suit your needs and give it a try. worst case, you'll need to revert to a nandroid backup. oh, and don't forget you'll need to sign the file and zip it back up in order to flash it onto the phone.
come to think of it, i guess maybe i should update the script using the latest modaco rom, though i'm not sure how helpful it'd be for everyone. to be honest, i've since bitten the bullet and moved on to flipz's rom and the gumbo kernel. runs beautifully!
Ok, so I formated the card, put the .zip file on the sdcard and tried to press home+power to enter the recovery council. When I hold home and press power I am taking to a screen that has an exclamation point and an image of the phone.
Can anyone help?
partylatino420 said:
Ok, so I formated the card, put the .zip file on the sdcard and tried to press home+power to enter the recovery council. When I hold home and press power I am taking to a screen that has an exclamation point and an image of the phone.
Can anyone help?
Click to expand...
Click to collapse
Boot the phone by holding home only. And...I'm assuming you have the recovery console installed and are rooted.
I think the problem is that a recovery boot image was not previously installed. A green screen with a set of options should've appeared.
http://forum.xda-developers.com/showthread.php?t=596879
I prefer 1.2.3
mercado79 said:
Boot the phone by holding home only. And...I'm assuming you have the recovery console installed and are rooted.
Click to expand...
Click to collapse
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
partylatino420 said:
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=596879 explanation
code from : http://forum.xda-developers.com/showthread.php?t=583291
13:
Code:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
14:
Code:
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
http://tinyurl.com/yc96j2z
partylatino420 said:
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
Click to expand...
Click to collapse
Your google search didn't turn anything up on "recovery council" because the operative use would have actually been "recovery console"..
that did it!! Thanks guys!!!
um, what???
mercado79 said:
So, what I've got here is a minimal update.zip file you can apply to your phone via the recovery console.
Click to expand...
Click to collapse
Apply via the recovery console? Sorry, still very new to this. Thanks!
Recovery Console
Go to the recovery console by holding down home when you power your Android. In that menu, you should see something that says 'flash update from SD card'... or something like that... then you choose the .zip that he has so kindly provided us.
Oh, and you have to put the .zip file that he provided on the SD card if that isn't already obvious :/
I also renamed it update.zip once I copied it to my SD card. Hope this clears it up a little. I just rooted my Hero yesterday.. so I am on the same NOOB level.
Do I need to wipe before flashing this / will this wipe my phone if I flash it?
fallonjp said:
Do I need to wipe before flashing this / will this wipe my phone if I flash it?
Click to expand...
Click to collapse
You shouldn't need to wipe your phone; however I really don't think it's a good idea to use this. I put this together last year when we were still running Android 1.5 so it's WAY out of date. Just go with Nfinite's ROMs. He keeps them almost completely stock (depending on which you choose) and they can serve as great back-up / go-to ROMs.

[BOOT ANIMATION] -- LCARS Custom Boot Animation by Jeremy Herrmann

LCARS boot animation replacement for SPRINT HTC EVO 4G ONLY
NEW METHOD USING SIGNED ZIP THANKS TO nebenezer
Download signed zip to sd and flash with recovery
Signed zip is in download section below.
NOW AVAILABLE FOR THE GALAXY TAB AS WELL, THANKS TO nobleskill
Link to Galaxy Tab thread here
OLD METHOD:
To install...
extract the zip file
reboot into recovery using rom manager
In the partitions menu select mount /system (or if using other recovery then manually mount /system through adb)
Code:
adb push [path to extracted bootanimation.zip] /system/customize/resource/bootanimation.zip
adb push [path to extracted SPC_animation_final.mp3] /system/customize/resource/SPC_animation_final.mp3
adb reboot
I use this on my own phone and love it.... I am happy to answer questions about installation if they come up, but feel the need to post the usual disclaimer of.... while there is no reason this should do anything negative to your phone as long as you follow the directions, should you brick your phone or cause your phone to act goofy, or drop your phone in the toilet, neither the lcars custom boot animation or myself are in any way shape or form responcible for it. If you don't like that then don't download it.
EDIT: Screen Shots as requested
Had to attach because i'm apperently not verified to post images
Can we get some screenshots?
works amazing and i can rub it in all my star wars fans faces
Oh I love it thank you.
These are probably noob questions.
Does this need root? Do I unzip to the root of the memory card? I'm going to guess a rom manager does need root. Is the code only for adb and not if you have rom manager?
jeffrimerman said:
Does this need root? Do I unzip to the root of the memory card? I'm going to guess a rom manager does need root. Is the code only for adb and not if you have rom manager?
Click to expand...
Click to collapse
Yes you need root because you have to write to the /system partition.
It is easiest to do with ROM Manager's recovery which is why i gave instructions for that.
You extract the zip to your computer and use adb to push to the phone in the correct location.
damn, wish i could flash this like a normal rom :-\
imneveral0ne said:
damn, wish i could flash this like a normal rom :-\
Click to expand...
Click to collapse
I would like to offer this as an update.zip, but i don't know how to sign them... if someone wants to email or pm me that information i will be happy to post it in an update.zip format
Process that I did and its not working
adb reboot recovery
Once the phone was in recovery I did
C:\Users\Tim\Desktop\Android root\tools>adb push bootanimation.zip /system/custo
mize/resource/bootanimation.zip
2584 KB/s (3253387 bytes in 1.229s)
C:\Users\Tim\Desktop\Android root\tools>adb push SPC_animation_final.mp3 /system
/customize/resource/SPC_animation_final.mp3
2402 KB/s (223929 bytes in 0.091s)
adb reboot
Nothing.
Dariuas,
Sounds like the system partition is not mounted...
jramz; said:
In the partitions menu select mount /system (or if using other recovery then manually mount /system through adb)
Click to expand...
Click to collapse
this is covered in the ROM Manager Menu which it sounds like you're not using so if you add
Code:
adb shell mount /system
once in recovery but before the file pushes you should be fine
Outstanding, it works. Now if I want to undo it? :O
Dariuas said:
Outstanding, it works. Now if I want to undo it? :O
Click to expand...
Click to collapse
Not sure why you'd want to....
But... if you do... just push these files the same way and you'll have the sprint 4g back
Nice!
I'm more of a TOS fan but this looks too nice for me to be picky.
I'm really new to Android. Is there a way to do this on the Mac? Thanks.
StormCell said:
I'm really new to Android. Is there a way to do this on the Mac? Thanks.
Click to expand...
Click to collapse
I don't use a mac, nor do i have any access to a mac... however since the android SDK is what gives you access to ADB and there is an Android SDK for mac... i'm assuming that you can do this by following the same steps using the android sdk for mac which you can get:
Here
Great job man, just pushed it to my Evo and its workin great. Thanks.
Pushed bootanimation.zip to Nexus One and it also works fine there.
This is SOOOOOOO awesome! Any chance of this becoming a theme?
jramz said:
I don't use a mac, nor do i have any access to a mac... however since the android SDK is what gives you access to ADB and there is an Android SDK for mac... i'm assuming that you can do this by following the same steps using the android sdk for mac which you can get:
Here
Click to expand...
Click to collapse
With some help I figured out how to do this last night pm me and I think i could get things working for you.
Flashed it and it's way awesome - I'd prefer it with no audio though. Can I just push a different mp3 or an empty file of the same name as the mp3?

HOWTO: Create your own TnT OTA updater system, using the Android Emulator

Pre-req: An understanding of how to install the SDK and how to built out a generic 2.2 device. I won't go into that, here. Let's also assume that the name of your new 2.2 image is "TnT", for the sake of these instructions.
So, assuming you have a 2.2 generic device in the emulator, ready for use, these are the steps that worked for me:
1- Get a copy of TnT's OTAUpdate.apk. You can grab a copy here: http://www.mediafire.com/?zaiiz12s599hlmk
2- Update the android image so that it has a system.image that you can alter. The way to do that is to take the sample system.img in /platforms/android-8/images and copy it into the same location as your image.
3- Reboot into the emulator device, which now has your new image. This is the syntax used, in Ubuntu:
./emulator -avd TnT -partition-size 96
4- Use ADB or sideload OTAUpdate.apk into the emulator, as a user apk (it should install fine).
5- Edit the build.prop so that the device thinks it's a TnT build. The three lines you want to emulate are:
Code:
ro.build.description
ro.build.fingerprint
ro.tapntap.version.release
6 - Reboot again. Then, run the OTA updater. It should update you if there's a new firmware avaiable. You can't actually install it here, but just check logcat and you should see the ZIP location and then just grab it manually. If there are no new updates when you do this, you might want to test by updating the three entries to something older, like this:
Code:
ro.build.description=harmony-user 2.2 FRF91 hudson-20101122-122046-TnT_SVN_2967 test-keys
ro.build.fingerprint=Flextronics/harmony/harmony/:2.2/FRF91/hudson-20101122-122046-TnT_SVN_2967:user/test-keys
ro.tapntap.version.release=1.0.1-2967
That way, you know that an update is out there and this should pick up on that.
Hope this helps!
Roebeet,
Your key looks like you are emulating the 2967 release. Have you tried it with the 3053 version?
Could this be why folks are not getting the OTA update on their Gtabs?
Bill
woneill1701 said:
Roebeet,
Your key looks like you are emulating the 2967 release. Have you tried it with the 3053 version?
Could this be why folks are not getting the OTA update on their Gtabs?
Bill
Click to expand...
Click to collapse
I was emulating a 3053 device, when I first set this up. I just used 2967 in this example, just because some people are still seeing 3053 as the latest.
roebeet said:
2- Update the android image so that it has a system.image that you can alter. The way to do that is to take the sample system.img in /platforms/android-8/images and copy it into the same location as your image.
Hope this helps!
Click to expand...
Click to collapse
Hi Roebeet, I was going to set this up in the emulator but I wasn't sure what you meant by this step. I have several avd's setup and one for 2.2. Where do I copy the system.img from the android-8/images folder to? (my .avd folder?).
Thanks!
EDIT: I tried to copy the system.img to my appropriate .avd/... folder but it hangs on boot.
prscott1 said:
Hi Roebeet, I was going to set this up in the emulator but I wasn't sure what you meant by this step. I have several avd's setup and one for 2.2. Where do I copy the system.img from the android-8/images folder to? (my .avd folder?).
Thanks!
Click to expand...
Click to collapse
That's the place....
Sprdtyf350 said:
That's the place....
Click to expand...
Click to collapse
Hmmm. it is hanging on boot up. what permissions need to be on the system.img?
prscott1 said:
Hmmm. it is hanging on boot up. what permissions need to be on the system.img?
Click to expand...
Click to collapse
I didn't do anything to it. Just copied it. I seem to remember running into the same issue unless I create the emulator, and then run it once before you put the system image in if I remember correctly.
Sprdtyf350 said:
I didn't do anything to it. Just copied it. I seem to remember running into the same issue unless I create the emulator, and then run it once before you put the system image in if I remember correctly.
Click to expand...
Click to collapse
Okay, I started a new avd - started it. shut it down. copied system.img. started it.
It boots now. but still won't let me write to the system folder. I pulled the build.prop to edit it but it won't let me push it back. Says it failed to copy it ... Out of memory
EDIT: I changed system.img to read + write for all but now it is in a boot loop again on the android bootanimation.
prscott1 said:
Okay, I started a new avd - started it. shut it down. copied system.img. started it.
It boots now. but still won't let me write to the system folder. I pulled the build.prop to edit it but it won't let me push it back. Says it failed to copy it ... Out of memory
EDIT: I changed system.img to read + write for all but now it is in a boot loop again on the android bootanimation.
Click to expand...
Click to collapse
And all of the sudden the light in my head comes on... I had the same issue. Had to start the emulator from a command line like this...
emulator -avd TnT -partition-size 128
Need to run that from wherever you happen to have emulator.exe located. Mine is in the tools folder like yours probably is. Change the name TnT to whatever yours is called. Has something to do with not having a partition to write to...
Edit: Once you have the build.prop changed you can start the emulator from the GUI. Seems to only need to be run from the command line to get it built.
Sprdtyf350 said:
And all of the sudden the light in my head comes on... I had the same issue. Had to start the emulator from a command line like this...
emulator -avd TnT -partition-size 128
Need to run that from wherever you happen to have emulator.exe located. Mine is in the tools folder like yours probably is. Change the name TnT to whatever yours is called. Has something to do with not having a partition to write to...
Click to expand...
Click to collapse
Yes! I just googled and found out the problem was I should start it from command line. I'm working now!
Thanks for your help.
I'm actually using a Galaxy tab addon for my play ground right now.
prscott1 said:
Yes! I just googled and found out the problem was I should start it from command line. I'm working now!
Thanks for your help.
I'm actually using a Galaxy tab addon for my play ground right now.
Click to expand...
Click to collapse
Cool... Fun stuff isn't it
i need OTA enginner whos build my system
i need OTA enginner whos build my system any body here contact me
thank u

HELP!!!! BOOTLOOP atrix 2

im stuck in a loopboot on my ME865 after installing 4.2.2 from this http://forum.xda-developers.com/showthread.php?t=2121029
i flashed the rom but didnt flash the gapps because it said to do it after with built in recovery but i didnt know how to so i used this http://forum.xda-developers.com/showthread.php?t=1346977
which got me into the loop boot i can boot into fastmode
PLEASE HELP ME!!!!!!
DaFrenchTaco said:
im stuck in a loopboot on my ME865 after installing 4.2.2 from this http://forum.xda-developers.com/showthread.php?t=2121029
i flashed the rom but didnt flash the gapps because it said to do it after with built in recovery but i didnt know how to so i used this http://forum.xda-developers.com/showthread.php?t=1346977
which got me into the loop boot i can boot into fastmode
PLEASE HELP ME!!!!!!
Click to expand...
Click to collapse
Well, first, turn off the phone and charge it so you don't loose battery.
Second, never install another recovery on top of an existing one without knowing what you are doing - ask first.. (You get into the built-in recovery on that cm10.1 by tapping the volume down button at the end of the red moto logo when the lights come on).
Next, you could possibly fix your system with adb and switching some files.. but that would take a lot of explaining if you are not familiar with it.. plus, you might not get adb recognized during the bootloop.
So, you need to use the FXZ files for your phone/region... Or, just flash the system.img only.. See here: http://forum.xda-developers.com/showpost.php?p=41436876&postcount=1106 - and see the link linked there.
EDIT: If you can get adb recognized, you might be able to just run these few lines to fix things from the command prompt:
Code:
adb shell
su
mount -o rw,remount /system
rm /system/bin/hijack
sh /system/bin/finalize_release
exit
alteredlikeness said:
Well, first, turn off the phone and charge it so you don't loose battery.
Second, never install another recovery on top of an existing one without knowing what you are doing - ask first.. (You get into the built-in recovery on that cm10.1 by tapping the volume down button at the end of the red moto logo when the lights come on).
Next, you could possibly fix your system with adb and switching some files.. but that would take a lot of explaining if you are not familiar with it.. plus, you might not get adb recognized during the bootloop.
So, you need to use the FXZ files for your phone/region... Or, just flash the system.img only.. See here: http://forum.xda-developers.com/showpost.php?p=41436876&postcount=1106 - and see the link linked there.
EDIT: If you can get adb recognized, you might be able to just run these few lines to fix things from the command prompt:
Code:
adb shell
su
mount -o rw,remount /system
rm /system/bin/hijack
sh /system/bin/finalize_release
exit
Click to expand...
Click to collapse
do you know any other place to download the zip file
and wheres the fxz folder supposed to be
DaFrenchTaco said:
do you know any other place to download the zip file
and wheres the fxz folder supposed to be
Click to expand...
Click to collapse
Look here
http://forum.xda-developers.com/showthread.php?t=2176124
Make sure you install the correct firmware otherwise you will brick.
And next time please search before posting. This has been asked a number of times before
Sent from my MB865 using XDA Premium HD app
nikhJ said:
Look here
http://forum.xda-developers.com/showthread.php?t=2176124
Make sure you install the correct firmware otherwise you will brick.
And next time please search before posting. This has been asked a number of times before
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray
alteredlikeness said:
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray
Click to expand...
Click to collapse
sorry for asking u so much stuff but i lost without help
ok so it says i have to edit it with the moto android depacker but i dont see any tutorials on how to do that
would it boot up if i use this hack to install the honk kong boot img on to it or would mess my device since its on "4.2.2." http://forum.xda-developers.com/showthread.php?p=35000737
DaFrenchTaco said:
sorry for asking u so much stuff but i lost without help
ok so it says i have to edit it with the moto android depacker but i dont see any tutorials on how to do that
would it boot up if i use this hack to install the honk kong boot img on to it or would mess my device since its on "4.2.2." http://forum.xda-developers.com/showthread.php?p=35000737
Click to expand...
Click to collapse
I am very confused at what you want to do. That link is only to root your device. But, if you are bootlooping, you need to replace your system.img.
You should download the entire SBF/FXZ zip file for your device/region/firmware. Then unzip it into a folder on your computer (best if it's close to C:\ with spaces in the path). Are you using a Windows OS on your computer?
Then, grab the restore-to-ics_win-batch.zip AND the restore-ics-system-only.bat.txt (remove the .txt extension) attached in this post: http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Mix those files in with the big FXZ files that you just unzipped. Then run the .bat file to flash the system.img only. If that doesn't work, then open the other .bat file (use Notepadd++ or similar), check that everything that is being flashed is actually in your folder and has the same name... and flash the entire FXZ. If none of that helped, then you probably flashed the wrong files to your phone.
Just flashing the system.img only is probably the safest.. Because if it's wrong, you can just flash another one. The other files in the FXZ package can mess up your phone if they are not for your specific device.
EDIT: If you still did not flash anything else, you could try to use adb... Get that restore-to-ics_win-batch.zip that I linked above.. Unzip it to your desktop. Power on your phone so it bootloops and connect with USB. Open a command prompt on the restore-to-ics_win-batch folder by holding down shift and right-click. Then type adb devices - if it returns a number with the word "device" (not the word "offline"), then you can try to use those adb codes I posted in my previous post. Otherwisem you need to use fastboot and flash fxz or system only.
alteredlikeness said:
I am very confused at what you want to do. That link is only to root your device. But, if you are bootlooping, you need to replace your system.img.
You should download the entire SBF/FXZ zip file for your device/region/firmware. Then unzip it into a folder on your computer (best if it's close to C:\ with spaces in the path). Are you using a Windows OS on your computer?
Then, grab the restore-to-ics_win-batch.zip AND the restore-ics-system-only.bat.txt (remove the .txt extension) attached in this post: http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Mix those files in with the big FXZ files that you just unzipped. Then run the .bat file to flash the system.img only. If that doesn't work, then open the other .bat file (use Notepadd++ or similar), check that everything that is being flashed is actually in your folder and has the same name... and flash the entire FXZ. If none of that helped, then you probably flashed the wrong files to your phone.
Just flashing the system.img only is probably the safest.. Because if it's wrong, you can just flash another one. The other files in the FXZ package can mess up your phone if they are not for your specific device.
EDIT: If you still did not flash anything else, you could try to use adb... Get that restore-to-ics_win-batch.zip that I linked above.. Unzip it to your desktop. Power on your phone so it bootloops and connect with USB. Open a command prompt on the restore-to-ics_win-batch folder by holding down shift and right-click. Then type adb devices - if it returns a number with the word "device" (not the word "offline"), then you can try to use those adb codes I posted in my previous post. Otherwisem you need to use fastboot and flash fxz or system only.
Click to expand...
Click to collapse
can not load "system.img" i went in and edited the the text to C:\system.img but it wont work
i tried the other one didnt work is the path supposed to be = C... or =C... what i mean is there a space or not
is the bat file scripted to work with me865 or only with mb865 flashing that sbf/fxz
and is the sbf/fxz file supposed to be unzipped and in a folder
or compressed
DaFrenchTaco said:
can not load "system.img" i went in and edited the the text to C:\system.img but it wont work
i tried the other one didnt work is the path supposed to be = C... or =C... what i mean is there a space or not
is the bat file scripted to work with me865 or only with mb865 flashing that sbf/fxz
and is the sbf/fxz file supposed to be unzipped and in a folder
or compressed
Click to expand...
Click to collapse
Unzip the sbf/fxz - all the files in a single folder, on your desktop or in the root of your C:\ drive (like C:\ InlineFlashing_Edison_XX-XX-XX_CFC_P3_APBP.xml - where that is the name of the folder)
Then put the .bat file and other files from my restore_to_ics zip and the restore_system_only .bat in that same folder.
Then, connect with USB while in AP fastboot mode, see if it says "OK to program", then double-click the restore-ics-system-only.bat
alteredlikeness said:
Unzip the sbf/fxz - all the files in a single folder, on your desktop or in the root of your C:\ drive (like C:\ InlineFlashing_Edison_XX-XX-XX_CFC_P3_APBP.xml - where that is the name of the folder)
Then put the .bat file and other files from my restore_to_ics zip and the restore_system_only .bat in that same folder.
Then, connect with USB while in AP fastboot mode, see if it says "OK to program", then double-click the restore-ics-system-only.bat
Click to expand...
Click to collapse
thank u so much is it safe to root and install cm10 with bootstrap?
and how do you enter cmw in cm10.1?
THX
Sorry to intrude with my following off-topic statement, but that was a lot of detailing you did there altered. xD Great job and it'll serve well to assist others who need the same solution.
Now on-topic;
Yes it's okay to root with any of the ICS root methods available.
Sent from the Ace's MB865 using xda app-developers app
Aceofzeroz said:
Sorry to intrude with my following off-topic statement, but that was a lot of detailing you did there altered. xD Great job and it'll serve well to assist others who need the same solution.
Now on-topic;
Yes it's okay to root with any of the ICS root methods available.
Sent from the Ace's MB865 using xda app-developers app
Click to expand...
Click to collapse
yeah true that this is a very detailed guide/thread i hope my problem will help all the others now that i know how it feels to mess up a two day old phone
alteredlikeness said:
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray
Click to expand...
Click to collapse
Ah..sorry my bad..Forgot his phone was me865..
Question about the original problem
DaFrenchTaco said:
im stuck in a loopboot on my ME865 after installing 4.2.2 from this http://forum.xda-developers.com/showthread.php?t=2121029
i flashed the rom but didnt flash the gapps because it said to do it after with built in recovery but i didnt know how to so i used this http://forum.xda-developers.com/showthread.php?t=1346977
which got me into the loop boot i can boot into fastmode
PLEASE HELP ME!!!!!!
Click to expand...
Click to collapse
Did you solve this? I have the same problem...
---------- Post added at 10:17 PM ---------- Previous post was at 10:01 PM ----------
alteredlikeness said:
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray
Click to expand...
Click to collapse
I encounter the same issue. I am not able to see the device in ADB.exe, but I am able to see in FASTBOOT.exe
Can I flash in FASTBOOT.exe?
Thank you
pa 3.60 problem from altered likeness
I tried to install Paranoid android 3+ from the link from altered likeness which was successful but the problem started after rebooting .The animation goes on forever and the first time the reboot gave me a message stating updating android system . Any solution to get back would be of a lot of help .I also have the recovery of my stock 4.0.4 done using CWM .
Same problem extension
Hi....
I faced the same problem and now after following the procedure facing a new prob.
Things I did
1. Upgraded from ICS to CM10.1--->Success
2. Forgot to install GAPPS ..so installed Atrix2Strap.apk (Bootloop problem started)
3. Flashed my atrix 2 with the procedure mentioned in the link by alteredlikeness.(Overcame the bootloop problem)
Now the problem is
I'm getting the lock screen but when I try to unlock it stays unresponsive.
How do I solve this. Please Help me out
Thnks guys
kyashwanth said:
Hi....
I faced the same problem and now after following the procedure facing a new prob.
Things I did
1. Upgraded from ICS to CM10.1--->Success
2. Forgot to install GAPPS ..so installed Atrix2Strap.apk (Bootloop problem started)
3. Flashed my atrix 2 with the procedure mentioned in the link by alteredlikeness.(Overcame the bootloop problem)
Now the problem is
I'm getting the lock screen but when I try to unlock it stays unresponsive.
How do I solve this. Please Help me out
Click to expand...
Click to collapse
Thanks guys for the wonderful tutorial...
Solved the issue by inserting a sim card into the phone.
Now I'm on CM 10.1

[shell][utility][terminal] munky-tool

***MUNKY-TOOL***
IS AN ONBOARD ANDROID UTILITY
FEATURES
[*]Copy system.img
[*]Copy boot.img
[*]Backup efs
[*]Logcat
[*]Backup and Restore Contacts
[*]Out For A Rip
Munky-tool will locate and copy most partitions without you having to track down paths. This is convenient if you use a ROM kitchen, or just want to make a backup of your system without using custom recovery. Some devices do have weird partition names, and munky-tool will not find them. If this happens to you, run the following command in terminal emulator
Code:
ls /dev/block/platform/*/by-name
Paste the output and your device name in the comments, and I will work your device in if possible.
INSTRUCTIONS
Download zip or clone git
Place extracted munky-tool folder in system partition (must be able to set permissions)
Set permissions of munky-tool script (not the directory) to at least 775 (rwx rwx rw)
Open terminal emulator and key in 'su' for root permissions
cd to the munky-tool directory
Type ./munky-tool to execute the script and start the utility
​
DOWNLOAD
github
Dude once again you're creativity and hard work is paying off. Great job man
Style point for the rip bud!
Sounds very helpfull and as markbencze already replyed I gues it's working on the O+O too. Have to try it in the next days.
thx markbencze for sharing.
SaschaKH said:
Sounds very helpfull and as markbencze already replyed I gues it's working on the O+O too. Have to try it in the next days.
thx markbencze for sharing.
Click to expand...
Click to collapse
Yes. I tested it on my OPO. It went out for a rip. It will run on any device, and it will find the partitions on most.
Where's the download link dude, i'm not find download link from github ?
itsnie said:
Where's the download link dude, i'm not find download link from github ?
Click to expand...
Click to collapse
On the right side of page near the clone url, there should be a button that says download as zip.
Just realized you have to be in desktop view to see the download as zip button. I will post an additional link a little later.
Just added backup and restore contacts.
N-i-c-e!
Thank you.
I've been working on the same sort of thing, and trying to figure out how to get adb connected to the phone with debugging off, for those people (I won't use the word I'm thinking of) who don't make backups, then break the screen, or bootloop the phone. Your script makes finding the data partition trivial, but I'm still working on the "force debugging on from outside" part.
But munky is going to be part of my phone from now on.
Rukbat said:
N-i-c-e!
Thank you.
I've been working on the same sort of thing, and trying to figure out how to get adb connected to the phone with debugging off, for those people (I won't use the word I'm thinking of) who don't make backups, then break the screen, or bootloop the phone. Your script makes finding the data partition trivial, but I'm still working on the "force debugging on from outside" part.
But munky is going to be part of my phone from now on.
Click to expand...
Click to collapse
Thanks, man. Glad to hear you like it.
mike the inkman said:
***MUNKY-TOOL***
IS AN ONBOARD ANDROID UTILITY
FEATURES
[*]Copy system.img
[*]Copy boot.img
[*]Backup efs
[*]Logcat
[*]Backup and Restore Contacts
[*]Out For A Rip
Munky-tool will locate and copy most partitions without you having to track down paths. This is convenient if you use a ROM kitchen, or just want to make a backup of your system without using custom recovery. Some devices do have weird partition names, and munky-tool will not find them. If this happens to you, run the following command in terminal emulator
Code:
ls /dev/block/platform/*/by-name
Paste the output and your device name in the comments, and I will work your device in if possible.
INSTRUCTIONS
Download zip or clone git
Place extracted munky-tool folder in system partition (must be able to set permissions)
Set permissions of munky-tool script (not the directory) to at least 775 (rwx rwx rw)
Open terminal emulator and key in 'su' for root permissions
cd to the munky-tool directory
Type ./munky-tool to execute the script and start the utility
​
DOWNLOAD
github
Click to expand...
Click to collapse
Good Tool, do you already plan to support restore EFS? which make a full loop of running time change the EFS setting without a PC,
this can help to me to control the modem band preset selections for network testing purpose.
Azlun said:
Good Tool, do you already plan to support restore EFS? which make a full loop of running time change the EFS setting without a PC,
this can help to me to control the modem band preset selections for network testing purpose.
Click to expand...
Click to collapse
It is usually done in bootloader, but I am pretty sure I can make it work. Just need to test it before I release it. I am also going to release this as an apk soon. (Don't know how soon, but I probably won't have time for a few weeks)
An app that we can point new users to that will back up their userdata partition? Fantastic!
Rukbat said:
An app that we can point new users to that will back up their userdata partition? Fantastic!
Click to expand...
Click to collapse
Yeah, I think it will fill a need. I am going to do an APK to do the things from this script, and a corresponding GUI Linux package for APK modding, and maybe do something for Windows as I get time. In the process of moving somewhat unexpectedly, so it is taking longer than I would have liked.

Categories

Resources