Hello!
First, sorry if similar thread has been posted, i searched a lot and found nothing similar.
It's been a while since i'm stuck with a "little" problem, here are the symptoms:
- the phone shutdown itself for no reason (no heat, no new application, no water splash, no drop to the floor...)
- then when i try to reboot it, MI logo appears for 5-10seconds, then shutdown (no bootloop, the phone stays OFF)
- after a random number of tries (almost 100 times, literally, sometimes), it boots like a flower and works perfectly for a random duration (weeks, days, hours, or 1 minute).
I tried everything i could find, read, or get advised to do. I also posted on Miui.en, if you find motivation to read it, look for "Redmi 4 Prime shutted down itself and keeps shutting down after MI logo" (i can't post link).
Troubles started a couple of days after the OTA update from official MIUI global ROM 8.1.2 to 8.2 (the OTA update got deleted some days after). I thought that it was only a ROM bug, so i flashed to anterior version, but bug still happened some days after.
That's the only thing i did that i can remember. The phone wasn't even rooted at this moment.
About my phone:
- when it manages to boot, it works perfectly, no heat problem, no connectivity issues, can access to stockages...
- when it can't boot, i still have access to fastboot, recovery mode/TWRP, and when it is turned off, it displays charging state when pluged, and the phone never shutdown itself during one of those states.
- after a full wipe in TWRP (factory reset, system + cache + data and all), it can be stuck in bootloop at MI logo for hours without shutting down itself (if i push power button for 10sec, it keeps rebooting on MI logo, so an "usual" bootloop)
What i tried:
- flash all official roms with MIflash (china rom, global rom, stable and developer versions, latest and old versions), with flash_all.bat (clean all data),
- flash official/customs rom with TWRP,
- flash official roms with MI PC Suite.
I managed to do a CPU bug report last time it turned ON (on official MIUI 8.1.2 global rom) that i also posted on my other thread at the 3rd page, and a log after the last flash i did with MIflash (official MIUI 8.2.4 global rom).
Today, i only can boot my phone with a lot of luck (i managed to revive it once in 3 days after a lucky flash i guess, then it shutted down after 5 min), so it is more dead than a little bugged...
I rode things about kernel manipulations, deep flash, or even just try to open it and disconnect the battery for 15min (i will try this last option when i get the good screwdriver), but i prefer asking in hope that someone ever encountered this problem...
Thank you for reading me and thanks by advance if somebody got some advises!
Tib347 said:
Hello!
First, sorry if similar thread has been posted, i searched a lot and found nothing similar.
It's been a while since i'm stuck with a "little" problem, here are the symptoms:
- the phone shutdown itself for no reason (no heat, no new application, no water splash, no drop to the floor...)
- then when i try to reboot it, MI logo appears for 5-10seconds, then shutdown (no bootloop, the phone stays OFF)
- after a random number of tries (almost 100 times, literally, sometimes), it boots like a flower and works perfectly for a random duration (weeks, days, hours, or 1 minute).
I tried everything i could find, read, or get advised to do. I also posted on Miui.en, if you find motivation to read it, look for "Redmi 4 Prime shutted down itself and keeps shutting down after MI logo" (i can't post link).
Troubles started a couple of days after the OTA update from official MIUI global ROM 8.1.2 to 8.2 (the OTA update got deleted some days after). I thought that it was only a ROM bug, so i flashed to anterior version, but bug still happened some days after.
That's the only thing i did that i can remember. The phone wasn't even rooted at this moment.
About my phone:
- when it manages to boot, it works perfectly, no heat problem, no connectivity issues, can access to stockages...
- when it can't boot, i still have access to fastboot, recovery mode/TWRP, and when it is turned off, it displays charging state when pluged, and the phone never shutdown itself during one of those states.
- after a full wipe in TWRP (factory reset, system + cache + data and all), it can be stuck in bootloop at MI logo for hours without shutting down itself (if i push power button for 10sec, it keeps rebooting on MI logo, so an "usual" bootloop)
What i tried:
- flash all official roms with MIflash (china rom, global rom, stable and developer versions, latest and old versions), with flash_all.bat (clean all data),
- flash official/customs rom with TWRP,
- flash official roms with MI PC Suite.
I managed to do a CPU bug report last time it turned ON (on official MIUI 8.1.2 global rom) that i also posted on my other thread at the 3rd page, and a log after the last flash i did with MIflash (official MIUI 8.2.4 global rom).
Today, i only can boot my phone with a lot of luck (i managed to revive it once in 3 days after a lucky flash i guess, then it shutted down after 5 min), so it is more dead than a little bugged...
I rode things about kernel manipulations, deep flash, or even just try to open it and disconnect the battery for 15min (i will try this last option when i get the good screwdriver), but i prefer asking in hope that someone ever encountered this problem...
Thank you for reading me and thanks by advance if somebody got some advises!
Click to expand...
Click to collapse
to me it sounds like hardware problem . how about warranty?
ttheodorou said:
to me it sounds like hardware problem . how about warranty?
Click to expand...
Click to collapse
I bought it on Gearbest, and of course, warranty is void if you touch the ROM... Same for Xiaomi once you unlock the bootloader i think (i did it because there weren't official global roms when i bought it) :crying:
Do you think about something else?
Or did it already happen to someone else?
Tib347 said:
Do you think about something else?
Or did it already happen to someone else?
Click to expand...
Click to collapse
the only thing i can think is hardware since you did all the software tricks
Related
I have a stock unmodified defy updated to 2.2.2, recently the phone started constantly rebooting, usually it stays on for about 2-5min before it goes off or reboots, either plug-in or not. I thought it would be some problem with apps or something like that, so i reset the phone to factory settings and the same kept happening. The phone never reboots in bootloader mode or in recovery mode.
Since this wasnt working i decided to install a custom rom or even the stock roms in wiki in this forum.
Through the times i flashed the phone i only used the custom recovery once, do i have to use it for each time i flash it? It is really hard to keep the phone on long enough to install the bootloader each time.
the phone was a stock uk unlocked debranded version i got from expansys.
Now I installed a 4.5.1-112 Orange GB 2.3.3 with MotoBlur stock sbf version
All i done to this version load the bootloader and install it. the phone is dead now with no response connection to rsd lite or white led. (which i am about to try to sort it).
All i wonder is if it is me installing the sbfs wrong and because of that it is not fixing the reboot problem, or if this has happened to more people and does anyone knows a solution for it?
I have installed 2.2.1, 2.2.2 (stock) and modified from a tutorial in here and now 2.3.3 as mentioned above.
I would appreciate if anyone could help me.
Now you're in 2.3.3. Have you try boot into stock recovery and do total wipe of cache/data, and reboot again??
A lot of people forget this step when they do the flashing and restoring process..
derviansoul said:
I have a stock unmodified defy updated to 2.2.2, recently the phone started constantly rebooting, usually it stays on for about 2-5min before it goes off or reboots, either plug-in or not. I thought it would be some problem with apps or something like that, so i reset the phone to factory settings and the same kept happening. The phone never reboots in bootloader mode or in recovery mode.
Since this wasnt working i decided to install a custom rom or even the stock roms in wiki in this forum.
Through the times i flashed the phone i only used the custom recovery once, do i have to use it for each time i flash it? It is really hard to keep the phone on long enough to install the bootloader each time.
the phone was a stock uk unlocked debranded version i got from expansys.
Now I installed a 4.5.1-112 Orange GB 2.3.3 with MotoBlur stock sbf version
All i done to this version load the bootloader and install it. the phone is dead now with no response connection to rsd lite or white led. (which i am about to try to sort it).
All i wonder is if it is me installing the sbfs wrong and because of that it is not fixing the reboot problem, or if this has happened to more people and does anyone knows a solution for it?
I have installed 2.2.1, 2.2.2 (stock) and modified from a tutorial in here and now 2.3.3 as mentioned above.
I would appreciate if anyone could help me.
Click to expand...
Click to collapse
you need to have custom recovery , wipe data and cache , then try or else search this forum (defy) for fixed sbf of your choice and flash that and then root and load your rom
farsight73 said:
Now you're in 2.3.3. Have you try boot into stock recovery and do total wipe of cache/data, and reboot again??
A lot of people forget this step when they do the flashing and restoring process..
Click to expand...
Click to collapse
I left the phone overnight without the battery on, and this morning for some reason i could reboot to 2.3.3 at first the phone stayed on without rebooting for about 30mins, but soon it started doing the same constant rebooting now it doesnt even go past the moto sign.
I have wipeout now the cache also and no changes.
dlcookie said:
you need to have custom recovery , wipe data and cache , then try or else search this forum (defy) for fixed sbf of your choice and flash that and then root and load your rom
Click to expand...
Click to collapse
What do you mean for a fixed sbf? That is a new term for me. It is really hard install the bootmenu thing because the phone doesnt stay on for long in the android os!!Is there any other way to connect to adb?
I got a fixed sbf and attempted to follow all the steps stricly, but when i dowgraded from gingerbread 4.5.1-112 Orange GB 2.3.3 with MotoBlur to Uk 3.4.2 froyo stock sbf from here
http://forum.xda-developers.com/showthread.php?t=933555
my phone this time gone really weird:
All i managed to do with this sbf was to root it with superclick, before it gone off again.
yesterday Saturday 03-12
-When I put the battery in, the phone refuses to go on, or to get in bootloader/recovery, after a few minutes the boots automatically and gets stuck in the moto logo (sometimes it goes off sometimes just stays there for 5min or more).
- If i plug the phone sometimes it stays off with the white led on, but rsd doesnt detect it, neither it goes on bootloader/recovery and sometimes it boots automatically sometimes doesn't come on at all.
Today:
- Tried to get the phone on this morning, it wouldnt go on or go into bootloader/recovery, then eventually it started up on its own and got stuck on the moto logo, i took the battery off and tried again, the phone wouldnt come on again, but eventually it started on its own and went to the bootmenu, where for the first time it crashed there, and it didnt recognise usb cable. I tried again and the phone booted up on its own with the usb cable to the bootloader,it gave the ok status for the usb connection but rsd lite never recognise it. Now it wont go on at all.
Please note that i have a desk charger and all this was done with a nearly full or full battery.
Does anyone know if the phone is completly dead now or if there is anything else I can do?
Thanks for the replies.
Mine just rebooting too
Dear derviansoul (",)
Hope all is well with you.
I just have the rebooting issue, like what you said (stayed on for 2-5mins before it goes off to reboot; phone never reboots in bootloader or recovery mode).
What i did was:
- i fell in love with Cyanogen mod 7.1.0-11 & 7.2-rc1 recently (thanks to Quarx & all in CM for your hard work);
- i had 32gb microsd card & decided to spent my hard-earned $ on a 64gb microsd card for this wonderful phone (due to CM, not Motorola);
- Sandisk microsd 64gb works AFTER erasing in Settings -> Storage;
- then, using Symantec Ghost 8.2 to clone my 32gb microsd card into 64gb;
- after putting in the clone-completed 64gb microsd card, the phone starts rebooting as described above;
- i tried to put back my own original 32gb microsd card, but the rebooting still happens!?!;
- in Recovery mode, i "wiped cache" & then go to "advanced", select "wipe dalvik cache", but problem remains;
- i formatted the the 64gb from Recovery mode, and manually copied the contents of the 32gb to 64gb using my WinXP computer, but the problem still remains!;
- (my solution) in bootloader mode, i go to "Tools" -> "share sd card", then from my WinXP computer, i can see the microsd card as Mass storage device, i deleted ONLY the folder ".android_secure" which is more than 2GB large.
- now there is no rebooting, and i just need to reinstall my apps from the Play Store, & my settings and data are all still there *sweet*.
Hope this helps.
Motorola Defy (red lens) cm7.2-rc1
EDIT:
UPDATED POST AT THE BOTTOM!
Hey guys,
flashed czechops CM 10.2 a while ago everything was running fine.
On Saturday i decided to let the battery drain completely to do a full recharge. That`s when the Problems started.
After booting the Phone up i was stuck in a Bootloop with the Cyanogenmod Logo turning around and around and around and so on.
Okay i thought let`s reboot and see what happens.
Still the same.
I then booted into recovery by holding the x button on the keyboard and power and then when the androind in the triangle showed up using vol + and vol - to get into recovery.
I then deleted the cache and rebooted again (No full wipe to factory default trying to avoid that).
After that the phone turned on saying Android is getting updated Updating Package x of y.
After its done its now stuck in Apps getting started.
After i found out to get to the Bootmenu i decided to check the Recovery Menu there.
I can choose between Motorola Stock Recovery (the normal one i already was on)
and Team Win Recovery.
So i choose Team Win Recovery and thought okay since its not working im gonna install the Update of czechops 10.2
Installing itself worked fine. But now im stuck in the same loops.
Currently im goind a Backup of the System with the Team Win Recovery in the hope i wont loose the data even if what im trying to avoid a full factory wipe.
What kinda poped in my eyes when i started the recovery was that it said E: Unable to locate '/boot' partition for backup.
Could this be the problem which is stopping the phone from booting correctly?
And if so how can i fix it?
Hope anyone can help me,
Kind Regards,
Invi
I had te same problem before doing a clean install.
I don't know why but, if you install the android 10.0 tezet and from there start the gapps, creating a account and installing your apps, you do not have problems to install the 10.2.
Good luck.
Sent from my A953 using xda app-developers app
jonasgitz said:
I had te same problem before doing a clean install.
I don't know why but, if you install the android 10.0 tezet and from there start the gapps, creating a account and installing your apps, you do not have problems to install the 10.2.
Good luck.
Sent from my A953 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the heads up jonas.
Unfortunately its too late its seems. My Milestone is just a stone now it seems.
After trying to install 10.2 12.03.14 and that not working correct after doing a full factory wipe i decided to install cm 11 from czechop.
Unfortunately it seems it failed.
My milestone just boots up and stops at the First Logo. No lights. No chance to get in any recovery mode except the normal one.
Bootloader was working some time but stopped cause the Battery is almost empty.
The Problem is i cant even load the Phone anymore cause as soon as i put it on a charger it boots up and wont get enough battery power to live for a few minutes.
So the only thing left working is the normal Android 3e Recovery. Hope i can do anything from there.
Don't give up.
Your problem it's normal, you fisrt need a global battery charger to recharge your battery.
After it, go to boot recovery, you must turn on the milestone holding " volume down + camera" or "volume up + camera", than you need to uses the RSD Lite to reflash your milestone 2.
Normaly, when do you came from another room, you stay in boot loop, so you need to entery in Miestone recovery, "x + volume down" than after it you do a factory reset. It will boot normaly after that.
To go to boot recovery, you must turn on.
Try harder.
(Guys, lets try to help a little)
Sorry about my poor english
I wont. Already ordered an global battery charger yesterday. In the mail from the store delivery is 7-10 Weekdays.
Good thing i have a second cellphone which i can use in the meantime.
i had a similar scenario
Invisan said:
Thanks for the heads up jonas.
Unfortunately its too late its seems. My Milestone is just a stone now it seems.
After trying to install 10.2 12.03.14 and that not working correct after doing a full factory wipe i decided to install cm 11 from czechop.
Unfortunately it seems it failed.
My milestone just boots up and stops at the First Logo. No lights. No chance to get in any recovery mode except the normal one.
Bootloader was working some time but stopped cause the Battery is almost empty.
The Problem is i cant even load the Phone anymore cause as soon as i put it on a charger it boots up and wont get enough battery power to live for a few minutes.
So the only thing left working is the normal Android 3e Recovery. Hope i can do anything from there.
Click to expand...
Click to collapse
hi, I had a similar situation to that earlier today, in that I got to the situation where on boot up I got the Motorola logo then nothing else (I was trying to install C.M. 11 from 10.2 but when it went to install got a message E;// error - verification signature installation aborted), after major panic thinking I'd bricked my milestone, I tried starting the phone in bootloader mode (press camera, volume up and power buttons at the same time) which gives a black screen saying boot loader 70.13 and towards the bottom says boot menu, connect USB, then on your pc find program MOTOROLA SOFTWARE UPDATER (hope you've got it) open the program, it'll say connect a device plug your phone in and let it do it's stuff, takes about an hour (charge your battery using a desktop battery charger beforehand) and your phone will be returned to the stock Motorola rom but at least your phone isn't a brick and you can always start again trying cyanogenmod.
hope this helps
mark13_2001 said:
hi, I had a similar situation to that earlier today, in that I got to the situation where on boot up I got the Motorola logo then nothing else (I was trying to install C.M. 11 from 10.2 but when it went to install got a message E;// error - verification signature installation aborted), after major panic thinking I'd bricked my milestone, I tried starting the phone in bootloader mode (press camera, volume up and power buttons at the same time) which gives a black screen saying boot loader 70.13 and towards the bottom says boot menu, connect USB, then on your pc find program MOTOROLA SOFTWARE UPDATER (hope you've got it) open the program, it'll say connect a device plug your phone in and let it do it's stuff, takes about an hour (charge your battery using a desktop battery charger beforehand) and your phone will be returned to the stock Motorola rom but at least your phone isn't a brick and you can always start again trying cyanogenmod.
hope this helps
Click to expand...
Click to collapse
So i downloaded Motorola Software Updater and RSD Lite + Motorola Device Manager newest Version
Unfortunately my Milestone seems not to be recognized by either Software updater nor RSD Lite.
In the Device Manager S Flash OMAP3630 shows up and is recognized.
Im running Windows 8.1 x64 and on a second Computer Windows 7 x64
What tool can i use ander Linux? Maybe the Phone will be recognized there.
EDIT:
K found it. Doing it with Linux at the Moment. Its working.
Only need to Root it then and after that flash my old Files and hope they are working.
At least i have an old Backup i made from Tezet before going up to 10.2 which i made with Clockworkmod
Hope it will work and not be broken like the one i made with Team Win Recovery.
Anyone knows how i can change stuff in a Team Win Backup?
Invisan said:
So i downloaded Motorola Software Updater and RSD Lite + Motorola Device Manager newest Version
Unfortunately my Milestone seems not to be recognized by either Software updater nor RSD Lite.
In the Device Manager S Flash OMAP3630 shows up and is recognized.
Im running Windows 8.1 x64 and on a second Computer Windows 7 x64
What tool can i use ander Linux? Maybe the Phone will be recognized there.
EDIT:
K found it. Doing it with Linux at the Moment. Its working.
Only need to Root it then and after that flash my old Files and hope they are working.
At least i have an old Backup i made from Tezet before going up to 10.2 which i made with Clockworkmod
Hope it will work and not be broken like the one i made with Team Win Recovery.
Anyone knows how i can change stuff in a Team Win Backup?
Click to expand...
Click to collapse
I did find it took a long time for the Motorola software updater (about 20 mins) to detect my milestone 2 (I'm using windows7 x64), I'm thinking the mistake I made when trying to upgrade to CM 11 was I didn't wipe data/cache before trying to install it
mark13_2001 said:
I did find it took a long time for the Motorola software updater (about 20 mins) to detect my milestone 2 (I'm using windows7 x64), I'm thinking the mistake I made when trying to upgrade to CM 11 was I didn't wipe data/cache before trying to install it
Click to expand...
Click to collapse
Hi mark,
well Windows popped up saying N/A
when it should show new Software.
It also couldnt recognize my Cellphone correctly it seemed.
But i flashed it with Linux anyways.
Flashing to tezet`s 10 worked also like a charm
and i could install my Backup i made in december before
updating to czechops 10.2.
Guess after i know what to do now i will try to update to cm11 now.
Invisan said:
Hi mark,
well Windows popped up saying N/A
when it should show new Software.
It also couldnt recognize my Cellphone correctly it seemed.
But i flashed it with Linux anyways.
Flashing to tezet`s 10 worked also like a charm
and i could install my Backup i made in december before
updating to czechops 10.2.
Guess after i know what to do now i will try to update to cm11 now.
Click to expand...
Click to collapse
let us know how you get on as I'm tempted to try again (I do like how CM10 gets rid of all the un-necessary apps but gives you control of all the system parameters) but want to step up to CM11 without having the same problem as before.
Hi all,
Yesterday my Jiayu S3 crashed and rebooted, after setting an alarm clock and using the Spotify app. However, it did not reboot into the OS as usual. It did not even show the Jiayu logo, but the phone vibrated (sign that it's booting), screen turned on, phone turned off again, repeating this cycle over and over (not the traditional bootloop as I know it). I was running a rom based on the original rom, with some slight modifications. This rom was running stable for more than a week. I know my way around Android, and am used to switching roms, flashing etc.
Right away, I checked the following things:
- Battery removal didn't help (I did not forget to put it in again ofcourse )
- Phone doesn't go into it's charging cycle when charger is connected
- I do NOT have access to recovery
- I can, however, access the boot menu (Volume up + power key, options: Normal boot, recovery, fastboot)
- I can get into fastboot mode (haven't tested ADB yet), that's the only thing that's still working
I tried to flash the original firmware using SP flashtool, and I am still able to upload firmware on the phone! I am sure that I'm using the correct ROM, and tried different PC's and drivers. Got a few succesful flashes, but still bootlooping.
I also had the idea that my battery was empty (didn't charge it overnight), and measured the battery at 3.52 V. So it was pretty empty but not that empty that it doesn't boot. In an effort to charge the phone, I left it bootlooping for an hour or so, and later on it turned out that it only drained the battery further, 2.99 V.
I didn't want to kill this battery so I did use 2 other batteries from an old Jiayu G4, which appear to work if you turn them around and hold them against the pins (note: I knew what I was doing here ). After a lot of Googling, and seeing a lot of generic "how to fix any brick" stuff I was not able to revive my phone again.
I still believe (and hope) that the error is on the software side of the phone. All the partitions should be ok and in working order according to SP flashtool.
Now this is where my knowledge stops and where (hopefully) your help comes in. What can be corrupted that I haven't checked yet? Do you guys have any suggestions to revive this "high-end" phone again? Once again, it did not happen because of bad flashing or something like that, it happened randomly when I was using the phone normally. I tried to be as accurate as possible (long story), but if there are any questions I'm happy to answer them.
Any suggestion is welcome!
Thanks in advance.
Bump..
Anyone?
bump
Hello,
yesterday I tried to boot my tablet and after the logo "Lenovo" appeared on the screen, nothing happened (the screen was stuck on "Lenovo").
Tried to power off/on several times, same behaviour.
I charged it the whole night, and today when I tried to boot it, after the logo "Lenovo" appeared on the screen, the screen started flickering (random gray/green lines here and there)...
Any help?
Do you think it's a hardware or software problem?
Thanks
did you tried to do something ? any flashing/rooting attempt etc?
in any case you could try flashing a stock rom anew so at least you will know what is the problem... could be anything
(i have assumed you have an android tablet, maybe you could also post the model when asking)
ionioni said:
did you tried to do something ? any flashing/rooting attempt etc?
in any case you could try flashing a stock rom anew so at least you will know what is the problem... could be anything
(i have assumed you have an android tablet, maybe you could also post the model when asking)
Click to expand...
Click to collapse
I rooted it and flashed it a few months ago. Have been using it with multiuser feature (4 users).
Worked until yesterday.
See http://forum.xda-developers.com/showpost.php?p=59609862&postcount=172
Model:
Lenovo Yoga 10 B8000-F tablet
Android version: 4.4.2
[.::MDT::.] said:
I rooted it and flashed it a few months ago. Have been using it with multiuser feature (4 users).
Worked until yesterday.
See http://forum.xda-developers.com/showpost.php?p=59609862&postcount=172
Model:
Lenovo Yoga 10 B8000-F tablet
Android version: 4.4.2
Click to expand...
Click to collapse
so... try and flash back your stock rom
Or try to wipe data from recovery.....
StepoXX said:
Or try to wipe data from recovery.....
Click to expand...
Click to collapse
Thanks.
While booting (when the LENOVO logo appears) I kept pressing VOLUME UP button.
It entered recovery mode, where I deleted cache only (no factory reset).
After that it booted correctly.
I reckon the multiuser feature (I set up 4 users) could maybe use a lot of ram and the device gets stuck.
Not sure how to reproduce the problem, I'll maybe try a factory reset to check if the issue is still there.
I've been using the stock rom on my phone for years, until after one update my wifi went incredibly choppy, so I tried rooting and LineageOS but experienced lots of other issues, so I reverted to the original stock rom.
I've stuck with 6.0 for over a year, unrooted, unspoilt, but I was constantly pestered with update notifications.
I accidentally hit 'Yes, I'm in' the other day and it downloaded the update, and the pestering went next level insane.
I'd hit dismiss and 5 seconds later - DO YOU WANT TO INSTALL THE UPDATE? It would reappear a minute later.
So I finally caved and just said yes, curious whether or not my wifi would suffer, figuring it might have been a bad update that caused my wifi issues which has since been fixed.
I installed the first update, which brought me to 6.0.1 I think, and then I installed the update to 7.0.
And then my phone died completely.
The only sign of life is when I plug it into the PC, the charging light blinks, but I don't even see a battery charging screen.
The screen has stayed black since, can't reboot into any mode.
What now?
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
hedgehog90 said:
I've been using the stock rom on my phone for years, until after one update my wifi went incredibly choppy, so I tried rooting and LineageOS but experienced lots of other issues, so I reverted to the original stock rom.
I've stuck with 6.0 for over a year, unrooted, unspoilt, but I was constantly pestered with update notifications.
I accidentally hit 'Yes, I'm in' the other day and it downloaded the update, and the pestering went next level insane.
I'd hit dismiss and 5 seconds later - DO YOU WANT TO INSTALL THE UPDATE? It would reappear a minute later.
So I finally caved and just said yes, curious whether or not my wifi would suffer, figuring it might have been a bad update that caused my wifi issues which has since been fixed.
I installed the first update, which brought me to 6.0.1 I think, and then I installed the update to 7.0.
And then my phone died completely.
The only sign of life is when I plug it into the PC, the charging light blinks, but I don't even see a battery charging screen.
The screen has stayed black since, can't reboot into any mode.
What now?
Click to expand...
Click to collapse
Does it vibrate or any other indication that the phone is trying to boot? Will it charge? needs to be at least 40% to recover. USB to ADB and see if the phone is recognized on a PC. Could be hard bricked ... there is one other mode that some phones use where the screen is black and the only way to talk to it is through a flashing tool. I apologize that I cannot recall the name of that mode but considering that Lenovo developed this phone it wouldnt surprise me if it was just in that mode, waiting for a boot load update of some kind. A lenovo flash program might be worth a try.
milesius said:
Does it vibrate or any other indication that the phone is trying to boot? Will it charge? needs to be at least 40% to recover. USB to ADB and see if the phone is recognized on a PC. Could be hard bricked ... there is one other mode that some phones use where the screen is black and the only way to talk to it is through a flashing tool. I apologize that I cannot recall the name of that mode but considering that Lenovo developed this phone it wouldnt surprise me if it was just in that mode, waiting for a boot load update of some kind. A lenovo flash program might be worth a try.
Click to expand...
Click to collapse
I eventually fixed it using adb following a set of unbricking instructions on XDA.
Sorry for not updating the thread.