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?
Related
So basically this rom is awesome but it had only one problem. When I plugged my phone in the charger while it was turned off, it bootlooped until I restarted with the cable off. It was no big deal and nothing bad ever came out of it.
Yesterday my batter ran out while I was asleep and when I woke up it was already turned off. I, absentmindly, tried to turn it on, LG Logo, off again. Did it one more time, nothing happened, realized it's out of battery. Plugged in charger, try to turn it off/on, usual bootloop happens. Say ok and proceed with what I always did, phone gets past LG Logo, goes into SlimLP boot animation and for the first it has just stayed there. No restarts, just endless loading. Longest i Left it on to load was about 45 minutes. Never got back on.
Apart from that, I think that for some reason my recovery got uninstalled somehow, by itself, a few weeks ago. I only noticed this because before, when I wanted to get into recovery, I pressed the usual buttons and it went straight into TWRP. Now the same buttons take me to the "Factory reset screen". I know that everyone says to just go ahead and press power, but I am afraid, since I am not sure if TWRP is still functioning. This happened to me another time on the same phone, and when I confirmed the factory reset, it factory resetted.
My problem here is that I want to get my music and photos. I'm only able to enter that factory reset screen and download mode. Can I "flash" twrp safely from download mode? Should I use Flash Tool 2014 and Normal flash(which says it keeps the data) a stock g2 rom? Can I mount my phone to the computer in download mode to copy my files? I want the most risk-free approach.
Thanks in advance.
giorgos123 said:
So basically this rom is awesome but it had only one problem. When I plugged my phone in the charger while it was turned off, it bootlooped until I restarted with the cable off. It was no big deal and nothing bad ever came out of it.
Yesterday my batter ran out while I was asleep and when I woke up it was already turned off. I, absentmindly, tried to turn it on, LG Logo, off again. Did it one more time, nothing happened, realized it's out of battery. Plugged in charger, try to turn it off/on, usual bootloop happens. Say ok and proceed with what I always did, phone gets past LG Logo, goes into SlimLP boot animation and for the first it has just stayed there. No restarts, just endless loading. Longest i Left it on to load was about 45 minutes. Never got back on.
Apart from that, I think that for some reason my recovery got uninstalled somehow, by itself, a few weeks ago. I only noticed this because before, when I wanted to get into recovery, I pressed the usual buttons and it went straight into TWRP. Now the same buttons take me to the "Factory reset screen". I know that everyone says to just go ahead and press power, but I am afraid, since I am not sure if TWRP is still functioning. This happened to me another time on the same phone, and when I confirmed the factory reset, it factory resetted.
My problem here is that I want to get my music and photos. I'm only able to enter that factory reset screen and download mode. Can I "flash" twrp safely from download mode? Should I use Flash Tool 2014 and Normal flash(which says it keeps the data) a stock g2 rom? Can I mount my phone to the computer in download mode to copy my files? I want the most risk-free approach.
Thanks in advance.
Click to expand...
Click to collapse
Hi, first If you can enter download mode I think you can flash kdz (Kitkat) file to stock using Flash Tool 2014. But I had this problem once and the keep data flashing didn't work (stucked at 50%), I ended up flashed it with other option (erased all data).
2. You can try the "Factory reset" nice and easy.
I think you can't see files on the device unless you enter Twrp.
It's wise to backup your phone on the computer montly or so, thank you.
I went ahead and nuked my download mode using the SRK tools. Then got access to fastboot, through which I booted to twrp and then I could move my files. All's fine, flashed my ROM again and it's going better than ever.
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
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)
Please help! My S5 Neo was in a drawer for a few months after the LCD got smashed. I recently bought a new LCD assembly and connected it to make sure it worked before fitting and it was fine. However, the phone immediately started doing a software update but was interrupted after a few seconds as the battery was dead. Now the phone won't power up or boot into download mode or recovery. When I plug the phone in to its charger, the LED flashes red but nothing is displayed on the screen. I had a new battery for it and charged it in another device but still no joy. I've been messing around with old galaxy phones for a couple of years now, flashing custom ROM's etc, so I wanted to just re-flash a stock ROM into it but there's no way I know of performing this without getting the device into recovery or download mode. Does anyone have any ideas? The device is totally stock and hadn't even been rooted. I'm currently using an S4 Active running Lineage OS 17.1 so I'm not desperate for a phone, but I loved my S5 and really would like to get it up and running again. It never once had any problems.
I have an S5 with stock Samsung ROM which I rooted some years ago with Magisk and TWRP recovery. For the last few years it has only been used as an alarm clock and I have forgotten how I set it all up in the first place, in fact I had forgotten that I ever rooted it. Up until now it has been working fine but I wanted to give it to my 9 year old daughter to use, so I did a factory reset on it through the normal Android menu. After that the phone works but will only charge in Recovery, not when its off or when its booted normally. Same cable and charger that I have been using up until now and I also tried others but didn't make any difference.
When the phone is off and I plug in the charger,it vibrates, the battery symbol comes up for a second and it displays the message "set warranty bit: kernel" then the screen goes off. The charging LED does not come on. Then after about 10 sec it does the same thing again: vibrate, battery symbol, message, screen off and just keeps going round that loop but never charges. When the phone is booted in normal mode it doesn't seem to detect the charger at all, nothing happens. In Recovery it charges perfectly but its a bit inconvenient!
I tried restoring the last TWRP backup that I had which seemed to contain all the partitions but it hasn't made any difference to the charging problem. It seems the phone has power and CAN charge but is deciding not to. Any ideas please how I can get it back into operation?
Model: SM-G901F
Android 6.0.1
Kernel 3.10.40-9709634
Build MMB29M.G901FXXU1CRH1
Magisk 19.3
Magisk Manager 7.3.4
Magisk version is old but I have not attempted to update it yet in case that makes the situation worse.
spencetj said:
I have an S5 with stock Samsung ROM which I rooted some years ago with Magisk and TWRP recovery. For the last few years it has only been used as an alarm clock and I have forgotten how I set it all up in the first place, in fact I had forgotten that I ever rooted it. Up until now it has been working fine but I wanted to give it to my 9 year old daughter to use, so I did a factory reset on it through the normal Android menu. After that the phone works but will only charge in Recovery, not when its off or when its booted normally. Same cable and charger that I have been using up until now and I also tried others but didn't make any difference.
When the phone is off and I plug in the charger,it vibrates, the battery symbol comes up for a second and it displays the message "set warranty bit: kernel" then the screen goes off. The charging LED does not come on. Then after about 10 sec it does the same thing again: vibrate, battery symbol, message, screen off and just keeps going round that loop but never charges. When the phone is booted in normal mode it doesn't seem to detect the charger at all, nothing happens. In Recovery it charges perfectly but its a bit inconvenient!
I tried restoring the last TWRP backup that I had which seemed to contain all the partitions but it hasn't made any difference to the charging problem. It seems the phone has power and CAN charge but is deciding not to. Any ideas please how I can get it back into operation?
Model: SM-G901F
Android 6.0.1
Kernel 3.10.40-9709634
Build MMB29M.G901FXXU1CRH1
Magisk 19.3
Magisk Manager 7.3.4
Magisk version is old but I have not attempted to update it yet in case that makes the situation worse.
Click to expand...
Click to collapse
Never mind, I got it working with a different charger. Very strange. The first charger works fine with my Huawei P20, maybe too high power for the S5? Although I thought the device only draws the power it needs even if the charger is capable of more.