yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] sir*mez:
So if he's working on something else that's more important than this, he shouldn't of let this out. Instead we are being his beta testers when it should of been himself testing it.
[G1 Android Development] Six6Sicks:
I don't agree with the "beta tester" theory. I was bricked to, but no one asked me to try this. I did it under my own power and without any threats of any kind. lol. As with everything I've gotten off xda to install on my phone, it is a risk I've been willing to take.

I'm not upset with Haykuro, I was just wondering if he had any suggestions.

Bricked but still smiling :)

New G1 should be here by Wednesday.
[G1 Android Development] exile20:
what do you mean? Did you get your phone working using a nandroid backup after a fail spl update? How?
[G1 Android Development] andonnguyen:
I'm sure he has tested this SPL himself, and it worked perfectly for me and for many others. As with anything in these forums, there is risk involved with modifying your phone's files, so basically we are all beta testers, even those that originally created the methods (i.e. apps to sd, etc, etc.) Hopefully you can find a way to bring your phone(s) back to normal, or take more precautions in the future (like checking MD5 checksums, or making sure the software is compatible with your current FW.)
[G1 Android Development] zer0day:
Everyone knows there's always a risk when flashing the SPL. No doubt he's flashed his own phone, he took a risk just like the rest of us.
[G1 Android Development] nick8197:
I have a question all this brick stuff is scaring me even though I SUCCESSFULLY installed the new SPL

If I want to go back to the HardSPL do I just dl that and install it?

waht do you think the chances of bricking would be?
[G1 Android Development] sir*mez:
There are people that have done it to 3 phone and have 1 phone brick. I've done it to 2 phones and had 1 phone brick. Now if that doesn't concern you that there might be something wrong with the spl then I don't know. I've been flashing roms from here ever since the wing and this is the first time something like this happens. Don't be fooled by my post count I've been here longer than you think, just lurk reading.

Edit: I'm not mad at haykuro. I'm just saying, he should atleast say something. He can't be a god in everything people also have to accept their failures.
[G1 Android Development] Henchman:
If you want to talk to the person responsible for your bricked phone, go finda mirror and have a nice little chat.
[G1 Android Development] d474rpr:
I am also suffering from the "Bricked" issue on my ADP. Here's what happened:

Loaded the spl as update.zip

The update froze me at the initial boot screen.

I rebooted the phone using [call] [menu] [power]

Entered the recovery console

Ran the update again

I saw the firmware "updating" image appear for a brief moment and then it went away.

Since then I haven't had any positive response from the phone.
[G1 Android Development] Henchman:
2nd flash should have been with your firmware update. Not the ALL update.
[G1 Android Development] andonnguyen:
So now, is your phone able to boot up? What modes are you able to enter (recovery, bootloader, etc)? Maybe we can offer you some insight to get you up and running again.
[G1 Android Development] sir*mez:
This SPL should be renamed from H-Special SPL to the Android Swine SPL. The count on bricked phone keeps going up.
[G1 Android Development] MarcusMaximus04@gmail.com:
Whew I was about to try this and then thought "Hmm 28 pages, lets see what people are thinking of this." Glad I read it, will wait to see what results come from this with all the bricked phones.
[G1 Android Development] TheDudeOfLife:
Add one non-bricked happy phone to the mix.

You guys are silly.

GIVE ME THE LATEST ****!!!!

MY PHONE CRASHED BECAUSE I LIVE ON THE EDGE!!!!

BURN THE WITCH!!!
[G1 Android Development] Gimpeh:
You should have been in the IRC Source channel when tanner came in complaining. It was comedy.
[G1 Android Development] speoples20:
Didn't you brick your girlfriends phone that wasn't rooted? But it worked on your rooted phone. So no one but yourself could be blamed for that. From what I've seen people bricking their phone is not that high and the people who are bricking seem to not know what they are doing. I'm sure lots of people have flashed this, myself included, have successfully flashed the new SPL.

We all know(or at least should know) there is a risk when doing this.
[G1 Android Development] exile20:
Can anyone give an insight into the long term effects and also some guy said some post up said that he used a nandroid back up to get back his phone. Is this possible?

My phone is fine after the spl update but i really feel for the people that have bricks now cause that could have easily been me.
[G1 Android Development] sir*mez:
You need to go back and reread. I said my phone and my girls phone both had jf's 1.5. From what I see I know what I'm doing you just don't know how to read.
[G1 Android Development] TheDudeOfLife:
Well, maybe next time don't use your girlfriend's phone as a guinea pig.
[G1 Android Development] sir*mez:
Well she likes to have everything I have so therefore I knew she wouldn't mind. She was bugging me about cupcake so I gave it to her then I saw this and thought it was a good idea and I gave her this too, but I guess I was too generous since the phone bricked. I then tried it on my phone cause I'm confident I did everything right and it worked on my phone. If I did anything wrong then I should of bricked my phone also.
[G1 Android Development] futango:
If you successfully did the new spl then i dont think there is a chance of bricking. its those in the process of putting on the new spl that bricks.
[G1 Android Development] MrADeveci:
You really are funny ......... someone must have held a gun to your head an forced you to flash your phone?

Oh no ... of course not, it's a developing community.

Do these things at your own risk, and don't forget to APPRECIATE the hard work developers do for you in their own time .....

In old money, we used to call people like that l33ch3rs!!!!!!!!!! :)
[G1 Android Development] paulobrien:
How's about just getting to the root of the problem rather than *****ing and moaning?

It's not user failure.

It's not a corrupt update.

It's not related to the memory card type / size.

It's not related to the radio version.

It's not related to the installed OS version.

(all based on both my own experiences and those in the thread).

I STILL think the most likely cause is board version variations, hence the plea to check board version from bootloader BEFORE flashing.

P
[G1 Android Development] paulobrien:
Also in total agreement that if you mess with your SPL, you gotta know that it's the one and only operation that could brick your device.

P
[G1 Android Development] futango:
With the post about the older spl being PVT not DVT. I have a good feeling that might be problem. I havent seen anyone that said they had a DVT and flashed the new spl and got it working successfully. Haykuro probably had a PVT G1 and got it working fine without knowing that there was a DVT-2.
[G1 Android Development] alapapa:
I agree...it almost has to be either related to board revisions or recovery partition version
[G1 Android Development] sir*mez:
That was totally intended as a joke. Fine you took offense to it. I give credit when its do. But when theres more than one brick phone off this then there's a problem. I'm just stating the problem so it gets fixed. If you call that *****ing and moaning then no problem in this world would ever get fixed. I have a problem and I want to fix it.
[G1 Android Development] Crackbone:
The issue is that not all the phones are getting bricked. The common element amongst the bricked phones isn't easy to identify, and honestly, when dealing with SPL, the first thought to enter my head is user error.

Now, I'm not saying that's the true cause. I'm not even saying that you did something incorrectly, however, riding F5 and then replying every 2 minutes isn't going to get your problem fixed more quickly.

I understand you are attempting to bring the issue to someone's attention, rest assured, we know you bricked your phone. We know that other phones have been bricked in this process. That's not the issue, the issue is the common denominator, and at this time, it's unrecognizable, unless, of course, it's user error.
[G1 Android Development] andonnguyen:
yeah yeah! Give me the cool stuff! I want it to the max! Crash and burn, i heart u android!
[G1 Android Development] sir*mez:
what bothers me is that haykuro hasnt said anything. hes repling in his ssshhhh thread cause hes being praised. but people should accecpt their failures as must as they accept their achievements. on the replies every 2 mins. im in a bigger forum and im used to repling fast cause of the convos that go on there.

like i said b4, ive been here since the wing and this is the first thread i post anything on.
[G1 Android Development] MarcusMaximus04@gmail.com:
His last post on that thread was about 13 hours ago. He's 17 years old and is in high school, of course he's not responding, he's probably in school right now.
[G1 Android Development] nukes777:
Hi All,

I am having trouble pushing the IME

I am getting the following error:

C:\android>adb push HTC_IME.apk /system/app/HTC_IME.apk

failed to copy 'HTC_IME.apk' to '/system/app/HTC_IME.apk': No space left on device

any ideas? I have 17mb internal space left

I am running Haykuro's ADP1.5Hr3
[G1 Android Development] sir*mez:
i guess he missed my post at 1:24pm right under his, since he left at 1:19pm. i didnt know hes 17yr.s old. i dont go into the personal stuff on forums.
[G1 Android Development] MarcusMaximus04@gmail.com:
Ok, ok. Just saying, give him a little bit of time. I didn't expect you to know he was, I was just throwing that out there as a possible reason why he's not responding.
[G1 Android Development] d474rpr:
So here's my theory for what happened to those of us with now semi-bricked Android devices. I think that some of us were using different flavors of builds and the update to the SPL is causing a buffer overflow. If anyone noticed the SPL update was 182kb compared to the ones released in January that were at 177kb. Now, I don't believe that the bricked devices are 100% dead and the reason for this is that when I initially plugged by phone in after the incident I didn't even get the red LED indicator for when the battery charges during the power off state. A few minutes ago I was showing a work collegue the issue and the LED lit up... I tried to load into the recovery console and the LED went off and I'm back to square one. (with a bricked device) This is a small glimmer of hope and I will continue to mess with this to see what will happen. Can anyone reproduce this?
[G1 Android Development] nukes777:
OK

after I rebooted my G1 I now get the following error

failed to copy 'HTC_IME.apk' to '/system/app/HTC_IME.apk': Read-only file system
[G1 Android Development] MarcusMaximus04@gmail.com:
Hmm that sounds like the battery was totally dead. For those with bricked phones, what was your battery level at? Mine worked perfectly but I had 95% battery when I flashed it.
[G1 Android Development] MarcusMaximus04@gmail.com:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
[G1 Android Development] sir*mez:
i was at 89%. i always check that b4 flashing anything.
[G1 Android Development] nukes777:
now i get the space error again...

#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

#cp sdcard/HTC_IME.apk /system/app/HTC_IME.apk

#cp sdcard/HTC_IME.apk /system/app/HTC_IME.apk

#cp: write error: No space left on device

C:\android>adb remount

remount succeeded

C:\android>adb push HTC_IME.apk /system/app/HTC_IME.apk

failed to copy 'HTC_IME.apk' to '/system/app/HTC_IME.apk': No space left on device
[G1 Android Development] andonnguyen:
Why are you copying HTC_IME.apk twice to /system/app?
[G1 Android Development] MarcusMaximus04@gmail.com:
busybox df -h

and check what space is available in /system(/dev/block/mtdblock3). The "sd card & phone storage" page just shows what's available in /data(/dev/block/mtdblock5).
[G1 Android Development] d474rpr:
Yeah, I do think my was fairly low but not low enough to not allow the flash to complete. I'm letting the battery charge now, hopefully not in vain but probably so...
[G1 Android Development] nukes777:
C:\android>adb shell

# busybox df -h

busybox df -h

Filesystem Size Used Available Use% Mounted on

tmpfs 48.2M 0 48.2M 0% /dev

tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals

/dev/block/mtdblock3 67.5M 64.8M 2.7M 96% /system

/dev/block/mtdblock5 74.8M 56.6M 18.2M 76% /data

/dev/block/mtdblock4 67.5M 1.8M 65.7M 3% /cache

/dev/block//vold/179:1

966.6M 414.9M 551.7M 43% /sdcard

so it appears im out of room on /system

arrrgghhh... any ideas what i might have in there that is hoggin space or stuff i can delete?
[G1 Android Development] sir*mez:
you can flash this spl to free up some space on your system... let us know how that goes if you do it. it will make your

/dev/block/mtdblock3

67.5M

64.8M 2.7M 96% /system

to 90M.
[G1 Android Development] speoples20:
You can delete some ringtones of you don't use them or notification tones. Thats what I did to get more room.
[G1 Android Development] MarcusMaximus04@gmail.com:
hmm fastboot should skip the G1 logo completely. Just out of curiosity, what comes up if you try a fastboot?

and a note just in case people think it's bricked not knowing what fast boot is or how to activate it:

to go into fast boot you have the phone completely off and then hold down camera and press power. Then when the skating androids come up you press back.
[G1 Android Development] tanner2007:
Nothing, hold down camera and then press and hold power and fastboot dont come up..nor recovery menu..nothing..press it down and hold it for 3 hours and still nothing
[G1 Android Development] MarcusMaximus04@gmail.com:
Ah, ok. I kept seeing posts saying that it hangs at the G1 logo even with fastboot and was like wtf. But not coming up to anything at all makes a lot more sense.
[G1 Android Development] d474rpr:
I originally had the issue where I did see the "G1" boot screen, whereas mine is just the Android logo since its the ADP and not a G1, however, after attempting to reload the H-SPL the second time I was redirected back to the recovery console. I entered the terminal screen from alt+x and typed reboot... phone powered down and I haven't seen a spec of life from it since.

The reason I suspect a buffer overflow is that when the power key is pressed it kills my power light. This is a far fetched notion but I've been working in software/hardware QA for a while now and this is the only thing that makes sense...
[G1 Android Development] paulobrien:
Both my devices had same recovery partition.

P
[G1 Android Development] MosquitoD4K:
It bricked my phone too, and please dont tell me about how to get into fastboot menu or recovery menu by pressing Camara /home button + power button. I had a G1 Developers Edition with root access and so on, I had newest JK RC9, 1 GB microSD. Let's hope there will be any solution solving this problem first thing I will try, is letting the phone crash by running out of battery if this wont work, I'll see ^^, problem is Im in Germany , and I bought this phone in America, so a little problem about getting a new one, maybe I could try a local T-mobile/T-Com store, but dont know if this'll work because I bought it at a google shop. What do you think?
[G1 Android Development] justanothercrowd:
You have no right to complain if you did not check the MD5 or SHA1 checksum before and after transferring the file to your SD card!!!

We already know most people don't use transfer cables with ferrite cores on them and everyone who has a bricked phone cannot confirm that they verified a checksum because they didnt....this is your fault! not Haykuros

The new SPL works fine on DREAM hardware.

For everyone wondering why this didnt happen with the HARD SPL...it did!!!!

There was a fraction of the traffic when one this forum when that SPL came out and we still had noobs bricking phones.

Now that everyone who can type "root g1" into google (even when they don't even know what "root" really is or what to do if they got it) is flashing their phone with custom ROM's...using apps2sd when they really don't need to be.

So now we have a much higher rate of posts with issues...this is not a bad SPL. This is noobs bricking their phones and trying to blame someone else for the issue when they didnt verify checksums of a critical file before renaming it and flashing it.
[G1 Android Development] d474rpr:
I think we're ****ed mate. Pardon the lingo but I'm a bit depressed atm.
[G1 Android Development] maxisma:
It is not because of corrupted files, but because of changes in the actual g1s.
[G1 Android Development] sir*mez:
so yea im a noob that flash one phone that brick and then i flashed another phone with the same method and that worked. there are people here that have done it to 3 phones and bricked 1. so yea I guess we're noobs. hmmm
[G1 Android Development] d474rpr:
Get off the f'n soapbox. No one has blamed Haykuro for brinking a phone and for the record I do use a cable with a ferrite core. So chill out. I have a fear that will all the mingling and mixing we've done with all the builds, radios, SPL's and variances in the kernel builds that something finally snapped for a few of us unlucky people. This has nothing to do with the MD5 or SHA1 checksum. If it did this would happen everytime a SPL hack comes about. And check you're damn resources before you start throwing the noob card.
[G1 Android Development] neoobs:
Thread Closed.

Haykuro can re-open the thread by PMing me. If it re-opens there will be no bickering about who is to blame and who is a "noob"
[G1 Android Development] Beast84:
You have the 1gb card the phone came with right? Put the spl update.zip on the 1gb card & the JF/haykuro/dude update.zip on your sdcard that you use & just switch cards
[G1 Android Development] nick8197:
FOLLOW MY DIRECTIONS!!!

you have to do the JF 1.5 update again and then it will work so you have to get your sd card back on your computer through an sd card reader and put JF 1.5 back on it rename to update.zip do the Home+Power and Alt+S
[G1 Android Development] sir*mez:
ok i need help... it seems like you can lend me a helping hand. i have a sdcard reader i did what was needed. but now im stuck at the t-mobile G1 screen. I took out the battery and have been restarting it with power+home and i get nothing. it stay in the t-mo screen... do you have an idea what to do next cause i cant get into recovery nor the spl boot.
[G1 Android Development] sir*mez:
sorry double post.
[G1 Android Development] beagz:
Make a directory on your sdcard called themes.

Make a directory in themes called spl

Get gscript and make this script save as spl

#!/system/bin/sh

echo "boot-recovery

--update_package=SDCARD:themes/spl/update.zip" > /cache/recovery/command

reboot recovery

Put the spl file in sdcard/themes/spl and rename to update.zip

Keep your rom in the root of your sdcard

Run the script in gscript when it finishes rebooting and loading, press home+back and it will reboot again, as soon as the screen is black press and hold power+home. At the boot screen press alt+s to apply your main rom (sdcard/update.zip) press home+back to restart and you are good
[G1 Android Development] Beast84:
Did you do what nick8197 said?
[G1 Android Development] sir*mez:
thats what i did but i cant get to the recovery. im stuck on the t-mobile screen. i've taken the battery out and restarted with home+power but nothing. it just hangs on the t-mobile screen. my girl is gonna kill me cause i decided to test this on her g1 first...
[G1 Android Development] :
Not sure if this will work, but try holding Home and Back while booting. Hopefully it will allow you to do a wipe and you can advance from there.
[G1 Android Development] Beast84:
Haha sorry that part just made me lol!!!

On another note, did you try doing a wipe after? Maybe even going back to the previous SPL? Did you at least backup before trying this?
[G1 Android Development] nick8197:
Well is your phone rooted?

If you did the directions I put up on the first page it should have worked
[G1 Android Development] sir*mez:
no i get nothing. still stuck on t-mo screen. im not doing this to my phone till i fix my girls phone!!

no i didnt do a wipe. but now i cant wipe, get into spl nor get into recovery. the phone just hangs on t-mo screen. damn my girl was on stock rc33 and i just rooted and updated it to jf 1.5 to be like, yo you got the cupcake update last night!!! i guess the trick is on me now!!
[G1 Android Development] sir*mez:
i had just finished rooting it and puting jf 1.5 on it. i was playing a trick on my girl so she thinks she got the cupcake update and i saw this new spl. i was like, let me test it on hers first. now shes gonna kill me in the mourning when she finds out!!!
[G1 Android Development] Manacit:
I installed it, then it got stuck at the first splash screen, so I took the SD card out and put thedude's 1.1a and installed it, rebooted and it worked fine. never wiped or anything.

The new IME works great too :)
[G1 Android Development] andrews240:
Waaaa. I broke my girlfriends phone and now she's gonna kill me, waaaa.

Just kidding. Try this:

1. Remove the battery

2. Firmly hold down the home button only, power will happen all on it's own

3. Re-insert the battery while holding down the power button, don't let go until you see the script text scrolling.

4. You should be in recovery mode at this point, so you can reinstall.

If this does not work, there is something wrong with the home button on your girl's G1. Good luck.
[G1 Android Development] doubleokneegro:
followed these exact steps... and within in 5 mins i was up and running, will post a screenshot of my new hopefully larger partition.... no wipe was neccessary... but idk if it did or not.. wasnt intitiated

had JFv1.5 by the way
[G1 Android Development] sir*mez:
lol at the waaa...

I did everything you posted and nothing, still stuck on g1 screen. there shouldnt be anything wrong with home button cause i had to get into recovery mode to update the spl. i even wish i could get into the boot so i can reflash it to rc29 but i cant get that either!!
[G1 Android Development] nick8197:
LOL i edited my directions

I just added take the battery out and put it back in because it hangs in case people figure it out themselves :)
[G1 Android Development] doubleokneegro:
here is a screenshot... i am using the internal memory card widget to show my space has increased to 89mb available as my maximum..
[G1 Android Development] sir*mez:
i wish i could flash the rc29 to start all over... i think i really bricked this phone!! no recovery and no bootloader nor even a fastboot.
[G1 Android Development] nick8197:
You said you did root today?

Are you for sure you were successful and had root on the phone?
[G1 Android Development] tanner2007:
Whats IME?
[G1 Android Development] Beast84:
The english HTC keyboard
[G1 Android Development] sir*mez:
yes, i had jf 1.5 i just did that root today on her phone. but my phone has been rooted since rc33 came out.
[G1 Android Development] nick8197:
thats wierd then I dont see why you cant get into recovery mode

You hold down home and Power until it comes on correct?
[G1 Android Development] andrews240:
Sorry bro. Hopefully someone can come up with a creative solution. Did you check to see if adb shell is available while it is stuck at the T-Mo splash screen?
[G1 Android Development] jamesbui12:
if you have any old phones like the t-mobile sidekick or dash, take your sd card and toss it in one of those phones and then copy whatever cupcake build you want to your sd card and rename it update.zip
[G1 Android Development] sir*mez:
yes i do hold home+power. i;ve even held it for 5 mins. with my hands cramping... lol

no adb shell. im just gonna call t-mo and send it back. i bought this for her on valentines, so it should still be under warrenty. im just gonna tell them i dont know what happened to it.
[G1 Android Development] udontcdis:
Can anyone plz tell me how to install ime?