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.
Related
Hi everyone,
This is my first post so I hope you are kind enough to help me with this issue.
I have an HTC 8X Blue (bought it factory unlocked) and recently I have updated it to GDR2. It happened what many other HTC 8X's user had. It bricked when I was playing some music.
I found an article that has a solution allegedly (I cannot post the link but it is the most popular solution aparently). But my problem is that I cannot enter Bootloader Mode as one of the first steps requires. My phone is simply dead, I tried every combination of buttons (hard reset and soft reset), but non is responsive. Of course, my PC does not recognize it and when I plug it in to the wall the red light does not turn on!
I do not have experience in modding or flashing or what-ever process needed (for Windows Phone), but I do know pretty much for iOS so I can learn quickly.
Any help would be greatly appreciated!
Your best option would be to get it repaired/replaced by a service center. If you're near a Microsoft store, they can take care of that for you. If not, it'll be trickier.
Otherwise, the only advice I can offer is to leave it for a while, let the battery drain entirely if you can, plug it in again, and try to start it... even if it won't boot normally, you may be able to access the bootloader mode now.
Thanks for the quick reply! I actually do not have a Microsoft Store as I live in Argentina...
I think i will try to drain the battery and restart it. Should I restart it the normal way? I mean by holding power button?
Yep, basically that.
You could also try calling HTC support and seeing if they have any other recommendations. The battery drain thing is basically just in case the phone got stuck in a weird state; resetting it that way may help.
is your phone stuck in QHSUSB_DLMODE i got my stuck there the other day. what i did was hold VOL UP, WOL DOWN and POWER all at the same time until the phone vibrated. wouldnt you know i unbricked my device.
Hi guys!
Since I upgraded to the latest release of Oreo 8.1.0.120 (C432) (branded H3G) the phone keeps crashing !!!!
Virtually all of a sudden the screen is divided into 2 vertically, a completely black part and a slightly lighter one with the time indicated.
The phone can not be unlocked in any way, either with the power button or fingerprints.
He receives phone calls (the accept and reject buttons are vertical) but nothing else.
Tried to do soft reset several times (deleted cache and system reboot), 1 time also hard reset: sometimes it restarts and returns to normal, sometimes it remains exactly locked as before.
Screen resolution modes is fixed to fhd + .....
I thought it was a bug on the reactivation from a bluetooth device (the speakerphone of the car) because the first time he did it when I turned off the machine and the device was obviously connected, but instead he did it on other occasions not attributable to that.
Face recognition doesn't work too (I'm not able to recognize and save the face).
I got the phone as soon as it came out, and it never had any kind of problem .......
Called huawei support and they told me to send him for assistance, called H3G and ditto, I asked if they had news of this bug but it is the first time .....:crying::crying::crying::crying::crying::crying:
Use funkyhuaewei or if you have TWRP installed reflash stock fw that should fix
Hi! Thank you for the help but I have no TWRP and I've seen that for funkyHuawei the minimum credit is about 40€!!!!!! Is there another procedure to reinstall the firmware??????
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
Click to expand...
Click to collapse
I would try flashing the latest factory image via fastboot.
[Guide] Root Pixel 4 XL with Magisk Android 13
[Guide] Root Pixel 4 XL With Magisk Android 13 Android Security Bulletin—Feburary 2023 Pixel Update Bulletin—Feburary 2023 Introduction This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The...
forum.xda-developers.com
https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/ (This is for a Pixel 2 XL but the process is the same. It's basically a condensed version of the one above.)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Click to expand...
Click to collapse
You did not provide the most important information we need- whether your phone is bootloader unlocked. Probably not, otherwise you would have already flashed it with a full Google image, which returns the phone to "out of the box" condition. You need to determine whether you can unlock your bootloader. If you cannot unlock (allow oem unlock is off and or greyed out in Dev options) then you will not be able to fastboot flash ANYTHING. If that is your case, the next best thing is flashing a full OTA image (sometimes called a rescue OTA) from recovery mode using the OTA via ADB option. This means you need fastboot/adb installed and working on your PC. Instructions on how are on the same Google dev page for OTA's.
So, my phone's bootloader is not unlocked. But I have an update for the crowd that may one day find this. I know your frustration and I can report that my phone is once again fixed.
A day (or two) after I sent this, a set of updates came down to my phone. And WebView was updated. That restored all of my sensors and also restored most of my crashing applications. It was an incredibly odd experience.
My phone once again functions. And the nightmare of owning a Google phone and talking to Google support has ended.
Hello!
I kind of "bricked" my tablet. Yesterday I wanted to try Ubuntu touch, installed it trough UBports, everything was easy. After some testing, I decided to go back to Android. The official website of by was shut down, bq doesn't exist anymore. I remember downloading Android images on their website years ago.
However, I was searching the web for copies of Android ROMs for this tablet and found two, one from 2016 (probably Android 5.1) and one from 2018 (Android 6.0, I guess).
I used the SP Flash Tool to flash the ROM onto the tablet. This process takes about three minutes and seems to work fine, I get the green check mark in the end. However, after flashing, the tablet turns on but stays in a blackscreen. First I thought it was bricked now, actually the Android system gets installed! After about ten minutes I can turn off the screen by pressing the Power button - and hear the lock sound! So it pretty much seems like the system gets installed successfully but maybe the screen driver doesn't work?
Plugging the tablet to my monitor through HDMI didn't give me an image either.
I once achieved to get to the recovery menu after a reboot - but again: only a black back-lit screen. I recognized this by randomly pressing buttons until the test sound played.
I tried flashing Ubuntu touch through the SP tool and then I get a fully working tablet, even though the OS itself is old and unusable. So... How do I install Android without the blackscreen? LineageOS or something else would be okay too.
Not sure if this is of any use to you still, but on this German forum there is a software repo that holds most software and firmwares from BQ: https://www.android-hilfe.de/forum/...itory-fuer-treiber-tools-firmware.964197.html.
That said, I have the same tablet and while it's getting kind of old, it's one of the very few tablets that has active development for a Linux operating system. I still have Android on it actually, but I plan to update it with Ubuntu in the near term. It seems stupid to just keep using an old Android version on it. I'm wondering what made you take the step to go back to Android after trying Ubuntu Touch?
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