Database Info

[Q] Modding From A to B Guide?

Sorry to sound pig ignorant about phones but I am ... my expertise is in PCs. So anyway I want to upgrade the Hero with CyanogenMod.
I backed up my contacts, apps, etc and rooted the phone with unrevoked ... lost everything in memory in the process, but that's OK -- the important stuff is backed up.
Rebooted into stock 21. ROM and skipped all the new user stuff ...
OK, here's where I'm lost ... to load the CyanogenMod ROM I apparently need something like Amon-RA, but to load Amon-RA image file I need to install the SDK pack.
So I downloaded the SDK pack, but it is nothing like what is described in all the install SDK posts I've been able to find. What I have found are instructions about running ASroot and other files that don't exist in the SDK version I have.
So like what do I do now, more important ... is there an A to B thread for doing this mod starting from a stock phone, going to unlocking, than loading SDK, than installing Amon-RA (or equivalent) and than installing CyanogenMOD.
I know all this info is out there, but it seems like most of the files I've found don't interface well in the sense that the ones that talk about doing step one aren't terribly relevant to ones that talk about step 2, etc.
Thanks

Yes. Its a sticky at the top of the page. Search "guides" lol...
Sent from my HERO200 using XDA App

All you need to do with the sdk is download it and extract it. I just put it in the root of my C: drive. Then open a cmd prompt in windows by going to Start > Run > cmd (press enter). Then in the command prompt you need to change directories to the sdk folder you extracted. For example, mine is in C:\android-sdk-windows. I just type "cd c:\android-sdk-windows" then "cd tools" to get into the directory where you can run the adb program. Make sure your phone is in debugging mode by going to settings > applications > development > check the USB Debugging box. Then you can hook the phone up to the usb and run the command "adb devices". If everything is working correctly then you should see a device serial number show up. If that doesn't work make sure you have the htc drivers installed by downloading htc sync from their website and installing it.
Once adb can see the phone then you should run the command "adb shell" and then when you get a $ prompt type su in order to elevate to root. Make sure you put a recovery image on the phones sd card using step 4 from this guide: http://forum.xda-developers.com/showthread.php?t=694572 I think he has a link to download the recovery in that guide but just in case here is a direct download link for the recovery: http://www.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-heroc-v1.6.2.img Feel free to rename it to recovery.img so that the commands in the guide can be used as is.
Now you should be able to start at step nine from the guide in that thread (you should be in an adb shell when you start). It should be the adb command to flash a recovery image. Once you do that installing roms is as simple as putting them on your sd card and booting into recovery to select the flash option.

Error: can not load recovery-Tiamat-R4c-100611-1150-cwm

So I have my Xoom unlocked and I am trying to flash the recovery in order to root. I have the recovery in the platform tools folder along with fastboot and all that, and I'm able to get the Xoom into fastboot from adb, but I can't get the recovery to flash. I'm typing the name correct. And I'm putting in 'fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img' without the quotes. Honestly I'm a little bit stumped at this point.

I have had the same issue for the past few days I have also tried the steps here no luck.... http://forum.xda-developers.com/showthread.php?t=1249798

supenova3000 said:
I have had the same issue for the past few days I have also tried the steps here no luck.... http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
I used the same guide. It just makes no sense that I can control the Xoom and unlock it, but I can't flash the darn recovery.

williamthegoat said:
I used the same guide. It just makes no sense that I can control the Xoom and unlock it, but I can't flash the darn recovery.
Click to expand...
Click to collapse
I tried moving the files from the tools folder to platform tools still no luck.. all of this for the I C S flash I'm going to keep working on a solution I will let you know if I have any luck!

So I have the android sdk in c:\ , and in the sdk folder I have everything, and in the platform tools I have my fastboot and recovery. I then use cmd to get into adb, then I put the xoom in fastboot. From there I try to flash the recovery, which always fails. I must be doing something wrong here.

Try downloading the IMG again. Or try out the rogue recovery. I actually like rogue better.
Sent from my MB860 using xda premium

I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys

Think you have to be stock to flash to ICS, at least that was the word yesterday.
I gave up trying to root just as I found out about the ICS update.

williamthegoat said:
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys
Click to expand...
Click to collapse
Two simple errors:
1) not opening the command window from the folder where you have fastboot and the image files you're trying to flash; and
2) not realizing that you have hidden file extensions in Windows, and typing ...recovery.img.img

williamthegoat said:
So I have my Xoom unlocked and I am trying to flash the recovery in order to root. I have the recovery in the platform tools folder along with fastboot and all that, and I'm able to get the Xoom into fastboot from adb, but I can't get the recovery to flash. I'm typing the name correct. And I'm putting in 'fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img' without the quotes. Honestly I'm a little bit stumped at this point.
Click to expand...
Click to collapse
I assume that you've set up a path in environment variables to run adb and fastboot from ay directory... and are running the flash command from a folder other than where your .IMG file is located. In order for fastboot to find the file you're trying to flash, you actually have to run your flash command from the folder your file is located...
So, cd\...\platform-tools and then flash

The simplest way I perform all of my operations for this:
I leave everything installed into it's default locations. I download tiamat's CWM image and place it into the platform-tools folder.
For Windows 7, I use Windows PowerShell.
For example: Open Start Menu > Type "power" to search, "Windows PowerShell" should show up. (For me, its default at the top - so I press enter to open it)
Once opened: I type this configuration EXACTLY as is: (Keys in <>)
Code:
cd C:\Pr <TAB><TAB> An <TAB> An <TAB> Pl <TAB><TAB> <ENTER>
This above brings me directly to:
C:\Program Files (x86)\Android\Android-sdk\Platform-tools\
Of course, this will be different depending upon your computer setup. I've nailed this routine to get to the path the quickest.
to use FASTBOOT (XOOM already in fastboot mode):
Code:
./fastboot flash recovery rec<TAB><ENTER>
This auto completes the filename as ./recovery-tiamat-r4c-xxxx.img
Of course, depending on how many files/folders you have, you may have to hit <TAB> multiple times. I have to do it 3 or 4 times to select the recovery image I want.
Auto-complete is a nice thing. "./" is added to command from the working directory.

williamthegoat said:
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys[/QUOTE
Worked for me too!!! Thanks!!!
Click to expand...
Click to collapse

[Q] please help using heimdall

hello devs i am very much interested in checking out the bhundven's cyanogenmod.the instructions say that i have to use heimdall to flash his kernel-sms-kj6-v0.2.0.right now i am using windows 7 64-bit.when i tried to load the zimage in the heimdall firmware packages it says tar header contains an invalid file size.so i clicked flash tab and i can see a pit file there i tried loading the zimage file again and it says its not a valid pit file.i tried loading zip file also but still dint get it.anybody please please help me i am a noob

saketh91 said:
hello devs i am very much interested in checking out the bhundven's cyanogenmod.the instructions say that i have to use heimdall to flash his kernel-sms-kj6-v0.2.0.right now i am using windows 7 64-bit.when i tried to load the zimage in the heimdall firmware packages it says tar header contains an invalid file size.so i clicked flash tab and i can see a pit file there i tried loading the zimage file again and it says its not a valid pit file.i tried loading zip file also but still dint get it.anybody please please help me i am a noob
Click to expand...
Click to collapse
How exactly did you try to flash it with Heimdall? In his [KERNEL][UVKJ6][BETA3.1] Subtly Modified Stock with CWM5 + Voodoo Lagfix [1/14/2012] thread he has instructions on how to flash the kernel via Heimdall & the command prompt. I have not tried it with this kernel yet, so I'm not 100% that's what you're looking for.

thanks for the kind concern and sorry for the late reply.my problem is that i installed the drivers in heimdall as given in post and then i put my phone my phone to download mode and then when connected to pc heimdall says no device compatible download mode detected i tried reinstalling the drivers,installing kies,restarting laptop and nothing worked for me please help

I just tried this and it works fine. Win7 64bit
I'll post my steps in a minute.
======================================
Install Heimdall - C:\Test\heimdall-suite-1.3.1-win32
Unzip “kernel-sms-kj6-v0.2.0-bml”
Copy "zImage" from \kernel-sms-kj6-v0.2.0-bml\kernel_flasher to C:\Test\heimdall-suite-1.3.1-win32
Put phone in download mode
Install driver “zadig” at “C:\Test\heimdall-suite-1.3.1-win32\Drivers”
Option list all devices – select Samsung and install driver
Open Command prompt “Run as administrator”
cd C:\Test\heimdall-suite-1.3.1-win32
heimdall flash --kernel zImage --recovery zImage
Phone boots with new kernel

so you say you have to copy the zimage file in heimdall suite folder itself?
when i load the file into heimdall firmware package or pit file i get either "tar header contained invalid file size" or "invalid pit file" error message
and also i am sure i installed drivers for my phone in heimdall as stated in the post
but still heimdall is not detecting my phone it says "failed to detect compatible download mode device"
please help me if you know anything abt this
thanks for the reply

Attached are two jpgs, first is device with Hiemdall driver (libusb) and the second is with Samsung driver in device manager screen. To change driver just un-install the device in device manager and then let computer scan for hardware changes, this will get you back to Samsung driver. You must use Heimdall to install driver for libusb. Hope this helps... Are you trying to use the Heimdall frontend? I'm not using frontend just command mode, try it...

actually i used frontend first i found it not detecting my phone and so i used heimdall cmd no luck there too
i tried uninstalling samsung usb drivers from the system and installed it again
today morning i found a samsung composite usb device option list(which i was not getting it before)
so the changes i made is changed the compatibility to windows xp and tried it worked fine but still its not detecting help me please please

this is what it looks like after i install heimdall driver
when i go to cmd go to heimdall and flash kernel image it says device not detected

From off
I press both up volume and down volume together
then connect the usb cable to my phone ("Warning!!" screen displayed)
then press the up volume to get download mode ("Downloading" screen displayed)
I enter at the command prompt: heimdall detect
the system returns: device detected

If heimdall is connecting ok then open the command window in the same folder you have the zImage in.
then at command prompt type: heimdall flash --kernel zImage (hit enter)
it will flash the zImage and reboot.. Done.

Racing19969 said:
If heimdall is connecting ok then open the command window in the same folder you have the zImage in.
then at command prompt type: heimdall flash --kernel zImage (hit enter)
it will flash the zImage and reboot.. Done.
Click to expand...
Click to collapse
Stop racing and smell the roses. The OP has a problem where heimdall does not see his device. Have you seen this type of error? Read the entire thread, maybe. Thanks for the help and look out for that tree!

i hope changing the os to windows xp will help i installed drivers for heimdall as instructed in the forum i followed every step suggested by some other devs but still no luck i dont know wt to do now

You can wait for them to finish CM7. You can make sure you are using the correct Heimdall Suite for your computer. You can look at Juls guide in the general section for additional help with Heimdall.

i will tell wt i did frm the begining
first i already had samsung galaxy s usb drivers installed in my windows 7 with which i used to odin roms into my phone then
and downloaded heimdall 1.3.2(binaries it says) for windows and i changed compatibility of zadig to windows xp and ran as an administrator
now i put my phone in download mode and connected to pc while on zadig
i found samsung composite usb device in the list i selected that & installed drivers (wtever was selected by default) then i disconnected my phone and restarted once and then put it to download mode again
this time i opened heimdall-frontend and in utilities i clicked detect
it said "failed to detect compatible download mode device"
i copied zimage file from bhundven's kernel to heimdall folder
now if i load heimdall firmware package and select zimage file i get an error saying "tar header contained invalid file size"
if i load flash pit file and select zimage file it says "invalid pit file"
so i tried this command in heimdall cmd
"heimdall flash --kernel zImage"
it said device not detected
i dont know wt to do please get me out of this situation and thanks for taking concern and replying me regularly

saketh91 said:
i will tell wt i did frm the begining
first i already had samsung galaxy s usb drivers installed in my windows 7 with which i used to odin roms into my phone then
and downloaded heimdall 1.3.2(binaries it says) for windows and i changed compatibility of zadig to windows xp and ran as an administrator
now i put my phone in download mode and connected to pc while on zadig
i found samsung composite usb device in the list i selected that & installed drivers (wtever was selected by default) then i disconnected my phone and restarted once and then put it to download mode again
this time i opened heimdall-frontend and in utilities i clicked detect
it said "failed to detect compatible download mode device"
i copied zimage file from bhundven's kernel to heimdall folder
now if i load heimdall firmware package and select zimage file i get an error saying "tar header contained invalid file size"
if i load flash pit file and select zimage file it says "invalid pit file"
so i tried this command in heimdall cmd
"heimdall flash --kernel zImage"
it said device not detected
i dont know wt to do please get me out of this situation and thanks for taking concern and replying me regularly
Click to expand...
Click to collapse
If you still have the Samsung USB drivers installed, then I suggest uninstalling them. They don't seem to get along with the Heimdall drivers.
Next, put your phone in download mode & plug it into a USB port on the computer.
Run Zadig again. Try to reinstall the drivers from there if you can.
Run the Heimdall front end. See if it recognizes your phone now. If so, you should be able to open a command prompt and run the command:
Code:
heimdall flash --kernel zImage --recovery zImage
Let us know if it works.

as i stated earlier that i am gonna use windows xp for doing this i shifted to my pc which has windows xp in it.i followed all the instructions and it worked pretty fine in that now i am able to install cm7 but i dont know wt has happened to windows 7 as it dint allow me to properly work with it
anyways thanks to all of you guys for supporting me and for spending your time for me
i defenitely owe you guys thanks a lot

nothing works
odin heimdall whatever u wanna call it doesnt work for bricked infuse i been trying for 3 months like 3 hours a day but its ok im not in the right state of mind im a criminal. i steal others peoples stuff if i got a good oppurtunity and i will never stop not even if im a millionaire. i break random peoples windows with a bb gun. people like these are the ones that encourage me to do these things. all these threads dont work on my infuse so now im going to drive my car and shoot out someones window. this is just me and im me ftw

undetectedcriminal said:
odin heimdall whatever u wanna call it doesnt work for bricked infuse i been trying for 3 months like 3 hours a day but its ok im not in the right state of mind im a criminal. i steal others peoples stuff if i got a good oppurtunity and i will never stop not even if im a millionaire. i break random peoples windows with a bb gun. people like these are the ones that encourage me to do these things. all these threads dont work on my infuse so now im going to drive my car and shoot out someones window. this is just me and im me ftw
Click to expand...
Click to collapse
Old thread is old. Also, this phone is different then infuse. Check the infuse forum for help.

bhundven said:
Old thread is old. Also, this phone is different then infuse. Check the infuse forum for help.
Click to expand...
Click to collapse
Better yet go see a counselor. Will someone report this I'm mobile. Thanks

Bootloop after Trickdroid tweaks

Hello Forum,
I have a problem with my Htc One S today i installed Trickdroid 8.0 and it worked fine so i wanted to install the tweaks too. So i selected what i wanted and when the phone started it got stuck at the bootloader screen. I thought it just needed some time but after 15 minutes i gave up and turnt it off. Then i went into the recovery to install the rom newly but it always says it can't mount the sd card. Already relocked the bootloader and tried to install the europe ruu 1.78 but i got error 131 i have read that might be, beacause mine was branded by T-Mobile (but no simlock or else)
Really need help appreciate any answer

Really no one knows how i can fix this ? Need to fix it pretty soon because i need my phone :/ I can't even turn mine off, so i just let the battery die don't think that's to good either

Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.

j0hnh0lmes said:
Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.
Click to expand...
Click to collapse
I can't reflash in recovery, because it always says "can't mount sd card"
Don't remember all of the tweaks i did but i did the nova launcher, remove sense, some apps, all of the tweaks on the first page and some other.

Okay now I did a "clear storage" and a "reset to factory defaults" with a stock recovery and after that i reinstalled the custom recovery again. Now I can access the sdcard again but it's empty of course. Then i bootet in recovery and tried to push the trickdroid zip on to the sdcard via adb like this "adb push Trickdroid_v8.0.0.zip /sdcard/Trickdroid_v8.0.0.zip" but then it says:
daemon not running starting it now on port 5037
daemon started successfully
protocol failure
and simply ends. How can I push the Rom really need help, because my phone has no rom at all right now ?
ah okay needed to use the adb in the android sdk folder not in the little fastboot folder i had it just worked

Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"

rugmankc said:
Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"
Click to expand...
Click to collapse
Thanks for your help but as i have written i already got it back working thread can be closed

Sorry,
I posted before your edit showed up--

Glad to hear.

steps for next time
Hi, just before the thread is locked.
What has helped me in more of these occassions:
1. Make sure you read the install instructions of the ROM builder (I overlooked the 'flash Boot.img' which was added after some version)
2. Make sure you don't 'custom' work your memory (no partitioning etc).
3. First install the ROM and do REQUIRED afterwork (most often: Data/factory reset. Which doesn't wipe your photo's or just your account information and saved settings that will interfere with new rom options)
4. after making sure it boots and it reboots.
5. If this is the case, make sure you get the tweak package pointed out by the rom builder.
6. If all else fails, first read up on XDA and rom builder's site (often community on XDA) THEN start actions well informed.

[Q] Problems loading factory image

I've looked all over, but cannot find anything on the problem I am having.
I go through the steps to load the current factory image onto my nexus s 4g through terminal on my mac, but for some reason it doesn't load everything. Here's what it says in terminal about the items that can't load:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
And here's what my folder looks like where I'm loading everything from:
I guess I can't post a picture from an outside source, so I'll just type in what my folder looks like:
boot.img
bootloader-crespo4g-d720spric1.img
flash-all.bat
flash-all.sh
flash-base.sh
image-sojus-jro03r
image-sojus-jro03r.zip
radio-crespo4g-d720sprilf2.img
there are files in the unzipped folder (image-sojus-jro03r) named:
android-info.txt
recovery.img
system.img
userdata.img
These seem to be some of the files that are missing, but even when i drag them over to the main folder, they still don't load. maybe something to do with the fact that they are .sig's?
I drag the flash-all.sh file into terminal and it loads and writes everything except for these .sig's, which I truthfully don't know what they are. Now I can't get into the correct recovery mode, it just shows some weird blue-lettered options that are different then the normal recovery options. That is why I think the fact that these .sig files are not loading is the problem.
I also booted up the new operating system and signed on, but for some reason none of my apps can download.
Sorry for my noobness, but I'm sure I'm missing one easy step that will fix my problems.
Does anyone know what I'm going through?
Any help is much appreciated.

Alright. I've searched the web and found a few different things. It seems that it's common for those .sig files to not load. Also, i loaded the factory image again and was able to download my apps.
I also now foolishly realize that to get a good version of recovery, I need to root my phone. I'm in terminal now, and for some reason adb is not showing my phone in adb devices. This wasn't a problem when I loaded the factory image, but now it's a problem when I'm trying to do this: http://forum.xda-developers.com/showthread.php?t=1129759
step 5 is a problem, but hey, I can turn off the phone and go into fastboot mode myself. I guess step 7 is the next problem I'm dealing with. Here's what I get in terminal when I do step 7 manually (I put a *#* where my name is just so everyone knows):
MacBook:~ *#*$ /Users/*#*/Desktop/adb-fastboot/recovery-clockwork-5.0.2.0-crespo.img
-bash: /Users/*#*/Desktop/adb-fastboot/recovery-clockwork-5.0.2.0-crespo.img: Permission denied
Does anyone know what I'm dealing with this time around?

You probably need to enable adb in Settings --> Developer Options. If it's an issue with adb while in recovery, i'm pretty sure the stock recovery (which will be overwritten on every boot from a stock ROM) doesn't allow it. What you need to do is flash a new recovery in fastboot (not in recovery).
Commands (while in fastboot mode):
/path/to/fastboot devices <-- this will tell you if your phone is connected properly
/path/to/fastboot flash recovery /path/to/recovery.img <-- this will flash the new recovery
You'll need to type in the path to fastboot unless you have it in somewhere like /bin or a more convenient environmentally recognised location. The command you typed there is the same as trying to open the .img file as a script, you want to tell fastboot to flash the file to the phone and not open it with the computer.
Edit: Also, once you root, you probably want to delete /system/etc/install-recovery.sh. That file replaces any custom recovery with stock each time you boot.

Thanks Harbb.
That's what I ended up doing, using fastboot. it worked perfectly. I did try to find the /system/etc/install-recovery.sh file in root explorer, but could not find it. don't know where it is.
Everything is rooted and restored on my custom rom to where I was previously using titanium backup.
Here's the tutorial I was using: http://forum.xda-developers.com/showthread.php?t=1129759
with this video being a walkthrough of the previous tutorial: http://www.youtube.com/watch?v=sP9ZDWmbLVM
I was actually using the recovery img in the android folder that I downloaded from the tutorial, and not the one he told me to download, which was my problem in the end. Here's the link to the download page where I should have downloaded it from: http://forum.xda-developers.com/showthread.php?t=988686&highlight=clockwork+4.0.0.2
Thanks again Harbb, much appreciated.

No worries buddy, glad you got it sorted.