Hey guys.
My friends Oneplus One 64GB got 'bricked' today, and I am trying to save it.
He has never modded the phone before.
Firstly, it got stuck in a bootloop.
I then cleared the cache, after which it worked fine.
About 2 hours late, the phone just switched off when he was using it.
I tried to clear the cache again, but there was no effect.
I factory reset the device through recovery, but it continued bootlooping.
I then downloaded the OnePlus One Toolbox from inthiaano, unlocked the bootloader, then flashed the official rr nougat.
it booted fine, but it immediately started bootlooping after it was unplugged from the computer.
I am on a windows 10 device, freshly formatted and installed, so i doubt its a virus from the computer.
After it started bootlooping, nothing would work.
It can only access fastboot at the moment.
Please help me.
Any help is much appreciated.
Related
The the device came in today and when I turn it on The Google logo comes, turns off and restarts for a boot loop. I even did a full restore using the recovery toolkit like swoggers and even then no luck. I was able to install twrp with no issue. Anyone have the same issue ?
Thanks
Anyone?
saadkhan07 said:
Anyone?
Click to expand...
Click to collapse
I had problems AFTER I installed TWRP, but before that it booted just fine.
My problems started after unlocking the bootloader and installing TWRP. Try wiping as much as possible (except System) with TWRP. I read somewhere it's a problem with the cache partition. I also went into "Mount" in TWRP (I think that's what it's called) and mounted System. I'm telling you all this from memory, not sure exactly how I fixed it, but eventually I was able to turn the phone on.
Hopefully this is the reason you're having problems. It'd be frustrating to have to try and get another one from the Goog.
Hi guys, my phone is right borked and I hope someone can help me out. I've been searching forums all day and I find bits and pieces of advice that apply to parts of my situation, but haven’t found a fix yet.
I installed CyanogenMod on my Rogers Samsung G3 a couple months back. Everything has been going smoothly until last night when I installed an update.
The phone rebooted and got stuck on the Samsung splash screen with the blue cyanogen dude. I left it for 30 min and when I got back, it was still the same.
I took the battery out, turned it back on and ended up in the same spot. I took the battery out again, turned it on and left it over night. Same thing this morning.
On advice from this forum I put the phone in recovery mode. I thought I had TWRP, but Clockwork Recovery comes up.
I did a factory reset, and cleared the cache. Rebooted and still the same thing.
I tried to flash the ROM, but it doesn't work. The android dude just lies there, dead. Poor guy.
I plugged it into my computer but even though the computer makes the connection ‘cah-ching’ its not recognized. Through the recovery screen I tried unmounting and mounting everything, and mounting as usb and the computer still won’t pick it up. I uninstalled Kies, and the drivers for the phone and re installed everything. The driver pop up says MTP has failed.
Any suggestions?
Hi, last week my phone started behaving very weird, out of nothing the phone freeze and stopped working and reboots itself and then got stuck on the boot logo, I tried to go to recovery via bootloader, but it didn't work, I tried everythging but it the only thing useful was connecting it to the pc and wiping cache via fastboot. This happened like 3 times a day. Now I have reflashed the stock firmware, installed some apps, xposed and other things, and when my device was ready, started behaving the same way like before, I don't know what to do now. please help.
Im using retail us 4.4.3 firmare.
this never happened with 4.4.2, is there any way to downgrade?
I followed this guide to restore stock firm: http://forum.xda-developers.com/showthread.php?t=2542219
Hi and thanks for reading.
My S6 is the 920p model. I had it rooted with Magisk v16.0, stock kernel, no xposed, DRA2.
Let me explain what happened.
Yesterday, I woke up because of a call sound. Once I finished talking, I tryed to unlock my phone using the fingerprint sensor. It was unlocked but suddenly it rebooted. When it booted I tryed to unlock it using the pin (obviousy), but it rebooted again.
I made a few more attempts but no luck, so I booted in TWRP, backed up my data on my laptop and made a factory reset.
Now the phone doesn't finish the boot, it only stays at "Samsung" blinking logo and the led in blue dimming, restarting again and again.
I installed the NexusOS 8.1, it booted, the phone is usable, but this rom doesn't recognize modem, so, no signal (Sprint modem not supported).
Since it works with that rom installed, I tried installing the DRA2 stock firmware wich I had installed at the beginning, but again stuck at bootloop.
Next thing I tried was using .pit file, and flashing one by one bl, ap, cp and csc. It only reached the "Optimizing apps" and rebooted again. I booted into recovery, wiped cache and reached "Starting apps" but, te phone rebooted again.
Right now I'm using it with the NexusOS rom wich is pretty, but with te Ril issue.
So, that's my problem, hope somebody help me.
Finaly solved: I just had to mark (Phone EFS Clear)
Apparently EFS was corrupt. After that, I had to unlock it. It's working properly.
Hi everyone!
Yesterday my GT-3100 got stuck on bootloop. Around two years ago, I got tired of seeing the Jellybean look so I gave custom ROMs a try. Even though I was incredibly scared of bricking my device, I went through with it anyway and flashed CyanogenMod 12 and made sure to make a backup of the stock version. Ever since then I've used the upgraded Lollipop 5.0.2 version. Occasionally it would get stuck on bootloop and it would get fixed on erasing the cache partition. Just yesterday the bootloop started again and even after trying everything, nothing's working.
I have CWM Recovery v6.0.2.7 installed, which I installed 1.5 years ago. I have tried factory resetting and after it rebooted I realized that nothing was even erased. My backup seemed to have disappeared as well since CWM can't find it even though it takes up almost 8Gbs of storage. After restarting, the home screen appears for about 30 seconds before restarting again in a continuous cycle.
I'm a noob when it comes to these things so any help (in simplified language) helps.
Thank you so much! :laugh:
Its probably a broken emmc. That means you need to replace the motherboard.