[Q] Rooting: 3 questions - Thunderbolt Q&A, Help & Troubleshooting

[I would've posted this in the Development section. But I'm not 'qualified' to post there due to my low post number -- I'm still a noob on this site]
I've been the proud owner of a TB for almost 2 months now. Been holding off on rooting, mostly out of fear of bricking the thing. I 'rooted' an old WinMO6.5 device about a year and a half ago. But the process for rooting TB is significantly more involved than my last one. However, I'm also frothing at the mouth after seeing all of the various ROMs out there, not to mention being able to be rid of all the crapware.. So...3 quick questions.
1) I've installed SDK on my home PC (Windows XP). But, when I extracted the .zip file, I extracted it to: C:\Program Files\Android\android-sdk. Only after the fact did I see in the instructions that I should have extracted to: C:\AndroidSDK
Does this difference really matter? As long as I drive to the correct directory on my PC when I start to run ADB, will its current location work ok? Or do I need to uninstall/reinstall?
2) There are a couple of places in the root process where you need to stop and verify an output alphanumeric matches what it should be. If the alphanumeric DOES NOT match, can I simply unplug the phone at that point and stop the root process? Or is it a situation where once I've started, I'm committed?
3) Finally, once I'm rooted, does it matter if choose a 2.2 (Froyo) or 2.3 (GB) ROM? My stock phone is running 2.2.
Thanks in advance for any feedback.

[I would've posted this in the Development section. But I'm not 'qualified' to post there due to my low post number -- I'm still a noob on this site]
I've been the proud owner of a TB for almost 2 months now. Been holding off on rooting, mostly out of fear of bricking the thing. I 'rooted' an old WinMO6.5 device about a year and a half ago. But the process for rooting TB is significantly more involved than my last one. However, I'm also frothing at the mouth after seeing all of the various ROMs out there, not to mention being able to be rid of all the crapware.. So...3 quick questions.
1) I've installed SDK on my home PC (Windows XP). But, when I extracted the .zip file, I extracted it to: C:\Program Files\Android\android-sdk. Only after the fact did I see in the instructions that I should have extracted to: C:\AndroidSDK
Does this difference really matter? As long as I drive to the correct directory on my PC when I start to run ADB, will its current location work ok? Or do I need to uninstall/reinstall?
2) There are a couple of places in the root process where you need to stop and verify an output alphanumeric matches what it should be. If the alphanumeric DOES NOT match, can I simply unplug the phone at that point and stop the root process? Or is it a situation where once I've started, I'm committed?
3) Finally, once I'm rooted, does it matter if choose a 2.2 (Froyo) or 2.3 (GB) ROM? My stock phone is running 2.2.
Thanks in advance for any feedback.
Click to expand...
Click to collapse
1. Yes, just run the commands from the dir you installed them.
2. If the md5's don't match then just redownload the file. Personally I have never had an md5 not match, however I do check them. Everytime.
3. Nope, run what you think you will like. The GB roms require the GB radios. You can find everything you need in the roms and kernel list. Its a sticky in the dev section.
I'm running BAMF sense 3.0 rc4. It uses the mr2 radio. Good luck with it and welcome aboard.
sent from my BAMF'n thunderbolt.

idahonld said:
[I would've posted this in the Development section. But I'm not 'qualified' to post there due to my low post number -- I'm still a noob on this site]
I've been the proud owner of a TB for almost 2 months now. Been holding off on rooting, mostly out of fear of bricking the thing. I 'rooted' an old WinMO6.5 device about a year and a half ago. But the process for rooting TB is significantly more involved than my last one. However, I'm also frothing at the mouth after seeing all of the various ROMs out there, not to mention being able to be rid of all the crapware.. So...3 quick questions.
1) I've installed SDK on my home PC (Windows XP). But, when I extracted the .zip file, I extracted it to: C:\Program Files\Android\android-sdk. Only after the fact did I see in the instructions that I should have extracted to: C:\AndroidSDK
Does this difference really matter? As long as I drive to the correct directory on my PC when I start to run ADB, will its current location work ok? Or do I need to uninstall/reinstall?
2) There are a couple of places in the root process where you need to stop and verify an output alphanumeric matches what it should be. If the alphanumeric DOES NOT match, can I simply unplug the phone at that point and stop the root process? Or is it a situation where once I've started, I'm committed?
3) Finally, once I'm rooted, does it matter if choose a 2.2 (Froyo) or 2.3 (GB) ROM? My stock phone is running 2.2.
Thanks in advance for any feedback.
Click to expand...
Click to collapse
In relation to your second question, the alphanumeric matches you're asking about are called an MD5 check sum. It checks a files integrity, like a finger print. As long as the characters match the file is intact and you know it is safe to flash. If the characters don't match then you will download it again and replace the original file you downloaded. Then run the MD 5 check sum again to make sure its all there (characters match). I have never had a MD5 not match, so its uncommon. If you were to flash an incomplete file it most likely would brick your phone.
I would recommend a 2.3 ROM. Part of what makes rooting and nand unlocking (S off) so valuable is the ability to run the latest operating system. I would suggest you try Cyanogen once you're comfortable flashing ROMS.

Thanks for the prompt replies. This helps a lot.
I've got the 3 files downloaded to my PC for the root, and they all are good w.r.t. MD5 checksum. So I think I'm good to go/root.
One more noob question. And I could probably find the answer to this by searching around, but as long as I have your attention...you say that the GB roms require the GB radios. Do most/all of the GB roms already have the GB radios built into them? Or is this something totally separate?

idahonld said:
Thanks for the prompt replies. This helps a lot.
I've got the 3 files downloaded to my PC for the root, and they all are good w.r.t. MD5 checksum. So I think I'm good to go/root.
One more noob question. And I could probably find the answer to this by searching around, but as long as I have your attention...you say that the GB roms require the GB radios. Do most/all of the GB roms already have the GB radios built into them? Or is this something totally separate?
Click to expand...
Click to collapse
radios are separate. For GB, you need MR2 or MR2.5 radios. They are in the dev section as well. Flash the radio before you flash the GB ROM or you will not have any cell signal.

Also be aware that when you start the rooting process, you need to use the USB connections at the back of your computer. ADB only recognizes the main USB ports. Good luck with your rooting!
Sent from my ADR6400L BAMF 3.0 RC4 using XDA App

Related

NEwBiE HELPP!!!

I have a massive headache trying to figure all this stuff out.
I have a t-mobile hd2
RAM of 576 and Speed of 1024MHz and Flash of 1024MB
when hold the volume and power button, it reads the following:
PB81120 SS-B3
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
I downloaded the andriod installer on my computer, along with HSPL, HSPL2, and HSPL3.
My objective is to hopefully get android on my Leo.
Ive read all the threads and im just really confused...I ran HSPL2 and i get an error screen that says i have a bad Model ID.
PLEASE HELP ME...IM SO LOST!!
You have some options:
1. Use search function of the board. (recommended)
2. Try to get the answer is the Android porting thread. I suggest to search the thread first (recommended, too)
3. this one
Ulti
i tried all of that and i get so confused...can someone actually help me?
I'm going to help so many next time you will help yourself and look a little more.
First of all you dont need to flash and thing to run android. It is in beta currently and is ran buy haret which is kinda like a emulator. When you read the link below you will realize that it has all kinds of problems. Those problems are known.There is also a Faq about those problems and what you can do to help solve them.
there are not instructions on how to operate android. By trying this we assume you know a little bit about android.
It looks like you already have the hslp but I am also going to provide a link on how to flash rom's and radio's.
http://forum.xda-developers.com/showthread.php?t=621930
This is direct information on forum for installing android.
http://forum.xda-developers.com/showthread.php?t=719646
This is the spoon fed version
>INSTALLATION INSTRUCTIONS FOR DIFFERENT BUILDS<
DarkStone1337 - HTC Sense (Desire build)
1. Download from one of the above sites and extract the contents to your pc
2. Copy all files to the ROOT of your Storage Card
3. Using a File Manager goto your Storage Card and run clrad.exe (it wont do anything but it has run) followed by haret.exe
4. Wait for Android to boot (may take upto 5 minutes)
dan1j3l - Froyo build
1. Download from one of the above sites and extract the contents to your pc
2. Copy the Android folder (including all files within the folder) to the ROOT of your Storage Card
3. Using a File Manager goto your Storage Card, Android folder and run clrad.exe (it wont do anything but it has run) followed by haret.exe
4. Wait for Android to boot (may take upto 5 minutes)
Or...you could try this...I've been using it for the last two days and everything seems to work on it
http://hotfile.com/list/600926/774f186
Download the Sense Droid and follow the istructions attached on file
No disrespect ment to you as I do know you have been around for a while. But it seems as though he doesnt have much experience in doing this.
That would seem like its just gunna cause more problems. there is still problems with power management. So its gunna eat away at his battery. This I know because I run android almost full time and thats a risk i'm just willing to deal with.
Secondly it boots right into android no stopping at windows. So if something goes wrong he is stuck. And will have to reflash.
I tried it and couldnt tether and had to go right back. Maybe he doesnt need to tether so it could be fine but I really think he should start off slow.
hazard99 said:
No disrespect ment to you as I do know you have been around for a while. But it seems as though he doesnt have much experience in doing this.
That would seem like its just gunna cause more problems. there is still problems with power management. So its gunna eat away at his battery. This I know because I run android almost full time and thats a risk i'm just willing to deal with.
Secondly it boots right into android no stopping at windows. So if something goes wrong he is stuck. And will have to reflash.
I tried it and couldnt tether and had to go right back. Maybe he doesnt need to tether so it could be fine but I really think he should start off slow.
Click to expand...
Click to collapse
Non taken mate...I was not thinking about what you said
If that's the case....he'll read both of your posts and make the proper desition.
Have a great day!
http://forum.xda-developers.com/showthread.php?t=732380
which one do i chose, The Energy.Leo.21911.Sense2.5.(Jul.21.7z) OR THE
Energy.Leo.23121.Sense2.5.(Jul.21.7z)????
i downloaded sense, but no android market...whats up with that?
Android
Why do you want Android on your WM phone???
The builds you downloaded are still windows mobile. You really need to read the htc-Linux thread
Sent from my HTC Desire using XDA App
all i want is the android app store on my phone...thats it. how do i do that without having to boot it up from my phone through haret.exe?
Android is a completely different operating system than windows mobile. The android app store and the apps will not work in windows mobile!
If you try to install a windows application on linux OS you will fail too.
Everything you need to know is in this post
This Thread tells you step by step how to do it want what you need to do it forum.xda-developers.com/showthread.php?t=893948 it work fine for me i had no problems at all doing it the market great and my phone is running just fine
ITZMACMATIC said:
This Thread tells you step by step how to do it want what you need to do it forum.xda-developers.com/showthread.php?t=893948 it work fine for me i had no problems at all doing it the market great and my phone is running just fine
Click to expand...
Click to collapse
Please look at dates of threads before you reply to them. This thread is 6 months old. It was made before Android was finished being ported. I'm sure the people in this thread already know about Android.
Sent from my HTC HD2 using XDA App
Sorry I saw it there didn't think to check the date my bad
Sent from my HTC HD2 using XDA App

Introduction to Android FRX07 - SD Card

Very Important Information For Beginners
/Introduction to Android for SD Cards
​
Okay, firstly I made this thread because pretty much every new person to this section of the forums is completely lost and unsure what things are or what to even do. We are also sick and tired of threads saying 'how do I get stared' or 'which is the most stable' etc.
----------------------
Download your files from here:
You will be accessing these websites quite often so it might pay to bookmark them
Kernel downloads, almost always download the top one, they are updated often (needs extracting): http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Rootfs downloads, download the top one, they aren't updated as often as the kernels above but still quite regularly (also needs extracting): http://files.xdandroid.com/rootfs/
Initrd downloads, rarely updated (don't extract, just rename to initrd.gz) http://files.xdandroid.com/initramfs/ People almost never need to download one of these separately.
----------------------------------
Basic need-to-knows:
Kernel: Your modules/zImage. Your zImage always needs be in the root (first folder) of your android folder on your SD and ALWAYS named zImage, your modules should also be in the root of your android folder named modules-LOTSofNUMBERSandLETTERS.tar.gz never rename your modules. It should always be in .tar.gz EG: modules-2.6.27.46-01276-g6a6a1c1-dirty.tar.gz
Rootfs: Must be in the root of your android folder named rootfs.img
Initrd: Needs to be in the root of your android folder named initrd.gz
Data.img: Generated on the first boot of android and placed in root of android folder. Is a virtual memory file that acts as the phones internal memory for android. Holds all your settings etc. May have to be recreated some times (just by deleting it)
Haret.exe: the file executed by your Windows ROM to kick Windows out of memory and boot android.
system.ext2: Main android file, must be in the root of your android folder. Holds all of your build.
startup.txt: File that instructs android how to start up. Needs to be in the root of your SD. (I will cover this further down)
ts-calibration: A file in the android folder that holds calibration information of the touch screen.
Various Folders: You will see/have/need other various folders created in the root of your SD and in the root of the android folder, such as conf, cache, data, media etc. You usually don't want to delete these.
Root: The root folder of any partition is the "highest" folder in the hierarchy. The root folder contains all other folders and can also contain files. For example, the root folder of the main partition on your computer is probably C:\. The root folder of your DVD or CD drive might be D:\.
Also Known As: "the root"
RIL: Radio interface layer: basically controls your radio (GSM/CDMA network)
------------------------------------------------
startup.txt
VERY IMPORTANT, your startup.txt must be customized to your device. (mine is a rhod110). You can find your model number under your battery. This file belongs in the folder with your android.
My startup.txt looks like this
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 rel_path=FRX07 physkeyboard=rhod100_uk acpuclock.oc_freq_khz=710000"
boot
Now I believe you should be able to copy and use this as yours with a few slight modifications. Change rel_path= to wherever your android is stored on your sd, for example when I go to my sd inside the folder frx07 (the root of my android folder) all my android files are there. If your folder was called andboot it would be rel_path=andboot. (without that full stop) Now change your physkeyboard= to your model of your phone, mine is rhod110 but the rhod100_uk keymap is EXACTLY THE SAME AS THE RHOD110 so that's why I use rhod100_uk instead of rhod110 (rhod110 isn't recognised by frx07), this is important to make sure your keys are assigned properly.
------------------------------------------------
Models of rhod:
From what I know that exists. If you find one not listed, make sure you tell me so I can update the list
rhod110 uses rhod100_uk and it works as it should
These can be used for physkeyboard= in startup.txt (needs updating, some may no longet be supported because F22 hasn't commited old changes)
rhod100_de
rhod100_es
rhod100_fr
rhod100_it
rhod100_nl
rhod100_nordic
rhod100_uk
rhod210
rhod300 (tilt2)
rhod400
rhod500
Getting set up:
Go to http://forum.xda-developers.com/showthread.php?t=1171052 and download the FULL BUNDLE
Other builds exist such as gingerbread but this guide only covers froyo frx07.
Replace/add the Kernel from the downloaded build with the latest one (remember this is the zImage and modules-NUMBERS.tar.gz). Updating is as simple as this, do it often - there is no data loss. See links mentioned above for links. Making sure that the (if there were) old kernel files are all deleted and the new ones are called zImage and modules-NEWdifferentNUMBERS.tar.gz
Replace/add the rootfs.img with the latest one from the link above it should be named rootfs.img.
Remember that the rootfs and kernel are updated quite often and that you should check and update every few days.
Make sure your startup.txt is correct and make sure everything is where it should be in a folder on your computer, then copy the folder to the root of your sd card.
Navigate to this folder using the file explorer in your Windows ROM (YOUR PHONE) and run the Haret.exe
It will then have some writing running down a black screen before booting android (it's just preparation to booting) read it if you want
Android will start and you should leave it about 2-5 minutes before touching anything, it has things running in the background and it will be slow, still setting itself up. Navigate to settings and set up your phone. If anything goes too badly wrong you can always delete data.img and start again! Data.img is the internal memory of the phone, remember? Well, until we get android working on the real internal memory...
---------------------------
Structure:
My SD card. (with android on it)
I'm running:
kernel: 20110819_183957 http://glemsom.users.anapnea.net/android2/htc-msm-linux/
build: Froyo FRX07http://forum.xda-developers.com/showthread.php?t=1171052
rootfs: rootfs-20110816-7e04198.zip from http://files.xdandroid.com/rootfs/
Code:
EncFiltLog.menc
kbd_info
Android
cache
download
tmp
Private
Games
Installs
DCIM
Others
Videos
Images
Sounds
media
frx07
rhodimg.nbh
My android is in frx07
inside my frx07:
Code:
data.img
ts-calibration
startup.txt
modules-2.6.27.46-01348-g9de837f.tar.gz
zImage
haret.exe
initrd.gz
system.ext2
AndroidApps
conf
media
rootfs.img
-----------------------------------------
Backup/Restore
when you have the need to backup and restore data, look for an app called Titanium Backup. I have never used it but heard it works brilliantly, even backing up your apps! There is a 'donation' version and a free version with not many differences. I suggest you go check it out!
-----------------------------
USB CONNECTIVITY
When your phone is in Android you can not use it like a USB, HTC's drivers will not work and you have to use certain programs until this is implemented.
Windows: Install DroidExplorer this lets you open a terminal (like command prompt) on the phone, lets you browse device adding/deleting files, among other features that are very useful. If that DroidExplorer doesn't pick up your phone (when picked up it will be called 0000000000) install PDAnet on your phone and pc. PDAnet provides the drivers needed to connect the phone. It also lets you use your phone as a modem and you can send SMSs using your computer. Do NOT run PDANET at the same time as DroidExplorer. When PDANET is connected it WILL use your phone for data connections - this is the only warning. The phone is not used for any networking when DroidExplorer is connected.
Mac: Unknown to me (can someone post?)
Linux: Never tried, it is easier than windows (can someone post a method?)
---------------------
Overclocking
Do NOT overclock WINMO.
If you want to overclock your device do so at your own risk.
it is as simple as adding "acpuclock.oc_freq_khz=710000" without quotes to your startup.txt cmdline. 710000 (approx 710 mhz) can be swapped for any number but this is practically the highest stable speed achievable. I use 710000, works fine for me.
-------------------------
Known problems across ALL BUILDS:
Media Player Some tracks might have playing issues. FIX: HERE
Bluetooth is experiemental
Speakerphone static : seemingly random issue
USB plugging the device into a computer, it will be recognised, but not by HTC drivers. FIX: You must use something like DroidExplorer and PDAnet to browse the device and ADB (android debug bridge). See above ^^ (USB tethering is being fixed/has been fixed)
FN LED On keyboard the caps LED works but the FN LED currently does not. FN still works fine
No deep sleep: FIX: disable GPS (or kill the running app causing phone to not sleep)
Failure booting Android: Phone fails to enter android after running haret.exe FIX: Make sure your winmo is NOT overclocked before booting android.
Booting or SD Card related problems: Make sure your card is formatted as FAT32 (reformat as Full Format if it is not working)
More information is available on the wiki, there is also information there if you want to get into development. There is a pretty good FAQ on that wiki too
Remember XDAndroid is not just for this device.
If any of this is wrong or you think something should be updated/changed, please tell me ​
The CDMA startup should have "board-htcrhodium.is_cdma=1" instead of "...is_gsm=0"
otherwise, looks good!
AkumaX said:
The CDMA startup should have "board-htcrhodium.is_cdma=1" instead of "...is_gsm=0"
otherwise, looks good!
Click to expand...
Click to collapse
Indeed, there is no "is_gsm" command .
arrrghhh said:
Indeed, there is no "is_gsm" command .
Click to expand...
Click to collapse
Thanks to both of you, not bad considering I don't even have a cdma phone eh?
anything I need to add? I will tidy it all up soon
Something that might catch out a beginner is if they have an older SD card and it isn't detected by more recent kernels.
Need to include this in the cmdline:
msmsdcc_1bit msmsdcc_fmax=14000000
the.decoy said:
Something that might catch out a beginner is if they have an older SD card and it isn't detected by more recent kernels.
Need to include this in the cmdline:
msmsdcc_1bit msmsdcc_fmax=14000000
Click to expand...
Click to collapse
I thought this was squashed in recent kernels?
arrrghh said:
saneksem said:
add that to startup,helped me on 2 gb card
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
Click to expand...
Click to collapse
You don't need this if you're on a newer kernel!!!!
Just update your kernel folks, no need for this in the startup!
Click to expand...
Click to collapse
Oh, ok. I must have missed that. I only needed it on my older SD which I haven't tried using for a month or so.
I guess the only thing I would suggest (all minor things) would be maybe to bold/underline keywords, like "kernel", "rootfs", etc.. to differentiate things that may change over time; ex: I'm running FRX05 system.ext2, 3/1/11 rootfs from F22, 3/1/11 zImage/modules (kernel) from arrgghh, etc... And, I guess you "could" be nice and show people what they could edit in the startup.txt, depending on their phone; ex: I'm Sprint, so I would do kb=rhod400, cdma=1, etc..., but for each phone.
I would probably have to do all the different startup.txt's in a different thread, unless I just provide a quick table... I will think about it however I do like the idea about bolding key words.
Most new people don't realize if they have their call/end/windows/back buttons on in winmo, they will stay on while on android and never go off. Might want to put that in your first post before telling them to run haret...
at the end where you say you can just delete the data.img and startover its probably a better idea to say to be patient and reboot the phone once or twice before ditching your data.img ! and creating it is the bulk of the first boot, the linux black screen with the scrolling words section.
you can talk about saving your data.img just incase something goes wrong.
titanium backup is a must
having an app that can save sms when you switch builds (not a big deal for everyone but important to some.)
also let new users know android isn't perfect, things randomly completely mess themselves all the time, don't get discouraged just start fresh with a format and new files when deleting the data.img doesn't work and you'll be just fine.
All I want to know now is if I have helped anyone yet and if they had any problems with any part of it or want me to clarify anything I will be quite happy with such replies ^-^
Is anyone able to provide me with some ETAs of fixes on the problems across all builds listed in the OP? Also are there any more I am not aware of? Oh and if anyone is working on them?
Much Appreciated
ryannathans said:
Is anyone able to provide me with some ETAs of fixes on the problems across all builds listed in the OP? Also are there any more I am not aware of? Oh and if anyone is working on them?
Much Appreciated
Click to expand...
Click to collapse
There's never an ETA for anything getting fixed - BT seems close, but who knows the exact date it will be done? As CyanogenMod says, the only rule is don't ask for release dates / ETA. It'll be ready when it's ready.
Some problems are being looked into more than others, but I wouldn't say one in particular has been left out to rot. jb is fixing up BT, entropy is working on GPS fixes, wistilt2 on the RIL of late... Basically devs pickup things that are of an interest to them to fix. There's a lot still to fix/cleanup, so taking it all on alone is a little daunting. Gotta break it down into smaller pieces so it's at least somewhat manageable.
Thanks and a question...
First, thanks for the awesome post - quite helpful...
Second: I haven't mussed with my phone for about a year, for various reasons, the main one being that I was happy with my previous phone and the ROM I finally settled on, the secondary one being that phone died, and I now have a (blech) Sprint TouchPro2 (RHOD400), and am on my sixth (yes, sixth!) brand new TP2 - they keep giving me a new one because of problems (things, like... oh... say, not being able to answer calls... kind of a basic function in a mobile phone, nah?!) And, I've had no interest in futzing with what is already a frustrating and non-functional phone. I was hoping I could upgrade instead of getting another TP2 the last time I brought it in for probs, but they would only downgrade me to worse phones. So... here I am, wanting to put Android on my phone and see if there is any improvement. Or, at the least, be able to utilize some of the decent progz/gamez for Android. I mean, if I can't answer calls, at least I can use it as a handheld gaming system, right?!
Long story short: when I was flashing ROMs to other phones, the instructions explicitly said that you needed to unlock, etc., first. I can't find any data re: if there are steps you must take on your phone to 'prep' it, *before* following the steps in this thread. I've browsed the DB and no luck.
My apologies for being an annoying n00b!
PS: one of my friends said "Tell 'em you're a hawt babe - then they'll help for sure!" (ROFL)
And, thanks, again!
Tynkrrbell said:
Long story short: when I was flashing ROMs to other phones, the instructions explicitly said that you needed to unlock, etc., first. I can't find any data re: if there are steps you must take on your phone to 'prep' it, *before* following the steps in this thread. I've browsed the DB and no luck.
My apologies for being an annoying n00b!
And, thanks, again!
Click to expand...
Click to collapse
Well the reason you can't find any info on it, is that it's not required .
These builds run entirely off of the SD (currently - I wouldn't try NAND yet, it's in its infancy) so there's no need to do any HardSPL or anything really to prep - just drop the bundle on your SD card - if it's at the root, run haret.exe and gogogo!
Oi. I get the stupidcard of the day!
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Tynkrrbell said:
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Click to expand...
Click to collapse
My gf suffices for that .
Hope you enjoy Android!
Tynkrrbell said:
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Click to expand...
Click to collapse
Not to burst any bubbles here, but if you are saying you are a "hawt babe" and give boobpr0n mumbo jumba, you are prolly not one and won't give it anyways.. so nobody will most likely believe you here..
Good luck though~

Different SBF **UPDATE** Bootable SBF CD -Hit A Roadbloack

Update 1-21-12
Ok, 1KDS ran into a small, well maybe not small, issue. The way the whole process works would require a large amount of RAM for the process to run properly. It's in the order of 6+ gigs because the scripts set up and run the operation in RAM. Since most people don't have that much RAM the project is on hold until a solution presents itself. I would like to thank 1KDS for looking into this. If anyone has ideas, feel free to post up.
Previous Info:
Ok, guys here's the deal. The dev is aware of what I'm asking and is looking into possibly doing this for us. Remember these simple requests:
1) Don't ask for ETA's. Enough said.
2) If a question is asked that needs your answers/input, please give it.
3) If he is successful, and I have to stress "IF', he will need testers. Please do, I know I definitely will.
And Finally
4) If you can, donate/support, he's doing this for YOU!
Previous Post:
Ok Here's an update. I pm'd the creator over at DXF and he has said it's pretty involved. He has said:
" It's pretty involved, it may be easier to make one myself. If you can link me the SBF file, instructions to get into the bootloader or wherever you flash from, instructions to factory reset afterward, and what root method is used for the MoPho I can work on one."
So I'm going to provide the info. My question to my fellow MoPho users is "Would you be willing to support and/or donate to him for his work on this?" If he's going to be nice enough to do this we should be nice enough to support him for his efforts. I'll update this as I find more info.
Mike
Original Post:
Have a question, how would one go about creating an automated Linux bootable CD with all the scripts and files to make it easier to SBF a MoPho?
I came from the Droid X and there was a file I downloaded that was in a word - awesome. Insert CD, boot from it, plug in phone, choose option 1, and viola!!! In a few minutes your device was flashed back to stock, no fuss no mess.
I'm a MoPho-er
I wish I could help, but IDK how to do that bub, try making a post in the Droid X Forums, ask for a dev to remake the files to boot on a CD and use this SBF file ---- use this link to download it.
See if that helps, someone may be able to make that CD.
Just thought I'd ask. It's been a few years since I dabbled with linux, Red-Hat was my last venture (10-12 years ago). I'll look at how the cd and the scripts are set up. I can probably figure it out.
I'm a MoPho-er
Let me know if you or someone can get it to work, I'd be very interested.
I think I can get it to work, just have to get the scripts right. Gonna take a fews days. I'm gonna post over at DXF and ask the person who creates them for some input.
I'm a MoPho-er
I'm linking this thread here as it has all the tools and info needed (hopefully) to create a bootable SBF CD.
http://forum.xda-developers.com/showthread.php?t=1393519
I'm a MoPho-er
Alright guys, I'll be working on a new image for the MoPho (I like that name!)
One question, anyone use the ZergRush root method on the MoPho? I have a nice script for that already as well as the Droid 3 method.
1KDS to the rescue!!!!!!!!
Thanks, your work is awesome!!!!!!
I'm a MoPho-er
I used Shabby's one click
I'm a MoPho-er
I looked at Shabby's script, looks pretty much like the Droid 3 method, I can use his script though, there may be a piece I'm not seeing that affects the MoPho. Does it work on the newest SBF/firmware?
I used it to root mine. Took it out of the box and it updated to the latest as soon as I activated it. I rooted about three days later and had success on the first try.
Edit: I don't know about the latest SBF, but (uneducated guess here) I would imagine it should.
I'm a MoPho-er
Alright guys, been busy but I'm ready to start on this new image, couple questions...
There was an SBF file posted on page 1, is that one preferred? I see there is a newer one out there.
Can someone post some clear instructions on getting into the bootloader or RSD mode and instructions for stock recovery to factory reset?
Is there a preferred bootstrap/clockwork? If one is preferred and offered free from the dev I can add a script to install it for you after rooting.
I hope I can give good info here, no one else is stepping up and I'm not fully "up to speed" on my MoPho yet. There's much I haven't tried because I'm "RSD skiddish". When I had my Droid X RSD and I just wouldn't "get along", so I'm not familiar with it. Hence the reason I loved the bootable CD.
For SBF files I think 198_6 is the latest official release. From what I understand 198_7 is out, but it's a leaked package as Sprint never released it.
As for CWM, there is one available, a thread is devoted to it. I think the version is 5.. dot something and it was made specifically for the Photon. It requires the bootloader to be unlocked as well, I believe. Thread here:
http://forum.xda-developers.com/showthread.php?t=1218417
For all the other steps there is a thread by qbking77 that has videos instructing how to root, flash, unlock, install CWM, etc. here:
http://forum.xda-developers.com/showthread.php?t=1250697
Hope this helps.
I'm a MoPho-er
Keep me posted. Can someone PM me the link to this thread when this is done, for some reason, I'm not getting updates on this thread...
Sent from my Motorola Photon 4G (MoPho) on Sprint, the Now Network using XDA Premium.
I had a couple bad downloads of the SBF file, I've got a good one now and unzipped it, the file (uncompressed) is 2.44GB! SliTaz (the Linux distro I use for these images) boots into RAM and my machine simply doesn't have enough RAM to unzip the file and stay stable, if I had more RAM I could make the iso but very few people would be able to use it as they would need 6+ gigs of RAM to run it. For now I'm putting this project on hold until I think of something else or a smaller SBF file is released. Sorry guys.
Ouch!!!!
Bummer 1KDS
Thanks for looking into it, though. I was curious why one didn't exist yet. I guess that would be a good reason why. I guess I'm just gonna have to break down and make RSD and me get along so I can do some modding to my MoPho.
I'm a MoPho-er
Question. Would a "virtual" environment work or is something like that just way to involved to work?
Edit:
Don't know if "virtual" is the right thought or not. I may have been thinking "RAM Disk" setup.
I'm a MoPho-er
Yeah, I use VirtualBox to build the images, my laptop has 4 gigs of RAM and I allocate around 2.5GB to the virtual machine so the machine stays stable and I can't even unzip it within that amount of memory. Like I said, even if I can build the image only a few people would be able to use it since it is so massive.

[Intensive Guide] Discovering your Mimmi -In progress-

For the Moderator who moved this thread, please contact me.
Click to expand...
Click to collapse
I am currently working on this: It is a work in progress. Many things will be updated as this goes on. I will publish it before it is ready mainly for you to know that I am doing this and to delete it before it is too late if you think it just isn't as good as I imagine it .
It could be useful to note that the dictionary may not be exactly correct, I can make mistakes and you can correct me too, if you are sure of what you say. Also, keep in mind that I define the concepts by what I understand from them and simplifying the language as much as I can for EVERYONE to understand every word.
Click to expand...
Click to collapse
Credits:
ShortFuse.org - SuperOneClick
ClockWorkMod Installer - rect2409, xda user
Contents:
1. Introduction
2. Dictionary -In permanent update as needed-
3. Getting started
/3.1 - Rooting
/3.2 - Getting your Recovery - CWM Recovery
/3.3 - Avoiding Baseband issues --Uncomplete--
1. Introduction:
Hey there, x10 Mini Pro community. First of all, the cheesy part, I would like to say thanks to the developers that have been in the main scenario since I came here, D4, slade, paul, nAa, TheMiltos, and lots of them whose usernames I should start looking for, but it is not like I do not recognize them. First, you may ask why would I make this thread if there is already another one, made by not less than one of the users I mentioned before. Well, I started on this community like on January 2011, when slade's Gingerbread was brand new and the Froyo ROMs were just getting a bit stable and ready for everyday use. I found it pretty difficult to start, since I've noticed that the support for newbies isn't kinda.. "the way" of xda. At least, when I was one of them, I felt pretty alone on this unknown roads, and also felt guilty to send a PM asking for help, not being able to post - and that was just when I finally decided to create an account... I spent hours and hours searching on Google, watching videos on Youtube, trying to understand what did they meant with all this technical language -disregarding the fact that my native language doesn't help at all (Luckily, my English is pretty good)-, reading blogs, and so on. I had to keep this intensive study for several weeks to, finally, get my very first custom recovery installed. And that was just the first step. Besides my own experiences -which are, by the way, the main reason for me to start thinking about a thread like this-, I noticed that all the particular problem solution threads just get lost within a month.
So, what am I looking for with this thread? What are the objectives?
-Full and friendly support for newbies to ask and be answered.
-Freedom to PM.
-Detailed step-by-step instructions, maybe even with screenshots later on.
-Some kind of a "dictionary" with words all over the Android development spectrum.
-Updated information.
-Make all of those lost tutorials and guides spread all over the x10 Mini Pro forums be compressed in one simple and extensive help center.
-End with the experienced ones complaining about newbies questions infinite cycle by creating this "encyclopedia".
-Maybe, just as an early idea, we could create a support team, whose purpose is pretty self-explanatory.
-Hope to add more objectives on the future.
2. Dictionary:
-Android Versions: Check Wikipedia for closer details on each version.
--> Cupcake 1.5: First public version of Android.
--> Donut 1.6: Initially the Stock version for our phones.
--> Eclair 2.1: Updated Stock version for our phones.
--> Froyo 2.2: Follow up to Eclair with some modifications
--> Gingerbread 2.3.x: Most widely used version by the moment.
--> Honeycomb 3.x: Version mostly for tablets
--> Ice Cream Sandwich: 4.0.x: Hybrid version, designed to unify Cellphones and Tablets OS.
--> Jelly Bean 4.1.x: It is still a rumor and it has not be released nor even confirmed yet, but it is still very likely to be true.
-APK: File extension used for Android-based applications. You can use them to install a specific application if you want to install it manually and not from the Market.
-Back-Up: It is a file made via Recovery that saves the ROM along with all the user data (Settings, applications, contacts, text messages...) on your SD to recover it later, just in case that something went wrong. It is sometimes referred as NAND Backup. NOTE: Every Back-Up is pretty heavy, and if you make another does not delete the previous one, so I recommend to delete the old/unneeded ones to save space on your SD.
-Boot: To turn on your phone.
-Bootloader: It is a part of the operating system that boots up your device and sets everything up to load Android, so your phone can boot and start as usual. Unlocking it allows us to flash custom kernel, which usually come with improvements compared to stock one.
-Brick: A Bricked device is a device that won't boot. It can be a full brick, when the phone just does not turns on, or a partial brick, where it turns on but it can not get to fully boot. A partially bricked phone can behave in many different ways while booting, for example, sometimes they get frozen at the Bootloader or sometimes they make a Bootloop. To Unbrick your phone means to get it back to normal from this state.
-CyanogenMod: Most commonly called by it's abreviation, CM. It is the most famous Android-based custom ROM, with both official ports to many devices and unofficial ports to almost every Android phone.
-Flash: To flash. It means to install something on your phone, this something can be a ROM, a Module for that ROM, can be almost anything. Any file we want to flash will be on a ZIP format, and it is made through your phones Recovery.
-Google Apps: Or GApps. Some of the apps developed by Google. They come in packages to flash them via Recovery. These apps include Android Market/Play Store, Google Maps, Youtube, Gmail, etc.
-Launcher: It is the application that is used by Android to show up your apps, homescreens, wallpapers, widgets, etc. Home Replacement Apps are alternative Launchers for you to install on your phone, and they can offer a major UI change (often used for more personalization).
-Overclocking: Commonly abbreviated OC. To overclock something means to make it run faster than the default speed set by the manufacturer. On computers, it can be applied to almost any component, on phones, it almost always is talking about the processor.
-OS: Short for Operative System. It is the "everything" of a computer. Mac and Windows are two really famous OS's you probably have used more than once. Well, Android is an OS too, and there are other OSs alternatives for phones too like Windows Phone, iOS and Symbian. The difference is much more than in the appearance thou, but it doesn't really matters to go further on this. Android haves different versions, and just like Windows haves Windoes 97, Windows XP, Windows Vista or Windows 7; Android has 1.6 Donut, 2.1 Eclair, 2.3 Gingerbread and 4.0 Ice Cream Sandwich (These are just examples, there are more).
-PC Companion, Flashtool, SEUS:
These are three common tools for your computer to update, flash or un-brick (alias revive) your phone.
--> PC Companion: Program by Sony Ericsson to update and save your Rom or parts (settings etc.) or to send media on your device
--> Flashtool: User-made program (credits to Androxyde and Bin4ry) to root, flash and set up many more things on your device.
--> SEUS (or Sony Ericsson Update Service): Program by Sony Ericsson to update or repair your official ROM. This is often the last chance to revive your bricked device, making me think if the "S.E.U.S." acronym is unintended or if it is actually made it to sound like the mythical god Zeus.
-Port: A ported ROM is a ROM, both custom or stock, that is available to some specific phone and someone manages to make it work for another device. Usually it includes changes like matching the desired device's screen and supporting it's own hardware.
-Reboot: Just turning off your device and then turning it back on, waiting patiently for it to completely load everything.
-Recovery: I usually call it a BIOS for my phone. It is not an application like Facebook or SMS, it is a program that can be optionally started while booting by pressing a certain key, in our case, we have to button-mash the "Back" button (Gamers will get that, it means to repeteadly tap the button). Your phone will enter a menu with black background and orange letters. Touch screen is not available here and the Menu button, the left one, serves no purpose at all. To control everything, you use the volume buttons at the side of your phone as Up/Down respectively, the Home button (the middle one) works as Enter and the Back button, the right one, is used to go back, as you might imagine. Recoveries are used to flash any flashable file to your phone. To exit and return your phone to normal, just back until the main menu and select Reboot Phone. It will reboot normally, and CWM will not show up unless you call for it with the back button.
-ROM: Its basically the OS that we install in our phones. It can be Custom or Stock: Stock ROM is the version that came with our phone, created by Google and then modified by your phone's brand company and then by your carrier, to go to your phone on it's original closed package. Also we have Custom ones, that are user-modified versions of Android. Every ROM in xda is a Custom ROM because they are developed by the user who uploaded it. We call it ROM because it resides in the ROM (Read-Only Memory) of our devices.
-Root: The first thing you must do over any Android device to get the full potential of itself, is rooting. Android, in basic terms, is based on Linux. Yes, that OS for computers you've probably heard of (If not, don't worry. You don't need to know about it.). And it is running just in your hand. On Linux, you need to get SuperUser permissions over a set password to make changes on the computer like installing programs and such things. On Android, you do not get his password and by default it is blocked, and rooting your phone means that you get this SuperUser access. Yes, if you are the one who goes exploring the phone 'till the last folder and modifying everything you possibly can, you will surely mess your phone up. But don't worry, if you just Root your phone and let TRUSTED apps to do their stuff, you are safe. What do I mean by trusted? With Root permissions you can do whatever you want on your phone, and so do Applications. You should just install applications whose developer you know you can trust, such as xda or market developed applications. Remember to always check the comments or posts people do reviewing their experience with that application, and beware if anyone tells so. Anyways, people is not that dumb and they have made the phone ASK for your permission before giving any new app the so called Root access.
-Run: To open a certain program or app. Can be used as "Running" for a certain program or app that is actually open, and so on.
-Stock: It refers to something that comes pre-installed on our devices, available when we just get them from the manufacturers.
-UI: The User Interface is the system shown on the screen of a device for you to interact with it.
-Undervolt: Usually abbreviated UV. It is the opposite of Overclocking, and, on phones, it consists of lowering the default voltage of the processor to make it run slower and thus decrease battery consumption.
3. Getting Started:
3.1 - Rooting
Steps:
-You can't imagine how easy and quick rooting can be. The first step, is to enable "USB Debugging" on your phone. I am going to be honest, I don't know what the **** is this, but keep it enabled. Always. Hehe. To do this, go to Settings and then under the Applications tab. Then, scroll down and go to Development. And there it is, you should tap "USB Debugging" once to get it checked and activated.
-Then, you need this software (Don't worry: it is free and very light, and you can just delete it after root). It is called SuperOneClick and this is the lastest version (2.3.3) until now. This is a screenshot of the interface that I grabbed from the original site. Install and open SuperOneClick, and continue to the next step.
-Now, with the USB Debugging enabled on the phone and SuperOneClick running on your computer, grab your USB cable that should have come along with your phone as your charger and connect with it your PC and your phone. On the phone it should show a message asking what to do, you should tap the option to charge the phone (This option is kinda "do nothing", it is the same as charging it from the wall). Now, go to SuperOneClick and click the big "ROOT" button. It should do all the work, so your task is to wait. Wait until it says it is ready and rooted, and then reboot your phone.
-Voile! Your phone is now rooted.
3.2 - Getting your Recovery - CWM Recovery
Steps:
-First, download this little program. It is a small Batch file (Commands for Windows) made by a user on this community called rect2409. On the original thread -Link under credits- you have a Linux version of this program, but I'm afraid have never used it and you will have to figure it out by yourself (Linux experienced-users encouraged to review over here). Extract the ZIP file and go into the folder you just extracted.
-Open install.bat. Batch files can be dangerous on the wrong hands but very useful on the right ones, so if any anti-virus or some kind of a security system tries to block this from working, tell them it is safe. You have my word (It wasn't even uploaded by me, so you can be sure I'm doing no trick here ). It will open a small black window with white text, follow it's instructions and answer it's questions. When it asks you for yes or no (Y/N), you have to write Y for yes or N for no and then press enter.
-When it says "If no errors are listed above then CWM has been installed. Finished.", you can close the window and delete everything you downloaded if you want. Everything you need on your phone is now there, so there's no problem if you want to delete this stuff.
-If you want to access CWM (That's how your new Recovery is called), you have to reboot your phone and at the "Sony Ericsson" text screen, press the "Back" button several times.
3.3 - Avoiding Baseband issues --Uncomplete--
Intro:
Your Baseband is a pretty large code that can be checked on your phone by going to settings and scrolling sown to "About phone". There, just like it says your Android version on a grey section, it should say your Baseband version on another. It should be a large code using both letters and numbers in a format like this ?????-????????-????? (? representing anything and - being itself, whatever it is called -I don't know it's english name-). What really matter are the last three digits, that have to be -015. If you have that, skip this step, because you are already done: The problem is when you have -006 (Like I had) or anything else, if it is possible. The point is that you NEED -015 Baseband version.
Steps:
-Of course, first make sure you have a wrong version of the Baseband, if you have the correct one, skip section.
-When you are sure you need to change your baseband, you have to change your "build.prop". Build.prop is a file hidden by the system, accessible via Root, that holds and manages some information and configuration about the phone. So, the first thing you need to do, is to get...
---To be continued---
Users who have helped:
karthiks.840 - ImInMunichBitch -
Click to expand...
Click to collapse
For Dictionary,
-ROM: Its basically the OS, we call it ROM because it resides in the ROM of our devices.
-Flashing: To install a new ROM. Basically any ROM will be in a zipped format. It can be flashed via any "Recovery".
-Recovery: A piece of program that can be optionally started on booting (In our devices by pressing "Back" button multiple times, when the device is turned on)
Just a quick suggestion: Everything you so far wrote is also applicable to the Robyn (X10Mini, E10i). If you keep it this general, you might consider posting this in the General Section, and maybe a mod could make it a sticky. Since this is not really about actual development, it looks kind of out of place in the development thread.
But keep up the good work
@nico444164: Thanks nico444164! This is probably the BEST thing I have ever seen on XDA - and I've been here since Mikevhl 's FroYo rom early 2011 (he was one of the main devs for x10 mini Pro) , followed by owain94 , slade87 , and paul-xxx who all slowly took over (over their predecessor's) one after another, slowly. I've never seen such a noob-friendly guide here at xda and I agree with your sentiment about it just not "being the way" it is here at xda. Frankly, it should be though and this thread by you is a hopefully a good indicator of/catalyst for xda slowly changing for the better. Cheers nico444164!
Suggestions for dictionary:
CyanogenMod:
Most famous Android-based custom rom of all times with many official and unofficial ports for many Android devices.
Brick:
Device doesn't boot anymore (fullbrick) or partially (halfbrick --> often bootloop to SE logo). Caused by wrong or incompatible changes in system related parts of Android (or many others as we know by now).
Stock:
--> Stock Rom: the operating system of our devices, how we get it from the manufacturer
--> Stock Kernel: same as Rom
Bootloader:
That part of the operating system, which boots up your device and sets everything on boot, so your Android can work as usual.
Unlock it allows us to flash custom kernel with improvements compared to stock one.
PC Companion, Flashtool, SEUS:
All three are tools for your computer to update, flash or revive your phone.
--> PC Companion: Programm by Sony Ericsson to update and save your Rom or parts (settings etc.) or to send media on your device
--> Flashtool: custom programm (credits to Androxyde and Bin4ry) to root, flash and set up many more things on your device
--> SEUS (or Sony Ericsson Update Service): Programm by SE to update your official rom (often the last chance to revive your bricked device)
Back Up:
Same as on a computer; saves the rom and its settings on your SD to recover it, when something went wrong (all usually via Recovery).
Android Versions:
--> Eclair 2.1: Stock version for our phones
--> Froyo 2.2: Follow up to Eclair with some modifications
--> Gingerbread 2.3: Mostly used version for our custom roms
--> Honeycomb 3.x: Version mostly for tablets
--> Ice Cream Sandwich: 4.x: Hybrid version for phones and tablets
APK:
File extension used for android based applications, if you want to install them manually and not from the market.
Launcher, Home Screen Replacement:
The application that is used by android to show up your apps, homescreens etc. Replacement apps take over those things (often used for more personalization).
A2SD, APP2SD, Link2SD:
Apps that allow you to free up your system memory by moving (non system) apps to your SD. Many custom roms implemented this in native settings.
GAPPS:
Commonly used google apps. Often in packages to flash them via recovery after installing a custom rom.
(Market/Playstore, Maps, Youtube etc.)
OC, UV:
-->Overclock (OC): used to get higher cpu values (decrease battery life but may increase performance).
-->Undervolt (UV): used to get better battery life by decreasing the voltage used by the cpu.
Just a few suggestions for this thread here.
I like the idea, would be a good sticky to new users, because this forum is
so high under development that many users forget that new ones may never heard of basic android knowledge.
Corrections are always welcome, hope my english is not that bad
Keep it up.
Marius
karthiks.840 said:
For Dictionary,
-ROM: Its basically the OS, we call it ROM because it resides in the ROM of our devices.
-Flashing: To install a new ROM. Basically any ROM will be in a zipped format. It can be flashed via any "Recovery".
-Recovery: A piece of program that can be optionally started on booting (In our devices by pressing "Back" button multiple times, when the device is turned on)
Click to expand...
Click to collapse
Added! Just changed some words I just thought should make a section for the users that help. Will do that in a few minutes.
SmG67 said:
Just a quick suggestion: Everything you so far wrote is also applicable to the Robyn (X10Mini, E10i). If you keep it this general, you might consider posting this in the General Section, and maybe a mod could make it a sticky. Since this is not really about actual development, it looks kind of out of place in the development thread.
But keep up the good work
Click to expand...
Click to collapse
Actually, that rooting process is kinda global. I thought about making this post a bit more general, but I wanted to start by little and taking my time, so maybe in the future I will ask someone to change it to General and I will add some info about each phone in details, if this gets to grow enough.
Also, I thought maybe this wasn't the place since it is not development, but:
-As a noob, I just checked this thread since I thought the others were exclusive for the Robyn.
-This is still particular to Mimmi.
-I have seen several tutorials and guides related to this on the Mini Pro development section, so I thought that if I am not the only one and it doesn't really hurts to have it here, it should be no problem. Besides, if this didn't work and get to be a real fail, it will just be forgotten with every other old posts out there
nightwing369 said:
@nico444164: Thanks nico444164! This is probably the BEST thing I have ever seen on XDA - and I've been here since Mikevhl 's FroYo rom early 2011 (he was one of the main devs for x10 mini Pro) , followed by owain94 , slade87 , and paul-xxx who all slowly took over (over their predecessor's) one after another, slowly. I've never seen such a noob-friendly guide here at xda and I agree with your sentiment about it just not "being the way" it is here at xda. Frankly, it should be though and this thread by you is a hopefully a good indicator of/catalyst for xda slowly changing for the better. Cheers nico444164!
Click to expand...
Click to collapse
Thanks for your message and support! And yeah, I hope noobs can find their basic ways here on xda, at a single and simple thread, as you might have wanted. I did, at least It would be only better if we could include all this novice people into this real complex world of development, even just as users.
ImInMunichBitch said:
Suggestions for dictionary:
CyanogenMod:
Most famous Android-based custom rom of all times with many official and unofficial ports for many Android devices.
Brick:
Device doesn't boot anymore (fullbrick) or partially (halfbrick --> often bootloop to SE logo). Caused by wrong or incompatible changes in system related parts of Android (or many others as we know by now).
Stock:
--> Stock Rom: the operating system of our devices, how we get it from the manufacturer
--> Stock Kernel: same as Rom
Bootloader:
That part of the operating system, which boots up your device and sets everything on boot, so your Android can work as usual.
Unlock it allows us to flash custom kernel with improvements compared to stock one.
PC Companion, Flashtool, SEUS:
All three are tools for your computer to update, flash or revive your phone.
--> PC Companion: Programm by Sony Ericsson to update and save your Rom or parts (settings etc.) or to send media on your device
--> Flashtool: custom programm (credits to Androxyde and Bin4ry) to root, flash and set up many more things on your device
--> SEUS (or Sony Ericsson Update Service): Programm by SE to update your official rom (often the last chance to revive your bricked device)
Back Up:
Same as on a computer; saves the rom and its settings on your SD to recover it, when something went wrong (all usually via Recovery).
Android Versions:
--> Eclair 2.1: Stock version for our phones
--> Froyo 2.2: Follow up to Eclair with some modifications
--> Gingerbread 2.3: Mostly used version for our custom roms
--> Honeycomb 3.x: Version mostly for tablets
--> Ice Cream Sandwich: 4.x: Hybrid version for phones and tablets
APK:
File extension used for android based applications, if you want to install them manually and not from the market.
Launcher, Home Screen Replacement:
The application that is used by android to show up your apps, homescreens etc. Replacement apps take over those things (often used for more personalization).
A2SD, APP2SD, Link2SD:
Apps that allow you to free up your system memory by moving (non system) apps to your SD. Many custom roms implemented this in native settings.
GAPPS:
Commonly used google apps. Often in packages to flash them via recovery after installing a custom rom.
(Market/Playstore, Maps, Youtube etc.)
OC, UV:
-->Overclock (OC): used to get higher cpu values (decrease battery life but may increase performance).
-->Undervolt (UV): used to get better battery life by decreasing the voltage used by the cpu.
Just a few suggestions for this thread here.
I like the idea, would be a good sticky to new users, because this forum is
so high under development that many users forget that new ones may never heard of basic android knowledge.
Corrections are always welcome, hope my english is not that bad
Keep it up.
Marius
Click to expand...
Click to collapse
Adding them right now And about the last thing you said, yes, it is so hard to join this community as you may all know, at least for users with no knowledge at all over any complex computer language. I consider myself an advanced-user, and even as that I had troubles at getting started. I can't imagine how hard it would be for a non-geek to flash something on their phones! EDIT: Added!
A very good guide for newbies! Will help a lot of people here! Ah, the old days, I remember, the first time I tried installing xREC I messed up and it wouldn't boot, scared the **** outta me xD had to do some reasearch before I could get back to normal. So this would be of great help!! Keep up the effort!
P.S: debugging mode is actually development mode. It allows transfer of data between the PC and the mobile. That's how you are able to run adb commands ( things like rooting, pushing APKs etc.) through the PC onto the phone!
Sent from my U20i using XDA
Wow... The guide is so complete... Even I don't know what I can add there xD
Hmm... How about adding some simple default tricks ?
I found that several user are asking how to backup their data... How about telling them how to upload their phonebook data to gmail and backup their apps through titanium backup ?
I think we can have some "unlocking bootloader" infos in here, as latter ROMs need to have custom kernel installed...
You can refer about the steps to unlocking bootloader in here :
http://forum.xda-developers.com/showthread.php?t=1462278
Hope that helped everyone
speedsys said:
A very good guide for newbies! Will help a lot of people here! Ah, the old days, I remember, the first time I tried installing xREC I messed up and it wouldn't boot, scared the **** outta me xD had to do some reasearch before I could get back to normal. So this would be of great help!! Keep up the effort!
P.S: debugging mode is actually development mode. It allows transfer of data between the PC and the mobile. That's how you are able to run adb commands ( things like rooting, pushing APKs etc.) through the PC onto the phone!
Sent from my U20i using XDA
Click to expand...
Click to collapse
Yees! That old days haha! I did exactly the same, me and my friend got our pretty new phones bricked
, so we were kinda.. O.O! Oh, divine SEUS. And about the Debugging stuff, I will add it tomorrow - Its kinda 2am here and tomorrow is another fun Wednesday to keep the awesome routine, hurray.
StardustGeass said:
Wow... The guide is so complete... Even I don't know what I can add there xD
Hmm... How about adding some simple default tricks ?
I found that several user are asking how to backup their data... How about telling them how to upload their phonebook data to gmail and backup their apps through titanium backup ?
I think we can have some "unlocking bootloader" infos in here, as latter ROMs need to have custom kernel installed...
You can refer about the steps to unlocking bootloader in here :
http://forum.xda-developers.com/showthread.php?t=1462278
Hope that helped everyone
Click to expand...
Click to collapse
It is not a bad idea to add the tricks, but this is quite a big job and I would like to finish keep my objectives clear and then start thinking of adding something else haha And bout the bootloader, yes, it will be added, my plan is to cover every single change available to your phone from complete Stock, Rooting and Installing Recoveries already written. Next I will introduce Custom ROMs, flashing aditional features like Hotfixes or Modules for specific ROMs, unlocking Bootloader, Custom Kernels, and so on. And maybe reviews about the best ROMs for the user to choose from what he best likes. Something like that is what I have in mind by now.
Sent from my U20i using XDA
Install CWM : error: protocol fault (no status)
rooted xperia X10 mini.
USB debug on
phone connected to pc in charge mode.
When I run install.bat for CWM (3.2 in manual), I get an error during first exploit. Here's the complete trace from install.bat:
Code:
ClockWorkMod Recovery Installer for X10 Mini Pro by rect2409.
Requirements and credits are listed in the README.txt file.
Please make sure requirements are met before continuing.
Please make sure that your phone is connected to your PC and USB debugging is en
abled.
Press any key to continue...
Is your device ROOTed? (Y/N):y
Starting ADB Server.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Pushing exploit to gain ROOT access.
426 KB/s (585731 bytes in 1.341s)
error: protocol fault (no status)
Mount system as R/W.
Do you already have a recovery installed? (Y/N):n
Pushing recovery tar file.
1898 KB/s (5027840 bytes in 2.586s)
Pushing chargemon.
130 KB/s (1341 bytes in 0.010s)
Pushing busybox.
2175 KB/s (735308 bytes in 0.330s)
Setting permissions for recovery tar file.
Setting permissions for chargemon.
Setting permissions for busybox.
Mount system as read only.
Reboot phone.
Stopping ADB Server.
If no errors are listed above then CWM has been installed.
Finished.
After the error is displayed, I got sounds on my pc and phone just like when I disconnect usb then reconnect it. Then the program continue (ask whether a recovery is already installed).
I don't think CWM has been installed: actually, when i press back many times on my phone while starting, nothing happens : normal boot from SE.
Can anybody help ?
Looks like you haven't got the adb drivers so its not actually pushing anything. Can't remember how to install the, now but I think its a package included in flash tool that you use.
X10man
Sent from my Nexus 7 using xda premium
x10man said:
Looks like you haven't got the adb drivers so its not actually pushing anything. Can't remember how to install the, now but I think its a package included in flash tool that you use.
Click to expand...
Click to collapse
I have installed drivers found in flashtool drivers 1.0.2, but still get that same error :
Code:
Pushing exploit to gain ROOT access.
1111 KB/s (585731 bytes in 0.514s)
error: protocol fault (no status)
Please help.

[Q] Rooting Problem: No space left on device

Ok...I have read all the pertinent threads on this to no avail. Am simply trying to root my vibrant. Has android 2.2 installed. I copy the required "update.zip" file to internal storage root location, reboot phone into recovery mode, reinstall packages, reboot again. Phone comes back fine with the Superuser.apk installed. It runs, but 'su' does not run.
Upon closer inspection, 'su' is found in the "/system/sbin" directory. Problem is it has a file size of 0. That's right, it is an empty program. If I unzip "update.zip", it has "su" in it, but does not have a file size of zero. It's like 22k in size.
So...then I tried running SuperOneClick from my PC...think it is 2.3.3. It runs fine, and says it complete fine...but when I look at the log it spits out, it clearly indicates the "system" directory has "No space left on device". When tries to copy "su", it can't. Now...my first thought was to delete some files in the "app" directory...no can do...everything is "read only" in permission. Can't change permissions without "su" working. I suspect there is something else here at work making the "system" appear full. Any ideas are welcome.
Thanks,
Steve
Odin back to eclair, then try super one click. I think I used an older version, like 1.7.5 or something.
I am Jack's smirking revenge.
samsgun357 said:
Odin back to eclair, then try super one click. I think I used an older version, like 1.7.5 or something.
I am Jack's smirking revenge.
Click to expand...
Click to collapse
This interest in rooting started when I could not turn off (permanently) Wifi Calling by uninstalling the APK. Well, to do this one needs to have su access. It sounds like if I downgrade to Eclair (2.1), root it, then upgrade to Froyo (2.2), I will loose root privledges again and be back to square one. Someone must have run into this problem too???
No you won't lose root going back to froyo.
I am Jack's smirking revenge.
Hi Steve,
Let's try some things. Do you know how to use ADB/SDK on your PC? If so, then let me know and I will be able to explain how to do this manually.
For now let's try some things first.
Since you already have 2.2 on there, the Update.zip method won't work. You have 3 choices here.
*First you can go into the Dev section and find the 3e to 2e Recovery thread and that will tell you how to convert your 3e recovery back to 2e so that the update.zip method will work.
*Second Are you wanting to stay on stock Froyo 2.2? If so, I think what might just be easier for you, would be to Odin back to stock JFD and then you can use the Update.zip to install CWR and then install •T959UVKB5 2.2 Stock by Moped_Ryder. It is basically Stock-Rooted Froyo. I do believe there is a Odin image floating around here that is Stock-Rooted as well.
*Third. Since you are apparently not afraid to mod your device, there are several custom ROMs out there that may work better for you. If you want something stable, you can pick from a bevvy of tweaked optimized Froyo ROMs. If you want something stable and still being worked on (sort of, but not really at this point bc they are all pretty much stable), I suggest and ICS ROM. And still if you are wanting to push the envelope, there is always Jelly Bean 4.1/4.2 but I must warn you that they are extremely experimental and it is not for the weak.
Almost all of these files can be found stickied in the Dev section in either my Repo thread or N00B's Bible thread.
The choice is yours and once you make it, let us know and we will help you through it.
Woody to the rescue! I'll admit, the op had me a little confused as to what they were trying to achieve.
I am Jack's smirking revenge.
Hi Woody,
I used ODIN and went back to 2.1, booted up update.zip (with CWR), then installed a rooted version of 2.2 (like you said). All is good now. Very interesting these phones. Thanks for the informative post.
Regards,
Steve

Categories

Resources