Database Develop

how should i change a rom from 1 to another?

??????????????

tink-14 said:
??????????????
Click to expand...
Click to collapse
more info on how your doing it....
generally
Alt-w
Alt-s

i mean like is it as easy as wipe and ad flash new rom on

I actually really recommend the switchrom.sh script over in the development section on the forum. You just make a backup using the script, then flash the new one (alt-w, alt-s), and if you ever want to go back, restore the backup. It works a little nicer than nandroid in the fact that it keeps all your apps, as well as app data, so you don't have to set everything back up, log in, stuff like that.

tink-14 said:
i mean like is it as easy as wipe and ad flash new rom on
Click to expand...
Click to collapse
Generally. If you have your apps on an ext partition and your phone bootloops after flashing a new ROM, you may need to wipe it.
If you do get a bootloop, type this in the recovery console, then wipe and reflash the ROM.
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
rm -r /system/sd/*

If I have cyan's stable build and I just got the app from the market that can check for updates to his ROMs, can I just use that app to do everything? I am not familiar with how it works. Sounds like it is based off of JFs if anyone uses it.

Preparation b4 flashing between ROMS?

is there a guide anywhere on this or could someone give me a rough guide?
Do I need to format the partitions I made on my SD to run Hero, when flashing to another ROM that uses APPS2SD like Soulife's Rogers? I'm getting untold weird problems with this ROM - syncing etc.
Also, looks like APP2SD might not be working - 45MB free space is this right?
(For the record, all I did was a 'wipe' and then flash - which didn't seem to get rid of most apps)
Thanks!

You need to wipe your ext partition before switching roms.
That will get rid of the apps that stayed.

Hmm.. I digg my double post even though I only clicked once. Thx xda

can you wipe with the 'repair ext filesystems' option in cyanogens bootloader?
didn't seem to work for me. :?

with adb:
adb remount
adb shell
rm -r /system/sd/*
reboot recovery
then flash the update

thanks!
when I do
rm -r /system/sd/*
I get:
cannot remove '/system/sd/*': No such file or directory
So I guess there's nothing there anyway? ... looks like it when I 'ls' the directory anyway... confused as to why my apps keep on showing up after flashing ???

what a minute I adb'd in when it was in bootloader mode would that effect what I see?

Flash w/out sdcard?

May have been asked before, but I tried searching and didnt find much luck.
I think my SDCard slot finally gave up, it just will not be read (tried two different 8gb cards that both worked fine on the computer). On Cyan 4.2.9.1.
Anyway, is there a way to flash the phone without the sdcard? I was trying to think how that would be possible, but I think its not right?
Just looking for a quick def. answer so I can know if i need to go phone hunting . Or do something different , which would be much better.
Appreciate it .
Happy holidays btw

You should be able to using ADB, not sure the command lines for that. As well, you might want to try getting a can-o-air and blowing out the SD card slot on your phone.
Lastly, this is the wrong section, should of been posted in Q&A.

pjcforpres said:
You should be able to using ADB, not sure the command lines for that. As well, you might want to try getting a can-o-air and blowing out the SD card slot on your phone.
Lastly, this is the wrong section, should of been posted in Q&A.
Click to expand...
Click to collapse
I didnt really think of adb, yeah that might work. Maybe someone knows them?
Maybe
adb shell recovery flash location/zip ?
Tried the canned air, didnt change. Good thinking though.
And lastly, I did debate which place, but I was thinking I saw a utility here or I am looking for the command lines and thought maybe alittle more technical than a general question? It will fall shortly anyway (hopefully after the commands ) or get moved/deleted.

If someone nandroided, they could just send you their system.img and you could fastboot it onto the phone. Provided you have the engineering/danger SPL.

persiansown said:
If someone nandroided, they could just send you their system.img and you could fastboot it onto the phone. Provided you have the engineering/danger SPL.
Click to expand...
Click to collapse
Thats a pain, and I dont think there are many of those out there...
No adb commands? Ive been searching but it seems scarce
EDIT:
Ok I tried my idea anyway,
adb shell recovery flash update.zip
And it just hangs (no errors though)...probably missing something?

Are you able to warranty your phone for the bad SDCard Reader??
If so, I started this thread and came up with an answer, but it will bring you back to fully stock cupcake
http://forum.xda-developers.com/showthread.php?t=560254

Search for a webpage , how to root/flash/hack g1. It's has everything you need.
You need to go into fastboot
Fastboot update update.zip. somthing like that or do like the website shows 1 at a time.
There might be an adb for it, but I've never used it. Fastboot only option I believe.

bildo said:
Search for a webpage , how to root/flash/hack g1. It's has everything you need.
You need to go into fastboot
Fastboot update update.zip. somthing like that or do like the website shows 1 at a time.
There might be an adb for it, but I've never used it. Fastboot only option I believe.
Click to expand...
Click to collapse
That is the better answer, thanks for continuing. If you just left that first sentence I would have said re-read my problem, I cannot use my sdcard (the normal way rom is flashed).
As for the fastboot, I will look into that. I appreciate it, thanks.

Im getting
No android-info.txt
No android-product.txt
In the package when i try to do this command while in fastboot:
fastboot update update.zip
I found android-info in the update file from htc, but I cannot resign right now. Im also guessing it will still yell about the android-product.txt anyway, so any ideas where to get that file?

If all you're trying to do is flash a .img (system.img, userdata.img, recovery.img) and you have a developer, or hardspl, you can flash using fastboot.
Code:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
flashing an update.zip is only possible through recovery mode, but can still be accomplished using the /cache partition
Code:
adb push update.zip /cache
and you should be able to do the update from cache.

haykuro said:
flashing an update.zip is only possible through recovery mode, but can still be accomplished using the /cache partition
Code:
adb push update.zip /cache
and you should be able to do the update from cache.
Click to expand...
Click to collapse
Using you're SPL, is it still possible to place an update.zip into /cache with the partition table having been re-written??''
I'm assuming yes, since you jumped in and posted that method, I was just curious

jackslim said:
Using you're SPL, is it still possible to place an update.zip into /cache with the partition table having been re-written??''
I'm assuming yes, since you jumped in and posted that method, I was just curious
Click to expand...
Click to collapse
Well you're cache partition should have 30720K (about 30MB)
the last cyanogen rom was 37 MB =[
my other recommendation for you is to push the updates to your sdcard through your phone. (just re-read your post and noticed the SD card is functional in your phone)
Code:
adb push update.zip /sdcard/update.zip
then just proceed as usual.

@theslam08
Your signature say's your using the "Danger SPL" Judging by that you could reflash your spl from fastboot to the hard spl
Code:
fastboot flash hboot spl.bin
Then use the method described above by Haykuro pushing updates to /cache with adb

Thanks for the responses guys .
As for pushing to sdcard while in phone, thats where the problem remains. The sd reader IN the phone is busted it would seem as it just says no sd card found (cannot mount) with 3 different cards I tried (all working on the computer).
Ok so if I flash back the spl will I have more than 40mb free on the cache partition? Because yeh, the most recent update from CM is ~40mb, so it wont fit currently.
ANd once pushed to /cache, how would I go about doing the actual update? You said "you should be able to do the update from the cache part.), not sure how, just give the location?
console: flash update /cache/update.zip ?
Thank you.

theslam08 said:
Thanks for the responses guys .
As for pushing to sdcard while in phone, thats where the problem remains. The sd reader IN the phone is busted it would seem as it just says no sd card found (cannot mount) with 3 different cards I tried (all working on the computer).
Ok so if I flash back the spl will I have more than 40mb free on the cache partition? Because yeh, the most recent update from CM is ~40mb, so it wont fit currently.
ANd once pushed to /cache, how would I go about doing the actual update? You said "you should be able to do the update from the cache part.), not sure how, just give the location?
console: flash update /cache/update.zip ?
Thank you.
Click to expand...
Click to collapse
i forgot the exact command to force a boot-recovery and have it flash through cache (the traditional method)
but if your on cyanogen's recovery you can do
Code:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
this should mount cache into /sdcard, allowing you to flash.

haykuro said:
i forgot the exact command to force a boot-recovery and have it flash through cache (the traditional method)
but if your on cyanogen's recovery you can do
Code:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
this should mount cache into /sdcard, allowing you to flash.
Click to expand...
Click to collapse
Excellent, that seemed to be the trick (after going back to HSPL because yeah, I didnt have enough room with haykuro's). Though some bugs with that.
I got it to copy once after making that partition mount, and I was able to see the update file. I updated, and everything went well (even though I wondered how in the middle of the update it says formatting cache, yet it still worked).
Now, I went to put on a theme file and it says out of room. I hit 'update from sdcard' in recovery and it says E: No zip files found or something like that, just no files. So if it gets 'wiped' how is there no space? Is there a manual format I should do?
And I dont think this has happened to anyone yet, so thanks for going through this , im sure others down the road will find it helpful.

Not to get off-topic or picky about anything, but having the phone without an SD card being able to be read seems kind of pointless.
After all, you won't be able to run A2SD, or move the cache. The phone's going to run as if it was "stock."

akapoor said:
Not to get off-topic or picky about anything, but having the phone without an SD card being able to be read seems kind of pointless.
After all, you won't be able to run A2SD, or move the cache. The phone's going to run as if it was "stock."
Click to expand...
Click to collapse
Not being blunt but, thats the point. I have 'no' other choice right now, I cannot get a new phone for a while (and warranty is over, its a yr and 3 months since pur)
I obviously know I cannot use A2SD, so I need to get it to run 'stock', and thats proving to be a trick (stock but not). I almost have it, but cache doesnt seem to wipe on its own, which is the new problem. Once that is cleared, then I should be all set .

theslam08 said:
Not being blunt but, thats the point. I have 'no' other choice right now, I cannot get a new phone for a while (and warranty is over, its a yr and 3 months since pur)
I obviously know I cannot use A2SD, so I need to get it to run 'stock', and thats proving to be a trick (stock but not). I almost have it, but cache doesnt seem to wipe on its own, which is the new problem. Once that is cleared, then I should be all set .
Click to expand...
Click to collapse
Ah, okay - now it makes sense. I didn't understand the purpose at first.

What is the BEST way to TOTALLY WIPE my rooted G1?

I got a new phone and someone wants to buy my G1 locally and I want to totally wipe it and clear all of my user info. I'm leaving it rooted because it runs SO much better and I just can't bring myself to downgrade it. So if I wipe all cache's / factory reset / re-install ROM will that be good enough to erase my personal information from the phone? Specs are in my sig. TIA -Frank

So here's what I did...
- Deleted everything from SD card.
- Wiped all caches in Amon_Ra recovery.
- Flashed Super E ROM.
- Flashed Gapps.
- Re-Flashed Firerat boot patch.
Booted it up without a SIM card and it started up fine and looks like my user data is gone. What do you guys think...good to go?

Just because its to easy..
You wanted to know how to wipe the G1 fully....... SO you wiped it fully and asked if you did the right thing to fully wipe it.....?
BEst part... you wanted to wipe your info... so you did, its gone, then you ask if you did it right.....

Lol, just making sure
Sent from my SGH-T959 using XDA App

lbcoder said:
Guess what?
You didn't wipe ANYTHING except the first 128 kB of the cache and data partitions.
which means that ALL of your data can STILL BE RETRIEVED.
In recovery mode, mount cache and userdata partitions,
dd if=/dev/zero of=/data/zerofile; dd if=/dev/zero of=/cache/zerofile; sync; rm /data/zerofile /cache/zerofile; sync
Click to expand...
Click to collapse
Can it help if you get strange problems?

lbcoder said:
In recovery mode, mount cache and userdata partitions,
dd if=/dev/zero of=/data/zerofile; dd if=/dev/zero of=/cache/zerofile; sync; rm /data/zerofile /cache/zerofile; sync
Click to expand...
Click to collapse
Please could you spell this whole process out for me... how do u mount cache and userdata partitions in recovery mode etc.
Many Thanx

In recovery go to console. Type "mount -a" without the "s and press enter. Afterwards just type the whole line "dd ...." that lbcoder suggested. It will use the input /dev/null (basically an infinite source of consecutive zeros) and direct them to a file called "zerofile" on each partition, thus filling the whole partitions with zeros, overwriting any existing data.
If you want to delete your sdcard also, try this:
dd if=/dev/zero of=/sdcard/zerofile; dd if=/dev/zero of=/sd-ext/zerofile; sync; rm /sdcard/zerofile /sd-ext/zerofile; sync

thanks for the quick reply;]

lol oops, didnt realize who I was replying too lol

Too late now. It's gone. I am pretty sure this person will not be messing about with it.

mblaster said:
In recovery go to console. Type "mount -a" without the "s and press enter. Afterwards just type the whole line "dd ...." that lbcoder suggested. It will use the input /dev/null (basically an infinite source of consecutive zeros) and direct them to a file called "zerofile" on each partition, thus filling the whole partitions with zeros, overwriting any existing data.
Click to expand...
Click to collapse
You got a little brain-fart in there.... /dev/null is the black hole -- its where you SEND stuff that you don't want spewing out on the console. Nothing ever comes out of the black hole.
If you want to delete your sdcard also, try this:
dd if=/dev/zero of=/sdcard/zerofile; dd if=/dev/zero of=/sd-ext/zerofile; sync; rm /sdcard/zerofile /sd-ext/zerofile; sync
Click to expand...
Click to collapse
Not that this wouldn't work, but there's a better way to wipe the sdcard;
umount /dev/block/mmcblk0p1; dd if=/dev/zero of=/dev/block/mmcblk0
** you don't need to sync this since it writes to the device rather than to the filesystem.
*if there are multiple filesystems on the sdcard that may be mounted, you need to umount them all;
for PART in /dev/block/mmcblk*; do umount $PART; done

robuser007 said:
Can it help if you get strange problems?
Click to expand...
Click to collapse
Unlikely.
This is what you do to secure the device prior to selling or giving it to someone to whom you don't want to provide access to your data.

lbcoder said:
Unlikely.
This is what you do to secure the device prior to selling or giving it to someone to whom you don't want to provide access to your data.
Click to expand...
Click to collapse
I did know where it's meant for, my problems sees to be solved btw (using android 1.0 and back to latest cm6, I reflashed and erased everything).

I'm coming from the other end. I just bought a rooted phone "Super E 1.0.3". What can I do to remove previous owners google account?
Read this thread: forum.xda-developers.com/showthread.php?t=454405
But I don't have "Google Apps" under Manage Applications.
I do have things like "com.android.provision"
did a factory reset and his account is still there; along with his phone book. microSD card is not in the phone ATM, don't know if that matters.
EDIT:
Reboot with home and back button held down; wipe data selected from boot loader. Phone is now reset

lbcoder said:
Not that this wouldn't work, but there's a better way to wipe the sdcard;
umount /dev/block/mmcblk0p1; dd if=/dev/zero of=/dev/block/mmcblk0
** you don't need to sync this since it writes to the device rather than to the filesystem.
*if there are multiple filesystems on the sdcard that may be mounted, you need to umount them all;
for PART in /dev/block/mmcblk*; do umount $PART; done
Click to expand...
Click to collapse
Great suggestion. Thanks.
I would also suggest an improvement... use /dev/urandom instead of /dev/zero in each command! And repeat the process 2-3 times.
Since your flash memory is over-provisioned and employs wear-leveling, you are not writing to each physical page of memory if you run this once. A user who bypasses the filesystem and accesses the memory directly could easily spot your non-wiped sectors since the others contain all zeroes. Why help them spot the good stuff? And hopefully by running the wipe 2-3 times, you've upped the odds of touching each physical page at least once.

[Request] Stock(5.5.959) virgin system.img needed

We are trying to solve how to make our own fastboot system.img files from dd the system partition on a phone. If we can get a stock, 5.5.959, system.img that has never been mounted read/write, then we should be able to compare it to a fastboot system.img and figure out the exact difference. We already have a start of an idea, but it has to be perfect.
By virgin, no OTA patches, and no mounting read/write. You do have to root the phone, but on the temporary root. Put busybox in /data/tmp or somewhere. Next chmod 755 /data/tmp/busybox . Then do something like /data/tmp/busybox dd if=/dev/block/system of=/data/tmp/system.img . Finally copy /data/tmp/system.img off the phone and post it in this thread, please.
Busybox

We already have this file.
You have had it for days, in fact. You converted it to system.tar.gz for me.
Source: erismaster
Satisfies all of your requirements -- 5.5.959 (not OTA!), Verizon, temp ADB root, never mounting /system, dd with those arguments.

psouza4 said:
We already have this file.
You have had it for days, in fact. You converted it to system.tar.gz for me.
Source: erismaster
Satisfies all of your requirements -- 5.5.959 (not OTA!), Verizon, temp ADB root, never mounting /system, dd with those arguments.
Click to expand...
Click to collapse
Is there anyways to get my hands on this? My phone is purely in fastboot mode only and have no other real options to me, so if i could somehow flash this via fastboot, it may actually solve my issue.
(I cant even get into recovery)

edru said:
Is there anyways to get my hands on this? My phone is purely in fastboot mode only and have no other real options to me, so if i could somehow flash this via fastboot, it may actually solve my issue.
(I cant even get into recovery)
Click to expand...
Click to collapse
http://www.megaupload.com/?d=N2FPWHE6

I tried a fastboot flash of this system.img and it gave me a crc check failure.

You can't flash it, it's not signed. It's only useful for development.
Sent from my DROID3 using XDA App

Thanks very much!

No worries about finding a system.img that hasn't ever been mounted . . . we now have "Like a Virgin" images for repeated re-mounting and her pleasure.

Location please?

Wolfhere said:
Location please?
Click to expand...
Click to collapse
the thread is on the main page . . . . http://www.necrotania.com/Download/swu.zip