I recently bought an Oppo N1 off of Swappa. I just got it today and its been one problem after another. Heres the story...
Rooted with Towelroot and installed Super SU/binary. Rebooted. The phone was running the stock Cyanogen 10.2 but it told me that CM had an update, so I figured id go ahead and update that aswell. It downloaded and installed but when it rebooted, the phone is just stuck on the OPPO screen. I can get into the recovery but I have absoutley no idea where to go from here. I've tried installing other versions of CM11 but it just says installiation failed. Still stuck on boot. It is also getting stuck and staying black and im having to leave it sit for awhile before it will boot. I'm literally begging anyone to help me out here. I'm lost. I will be closely monotoring this thread
After some research, apparently CM11 needs a custom recovery installed which i do not have. Is there a way i can install TWRP, or possibly revert the N1 back to 10.2???
Please, somebody help me
Related
Alright, I have a verizon GS3 I rooted it about a year ago and installed AOKP. Back in october i switched to CM without any problems. About two weeks ago or so, a CM 11 M3 update came through the automatic updater in CM so i figured i'd give it a shot. I installed it and it boot looped. So i figured it was just messed up went back to CM 10.2.1. After i went back to 10.2.1 i immediately got "xx app has stopped working" for almost all of my apps upon booting. Then i figured out what might have been wrong when i switched to CM 11 M3 and flashed the new gapps, well it still boot looped. So then I flashed a recovery (which was AOKP) that I made back in October and the phone was fine, until last night when I was at work and the battery died. After i got it on the charger and went to boot it up it started boot looping.So i went to try and flash the recovery again to see if i can salvage anything but i get an MD5 mismatch error when i try to flash any of my recoveries. I tried advanced system recovery as well and i didnt get an MD5 mismatch error but it just went back to boot looping. I have very basic knowledge of rooting and flashing ROMs and i've looked around the web quite a bit to see if i could find a fix but i havent found anything. Any help would be appreciated. Thanks
BobbyTam said:
Alright, I have a verizon GS3 I rooted it about a year ago and installed AOKP. Back in october i switched to CM without any problems. About two weeks ago or so, a CM 11 M3 update came through the automatic updater in CM so i figured i'd give it a shot. I installed it and it boot looped. So i figured it was just messed up went back to CM 10.2.1. After i went back to 10.2.1 i immediately got "xx app has stopped working" for almost all of my apps upon booting. Then i figured out what might have been wrong when i switched to CM 11 M3 and flashed the new gapps, well it still boot looped. So then I flashed a recovery (which was AOKP) that I made back in October and the phone was fine, until last night when I was at work and the battery died. After i got it on the charger and went to boot it up it started boot looping.So i went to try and flash the recovery again to see if i can salvage anything but i get an MD5 mismatch error when i try to flash any of my recoveries. I tried advanced system recovery as well and i didnt get an MD5 mismatch error but it just went back to boot looping. I have very basic knowledge of rooting and flashing ROMs and i've looked around the web quite a bit to see if i could find a fix but i havent found anything. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
Try and odin back to stock if your back ups are on the sd card.
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.
Besides my comments in the title, the only thing my K1 can do right now is go into the bootloader and nothing else.
The Story:
I was running Blisspop 4.0.3 (Lollipop 5.1.1) then flashed to Blisspop 6.0 (MM 6.0). After that, it wouldn't boot into the OS. I did a complete wipe of everything and tried to flash Blisspop 6.0 again, same outcome. I heard I needed to get my hands on TWRP 3.0.0.0 to get MM roms up and running. My dumb ass flashed it and now, I don't have a recovery either now because it gets stuck on the first slpash screen. I went digging around the forums here and I felt like I read something about doing a bootloader update. If that's true well then I done messed up now. At this moment in time, I am only able to launch the bootloader but for the life of me, I can't get ADB to detect it connected to my computer to fix these issues. So as of right now, it's a $200 brick. If anyone can point me to some awesome tools to hack my way around this conundrum, I'd love you forever. Thanks in advance for listening to my problems.
Hello guys, so yesterday i started playing a bit with my Huawei P9 lite, started installing Resurrection Remix ROM, sim was unable to read, so I flashed EliteROM, and there were some weird bugs that I couldn't keep on with.
After that I decided I wanted to go back to the stock ROM, read some things and watched some tutos and ended ****ing up (I think so)
Failed with the dload method and all these things.
Right now I'm sitting here with a probably broken boot, I have Twrp recovery installed, of course phone doesn't boot and goes directly to eRecovery...
So, anyone knows what can I try to do to get my P9 lite working again? If I could go back to the original ROM it would be great, if not, I can still go back to another working ROM?
Really nooby at this, HELP REALLY APPRECIATED!!
I have asked on a few threads including the TWRP thread but no one seems to be answering for some reason so I thought I'd risk putting up a separate post to try and get an answer.
I followed the instructions to the letter on how to install TWRP from the thread and it installed all ok, the only problem is that the screen is totally frozen and there is nothing I can do to get it to work. I have now gone back to Oreo via Odin until I can get help on what's gone wrong. Would it make a difference if I tried from Nougut 7.0?
I have rooted and installed roms, TWRP's pretty often last year with my M10, M8 etc so I'm not that new to this but it's got me foxed this time.
Good question. I had an issue after installing CarHDROM, v9 for a bit where I could get into TWRP, but the phone would boot loop getting out of TWRP and I had a hard time getting back into recovery or download mode.
I re-flashed the phone and TWRP as well, and after that all was well. I did not change anything on the re-flash.
Sometimes things just get mux'ed.