yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] davil124:
having a little Issue installing the IME...can someone help in how to apply this feature ? i am changing the name to update...going to the recovery and applying the ALT + S command and it gives me a error and fails to apply the settings....am i doing it wrong ?! or there something that i need 2 do first ?
[G1 Android Development] :
If you're using a JF build: http://xdaforums.com/showthread.php?t=515840
[G1 Android Development] meww:
Worked perfectly, Thank You. And the guy who is having problem you must have messed up pretty bad. After I installed the new SPL the phone rebooted and took me in JF 1.43 recovery menu and I update my firmware.
[G1 Android Development] jaaronmoody:
yo!! the ime is not an update. do you know how to push an app via adb? if not STOP!!
[G1 Android Development] tubaking182:
i don't own an sdcard reader or adapter and i know i am a techy, and i am pretty sure many members here would agree. they aren't necessary when you know how to work in the console or use another phone/camera/mp3 player/whatever else can hold the card
[G1 Android Development] udontcdis:
thanks for the info.
[G1 Android Development] sir*mez:
I grew some and tried it on my phone!!!

well i grew some and i wanted to see if it would brick MY PHONE. i followed the directions and it worked. so i updated my spl but my girls phone is still bricked. theres nuthing i can do with it. no recovery, no fastboot adp and i cant even flash it to RC29, oh well back to t-mobile it goes!!!
[G1 Android Development] justanothercrowd:
If you flash a corrupt SPL it can brick the phone...be careful guys!
[G1 Android Development] sir*mez:
so then i just bricked my girls phone. but then i did it to mine and it worked perfectly.
[G1 Android Development] serialtoon:
Im sure you can recover that easily by re flashing a non corrupt spl. Also, the new SPL seems useless for us Apps2SD people...correct? I already see a ton of free space :-p
[G1 Android Development] sir*mez:
i cant flash anything on it. it wont pass the t-mobile g1 screen. i just called t-mo and they're replacing it. i also did this spl update on my phone and it worked so i dont know what happened with my girls phone...
[G1 Android Development] serialtoon:
I think you are worrying to much. Its almost impossible to brick this phone. Did you put in the spl, rename it to update and then hold home+power key till you get the recovery menu and press ALT+S to update?
[G1 Android Development] Chahk:
The new SPL works fine with Dude's 1.1a (after re-flash of Dudecake rom), even with apps on SD enabled. The IME is giving me force-closes though.
[G1 Android Development] sir*mez:
yes, i changed spl to update then reboot alt+s it updated and it even showed the arrow pointing to the chip. it rebooted and then it stood stuck on the t-mobile screen. i took out the battery, pressed the home button+power for 5 mins and nothing happened. i cant even go into power+camera. I cant do fastboot for adp. It just stays on the t-mobile g1 screen. no worries here if i can fix it but i cant in this instant.
[G1 Android Development] serialtoon:
Ahh ok. You are simply missing one little last step. Place the ROM you chose again on your phone. If you are using JFs 1.5 then update it again with no wipe to that. If you are using the dudes then update with no wipe to that...etc etc. Im assuming you are using JFs ADP 1.5 so here goes.

-Place JFs1.5ADP on sdcard

-rename it to update

-power off phone

-power on while holding Home+Power to boot into recovery

-Press ALT+S to re-update the OS onto the phone

-Press Home+POwer to turn off device and boot into your home again :-D
[G1 Android Development] sir*mez:
thats the thing i cant. i cant go into recovery. all the phone does when i hold home+power or camera+power is hang on the t-mobile g1 screen. i get no movement from that t-mobile g1 screen. if i could do the camera+power i would just start over with RC29 but i cant even do that. the phone has been on for an hour stuck on the t-mobile screen. i've also held the home+power for 5mins and nothing.
[G1 Android Development] nick8197:
Yea man I would just return it I dont understand why it is not working?

the file must have got corrupted somehow
[G1 Android Development] sir*mez:
yea i am, i just got off the phone with t-mo. but the funny thing is, i did the update to my phone and it worked. so i dont know what i did to her phone.
[G1 Android Development] Chahk:
Hope the couch is comfy ;)
[G1 Android Development] sir*mez:
She won't know till the mourning... lol
[G1 Android Development] speoples20:
Flashed the new SPL fine. No issues on Lucid JF1.5 A2SD.
[G1 Android Development] theslam08:
Flashed SPL here, went very well (feel bad for bad-luck dude up there...:confused:) [AMAZING WORK TO PORTER!!!! THANKS AWESOME!]

Though anyone having some issues with the new vk? I pushed it but after restarting the screen kinda got messed up at the bottom, then went fine. When trying the 'supposedly' new vk, it was still standard. Is it working fine with the normal adb installs for everyone?
[G1 Android Development] savethechicken:
he has already though all of the posts and attempts of help done all this. The problem is the SPL is the "bootloader" so if something goes wrong during the install of the bootloader you can't boot into anything it just hangs. This is why there is the two boots screen, i believe. There is no recovery there is not getting back into the bootloader (SPL) as it doesn't pass the first boot screen. This is really the only true way you can brick your phone. He is already on the right path for resolution...exchange.
[G1 Android Development] cigar3tte:
I'm having a problem, but not the same as Mez...

I installed SPL and can reach recovery console, but I've tried reflashing Haykuro, JF, and the Dude's and it still comes back stuck at the G1 screen.
[G1 Android Development] rwbarnes67:
Just completed and my phone is so freekin' fast now!
[G1 Android Development] savethechicken:
Have you Wiped the device? Mine did hang on the G1 screen for a bit longer than normal, but it did boot up correctly.
[G1 Android Development] cigar3tte:
It's back up now, but I think my problem was caused by a weird SD card. I think it booted right after I ejected the card. After phone is up, it won't read my card, but Windows sees it just fine.

I will try formatting the card and see it phone can see it again. Tomorrow though, I don't want to be up past 4am.
[G1 Android Development] AndroidAutobot:
Freakin sweet!! my available space changed from 8MB to 23MB! =) I followed the instructions laid down on page one and they worked like a charm w/ out incident.
[G1 Android Development] paulobrien:
Mine is bricked too - same problem as earlier in the thread, no ability to go into recovery image, holding down back and home to enter bootloader at startup doesn't work, stuck on G1 screen. :(

P
[G1 Android Development] MontAlbert:
right. that does it- being in australia and having bought my G1 on ebay i cant exactly ring up t-mob for a new 1. i am not going to take the risk..... at this stage that is! :D
[G1 Android Development] sir*mez:
I know what your going thru. I tried it on my girls phone and bricked it. Then tried it on my phone and it worked. I don't know what went wrong with my girls phone tho.
[G1 Android Development] _Trev_:
it'd be great if we could get an MD5 for the SPL. this would help prevent bricking issues.
[G1 Android Development] sir*mez:
Damn so far 2 bricked phones. Atleast I wasn't the only one.
[G1 Android Development] MontAlbert:
there is an md5 on haykuros google code page.
[G1 Android Development] yellowmegaman:
Haykuro!WE NEED UR HELP RIGHT NOW!i believed u since your first roms but right now phone is bricked!!!bootloader god damn it(((
[G1 Android Development] funbacon:
Someone said that their phone was brick. Please read this !!!!!!!!!!!!!

1. Download the SPL

2. Rename to update.zip

3. Update using this update.zip

4. Your phone will go to Tmobile screen (or blink android screen) and stuck here. You need put out your battery and your memory stick (sdcard)

5. NOW !!!!!!!!! Using a Card Reader remove old update.zip and copy the update.zip of your current FW

For and example : I use ADP1.5H, I want to use new SPL, I run SPL update, after that, I put out my sdcard and copy update.zip of ADP1.5H to my sdcard and go to step 6

6. Put your battery and sdcard into your phone

7. Run the update
[G1 Android Development] metallicant:
I think I flashed the SPL but maybe I didn't. Before I flashed I forgot to check what available internal memory was left.

How can I check and see if this has given me more memory or not and if this has been applied successfully or not?

All that it's saying for internal memory is 24mb. I can't quite remember if it was less then that or not before I flashed.
[G1 Android Development] andrews240:
@metallicant - Do you have ADB setup? If so, you can:

adb shell df

and you should get this if you were successful:

/dev: 49352K total
/sqlite_stmt_journals: 4096K total
/system: 92160K total
/data: 91904K total
/cache: 30720K total
[G1 Android Development] metallicant:
I'm lost. I just tried this in Terminal Emulator. Got the adb: permission denied
[G1 Android Development] baggus:
Just type "df" in Terminal Emulator.
[G1 Android Development] metallicant:
GOT IT!!! Thank you all..
[G1 Android Development] magicditto:
looks like i'm number 3

yes, i was rooted, on jf... tried the new spl, and kaput... no recovery, no bootloader, no adb, no fastboot... hopefully the tmobile booth opens soon...:(
[G1 Android Development] ChrisiMA:
Hi guys,

with this SPL, the German keyboard layout is switched off... how can I correct this? (Setting the Locale does not help, the hardware keyboard is switched to English... I need the German one...)

Greets
[G1 Android Development] metallicant:
I got this.....

$ df

/dev: 49356K total, 0K used, 49356K available (block size 4096)

/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)

/system: 92160K total, 55732K used, 36428K available (block size 4096)

/system/modules: 492K total, 492K used, 0K available (block size 4096)

/system/xbin: 3524K total, 3524K used, 0K available (block size 4096)

/data: 91904K total, 66696K used, 25208K available (block size 4096)

/cache: 30720K total, 1160K used, 29560K available (block size 4096)

/sdcard: 991664K total, 143872K used, 847792K available (block size 16384)

$
[G1 Android Development] jrherras:
I have 91mb /data and 84mb left from 69mb and I noticed it's faster when using this spl than hardspl. Anyone noticed or it's just my g1?
[G1 Android Development] DOHCtor:
I want to try this but the 3 bricked phones are scaring me.
[G1 Android Development] free-sidux:
indeed, I think the same. it would be nice, if the reason for the bricks would be clear.

@ mez: did you check the md5sum of the update.zip you applied? + did you apply the same file to both phones or were you downloading it for two times?
[G1 Android Development] bfreexxx:
I just flashed the new SPL and then Dude's 1.1a and it worked without incident. I'm NOT using A2SD and so far it seems all my apps and settings have been preserved.

I thought I should mention that after flashing the new SPL and rebooting, it went back into the Recovery Utility on it's own. I had to press Home+Back to reboot one more time before I got stuck at the boot screen.

Then, I flashed Cupcake and it worked flawlessly.

Is there some magic that happens during the reboot when it goes back into the Recovery Utility? Maybe pulling the battery out prematurely is causing the bricking? Anyway, just in case there is any confusion I thought the directions might be edited to let people know that the phone will reboot on it's own once. (Whether or not this is the case for everyone, I think it should be mentioned)
[G1 Android Development] metallicant:
Does this show the SPL installed and I have 24 megs of internal memory left?

Actually what do I look for that shows the SPL installed?
[G1 Android Development] speoples20:
Yes that could cause bricking if you don't let it finish flashing the new SPL. Wait till you reboot the second time from the recovery screen to reboot.

1. Rename new SPL as update.zip and place it on the root of the SD card.

2. Reboot phone into recovery and flash phone Alt+S

3. Reboot phone HOME + BACK to reboot.

4. Let phone reboot back into recovery mode and then HOME + BACK to reboot again and wait for phone to hang on G1 screen.

5. Pull battery and take out SD card. Then use SD card reader or some other means to put your current build back on root. Flash that build and should be good to go.
[G1 Android Development] matt_stang:
I have one little problem with the new IME... When you have touch input enabled with the new ime, the autocorrect for the hard keyboard gets disabled. Anyone know how to use the new ime but still have auto correct on the device keyboard? That's the only thing that is turning me away from the new IME
[G1 Android Development] rjlan82:
Welp, bricked my phone. Stuck at the Tmo screen, can't do a damn thing.

EDIT: That makes 4?
[G1 Android Development] jrherras:
take out your memcard put adp1.5/haykuro rom or whatever rom you're using then rename it to update.zip and alt+s on recovery that's it
[G1 Android Development] kylebrodeur:
I don't get sound feedback but that could be due to the Dude removing alot of system sounds.

But I don't get the autocorrect thing shown in one of the images for the hardware keyboard.
[G1 Android Development] dwang:
Is the speed due to the new spl or from wiping?
[G1 Android Development] .PaNiNi.:
who are you typing to?
[G1 Android Development] .PaNiNi.:
thank you this is hwy i love you LOL
[G1 Android Development] .PaNiNi.:
LMMFAOOOO sorry made me lol too lol
[G1 Android Development] :
read and you will find the answer to this....
[G1 Android Development] :
you guys need to follow the suggestions made in this thread, my phone got stuck too and i rebooted and reflashed the JF update (or whatever you are using) and all is fine.

if you are stuck and dont have a memory card reader do this (sir*mez - this is for you too):

plug phone into your computer over usb.

adb shell reboot recovery

then you will be in recovery mode - alt X to exit to terminal (on Phone) -

when in terminal (on phone) type:

mount -a

then - you can access the sd card and move your update to the root and reflash

once you have renamed your update, - type reboot recovery on the phone

voila
[G1 Android Development] rjlan82:
Maybe you don't get it. YOU CAN'T DO ANYTHING. There is no recovery anything to flash an update.zip. It's bricked.
[G1 Android Development] DAKIDD236:
good idea!..lol
[G1 Android Development] DSBP1:
I am only getting 67mbs.....
[G1 Android Development] alapapa:
i don't see any checksums for the SPL...

here's my sha1:

34b26d57985a610f538633e6571d1847c8a4800b spl-signed.zip

can someone verify?
[G1 Android Development] gtest12:
new spl allocates more space to data and system out of cache section. I guess no need to have a bid cache in internal memory. The new cache is about 30mb. I hope it would not cause any problem for ota update, since update file size is larger than 30 mb.
[G1 Android Development] DAKIDD236:
Worked flawlessly, it took about 6 mins the most. Thanks for all of the post!:D
[G1 Android Development] zer0day:
Decided to take the risk and try it. Thought it was bricked but it wasnt :D

I was following your instructions but hit a roadblock when I realized the card reader I had was for MiniSD cards :eek: Big fail on my part.

Anyway, before applying the SPL, I put the JF image on my sdcard via usb named to jf.zip. I put the SPL as update.zip and flashed. It hung at my (custom) bootscreen and I used Call + MENU + Hang up to reboot and then used Hang up + Home to get into JF's console and ALT + X to get into command line.

After doing this, I was able to use adb shell to rename jf.zip to update.zip and reflash the system (without wiping).

Basically, stick both the system images and the SPL on the sdcard before flashing and use the method above to rename it to update.zip and flash the system to avoid a hang on boot.

Hope that helps.

This is the result I see on my phone:

Before:

/dev: 49356K total, 0K used, 49356K available (block size 4096)

/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 409

/system: 69120K total, 59304K used, 9816K available (block size 4096)

/system/modules: 492K total, 492K used, 0K available (block size 4096)

/system/xbin: 3524K total, 3524K used, 0K available (block size 4096)

/data: 76544K total, 42784K used, 33760K available (block size 4096)

/cache: 69120K total, 1528K used, 67592K available (block size 4096)

/sdcard: 1925464K total, 412276K used, 1513188K available (block size 4096)

After:

/dev: 49356K total, 0K used, 49356K available (block size 4096)

/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 409

/system: 92160K total, 55988K used, 36172K available (block size 4096)

/system/modules: 492K total, 492K used, 0K available (block size 4096)

/system/xbin: 3524K total, 3524K used, 0K available (block size 4096)

/data: 91904K total, 42812K used, 49092K available (block size 4096)

/cache: 30720K total, 1160K used, 29560K available (block size 4096)

/sdcard: 1925464K total, 523696K used, 1401768K available (block size 4096)
[G1 Android Development] alapapa:
not specific to theDude's build....no sound feedback in Hv1.5r3 either

lovin the IME & extra space

I had to pull the battery @ my hung splash after flashing the SPL -- otherwise easy peasy
[G1 Android Development] nick8197:
I edited my instructions on the first page hopefully it is more detailed!!

I really dont see how people are bricking their phones?

lol considering when I did it I didnt have any instructions:eek:
[G1 Android Development] cigar3tte:
Followed every step of the way, still stuck at G1 screen at the end. I have no problems going into recovery mode like some of the claimed bricked phones, but I'm still stuck at G1 screen after flashing the build.
[G1 Android Development] nick8197:
you have to put your 1.5 rom back on

read my instructions on the first page
[G1 Android Development] cigar3tte:
I did. Did Haykuro's regular ADP15Hr3. :(
[G1 Android Development] wizern23:
does anybody know the steps to put the new IME on the phone through terminal emu. or recovery term.
[G1 Android Development] jrherras:
I didn't wipe my phone I just followed the instruction update spl G1 hangs on screen removed battery and put JF ADP1.5(MY choice of rom) and flashed it that's it. I noticed speed in home and opening apps actually EVERYTHING!! :)

Now I have 84mb free apps, cache, and dalvik on ext2
[G1 Android Development] Beast84:
And the part of your signiture about "girls with butts like yours" is why I love you lol

That was a classic

Glad I could be of some help here. Did that work out for you?
[G1 Android Development] paulobrien:
I've updated 2 phones, identical methods (and I know what i'm doing) - 1 bricked, 1 went fine... so beware, as of yet there is no reasoning to why the bricking - the 2 phones I have were on identical builds. Same bootloaders, same builds (Haykuro 1.5r2 A2SD).

Strange...

P
[G1 Android Development] sir*mez:
Yes I applied the same file to both phones with the same directions and the same way nothing different. One phone bricked and on the other phone worked.
[G1 Android Development] jonnybueno:
I have two phones as well (3 if you count my girlfriends phone.... not gonna mess with that though). Did you use the same memory card to apply the new spl to both phones? I'm wonder if this is happening because of bad file integrity or perhaps this spl just hates some phones?:confused:

I succesfully applied the spl to one of my phones, but I don't really see the point in putting that new spl on both....
[G1 Android Development] nyayo99:
Thanks for these directions! Worked perfectly. I used haykuro's ADP1.5h3. Now have 66mb free!
[G1 Android Development] grokdesigns:
For those of you are are stuck in a boot loop, but can get to the recovery console, do the following:

Connect phone to computer via USB.

Boot to recovery console.

Press Alt+X.

Press enter.

Type "echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file" without the quotes (this can also be done from adb shell I believe).

This should mount your SD card to your computer so you can copy another update.zip over.

What I ended up doing, after wiping and flashing a fresh JF ROM, is restoring a Nandroid backup. Surprisingly, after restoring with fastboot, the system still recognizes the new partition sizes.
[G1 Android Development] ei8htohms:
did you check the file integrity?

If you used the same method on two phones with different results, it seems pretty likely that the file was corrupted while copying it to the SD card. Did you check the sha1 or MD5 sums before updating?
[G1 Android Development] sir*mez:
On my girls phone I used the supplied t-mobile G1 1gb sdcard and on my phone I used a 8gb class 6 sdcard.
[G1 Android Development] sir*mez:
No I did not check the md5 nor the sha1 on both phone.

Update: my girl wasn't upset this mourning cause I called t-mo for a replacement already. So she's happy I took care of business.
[G1 Android Development] jonnybueno:
Thats good mine would have killed me.
[G1 Android Development] paulobrien:
I didn't check the hashes of the files, but bear in mind the first thing the device does with an update is verify it, surely that shouldn't be the problem?

Besides, has anyone EVER had a problem with a device not updating properly due to a corrupt update file before?

P
[G1 Android Development] sir*mez:
She was laughing at me cause the joke was on me. I tried to trick her. I was gonna tell her she got the cupcake update... lol
[G1 Android Development] jonnybueno:
I've had problems flashing partitions other than the bootloader due to bad usb cables and bad micro sd cards. I guess this is the one partition you just really need to be careful with. :(
[G1 Android Development] tanner2007:
how can we use old bootloader again?

ever since I put it i cant get fastboot to work and this

http://i72.photobucket.com/albums/i172/Tanner2007/here.jpg
[G1 Android Development] Manacit:
So this can brick your phone? I had no problems with it at all, I had to reflash 1.1a, but now it works great :)
[G1 Android Development] wiked1r:
i changed the spl reinstalled jf1.5 hung at boot screen .. removed battery went back power + home wiped and everything is good. even put back aero theme on a2sd .. have 85 mb internal memory
[G1 Android Development] unnatural1:
Thank you. I dont have a card reader, this worked great.
[G1 Android Development] funbacon:
More trick: Push Click.apk from Haykuro H build to use calbiration.
[G1 Android Development] rjlan82:
i checked the sha1 before putting it on my G1 and it was fine. Flashed, bricked. Out of curiousity, i just checked it from the sdcard using my reader, since i didn't check it after copying it over to the sd. checked out fine.

i'm on way out the door right now to buy a replacement off someone from craigslist. i'm pissed.
[G1 Android Development] sir*mez:
damn now that I see more and more g1's being bricked, I was crazy enough to even still try it on my phone after I bricked my girls phone. I would of felt crumy if i'd bricked my phone also.
[G1 Android Development] ei8htohms:
very cool

This worked great, but I think you mean "Clicker.apk".

Thanks funbacon!