Hey guyss
I am currently using RemPuzzle's latest ROM but the reason why i am posting it here is becoz it has been happening with all the ROMs that I have tried!
The phone works completely fine until the display is turned off for quite some time (put to sleep)! Then when ever I try to open it, it wont! The only way to make it work is by battery pull! I have tried flashing other ROMs but the same problem occurs with them. For now, I have selected in 'Screen Timeout' to 'never turn off'! But still it is very annoying me!
What I do when flashing the ROM: (CWM 5.0.2.0)
Wipe data/cache partition
Wipe cache partition
Wipe Dalvik Cache
Wipe boot
Wipe cahe
Wipe data
Wipe system
Flash ROM
Flash gapps (if necessary)
Flash CronMod
Flash CronMod dalvik cache wipe tool
Reboot system
Do tell me if im doing anything wrong!
Thnx in advance!
CallOfHonor100 said:
Hey guyss
I am currently using RemPuzzle's latest ROM but the reason why i am posting it here is becoz it has been happening with all the ROMs that I have tried!
The phone works completely fine until the display is turned off for quite some time (put to sleep)! Then when ever I try to open it, it wont! The only way to make it work is by battery pull! I have tried flashing other ROMs but the same problem occurs with them. For now, I have selected in 'Screen Timeout' to 'never turn off'! But still it is very annoying me!
What I do when flashing the ROM: (CWM 5.0.2.0)
Wipe data/cache partition
Wipe cache partition
Wipe Dalvik Cache
Wipe boot
Wipe cahe
Wipe data
Wipe system
Flash ROM
Flash gapps (if necessary)
Flash CronMod
Flash CronMod dalvik cache wipe tool
Reboot system
Do tell me if im doing anything wrong!
Thnx in advance!
Click to expand...
Click to collapse
I think the phone isn't functioning properly, you've done everything right :good:
But my best guess that it's the phone
I've got a few tips, revert back to stock
Flash cwm revolutionary 4.0.1.4 and re install a custom ROM, it's what I've done every time to solve all my issues :good:
If my way doesn't work or solve any issues, then I'll try to give more advice in return, if others would like to aswell
Also if phone still reacts all weird, it's best if you take the phone to someone who can fix it up :good:
In any case i'll try and do my best
CallOfHonor100 said:
Hey guyss
I am currently using RemPuzzle's latest ROM but the reason why i am posting it here is becoz it has been happening with all the ROMs that I have tried!
The phone works completely fine until the display is turned off for quite some time (put to sleep)! Then when ever I try to open it, it wont! The only way to make it work is by battery pull! I have tried flashing other ROMs but the same problem occurs with them. For now, I have selected in 'Screen Timeout' to 'never turn off'! But still it is very annoying me!
What I do when flashing the ROM: (CWM 5.0.2.0)
Wipe data/cache partition
Wipe cache partition
Wipe Dalvik Cache
Wipe boot
Wipe cahe
Wipe data
Wipe system
Flash ROM
Flash gapps (if necessary)
Flash CronMod
Flash CronMod dalvik cache wipe tool
Reboot system
Do tell me if im doing anything wrong!
Thnx in advance!
Click to expand...
Click to collapse
Do you have a HTC buzz or a HTC bee? This is a deep sleep issue from the kernel. My and kylon had this issue with the htc bee.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
heavy_metal_man said:
Do you have a HTC buzz or a HTC bee? This is a deep sleep issue from the kernel. My and kylon had this issue with the htc bee.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Click to expand...
Click to collapse
Yep! I am sure it is HTC buzz!
Stone. Cold said:
I think the phone isn't functioning properly, you've done everything right :good:
But my best guess that it's the phone
I've got a few tips, revert back to stock
Flash cwm revolutionary 4.0.1.4 and re install a custom ROM, it's what I've done every time to solve all my issues :good:
If my way doesn't work or solve any issues, then I'll try to give more advice in return, if others would like to aswell
Also if phone still reacts all weird, it's best if you take the phone to someone who can fix it up :good:
In any case i'll try and do my best
Click to expand...
Click to collapse
Unrooted and rooted again! At first, i thought it had worked but...BAM...it hanged again!
I think I am not rooting correctly...=(
1. I wasnt able to S-ON my device after unrooting so I carried on...=/
2. After doing the revolutionary part, I wasnt able to install Android Bootloader Interface! It kept giving me the error that the hash of the file is missing or something! So I did something else. Now, when I go to cmd and write 'adb devices', it doesnt show my device! Although, when I write 'fastboot devices', it shows my device attached! (weird)
3. I flashed recovery with revolutionary so I reckon that I didnt had to do the unrevoked method...was i wrong??
Help appreciated...=)
CallOfHonor100 said:
Yep! I am sure it is HTC buzz!
Unrooted and rooted again! At first, i thought it had worked but...BAM...it hanged again!
I think I am not rooting correctly...=(
1. I wasnt able to S-ON my device after unrooting so I carried on...=/
2. After doing the revolutionary part, I wasnt able to install Android Bootloader Interface! It kept giving me the error that the hash of the file is missing or something! So I did something else. Now, when I go to cmd and write 'adb devices', it doesnt show my device! Although, when I write 'fastboot devices', it shows my device attached! (weird)
3. I flashed recovery with revolutionary so I reckon that I didnt had to do the unrevoked method...was i wrong??
Help appreciated...=)
Click to expand...
Click to collapse
What is this cronmod you've been flashing?
Sent from my Nexus 7 using Tapatalk 4
heavy_metal_man said:
What is this cronmod you've been flashing?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Its this:
http://forum.xda-developers.com/showthread.php?t=1716124
But now there is something else!
I again unrooted my phone and rooted it again! This time, I did everything perfectly! The drivers, the unrevoked, everything right! But, I didnt flash ANYTHING!! I didnt flash cronmod or even a ROM! And it still hangs up!! =(
Is it possible that im rooting it wrong! Or it doesnt support sense? =/
CallOfHonor100 said:
Its this:
http://forum.xda-developers.com/showthread.php?t=1716124
But now there is something else!
I again unrooted my phone and rooted it again! This time, I did everything perfectly! The drivers, the unrevoked, everything right! But, I didnt flash ANYTHING!! I didnt flash cronmod or even a ROM! And it still hangs up!! =(
Is it possible that im rooting it wrong! Or it doesnt support sense? =/
Click to expand...
Click to collapse
Well this will only work if you have the correct ext partition on your sdcard, and I don't think root has anything to do with this. Have you ran an ruu yet? If not run one, if yes which one?
Sent from my Nexus 7 using Tapatalk 4
heavy_metal_man said:
Well this will only work if you have the correct ext partition on your sdcard, and I don't think root has anything to do with this. Have you ran an ruu yet? If not run one, if yes which one?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Oh DAMN! I completely forgot about the ext partition! =D
I made the partition long ago via recovery! I dont know what type of ext it is... =/
will removing the ext would solve the problem?
Which ext is the correct ext partition??
Related
HI... i updated my phone with cyanogen 7 rc2, but after it booted up it's stuck in the animation that says cyanogen mod 7 , and the blue android sign... in comes than goes, again it comes... about 20 min stuck... what to do???
It sounds like you need to go into recovery mode and delete all your caches. If you are using ClockworkMod recovery do the following (make sure you are backed up first):
Delete all user data and info (under wipe data/ factory reset),
Wipe cache (under wipe cache partition),
Wipe Dalvik Cache (under advanced).
Then once you've done that try installing and running the ROM again.
i done that one time... for info im using AmonRA.. i cleaned all the cache and everything also... and installed again... nothing happens... fortunately i restored my nand backup and booted my phone with the OTA again... waiting for some answer.... do u think that installing stable version can fix this?
Sounds like a bad flash. I had rc2 running for a month or so with no issues. I've had times when the rom just doesn't install properly ans reflashing fixes it.
Download the zip again, if possible check md5 to make sure it's all good, make sure you have the desire/bravo GSM version, clear everything and flash just the rom and nothing else. If it boots, then go back and flash your gapps and whatever else you want.
Sent from my HTC Desire using XDA App
thx for replying.. as i was waiting for your reply, i download the cm 6 that is a stable version and checked, it has the same problem too.. i also downloaded GingerVillain 1.6 and it had the same problem too. do u think the problem might be that my phone is "s-on"? and how should i know if my phone is s-on or s-off... when i was rooting my phone with unrevoked, i checked the option that says disable security, but i'm not sure if it's disabled.... because i can't install un-signed zip packages....
any reply?
That definitely sounds odd. Its definitely not an issue with S-ON/OFF, nothing you've done here requires S-OFF to work properly.
Lets just make sure you're following all the steps.
In amonra, you've done your nandroid backup, so no need to do it again. There's no point having a non working backup
Go to wipe and wipe data/factory reset
Wipe davlik cache
Wipe sd-ext (shouldn't need to do this one as you don't have apps2sd yet, but better to be safe)
Now you flash your update.zip, then reboot and you should be fine. The only other thing I can perhaps suggest if every rom you flash sticks at boot is to perhaps try clockwork recovery instead of amonra. Apart from that we might have to wait for folks more knowledgeable than myself cause I'm all out of ideas.
thx for reply.... in meanwhile , i s-off ed my phone and it has the same problem too... i have problem with all cm and gingervillain roms.. but i don't have any problem with leedriod... one more question that maybe the problem is that i have android 2.2 installed, but gingervillain and cm use android 2.3 ... this maybe the problem.... and that's why leedroid works right, because it uses android 2.2.... i'm going to check OxyGen roms... i will post the result here...
i also faced same problem CM7 .. i tried CM6 and it went on fine..
heyyy... right after i posted the reply , i went to recovery and wiped anything, then installed gingervillain 1.6, and everything's fine now... it booted up and now im setting it up.... im going to check the cm 7 too.
i tried cm7 rc2 ... and it was fine and now im using it... here's a how to for solving the problem...:
1.S-OFF your device with AlphaRev : http://forum.xda-developers.com/showthread.php?t=805811
2.Install the AlphaRev Recovery(S-OFF Image will do it automatically).
3.Go to recovery and install the rom...
4.Boot up and it should not go to system and it should stay in loop as the problem was..
5.Now you should reboot your device into recovery... there are two ways to do this... either take the battery off and put it on, then boot to bootloader by pressing the volume down and the power key and select recovery , or the second way connect it to your computer and start adb and run this command:
adb reboot recovery
6.In AlphaRev recovery first wipe the cache partition , wipe user data, and factory reset...
7.then install the rom (either cm7 or gingervillain)...
8. boot up , and now you have the system running...
This solved my problem... reply if it didn't yours...
hooo.. it worked for me now. just kept update.zip in a new SD card and not flashed google apps..
im very happy that i solved one's problem.. ... thread marked as solved...
*UPDATE* : now i realized that we can mark it as solved.. !!! hehe.. Admin do it for us...
I have flashed leedroid 2.4 and at first it worked well, but i turned off USB Debugging and after reboot it stuck at first boot screen... (didnt see Leave USB Debugging active!)
then i flashed it again..
now im getting bootloops..
tried to flash a few times, but i always get bootloops..
(wiped data/factory reset, wiped cache, and dalvik)
I have tried to flash leedroid 2.3d, and again bootloops..
I dont have problems with other roms...
can somebody help?
Sorry for my english...
can somebody help?
Hmm,that's odd o.0
Did u refarmat the Sdcard ? id suggest that,maybe some corrupt data was left on the ext partition ,dunno...and did u ask this in the LD 2.4 thread? Lee almost always answers all q/ in his thread
i cant post there..need 10 posts..
all other rooms are working normal... i have a 1gb ext3 partition...
Lee is working on the fix. His Rom currently needs to have usb debugging enabled to work. Check his Rom thread to see how to fix it!
Sent from my HTC Desire using XDA Premium App
wnp_79 said:
Lee is working on the fix. His Rom currently needs to have usb debugging enabled to work. Check his Rom thread to see how to fix it!
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
and there isn't a way from reenable usb debugging from recovery? or adb (if it's possible to use it) ???
I'have just do this terrible error: disable usb debugging
I don't want to wipe my just fully configurated leedroid 2.4
Thank You
atlaware said:
I don't want to wipe my just fully configurated leedroid 2.4
Click to expand...
Click to collapse
You can try to wipe cache/dalvik-cache and flash LeeDroid 2.4 again, Lee said it should work. But in fact it seems that it doesn't work each time ... I you're in a bad luck you will need to full wipe your brand new LeeDroid ...
Unfortunately it looks like having to flash 2.4 back over the top of it is the only answer for now, as Lee clarifies in this post...
http://forum.xda-developers.com/showpost.php?p=12764784&postcount=20357
Soz. I'm not even sure if the upcoming patch will prevent you from having to do this anyway though. He says it'll be up by the weekend.
Edit: Did you do a Titanium backup of your apps/settings?
wnp_79 said:
Edit: Did you do a Titanium backup of your apps/settings?
Click to expand...
Click to collapse
Yes, but it's a backup of 10 days ago of my "old" leedroid 2.3d
Ed Roid said:
You can try to wipe cache/dalvik-cache and flash LeeDroid 2.4 again, Lee said it should work. But in fact it seems that it doesn't work each time ... I you're in a bad luck you will need to full wipe your brand new LeeDroid ...
Click to expand...
Click to collapse
For me it doesn't work i need to full wipe damm!
Thank U
atlaware said:
For me it doesn't work i need to full wipe damm!
Click to expand...
Click to collapse
I'm afraid you don't have any other choice. Too bad ...
RyuKai said:
I have flashed leedroid 2.4 and at first it worked well, but i turned off USB Debugging and after reboot it stuck at first boot screen... (didnt see Leave USB Debugging active!)
then i flashed it again..
now im getting bootloops..
tried to flash a few times, but i always get bootloops..
(wiped data/factory reset, wiped cache, and dalvik)
I have tried to flash leedroid 2.3d, and again bootloops..
I dont have problems with other roms...
can somebody help?
Sorry for my english...
Click to expand...
Click to collapse
try to partion it again
maybe work
please help me
I try about 3 roms and when I try to install new app the device reboot..
what should I do ??? please help me X_x
Which roms did you use?
Model: Wildfire S A510e
Recovery: unofficial CWM
Rom: JxMatteo_ROM_V1. 1 with Link2sd - OC - Rooted
apparently freezes and reboots can be a problem if you forget to clear everything before installing custom roms....so you need to do factory reset, clear all cache, clear dalvik cache or whatever it's called, then install rom.
this didn't actually work for me when i tried to put CM7 on my phone, i've ended up clearing it all, formatting evrything and just going back to stock because CM7 was so unstable on my phone.
but if you forgot to clear everything when you first installed, try that first?
Hope you get it going. If not, you can also install stock, but you can still partition the sd card and use link2sd to give you basically a gig of "internal" storage (it lets you install pretty much all apps to the 2nd partition on the sd card. running very well now on mine.
I was just about to create a thread about this problem. I flashed m1ndh4x8r's ROM onto my device after a bad experience with the CM7 nightly, fully wiped, permissions fixed. I was on that exact same ROM the day before flashing CM7 and it was working perfectly, did everything it said it would, apps installed just fine. And the first time I installed that ROM, I didn't wipe a single thing.
So, now I'm thinking we should revert to the stock ROM, then flash this one back over it with no wipes, then if that doesn't work, revert to stock again and try flashing the ROM the proper way, wipes and all.
I'll try fixing this every way I can. I'll tell you if I find a fix for myself that you could use as well
matt5eo said:
Which roms did you use?
Model: Wildfire S A510e
Recovery: unofficial CWM
Rom: JxMatteo_ROM_V1. 1 with Link2sd - OC - Rooted
Click to expand...
Click to collapse
1- JkantaruROM XE
2- alquez cyanogenmod 7
3- m1ndh4x8r
Gloris said:
apparently freezes and reboots can be a problem if you forget to clear everything before installing custom roms....so you need to do factory reset, clear all cache, clear dalvik cache or whatever it's called, then install rom.
this didn't actually work for me when i tried to put CM7 on my phone, i've ended up clearing it all, formatting evrything and just going back to stock because CM7 was so unstable on my phone.
but if you forgot to clear everything when you first installed, try that first?
Hope you get it going. If not, you can also install stock, but you can still partition the sd card and use link2sd to give you basically a gig of "internal" storage (it lets you install pretty much all apps to the 2nd partition on the sd card. running very well now on mine.
Click to expand...
Click to collapse
how can I go back to stock ?? and what is CM7 meaning???
johnnyspritz said:
I was just about to create a thread about this problem. I flashed m1ndh4x8r's ROM onto my device after a bad experience with the CM7 nightly, fully wiped, permissions fixed. I was on that exact same ROM the day before flashing CM7 and it was working perfectly, did everything it said it would, apps installed just fine. And the first time I installed that ROM, I didn't wipe a single thing.
So, now I'm thinking we should revert to the stock ROM, then flash this one back over it with no wipes, then if that doesn't work, revert to stock again and try flashing the ROM the proper way, wipes and all.
I'll try fixing this every way I can. I'll tell you if I find a fix for myself that you could use as well
Click to expand...
Click to collapse
Ok thank you , I'm waiting you
but can you tell me what is the CM7 ???
*_^AL_Ha$aN^_* said:
Ok thank you , I'm waiting you
but can you tell me what is the CM7 ???
Click to expand...
Click to collapse
is a type of rom... currently cm7.2 stable build... CM stands for cyanogenmod
check this site: cyanogenmod.com
Pretty much every ROM ever made says be sure to wipe EVERYTHING. They put that there for a reason. The only time time you MIGHT get away with not wiping is if your flashing the exact same ROM you just had. Then and only then, you might get away without wiping your dalvik.
Sent from my HTC_A510c using Tapatalk
Idk, the ROM worked fine for me, even though I think I didn't wipe anything. When I did wipe the phone before flashing, there was a problem. Though it could just be my device and my bad luck
God hates me, I don't know why I even bother living anymore -.-
EDIT: My faith in God is restored. Just flash this ROM instead. You'll be happy with it and it works just fine for me. Also, wipe EVERYTHING I can't agree that you always have to wipe everything, since not wiping actually solved a problem I had with CM7, but I think that was just an isolated case.
I was running Paranoid Android 2.99.
Okay, heres what I have done. May be the worst mistake I could do, I chose /system to format in recovery after installing the custom kernel packed in the zip of Paranoid Android by extracting it separately. And now, what I get is a phone stuck in bootloop.
After this I tried the following:
Restoring a NanDroid backup of my HTC Sense, and I know it won't work because I was using Titanium KISS kernel. Now, when I want to flash a new kernel through HTC All in one toolkit, I get a <unknown error>. The kernel of Titanium required for sense is not flashing in my phone. In fact, no kernels are flashing in the phone through the toolkit.
The phone is not bricked, because the LED glows, I can go into Recovery and Bootloader mode.
Please help me, what should I do??
First of all: Are you GSM or CDMA?
Second of all (if you are GSM) YOU SHOULD NOT FLASH THE KERNEL THAT WAS PACKED INTO THE ROM! you should download the Hellboy kernel, the latest (i think it is 20121215) and flash that.
Yes, I made that mistake. I flashed the boot.img, and now I am dead! X(
I am on GSM. Any fix? Please!
techie.anish said:
Yes, I made that mistake. I flashed the boot.img, and now I am dead! X(
I am on GSM. Any fix? Please!
Click to expand...
Click to collapse
Bootloops are nothing
Just flash the kernel and u are good to go
Sent from my One V using xda premium
techie.anish said:
I was running Paranoid Android 2.99.
Okay, heres what I have done. May be the worst mistake I could do, I chose /system to format in recovery after installing the custom kernel/QUOTE]
well.. you missed a lot of things here
like:
boot into recovery and do:
factory reset
wipe cache
wipe dalvik cache
and then wipe system
after that, flash the rom ( you didn't stated this either).
then boot into bootloader and flash the kernel hellboy.
reboot
if this doesn't help, do the followings:
go to bootloader
flash the kernel again
go to recovery
do:
factory reset
wipe cache
wipe dalvik cache
wipe system
install rom again.
reboot
one of these two should work just fine. your phone is not bricked or unfunctional. don't worry!
Click to expand...
Click to collapse
Flashing the kernel gives a sort in the cmd "Malformed 1 byte"
Now
Sent from my MT11i using xda app-developers app
techie.anish said:
Flashing the kernel gives a sort in the cmd "Malformed 1 byte"
Now
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
redownload the kernel once more
oh sorry, my stupid mistake!
i was flashing it in HBOOT mode... lol!
sorry, once again :embarassed:
cybervibin said:
Bootloops are nothing
Just flash the kernel and u are good to go
one of these two should work just fine. your phone is not bricked or unfunctional. don't worry!
Click to expand...
Click to collapse
neither of them are working for me.. dont know what to do
i want to root, unlock bootloader and flash this ROM to my device
but i have several question regarding to the feature of this ROM
it says, same look but much faster..
does this mean:
-it supports HTC Media Link HD?
-it have the ImageSense and able to take photos while recording videos
-it is basically the exact same ROM as the stock one in pretty much everything but more speed?
thanks in advance.. :good:
Yes
Yes, if you can on stock ROM
Yes and it's rooted
well thank's! time for root now muehehehe
Good luck! If you run into problems, just ask in this thread and don't create a new one. Thanks.
Hy guys. I installed Revolution HD on my HTC wile ago. Everything is working perfect except the proximity sensor. In calls the screen won't come off. Does any one has the same problem. And the usb doesn't work anymore on my car stereo dvd.
And how can i downgrade to the original rom my htc from revolution hd. Should i only connect it to htc menager and install the rom or what. Thanks guys.. And so sorry for my bad english.
Greatings from Croatia.
Silvach1 said:
Hy guys. I installed Revolution HD on my HTC wile ago. Everything is working perfect except the proximity sensor. In calls the screen won't come off. Does any one has the same problem. And the usb doesn't work anymore on my car stereo dvd.
And how can i downgrade to the original rom my htc from revolution hd. Should i only connect it to htc menager and install the rom or what. Thanks guys.. And so sorry for my bad english.
Greatings from Croatia.
Click to expand...
Click to collapse
What ARHD are you using? did you do a Full wipe/ wipe dalvik cache. Also make sure u do fastboot erase cache after u fastboot your boot.img.
Dizy801 said:
What ARHD are you using? did you do a Full wipe/ wipe dalvik cache. Also make sure u do fastboot erase cache after u fastboot your boot.img.
Click to expand...
Click to collapse
since i update it from original to ARHD it wont work at all.. i did full wipe in the restore before instaling the arhd or this is something else? Could you help so i can try it?
Silvach1 said:
since i update it from original to ARHD it wont work at all.. i did full wipe in the restore before instaling the arhd or this is something else? Could you help so i can try it?
Click to expand...
Click to collapse
What are the steps you are taking to flash your rom and boot.img?
when you flash your rom it should go into aroma.. choose the option that says do full wipe, if you dont you'll run into problems. after you have flashed it, flash your boot.img in fastboot mode from your computer then do fastboot erase cache to prevent any problems from the boot.img. Can you give me the steps your taking to flash?
Dizy801 said:
What are the steps you are taking to flash your rom and boot.img?
when you flash your rom it should go into aroma.. choose the option that says do full wipe, if you dont you'll run into problems. after you have flashed it, flash your boot.img in fastboot mode from your computer then do fastboot erase cache to prevent any problems from the boot.img. Can you give me the steps your taking to flash?
Click to expand...
Click to collapse
Taking all the steps needed to install it but i didnt do fastboot wipe... i find the wipe steps...
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Boot phone in recovery mode
Wipe data/factory reset
Wipe cache partition
Wipe dalvik cache
Install zip from SD card -> pick rom
i'll do this and try it again.. so i'll get back.. U thing that the problem is in the wiping?
Silvach1 said:
Taking all the steps needed to install it but i didnt do fastboot wipe... i find the wipe steps...
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Boot phone in recovery mode
Wipe data/factory reset
Wipe cache partition
Wipe dalvik cache
Install zip from SD card -> pick rom
i'll do this and try it again.. so i'll get back.. U thing that the problem is in the wiping?
Click to expand...
Click to collapse
Wiping is VERY IMPORTANT! if the necessary steps arn't taken then you can mix up new codes with the old codes leaving you with many different problems. Thats why devs ALWAYS recomment wiping even when Wiping isnt needed to avoid such problems. Also you might want to check your md5 sum from your downloaded rom.. could potentially be a bad download
Dizy801 said:
Wiping is VERY IMPORTANT! if the necessary steps arn't taken then you can mix up new codes with the old codes leaving you with many different problems. Thats why devs ALWAYS recomment wiping even when Wiping isnt needed to avoid such problems. Also you might want to check your md5 sum from your downloaded rom.. could potentially be a bad download
Click to expand...
Click to collapse
Done everything again with wiping all the data and again proximiti sensor doesn't work. Even dont light up red... damn.. maybe the sensor is dead? how can i install the original software on it? do stepst of flash boot boot.img and install it like the ARHD
Silvach1 said:
Done everything again with wiping all the data and again proximiti sensor doesn't work. Even dont light up red... damn.. maybe the sensor is dead? how can i install the original software on it? do stepst of flash boot boot.img and install it like the ARHD
Click to expand...
Click to collapse
I had something like this with my HOX once, but the problem was due to loose connections after i had cracked it open. you can look at the development section to revert back to original. http://forum.xda-developers.com/showthread.php?t=2094113
Dizy801 said:
I had something like this with my HOX once, but the problem was due to loose connections after i had cracked it open. you can look at the development section to revert back to original. http://forum.xda-developers.com/showthread.php?t=2094113
Click to expand...
Click to collapse
So much download here which to download? Really don't now. Help pls. This are stock roms for hox?
Silvach1 said:
So much download here which to download? Really don't now. Help pls. This are stock roms for hox?
Click to expand...
Click to collapse
You need to know what stock rom u need first. Check your phone's CID number. Yes these are all factory stock roms
do i really need to go to HTCDev.com to unlock my bootloader? or is there any other way?
Briztama said:
do i really need to go to HTCDev.com to unlock my bootloader? or is there any other way?
Click to expand...
Click to collapse
You have to go there, they send you a unique code to ur email for your device that unlocks the bootloader
Dizy801 said:
What ARHD are you using? did you do a Full wipe/ wipe dalvik cache. Also make sure u do fastboot erase cache after u fastboot your boot.img.
Click to expand...
Click to collapse
what the heck is a dalvik cache? what is full wipe? omg i did now know anything about rooting looks like it is not that simple
man probly it's better to avoid any root/flashing anyway to avoid problems like that guy faces
my stock is good but i don't know the fully unlocked experience.. been hesitating due to these kind of problem...
and probly i can't go back either
Briztama said:
what the heck is a dalvik cache? what is full wipe? omg i did now know anything about rooting looks like it is not that simple
man probly it's better to avoid any root/flashing anyway to avoid problems like that guy faces
my stock is good but i don't know the fully unlocked experience.. been hesitating due to these kind of problem...
and probly i can't go back either
Click to expand...
Click to collapse
Its simple once u get used to it. looks a lot more complicated until u have it finished lol. wiping and dalvik cache is an option in recovery.hard to miss when installin roms. no need to worry about that with unlocking.
Dizy801 said:
You need to know what stock rom u need first. Check your phone's CID number. Yes these are all factory stock roms
Click to expand...
Click to collapse
I just downloaded and instal 4.0.1. ARHD 9.9 and the usb mass storage works again but proximity sensor doesn't. Loks like it going on service cous it's probably broaken.
The rooting the HOX is not so complicated download some things and ur on new rom... Everything is going on in CMD line so nothing couldn't get wrog...
Silvach1 said:
I just downloaded and instal 4.0.1. ARHD 9.9 and the usb mass storage works again but proximity sensor doesn't. Loks like it going on service cous it's probably broaken.
The rooting the HOX is not so complicated download some things and ur on new rom... Everything is going on in CMD line so nothing couldn't get wrog...
Click to expand...
Click to collapse
Try a different rom other then ARHD?