Related
I Now have the jf1.5 and for some reason It doesn't come with the amazonmp3 app. I need this, can some please post it so I can download the apk
mimic1011 said:
I Now have the jf1.5 and for some reason It doesn't come with the amazonmp3 app.
Click to expand...
Click to collapse
ADP builds of Android do not have TMobile apps such as Amazon MP3. This has been discussed ad nauseum if you had bothered to search.
mimic1011 said:
I need this, can some please post it so I can download the apk
Click to expand...
Click to collapse
It's a protected app. If you need it that bad that I suggest you go back to an RC build and do research before blindly flashing whatever build of Android is at the top of the forum.
mimic1011 said:
I Now have the jf1.5 and for some reason It doesn't come with the amazonmp3 app. I need this, can some please post it so I can download the apk
Click to expand...
Click to collapse
If you still have the RC firmware you can just unzip it copy the amazon apk out and install it into the adp the amazon works. I dont think anyone has the IM app working though
We should have an official rc update from tmobile real soon, which will have amazon mp3, myfavs, etc...
Just open a RC33 update.zip and extract the file from /system/app. Then you can install it by adb push.
Verified as working. I just added it to the app folder of Dudes 1.1 build and then did the update and it works just great. Purchased and downloaded a song to verify.
Here it Is
http://droiddeveloper.com/com.amazon.mp3.zip
enjoy it works for me...
Really Bad,
In Germany it cannot charge my creditcard... It has enough money on it.
I have the dude's 1.5 version, and cant seem to get it running. It forces closed upon trying to open. Any thought? It is saved to my SD in the app folder.
TIA
Read my guide
http://forum.xda-developers.com/showthread.php?p=3763025
TY SolemnWishing, this is how I got the app on my SD card to begin with - yours is a very helpful thread for a n00b like me. Unfortunately, I was never able to get the app to open. I am not sure how I could have messed it up - pretty simple, I navigate to the app folder on my SD and click the apk file which proceeds to install Amazon MP3. No go.
If you have any ideas on what the problem might be I would appreciate the input.
Thanks again for your great tutorial
Hmm... I assume you deleted the .zip and renamed it to .apk, what firmware are you using?
I am using firmware 1.5. Yes I renamed to apk. I wants to work, just force closes before it fully loads. I also have this problem with oi music player. It used to work, now no longer loads. I wonder if my SD card is the problem. It is 8 gb, but I am sure only like a class 2 card.
Strange. I have JF 1.5 and installed the Amazon app the normal way for any app on the G1 and have rebooted several times. The app still works. I thought if you did not push the app to the G1 it would need to be reinstalled each time you reboot the device?
Well, I am pretty positive it was my SD card - after writing my post this morning I pulled the SD card and have not been anble to get the phone back since. This thread pretty accuratly describes what is going on...long story short, i think I fried my SD card and as a result am stuck on Splash 2. I have wiped several times...
http://forum.xda-developers.com/showthread.php?t=516874
uggg...all for mp3's!!!! any thoughts and lots of luck would be appreciated.
K
Ahh I did the same thing. Here is what you need to do, you will need to force format it. Windows will NOT detect the card, and it may even freeze your computer. Put the phone into another device, such as a palm pilot or another cell phone and format it from there. It shouldn't take very long, and when it is completed, it will likely say the memory card only has 5Kb or so of memory on it. NOW insert the card into your computer and reformat it into a FAT32 format (+Ex2 for apps to SD) and you should be good! Of course, you will need to reload all your files though. That will fix your SD card. As for your phone... you will need to completely reflash a new firmware onto it, as right now starting up your phone is looking for items on your SD card which it may need, which no longer exist.
edit: if that doesn't work, completely start from the beginning by flashing the dreamimg.nbh file for rooting.
I was able to reformat the SD card, lost all my backups of course, and had to reflash dreaming.nbh and start from scratch. No biggy, at least i still have my phone.
thanks for all the tips...once i get my card re-partioned, I will try the Amazon.apk again.
K
I got it to load - thanks for all your help.
K
No problem at all, glad I could help.
0. Make sure phone is hard-spl first
1. Make sure SD card is formatted with fat-32
2. rename the image file (ruu_signed.nbh) to rhodimg.nbh, then copy that to the ROOT OF THE MICRO SD CARD, Insert card into phone
3. Set your phone in bootloader (Hold the "volume down" and hold the power on button until you see the tri-color screen.
4. Then follow the on-screen instruction
5. (OPTIONAL) -after flash, make sure to hardreset (pull battery, insert battery then hold green and red PHONE buttons (send/end) and hold powerbutton) follow onscreen instruction.
thanks for the info
I've tried the above and somehow it won't work on my TP2, it stays at "Serial" text in the white box, I'm assuming it already went past the SD slot then? Checking for the image.
I have the Energy rom loaded on the SD card, named as explained in the first post in this topic, it is placed in the root of the SD card, no folders or other files exist on that card. I removed the SIM card from the phone just to be sure. Is there anything I am missing, or is there anyone else who actually used this method to flash his or her device?
Info:
SPL: OliNex 0.85
ROM: |RHOD|6.5|ROM|WWE| ★ EnergyROM "Warhawk" (23016) ★ | Built Aug 21 |Manila 2.5 / 2.1|
SD Card: 4GB MicroSDHC (No brand on card, supplied with the branded T-Mo TP2 (Vario V)
Formatted: fat-32
Thanks
The nbh file needs to be in capital letters! RHODIMG.nbh
And step 5 isnt to be done until the "Tap screen to set up device" screen!
Just reset when your phone says Update successful!
And done, name changed to the correct format. No luck. Reformatting the card now to see if that changes anything. Update in a few.
And that too didn't work sadly. Either someone here notices I'm doing something wrong, or I'll just wait till I get near a machine natively running Windows Running Mac OS here so can't run the executable, and read that it's not quite a good idea to flash it from a virtual OS.
PositiveCreep said:
And done, name changed to the correct format. No luck. Reformatting the card now to see if that changes anything. Update in a few.
And that too didn't work sadly. Either someone here notices I'm doing something wrong, or I'll just wait till I get near a machine natively running Windows Running Mac OS here so can't run the executable, and read that it's not quite a good idea to flash it from a virtual OS.
Click to expand...
Click to collapse
You will want to partition your card so the nbh image is in a partion of at the largest 1G, anything larger makes it hard for the phone to find and read the nbh file! I have a 1G card just for flashing and it works perfect! And it also may be the mac, they never play nice with windows!
It's not the mac screwing it up in this case as I am using a virtual Windows OS to work on the card. (MacOS leaves some folders on the card that I don't want on it)
Will try partitioning the card, cheers. I'll update when I know more. ANd thanks for the help ^_^
Update:
Partioned the MicroSD card to 0.5GB, no change sadly.
thanks for information
Ok, SD update worked now, however, step 5 won't go (Oh crap...) Have the grey screen with "Update Complete" and "UPDATE SUCCESS" However, it won't do anything if I hold down Send/End/Power at the same time for over 10 seconds. How long should that take normally? What's my best option right now? Can't see any other than to unplug the phone and take out the battary, however, will this brick it?
PositiveCreep said:
Ok, SD update worked now, however, step 5 won't go (Oh crap...) Have the grey screen with "Update Complete" and "UPDATE SUCCESS" However, it won't do anything if I hold down Send/End/Power at the same time for over 10 seconds. How long should that take normally? What's my best option right now? Can't see any other than to unplug the phone and take out the battary, however, will this brick it?
Click to expand...
Click to collapse
When is says "UPDATE SUCCESS", just rest with the stylus.
Dave
Thanks for the swift reply! Done it, it's booting up as I am typing this. Didn't quite have the guts to just do that without having read I could when flashing from SD. (Was unsure how the device would react to soft reset then a first booth with the SD present etc)
Anyways, rambling. Thanks!
these post are telling me how to flash while the rom is already on the phone, but i'm missing the step on how to get the rom file on the phone in order to move it to the sd card.......... how do i get the file to the phone? do i put it onto the phone from the computer or do i go to my browser on my phone and download it from there to the phone
htctpII said:
these post are telling me how to flash while the rom is already on the phone, but i'm missing the step on how to get the rom file on the phone in order to move it to the sd card.......... how do i get the file to the phone? do i put it onto the phone from the computer or do i go to my browser on my phone and download it from there to the phone
Click to expand...
Click to collapse
Everything you need to know is HERE. I really suggest you fully read the instructions so you avoid bricking your phone by mistake.
In re: making sure you're hardspl'd first, does that still apply if you're flashing an official ROM? Or just for user cooked ROMs?
I'm about to update my Verizon TP2 with the newly released official 6.5 from verizon. I'm not hard spl'd, and honestly, know very little about that particular modification.
not for official
I dont think you have to be hard SPL'd for an official ROM. I think everything is included in the ROM package. (at least for T-Mobile it is)
btw the .nbh does not have to be named in all capitals. I have personally done it both ways with no problems at all. RHODIMG.nbh works just as well as rhodimg.nbh
kwambewright said:
I dont think you have to be hard SPL'd for an official ROM. I think everything is included in the ROM package. (at least for T-Mobile it is)
Click to expand...
Click to collapse
Thanks for the quick response!
Sadly, the way the install file is set up to work, I can't get to the nbh file. It insists on installing that via an active sync connection. I was hoping it would extract from the exe and schedule it for active sync installation, then I could hunt down the ROM, copy it to my SD card, and run it from there.
fortunz said:
Thanks for the quick response!
Sadly, the way the install file is set up to work, I can't get to the nbh file. It insists on installing that via an active sync connection. I was hoping it would extract from the exe and schedule it for active sync installation, then I could hunt down the ROM, copy it to my SD card, and run it from there.
Click to expand...
Click to collapse
hmm.. sorry for kicking this post, but you can unpack the exe-file with winrar. just grab the biggest file you can find (RUU_signed.nbh, and rename it to rhodimg.nbh), copy it to your root-folder (fast way for accessing bootloader is to also copy the "EnterBootLoader.exe" -file to your SD-card, and to start that file after copying both the files). Now just enter the bootloader, and it works! (don't be scared when the screen goes black for a moment, and the bootloader has reloaded. It's meant to do that )
I still have a little question by the way: is it possible to flash the hardSPL this way? or should i rename it to something else?
No, Hard SPL needs to be done from the PC as it checks IMEI online and IP address. You only get 1 licence, can ask for more or purchase more licences, but it can't be done any other way...
ultramag69 said:
No, Hard SPL needs to be done from the PC as it checks IMEI online and IP address. You only get 1 licence, can ask for more or purchase more licences, but it can't be done any other way...
Click to expand...
Click to collapse
Yeah, it's a pity this has been done (though I understand why...)
My device cannot connect to PC anymore, so cannot use HSPL anymore!
InjecTioN said:
hmm.. sorry for kicking this post, but you can unpack the exe-file with winrar. just grab the biggest file you can find (RUU_signed.nbh, and rename it to rhodimg.nbh), copy it to your root-folder (fast way for accessing bootloader is to also copy the "EnterBootLoader.exe" -file to your SD-card, and to start that file after copying both the files). Now just enter the bootloader, and it works! (don't be scared when the screen goes black for a moment, and the bootloader has reloaded. It's meant to do that )
Click to expand...
Click to collapse
Much obliged. I've actually been scared off the official vzw 6.5 because of issues upgraders have reported, but someday I'll put that to use.
Bad day today. Why? Because this morning I decided to try out one of the Eclair roms before leaving for work. I flashed it, tried it and then looked at the time. After noticing that I had only 15 minutes before having to be at work I decided that it was time to lock up my computer and take off... but first... I need to restore back to a stable rom. So I restarted my phone and using switchrom I recieved an error of some kind. Not a big deal because anytime I flash a new rom I do a switchrom -s, bart backup AND nandroid+ext backup. Then everyday I use a bat script to automatically mount my sdcard and back it up to my pc just in case I need to format my card and restore everything later. Which brings me to the point of this thread. I was able to restore CM-4.2.8.1 but it was booting VERY slowly (about 15 minutes) and I noticed that it still said "Checking for errors" in the status bar. I left my phone on the charger and checked it later and it said that my sdcard was damaged. I have absolutely NO computer access and my phone is running WAAAYYYY to sluggish to use. So I just turned it off and put my sim in my old Tilt phone and used that for the day.
So... throughout the ENTIRE day I was going through Android withdrawls. I needed my G1. It was killing me.
So my question/idea is, is there a way to do a chkdsk on the fat partition of from the recovery menu or from terminal? I did a little searching and came up with something called dosfsck. And I looked in the /system/bin/ directory and saw something called fsck_msdos. Can we use this to repair the errors that the system finds on the sdcard? If the OS can scan and detect errors, then why can't we have an option to fix them? Instead of having to use a computer at home or the office.
Any thoughts? Thanks.
Binary100100 said:
I was no longer the Hero.I needed my hero. I needed to be rescued.Times were changing people changed, things got hard for me .
Any thoughts to rescue my savior ???
Click to expand...
Click to collapse
The thing is that is part of the windows OS, i know cause i use it to check for errors on my HDD or SD cards time-time. Im not sure if linux or distro or whatever its called has that feature avail.
Oh and i had that prob before where it was devastatingly sluggish.
Ace42 said:
The thing is that is part of the windows OS, i know cause i use it to check for errors on my HDD or SD cards time-time. Im not sure if linux or distro or whatever its called has that feature avail.
Oh and i had that prob before where it was devastatingly sluggish.
Click to expand...
Click to collapse
Uhhhh... is that a paraphrased version of what I said in the quote? LOL.
Here... I found this: http://linux.die.net/man/8/fsck.vfat
I don't see why it can't be implimented somehow into a recovery.img to avoid future problems. It'll basically be like e2fsck but for fat.
Binary100100 said:
Uhhhh... is that a paraphrased version of what I said in the quote? LOL.
Here... I found this: http://linux.die.net/man/8/fsck.vfat
I don't see why it can't be implimented somehow into a recovery.img to avoid future problems. It'll basically be like e2fsck but for fat.
Click to expand...
Click to collapse
Oops sorry about that, didnt think anyone would notice.
Maybe you should check that up with Amon_RA?
I usually use my SD reader to check for errors before i flash a rom.
Ace42 said:
Oops sorry about that, didnt think anyone would notice.
Maybe you should check that up with Amon_RA?
I usually use my SD reader to check for errors before i flash a rom.
Click to expand...
Click to collapse
Yeah I guess I'll do just that.
I did find this too:
http://www.netmite.com/android/mydroid/donut/external/dosfstools/doc/README.dosfsck
So it looks like someone had the idea already. I wonder why it's never been implemented.
Binary100100 said:
Yeah I guess I'll do just that.
I did find this too:
http://www.netmite.com/android/mydroid/donut/external/dosfstools/doc/README.dosfsck
So it looks like someone had the idea already. I wonder why it's never been implemented.
Click to expand...
Click to collapse
The fat32 probably does get corrupted, sometimes i get the sd isnt inserted error.
Ace42 said:
The fat32 probably does get corrupted, sometimes i get the sd isnt inserted error.
Click to expand...
Click to collapse
I never get that but whatever is wrong with my sdcard it must be major because my pc is still trying to recover it after an hour later.
Binary100100 said:
I never get that but whatever is wrong with my sdcard it must be major because my pc is still trying to recover it after an hour later.
Click to expand...
Click to collapse
Copy the files to your pc, then erase the partition via console.Then do the error check again. I think its having trouble since you have a lot of files on your sd that must be zip or maybe you have a .img
Ace42 said:
Copy the files to your pc, then erase the partition via console.Then do the error check again. I think its having trouble since you have a lot of files on your sd that must be zip or maybe you have a .img
Click to expand...
Click to collapse
I think it was Vista. I never should have used the error check option in the disk properties menu. I just tried it again using dos (chkdsk f: /R) so it actually tells me what it's doing. The error checking tool in vista is just like the defrag tool. You have absolutely no idea what's going on or how much longer it's going to take. Sucks.
Binary100100 said:
I think it was Vista. I never should have used the error check option in the disk properties menu. I just tried it again using dos (chkdsk f: /R) so it actually tells me what it's doing. The error checking tool in vista is just like the defrag tool. You have absolutely no idea what's going on or how much longer it's going to take. Sucks.
Click to expand...
Click to collapse
I upgraded to 7
But i did like vista because of the HW support and eye-candy. I do wonder what its checking while it does that though.
I'm no longer keeping up with NAND on the vogue. So if anyone would like to keep me informed and email me or post me on any changes with NAND, ill be happy to add the news on the first post. The lock up issue with NAND has been fixed!
This is simply for any noobs or others who are having issues with Android and NAND.
IMPORTANT!!!
FOR VOGUE USERS ONLY
I am not responsible for any bricked or messed up devices. By continuing you are agreeing to my simple rule.
MY SIMPLE RULE: I owe you nothing.
I will help you through the way though if you bricked or need any sort of help.
How-to Video up NOW!!!
http://www.youtube.com/watch?v=3gTkJkOc7m4
First off, What is NAND?
To keep it simple...its your phones internal memory. Up untill recently we (Vogue Users) had to run Android off our SD cards using HARET. But thats another story.
What are the benefits of running from NAND? (based on what I have seen)
-Runs faster
-Longer Battery life
-faster boot up
-can be faster to put together.
-Easier to connect your vogue with android to your pc and sync
-Much more convenient.
So how do I start?
STEP1:
The Build
First you need to find a Build that is usable with NAND. Most Hero builds at this moment are not. Here are some links:
Donut 1.6
http://forum.xda-developers.com/showthread.php?t=591104
Hero
http://forum.xda-developers.com/showthread.php?t=603028
Cupcake 1.5
Method 1 from http://forum.xda-developers.com/showthread.php?t=593786
DO NOT DOWNLOAD ANYTHING JUST YET! I WILL TELL YOU WHEN A GOOD TIME WOULD BE
You may want to consider reading the rest...
STEP2:
Base Files (Most builds will supply these)
For all builds (Except the Link in Cupcake "instructions are givin in the download.) you will need a basic set of base files. The link below contains the 3 basic empty files for all builds and Systems.
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/Androidstuff.rar
IF
You are using Hero make sure you download hero.user.conf too:
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/hero.user.conf
-create a new folder called conf
-and place hero.user.conf in your new folder.
STEP3:
Rootfs
After you have the Base files you will need a rootfs. Depending on your Build, you may need a different type then the one I am going to supply you. Most builds will supply you with one. This one is DZO's rootfs.
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/rootfs.img
STEP4:
Prepare
-You need to clean out your storage on your SD. Make sure you delete everything.
-Create a file called android on your desktop.
-Download the base files, unzip, open folder, and place all 3 in your android folder
-Download the rootfs and place them in your android folder. Make sure you either download DZO's or the one your Build provides.
-Download a System.img. When you download a System most likely it will have a different name such as system-hero-123.img. You need to rename it system. So it should look like system.img . Then place it in your android folder.
-If you are using Hero place your conf folder in your android folder.
-Depending on your Build (mostly Hero) you may also need a Data file. The build you select should supply one. Download it and place it in your Android Folder
STEP5
Placing
Open up your android folder of all your collected files and select all, copy, and paste into your empty SD card.
STEP6
Unlocking
If you have never flashed a ROM before than you don't have HardSPL installed. So unlock your phone with...
http://forum.ppcgeeks.com/showthread.php?t=20370
Make sure you follow the forums directions.
STEP7
Method
Method1: The way I do it.
Download ROMUpdateUtility.rar
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/ROMUpdateUtility.rar
Extract to a newfolder
Download a kernel with your screen size
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Don't know your screen size...check this out
http://forum.xda-developers.com/showthread.php?t=544906
After you have have gotten the kernel:
rename it to RUU_signed and place it in the ROMUpdateUtility folder you created.
NOW you need to plug your phone into your computer. Establish active sync. And run ROMUpdateUtility.
-Follow the Instructions on the screen.
Method 2 and 3 can be found here:
http://forum.xda-developers.com/showthread.php?t=593786
This also shows my method...but a little less detail. You can also find many other helpful things there.
If you fail OR think your bricked your phone.
You will need to download one of these depending on your carrier...Make sure you download the shipped gps rom. (If you are Verizon skip down)
http://forum.ppcgeeks.com/showthread.php?p=191607
Than you will put your phone in boot mode. Hold the Camera and Power button. While holding both of them...get a pen or something small and hit the little restart button on the bottom of your phone. You may have to hold it for like a second.
-you will see three color bars on your phone
-plug your phone into your computer
-run the backup
After your phone is all back to normal. Make sure you run internet explore on your phone. It will enable you to get data.
For Verizon follow the instructions here.
http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS
That is about it. I'm sure I forgot some stuff and will add on to this. Make sure you donate to the Devs for all their hard work.
DZO
http://forum.xda-developers.com/showthread.php?t=593786
jamezelle
http://forum.xda-developers.com/showthread.php?t=603028
plemen
http://forum.xda-developers.com/showthread.php?t=591104
vilord
http://forum.xda-developers.com/showthread.php?t=523692
They deserve it.
thank you this was very helpful
inphin1ty said:
thank you this was very helpful
Click to expand...
Click to collapse
No problem...
yea here is the md5sum: 9b08971e7f23619b6a9a4db9d52d857a
jamezelle said:
yea here is the md5sum: 9b08971e7f23619b6a9a4db9d52d857a
Click to expand...
Click to collapse
Whats that?
staud8469 said:
What are the benefits of running from NAND? (based on what I have seen)
1 Runs faster
2 Longer Battery life
3 faster boot up
4 can be faster to put together.
5 Easier to connect your vogue with android to your pc and sync
6 Much more convenient.
Click to expand...
Click to collapse
great thread. I've run both from nand and sdcard. i have not messed with ext2 on the sdcard.
I agree with 3 for sure. I would also add that there is a deep gratification in wiping win mo off the sdcard
6 is debatable, depends on which conveniences you want. changing lcd.density, changing resolution are all much faster running from the sdcard - no flashing or messing with build.prop, just edit default.txt and reboot (aside - if you have a non-sdhc card you can flash on the fly from the sdcard, but changing lcd.density still requires pulling and pushing files from the system, which is not as easy as changing the default.txt). also more convenient to back-up or revert to a data.img when running from sdcard. definitely booting straight into android is convenient, as is the new mass storage on boot method, as well as having a re-writable system (which you also have using ext2).
1 and 2, I honestly have not noted a significant difference in battery life. With a fast sdcard, I don't think there is a significant difference in speed either - dzo has said this in one of the non-vogue forums as well. i have not tried any sense builds from the sdcard though, and that's where you would notice the greatest difference in speed if there is any.
4 I agree with in general.
I think running from the nand is a huge advance, and great for everyone to try. but, running from the sdcard is still a decent way to use android. choosing between the two comes down to choosing which conveniences suit your usage style the most.
One last thing - please add vilord to your donate links (his google ion on vogue thread), he has been instrumental in developing the ril and advancing android on the vogue. srwalter also deserves mention for his reverse engineering of the libgps.so to bring gps first to cupcake and now to donut as well. jamezelle, plemen, mssmison, zenulator, enatefox, f00bar (no specific order) have all worked hard porting roms and working on things like compcache, swap, modem, etc, which has all been invaluable (zenulator and mssmison deserve special credit for spearheading the porting business). however the gruntwork of porting to the vogue has been done mainly by dzo who brought us the kernel and initial ril and now nand (he's just frickin amazing, he singlehandedly got the first functioning port to the vogue and others helped from there), then vilord who took the ril and really refined it. I guess suffice to say, there have been a lot of people involved along the way, thanks to all of them.
when i try to run android from both nand and haret i always get an error about not being able to mount sd card. does this mean i need to reformat the card? if so how do i do this?
Barogi44 said:
when i try to run android from both nand and haret i always get an error about not being able to mount sd card. does this mean i need to reformat the card? if so how do i do this?
Click to expand...
Click to collapse
When do you get this error? During linux kernel bootup?
Verizon users.
I just update a fix for Verizon users. Shows you how to get GPS too!
Also...there will be a video up soon. It seems that there are so many people having issues. So I will create a video from start to finish. Will be posted up late tonight/ tomorrow morning.
staud8469 said:
When do you get this error? During linux kernel bootup?
Click to expand...
Click to collapse
Yea.. i think i may need a new sd card. Can android boot from a 4gb card or is 2 the max?
Barogi44 said:
Yea.. i think i may need a new sd card. Can android boot from a 4gb card or is 2 the max?
Click to expand...
Click to collapse
i running with a 8gig PNY sdcard
it could theoretically run off of a 512, but you would be a little cramped on space
i guess android doesnt like some of them
so really it doesn't matter how big the card is? do they all have to be formatted to fat32?
Barogi44 said:
so really it doesn't matter how big the card is? do they all have to be formatted to fat32?
Click to expand...
Click to collapse
short answer, yes.
Hey guys...I will try my best to get that video up today. I am about to start recording it.
Am I correct in assuming that step 4-b is create a FOLDER name android on the desktop?
Can I delete those files from the SD when flashing is done?
THANK YOU for the N00B instruction, works great.
stopthebus said:
Am I correct in assuming that step 4-b is create a FOLDER name android on the desktop?
Can I delete those files from the SD when flashing is done?
THANK YOU for the N00B instruction, works great.
Click to expand...
Click to collapse
Yes that is correct, as for deleting the files...I would assume you could. But im not sure. Maybe they are still needed on boot. Never hurts to try though.
im not getting access to the internet after i flashed, am i suppose to edit anything?
im running the donut flash on my sprint vogue.
gigermunit said:
im not getting access to the internet after i flashed, am i suppose to edit anything?
im running the donut flash on my sprint vogue.
Click to expand...
Click to collapse
Wait...NVM you want data to work right?
If you are using donut...try to restart your phone one time. After it boots back up you should see a 3g symbol appear on the notification bar.
If that does not work...go to your apps and open modem. Click once on disconnect and then once more. Then click connect.
Tell me if that works...
Hello everybody,
I try to root my 1.6 G1 for many days now. Followed many more tutorials. TheUnlockr, YouTube, XDA-Dev and other Android-Forums.
The problem is an error message when I try to flash the 1.5 Update. Everytime it says "00028002 Not allow". Tried the flashing process with so many DREAIMG.nbh's from different websites. Tried the US and the UK Version but nothing, really nothing worked.
And now, after Google and all these tutorials didn't work, I ask you for help. I hope that i won't get stupid posts =)
Thanks in advance!
did you format to FAT32?
I really don't know. I normally use Mac OS X 10.6.2 and don't know how to format there. Under Windows 7 which I use with BootCamp I right-clicked the SD-Card and selected "format..." but then there is an error message too like "not found". I don't have an adapter for the microSD. Do you have any Tips for me?
i'm not sure about other ways to format (anyone, lend a hand please?) but i think you need it to be FAT32.
EDIT: disk utility. i think you can get it there. just backup beforehand.
I Googled for formatting under Macintosh. FAT works, but there's no option for FAT32... Really need help.
Could anyone post me the "best" files/tutorial for downgrading a german G1, please?
19SK91 said:
I Googled for formatting under Macintosh. FAT works, but there's no option for FAT32... Really need help.
Could anyone post me the "best" files/tutorial for downgrading a german G1, please?
Click to expand...
Click to collapse
Well read the edit in my post. Some say Disk Utility works for FAT32, some say it doesn't. Hmm, i don't have macintosh so i can't really try it ATM.
Disk Utility was what I tried. But I just have these options:
4 times "Mac OS X Extended" and "MS-DOS Dateisystem (FAT)". Don't think that this is right.
But do you have a link to a tutorial for rooting a german G1 at 1.6? Because the files I downloaded always had different sizes and I don't know which the right one is/was?
19SK91 said:
Disk Utility was what I tried. But I just have these options:
4 times "Mac OS X Extended" and "MS-DOS Dateisystem (FAT)". Don't think that this is right.
But do you have a link to a tutorial for rooting a german G1 at 1.6? Because the files I downloaded always had different sizes and I don't know which the right one is/was?
Click to expand...
Click to collapse
Fat32 might be a windows only format just like EXT is a linux only format, so you will need to find a program that can do it like paragon or have a friend format it on their computer.
I do have Windows but it always says that the SD card can't be found. Don't know why.
I connect the G1 to my MacBook and run Windows 7. I mount USB and choose the SD card in Windows. Then I right-click on it and say "format...". After that it seems that the G1 automatically dismounts the SD card so that Windows can't find it...
Edit: How does the G1 itself format the SD card?
Edit 2: After formatting G1 in Mac (MS-DOS (FAT)) it said that something's wrong with the SD card and Android wanted me to format it again. I did it but Windows doesn't find the SD card anymore -.-'
Edit 3: G1 also doesn't find the SD card anymore xD
Formatted the SD card to FAT32 but the problem doesn't disappear...
Will try it now with RC7 instead of RC29. Don't think that it'll work because I already tried this before but who cares...
Edit: RC7 also doensn't work. I tried to install the "signed-kila-ota-148830.de6a94ca" update too. But after a while it says "Installation aborted"... I really need help!!
19SK91 said:
Formatted the SD card to FAT32 but the problem doesn't disappear...
Will try it now with RC7 instead of RC29. Don't think that it'll work because I already tried this before but who cares...
Edit: RC7 also doensn't work. I tried to install the "signed-kila-ota-148830.de6a94ca" update too. But after a while it says "Installation aborted"... I really need help!!
Click to expand...
Click to collapse
Alright put your sd card back into your g1. Unmount it in settings, then format it from there. When it's done, plug your g1 back into your computer or use and sd card reader (Personally, I prefer the card reader.) I use a mac based laptop as well, but i put windows on it as a partition. (I needa play my games ) See if your computer detects it now. And what do you mean that the problem doesn't disappear? Wasn't your problem the fact that the card didn't format?
No, the original problem is/was, that I can't get back to 1.5. No matter what file I choose, this damn "00028... Not Allow" problem appears everytime.
19SK91 said:
Formatted the SD card to FAT32 but the problem doesn't disappear...
Will try it now with RC7 instead of RC29. Don't think that it'll work because I already tried this before but who cares...
Edit: RC7 also doensn't work. I tried to install the "signed-kila-ota-148830.de6a94ca" update too. But after a while it says "Installation aborted"... I really need help!!
Click to expand...
Click to collapse
Na bra... go ahead an try one more thing..
Macs by default automatically unzip files when downloaded from the internet.
So if this is the case, the file your downloading isn't in the correct format (atleast for the phone). You can even try re-zipping the file but its not gonna work. This happened to me, the only way to fix it is to change the Mac preferences to not automatically unzip/open/handle files downloaded. Its been so long I cant remember the right steps in order to do this. But Im pretty sure thats why you're getting hung up. If you have a Windows availible to you, try downloading it again on the PC and moving it to your SD and see if it works Oo. Or just change your Mac settings and redownload. This MIGHT be your problem.
On second though, this might not be your problem. But maybe worth a try.
19SK91 said:
Hello everybody,
I try to root my 1.6 G1 for many days now. Followed many more tutorials. TheUnlockr, YouTube, XDA-Dev and other Android-Forums.
The problem is an error message when I try to flash the 1.5 Update. Everytime it says "00028002 Not allow". Tried the flashing process with so many DREAIMG.nbh's from different websites. Tried the US and the UK Version but nothing, really nothing worked.
And now, after Google and all these tutorials didn't work, I ask you for help. I hope that i won't get stupid posts =)
Thanks in advance!
Click to expand...
Click to collapse
Looking at your info, I'm assuming you're using a German G1
If that's the case I'm pretty sure you have to use the goldcard method to downgrade your G1 then root.
I'm not 100% sure on this, but based on what you've already tried and the flag below your location and post count, it might be a good idea to read up on it and try another method.
Check this thread out for a little more detail
http://forum.xda-developers.com/showthread.php?t=485364
@nopotential: So, could you tell me how to change this in the settings? 'Cause I right-clicked on a .zip, chose "open with..." and said "The unarchiver". Then i said "always open with" but it doesn't work...
@jackslim: I do have Windows 7 and the MacBook Pro does have a SD card reader but I do not have an adapter... Is there any chance to do this without a WM Device (If this is also Windows 7 ^^)?!
@all: Does anybody have a good downgrading tutorial für GERMAN/EUROPEAN G1s that worked for him/her too? That would be really nice.
By the way: What time is it in the US now? Is it in the morning?!
I'm just piecing together bits of other information I've found on various posts, so this may or may not work. Since you'll be using a macbook you should be able to dd to the sdcard
The first thing you need to do is get the CID of your SD Card
You can do this with adb, if you need help setting up adb see here
After ADB is setup
*Make sure on your phone you go to settings -> applications -> development and make sure USB Debugging is checked
check that it is working by opening a terminal and using
Code:
adb devices (enter)
If you see a serial number it's working, if not refer back to the adb setup guide and check for what you may have missed. If you seen a serial number do the next step
Code:
adb shell (enter)
cat /sys/class/mmc_host/mmc1/mmc1:*/cid (enter)
Now you should have the CID of your SD Card (write it down exactly). If you know an easier way to get this info directly from your macbook, feel free to try it that way.
Once you have your CID, go to this website scroll to the bottom, enter your email and cid as directed to, then wait for the email with your goldcard img
Once you recieve your goldcard.img, on your mac open a terminal, go to the directory you saved the goldcard.img to and
Code:
dd if=goldcard.img of=/path/to/your/sdcard bs=384 (enter)
*Note: Change /path/to/your/sdcard to what it actually is
Now add DREAIMG.nbh to the SD Card, and reboot your phone into the bootloader Camera + Power **Cross Fingers While You Wait*** And hopefully it will work
I don't have a Mac, never even used a Mac. I'm just piecing bits of information from different posts in an attempt to assist you downgrade. Although none of these steps should cause any damage to your Macbook/PC/Phone/House/Leg/Car or grandchildren. Try these steps at your own risk
And inresponse to the current time in the US, it's approximately 11:10 am on the eastern coast
Whoa, thanks for this. I don't know how to show you how thankful I am in english ^^
At the moment I'm not able to try this 'cause I'm busy but I'll post the result of it =)
Thanks again.
Also see this post
It specifically says for a Dutch phone, but I think most continental G1's that are having the downgrade problem require the same method to fix it