My OnePlus One fell to the toilet. I opened it up and dried it. When I turned it on, it was stuck in a bootloop. So I flashed the latest CM 13 via fastboot. It was still stuck in a bootloop. I flashed the latest CM 12 via fastboot. And it was still stuck in a bootloop. So I flashed the CM 11s the phone came with. I updated it via OTA a few times... and stuck on a bootloop again. I don't know what I can do. It seems that everything I do ends on a bootloop. I need help.
First thing put the phone in a container full of rice so it will absorb the humidity. Salt could stick to the circuits and create short circuits.
I had a Nokia C7 that met heavy rain while I was going home ? still working except the touch.
The fact that you are trying to fix it with software well... ? Good luck. You can't troubleshot water in a phone.
Phone works well with CM 11s. The thing is that I can't update to a newer version. And it used to work with CM 13.
Pablopr3 said:
Phone works well with CM 11s. The thing is that I can't update to a newer version. And it used to work with CM 13.
Click to expand...
Click to collapse
And you flashed the COS13.1 stock from fastboot?
https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/
Yep, I did
Related
I have a tf300t us sku.
I unlocked it about a year ago. I was running pacman, when in April, my lcd cracked. So, I bought a new lcd and replaced it. In the process of replacing the lcd, the digitizer cracked! So, I ordered a new digitizer. I installed it, and seems pretty solid, and looks good, but touch still does not work.
So, I thought maybe I had to update the touch firmware. Tried to run a command to fix that with the updated firmware, but my rom returned that the update_fw was not found.
I think I need to be on stock to fix it. So I downloaded V10.6.1.27.5 Only for US SKU (Android 4.2) from the asus website. I tried to put it on an sdcard, and transfer it over. It found the sdcard the first time and seemed to install the sku no problem. But it bootlooped! So i tried again, same thing! I keep bootlooping. Before all of this happened, I was already on 4.2 bootloader and all that, so i should be fine, but it's not working. I don't know how to exit this bootloop...
Edit:
I just tried to flash twrp. Seemed to flash fine, but when I try to boot into twrp I don't have a recovery....
Edit 2:
Got twrp installed. seems that I have 5% battery life. so I'm gonna charge it all the way up then try to flash the firmware.
Edit 3:
I did a cold reset, which fixed the bootloop. After I could boot I flashed philz recovery. Problem was, I had ghost touches. So it was hard to get root. Finally got root and successfully updated touch screen fw. Its running very well now, bout to slap pacman on this guy.
Hi guys,
After searching for a few days and doing stuff myself (perhaps not everything for the best), I finally get it over with and ask for advice.
I've got a GT-N8010, since long been running an unofficial CM11 build (since one of these CM11 builds, the device was known as a GT-N8013).
Last week I started looking at the unofficial CM12.0 and CM12.1 builds, those looked promising.
After some info, I flashed to the CM12.1 build. A few minutes later, Android 5.1 in all it glory... everything running fine. Saturday evening I noticed I didn't get root.
Without thinking straight, the next morning I started flashing superuser but as you might imaging, that totally f'ed the system.
Now logically, one could just reflash CM12.1 and be done with it .. somehow I skipped all logic and started tinkering in recovery (TWRP).
After some doing, I managed to even F-up TWRP, it wouldn't boot anymore. The TeamWin logo was visible, screen flashed, logo and back.
No worries, there's still the download mode .. yeah about that ... already in panic mode .. doing more harm than good.
So .. Now I'm at this curious state.
I've managed to get it booting to a stock ROM. TWRP is also running.
The weird stuff I'm encountering now:
The device is semi recognized as a GT-N8000, if it was just that, I really don't care.
I said semi, when I want to flash another ROM (even specifically the CM12.1 for GT-N8000) it always states (in ADB Sideload in TWRP) that the package is not for this device.
There's a whole lot of devices listed, then it states "this device is ." , as in blanco device?
Anyone got an idea how to fix it so I can enjoy the Android 5.1 build again? (and seriously, remove the stock rom would be the first priority)
Thanks.
Please pardon me for any faux pas as I am new here.
Mods please refer me to the appropriate thread and close this one, in case this one is a duplicate.
It seems my Moto G 1 Gen XT1033 is hardbricked. I had been running a CM 12 for falcon - nightly release since May 2015 and had had no problems so far. I had also upgraded my recovery to CWM Touch.
Two weeks ago, my phone got stuck in a boot loop (I now realise that that is called a softbrick), I managed to boot into recovery and updated my OS with the latest nightly release of CM 12 for my phone. I also tried to upgrade the recovery version with the same as that of the OS version but I don't think that it got upgraded. (I'm not sure what it said).
Anyway my phone was working fine for an hour or so until CM gave some errors on opening the themes configuration, so I thought rebooting my phone would solve the problem.
My phone never booted after that. It didn't even turn on or boot into the bootloader/recovery etc. I checked the battery etc. and it was fine. There was no issue with the hardware.
I then connected my phone to my laptop and it recognised it as qhsusb_bulk. I have spent a lot of time searching and trying various methods like:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076
Using the MotoTool All In One etc.
I cant seem to figure out the problem. I don't even know what my bootloader version was etc.
Is there a problem with my bootloader or recovery? I can't seem to understand.
Can someone please help me with this?
Thanks
Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic
motolollipop said:
Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic
Click to expand...
Click to collapse
Thanks man. But no help so far
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.
CoolCrusader said:
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.
Click to expand...
Click to collapse
That happened to me too, I think even the same image! It was a long time ago and I have now switched to a Oneplus One after using a Moto E which actually isn't that bad - I got it new super cheap. For me, Cyanogen restarted to update and after a LONG period of time stopped doing anything (I have upgraded before). I couldn't mount anything in CWM and I lost all data irrecoverably. The partition table got all messed up, and I had to flash a dual sim image as it was the only one that loaded - done through fastboot. I then flashed the original kitkat image and then massively messed up and updated, making my phone qhs_bulk.
Basically everyone who has had lollipop on their devices and have this are waiting for files to be leaked from Motorola so they can make their phones work. Not much is happening currently, you might as well get a new budget phone - some of the new ones are much better than the Moto G 1st gen! Or you could do what some people are doing which is ordering broken Moto Gs off eBay and replacing the board. Good luck!
---------- Post added at 01:49 AM ---------- Previous post was at 01:42 AM ----------
Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
You may want to go the fastboot method to flash a stock lollipop image and CWM recovery - if you don't have a backup, you may want to try just flashing something like TWRP to see if you can get some files off your device, then completely flash over it.
Hi everyone.
I recently replaced my shatter LCD and was subsequently trapped in a bootloop. I began to wonder if the LCD I ordered was defective, so I removed the new screen and attached the old one. The device booted up fine (as fine as a devastated LCD screen would permit anyway). I detached the broken screen and reattached the new one and the device seems to be working fine.
I am now worried that shutting down the device will cause it to enter a boot loop again. Would reflashing the stock rom solve this issue? Has Motorola installed a failsafe that would prevent devices from booting up if there is a replacement screen attached to the logic board??
I am having the same issue, did you find a solution?
mike29892 said:
I am having the same issue, did you find a solution?
Click to expand...
Click to collapse
Unfortunately, no. After replacing the screen I've opted to keep the device on. Have you turned your phone off after getting it to work with the new screen?
ElonNoir said:
Unfortunately, no. After replacing the screen I've opted to keep the device on. Have you turned your phone off after getting it to work with the new screen?
Click to expand...
Click to collapse
I restored the phone to 5.1 and it booted up fine. Unfortunately my new screen seems defect, it has phantom touches and is not accurate. Perhaps with 6.0 a screen hardware test was added on bootup and both of our devices are failing it?
mike29892 said:
I restored the phone to 5.1 and it booted up fine. Unfortunately my new screen seems defect, it has phantom touches and is not accurate. Perhaps with 6.0 a screen hardware test was added on bootup and both of our devices are failing it?
Click to expand...
Click to collapse
Were the phantom touches present before restoring to 5.1? I'm running Marshmallow right now and I don't have a phantom touch issue. I've thought about reflashing stock rom and updating back to 6.0 but if a hardware test was indeed added, perhaps Flashing CM will allow the phone to operate free of bugs. Maybe that's just wishful thinking.
ElonNoir said:
Were the phantom touches present before restoring to 5.1? I'm running Marshmallow right now and I don't have a phantom touch issue. I've thought about reflashing stock rom and updating back to 6.0 but if a hardware test was indeed added, perhaps Flashing CM will allow the phone to operate free of bugs. Maybe that's just wishful thinking.
Click to expand...
Click to collapse
I couldn't even get the device to boot before restoring to 5.1. I was on 6.0 broke my screen and then replaced the screen. After turning the phone back on it entered a boot loop. I restored to 5.1 and it was able to boot, but the touch screen was all wonky, and getting phantom touches. I tried to flash 6.0 again and it just put me in the boot loop again.
Same issue here on XT1540. Ordered from the most popular seller on Ebay. I'm wondering running CM might fix it.
Update - unlocked bootloader and flashed CM12 - no issues any more with new LCD. Maybe some sort of hardware check with the stock ROM? Tested the digitizer with the "pointer location" dev tool and it was accurate.
Update 2 - can't seem to boot into TWRP with the new screen and CM12 flashed. Rom boots with no issues and runs with no issues though. Old broken screen boots TWRP no problem. Not sure why this is. Can boot cyanogen recovery but that doesn't seem to flash correctly.
fresh cut vegetables said:
Same issue here on XT1540. Ordered from the most popular seller on Ebay. I'm wondering running CM might fix it.
Update - unlocked bootloader and flashed CM12 - no issues any more with new LCD. Maybe some sort of hardware check with the stock ROM? Tested the digitizer with the "pointer location" dev tool and it was accurate.
Update 2 - can't seem to boot into TWRP with the new screen and CM12 flashed. Rom boots with no issues and runs with no issues though. Old broken screen boots TWRP no problem. Not sure why this is. Can boot cyanogen recovery but that doesn't seem to flash correctly.
Click to expand...
Click to collapse
Sorry for the delayed response. How did you manage to flash a ROM if the device goes into bootloop when turned off or rebooted? This is what is keeping me from doing it flashing CM. I fear the device will reboot during the flashing process and it will be borked and stuck in a bootloop.
ElonNoir said:
Sorry for the delayed response. How did you manage to flash a ROM if the device goes into bootloop when turned off or rebooted? This is what is keeping me from doing it flashing CM. I fear the device will reboot during the flashing process and it will be borked and stuck in a bootloop.
Click to expand...
Click to collapse
It won't reboot until the OS starts loading, as long as you can access TWRP you should be safe to flash a custom ROM... it seems to be a known issue that a non-Moto replacement screen will bootloop the OS with Marshmallow but not Lollipop, unknown if CM13 and ROMs based it (which is all custom MM ROMs) will bootloop or not.
Best solution is replace it with an OEM Moto screen, it won't bootloop, only 3rd party ones do.
Bare with me, I'm a total noob and I hold my hands up, I got a galaxy note 8.0, rooted it fine then I went to install CM 13 for it following partially instructions partially my own knowledge and now it's muffed. No matter how many times I tried it wouldn't work and I was messing around with it all night last night and all day today and in my infinat wisdom I removed all OS from it full stop. I have been sat here for 6 hours trying to put cm on it (tried 11, 12 and 13) tried installing stock marshmallow I downloaded from some site, and even some other ROM I can't remember off the top of my head (the logo is a horse's head or something) and yep nothing what so ever i have tried several different boot thingies like twrp and it always fails when I try to install the ROM, I know I should have backed up and I thought I had using titaniumbackup but that went with the OS. It's currently got twrp on it and I can get into that and connect it Odin (I think that's what it's called) but that's all I can do. Is it fixable or is it scrap? >.<
Update, after putting it down and thinking about it from another perspective I worked out a fix, it's back running 4.4.2 and works fine (on my note I will say the latest update of the Google app causes a problem with the system UI if you have Google now as your launcher) I'll update with full details in the morning in hopes that if anyone else has a similar problem this will help.
QuesteU said:
Bare with me, I'm a total noob and I hold my hands up, I got a galaxy note 8.0, rooted it fine then I went to install CM 13 for it following partially instructions partially my own knowledge and now it's muffed. No matter how many times I tried it wouldn't work and I was messing around with it all night last night and all day today and in my infinat wisdom I removed all OS from it full stop. I have been sat here for 6 hours trying to put cm on it (tried 11, 12 and 13) tried installing stock marshmallow I downloaded from some site, and even some other ROM I can't remember off the top of my head (the logo is a horse's head or something) and yep nothing what so ever i have tried several different boot thingies like twrp and it always fails when I try to install the ROM, I know I should have backed up and I thought I had using titaniumbackup but that went with the OS. It's currently got twrp on it and I can get into that and connect it Odin (I think that's what it's called) but that's all I can do. Is it fixable or is it scrap? >.<
Update, after putting it down and thinking about it from another perspective I worked out a fix, it's back running 4.4.2 and works fine (on my note I will say the latest update of the Google app causes a problem with the system UI if you have Google now as your launcher) I'll update with full details in the morning in hopes that if anyone else has a similar problem this will help.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried any of the CM based roms from xda ? You may only need to update your recovery. Both of these should work on your device
https://forum.xda-developers.com/ga...0-1r61-rom-resurrection-remix-v5-7-3-t3449444
https://forum.xda-developers.com/ga...m-unofficial-lineageos-14-1-gt-n51xx-t3533329
Latest twrp
https://forum.xda-developers.com/galaxy-note-8-0/development/recovery-twrp-2-8-5-0-t3035004
Good Luck
Sawdoctor