After using a custom ROM for several months, my DerpFest OS started experiencing frequent auto restarts. It's normal for custom ROMs to have occasional auto restarts due to their experimental nature. Despite switching to different custom ROMs and kernels, the issue persisted, and my device would still auto restart.
To address this, I decided to flash the stock ROM using MiFlash Tools, the official flashing tool. However, during the flashing process, an error occurred, specifically "error: Writing 'modem'." I checked the MiFlash Logs, and this error message was displayed.
I also attempted to flash the stock ROM through Platforms Tools bootloop, but encountered difficulties in the process.
In my attempts to resolve the issue, I installed different versions of the custom recovery OrangeFox (1.3 and 1.4), but I couldn't successfully boot into recovery mode.
Finally, I tried flashing a custom recovery called SHARP Recovery, and the flashing process was successful. However, when I tried to boot into recovery mode, I encountered a battery error.
Currently, I can only boot into fastboot mode when the device is connected to a charger. When I connect it to a PC, I receive a battery error message.
( M2010J19SG )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
hi
i am having issue with my galaxy s6 edge G925T phone was working properly battery got runt out so after when i charged and did power on after phone is not powering on and got bootloop
i found a post regarding this on xda forum followed that all method as they mentioned but unsuccessful
before i had the same model and got the same issue after when i flashed compatible kernel on g925t problem was sorted out , but with this phone same model when i flash kernel to get it out from boot loop then
the kernel doesn't get flashed and i get the following message as in the pictrue
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same thing happened to me flashing a Tmobile rom. To prevent this you need to go through the setting and allow unlocked bootloaders (or something like that, currently flashing my phone to look it up) but this will prevent this lock from triggering. How I got past this? Odin'd back to stock and flashed everything again.
Bro phone doesn't go to main windows how I can go to setting it's only stuck on bootloop
Have you tried flashing the stock image in odin?
Stock rom from sammobile?
Yeah, you'll need to get familar with the hardware keys and how to boot into download mode with them. Typically I'd link you with instructions but I think googling it yourself will do you some good. Do some research and be sure to answer nicely to those who offer help.
Ok, so to begin with information that this is my old phone so I use it for fun.
Earlier I installed Android 4.4.2 on him, overclocked him and everything was fine (except low RAM and little heat problem xD).
Yesterday I wanted to install Android 5.0 and I copied files, went to recovery mode, wiped data, then install ROM and everything. Then I turned on phone for first time after installing, and phone pops this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I suppose I should have rebooted phone but I clicked Reset phone. After that phone rebooted himself and after cyanogenmod and devconnection logo, TWRP logo start flashing. And every time I tru to turn phone on booting stops on TWRP logo and it start flashing.
I turned it off again, and tried to go to recovery mode but unsuccessfull, tried it couple more time same result. Then I tried to go to download mode and I was successfull.
So I went to computer, download Odin (few versions just in case), downloaded TWRP and CWM recoveries for my phone. I opened Odin, connected phone in download mode (Added! poped in Odin) and tried to flash TWRP on my phone. Then Odin was stuck on "setup connection", older versions of Odin aswell. Then I changed ports, versions and even computers (tried even on laptop) - same effect.
So my question is can you help me do factory reset or how to flash new recovery?
Any suggestion is welcome.
bump
Hi all,
So, I was running fine with CROMi-X KitKat, but wanted to upgrade to Marshmallow (to install sw not supported in KitKat), so decided to try KatKiss 6.0. It's been years since I've played with flashing ROMs, but I did a little reading to refresh my memory. Then I rebooted into recovery (ClockworkMod), backed everything up, then wiped everything, formatted /data, and tried flashing the KatKiss zip file. At that point, it just sat there forever at the ASUS logo screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried several times to boot back into recovery by holding the Vol+ and Power buttons, but it either doesn't boot, or boots to the above screen. I've connected it to my Mac w/ the Android SDK Platform Tools, but adb doesn't see any device listed. [I've got an old Windows laptop (XP?)] I could use if it will do something the Mac can't.]
Any advice on how I can save this tablet?
Have you found a solution finally?
Well, I haven't found a solution, but after letting it sit unplugged for months, I came across it today as I was straightening up. I plugged it in, waited maybe half an hour, and was able to boot it into recovery mode. I was then able to restore from a backup, and damned if it didn't reboot and come up just fine. No idea why it wouldn't boot into recovery before, but I'm happy camper!
Hello. I have motorola x4 Indian variant (xt1900-2). I have bootloader unlocked on my device. Few days ago I had Pixel Experience 12 running on my phone, and I tried to update it to Pixel Experience 13 using PixelExperience's own recovery through ADB Sideload. It worked but after that I tried to flash gapps using same way but it was not working. I thought TWRP recovery can install it So I flashed TWRP zip using same method in recovery's update using ADB Sideload option. Recovery got flashed.
Now, my phone is bootlooping since then after it rebooted to system after flashing twrp zip. I can access fastboot on my phone, but any command I enter in fast such as 'fastboot boot recovery.img' gets stuck forever.
Also, sometimes commands dont even work. Fastboot says unknown command. I tried using different cables on diffrent ports including 2.0, 3.0 ports, and also using c-to-c type cable but still no luck. I even tried to downgrade to Windows 10 from 11. Still same issue. I Can't boot to recovery, cant flash recovery, cant boot into OS, just fastboot is working.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help me in this case. I have original firmware available for my device. I tried flashing it but gives same error command not found or gets stuck forever.
So I wanted to do a fresh install after experiencing some issues. But doing a factory reset in recovery mode didn't completely fix my issues because play store stated that my device wasn't certified. The state of my phone at that time was; unlocked bootloader, no root and developer options disabled. If having the bootloader unlocked makes the device not certified then thats news to me.
But I thought whatever, Ill root the phone. Using the boot extracted from payload.bin from the full ota with the same version and patched that in magisk. Booted using the patched image without flashing and patched the stock boot from magisk.
That resulted in a bootloop, flashing the stock boot didn't resolve the issue. Tried both slots. I then tried to flash the full firmware in fastboot/fastbootd and that resulted in fastbootd being not bootable anymore for the current slot. I then tried in the other slot to flash the firmware by resizing all logical partitions and that ofcourse resulted in that fastbootd is no longer accesible in any slot, recovery is unaccesible and fastboot restarts every 5s back to fastboot. As some sort of last measure I locked the bootloader again which didnt help and now I cant flash anything.
So now to the real issue. I know that EDL is my only solution now and I have gathered all the tools and firmware needed. I can boot it into EDL with some driver errors
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The problem is that even in edl mode the phone reboots after 5s to fastboot.