yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] DemoShadow:
if we can access the spl within the blue led mode we could put a nbh inside the card and it should unbrick the device. installing both a new system data and radio and spl. but if it is doing this it would defeat the purpose of the spl bricking our devices. give me proof of the blue led mode accessing the spl and i will further investigate.
[G1 Android Development] soloxp:
It does NOT work.
[G1 Android Development] Geniusdog254:
No one said that it would allow access on a bricked device. However, it does provide a little more insight into blue light mode. Like etjazz001 said, it appears to be a hardware mode, not SPL, which means it must activate something.

I don't understand why it would begin to boot into regular mode while still on blue light. I will look at an ADB logcat of booting like this.
[G1 Android Development] etjazz001:
SPL while blue led mode

geniusdog:

for my Haykuro's brick it does only stay in the first G1 screen fixed.

But I have a new theory:

I think blue led mode is done in primary boot level (hardware one) and comunicate with the device that controls the color led.

When SPL load it seems to ignore the status of the led for a while, but in an unbricked phone the software switches it off when it gains control of it again.

The proof can be that if you plug the power connector to charge with red led and you power up the phone you will see the same behaviour with red instead of blue.

This shows that blue led mode is something hadrware that resides in primary bootloader and it must be controlled by SPL software or simply it may be finished before SPL is started.

etjazz.
[G1 Android Development] Geniusdog254:
Here is my theory about it:

The IPL (radio) contains all the codes of what to load depending on what button you press (i.e camera, home, trackball). It then loads whatever mode you select.

When you brick the device, when you try to load SPL the radio doesn't know how to talk to it, causing the freeze. Since the SPL loads the main Android OS & the Recovery partition, no SPL means no boot.

But, Blue LED mode is in hardware, as you said. Since it requires no SPL it can run straight from the IPL. It has to have a hardware based function in theory as they wouldn't just build it in with no purpose. This in theory should be something like JTAG or some other flashing method.

We don't even know how Android is installed at the factory yet. We need to understand these things before we can truly get a solution to the problem.
[G1 Android Development] etjazz001:
SPL while blue led mode

Probably you are right, Do you know that IPL is loaded before SPL?

The strange thing is that I can't reproduce the SPL while blue led every time I try, I can not figure out the exact procedure and timing that produce it.

Are you able to do it anytime?

etjazz
[G1 Android Development] 2600xt:
Maybe if the blue led mode could somehow allow a jtag solution through the usb cable (and some specialised computer program) :confused:
[G1 Android Development] dodox:
Is there somebody trying to find JTAG pinout? Do You need help how to remove CPU from board?
[G1 Android Development] LeonardoFloripa:
Well...

Thos guy tried to JTAg the Dream.. And failed:

http://r3nrut.com/?p=124

and got some good links:

http://r3nrut.com/?p=1

Sorry, the ppl commented about him before..

RTFF... [:)]
[G1 Android Development] LeonardoFloripa:
More on the blue led mode...

Searching at FCC (fcc.gov) by the ID NM8DRM you can see details on the Dream .

Go to internal photos, and see details on the beast.

Well, after some time, the big chip showing in the photo with the label "Internal of EUT - 3" gets hot. No too much, but noticeable hot. And at the same temperature.

Is this an interesting clue of just random babble ?

;)
[G1 Android Development] Geniusdog254:
I am able to di it at any time. And yes I know for a fact that the IPL is loaded before the SPL. The IPL is just the radio. Thats why the wrong radio bricks the SPL, since it can't talk to it right.
[G1 Android Development] nickL0V3:
Ok

HTC Dream with the danger SPL

FAT32, Ext4, and Linux Swap Partitions

ever since last night my phone has been hanging here:

#
- waiting for device -
#
I//system/bin/sh( 50): --- Welcome to Android/CyanogenMod!
#
I//system/bin/sh( 50): vm.page-cluster = 0
#
I//system/bin/sh( 50): --- Executing firstboot.sh
#
I//system/bin/sh( 50): --- Checking ext filesystems
#
I//system/bin/sh( 50): e2fsck 1.41.6 (30-May-2009)
#
I//system/bin/sh( 50): ext2fs_check_if_mount: Can't check if filesystem is mou
#
nted due to missing mtab file while determining whether /dev/block/mmcblk0p2 is
#
mounted.
#
I//system/bin/sh( 50): /dev/block/mmcblk0p2: recovering journal
#
I//system/bin/sh( 50): /dev/block/mmcblk0p2: clean, 100/244320 files, 70262/48
#
8281 blocks
#
I//system/bin/sh( 50): cp: cannot stat '/data/app-private/*': No such file or
#
directory
#
I//system/bin/sh( 50): cp: cannot stat '/data/dalvik-cache/*': No such file or
#
directory
#
I//system/bin/sh( 50): +++ Apps-to-SD successfully enabled
#
I/logwrapper( 50): /system/bin/sh terminated by exit(0)
#
I/vold ( 120): Android Volume Daemon version 2.0
#
I/DEBUG ( 121): debuggerd: Sep 3 2009 18:06:09
#
I/vold ( 120): New MMC card 'SU02G' (serial 1086593150) added @ /devices/pla
#
tform/msm_sdcc.2/mmc_host/mmc1/mmc1:e624
#
I/vold ( 120): Disk (blkdev 179:0), 3970048 secs (1938 MB) 3 partitions
#
I/vold ( 120): New blkdev 179.0 on media SU02G, media path /devices/platform
#
/msm_sdcc.2/mmc_host/mmc1/mmc1:e624, Dpp 3
#
I/vold ( 120): Partition (blkdev 179:1), 2931640 secs (1431 MB) type 0xc
#
I/vold ( 120): New blkdev 179.1 on media SU02G, media path /devices/platform
#
/msm_sdcc.2/mmc_host/mmc1/mmc1:e624, Dpp 2
#
I/vold ( 120): Partition (blkdev 179:2), 976563 secs (476 MB) type 0x83
#
I/vold ( 120): New blkdev 179.2 on media SU02G, media path /devices/platform
#
/msm_sdcc.2/mmc_host/mmc1/mmc1:e624, Dpp 1
#
I/vold ( 120): Partition (blkdev 179:3), 61844 secs (30 MB) type 0x82
#
I/vold ( 120): New blkdev 179.3 on media SU02G, media path /devices/platform
#
/msm_sdcc.2/mmc_host/mmc1/mmc1:e624, Dpp 0
#
I/vold ( 120): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mm
#
c1:e624/block/mmcblk0' for mountable filesystems for '/sdcard'
#
I/vold ( 120): Aborting start of /sdcard (bootstrap = 1)
#
I/vold ( 120): Volmgr not ready to handle device
#
D/vold ( 120): Bootstrapping complete
#
E/flash_image( 127): error opening /data/recovery.img: No such file or director
#
y
#
D/AKMD ( 129): akmd 1.6.6 START
#
D/AKMD ( 129): library version: 1.2.1.1129
#
E/RIL Acoustic( 122): Fail to open /system/etc/AudioPara_TMUS.csv -1.
#
I/RIL Acoustic( 122): open /system/etc/AudioPara4.csv success.
#
I/RIL Acoustic( 122): acoustic table version: Dream_TMU_20090305
#
I/RIL Acoustic( 122): read_audio_para_from_file success.

on EVERY Cyanogen ROM I have been trying this morning. (going as far back as 4.0.4)

can ANYONE dignose this? Because I am without a phone until I get it figured out.

Ive messaged Cyan about it, but Im sure A LOT of people are messagin him with all of their lifes problems
[G1 Android Development] DemoShadow:
do you have a workable recovery?
[G1 Android Development] nickL0V3:
yep, Ive FINALLY been able to get JF 1.51 running, but the browser and gmail wont open, so Its a pretty temporary solution
[G1 Android Development] dr.frankinfurter:
Still no solution? Man, that kinda sucks. Guess I should start looking for broken G1s. A lot of appreciation to all who devoted their time to helping to fix the problem. Time to go buy a $100 broken phone. :eek:
[G1 Android Development] chevycowboyusa:
DREADIAG.nbh

I found this. Would be great if it helps...

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

I did some reading on this... and I'm totally confused. Maybe oe of you can get somewhere with this. the link to the file works. I dont know what MTTY or PUTTY is or how to use them.

Good Luck!
[G1 Android Development] Nismo300zx:
anybody? im not new to the g1 but i just briccked my new phone anybody get any progress?
[G1 Android Development] infernofalcon:
Some brainstorming

I am not a developer. I know nothing of development. These are just random ideas I had. I have absolutely no clue what I'm talking about. If I'm being stupid, please feel free to tell me to STFU.

-

So I had some harebrained ideas today, and thought somebody might want them.

First of all, when a g1 is bricked, is it that we CAN'T run anything, or we just can't get somewhere where we are ABLE to run anything?

Also, when they're hanging at the g1 screen, is it just hanging at the first screen, or does it actually go to the g1 screen? Could we replace the g1 screen with an interface to somehow flash a different SPL? So, like, completely replace the g1 screen with a recovery screen - would that be possible? If so, would it help?

These ideas wouldn't unbrick anything, but assuming all that would work, it could prevent future phones from being bricked. Especially if proven stable, was included in cyanogen, and other such roms.
[G1 Android Development] DemoShadow:
When you are truly bricked you cannot doing anything but turn you device on and access the blue led mode. That is it, no running scripts, no applications, no solutions. Until we can think outside the box we will never unbrick our phones.

And about the blue led mode :

we don't even know if that is even useful cause it does nothing
[G1 Android Development] infernofalcon:
So there's more to it than simply not being able to get past the g1 screen? =\
[G1 Android Development] Geniusdog254:
Exactly, you can't get to recovery, SPL, fastboot, nothing. We have tried just about everything and if we had jtag then we could get these unbricked most likely but we can't get the jtag pinouts, we already have the software & cables.

I personally believe blue led mode is useful for something but i don't know what.
[G1 Android Development] infernofalcon:
Darn!

Did everyone give up on the J-tag solution?
[G1 Android Development] infernofalcon:
boot from sd?

spl2sd?

non-handheld computer is to live cd as android is to livesd?
[G1 Android Development] DemoShadow:
dont double post.

you should read fully both this tread and the "brick" thread.

[evil thoughts][/evil thoughts]

just read them all the way through and post your thoughts
[G1 Android Development] Nismo300zx:
i just bricked my phone and about to send it to htc for warrenty repair. Would the brick be considered hardware damage...or u think they will find me responsible and make me pay for the repair?
[G1 Android Development] infernofalcon:
So has it been proven that if you flash the newest radio then spl you will NOT brick?
[G1 Android Development] Nismo300zx:
yea pretty much
[G1 Android Development] infernofalcon:
can anyone else confirm this?
[G1 Android Development] b0ricuaguerrero:
just bricked my phone after installing latest spl :mad:
[G1 Android Development] kiiiiiid:
I bricked my phone by updating SPL. But the Radio was updated before.

I updated the Radio then after a few weeks updated the SPL to reflash to Jachero.

I thought every thing is right but it bricked.
[G1 Android Development] R3nrut:
Just say that you were updating the ROM as specified by Carrier/HTC website and everything went fine. You rebooted and nothing happened.

DO NOT TELL THEM YOU MESSED WITH THE SPL.

Should be fine.
[G1 Android Development] R3nrut:
Self-Help and a JTAG update

If you like your phone, do not upgrade to the latest SPL. If you desire the who Sense UI so badly that you'd risk bricking your phone try this>

Get CyanogenMod-4.0.1 (Stable)

Get a theme that looks like Sense UI

Get Weather Widget - Donate from the Market

Weather Widget will give you the flip down clock and weather forecast. I am very pleased and happily forked over the money for this widget.

_________________________________________________________________

JTAG Update

I've spent countless hours now trying to rip apart a donated MSM7201A processor from the G1's main board. I've put the project on hold briefly for the birth of my daughter but I will be digging right back into it once things settle down a bit. (Once the In-Laws stop sleeping in my work area)

I've posted tid-bits of information and even stated that I had given up once on my blog but I've gotten some more information that has brought new light to my efforts. Once I get the processor scraped off the board I will update my site with new magnified photos. Hopefully some more progress will be made by then.

:cool:
[G1 Android Development] infernofalcon:
Awesome. Too bad I can't use this theme, though :\ http://xdaforums.com/showthread.php?t=555155
[G1 Android Development] Nismo300zx:
thanks but what about when they see the remnants of the failed spl update and updated recovery image?..or would this not matter?
[G1 Android Development] DanDroidOS:
my buddy sent in his bricked g1 and they didn't know:) I don't think they test them;)
[G1 Android Development] infernofalcon:
My new g1 came in the mail today.

I'm up and running cyanogen again, but I won't be happy until I can use the danger spl...*facepalm*

Having a pvt board, and having latest radio - any other things I can do to minimize brick chance?
[G1 Android Development] R3nrut:
They don't have engineers looking at returns, just someone to see if the thing will boot up or not. I've returned my ADP1 twice already without a problem.
[G1 Android Development] R3nrut:
Why can't you use that theme??
[G1 Android Development] infernofalcon:
Because it requires the danger spl, and the version that doesn't is broken =l
[G1 Android Development] Nismo300zx:
oh man you just shed light to this whole thing for me man...i did not wanna shell out another 300 for a g1...im bout to call htc for a RMA right now lol

edit---i just talked to a htc rep and they said that its a 9 out of 10 chance i would have to pay for the repair cuz they consider tmobile to b a 3rd party which would then cause the phone not to be covered under warrenty.. now $155-360 to fix the phone is just too much..and its money i dont have...what you guys think?
[G1 Android Development] lbcoder:
I think that you are missing how absolutely DEAD SIMPLE it is to NOT NEED the deathspl... all that this SPL does is it MOVES STUFF AROUND. You can do the SAME YOURSELF. Take your preferred system image, and move some files out of the /system partition into OTHER partitions, and just symlink to them! Problem solved withOUT bricking.

I.e., even without touching the /cache partition, if you are using apps2sd, then you probably have, what, 40-50 MB available in /data? Push some of your /system junk in there and symlink to it!!!!

If you want to get fancy, use a kernel with loop filesystem support. Create a couple of files in /cache -- /cache/cache.img and /cache/systemapp.img, format them as ext3, change the mounts so that you mount /cache at /cachehack, /cachehack/cache.img at /cache, /cachehack/systemapp.img at /system/app. What does that do? It recovers the space wasted at /cache and gives it over to /system/app.

You could even do other simpler things, like remount /cache at /cachehack, and simply creating two directories in there -- /cache and /systemapp and symlink /cache --> /cachehack/cache and /system/app --> /cachehack/systemapp.

I really would like to reiterate that there is ABSOLUTELY NO ADVANTAGE to using the deathspl! The only thing you accomplish with it is to risk bricking your phone! There is NO NEED to take this risk.
[G1 Android Development] alritewhadeva:
agreed with ^. You can ask the ROM maker to include script to symlink or you can create script yourself
[G1 Android Development] R3nrut:
That sucks. I have the ADP1 that I got from Brightstar. My warranty was valid through them.
[G1 Android Development] Nismo300zx:
yea man...so idk what to do now..im pretty much screwed then cuz 150-300 is too much to fix a phone..damn

any1 buyin bricked g1s?
[G1 Android Development] infernofalcon:
What about hero roms? Don't they need the dangers spl?
[G1 Android Development] lbcoder:
Why do I bother with all the typing? Did you read it?

Answer: OF COURSE NOT!!!
[G1 Android Development] infernofalcon:
Mmkay, thanks and sorry.
[G1 Android Development] snakebitezz:
delet this post

please delete this post as i missed a few pages in the thread
[G1 Android Development] LeonardoFloripa:
Can anyone try...

.. to follow this instructions :

http://www.instructables.com/id/Android_G1_Serial_Cable/

that R3nrut posted on his blog and see if there's any activity on the USB port while the G1 is in the darn "Blue LED Mode"?

I'm curious...
[G1 Android Development] ghilgames:
Battery out during flashing

Guys,

So stupid: was flashing CyanogenMod 4.1.999 and had phone on my lap, hooked up via USB to laptop. The battery cover wasn't on and disaster:

dropped the phone, battery came out DURING THE FLASHING!!!!!

Phone is dead, no G1 screen, no leds come on, hooked up to pc, plugged to mains, NOTHING.

DEAD AS A DODO!!

Who has a motherboard (working :D)????
[G1 Android Development] dopeking:
bricked htc magic

Hy

First of all... THANKS A LOT FOR YOUR WORK!

As a java-developter i'm not a big help to this project, but if i cant get the phone fixed on warranty, i'll be glad to send it to you.

As many others i successfully managed to get my htc bricked :eek:

I had cm-recovery-1.4 on it when i tried to flash the htc-radio-image (signed-dream_devphone_userdebug-ota-14721) for the new cyanogen 4.99 rom.

After the radio-update, the phone just shows the htc-logo and freezes. After a couple of minutes it stops showing the logo and a red light starts at the speaker of the phone (on top).

If i press the trackball while turning the phone on, there is no logo showing, but the light at the top of the phone turnes blue. :rolleyes:

I neider get access through fastboot nor adb. Putting a cm-recoverfy image on a fresh formated sd-card didn't worked as well.

... and jeahh... i know that the fun of playing with some new toys can have a price of bricking the device.... no risc no fun :D

Wish you all the best

dope
[G1 Android Development] newspeak:
I recently installed hero for the first time (KiNgxKxROM Version 1.6)

along with the current radio and the danger SPL...i played with it for about 2 days then tonight i was fiddling with the phone and it reboot on its own...went to the tmobile screen then went black...i didn't think anything of it and pulled the battery and now it is totally unresponsive...can't boot anything and the charging indicator light doesn't even come on when plugged in

the tmobile rep wants to send me a new battery so i am going in to the store tomorrow to prove it was the "donut update" that did it rather then the battery

i just wish i was at home when it happened i might of tried seeing if i got a response from adb rather then pull the battery
[G1 Android Development] RC4:
Can someone do something with this datasheet of the MSM7200A (maybe pin compatible) maybe to make a JTAG.

http://www.box.net/shared/etsai78xa2
[G1 Android Development] ghilgames:
Has anyone sen this? it could help...

http://repair4pda.org/handheld_jtag.html

http://tuxmobil.org/linux_jtag_tools.html
[G1 Android Development] ghilgames:
USB to serial board

http://www.coolcomponents.co.uk/cat...d=100&osCsid=85a8f25beec13bdf3d3042aded0c69fb

and

http://www.coolcomponents.co.uk/catalog/product_info.php?products_id=266
[G1 Android Development] R3nrut:
The only piece of the puzzle I have left to find is where the physical pin outs are on the board. As some may already know, I dissected a MSM7201a and then caught it on fire to see if I could get the processor off the board. This led to a chard remain with little useful information to gain. If I can find the board, which was misplaced by my mother-in-law during her invasive visit to help with my newborn daughter, I will post the burned remains in pictures on my site. Until then, I'm waiting on another donated device to arrive for more experiments.

So far here is what I have:

80-VA736-2-MSM7200-SoftwareInterface.pdf

80-VE263-25-MSM7200A-BasebandTopics.pdf

SECJTAG FLASH(SJF) USER’S GUIDE for the S3C2440 RISC MICROPROCESSOR which has detailed schematics for a couple JTAG dongles

ti_20278.pdf from Semiconductors Insight which contains a die photograph of the MSM7201a applications processor.

http://r3nrut.com/android/jtag/bottom_of_msm7201a.png

http://r3nrut.com/android/jtag/msm7500iv0.jpg <-- a die photograph of the MSM7500

Completed schematics and hardware design for JTAG interface with is based off several LPT to JTAG solutions I've pieced together. I have a second design I need to build that is USB to JTAG.

http://r3nrut.com/android/jtag/LPT2JTAG.pdf

Pictures of the constructed interface are on my site.

JTAG code and executable for the HTC Dream (thnx to daproy)

JTAG PIN configuration

http://r3nrut.com/android/jtag/JTAG_Adapter_IC.png

JTAG PIN points on the physical MSM7201a chip

http://r3nrut.com/android/jtag/JTAG-PIN_Config.ods

TLMM Architecture wireframe

http://r3nrut.com/android/jtag/TLMM_Architecture.png

**to clarify: my intention was not to set the board on fire, its just what happened when I cooked it in a gas oven.

**If anyone wants something I listed on here but didn't supply a link to, please contact me by email and I'll post a RapidShare link. The DreamJTAGcode.rar file is about 125MB.
[G1 Android Development] R3nrut:
Here is a thread I found interesting. Maybe some of you software guys can look into this? I'm not sure there is anything we can extract from this project to help but I'm open to any thing at this point.

http://xdaforums.com/showthread.php?t=559380
[G1 Android Development] B-man007:
The thing is that that mod requires a special kernel, which needs to be on the phone before its bricked, and I'm pretty sure its not even making it to the kernel
[G1 Android Development] R3nrut:
yea... you're right. i'm just sick with desperation. :eek:
[G1 Android Development] BinaryDroid:
I'm going to have the Jtag test locations posted tonight so someone can test if they can access the port. im also going to try to connect to it myself but the phone that i yanked the chip from was a spare board so i'd like to keep the CPU off until we can verify this works before I put the CPU back on. dont want to try to connect to my main full working phone just yet lol.
[G1 Android Development] R3nrut:
How did this work for you? Any updates???
[G1 Android Development] lbcoder:
LOL. Look at when he posted that message. He said "tonight", and you asked for updates only a HALF HOUR after he posted that... Be patient, wait until tomorrow *at least*.
[G1 Android Development] lbcoder:
You sure that it was due to flashing and not due to the drop?

CM has no business flashing the radio or SPL, and in fact, reading the update-script in his update.zip, he does NOT flash the radio or SPL (which aren't even included with the file), therefore I can't see any possible way that it *could* brick your device given what you've said.

I believe that you are actually premature in looking for a replacement mainboard. Take the thing apart and look to see if anything is disconnected or obviously broken. Maybe the LCD ribbon?