Hey guys i had an invicta os rom . I wanted to go back to stock so i went back using a july 2016 stock firmware. It booted up and worked. Now i received nougat update. I downloaded and installed it. Due to some problem my phone is not booting. It is not even showing battery icon when charging. No response on cliking power and volume buttons for more than 120 seconds. When i connect the charger the indicator led flashes. That is all. What should i do????
Since no response on power and volume buttons i cannot go into bootloader and recovery also. Im suck on a black screen not change in color on charging. Only the led blinks when charger is connected... Pls help
By downgrading to stock Marshmallow from having stock Nougat, and then attempting to update via OTA, you've hard bricked. I warned about this in this post: https://forum.xda-developers.com/showpost.php?p=75033410&postcount=1166 Had you flashed the September 2017 stock ROM you would probably have been okay.
Effectively, by downgrading, you had a Marshmallow based system but a Nougat based bootloader (likely March/June/September 2017). By taking the OTA, you likely attempted to flash the December 2016 firmware update, including the bootloader, which corrupted your newer bootloader. Your device is showing the classic signs of being hard bricked from a corrupted bootloader, and I imagine if you connect your device to your computer, you'll see HS-USB 9008 or similar in Device Manager.
To rescue your device, you can try the blankflash and ROM here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
In future, do not flash older stock ROMs to your device (e.g. Marshmallow or old Nougat firmware), or if you do, do not accept OTA updates. Else the same thing will happen and then the blankflashes may not work, leaving you with an expensive paperweight (or very expensive repair).
Related
After a year of playing with Galaxy S3 I got bored with constant flashing and well, I never got used to onscreen keyboard.
I wanted a phone that will just work and decided to go for a Droid Pro+. Device was form Germany as there is no official distribution in Poland. It worked like a charm for two weeks till just now.
While playing with it (changing ringtones and stuff) I got several messages about services failing - com.service.usb, com.service.google, etc.) As it happened before (but only com.service.usb) I restarted it - in a normal way - power button and then Reboot. It rebooted and after that got stuck on M logo.
The firmware was as stock as it could be. No modifications were made. What's strange, the device can't be hard resetted. I can hold the power button for several minutes and it won't turn off.
Recovery mode works, but wiping does not help. Fastboot also works, but RSD Lite shows N/A in every column of Device info. I flashed GB 2.3.6 (5.5.1Q-110_ELW-TA-36-65-release-keys-signed.Retail-en-GB.tar) found on XDA. The rom itself should be OK, as no functionality was lost (recovery and fastboot), but the device still hangs on the boot logo. Device info is still N/A.
Could it be a hardware malfunction or is there something else I could try? Warranty is probably not an option since as i mentioned there is no official distribution in Poland. Any help would be appreciated since I'm out of ideas by now... Also, does anyone know if the battery is charged when in Recovery or fastboot mode? Connecting to a charger ends up on the M logo. And because very few people in Poland have Moto devices I have no other way to recharge the battery.
Hi,
I picked up a second hand XT1622 super cheap the other day. It didn't seem to want to boot at first, and stuck around on the blue Motorola logo for a while, but eventually after leaving it alone for an hour or so it sprang into action.
Trouble was I then made the mistake of downloading the December OTA update, and since rebooting from that installation it's been stuck on the blue screen again.
I thought maybe something went wrong with the OTA, and flashed the December firmware through Fastboot hoping that would resurrect it, but I'm still getting the same result.
The bootloader is locked unfortunately, and I can't boot into recovery mode either - same issue.
Does anybody have suggestions other than me breaking the phone in half (which is probably going to happen today anyway)?
Phone suddenly sprang to life, but for some reason wouldn’t let me press return after entering my PIN after prompting for it in setup - maybe it’s a hardware issue and the phone’s on its way to the great G4 graveyard in the sky?
The original G destroys this nonsense of a phone.
For and download the stock firmware, and then flash it through fastboot. After that, see if it boots. If it does, unlock the bootloader so you will have b easier time if this happens again.
Hi
I am stuck with Pulsing blue LED and the "Powered by Android" screen,
have access to both the recovery and the download Mode,
I also have Odin (version 3.13) on my computer along with TWRP (3.1.1 trlte and 3.2.1 version)
My device is a Samsung Galaxy Note 4 N910F bought in shop, no special carrier. It was bought in the Netherlands.
I have tried everything that I have read. The furthest that I can go is the Second Samsung Logo with the Flashing Light
Whenever I try to Flash the stock Firmware for my N910F, everything goes well in Odin but then when the phone reboots, it (sometimes) install the system update until 30% then shows erasing then either crashes right there and then or load the system update bar, completes it then shuts down.
I have tried multiple firmwares, even recovery firmwares. All the same problem. I can see the firmware is flashed, because when I enter recovery mode after I flashed a different ROM, it shows the version I flashed.
I cannot seem to install TWRP because it was never rooted.
Whatever I do, at some point, my phone either gets stuck in a bootloop, freezes with the LED light or shuts down.
And I have also proceeded to use different batteries.
Do you have any options?
Thank you
Heat????
I'm far from an expert here, but I've just experienced a similar problem where my N910F started boot looping / freezing within 15s to 2 min after unlocking. Unfortunately my micro Sd (SanDisk 256GB) was corrupted a week ago, so before doing anything else I did some research (XDA/YouTube) and probably found pretty much what you've found. I frequently change batteries so I could discount that as an issue. Someone suggested using the Samsung Smart switch here https://www.samsung.com/uk/getting-started/smart-switch/, but I haven't used it (yet) so I can't tell. I presume you had the latest firmware from Sams https://www.sammobile.com/firmwares/galaxy-note4/SM-N910F/.
My issue was that I needed to recover data, docs, photos, phone numbers etc. When boot looping the note 4 got very hot . In particular around and to the left of the camera (looking at the rear). Thinking it could possibly be the dreaded eMMC problem which also manifests itself by creating heat, I thought cooling the device might help. I placed the Note on a cooler box freezing block and voilà! No boot loop. I was able to remove all, but necessary apps and do a full copy to my PC. Storage was reduced from around 90% to 50% and memory 80% to 60%. It's now been stable for 12 hours, but the jury is still out. Next will be full reset with he latest available firmware 6.0.1 as mine was still on 5.1.1.
Good luck and hope this may be of some help.
I've got this problem, too, when using the unofficial Lineage 15.1 rom. SIM death and boot loop. After flashing the latest stock rom through odin, it passed but the screen was black and no system was installed. The blue notification light was constantly stuttering, though. And I couldn't even go to recovery!
When flashing, a 910F can get hot - use a cool temperature room and/or a fan blowing onto the device.
If it's not too late...
Hey, I was running Lineage OS 14.1 and then decided to go back to Stock because of network & Bluetooth issues. I flahsed the right stock rom 5.1 , it booted right on, did an OTA but the phone didn't turn on after that.
I tried Vol down + Pwr to boot bootloader, i tried to connect charger, connect to my laptop but the phone is just not responding to anything.
never downgrade it hard bricks, you can't do anything i think unless you have a jtag unit, you did an OTA and apparently it hard bricks the phone if you weren't on stock the whole time
Unfortunately you can downgrade it without problems only with de-bloated roms flashed from twrp
Hi, so about a week ago I updated my S8 and everything was fine. But then while I was making a phone call it shut down. I tried to make it power up but got stuck at the Samsung Galaxy S8 powered by Android screen. No matter what I did I couldn't get passed this screen.
I can't access Recovery Mode. I can access Download Mode tho. I tried flashing stock firmware, it flashed but nothing happened I got the same screen.
I flashed latest firmware downloaded from Frija. I didn't flash the wrong firmware because I tripled checked it with the information gotten from the Download Mode screen.
OEM and FRP locked, so suggesting TWRP is useless (believe me I tried).
Also, I charged the phone fully, nothing happened. I let the phone discharge completely then connected it to the computer, nothing happened. Lastly, I tried flashing combination firmware but it failed every time because my FRP is locked.
Is there anything I could possibly do?