After root only sloooow charging - Samsung Galaxy A7 (2018) Questions & Answers

Hello everyone,
I installed successfully LinegeOS 17.1 with this instuctions on my Samsung Galaxy A7 (2018). It works fine, but after installing system (it is rooted too) the charging is sooo slow (It takes more than one hour to charge only 7-8 %). I tried same cable (that charged perfectlly before installing LineageOS) and some others, but without success.
I tried with installing Magisk-modules too:
1) Notzeetaa - It is same
2) Magisk Fast Charge Version Green - When I try to flash, in the step when I need to choose option with volume up or down, it only shows numbers 1,23,.... and I cannot do anything. When I restart, it shows in Magisk, that FCGreen module is installed, but the charging is same
Can someone suggest, what should I do?

Why you installed LineageOS 17.1, It is like Android 10. If it was for the interface just install the Lineage launcher.

Reinstall the original firmware via sammobile.

And unroot.

But what if I want to use this system and dont want to root? Do you know how to solve problem with charging or not?

Flash the official ROM. It was almost unnecessary to move on LineageOS.

Yes, but then I will lost TWRP?

Ofcourse, you will lost TWRP when you change ROMs, you will lost ROOT too.

Is there an option, that I install Android 10 and THEN TWRP (I want Android with TWRP)?

Yes, sure. Just install Android 10 and then, flas TWRP

Samarimama said:
Yes, sure. Just install Android 10 and then, flas TWRP
Click to expand...
Click to collapse
But is there an option, that I install permanently TWRP?

What do you mean ?

I know I can flash TWRP after installing Android 10, but is it possible to have TWRP for always? I mean, will I have both: system and TWRP-recovery?

I think no, because when I flashed LineageOS in my Tab E Lite, I can't go to TWRP anymore.

What is this now??? I had blue and black colours when I boot (I could see logo, but barely). I could go into system (Lineage), but I see things only in blue and black colour. NOW I DONT SEE ANYTHING. Can someone explain why is this happening and what can I do?

dev_33 said:
What is this now??? I had blue and black colours when I boot (I could see logo, but barely). I could go into system (Lineage), but I see things only in blue and black colour. NOW I DONT SEE ANYTHING. Can someone explain why is this happening and what can I do?
Click to expand...
Click to collapse
Failed flash.

Maybe you bricked your device, can you try again flashing the firmware ?

cmfCyangenModteam said:
Failed flash.
Click to expand...
Click to collapse
I dont understand. It worked perfectly, but now I see only black screen.

Samarimama said:
Maybe you bricked your device, can you try again flashing the firmware ?
Click to expand...
Click to collapse
I tried, but when I connect USB to my PC, PC detects it, but there is an error and I cannot see files from phone or do something with Odin.

Related

I had to install all the system after several flashs ! Help !

Hy friends,
I have problems.
So I have a nexus 5, and I flashed several times, to test cyanogenmod, to test the preview of Android M, to install kernel... Maybe more that 12 times.
And it's happen. My phone now won't turn on. When I charge it the red led twinkle several times and after nothing. I can go to the bootloader but when I want flash something nothing happen. On the cmd console it seems like the installation works well but in fact it's useless. Yesterday I tried and suceeded to install TWRP ! Furthermore my Nexus 5 can't turn on alone, when I flash the bootloader must turn off then turn on, my phone no, I had to press Volum Down + Power button.
So yes, now I have TWRP on my phone and the application shows me that my intern storage of my phone is empty, like completly empty.
So maybe I have the solution, I want a backup which is compatible with TWRP to install it on my phone !
Do you have other ideas or maybe my idea is a ****ing bull**** and my Nexus 5 is definetly dead :crying:
Thanks a lot !
xython said:
Hy friends,
I have problems.
So I have a nexus 5, and I flashed several times, to test cyanogenmod, to test the preview of Android M, to install kernel... Maybe more that 12 times.
And it's happen. My phone now won't turn on. When I charge it the red led twinkle several times and after nothing. I can go to the bootloader but when I want flash something nothing happen. On the cmd console it seems like the installation works well but in fact it's useless. Yesterday I tried and suceeded to install TWRP ! Furthermore my Nexus 5 can't turn on alone, when I flash the bootloader must turn off then turn on, my phone no, I had to press Volum Down + Power button.
So yes, now I have TWRP on my phone and the application shows me that my intern storage of my phone is empty, like completly empty.
So maybe I have the solution, I want a backup which is compatible with TWRP to install it on my phone !
Do you have other ideas or maybe my idea is a ****ing bull**** and my Nexus 5 is definetly dead :crying:
Thanks a lot !
Click to expand...
Click to collapse
1) Adb a twrp flashable rom to your internal.
2) Use OTG and usb stick
If the led flashes red when off and connected to a charger, the battery is cmpletely discharged. Leave it connected to the original charger and USB cable for a few hours.
wangdaning said:
1) Adb a twrp flashable rom to your internal.
2) Use OTG and usb stick
Click to expand...
Click to collapse
I used adb to put a twrp recovery in my phone and when I want to install it with twrp it's wrote : FAILED. Gonna be different with OTG and USB stick ?
xython said:
I used adb to put a twrp recovery in my phone and when I want to install it with twrp it's wrote : FAILED. Gonna be different with OTG and USB stick ?
Click to expand...
Click to collapse
You can adb push the zip (rom) to the phone and try fastboot boot (twrp.img) then use twrp to flash the rom on the phone.
If this does not work it seems you motherboard is fried.
If you have twrp and the otg cable, then put the rom on your usb stick and connect in twrp. Try flashing off the drive.
Again, I am getting the feeling this is hardware. Your memory or battery seem to be failing. It has nothing to do with prior flashing. My N5 has gone through way more than yours, and I am sure others have done more than me. We still have working phones.
Also consider the power button issue.
Try the steps though.
wangdaning said:
You can adb push the zip (rom) to the phone and try fastboot boot (twrp.img) then use twrp to flash the rom on the phone.
If this does not work it seems you motherboard is fried.
If you have twrp and the otg cable, then put the rom on your usb stick and connect in twrp. Try flashing off the drive.
Again, I am getting the feeling this is hardware. Your memory or battery seem to be failing. It has nothing to do with prior flashing. My N5 has gone through way more than yours, and I am sure others have done more than me. We still have working phones.
Also consider the power button issue.
Try the steps though.
Click to expand...
Click to collapse
Thanks !
Do you know where I can download a TWRP recovery for nexus 5 (hammerhead) ?
xython said:
Thanks !
Do you know where I can download a TWRP recovery for nexus 5 (hammerhead) ?
Click to expand...
Click to collapse
TWRP thread in original development.

My huawei ascend mate 7 was bricked when i try to root via twrp

my huawei mate 7 stuck in logo and not turn on when i root it , after that i have wipe t
data and it still not turn on, on the reboot it said '' No OS installed!!!
how to fix it, please help.
I already lost my data and files:crying::crying:
You need to flash your stock firmware via odin
Sent from my SM-N910V using Tapatalk
low user said:
my huawei mate 7 stuck in logo and not turn on when i root it , after that i have wipe t
data and it still not turn on, on the reboot it said '' No OS installed!!!
how to fix it, please help.
I already lost my data and files:crying::crying:
Click to expand...
Click to collapse
Ok, you already have TWRP installed on your phone. So you aren't exactly a newbie. What version of OS did you have installed before you broke the phone?
it is marshmallow, it is more bad, my phone not only stuck in logo now it still turn on and turn off itself and just show the logo and turn off.
sorry for my English.
CloudCompute said:
Ok, you already have TWRP installed on your phone. So you aren't exactly a newbie. What version of OS did you have installed before you broke the phone?
Click to expand...
Click to collapse
it is marshmallow, it is more bad, my phone not only stuck in logo now it still turn on and turn off itself and just show the logo and turn off.
sorry for my English.
low user said:
it is marshmallow, it is more bad, my phone not only stuck in logo now it still turn on and turn off itself and just show the logo and turn off.
sorry for my English.
Click to expand...
Click to collapse
Looks like you accidentally wiped the system partition. Did you already try keeping the 3 keys, vol up, vol down and power key pressed for 9 to 10 seconds to get into recovery mode?
i got myself in the same position to when trying to root.
if you are using this
http://forum.xda-developers.com/mate-7/development/tool-srk-tool-huawei-beta-02-20160501-t3369990
you can use that to restore back your stock bootloader. then rollback then only install back prefered rom.
in my case in got bootloop at b522. use the above batch file i restore stock bootloader. then rollback to b500 ( here it will still bootloop) then i flash back ( using dload in sdcard). it took 20 minutes for the phone to boot to system. lucky.
you have to use sdcard and computer to copy presered rom dload file.
root now works with the latest kingroot but beware the consequences created by kingroot
low user said:
it is marshmallow, it is more bad, my phone not only stuck in logo now it still turn on and turn off itself and just show the logo and turn off.
sorry for my English.
Click to expand...
Click to collapse
i still resolve this problem :
boot into twrp
plug your phone to PC : you can access to your sd card (intern)
copy update.zip (B514) to your sd card
on your phone clique install button TWrp and choose your update.zip und swipe
when done reboot
it's all
ahhl said:
root now works with the latest kingroot but beware the consequences created by kingroot
Click to expand...
Click to collapse
ONLY root by flash from TWRP.
Flashing from an app in the OS is not how to do it.
low user said:
my huawei mate 7 stuck in logo and not turn on when i root it , after that i have wipe t
data and it still not turn on, on the reboot it said '' No OS installed!!!
how to fix it, please help.
I already lost my data and files:crying::crying:
Click to expand...
Click to collapse
Bro, I think we have encountered a similar problem, although our current situation is now a bit different. Your's seem to be your system partition has been damaged, hence, the "no OS" message. For me, it's a stuck-at-the-logo situation. You can check it here in case you're interested... http://forum.xda-developers.com/mate-7/help/hard-bricked-mt-tl10-t3400467
Reading further, I see you're also stuck at the logo. Are you able to boot to recovery or BL?

Nexus 5 bootloop, stuck in Rom intro - Don't know how to connect it to my pc

First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:
Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw
Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked
ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great
It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.
hmm not a bad idea at all. Thank you!

Help me fix a bricked OPO :(

Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
try charging the phone for a few hours
se7enlyn said:
try charging the phone for a few hours
Click to expand...
Click to collapse
yeah, forgot to mention that. can't even charge it. when I plug it in it does the same. tries to turn on. shows the first splash screen and reboots doing the same again and again. doesnt even show the charging screen with chinese text and battery animation.
sounds like u need a new battery
ireaper4592 said:
sounds like u need a new battery
Click to expand...
Click to collapse
already tried that too. had a replacement battery laying around. changed it and still no luck.
@bmark240
help please
se7enlyn said:
@bmark240
help please
Click to expand...
Click to collapse
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
bmark240 said:
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
Click to expand...
Click to collapse
Yes, I have TWRP installed, but cant access it. Shows the TWRP splash screen and then reboots after like 10 seconds or so.
ADB does not see device. Only shows the device during that 10 second TWRP splash screen time, but even then no commands are effective and it just reboots.
Already tried holding down power button for few seconds. No luck.
I already installed all the possible drivers and media feature packs on my Windows 10. Still no luck.
And yes, I am running latest Windows 10 Pro x64.
And no, since I cant access Fastboot, I can not re-flash TWRP either.
kallum7 said:
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Gonna try that right now. Hopefully that will fix it.
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
THEVAN3D said:
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
Click to expand...
Click to collapse
because i had bricked my phone a few months ago and that is how i got my phone back using the colour os
THEVAN3D said:
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
Click to expand...
Click to collapse
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
FairuzOnn said:
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
Click to expand...
Click to collapse
Thanks, but I already fixed it.
i had it in the past for some reason too. Managed to fix it using the color os method. Carefully followed the steps until i could flash again. That was a year ago tohugh. There should be some thread around wit some all-in-one solution against bricks.

Only official binaries are allowed to be flashed

Hi,
The phone came back from service. Since then I can't take root.
When attempting a flash recovery it writes: Only official biranary are allowed to be flashed.
I've found many tutorials on how to fix this, but none works for me. Any advice please?
Hi,
I remember back a long time ago... It's red and appears on bootscreen on top? That was caused by something was changed through an OTA update and the try to root leads to that.
The thing that I've done was flashing a stock Oreo Firmware an then flashing twrp and root. I'm on custom ROM now and avoiding things like that.
Greetings.
Same thing happened to me when I flashed latest firmware for s8(pie may build).
So flash any oreo firmware and flash twrp. Or flash the first official pie firmware and flash twrp. then custom rom or root or whatever you want.
Note 9 only official released binaries are allowed to be flashed. FIX?
Akhil G said:
Same thing happened to me when I flashed latest firmware for s8(pie may build).
So flash any oreo firmware and flash twrp. Or flash the first official pie firmware and flash twrp. then custom rom or root or whatever you want.
Click to expand...
Click to collapse
Hi,
I tried to root my Note 9 (Exynos version, pie 9) using Max Lee's (HighOnAndoid) guide. The process seemed okay until I reached Dr Ketan script's last stage, when it got kind of stuck. It was loading for hours. Then I pressed Next, then Finished on DR. Ketan's script. Went into TWRP after this. Rebooted system. Then the phone loaded up normally, but wasn't rooted.
First 'root' trial of Note 9 was unsuccesful. Thought I could try again.
Problem was I couldn't get into 'Download Mode' anymore on my Note 9 !!
I could access 'Download Mode' obviously a few hours before this (when tried to root Note 9 the first time).Tried many variations of (Vol down + Bixby then insert USB) to succusflully access 'Download Mode', but no luck unfortunately.
So, I then accessed TWRP, selected WIPE option to Factory Settings.
Phone rebooded normally. Everything seemed normal (without the root). My goal is still to root my Note 9.
I restarted the phone, but after this last restart the note 9 never rebooted again.
I can only see in the upper left corner with REDletters "only official released binaries are allowed to be flashed".
How to FIX this problem?
Button techniques that did NOT work:
- Vol UP + power button.
- Vol up then power button for 10 seconds.
- Connected USB computer with Note 9. Pressed Vol UP then power buttong for 10 seconds.
How to FIX 'only official released binaries are allowed to be flashed' in the right upper corner in Red colour problem?
Help
pacal1983 said:
Hi,
I remember back a long time ago... It's red and appears on bootscreen on top? That was caused by something was changed through an OTA update and the try to root leads to that.
The thing that I've done was flashing a stock Oreo Firmware an then flashing twrp and root. I'm on custom ROM now and avoiding things like that.
Greetings.
Click to expand...
Click to collapse
So the same thing happened to me too while rooting my device so I tried to flash my device no matter what I do it won't flash sometimes the Odin gets stuck and sometimes it shows the process failed,I"be been trying to unbrick my phone from a week now but nothing seems to really work,so help if you can,thank you!

Categories

Resources