Database Users

Stuck after flashing

Hey guys, I usually try to avoid asking for help because I can usually find several topics to guide me on how to do thigns, but today I find myself completely stuck. So here's my story:
A couple of days ago I was running cyanogen's 4.2.4 rom. I had ended up with some bugs like not syncing with gmail and it was giving me 3-4 hours of battery life while idle and everything turned off. The previous rom had none of these problems. Anyway, I heard about Dwang's and decided to try out v1.11 of his rom and loved it. However last night when I tried to flash to version 1.13 it froze on my rogers screen. My last nandroid backup was the one made on the cyanogen rom. I spent all day fiddling around trying to do everything to get anything stable to run and now tonight I ended up overwriting the nandroid backup and now it can't boot anything up other than the fastboot and 1.4 loader. I've tried wipes loading older roms, newer one (both dwang and cyanogen)
I don't wanna touch anything else for tonight in fear of bricking my phone but I'm hoping someone can help. It's not bricked, but I feel at this rate and how frustrated I am I have a feeling that might happen and I want to avoid it.
I know there are some other topics that may be similar because I've done a search but I'm not exactly 100% that the solution given to them might be used for my problem as well.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA210000)
CPLD-4
RADIO:2.22.19.261

Ok well, I seemed to have made things a bit worse somehow. Now when I hold camera+ home it brings up a triangle with an exclamation mark and a phone logo. BUT I'm still able to fastboot.

Did you boot on the ADP 1.6 ROM?

Yes I did as it was one of the steps on cyanogens wiki. I even tried to flash it without flashing cyanogen's rom and what it does is just show the android screen, then when it finishes loading it goes black for a split second and then goes back to the android screen. I managed to load older nandroid backups of cyanogen again but whenever I try to flash the 1.6 and then either dwangs or cyanogens it doesn't work. I also cannot do fix_permission at the recovery screen. it tells me something about e2fsck.

Here some of the things I've tried today on the phone without any success:
Another thread had a similar problem and one of the tips was to fastboot and do
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-RAv1.3.2G.img
so I tried that and now I am equipped with the ra recovery and when I try to flash the rom it still doesn't work. I also let it hang for about 20 minutes before trying something else.
I've also flashed it to 1.6 htc stock and it works but it doesn't let me have the proper recovery screen and whne I try to update with a renamed rom file it says installation aborted.
So now I feel stuck :-(

1.33.2005

Hi all,
I'm a complete newbie. Most of you will have little patience for me but I'm hoping to find at least a couple of you willing to help me out. Here's my story. I thought it would be cool to by a used HTC Magic from Ebay to use with AT&T. The guy that sold it to me put Froyo on it and I was excited to have the latest Android on the phone.
I got it yesterday and the trouble started quasi immediately. I will post the exact things that happened as well as I can.
1. First the phone was rebooting on its own. It would make it as far as the home screen with the icons but if I tried to press anything, like contacts, it would reboot.
2. Then it eventually took me to the recovery screen where, after reading several threads, I downloaded the newest (not ROM, but whatever the first thing is on that page that you can update it).
3. Then the phone stopped rebooting itself but I couldn't get to the market or email because the dumbass that sold me the phone hadn't wiped his user info. So I googled again and was told to factory reset.
4. I tried factory reset 3 times and it did nothing.
5. Went back to the recovery page to see if that had anything that would help and I clicked Fix Permissions and let it run that.
6. Still no change when it came to wiping his user info.
7. Got frustrated and googled again. This time I saw a thread that said you should reboot using the up/down key and power. Did that.
Since then, I've had a blinking HTC green screen. At some point during this process I made it to what looks like a basic OS window from which I copied the following information:
sapphire pvt 32b eng s-off h
1.33.2005
radio-2.22.19.261
apr 20 2009, 15:30:43
hboot
What do you suggest I do now? I emailed the guy who sold me the phone because I figure if he put it on there, he can put it back. Or at least send me the files. Not sure he will care or want to help me. Besides, doesn't seem like he got it right.
I am willing to try to fix this myself but I don't want to start downloading files and flashing the phone only to destroy it. Guidance is needed.
Thank you in advance.
Seelier.
Metuchen, NJ

If the device actually booting then you should be alright, just sounds as if the guy who sold it to you flashed it with something crappy.
1.33.2005 is your SPL version, and that particular SPL version is what's referred to as an "engineering SPL" which allows you to flash roms and custom recoveries via fastboot (basically). For more info you can read here , but it doesn't overly concern you now.
To flash any roms yourself (more easily) you will need a custom recovery such as Amon_RA's Recovery, which you can download in this thread. Follow his instructions. You may already have this but you didn't say so.
Once you have done so, I suggest you install a ROM such as CyanogenMod, which you can get from here. Again, instructions on how-to flash it are in his thread. Essentially though, it is as follows:
- Put cyanogenmod rom on your SD card.
- Boot in to recovery screen (press the ON button whilst holding HOME)
- Wipe data/dalvik-cache
- Flash .zip from SD card & choose the file you put there
- Reboot the phone and wait patiently
Edit: Just to reassure, the things that tend to "brick" phones are flashing SPL and Radio updates, which you don't appear to need to do. Flashing roms very rarely causes devices to break, it is usually just the rom at fault.

Not Development related. Moved to General.
OP, next time you post make sure you post in the correct section or I'll close the thread.

New Mytouch fender user, semi-bricked. Looking for help

Hey guys, I am a decently experienced android user (D1, D2, Eris, SGS, etc). But I seem to have run into a problem. I had rooted a friend of mines MyTouch Fender months ago, using some root app, I forget which, z4root or one of those.
Anyways, he came to me the other day because he got a new phone, and the MyTouch Fender is semi-bricked, im not sure what he did, he said he was playing with it and screwed it up. Anyways, the phone just stays at the Fender loading screen. I can access hboot, recovery etc. The phone is completely stock, 32A, S-ON Google, etc. So what would be the easiest way for me to get this phone going again? He's given the phone to me for free, and I would like to get it working to give to my gf to replace her crackberry curve.
If someone could point in the right direction that would be great. Unfortunately I have no idea what he did to break it in the first place. I've tried wiping data and cache via stock recovery to no avail. Is there maybe a stock oem update.zip that could be flashed via recovery that would flash it back to stock?
I do eventually want to mod the phone and probably throw CM6 on it, but for now I'd rather just bring it back to working stock. Unless rooting it and custom recoveries would be faster.
Thanks in advance.

It's certainly fixable, but I don't know about getting back to stock. The issue is that no one has an actual stock Fender sappimg (sappimg being a file you flash from fastboot to get completely back to stock). The things you will lose by rooting will be the extra Fender apps and the Fender splash image (the first image you see when booting the phone). That's pretty much all that's missing, but there's a group of guys working on getting it back in order. So it all really depends on what you want to do right now. Do you want to root and install a custom recovery/ROM (which will be the quickest fix right now) or would you rather wait until someone can get a similar stock image put back together?
Since you can't get into the ROM, you'll have to root using the goldcard method. Luckily for you it seems you have an extra Android powered phone around to be able to make the goldcard (you need to be able to boot the phone to complete this process).
At either rate, the best way to go about getting you straightened out would be for you to post the phone's current fastboot information. To do this, turn the phone off, then turn it back on holding the back button+power. Post everything from there.

Thanks man. Here's the info from HBOOT:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CLPD-13
RADIO-2.22.28.25
For the moment I would like whatever is the easiest way to get it close to stock. My problem is I don't always readily have access to a computer, but I have lots of android phones, lol. I'd like if I could just make a goldcard on another phone if possible, and flash a normal stock image from another dream/sapphire that is compatible. Is this possible?
Sent from my SCH-I500

hello first post

You could flash the stock sappimg for the myTouch 1.2. The myTouch 1.2 is the one that came out after the Fender. Same everything minus the Fender splash screen and apps. It also isn't capable of getting the 2.2.1 OTA update that came out last month. It's also stock 1.6, but it is very stable and pretty fast considering the phone's hardware.
I can tell that you that your friend's phone got hosed doing the OTA update and he could've gotten a Samsung Vibrant as a trade-out if he would've called T-Mobile about the issue, but we won't tell him that.
Rooting would require computer access. Actually, you'll need a computer period. Either rate. Before we do anything, try booting into recovery (hold home+power) and doing a "wipe data/factory reset" and then reboot. We could also try just reapplying the update.
You can hit me up on Google Talk at [email protected] if you want to get this sorted out tonight instead of having to go back and forth.

Do you have custom recovery or stock recovery...
If it is custom recovery, then fixing your problem(s) is pretty straight forward...

mumilover said:
Do you have custom recovery or stock recovery...
If it is custom recovery, then fixing your problem(s) is pretty straight forward...
Click to expand...
Click to collapse
Got him on Google Talk. Apparently his friend or the former owner hosed the phone doing the OTA since he's got the new radio and the SPL is untouched. We're going to try re-flashing the OTA update and maybe root later on. He's just trying to get it back working.

Yup. Stock recovery. From what I just got from the guy I got it from, it died after/while doing the ota update. It stuck on the splash when it went to reboot.
My guess its due to the fact I rooted the phone like 8 months ago, and removed a bunch of stuff via adb. Including probably what it considers some critical system stuff.
Sent from my SCH-I500

have a mytouch 3g 1.2 with the old radio and SPL, i acidently bricked it trying to flash the new radio and SPL and now i cant get into recovery or fastboot and the flash screen is frozen, pleassssssee help me get this fixed it has been completel useless for the last week or so

Stupid Mistake, flashed HERO recovery not HEROC

So I flashed the wrong RA recovery. This is the second time I've done this. I did this a months and months ago. For some reason I still had the hero RA on my computer and when I went to copy it over to flash, I didn't realize it was hero and not heroc. I flashed it and rebooted, and now I'm stuck at the HTC screen. I can't get passed it. Last time I was able to start booting, but it would bootloop. However in the bootloop I had adb shell access. Now I can't get passed the HTC screen. I can't get to fastboot either; when I hold the volume up button and power on it just stays at the HTC screen. I feel really stupid, but I was just flashing back to RA so I could install a sense rom to update my prl.
Anyone have any ideas? I just need to flash back to cm recovery. I'm not s-offed, nor did I use firerats, but I don't think that would help anyway. Anyone have any ideas?

Shelnutt2 said:
I can't get into fastboot though. When I hold the volume up button and power on it just stays at the HTC screen. I feel really stupid, but I was just flashing back to RA so I could install a sense rom to update my prl.
Click to expand...
Click to collapse
From powered off state: hold volume DOWN then press power, should boot into hboot, then press volume up for fastboot.
You can always use cwm 2.xxx to flash amend zips, or restore nands from ra, just move the nand from sdcard/nandroid/###/ to sdcard/clockworkmod/backup/
Good luck.

il Duce said:
From powered off state: hold volume DOWN then press power, should boot into hboot, then press volume up for fastboot.
You can always use cwm 2.xxx to flash amend zips, or restore nands from ra, just move the nand from sdcard/nandroid/###/ to sdcard/clockworkmod/backup/
Good luck.
Click to expand...
Click to collapse
It's a no go. Just stays at the black HTC screen. Booting normally, hboot or recovery just gives me the black htc screen. (I know recovery won't work but I was just going through everything)
Yeah I should have just used a cwn 2 recovery. But this was suppose to be a 5 minute process and I already had RA sitting there so I just copied it over with the prl and NFX rom.

I tried to RUU my hero but I can't RUU because I get the usb error 170. I guess not surprising because the phone doesn't boot far enough along.
Anyone have any ideas? Is the phone bricked? There has to be someway to wipe the phone clean. There has to be a way to wipe the flash memory completely and then just start over. Can I bootstrap a hero?

Shelnutt2 said:
I tried to RUU my hero but I can't RUU because I get the usb error 170. I guess not surprising because the phone doesn't boot far enough along.
Anyone have any ideas? Is the phone bricked? There has to be someway to wipe the phone clean. There has to be a way to wipe the flash memory completely and then just start over. Can I bootstrap a hero?
Click to expand...
Click to collapse
Tap on duce's avatar he's posted many of links and responses on that particular error.
#Root/Hack-Mod_Always*

laie1472 said:
Tap on duce's avatar he's posted many of links and responses on that particular error.
#Root/Hack-Mod_Always*
Click to expand...
Click to collapse
My problem is though that I can't get into hboot, so I can't fastboot. I can't get anywhere past the HTC screen. If I could get into hboot this would be a piece of cake. Anyone whose had the 170 error has at least been able to get into hboot, and that's how they fixed it.

Shelnutt2 said:
My problem is though that I can't get into hboot, so I can't fastboot. I can't get anywhere past the HTC screen. If I could get into hboot this would be a piece of cake. Anyone whose had the 170 error has at least been able to get into hboot, and that's how they fixed it.
Click to expand...
Click to collapse
Try google, I'm sure someone has had that.
sent from a series of tubes.

Yeah I'm looking around. I can't find anyone who recovered from this, so my goal right now is to see about two things. 1) Find out if I can somehow access the flash memory and just dd a good image onto it. Or 2) Find a way to make the hero boot of the sdcard so I can put an image on the sdcard and go from there.
Now I've seen a two posts of peopel using an HTC phone and "booting" off of an sdcard. However their posts were not explicit so I don't know if they just hboot'ed and installed from there or if they made the sdcard the rootfs. There was a thread for the G1 but that was for hboot I'm pretty sure.
I'm just posting what I'm looking for incase anyone else runs into this trouble also.

heroC member "uncorrupted" has a dual boot method which allows you boot a ROM from the sd card, if that's what you're looking for.

il Duce said:
heroC member "uncorrupted" has a dual boot method which allows you boot a ROM from the sd card, if that's what you're looking for.
Click to expand...
Click to collapse
His method is too high level, from what I can see.
I need to alter the SBL (or little kernel/hboot). I am pretty sure that is where my problem is. From what I can see the hero (like a lot of phones) uses the Little Kernel bootloader. But again I don't know how to flash/dd the flash memory on the phone without atleast hboot working, still trying to see if I can find a way to flash the ram a different method.
Somehow the bootloader (hboot) is messed up I think. I don't know if the recovery effects hboot, but I have a few theories. Either 1) The SPL was modified by flashing RA recovery thus now it fails authentication process and the SPL doesn't actually start. This probably would be do to the slightly different processors the gsm and cdma use[2]. 2) The hboot was slightly modified, and there is a failure there.[3]
The SPL should be able to boot hboot(LK) or recovery directly from what I read. Thus I should be able to get into hboot no matter what.
Now I know the chances of the SPL being messed up is very very slim, but these are the only two things I'm seeing from looking at dev docs.
I think I'm going to take it to sprint and see if I the guy I normally deal with will work with me on getting a hero. I know they are no longer sold, and back when I had a bunch of rumors after they were no longer sold and I was having problems they just swapped my phone for a parts phone they had.
If not then I am going to tear apart the hero and see about switching the GPIO95 pin[1-20] to low and disable secure boot. I'm fairly decent at soldering, so this might be a possibility. Either way I'll post back up with results if I can figure this out.
It just kills me that I've done this before, and fixed it but now it won't even boot. There are only three major differenes this time around, I was coming from cw recover 3, not RA 1.5. I have a AOSP (cyanogenmod 7) rom, not a sense rom, and I flashed the recovery while I was in recovery not while in the rom. The only one of these I think it might be is because I was in the recovery. It might be that since I flashed it in the recovery somehow hboot was messed up and will only boot back into what I was, aka recovery this time. My recovery won't boot because it's wrong -march. Last time I did this I was in the room and thus it tried to boot rom. I don't know, I've got different theories but not answers (yet).
[1] http://www.scribd.com/doc/51789612/80-V9038-15-APPLICATION-NOTE-MSM7XXX-QFUSES-AND-SECURITY
[2] http://avs234.net/docs/cpu/qualcomm/80-VM984-1_B_Android_Board_Bringup.pdf
[3] http://tjworld.net/wiki/Android/HTC/Vision/BootProcess

how do you fix this bc i know ill do it eventually

[Q] Desire Z unbootable and unflashable

Hey xda crew,
I am pretty sure my Desire Z is up sh*t creek now without a hope. As such I am here with my begging on... Help please!!
Last night I went through the app library and manually updated about 7 apps simultaneously. At some point the phone hung, and wouldn't respond. I pulled the battery and booted it back up, and it simply hung again as soon as it connected to wifi. It ran fine without a data connection however.
So this went on and on. I booted, connected to wifi and tried to kill each download asap before it hung again (can't access the market to kill the d/l w/o connection!). Inevitably it would hang each time and then i'd repeat. Finally though it simply got stuck on the HTC boot screen and never went any further.
I've tried everything googleable so far, but unfortunately no love. Here are my specs:
Desire Z, stock standard, no modding, ever.
Vision pvt ship S-ON
HBOOT-0.85.0013
Microp-0425
Radio-26.10.04.03_M
eMMC-boot
Apr 11 2011
I have tried the following to recover the phone:
Leave it loading on HTC screen (30+ mins): Never loads
Factory reset in HBOOT: Hangs
Recovery in HBOOT: Goes to HTC screen, then the green recovery icon, and then blacks out. As soon as the screen goes black it vibrates fiercely 7 times in anger and then dies.
Fastboot w/ RUU_Vision_Gingerbread_S_hTC_Asia_TW_2.42.709.10_Radio_12.56.60.25_26.10.04.03_M_release_201045_signed.exe: RUU sees phone but cannot reboot into bootloader, times out.
Flash manually using PC10IMG.zip, (rom.zip) from the RUU above: Initially didn't work due to CID invalid warning in HBOOT, however have made a gold card manually on PC and gotten past that warning. The ROM reads and verifies fully in HBOOT but upon verification just goes back to HBOOT screen without the option to flash.
With the intent to wipe everything: Flash the HBOOT with an engineering version from here: virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html: As per the RUU Rom, HBOOT reads and verifies successfully but never gives the option to flash.
Erase cache from fastboot command line: Hangs
Beyond that I don't know what else to try. I can't use adb as I cannot boot and don't have any custom recovery roms installed that will allow it. Likewise I can't flash with fastboot due to S-ON.
So because warranty ended a month ago, it goes in the bin tomorrow unless someone has an alternative Even if it is a highly dangerous method, I don't really care, it's good as dead anyway...
Interestingly enough it seems there are a few people with the same issue, all posted within about a week of each other. Everyone was doing the same thing... updating a bunch of apps!
Thanks in advance

When I rooted mine, I simply followed the instructions provided over at CyanogenMod ( http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Firmware_Downgrade_(Gingerbread) ) doing the firmware downgrade and then the rooting exploit, from there I actually upgraded the radio (thread in my signature) and then got the EliteMod rom.
PS: My Bootloader screen is basically:
VISION PVT ENG S-OFF
HBOOT-0.76.2000 (PC1010000)
MICROP-0425
RADIO-26.13.04.19_M
eMMC-boot
Aug 20 2010,16:51:01
Just not entirely sure how you're going to go bout the fr3vo method without least a stock rom to exploit into.

well jtag... not what you wanted to hear I'm sure
not trying to add insult to injury but next phone make sure you root it right away, chances are this all could have been fixed with the right permissions, short of a hardware failure of course
Sent from my HTC Vision using xda premium

Thanks for taking the time to help out mate.
As it stands, there is no way to use adb so I can't downgrade as per the directions in the link.
I have since tried several other newer and older roms as well, still the same thing, it unpacks them and verifies and then does nothing.
Quite sure now it is dead, so I have just bought a new one off ebay.
Poor old thing, I did enjoy that phone!

demkantor said:
well jtag... not what you wanted to hear I'm sure
not trying to add insult to injury but next phone make sure you root it right away, chances are this all could have been fixed with the right permissions, short of a hardware failure of course
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Yes, you are absolutely right... I was thinking the same thing. Thew new one will be rooted the minute it arrives. The good news i suppose is that desire z's are so cheap now that they are discontinued.
I honestly love the functionality, speed etc.. no need to upgrade whatsoever.

Your bootloader is stock and you are S-On why not just use your warranty ?