Related
first, sorry for my english
Camera Flash does not work with any ROM...
I tried all the ROMS available ... stopped working after the Chinese ROM Froyo 2.2, But now no longer works with any ROM, or 3.4.2 UK or Roms Eclair etc...
But I can not access the Developer Forum, I've put it here ... I know there are more users having the same problem
Repeat, sorry for my english and Thanks for the Help.
I have exactly the same problem. Since china 2.2 sbf and rom, every rom and firmware exhibits the flash either not working on apps, or is out of sync with a blue tinge. I've tried every combination of fixes out so far, but nothing works. Will keep trying things out and post here if I find anything.
Sent from my MB525 using XDA App
Foxhound.kl said:
I have exactly the same problem. Since china 2.2 sbf and rom, every rom and firmware exhibits the flash either not working on apps, or is out of sync with a blue tinge. I've tried every combination of fixes out so far, but nothing works. Will keep trying things out and post here if I find anything.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Yes, I saw in the other section you had the same problem .. several days trying things and more things, and ROMS of all types, but does not work any ways ... will have been spoiled by Hardware? coincidence as the Chinese Rom
On me, the flash does not work none time, only a very small light blue-green
If you find anything, any minor detail, let me know please.
Thanks
I have to test more, but mine has low light and light borders are greeny.
Sent from my Defy using Tapatalk
Have the same problem. Flashed the chinese rom just a few days ago following a guide and the flash is now weak and greenish even when I'm back on my stockrom.
Whats strange is that I tried this rom following a guide several weeks ago, flashing only the 2.2 bootloader and using a nandroid backup. The flash just worked one time, so I went back to my stock rom, 2.21, again and the flash worked as before.
I think I have tried flashing the whole chinese rom and then gone back to stock with no prob before also. It was just this last time the flash stopped working as it should, no matter witch safe rom I now flash again.
I have tried the uk 2.2 with dowgradebility to get the flash working as explained by Higgsy but no go.
The only thing I can think of is that when you try to use the flash to many times when you are on the chinese froyo rom the flash gets damaged somehow.
Sent from my Defy
Did you guys notice that there's a black or dark yellow spot in the middle of the flash light? Many people who had this weak green light problem reported that their flash lights are like so because it's been burnt.
mimel said:
Did you guys notice that there's a black or dark yellow spot in the middle of the flash light? Many people who had this weak green light problem reported that their flash lights are like so because it's been burnt.
Click to expand...
Click to collapse
Looking at the LED, there's a slighty darker yellow spot in the middle, but not that dark, just a slight shade above the outer part. Not sure if its burnt out to be honest, becasue when the flash does work, its pretty bright and lights up what i'm pointing it at, but the moment the camera captures the image, the flash is already off, so its just not in sync with the image capture. The blue/green tinge comes after the bright flash, just as it ends. Can you tell me where the burnt out LEDs are being reported mimel?
I have it all yellow, I no see black spot.
Since the Chinese Rom, did not run the Flash, no weak, no strong, not be in sync, none of this, only not work, only shows a very very small light blue-green.
I would like to see a picture of a burned Flash.
Thanks for all the help and sorry for my English.
Yours probably is not burnt and might get back to normal by flashing the latest T-Mobile or uk sbf.
A burnt flash light can flash everytime but with very weak white light and ends with green/blue. It's unrecoverable even upgraded to the latest sbf or downgraded to 2.1.
Foxhound.kl said:
Looking at the LED, there's a slighty darker yellow spot in the middle, but not that dark, just a slight shade above the outer part. Not sure if its burnt out to be honest, becasue when the flash does work, its pretty bright and lights up what i'm pointing it at, but the moment the camera captures the image, the flash is already off, so its just not in sync with the image capture. The blue/green tinge comes after the bright flash, just as it ends. Can you tell me where the burnt out LEDs are being reported mimel?
Click to expand...
Click to collapse
Sent from my MB525 using XDA App
mimel said:
Yours probably is not burnt and might get back to normal by flashing the latest T-Mobile or uk sbf.
A burnt flash light can flash everytime but with very weak white light and ends with green/blue. It's unrecoverable even upgraded to the latest sbf or downgraded to 2.1.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
It is not my case, I have tried all the ROMS and does not work .. do not see any white light, only a very very small light blue-green.
I tried all the ROMS, I have the UK currently 3.4.2, but I also tried the T-Mobile and earlier ones, spent several days doing tests ...
I had the similiar trouble, only first flash and then a reboot was needed. Finally I managed to have normal flash.
What I did?
It is not just sufficient to flash another rom, but to meticulously follow a recipe. In this case I went from 2.21 Stock Rom Central Europe to 2.34 JIT Version, flash still normal. Then Chinese 2.2 ROM, flash only at first time, then reboot needed. I went back to 2.34 JIT Version, flash normal again. Then after a while when the UK 2.2 version came out, I still waited till Higgsy found out how to circumvent the flash troubles: http://forum.xda-developers.com/showthread.php?t=934366
It is for all people who never flashed a non downgradable 2.51 UK Version.
Just follow meticulously every step in Higgsy thread. If flash is working, please inform us here we also need positive affirmation
vince89 said:
I had the similiar trouble, only first flash and then a reboot was needed. Finally I managed to have normal flash.
What I did?
It is not just sufficient to flash another rom, but to meticulously follow a recipe. In this case I went from 2.21 Stock Rom Central Europe to 2.34 JIT Version, flash still normal. Then Chinese 2.2 ROM, flash only at first time, then reboot needed. I went back to 2.34 JIT Version, flash normal again. Then after a while when the UK 2.2 version came out, I still waited till Higgsy found out how to circumvent the flash troubles: http://forum.xda-developers.com/showthread.php?t=937319 In the meantime, this thread is altered again, from a full stock 2.2 UK version do a deblured variant but I believe it still works as a remedy for flash troubles.
It is for all people who never flashed a non downgradable 2.51 UK Version.
Just follow meticulously every step in Higgsy thread. If flash is working, please inform us here we also need positive affirmation
Click to expand...
Click to collapse
This process of Higgsys has been followed many times by myself, and I still have this flash issue. Problem is that when 2.1 firmwares are flashed via RSD Lite, the flash issue remains, and not working as usual as you and Higgsy have described. I'm going to try to uninstall the windows drivers and RSD Lite, reinstall these fresh, and then start the whole process again to see if that makes any difference.
Sent from my MB525 using XDA App
In my case, I have the ROM 3.4.2 UK and this ROM is not "downgrade" but I followed the steps of Higgsy and I do not work, I think my case is different from yours and my Flash is Burnt ...
Thanks for you help...
I think it must be burnt as I have never used the camera flash fixes in some of the ROMS when the camera flash was dodgy and now I am higgsys 3.4.2 ROM and all is good. Cheers
Ok, so I'm still facing this problem on my phone where the camera flash is either out of sync, which flashes brightly too early before image capture, and takes the picture as if no flash was on at all. This occurs on all camera apps on all ROMS installed will all methods, and the flash doesn't work at all on any flashlight apps.
After doing some research, I have found similar issues on other motorola phones, which may or may not help in this regard.
There seems to be a cutoff to the flash reported on Droid phones, either disabling or weakening the flash if the battery threshold is below 30-40%. When the phone has a higher charge than 30-40% or is plugged in to charge, this has eliminated this problem. It seems the driver to the camera flash can determine what your battery level is, despite what your phone is reading out, so if your reading is inaccurate, the flash will cutoff or weaken if below this threshold.
To solve the battery indiactor inaccuracy, follow the steps in the link below using ADB or Clockwork recovery to reset battery stats. Instead of turning off the phone when instructed, take the battery out of the phone for 10 secs and put back in for good measure;
http://androinica.com/2010/02/11/tip-how-to-fix-your-androids-battery-issues-rooted-devices/
Don't know if this will work for people with the flash problem on the Defy, but its worth a try. I haven't tested this. I will later and report back.
I was thinking about the build prop as well, as this seems to feature some lines pertaining to the flash intensity, as quoted by mflich in another post;
mflich said:
hi
i have a defy with 2.21_UK.And when i saw this patch i decide tu up to 2.2_Chinese.
but when i finished it the flash just worked at the first time of reboot
so i want to patch it but i can't enter the custom recovery(at that time i didn't know it's because of USB debugging)
and then i flashed 2.51_UK. but the flash didn't work too.
at this time i can only recovery 2.2 or flash 2.51 and the flash works with low intensity in green light
i noticed that the flash fix is some file in system and i can't read the file with .so
but i found that in build.prop there was some line like this:
ro.media.capture.maxres=5m
ro.media.capture.flash=led
ro.media.capture.classification=classH
ro.media.capture.flip=horizontalandvertical
ro.media.capture.flashIntensity=41
ro.media.capture.torchIntensity=25
but in the same file in 2.21 there are the only two lines:
ro.media.capture.maxres=5m
ro.media.capture.flash=led
so i guess it's because of the differents in this file my flash doesn't work
and the num 41 25 means 41% and 25%?
and what does the classification and flip mean?
with this can i make my flash work again?
sorry for my poor english
Click to expand...
Click to collapse
Can anyone else with flash problems see what is stated in their bulld prop lines for the flash? Maybe we can alter some values to solve our problems?
My flash dont work on today, But I dont have problems synchronizing or low light intensity, light Does Not Work, That appears on the flash is so so small That Is Not Appreciated in a dark room completely.
I think there has been "melted" FlashLED, this strange yet it seems that happened to me when I put the Chinese ROM Froyo and since then no work with any other ROM.
If I indicate that I can do tests to try to fix it, I will.
EDIT: Where are these lines? as I can watch them?
Sorry for my english!!! ... and thanks for the help!
Darkcaptain said:
EDIT: Where are these lines? as I can watch them?
Click to expand...
Click to collapse
You need the PropEditor-0.3.apk from the follwoing link. Be really careful with this, you can modify your system files and possibly brick your phone. Make a backup of your .prop first in this app before making any changes.
http://code.google.com/p/net-widgetron-propeditor/downloads/detail?name=PropEditor-0.3.apk
I have the same issue with the flash that you, Foxhound.kl. I found a temporal solution to the desync. I turn on the led with the tesla app, and then i launch the camera with the auto-flash enabled.
After the first photo the led is turned off, but the tesla app keep running in the background and some way make the flash to be sync and work properly in the other photoes.
Sry for my english.
Appears to me the same thing:
ro.media.capture.classification=classH
ro.media.capture.flash=led
ro.media.capture.flashIntensity=41
ro.media.capture.flip=horizontalandvertical
ro.media.capture.maxres=5m
ro.media.capture.panorama=0
ro.media.capture.shuttertone=1
ro.media.capture.torchIntensity=25
Click to expand...
Click to collapse
ro.media.capture.classification=classH
ro.media.capture.flash=led
ro.media.capture.flashIntensity=41
ro.media.capture.flip=horizontalandvertical
ro.media.capture.maxres=5m
ro.media.capture.panorama=0
ro.media.capture.shuttertone=1
ro.media.capture.torchIntensity=25
I also have these same values.
I am new to flashing things and am trying to fix a problem involving signal loss that requires airplane mode toggling or rebooting to fix.
I was going to try to change my baseband to see if that would help but I am not really sure what mine are. After some research I found this list, https://faramir.eriador.org/r/modem/galaxy_nexus/, and I don't know if I can use all of those. Before I flash any I just want to make sure I wont brick my device.
Thanks
fopho said:
I am new to flashing things and am trying to fix a problem involving signal loss that requires airplane mode toggling or rebooting to fix.
I was going to try to change my baseband to see if that would help but I am not really sure what mine are. After some research I found this list, https://faramir.eriador.org/r/modem/galaxy_nexus/, and I don't know if I can use all of those. Before I flash any I just want to make sure I wont brick my device.
Thanks
Click to expand...
Click to collapse
its a common issue across all roms/kernels, and even stock. some experience them, some dont. but i dont think there is any solution for it yet, just a bunch of non-solutions.
need newbie here.......................
We're going to need some more info. Which ROM? Which recovery? Have you noticed the problem before on another ROM? Is this your first ROM? Full wipe?
bananagranola said:
We're going to need some more info. Which ROM? Which recovery? Have you noticed the problem before on another ROM? Is this your first ROM? Full wipe?
Click to expand...
Click to collapse
from jellytime r29 and cwm 5.0.37 i think i always reroot and root the fone because of this issue the screen will eventually go away im tired of it can u help me.... it started when i flash the venom ics and i have 4ext newest version
ipman777 said:
from jellytime r29 and cwm 5.0.37 i think i always reroot and root the fone because of this issue the screen will eventually go away im tired of it can u help me.... it started when i flash the venom ics and i have 4ext newest version
Click to expand...
Click to collapse
i did a full wipe always did i do something wrong i keep ending half screen flickering after a days or a week it keep bothering me........... once i get to the recovery its till there???????????????? help please
I'm having a very difficult time understanding your writing style and need to clarify.
So far as I understand, you originally had Venom ICS flashed from the latest 4ext. After a few days or a week, half of the screen began flickering. I believe you then rerooted the phone? Then you full wiped (so that's system, data, and cache). You then flashed JellyTime R29 from CWM 5.0.37. The problem showed back up after a few days or a week again. Is that accurate?
Have you flashed any other ROMs? Has the phone been dropped or taken any other damage? Have you tried flashing a stock ROM? Have you had any ROMs on which the problem didn't show up? Did you have this problem on stock before rooting?
bananagranola said:
I'm having a very difficult time understanding your writing style and need to clarify.
So far as I understand, you originally had Venom ICS flashed from the latest 4ext. After a few days or a week, half of the screen began flickering. I believe you then rerooted the phone? Then you full wiped (so that's system, data, and cache). You then flashed JellyTime R29 from CWM 5.0.37. The problem showed back up after a few days or a week again. Is that accurate?
Have you flashed any other ROMs? Has the phone been dropped or taken any other damage? Have you tried flashing a stock ROM? Have you had any ROMs on which the problem didn't show up? Did you have this problem on stock before rooting?
Click to expand...
Click to collapse
yes, its accurate sorry for my english. it started really when i updated the latest 4ext. i flashed sabsa prime and blackout ics before after that jellytime all the way i try to flash the venom ics for fun i guess i paid the price thats when it started. i dont have any problem before that. i did not tried flashing stock rom or damage my phone all rom i flashed show up. this problem has not been my stock rom before. what should i do???????
ipman777 said:
yes, its accurate sorry for my english. it started really when i updated the latest 4ext. i flashed sabsa prime and blackout ics before after that jellytime all the way i try to flash the venom ics for fun i guess i paid the price thats when it started. i dont have any problem before that. i did not tried flashing stock rom or damage my phone all rom i flashed show up. this problem has not been my stock rom before. what should i do???????
Click to expand...
Click to collapse
Assuming you did a full wipe of system, data and cache I can only guess that it's a hardware problem. It persists across multiple ROMs, so that's my guess. See if anyone else has a suggestion.
bananagranola said:
Assuming you did a full wipe of system, data and cache I can only guess that it's a hardware problem. It persists across multiple ROMs, so that's my guess. See if anyone else has a suggestion.
Click to expand...
Click to collapse
But the flickering started when i over charge the fone or i auto brightness it.......... So no one can help me..... About this
ipman777 said:
But the flickering started when i over charge the fone or i auto brightness it.......... So no one can help me..... About this
Click to expand...
Click to collapse
Wait, you didn't say that before. Have you messed with the auto brightness settings before? Try turning it off; is it still a problem? When you say flickering do you mean the back light? Or graphical glitches? Or something else?
bananagranola;351hu 24806 said:
Wait, you didn't say that before. Have you messed with the auto brightness settings before? Try turning it off; is it still a problem? When you say flickering do you mean the back light? Or graphical glitches? Or something else?
Click to expand...
Click to collapse
Graphical glitches i think it look like tv straight lines it bug me becoz it cover the half screen. When i re flash the rom its still there in the recovery but when i pull battery and i try the bootloader and stanby with a half day it will slowly gone bit n bit. It is posible a hardware becoz i try to reroot and go to stock rom and its still it only gone.... If i stanby in bootloader...... Is any where i can do please help i from philippines know where in the world i can repair it here
ipman777 said:
Graphical glitches i think it look like tv straight lines it bug me becoz it cover the half screen. When i re flash the rom its still there in the recovery but when i pull battery and i try the bootloader and stanby with a half day it will slowly gone bit n bit. It is posible a hardware becoz i try to reroot and go to stock rom and its still it only gone.... If i stanby in bootloader...... Is any where i can do please help i from philippines know where in the world i can repair it here
Click to expand...
Click to collapse
The persistence across ROMs (and I'm assuming that you haven't messed with settings) suggests that it's probably a graphics hardware issue. I vaguely remember someone else having this problem but can't remember who; I'll ask around. Unfortunately I'm not from the Philippines, so I don't know where you can get it repaired.
I think gizmoe knows the answer to this one.
Sent from a dream.
bananagranola said:
The persistence across ROMs (and I'm assuming that you haven't messed with settings) suggests that it's probably a graphics hardware issue. I vaguely remember someone else having this problem but can't remember who; I'll ask around. Unfortunately I'm not from the Philippines, so I don't know where you can get it repaired.
Click to expand...
Click to collapse
Thanks for replying........ For all my questions and help. Thanks for the effort tho i need it so bad to resolve my problem, i love my dhd i dont wanna change a fone or buy a dhd again not in my world i buy this fone in london............
Teichopsia said:
I think gizmoe knows the answer to this one.
Sent from a dream.
Click to expand...
Click to collapse
Who's gizmoe how can i reach him or contact him in this forum im newbie here i love what they done to my fone in this site tho you guyz are mad genius........... All around the rom
ipman777 said:
Who's gizmoe how can i reach him or contact him in this forum im newbie here i love what they done to my fone in this site tho you guyz are mad genius........... All around the rom
Click to expand...
Click to collapse
You can private message him here on the forums. His username is Gizmoe.
You can also search for the answer in the dhd and inspire forums, to see if it shows up.
I'm guessing gizmoe may not know the answer since he would have surely posted something in this thread by now. I may be wrong about that as I may also be wrong about him knowing the answer.
Sent from a dream.
Hi guys... First post here as i seem to be stuck.. My phone is a DHD.
I'm not new to rooting or custom ROM's as i often change the ROM on my phone easily without any problems.. Done it 40-50 times now. Never had a problem. I'm used to the AAHK and know what i'm doing.. However, last night i got fed up of the ROM i had, been having some teething troubles lately so figured i'd put it back to stock and then root again and flash a new ROM, this always solves my problems. Now i always have a few others stored on my SD card incase one won't work (i sometimes get the bad installation, aborted) message and i'm not left without a working ROM, but wanted to unroot and put back to stock so opened the AAHK and proceeded as normal to do so ..
Everything was running fine, writing codes as it should, then when it came to the radio downgrade, it got to a part where it usually moves on to the next stage fairly quickly, but this time it just hung.. I left it a few mins to see if it would carry on, no such luck.. I had no choice but to remove the cable and try again.. Now i'm not a fan of removing cables midway through, but it would have just hung forever so i had no choice..
Anyway.. I can still access the CWM screen and have tried every option to get it to do something, but no matter what i do, i can't get past either the white HTC screen or the Black background with the red triangle.. The files are still there on my SD card obviously, i can access them via a card reader, it's just the phone won't move on as i'm guessing the downgrade being interrupted left it with corrupt data... I would have thought running the AAHK again would have started from scratch and just re-run, but this obviously isn't the case.. Any ideas what to do?
RyanH77 said:
Hi guys... First post here as i seem to be stuck.. My phone is a DHD.
I'm not new to rooting or custom ROM's as i often change the ROM on my phone easily without any problems.. Done it 40-50 times now. Never had a problem. I'm used to the AAHK and know what i'm doing.. However, last night i got fed up of the ROM i had, been having some teething troubles lately so figured i'd put it back to stock and then root again and flash a new ROM, this always solves my problems. Now i always have a few others stored on my SD card incase one won't work (i sometimes get the bad installation, aborted) message and i'm not left without a working ROM, but wanted to unroot and put back to stock so opened the AAHK and proceeded as normal to do so ..
Everything was running fine, writing codes as it should, then when it came to the radio downgrade, it got to a part where it usually moves on to the next stage fairly quickly, but this time it just hung.. I left it a few mins to see if it would carry on, no such luck.. I had no choice but to remove the cable and try again.. Now i'm not a fan of removing cables midway through, but it would have just hung forever so i had no choice..
Anyway.. I can still access the CWM screen and have tried every option to get it to do something, but no matter what i do, i can't get past either the white HTC screen or the Black background with the red triangle.. The files are still there on my SD card obviously, i can access them via a card reader, it's just the phone won't move on as i'm guessing the downgrade being interrupted left it with corrupt data... I would have thought running the AAHK again would have started from scratch and just re-run, but this obviously isn't the case.. Any ideas what to do?
Click to expand...
Click to collapse
Why are you running the Hack Kit being S-OFF? there is no use in doing that. You could have flashed a different rom from recovery after doing a full wipe and everything might have been solved, if it was a software issue.
glevitan said:
Why are you running the Hack Kit being S-OFF? there is no use in doing that. You could have flashed a different rom from recovery after doing a full wipe and everything might have been solved, if it was a software issue.
Click to expand...
Click to collapse
Yes i realise that.. That's how i always flashed new ROM's. i could have a new ROM installed in minutes that way, but the reason i was running the hack kit was to put it back to S-ON and stock RUU.. As far as i was aware you had to run the hack kit to put it back to stock, that's the only way of doing it is it not?..
But that's not the problem, my problem now is, getting the phone to show some signs of wanting to get past either screen.
RyanH77 said:
Yes i realise that.. That's how i always flashed new ROM's. i could have a new ROM installed in minutes that way, but the reason i was running the hack kit was to put it back to S-ON and stock RUU.. As far as i was aware you had to run the hack kit to put it back to stock, that's the only way of doing it is it not?..
But that's not the problem, my problem now is, getting the phone to show some signs of wanting to find get past either screen.
Click to expand...
Click to collapse
Are you still S-OFF? then flash recovery again and then a custom rom. Problem solve. If you want to revert to stock, then do that first and the set S-ON the second time...just in case.
glevitan said:
Are you still S-OFF? then flash recovery again and then a custom rom. Problem solve. If you want to revert to stock, then do that first and the set S-ON the second time...just in case.
Click to expand...
Click to collapse
Yes it is still S-OFF, but it won't let me flash anything, run bootloader, access the SD card or i wouldn't have the problem i have..
If i hold volume down and power, i get the usual screen with fastboot, recovery, factory reset, simlock and image crc.. I've tried every one of these apart from the simlock with the same results.. Nothing.. If i select recovery, it flashes the white HTC screen as if it's going to boot, then i get the black phone with the red triangle and it won't go any further.. If i hold volume up and power at that stage, it gives me the apply sdcard:update.zip (which i can't seem to access or just don't have, i'm not sure) and the wipe data/factory reset and cache options..
The only thing it tells me on the screen is E:Can't open /cache/recovery/command
I fear i can't do anything with this phone, even trying to get the hack kit to run is a pain and keeps giving me several errors including the ECHO OFF message. I presume this is because having done the wipe cache and data, i've removed the usb debugging priviliges..
RyanH77 said:
Yes it is still S-OFF, but it won't let me flash anything, run bootloader, access the SD card or i wouldn't have the problem i have..
If i hold volume down and power, i get the usual screen with fastboot, recovery, factory reset, simlock and image crc.. I've tried every one of these apart from the simlock with the same results.. Nothing.. If i select recovery, it flashes the white HTC screen as if it's going to boot, then i get the black phone with the red triangle and it won't go any further.. If i hold volume up and power at that stage, it gives me the apply sdcard:update.zip (which i can't seem to access or just don't have, i'm not sure) and the wipe data/factory reset and cache options..
The only thing it tells me on the screen is E:Can't open /cache/recovery/command
I fear i can't do anything with this phone, even trying to get the hack kit to run is a pain and keeps giving me several errors including the ECHO OFF message. I presume this is because having done the wipe cache and data, i've removed the usb debugging priviliges..
Click to expand...
Click to collapse
You have to flash a recovery in fastboot.....no other way will work.
glevitan said:
You have to flash a recovery in fastboot.....no other way will work.
Click to expand...
Click to collapse
How do i do that exactly?? If i select fastboot, it takes me to the next screen which has bootloader, reboot, reboot bootloader and power down, and again, no matter what i press it won't open any external folders or do anything..
RyanH77 said:
How do i do that exactly?? If i select fastboot, it takes me to the next screen which has bootloader, reboot, reboot bootloader and power down, and again, no matter what i press it won't open any external folders or do anything..
Click to expand...
Click to collapse
ok, if it is ok with you, I can connect over teamviewer and do it for you to show you how to do it....send the ID and PASS in a PM.
glevitan said:
ok, if it is ok with you, I can connect over teamviewer and do it for you to show you how to do it....send the ID and PASS in a PM.
Click to expand...
Click to collapse
What ID and PASS?? I don't understand? Where would i find them??
RyanH77 said:
What ID and PASS?? I don't understand? Where would i find them??
Click to expand...
Click to collapse
Are you reading what I wrote?? if you are interested, I can connect to your PC via teamviewer (http://www.teamviewer.com) but I need the ID and PASS to do it.
RyanH77 said:
What ID and PASS?? I don't understand? Where would i find them??
Click to expand...
Click to collapse
Ryan, from now on, know that if you lie on what you did your phone to someone trying to help you is the worst thing ever. Not only because it won't help to fix it but also because I could also have scr*wed your device by doing some flashing on a messed bootloader.
Lying is the worst strategy ever....I am done. You won't get any help from me anymore. Congrats.
glevitan said:
Ryan, from now on, know that if you lie on what you did your phone to someone trying to help you is the worst thing ever. Not only because it won't help to fix it but also because I could also have scr*wed your device by doing some flashing on a messed bootloader.
Lying is the worst strategy ever....I am done. You won't get any help from me anymore. Congrats.
Click to expand...
Click to collapse
You've misread the situation.. I didn't lie to you about anything, ok, i was unsure of what i'd done, but i certainly didn't ask for help to mislead you and help break my phone. Why would i do that??? I genuinely got stuck with a problem that i didn't know how to get out of.. To be honest i've never had a problem with it before and didn't realise you had to know every single piece of info about it, most of which you forget whilst trying to sort it anyway, and i can't remember if it was flashed previously with a stock ROM or not, but what you mentioned sounded familiar which is why i said i think it might have been, but i can't be 100% certain on that..
I feel bad that you saw it as misleading, as i didn't feel i had been, and that certainly wasn't my intention.. But even though you are unwilling to help me again, i thank you very much for the help you gave me, without you it would still be in a useless state. Thankfully, i have managed to get it working perfectly again and will be more careful in future..
glevitan said:
Ryan, from now on, know that if you lie on what you did your phone to someone trying to help you is the worst thing ever. Not only because it won't help to fix it but also because I could also have scr*wed your device by doing some flashing on a messed bootloader.
Lying is the worst strategy ever....I am done. You won't get any help from me anymore. Congrats.
Click to expand...
Click to collapse
What's wrong with you dude?
If someone doesn't have a knowledge on something (misunderstoods, etc..) it doesn't mean hes lying, lol.
-SmOgER said:
What's wrong with you dude?
If someone doesn't have a knowledge on something (misunderstoods, etc..) it doesn't mean hes lying, lol.
Click to expand...
Click to collapse
Maybe you don´t have a clue on what happened. What's up with me? I will tell you what is going on...i spend many hours of my life helping people in here and in the Hack Kit IRC Support Channel for free, I do it because I enjoy it and don't expect anything in return.
But the worst thing ever is to come accross someone that lies about what he did to his phone. I have been around this site for about 2 years now and never made a brick, do you know why? because I always make sure to follow instructions and ask people what they did in order to provide the best fix, if possible.
When you spend and hour trying to figure out what is going on and trying to flash something and then find out that a froyo RUU might have been flashed (perhaps, I don´t know, not sure...WTF???) and what you did might have scr*wed his phone, it really makes me angry and feel cheated.
To sum up, my time...my decision...maybe you can help him yourself instead of questioning me.
glevitan said:
Maybe you don´t have a clue on what happened. What's up with me? I will tell you what is going on...i spend many hours of my life helping people in here and in the Hack Kit IRC Support Channel for free, I do it because I enjoy it and don't expect anything in return.
But the worst thing ever is to come accross someone that lies about what he did to his phone. I have been around this site for about 2 years now and never made a brick, do you know why? because I always make sure to follow instructions and ask people what they did in order to provide the best fix, if possible.
When you spend and hour trying to figure out what is going on and trying to flash something and then find out that a froyo RUU might have been flashed (perhaps, I don´t know, not sure...WTF???) and what you did might have scr*wed his phone, it really makes me angry and feel cheated.
To sum up, my time...my decision...maybe you can help him yourself instead of questioning me.
Click to expand...
Click to collapse
Like SmOgER said before you Glevitan, i wasn't lying, you just got annoyed with me because i didn't give you 100% of the info you needed, and the only reason for that was because i didn't know it!! When you think you're phone is playing up, you try various ways to get it right again, i'm sorry i don't keep track of every little step i did and i'm sorry this displeased you. But a liar i am not.. The term more appropriate would be clueless!!
You have to accept that us newbies just don't know anywhere near as much about these phones and how they work as you do.. It doesn't mean i lied.. What you see as a misrepresentation of facts doesn't mean i am a liar, it just means i didn't give you the info you wanted, simply because i didn't know it, not that i was withholding it on purpose, THAT would have been bad!!
I am no expert like you, i just root and ROM like most people and hope that it goes right...
Like i said before, i really appreciate the time you took to help me and didn't go unnoticed, and it's great that you help people like me for free, but maybe you should take it a bit easier on the newbies if they're not so expert.. My 1st post asking for help and i already feel like i'm not welcome anymore.. That's pretty bad for such a big community!!
SmOgER.. At least YOU understood where i was coming from..
1. Flashing a Froyo RUU is an important stop on the quick path to bricking your phone, and that warning is splashed all over AAHK and other documentation. That's why glevitan is so upset about not being told of the possibility that you might have done it: it's very bad, and users should know that it's very bad, and it wastes a lot of time.
2. Not knowing what you're doing and messing with your phone, and then not keeping track of what you're doing, is extremely unwise. When helping out on XDA, I personally don't expect everyone to know everything, but taking basic precautions really does seem like common sense.
3. Next time, read similar threads that came before you and ask the community. For example: I have X problem. I have researched and found Y and Z thread links with similar symptoms. I am considering trying what A suggested in Y. Is that the wisest course of action? Then you show that you have done your part in solving your own problem, and the community will respect that, even if you're way off base.
Obviously, I personally wasn't there on teamviewer, so I have no idea about the clueless v. lying thing.
bananagranola said:
1. Flashing a Froyo RUU is an important stop on the quick path to bricking your phone, and that warning is splashed all over AAHK and other documentation. That's why glevitan is so upset about not being told of the possibility that you might have done it: it's very bad, and users should know that it's very bad, and it wastes a lot of time.
2. Not knowing what you're doing and messing with your phone, and then not keeping track of what you're doing, is extremely unwise. When helping out on XDA, I personally don't expect everyone to know everything, but taking basic precautions really does seem like common sense.
3. Next time, read similar threads that came before you and ask the community. For example: I have X problem. I have researched and found Y and Z thread links with similar symptoms. I am considering trying what A suggested in Y. Is that the wisest course of action? Then you show that you have done your part in solving your own problem, and the community will respect that, even if you're way off base.
Obviously, I personally wasn't there on teamviewer, so I have no idea about the clueless v. lying thing.
Click to expand...
Click to collapse
Yes i understand what you're saying, and i appreciate most of it. However, it's not often practical or even possible in some cases to write down or note everything you do in a documented fashion.. And like you might have previously missed, i have flashed various ROM's 40-50 times, and the AAHK has worked perfectly for me everytime except the last where it took it upon itself to just freeze on me, it was a computer issue, not a human error.. Also, why would reflashing a Froyo RUU to a phone that was originally shipped as a Froyo unit cause any problems??
I don't understand that part..
One final note, i did have a look through similar threads, but there are so may threads with similar symptoms that it's hard to sift through them all for a definitive answer, and even when you do read them, only one or two parts might be relevant, if any.. So it's quicker to come straight out and ask rather than waste hours trawling through them all to no avail i think.
Whatever happened doesn't matter anymore. Lesson learned.
You seem like a nice guy. Let's back on topic.
Is the issue solved or not?
Try to state what is the current issue. What was the state of the phone when it was working. What happened or what were you trying to do when it got messed up. What have you tried so far. Etc, etc, etc. The more the info the better.
Edit: Nevermind. You *******, you flashed a froyo hboot on your HTC Inspire/DHD after we’ve warned NOT to for over a year. Here’s the fix:
Sent from a dream.
RyanH77 said:
Yes i understand what you're saying, and i appreciate most of it. However, it's not often practical or even possible in some cases to write down or note everything you do in a documented fashion.. And like you might have previously missed, i have flashed various ROM's 40-50 times, and the AAHK has worked perfectly for me everytime except the last where it took it upon itself to just freeze on me, it was a computer issue, not a human error.. Also, why would reflashing a Froyo RUU to a phone that was originally shipped as a Froyo unit cause any problems??
I don't understand that part..
One final note, i did have a look through similar threads, but there are so may threads with similar symptoms that it's hard to sift through them all for a definitive answer, and even when you do read them, only one or two parts might be relevant, if any.. So it's quicker to come straight out and ask rather than waste hours trawling through them all to no avail i think.
Click to expand...
Click to collapse
It is not about if you are an expert or not...I am not, belive me. But I am wise enough to read and try to learn. Doing things like a monkey will not excuse you.
If you don't understand, maybe it is time for you to buy an Iphone. Hacking is not for the lazy b*stards who don't even know what they do. And belive me, your story is hard to belive, running the Hack Kit with a custom rom is not possible...you should have got stuck, that is how it works.
YOUR PHONE....YOUR PROBLEM...I don't give a penny for it.
glevitan said:
It is not about if you are an expert or not...I am not, belive me. But I am wise enough to read and try to learn. Doing things like a monkey will not excuse you.
If you don't understand, maybe it is time for you to buy an Iphone. Hacking is not for the lazy b*stards who don't even know what they do. And belive me, your story is hard to belive, running the Hack Kit with a custom rom is not possible...you should have got stuck, that is how it works.
YOUR PHONE....YOUR PROBLEM...I don't give a penny for it.
Click to expand...
Click to collapse
I wouldn't be seen dead with an iPhone.. I hate Apple and Apple products for that specific reason. They don't give the freedom of open source and don't allow real control. But i will be more careful in future and learn from my mistakes.. However, i'm not a lazy bastard hacker as you so put it, and i don't care for the accusation of being one either, please be careful what you say in future as statements like that are completely uncalled for ..
I understand you are somewhat unhappy with me, but please don't resort to slating me. I wouldn't do the same to you if you were wrong.
And yes Teichopsia.. I am a nice guy, thank you for noticing.. I realise now i made a mistake and i just got stuck, but the phone is now running absolutely flawlessly thank you..
Hello there,
I'm very new, so apologies if I'm posting in the wrong forum, or if there's a more appropriate place for this quesion!
Here's the thing... In an attempt to root my Sony Xperia C1905, I was trying to revert my firmware to a previous version of Android (4.2, I think). Anyway, something happened and things didn't work out, so I re-flashed it with a version of 4.3 that I downloaded from somewhere (I don't know where, but the default language was set to German!)... Thing is, when I turn my phone on, I get stuck in a boot-loop (pretty Xperia colous) for about 3-5 minutes until it gets to the main screen.
I have tried things like using the Sony PC Companion to repair it, but to no avail. Is there some other way I can fix this, or revert it to its original firmware, without this stupid boot-loop?
Thanks for reading!
TheStudent said:
Hello there,
I'm very new, so apologies if I'm posting in the wrong forum, or if there's a more appropriate place for this quesion!
Here's the thing... In an attempt to root my Sony Xperia C1905, I was trying to revert my firmware to a previous version of Android (4.2, I think). Anyway, something happened and things didn't work out, so I re-flashed it with a version of 4.3 that I downloaded from somewhere (I don't know where, but the default language was set to German!)... Thing is, when I turn my phone on, I get stuck in a boot-loop (pretty Xperia colous) for about 3-5 minutes until it gets to the main screen.
I have tried things like using the Sony PC Companion to repair it, but to no avail. Is there some other way I can fix this, or revert it to its original firmware, without this stupid boot-loop?
Thanks for reading!
Click to expand...
Click to collapse
Please refer to this thread as it will tell you how to flash .ftf files manually. Also, make sure that you tick wipe data and wipe cache. This is probably the source of your bootloop problems. Have a good day, feel free to PM me if you need more help.
Wait, buddy i might be wrong here but did you say that it goes to the min screen after the bootanimation ( pretty colours). If so, then that isnt a bootloop. A bootloop is when your phone stays on that bootanimation and never loads up, it's also called a soft brick. As gamer649 above me said, you might wanna check out that thread to know how to flash ftfs manually.
Thank you both so much for responding so quickly! I shall indeed check out that thread posted by gamer649 and hope that solves the problem (If not I shall report back.)
Thanks again!
paper13579 said:
Wait, buddy i might be wrong here but did you say that it goes to the min screen after the bootanimation ( pretty colours). If so, then that isnt a bootloop. A bootloop is when your phone stays on that bootanimation and never loads up, it's also called a soft brick. As gamer649 above me said, you might wanna check out that thread to know how to flash ftfs manually.
Click to expand...
Click to collapse
Ah yeah, you're right, it's not a boot-loop in that case because it does indeed load up after a while, my mistake!