Related
Sorry if this is the wrong section to post this, but i just had about 3hrs of "Did i really Jack this Up"... Not sure if this will go for everybody but its what i found out, a "Tip" i would call it.
If you have used the Nandroid backup (for safety) of cuz your like me and hate redownloading everything and customizing your home screens again, and you've ran into this error when trying to "Restore" from Recovery.
"Error: run 'nandroid-mobile.sh restore' via adb"
I did this and followed some steps online to do so, and then the boot screen would just keep reloading and never get thru...
Foundout, after you save your rom, and connect via usb to pc, and go into your "nandroid" folder, then choose the HT***** folder it will have your Back up, minez started with B******, i changed that name (i.e. manup - Eclair 2.1) so that i can easily choose which rom i wanted to run. well if there is any spaces in the "Name" of your Back-Up, you will get the "Error" listed above, i renamed the folder from; manup - Eclair 2.1 to manup-Eclair2.1 and then booted into recovery via device, and the Nandroid Restore worked perfectly fine, i tested this theory with two other roms i had in my nandroid back up and my theory was correct... so all in all, if you change the folder that has your "Back'd UP" info in it, dont put spaces in the new folder name.
my bad if i confused anyone it's lat. lol
Well, I guess I'll add on to this for fun! If you have low batteries, it'll say the same thing!
good to know, more info given the better
KAwAtA said:
Well, I guess I'll add on to this for fun! If you have low batteries, it'll say the same thing!
Click to expand...
Click to collapse
sanman1185 said:
good to know, more info given the better
Click to expand...
Click to collapse
Or if your sdcard is corrupted.
Okay so this tip comes from personal experience,k before I figured out how to fic the problem that this one created for me.
So, I did a backup before I flashed a mod someone did earlier. Well, the mod did nto work, and it broke some stuff on the phone, so I wanted to do a restore. That was an absolute no-go. I got this error message:
(image link)
So, I got a little worried that I had lots bigger problems. Long story short, I was missing the md5 file that nand creates when it makes a backup.
TIP: When doing a NANDROID backup, verify it's completeness by pressing your "back" key on your phone once the backup is complete. Scroll to USB-MS and select it. This *should* make a box pop up on your computer, meaning that you have access to your SD contents now.
In the SD card, navigate to nandroid/(Hero Serial Number)/XXX-XXXXXXXX-XXXX/ and make sure there is a nandroid.md5 file in there, as well as 3 other files, boot, data, and system.
If any of these are missing, press "Back" hard key to close USB-MS, and do another backup. Delete the current one if you do not have enough room.
The xxx-xxxxxxxx-xxxx above will be a folder, mine's named: BDS-20100523-0334, which is BDS-(year)(mo)(day)-(time). year 4 digits, month 2, day 2, and time 4 digits. If you have multiple ones, choose the most recent one, which would be the nandroid you just made.
Nice tip thanks, I do have a question though.
I thought the whole point of having a recovery in the Hero was to flash roms regardless of what breaks, even nandroid? I mean if your nandroid breaks you can just go into recovery enable usb drive and copy another rom over?
Yeah you should be able to flash any Rom regardless of whether you made a backup or not. I am just saying, its a helpful top to make sure your backup completed properly in case you ever want to go back to your old Rom, in your case, or if you're flashing an update that says will work with any Rom, or your just testing the update, and that update breaks. Same goes with current Rom modifications that you may want to try out.
Long story short, if you know you night need to nandroid backup or want to restore if you're just testing something, be sure to follow the tip above. One more step to save you problems.
-------------------------------------
Sent from your mom!
Hi devs,
Strictly speaking, this is not a development issue, but I thought it warranted some special attention as it sheds a little bit of new light on the "bricking" caused by Clockwork (version unknown).
A new XDA member, SoSickWiTiT, brought back an Eris from the grave. The phone he started with could only be put into RUU mode - initially it would not even start correctly in Hboot or Fastboot mode (weird, right?), and is now fully functional. The long and tortuous thread is here in the Q&A forum.
The essential finding was that the "bricking" was apparently caused by enormous numbers of pages in the flash memory device being marked as bad pages, and that this was correctable by using the "flash_erase" tool of the mtd-util project. (This tool allows you to reclaim flash pages marked as bad if they erase successfully.) I built some of the tools for ARM/Android and posted them up here.. As long as you can get Amon_RA to come up, you can run this tool from Amon_RA (using adb) and erase/reclaim partitions on a partition-by-partition basis.
Also SoSickWiTiT found a useful hack that I hadn't seen before: because he could only get his phone to start in RUU mode, he started the "Official RUU", ran it to the point where it unpacks all files, and then replaced the "rom.zip" file (in the Temp folder the RUU utility unpacks) with the HTC Root-ROM (renaming it to "rom.zip", of course). Because it signed by HTC, it got the 1.49.2000 S-OFF bootloader installed (but the rest of the install failed). SoSickWiTiT was then able to flash Amon_RA via fastboot and continue gaining traction from there. Note that just flashing a ROM from this point would not work - his mtd3 (system) partition appeared as if over 60% of the pages were marked as bad, and I think his boot partition was similarly affected. "flash_erase" was able to reclaim these pages using the "-N" command line option.
Anyway, the behavior of his phone (excluding the RUU-only behavior) was consistent with prior bricking reports of how filesystems appear to be "corrupted", and this causes difficulties flashing new ROMs (largely due to lack of free space). SoSickWiTiT reports that the phone he obtained from a friend had been bricked by "a failed ROM flash in Clockwork/ROM Manager followed up with an attempt to use the RUU" - there have been at least one other report of this exact same scenario causing the "bricking".
So now I am wondering - are there a few "bricks" laying around that might be rescued?
bftb0
Very interesting and good to know, thanks! And thank you for the tool, great work.
Think this could be applied to deleting the NRAM flash on a router? =p
WAIT wait wait!!!
He changed the bootloader from S-On to S-off??? Was it on 1.49? If so couldnt that have been used to root our phones, A LONGGG time ago? lol
Nikolai2.1 said:
WAIT wait wait!!!
He changed the bootloader from S-On to S-off??? Was it on 1.49? If so couldnt that have been used to root our phones, A LONGGG time ago? lol
Click to expand...
Click to collapse
A looooooong time ago - December '09 (circa "MR1") iirc, someone attempted to stuff a different - and unsigned - "rom.zip" file into the running (MR1) RUU.
Naturally, that didn't work, 'cuz it wasn't a HTC-signed PB00IMG.zip file. To my knowledge, this is the first time anybody tried doing things this way (swapping in the validly-signed HTC Root-ROM into the RUU's "rom.zip" location)... maybe it would have worked for the "leakers". I suppose that someone could roll back their phone and give it a shot to see it if works, but that seems sort of academic at this point - hence your "LOL".
There is evidence that both the RUU- and Hboot- based update processes actually end up checking the contents of the "misc" partition for version information TWICE - first before any flashing occurs, and second, only after the bootloader has been flashed and reloaded, but before the remainder of the PB00IMG.zip/rom.zip file has been flashed. I don't think that even at this point in time this behavior is well understood: it is possible that the hboot flash of the bootloader can occur, but then the subsequent flashing of the rest of the PB00IMG.zip file fails due to a "Main Version is Older" error. Sort of hard to understand why that would ever occur (it happened to me once, so I know it occurs).
For anybody that has a brick, but can get RUU mode running, it is certainly worth a try to see if they can replace the bootloader with the S-OFF bootloader - what do they have to lose? In this particular case, it is hard to know what the state of the misc partition was; after all, it was a phone that was previously rooted. The result obtained using the RUU utility likely depends on what was going on in the misc partition on that phone, so it is not obvious that this (RUU utility) "trick" is universal. It might have been that the same phone would have been happy to accept the Root PB00IMG.zip file - but SickWiTiT couldn't get the phone into Hboot mode initially, so that wasn't tried.
cheers
bftb0
So if I have been using Clockwork to flash a few roms do you think I would have any bad pages in my flash memory? Is there an easy way to check this?
xtreme3737 said:
So if I have been using Clockwork to flash a few roms do you think I would have any bad pages in my flash memory? Is there an easy way to check this?
Click to expand...
Click to collapse
I don't think that using Clockwork causes slow growth in bad pages; afaik, when the problem occurs - whatever causes it - only then do you see a catastrophic number of pages marked this way. I mentioned it only in case someone bricks their phone and then asks for advice here - they can check to see if this repair works for them at that time - after they have determined that this is the nature of their problem. In the meantime, there is not much need to worry about it.
Short of actually performing a flash_erase with the "-N" option turned on, I don't know off the top of my head a way to determine the number of bad blocks easily, and there are good reasons why you should not be doing that unless you absolutely have to.
The tool "nanddump" that I compiled actually reports the number of bad blocks - but it also wedges the Amon_RA kernel when you run it. Rats.
bftb0
I just wanted to add my thanks for this very informative and interesting information and tool in case it becomes necessary. I do use Clockwork (loaded from Amon RA), BTW.
Thanks for the useful info as always.
It really seems like a bad idea to use clockwork
Sent from my nonsensikal froyo
SikYou said:
Thanks for the useful info as always.
It really seems like a bad idea to use clockwork
Sent from my nonsensikal froyo
Click to expand...
Click to collapse
bftb0 said:
I don't think that using Clockwork causes slow growth in bad pages; afaik, when the problem occurs - whatever causes it...
Click to expand...
Click to collapse
I haven't once had an issue with Clockwork Mod through ROM Manager, and have been using it for 3+ months now.
thanks for this thread i sort of helped one person put their phone into the grave by telling them to flash an ruu (still feel bad about it)
jamezelle said:
thanks for this thread i sort of helped one person put their phone into the grave by telling them to flash an ruu (still feel bad about it)
Click to expand...
Click to collapse
That cus you are a baddie jamezelle xD
Very informative read, thanks bftb0!
I spent some time tonight fooling around with RomManager (v3.0.0.7) and ClockworkMod (v2.5.0.1 for the Eris). Sort of an eye-opener, actually.
The way it works is that it is actually NEVER "FLASHES" ANYTHING TO THE RECOVERY PARTITION. Instead, when you first tap on the menu item to "flash the recovery", what ROM Manager does is identify your handset type, and then downloads some files to
/sdcard/clockworkmod, e.g.:
/sdcard/clockworkmod:
----rwxr-x 1 system sdcard_r 829658 Jan 17 02:23 recovery-update.zip
/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries:
----rwxr-x 1 system sdcard_r 829658 Jan 17 00:56 recovery-clockwork-2.5.0.1-desirec.zip
/sdcard/clockworkmod/download/rommanager.appspot.com:
d---rwxr-x 2 system sdcard_r 4096 Jan 17 02:23 manifests
/sdcard/clockworkmod/download/rommanager.appspot.com/manifests:
----rwxr-x 1 system sdcard_r 11492 Jan 17 02:23 devices.js
Note that "recovery-update.zip" and "recovery-clockwork-2.5.0.1-desirec.zip" are the same size - less than 1 MB. In fact, they are identical. It is a signed update package - but too small to even contain an Android kernel.
Here's how ROM Manager works: when you press the button "Reboot into Recovery", what actually takes place is this:
- Rom Manager copies "recovery-update.zip" into /cache/update.zip, and then places the following command into /cache/recovery/command
Code:
"/sbin/recovery" "--update_package=CACHE:update.zip"
and then executes a "reboot recovery" command.
The next thing that happens is that whatever Custom Recovery that IS ALREADY FLASHED to your recovery partition on the phone boots up, and immediately begins to process the /cache/update.zip file
Here's the $64,000 observation:
This update.zip modifies NOTHING IN FLASH MEMORY - IT ONLY MODIFIES THE RAMDISK OF THE BOOTED RECOVERY ALREADY PRESENT.
Towards the end of the updater-script, it kills off the old /sbin/recovery and /sbin/adbd processes; but since these processes are defined as services, they get restarted automatically, using the new "ClockworkMod" version of these program files. Voila! The ClockworkMod recovery menus pop up.
There are two important observations that arise from this analysis:
- It does not have it's own kernel - it uses the kernel of whatever was already present in the recovery partition boot
- To get ClockworkMod to be cold-bootable, you need to COMBINE IT WITH A KERNEL AND BOOTSCRIPTS FROM SOMEPLACE ELSE - but WHERE exactly?
Now, I don't know if ROM Manager formerly worked in a different fashion - but the point is fairly obvious: if you wanted to provide a rooting method which installs "ClockworkMod" as a recovery - well then, you would need to combine the minimal components of "ClockworkMod" (mostly just the /sbin/recovery program !) with someone else's bootable recovery. And you could not use an HTC stock recovery - because then koush's "update.zip" files would have needed to be signed by HTC in order to get processed.
If you accept the hypothesis that the so-called "Clockwork" brickings have been due to a bug in the kernel MTD driver - and nobody ever seems to see those bugs happening with Amon_RA v1.6.2 - then the real problem comes from a kernel which is was kanged into a flashable "Clockwork Mod" recovery by a third party - not koush.
Who is it then - the unrevoked team? Someone else? What kernel is it?
As I recall, nearly every one of the brickings that have been reported here have been folks that got their rooting instructions from outside the XDA Eris community.
Bottom line - it's starting to look like the problem is not really due to Clockwork - its a problem kernel from unknown origins.
Perhaps Rom Manager did not always work this way on the Eris - but the way it works now is that if you install it after already having Amon_RA in the recovery partition, if you cold-boot (Vol-up+End or via HBOOT), what will come up is Amon_RA, not Clockwork.
So - if you can cold-start your phone into recovery, and up pops a ClockworkMod menu instead of a Amon_RA menu - how did you root your phone originally?
bftb0
(sorry if this post is a bit of a ramble - it's pretty late/early)
When I 'cold boot' I get the Clockwork V2.5.0.1 screen.
I rooted originally the day root was discovered here at XDA. I originally loaded Amon. Somewhere in the last year, I may have clicked the 'install Clockwork mod' at the top of ROM Manager, but I don't think I did.
I don't know if this helps, but I found your post interesting.
meanm50 said:
When I 'cold boot' I get the Clockwork V2.5.0.1 screen.
I rooted originally the day root was discovered here at XDA. I originally loaded Amon. Somewhere in the last year, I may have clicked the 'install Clockwork mod' at the top of ROM Manager, but I don't think I did.
I don't know if this helps, but I found your post interesting.
Click to expand...
Click to collapse
Huh.
If you do that, and then fire up an adb session, what kernel string does
Code:
adb shell uname -a
report?
When I click "Flash ClockworkMod Recovery", all it does is ask me to verify the phone model ("Droid Eris (CDMA)"), requests root (SuperUser), goes to the Internet and downloads stuff, and then pops up a message on the screen saying "Successfully downloaded Clockworkmod Recovery!" If I shut down the phone normally and then cold-boot the recovery afterward, what is there is Amon_RA - not clockwork.
Hmmm. Just used it to perform a ROM backup**. For this operation, the same thing happens - Amon_RA comes up first, followed by chaining to ClockworkMod and then the backup starts happening. I note that it also backs up the recovery partition - maybe it only modifies the recovery partition when it is installing a new ROM?
Hmmm (part 2). Just wiped and flashed a clean ROM using Clockwork. Cold start into recovery afterward gives me Amon_RA, not Clockwork.
Maybe koush has changed the basic methodology somehow. I have to say, the way I currently am experiencing it makes a great deal of sense - it means that koush does not need to be in the kernel-making/kernel-collecting business in order to support ROM Manager on a new handset.
Can anyone with a more long-term exposure to Rom Manager/ClockworkMod (on the Eris) shed some light on this?
bftb0
** Interesting side note: CWM backup now backs up (and I presume restores) /sdcard/.android_secure; also, a "wipe" operation will attempt to wipe any SD card ext partition if it is found.
I will adb when I get home...my work comp doesn't have the required programs installed...
bftb0 said:
** Interesting side note: CWM backup now backs up (and I presume restores) /sdcard/.android_secure; also, a "wipe" operation will attempt to wipe any SD card ext partition if it is found.
Click to expand...
Click to collapse
Also the /cache partition.
bftb0 said:
Huh.
If you do that, and then fire up an adb session, what kernel string does
Code:
adb shell uname -a
report?
Click to expand...
Click to collapse
Linux localhost 2.6.29-DecaFuctCFS-dirty-c6271491
meanm50 said:
Linux localhost 2.6.29-DecaFuctCFS-dirty-c6271491
Click to expand...
Click to collapse
Sorry - I meant adb with your recovery booted, not the normal OS. (The above must be from your regular OS right?)
I understand there's a tips and tricks thread that explains things in more detail but how does somebody go from just getting the phone to installing, or even understanding, things like obsidian, onyx, morphing and learning what the basic functions of such programs are.
The question I currently have is concerning flashing custom roms. In the tips & tricks thread, it talks of froyo builds (ex: bionix & frankin-twiz). What is it exactly? From what I understand, it sounds like a mini os that you install onto your device which helps in applying different functions to it, which makes custom roms possible.
I'm currently trying to get http://forum.xda-developers.com/showthread.php?t=845530 to work on my vibrant. Can anybody help a newbie out?
VibrantUser1 said:
I understand there's a tips and tricks thread that explains things in more detail but how does somebody go from just getting the phone to installing, or even understanding, things like obsidian, onyx, morphing and learning what the basic functions of such programs are.
The question I currently have is concerning flashing custom roms. In the tips & tricks thread, it talks of froyo builds (ex: bionix & frankin-twiz). What is it exactly? From what I understand, it sounds like a mini os that you install onto your device which helps in applying different functions to it, which makes custom roms possible.
I'm currently trying to get http://forum.xda-developers.com/showthread.php?t=845530 to work on my vibrant. Can anybody help a newbie out?
Click to expand...
Click to collapse
the link you posted is just to a theme.
to get the theme to work you'll need to be running obsidian first.
so lets see, the easiest way to explain the different versions 2.2, 2.1 1.6, 1.5 and so forth is this...
its pretty much like going from windows 95 to 98 to 2000 to xp to vista and so forth.
our vibrants come with android 2.1, 2.2 is the next version of the os to come out (basicaly like moving from vista to windows 7)
the different roms like obsidian and Macnut and such are just names that the developers gave their roms.
what happens is a developer starts out with a version of android (in the case of Macnut and Obsidian this is 2.2)
and then they add their own modified tweaks and such to it.
and so in the end they get Obsidian which is a modified 2.2
or Macnut which is also a modified 2.2
they differ a bit though as Obsidian is based almost totaly on a leaked version of 2.2 for the US vibrant, where Macnut is based alot on the 19000 version of 2.2 for the european phones.
so when choosing a rom just choose the base you want first: 2.1 or 2.2
then look through the tweaks on a few roms and read some of the thread for that rom untill you get a feel for what makes it unique
you can also just experiment by flashing a rom for a day or so and then switching to a new one untill you find one you like.
Morphing is a way to apply a theme to a rom, this does not generaly change functionality at all, it only changes apearance.
alot of themes are either morphs (you install them using metamorph, which is an app from the market)
or they also come in zip format (which are installed by flashing from recovery)
for the theme you posted you will need to flash obsidian, and then flash the zip for the theme afterwards.
have you rooted your device yet?
thats the place to start, if you need help just pm me or repost here and I'll do what I can.
also, there is a "newbie's guide":
http://forum.xda-developers.com/showthread.php?t=732458
nearblack said:
also, there is a "newbie's guide":
http://forum.xda-developers.com/showthread.php?t=732458
Click to expand...
Click to collapse
lol true true
Before you even want to start with anything, you have to learn what 'rooting' your phone means.
Without root, you won't be able to do any of the above. You might be able to download the programs necessary, but you won't be able to use them.
For ex. Titanium Backup, ROM Manager, etc.
We use ROM Manager to install different ROMs on our phones.
Much to read, my young grasshopper.
OP, I made the Tips/Tricks sticky... would you PM be exactly what you think it lacks? I want to make sure it is applicable to everyone... I thought it was straight-forward, perhaps not.
my phone is rooted. So how do I go about flashing obsidian?
I thought roms were the same as themes? What's the difference?
And just to clarify I understand the tips and tricks thread is sort of the newbies guide but even then theres a lot of terminology that a new user wouldn't understand. I just wanted some basic information that would allow me to transition into the tips and tricks thread more easily.
I appreciate the responses so far
Have you download Rom Manager from the Market? If not, do so.
Then follow the instructions (in the sticky) to flash the recovery (it's the top of the list when you open Rom Manager).
Assuming you did that, you can reboot into recovery, make a backup of your system.. something you can always come back to (a timestamp of your system at that moment).
Download the ROM you want, put it on your internal memory (sdcard/....) NOT in a folder.
Go to Clockwork recovery, choose to insall a zip from sd card... select the name of the ROM and then click Yes to install it.
It will run it's course, then you can just reboot when done.
The first bootup will take a long time (10 minutes probably)... let it boot.... leave your phone alone for like 10 or so minutes after bootup (suggested by Team Whiskey, I never really do this).
It's that easy.
Think of a ROM as an OS... the developers take Froyo (2.2) or Eclair (2.1) and make a lot of tweaks, remove things, add things... basically anything to enhance the user experience.
THEMES are something you flash over a custom ROM... it can change the icons, graphics, notification bar, etc... they are cosmetic. You see in my signature I have Axura 2.0.3 (amazing rom and there is a newer version out) and then I have BlackFroyo (which is the theme) on top of the ROM to change the look of things. Axura has a steel looking notification bar, I much prefer black (hence the theme I chose).
The ONE thing that can be confusing... if you make a backup right now (you have stock eclair), if you flash a froyo rom... you would need to flash either the stock eclair kernel (the download link is also in the sticky) to restore your nandoid backup.... OR, you could just flash another ROM that has a kernel (most do) and you would be good to go too.
And addition to this is to make sure your phone is NOT hardware locked.
To test it:
1) Take out battery from the phone and put it back in again
2) The USB cable plugged into the computer (not in the phone yet)
3) Push and hold down both of the Volume buttons at the same time
4) Plug in USB cable and it should take you into the Download mode.
If it does you are good to go. Just read some about Odin and Stock Android
If it isn't you need to make sure to flash JI6 to your phone (also Stock) onto your phone using Stock Manager. That should fix your hardware locked. Go over the above steps to make sure that is the case.
At this point, I have rooted my device and downloaded rom manager.I believe I have backed up everything after following the directions and I do have the blackfroyo.zip on my sd card and for some reason it won't "go" (although I'm sure there's a step I am missing here, something with obsidian) so that wasn't much of a surprise.
Edit: I noticed I tried to use a theme on there and not the obsidian "OS" (idiot) when I tried the backup thing with rom manager. Where can I download the most recent version of obsidian and/or is axura an acceptable alternative?
VibrantUser1 said:
Edit: I noticed I tried to use a theme on there and not the obsidian "OS" (idiot) when I tried the backup thing with rom manager. Where can I download the most recent version of obsidian and/or is axura an acceptable alternative?
Click to expand...
Click to collapse
Been working on updating the wiki. Please check out http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs for the different ROMs currently available.
^^ both are solid. I prefer Auxura *no touchwiz*.... download it from the development section. Place in on the internal (sdcard/ ) and flash it, reboot... I would let the phone chill for awhile then reboot again.... THEN if you want, start messing with the theme. You can see from my signature you and I are similar.
to the OP, I started a noob friendly guide in the Q&A section. Please let me know exactly what you want in there.
Here is a video guide, its kinda old but the principles are the same.
http://theunlockr.com/2010/08/02/how-to-load-a-custom-rom-on-the-samsung-captivate-vibrant/
I have been browsing around and reading on XDA since I got my G1 on release day. I have since upgraded to the MYT3G and now to the Vibrant. I have always used XDA as a source of information for rooting, etc. I don't post very often, but, I would like to throw props out to all the individuals in the thread, this is one of the few threads I have read on XDA that no one got flamed for being a "noob" and asking basic info, the information given was clear, accurate and very helpful. No one pointed to using the search function, everyone just gave good answers. AWESOME
I hope to see more threads like this in the future. Bravo and well done to all.
So I tried installing obsidian 5 and this is what happened. I first put the zip file on my sd card, I did all the necessary prerequisites (I think) using rom manager, flash recovery > vibrant yada yada yada and then pressed install rom from sd card and chose the obsidian zip file. Then the phone starts backing itself up and it finally reaches a point where it says (E: Can't open/sdcard/sd/obsidian_v5_beta.zip (no such file or directory) Installation aborted.
I then try to navigate to the file from the menu but whenever I click the sd file, it just exits, I think it says that no zip file is found or something but when I boot it up normally afterwards, the file is still there.
But the file is within the sd file . . . what am I doing wrong? I tried to fix permissions thinking it was that but no luck.
You probably need to move to the rom to the internal sd card. I thought you're able to add it to the external with the recent update but perhaps not
Sent from my GT-I9000 using XDA App
bellrb19 said:
You probably need to move to the rom to the internal sd card. I thought you're able to add it to the external with the recent update but perhaps not
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
the rom IS on the sd card, unless you mean the memory on the actual phone itself
ROMs go on the root of the internal memory (no folder)... drop it in sdcard/
Also, this was mentioned in Post 8, and in team whiskeys install guide. Please pay attention to details.
oh okay, this whole time I've been thinkin the sd card folder was the root folder. Well I have finally put obsidian with success and now I'm having a difficult time implementing http://forum.xda-developers.com/showthread.php?t=845530. I have downloaded the zip file but I don't understand what "flash it through clockwork recovery" means. It kinda sounds like I should use something in rom manager but I'm not sure, I have tried to reboot into recovery through rom manager with no luck.
I've also tried using metamorph but when i choose the blackfroyo.zip file, it says that the file is invalid and that the theme control file could be missing. Am I doing something wrong here as well?
Thanks for all your help so far, I really appreciate you taking time out of your busy life to help an individual with (what may be to you) simple problems
VibrantUser1 said:
oh okay, this whole time I've been thinkin the sd card folder was the root folder. Well I have finally put obsidian with success and now I'm having a difficult time implementing http://forum.xda-developers.com/showthread.php?t=845530. I have downloaded the zip file but I don't understand what "flash it through clockwork recovery" means. It kinda sounds like I should use something in rom manager but I'm not sure, I have tried to reboot into recovery through rom manager with no luck.
I've also tried using metamorph but when i choose the blackfroyo.zip file, it says that the file is invalid and that the theme control file could be missing. Am I doing something wrong here as well?
Thanks for all your help so far, I really appreciate you taking time out of your busy life to help an individual with (what may be to you) simple problems
Click to expand...
Click to collapse
From where you are now. Make sure the zip file is in the internal sd card, Open rom manager go to install rom from sd card then choose the that file then click ok and CW will do its thing. Also this is only for Obsidian v4.2 and Auxura 2.05. Good luck! Also you should make a nandroid back up first just in case.
i just wonder how you install the fixes thats beeing released here.
e.g videofix for DHD NAND (the stream shutting of)
i downloaded the fix, but dont know what to do with it?
also the fasterg GPS (you select Europe istead of something else, or something)
where do you install these, and how?
be so kind and make a little step by step instruction.
have a nice day everyone
normally the instructions are in the thread, you either install it from CWM or there might be a batch file you need to run to push the files
first thing is to read the thread where you got the fixes from
done that... doesent tell
i now people like to be comfortable, but please... everyone does not know how to fix some stuffs. espec. if its your first time
As far as I remember, you install updates the same way you'd install full rom - copy zip file to SD, then CWM, Ad Recovery and Install Zip from File
yeah, but i dont have CWM - does that matter?
have DHD NAND magldr 1.12
Sorry, but I've used only CWM ROMs - have no idea how updates for DAF should be done
if you mean this http://forum.xda-developers.com/showthread.php?t=959927 then it says you need CWM installed to be able to update it
also the faster gps is CWM installation only