yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] lbcoder:
Your thoughts aren't quite right. Yes, when flashing the hacked SPL, the flash memory is corrupted, so the kernel won't boot. This *always* happens and doesn't matter since if the flash was successful, you start up in fastboot and flash the system images as normal. The problem with the bricked devices is that it *never gets to the kernel*. It dies on the IPL->SPL handover. Boot process is IPL->SPL->Kernel.

Also note: IPL (initial program loader) and SPL (second program loader) are bootloaders with the purpose of starting up the kernel. There are no flash drivers needed at the initial loading stage since the CPU begins in a default state with a program counter set at 0, which is the memory address at which it begins execution. It then begins executing IPL instructions and progressing the program counter. The memory where the IPL is located is directly linked with the CPU data lines so that it can begin executing the IPL as soon as it powers up. The IPL performs a few low level initializations (i.e. sets up memory and loads SPL) and ends at a jump where it sends the CPU to execute the SPL. The problem is that with the wrong IPL, it doesn't know where to find the SPL, so it tries to execute gibberish and crashes.

In successful SPL bootup, the flash memory allocation and kernel are loaded into memory and the CPU is jumped to the start of the kernel.

Basically, the way to repair the brick problem is to rewrite either the IPL or SPL to a version compatible with the other. The kernel doesn't come into it at all.
[G1 Android Development] tanksta:
replace mobo?

can anyone confirm that replacing the motherboard on a bricked g1 with a working one fixes the bricked hardware...

:o

thanks
[G1 Android Development] DirectMatrix:
Should work like a charm as far as I know.
[G1 Android Development] scholbert:
If your car is broken because the engine is broken and you buy a new engine the car should drive again. As far as you are able to drive ;)

Of course there are many reasons why it still won't do it's job.

You may ask the mechanic :p

Regards,

scholbert
[G1 Android Development] rosciio:
hello I'm italian boys.

I read your post but I am not clear if anyone was able to unlock an htc g1. I have a htc g1 blocked groped and I want to weld the wires to the jtag but I did not understand how to do

Can you help?
[G1 Android Development] linuxhall:
Hello,

Someone can fixed it (rmb/cny: 550),

http://www.baijiaxin.com.cn/news_207.html

http://www.androidin.net/read.php?tid-6029-fpage-0-page-1.html

But G Sesnor will not work after debrick.
[G1 Android Development] Cuore_alfa:
Guys... i just remplace the motherboard of my G1 because the H. SPL corrupt my phone, Go to ebay and grab a cheap broken phone.

And AVOID installing unsafe wanna be cool Roms from 'developers' because most of them are full of bugs or push you G1 to the limit, and they don`t worth it, if you want to make your G1 looks c00l try to update the phone Theme, the 98% of the people that actually flash their phones with theses roms don`t really need all the crap that they claim to do.

I update to cupcake 1.5 and T - Mobile send the CR1 update the phone work great and i`m just downloading apps from the market, be aware!
[G1 Android Development] dman977:
First off, thank you for that awesome explanation. ;)

The way I was perceiving things, I thought the key-presses were being ignored completely. As you explain it, the IPL starts up, but then the system crashes when it tries to hand off the boot process to the SPL. But, since the SPL is what we use to load in a modified SPL, we are SOL unless there is some way to re-flash the SPL without having a working SPL.

What I still don't understand is what the radio image has to do with this. Am I looking at this wrong, thinking the radio image has anything to do with the cellular radio? If the radio image is actually the IPL, that would make loads more sense. That would make the new radio image backwards compatible with the old SPL, but the old radio not compatible with the HardSPL. Makes loads more sense if this is correct.

Also, if the serial and usb are controlled(or drivers loaded) by the SPL, then I see why the JTAG connections are the way to go.

One last thing.... are the key-presses to get into the SPL actually part of the IPL? So the key-presses are recognized by the IPL, which tells the SPL to start the bootloader, recovery, fastboot, or reboot?

Sorry if I am asking loads of questions. I am just trying to figure things out. Just thinking in the think tank. :D

Thanks in advance.
[G1 Android Development] lbcoder:
It's actually both. Think of it as an initialization routine for the radio hardware that, upon completion, hands off control to the SPL.

HardSPL is a slightly modified (uselessly modified) EngineeringSPL and is compatible with ALL IPLs. HACKED-SPL is something else entirely and is what is not compatible with the old-IPL.

USB is definitely useless. RS232 though...? I have a theory that the blue-led mode does *something* -- perhaps something with RS232.

Don't know, doesn't matter since even if the keypresses are passed to the SPL by the IPL as parameters, it doesn't help with the fact that the SPL won't work.... except for that mysterious blue-led mode........ not sure what's up with that. I think its trackball+power that does it.
[G1 Android Development] dman977:
It seems as though maybe this puts the G1 into a loader state. What can be done with that, I have no idea. I think it may be a loader via CMOS since we are getting 2.3VDC from the ExtUSB connector. You do have Tx/Rx connections to a UART from pins 8 & 9. Once again, I am spitting out suggestions. I in no way claim to know what exactly I am talking about, but hopefully I will learn.

ExtUSB pinouts - http://www.telesphoreo.org/pipermail/g1-hackers/2009-May/001281.html
[G1 Android Development] wmantly:
about that blue LED...

Maybe the blue LED is stating that it's in some sort of TFTP mod. Isn't that how older HTC phones got flashed? I know nothing of how to set up an IP connection over USB, but if someone knows maybe we can solve this issue!
[G1 Android Development] kylebrodeur:
I've flashed this before and it worked...I used the same procedures again on the same phone now it doesn't work what do I DO? it stuck on TMobile G1
[G1 Android Development] rosciio:
thanks, but speaking in Chinese or Japanese. the fact is that I still do not know if it was already a sbriccato htc g1 or you are still working
[G1 Android Development] bertrandno7:
hello i learned chinese b4 its seem to be impling that the two black chips shown in the pics need to be replaced with one from a working phone. after that one can flash the rom in and then replace the new chips in the "bricked" phone with the old chips and things can work.
[G1 Android Development] dman977:
On one of those links, the one picture is not even a G1.
[G1 Android Development] lbcoder:
Heh... if you swap the chips, then the chip you swapped OUT is STILL BRICKED, so you go from one mainboard working and the other bricked and reverse them... maybe. Could very easily break something in the swap and it doesn't accomplish anything since since you will have one working and ONE BRICKED.

And it definitely does NOT need both swapped, only the one where the SPL is loaded.

Also note: Impossible to swap out hot since the thing will instantly turn into a smoky mess.

Oh, and regardless of how you look at it, the replacement chip STILL NEEDS TO BE PROGAMMED, so there's no point in swapping anything.
[G1 Android Development] lbcoder:
After a translations, they want to replace the K5E2G1GACM, which is the FLASH/RAM chip. I think they are a reprogramming service. You send in your chip and they'll send back one that they've already reprogrammed.
[G1 Android Development] rosciio:
è molto complicato farlo. ma io penso :

se è possibile riprogrammare il chip smontandolo e inviandolo allora sarà molto semplice aggiornarlo con il cavo jtag, o mi sbaglio?
[G1 Android Development] cl2eep:
Why is this thread in particular so attractive to people who don't speak English?
[G1 Android Development] henrylim:
I am a Chinese guy who is ok in both English and Chinese language. Let me attempt to translate.

The repair procedure:

1. Remove the motherboard from the bricked G1 phone.

2. Locate the K5E2G1GACM chip and remove it from the motherboard.

3. Use their special equipment to read the data off a good K5E2G1GACM chip from another phone, and write it into this chip.

4. Put the reprogrammed chip back onto the motherboard, and the motherboard back to the G1 phone.

Note:

1.Some G1 phones uses H8BCS0SJ0MCP or H522F1GACM chip instead, but they are in the minority. The repair cost will remain unchanged at RMB 550.

2. As there will be bad sectors in the chip, we cannot guarantee 100% repair success. However, we have not encountered any failures in our repair jobs yet.

3. Your "Gravity Sensor" will failed. We are unable to resolve this glitch at this point in time.

Note by translator:

1. There is no "gravity sensor" in G1. I suppose the author is referring to the accelerometer.

2. By "special equipment", I reckon the author is referring to chip reader and writer equipment.

3. The G1 motherboard diagram I found in other websites (may be useful to you):

EDIT: Goto http://www.hiapk.com.cn/read.php?tid-6478-keyword-NAND.html (chinese Android forum site). It has some technical details on the layout of the K5E2G1GACM chip.
[G1 Android Development] rosciio:
I am a Chinese guy who is ok in both English and Chinese language. Let me attempt to translate.

The repair procedure:

1. Remove the motherboard from the bricked G1 phone.

2. Locate the K5E2G1GACM chip and remove it from the motherboard.

3. Use their special equipment to read the data off a good K5E2G1GACM chip from another phone, and write it into this chip.

4. Put the reprogrammed chip back onto the motherboard, and the motherboard back to the G1 phone.

Note:

1.Some G1 phones uses H8BCS0SJ0MCP or H522F1GACM chip instead, but they are in the minority. The repair cost will remain unchanged at RMB 550.

2. As there will be bad sectors in the chip, we cannot guarantee 100% repair success. However, we have not encountered any failures in our repair jobs yet.

3. Your "Gravity Sensor" will failed. We are unable to resolve this glitch at this point in time.

Note by translator:

1. There is no "gravity sensor" in G1. I suppose the author is referring to the accelerometer.

2. By "special equipment", I reckon the author is referring to chip reader and writer equipment.

3. The G1 motherboard diagram I found in other websites (may be useful to you):

EDIT: Goto http://www.hiapk.com.cn/read.php?tid...word-NAND.html (chinese Android forum site). It has some technical details on the layout of the K5E2G1GACM chip.

Attached Thumbnails

Click image for larger version Name: igoogle_2.jpg Views: 3 Size: 75.0 KB ID: 208379

thanks for translation

is very complicated to do so. but I think:

if you can reprogram the chip disassembling and then sending it will be very simple to update it with the jtag cable or I mistake?
[G1 Android Development] infamousrev:
Try connecting the phone to a linux kernel, and typ dmesg. The error code can give extra information about how responsive your phone.

From my experience, the fact that the computer sees a USB device means nothing yet. I once connected a usb camera that smashed and molten. Still it recognized it saying error -71
[G1 Android Development] dman977:
G1 uses USB3316 for USB communication

Having said that, I was able to find schematics for the SMSC USB3316 that is used in the G1 for data transfer. The pdf file is here (SMSC USB3316). There is a Carkit UART mode for non-USB serial data transfers. Although, this may be a problem, "In USB UART mode, the USB3316 DP and DM pins are redefined to enable pass-through of asynchronous serial data. The USB3316 can only enter UART mode when the user programs the part into this mode."

How this can be utilized, I do not know. I am not quite that smart. I am simply just trying to find the resources.
[G1 Android Development] R3nrut:
Alright, I'm back in the game thanks to asphaltor for sending me his brick to use for figuring out this JTAG interface. I'll post back once I have something useful to contribute. As always I will keep my website and twitter update as well as this thread with any new developments. Thanks again asphaltor!
[G1 Android Development] anglisano:
Please tell me my phone is not a brick...

***any positive feedback is greatly appreciated***

So im rather new to this whole scene as I just bought a G1 last week. I followed the steps to jailbreaking made easy and rooted my phone successfully. However, since I ran into trouble installing Hero SuperLite, I rooted my phone with cyanogen MOD and the phone then powered on fine.

After that, I was back to CRC1 and without (probably a mistake) downgrading to RC29 and then to RC33, I performed a wipe and tried to flash the new radio "ota-radio-2_22_19_26I.zip". I pressed Home+Back to reboot and my phone turned on to the Battery Screen...(the one with the arrow that loops and points to the battery).

I try to power on to the recovery utility but no such luck... just the same battery screen.

Am I f'd? or is there anyway I can recover??? PLEASE help me.. I know Im an idiot so please spare the ridicule. Thank you, thank you, thank you!
[G1 Android Development] Proxin:
-First, try turning it on and waiting a while for it to do its 'thing'. I get the battery screen (I think it's the battery screen... it has an arrow that loops over to a chip I think?) once in a while when I do certain changes to the firmware. Anyway, leave it sitting there while you go eat dinner or something, and if you come back and it's still there, try the rest of these.

-Try taking out the battery, putting it back in, then going to recovery again.

-If that doesn't work, try holding the Camera button and going into fastboot mode, just as you used to gain root access on your phone. If that works, you can get to RC29 via that DREAIMG.nbh you used for rooting.
[G1 Android Development] wiggy2k:
Hi all,

Im one of the stupid users who bricked his phone by flashing haykuro SPL without flashing new radio. Now my G1 wont start anymore.

It always stucks at the T-Mobile G1 Screen and no recovery mode runs. The Power+Camera / Power+Back etc thing does not function.

If ANYBODY has a resolution for our problem, PLEASE PLEASE let me know, Im missing my cute little T-Mobile G1 :(.
[G1 Android Development] lbcoder:
This is NOT the place to be complaining that you screwed up. This is the place to offer thoughts regarding solutions, i.e., this is a place to CONTRIBUTE TO THE DEVELOPMENT of the solution. If you just want to complain that you screwed up, go join one of the "help me I'm dumb" threads.
[G1 Android Development] skfalco:
Success

yeeeah at last my g1 is up and running :S but after unbrick by changing the motherboard the camera won't start and the down part of the phone behind the buttons is really hot when charging, also the battery is not charging =( it just stays red and won't charge, any help is greatly appreciated
[G1 Android Development] Deuces:
sounds like you missed some connectors or screwed up another board
[G1 Android Development] skfalco:
Success2

Yeah i guess so jaja i opened and reorder everyting again but signal is a little bit weak, can anyone tell me which board is the signal one or something like that? thanks
[G1 Android Development] lbcoder:
Heh... that is NOT an unbrick. That is a REPLACE.
[G1 Android Development] Cuore_alfa:
The signal if i`m not wrong is a cable with a round end, you can`t miss it, my phone is working like new with my 10.00 buck ebay water damage board :D
[G1 Android Development] IConrad01:
For those of you out there who borked up the Haykuro SPL update, and now can't boot your phone...

I fixed my issue w/ this by turning it on, and using the adb shell to mount the sdcard. ( " # mount /sdcard " ). From there, I was able to flash the update by rebooting into recovery.

I don't know if that will help you guys, but it worked for me.
[G1 Android Development] Jigga0o7:
The computer will not recognize a truly bricked G1. Otherwise unbricking would be somewhat easy.
[G1 Android Development] R3nrut:
whoa, deja vu!
[G1 Android Development] letropezien:
says if you like a tutorial
[G1 Android Development] dr.frankinfurter:
Any closer?

Is anybody working on this?
[G1 Android Development] rosciio:
it says it is successful, then no longer feel?
[G1 Android Development] Fiireball32:
is there any way you can use the android sdk to unbrick
[G1 Android Development] lbcoder:
You would be best off spending a little time reading up on what an SDK is...
[G1 Android Development] tanksta:
replaced mobo but still stuck on g1 screen

i bought a busted g1 from ebay and replaced the motherboard but its still stuck on the g1 boot screen.

the phone was bricked when i tried to apply spl without the radio update.

is there a separate daughterboard that i need to swap out?

:confused:
[G1 Android Development] Deuces:
you probably bought someone elses bricked g1. i bought a "broken" g1 on ebay and someone had already opened the device and screwed around with stuff. was weird because the void seal was still intact, but i could see "pry" marks around the casing
[G1 Android Development] tanksta:
you are right about someone having screwed around with the phone. all the screws had scuff marks and UMTS cable was pinched under the motherboard.
[G1 Android Development] dr.frankinfurter:
Question

Is anybody still trying to find a solution to 'unbricking' a G1 with a damaged SPL? I would do it myself but I simply do not know enough. Is the JTAG option still being looked into?
[G1 Android Development] lbcoder:
Yes. Yesterday, a mainboard arrived from gospeed.racer. I've popped off all the covers and there seem to be plenty of easily accessed test points on the board and very near to the CPU. I *suspect* that the contacts to the immediate lower left of the CPU are the jtag points, but I will have to look into it in more detail over the next little while. Note: I am not going to be giving any definite time schedules for this since I do have other obligations that take priority.
[G1 Android Development] dr.frankinfurter:
I have a question. Does the the SPL work like a BIOS of a motherboard? And would the JTAG debugging method sort of work like flashing a BIOS chip? So, I heard that when some one opened the G1 they could not find the pin layout in order to do the flashing (innuendo intended). Has anyone else tried this? I do not know much about embedded devices as I am only a desktop developer. I do tinker from time to time with electrical circuits but nothing major. How hard would it be to open up the phone, and with some online knowledge gathered about JTAG debugging, you know... fix it?
[G1 Android Development] dr.frankinfurter:
I'm sorry, by BIOS chip I meant the CMOS chip if that confused any one.
[G1 Android Development] zoid_99:
Bricks are not much fun to play with....
[G1 Android Development] dr.frankinfurter:
Would something like this work IF the pin layout was found?

http://xdaforums.com/showthread.php?t=391047

Am I on the right track to finding out the layout by looking at this?

http://wiki.xda-developers.com/index.php?pagename=WallabyJTAG
[G1 Android Development] fabioccoelho:
G1 - Bricked (Continental European - Germany)

Hi all, i have a big problem.

I try update my hardspl and my phone has bricked. Somebory know as recovery ? Please, i need....

The keys Camera + Power Button and Home + Power Button not work and my phone frezze on boot loader.

Regards.

:( :confused:
[G1 Android Development] lbcoder:
Actually, BIOS was correct.

CMOS is not.

* so you see that the data stored in CMOS SRAM was simply the user configuration data (which these phones don't have at the bios level), and that CMOS SRAM is no longer even in use for BIOS storage.

But to answer your question more directly... the IPL (radio) is more like the BIOS. The SPL is more similar to a bootloader (GRUB, LILO, etc.) **THOUGH I have to admit that the lines between the various levels of program loaders are blurring these days. For instance, with some BIOSes, the bootloader (or even a Linux kernel !!!) can be shoved right into the BIOS flash payload. Coreboot does this for instance.
[G1 Android Development] lbcoder:
Yeah, thats the idea!
[G1 Android Development] lbcoder:
This is not the place to complain that you screwed up, this is the place to contribute useful ideas in the development of the brick solution.
[G1 Android Development] mohsinkhan47:
i got 2 idea

First idea

Why don't we learn how to read hboot and recovery images????? I asked cyanmod but he never answer backed and some other people tried and failed. So now what....

Idea two

There is a way for the sdk on the computer to flash. All u have to do is get the sdcard running on it and install a file manager apk on it... I am trying going to see if that is possible on sunday. I will try to post my results.

-----------------------------------------

PM me at mohsinwithglasses@gmail.com
[G1 Android Development] stuff:
I hope to god you miraculously get this to work.
[G1 Android Development] Deuces:
Devices that are [TRULY BRICKED] cannot be accessed via ADB, USB, or SDCARD. This is because on a [TRULY BRICKED] device the components to access USB or SDCARD are

not

loaded, which is why we cannot recover via ADB and/or CardReader.

I believe, even if you are able to get some type of "fix" onto the SDCard, the screwed up SPL will not load the SDCard before the device fails(aka stuck at g1 logo).

So far, the consensus seems, that only a direct chip access via Blue-LED mode or JTAG is a possible Un-Brick solution.
[G1 Android Development] magicman1987:
do i have a bricked phone?

i have a rooted g1, on jf 1.43 rc9 (uk version), i can get to the home + power, and camera + power menu, but when i turn the g1 on, i get the tmobile g1 screen, and it doesnt go any more past that, it just freezes on a blank screen,

does this mean my phone is bricked?

is thier any way i can reflash it?

i did a wipe (alt+W) and then i ive tried to update the older dreaming-rc7, but it didnt make no difference, still get a blank screen after the t-mobile g1 logo.
[G1 Android Development] R3nrut:
I have received a bricked device and will begin working on the JTAG where I previously left off. Just to recap, I have constructed the cable and have the software necessary to execute the reprogramming, however, I do not have the connection points mapped on the mainboard to try this. Again, if anyone has information about the MSM7201a chipset and the pinout mapping please pm me or contact me from my site.

Thanks to asphaltor for the device... I'll do my best.
[G1 Android Development] dr.frankinfurter:
Thank you Ibcoder for the clarification and thank you R3nrut for your efforts to help us find a solution to this problem. Too bad I don't know much about embedded devices or circuitry and such then I could find a way to contribute.
[G1 Android Development] bassbox:
latest radio, spl, and cyanogens 1.4recovery

fresh formatted and partioned 8gb sd, fat32, ext3, linuxswap

clean install of maxisma v2.1 (or any other rom i tried so far...) :-/

see attachment. stucks at first G1 Tmobile screen.