Related
Hi
I've upgraded to 2.3.3 and my camera doesnt work anymore. The screen comes black for a few seconds and then the message "Camera error. Cannot connect to camera" appears. The flashlight is also doesnt work. I have some MoDaCo firmware HTC Sense before, as I remember...
Help me to fix it, please.
Thanks
Flash newer radio.
Jack_R1 said:
Flash newer radio.
Click to expand...
Click to collapse
Could you tell me how to do it, pls? What is the last version of radio? How to check it?
Settings / About / Baseband
If the version is 4.06 / 5.08 / 5.12 (the version is in the middle of the long string there) - then there's some other problem in the system. If the version is 4.02 or 4.04 - then you need to go to Developers forum, open any Gingerbread ROM thread, and see the instructions for flashing Radio. Or look at my signature.
Jack_R1 said:
Settings / About / Baseband
If the version is 4.06 / 5.08 / 5.12 (the version is in the middle of the long string there) - then there's some other problem in the system. If the version is 4.02 or 4.04 - then you need to go to Developers forum, open any Gingerbread ROM thread, and see the instructions for flashing Radio. Or look at my signature.
Click to expand...
Click to collapse
The Baseband Version is 32.41.00.32U_5.08.00.04
What I'm thinking is could it be the problem because my Nexus had non original firmware before the GB update, and maybe I didnt make some important thing which blocking my camera now? Maybe I need to re-flash the radio with some original image? I'm totally NOOB in all these things...
Your radio is 5.08 - which means it's updated and the problem is elsewhere.
If you didn't upgrade to Gingerbread from a clean FRG83G build, but from some other build - you'll need to reflash the ROM. You can do it if you have unlocked bootloader. Read Wiki, it has the guide for installing custom ROMs - execute it, and use Gingerbread stock build from one of the threads in Development forum.
Jack_R1 said:
Your radio is 5.08 - which means it's updated and the problem is elsewhere.
If you didn't upgrade to Gingerbread from a clean FRG83G build, but from some other build - you'll need to reflash the ROM. You can do it if you have unlocked bootloader. Read Wiki, it has the guide for installing custom ROMs - execute it, and use Gingerbread stock build from one of the threads in Development forum.
Click to expand...
Click to collapse
Thanks for your advices. Just upgraded the radio to 5.12 via fastboot. The camera still not work Will try to flash to original state...
ok, i've tried to rollback to original FRG83, se-flashed boot, recovery, but no luck - camera didnt started. Hovewer, i tried the flashlight torch and it started to work (it didn't like a camera before), so I'm sure now the camera issue is the software now - not a hardware.
Does anybody have some advices?
P0MkA said:
ok, i've tried to rollback to original FRG83, se-flashed boot, recovery, but no luck - camera didnt started. Hovewer, i tried the flashlight torch and it started to work (it didn't like a camera before), so I'm sure now the camera issue is the software now - not a hardware.
Does anybody have some advices?
Click to expand...
Click to collapse
How did you flash frg83? via passimg or you flashed rooted rom from dev section? If you didn't use passimg method you should try wiping everything (cache, dalvik, factory reset) from the recovery.
BTW, if you have custom recovery you should be able to restore nandroid backup (which I assume you did;P ) and see if there is this problem too.
Cheers!
k_myk said:
How did you flash frg83? via passimg or you flashed rooted rom from dev section? If you didn't use passimg method you should try wiping everything (cache, dalvik, factory reset) from the recovery.
BTW, if you have custom recovery you should be able to restore nandroid backup (which I assume you did;P ) and see if there is this problem too.
Cheers!
Click to expand...
Click to collapse
i've flashed frg83 using fastboot. And updated to 2.3.3 via recovery (RA-passion-v2.2.1). And yes, I wiped everything using the recovery. Unfortunately, I do not know what is nandroid backup, so I didnt do it
Hope there is a way to get my camera back to work... Could you tell me what to do, step by step, to make my Nexus fully functional with the 2.3.3 firmware, please!
P0MkA said:
i've flashed frg83 using fastboot. And updated to 2.3.3 via recovery (RA-passion-v2.2.1). And yes, I wiped everything using the recovery. Unfortunately, I do not know what is nandroid backup, so I didnt do it
Hope there is a way to get my camera back to work... Could you tell me what to do, step by step, to make my Nexus fully functional with the 2.3.3 firmware, please!
Click to expand...
Click to collapse
I'd love to, but unfortunately I don't know what causes this problem at the moment I think it wouldn't hurt to try loging what is going on when you open camera.apk. Try adb logcat from your pc or install "alogcat" from market, start camera app and paste here the log file.
Lesson for future always do nandroid backup You can do this from recovery, it will do phone's memory image Then you can always revert back to what you had before flashing new rom
k_myk said:
I'd love to, but unfortunately I don't know what causes this problem at the moment I think it wouldn't hurt to try loging what is going on when you open camera.apk. Try adb logcat from your pc or install "alogcat" from market, start camera app and paste here the log file.
Lesson for future always do nandroid backup You can do this from recovery, it will do phone's memory image Then you can always revert back to what you had before flashing new rom
Click to expand...
Click to collapse
Yeah... backuping is a cool thing.... It is just my first experience with the Android phone... Maybe will find some kind of solution for this...
Well... Problem stays... However I've found few interesting things. As I've mentioned above, after the 2.3.3 update the camera and flashlight doesnt work enymore. But I've installed Z-DeviceTest and found that after the reboot this app (which provides the hardware test) sees the camera and flashlight! But, unfirtunately, doesnt able to test it. Moreover, if to start some torchlight widget directly after the reboot, the flashlight works!!! But it is not after the camera start... So, maybe someone will find this information useful.
@Pomka
have you found the Satu Solution yet ?
mmm. i guess you borrow from somebody the nandroid back up and restore it...
then u will know whether it is a hardware issue or Software Issue.
Logic ?
sevensaints said:
@Pomka
have you found the Satu Solution yet ?
mmm. i guess you borrow from somebody the nandroid back up and restore it...
then u will know whether it is a hardware issue or Software Issue.
Logic ?
Click to expand...
Click to collapse
Stupid actually. Its stay the same, not working....
found the solution!
http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91
You have go go back to stock ROM.....then camera Happy Trigger Finger!
yeah...
1. Go back to stock through HBOOT
2. Flash back ur fav ROM - mine-MIUI AU
pls click thanks
I have searched thoroughly through the various CWM and OC Kernel threads but it's not clear to me if I can achieve having ClockworkMod Recovery and an Overclocked Kernel running on a Sprint (CDMA) Tab without any issues with the GPS or Camera.
I am perfectly fine running the stock Samsung ROM, but want to be able to overclock to 1.4GHz and be able to run CWM so that I can at least be able to do nandroid backups. From what I gather some of these CWM solutions and OC kernels (which may be really designed for Verizon Tabs and not Sprint Tabs) may cause issues with the GPS and/or Camera. I cannot afford to lose those two functions of the Tab.
So for those Sprint owners out there, what has worked for you to get a working CWM and OC kernel without sacrificing the GPS and Camera? Thanks!
apparently this isn't possible? it's a shame...as if a CDMA Tab were bad enough, it looks like the Sprint one is the true ugly stepchild of the bunch.
The VooDoo CDMA Kernel that I just flashed appears to have a working FF and RF camera as well as working GPS.
I'm pretty new to the SGS scene so I may not be talking about the same thing you are.
ad720 said:
The VooDoo CDMA Kernel that I just flashed appears to have a working FF and RF camera as well as working GPS.
I'm pretty new to the SGS scene so I may not be talking about the same thing you are.
Click to expand...
Click to collapse
Awesome! So you are using a Sprint Tab? And you can run Google Maps or Navigation and it locks your location using GPS? I just want to be sure before I proceed down this path, since I've read about some users not being able to get their GPS to operate once they've borked it.
And if you don't mind me asking, how did you get the VooDoo CDMA Kernel on there? Did you first install v4 through SGS Kernel Flasher or perhaps Heimdall? And then you installed v5 through CWM?
Thanks!
Yes, Sprint Tab (I just got it from the most recent woot sale).
Google Maps locked to my location within 20 meters inside of my office, and then dead on my front door just now. I turned my WIFI off to make sure it was really the GPS. I started up Navagation and it showed waiting for GPS for a about 2 seconds before starting with the turn by turn.
I have taken pictures with the RF and FF camera but I haven't tried a video chat so that might not work. When I take a picture the preview does glitch out on the screen a bit but the picture is just fine.
I flashed the latest version directly through SGS Kernal Flasher. I don't have the files in front of me but I just followed the directions in the OP.
The issue that I had was my auto-rotation wasn't working. I found the file to replace in the thread but root explorer wasn't recognizing my SD card until I turned off the VooDoo enhancements in CWM and then turned them back on as specified by the troubleshooting section of the OP. At that time I was able to replace the file to restore auto-rotate.
Please keep in mind that while I am not new to Android I am quite new to the SGS so do plenty of reading and keep in mind that this is just my experience (or inexperience) with it and I may just have gotten lucky.
Also, I do NOT have data services through Sprint, I am using WIFI only so I can't speak to the effects of the Kernel on that.
Good luck!
Thats pretty awesome, atleast we have an alternative until Samsung hopefully release the 3.34 for all G tab owners.
ad720 said:
I flashed the latest version directly through SGS Kernal Flasher. I don't have the files in front of me but I just followed the directions in the OP.
Click to expand...
Click to collapse
Thanks again. This is really helpful. But from what I understand the latest version (v5) is only updatable through CWM. v4 can be flashed through SGS Kernel Flasher. Is it possible you're not running v5?
onlinespending said:
Thanks again. This is really helpful. But from what I understand the latest version (v5) is only updatable through CWM. v4 can be flashed through SGS Kernel Flasher. Is it possible you're not running v5?
Click to expand...
Click to collapse
Correct. I'm looking at the files now and I used SGS Flasher to do the v4 (step 1) and then CWM to do the v5.zip (step 2). If there is a way to verify which Kernel, let me know and I'll double check.
ad720 said:
Correct. I'm looking at the files now and I used SGS Flasher to do the v4 (step 1) and then CWM to do the v5.zip (step 2). If there is a way to verify which Kernel, let me know and I'll double check.
Click to expand...
Click to collapse
Hmm, for some reason I cannot get v4 flashed using either SGS Flasher or Heimdall. I first got the latest OTA update (build EB28) before doing this however, so I'm not sure if that is an issue. Can you confirm you were or are on build EB28 (under Settings -> About My Galaxy Tab)?
onlinespending said:
Hmm, for some reason I cannot get v4 flashed using either SGS Flasher or Heimdall. I first got the latest OTA update (build EB28) before doing this however, so I'm not sure if that is an issue. Can you confirm you were or are on build EB28 (under Settings -> About My Galaxy Tab)?
Click to expand...
Click to collapse
I can confirm that I am currently on EB28. Not sure if it was different before the Kernel flash. I got two OTAs before I even really started to play with the Tab...
Where are you running into a problem? Does SGS not run?
ad720 said:
I can confirm that I am currently on EB28. Not sure if it was different before the Kernel flash. I got two OTAs before I even really started to play with the Tab...
Where are you running into a problem? Does SGS not run?
Click to expand...
Click to collapse
Sounds like you had EB28 even before you did the flash. SGS runs fine. It says the kernel flashed successfully, but upon reboot the Tab is just stuck at the Samsung boot screen. I cannot even enter Recovery (using Vol Up + Power).
I've reverted to stock and have tried a few times all with the same result (even tried Heimdall and Odin).
There has to be something different between our Tabs that would cause the issue I'm seeing.
After the EB28 update, I have the following:
Hardware version: P100.08
Firmware version: 2.2.1
Baseband version: S100.08 S.EB28
Kernel version: 2.6.32.9
Build number: SPH-P100.EB28
Unless you have something different in one of the above, I'm at a bit of a loss. I may need to go some alternative route.
The first OTA on my device is downloaded, but not installed, and I'm curious if I should even take them at all?
I currently have the following:
Hardware version: SPH-P100.08
Model number: SPH-P100
Firmware version: 2.2
Baseband version: S100.08 S.DJ29
Kernel version: 2.6.32.9
Build number: SPH-P100.DJ30
I'd like some type of recovery and eventually HC... boy these Sprint tabs, and tabs in general, are funky compared to my Incredible.
onlinespending said:
Sounds like you had EB28 even before you did the flash. SGS runs fine. It says the kernel flashed successfully, but upon reboot the Tab is just stuck at the Samsung boot screen. I cannot even enter Recovery (using Vol Up + Power).
I've reverted to stock and have tried a few times all with the same result (even tried Heimdall and Odin).
There has to be something different between our Tabs that would cause the issue I'm seeing.
After the EB28 update, I have the following:
Hardware version: P100.08
Firmware version: 2.2.1
Baseband version: S100.08 S.EB28
Kernel version: 2.6.32.9
Build number: SPH-P100.EB28
Unless you have something different in one of the above, I'm at a bit of a loss. I may need to go some alternative route.
Click to expand...
Click to collapse
That is identical to mine.
I wish I knew more about the tab so I could be a help.
Well seems like I solved my problem. Not entirely sure why, but when I swapped in a small 1GB sdcard I was able to flash this Kernel without issue. Using the 16GB card that came with the Sprint Tab didn't work.
onlinespending said:
Well seems like I solved my problem. Not entirely sure why, but when I swapped in a small 1GB sdcard I was able to flash this Kernel without issue. Using the 16GB card that came with the Sprint Tab didn't work.
Click to expand...
Click to collapse
Maybe a format issue? That's interesting...
I had a similar issue with the 16gb card. put a 2gb card in, and was able to flash the kernel and then get into CWM. sadly once I got that far it didn't seem to matter what rom/kernel i tried it wouldn't boot past the samsung logo anymore. So back to stock rooted for now I guess.. Really want to play with the HC port, but not sure why it won't work. Also can't seem to get Heimdall to recognize my Tab, Odin works fine however.
another new Sprint SGT owner from Woot sale here. Also just flashed the Voodoo OC kernel last night, all seems well camera and GPS etc, I have no idea if 3g works as there is no Sprint in my state.
I flash the V5 using a guide I found over on the unlocker site. took several tries before I got it to go, lots of command line stuff and I think I had a few typos along the way.
Another woot sprint tab user here... I also have "KhasMek Voodoo Plus v5" installed on my tab but GPS does not work for me. Well, it has never worked for me even with stock kernel and EA24 ROM.
Any other woot user with a none working GPS straight out of box?
Update: GPS will not lock if Sprint tab is in airplane mode. Even though by the window works for my HTC hero phone but not the tab. It needs to be outdoor in order to get proper GPS signal.
I have been using the latest cos-ds rom 2.3.4 on my G1 (rooted) it was working good then I was messing in rom manager and it installed (after backing up my old system) a rom from ROM MANAGER (free version) i think it was ginger yoshi. it never booted the D/l rom just a G1 loop at startup. now i have my phone restored and i keep getting the error com.android.phone and the force close button and i have no cell service. here is what i can manage to get info wise.
under about phone:
model # cos-ds
android version 2.3.4
Baseband version: Unknown
Kernel Version: 2.6.36.4-s3-cos
Mod Version: cos-ds-07182011
Build #: grj22
The phone wont let me enter Mobile Networks button under wireless ands network. Any help would be greatly appreciated
Same answer as the other post:
http://forum.xda-developers.com/showthread.php?t=1222438
lol ^^ same problem twice in a row??
ldrifta said:
lol ^^ same problem twice in a row??
Click to expand...
Click to collapse
Yea! At least to my understanding from their post. At first I thought it was a double post. But the poster was different. LOL!
haha i just had a problem yesterday just like it too... well kinda.. lol flashed cwm for a second to see if my rom showed up on rom manager, than my dog knocked my phone off table and knocked the sd card loose so my phone freaked out on me..
i couldn't figure out how to repair ext on cwm so i stupidly flashed amonra.zip (via recovery) on top of it without wiping... so now i couldn't use recovery lol had to flash orange.nbh in order to flash new recovery via fastboot, than upgraded back to 28.25 so easily lol so i live fastboot now
sorry for the long story but who knows it might help this guy out lol
congrats that you finally could find out the advantages of fastboot ...
Sent from my Gingerbread on Dream using XDA App
well i got it fixed. i used 3 different nandroid backups i had 1 on sd and 2 others on pc, they would restore the phone but still no radio. i found out when i upgraded to green rom it killed the radio for cell service. what i ended up doing was flashing back to RC29 via fastboot and then just rerooted and installed cos-ds again. kinda sucked being on android 1.0 again forgot how stripped it was of features. thanks for the help guys
I have an HTC Hero CDMA for Alltel. I have been on a quest to make it faster by overclocking or installing a new rom. Upon receiving the phone it would not work with MMS messages so Alltel had me flash the rom using HTC sync. The software came from here: http://software.alltel.com/software.aspx?deviceID=103&platformID=22. This updates the kernel to 2.41.556.1.
Since then I tried rooting it and had many difficulties. I tried 3 different rooting strategies before (semi?-) sucessfully running this one click root apk: http://forum.xda-developers.com/showthread.php?t=743289. It installs Darchstars Recovery.
I have since tried flashing 4 different roms such as cyangenmod 6.1 and 7.06. ALL of them bootloop for hours but recovery always restores the phone successfully.
None of this was working so I re rooted it again (never unrooted it, possibly a problem) following this guide: http://forum.cyanogenmod.com/topic/20126-cyanogenmod-7-for-the-htc-hero-cdma-v703-5-may-2011/. I installed the Andoid SDK on my computer and successfully ran all the needed commands to root my phone. Now instead of Darchstars Recovery it has ClockWorkMod 2.5.07. I tried installing all of the roms I tried before but again to no success.
At this point I'm desperate to just overclock it at least. I read around that people were getting into the mid 700 mhz ranges and I wanted that. So instead of a new rom with a newer Android version I wanted- I flashed a new overclock kernel onto the standard Alltel rom I updated my phone with. I used Zen Kernel found here: http://forum.xda-developers.com/showthread.php?t=750170. Upon flashing the new kernel the phone went into bootloop and exhibited the same behavior as the other roms did. I recovered and set back to normal. I tried the Zenkernal flash one more time but used StockVoltage Overclocked Kernel found on the same post. This time it worked!
With the new overclock kernel 2.62.29 I installed setcpu and overclocked. However I can only hit 672mhz with it - Not what I wanted. Also with the new kernel SuperUser permissions have to be set every time. It will not remember that I previously gave permission. Additionally RomManager 4.3.3 seemingly doesn't think my phone is rooted. It fails if I try to install a rom or new recovery through it citing that it can't get superuser permission. Even though I give it permission.
The thing I noticed that is messed up and possibly causing things to become awry is that in ClockWorkRecovery when I try to clear the Dalvik Cache I get a E:Can't Mount /Dev/block/mmcblk0p2 (file Exists) message. I'm thinking this may be causing the problems and it may have been messed up by my prior attempts to root it. Can anyone shed some light on this?
Since I installed the new updated Alltel rom 2.41.556.1. I have been reading that with Sprint the newer rom breaks the ability to root the phone using many methods. I'm starting to believe this may be the case with the newer Alltel rom as well.
From my understanding to fix my problem I need to restore everything to stock, find a way to unroot, downgrade Alltel's rom, root on the downgraded rom, flash a recovery, flash a new rom? I am unclear on how to do this and it's where I need some help.
Basically my current plan (At work can't do it now) is to:
1. Install Darchstars recovery instead of ClockWorkMods because Darchstars recovery has my first original Nandroid backup to undue everything else I've done. Clockwork and Darchstar appear not to be able to restore from one others backup Nandroid, is that correct?
2. To downgrade I was going to follow these instructions: http://tech-n-life.com/index.php/2010/01/support-sunday-how-to-un-root-your-htc-hero/. The problem I see with it is finding an original Alltel RUU as opposed to Sprints.
3. Root and install new rom.
Does anyone have suggestions or a better way to approach this in finding a way to flash a new rom and actually have it work?
I'm not on Alltel, but you're definitely on the right track to resolve the issue.
I know there's a ruu for the Alltel around here. I remember reading it a while back. After PT I'm come back and help locate it with you.
And keep up the excellent investigation! I applaud your digging efforts. First round is on me if I see you at the bar.
I've made much progress in the way of getting it rooted. Just about everything on the internet WILL NOT WORK to root it. Most of it is out of date. I have finally rooted it and have made it stay rooted. I found out that the device would unroot itself after rebooting it - must be something with the newer Alltel version 2.41 idk.
I used this post and program to root it: forums.regawmod.com/showthread.php?tid=6
The above attempt has flaws however. It makes the recovery inoperable. To fix this I ran the commands below in ADB. These commands are the only way to get a recovery on the phone properly. I have found every guide on the net is outdated or incomplete; after lots or trial and error I developed this. Flash_image and a recovery image are needed.
Code:
cd /d E:\HTC Hero\rooting
adb push recovery-RA-heroc-v1.6.2.img /sdcard/recovery-RA-heroc-v1.6.2.img
adb push flash_image /sdcard/flash_image
adb shell
su
mount -o remount,exec /dev/block//vold/179:1 /sdcard
cd /sdcard/
./flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
reboot recovery
--------or-------
adb push recovery-clockwork-2.5.0.7-heroc.img /sdcard/recovery-clockwork-2.5.0.7-heroc.img
./flash_image recovery /sdcard/recovery-clockwork-2.5.0.7-heroc.img
At this point the WiFi is broken and unable to start because of the root.
I flashed zenkernal again and, like before, the one with perflock disabled will not boot and the one with perflock on works - this kernel corrected the wifi issue. forum.xda-developers.com/showthread.php?t=750170
I'm pretty much back to where I started. I have to grant super user access constantly again. However I found this can be fixed by flashing "su-2.3.6.1-ef-signed.zip" via recovery mode.
Because I can't get a new rom to work I have pretty much altered the stock rom in a way that suits me. I have it overclocked decently (wished for more) at 673, it's 100% stable, and I used Fresh Kitchen 3.0.0.1 to delete all the crap such as Amazon MP3 that was on my phone.
Support for the Alltel HTC Hero is very lacking around the net. Strategies that work on Sprint and other phones don't work on this one. Also most strategies are very outdated. It seems I missed the bus by buying this phone at this point in time - but I did get a really good deal on it.
EDIT: I have constantly read about s-on and s-off but no one ever actually said what it was or what it had to do with anything. I didn't think it was important. I just researched it and mines on still. I'm gonna give everything a try again once I get it off.
Edit2: S is off via flashing unrevoked-forever.zip in recovery. It made no difference for booting other roms. The only apparent thing that I noticed is that the E:Can't Mount /Dev/block/mmcblk0p2 (file Exists) message is gone - it may have been fixed a while ago and I just never noticed.
Currently the phones set to S-off
adb says the phone is rooted via the # symbol
It's running Clockwork2.5.0.7
It's running ZenKernel-HTC-08122010 perf lock 2.6.29
Alltel Software version 2.41.556.1
Super User package su-2.3.6.1-ef-signed.zip
Overclocked to 672mhz
However RomManager says, "An error occured while attempting to run privileged commands!" and SystemTuner claims my phone is not rooted.
I don't know what to do with this phone.....
Hmm, that doesn't sound good. I recently had trouble with changing VM and busy box, and managed to destroy my phones driver's. I couldn't connect to Wi-Fi(MAC address was <UNKNOWN>), Bluetooth(Address was <UNKNOWN>, or mobile(My phone number was missing). After factory reset, I took it to Alltel and they said they would put an update on it that would fix many problems. It now works, but lags more, it doesn't crash as much, seems to run warmer, and the battery doesn't last as long. I was wondering if it was just a minor overclocking mod and a few bug fixes, but if root doesn't work, that may be a problem for me.
Flash that zenkernel I mentioned. It seems to somehow be better with battery life.
I have no way to prove this but I work from 7am till 5:30pm. Before the zenkernel battery life would be around 70% after work. The other day it was at a low 80% after the kernel update. It may have been affected by outside temperatures as well I have no idea but it does appear to have better battery life.
DerekZ10 said:
Flash that zenkernel I mentioned. It seems to somehow be better with battery life.
I have no way to prove this but I work from 7am till 5:30pm. Before the zenkernel battery life would be around 70% after work. The other day it was at a low 80% after the kernel update. It may have been affected by outside temperatures as well I have no idea but it does appear to have better battery life.
Click to expand...
Click to collapse
this is the same thing you did from the alltel site but there is a flashable zip for the update you used.
http://forum.xda-developers.com/showthread.php?t=894925
or this one
http://pcdphones.com/our-devices/products/75-adr6250al/downloads/42
maybe a bad download
for root look here
http://forum.xda-developers.com/showthread.php?t=710483
i would try one of dac's kernels here
http://forum.xda-developers.com/showthread.php?t=756774
you can try flashing this alltel rom i was messing with.
http://dev-host.org/?op=my_files&fld_id=24
this is all ready rooted and the updated one you flashed.
DerekZ10 said:
I have an HTC Hero CDMA for Alltel. I have been on a quest to make it faster by overclocking or installing a new rom. Upon receiving the phone it would not work with MMS messages so Alltel had me flash the rom using HTC sync. The software came from here: http://software.alltel.com/software.aspx?deviceID=103&platformID=22. This updates the kernel to 2.41.556.1.
Since then I tried rooting it and had many difficulties. I tried 3 different rooting strategies before (semi?-) sucessfully running this one click root apk: http://forum.xda-developers.com/showthread.php?t=743289. It installs Darchstars Recovery.
I have since tried flashing 4 different roms such as cyangenmod 6.1 and 7.06. ALL of them bootloop for hours but recovery always restores the phone successfully.
None of this was working so I re rooted it again (never unrooted it, possibly a problem) following this guide: http://forum.cyanogenmod.com/topic/20126-cyanogenmod-7-for-the-htc-hero-cdma-v703-5-may-2011/. I installed the Andoid SDK on my computer and successfully ran all the needed commands to root my phone. Now instead of Darchstars Recovery it has ClockWorkMod 2.5.07. I tried installing all of the roms I tried before but again to no success.
At this point I'm desperate to just overclock it at least. I read around that people were getting into the mid 700 mhz ranges and I wanted that. So instead of a new rom with a newer Android version I wanted- I flashed a new overclock kernel onto the standard Alltel rom I updated my phone with. I used Zen Kernel found here: http://forum.xda-developers.com/showthread.php?t=750170. Upon flashing the new kernel the phone went into bootloop and exhibited the same behavior as the other roms did. I recovered and set back to normal. I tried the Zenkernal flash one more time but used StockVoltage Overclocked Kernel found on the same post. This time it worked!
With the new overclock kernel 2.62.29 I installed setcpu and overclocked. However I can only hit 672mhz with it - Not what I wanted. Also with the new kernel SuperUser permissions have to be set every time. It will not remember that I previously gave permission. Additionally RomManager 4.3.3 seemingly doesn't think my phone is rooted. It fails if I try to install a rom or new recovery through it citing that it can't get superuser permission. Even though I give it permission.
The thing I noticed that is messed up and possibly causing things to become awry is that in ClockWorkRecovery when I try to clear the Dalvik Cache I get a E:Can't Mount /Dev/block/mmcblk0p2 (file Exists) message. I'm thinking this may be causing the problems and it may have been messed up by my prior attempts to root it. Can anyone shed some light on this?
Since I installed the new updated Alltel rom 2.41.556.1. I have been reading that with Sprint the newer rom breaks the ability to root the phone using many methods. I'm starting to believe this may be the case with the newer Alltel rom as well.
From my understanding to fix my problem I need to restore everything to stock, find a way to unroot, downgrade Alltel's rom, root on the downgraded rom, flash a recovery, flash a new rom? I am unclear on how to do this and it's where I need some help.
Basically my current plan (At work can't do it now) is to:
1. Install Darchstars recovery instead of ClockWorkMods because Darchstars recovery has my first original Nandroid backup to undue everything else I've done. Clockwork and Darchstar appear not to be able to restore from one others backup Nandroid, is that correct?
2. To downgrade I was going to follow these instructions: http://tech-n-life.com/index.php/2010/01/support-sunday-how-to-un-root-your-htc-hero/. The problem I see with it is finding an original Alltel RUU as opposed to Sprints.
3. Root and install new rom.
Does anyone have suggestions or a better way to approach this in finding a way to flash a new rom and actually have it work?
Click to expand...
Click to collapse
Any of these should work :: http://www.pcdphones.com/our-devices/support/adr6250update but u should try the Bittersweet ROM (http://forum.xda-developers.com/showthread.php?t=658755) And i use the Kernel from here: (http://forum.xda-developers.com/showthread.php?t=1110418) AND if that dont work try dropping it and see if that helps (hasn't for me ... but does relieve some stress)
DerekZ10 said:
Flash that zenkernel I mentioned. It seems to somehow be better with battery life.
I have no way to prove this but I work from 7am till 5:30pm. Before the zenkernel battery life would be around 70% after work. The other day it was at a low 80% after the kernel update. It may have been affected by outside temperatures as well I have no idea but it does appear to have better battery life.
Click to expand...
Click to collapse
I'm really not wanting to mess my phone up again, I should be getting a new one shortly, then I will test out flashing ROMs and all that. I get the idea and how its done, I just don't feel like taking the chance. My stomach dropped literally when I turned my phone on and it had no service and the HTC video didn't display. I thought the phone company may deny fixing it, but I came up with an elaborate story that the lady there took. She did break into my phone though, and now it is still partially opened in between the volume keys, and the silver vertical bar that goes around the phone, I wasn't happy about that.
The end game is to hopefully disable my bootloader so HBOOt finally reads: (S-OFF). Have had phone rooted for a while but would like more freedom and after flashing a nightly seemed to have lost root... but with ur guys's help, hopefully no more!
Explicitly Following the directions below:
http://forum.xda-developers.com/showthread.php?t=850308
As I understand it, I simply need to flash the .27 radio, (however all the dropbox links appear to be down) Could someone please post an active one for me.
I am running the unofficial CWM Recovery V4.0, however, I plan on flashing the CWM V 2.5 to make my life easier.
Here is a rough outline of my approach to unlocking bootloader? Any suggestions, corrections, and feedback, would be greatly appreciated. The last thing I want to do is brick my Hero.
Note: Because i have the latest radio and CWM (v.4), Android Version 2.3.4 AOSP flavo
1. Flash CWM rec. 2.5
2.downgrade radio to .27 (would greatly appreciate a fresh dropbox link)
3. Place HERCIMG.zip on the root of SD (carefully following the directions listed)
3.upgrade radio to .29
Voila S-OFF ...?
Thanks in advance
BTW, if anyone wants any Google music beta invites I have plenty
I believe I have an RUU sitting around that has the .27 radio. I'll package it into a flashable zip.
Sent from Dorian's EVO 3D
moisaal said:
The end game is to hopefully disable my bootloader so HBOOt finally reads: (S-OFF). Have had phone rooted for a while but would like more freedom and after flashing a nightly seemed to have lost root... but with ur guys's help, hopefully no more!
Explicitly Following the directions below:
http://forum.xda-developers.com/showthread.php?t=850308
As I understand it, I simply need to flash the .27 radio, (however all the dropbox links appear to be down) Could someone please post an active one for me.
I am running the unofficial CWM Recovery V4.0, however, I plan on flashing the CWM V 2.5 to make my life easier.
Here is a rough outline of my approach to unlocking bootloader? Any suggestions, corrections, and feedback, would be greatly appreciated. The last thing I want to do is brick my Hero.
Note: Because i have the latest radio and CWM (v.4), Android Version 2.3.4 AOSP flavo
1. Flash CWM rec. 2.5
2.downgrade radio to .27 (would greatly appreciate a fresh dropbox link)
3. Place HERCIMG.zip on the root of SD (carefully following the directions listed)
3.upgrade radio to .29
Voila S-OFF ...?
Thanks in advance
BTW, if anyone wants any Google music beta invites I have plenty
Click to expand...
Click to collapse
Here is the .27 radio flashable from any recovery and it is signed: http://db.tt/wEKZmkA
Then go to this link and flash the download at the bottom from recovery as well: http://forum.xda-developers.com/showthread.php?t=759955
Once its all done reboot your phone then reboot to your bootloader to see if you have S-OFF. Once you do flash this to get .29 radio: http://db.tt/pDMHHpH
Big upps man, really appreciate it
Seems as though the .27 signed radio did not do its job? I placed the .zip file on the SD Root and continued to flash, it seemed like it worked but Im still stuck on .29 Any ideas?
moisaal said:
Seems as though the .27 signed radio did not do its job? I placed the .zip file on the SD Root and continued to flash, it seemed like it worked but Im still stuck on .29 Any ideas?
Click to expand...
Click to collapse
I'll redo it then
Edit: link: http://db.tt/q4jFubA
Still nothing doing. Is it possible that the CWM 4 is the problem? and i should reflash a lower version. That time during recovery it looked like it genuinely worked but the baseband still reflects the .29 . Thanks for all your help
moisaal said:
Still nothing doing. Is it possible that the CWM 4 is the problem? and i should reflash a lower version. That time during recovery it looked like it genuinely worked but the baseband still reflects the .29 . Thanks for all your help
Click to expand...
Click to collapse
Yeah maybe try a 2.x recovery. It should work with 4.x but idk why.
Sent from Dorian's EVO 3D
I went into rom manager and tried to flash their current recovery and halfway through it yielded an error because the wifi disconnected, however, after doing it again it said Clockwork mod succesfully flashed. Upon booting the phone i just get to this White HTC screen with Fastboot USB in red .
Edit: Took out the battery and rebooted the phone with no problem. Lets hope things go smoother from here.
got it sorry for the rambling. XDA is a hell of a drug
It was all a matter of flashing the 2.5V of CWM recovery, after that i didnt encounter anymore hiccups. Thanks again for your help.