It's a very odd one in landscape they light up, in portrait mode they don't. Well, when I noticed that problem I immedeately flashed framework-res.apk - didn't fix so I remembered when I went to recovery they did light up, so did I and started counting seconds while it loaded into it but they didn't light up. So is this some kindo of physical damage? Landscape uses obviously different LED's, it ruins the niceness from that phone, when bottom bar is dark At the moment i was using Nik's Trinity 2.0 rom and i'm using it so far.
Can you guys provide some help, it will increases my love to the phone substantially.
Therefore my phone will be shiny and elegant again!!
I don't think you need to worry that it's a physical damage... If that was the case landscape buttons would be dead aswell. I wish I could help you but why not just flash an official rom and start over? I think running an HTC rom should fix the buttons at least...
owziee said:
I don't think you need to worry that it's a physical damage... If that was the case landscape buttons would be dead aswell. I wish I could help you but why not just flash an official rom and start over? I think running an HTC rom should fix the buttons at least...
Click to expand...
Click to collapse
Yes I would agree that you need to try a stock HTC ROM before you blame it on the hardware.
tpbklake said:
Yes I would agree that you need to try a stock HTC ROM before you blame it on the hardware.
Click to expand...
Click to collapse
Yes, but they worked in recovery earlier
henrylife said:
Yes, but they worked in recovery earlier
Click to expand...
Click to collapse
When you boot in recovery, it is not using the custom kernel that your ROM is using. In order to rule out hardware, you need to check the phone using the stock HTC IncS kernel and a stock ROM.
Installed CM 7.1 nope didn't work and tried a load of kernels...
So how do i take that apart?
henrylife said:
Installed CM 7.1 nope didn't work and tried a load of kernels...
So how do i take that apart?
Click to expand...
Click to collapse
get back stock to test whether it is working,cm7 wasn't stock though..
Sent from my HTC Incredible S using Tapatalk
Don't lose root.... newest stock will up date your h-boot
I don't want to know to stock I know how these lights work. They depend on framework-res.apk and on kernel. Ok well stock may change but it's 5% reasonable. Is there some kind of diagnostic tool out? A fastboot one will be great.
UPDATE: 2 days ago I used my phone as router and it was charging, so yesterday I did disconnect my phone and saw lights worked. While in bus they started blinking
(like dying bulb) and few minutes ago i barely saw them and then everything was dark again. Sometimes they get revived for some time and process is under loop again
I'm trying to remember, it occured after attempts to get it charge, Incredible S usb dock doesn't work properly so i crumpled it a little bit and finally it turned on. First notice were the lights, and after heavy charge they got somehow revived. I want to see this panel with my own eyes, can someone put disassemble guide please?
I'm pretty sure new backlit is quite expensive but unfortunately Physical damage it is.
It should be ROM's problem?
Maybe flash another ROM or restore stock ROM.
uggies said:
It should be ROM's problem?
Maybe flash another ROM or restore stock ROM.
Click to expand...
Click to collapse
Nah, it shouldn't
Related
I was updating my G1 to Kingxkxlick ROM & it was just stuck at screen of X, I tried to re-update it via RECOVERY, & I don't know but it restarted when I click to HOME for update.
When it restarts, it showed G1 & X logo, stuck there for a while, but THEN I TOOK OUT THE BATTERY
& It's no more working, not charging, not turning on, BATTERY WAS 100% charged
Please help me out, I don't wanna lose my g1, i'm not even in US right now
If you get to the boot screen and you've past the G1 logo, your phone is fine. Its the ROM you're trying to flash.
Make sure before flashing any rom that you do a factory data wipe, dev wipe, and make sure you have 3 partitions, swap, ext2-3-4,and fat
once you have done this, make sure youre using kingklicks 6.1 first, then upgrade to the 7
Kings 7 rom is only minor changes to add to the base 6.1, if you're trying to flash the newest update alone, if you notice its only 6MB which is definatly NOT the correct size a ROM should be.
So download the older version 6+ then flash, then without rebooting, flash update version 7 over it, and then reboot.
Hope that helps!
To be more clear than the guy above me...
Assuming your talking about this King rom.
http://forum.xda-developers.com/showthread.php?t=622170
Download 1.7
Download 1.7.1
Flash 1.7
reboot
Flash 1.7.1
What recovery do you have? Stock? Amon Ra? What SPL?
Can probably fix your phone if you answer those questions.
G1ForFun said:
To be more clear than the guy above me...
Assuming your talking about this King rom.
xxxx
Download 1.7
Download 1.7.1
Flash 1.7
reboot
Flash 1.7.1
What recovery do you have? Stock? Amon Ra? What SPL?
Can probably fix your phone if you answer those questions.
Click to expand...
Click to collapse
I've already told phone is not charging, not starting recovery or fastboot screen
I had Amon RA recovery, just had CyanogenMOD Latest one
Was changing it to Kingxkxlicks latest ROM & got it all done
Any hope for recovery OR what else Option I have ?
PS: Not in US
rawfire said:
I've already told phone is not charging, not starting recovery or fastboot screen
I had Amon RA recovery, just had CyanogenMOD Latest one
Was changing it to Kingxkxlicks latest ROM & got it all done
Any hope for recovery OR what else Option I have ?
PS: Not in US
Click to expand...
Click to collapse
If its not turning on, then I'm pretty sure it's dead. Needs a new board all together, I had the same thing happen to me, pretty much the same exact way. It was taking way too long to boot (20+ mins) so I took out the battery and now won't turn on at all. If you find a way to fix it let me know so I can revive mine.
dcontrol said:
If its not turning on, then I'm pretty sure it's dead. Needs a new board all together, I had the same thing happen to me, pretty much the same exact way. It was taking way too long to boot (20+ mins) so I took out the battery and now won't turn on at all. If you find a way to fix it let me know so I can revive mine.
Click to expand...
Click to collapse
I contacted some local repairers, they just told that it need to get it's boot reset by putting some wires & stuff on board to make it work again.
It's costing me too much so I haven't done it by yet (almost 5,000 PKR)
If anyone here know the thing I told, do let me know, I can do it by myself (can take risk), but can't spend that much money lol
rawfire said:
I contacted some local repairers, they just told that it need to get it's boot reset by putting some wires & stuff on board to make it work again.
It's costing me too much so I haven't done it by yet (almost 5,000 PKR)
If anyone here know the thing I told, do let me know, I can do it by myself (can take risk), but can't spend that much money lol
Click to expand...
Click to collapse
They trying to rip you off.. Nobody has got JTAG working on the g1 yet, they can't do anything by "putting some wires and stuff on board". If it won't charge and won't turn on, there's nothing you can do except replace the board.
goldenarmZ said:
They trying to rip you off.. Nobody has got JTAG working on the g1 yet, they can't do anything by "putting some wires and stuff on board". If it won't charge and won't turn on, there's nothing you can do except replace the board.
Click to expand...
Click to collapse
what's the lowest price I have to pay for motherboard of G1, because it's not available in local market by now ?
You won't find the mainboard for sale anywhere, so your best bet is to search ebay for a g1 with a broken screen.. then you can swap in the board from that and keep the rest of the parts as spares:
http://cgi.ebay.com/T-Mobile-G1-Bro...Cell_Phones?hash=item2eabb4e988#ht_500wt_1182
edit: before you go swapping the board.. have you tried a different battery? it could be as simple as that.
I recently bought this Nexus off eBay and it worked fine.
Owner said it had problems with the SD card, but it seemed to be working, for they said it wouldnt read, when it does.
Anyway, it had cyanogen mod 6.1.1 on it, and I hate the setup...so i changed roms. That was a success, but when i flashed a sense rom thru clockwork(most updated) it said:
E:Error in /sdcard/N1Sensation_v0.4.zip
(Status 0)
Installation aborted.
Now, when i flash any roms, whether it says it installed correctly, it doesnt change anything. Now it's stuck at the 4 color x with the unlock icon. Any advice is good advice!
In my hboot, it says:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANAL-SYNT0103
RADIO-5.00.00.04
Oct 12 2010, 14:33:16
HBOOT
Etc. Etc. Etc.
Thanks for any help!
Edit: I fixed the issue with why it failed, was my fault, didnt partition the card...but i was flashing a stock rom and it said complete and when i rebooted it stayed at the X and then powered off. Since then has never turned on. I don't know what to do. Nothing will turn it back on. I have a universal charger that charges the battery and it said the battery is full. I need help!
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Dude Random21 said:
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Click to expand...
Click to collapse
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
matistight said:
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
Click to expand...
Click to collapse
Try flashing CM7. Also...before you do...you may want to search for a format.zip from a member named temasek. It'll wipe your phone...clean. Real clean. Then flash CM7. try that.
also....those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
SiNJiN76 said:
Try flashing CM7.
those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
Click to expand...
Click to collapse
I can't flash anything. Phone wont react to anything anymore. Hoping one of my family members can fix it. But if I get it on I will try that.
I am pretty sure i waited long enough, but who knows. I didn't partition my card, which may have been the problem. And also it was S-On....which i thought was odd when it had a custom firmware.
Unlock bootloader. Flash recovery. Boot into recovery. Wipe everything. Flash rom.
Why do you guys keep suggesting software stuff when it's probably a hardware problem he can't get the phone to boot up so he can't do any of that.
Although there is one thing I want you to try before your family take a crack at it to take it apart and what not, it's a long shot but it's your last chance if it's software. Hold down trackball and press power keep holding trackball for another 5-10 seconds (better to long then to short) then connect it to the computer via USB you could see a popup notification saying that it's looking for driver software if you do then it's software and we need to reflash everything and might need to unlock the bootloader. Now if you don't see a popup notification I would still go check in the device manager and check for an unidentified device probably in other (it should be extracted so that you can see it).
If this doesn't work then sorry but I think it's a brick
Because in order to find out if its truly a hardware problem you need to try every software fix first.
Op mentioned nothing of trying fastboot as well. Software fix is free hw is not. That is why we suggest software fixes.
Sent from my Nexus S using XDA App
Let me remind you guys, THE PHONE WONT TURN ON AT ALL REGARDLESS OF WHAT I DO. I can post a YouTube video to show everything. It'd be very random for it to be hardware because it just turned off and will not turn back on. If there is any software like an RUU out there, that would help, if not, ill have to buy a bottom piece and warranty it out. But I'd feel bad because that isn't the right thing to do.
I don't expect you guys to fix it and I and very thankful of your help! But the phone won't turn on at all. So telling me to flash roms doesn't work. Imagine it as flashing a rom with the battery out of your phone. I am wondering if there's an adb way or something to get it to turn on and restore to stock?
With all that said, any help is amazing help and I am very grateful that this isn't a post I have to bump! Thank you so much, when I go on the PC, ill thank the helpful posts
Sent from my (finally) permanent root Sensation 4G
Then it is a brick if it won't turn on at all. The entire getting stuck at the x thing confused me to think it was powering on.
You have me confused sir, I'm not quite sure what good it is your looking for a RUU for. If the phone truly won't turn on/go past the X screen and you have it on a charger with no LED notification, then the phone is bricked. When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom. If you can still get to the bootloader screen then you are not bricked and should retry everything from scratch.
Thread Closed
xsnipuhx said:
When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom.
Click to expand...
Click to collapse
Sensation based, but it was a Sense rom
Confirmed it is bricked.
Sold on eBay for $100
Bought for $77
Semi-Winning.
Thread Closed
Hi guys, My galaxy note isn't working properly.
I can't see anything on the screen. (Black screen) but touch works.
I can still see the lights on menu and back button. Phone itself works fine. I called the phone and slide pick up even though I can't see the screen, I can talk.
So basically screen has stop show images.
Any idea what it is?
What did you do?
Honestly I didn't do anything. I left my phone in my bag then couple of hours later it stopped working. Works fine in the morning.
Can you elaborate your Note's configuration? Which ROM, kernel, etc?
kopitalk said:
Can you elaborate your Note's configuration? Which ROM, kernel, etc?
Click to expand...
Click to collapse
Phone is rooted, Running rocket ROM. Been running rocket ROM for almost 1 month. I didn't do anything before this happen.
and fyi, when I boot up the phone, still can't see anything, even with recovery mode.
Probably an SOD. Have you tried rebooting? Which kernel do you use?
kopitalk said:
Probably an SOD. Have you tried rebooting? Which kernel do you use?
Click to expand...
Click to collapse
I've tried rebooting, taking out battery and restart, tried going to recovery mode, anything I could think of.
I'm not sure about kernel. I can't check. But it's the kernel the comes with Rocket ROM.
nicksnoobie said:
I've tried rebooting, taking out battery and restart, tried going to recovery mode, anything I could think of.
I'm not sure about kernel. I can't check. But it's the kernel the comes with Rocket ROM.
Click to expand...
Click to collapse
And after anything you could think of the screen doesn't show anything?
Sorry mate, seems that your hardware is faulty and you need to send it back for repair.
kopitalk said:
And after anything you could think of the screen doesn't show anything?
Click to expand...
Click to collapse
When I rebooted my phone, I can still hear my unopened text messages notification sound. Buttons and touch are responsive.
and phone is rooted, doesn't that void the warranty?
this has happened to me a couple of times..
it happens randomly after trying to come out of sleep...the phone works fine after a reboot..
i wonder what this problem is??
thankfully it only happens once in a blue moon...
I'm on stock rom unrooted...
Sent from my GT-N7000 using XDA
Do you have custom binary counter increment and/or yellow triangle?
Well if you can't see anything on the screen, they won't either, provided it is a hardware malfunction.
I bought this phone on eBay, and it's overseas seller. Do I contact Samsung or the seller?
You should contact the party responsible for the warranty of your product.
Well, if they find out that you are on custom ROM they could deny warranty.
Since it looks like your screen went off, PC odin should still work, unconditionally.
So just boot up the phone in download mode (vol down+ menu+ power), connect to PC odin and flash stock firmware relevant to your country and you are good to go.
anilisanil said:
Since it looks like your screen went off, PC odin should still work, unconditionally.
So just boot up the phone in download mode (vol down+ menu+ power), connect to PC odin and flash stock firmware relevant to your country and you are good to go.
Click to expand...
Click to collapse
I will try that and let you know how it goes. Thanks
nicksnoobie said:
I will try that and let you know how it goes. Thanks
Click to expand...
Click to collapse
Hey this does not mean that your screen works, sorry for my misleading reply.
That is just to be sure that you get the warranty.
still doesn't work. Gonna have to send it for warranty i guess...
and could this be like a loose plug/connector inside a phone?
Hi Guys,
I had a reboot loop problem in my X8 after installing Viber from a Wifi connection and decided to mod it. I successfully unlocked the boot loader & rooted my Xperia X8. Flashed it with CM7 RC1 V4. I rebooted the phone to see the Cyanogen Mod screen with the skate board and it proceeded to ask me a question about the setup wizard or market option, I made a selection and the phone went dead. It rebooted and started hanging on the SE logo. I thought it was due to Baseband 15 and flashed it but no luck.
I have Clockwork Mod on it and can randomly enter it also. I would appreciate any help and pointers, is this an issue due to using the wifi and is the hardware at fault. Once the boot loop starts the battery drains pretty fast I can see the Cyanogen battery status icon and try to wait for it to charge completely
Many thanks & regards
bytecodeboy said:
Hi Guys,
I had a reboot loop problem in my X8 after installing Viber from a Wifi connection and decided to mod it. I successfully unlocked the boot loader & rooted my Xperia X8. Flashed it with CM7 RC1 V4. I rebooted the phone to see the Cyanogen Mod screen with the skate board and it proceeded to ask me a question about the setup wizard or market option, I made a selection and the phone went dead. It rebooted and started hanging on the SE logo. I thought it was due to Baseband 15 and flashed it but no luck.
I have Clockwork Mod on it and can randomly enter it also. I would appreciate any help and pointers, is this an issue due to using the wifi and is the hardware at fault. Once the boot loop starts the battery drains pretty fast I can see the Cyanogen battery status icon and try to wait for it to charge completely
Many thanks & regards
Click to expand...
Click to collapse
* Did you factory reset it from CWM before installing the ROM? Boot loops are common when one doesn't, particularly if you're coming from another ROM (from what you say, I guess you're coming from stock 2.1)
* It seems that you flashed baseband 015 AFTER flashing the new ROM. AFAIK it should be done BEFORE flashing a new ROM, while still on stock 2.1. If that's the case, you'd have to go back to 2.1 using SEUS (or Flashtool; there are stock ROM images here on XDA), THEN flash baseband 015, THEN root, THEN flash CM7 again.
---
As a side note, you unlocked your bootloader but didn't install a new kernel, which is what one normally unlocks the bootloader for. Unlocking the bootloader isn't needed to flash a ROM as long as it works with the stock kernel (most don't, but yours should.)
Mod issue or battery or hardware fault
Cheshire-Cat said:
* Did you factory reset it from CWM before installing the ROM? Boot loops are common when one doesn't, particularly if you're coming from another ROM (from what you say, I guess you're coming from stock 2.1)
* It seems that you flashed baseband 015 AFTER flashing the new ROM. AFAIK it should be done BEFORE flashing a new ROM, while still on stock 2.1. If that's the case, you'd have to go back to 2.1 using SEUS (or Flashtool; there are stock ROM images here on XDA), THEN flash baseband 015, THEN root, THEN flash CM7 again.
---
As a side note, you unlocked your bootloader but didn't install a new kernel, which is what one normally unlocks the bootloader for. Unlocking the bootloader isn't needed to flash a ROM as long as it works with the stock kernel (most don't, but yours should.)
Click to expand...
Click to collapse
Many thnks for the reply mate, what you said is right. I might have missed a few things. But I reflashed Baseband 15 yesterday before your reply to my post and now it seems to be booting into cyanogen mod happily but each time it takes only a few seconds and through a few setup screens before it reboots again.This is exactly what was happening even on the stock ROM before doing any Mod procedure and the battery gets drained too. Could this be a hardware fault.
bytecodeboy said:
Many thnks for the reply mate, what you said is right. I might have missed a few things. But I reflashed Baseband 15 yesterday before your reply to my post and now it seems to be booting into cyanogen mod happily but each time it takes only a few seconds and through a few setup screens before it reboots again.This is exactly what was happening even on the stock ROM before doing any Mod procedure and the battery gets drained too. Could this be a hardware fault.
Click to expand...
Click to collapse
i didnt get it, when on setup screen you mean when it tells to add your email.....and when you are finished it reboots?!
if i understood well,there is no hardware problem, go to cwm, full wipe-factory reset,advanced>wipe dalvik, reinstall your rom(install custom zip) and it should work:fingers-crossed:
stamatis16 said:
i didnt get it, when on setup screen you mean when it tells to add your email.....and when you are finished it reboots?!
if i understood well,there is no hardware problem, go to cwm, full wipe-factory reset,advanced>wipe dalvik, reinstall your rom(install custom zip) and it should work:fingers-crossed:
Click to expand...
Click to collapse
Thanks for the reply stamatis, basically its just shutting down because there is no battery left to power it, it seems. At times it reaches upto the setup wizard (shown when booting for the first time), the next time it could go up to adding a gmail account or language selection screen. I have even seen it load the home screen before it shuts off. This all started happening after downloading some apps from a wifi connection. I have done that before wiping and re installing but will try again. My presumption is that since it was happening on stock ROM and now on CM7 too then it's probably a hardware issue
Regards
bytecodeboy said:
Thanks for the reply stamatis, basically its just shutting down because there is no battery left to power it, it seems. At times it reaches upto the setup wizard (shown when booting for the first time), the next time it could go up to adding a gmail account or language selection screen. I have even seen it load the home screen before it shuts off. This all started happening after downloading some apps from a wifi connection. I have done that before wiping and re installing but will try again. My presumption is that since it was happening on stock ROM and now on CM7 too then it's probably a hardware issue
Regards
Click to expand...
Click to collapse
ok i see now,your problem is battery drain,
is it that extream? i mean, you charge to full and when you open it up it shut down by low battery?
have you try to opening while charging?is it the same?
are you sure its charging?
that way too xtream to be software problem so its more likely that its hardware...
stamatis16 said:
ok i see now,your problem is battery drain,
is it that extream? i mean, you charge to full and when you open it up it shut down by low battery?
have you try to opening while charging?is it the same?
are you sure its charging?
that way too xtream to be software problem so its more likely that its hardware...
Click to expand...
Click to collapse
yes you got it right. I do charge it fully and when it boots the CM7 UI for a few seconds the battery goes down half or even less or nearly empty. I have tried opening it while charging and thats when the above happens, yes I can see the Cyanogen charging icon. So you think its a hardware issue and I should not pursue it further
bytecodeboy said:
yes you got it right. I do charge it fully and when it boots the CM7 UI for a few seconds the battery goes down half or even less or nearly empty. I have tried opening it while charging and thats when the above happens, yes I can see the Cyanogen charging icon. So you think its a hardware issue and I should not pursue it further
Click to expand...
Click to collapse
yea, i guess your battery almost dead.....and i dont think its a good idea to by new battery, you better buy new phone,as the batteries are quite expensive if you think that the worth of the x8 right now would be 50 euros....
Try ebay bro
Sent from my E15i using Tapatalk 2
Flash rom with xrecovery not cwm
Sent from my X8 using xda premium
Hi guys, as a lot of people now confirmed to me that it solved their problems complete when they switched to the GPE Firmware i think it is a good thing to write all that in a little own thread so not every user has to spam for the same bugs in all Android N Rom Threads.
First of all, YOU NEED TO HAVE S-OFF to flash Firmware files!!!
Using the GPE Firmware can solve the following bugs (thats no guarantee there can still be bugs in the Rom+Kernel):
-In Call Sound problems
-Camera Problems
-Mobile data problems
-wifi problems
-battery problems
Those bugs where already existing when the first Android 6 (M) Roms came to our M7 and with Android 7 (N) its still the same. But, those bugs are mostly present while using a Custom Rom on a Sense Firmware and they are nearly complete gone when you use the GPE Firmware.
Thanks to the Slim Jim Guy we have everything we need already here in the Forum. And please be that nice just give him a thanks for his thread as it helps us all a lot. Here is his Post and here is the direct download of his complete prepared Firmware without recovery and boot img GPE Firmware Download. It will delete nothing from your device, just changes the Firmware.
This Firmware is complete different to the one from HTC and is newer because Google provided much longer official updates for the m7 GPE than HTC did for the usual version.
Changed OP for complete Firmware file from Slim Jim Guy (thanks to maciclazar for this information)
just a little bump as a reminder haha
So if I understood right, it's better to have gpe firmware if I have a nougat ROM even if my phone is not GPE?
JustElisha said:
So if I understood right, it's better to have gpe firmware if I have a nougat ROM even if my phone is not GPE?
Click to expand...
Click to collapse
You can flash the GPE Firmware on any device thats not from a provider with CDMA radio like Verizon devices.
saturday_night said:
You can flash the GPE Firmware on any device thats not from a provider with CDMA radio like Verizon devices.
Click to expand...
Click to collapse
I just have to flash it in twrp or S-OFF is required?
JustElisha said:
I just have to flash it in twrp or S-OFF is required?
Click to expand...
Click to collapse
Like written in OP "First of all, YOU NEED TO HAVE S-OFF to flash Firmware files!!!"
@saturday_night I was using that firmware from Santod040's thread for months until I realised it was not full firmware.
The full GPE firmware is located in this post by Slim Jim Guy. It is full firmware containing hboot, radio and everything else and will turn you phone in full GPE device and the best thing is it fixes random reboots on nougat and marshmallow roms.
Edit: Never mind. Found the answer I was looking for.
maciclazar said:
@saturday_night I was using that firmware from Santod040's thread for months until I realised it was not full firmware.
The full GPE firmware is located in this post by Slim Jim Guy. It is full firmware containing hboot, radio and everything else and will turn you phone in full GPE device and the best thing is it fixes random reboots on nougat and marshmallow roms.
Click to expand...
Click to collapse
Exactly, link of post #1 is the black hboot 1.54 only
Would this work for Android N ROMs with the international variant? Running Xenon 7.1 ATM.
Not sure what's wrong. I've flashed GPE firmware, got a new battery, still phone does this awful thing Could be mainboard problem? How can I test motherboard?
Thanks
umbyka said:
Not sure what's wrong. I've flashed GPE firmware, got a new battery, still phone does this awful thing Could be mainboard problem? How can I test motherboard?
Thanks
Click to expand...
Click to collapse
What ROM are you using right now, how did you get S-OFF?
Yesterday I've turned back to stock GPE 5.1, hoping that it's a ROM problem, but still my phone shuts down by itself, even at 90%. S-OFF I gained a few years ago, in 2014 I think. Rumrunner if I remember right.
@umbyka are you able to completely drain the battery to zero, then, without powering the phone back on, connect it to a charger and let it charge to 100%?
93zx7 said:
@umbyka are you able to completely drain the battery to zero, then, without powering the phone back on, connect it to a charger and let it charge to 100%?
Click to expand...
Click to collapse
Yes, I'm able. So..I did turn back to 5.1 GPE, full stock, seems that, with this ROM, everything is normal. Didn't mention, that with all N ROMs the phone went so hot, that it was almost burning, but with 5.1 GPE it doesn't. I did this HTC said battery calibration, with both volume buttons + power button for 2 minutes also. Hopefully it's not a mainboard issue after all...
umbyka said:
Yes, I'm able. So..I did turn back to 5.1 GPE, full stock, seems that, with this ROM, everything is normal. Didn't mention, that with all N ROMs the phone went so hot, that it was almost burning, but with 5.1 GPE it doesn't. I did this HTC said battery calibration, with both volume buttons + power button for 2 minutes also. Hopefully it's not a mainboard issue after all...
Click to expand...
Click to collapse
How's the camera performance? How often does the purple hue come?
zeeBomb said:
How's the camera performance? How often does the purple hue come?
Click to expand...
Click to collapse
This is a hardware problem and not software related. When HTC made the first OTA Updates the device became too hot during the update process so that some camera modules got a little damage which caused this purple pictures. If it wasnt repaired under guarantee the only way for you to get this fixed is replace the camera module.
saturday_night said:
This is a hardware problem and not software related. When HTC made the first OTA Updates the device became too hot during the update process so that some camera modules got a little damage which caused this purple pictures. If it wasnt repaired under guarantee the only way for you to get this fixed is replace the camera module.
Click to expand...
Click to collapse
right...but what exactly would the camera fix be if i flash gpe?
So, I haven't been around for a while now, but I'll share with you the problems I have :
Even with GPE ROM phone shuts itself down sometimes even at 70% battery, sometimes it lasts till 20%. When it shuts down itself, turning it back on seems to get a problem. Normally it should get back on with all my settings saved, I mean background, ringtones, etc., but it starts with a message : Android is optimising apps..., and when it boots up finally, everything is gone. I mean background, ringtones, passwords. So, anybody has a clue what's going on?
umbyka said:
So, I haven't been around for a while now, but I'll share with you the problems I have :
Even with GPE ROM phone shuts itself down sometimes even at 70% battery, sometimes it lasts till 20%. When it shuts down itself, turning it back on seems to get a problem. Normally it should get back on with all my settings saved, I mean background, ringtones, etc., but it starts with a message : Android is optimising apps..., and when it boots up finally, everything is gone. I mean background, ringtones, passwords. So, anybody has a clue what's going on?
Click to expand...
Click to collapse
Did you clean flash everything including firmware? If yes, that sounds like a hardware damage