First of all, If I am copying an already existing Post I am sorry for that but I think i found nothing similiar to my "weird" situation here.
Now to my problem (with a short intro tho) :
I had my OPO for a half year, when i decided to root it. When i did this, I was a total rookie, so I just followed steps/guides I've found in the Internet. I unlocked Bootloader, installed TWRP-Menu and finally rooted my device. Everything went totally perfect for me and my device was running smooth and without any problems. But after some dirty- and some clean- updates(always only the cyanogen updates that were showen on my phone), my OPO randomly shut down. Earlier on, I made a Backup. So i wiped calvik&cache and thought i lost all my problems. But in the last weeks, new problems occured. So i started looking for them in the Internet. I found out, that i had a "bootloop"/ Softbrick on my phone. It randomly shut down and it sometimes felt like especially the standby-mode made my phone to go offline. After solving this problem aswell via a "zip" from the Internet that I installed via TWRP, my device was again stable for like two weeks. But then after a Night I faced a new Problem, my Phone was again offline. It shut down without doing anything from my side. I saw all indications for a hardbrick. So i tried to "rescue" my phone via the xda-guide. And randomly after plugging it into my pc via the usb-connection it rebooted. But this just created the newest and maybe biggest problem.
Right now: My phone shuts down after beeing in standby-mode for like 5minutes. Neihter my LED is blinking or anything else is happening. It has no Bootloop but sometimes I am again scared of having a Hardbrick.
For me as normal User, who just wanted to get more privacy on his phone, these Problems exceed my knowledge and that's why I posted my Problem here in this forum, full with people who might know how to fix this problem or even be experts in rooting mobiles.
P.S: Please excuse my bad english at some points. Try to overlook it )
rubiix said:
First of all, If I am copying an already existing Post I am sorry for that but I think i found nothing similiar to my "weird" situation here.
Now to my problem (with a short intro tho) :
I had my OPO for a half year, when i decided to root it. When i did this, I was a total rookie, so I just followed steps/guides I've found in the Internet. I unlocked Bootloader, installed TWRP-Menu and finally rooted my device. Everything went totally perfect for me and my device was running smooth and without any problems. But after some dirty- and some clean- updates(always only the cyanogen updates that were showen on my phone), my OPO randomly shut down. Earlier on, I made a Backup. So i wiped calvik&cache and thought i lost all my problems. But in the last weeks, new problems occured. So i started looking for them in the Internet. I found out, that i had a "bootloop"/ Softbrick on my phone. It randomly shut down and it sometimes felt like especially the standby-mode made my phone to go offline. After solving this problem aswell via a "zip" from the Internet that I installed via TWRP, my device was again stable for like two weeks. But then after a Night I faced a new Problem, my Phone was again offline. It shut down without doing anything from my side. I saw all indications for a hardbrick. So i tried to "rescue" my phone via the xda-guide. And randomly after plugging it into my pc via the usb-connection it rebooted. But this just created the newest and maybe biggest problem.
Right now: My phone shuts down after beeing in standby-mode for like 5minutes. Neihter my LED is blinking or anything else is happening. It has no Bootloop but sometimes I am again scared of having a Hardbrick.
For me as normal User, who just wanted to get more privacy on his phone, these Problems exceed my knowledge and that's why I posted my Problem here in this forum, full with people who might know how to fix this problem or even be experts in rooting mobiles.
P.S: Please excuse my bad english at some points. Try to overlook it )
Click to expand...
Click to collapse
Let me clear few of your terms
Bootloop : Your device spins on CyanogenMod logo
Hard brick : Your device won't even boot into recovery and when you press power button(10-15sec), it'll vibrate just once
Softbrick : Same as bootloop, but you can boot into your custom recovery like TWRP
The solution to all your problems is to flash fastboot/factory images of Cyanogen OS 12.1 (Tutorial link in general section). Make sure that you backup your internal storage.
Flash them and use it for 2 days, if you continue to face issues, quote me here or somebody else will help you on this board
Might be a hardware issue
rubiix said:
First of all, If I am copying an already existing Post I am sorry for that but I think i found nothing similiar to my "weird" situation here.
Now to my problem (with a short intro tho) :
I had my OPO for a half year, when i decided to root it. When i did this, I was a total rookie, so I just followed steps/guides I've found in the Internet. I unlocked Bootloader, installed TWRP-Menu and finally rooted my device. Everything went totally perfect for me and my device was running smooth and without any problems. But after some dirty- and some clean- updates(always only the cyanogen updates that were showen on my phone), my OPO randomly shut down. Earlier on, I made a Backup. So i wiped calvik&cache and thought i lost all my problems. But in the last weeks, new problems occured. So i started looking for them in the Internet. I found out, that i had a "bootloop"/ Softbrick on my phone. It randomly shut down and it sometimes felt like especially the standby-mode made my phone to go offline. After solving this problem aswell via a "zip" from the Internet that I installed via TWRP, my device was again stable for like two weeks. But then after a Night I faced a new Problem, my Phone was again offline. It shut down without doing anything from my side. I saw all indications for a hardbrick. So i tried to "rescue" my phone via the xda-guide. And randomly after plugging it into my pc via the usb-connection it rebooted. But this just created the newest and maybe biggest problem.
Right now: My phone shuts down after beeing in standby-mode for like 5minutes. Neihter my LED is blinking or anything else is happening. It has no Bootloop but sometimes I am again scared of having a Hardbrick.
For me as normal User, who just wanted to get more privacy on his phone, these Problems exceed my knowledge and that's why I posted my Problem here in this forum, full with people who might know how to fix this problem or even be experts in rooting mobiles.
P.S: Please excuse my bad english at some points. Try to overlook it )
Click to expand...
Click to collapse
I've had a similar issue arise in my OPO around a month back. The phone used to randomly switch off. In most cases it didn't switch on for around 10-15 minutes. I installed different roms, cleared data/dalvik .... you name it, I did everything, but the issue still persisted. I came to the realisation that it had to be a hardware issue. Took it to a service centre, where they confirmed it was an issue with the motherboard ( although initially they just flashed cm11 and handed it to me). So basically, my phone is with the service centre for the past 5 days and is awaiting the new part.
What I'm saying is, get it to the service centre as quickly as possible, if you're nearing the end of your warranty and get it analysed and fixed. Wish your OPO a speedy recovery
Mr hOaX said:
Let me clear few of your terms
Bootloop : Your device spins on CyanogenMod logo
Hard brick : Your device won't even boot into recovery and when you press power button(10-15sec), it'll vibrate just once
Softbrick : Same as bootloop, but you can boot into your custom recovery like TWRP
The solution to all your problems is to flash fastboot/factory images of Cyanogen OS 12.1 (Tutorial link in general section). Make sure that you backup your internal storage.
Flash them and use it for 2 days, if you continue to face issues, quote me here or somebody else will help you on this board
Click to expand...
Click to collapse
Thanks for the Information,
I really appreciate your Help. Just one question, is the backup that I can create via TWRP enough or should i backup everything seperatly?
And @p403nix, Thanks for your tip !!! That's a nice information, the only Problem about that is, that in my Homecountry the Oneplus Support is very terrible. I am in contact with the customer support tho, but I don't expect too much
Related
Hello all, I have an HTC Arrive running LEAD's 7.8 8858 ROM. I've been running this rom since January with very little issues. However, within the last couple of weeks I have been noticing strange things going on with my phone. Some mornings I have woken up and left for work and notice my phone is almost dead, even though I remember plugging it in the night before. Also, as of this week, after a reboot of my phone, the Call button shows Home Service instead of Sprint, but eventually changes over to Sprint. At times I will go to use my phone and see it has put itself in Airplane mode or has a locked sim card logo displayed instead of signal bars. In this case I have to reconnect to the network to regain functionality.
Now as of last night my phone is constantly rebooting while charging. I plugged it in last night and kept hearing a buzz (I keep it on vibrate), looked at the phone and it would be booting up. It fully boots to the Start screen and I can go ahead and begin doing something, but no matter what I'm doing it just shuts completely off without even saying Goodbye (literally). It continues to do this until I unplug it, and it ONLY reboots when plugged in. I've tried a battery pull a couple of times but to no avail. Its getting very annoying because it takes much longer to actually charge, and I also don't imagine this is very good for the phone itself.
I was planning on flashing LEAD's latest release to see if it fixes it, but I'm not sure if the phone will react this way plugged into the PC as well. I haven't plugged in to the computer yet to find out, hopefully it won't do this, else I won't be able to flash it.
Any ideas or suggestions? Has anyone else had this issue?
well i plugged into the pc and it still reboots however, when in the tricolor bootloader it does not reboot! so with this discovery i now know that its a bug in the OS causing the reboots. also, because its not rebooting in the bootloader, i should be able to reflash without issues, correct?
as a side note, the phone got VERY hot last night while left in to charge, so i will just charge my wifes phone and swap the batteries so that i wont damage my phone.
no one else has reported this issue with this ROM as far as i can see, only random reboots.
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
leadpoizon said:
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
Click to expand...
Click to collapse
thanks for the reply lead! i am going to flash you latest release now. i am going to look for an alternative way to backup pictures outside of Zune and the PC, but i dont think any exist.
i will post back when its up and running.
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
x_orange90_x said:
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
Click to expand...
Click to collapse
No problem. Glad your issue is fixed now.
Ok so I am no longer having the charging or battery issues anymore, but now my Marketplace is basically broken. When I can manage to begin a download it immediately goes to Attention Required, and upon clicking i get error code 8000ffff. So no apps will install/download from Marketplace. Also, on almost every game and app, it says this app is not available for your device, even ones i used to use on 8858. Some i have even manually installed and they work fine. Also when trying to even view many of the games in the Marketplace, I get error 805a0194. So far I haven't managed to install anything from the Marketplace aside from the Bank of America app.
I have tried resyncing with Live, rebooting the phone, tried changing Marketplaces and settings with the Marketplace Config app. Nothing fixes it
Any suggestions?
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
x_orange90_x said:
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
Click to expand...
Click to collapse
Sorry, I've moved on from this device, so I can't test anything now. I never had any issues like this on my device and I used it extensively for a long time after flashing that ROM.
Hey people!
I've had my Ace Plus for a while now, and there's one problem that's getting on my nerves. A year or so ago, I rooted the thing, and then accidentally updated the OS- causing it to be soft-bricked. I fixed that by following one of the many guides and reinstalling android, and it works perfectly now- except for the random moments where it reboots without warning, sometimes more than once per day, sometimes not for a week, when I'm using it, but also when it's just sitting there or on the charger. Especially the last is annoying, since it will not reboot but just show the battery status if charging.
Seeing that the problem started after I bricked it that first time, I don't think it's an app that's causing it. I've tried 'unbricking' it a few times (always following guides). I also tried underclocking it (no result) and I even tried running a logger overnight a few times, which also didn't manage to catch the reason for the reboot when it did happen.
I did repair my sister's bricked phone once by not only flashing the PDA file, but also the bootloader, csc, modem and pit file. Is that what I need to do with mine? If so, where do I find these?
I still see it as a fine phone, and even though I'm ready to go get a better one, I was wondering what else I could try to find out what is happening/stop it from happening.
Thanks in advance, even if it's just for reading!
Hello,
When connected to a PC, it is showing up as "QHSUSB_BULK". I only have official software from AT&T OTA, and phone is not rooted.
From my reading online, it means hard brick..... I cant get into recovery,download modes or anything at all now..... definitely not motherboard since the phone turned on over the weekend, when battery was almost zero and had to connect to charger to completely turn on.....
Tried downgrading to kitkat from lollipop because a continuous restarts.
Currently, neither fastboot nor ADB recognises this phone or I cant use LG flash tool to install official kitkat onto it. I have tried looking at various forums and couldnt find this exact situation of phone not turning on at all. Also phone is not showing up in disk partitions as well
Can someone tell me how to fix this phone, having this issue from almost 3 weeks now.
I got a same problem, In my case, I changed the battery then fixed the problem
ANy help guys...This G2 forum is too quite
Any help people.... Its been more than a month now
If you cannot get into DOWNLOAD or fastboot then you will have to open the device up and short out the 2 circuits. I just had the same thing happen to me when I ended up putting mismatched boot files on the system. It is time consuming and a pain but really not that hard. MAKE sure you have the right tools. I bought some off amazon before doing.
Out of nowhere my phone started to restart randomly to the point when it looks like a boot loop. Also I have noticed that those boot loops occurs when my battery is below 50% and when I'm charged to 100% I can boot but after 3-4 minutes it goes to restart anyway. Also when I have turned off WiFi, GPS and BT there are no more reboots so far but I'm not able to turn on back WiFi, GPS or BT unless I will pull battery out and put back and turn on them back quickly but then I'm getting back those random restarts.
I'm on a stock but rooted Lollipop with TWRP.
I saw some threads with similar issues and were related to a battery but in those cases phones stay up when were charged or a battery pack and mine has still if is connected to the wall or a battery pack.
Any clue what is going on?
Thanks
OK now I'm not able to get to the Factory Reset screen (Power + Vol Down). Any clue on that?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
So now I have issues to get started that phone. Mostly goes into boot loop mode (LG logo, LED flashes few times and reboots). Sometimes it goes beyond LG logo - to AT&T logo and reboots there. When I pass that I have a luck and I can get phone to work but I need to disable WiFi, BT and NFC.
Also I have got into MiniOS and run that ATT testing tool which came all passed except one - OTG or something like that failed.
Any help?
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
Click to expand...
Click to collapse
try a new battery @TheNetwork @Scyzor
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Click to expand...
Click to collapse
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
harffmut said:
try a new battery @TheNetwork @Scyzor
Click to expand...
Click to collapse
Zahr said:
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have got two batteries week ago. One original replacement (3000 mAh) and some OEM (3500 mAh) - both were failing into boot loop until I will get to be lucky enough after full charge over the night and boot to the system and leave it as is but last Tuesday my screen started to fade away instead of turning off and after that it went again into boot loop.
But I don't have any problems booting into recovery (TWRP) or DL mode. Strange...
Scyzor said:
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
Click to expand...
Click to collapse
This happens with all phones as devs are like anyone else. They upgrade their devices and focus on the new device. Some sell their old device to offset the cost of the new one. Development takes time and many of these individuals have lives outside of development. They have jobs and/or families. What they do is for the fun of it and so they can get more of what they want out of Android. If they share it, then that is up to them and does not mean they owe support to those who choose to use their ROM(s). The fact that a development site lets non developers use ROMs that are uploaded is a privilege and I'm thankful for it. I'm not a developer but have been able to use info from here to get more of whst I want from my phones.
Strange problem. Battery full, no problems there. After getting mad about sdcard not being recognized, even with cm 12.1 , I decided to install cm 6.01 rom(marshmallow) nightly. Installed, changed launcher to nova prime, right gapps, and installed kernel auditor. Downloaded xposed for marshmallow, rebooted, everything was fine(or so I thought). Two days later, coming back from store, looked at my phone and hit power, to get it out of sleep. That's when everything went wrong. It didn't come back, and no pressing of the power button did anything, I had to battery pull. I rebooted to twrp, and over the next week tried to get it right. Uninstalled cm 6.01 nightly, and put xneon rom on it. Same problem persisted, no boot to the os, or partial boot to the lockscreen. I knew the phone wasn't hard bricked, since twrp was still working, and phone wasn't shutting down to no response. Whenever I tried to boot into the os' , it would still get stuck on startup, though. I read all of the advice to return to stock, using flashtool, or lgup, going into download mode, everthing that I could read up on, and implement. I ran to best buy, and ordered a huawei 5x, and said to myself, I can't fix it. Well, today, I said why don't I short the battery pins, and repeatedly press the power buttons, at the same time( because when i put the battery in, even after 10~15 seconds, it would boot to the lg logo, then fade to non-responsive again). Viola! it booted into the os' , and didn't shut down to unresponsive condition(no power button action, and ultimately, battery pull). It seems everthing was fine, until I used the browser, then condition came back. Battery pull again, and it's working now, haven't shut it down since, so I adjusted the display off time to 30 min. , and turned off power saving modes. I don't know if it's truly fixed, but I thought my phone was going to my archives history drawer(all my other phones still work, but they're underpowered, old os' phones). It may still go there, once I pick up my huawei, but I'm glad to see it still living. Is there some type of time out I'm not aware of? or a shutdown by internal fuse, or reset that's built into the firmware? I've heard of bad screens with this, but didn't think that was the problem, since, when in twrp, it never shut down to being unresponsive, and when twrp shut off screen, it would come back, even after hrs of it on. I want to know if the bootloader has anything to do with this, and by shorting it, cleared the emmc.
I have made a video how it looks on my LG G3:
PS.
Is there flashable CWM for D850? I have heard that TWRP is creating those issues from the video.
Well, based on some articles it looks like a hardware issue mostly related to the overheating and "cold soldering joints". Based on that article most of LG phones may experience that issue:
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/
Dear all,
On my redmi 6, I was on android 8.1 (10.3.6.0 cereus precisely) and I prepared myself to try android 9
I had exactly this recovery recovery-TWRP-3.3.0-0423-REDMI6-CN-wzsx150.img and I did the necessary (backup everything) to be ready for the worse
Don't ask me why but I +/- remembered that recovery was tricky with android pie and I stupdly decided to flash the latest recovery I found on TWRP: twrp-3.5.1_9-0-cereus.img
Just after the flash I said reboot to recovery but: I'm in a "bootloop" not the one people have when booting in android, it's before!
Whatever the power or vol+ / vol- combination, long press power etc. , the screen is black it vibrates every 5 sec and I cannot enter neither recovery (i can understand...) NOR fastboot!
First time it happened to me to be stuck at this level. I do not know what to do, I tried desperate physical manipulations and crawl the internet meanwhile, but I do not see any trick, only solution is for an android bootloop, but not "early phone boot" (the 1 second before recovery or fastboot)
Can someone save me?
Hi, you've got your phone hard bricked, which means, that it coould be fixed, but it takes a lot of time to find a solution or you'll spend days trying to fix it, but its just gonna be a waste of time.
You can try methods that other people did, and maybe you'll get lucky, and unbrick your phone.
Other fix, is that you're gonna take your phone to an authoried Xiaomi store and hope for the best.
There are 10s of threads on hard bricks on Redmi 6 (for example: removing your battery for a couple of minues and putting it back, using SP flash (but you must have an authorized Xiaomi account, ...)).
If none of my solutions worked, I suggest buying a new phone. Redmi 6 is old and unstable after all (it didnt get MIUI 12 because of "performace issues"), so I guess thats the best you can do.
Im not really an expert for this kinda stuff.
I hope this will help you, but Im not saying that I could solve the brick.
Hi Sucharek,
I put the phone to the back of a drawer one week ago, because the vibrations every 30s where annoying. This afternoon I just "found" it again, likely out of power (no screen no vibration), and I charged it. Hopefully, it rebooted, not too far, as expected, but at least in fastboot mode and I was able to flash the TWRP and everything was fine!
With much more time and tools, I could have maybe follow one of your advice like removing battery, but I saw your replay 'too" late.
Strange and funny thing, I couln'd pass the pattern at the system lock screen. I can't forget it: it's the same I use on many phones. As this remdi was rooted, it was a piece of cake to remove the lock
So, in this story, I learnt that the fastboot is not a kind of secure sanctuary where you can go that easily...
edwin_r said:
Hi Sucharek,
I put the phone to the back of a drawer one week ago, because the vibrations every 30s where annoying. This afternoon I just "found" it again, likely out of power (no screen no vibration), and I charged it. Hopefully, it rebooted, not too far, as expected, but at least in fastboot mode and I was able to flash the TWRP and everything was fine!
With much more time and tools, I could have maybe follow one of your advice like removing battery, but I saw your replay 'too" late.
Strange and funny thing, I couln'd pass the pattern at the system lock screen. I can't forget it: it's the same I use on many phones. As this remdi was rooted, it was a piece of cake to remove the lock
So, in this story, I learnt that the fastboot is not a kind of secure sanctuary where you can go that easily...
Click to expand...
Click to collapse
Hi Edwin, Im glad to hear that your phone is back and running
For any of you other people that have this problem, I would recommend removing and replugging the battery, but remmember, there are more solutions you can find on XDA, that could fix the hard brick.
Also, for those of you that are willing to wait days, weeks, or even months and dont have the tools to open your phone and removing and replugging the battery, I would recommend checking out other solutions or just buying a new phone. Like I said before, Redmi 6 is old and unstable and theres a high change that you might get a hard brick, so if you want to install a custom ROM or a custom recovery, think twice before you do it and always have a backup phone.
I wish you all the best in solving your hard brick