Database Develop

SD Card Reader Bad!

I recently dropped my G1 from a fairly high location, luckily it still works (for the most part). It seems that my SD Card reader is malfunctioning. I have tried 3 different card 2 x 1GB & 1 8GB card, I've gone through all three cards making sure they are recognized by the PC and have reformatted them and still nothing. I've also tried taking out the battery for awhile and restarting the phone with no SD Card and then inserting a card after the phone boots, no luck. Also I have not been able to mount from console, so I'm left to believe that the reader is toast. I believe I can get my phone replaced from T-Mobile using their warranty service, but I am apprehensive about sending in a phone that's been modded. So I'm wondering if it is possible to restore the original SPL and software without a SD Card, possibly using adb or some other method?

is there no physical damage to the case from the fall? If there is tmo will call it abuse and call the HTC police.

No, no physical abuse from the fall, I had purchased the body glove case that surrounds it and it did it's job. Phone still looks new, and the white dot near the battery is still white. So I believe they'll exchange

I'm still tryin to figure this out. I'm thinking that I may be able to do this with fastboot, but the only nandroid backups I have were made with cyanogen roms and themes. Does anyone have the defualt sytem.img boot.img & userdate.img files so I can test this theory??

Unrooting/Restoring G1 Without An SD Card
Well after quite a few hours of searching I ended up successfully Unrooting/Restoring my G1 for warranty purposes without the use of an sd card. I found quite a few posts regarding the same thing, but none with the answer. So I decided to share what worked for me with anyone else who may come across the same problem. My terminology may not be exactly proper but bear with me.
*** I take no responsibility for what you do with you're phone, theese steps worked for me, but I cannot guarantee you the same resulsts***
*** I had Haykuro's SPL installed and was able to use fastboot by booting into the bootloader using camera + power. You need to have a bootloader that has fastboot either Hard/Engineering/Haykuro (Danger) & be able to use fastboot on your PC, see here if you need help setting up fastboot to work on your PC ***
Some of these steps are redundant but I did it this way because without the use of an SD card I wanted to make sure I still had access to a modified recovery or fastboot incase something goes wrong.
1) Download the necessary files from here
*If you were wise and created a NANDroid backup before you started installing custom ROM's (which I wasn't). You can skip the download and use you're own files.
Nandroid Recovery Folder contains system.img, recovery.img & boot.img from freshly rooted G1
Original Recovery Folder contains just that, the original recovery image shipped with the G1
Original SPL Folder contains you guessed the original SPL
2) Open up your terminal of choice and change directory to ~\G1 Restore\Nandroid Backup\ from the archive you just downloaded
Now run each of theese commands
Code:
fastboot flash system system.img (enter)
fastboot flash boot boot.img (enter)
Optional: This will overwrite your recovery with Cyanogen's Recovery Image, you can skip this if you already have it, or if you are using Amon_RA's and do not want to switch over to Cyanogen's
Code:
fastboot flash recovery recovery.img (enter)
At this point I rebooted my phone to make sure that everything loaded properly. If everything starts up move on to the next step
*Note at this point you still have Cyanogen's recovery and your SPL incase of failure
3) Now that we're happy that the original system has loaded up boot back into your bootloader (SPL (camera + power)) and it's time to overwrite Cyanogen's recovery with the original recovery. Change directory in your terminal to ~\G1 Restore\Original Recovery\
Code:
fastboot flash recovery recovery.img (enter)
Again I rebooted to make sure everything loaded correctly while we still have access to fastboot and can undo what we've done up to this point if necessary.
4) Change Directory into ~\G1 Restore\Original SPL\
Code:
fastboot flash hboot spl.bin (enter)
And now your phone is back in it's original condition minus the sd card reader that has failed and brought you to this guide. So at this point I'd go into your phone's setting's -> SD card & phone storage and choose to do a factory reset to clear all your data and get ready to return your phone
Hope this helps

Help!! Need to go back to original spl

I need some major help guys.... i need to send my g1 to tmobile but my only problem is i cannot seem to unroot. each time i get to the Grey and Blue screen it does not load, it says (loading no image)... then it goes back to the RAINBOW screen. im i doing something wrong? I have followed these steps. i would greatly appreciate your help.
I. Downgrade the SPL (If you never loaded a new SPL or are coming from a completely stock Donut G1, SKIP THIS SECTION).
1. Download the Original SPL:
Original SPL
2. Rename the Original SPL to Update.zip and place it (now named update.zip) on the SD card (not in any folder).
3. Turn off the phone
4. Turn on the phone holding Home and End key till the recovery screen pops up.
5. Hit Alt W to wipe the phone, then hit Alt S to load the update.zip
6. After the update is complete, press Home and Back to reboot.
7. Once the phone reboots to the G1 Logo, turn it off by taking out the battery. Then put the battery back in. *READ THE REPORTED ISSUES FOR A COMMON ISSUE WITH THIS STEP!
II. Load the DreaIMG.nbh File
1. Download the Original DreaIMG.nbh file:
Original DREAIMG.nbh
2. If the file downloaded above downloads as a .Zip file, please unzip it first then put the DreamIMG.nbh file that is inside on the SD card, NOT in any folder. (If you did Section I the phone is off still, take out the memory card, put it in the MicroSD adapter and plug it into your computer to transfer the file over, since your G1 won’t turn on right now if you did Section I above. Otherwise if you did not need to do Section I above, then you can just put it on the SD card normally using the usb cable and the phone).
3. Turn the phone off if it is on.
4. Turn on the phone by holding the Camera button and the End key until the bootloader screen turns on.
5. Hit the End key to start the update. DO NOT INTERUPT THIS PROCESS.
6. Once it is done, hit the trackball to restart the phone. You now are on the stock firmware RC29.

First step is posting in correction section(Q&A). Second step is using the search.

Read the damn rules for posting new threads or go away

i did!! n i still didnt get help from the thread that was posted by {tubaking]

Did you place the file DREAIMG.nbh on the root of your sdcard??

yes i did... i even tried with rc30 but it didnt work.
i keep getting stuck on the last step. i have cynogenmod.

You are pressing camera+power to get this done??

yes i am...
i followed all the steps correctly..for some reason it keeps messing up at the end when it gets to the grey and blueish screen.

And is your card formatted to Fat32. And did you check the MD5sum on the file to make sure it's the complete file.
Wow mikey on here helpin.

yes it is formatted
i don't know what that is..MD5sum

http://en.wikipedia.org/wiki/Md5sum

how do i check if the MD5 is a complete file>?

To see if a given file is valid, pass the output of a previous md5sum run with the switch -c. Thus, the following two steps occur:
1. Compute the MD5 sum and store it in a file using md5sum file > file.md5
2. Check for validity with md5sum -c file.md5
If file is not present, omitting the file parameter or passing a - reads from standard input
i don't understand smh

Just redownload the RC29 file again and retry it then.

would you happen to have a RC29 file for download? i've tired about 4 different files

afriican qwee said:
would you happen to have a RC29 file for download? i've tired about 4 different files
Click to expand...
Click to collapse
http://www.megaupload.com/?d=EMY1HIVU

its still not working

Is the file named DREAIMG.nbh and not DREAMIMG.nbh.

if your seeing a rainbow screen... your at the stock spl....
whats the error its giving you

when i get to the rainbow screen it goes to the grey and blue screen to do the last loading. all it says "loading no image" then it goes back to the rainbow screen within 10 seconds. and ill have to pop the battery out and restart my phone regular again...
do you think something is wrong with the ROM that i have?
im also wondering if i can change the ROM and try to unroot if it will work...
any suggestions?

What happend when I suddenly cant flash?

For about 6 month ago I flashed my HTC touch pro and everything works.
I have RapaelsHardSPL Unsigned 190_1_3.
When I tried to flash thruu ActiveSync I always get Invalid Model ID
so I tried this guide "[UPG][TRBL]How-to fix: Update/Flash doesnt work, stops at 0% or 5% (invalid model ID) "
But with no luck.
Then I tried to copy the NBH file to my memorycard and reset with volume down and reset button, the message then is no image file is found then it stopped and show a text that say "serial"
I also tried to copy the file to the internal memory of the phone but same thing happend.
Is the filename of the NBH file important?
I have tried alot of names I found in different guide but nothing have worked.
I have tried and tried for some days now and is out of ideas.
Can someone tell me what I could tried next...

Hi, to flash from your SD card the image should be called raphimg.nbh (for touch pro) and it should be located in the root of your SD card. Try it you'll be good

Now it works better but not all the way.
Volume down + reset then then it say "loading"
After that "checking"
The colourful rows are back and it say serial.
Is there something wrong with my IMG file?

Definitely something wrong. Get your carrier rom, or htc rom if the device is unbranded or a cooked one. Connect the phone to an usb port, press volume down+reset, start installation on pc.
Make sure your image is named "raphimg.nbh" and it is located in the root directory, while flashing you must not have the phone connected with usb cable

It also show this numbers: 00058002

I use this rom and get it working
[ROM][FR/WWE]TOUCH PRO[SENSE 2.5][03/2010] ۞ TOSHIRO_SERIE® ۞[Wm 6.5.2/Wm 6.5.5]
BUT I think it was read/write properties, I use linux and when I transfer the file to my memorycard it probably was writeprotected.
Could this be the problem?
And freakzone.... Big thanks for the help.

I have used ubuntu to transfer files, never had any problem.
Try flashing from pc.
You're welcome
edit: vol down+reset and then connect usb and start the customruu

[Q] Stuck at Padlock with X screen after repeated flash attempts

The title mostly sums it up, I have a Nexus One and unlocked the bootloader to install CM 6.0. I tried Amon's RA recovery image but kept getting file corrupted errors from the .zip files even after verifying the md5 checksums. I was able to get past that problem thanks to Fubaya in another thread pointing out that there are recovery images that allow you to ignore the checksums.
I have now been able to load ROMs from .zip off the SD card, but no matter which one I try (eViL's Sense, CM6, Kang-O-Rama or stock) or how many times I try it, I can't get it to load past the 'X' with the padlock screen at boot. It will sit there for about a minute, then reboot into recovery. I have wiped everything on the phone multiple times but no luck. It just sits there until I pop the battery out. Any idea's what could cause this problem? The recovery image does not show any errors and looks like it flashes successfully

the file corruption errors are a bit troubling.. have you tried re-installing the recovery before proceeding? perhaps the flashing itself is not being done correctly.
often times being stuck at the X can be fixed by wiping the dalvik-cache from recovery, but your problem might be deeper than that.
try putting on amonRA's recovery again and see if that makes a difference.

Uh yeah, you shouldn't be getting any checksum errors. Sounds like something isn't transferring correctly.
As I understand it as long as you have the recovery on there properly (you HAVE to install it correctly AND remove a few files if you're using the stock ROM otherwise it'll wind up at the stock recovery!) you'll "never" be able to brick your phone, with the exception of when flashing the radio apparently..
But flashing with corrupted files still doesn't seem like a great idea, so I'd figure out why this is happening. Can you pull the card out of the phone, put it in a card reader, and check the checksum with md5sum or whatever checksum the particular ROM used... md5 isn't very popular anymore, but it is fast and probably still used a lot for non-secure things, like verifying a transfer etc..

I've tried reflashing recovery multiple times and never seem to have a problem getting in there, either with Clockwork or with Amon. I also tried copying the .zip files back off of the SD card and re-checked the md5sum, it looks like the file is still unmodified so I have a hard time believing that it's corrupt. It does this with multiple SD cards as well, so I don't think its the card either.
I was able to get CM 6 to boot a couple times but the first time didn't seem to work right some error kept popping up that needed to be force closed over and over. So I reflashed and then was stuck in a boot loop with the CM logo. Since then, I have not been able to flash with anything.
Does this sound like some sort of hardware problem with the phone itself?

what radio are you running

4.06.00.12_7. I had Froyo running on here previously, and like I mentioned above, it booted into CM6 once but never came back after a second reboot. I tested and was able to make a call when it was running.

Flash the Recovery via ADB, not the SD card.
Do you still get checksum errors then?

I can't seem to get the phone to show up as an ADB device, I just get "device not found". After doing some reading, it looks like I did not enable USB debugging before flashing. Is there a way to enable this from recovery?
EDIT- Looks like the driver had uninstalled, I now have the driver back up and it shows up under ADB Device as being in recovery.
I copied the Kang-o-rama-1.0-Final.zip over via ADB and then tried to flash from SD Card from within Amon. It still shows E:Corrupt file: with a random file from within the zip as failing and then says verification failed.
Is it possible there is some sort of corruption elsewhere in the phone besides the SDCard that is causing these errors? It seems that whatever is causing the corrupt file errors (even though the .zip files pass the md5sum) is likely the root problem I am experiencing. Any ideas what else I could try to fix this?

Different SD card partitions?

Disclaimer: I'm relatively new to the realm of modding the the kindle. I have a 2012 7" hd. I rooted it and loaded a 2nd bootloader and recovery via various tutorials. I attempted to to load a rom (lolipop 5.1 and corresponding gapps). The process seemed to go fine and when it booted into android the initial setup screens appeared (connect to wifi etc); but then I got a message that the setup wizard had failed. I tried "skipping" screens etc and regardless of what I did I couldn't get past that screen. I clearly either did something wrong or didn't have a good rom file. I was an idiot and didn't create a backup before flashing the new rom. So I mounted it in recovery and loaded a factory image that way and flashed back to norm. My intention was to start things over. I rooted again, went through the whole process; however, I'm seeing a weird phenomenon. When I am in windows (or ES explorer for that matter) and access the files on the sd card partition...I can load files onto there (for flashing in recovery etc); however, once I am actually in recovery and go to "install" the partition that I view in recovery is the files I had from the very first flash. I can create new files in windows or ES explorer and everything works as expected....but once in recovery, none of those folders are present...and the only zip files that are available to "install" are the ones I used the first time that didn't work. I'm clearly looking at some other partition or image in recovery than I am in windows. I have cleared cache and everything I can think of (again I'm a complete amateur). Does anyone have a suggestion of what I am doing wrong or how to resolve? Thanks in advance.
Cranky

The issue with your first problem was that it could have been a bad gapps, in the future try different gapps if you see weird problems like that, to your second problem, when flashing lollipop on a device that had ICS it'll change the directory of the SDcard, no biggie though, just search in recovery data/media/legacy or data/media/0 it should be in one of those that your files are in.
Sent from my Nexus 9 using Tapatalk

Try this.
Try to send files over using adb whilst in recovery. If you do not know how then watch this youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.