I am having a strange issue in my a6020a46(k5 plus). The first time i installed pixel rom from xda) the system booted up fine then after using for few hours i installed bean Gapps(mini version) but play store was unstable. It was never able to sign me up so i again fully removed everything for clean installation (dalvik/cache,data,system,cache). After installing OS i installed wifi+kernel fix and again bean Gapps which strangely didnt got installed unlike first time. Then problem began. When i rebooted it got struck into bootloop. I waited for 1 hrs but nothing happened. Then phone was not even going into recovery no matter what key combination i tried. It only got struck in penguine icon which kept restarting again and again. After many many attemps I was able to get it into recovery mode by pressing vol+,- and power button after immediately pluging it into charger. I again tried to install pixel but same problem occured. Then I tried installing other ROMs and it boots up but same pengiune icon is present there. I am not able to get rid of that icon nor able to boot up my phone with pixel OS. One more strange thing is happening and that is when phone is completely off and plugged into PC there is sound that notifies that ext device is connected and penguine icon comes in screen but when i power on my mobile then disconnecting sound comes and it never connects again untill i completely turn off my mobile and plug in USB. So summerising it here-
1) Pixel OS (no gapps+wifi,kernel fix) installed on 1st attempt
2)open gapps are not compatible so installed bean gapps mini version but play store was unstable+not able to sign in
3)did clean install but beanGapps didnt installed,errors were present. Installed wifi+kernel fix(by mistake did it twice). Booted and it got into bootloop
4)when device is off and connect via usb penguin icon pops up and sound of device connected play. when i switch on device usb disconnected sound plays and never connects again untill mobile is completely switched off again
5)installing other roms didnt removed penguin icon. other roms get installed but when tried to go in recovery mode it get struck into pengin icon(doesnt proceed until turned off and hold power and vol+,- button and immediately connected to power supply)
6neither pixel OS nor beangapps are able to get installed again. Bootloop (gapps ending with error 1)
I hope i can find answers soon. Thanks
Related
So i recently tried to upgrade my phones kernel and applied the aurora ics 4.1 update1a. The installing seemed fine, no errors so I pressed reboot now on my cwm (from the phones reboot recovery mode), but then it happened, the huawei logo appears and it doesn't go further than that. Tried many methods like removing the battery and running with usb, without battery and on usb, on battery and usb but non worked. If i leave it up a while, I press the power button again and then it turns off. So basically it won't boot further than the huawei start-up logo. Help ?
The phone random installed 2.3.5 on its own, so there the problem is solved.
I might have bricked my LG G2.
Here is everything I did:
-I rooted the phone with the IO root kit
-wanted to installed a recovery so I installed TWRP manager
-applied SD card patch
-tried to install recovery with TWRP manager several times but app always crashed
-installed SDK on the PC
-started adb and executed "adb reboot bootloader"
the phone got a backlight screen and hasnt been reacting so far.
When I held the power button the screen went black but sometimes the backlight appeard again. I don't know how to reproduce the backlight though.
adb can't detect the phone when connected to the PC.
As soon as I plug it in dozens of Partitions show up. Windows show an error message for each of these partitions. It says I have to format the volumes to use them.
After testing I realized that everytime i long-press the power button for a few seconds the windows errors start popping up.
When i long pressed the power button for 30+ seconds to completely shut it down the notification LED started blinking red 8 times in roughly second intervals. then there was a short break and the 8 blinks repeated.
Thank you for all help, it would suck to have a 1 day old phone broke...
You probably chose the wrong device in TWRP Manager. Choosing the wrong device can easily lead to a brick because TWRP Manager may attempt to flash to the wrong partition. The G2 does not have a TWRP Manager flash available due to loki, so you couldn't have chosen the right device.
Almost have the same problem... the only difference is my black screen is blinking continuously while it is connected to the mac... Seems like it tries to boot but gets blocked and retries in a loop. Tried around now for two evenings without any progress...
Anybody who can help?
Tried to install a custom ROM on my old N4 via Toolkit but got a bootloop on the Nitrogen logo. Right after the screen the phone would turn off. So, i rolled back to stock rom, unrooted and everything but now it seems the problem its even worse: the boot doesnt go past the Google logo. When the phone is charging i can access the recovery and even boot into Android. Off the charge it looks like i cant do nothing other than go to fastboot. If i choose the recovery option the phone turn itself off. I tried to install other ROM via TWRP when charging, but right after 2 seconds after the process begins, the phone turns off.
I think it may be a battery problem, but i wanna make sure it is so i dont waste money.
Thanks
Pwoper said:
Tried to install a custom ROM on my old N4 via Toolkit but got a bootloop on the Nitrogen logo. Right after the screen the phone would turn off. So, i rolled back to stock rom, unrooted and everything but now it seems the problem its even worse: the boot doesnt go past the Google logo. When the phone is charging i can access the recovery and even boot into Android. Off the charge it looks like i cant do nothing other than go to fastboot. If i choose the recovery option the phone turn itself off. I tried to install other ROM via TWRP when charging, but right after 2 seconds after the process begins, the phone turns off.
I think it may be a battery problem, but i wanna make sure it is so i dont waste money.
Thanks
Click to expand...
Click to collapse
hi buddy, problem is also happend to me, unfortunatly its not a software issue , its a battery problem, and its only fix with changing battery or you could turn on airplane mode (to turn off radio and only in custom rom) and keep using the phone offline.
Hello friends, I have a similar problem with my nexus 4.
I can use the device well if it is connected to a USB or plug. (If the device isn't connected, this turns off). But I can use TWRP without problems (works without connect to a USB or plug), I can install ROMS until finish, but when I want to start the system, only stuck on Google Logo and the device turns off (I tried to start the device but just stuck in Google Logo and turns off again) But if it is connected to a USB or plug works well without problems.
I tried to install all STOCK roms too but only work well when the device is connected. I think that isn't a battery problem because I can use TWRP (without connect to a usb or plug) and install every rom.:crying:
Someone would like to help me. Thanks a lot.
Angel Hyerald said:
Hello friends, I have a similar problem with my nexus 4.
I can use the device well if it is connected to a USB or plug. (If the device isn't connected, this turns off). But I can use TWRP without problems (works without connect to a USB or plug), I can install ROMS until finish, but when I want to start the system, only stuck on Google Logo and the device turns off (I tried to start the device but just stuck in Google Logo and turns off again) But if it is connected to a USB or plug works well without problems.
I tried to install all STOCK roms too but only work well when the device is connected. I think that isn't a battery problem because I can use TWRP (without connect to a usb or plug) and install every rom.:crying:
Someone would like to help me. Thanks a lot.
Click to expand...
Click to collapse
i told just above your post,that is a battery problem and only fixes with changing battery, the reason you can use twrp is that the voltage needed for boot phone in recovery mode is less than for booting the whole system with apps and radio functions
So, my G4 Plus got itself bricked out of thin air. I got it last year , unlocked it ages ago, tried some ROMs but decided to go back to stock+ because of pesky camera problems.
Earlier today i was using it normally when it froze and a long vibration started. With no other options I made a hard reboot and it started up again, only it didn't... The boot animation came out all choppy before rebooting itself again. Sometimes it lasted longer, sometimes a bit shorter but it never fully booted up again. Back home I booted into TWRP, flashed cache/dalvik, nothing. It DID get to a full "G" logo, then rebooted itself again. Got a ROM into the SD card, started flashing, froze, reboot again. Tried formatting everything, same thing, froze, reboot.
Just about the only things I can do with it are boot to TWRP and do anything that doesn't involve storage (so pretty much useless) and bootloader.
I also tried just about everything in my power to flash it on ADB/fastboot, but windows itself won't recognize the thing. All sorts of drivers, command lines, windows test mode (for driver certificate shenanigans), nothing worked. I even tried the same on a netbook with win7 since my desktop doesn't have a single USB 2.0 and I heard ADB has trouble with 3.0, nothing again. It doesn't recognize the device at all. They do recognize my girlfriend's G5 by the way, but seem to want nothing to do with my crippled-down-to-bootloader G4+.
I need some help guys, any clues?
Remember:
-Not your everyday bootloop
-Stuck with bootloader and limited usage of TWRP (i can copy files from SD to Internal with no problems)
-Neither Win10 with USB3.0s nor Win7 with USB2.0s recognize the phone at all, at least in this state (every driver out there already installed in every order)
I used to have a Pixel 5 phone, which unfortunately was run by a truck and now I am stuck with an old Samsung Galaxy S7 Edge phone. I have decided yesterday to install Pixel Experience on it and it all went fine. I have unlocked the OEM, enabled USB debugging, installed the latest version of TWRP with heimdall, and sideloaded the Android 11 Pixel Experience Plus ROM.
I had done a full wipe of the phone before doing it, including the system, etc. I have then recovered from the backup from my Pixel, and it installed all apps. Then I saw that there is a new version of the Pixel Experience, installed it, and plugged it into the charger and I woke up at the Google logo. I disconnected it from the charger and the Google logo was still there, it took me a couple of minutes to switch it off while holding continuously the power button.
I tried to go into recovery or download mode without any success. Then I have connected it to the charger again and I saw the battery indication with lightning inside, but normally it also shows you the battery percentages but this time, it didn't. I have then tried to connect to my PC, thank God this time, it booted straight into recovery. I have tried to sideload again the ROM, and this time, it worked till the end, but then I was unable to slide the slider to unlock it and restart the phone. Then switched it off and tried once again to sideload it, this time the phone died at half of the sideload. I am completely desperate now. Am I doing something wrong?