Everytime i try to boot my phone its shows a warning symbol and the following text "This phone has been unlocked and it can't be trusted your device will boot in 5 seconds" or something like that, now this is normal for my phone as it just skips it and boots normally but this time something unexpected happened. After the that another text appears saying " Your device has been unlocked and the boot image isn't working" and it just keeps repeating those 2 stages.
Things that might be important to mention
-I had an sd card on it until i bought a new phone and removed it
-I have installed TWRP in the phone (pretty sure its gone by now)
-And it cant charge because it tries to boot when it can't so it just repeats these stages until it powers off.
How do i make it boot into the system?
Now ,after 6 hours, it cant even go to the first stage with the "device can't be trusted" it just sits with its orange light and consumes power, nothing else.
Try to flash stock rom, maybe you install the wrong rom version
Related
So, it's been a fun couple of days.
I was 'tabling' away, as usual, and my tablet suddenly reboots (if it matters, I was just opening FPSE, as I'd done dozens of times before; Skype was on background; every other process was finished). 'Ok', I thought, 'that's weird'. When the tablet's done rebooting, the lockscreen shows up, and when I try to unlock it, the scren just freezes. Couldn't turn off the screen, nothing. So, I force a shutdown by pressing the power button.
When I try to turn it on again, it just stays stuck at the Google logo screen. I tried going in through recovery, but the result is the same. Select recovery, Google logo shows up, little android with exclamation point doesn't.
I tried formating through fastboot -w, but the process just keeps endlessly deleting, while doing nothing at all. I have to quit command line, shut down tablet or unplug the USB cable with a command line message showing up (I once left it while I went for a coffee; two hours of deleting nothing at all). Same thing with trying to unlock bootloader to maybe going to recovery after flahsing a custom recovery.
I don't mind losing everything I had. All pictures are recuperable and the rest is either in the cloud or in my phone/PC. The most annoying thing would be to set up the whole thing again, wich is no trouble at all (that and going through PvZ2 and TD Bloons 5 from the start :crying: ).
I was using Android 4.4 (KRT16S), everything stock.
Is it bricked, soft-bricked, did the aliens get it? I am e-mailing with someone from the store I bought it from, hoping for a solution or (worst case scenario) RMA, but I would rather solve this without having to.
Try flashing system.img, recovery.img, and boot.img, by hand.
Your emmc likely got corrupted
How do I do that with a locked bootloader and no access to recovery? Is it possible?
A little background on the issue:
I had my phone on the charger for awhile, saw it at 100% so I unplugged it, put it into my pocket, and thought nothing of it. Next time I pull it out of my pocket(about 4-5 minutes later), I find that my phone has restarted itself and won't boot whatsoever. I then tried to boot into recovery to see what was what, and found I couldn't do that either(using vol up+power). I found out that the only way to get into my recovery is to plug into the pc, then use vol up+power(?????). After getting into the recovery, I found that every time I boot into it I'm greeted by a message saying "Keep system read only?", with option below to swipe to allow modifications. It doesn't seem to matter which I choose as neither do anything. I look at my drives and see that my internal storage is listed as 0MB. I then tried restoring a Nandroid backup I made a month previous, but I was greeted with a log saying the phone failed to mount literally everything, followed by "invalid arguement" after every line(would post logs but my phone is currently stuck in a loop in an ruu). This happens with anything I try to do in TWRP(running 3.0.0.0), whether I try to change the filesytems to FAT or try flashing a new ROM(seemed to open fine with Aroma installer, but gets stuck writing to /data). After exhausting everything I knew to try and everything on the Interwebs, I resorted to trying an RUU. It opened fine, recognized my device fine, but is now stuck doing the same process over and over(currently at 46 min). I'm running ViperOne 3.5 with an unlocked bootloader and S-on. I'm currently at a loss of what to do, and would appreciate any and all help. :3
Corrupt nand I think.. It cant find any partitions.
Beamed in by telepathy.
Any ideas on a solution?
Hello, I would like to first tell you the story my LG G4 has gone through and then I tell you the error.
So, at first my phone was working absolutely properly. I accidentally deleted some pictures and to do a recovery, I had to root it. And rooting would be useful for later so why not do it?
So I first unlocked the bootloader through the code from the LG site. After unlocking, the phone reset (because it would be just too good to make some memory changes and nothing more.) But allright. Then I was ready to root. I just booted the phone, everything was fine. I unlocked the developer mode and opened ADB. I rebooted to recovery through
Code:
adb reboot recovery
I was expecting to see some menu with buttons (but that would be just too good). However, I saw just android with a red triangle in the middle. Nothing more. No response to buttons, nothing.
So I thought. Allright, let's boot into recovery using hardware buttons (vol down + power) at startup. Unfortunatelly, it seemed like there is no such mode System just normally booted (and that was just after bootloader unlocking. Recovery mode goodbye.).
I tried to send commands to the phone using diagnostic port. Unfortunately, it responded by FAIL to every command.
I reboot to bootloader and booted an image: "boot-em.img" (from here: google: how-to-root-lg-g4-on-android-6-0-marshmallow-20a20b-firmware. I'm a newbie here. thx for understanding.)
After that the console uploaded the image and booted successfully. Then, however, system started to boot up and was endlessly booting (LG boot animation) till the battery was critical.
I was able to access the EMI number through volume-down button and volume-up button pressed simultaneously.
I was also able to access some factory-reset dialog by holding volume-down and pressing power-button several times. I choosed to reset everything and then accepted it with one more 'are you sure dialog'. System rebooted and was stucked in the LG boot animation.
Then I got to download mode, since recovery mode was lost in hell. Through LG-UP I flashed the original KDZ firmware and everything got back to normal, but recovery mode was still inaccessible through the hardware buttons. I got through the process of setting everything up, getting developer, rebooting to bootloader and I booted TWRP.
TWRP loaded and it responded to double-tap on screen to wake it up. I just checked the menus and let the phone sleep.
After several hours I went back to the phone and double-tapped on display. Nothing. Phone was not responding. I pressed the power button and the phone restarted (I think. It either restarted into the system or was not responding to power button.)
So I got to the system and again rebooted to the TWRP (through fast-boot). I tried to back-up one partition to the disk. During the process phone had turned the display off. So I double tapped. Nothing. I removed the SD card and the phone woke, saying that back-up process was not able to complete. Suddenly it stopped responding to double-tap. It woke up through an interrupt. I re-inserted the card, successfully backed-up the partition to the SD-card and I left the phone laying on the bed plugged in the charger. It stayed that way for 4 hours or so, doing nothing. All of a sudden, a yellow screen was there, (and that's a screen of absolute death that was never supposed to come. Little I knew.) saying that an unexpected critical error happened and to do a memory dump, insert a cable, set up some communication (I don't remember what it was, didn't take a picture of it.) and it could send the memory dump to PC or somewhere. I thought to myself. So, the application is not so stable after all. It said that to reboot just press the power button or something.
And now the problem comes:
The first start: Bootloader booted, LG animation went on and finished. The starting up apps dialog came rolling. Then, system restarted.
The restart: Bootloader booted, LG animation went on and freezed. Then, the phone restarted.
Second restart: The same thing as the first one.
Fourth restart up till now: Bootloader tries to boot and restarts before the LG animation.
I got to download mode and it restarted even there. After re-inserting the batterry I can sometimes get to the Firmware Update window and communicate. There I flashed the official firmware again.
No success, as if I didn't even do it. It restarts before the animation.
Can I do anything with the phone? Hopefully I can. No hardware problem occured (except for a situation where the error could fry the wires inside the mighty System On Chip.)
For the software state I cannot even tell but I might say it's cooked just wrong. That's why I came here.
I know I did some pretty stupid steps. But the error was not done by me. It worked fine and after the yellow screen which came by itself, it just (some bad words).
Thanks for replies.
Phone: LG-G4 H815, European market
Solution
So, I was looking around and believe it or not, this problem disconnected the pins on the motherboard's snapdragon 808.
I think this happened: The device, although it was heated many times during its life, it withstood that so far.
However, a longer run of the TWRP had finished it off. Memory got disconnected while running and it threw a yellow-screen.
Pins got disconnected and from then on it was just a standard common LG bootloop issue.
The continuous process of dying (First it partially loaded, then only animation, then nothing) is explained by this fact that the pins were so-so there and a couple of reboots just got it totaled.
Temporary fix:
Pre-heated the memory chip to 250°C using Hot-Air gun. After 18 seconds at this temperature I pressed the memory on top of the snapdragon down to the board while cooling.
Then I added a little metal square on the metal part that is covering the system on chip. This part is over the SOC where before there was just some tape.
This can work for several days in sleep mode or a couple of 'heat-demanding' operations on the phone.
Permanent solution should be to reball the memory chip on the snapdragon. That's my next step.
Hello everyone,
a friend of mine is having problem with his M9. He recently downloaded an update to the phone, but after restart the phone no longer boots, says 0% battery and would not charge (just keeps heating). After a while on the charger it tries to boot (white screen with HTC logo), but after like 20 seconds it reboots.
I can make it enter the "service menu" (or how is it called) - white screen saying "Software status - modified, LOCKED, S-ON" and some menu items (I would post a picture but the forum won't let me because I am new...)
the problem is that Recovery mode does not work, there is just black HTC logo in infinite reboot loop. Reboot to bootloader just reboots to the same menu. The download mode basically says "Failed to boot to download mode. This build is for development purposes only..."
If I plug the phone to PC, while the menu is present, I hear a sound that is was plugged to PC, but a second later it's unplugged, so I was unsuccessful trying to make some sense to it using ADB.
Can the phone be saved? Thanks for help
Whats annoying is that the phone keeps rebooting until it runs out of battery power, I haven't found a way to prevent it from rebooting. So-called "smartphone"...
I tried to update the firmware using RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.23.617.1.exe, but it said I don't have sufficient battery charge. So I plan to use the Fastboot-battery-recharge.bat overnight to give it a charge.
The problem however is that the command
Code:
fastboot getvar battery-voltage
returns "battery-voltage: " without the voltage itself. Anyone experienced this? I am using the latest minimal ADB and fastboot (1.4.3)
BTW the phone is originally EE UK.
So I had the RR-N-v5.8.5-20170926-n7100 custom os installed on my GTn7100 phone. Yesterday, the battery was drained. I had the wifi on and it was consuming battery very fast. So when I charged it to nearly hundred percent, the phone lagged crazily. I even noticed that the arrangements of the icons of my apps were changed. Then it hanged for about 5 seconds (the screen was on home) and then it went off. I was really confused as to what just happened. And turned it on, the phone is not booting anymore. It's just stuck on the "samsung galaxy gt n7100" boot screen (it's not on loop). I thought it's just some random bug and went to restart it again but to no avail. I had the TWRP 3.0.2-0 installed and thankfully it's still working after pressing the combination. At the start, there is a prompt about 'unmodified system partition...' and I thought factory resetting the device might resolve it, but to no avail again. The process was succesful but in the terminal, there are errors in blue line that says that there is no storage to wipe or something like that. And there is also a prompt that the device has no os installed. Even in the mount settings, when i select a storage, the prompt says that the 'Internal storage (0mb)'
What to do?
I recommend flashing the latest stock ROM with Odin as a first step. If the phone boss properly, then you know it was a software problem.