Related
Hi Guys,
I recently unlocked the bootloader of my Optimus G (E987 flashed to E975) using Freegee (Downloaded from the market) and installed TWRP. I did a back up of the EFS partition before this.
Now, I'm having some weird issues when charging the phone while it's off. I noticed that I have a new charging animation and after a few seconds it disappears like the screen it's going to turn off but it never does!! It stays on a black/gray screen but is still on as you can see the brightness. It never turns off! Also, if I unplugged the phone and hit the power button the screen turns on and the charging animation appears, like the phone was still charging :/
I need some help! I downloaded an alternative bootloader. What should I do? Should I flash the alternative bootloader and will this solve the problem?
thanks!!
ramicba said:
Hi Guys,
I recently unlocked the bootloader of my Optimus G (E987 flashed to E975) using Freegee (Downloaded from the market) and installed TWRP. I did a back up of the EFS partition before this.
Now, I'm having some weird issues when charging the phone while it's off. I noticed that I have a new charging animation and after a few seconds it disappears like the screen it's going to turn off but it never does!! It stays on a black/gray screen but is still on as you can see the brightness. It never turns off! Also, if I unplugged the phone and hit the power button the screen turns on and the charging animation appears, like the phone was still charging :/
I need some help! I downloaded an alternative bootloader. What should I do? Should I flash the alternative bootloader and will this solve the problem?
thanks!!
Click to expand...
Click to collapse
Do you selected MAKO bootloader, or STOCK bootloader?
I will explain quickly. STOCK bootloader had that problem, you cant charge your phone when its off. We have the MAKO alternative because it work fine, i mean you can charge it off.
PD: im from Argentina too:good:
nch26 said:
Do you selected MAKO bootloader, or STOCK bootloader?
I will explain quickly. STOCK bootloader had that problem, you cant charge your phone when its off. We have the MAKO alternative because it work fine, i mean you can charge it off.
PD: im from Argentina too:good:
Click to expand...
Click to collapse
Hi!! I installed the STOCK bootloader :/ So what's the solution? What can I do now to fix this? Should I "unblock" the bootloader again installing MAKO bootloader? I also downloaded, from the forum, an alternative bootloader (cwm-geeb-4-3-z20i-bootloader_only.zip).
By the way, I didn't see an option to send you a private message!
Muchas gracias!!!
it is better not to unlock bootloader .. it causing problems only... on LGs ..
ramicba said:
Hi!! I installed the STOCK bootloader :/ So what's the solution? What can I do now to fix this? Should I "unblock" the bootloader again installing MAKO bootloader? I also downloaded, from the forum, an alternative bootloader (cwm-geeb-4-3-z20i-bootloader_only.zip).
By the way, I didn't see an option to send you a private message!
Muchas gracias!!!
Click to expand...
Click to collapse
You can flash the bootloader that you download, i did this one time. In my case when flash bootloader from recovery no problems. you should dont have problems.
Maybe i dont have the option active?
GalaxySIIII said:
it is better not to unlock bootloader .. it causing problems only... on LGs ..
Click to expand...
Click to collapse
I did it cause I needed to solve the baseband issue after flashing my E987 to E975...Freegee has an option to "re-lock" I think it's to install stock recovery and bootloader but I don't have any of those, do you know where I could get them?
nch26 said:
You can flash the bootloader that you download, i did this one time. In my case when flash bootloader from recovery no problems. you should dont have problems.
Maybe i dont have the option active?
Click to expand...
Click to collapse
I installed the bootloader that you told me (wm-geeb-4-3-z20i-bootloader_only.zip) but I'm still having the same problem, I don't know what else to do to solve this. I wouldn't want to go back to the stock ROM, I like this one =/
The only problem is that the screen doesn't completely turns off while charging the phone when it's off.
ramicba said:
I did it cause I needed to solve the baseband issue after flashing my E987 to E975...Freegee has an option to "re-lock" I think it's to install stock recovery and bootloader but I don't have any of those, do you know where I could get them?
I installed the bootloader that you told me (wm-geeb-4-3-z20i-bootloader_only.zip) but I'm still having the same problem, I don't know what else to do to solve this. I wouldn't want to go back to the stock ROM, I like this one =/
The only problem is that the screen doesn't completely turns off while charging the phone when it's off.
Click to expand...
Click to collapse
Is not a ROM problem, is a bootloader problem. With mako i dont have this issue. But i hear that some people have issues charging with phone off.
with any bootloader. simple charge it with phone on, or restore bootloader backup and go to stock rom...
nch26 said:
Is not a ROM problem, is a bootloader problem. With mako i dont have this issue. But i hear that some people have issues charging with phone off.
with any bootloader. simple charge it with phone on, or restore bootloader backup and go to stock rom...
Click to expand...
Click to collapse
hmmm... i install mahdi rom ... and i don't notice this issue. than it's not just a bootloader prob i think.anyway!
Hey, i flashed CM11 about half a year ago. The last Saturday (20/12), it started to go in an infinite loop. First it could boot in apps, but then it crashes all the time. So What I 've tried:
Reset factory data/davlik/cache
Flashing another rom via Recovery
Bring back to stock via bootloader (cmd+fastboot)
Downloading mode (ODIN)
OmapFlash
Nothing made even a little change to my phone. It boots in the same OS, and it crashes all the time. It's like its in a readonly mode. It's like it has the program for PC Deep Freeze, that restores your phone to its first condition in every simple reboot. Can you help me plz?
dannaros said:
Hey, i flashed CM11 about half a year ago. The last Saturday (20/12), it started to go in an infinite loop. First it could boot in apps, but then it crashes all the time. So What I 've tried:
Reset factory data/davlik/cache
Flashing another rom via Recovery
Bring back to stock via bootloader (cmd+fastboot)
Downloading mode (ODIN)
OmapFlash
Nothing made even a little change to my phone. It boots in the same OS, and it crashes all the time. It's like its in a readonly mode. It's like it has the program for PC Deep Freeze, that restores your phone to its first condition in every simple reboot. Can you help me plz?
Click to expand...
Click to collapse
Forget about #1 and #2 in your list.
In #3, what happens when you try to flash the images?
efrant said:
Forget about #1 and #2 in your list.
In #3, what happens when you try to flash the images?
Click to expand...
Click to collapse
Nothing, still the same CyanogenMod OS. Even if I run oem lock, after rebooting to bootloader it will shown as unlocked again.
dannaros said:
Nothing, still the same CyanogenMod OS. Even if I run oem lock, after rebooting to bootloader it will shown as unlocked again.
Click to expand...
Click to collapse
If the images appear to flash properly in fastboot, but you are still on the same ROM, then I would suspect your NAND is toast.
efrant said:
If the images appear to flash properly in fastboot, but you are still on the same ROM, then I would suspect your NAND is toast.
Click to expand...
Click to collapse
What is NAND. Is NAND phone's internal memory? And what can I do now? Is it a solution or is it a hardware issue? Thank you for your help btw
dannaros said:
What is NAND. Is NAND phone's internal memory? And what can I do now? Is it a solution or is it a hardware issue? Thank you for your help btw
Click to expand...
Click to collapse
Yes, it's your devices internal flash memory. It looks like there is something wrong with it. (Others have had similar issues in the past.) So, yes, it looks like it's a hardware issue and there's nothing you can do yourself to fix it.
efrant said:
Yes, it's your devices internal flash memory. It looks like there is something wrong with it. (Others have had similar issues in the past.) So, yes, it looks like it's a hardware issue and there's nothing you can do yourself to fix it.
Click to expand...
Click to collapse
Ok mate. thank you so much. have a nice happy new year for you and your beloved ones. Plz reply me to my pm.
Hello all,
This is just the continuation of my last post - http://forum.xda-developers.com/galaxy-s4-tmobile/help/s4-acting-buggy-using-roms-t3306395
I was recommended to use Odin to flash the original 4.4.4 firmware, so I did just that and my phone worked for a few hours. But then, it would freeze again and force reboot. Then it would get stuck in bootloop and I would have to take the battery out to reset it. When this finally loaded, I wouldn't get any service and told me to insert an SIM card even though there was one already inserted. A few moments later it would crash again.
After this, I flashed the 4.4.2 firmware through Odin, and the same things kept happening. I'd only be able to use my phone normally for about an hour or so and then the cycle of crashing and bootlooping would start again.
I noticed that whenever I did a factory reset and wiped all data, the phone would work normally for a short period of time. But as usual, a bit later it will freeze.
Is this just a hardware problem with my phone and practically unsolvable, or is there a fix to this?
Any help will be appreciated, thank you.
Did you restore any data or apps after flashing the fresh firmware?
lumin30 said:
Did you restore any data or apps after flashing the fresh firmware?
Click to expand...
Click to collapse
Nope, I just went to the store to get a couple of my most used apps like WhatsApp, Twitter, and Soundcloud. I didn't restore anything else
Did you take out the micro SD card as well? Do you get messages when the device crashes?
Sent from my SM-G920T using Tapatalk
serio22 said:
Did you take out the micro SD card as well? Do you get messages when the device crashes?
Sent from my SM-G920T using Tapatalk
Click to expand...
Click to collapse
Yup, I tried rebooting without my SD card as well, same problem occurs. And usually what happens is it'll boot up, but becomes unresponsive as soon as I touch it. It will then reboot by itself and go into a bootloop. In the rare occasion I am able to bypass my lock screen after booting, I get a com.process is not responding and my background is all black. This too will eventually freeze and enter a bootloop.
fmaster12 said:
Hello all,
This is just the continuation of my last post - http://forum.xda-developers.com/galaxy-s4-tmobile/help/s4-acting-buggy-using-roms-t3306395
I was recommended to use Odin to flash the original 4.4.4 firmware, so I did just that and my phone worked for a few hours. But then, it would freeze again and force reboot. Then it would get stuck in bootloop and I would have to take the battery out to reset it. When this finally loaded, I wouldn't get any service and told me to insert an SIM card even though there was one already inserted. A few moments later it would crash again.
After this, I flashed the 4.4.2 firmware through Odin, and the same things kept happening. I'd only be able to use my phone normally for about an hour or so and then the cycle of crashing and bootlooping would start again.
I noticed that whenever I did a factory reset and wiped all data, the phone would work normally for a short period of time. But as usual, a bit later it will freeze.
Is this just a hardware problem with my phone and practically unsolvable, or is there a fix to this?
Any help will be appreciated, thank you.
Click to expand...
Click to collapse
i am also have some problem.
I am in a position where the phone freezes and bootloops but I can flash stuff on fastboot, so I flashed entire stock image and imma gonna RMA. Should I lock the bootloader also or send it like that? could they give problems?
Considering that you can harm your hardware modifying the ROM, overcloking,etc... I would be better to block it so they can't say that your damaged it.
Does it happens a lot?
I just sent mine in today for RMA. Fingerprint scanner gave up the ghost 10 days after Google's warranty period. Since I had to factory reset anyway I just flashed everything stock in fastboot and then locked the bootloader. I can't think of any reason not to if you're flashing stock anyway.
Paco_LUE said:
Considering that you can harm your hardware modifying the ROM, overcloking,etc... I would be better to block it so they can't say that your damaged it.
Does it happens a lot?
Click to expand...
Click to collapse
jgummeson said:
I just sent mine in today for RMA. Fingerprint scanner gave up the ghost 10 days after Google's warranty period. Since I had to factory reset anyway I just flashed everything stock in fastboot and then locked the bootloader. I can't think of any reason not to if you're flashing stock anyway.
Click to expand...
Click to collapse
The problem is that even if I flashed everything stock, if while locking it it freezes or restarts like randomly hapens and then something goes wrong, and the phone shows the red screen on bot and doesn't boot, I won't be able to do anything fron that point since I won't be able to boot to change the allow oem unlocking option in settings. And I don't know what they can say with that.
I mean, after a problem I had due to EFS corruption bug that TWRP 3.0.2-1 had, in some point I reflashed the entire rom via a total OTA, and after that, with everything stock, and the bootloader unlocked, it didn't show the orange unlocking screen, but shown the red one!!!!!! (which is something impossible to happen if we follow the diagram from google itself, but it did..), so I am not sure if even after flashing the entire stock something like this may happen .
Thanks a lot!
RusherDude said:
The problem is that even if I flashed everything stock, if while locking it it freezes or restarts like randomly hapens and then something goes wrong, and the phone shows the red screen on bot and doesn't boot, I won't be able to do anything fron that point since I won't be able to boot to change the allow oem unlocking option in settings. And I don't know what they can say with that.
I mean, after a problem I had due to EFS corruption bug that TWRP 3.0.2-1 had, in some point I reflashed the entire rom via a total OTA, and after that, with everything stock, and the bootloader unlocked, it didn't show the orange unlocking screen, but shown the red one!!!!!! (which is something impossible to happen if we follow the diagram from google itself, but it did..), so I am not sure if even after flashing the entire stock something like this may happen .
Thanks a lot!
Click to expand...
Click to collapse
Are you sure that you used a stock imagen? Original bootloader as well?
Paco_LUE said:
Are you sure that you used a stock imagen? Original bootloader as well?
Click to expand...
Click to collapse
Yep, it was after flashing an stock total OTA on stock recovery. So all partitions were signed by google, and a red warning appeared instead of the bootloader warning one, which if you follow android developers guide for booting sequence, it says that this can't happen, but it did and got me really scared lol.
Even that has bugs, and I experienced that one lol..
So I was using my phone normally yesterday, until it shuts down randomly while using the camera. So I restarted it, but it still restarted as I got to my home screen. So I said to myself that there must be something went wrong in the rom that I am using (which is LOS 14.1), but I've got a backup before **** happened, not to worry, after I restored it though, IT STILL RESTARTED, but the weird part is, It doesn't restart if it is charging. So I wondered maybe the battery has given up, but in the TWRP, it doesn't restart even unplugged?
Things that I had tried:
1. Tried a new rom (this time using BORETS ROM), still restarts when unplugged.
2. Ran the backup again, still no change.
3.Drained my battery in TWRP, charged it up to 100%, still restarts.
Also, when I boot up my phone without a USB cable plugged in, It restarts when loading the main rom (the rom's splash screen, not the main splash screen), PLEASE HELP ME.
Xnin47 said:
So I was using my phone normally yesterday, until it shuts down randomly while using the camera. So I restarted it, but it still restarted as I got to my home screen. So I said to myself that there must be something went wrong in the rom that I am using (which is LOS 14.1), but I've got a backup before **** happened, not to worry, after I restored it though, IT STILL RESTARTED, but the weird part is, It doesn't restart if it is charging. So I wondered maybe the battery has given up, but in the TWRP, it doesn't restart even unplugged?
Things that I had tried:
1. Tried a new rom (this time using BORETS ROM), still restarts when unplugged.
2. Ran the backup again, still no change.
3.Drained my battery in TWRP, charged it up to 100%, still restarts.
Also, when I boot up my phone without a USB cable plugged in, It restarts when loading the main rom (the rom's splash screen, not the main splash screen), PLEASE HELP ME.
Click to expand...
Click to collapse
Hello ..a few questions.
What phone is it ?
What number TWRP do you have ? 3.0.X.X
X= ?
timbernot said:
Hello ..a few questions.
What phone is it ?
What number TWRP do you have ? 3.0.X.X
X= ?
Click to expand...
Click to collapse
It's a ZE551ML and I currently have returned to stock boot loader and recovery image, but the time that it happened I was on TWRP 3.0.3-M4. Why'd you ask?
Xnin47 said:
It's a ZE551ML and I currently have returned to stock boot loader and recovery image, but the time that it happened I was on TWRP 3.0.3-M4. Why'd you ask?
Click to expand...
Click to collapse
Thought you might have older TWRP - no worries
Alls OK now then ?
If it is ? Put **[ solved ]** in title :good:
timbernot said:
Thought you might have older TWRP - no worries
Alls OK now then ?
If it is ? Put **[ solved ]** in title :good:
Click to expand...
Click to collapse
Unfortunately, No it's still not okay.
Xnin47 said:
Unfortunately, No it's still not okay.
Click to expand...
Click to collapse
Have you got IFWI version 0094.0183 in bootloader and M stock recovery ?
If you have , you can use my downgrade from M to LP via SD card from my signature below
If, when back in LP .196 -- You still have the same problem , you will be looking at an hardware and not software problem :good:
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
timbernot said:
Have you got IFWI version 0094.0183 in bootloader and M stock recovery ?
If you have , you can use my downgrade from M to LP via SD card from my signature below
If, when back in LP .196 -- You still have the same problem , you will be looking at an hardware and not software problem :good:
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Click to expand...
Click to collapse
Today I flashed 2.15.40.13 on raw using Asus Flash Tool, still no luck , I guess it's a hardware problem huh?
Xnin47 said:
Today I flashed 2.15.40.13 on raw using Asus Flash Tool, still no luck , I guess it's a hardware problem huh?
Click to expand...
Click to collapse
Seems like you didn't need any help.
timbernot said:
Seems like you didn't need any help.
Click to expand...
Click to collapse
The problem just seems very weird to be a hardware problem , So, again, after charging my phone up to 100 percent, booted it up to Android and then unplugged it, and I had about a minute of activity now before it shuts down. Again in recovery or boot loader, it never shuts down.
Do me a favour , test with cable attached to phone but detached from charger to rule out USB socket , cable etc:good:
timbernot said:
Do me a favour , test with cable attached to phone but detached from charger to rule out USB socket , cable etc:good:
Click to expand...
Click to collapse
Tried it now, still shuts down.
Xnin47 said:
Tried it now, still shuts down.
Click to expand...
Click to collapse
If its out of warranty , i would first check all connections inside phone ,
it could be battery
it could be main board or usb board.
If it were battery though , it should shut down connected to lower amp pc usb2.
Not much you can do really apart from above, usb boards are cheap`sh to buy, maybe worth the gamble ? Obviously if connections dont fix before ditching if main board. Try a discon of all connections and reconnect before ditching
I have the EXACTLY same problem.
Did you solved?
Guys, I know it's been a long time this question was asked, but I'm having the exact same problem since a week.
@owenreilly @Xnin47 any luck on solving it?
Thanks a lot!
neves4 said:
Guys, I know it's been a long time this question was asked, but I'm having the exact same problem since a week.
@owenreilly @Xnin47 any luck on solving it?
Thanks a lot!
Click to expand...
Click to collapse
Wow this is an old problem. Nope, I didn't fix it, instead I was back on my Galaxy Alpha until I moved on to newer phones. I believe the problem though was the battery, so if you want, you can replace that. Sorry for the late reply bro!
Xnin47 said:
Wow this is an old problem. Nope, I didn't fix it, instead I was back on my Galaxy Alpha until I moved on to newer phones. I believe the problem though was the battery, so if you want, you can replace that. Sorry for the late reply bro!
Click to expand...
Click to collapse
Hey dude! I've replaced my battery 3 weeks ago based on a Brazilian forum and it was, indeed, the culprit haha. Now everything is back on track again.
Thanks a lot for the answer