I am running the factory preloader and lk.img
I rooted my RN8Pro, using LR Team TWRP, running Riru Edxposed. I rebooted the phone while charging and suddenly it I'm in this weird black screen where at the bottom it says Written 137M and at the top it says
... triggered by MRDUMP_KEY ...
... kernel detected
Userdata size 53353Mb
Output to EXT4 Partition emmc:
Pre-Allocate starts at LBA: 77824
SYS_COREDUMP starts at LBA:79270
Not all of it was showing up on screen.
Can someone please explain what it's doing and how to fix it?
Update: Phone rebooted, not into MIUI though. Now its just black screen, I can't get into recovery, nor I can get into fastboot mode when I select fastboot mode I'm greeted by a bunch of chinese options. I believe this is the factory options.
I can access adb through this, but it is unauthorised so I can't even call adb reboot.
Update, I clicked emmc on that chinese menu and I've ended up booting into android. But it's a fresh install, not sure what is going on to be entirely honest lol.
KworrV said:
I am running the factory preloader and lk.img
I rooted my RN8Pro, using LR Team TWRP, running Riru Edxposed. I rebooted the phone while charging and suddenly it I'm in this weird black screen where at the bottom it says Written 137M and at the top it says
... triggered by MRDUMP_KEY ...
... kernel detected
Userdata size 53353Mb
Output to EXT4 Partition emmc:
Pre-Allocate starts at LBA: 77824
SYS_COREDUMP starts at LBA:79270
Not all of it was showing up on screen.
Can someone please explain what it's doing and how to fix it?
Click to expand...
Click to collapse
yesterday i have experienced the same issue and i have seen that Written 137M is increasing progressively like 137M 180M 210M... so i have just waited and didn't touch anything and it did reboot. Everything is working smoothly now.
I just held the power button to force shut down and turned on normally. It seemed to boot into android with no issues. It's kinda risky though, not sure if I'd recommend doing that. Also the factory preloader seems to have different power on button combinations, as pwr+vol up will load another menu that will allow u to boot to recovery or kinda like safe mode for windows, and pwr+vol down will load you into factory qc testing stuff (all in Chinese). I just use adb or other apps to boot into recovery because honestly I'm kinda scared to fiddle with that stuff given how easily this device gets bricked.
That's odd, for both of you it seems that it just rebooted fine, I completely lost android for some reason, had to reroot and flash twrp, edxposed and all that again! All seems to be working fine at the moment although getting random reboots here and there, not sure why!
Answer
KworrV said:
That's odd, for both of you it seems that it just rebooted fine, I completely lost android for some reason, had to reroot and flash twrp, edxposed and all that again! All seems to be working fine at the moment although getting random reboots here and there, not sure why!
Click to expand...
Click to collapse
Hi, I had faced the same problem, the issue here is that TWRP is just set to 0% brightness that means that everythink is fine but you need to go to the settings and than adjust the brightness. For an screenshot just answer.
Related
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?
I enrolled in the Beta Program, and upgraded to Android O. Everything was great! Until I rebooted, things were acting funny. I have played with enough nightly builds and custom roms to realize, I need to factory Reset.
Bootloop.
I was able to get into the recovery mode: and then did another factory reset from here--
Now my recovery mode is only, "No Command" Vol up + power did not get me a list of options again
So, I followed this guide: https://forum.xda-developers.com/nexus-5x/help/guide-fix-bootloop-locked-bootloader-t3608679
I got here: "click on all buttons and flash all partition files from extracted archive - except recovery ,userdata and cache."
And still was boot looping
So, I went to this guide: https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Installing the "LGUP_8994_DLL_Ver_0_0_3_23" Looks rather uneventful.
But, I booted up with Vol UP+Power
and got to the Firmware Update screen.
It's been sitting at 0% for twenty minutes... "Do not unplug the USB connection until the process is completed"
and "LG USB driver installation is needed before starting LGUP"
and I will need to close my laptop in an hour
Im lost
Edit:
Okay, I got the LGUP to install a new TOT file--
LGH791 - resulted in freezing on "google" after reboot
LGH790 - also frozen on "google" after reboot
However, my recovery mode is no longer "No Command"
So I'm going to try to Sideload an update
I Has an operating system! I'm going to update my firmware to 791 now
hmm.. .no option for "BIN" so I'm going to leave it-- i was supposed to go an hour ago
[Follow-up] My sensors were "malfunctioning" with LGH790. Upgrading to LGH791 fixed all of my sensor issues.
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.
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.
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
I would just like to reply here and add my own potential fix and also would like confirmation that it would work.
So I have a SM-G996B in a boot loop which returns a 'fs_mgr_mount_all' error. Possible to reboot into recovery mode, cleared cache and restarted bootloader etc with the same boot loop. Powered off and connected to PC for Download mode for ODIN recovery but upon pressing volume up, it then restarts again so Download mode recovery is impossible.
I know however that Developer options and USB debugging was enabled on the device as well as unlocked boot loader. I was able to download the correct original stock OS based on the PDA , CSC and Android version.
I have then installed the latest ADB software on my PC and Samsung USB drivers.
By then rebooting into recovery mode, I have the option of 'Apply update from ADB'. I have then confirmed the device connects using the ADB devices command.
I would like to clarify one thing however. I want to keep the user data at all costs. By using the stock firmware and renaming as update.zip, will it use the HOME_CSC and not the CSC file? If not would it work if I open the zip and remove the CSC before re-zipping to make sure?
Thanks
Reebee said:
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Similar issue with same phone. In a bootloop after trying to root. None of the button combinations have worked for me, for the past several days.
Tried powering the phone off for the whole night.
When connected to the PC shows phone is in recovery mode via adb (blank screen though).
Want to know how to get into DL-mode, guaranteed.
Got to DL mode by pressing vol up + down + power + usb cable connected in PC and phone. However, couldn't do anything there, but maybe you can
Also, phone is still working and I still have no clue what was the problem and what fixed it.