Hi all,
well, to be honnest I already posted my story in the help thread but no answer came so I try with a new thread
We'll see if I'm luckier this way !
a few weeks ago I broke my screen and decided to change it myself.
Everything went fine (even restarted successfully my phone before applying the tape to fix the screen) until I finally tried to restart my phone after the repair is done.
Since then I'm not able to turn on my phone
Holding the power button starts fastboot mode, UP + power doesn't do anything and DOWN + power enters recovery. Weird !
Another weird thing: it only works if I'm not plugged. When I'm plugged nothing ever happens.
I suspected I could have damaged buttons or cables. I have looked carefully but nothing appears to be broken.
Here is what I already did without any result:
- I had access to the original recovery so wiped the cache
- I tried to recover the phone but that did not work so
- I installed twrk using adb (like here)
- and then installed the rom as explained here (I used the last release here, so it should be cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-bacon.zip). It seemed to work but finally no, same situtation
- I tried this but so far not able to get the qualcomm port listed once the phone is on. It may be related to the fact that I have to unplug to boot it but I always got a Android bootloader interface listed.
Any idea someone ?
Thank you very much for your help !
Did you try to "fastboot reboot" while in fastboot mode?
Try flashing a CM14 rom. Mine came with CM12 so I tried flashing back to CM11 and I did flash it successfully through Fastboot but alas it won't boot. The boot logo loads but then I'm introduced to a black screen.. So I flashed back to a (at that time the latest stable) CM12.1 but same result. And I got worried. Then I decided to flash a CM13 rom which was a beta build (at that time newly released Android 6) and it booted into it alright! So I suggest flashing a CM14 and let me know how it does.
The problem seems be much deeper than just a broken screen. It may sometime affect the chipset of the cellphone.
For that we can't do anything.
For now you can try the following things :
1 . Flash the latest Cyanogen Firmware from the same place you have downloaded the snapshot cm13.
2. Flash recovery (TWRP) using adb.
3. Wipe
-System
-Data
-Cache and Dalvik Cache
4. Flash the latest Cyanogen Rom .
5. Boot into recovery.
6. Flash some gapps as per the Android version.( Open Gapps I recommend)
7. Boot back to recovery .
8. Boot into System.
This is the max you can do for now.
You can also check device forums for recovering from a bricked device post.
Go through the post and check if any symptoms matches yours. You'll find the answer right away.
And the last option you can do is going to service center, they will charge you mostly (even if in warranty as you have yourself tampered hardware of the phone.)
Hope it will help. Thanks
Related
so today i went to unlock and flash CM 10.1 on my tablet.
unlocking went smoothly
installing clockwork recovery went fine
installing cm10.1 and gapps went fine
once i booted into cm successfully, i checked the internal storage to see if it was clear. it wasn't, so i went to settings, backup and reset, and done a factory reset. now i'm stuck on this one screen and i dont know what it is.
i've held the power button and volume down until the tablet restarts and that results in the same thing.
i've tried power and volume up. that seems to start the tablet but the screen stays blank. i connected it to the computer and my computer installed an APX or APTX or something like that driver.
i've tried holding power, volume up and down, and that does the same as the power and volume up.
i'm very new to installing custom recoveries and roms. can anyone give me an idea on whats happened
Once you have a custom recovery installed you should NEVER wipe from the system settings or the bootloader menu. You wipe from your recovery.
If you do that, the bootloader seems to write a command to the misc partition to reboot into recovery.
And that is the loop you seem to be stuck in.
You can try _that's method to clear the misc partition from here: http://forum.xda-developers.com/showthread.php?t=2528313
Read the whole thread, salvation may be found in post 7.
If that does not work, you could try this:
http://forum.xda-developers.com/showthread.php?t=2399698
buster99's method may be another way to enable you to boot into the bootloader and flash a working recovery.
Good luck!
Thanks for the tip. I'll remember to do that next time. As of now it is fixed. I found a post on the cyanogen forum of someone who done the same thing. And he said he had to wait a painful 6+ hours of that screen I posted. Lucky for me it was only a ~45 minute wait. So all is good. Cyanogen is running. Recovery is working. All the stress is gone.
Dudes,
I was running CM 0701 nightly fine and decided to boot to CWM-based recovery and flash latest nightly from 0703. It got about 2/3 the way through updating apps after boot and froze. Then screen stayed black, but would backlight. Was unresponsive to touch, but I could get it to take screenshots (at least I could hear the sound made by triggering one). I longpressed the power button to force reboot and entered bootloader. Finally I could see the screen again. I thought all was better and it just needed a reboot so I reboot again and let it boot. Still no screen. So I longpressed to reboot, got into bootloader, then revovery... and tryed to reflash nightly from 0701 but it won't access my "/sdcard" because it won't mount. Same error ("Error mounting /data!) when I try to fatory reset or mount/unmount.
WTH?!
Anybody have any ideas what broke this? What it a change in last two nightlies? A change to the recovery?
I'm going to try http://forum.xda-developers.com/google-nexus-5/help/help-e-mount-sdcard-cwm-6-0-4-5-trying-t2802715 when I get home... in way too many hours. Sadface.
I also posted this in CM Forums: http://forum.cyanogenmod.com/topic/...cant-mount-data-after-0703-nightly-boot-fail/
Firstly try and fastboot flash a stock cache.img
rootSU said:
Firstly try and fastboot flash a stock cache.img
Click to expand...
Click to collapse
Thanks @rootSU. Ultimately and unexpectedly the phone came back to life before I could get to a computer with adb access. I had tried rebooting several times before, but magically after about 6 hours of downtime (no charge or anything) it rebooted up fine. It was a little shaky and slow at first, and ran the update apps process again on the next boot but has since be stable. No flashing. A couple reboots. All fine.
Thanks to the XDA community for existing and providing such a reassuring resource for knowledge and problem solving!
So I haven't had any luck with my Oneplus One lately . I had rooted the phone and was running the CyanogenMod nightlies for a while, but recently for some reason when I updated it for Nov. 25 I have been suck in a reboot loop where the phone boots up and it starts updating apps, but then it continuously does this cycle of rebooting and updating apps. I have tried to enter recovery mode to try and remedy the situation as I have twrp, but for some reason it doesn't boot to recovery when I press down the power and vol down buttons. I have tried to adb to try and reboot into recovery mode but I haven't been able to get it to work. I'd really appreciate some help on this as I have no idea what to do at this point.
I should also mention that I would like to see if it is possible to recover my data as I foolishly did not make a back up.
Thanks in advance.
So just an update I was finally able to get into recovery mode. I backed up my data with twrp and I tried the method mentioned in the reddit link below.
http://https://www.reddit.com/r/AndroidQuestions/comments/1ly5b1/is_it_possible_to_restore_my_sms_from_a_twrp/
I installed the newest version of nightlies CM 13.0 2015 11/30 along with gapps 6.0, but now my phone just boots up and optimizes apps but when it restarts after that it just goes to a black screen.
I know I can wipe everything through twrp and install cm 13.0 probably eliminating the issues I am having, but I'm reluctant to do so as I would like to retrieve my sms messages. I have taken my photos off my phone so I have that.
If any one can advise me on if I can restore my sms from the twrp back up I have made then I'll wipe my phone and do a clean install.
Thanks in advance
i have the exact same problem. would be nice to have it fixed and working without losing all the data.
So I decided to go ahead and wipe my system as I have all of the data I could get out of my phone on my pc now. I get get cyanogen working nicely, until I go into twrp and try to restore the data files I had backed up. This goes well until the reboot then a message pops up saying something isn't working (too fast too read). I then get a blank screen.
Now I still have the same problem of how to put the data I had saved when I used twrp back on to my phone. I believe something in my data is corrupt which is why this is happening, but I'm not sure. Is there just a way to extract say the sms from the data I have saved, that's really all I need at this point. The backups made by twrp are in a format .WIN that I have never seen before and I would appreciate the help if someone can advise me what to do from here.
CM13.0 struck in Reboot loop
When I was browsing and doing some multitasking stuff..noticed that phone was lagging a bit .So i thought to reboot so that it would come out of that...But it completely struck in reboot loop forever.
please help me out of this issue.
Thanks in advance
Novius vi said:
So just an update I was finally able to get into recovery mode. I backed up my data with twrp and I tried the method mentioned in the reddit link below.
http://https://www.reddit.com/r/AndroidQuestions/comments/1ly5b1/is_it_possible_to_restore_my_sms_from_a_twrp/
Click to expand...
Click to collapse
How did you get into recovery ?
I'm not been able to boot into recovery even while pressing vol - and power. And system is also not booting up just stuck on oneplus logo. i can enter fastboot though
vindows18 said:
How did you get into recovery ?
I'm not been able to boot into recovery even while pressing vol - and power. And system is also not booting up just stuck on oneplus logo. i can enter fastboot though
Click to expand...
Click to collapse
Are you pressing the Vol down button and power button. Also I unscrewed the back of the phone to unhook the battery cable then I pressed the buttons. I found also, through trial and error on my phone, that you can hold down the buttons for too long so you have to watch and make sure on that. I found that you should hold the 2 button combo through the oneplus one boot logo and you'll see the lights dim then you let the buttons go and its worked so far at least on my phone.
Ok so, I flashed a CM13 rom on a K4 Note (16GB internal and 3GB ram version). I pretty much followed all the steps required for flashing - unlocked bootloader - installed TWRP - wiped (factory reset) - flashed the Rom. Now, the phone booted up alright and worked for a day. The phone doesn't belong to me, and the owner decided that he wanted to factory reset it one more time. Since I also wamted to show him how TWRP functions, I booted into recovery via the advanced boot option in Cyanogen (Did not use the key combination). So this phone turns off and decides not to start. I waited for some time and decided to manually power it up. It won't. I held down the key for about 5 minutes and yet, to no avail. Not even a vibration. No response at all.
So, I would like to understand what happened with the phone, since as far as I can tell, TWRP was working fine. I used the key combo method to boot into TWRP thrice the night before - to flash CM, to flash gapps and to flash thr xposed installer. I can say CM was working fine since I used it for a night to get a hold of any bugs. Nothing went wrong at that time.
So, what can I do now? Since the phone is completely unresponsive and is not being detected upon being connected to the PC, I suppose it's hard bricked. But what cause the brick in the first place? Any possibe way to recover the phone? Is it even hard bricked though?
What about battery charging % frist chik battery I think battery fult
Sent from my GT-I9505 using Tapatalk
Nah, it doesn't charge either. I tried plugging it in and turning it on. It still won't.
It's just sitting there. Doing nothing.
I did a very stupid thing and rebooted while flashing. Without my knowledge it was a bad and dumbthing to do. Now whenever I start the phone it goes to the white startup screen, but quickly turns completely off in disregards of any button combinations I enter. I followed the advice at this thread. But it seems like it isn't working because Smart Phone Flash Tool is just staying there greyed out with no progress bar.
UPDATE: I managed to get SP Flash Tool to work and in downloaded all the stuff and gave me a green check mark. This didn't affect my phone at all. I'm going to test the battery with my multimeter when I get home.
UPDATE 2: I tested the battery with DC Volt and it returned 4.31 V. Battery seems to be fine. Maybe phone is hard bricked?
UPDATE 3: I retried SP Flash Tool and for some reason I am able to access TWRP now. I'm currently preparing images that I will put on the usb to install them from TWRP.
FINAL UPDATE: I flashed the default rom and it didn't work because TWRP was unable to mount /data and storage. I reformatted Data to ext3 and rebooted and it worked.