yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] HipKat:
Seems like 95% of the people with this problem use CM, though...

I think I've only seen 2 or 3 cases that weren't CM, and I don't think the number of CM users is that same ratio or even close to it. To me, that's enough times to never put CM on my phone
[EVO 4G Q&A, Help & Troubleshooting] fenixjn:
If you have access to the bootloader then you should be able to flash either stock (if s-on, you can s-off once you have a working phone) or a new recovery.
[EVO 4G Q&A, Help & Troubleshooting] Indirect:
I have a suggestion, I think I remember that if you wipe boot, it causes it to default to recovery so I can suggest this: go into recovery *when possible* and format BOOT

you should then remove the stacked OS' so basically you will have a recovery based phone which is the ability to fix anything hence the point of recovery. So just try that and you should be good. You can also do a full system, data, dalvik, and cache wipe just to start 100% fresh.
[EVO 4G Q&A, Help & Troubleshooting] nanstedt:
This just happened to me a few days ago. I went from MikG to Deck to CM7. I just flashed CM7 over Decks 1.3 wiping only cache and dalvik. I was starting to really dig CM7 and I was planning on sticking with it. When it happened I was using the stock web aplication. I finished reading the page I was on and hit the back button (the one at the bottom of the phone) and next thing I knew my phone started rebooting. It never made it past the Evo splash screen since. I've been able to flash different hboots and it takes but it does not take any of the recoveries or RUUs. Has anyone had any luck with this yet? Or does anyone have any different advice with the extra info I have provided?
[EVO 4G Q&A, Help & Troubleshooting] nanstedt:
Hello, me again. I was wondering if I would get banned if I posed this in the dev section? This seems like a problem only devs can fix but i'm not sure if this would qualify. I've seen this issue on xda and androidforums in multiple areas but I think if it was in the dev section it would get the proper attention.

My phone just continuously boot loops, gets right to the HTC EVO 4G screen, goes black, then cycles through that. I can get into my bootloader, but not recovery... If I pick recovery, it will just cycle back again. I was running the latest CM7 stable build, and I have no idea what to do. Is my phone a lost cause now? How the heck can I get back to my Nand!
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Have you tried flashing a recovery via PC36IMG?

its possible you may have bad nand blocks.
[EVO 4G Q&A, Help & Troubleshooting] HipKat:
I think he's the newest victim of the White Screen of Death
[EVO 4G Q&A, Help & Troubleshooting] PabloKoala:
Boot Loop with No Recovery

Same is happening to my evo when i tried to flash FEARMEde beta8 to beta 8.5. Before that i partitioned my sd card to ext2 to 3 and it wouldn't flash no rom. I tried a new pc36100img but it didnt work. Also tried VR_SUPERWIPE to fully wipe then install any roms but nothing works.

Recovery: AmonRA v2.3

HBOOT: 6.16.1002

Radio: 2.15.00.0808
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
What was the PC36IMG supposed to do?
[EVO 4G Q&A, Help & Troubleshooting] PabloKoala:
to unroot the phone
[EVO 4G Q&A, Help & Troubleshooting] nanstedt:
yes sir. Unless yoiu have a special one i haven't tried yet:-)
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Well, how did you root? As in unrevoked or revolutionary?
[EVO 4G Q&A, Help & Troubleshooting] HipKat:
I would try to reformat your SD Card, and start over on your partitions. You might have to use something like MiniTool Partition Wizard to remove your partitions, then use Amon Ra to partition again. Swap 64 EXT 1024, convert EXT2 to EXT3 then wipe everything except SD Card: and Battery Stats if it's not fully charged and reflash your ROM
[EVO 4G Q&A, Help & Troubleshooting] nanstedt:
Unrevoked over a year ago. Froyo was pretty new when I rooted.

---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------

Unrevoked over a year ago. Froyo was pretty new when I rooted.
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Are you still able to get into recovery?
[EVO 4G Q&A, Help & Troubleshooting] jcthelight:
Well I guess I'll join the group of bootlooping evo's but mine started after i rewrote nv files to it. And I've tried everything also
[EVO 4G Q&A, Help & Troubleshooting] nanstedt:
Nope, I cannot get into recovery. I can flash PC36IMG files and run the RUU.exe files from windows but it still doesn't boot past the HTC EVO 4G white screen.
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Have you tried flashing a boot.img for the rom you are trying to flash over fastboot? it seems like your have a bad boot img.
[EVO 4G Q&A, Help & Troubleshooting] nanstedt:
No, I have not. That is a new idea. Do you know where I can get a boot.img and instructions on how to do that?
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Well download a rom, open it up, and inside it will be a boot.img, extract it and put it in your adb tools folder. Boot into the bootloader, then select fastboot and connect to the pc using the usb cable.

Open command prompt and navigate to your adb tools folder and it should be:

fastboot flash boot boot.img

fastboot reboot

Then try let it booting up.
[EVO 4G Q&A, Help & Troubleshooting] jcthelight:
What do you mean by put it abd tools folder on sd card or pc and how do i navigate to that with command prompt?
[EVO 4G Q&A, Help & Troubleshooting] HipKat:
I guess the first question is, do you have Android-SDK installed on your computer?
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
You download the sdk to you pc. http://developer.android.com/sdk/index.html

I recommend installing on the desktop [for ease of use]

To navigate:

cd desktop/xxxxx/tools

where xxxx is the name of the sdk folder [i change mine to android for ease of use again].

I'm guessing no. :p
[EVO 4G Q&A, Help & Troubleshooting] j7jman:
Bump

Sent from my Random, old but still kickin, Epic 4g
[EVO 4G Q&A, Help & Troubleshooting] nanstedt:
Thanks! I'll give this a shot.
[EVO 4G Q&A, Help & Troubleshooting] jcthelight:
Yes but when i put in fastboot flash boot boot.img

fastboot reboot

it says fastboot is not reconized as internal or external command operable program or batch file.
[EVO 4G Q&A, Help & Troubleshooting] nanstedt:
Well, I got fastboot installed and did what you recommended above. According to the command prompt everything ran well but I am still not getting any results. Still in the HTC Evo 4G splash screen boot loop. Do you know if there is a way to format all the partitions from adb or hboot so I can start with a clean slate? Or am I going to deep at this point. perhaps there is a way to push a complete image through adb? I really want to figure this out. Not only to get my phone running but I am also learning a bit through this process. This is kind of fun although at the demise of my Evo. Hopefully it can be resurected.
[EVO 4G Q&A, Help & Troubleshooting] Indirect:
Run

fastboot erase system erase cache erase userdata erase boot

It wipes all but recovery and bootloader.

Sent by breaking the sound barrier
[EVO 4G Q&A, Help & Troubleshooting] nanstedt:
Is it safe to assume if I put erase recovery it'll wipe that too?
[EVO 4G Q&A, Help & Troubleshooting] Indirect:
Yes it will erase recovery

Sent by breaking the sound barrier
[EVO 4G Q&A, Help & Troubleshooting] nanstedt:
If I "fastboot flash" each img file it will restore them all or is there a better solution?
[EVO 4G Q&A, Help & Troubleshooting] Indirect:
I can suggest using an RUU first since system.img is usually too large to take..
[EVO 4G Q&A, Help & Troubleshooting] jcthelight:
I don't get it every command i enter is not reconized.
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
The you don't have fastboot or you're in the wrong directory.
[EVO 4G Q&A, Help & Troubleshooting] jcthelight:
I don't know why when i copy and paste it from the command prompt it shows a space where fast b oot is thats not how its shown but this is the error I get. And I tried it 2 different ways with and without the back slashes.

Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>cd desktop\android\tools

C:\Documents and Settings\Administrator\Desktop\android\tools>fastboot\ erase system\ erase cache\ erase userdata\ erase boot

'fastboot\' is not recognized as an internal or external command,

operable program or batch file.

C:\Documents and Settings\Administrator\Desktop\android\tools>fastboot erase system erase cache erase userdata erase boot

'fastboot' is not recognized as an internal or external command,

operable program or batch file.

C:\Documents and Settings\Administrator\Desktop\android\tools>
[EVO 4G Q&A, Help & Troubleshooting] psg190:
Alright everyone. I'm in the same boat as well. Had originally rooted with Unrevoked. I'm on hboot .76 and while trying to flash a sense rom to get to the dialer codes things went bad. Now I show as s-on with no recovery. I can fastboot into recovery but I can't flash recovery without getting a "signature verify fail" error. Any suggestions?

Update: Spent hours working on this so far without any luck. Tried to flash unrevoked from zip after fastbooting into recovery. Only problem is that I can't get the SD card to mount while in a temp boot into recovery. Tried the big 3 recoveries and all had the same problem. Also tried doing a fastboot udpate, but can't find a good file to flash that won't give me an error. If I could just get s-off I think I'd be ok, but I don't know of any good way to get it without adb or the ability to flash a zip from recovery. Arghhh!
[EVO 4G Q&A, Help & Troubleshooting] nanstedt:
Thanks for the suggestion, but I've tried a number of RUUs with no luck to my dismay. I've tried a few of them and I do notice that the images do get written as indicated by the RUU program on the update from/to page. So the RUUs are writing to the phone but something is borked.

I've also been able to use flashboot to write to and erase a nubmer of the partitions such as boot.img and system.img. Once again I notice that the files are getting written but nothing is seeming to affect the HTC Evo splash screen boot loop.

There just seems to be an issue with the handoff from hboot to recovery/android. can anyone think of another suggestion? Is there a way to check for bad sectors or resizing the partitions? Maybe hboot is getting pointed to the wrong sector. Any ideas?

---------- Post added at 08:24 AM ---------- Previous post was at 08:19 AM ----------

To make it easier you should have fasboot installed in the same directory as adb, i believe it's platform_tools. Also, you should put any of the images you want to flash in that same directory.
[EVO 4G Q&A, Help & Troubleshooting] psg190:
So I FINALLY got a stock PC36IMG.zip to take and now on occasion the phone will boot, but it's only a matter of time before I get the 5 vibrates and the screen goes blank on me. I can't even get adb or mount the sd card when it's on and attached to the computer. Any ideas as to where I could go from here.
[EVO 4G Q&A, Help & Troubleshooting] tooill:
this boat is on the verge of sinking. add me in guys -_-, tried almost everything said on this thread, and no luck

white screen of death = 1

me = 0 :(
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Well open up the the tools folder and look for fastboot.exe. Is it there? You may have to download it separately because I think it was removed from later versions.
[EVO 4G Q&A, Help & Troubleshooting] jcthelight:
Ok I figured it out didn't know i needed to have fastboot in the folder too so I moved the fastboot I had in my auto root folder. I entered the commands and got these messages in the command prompt.

Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>cd Desktop\android\platform-tools

C:\Documents and Settings\Administrator\Desktop\android\platform-tools>fastboot

erase system erase cache erase userdata erase boot

< waiting for device >

erasing 'system'... FAILED (remote: not allowed)

C:\Documents and Settings\Administrator\Desktop\android\platform-tools>fastboot

erase system erase cache erase userdata erase boot

erasing 'system'... FAILED (remote: not allowed)

C:\Documents and Settings\Administrator\Desktop\android\platform-tools>fastboot

flash boot boot.img

sending 'boot' (2550 KB)... OKAY

writing 'boot'... INFOsignature checking...

FAILED (remote: signature verify fail)

C:\Documents and Settings\Administrator\Desktop\android\platform-tools>fastboot

reboot

rebooting...

C:\Documents and Settings\Administrator\Desktop\android\platform-tools>

C:\Documents and Settings\Administrator\Desktop\android\platform-tools>fastboot

flash boot boot.img

sending 'boot' (2550 KB)... OKAY

writing 'boot'... INFOsignature checking...

FAILED (remote: signature verify fail)

C:\Documents and Settings\Administrator\Desktop\android\platform-tools>fastboot

reboot

rebooting...

C:\Documents and Settings\Administrator\Desktop\android\platform-tools>
[EVO 4G Q&A, Help & Troubleshooting] nanstedt:
Does anyone have any ideas on checking for bad sectors and resizing partitions. I'm willing to try anything at the moment.
[EVO 4G Q&A, Help & Troubleshooting] nanstedt:
I'm not sure if anyone was wondering what happend here, I'd like to give an update. After trying to flash numerous PC36IMG files and running multiple RUUs I had no luck getting out of the boot loop. My last shot in the dark was to see if the sprint techs had some magic bullet our XDA collective didn't. I didn't have insurance and I was over my 1 year warrentee. I was also S-off. The nice little lady at the front desk said that if Sprint can fix my phone it would cost me $35 and if they cannot fix it they will replace it. I didn't think she knew what she was talking about due to the in training badge she was wearing but I moved forward with this. I figured what do I have to lose. If they can't fix it I'm out nothing if they do I get my Evo back for $35. As, I figured they could not fix it but to my disbielief they did replace it and it only cost me $35. Got to say I'm pretty stoked!
[General Questions and Answers] 4nzikJunkie:
Ok so here is the deal, I have read all of the different instructions, I fancy myself as someone who knows how to follow directions, and I am still receiving an error while trying to do the manual update.

The first error I receive is this one: E:Can't open /cache/recovery/command I get this error when I go to the system recovery screen, but it still allows me to choose "apply sdcard:update.zip [Alt+S]"

The second error I receive is:

--Install from sdcard...

Finding update package...

Opening update package...

Verifying update package...

Installing update...

Verifying current System...

assert failed: apply_patch_check

("MTD:boot:1888256:52022649d20fe

178f866dc52df8e882bd3da66bf:2357

248:84385c90406d6449ee5be40da765

cf77baaf6e58")

E:Error in /sdcard/update.zip

(Status 7)

Installation aborted

This error is received when I click "apply sdcard:update.zip [Alt+S]

I hope someone can help me with this. Also before you ask, my phone is the MyTouch 3G 3.mm (non-fender), and to my knowledge it is stock. I have no interest in rooting my phone, so that is why I know I didn't root it. However, it is a recent referb that I received from T-mobile after my first one took to the grave. I appreciate anyone willing to be patient with me.

**UPDATE**

My OTA came through last night but it is also failing when it gets about half way through the installation. Anyone have an idea what could be causing this and how I can fix it?
[General Questions and Answers] Dirk:
I've encountered this recently and have no idea what causes it!

Long story short... i was trying to get off the Vodafone ROM from my phone and hopefully update too in the process. I flashed a couple of stock ROM images but each time the OTA would fail during installation as would a manual install. At first it would fail signature checking, so i would disable the check using Clockworkmod, run the update again and then i would get the error you posted.

I'm wondering now if the official 2.2.2 update will ever work, even when Vodafone release it, and whether the 2.3 update will also fail when that is released.

You and i may have to bite the bullet and go down the fully custom route. Once Gingerbread is released i'm hoping that one of the chefs releases a nice Stock version that i can use :)
[General Questions and Answers] 4nzikJunkie:
Actually...

I was soooo frustrated with the way I was treated by a T-mobile rep, when I called about the error today, that I decided to cancel my service with them. I have had several issues with their products and services and continued to give them chances. However, after today's incident I decided to terminate service... just as soon as my new phone from my new provider arrives on Friday.

In addition, since I am no longer going to be using the phone, I decided to try my hand at rooting.... and what do you know, I did it without a problem. LOL Oh well.
[General Questions and Answers] Dirk:
Congrats on getting a new phone. It never hurts to have an old one spare to use for experimenting with new ROMs etc. :)
[Nexus S Q&A, Help & Troubleshooting] rickysquared:
Hello,

I am wondering if anyone knows the audio specs of the Nexus S? Like, the range of the output and the power, etc... I can't seem to find them online..

I am asking because I am considering getting a small headphone amp. Depending on the output power of the headphone jack, one headphone pre-amp may work better than another..

Thanks,

RickyRicky
[Nexus S Q&A, Help & Troubleshooting] RogerPodacter:
well gsmarena started doing some nice audio tests, check the nexus one review below to see what they did with audio:

http://www.gsmarena.com/google_nexus_one-review-457p6.php

let me look and see if the nexus s has the same..
[Captivate General] problem?:
I searched over the XDA forums but I couldn't find anything similar to this.

Basically, I had a perfectly working Captivate. I got it from Rogers through a hardware upgrade. Long story short, it got a scratch on it and I wasn't too pleased. It wasn't a big deal to me or anything but if I wanted to sell it in the future it would definitely devalue it significantly. My cousin didn't care though, so I sold it to him. I ended up getting another Captivate as sort of a gift from a friend who had a bunch of gift cards to Future Shop or some store (I paid the difference).

Problem is, my phone is now completely bricked. I followed the tutorials here very closely, they were awesome. The phone is rooted as well. I was using odin try to flash the phone but it never succeeded. The first time I was able to get passed the download screen, and then to some menu and the phone got to the rogers load screen, but then after that it failed. Since then the phone would get stuck at the computer with the cell phone screen. That wasn't a problem to bypass and get to the download screen (there were 2 combos you could use: put in battery/volume down/power or plug in USB/Battery/both volume buttons and power/release volume up). The final attempt happened when using odin I used the proper 512 pit file and the correct PDA file. The phone was recognized by my computer and showed up in Odin (com3). I clicked start, the blue progress bar appeared on the phone and it looked like it was going well. Then all of a sudden the screen turned bright blue and just stopped completely. Then it turned off. And now its completely unresponsive. No combination of batter/USB/power/volume button works at all, it's dead.

Long story short, I spoke with a Rogers tech. He tried to help me out but couldn't do anything. He told me that he'll ship me a new Captivate which I received. He also asked me for my IMEI number, and I gave him the number of my original phone that I sold to my cousin. I'm not sure why I gave him that one, I had the original box in front of me and I just read that, plus I thought that this number is like my ID with rogers or something, I don't know.

Anyways, this phone that I have, because it's a third party phone, rooted, and completely dead, can I send it back or should I just pay for the phone they sent me? Should I take the risk and send it back? My cousin said we can just replace the sticker that has the IMEI number from his phone with my phone, but I don't know about that. If we did that, and Samsung found out, what's the worst that could happen :x Sounds shady...Plus, would Rogers care if the phone I send back is not the original one that I got through them, even though it is a captivate that is with Rogers?

I'm afraid that if we replace the sticker, sure if Rogers looks at that to make sure its my original phone it would get passed them since you can't even turn my phone on...but once it gets to Samsung, can't they look at the internal IMEI number and if they compare that to the sticker....owned?

Thanks
[Captivate General] SwiftJudgement:
My vote would be to send in the bricked phone. The Rogers tech guy knew that your phone was bricked, so sending in a bricked phone shouldn't be a problem.

If they ask you why it has a different IMEI number than the one you gave them, just explain that you grabbed the wrong box.
[Captivate General] newter55:
Not with rogers but I changed my mind on which of our three I wanted to return to at&t after talking with them and providing my imei number. I originally wanted to warranty mine but decided to send in the wifes because her screen was developing a strange clarity issue. Never heard anything from them on the issue. I would definitely not recommend you trying to swap stickers.
[Captivate General] norcal einstein:
Do NOT tamper with the IMEI number (sticker swapping included). Tampering with it is illegal...
[Captivate General] z28james:
Swapping the sticker will not change the contents of the files inside of /efs which have the IMEI both in plain text and encoded.
[Captivate General] problem?:
Ah thanks for the replies everyone, that was so quick.

I guess my main concern is that if Rogers looks at the IMEI number on my phone sticker, and realizes that its not the same as my original phones that I got through Rogers, they'll send it back. Is that the case, or does my warranty transfer over to my new phone? I'm not even sure if this is a warranty issue though since its definitely passed the 30 day period. Is there a warranty deal that Samsung specifically has with its customers, specifically pertaining to bricking as a result of software upgrades?

Or is this not as much a Rogers issue as it is a Samsung issue? I wish I understood how the process worked...for all I know, my phone has already been approved for shipment to Samsung, so as soon as Rogers receives it, they just send it over to Samsung and they don't care about those details pertaining to a persons Rogers account.

But I'm sure a lot of people are in the situation where they no longer have the original phone they received from their provider, and purchased one from a third party dealer, and something happens to it...what is their condition?

James, I think the reasoning for wanting to switch the sticker was because Rogers knows that the original phones IMEI number is as such, and because they can't turn the phone one they would probably just glance at the number on the label, and then send it off to Samsung. So I was wondering maybe I should call Rogers and tell them I gave them the wrong number? If I do that then, again, would they say that because the phone I"m sending in is not the original one they can't send a replacement and so I'd have to pay for it?
[Captivate General] problem?:
Thanks for the reply, that was a great help. Did you have to send it back in your original box for your phone?
[Captivate General] newter55:
The way it works here is you return your phone in the package they sent the refurb in. Just the phone, no cords, battery, etc.
[Captivate General] xThe Enforcer:
Integrity.