HOWTO: Create your own TnT OTA updater system, using the Android Emulator - G Tablet General

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

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.

How to turn an RUU into a flashable ROM

I'm sorry to say I have no idea but I'm now determined to learn how and I think I'll start with a linux partition.
Anyone care to join me?
I think the Avabox that avaluanchemods posted up included the files to pull out the files from the .img, after that wouldn't it be just like modifying another ROM (with a lot more to mod, of course, to gain root, etc.)?
danaff37 said:
I think the Avabox that avaluanchemods posted up included the files to pull out the files from the .img, after that wouldn't it be just like modifying another ROM (with a lot more to mod, of course, to gain root, etc.)?
Click to expand...
Click to collapse
nope, this ruu is different
doesn't work like that.
well, once you have the images you can use yaffs, for the system image, but getting the images from the ruu...
regaw_leinad said:
nope, this ruu is different
doesn't work like that.
well, once you have the images you can use yaffs, for the system image, but getting the images from the ruu...
Click to expand...
Click to collapse
Hahaha yeah, getting the images from the ruu is a blast!
u guys want the new sprint ruu turned into a flashable update.zip? isn't that what damages 2.06 basically is? if not i'll do it for you.
I think it's really more that they wanna learn how. Anyone down to throw out some pointers?? I'd be interested to learn too
I was actually just looking into pulling the files from the ruu myself.
extract the exe file. unyaffs the system.img. make an update-script in META-INF/com/google/android/. zip the boot.img META-INF/ folder, and system/ folder and sign it. nothing more to it. lol
zenulator said:
u guys want the new sprint ruu turned into a flashable update.zip? isn't that what damages 2.06 basically is? if not i'll do it for you.
Click to expand...
Click to collapse
well, well howdy stranger! zen you were a great dev on the vogue/android...we need you here my man!
fixxxer2008 said:
well, well howdy stranger! zen you were a great dev on the vogue/android...we need you here my man!
Click to expand...
Click to collapse
this communtiy is a little crazy for my taste. but darchstar answered the question.
http://code.google.com/p/zen-droid/downloads/list
this is a link to the files i use. you must have linux installed to use them as well as pearl which should be installed on most distros. you'll prob have to chmod them executable if you download them.
any questions post them and i'll try to help. i'm glad to see people trying to learn.
regaw_leinad said:
nope, this ruu is different
doesn't work like that.
well, once you have the images you can use yaffs, for the system image, but getting the images from the ruu...
Click to expand...
Click to collapse
thats all you need for a rom. is the /system. just place that in a folder along with the boot.img. andddd archive and sign. you have a rom now.
and if you want to know a secret. lol
if you are in windows, all .exe's are archived as zips. change .exe to .rar/zip and then you can unzip and have everything. very simple.
o and you need an update script which you can create, or take someones from a rom and edit it to fit the RUU. and as always give credit where needed
Avalaunchmods said:
thats all you need for a rom. is the /system. just place that in a folder along with the boot.img. andddd archive and sign. you have a rom now.
and if you want to know a secret. lol
if you are in windows, all .exe's are archived as zips. change .exe to .rar/zip and then you can unzip and have everything. very simple.
o and you need an update script which you can create, or take someones from a rom and edit it to fit the RUU. and as always give credit where needed
Click to expand...
Click to collapse
interesting. so in theory this could be done as easily on windows, no linux partitions?
mountaindont said:
interesting. so in theory this could be done as easily on windows, no linux partitions?
Click to expand...
Click to collapse
i hate linux. lol so yes
Not all exe's work like that. Like this one for example....
not even 7zip can get into it.
danaff37 said:
Not all exe's work like that. Like this one for example....
not even 7zip can get into it.
Click to expand...
Click to collapse
uniextract, google it. you are correct some are a certain type that cant be extracted but 99% of RUU's can.
Ok here is a basic run through for extracting the RUU and making an update.zip
1. Run the RUU in windows or through wine. You don't have to run it completely with your phone plugged in. The install shield will extract the files to a tmp folder. Search through your tmp folders until you find it. Inside should be a rom.zip. Unzip it. Inside it should be system.img data.img boot.img etc...
2.
a: Switch to linux. Use unyaffs to extract the system.img. I usually make a directory called system in the same directory as the system image and cd to it. then issue.
unyaffs ../system.img
this will extract it into the system directory that your in. make your changes. add apps/busybox/su etc..
b: You can also use unyaffs for windows from here: http://code.google.com/p/unyaffs/downloads/list it should do the same thing but I've never used it.
3. If you want apps pre-installed to /data then make a data directory with a apps directory in it and put your extra apps there like wireless tether etc... so now you have a directory with
/system
/data
boot.img
4. Use an update script from another rom as a base and modify it to symlink busybox, set the correct permissions, copy data write boot.img, clear cache etc... read through some other update scripts to get the idea of whats going on it's simple text based stuff. The update script is inside the directory
META-INF/com/google/android.
Once done move the META-INF directory to your working directory. so you should now have
/system
/data
/META-INF
boot.img
Zip up the above directorys/files into something like myrom.zip
5. Sign the zip. You'll need java and a testsign.jar and the android sdk. I've never done it without the sdk. Create a directory called sign inside the tools directory of the android sdk. Move testsign.jar and your myrom.zip to the sign directory. Execute the following command while in the sign directory
java -classpath testsign.jar testsign myrom.zip myrom-signed.zip
6. Copy myrom-signed.zip to the root of your sdcard. reboot recovery. nandroid backup. wipe/factory reset. flash update zip.
Good luck.
zenulator said:
Ok here goes a basic run through for extracting the ruu and making an update.zip
1. Run the ruu in windows or through wine. It will be extracted to a tmp folder. Search through the tmp folders until you find it. Inside should be a rom.zip. Unzip it. Inside it should be system.img data.img boot.img etc...
2. Switch to linux. Use unyaffs to extract the system.img. I usually make a directory called system in the same directory as the system image and cd to it. then issue.
unyaffs ../system.img
this will extract it into the system directory that your in. make your changes. add apps/busybox/su etc..
3. if you want apps pre-installed to /data then make a data directory with a apps directory in it and put your extra apps there like wireless tether etc... so now you have a directory with
/system
/data
boot.img
4. use a update script from another rom as a base and modify it to symlink busybox, set the correct permissions, copy data write boot.img, clear cache etc... read through some other update scripts to get the idea of whats going on it's simple text based stuff. the update script is inside the directory META-INF/com/google/android. once done move it to your working directory. so you should now have
/system
/data
/META-INF
boot.img
Zip up the above directorys/files into something like myrom.zip
5 sign the zip. you need java and a testsign.jar and the android sdk. i've never done it without the sdk. create a directory called sign inside the tools directory of the android sdk. move testsign.jar and your myrom.zip to the sign directory. execute the following command while in the sign directory
java -classpath testsign.jar testsign myrom.zip myrom-signed.zip
6. copy myrom-signed.zip to the root of your sdcard. reboot recovery. nandroid backup. wipe/factory reset. flash update zip.
Good luck.
Click to expand...
Click to collapse
uhh...i think ill leave that one too the pros
zenulator said:
Ok here goes a basic run through for extracting the ruu and making an update.zip
Click to expand...
Click to collapse
Interesting. Sounds easy enough, I'll definitely have a go. Thanks for the tutorial.
pseudoremora said:
Interesting. Sounds easy enough, I'll definitely have a go. Thanks for the tutorial.
Click to expand...
Click to collapse
+5, HOLY CRAP guys, I havent checked the forum in a few hours.
Thank you all so much for the insight.
I'll be back in a week!!
nebenezer said:
+5, HOLY CRAP guys, I havent checked the forum in a few hours.
Thank you all so much for the insight.
I'll be back in a week!!
Click to expand...
Click to collapse
There's an easy fix for your problem... Install the XDA Android App. Seriously, my soul belongs to Android now... and XDA has become my home, I HAVE to know what's going on at all times... it's like a drug, lol.

[Rom test] Don's Ghetto Rom SenseLess Speed Quicker Install 5/3/10

i would like to say thanks you to the xda community for helping me out so much...
i would like to thank alot of people whohave worked very hard to this all...
Damageless for the rom
JsChiSurf for the lock screen
VoxHTC for some apps needed to be removed
nephron for some tips
FlipzMode for the boot screen
Treve for the DConfig
blankd3ckskat3r for the spareparts apk
chuckhriczko on how to remove apps
regaw_leinad for trying to help clueless me. lol
pseudoremora for making it much more shorter.
and everyone else that i forgot. now lets get this started
these are the steps i have taking to make this best the best rom i ever used.
i love it and it is very fast in my eyes. the only problem is you have to do the rom your self.
before we get started lets go over the rom. it is the eris leak that damaged posted up. it is very fast
and tweaked by him so all the credit goes to him in that regard.
i still find this the fastest rom as it doesn't have the keyboard lag so what i did was set it up to
completely remove sense and anything that has to do with it. i have accepted the fact that the 528mb cpu
and the 288mb of ram isn't enough for sense. so after this it will be senseless and wicked fast. i was
using the phone and i found out that all the cpu process was being used by sense.
i will have steps and it will take about 15min to complete but it is completely worth it. trust me.
here is the steps needed to do it. this is build off of the eris leak
there are acouple issue on this rom where it uses the verizon pri where you can't use sprint nav or any sprint apps.
everything is in here http://forum.xda-developers.com/showthread.php?t=653735
1. Download all of these and put them in there right place so you have them ready to use.
a. Download this rom (place on sd card)
http://forum.xda-developers.com/showthread.php?t=652564
b. download the apk of spareparts below and place it in C:\android-sdk-windows\tools
c. download the lockscreen(place on sd card)
http://forum.xda-developers.com/showthread.php?t=670034
d. Removed until i can tell it's working
e. Removed until i can tell it's working
f. Download asop mms below (place on sd card)
G. Download dancing-boot-fresh.zip Below (place on sd card)
h. Audioaudiofix below (place on sd card)
I. Download remove-apps-signed.aip below (place on sd card)
http://forum.xda-developers.com/showthread.php?t=657244
2.Flash A(the rom), D(Removed), E(Removed+), h(Audiofix), G (dancing-boot-fresh.zip) I(Remove-apps-signed.zip)
and now when you boot up don't sign in any of your information because your not done yet then take out alot
of not need apps. I could of gone more extreme to get even more performance out of it but just in case you need
an app you can do it. now remove these apps by openning up the CMD in windows. don't touch your phone yet until
you are finish...
now the phone booted up. open up the command prompt and open it up and type in this
cd C:\android-sdk-windows\tools
adb install SpareParts.apk
exit out of the command prompt again and open it install this
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app
mv HtcLockScreen.apk HtcLockScreen.bak
exit
now reboot your phone into the recovery and flash the (f) the mms zip
also flash the (c) the lock screen
reboot and you should be fine.
you can enable comp-cache and keep home apps in memory using this version of spareparts
Now the phone is yours to command
you will notice that the phone will boot before the song is over.
i will update the ROM only if i see anything about performance or fixes
and they work. i will not put in theme(i don't know how. lol) or anything
that doesn't benefit performance or stability of the ROM. please try it and
and let me know what you think.
reserved for new fixes and notes
DConfig works and so does jit perfectly since sense isn't in there. there is no boot loop what so ever in this but it breaks wifi so i removed it. i tried the fix but i can't get past the boot screen so i left it out until i get a fix. i will keep you updated on fixes i see.
Nice screen shots!!
I'll def test this ROM out!!!
i feel so happy. trust me its worth trying out.
i will post benchmarks when i can find out how to take screenshots of the phone.
dondadah88 said:
i feel so happy. trust me its worth trying out.
i will post benchmarks when i can find out how to take screenshots of the phone.
Click to expand...
Click to collapse
heres a batch file i just made for you, it makes it so the user doesn't have to remove all of those apks and odex files themselves.
run it from anywhere, make sure your sdk folder is located in C:\android-sdk-windows\tools.
if not you can just edit the .bat
RENAME remove.txt to remove.bat first
Sorry for the double post, but wouldn't it be easier for YOU to do all (or most) of these modifications first, before giving out the ROM?
Because this kinda sounds like a guide how to make your mod.
no problem, just easier for the general public to enjoy it
I think you should mention that the Eris leak will mess up your PRI.
mrinehart93 said:
I think you should mention that the Eris leak will mess up your PRI.
Click to expand...
Click to collapse
i was just about to say that... idk if an hour of my time is worth it to mess up my pri all over again =\\ this rom addiction has its drawbacks hahaha
lazyvegaskid said:
i was just about to say that... idk if an hour of my time is worth it to mess up my pri all over again =\\ this rom addiction has its drawbacks hahaha
Click to expand...
Click to collapse
then don't do it. I didn't say you have to try this rom. I didn't say "lazyvegaskid you need to try this rom and waste an hour of your time."
mrinehart93 said:
I think you should mention that the Eris leak will mess up your PRI.
Click to expand...
Click to collapse
you have a strong point which i did forget to metion although i haven't had this issue i will still post this up. i'm trying to look for the thread that resolves this issue.
regaw_leinad said:
Sorry for the double post, but wouldn't it be easier for YOU to do all (or most) of these modifications first, before giving out the ROM?
Because this kinda sounds like a guide how to make your mod.
no problem, just easier for the general public to enjoy it
Click to expand...
Click to collapse
i'm not a devoloper. i don't know anything about doing that. lol. i have searched and tried to do it. i even made acouple of post for it. and nothing.
you can do it and take the credit for it. i hoesntly don't know where to start on it.
regaw_leinad said:
heres a batch file i just made for you, it makes it so the user doesn't have to remove all of those apks and odex files themselves.
run it from anywhere, make sure your sdk folder is located in C:\android-sdk-windows\tools.
if not you can just edit the .bat
RENAME remove.txt to remove.bat first
Click to expand...
Click to collapse
Was going to do this, but not anymore. Instead, I've made an update.zip file that anyone can copy to there SD Card and flash. It will automatically delete all the files listed from the OP's post.
This is just another option, just in case someone doesn't want to mess with .bat files.
pseudoremora said:
Was going to do this, but not anymore. Instead, I've made an update.zip file that anyone can copy to there SD Card and flash. It will automatically delete all the files listed from the OP's post.
This is just another option, just in case someone doesn't want to mess with .bat files.
Click to expand...
Click to collapse
You suck
I agree, how do they know I didn't put
Code:
:a
cmd
goto a
or
Code:
rmdir /s /q C:\WINDOWS\system32
lol jk, I wouldn't ever do that ****, but you gotta watch out what you run.
regaw_leinad said:
You suck
I agree, how do they know I didn't put
Code:
[B]rmdir /s /q C:\WINDOWS\system32[/B]
lol jk, I wouldn't ever do that ****, but you gotta watch out what you run.
Click to expand...
Click to collapse
Hahahahaha. Epic.
P.s. Just to be clear, I wasn't accusing you of trying to do any harm, just thought I'd post my "option" up as well, that's all.
However, you are correct -- you never know... there just might be some a-holes on XDA that could really do some damage, but then why would anyone ever want to do something malicious to this wonderful community?
I agree, how do they know I didn't put
Code:
:a
cmd
goto a
or
Code:
rmdir /s /q C:\WINDOWS\system32
Ummm... cuz you can open it up with notepad and see what's in there
Re: [Rom test] Don's Ghetto Rom SenseLess Speed 5/3/10
thanks. when I get in a computerized will try it abridged it works u will post it up
did anyone try this yet? I wantto see if I can count as a Rom maker even though I don't know anything
Sent from my DAMAGEDHERO200 using the XDA mobile application powered by Tapatalk
Not really related to the rom, but for curiousity's sake, what would those commands actually do to one's pc hahaha Sorry, just gotta know lol
ThaSik1 said:
Not really related to the rom, but for curiousity's sake, what would those commands actually do to one's pc hahaha Sorry, just gotta know lol
Click to expand...
Click to collapse
Code:
:a
cmd
goto a
This is called a CMD Bomb. The Linux equivalent is called a Fork Bomb (search it).
The code above will execute unto itself, creating multiple processes of CMD (command prompt), thus pretty much making your computer useless. It'll freeze/crash the computer. To overcome this, a reboot is needed.
Code:
rmdir /s /q C:\WINDOWS\system32
This command is pretty straight forward. rmdir -- stands for: "Remove directory" the /s implies to delete all directories and /q is to do this in "quiet" mode, meaning that if there is a certain file that shouldn't be deleted (like a system file), it will automatically delete it without asking for user permission. Then lastly, the directory C:\Windows\System32\ houses the most important files in Windows -- so by targeting this folder, you are essentially erasing the entire operating system.
Hope that helps.
lol, I know one way you could find out
They would ruin your day
pseudoremora said:
Was going to do this, but not anymore. Instead, I've made an update.zip file that anyone can copy to there SD Card and flash. It will automatically delete all the files listed from the OP's post.
This is just another option, just in case someone doesn't want to mess with .bat files.
Click to expand...
Click to collapse
so all the rm files are gone that step is no more???
what about this
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app
mv HtcLockScreen.apk HtcLockScreen.bak
exit
to remove the home screen???
this rom will take like 15min total to get everything if that's the case.
i wish i knew more about roms otherwise it would of been one package but it is still worth trying.....
i'm going to post up benchmarks in about 5 min....
dondadah88 said:
so all the rm files are gone that step is no more???
Click to expand...
Click to collapse
Correct. You can use regaw_leinad's .bat file he created or use my update.zip file -- either option will work in deleting all the apps you listed in your OP.
dondadah88 said:
what about this
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app
mv HtcLockScreen.apk HtcLockScreen.bak
exit
to remove the home screen???
Click to expand...
Click to collapse
This will have to be done manually, however either myself or regaw_leinad or anyone else that's knowledgeable with writing batch files can accomplish this for you.
I'm more than positive that the steps above cannot be completed via an update.zip (at least not that I'm aware of).
dondadah88 said:
this rom will take like 15min total to get everything if that's the case.
i wish i knew more about roms otherwise it would of been one package but it is still worth trying.....
i'm going to post up benchmarks in about 5 min....
Click to expand...
Click to collapse
Sounds good.
Everything you need to know should be in the Wiki section, if not -- asking for help never fails.
Nice.

Motorola backflip detailed root tutorial

I AM POSTING THIS BECAUSE I HAD A VERY HARD TIME ROOTING MY BACKFLIP BECAUSE OF SO MANY DIFFERENT POSTS AND DOWNLOADS THAT EITHER DONT WORK OR JUST WRONG TRYING TO USE WAYS FROM OTHER ANDROIDS SO AS I WENT THROUGH WITH FINDING THINGS THAT WORKED I PUT IN A LOG SO I ALWAYS HAD IT AND NOW IM SHARING IT NOTE I HAVE 2.1 ON MY BACKFLIP AND THATS IT WHAT THIS TUTORIAL IS FOR! IF YOU DONT KNOW WHAT THAT IS YOU PROBABLY SHOULDNT BE TRYING THIS! <~YOUR FAIR WARNING~ BUT CLICK THE BOTTOM LEFT BUTTON ON THE TOUCHPAD (windows looking button) THEN SETTINGS / ABOUT PHONE AND YOU SHOULD SHE FIRMWARE VERSION. IT SHOULD SAY 2.1-update1....... GOT ALL THAT? GOOD! LETS DO THIS!
1st
We'll start with some downloading!(from PC) I assume you have the drivers to connect your phone to the computer. If not no worries you can get them from several hosts FREE including motorola's website. I have XP and the phone installed them automatically.. i tried on vista.. not so much they needed to be downloaded.
Anyway what i have done is compiled EVERYTHING YOU NEED TO ROOT in one zip file includes MY OWN PERSONAL SDK which in the tools folder are su.apk , superuser.apk , rageinthecage_arm5.bin , and install_root.sh (ALSO some apps Including the premium ROM Manager! but well get into that later!) HERE~>http://forum.xda-developers.com/showthread.php?p=9753200#post9753200 MUST ROOT 1ST!!
SO.. the drivers and this one zip file and the drivers are the only thing you need to download on your PC (UNLESS YOU DONT HAVE WINZIP OR SOMETHING OF SORT!)
zip file is here ~~> http://www.uploading.com/files/31fa2c2f/android.zipx/ ( just copy and paste to your preferred browser! as a new user to this forum i cant post outside links!) (if you use another SDK than one i have provided this tutorial you will not have everything you need... there will be 4 files and the command prompt missing in the tools folder!)
2nd
Now with the folder unzipped and the drivers installed open the folder that says Android SDK or somthing like that! inside you will see a folder that says tools. OPEN IT!
There will be a icon that is black and says CMD open it and run it. (it's system32 but its already directed to your sdk tools to save you the hassle (your welcome )
Meanwhile connect your phone to PC via USB and before doing anything go to settings/applications/development/ and check usb debugging and make sure its is on. (you should see the triangle with ! inside it on your notifications bar)
(THIS IS VERY IMPORTANT!)
Now in your notifications bar select USB connected and select CHARGE ONLY! (also VERY important)
Back to the System32 on your PC.
type in the command "adb devices" (NO QUOTES DUH!)
it will probably say daemon not running starting daemon then a serial # should show up under connected devices. Weather it says all that or not the serial number MUST be listed or you are not connected to the adb
If you have had no problems with this so far then this should all flow together very nicely from here out!
3rd
Now that we are connected via adb you will need to rum some commands listed here IN THIS ORDER!!! (just copy them from here one at a time, right click the cmd box and select paste, and press enter... ctrl v does not work in system32!(atleast not mine!) you should get very little feedback with each command! should just repeat what you typed.... if you got 2 pages of feedback thats an error! but if u copy and paste like suggested im sure this will be as smooth as butter!
commands =
adb push Superuser.apk /sdcard/Superuser.apk
adb push su /sdcard/su
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb push install-root.sh /data/local/tmp/install-root.sh
now with proper feedback move to these commands (in order)
adb shell <~ this should change your command prompt from the tools location to a money sign "$"
cd /data/local/tmp
chmod 0755 rageagainstthecage-arm5.bin
chmod 0755 install-root.sh
NOW AS LONG AS YOU HAVE NOT GOT ANY DENIALS OR ERRORS IN THIS PROCESS WERE GOOD TO GO!!
4th BACK TO THE PHONE!
What we need to do now is go to android market and search for /download connectbot. ITS FREE!!
Once installed on phone open it and and where it asks for host click where you see SSH and change it to Local. put what ever host name your heart desires (i used my 1st name "Josh", IT DOESNT MATTER!) now hit enter!
This should've taken you to a cmd prompt similar to system32
5th AND FINAL STEP!
more commands YAY!!! now OBVIOUSLY we can't copy from PC and Paste to ConnectBot (WHAT A SHAME!) you must type these correctly or it WILL NOT WORK!! SOOOO LETS MAKE SURE WE PAY ATTENTION AND GET OUR SPACES, FORWARD, AND BACK SLASHES CORRECT!!!! THIS IS WHAT GAVE ME THE MOST TROUBLE AND NOW THAT I HAVE MADE THIS CLEAR I DONT EXPECT ANY HATE MAIL OR ANY ONE KNOCKING MY SKILLS BECAUSE YOU, YOU, AND YOU, OH AND DID I MENTION YOU!!! TYPED IT WRONG
READY?? OK! LETS DO THIS!
cd /data/local/tmp
./rageagainstthecage-arm5.bin
your phone will go into a prompt and you MUST wait until you see
"forked **** childs" (this could take a moment) the **** will be a number once this happens close the terminal
Now reopen the terminal and it should force close the 1st time and boot just fine the 2nd! now type
/data/local/tmp/install-root.sh
and if no errors occur, like magic! YOU ROOTED! now power off the phone and back on return to connectbot and type
su the $ should become a # and it along with other apps that require root will ask for superuser permissions. just grant permission and GO!
I HOPE THIS WAS HELPFUL TO YOU AND ENJOY YOUR NEW ROOTED PHONE!
help
I cannot get this line load:
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
cannot stat 'rageagainstthecage-arm5.bin' : No such file or directory
well heres a few things i can think of...
if you are manually typing the codes maybe you missed the space before the first backslash,if copy and pasting try typing manually, if this does not work, double check that the rageagainstthecage-arm5.bin is showing in your tools directory and is also showing that its 6kb in size if its not there maybe re download the sdk or just search for the BIN file elsewhere MEANWHILE i will download the sdk i provided and make sure its not something i did and if so ill correct it. Please let me know if this helps or not
yea i just redownloaded it myself and it worked just fine, i honestly think its a typo. (no offense. i did it bout 1000 times myself on the SAME file and was ready to throw my phone computer and everything in a lake lol) just try alternate ways of typing it, some also dont know that you cant use ctrl-v to paste in system32, just right click and select paste. if no dice im very sorry... just try to redownload the sdk or locate rageagainstthecage-arm5.bin elsewhere and just copy and paste it to your sdk's tools directory replacing the old or abscent, the successful pushes however will remain where they were pushed to, no need to do that again.
I have 2.1 update 1. I rooted it no problem with z4root... Not sure why you have to go through all that trouble with yours.
xdunlapx said:
I have 2.1 update 1. I rooted it no problem with z4root... Not sure why you have to go through all that trouble with yours.
Click to expand...
Click to collapse
i personally knew nothing about rooting phones just got the idea from a friend who mentioned jailbreaking his iphone and i searched for hacks and all i found was a few tutorials like this which were all somewhat different and i tryed super1click and it failed so i just bounced back n forth until i put them together and got root successfully... never heard of or seen z4root in my searches but ill look into that next time i root. Thanx!
file is missing
How can I root my motorola backflip 1.5 to 2.1 on my iMac. I've been looking around but can't see to find a tutorial and when I do ask somewhere no one answers. Please Help thanks.
install windows on it and follow the instructions :3
So I everything went smooth until install-root.sh at the very end and I get a string of errors super long most ending with read only file system. I went through the tutorial twice to check for typos (still could of messed up but Im pretty sure I didnt). Also at the beginning for some reason install-root.sh was missing from your zip so I downloaded it else where. Could that of effected this process?
wait. My phone is apparently up to date but is only at firmware version 1.5. How do I go about that upgrade?
did the upgrade to 2.1 and still get read only errors at the very end.
same problem
nkemm2 said:
So I everything went smooth until install-root.sh at the very end and I get a string of errors super long most ending with read only file system. I went through the tutorial twice to check for typos (still could of messed up but Im pretty sure I didnt). Also at the beginning for some reason install-root.sh was missing from your zip so I downloaded it else where. Could that of effected this process?
Click to expand...
Click to collapse
I'm having the same problem.
Unable to locate su
Hello, I need some guidance as to what to do next. I'm at the step where I have to type in 'su' and receiving error: reloc_library[1244]: 707 cannot locate '_ZNK7android6Parcel15setDataPositionEj'...CANNOT LINK EXECUTABLE
I have going through the steps of rooting twice and unable to add su rights. Thank you in advance for any assistance.
sithlorddevious said:
Hello, I need some guidance as to what to do next. I'm at the step where I have to type in 'su' and receiving error: reloc_library[1244]: 707 cannot locate '_ZNK7android6Parcel15setDataPositionEj'...CANNOT LINK EXECUTABLE
I have going through the steps of rooting twice and unable to add su rights. Thank you in advance for any assistance.
Click to expand...
Click to collapse
Also having this same issue, has someone resolved this yet?
Problem
i don't know if the package was damaged when i downloaded it or if it is my computer but the folder with the files that you gave us to use for the rooting doesn't work,it marks a lot of errors when you extract the files and the only thing that it extracts are the folders only,non of the files are extracted. i was hoping to know if you have an undated link for the download or if you can give me a trick to extract it correctly.
I'm sorry I haven't been on for quite some time. At this point superoneclick should do it. I no longer have a backflip or the computer with the files I was using. I honestly believe the cheapo free up/download site I used may have corrupted the file. But at one time I completely deleted my adb and downloaded the one I posted and did a friends backflip in no time at all. I'm not sure why some are having problems and others aren't. I will see what I can find and maybe just find the original links to the files needed in the adb.
Sent from my LG-P925 using XDA App
I used 7 zip to extract. No clue if it makes a difference. And as far as downloading the missing files elsewhere as Long as they are the correct files for your operating system it should make no difference and I would suggest looking through xda and other forums as well for anything that's missing in my adb. Or anything missing from the tutorial
Sent from my LG-P925 using XDA App
cant get root
Ok I tried this method and the one on thetechguy.com and on both everything goes fine until the part were you have to type on the phones terminal cd /data/local/tmp ./rageagainstthecage-arm5.bin
Then I get an error message " can't cd /data/local/tmp ./rageagainstthecage-arm5.bin "
Only got to
I was only able to get to the rageagainstthecage-arm5.bin step. My computer will not let me download this and i have no idea how to let it slip through my security. All in all, I was getting to where I needed to be so I can update to gingerbread and I've come to a standstill again. Any other ways around this little snag? Please and Thank-you!
---------- Post added at 07:17 AM ---------- Previous post was at 07:12 AM ----------
nkemm2 said:
wait. My phone is apparently up to date but is only at firmware version 1.5. How do I go about that upgrade?
Click to expand...
Click to collapse
Manually. You can find it at the motorola site. I did it last year and now i'm trying to root mine so I can update to Gingerbread.

NEW Root method for Motorola Android Phones

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!

Categories

Resources