Hi,
So I was on the unlocked kit kat for awhile but it was so slow the tablet was unusable. I went to upgrade to lollipop and all hell broke loose.
Now, when i boot the twrp recovery it asks for a password (i never set one), and then when I hit cancel to bypass the password screen, if I try to wipe or install anything, it fails with a can't mount cache error.
I can boot the recovery and fastboot and that's about it.
Any advice? I tried flashing other recoveries but it seems to fail when trying to do that as well because the tablet will lockup after sending and then when I restart the same recovery is there.
Can anyone please help me!?
Thank you!
So to add to the problem... or what is probably the biggest problem I'm encountering is...
Whenever I flash something in fastboot, the device hangs!
I am desperate for some help guys please!
Did you fix this ?
Related
Hi Guys,
I tried to update my TWRP, I think Modded 2.6.3.0 TWRP for KitKat from Voyager2k. But.. I didnt know, that there is a issue with password requirement. So i cant mount any partition, cant wipe or instal anything. Same time I got brick 1a, it always immediately reboot into recovery. No way to get into fastboot mode (power + vol Up). If I follow steps here http://forum.xda-developers.com/showthread.php?t=1514088 nothing happends. As well I attempted to use fastboot, erase, flash. WSG UnBricker doesnt work too. Everytime appears only "waiting for device". So I am stuck in TWRP, but cant do anything there.. Please tell me, it is not hard bricked..
Thanks for any help.
Hello xda,
Basically, I am stuck on booting screen. All I see is that blue cyanogen boy. Dammit. I feel so miserable now. I tried everything to solve this problem, yet without any progress. I think I know where the problem is, I forgot to wipe the data and cache before I began installing the Cyanogenmod.
Stuff I tried (the goal was to wipe all the data):
1. Can't get into recovery mode
2. Can get into download mode, yet odin doesn't recognize the device or something
3. Tried to wipe all the data with adb, using adb shell --wipe_data, it says /sbin/sh: --wipe_data: not found
Can anybody please help me? If you need some more details, let me know down in the comments
Hi guys, I really need your help.
I'm new at this rooting stuffs and I tried to root my Oppo Neo 5.
I tried so many softwares like OneClickRoot, FramaRoot, and Kingroot but none seemed to work.
So I resorted to an app called oppo tools
It worked at first but I got really annoyed when my status bar suddenly colored to red when my phone discharges to 15% so I unrooted my phone and rooted back again. I really thought that was going to fix my problem but that's where the bootloop issue started.
I tried to flash some custom recovery zip but it failed since I only have a stock recovery.
But the thing is, I found a guide that says to rename the clockworkrecovery img to PG86IMG.zip.
So I did tried that and as soon as I flashed the zip from my stock recovery, my phone hanged.
I long-pressed the power button to restart and boot into recovery mode but nothing seems to happen.
I'll try to explain a bit more on how it looks when I boot my device.
When it boots normally (I mean not pressing the volume to enter recovery mode) it will only show the logo but when I try to go into recovery mode it will show the logo with a little text on the lower left portion "Recovery Mode"
Before I flashed the PG86IMG.zip, recovery mode was still working and the charging screen when off is working too.
but after I flashed the zip, every time I try to recovery mode the logo shows up with the little text but RECOVERY MODE isn't working. When I charge my phone it automatically boots up and shows the logo and text like it's trying to go recovery mode (I'm just trying to charge? It's going to recovery mode)
I tried using "adb devices" on cmd but it's not detecting any devices.
I'm really out of ideas guys, I know not all people use this model but what would be your suggestion?
A suggestion on how to fix this would really be appreciated :good:
I'm sorry I'm really new at this, please correct me if I did something wrong starting this thread. :angel:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Salman Al-Badgail said:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Click to expand...
Click to collapse
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
DeepBricked said:
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
Click to expand...
Click to collapse
You made a soft brick, not to worry flash it with correct stock firmware, if the phone is in warranty than ask them to do flash, this will take approx 10-30min. If it isn't in warranty than you should try it own or else pay some amount and the rest they will do.
Salman.
how about bootloop, cant enter recovery, reboot continiously when turn on even going to recovery, only fastboot isnt rebooting automaticaly but pc days drivers not succesfuly installed, and when off it qont detect by pc because of rebooting auto,
where can i find a rom for my oppo neo 5
pls help me pls
Hello everybody, My father's old S2 was running well till today, then suddenly it didn't wake up. Tried restarting and got a kernel panic. Then, nothing. The phone stucks on the I9100 logo or sometimes tries to boot, but it's stuck. It DOESN'T enter recovery mode, only download one. I was running a modded Nougat or Marshmallow ROM, and I've found a soft-brick/NAND RW corruption thread here:
https://forum.xda-developers.com/galaxy-s2/help/guide-fix-unflashable-soft-bricked-gsii-t1457458
It's quite old and I don't know if it works, it refers to the old ICS, and, since I don't want to mess up things more than this, I prefer to ask you if someone has some other recent discussions or solutions for me.
Thank you so much in advance!
Guys can someone please help me? I tried that guide but I can't enter recovery mode, I tried flashing the CMW recovery with ODIN and it always get stuck on "NAND write start!". There is no chance to revive the phone? I can't flash a ROM with ODIN too, it gets stuck at the same point..
Also had the issue once that my device suddenly wouldn't boot up anymore. Also recovery didn't work. I fixed by flashing another recovery via Odin in download mode.
Did take quite long though until I finally succeeded, because at some recovery flashes Odin wouldn't pass 'NAND write start' or something. I tried with different recoveries and USB ports and somehow managed to get it working again. Then I wiped data, cache, system and reinstalled the ROM and Gapps.
Hope this helps.
Realme 5i, I flashed a C73 firmware on it. It rebooted but kept restarting. The fastboot fix (file attached) that a kind dude gave me used to work but it doesnt work anymore. What Im guessing is, I flashed the wrong firmware so how do I delete it? I can go to fastboot but not recovery mode which the fastboot fix should fix but didnt. Any help is appreciated. If I somehow fixed past this, is there a way to know my exact build number? Through custom recovery or anything(pc) cause I dont have any OS on my phone.
Edit: I've fixed the rebooting loop but whenever I try to use the same method I did to fix fastboot, it goes back to rebooting automatically and not letting me go to recovery mode. Also, I still want the firmware removed maybe that way I can do the fix once more and hopefully it would work again and flash a new firmware.