Phone keeps rebooting for some reason, I've tried MiFlash/EDL/TWRP, tried multiple roms, even original MIUI Global/Dev/Stable..
I can get it to flash/boot, but it won't stay on long enough, just reboots.
I've edited rawprogram0.xml to flash persist.img even did it in twrp terminal, still no go.
Only time it won't reboot by itself, is in EDL/FASTBOOT mode. It reboots itself in TWRP/recovery sometimes.
Phone dead? Or something else I can try.
My first thought was an UV/OC issue but you said it's happening in TWRP too. Have you tried running a custom kernel and played with different governors? At this point I am thinking it's a hardware issue; bad memory that may be causing reboots. Is there a memory test/disk scan you can do to determine the health of the two?
abadidea said:
Phone keeps rebooting for some reason, I've tried MiFlash/EDL/TWRP, tried multiple roms, even original MIUI Global/Dev/Stable..
I can get it to flash/boot, but it won't stay on long enough, just reboots.
I've edited rawprogram0.xml to flash persist.img even did it in twrp terminal, still no go.
Only time it won't reboot by itself, is in EDL/FASTBOOT mode. It reboots itself in TWRP/recovery sometimes.
Phone dead? Or something else I can try.
Click to expand...
Click to collapse
Try changing sim card, or just removing it.
Not very likely the problem, but easy to check.
Related
Good morning guys,
I'm not sure how to explain the problem.
It started when I downloaded Telegram (Whatsapp + encryption = <3)
The phone crashed and the problems began. Everytime it started, its trying to download Telegram again and sais, that there is an error.
Also it randomly crashes.
And somehow my phone is loading a "image" each time its starting.
That means, i can flash, change, root, whatever I want to do, but as soon as I restart the phone, its booting into the same.
Hard to explain. Whatever I changed, send or recieved - dissappeared.
TWRP somehow also doesnt work, its not even booting in it.
Also, I cant get into the Bootloader, as soon as I do the Vol+ Power combination the Samsung logo appears and nothing happens, i have to pull the battery our to restart it. Well, the phone vibrates once, but thats all.
In the download-mode Im able to flash with Odin, but that doesnt changes anything after the restart.
Im not sure, maybe I clicked RE-Partition while trying to fix it or my flash wasnt clean or sthing like that, but atm the phone is unusable.
Hope you got some ideas
-maverick_skaw
Hi,
I have the same problem.
Somebody, any idea?
MaverickSkaw said:
Good morning guys,
I'm not sure how to explain the problem.
It started when I downloaded Telegram (Whatsapp + encryption = <3)
The phone crashed and the problems began. Everytime it started, its trying to download Telegram again and sais, that there is an error.
Also it randomly crashes.
And somehow my phone is loading a "image" each time its starting.
That means, i can flash, change, root, whatever I want to do, but as soon as I restart the phone, its booting into the same.
Hard to explain. Whatever I changed, send or recieved - dissappeared.
TWRP somehow also doesnt work, its not even booting in it.
Also, I cant get into the Bootloader, as soon as I do the Vol+ Power combination the Samsung logo appears and nothing happens, i have to pull the battery our to restart it. Well, the phone vibrates once, but thats all.
In the download-mode Im able to flash with Odin, but that doesnt changes anything after the restart.
Im not sure, maybe I clicked RE-Partition while trying to fix it or my flash wasnt clean or sthing like that, but atm the phone is unusable.
Hope you got some ideas
-maverick_skaw
Click to expand...
Click to collapse
R. T. F. the guides on general and Q&A section
Hi everyone, I'm having a lot of problems with my phone: last night, after it dropped to 0% battery life, it wouldn't charge. So i waited a while and ifinally managed to turn it on, but It wouldn't go past the Cyanogenmod logo. So i tried few things,first wiping cache, then factory reset from TWRP and I even tried the "Factory" option in the fastboot screen. Nothing worked, and it even got worse I think, TWRP says it's unable to mount /data partition and /storage partition. I don't know what caused it, and i don't remember the precise moment it became "unmountable" for the first time (since I've been trying to fix this thing for like 24 hours now).
Since i couldn't fix it via recovery, I tried looking for people who had the same problem on the internet, and I tried everything i could find. (like this: http://forum.xda-developers.com/showthread.php?t=2683787).
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Are you able to pull logcat?
Logcat command works, i don't get errors in the terminal, but in the text file there's only this line : "/sbin/sh: exec: line 1: logcat: not found"
Dmesg works though, I don't know if it's helpful
"
dagrot said:
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Click to expand...
Click to collapse
I have same phone, you mentioned you also tried to flash stock rom without success, did you flash the partition file aswell before flashing system and the rest of files ? Check the flashfile.xml file into the stock firmware folder to make sure you not missing anything.
Code:
fastboot flash partition gpt.bin
Good luck.
i'm on the same boat. It seems it's a NAND issue, but how come it happens randomly?
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Lynse said:
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Click to expand...
Click to collapse
If it's a bit rare, how come there are a rather interesting quantity of posts regarding that matter? I'd like to know WHY I can't write even with fastboot. There should be a way of unlocking the NAND / partitions. Even if I try to hard brick it, it's impossible.
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
jhonnyx said:
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
Click to expand...
Click to collapse
Unfortunately I didn't quite understand what that is about, if you happen to try it out let us know.
Anyway, if we don't manage to fix it, I guess I'm going to try and take it back to the store, since it is a common problem. Only problem is I'm on a custom rom and I can't even go back to stock and relock the bootloader, so I don't think they are going to replace it, but it's worth a try.
You can try by helping me to look for a circuit PDF from the board or trying it yourself.
I could try and disassemble it, but you're gonna have to wait a few days, I'm not at home and I'm gonna be back on the weekend.
As for the circuit pdf, I was only able to find videos and guides on how to disassemble it, unfortunately
Dude, no worries. Ive took the back out with all the screws, but I have nothng to make shorts with.... I'll come up with something. Take your time and keep me posted.
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
gbb14 said:
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
Click to expand...
Click to collapse
After that.... well.... after some research, we'll be needing singleimage.bin to use the blankflash utility for lollipop phones (mbm-ci 5.0 lollipop) so somebody can generate the singleimage.bin for us.
Once we have that, we can try to flash the phone at lowlevel to see what happens.
I will search the internets in hoping to find the schematics of this phone.
Keep me informed if you find it faster .
Cheers mate
we can connect through hangouts / etc.
look up for my user at gmail
Hi, this is my first post. I have tried to search and look through the question threads, but nothing seems to be close to the problem I have here, hoping someone can help me.
I have this Xperia TX, recently given by my friend, it can boot up ->sony->ribbon-> entering system->shutting down, it's not like a sudden blackout but more like a command sent telling the phone to shut down, it has the window saying shutting down and vibration at the end, but the shutting down is instant, can't operate yet. I made several approaches trying to fix it, these are what I have been done with it.
-Flashing different stock ROMs using flashtool, the flashing went perfectly without errors, and phone will boot and install new system until the setup wizard (languages, time etc) comes out on screen, and it shuts down right away.
-I used flashtool to unlock BL, succeeded.
-I flashed TWRP, it can boot into TWRP without any problems and working fine.
-I formatted the phone partitions using TWRP, working fine.
-I flashed cm-12.1-20151010, and same thing happened as soon as the system launcher comes out.
-And I flashed stock ROM again, the problem remains.
The phone won't charge the battery, so I tried using a separate charger avoiding 0 battery situation (I do see the battery icon showing 50%+ when it shutting down), and I also tried another lt18i battery (don't want to buy a new one yet in case the phone is dying), and there is no different.
I don't understand the problem, all the operations work fine but can't boot in system, doesn't seem like a hardware thing but what else can it be? I am not hoping to fix it any more at this point, but can anyone tell me what could possibly cause this? Can I read a boot up log somewhere so that I know what happens during booting?
I hope I didn't break any routine or do anything wrong here, if I did, apologies in advance, thank you.
Hello guys,
suddenly my Note 4 won't work anymore, it freezes and reboots every 30 seconds. The sim card won't be recognized and in the settings things like IMEI and the carrier are unknown. Deleting cache in recovery didn't solve anything. I didn't do anything, the phone wasn't rooted, I didn't try to flash something, it justs got semi-bricked one day! Then I got a new battery and then it worked again! At least for some hours. Then it froze and rebooted again.
So I tried to flash stock with odin. Didn't work, even with the pit file and different versions of odin. It stops right at the beginning.
It's a N910F if you want to know.
And yeah, KNOX counter still at 0x0. But I don't have warranty any more.
Thanks in advance!
When did this start? Funny thing I have a similar issue. Yesterday my phone was fine. Had it with me on my desk until I went to bed, plugged it in and thought nothing of it. About half hour after I get to sleep the phone reboots, I hear the TMO gingle. I paid no attention to it, about 15 minutes later it does it again. I shut it off and this morning it all went downhill. Phone won't stay on, keeps rebooting. It sometimes freezes and becomes unresponsive.. you name it, everything that could have gone sideways has.
Jhnsn said:
Hello guys,
suddenly my Note 4 won't work anymore, it freezes and reboots every 30 seconds. The sim card won't be recognized and in the settings things like IMEI and the carrier are unknown. Deleting cache in recovery didn't solve anything. I didn't do anything, the phone wasn't rooted, I didn't try to flash something, it justs got semi-bricked one day! Then I got a new battery and then it worked again! At least for some hours. Then it froze and rebooted again.
So I tried to flash stock with odin. Didn't work, even with the pit file and different versions of odin. It stops right at the beginning.
It's a N910F if you want to know.
And yeah, KNOX counter still at 0x0. But I don't have warranty any more.
Thanks in advance!
Click to expand...
Click to collapse
Probably your motherboard is dying.
Try to flash twrp recovery via odin and flash any rom and see if it works.
RIP mine is completely dead. Won't boot anything at all. Best of luck to you OP.
I have the same issue. Changed battery, nada. Flashed stock via odin, and it'll flash, and then it'll boot for a bit after flashing then freeze and go into bootloop, even if i try to boot into safe mode and try to boot into recovery. Flashing twrp with odin just makes it bootloop. I've tried every combination of things and can't get this thing to boot up properly. I'm convinced its a hardware issue.... perhaps processor going as someone above has mentioned?
I've been facing a weird problem with my G800H since yesterday. The phone will reboot constantly. It will boot into android, I will even be able to open apps, but it will suddenly reboot after a minute or so. I didn't do anything to my phone for it to start doing this. The weirdest part is that the rebooting will happen even if I am in recovery mode (TWRP). Also, the phone will automatically turn on if I take off the battery and put it back in, something that never happened before.
I use stock 6.0.1 (rooted) and TWRP 3.0.
Things I've already tried:
Charging it;
Safe mode (same problem);
Taking off SD card (who knows);
Wipe cache/dalvik (phone restarts before finishing);
Re-install ROM ( Download mode (ODIN) doesn't open, insta-restart after 'press volume up to enter odin').
I really dont want to do a full factory reset, only as a last resort, as i don't even know if it will have time to do so, or even if it will fix it. Does anyone know a way for wiping the cache without having to format it ( takes too long in TWRP so phone restarts before finishing ), or maybe have some other way of entering download mode, maybe with adb, or finding out what went wrong. Any sugestions on what to do or what happened?
I (my wife) have the exact same problem, I bought a new battery which didn't solve the problem.
Also tried a factory reset, didn't help either.
It is a non rooted phone...
Next try is a custom rom, hope it helps...
Install an app that records logs like Logcat, set it in record mode and wait until the phone reboots. Then look through the file, study what happens near the end when the phone turns off. You'll most likely find the cause there.