I bricked my phone while downgrading from the Brazilian lollipop to Asian Kit Kat, I did it directly which I think was my mistake. My phone won't boot up android or even the recovery (twrp). When I do a fastboot and choose recovery it will reboot into the recovery and show the flickering screen (different from the one you get after downgrading) and shows the android symbol with a warning sign. I tried to flash a new cm12 while the recovery was working and it said it was successful, which caused the damage to the recovery. At that point my phone could no longer be detected by my windows PC (tried on a different PC with ubuntu). I took my phone to some stores thinking it can be repaired but they failed, they only managed to get the recovery to work again (cwm). I tried installing a cm12 again using otg, it seemed as if it was successful but when I restarted my phone it failed and broke the recovery again. I just left the phone till it ran out of battery since it won't turn off. I'm hoping someone out there might have a solution, I tried most of what I could find on the net but alas.
Is there no one with a solution :crying:
Related
Ok so I have a sprint nexus s 4g that has never been rooted/modded or anything. It all of a sudden won't boot android now, it just stays at the "Google" logo, so I guess it is bricked but I have no idea how it got to this state. I am able to boot into recovery and download mode so I did a factory reset and wiped cache but still I was unable to boot. USB debugging was disabled when the phone was bricked so I am unable to use adb and fastboot. I managed to re-flash the stock rom via odin which unlocked the bootloader (odin actually recognized the phone in download mode), but still I have had no success... is there any way to get into android or is this a hardware problem? (i'm okay with rooting I've done it a couple times with another device) this is just a spare phone that I have to just mess around with since I recently got my upgrade.
my phone is running cyanogenmod snapshot m9
yesterday i tried to flash the new twrp recovery with flashify.
an error must have occured because after restarting i am stuck.
the phone wont boot it just goes directly to odin mode.
at the top of the screen in red writing it says "Could not do normal boot"
my laptop wont recognize anything being pluged into the usb
when i plug the phone in with no battery the red light turns on for a few seconds then goes out
not sure what else to try
thanks for any help
Looks like me and you caught the same bug.
You make any progress? I too atempted to flash TWRP 2.8, I used terminal emulator. Caused hard brick however I used the sdcard bricked boot and I can now get it to boot to ODIN. But every attempt to flash to stock or flash a new boot-loader, fails
Hello everyone
I own the Motorola Moto G ( 1st gen) xt1033 model. I had cm 13(latest release) flashed on it and my custom recovery is TWRP 2.8.4.0 and it was working fine until today after using it for around 2 months.
So what happened today is that while running an application, my Moto G shut down randomly( I don't know the reason for that),and it got stuck in bootloop ( Everytime I start it, the cm logo will appear and then it sometimes even shows my lock screen but instantly becomes black after that and most of the time its stuck only on the cm logo). After this I thought of restoring it back to the original firmware using this link: http://forum.xda-developers.com/showthread.php?t=2700502
I can get into fastboot mode but can't access the ADB as USB debugging mode was not enabled ( that's the main problem )
So following the procedures of that post, everything worked well on the log of the fastboot (no errors) but after that when I reboot my phone, again the cm logo appears (Even when I flashed it to stock 5.0.2 Lollipop!) and I can even get to my old lock screen sometimes and then instantly it goes black. Even if I try flashing a custom image like stock or some other ROM , it gives no effect as again the cm logo would appear.
I think this has to do with the fact that USB debugging mode was not enabled on it.
Also, I can't enter my recovery. When I use the standard procedure to get into fastboot (power button + volume (-) ) and select recovery, the TWRP splash screen comes then the screen turns black and normal reboot takes place( stuck on the cm head). I tried flashing different recoveries using fastboot (also tried mfastboot) like CWM and even TWRP again but still that bugged TWRP recovery remains.
I can't get to recovery neither can I boot up my phone. I can flash recovery or image files(It shows no errors flashing things, but no effect takes place :/ )
Can someone please help me in finding the solution for this problem? Thanks in advance
Just clear the data, cache and dalvik cache. Phone should boot
Hello,
I apologise for any mistakes as this is my first time posting here.
I recently changed the screen on my brothers OnePlus One. The installation went really smoothly and the phone displayed on startup.:good:
But for some reason now when ever it it starts up you get a 1+ logo and then it has the android man with the red triangle. It then puts you into recovery . My brother has never tried custom roms on his opo, so he has the stock recovery. I try to install some zips using the ADB sideload method but it gets about 80% done and then says that the signature verification failed even on roms downloaded from the official site. I think the phone would work if I could get TWRP installed and install the rom through there, but I can't get into fastboot mode. My brother has never been in fastboot so I don't know if you had to enable it in the OS first or something like that. If I press reboot bootloader in advance settings in the recovery it just restarts the phone back into recovery. I am not sure whether to try some type of brick fix method however it isn't hard bricked because it turns on and in soft bricked you have to use fastboot for every method that I've seen.
Any help would be brilliant.
Thanks!
Hello, i have a moto g5s plus and i tried to root my devices using TWRP and magisk..
but after loading TWRP recovery magisk was not loading and kept returning an error..
then in order for it to work i accidentally wiped my system files, but managed to write different OEM versions like Sanders, Potters etc.. still showed some issue like no OS found, cycle rebooting in bootloader, fastboot to bootloader as UTAG bootmode configured as fastboot,
also tried different oneslike lineage, resurection, beanstock etc..
Untill This point atleast the phone used to boot either to bootloader or TWRP recovery.
then i gave my phone to a friend that uses one plus 3, he tried to boot the phone using some of his tools and tricks and finally NOW!!! the phone does not boot at all...
whenever you connect the phone to the computer is just keeps blinking..
I have tried to get the blank flash solution but it did not work for my device..
please help!!!