yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Damn, so no recovery access at the moment. That means no adb. Do you have the fastboot binary on your computer, so you can run fastboot commands? I'm starting to run out of ideas here. I wonder if you have bad blocks. If you can use fastboot, try 'fastboot oem listpartition', and post the output back here if you can. I'm not sure if that .79 hboot accepts all fastboot commands. If not, maybe try downgrading to the ENG 0.76 hboot, which accepts all fastboot commands. Do you know what hardware version your phone is? I'm wondering if it has the 0020000 or 0040000 erase block size (you need to adb command cat /proc/mtd to find out for sure...but you have no access to adb since you cant get to recovery or past splash screen :mad:)

EDIT: and i'm extremely tired at the moment, I apologize in advance if I disappear....it means I passed the eff out :)
[EVO 4G Q&A, Help & Troubleshooting] Sn4ckm4st3r:
Ummm not entirely sure, I know if I got to my Hboot and run CMD on my computer, I can use Fastboot commands still.

I can get whatever information from that you are asking for, I am just not entirely versed in what I will need to type so that it will give me what I want. I also know then when I run in Hboot- and use the ADB thing, it shows that my device is on there. If that is any help at all to the cause.

If you can tell me what to type, or what I might need in order to get the information you wanted, I can definitely do it.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
so you're saying that ADB recognizes the device from your hboot?? I didn't think that was possible...but I could've been wrong. Try typing 'adb devices'. Does it give you an output? If adb detected the phone, it should spit out the serial number. If you do indeed get the serial number, that means the phone's detected. So in that case, to check what size your partitions are, do this command:

adb shell

# cat /proc/mtd

if all the numbers you see are 0020000, you've got the old partitions. If you see 0040000, you have the newer partitions.

Let me know if any of that works. I'm trying to stay awake to keep trying to help, but I'm fading fast. Super tired!
[EVO 4G Q&A, Help & Troubleshooting] Sn4ckm4st3r:
Seems the news leaves me with 0020000.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
okay, that's good. The older partitions. (I'm still a bit unsure how adb worked from the bootloader, that has me puzzled. I just tested, and I get no device at the bootloader, splash screen, etc. I only get my serial number when I'm in recovery, or any time after the boot animation starts)

Did you try using the fastboot commands to erase everything? From the .docx tutorial that I attatched earlier? I would try running a newer RUU, one more time. See if that will at least get you to boot. If you're still stuck, I would try using the fastboot commands from that tutorial to erase EVERYTHING off the phone, then try running the RUU. (i was unsure if you already tried that before, if so I apologize, and ignore) It's starting to seem grim.

when you select fastboot from your bootloader, and type 'fastboot oem listpartition', you should get an output after that. Post the results of that command, and hopefully someone will be able to tell you if you've got bad blocks. That's a bit over my head though, to analyze the results.
[EVO 4G Q&A, Help & Troubleshooting] Sn4ckm4st3r:
I ran everything to the Tee from the doc you sent to me.

I installed the RUU listed with it, however I am currently downloading from an XDA post the NEWEST, or what would seem to be the MOST recent RUU listed on there and will be giving it a shot as well. Grim seems to be an understatement =[. But with Hboot still working, I am still trying.

Also, the Fastboot command you told me to type, doesn't seem to take, I keep getting "INFO[ERR] command error !!" but all the other fastboot commands in the DOC you attached earlier take just fine.

Going to run that RUU now, and see what happens.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Hmm, I wonder if fastboot OEM listpartition only works on the ENG bootloader. I'm not sure... hopefully the next RUU will do a bit better for ya. I'm wondering how much damage was done initially on the failed OTA update. When you got it, and said it was bootlooping, did u mean it was rebooting the splash screen or the boot animation?
[EVO 4G Q&A, Help & Troubleshooting] Sn4ckm4st3r:
I meant it kept going black, and kicking to the splash screen.

However the newest RUU I tried, still results in hanging on the splash =[.

BUT!!!! I was able to get my cmd to run through the fastboot oem listpartition......I had to capitalize the OEM part haha....I feel dumb :p

Anyways after typing it in I get this on my CMD.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Well, I'm not sure. I was expectating to see something more like this....

fastboot oem listpartition

INFO[radio]:(OTHER) block start=0, size=497 (0 KB)

INFO[hboot]:(RAW) block start=497, size=6 (768 KB)

INFO[misc3]:(RAW) block start=503, size=7 (896 KB)

INFO[mfg]:(RAW) block start=510, size=6 (768 KB)

INFO[sp1]:(RAW) block start=516, size=9 (1152 KB)

INFO[wifi]:(RAW) block start=525, size=5 (640 KB)

INFO[recovery]:(RAW) block start=530, size=40 (5120 KB)

INFO[boot]:(RAW) block start=570, size=20 (2560 KB)

INFO[system]:(YAFFS) block start=590, size=2800 (369600 KB)

INFO[cache]:(YAFFS) block start=3390, size=1280 (168960 KB)

INFO[userdata]:(YAFFS) block start=4670, size=3421 (451572 KB)

INFO[wimax]:(RAW) block start=8091, size=96 (12288 KB)

INFO[misc]:(RAW) block start=8187, size=5 (640 KB)

INFO[rcdata]:(OTHER) block start=0, size=0 (0 KB)

INFO[cpld]:(OTHER) block start=0, size=0 (0 KB)

INFO[microp]:(OTHER) block start=0, size=0 (0 KB)

INFO[a1026]:(OTHER) block start=0, size=0 (0 KB)

INFO[tp]:(OTHER) block start=0, size=0 (0 KB)

INFO[nv]:(OTHER) block start=0, size=0 (0 KB)

OKAY [ 0.078s]

finished. total time: 0.078s[/QUOTE]

That's an example of one with bad blocks I believe.

I'm signing out for the night. So tired. I wish you luck, and will check back in the afternoon. Hopefully someone can help you, but it's seeming like the phone is jacked up a bit.
[EVO 4G Q&A, Help & Troubleshooting] Sn4ckm4st3r:
So here is a crazy thought, I know that RUU's are done as a whole. And that good jazz. But being S-Off, I am able to run anything per-say. Is there possibly a non-signed RUU somewhere I may be able to try instead of these bull crap signed ones that no one wants anyway?

Probably won't work, as of now I no longer hang, I just get to the splash screen, and then a few minutes later I am sent into diagnostic mode.
[EVO 4G Q&A, Help & Troubleshooting] sharkboy0901:
If you have am ra recovery get the lastest ruu put it on your sd card than wipe everything I mean everything including boot, and cache, battery stats, dalvik cache just do all the wipe options except your sd then flash thru the recovery the lastest ruu than wipe data and cache reboot and see if it works
[EVO 4G Q&A, Help & Troubleshooting] Sn4ckm4st3r:
Sharkboy- When I said if you can post something helpful, I meant HELPFUL....next time, please read the 6 posts before your own, before you give me a solution (which given my posts I already knew how to do) that will not work, because it has been stated a good number of times that I can not enter recovery......thanks.

As of right now, the phone is in a new bootloop sequence after running the completely OEM HTC RUU. It gets all the way thru the 4G animation, and then restarts, I made it to the phone setup.....ONCE and then after it kicked back to the boot loop. I kinda feel like I am making progress, if only it will fully boot, and stay that way, I may be able to yank more info out of it using ADB for people to get a better idea of what kind of issue we are looking at.
[EVO 4G Q&A, Help & Troubleshooting] sharkboy0901:
Right sorry stupid mistake :p

Damn. This is hard it happened to me once but I just flashed the unrooted latest ruu in boot loader and that fixed it but in your case its not working OK let me think a bit more ill get back to you
[EVO 4G Q&A, Help & Troubleshooting] Sn4ckm4st3r:
My apologies if I sounded rude. I am just kind of a straight forward person. :cool:

But yes, put your think caps on, I have been trying a few things. If I can get it to the main phone again, I can run ADB and maybe pull some more information for this issue and dig to the "root" of the problem haha.

Any other ies will be taken into consideration, do remember, I have S-Off, but no super user or custom recovery, I did try and flash a custom recovery, but still no dice.
[EVO 4G Q&A, Help & Troubleshooting] AbsolutZeroGI:
if you have adb, could you do a logcat and have it running while trying to boot? It'll give us an idea of where the errors are and how to fix them. At this point it could be anything. If we figure out what's actually broken, we can try a more targeted approach to fixing it. Type this while in bootloader:

adb shell

logcat

after that, try to reboot it. Once it gets stuck, go ahead and stop it (battery pull) and then give us some logcat goodness. At least we'll know exactly what it's getting hung up on.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Any further progress? As absolutezero suggested, are you able to pull a logcat while it's booting up and looping? I know you had access to ADB last night (surprisingly from the hboot??) Run adb logcat while it's trying to boot, and let it run for a bit. cntrl+C will stop the logcat from recording when you're ready to stop it. What RUU did you run that was able to get you to the boot animation and actually into the UI for a second?

Your Location says Henderson...is that Henderson NV, or some other henderson? Just curious. I'm in nevada as well.
[EVO 4G Q&A, Help & Troubleshooting] Sn4ckm4st3r:
Well, I would run logcat, but no device found while it's loaded into boot loader now. Somehow miraculously last night it let me do it and I was able to pull out which partitions I was running on.

But error device not found, means no logcat I guess, which means no newer specific information :(.

So, guess it's back to brainstorming, and we will take another approach, Thanks for not giving up, if any of you decide this isn't something you want to help chase down, I understand haha. I just have this inability to really give up until I know exactly what is causing this, even if it's unrepairable, I want to know.....OCD, it sucks.

Anyways, no new info K2, and no Henderson, Ky......not NV lol
[EVO 4G Q&A, Help & Troubleshooting] Sn4ckm4st3r:
BIG UPDATE!!!!

I got the phone fully booted and it is being recognized by the computer.

By full booted, I mean like it normally would be on if you were using it day to day.

So, if anyone knows how and what information would be best to pull while I have it fully functioning, please let me know, so that I can get it for you guys and run it by you to find what the flaws are in this system!!! :D:D:D
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Nice! Good news man. What'd you end up doing to get it where you're at now? Does it have more stability than it did before (ie reboots / lockups / forcing into diagnostic mode)?

Are you still on the same bootloader with S-off as you were as of your last update? Or did that get changed in the process of getting to where you're at now (RUU would change it)

There isn't too much info other than the standard stuff that is needed, such as hboot version, software version, baseband, pri, kernel. Note that stuff down, so you know which combo worked to get it booting for you. Find that stuff under menu>settings>about phone>software information.
[EVO 4G Q&A, Help & Troubleshooting] r.storm85:
Well you got it booted. I think running an RUU through HTC Sync is the way to go.

But from what I heard, the best RUU to run is the one that matches your radio/pri version.

Every RUU comes with its own set of radios and you should run that one to have the biggest chance of success. Since you have it booted.note all your radio versions and find that RUU.

I have unrooted a phone by running a RUU (once) and I used the RUU I described above. It worked first try. So this is what I would try. Good luck!
[HD2 Android Q&A, Help & Troubleshooting and Genera] albanianbrotha:
I do not recall exactly which rom I installed, but i think it was called Nexus HD2 or something.

Very stable and solid ROM, but I use GPS quite a bit for my work, but it could never lock on my positon for turn-by-turn nav. Is something wrong with my phone? It was sitting right under the windshield the entire time, and no satellite lock. The blue circle would get small, but it never pinpointed my position.
[HD2 Android Q&A, Help & Troubleshooting and Genera] slbenz:
Have you checked the gps.conf file on your ROM to be sure that it is configured for your region?
[HD2 Android Q&A, Help & Troubleshooting and Genera] albanianbrotha:
How can I do that?
[HD2 Android Q&A, Help & Troubleshooting and Genera] slbenz:
You need to use some type of file explorer. I use ES File Explorer found on the Market. Go to Systems/Etc/gps.conf on your phone and NOT the SD card and there you will see what region the file was configured for. If it is set up for the wrong region for you, then go to Instantaneous GPS Fixation thread:http://xdaforums.com/showthread.php?t=953630 and download the correct zip for your region and flash it via CWR.
[HD2 Android Q&A, Help & Troubleshooting and Genera] flame10:
GPS Libraries v1.3 for HD2 Gingerbread , A definite requirement fo users with android on HD2
[HD2 Android Q&A, Help & Troubleshooting and Genera] albanianbrotha:
Flashed two CWM zips, testing it later today at work. It would literally try getting a lock for 10 minutes without succeeding. Hopefully this now cuts it down to under a minute (maybe I'm too hopeful).
[EVO 4G General] Bkbitar:
Hi all,

Cm7 problem. I was at the Bruins parade today trying to record some video, and there times I got a reboot. Was recording in "YouTube" quality. Also got some force closes in the regular camera. Anyone know how to fix this?

Edit: running version 7.0.2.1
[EVO 4G General] mattykinsx:
What kernel?

Also, why an outdated "stable version"?
[EVO 4G General] MedicStuder:
copy the contents of ur dcim folder. then delete your dcim folder. reboot phone. phone will recreate dcim folder and hopefully everything should work fine.
[EVO 4G General] Rem3Dy:
Why YouTube quality. Just record in the highest quality. It will still upload to YouTube just fine and will look better
[EVO 4G General] Bkbitar:
As soon as I get the chance I will try that, thank you.
[Wildfire General] halaue:
I've tried to format my device, and flash SUnAaBh_v1.1 into it.

After my device rebooted for few times, now it hang at the HTC screen, I not even able to enter recovery page. I have tried to unplug my battery and turn it on again, it still shows the same thing!!

Did anyone encountered this problem before and has found the solution?

It's so urgent! Please help!
[Atrix 4G Themes and Apps] Gutterball:
Hey everybody! I made this android robot battery mod icon using uot with the gladiatrix 3 b2 framework and gingerblur 4.5. so only flash this if you are on gladiatrix3 b2 or gingerblur 4.5 !!

I have tested these different uot battery icons on my phone which is an ATT atrix with 1.83 firmware numerous times and they work perfect if done the correct way!!This will not make your phone do 1% percent battery increases/decreases it just will give you a new battery icon! Thats it! If you want the 1% mod look for it in the apps and themes thread here! http://xdaforums.com/showthread.php?t=1105272&highlight=battery+mod This is to be flashed through Tenfars CWM only!! If you guys want more? I will make more through UOT as there are many different kinds besides the robot. :D

Heres the link for the mod for gladiatrix3 b2!! http://www.mediafire.com/?jkoodi47o3ui56u

Link for those on gingerblur 4.5 http://www.mediafire.com/?9u2gl9n9bmsyl4h

Note: I am not responsible for any kind of damage or data loss from flashing this!! flash at your own risk!!! Always backup before flashing anything as well!! Enjoy!

Heres a pic!!!
[Atrix 4G Themes and Apps] netinetinet:
please

please version for Gingerblur 4.5 ATT (1.8.3)
[Atrix 4G Themes and Apps] Gutterball:
Alright dude! Gingerblur 4.5 mod added as well! :D
[Atrix 4G Themes and Apps] mirageromeo:
Awesome !!!!!
[Atrix 4G Themes and Apps] G-Man.:
Nice work! Any chance of making a sweet skull battery mod? for Ginger 4.5 also?
[Atrix 4G Themes and Apps] netinetinet:
thank you...super great...
[Atrix 4G Themes and Apps] Gutterball:
I wish! I just made a thread about that myself! I dont actually make these! They're from a site called UOT but alot of people were having problems with installing these. So I fixed it all up so you can just flash it like normal through tenfars CWM and you're done no work involved with matching up frameworks and fixing errors and things of that nature! These are cool but as I said alot of people ended up soft bricking and such when attempting to do it on their own. So I wanted to make it as easy as possible for everyone to have these batt mods! Thats all! If anybody out there can do a skull batt mod I'd greatly appreciate it! :D

I may do the dogs paw one next it kinda caught my interest!
[Galaxy S I9000 Android Development] Lukiqq:
I've made this thread to show you how to fix this frustrating bug. After few steps you'll get working light sensor better than in previous GB versions :)

Files need to be replaced or edited:

- services.jar

- framework-res.apk

- sensors.default.so

Recommended kernel:

- Galaxian*

Based on original Samsung sources

All Voodoo addictions (color fix, sound V9)

CPU frequencies: 100MHz, 200MHz, 400MHz, 800MHz, 1000MHz, 1200MHz, 1300MHz, 1400MHz.

CONFIG_HZ=500

CWM 3.0.0.5 based on, and fully compatible with CF-ROOT

Light sensor polling 1s instead of 2s

Compatible with RFS and EXT4

Much more I can't remember

What needs to be done:

framework-res.apk edit

1. Get apk manager (attached)

2. Put framework-res.apk in "place-apk-here-for-modding" folder

3. Run apk manager, decompile with dependancy (option 10)

4. Drag twframework-res.apk from your ROM into the script, or extract it somewhere and type path to it

5. Go into projects\framework-res\res\values\arrays.xml

6. Replace two sections:

7. Delete .bak file if you got one after changes

8. Go back to script and select compile

9. Say y

10. Say y

11. Delete resources.arsc from keep folder

12. Enter in script

13. U'll find unsignedframework-res.apk in "modding" folder

14. Use ADB

adb push unsignedframework-res.apk /data/local/tmp/framework-res.apk
adb shell
su
mount -o rw,remount /dev/block/stl9 /system
stop
rm /system/framework/framework-res.apk
cp /data/local/tmp/framework-res.apk /system/framework/
rm /data/local/tmp/framework-res.apk
reboot

services.jar replace/edit

Attached services.jar should be compatible with all JVP releases as long as author didn't modified it. If you are not sure you can always edit your own version by doing:

1. Get apk manager (attached)

2. Put services.jar in "place-apk-here-for-modding" folder

3. Rename it to services.apk

4. Run apk manager, decompile (option 9)

5. Go into projects\services.apk\smali\com\android\server\

6. Replace PowerManagerService.smali file with the one from my services.jar

7. Delete .bak file if you got one after changes

8. Go back to script and select compile

9. Say n

13. U'll find unsignedservices.apk in "modding" folder

14. Rename it to services.jar

14. Use ADB

adb push services.jar /data/local/tmp/
adb shell
su
mount -o rw,remount /dev/block/stl9 /system
stop
rm /system/framework/services.jar
cp /data/local/tmp/services.jar /system/framework/
rm /data/local/tmp/services.jar
reboot

sensors.default.so replace

1. Use ADB

adb push sensors.default.so /data/local/tmp/
adb shell
su
mount -o rw,remount /dev/block/stl9 /system
stop
rm /system/lib/hw/sensors.default.so
cp /data/local/tmp/sensors.default.so /system/lib/hw/
chmod 644 /system/lib/hw/sensors.default.so
rm /data/local/tmp/sensors.default.so
reboot

GALAXIAN KERNEL:

1. Go to the Market place

2. Install SGS kernel flasher

3. Extract zImage.7z to your internal SD card

4. Select zImage and flash

5. Be happy

New version of sensors.default.so! Now all 4 steps are working!

BTW. With those files you will now loose BLN!
[Galaxy S I9000 Android Development] Brotuck:
Thank you very much in providing this fix. :)
[Galaxy S I9000 Android Development] yoohoo:
Thks

This is what I have been waiting for....

I will recompile my services.jar n framework-res.apk and incorporate them into my custom rom.

Thank you so much!
[Galaxy S I9000 Android Development] $omator:
i do not get it =) what is this fixing Oo
[Galaxy S I9000 Android Development] Faryaab:
It fixes the Auto brightness issue in some kernels.
[Galaxy S I9000 Android Development] $omator:
i guess when auto brightness is checkedit is not reacting or reacting wrong?
[Galaxy S I9000 Android Development] FuryriderX:
Im guessing this only works on deodexed?
[Galaxy S I9000 Android Development] flypubec:
This is a fix of the moth !

THANK YOU SIR !

btw., what kernel is this? your own ?

Simce I can't find Galaxian anywhere on the forum.

Btw. where are the attached binaries from? Extract from original JVP kernel ?
[Galaxy S I9000 Android Development] Brotuck:
In some kernels the brighness is reversed or totally wrong.

This has fixed it.
[Galaxy S I9000 Android Development] eternal-intent:
@ Brotuck

Will you try and include this in your GingerMod Rom? (...does it need it?)
[Galaxy S I9000 Android Development] Brotuck:
I already updated my GM22 @ damians site.

It also uses a slightly different value, tested it today worked fine !
[Galaxy S I9000 Android Development] eternal-intent:
Cool.

Well, I'm off to check it out...

And to the OP thanks, I'm interested to see what effect this has...it's not that I'm lazy, I just still lack confidence in my adb (dis)ability :confused: or I'd be more inclined to try and do it myself. :o:D
[Galaxy S I9000 Android Development] qxv1:
CWM can ask :-)
[Galaxy S I9000 Android Development] $omator:
ok now i see what is going on here =)
[Galaxy S I9000 Android Development] habylab:
Ill look at this properly, but couldn't you put this in a CWM flashable package? Thanks if you can.

Sent from my ever changing Galaxy S
[Galaxy S I9000 Android Development] asicman:
CWM flashable package, please :D
[Galaxy S I9000 Android Development] Brotuck:
The biggest "problem" is that you need to change values in the framework.

And that one is connected to the theme you use.

Battery color / lockscreens stuff like that.

So making 1 general CWM is a problem.... ;)

If you encounter brightness problems, like not responding to changes or bright light in the dark (when it should be darker)

Then but only then consider this mod, if you do not know how to do it, then ask the theme maker. ;)
[Galaxy S I9000 Android Development] $omator:
ill rephrase my question =)

why those fixes (left stock, right this fix/tweak)

ALL_BRIGHT from 15 to 255

ANIM_STEPS from 10 to 50

AUTOBRIGHTNESS_ANIM_STEPS from 10 to 50

LIGHT_SENSOR_DELAY from 2000 to 1000
[Galaxy S I9000 Android Development] paratox:
@$omator: it`s working! i think this is the only relevant answer!

you know a better way? then do it and start your own thread! :P
[Galaxy S I9000 Android Development] TheVisitorX:
I'd like to try this fix but I can't because each time >compile< gets me an error in APK Manager! Something like "unknown source" and "could not exec command". Does anyone here have any success with this fix and Bezke JVP-ROM?
[Galaxy S I9000 Android Development] Lukiqq:
Sensors.default.so isn't 100% same as original JVP one... It is JVH one, COMPLETELY DIFFERENT! Like paratox said, if you know how to do that better, create your own topic and stop be nosy...
[Galaxy S I9000 Android Development] $omator:
sensors.default.so that is 1:1 stock JVP

is fixing here

i guess

as any other changes are irrelevant am curious why arent they listed as additional 'tweeks' in main post or something

just want anserws =)
[Galaxy S I9000 Android Development] $omator:
oh true i must have compared it to jvo one =)

anyways what is the purpouse of other changes?

and why not use jvp stock lib ?