yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Six6Sicks:
Add 1 more to the bricked list. Poo!

And people, please stop giving directions how to "fix" the phone. Unless you actually bricked yours, (G1 SCREEN ON FOREVER), and come up with a real solution, there is no point giving your 2 cents because all of us that are bricked know what to do as far as the basic 5 choices on how to "ATTEMPT" to fix this. Those options aren't working.

My 2 cents......

CAUTION WHEN ATTEMPTING THIS SPL UPDATE.

Most have succeded, but some have new G1 paperweights.
[G1 Android Development] sir*mez:
damn!! welcome to the bricked club.
[G1 Android Development] Six6Sicks:
Thanks! I'm gonna see if driving over my G1 with my car helps with the unbricking.
[G1 Android Development] Rickster08:
lucky here just did the same steps and reflashed.....now 82 free...:)
[G1 Android Development] sir*mez:
It should, I've heard that's the only way to unbrick it. The only reason i havent done it, is because t-mo wants to do it for me, so they are sending me a new one, so they can drive over the bricked one for me to unbrick it so they can sell it to someone else.
[G1 Android Development] Manacit:
My phone was stuck at the G1 screen without going to the flashing android, I pulled the battery out and hit home + power and re flashed TheDude's 1.1a and it worked fine.
[G1 Android Development] tanner2007:
If I was your guys, I would not do this, like many My phone hung on T-mobile boot screen, recovery menu nor fastboot/bootloader or what ever it is called wont access. So I had to order another damn phone
[G1 Android Development] sir*mez:
Damn how many are we already with bricked phones. I'm not going back and reading... lol

I'm guessing there are 6 to 7 of us that are bricked since yesterdays release of this spl.
[G1 Android Development] savethechicken:
There has to be something that is causing it because less then 10% of the persons that have done this are bricking the phone. The file is obviously not corrupted at the source (would affect everyone) maybe it is getting corrupted during the download. No Clue, but definitely proceed with CAUTION!
[G1 Android Development] Six6Sicks:
I'm just gonna send back to T-Mobile for a replacement before they starting wondering why the G1 got the SPL swineflu and is being returned like crazy.

Fingers Crossed.
[G1 Android Development] savethechicken:
Is everyone pulling the battery AFTER it goes back to recovery or before?? SO are you hitting home + Back 2 times or one time... If you are doing it one time this might be why this is happening. Just trying to find the trend as to how this is happening.

Sorry I trouble shoot for a living so i just tend to do this naturally, just want to find the root cause.
[G1 Android Development] alapapa:
who knows, man. i just wanna get to the bottom of why some brick and some don't (& maybe help those who know a lot more than I to figure out a fix)

did both phones have the latest radio from HTC's site? were both white? (i think you said your gf's was..). did one or both have apps to sd?

also, it is possible (highly unlikely, of course) to buy two devices off the same shelf @ the store and have them be different hardware revisions -- it's happened to me :-/

cheers
[G1 Android Development] alapapa:
Here's what I did (successful flash):

push spl & rom zips to sdcard

copy spl zip to update.zip & verify sha1sum of update.zip on the device == 34b26d57985a610f538633e6571d1847c8a4800b

boot to recovery

make a nandroid backup (fat load of good that would do if I couldn't get to the bootloader to flash)

Alt + S to apply the spl update

after it completed, i hit home + back to reboot -- it continued applying and rebooted to recovery & applied something else)

hit home + back to reboot once more and it hung @ my custom splash1

I waited 5+ minutes to make sure it was good and stuck

pulled & replaced the battery

held home and hit power to enter recovery

copied Hv1.5r3 zip to update.zip and applied it w/ standard procedure

so, in response, i did home+back twice and made sure it was done applying the hboot.img before pulling the battery for good measure
[G1 Android Development] KidJethro:
My flash was a success. Just to add to the trouble shooting procedure-

After the initial flash of the new spl, I hit home+back to reboot. It rebooted right back to where it was. Home+back again and it hung on the first boot screen, I have a custom boot image, it hung there. I then pulled the battery and the sdcard. Put the sdcard in the reader and into my laptop. Added dude's 1.1a, renamed to update.zip etc etc... Put sd back in phone, re-installed battery. Home+power, alt+s to flash.

That is exactly the procedure I used, in that order and it worked.
[G1 Android Development] savethechicken:
so how about the people that bricked their phone?
[G1 Android Development] Six6Sicks:
Still bricked here. Total bummer.
[G1 Android Development] bfreexxx:
I've noticed that in most cases, my phone is a little snappier and I have more space on my phone to install apps! YAY!!!

Thanks Haykuro!!! for all of your contributions!!!
[G1 Android Development] lazzy81:
Anybody getting the hard keyboard working with the new IME. Mine does not auto correct or suggest
[G1 Android Development] tanner2007:
Guys, I did it last night and had to re flash my phone and another time had to redo my JF 1.5 build. but today after redoing my entire phone due to something unrelated on my part. broke it completely, like me some of use can;t get into fastboot nor recovery menu. I pulled battery; I did it all! and see just t mobile boot screen ands that's it

I respect haykuro for all his work, but he really should never have released something thats causing people to completely break there phones and some have to pay top replace, or atleats gave use a huge warning saying its causing this. but when people see a guy we trust with a release. we download without worrying about anything and look what happen this time
[G1 Android Development] gtest12:
Just had my phone bricked when I try to replace version 26I radio with old radio RC33 radio. It hangs on G1 screen right now.

My update on SPL actually went through.
[G1 Android Development] KidJethro:
With the hard keyboard open, tap in the text box as if calling up the on screen keyboard, nothing will visibly happen, but it should work after that. It does for me.
[G1 Android Development] lazzy81:
Thank you worked like a charm on the keyboard
[G1 Android Development] g2crx:
curiosity was killing me so i tried it lol.i followed these steps and worked like a charm.:D
[G1 Android Development] savethechicken:
I flashed back to the HardSPL, and my custom boot image returned ::puzzled:: when I had the Hayruko SPL I only had the T-Mobile G1 Screen. There has to be a problem with this SPL that it didn't show my second boot image, or is that what was changed to save space. heh.

That make sense.
[G1 Android Development] johnnylicious:
yeah haykuro removed the 2nd bootscreen with the flash android text to save more space for the partition
[G1 Android Development] jashsu:
Maybe that's the problem?
[G1 Android Development] justanothercrowd:
Well obviously the download isnt corrupted but when you trasnfer a file to your flash card there is a chance it will become corrupted. I'm positive that this is what happened to those with "bricked" phones.

We know this SPL will run on the G1's hardware without issue. I have it on mine in fact. The SPL is just really important and you need to take extra precautions to make sure everything is good before you flash.

Even if Haykuro didnt provide a checksum for the file you can check it on your flash and in your download location to make sure they are the same.

Sorry that you guys have a brick now but this isnt something to go about worry free anyways....its the SPL folks!@
[G1 Android Development] tanner2007:
thats what happen to me
[G1 Android Development] daveid:
I am not entirely sure as to why so many of you are trying this anyways. I mean, do you need more free space on your /system partition? Most of you (if not all) have your apps2sd going, so you don't need more space on the /data partition. I am just curious as to what what drive you do do this, without a direct need. I think it is cool, and I have been waiting for someone to modify the partition table, but seriously.. I have 4.5M free on my system partition (with like 12M of custom ringtones on it) and 59M on my data partition. So, I fail to see what this mod would do to enhance my phone in it's current state... not worth the risk to me, but a great idea!
[G1 Android Development] jmon777:
aman!!!

if this is something so simple as an issue with transferring from pc to phone and it getting corrupted how come this did not happen with hard slp?:confused:
[G1 Android Development] crazythunder:
i just do it for the challenge. like most,and because we can. but the mods that provide more functionality is what it's about. i hear ya on that.
[G1 Android Development] cigar3tte:
I didn't like apps2sd, so I tried this. Mine wasn't bricked as I still had access to Recovery, but reflashing continues to bring me back to the stuck G1 screen.

As for now, I'm fine, I fastbooted the boot.img from Haykuro's Hr3 zip file.
[G1 Android Development] alapapa:
I wanted to install the IME and my system partition was full...that's what prompted me anyway

i don't do apps to sd b/c i only have a class 2 card
[G1 Android Development] jmon777:
eat roman for a few months and buy a class 6 like i did jk :D

but why did we not have this issue with hard spl?
[G1 Android Development] sir*mez:
Exactly what I was thinking, why didn't the hard spl do this to anyone elses when they flashed that? I should of stayed with hard spl. I want to go back to hard spl but I'm afraid to brick this phone cause I don't have warrenty. I'm on the H special spl and I don't want it cause of the risk I'm running and it bricked my girls phone.
[G1 Android Development] zombierockstar:
Haykuro...you freakin' rock! This is sweet! My G1 is faster now! No lag!
[G1 Android Development] nick8197:
Really? I have the new SPL and I still get the flashing android text...
[G1 Android Development] sir*mez:
I also get the flashing android text also!!!
[G1 Android Development] jayb222:
Me too! Still there but 70mb free instead of 40mb. So did it work? I'd assume so.
[G1 Android Development] nick8197:
lol yea it worked
[G1 Android Development] sir*mez:
I have 87mb free.
[G1 Android Development] nick8197:
Mine says Memory 34MB / 89 MB

I dont have apps2sd or anything so all my apps are on my phone
[G1 Android Development] sir*mez:
I wish my girl could of enjoyed this tho and the other 6 bricked phones on here!! I wish haykuro would atleast post something to why this may of happened.
[G1 Android Development] jayb222:
Reading it again it says,

free internal space: 76.0mb/94.0mb

So it's right even though I have both splash start up screens?
[G1 Android Development] barakinflorida:
just did it myself.... i think i know why..

You said that your phone was jail broken before and you "just rooted hers"

if i got that right .... did you install a cupcake build on her phone before installing the new spl.... did you install the recovery.img from the how to root. Or the one that is on your phone 1.42 or 1.43 first? did you ever see the recovery screen that you did not have to press alt l to see the text? I think the problem is that you cannot do this on top of rc29 with the recovery.img from the how to root.

ps.... I have jail broken several phones and after giving mine away tonight fully upgraded new spl and all I BRICKED my phone.... same stuck @ g1.

If I'm right you need to check to make sure you are on 1.42 or better... good luck with the warranty.
[G1 Android Development] bakachu:
Does any one have theories for how the SPL makes the phone to look a bit faster? Or could this just be placebo?
[G1 Android Development] nick8197:
Im guessing the more memory is free which makes it a little faster
[G1 Android Development] nick8197:
Yes I also have both start up screens Im pretty sure you are supposed to!
[G1 Android Development] sir*mez:
I was on jf 1.5 on both phones. Two phones identical. One bricked and the other flashed without a problem. T-mobile already texted me saying that they have my new g1 ready to ship.
[G1 Android Development] chamelieon:
same thing i did step by step and all succesful!

edit: i have the flashing android boot also.
[G1 Android Development] jayb222:
Cool! I'm glad it went smooth. I didn't know about the bricked phones before trying it.
[G1 Android Development] nick8197:
Yea its weird that people are bricking their phones I added a warning on my directions

Do you remember on your gf's if you took the battery out before the 2nd reboot or not? maybe that did it if you take it out premature?
[G1 Android Development] jashsu:
It only increases /system memory (flash memory), not RAM. Any increase in speed is either a) placebo b) due to clean reinstallation.
[G1 Android Development] nick8197:
Yea but wouldnt having more space be able to make the phone faster such as if you had no apps installed it would be faster than if you had alot of apps installed on your phone and not alot of free memory?

I think it seems faster in that sense!
[G1 Android Development] barakinflorida:
I understand, but I also remember that JF mentioned that you need to install 1.43 if you want the boot loader and if you notice the jf1.5 is only 36.xx Meg. I know for a fact the the first phone I applied the NEW spl to had 1.43. (at about 9:00pm) The second phone I MANAGED TO BRICK (at 1:35am)when I was installing the spl update.zip I had to hit ALT L to see the Boot loader menu.... my question is did you ever install a copy of jf rc331.42 for dev1.1 1.43 on you girlfriends phone....
[G1 Android Development] nick8197:
Yea thats correct!!

I also had 1.43 before and had the bootloader and mine went fine
[G1 Android Development] wwwhershcom:
the new SPL work for me.

i had a little trouble at first with it getting stuck, this is what happened.

when i took the battery out, and put it back in, it automatically turned on.

there was no time to press home+power.

so i pressed the buttons, then dropped the battery in with my teeth.

lol, it helped.
[G1 Android Development] alapapa:
perhaps OP instructions should instruct users to flash the recovery only image if they are uncertain they already have it:

http://jf.odiness.com/v1.43/JFv1.43_Recovery.zip

couldn't hurt
[G1 Android Development] sir*mez:
It booted twice. I flashed it then the chip with the arrow came out it rebooted and then nothing. I was like ok this is where they said i'd have to reflash jf 1.5 so I waited awhile took the battery off and started the phone with home+power and I couldn't do anything.
[G1 Android Development] theslam08:
In the long run it might be worse if you think about it, having more space means more things on the main memory for the phone to support at all times (actively). This could slow it down because you added 50 more apps than you could previously. Only an assumption.

[FOR BRICKED PHONES TRY:]

Next, something I have not tried but im thinking of past phone recoveries....sometimes when booting I get an error stating unknown usb found (while plugged into the computer). If you get the ADB drivers installed, you 'might' be able to do this:

adb shell recovery

I believe if you do that, you might be able to get into the recovery mode from the computer (while the screen loops). If it says error then it does not work. But if nothing comes up or it just goes to the next like then you have to research and find the exact commands of doing the update.zip file from there. Good luck.
[G1 Android Development] iammrwizard:
Hey Guys, my 2 cents...

After applying the new SPL I was stuck at the G1 screen so I pulled the battery and it would just stay stuck at the G1 screen (I'm assuming this is what everyone thinks is bricked?)

If you pull the battery and then put it back in and turn it on holding home and power then just re-flash your haykuro or whatever cupkcake build you were using it works great, I've done this on three different phones.

I would be surprised if you didn't have to reflash the build after changing system partition sizes the OS is going to be all screwed up until you reflash..

P.S.

(Dont forget you have to pull out the memory card put it in a card reader and remove the spl that you had named update.zip and replace it with the cupcake build as update.zip then put it back in the phone and turn it on holding home and power to reflash the build Alt-S otherwise you are just reflashing the SPL over and over)
[G1 Android Development] SolemnWishing:
After reading 25 pages of the same advice for people with bricked phones, I need to emphasize that

THE PHONE'S SPL AND BOOTLOADER FAILED. THIS MEANS THE PHONE CANNOT BOOT WHAT SO EVER. YOU CANNOT ENTER THE BOOTLOADER OR THE RECOVERY SYSTEM. MEANING, YOU CANNOT REFLASH YOUR ORIGINAL FIRMWARE OR ANYTHING AT ALL. ONLY OPTION-RING UP TMOBILE AND ASK FOR A REPLACEMENT.

Is that clear enough? (:

And again, this really shows the importance and dangers of flashing a new SPL. I never had known this process was so risky, and chances are I will think twice about reflashing a new SPL now.
[G1 Android Development] futango:
I dont know if you just can't read or just dont understand the last 16 pages. But they CANT GET INTO RECOVERY OR ANYTHING!
[G1 Android Development] jashsu:
I implore people who have bricked their phones with hacks (e.g. this latest SPL) not to lie to T-Mobile for a replacement. This kind of behavior demeans the legitimacy of the dream hacking community. From a legal perspective, it is fraud.
[G1 Android Development] paulobrien:
For those who have successfully flashed...

does anyone's bootloader show hardware bersion DVT2-1 as below?

DREA100 DVT2-1 32B

This is the board build revision, and could be a clue to the brickings. To those who have NOT flashed, could you check this before you do so?

Maybe a mod could add this to the first post?

My DVT2-1 bricked, and my non DVT2-1 didn't.

P
[G1 Android Development] sir*mez:
I just told them that it was charging and when I went to check on the phone it turned on like someone turned it off and its stuck on the g1 screen. I tried to dumb myself down and not know what cupcake was when he asked me, lol. I got a new g1 coming to my doorstep by tues. Or weds.

By this time id think they would get it but idk. I bet there's gonna be another smart guy who suggests the same sh!t!!
[G1 Android Development] nick8197:
Here is what mine says exactly I have the new SPL

Dream PVT 32B ENG S-OFF

HBOOT-1.33.2005 (DREA10000)

CPLD-4

Radio- 2.22.19.26I

Apr 20, 2009, 15:30:43
[G1 Android Development] SolemnWishing:
I understand where you are coming from, and now that I look back at what I had said, I see what you mean. However, when someone loses their several hundred dollar investment, it is a bit difficult to deal with. The only reason I brought that up was because I had my G1 replaced for the reason that the screen was wobbly. They never asked me about the condition of the firmware, so I assumed it wouldn't matter. Moreover, the wobbly screen issue will hit 95% of G1's within a few months, so it is very likely many people have this issue. Again, I understand what you mean, so I will remove the last part of my post.
[G1 Android Development] savethechicken:
The flashing android isn't one of the boot/splash screens i was talking about. there are a total of three boot screens.

Two of them are the Tmobile G1... unless you have put a custom splash screen(s) on your phone you would never know the difference...

For example my phone boots to tmobile G1 then about 2 seconds later if that it goes to a screen with a penguin that says linux inside. then it goes to the Android screen after. When I had this SPL on my phone I only saw the Tmobile G1(and it was on for the 20 seconds my penguin usually took) I was not able to see the penguin screen then it went straight to the android flashing screen.

So you should have two boot screens that you see... The T-Mobile G1 screen and then Android flashing.

but with other SPLs you see three.
[G1 Android Development] paulobrien:
OK... so has anyone successfully flashed with anything other than PVT?

P
[G1 Android Development] barakinflorida:
omfg

Ok so I don't know why some float and some sink like a brick, but....

The second phone i flash with the new spl was just jail broken... and I bricked it!

The first was my phone and that went well...

The third...(yes, don't fear the brick) was my first ever g1's (long ago dead do to sd card slot death) main board taken out and replaced in the brick...

it worked.

more later my 3.5 year old is waking up and i DID NOT SLEEP...

parts of g1 all over the place

:eek:

PVT NOT DVT-2
[G1 Android Development] jashsu:
Thank you. Obviously neither I nor anyone else can stop folks on here from doing shady things. However, at the very least I hope no one on xda will endorse illegal and/or unethical choices.

I have and continue to rail against the irresponsible release and consumption of hacks on xda. Too many newbies and self-proclaimed experienced users are jumping straight into some

very untested and possibly dangerous hacks

without recognizing that they could very well perma-brick or near-brick their phones. What they don't recognize is that a lot of these hacks are works-in-progress or untested on all hardware/software configurations and should only be attempted by developers and hackers who A) know exactly what the hack entails and what they are doing and B) that they quite possibly are risking a brick.
[G1 Android Development] paulobrien:
Agreed, I still maintain the first post of this thread should be updated with info re: the bricking, and also asking users to record their hardware revision from the bootloader to potentially isolate problem devices.

P
[G1 Android Development] exile20:
Wow, I added the new spl like when this thread hit page 3 and now at 20+ with all this bricking i would have never tried it. Anyway i realised that after the update process and i press back and home i saw that it updated some more stuff then restarted. Maybe people are taking out the battery before pressing home and back. Anyway my question is what are the long term effects pertaining to use and adding new firmwares and running out of internal space. What is Haykuro's take on this? Maybe he can shed some light.
[G1 Android Development] jashsu:
The reason that the phone may be faster when no apps are installed isn't because there is more space. The reason is most likely because when more apps are installed, there is a good likelihood those apps are running background processes which slow the system down.

If your computer had a hard drive that was half full, and then you doubled the size of the hard drive (without changing its rotational speed or cache size), would your computer be faster? No, not really.
[G1 Android Development] grokdesigns:
Anybody notice that with the new IME, the right shift button on the keyboard doesn't capitalize letters sometimes?
[G1 Android Development] snear:
both working great on 502 a2sd

thanks!
[G1 Android Development] robbie725:
seems to be working for me...

And with the SPL issue(which i am not trying) I don't pretend in anyway to be an expert on this but could it be a issue with different radio versions...???

peace
[G1 Android Development] barakinflorida:
I didn't take a chance.... I installed the latest radio + JFv1.42 + JF1.50 + Hardspl and only then did I try the new spl....

first phone good

second phone brick

third phone good.
[G1 Android Development] Six6Sicks:
So all these brickings (including mine) and not a single word from Haykuro regarding any of this? Not cool.
[G1 Android Development] Christopher3712:
The new SPL got me too, I had to use a nandroid backup. Anyhow, Haykuro's working on something that pretty much renders this SPL useless. He can only do so many things at once.
[G1 Android Development] sir*mez:
I tried askiing him on the ssshhhh thread and he hasn't answered me. Only his supporters saying the same crap about reflashing. I asked haykuro and all his cheerleaders answer for him.