Guys, I'll explain what happened...
First, I bought the cell phone and a day later I changed the ROM, carrying out all the correct procedures. A few days later, I noticed that when I rebooted the phone, it performed some reboots, maybe two even giving the final boot and entering the system.
I changed the ROM, I needed to perform some procedures by TWRP involving Partitions (Maybe this is the problem) and finally... The cell phone called.
But a big problem came up, (less than thirty days after all this process) The cell phone when restarting, it has an extreme difficulty to get to the system startup... It was at boot and keeps rebooting forever, it's my current problem.
Some things I can't do anymore...
1) TWRP, I've tested several versions and none reach it, it just keeps rebooting and showing the logo until I decide to go into Fastboot mode.
2) Roms. I've tested some Stocks with several different procedures including ASUS FLASH TOOL, but I always run into the same problem, system rebooting and rebooting. Maybe it can even enter the system, but if you reboot it keeps rebooting all the time and LUCKLY will enter the system.
Guys, I really believe in two things:
# Motherboard problems
# Situations involving partitions, I don't know how to fix it
# Battery maybe? But it lasts a long time (When you don't have the rom stock)
my phone had 2 problems that caused bootloops.
first one was the battery. it was still lasting the whole day just before that problem started. phone batteries are weird like that when they fail. it was still showing over 4v with a multimeter, i could boot in the recovery or fastboot and it was staying on... but replacing the battery solved the problem.
similar problem is happening with my other phone, nokia 8 can last over a day on idle but if you try taking a photo with around 50% battery or below it's crashing and restarting.
second problem was the cpu. it was working fine on the stock rom but all the custom roms were bootlooping or lagging and crashing shortly after boot. i figured it out tho, it was crashing when the little cores were hitting 1.1ghz, modified a custom kernel and removed 1.1ghz from the frequency tables for little cores. now it only goes up to 1ghz and stable.
since you have the problem in twrp and on stock roms my first guess is the battery.
i tried connecting an external power supply directly to the terminals to test that, like 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"
}
and it was working. so i was sure that it was the battery. then ordered a new one.
you can try this method to confirm if it's a battery problem.
if it's a software problem then flashing the stock recovery and installing the stock rom via recovery or adb sideload should fix the problem. it contains all the firmware not just system image. it should fix any problem related to software.
and if it's a cpu problem like mine, you can try underclocking with a kernel manager. you need a root and should be able to boot for that tho. you need couple minutes to install a manager and underclock. if you can't even boot into the os you can't do that. you would have to flash a modified kernel first. but since you can't boot into twrp i don't think its the same problem.
90% chance it's a battery problem.
Interesting. A friend thought it was the battery. I'm afraid to buy and the problem is some partition or maybe Damaged Hardware... I'm out of action for this situation
just try what i did then. connect an external power supply to the battery terminals.
you just need a 5v charger and a cheap usb cable to sacrifice.
if it's working properly with an additional power then it's 99.99% battery related.
Related
After replacing the battery my phone stopped working. To be exact the phone shows the following behaviour.
I press the power button and everything goes fine until the phone boots into android. Then a message appears saying that the device will shut off and as you can easily guess the phone shuts off. This is the same message as the one appearing when the battery is low.
http://oi64.tinypic.com/mr67ut.jpg
I removed the new battery and installed again the previous but the exact same thing happens.
If I connect a charger cable or on my computer the phone starts booting but this time everything goes super slow. When it boots into android, this time the phone does not shut off after the popup message but reboots again. And as long as the usb cable stays connected the same thing occurs again and again. Tried entering recovery/download mode without success.
The huge problem with that situation is not the phone itself but the data that I have not backed up yet.
Any help is welcome.
My phone is an lg g2 d802 running stock 4.4.2 rom, unrooted.
cabrinha said:
After replacing the battery my phone stopped working. To be exact the phone shows the following behaviour.
I press the power button and everything goes fine until the phone boots into android. Then a message appears saying that the device will shut off and as you can easily guess the phone shuts off. This is the same message as the one appearing when the battery is low.
http://oi64.tinypic.com/mr67ut.jpg
I removed the new battery and installed again the previous but the exact same thing happens.
If I connect a charger cable or on my computer the phone starts booting but this time everything goes super slow. When it boots into android, this time the phone does not shut off after the popup message but reboots again. And as long as the usb cable stays connected the same thing occurs again and again. Tried entering recovery/download mode without success.
The huge problem with that situation is not the phone itself but the data that I have not backed up yet.
Any help is welcome.
My phone is an lg g2 d802 running stock 4.4.2 rom, unrooted.
Click to expand...
Click to collapse
Have you tried flashind official android 4.4.2.kdz firmware?
I cant connect to the phone via computer.
cabrinha said:
I cant connect to the phone via computer.
Click to expand...
Click to collapse
You dont have download mode?
Last screen before shut down. It says that the device is going to shut down.
{
"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"
}
Hi,
I have flashed back to a stock rom for my s7 edge via odin G935FXXU1DQBF_G935FTEL1DQB5_TEL with a complete wipe as recommend.
I flashed it according to the instructions for ODIN however after it tried to install apps it is now stuck in a black screen with the soft keys lit. The blue light is not on.
I cannot force it to turn off at all, I've tried every combination I know however it is stuck on. Odin did complete and it did show up with the samsung logo and starting install
apps but that was it.
Any ideas on what I can do? I would love to rip the battery but hassel .
Thankyou
{
"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'm hoping someone might have a quick way to discharge the phone without opening it up and disconnecting the battery. Thats all it does and has been like that for the last 6 hours. LAst time I checked it had 68% battery
So, volume down + power does not work?
If enabled (and host authorized) try adb.
Otherwise just wait a couple of days... (calling the phone may speed it up if registered to a network)
Thanks mate. I can't seem to find it in device manager and I have tried any sort of recognition to acknowledge a device. Tried in MAC OSX, Fedora 22 and win10 and get nothing . Wish I could strap something to the port to try drain it but that will probably cause more bad then good.
Volume down + Power nothing and about every other combo as well.
So just a update. It took 9 hours but it went flat and I am restoring via smart switch.
Thank god , I'll probably just do that next time as I think that not wiping everything on the phone caused issues with the stock rom setting up. My bad but hopefully someone gets help from this in the future.
So on superman rom it took a few days but now its froze and i'm pretty sure i might have a hardware problem. I'm thinking I'll have to remain stock or I've got a hardware problem . Can't stand life without root/better battery savings but I had 52% battery on superstock rom so it's going to be a long night/day to wait for it to drain hopefully.
Hello to all who read this.
My phone only shows this two modes but does not get into recovery mode at all, it only shows the first step and then it reboots form the start:
{
"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 can't get into TWRP, even if I flash a new recovery with fastboot and run the boot command.
That said I can open fastboot mode and qfil mode.
The problem occurred last night I was watching youtube and in the morning the battery on the phone was fully drained and I couldn't boot into the lineageOS 16 that I'm using (had for 1 month).
The LED light in the top right corner is never lightning up, only when is fully drained then it shows the battery is empty and some blinking red light on the LED.
Well I tried :
- to install/run TWRP it couldn't let me run it
- to qfil the stock ROM and it did let me flash it but it was the same when I pressed the power button after the flashing process
- to use the "update" command in fastboot mode to update the stock ROM on to the phone and it said:
error: update package 'update.zip' has no android-info.txt
Does anyone know how to solve this?
Please help me!
All best,
Jasmin
I had the same issue with X727. Your battery is faulty and needs to be replaced. I got mine from this guy and received an original LeEco battery albeit with 2016 manufacturing date but it works well and phone does not reboot anymore.
nwaves said:
I had the same issue with X727. Your battery is faulty and needs to be replaced. I got mine from this guy and received an original LeEco battery albeit with 2016 manufacturing date but it works well and phone does not reboot anymore.
Click to expand...
Click to collapse
Okey, thanks for the replay.
Hi, Jasmin slayer!
Did that Work for you to replace the battery? If not, try to flash some bootloader and verify , If twrp Boots again after flashing. Remember you need twrp 3.3.1 for Andro Pie!
LupusC said:
Hi, Jasmin slayer!
Did that Work for you to replace the battery? If not, try to flash some bootloader and verify , If twrp Boots again after flashing. Remember you need twrp 3.3.1 for Andro Pie!
Click to expand...
Click to collapse
I have the same problem my Le pro 3 x720 device. It is in a boot loop. I wonder if changing the battery will work.
Howdy everyone...
OnePlus 7t Pro McLaren edition (International Edition **NOT T-MOBILE**)
Model: HD1913
Current Software Build: Oxygen OS 10.0.5.HD01AA (OTA update when I first unboxed).
I am having issues trying to return to stock. I rooted the phone with a combination of a couple guides found here (https://forum.xda-developers.com/7t-pro/how-to/10-0-3-patched-boot-image-oneplus-7t-pro-t3986351 and . I noticed after doing that I was missing the stock Oxygen apps and my build information was missing data. Not a huge deal, but I need to wipe the phone and start from scratch anyway, for other reasons. I decided to go back to stock if I have to redo everything anywhere.
First thing I tried, I got the stock firmwares (https://forum.xda-developers.com/7t-pro/how-to/oneplus-7t-pro-repo-oxygen-os-builds-t4003455). And this is where my issues started. My software build is weird... I have the HD1913, however my software build is HD01AA. Per that post, I should have HD01BA. I grabbed both of them for giggles, put them on my storage and booted into TWRP. Tried to flash the HD01AA (since that was what I have now), and it failed. Tried the other one, same issue. I'm getting a bunch of errors while trying to mount the system ("System unable to mount: invalid argument").
Second thing I tried, was to use the built in software update that OnePlus says to use (through the system update). It wouldn't install them (surprise).
Third attempt... Using the MsmDownloadTool (https://forum.xda-developers.com/7t-pro/how-to/op7tpro-unbrick-tool-to-restore-device-t4002909) I downloaded both versions cause I don't know which to use, and followed the instructions to get the phone into the mode. Turn the phone off, hold the vol up button and plug the cable in (very simple). It shows up connected in the software. Exactly 5 seconds later, the phone reboots and boots normally... I repeat this process aprox. 2.3 million more times. It does not matter what USB-C cable I use, the port on my computer, or how long I hold the buttons. The phone will boot into the download mode (or whatever it's called) show up as connected in MsmDownload and then reboot.
The phone works. I am still able to boot it up.... All I want to do is get this phone back to stock. I don't HAVE to, but now that it's fighting me, I have to beat it...
imgur.com/a/KhBGwao
{
"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"
}
Okay - After sacrificing an iPhone to the Android God, I got it.
Instead of using the button combination to get into EDL Mode, I found an article that gave an adb command (adb reboot edl) to get to it. It did not reboot this time, and I was able to flash HD01BA to it, which matches what the phone should have...
My Xiaomi Redmi Note 7 (lavender), gave Brick after formatting the cell phone, which was with a Lineage ROM, but immediately the cell phone would not boot, the ROM corrupted and to make the recovery worse, the TWRP, apparently it ended up corrupting, it does not enter and hangs in the TWRP logo.
Fastboot mode still works, but I can't get any device to recognize it, nothing just happens. I've tried ADB, MI Flash and some other programs, but it ends up not working, My computer can't recognize the Note 7. I switched cables and tried different ways, using my second phone as a command prompt, but it still didn't recognize it. Just need to try another computer
I wanted to know if the problem is reversible, because if not, I have a screened brick
I think the connector may be defective but I think it's unlikely as it worked perfectly before
If any expert can help me, that would be great
Sorry for the robotic English, it's not my mother tongue
1Henryx said:
My Xiaomi Redmi Note 7 (lavender), gave Brick after formatting the cell phone, which was with a Lineage ROM, but immediately the cell phone would not boot, the ROM corrupted and to make the recovery worse, the TWRP, apparently it ended up corrupting, it does not enter and hangs in the TWRP logo.
Fastboot mode still works, but I can't get any device to recognize it, nothing just happens. I've tried ADB, MI Flash and some other programs, but it ends up not working, My computer can't recognize the Note 7. I switched cables and tried different ways, using my second phone as a command prompt, but it still didn't recognize it. Just need to try another computer
I wanted to know if the problem is reversible, because if not, I have a screened brick
I think the connector may be defective but I think it's unlikely as it worked perfectly before
If any expert can help me, that would be great
Sorry for the robotic English, it's not my mother tongue
Click to expand...
Click to collapse
For fastboot you just need to update the drivers, run the same process you did sometime, when it, firstly, worked. Remember that a corrupted device must have the drivers updated, a kind of communication lost, nothing more.
I´ll upload some screenies from the process you need to do:
{
"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"
}
Once you get it, repeat the process, i.e. boot to recovery and flash the ROM.