Hi guys, I know, is a very old device, but even without IMEI (I buy knowing this problem) is a very useful device for me, it has working very nice with an ics rom.
lets go to the my problem now. I try to put an newest rom (cm13), not work, and now no more rom work, all comes with the same issue: after in the welcome screen, he freezes and shutdown.
I googled a lot, read many threads, tryed many procedures, with cwm, twrp, odin, pray for "the old gods and the new ones" with no luck.
tryed stock, cm10, cm11, cm12 and cm13 (I lost the cm9 and can´t find it)
the battery is charging ok, no warm abnormally, the heat on device is normal too, and the power button is working as expected.
I appreciate your help
http://forum.xda-developers.com/showthread.php?t=2176593
Related
Hello folks, first post, hope you can help.
My phone has a very specific problem that happens with every rom BUT with AOKP.
When the phone is on idle it just gets stuck, black screen, button lights are on. Only thing to do is pull the battery out. It also happened with the stock rom, so I tried to unroot it and give it to sprint but they couldn't take it because of a small crack on the screen(been there forever).
I came back home and tried to flash it with a custom rom again, and recovery was broken, so I flashed recovery on the device 3 times before it started working again.
I randomly chose AOKP and it was working pretty well, although it slowed down lately a lot. I tried to install JB on it recently and the problem returned, so I tried CM9 again, CM10 even tried Bugless Beast, same thing. I keep going back to the backup I have of AOKP and it's the only one that doesn't crash my phone.
I've attached the phone information so you guys can see exactly which built I'm running.
Bump.
Please help me fix my phone, I'm really at loss how to solve this problem,
Do you turn deep idle on? If so that could be the problem......when u flash a new rom, as your setting everything up, make sure deep idle is turned off.....the option is under advanced in the cm roms .......hope that helps
10....0011....10101
I'm new to this forum and idk if this is the right place to ask for help! Excuse me if it isn't
I recently flashed a custom ROM from aospal.com and it turned out to be a disaster. After installation, it deleted my recovery software (now I can't use/ don't have cwm or twrp). I can't boot into recovery anymore. Whenever I try doing so, the screen just goes blank after the note logo (I have a note n7000) but the soft-keys glow. I can only restart the phone after connecting it to the charger. The ROM is highly unstable and it eats up my battery very quickly. I've flashed many ROMs before and they were all fine. No problem. But this particular one messed up my phone. Someone please help me out! I can go into the download mode!!
I have been successfully running custom lollipop rom's from november, but couple of weeks ago it changed.
I installed some new rom to my OPO, can't remember what. It installed and run fine, but when I disconnected the usb cable connected to pc it freezed and started bootlooping. Phone sometimes boots to os but freezes immediately and bootloops again. If I connect it back to pc, everything works fine.
I managed to get it working by restoring to stock and locking bootloader with OneToolkit for OS X. But there were some problems; the screen wouldn't rotate, battery drains a lot faster, like in 10 hours with very little use, and many more. I unlocked bootloader, installed custom recovery and rooted, nothing changed, but when I installed different rom bootloop starts again. I've tried with many roms. It does'n matter if I install the rom with usb connected or not.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
With these two guides the phone works normally, but still can't use any other roms.
"make_ext4fs /dev/block/mmcblk0p15" fix didn't do anything.
Any similar problems?
Sorry for my bad english.
I am facing the same problem.
Someone please help us fix this problem.
Do you have the latest firmware flashed? That is a requirement for most LP ROMS lately. It normally posted on the first post of the ROM's forums, its also included in the lastest CM12 nightlies from what I've read.
Hello guys,
some days ago my phone was permantly booting up in the recovery mode nothing else was possible. As I was on road and couldn't access internet anywhere I just tried to do some wipes, which then made my phone not show anything. I guess the reason that it didn't boot up anymore was that the battery was fully drained. When I was finally back home I was able to charge my phone but then the following happend:
I can start my OPO, see the android logo and then it turns black, but it fully boots up. I mean I can even click the touchscreen and hear some touch reactions/sounds. Also I'm able to turn up/down the volume and hear my phone. Furthermore I'm also able to do the "V-gesture" to turn on the flashlight. When I boot up into fastboot mode I also see the message "fastboot mode" + the little cyanogen face.
All in all everything seems to work, aside that I dont see anything else than dark after the logo.
I tried flashing new roms, stock reset, like seriously anything, but I can't get my phone to work probably again.
Does that mean that my phone got some hardware problems, maybe the touchscreen?
Help is appreciated, thanks in advance!
btw: English isn't my first language, so please excuse any mistakes.
You'll have to try flashing completely stock CM11 rom or CM12 rom, img by img in fastboot..modem, boot, system etc. I helped a friend who had this kind of problem. Probably not the cleanest way, but at least it works.
Already did that 3times using different methods. Stock CM11, CM12 and colorOS
I have a similar problem, did you manage to fix it? And if so, how?
Thanks,
Capelare.
Sorry everyone for this annoying post but I have done research enough to think that I may be out of luck so you guys are my last hope here.
Here is the senario;
I have been running Cyanogenmod 12 (courtesy of Sultan). Once the ROM was discontinued I decided to give Paranoid 5.1 a shot. I downloaded the new rom, suggested SuperSU and Gapps and booted to the most up to date TWRP. I flashed the rom, then supersu, and finally Gapps and then rebooted my phone. The phone stayed in the boot screen for about 45 minutes (maybe even an hour) so I powered off the phone, pulled the battery, and attempted to boot back into recovery using the power and volume buttons but nothing was working. The phone would just keep vibrating (pulsing) until i let the buttons go and then jump right back into the booting screen until I turned the phone off again. Hopefully I am doing something wrong and there is an easy fix but Im afraid that I now havae a brick on my hands.
Please help,
SuperNewb
[Update]
Now the phone will hold the boot screen for a couple minutes then the screen just goes black. Not sure what that means.
Also, just so you guys dont think im too ignorant, I will say that I I have flashed at least 10 different ROMs before this so I would like to think that I have a decent understanding of how this all should work.
My mistake on posting this question here. I have reposted in the Q&A Forum.