Recently my display was cracked, so I changed it. This led to another issue, where my battery popped out. All this should be solved now, although the backside camera is off (and probably will stay that way)
During the process, I ended up with updated software - now 6.0.1 build 23.5.A.0.570.
My bootloader is unlocked, however the software not rooted.
When I try to enter the Fastboot part of rooting (tried the VolUp+USB, ADB commands, Kingo (even directly from phone)), I get stuck. Blue LED is on, but screen is black, and the device is not accessible. Although I hear Windows (10) making sounds like when a device connects, it doesn't show up in any application.
Any ideas? Thanks for help.
---
Z3C, D5803, 6.0.1 build 23.5.A.0.570, Windows 10
Related
Hi,
a couple of days ago I falshed the CM 10.1.3 on the 4X. The phone is my brothers, so what is written under *1.* is what he told me. There are two problems with lockscreen:
1. (more major) This happened three times now; the phone cannot be unlocked with the power button, so it has to be turned off and on to be usable again. It seems to be random.
2. When the phone is woken on lock screen and unactive for a couple seconds, the screen should turn off by itself (it's set to turn off after 5 seconds in settings). But it doesn't, it just stay with the screen on indefinitely.
I can think of two things right now that are possibly a problem, but it's totally random brainstorming on my side:
1. When I unlocked the bootloader, I didn't use the "adb reboot oem-unlock" (I found out about that when I already unlocked it), instead I used "adb reboot bootloader" and "fastboot oem unlock". The bootloader is shown as unlocked either way, but here is says that that was not the right procedure, so I just thought that it might have something to do with it.
2. My brother has Smart RAM Booster installed. He had it installed on stock ROM too. It seems very unlikely to me that this could be a problem, but as I said, I'm just throwing stuff out there.
Hopefully someone will know the solution...
Solution
Ok, at the moment is seems that the problem really was in Smart RAM Booster.
I'll update if it turns out I'm wrong.
Hi guys,
My phone is in a permanent state of rebooting. I have searched these forums and other websites, but none of the solutions I found apply to my situation. I am going to provide as many details as I can here, even if they seem irrelevant.
My phone when it crashed
Sony Xperia V, stock firmware 9.2.a.1.210. (Which is the second latest. Couldn't get latest because neither Sony PC Companion or Update App found updates. This was BEFORE rooting.)
Rooted this morning using Towelroot.
(EDIT) Then I installed latest version of SuperSU.
Unless Towelroot somehow unlocks bootloader, I have a locked bootloader.
Deleted some pre-installed apps (which is why I rooted in the first place). Using Clean Master, I removed:
Google Play Movies
Google Play Books
Google Play Magazines
Sony Select
Sony Music Unlimited
Sony Xperia Link (Not sure about name. Used to view stuff like messages on other devices. Purple icon.)
I think that is all. I'm pretty sure I didn't remove anything vital. (My knowledge of Android is limited, and so I didn't go on a killing spree.)
Using Xperia Smart Connect, (I decided to try it after all), I set up an event. (When connecting to my TomTom Go, switch off Wifi. Afterwards, Switch on Wifi. The TomTom was turned off.)
Everything was fine after that.
The crash
Later on, I wanted to take a picture using the stock app. The app launched and worked for a few seconds, displaying what the camera registered. Then, the screen froze. After some time, I tried turning off my phone, to no avail. So I removed the battery. Re-inserted battery, pressed power button. Since then, my phone keeps on rebooting.
What happens exactly
After I insert the battery and press the power button, the phone vibrates and seems to boot normally. I get the colorful boot animation, followed by the lock screen. A lot of systems seem to be functioning correctly:
The lock screen looks normal. It displays the background I have set (from the stock Winter theme, I think) and shows the authentication dialog (more on that later).
The displayed time was correct after the first few boots, before I removed the battery for longer than a few seconds. After that, it was wrong a couple of times, before getting it right again a few boots later.
Other icons being shown in the status bar: Bluetooth (grayed out, which is normal if there's no connected device), no SIM card, no network, battery status (correct) and Wifi (best reception with constant up and down arrows).
The notification LED works. (Changes with battery status.)
"Battery almost empty" sound when applicable.
My phone never registers any input on the touch screen, save for one time, when it registered the first digit of my PIN code. After a while of displaying the lock screen, the whole screen turns a certain color (I've seen different colors on different occasions: red, purple, ...) like some kind of color filter is being applied. (The image is visible, but in one color.) After, that it fades into black and reboots.
What I have tried
Charging the phone for about an hour. The power led is orange when charging, meaning the battery has a decent amount of juice.
Removed the battery several times (one time for over fifty minutes). After I re-insert it, I need to press power button to get it to boot, which is of course normal. (As opposed another thread I've read, where the phone would boot as soon as the battery was inserted.)
Connecting to PC using USB cable and Sony PC Companion (SPC). SPC can't connect, most likely because the phone reboots before it can finish detection process.
Tried a forced reboot by pressing and holding power+volume up. Has no effect.
After a few reboots, I removed SIM and SD cards. The only effect that had: instead of the enter PIN code dialog, I get the "connect the dots" dialog. (Which makes sense.) No input is being registered. The pattern (dots) used to be my secondary authentication method, the primary being facial recognition. My phone doesn't seem to initiate facial recognition.
Let it reboot repeatedly. I estimate it has rebooted 15-20 times now.
On flashing
If flashing is my only option, I want to try Cyanogenmod instead of Sony firmware. I'd rather not flash at all, though, since I have no experience. All of my data has been backed up, so an internal wipe is no deal breaker.
If I do have other options, I'd prefer the quickest and simplest method of getting my phone operational. Provided there is one...
Phone is acting very irregular. Was able to unlock lockscreen using dot pattern twice, but froze after loading some home screen elements. Didn't get past lock screen on other occasions.
After crashing, sometimes forgot battery level. Claimed almost empty while almost full seconds before that.
Etc etc.
So! Want to flash to Cyanogenmod using this guide.
Downloaded and installed ADB here.
Flashtool drivers here. Installed following drivers from package:
Flashmode Drivers
Fastboot Drivers
Common drivers Blue3.0 board (Xperia V, T, TL, ...)
And a bunch of device specific drivers, since Xperia V wasn't literally listed. ("Xperia VL" came closest but didn't do the trick - ADB couldn't find device.)
Backed up current boot image (ROM) and system. (Couldn't mount \data). I don't think I'll be missing these files?
When trying to push Cyanogenmod zip, adb gives "error device not found".
Download additional drivers here (Sony Xperia VL drivers).
Still not doing the trick. Windows shows a device "Xperia V" with inadequate drivers and won't accept the VL drivers.
Can't seem to find fitting drivers anywhere.
Never mind. Bypassed the entire problem by inserting SD into PC, copying zips I needed to push manually, re-inserting SD into phone, rebooting ("fastboot reboot" from console) and installing zips from recovery menu.
Just writing this down for anyone else who's struggling with this.
Sorry for the messy monologue. Been at this for the better part of the day now, and it's currently 1:47 at night here. So I'm kinda tired. But happy
Still would like to know how to get decent drivers ADB drivers for Xperia V, though.
So my brother go some Black/Green screen on his S8 recently. He said it happened a week or so after a update he did on the phone. It's completely unusable. The only image on screen is either black, very dark (almost black) green, or when its booting sometimes it has black with green dots. Physically the device looks nearly perfect and he says it has no water damage. Upon searching the internet, other people have the same problem but theirs is usually fixed by restarting.
What I want to do is flash the stock Samsung stuff using Odin and see what happens. I am unable to get into recovery mode but I can get it into Download mode. Odin does detect it too. But the problem I am at is, I have no idea what version of bootloader or OS he has, since I don't follow the device at all. Anyone able to help me out with the version numbers so I can safely follow a guide that says like "only do on X bootloader/OS".
moccor said:
So my brother go some Black/Green screen on his S8 recently. He said it happened a week or so after a update he did on the phone. It's completely unusable. The only image on screen is either black, very dark (almost black) green, or when its booting sometimes it has black with green dots. Physically the device looks nearly perfect and he says it has no water damage. Upon searching the internet, other people have the same problem but theirs is usually fixed by restarting.
What I want to do is flash the stock Samsung stuff using Odin and see what happens. I am unable to get into recovery mode but I can get it into Download mode. Odin does detect it too. But the problem I am at is, I have no idea what version of bootloader or OS he has, since I don't follow the device at all. Anyone able to help me out with the version numbers so I can safely follow a guide that says like "only do on X bootloader/OS".
Click to expand...
Click to collapse
Just flash the latest. 5th digit from far end on firmware is a 1 through 6. 6 is pie. That's the best way to not have to download a bunch of them.
Hello good afternoon greetings from Mexico, a pleasure to greet you from here, months ago I tried to install lineage in a new motog7 plus since the factory rom is extremely restrictive and slow; in addition to the major security flaws.
at first all fluent install twrp and activate developer permissions, likewise unlock the bootloader; When flashing the phone, there was no problem, even I installed the gapps, the problem started when restarting it simply no longer turned on, it only lit the phone's led in red, when performing some procedures I managed to start it but it does not pass the image.
I have left it charging for hours and only the lightning logo comes out (which implies that it is charging); and in very small letters it says "any key to shutdown".
when I manage to turn on it does not go beyond the android logo.
These are the specifications:
Motog7 Plus Model: XT1965-T
Black
Dual SIM
I have tried to connect it to the pc to flash it and return it to its original state but it does not detect it.
Neither does it enter the recovery mode, the keys simply do not seem to work to enter the modes that it has natively.
Currently I have another phone the same since in those months I bought two similar ones; which I have not touched at all so as not to ruin it.
Any help to revive it would be greatly appreciated, thank you very much colleagues.
Hi,
A few days ago, I replaced a USB socket on friend's old Samsung Note 1 (GT-N7000). Soldering may not be very professional, but it does the job - the phone is charging and it can connect to the computer.
Today (3 days after replacing the USB) he came back to me with another problem -
after turning on the phone, only the white brand name and model appear at the start and then nothing, a black screen. I think it's turning off. He says he had some problems with the battery in the meantime and the screen was flickering strangely.
He had a custom ROM loaded for a long time that worked normally and worked well on this phone.
Today, despite not starting the system, I was able to enter TWRP recovery and DL mode. However, if I wanted to do anything in recovery (backup, factory reset, etc), the screen turned off. After a few attempts, it stopped going into recovery.
I have restored the original software using Odin and N7000XXLSZ_OXELS7_4.1.2_Repair_Firmware
- still after the white inscriptions at the start, the screen goes black and nothing
- trying to enter recovery, overturned android appears for a moment and the screen goes black
- DL mode works
Maybe someone knows what could have happened and most importantly how to get this phone work? Preferably on some "custom ROM" to have at least Android 7.
I was thinking, I was looking, I was tearing my hair out of my head. I searched half the internet and suddenly stumbled upon this - https://forum.xda-developers.com/t/...bricked-only-download-mode-available.3096409/
The phone is the same, the problem is the same - the battery is to blame. I immediately called the owner to give all the batteries he has.
OH, OF COURSE! The one I got along with the phone and its problems was the only one that caused all the restarts and errors. After inserting a different battery, the problems were resolved.
All that's left is to clean up Android and the case is closed.
By the way - I have collected in one place the files and information (Polish language only) on how to install NightOwl LineageOS 14.1 Android 7.1.
2 on this phone. If anyone needs this information, please visit here - https://drive.google.com/drive/folders/1libYpWC4qJbjGJRE1Szf8L3eTdoHPTpE?usp=sharing