Related
My phone's camera refuses to work in custom ROMs. It works in the stock ROM without any problems whatsoever.
It's not ROM specific, I've tried a bunch of ROMs.
The camera app will FC on open, or display an error message (unable to connect to camera) or give me a black screen. It depends on the ROM.
Last ROM I tried was CM9, which gives me an "unable to connect" error (with and without patch #2). But it's not just CM, camera didnt work in any of the virtuous ROMs either.
When I flash back to the stock ROM, the camera just works.
Please don't assume user error. It isn't. I manually full-wipe every time I switch ROMs. I try the camera first thing, after a "clean" install, before installing any apps.
I'm now seriously considering RMAing this phone in hopes of getting a replacement unit that behaves without camera problems - but that probably means I'll get the new HBOOT and be stuck with S-ON.
So... if you have any ideas or suggestions, I'd love to hear them. I really don't understand why I seem to be the only person having this problem, but it's very frustrating. ANY help much appreciated.
dadewy said:
My phone's camera refuses to work in custom ROMs. It works in the stock ROM without any problems whatsoever.
It's not ROM specific, I've tried a bunch of ROMs.
The camera app will FC on open, or display an error message (unable to connect to camera) or give me a black screen. It depends on the ROM.
Last ROM I tried was CM9, which gives me an "unable to connect" error (with and without patch #2). But it's not just CM, camera didnt work in any of the virtuous ROMs either.
When I flash back to the stock ROM, the camera just works.
Please don't assume user error. It isn't. I manually full-wipe every time I switch ROMs. I try the camera first thing, after a "clean" install, before installing any apps.
I'm now seriously considering RMAing this phone in hopes of getting a replacement unit that behaves without camera problems - but that probably means I'll get the new HBOOT and be stuck with S-ON.
So... if you have any ideas or suggestions, I'd love to hear them. I really don't understand why I seem to be the only person having this problem, but it's very frustrating. ANY help much appreciated.
Click to expand...
Click to collapse
Are you sure you are not on the new hboot? I have flashed 6+ roms and my camera is always fine. My boyfriend has the new hboot, and when he flashed roms, his camera didn't work, because he forgot the step to flash the kernel through fastboot. I had to fix it for him. Once I flashed the kernel through fastboot, and then flashed the rom through cwm everything works great, even the camera.
yellowjacket1981 said:
Are you sure you are not on the new hboot? I have flashed 6+ roms and my camera is always fine. My boyfriend has the new hboot, and when he flashed roms, his camera didn't work, because he forgot the step to flash the kernel through fastboot. I had to fix it for him. Once I flashed the kernel through fastboot, and then flashed the rom through cwm everything works great, even the camera.
Click to expand...
Click to collapse
Well my phone says S-OFF, HBOOT 1.44.1107 so I think I'm good. Since I'm checking out the CM9 alpha2 anyway, I tried it the S-ON way, just for kicks:
adb reboot-bootloader
fastboot flash boot boot.img
<wait for it to flash, boot in to CWM>
clear cache, clear dalvik
factory reset
format /data, format /system
flash from zip: cm9alpha2
flash from zip: gapps ics 0429 version
reboot
setup gmail account
click on camera icon...
.... "unable to connect to camera"
dadewy said:
Well my phone says S-OFF, HBOOT 1.44.1107 so I think I'm good. Since I'm checking out the CM9 alpha2 anyway, I tried it the S-ON way, just for kicks:
adb reboot-bootloader
fastboot flash boot boot.img
<wait for it to flash, boot in to CWM>
clear cache, clear dalvik
factory reset
format /data, format /system
flash from zip: cm9alpha2
flash from zip: gapps ics 0429 version
reboot
setup gmail account
click on camera icon...
.... "unable to connect to camera"
Click to expand...
Click to collapse
Hmm, that is odd. Maybe it is a hardware issue, but then why would it work on stock? I hope someone else has some Ideas. I would probably just end up replacing the phone if the camera doesn't work, because that was one of the main reasons I picked this phone, was the awesome camera.
I'm in the same boat and I'm running pyros ics on the new hboot, my camera won't work. And yes it did work perfectly.
Sent from my HTC myTouch_4G_Slide using XDA
homeboy773 said:
I'm in the same boat and I'm running pyros ics on the new hboot, my camera won't work. And yes it did work perfectly.
Sent from my HTC myTouch_4G_Slide using XDA
Click to expand...
Click to collapse
And when you flash back to stock, it works again? Sort of glad to see I'm not the only one.
You guys are flashing the kernel through fastboot and adb right? When my boyfriend was flashing roms on his phone with the new hboot, his camera didn't work until I flashed the kernel to his rom through fastboot.
I've flashed quite few htc phones in the past. When I cooked and flashed rom with wrong camera software version the camera didn't work, even when I tried to manually install .cab file with correct camera app version later. It had to be cooked-in. For example Kaiser ROMs, there were camera cabs version 4.x and newer 5.x from Windows Mobile 6.0 and WM6.1 - apparently they had different camera drivers included, and different ROMs required different version of camera software (drivers). Granted, it was all Windows Mobile environment, but I think similar general rules apply to Android OS too since AFAIK some software from Ginger won't work on ICS too, which is the same as it was with WM5.0 vs WM6.1 vs WM6.5 upgrades...
So perhaps different/correct "Camera.apk" is needed for this ROM?
yellowjacket1981 said:
You guys are flashing the kernel through fastboot and adb right? When my boyfriend was flashing roms on his phone with the new hboot, his camera didn't work until I flashed the kernel to his rom through fastboot.
Click to expand...
Click to collapse
Does you bf have s-on , I think I seen you said yes. If so explain flashing the kernal. When I do it I flash the boot.img then the rom , nothing more. Doing that only pyro ics works. Every thing else fc's once I get in set up mode.
Sent from my HTC Vision using XDA
homeboy773 said:
Does you bf have s-on , I think I seen you said yes. If so explain flashing the kernal. When I do it I flash the boot.img then the rom , nothing more. Doing that only pyro ics works. Every thing else fc's once I get in set up mode.
Sent from my HTC Vision using XDA
Click to expand...
Click to collapse
That is your problem right there. When you are S on, you have to flash the Kernel separately through fastboot. That is why your camera is not working, and other things are probably wonky too. You can't just flash the rom through clockwork, with out also flashing the kernel through fastboot. Follow the directions in this thread. That is how I fixed this same issue that my bf was having. These instructions will work with any rom, not just the ICS ones. I have bulletproof working flawlessly on my bf's S-on phone, with the new hboot.
http://forum.xda-developers.com/showthread.php?t=1508556
Edit : I just reread what you posted, and saw that you are flashing the boot img. , then flashing the rom. Are you using the instructions in the above thread to do this? Those were the instructions I used and it worked perfectly. Tell me exactly what you are doing. Explain how you are flashing the boot img. Are you using fastboot, and the command prompt on your computer?,or are you flashing through clockwork? I was having an issue flashing the boot img. at first, because I was unknowingly leaving out a space. Maybe that is your issue?
Fixed!
Updating this, as I am happy to say I have CM9 alpha4 running AND have a working camera!
Alpha4 Changelog (from Alpha3)
- Alternative samsung 8mp camera driver added
So, apparently this is the magic required, since alpha 3 did NOT have a working camera, on my phone. This new alpha 4 with the alternative driver, does.
YAY!
I rooted and unlocked my One S[S4] by this guide http://forum.xda-developers.com/showthread.php?t=1583427 and it went fine.
Wifi was working fine on stock Rom but when I flashed LeeDroid's Rom and booted the wifi didn't turn on. I just said error.
Then I tried Flashing Viper One S rom and no luck it gave the same error. I tried flashing the kernel and still didn't work.
Anyway I kept on trying different things and got the wifi to turn on but now it shows the connection but doesn't connect to it. It tries two three times and automatically turns off or the phone hangs and restarts.
Please help I need wifi and I can't get it to connect.
Baseband version: 1.08ts.50.02.16_10.08e.50.04L
Build Number: 2.31.401.5 CL81535
HELP!!
Anyone here can help me please. I'm stuck with this problem as I cannot find a direct solution and I have tried eveything I can but cannot get it to connect.
When you flashed it, did you flash the boot.img before, too? Do this!
And, also important: After each change of ROM, always also wipe "System" in Recovery! Maybe some ROMs don't do so automatically. And if you change from ROM A to ROM B, also factory reset your phone.
// you find the boot.img in the zip-file you flash
I would recommend to:
- choose a ROM (Viper?), transfer it to your sd-card
- get into bootloader, flash boot.img which comes in the zip-file
- from bootloader select recovery to boot (best use TWRP)
- go to wipe, choose to wipe system, androidsecure, dalvik- and cache and do a factory reset
- select install in recovery, install new ROM
I am pretty sure, everything will work after this
andryyyy said:
When you flashed it, did you flash the boot.img before, too? Do this!
And, also important: After each change of ROM, always also wipe "System" in Recovery! Maybe some ROMs don't do so automatically. And if you change from ROM A to ROM B, also factory reset your phone.
// you find the boot.img in the zip-file you flash
I would recommend to:
- choose a ROM (Viper?), transfer it to your sd-card
- get into bootloader, flash boot.img which comes in the zip-file
- from bootloader select recovery to boot (best use TWRP)
- go to wipe, choose to wipe system, androidsecure, dalvik- and cache and do a factory reset
- select install in recovery, install new ROM
I am pretty sure, everything will work after this
Click to expand...
Click to collapse
Yes, I flashed the boot.img before then flashed the ROM from recovery.
I just did a factory reset, did not specifically do the system wipe.
Let me try wiping the system and then flash the ROM. I'll get to you after trying.
akhrot91 said:
Yes, I flashed the boot.img before then flashed the ROM from recovery.
I just did a factory reset, did not specifically do the system wipe.
Let me try wiping the system and then flash the ROM. I'll get to you after trying.
Click to expand...
Click to collapse
Okay
you could flash the official RUU ，the problem will be solved…remember.，when you flash a ROM using recovery，you'd better format SYSTEM，that's important…
Sent from my HTC One S using xda app-developers app
andryyyy said:
Okay
Click to expand...
Click to collapse
I did exactly as you said but wifi doesn't connect. When I enter my wifi password it goes to connecting and quits stating the network out of range even when I'm standing besides the router and then it hangs and reboots.
All other things work fine, i.e bluetooth, mobile network etc.
I flashed the boot.img prior to flashing the ROM in TWRP. Wiped system, android.secure, cache and wiped data/factory reset. No luck.
I've no idea why is this happening. :S
harveychina said:
you could flash the official RUU ，the problem will be solved…remember.，when you flash a ROM using recovery，you'd better format SYSTEM，that's important…
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
The RUU is a .exe file and I'm on Ubuntu 12.10. I can't run RUU.
I borrowed a friend's laptop which was running on windows 7 but could'nt get the sync manager to sync my phone.
I'm stuck!!!
Strange .. you have neighbours you can ask to connect to their wifi for test?
Is your wifi "b/g" or "n" only?
Will write when I got another idea .. sorry.
andryyyy said:
Strange .. you have neighbours you can ask to connect to their wifi for test?
Is your wifi "b/g" or "n" only?
Will write when I got another idea .. sorry.
Click to expand...
Click to collapse
Yes, They can let me do that. I'll try that too.
Its b/g/n.
Its so frustrating, can't connect to wifi.
It's a T-Mobile phone with Hboot 1.14.0004 maybe this can help you think of something.
Thanks for your help.
akhrot91 said:
Yes, They can let me do that. I'll try that too.
Its b/g/n.
Its so frustrating, can't connect to wifi.
It's a T-Mobile phone with Hboot 1.14.0004 maybe this can help you think of something.
Thanks for your help.
Click to expand...
Click to collapse
Hey,
searched the Viper thread:
"Hello,
Did you do the 2.35 OTA from T-Mobile? If so then you can't get Wi-Fi working on any other rom then Trickdroid 7.0.0 or Stock 2.35. It all has to do with the way Wi-Fi is handled in 2.35 and hboot 1.14 not letting you downgrade those partitions.
You Could always SuperCID your phone and in stall the 2.31 RUU then install Viper. That has the same hboot so you shouldn't have any problems. I haven't tried this because I dont need to. Hope that helps.
Rsotbiemrptson"
To be sure, best wipe everything as before, then flash trickdroid 7.0.0
//edit: just editing CID is not enough, I guess .. I would modify mmcblk0p23 to 1.00.000.0 (see thread "downgrade/unbrick"), too. If that does not work, downgrade hboot, works fine. I think you are good with linux.
andryyyy said:
Hey,
searched the Viper thread:
"Hello,
Did you do the 2.35 OTA from T-Mobile? If so then you can't get Wi-Fi working on any other rom then Trickdroid 7.0.0 or Stock 2.35. It all has to do with the way Wi-Fi is handled in 2.35 and hboot 1.14 not letting you downgrade those partitions.
You Could always SuperCID your phone and in stall the 2.31 RUU then install Viper. That has the same hboot so you shouldn't have any problems. I haven't tried this because I dont need to. Hope that helps.
Rsotbiemrptson"
Click to expand...
Click to collapse
hi. I don't know this because I just got the phone from my cousin last night and he has no idea too. Where could check this if the OTA is done or not?
Okaaay. I tried Trickdroid v8.1.0 and it didn't work. I'm downloadiing the v7.0.0 right now to test it.
He must have dont the 2.30 OTA that's why wifi is not working on any other ROM.
Can you tell me a way other than virtual machine for me to apply the 2.31 RUU on Ubuntu/linux?
Shrink your ext3/4 partition using gparted and install win7
Virtualising and using "pass-through" will not work anyway. The phone switches its mode too often, you would need to "pass-through" it again and again.
You best use a laptop of a friend .. :/
But yes, try 7.0.0
So it worked?
andryyyy said:
Shrink your ext3/4 partition using gparted and install win7
Virtualising and using "pass-through" will not work anyway. The phone switches its mode too often, you would need to "pass-through" it again and again.
You best use a laptop of a friend .. :/
But yes, try 7.0.0
Click to expand...
Click to collapse
IT WORKED!! :laugh:
Thank you SO much andryyyy. I would've died without wifi on my phone.
Thanks again. :laugh::good:
Hi,
Try the following link
http://forum.xda-developers.com/showthread.php?t=2151142
I use Viper 2.1 and hboot 1.14.004. But, remember to use stock kernel when you flash your Viper rom.
Thank you
I have S3 right here and I tried flashing Trickdroid ICS, JB as well as JellyBean Official TWRP zip.
It is S-ON, so after flashing the zip, I go to fastboot and flash boot.img.
I did it already 2-3 times with every rom, but every time I get boot loop. Phone restarts as soon as the first HTC logo disappears.
What is wrong with that?
Do you have the latest TWRP 2.4.1.0 ? (did you try reflashing your recovery?)
What android did you have before unlocking your bootloader? 4.0.3 or 4.0.4?
(and don`t panic If nothing works there is always a solution by relocking your phone and flash the ruu for your phone from here)
http://www.androidfiles.org/ruu/?dir=VilleC2
take a look here:
http://forum.xda-developers.com/showpost.php?p=37498221&postcount=309
impactor said:
I have S3 right here and I tried flashing Trickdroid ICS, JB as well as JellyBean Official TWRP zip.
It is S-ON, so after flashing the zip, I go to fastboot and flash boot.img.
I did it already 2-3 times with every rom, but every time I get boot loop. Phone restarts as soon as the first HTC logo disappears.
What is wrong with that?
Click to expand...
Click to collapse
What's was you on before flashing a custom rom? because just a guess but I think it was 4.0.3 if that is so then try TrickDroid for S3 and get v3 which is 4.0.3 so should work.
It was stock, but I didn't check the version before flashing.
So, TD 3.0, then TD 5.0 and it will work?
By the way, what is better? TD 5.0 or JellyBean Official TWRP?
impactor said:
It was stock, but I didn't check the version before flashing.
So, TD 3.0, then TD 5.0 and it will work?
By the way, what is better? TD 5.0 or JellyBean Official TWRP?
Click to expand...
Click to collapse
No only v3 but if you can get an RUU thats more up to date then do that and the v4/5 should work.
So you didn't install a custom kernal before
Sent from my KFTT using xda premium
KindleFireGuy said:
So you didn't install a custom kernal before
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
Em what he said he did.
You cannot flash S4 roms with an S3 phone, have you made sure that the Roms you flash are specifically assigned for S3? Cuz most are S4
Thanks, guys. That was HBOOT problem. I flashed latest RUU and then I was able to use JB roms.
I am terribly sorry to bump this thread but it is EXACTLY what I need. I read through it and am slightly confused with what you guys said.
Here's my situation:
I have a HTC Evo 3D and have tried running multiple ROMs and on every ROM I run into a boot loop. I use TWRP 2.2.0 and boot that onto my phone using the code "Fastboot boot twrp-shooter.img", then from there I go into TWRP and add the ROM to the root of my SDcard. Then I use TWRP to wipe my cache, delvik cache, system, and do a factory reset. Then I go to install from SDcard and install my desired ROM that I am trying. It is successful and when I reboot it shows the HTC logo, then the loading screen for the ROM, then it goes black, then back to the HTC logo and it continues to loop the same booting sequence over and over.
Am I doing something wrong? Is there something different that I should use or do?
I've been trying to figure out this issue for more than 36 hours and I am borderline psycho right now, I really need answers!
pcout64 said:
I am terribly sorry to bump this thread but it is EXACTLY what I need. I read through it and am slightly confused with what you guys said.
Here's my situation:
I have a HTC Evo 3D and have tried running multiple ROMs and on every ROM I run into a boot loop. I use TWRP 2.2.0 and boot that onto my phone using the code "Fastboot boot twrp-shooter.img", then from there I go into TWRP and add the ROM to the root of my SDcard. Then I use TWRP to wipe my cache, delvik cache, system, and do a factory reset. Then I go to install from SDcard and install my desired ROM that I am trying. It is successful and when I reboot it shows the HTC logo, then the loading screen for the ROM, then it goes black, then back to the HTC logo and it continues to loop the same booting sequence over and over.
Am I doing something wrong? Is there something different that I should use or do?
I've been trying to figure out this issue for more than 36 hours and I am borderline psycho right now, I really need answers!
Click to expand...
Click to collapse
1. check if you are s-on or s-off. If you are s-on, you will also need to flash the kernel (boot.img) from a computer (after you flash the zip)
2. make sure your rom is compatible with your phone
asdfasdfvful said:
1. check if you are s-on or s-off. If you are s-on, you will also need to flash the kernel (boot.img) from a computer (after you flash the zip)
2. make sure your rom is compatible with your phone
Click to expand...
Click to collapse
I already know that I am s-on, and that all I need is the RUU because all I want is to get right the hell back to stock. The problem is that I can't find a RUU that is compatible with my phone!! Your help searching for one would be amazing!!
HTC Evo 3D CDMA Sprint
Mainver: 2.95.652.5
CID: SPCS_002
pcout64 said:
I already know that I am s-on, and that all I need is the RUU because all I want is to get right the hell back to stock. The problem is that I can't find a RUU that is compatible with my phone!! Your help searching for one would be amazing!!
HTC Evo 3D CDMA Sprint
Mainver: 2.95.652.5
CID: SPCS_002
Click to expand...
Click to collapse
Still new to xda, but check this out?
http://forum.xda-developers.com/wiki/HTC_Evo_3D/CDMA
(ctrl + f and find "ruu")
My mainver is not listed, I have already seen this page
The page was last edited in November of 2012, I think it's a bit out of date
everytime i flash an android 4.3 based rom my phone will bootloop... install it works for a few.. then crashes then back into bootloop then works... reboot.. bootloop...
doesn't happen when i installed the cm 10.1.3
any ideas?
MadMan29729 said:
everytime i flash an android 4.3 based rom my phone will bootloop... install it works for a few.. then crashes then back into bootloop then works... reboot.. bootloop...
doesn't happen when i installed the cm 10.1.3
any ideas?
Click to expand...
Click to collapse
I'm having exactly the same issue with my one s, when it bootloops the only way to recover it is to boot into recovery, power off & reboot. Tried multiple CM/AOKP roms with the same issue.
As far as i know i'm on the latest firmware (how do you check in CM or is it baseband?) as it was RUU'd to 3.16.xxx then s-off'd, i'm not superCID currently as I had to change it back to HTC__001 to run the RUU. Hboot: 2.15, baseband: 1.11.50.05.28_10.27.50.08L
Its a European (UK) phone with the S4 if that makes any difference
Annoyingly I cant seem to get it to do it when I have a PC with ADB set up on it nearby!
Is there any more info that might be helpful that can be provided?
I also experienced the same thing. Hope senior member help us. :crying:
MadMan29729 said:
everytime i flash an android 4.3 based rom my phone will bootloop... install it works for a few.. then crashes then back into bootloop then works... reboot.. bootloop...
doesn't happen when i installed the cm 10.1.3
any ideas?
Click to expand...
Click to collapse
aosp 4.3.x need a hboot >= 2.15.x
have the ville with hboot 2.15, S-OFF, SuperCID, latest firmware (afaik)
Sent from my One S using Tapatalk
Which version of HTC one S? The Villec2 or Ville?
Kerjifire said:
Which version of HTC one S? The Villec2 or Ville?
Click to expand...
Click to collapse
the ville
I am having the same problem with my s4 ville hboot 2.15, S-ON, latest frimware
Any solution guys?
I spend the whole day running RUU's, re-locking, unlocking the phone, flashing different 4.3 AOSP ROMs but every time I boot the same thing happens: Sometimes I can't even get the rom to boot, but if it does, it usually crashes back to the splash screen after a couple of seconds. I am out of ideas. Any help?
I flashed the JB firmware as per the firmware thread and it has mad my current rom (beanstalk, couple of builds ago) slightly more stable, however flashing anything else results in a bootloop.
Incidentally as well, starting maps navigating, hitting home, then going back into maps again results in bootlooping
Edit
Attached a logcat of the phone bootlooping caused by the maps issue above, did have one of it happening in maps but I fat fingered my cmd prompt and overwrote it. I'll grab another once its recovered
Reading through it it doesn't seem to have captured the actual bootloop, i used 'adb logcat < file.txt' to record it, or is there a better method of capture, using the -f flag as per the dev website gave me a read only error either 'adb logcat -f file.txt' from a path i have write access to or 'adb logcat - f <filepath>file.txt' can I get adb to continue writing between device reboots?
Just flashed the awesome kernel cleaner script and then flashed bubba kernel so far it seems to be working, will report whether it worked or not after i test it more...
UPDATE: crashed into a bootloop
Hey guys,
Having some problems with this ROM. I downloaded the ZIP, used Titanium backup to back it all up, and flashed the Rom with no problems at all...got through all the screens and whatnot, and upon launching for the first time it's stuck on the "Beats Audio" screen. Not really sure why or what happened. I'm coming from MIUI ROM and haven't had issues with flashing any other ROM before.
One thing I noticed is on the HD 7.3 first page there is a firmware update that you apparently need before you flash the ROM but all links are 404/not found.
Wondering if any of you pros can offer a hand?
-Cain
Cainsmoker said:
Hey guys,
Having some problems with this ROM. I downloaded the ZIP, used Titanium backup to back it all up, and flashed the Rom with no problems at all...got through all the screens and whatnot, and upon launching for the first time it's stuck on the "Beats Audio" screen. Not really sure why or what happened. I'm coming from MIUI ROM and haven't had issues with flashing any other ROM before.
One thing I noticed is on the HD 7.3 first page there is a firmware update that you apparently need before you flash the ROM but all links are 404/not found.
Wondering if any of you pros can offer a hand?
-Cain
Click to expand...
Click to collapse
post the output of this command
fastboot getvar all
don't show your imei and serial number
and what recovery do you have?
rzr86 said:
post the output of this command
fastboot getvar all
don't show your imei and serial number
and what recovery do you have?
Click to expand...
Click to collapse
In looking at my Hboot, it's old as sin....I'm using Revolutionary Hboot 1.17.1111 and Radio 10.14.9035.01_M
I run clockwork recovery mod v5.0.2.0 as well. This could be an issue causing the problem. I've been using the MIUI ROM for probably 2 years or so because I enjoyed it but I'm ready for a change. Apparently my phone doesn't agree. lol.
You want me to connect via USB and run the cmd prompt for the getvar command and let you know what it says?
Cainsmoker said:
In looking at my Hboot, it's old as sin....I'm using Revolutionary Hboot 1.17.1111 and Radio 10.14.9035.01_M
I run clockwork recovery mod v5.0.2.0 as well. This could be an issue causing the problem. I've been using the MIUI ROM for probably 2 years or so because I enjoyed it but I'm ready for a change. Apparently my phone doesn't agree. lol.
You want me to connect via USB and run the cmd prompt for the getvar command and let you know what it says?
Click to expand...
Click to collapse
there is no need to do it now
you gave me exactly what i need
you still have gb firmware that's why you can't boot ARHD 7.3(ics rom)
see this thread
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the instructions to the letter
and before flashing check md5 sums(important)
The speedy reply is much appreciated.
I'll go ahead and update the firmware and see where that lands me. I figured it could have been a problem from the get go but in the original thread for the HD 7.3 Rom the firmware link has been removed (likely since it was from 2011)
Thanks for the point in the right direction Rzr, and I'll let you know how it goes!
rzr86 said:
there is no need to do it now
you gave me exactly what i need
you still have gb firmware that's why you can't boot ARHD 7.3(ics rom)
see this thread
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the instructions to the letter
and before flashing check md5 sums(important)
Click to expand...
Click to collapse
Hmmm....the firmware update didn't work.
I can verify that I'm on the firmware 3.3, Hboot is 1.27.1100, Radio is 11.24A.3504.31_M.
Each time Hboot is run it asks if I want to start the update. If I select yes, I've got 9 on screen options that it runs through and tells me "Update complete. Press power to reboot" The only way to do anything at all is to take out the SD card so it does not try to load up the firmware zip
Pushing power reboots the phone on an endless boot loop. Regardless of what ROM is being used (I also downloaded cyanogenmod) I can not make it past the spash screen.
Could it be that I'm just flashing the ROM incorrectly? To my knowledge I've followed instructions for both and have backed up my phone and it's contents and done everything from a factory reset/wipe to wiping the dalvik cache, etc. I didn't have this many problems rooting my phone and putting on MIUI to begin with and have flashed ROMS before with no trouble....not really sure where I'm going wrong on this one.
Anyway, I'll await your reply.
Thank you!
-Cain
Update: awww frick. So now it looks like this will be more difficult....I hope you like a challenge. I can now no longer get into my phone. It appears that it's soft bricked. I have tried going to a clockwork mod recovery from my first MIUI in 2012, it goes through the entire process of factory resetting restoring the boot image, system and data information. It asks for a reboot which I do. It goes to the white HTC splash screen and the MIUI initializes and goes black immediately. There doesn't seem to be a way to get my phone connected to my computer to get into the SD card to troubleshoot from inside the phone. Hopefully one of you guys has the answer for me. Is there any way to get into it via bootloader usb?
Cainsmoker said:
Hmmm....the firmware update didn't work.
I can verify that I'm on the firmware 3.3, Hboot is 1.27.1100, Radio is 11.24A.3504.31_M.
Each time Hboot is run it asks if I want to start the update. If I select yes, I've got 9 on screen options that it runs through and tells me "Update complete. Press power to reboot" The only way to do anything at all is to take out the SD card so it does not try to load up the firmware zip
Pushing power reboots the phone on an endless boot loop. Regardless of what ROM is being used (I also downloaded cyanogenmod) I can not make it past the spash screen.
Could it be that I'm just flashing the ROM incorrectly? To my knowledge I've followed instructions for both and have backed up my phone and it's contents and done everything from a factory reset/wipe to wiping the dalvik cache, etc. I didn't have this many problems rooting my phone and putting on MIUI to begin with and have flashed ROMS before with no trouble....not really sure where I'm going wrong on this one.
Anyway, I'll await your reply.
Thank you!
-Cain
Update: awww frick. So now it looks like this will be more difficult....I hope you like a challenge. I can now no longer get into my phone. It appears that it's soft bricked. I have tried going to a clockwork mod recovery from my first MIUI in 2012, it goes through the entire process of factory resetting restoring the boot image, system and data information. It asks for a reboot which I do. It goes to the white HTC splash screen and the MIUI initializes and goes black immediately. There doesn't seem to be a way to get my phone connected to my computer to get into the SD card to troubleshoot from inside the phone. Hopefully one of you guys has the answer for me. Is there any way to get into it via bootloader usb?
Click to expand...
Click to collapse
remove the pg58img.zip from your sdcard so it won't scan and identify any pg58img.zip file
and don't restore your miui rom because probably is a gb one and now you have an ics firmware installed
just download an ics or jb rom
put it on your sdcard
full wipe from recovery
flash the rom
done
rzr86 said:
remove the pg58img.zip from your sdcard so it won't scan and identify any pg58img.zip file
and don't restore your miui rom because probably is a gb one and now you have an ics firmware installed
just download an ics or jb rom
put it on your sdcard
full wipe from recovery
flash the rom
done
Click to expand...
Click to collapse
With the phone being in a boot loop I can't get it detected by my computer to remove/add anything from the SD card. I do have the HD 7.3 ROM on and the Gapps that's required but it never makes it past the "beats audio" splash screen. I have no idea what's going on with it but will try any suggestions you've got up your sleeve.
Ahhhhh....I've gotten a fix for this!
I was unable to do anything because of the update zip which wanted me to update every time bootloader was initiated. By keeping my case off I removed my SD card to be able to boot in recovery and then put the SD card back in to load the HD 7.3 zip from the card. This seemed to take care of the problem.
Thanks for the help Rzr