Hi all,
I wanted to access TWRP on my Huawei Y300, so I switched the phone off and tried to boot into recovery... But to my horror the phone just froze on the startup logo and I was unable to enter TWRP (waited several minutes but nothing happened). I've repeated the same process several times but still can't enter recovery...
I haven't been messing around with the recovery recently... But it should be noted I erased both the external SD and internal SD on my phone yesterday, so I'm guessing this is the cause of the problem.
What should I do? Is TWRP completely gone or is it still there but inaccessible? Should I reflash TWRP through fastboot, or will that aggravate the problem?
Thanks so much for your help, happy New Year.
Related
Hi. Just got a Note2 which was running 4.4.2
I downloaded Odin3-v3.07 and got root access. I then used a checker to confirm.
From there, I used the TWRP Manager to install 2.8.7.0.
I think this is where things went wrong. I know I selected the correct phone model, but it gave me an error saying something went wrong ( I think it said something about me having the latest TWRP) . Then my phone rebooted and took me into TWRP.
I made a backup and tried to flash the CM12 rom for sgh-i317m.
That's when I noticed I couldn't get out of TWRP. Rebooting or pulling the battery has no effect. Phone keeps booting into TWRP. I tried wiping delvic cache, cache and other things, but no matter what I do I can't boot into the OS. I tried restoring and it says it was successful, but again am stuck in TWRP. I've now spent the last hour searching for a way to get out and still can't find a solution. Any help would be greatly appreciated.
Notes:
Not sure if this has anything to do with it, but I had forgotten to enable USB debugging when I was in my OS.
Another thing I noticed is when I open the terminal command, there's a running boot script error: E:/sbin/runatboot.sh process ended with ERROR=1
Problem resolved: I booted into download mode and used Odin to root again. That seem to overwrite whatever was causing the Note 2 to be stuck booting into TWRP.
I enabled USB debugging and installed TWRP again. Got the same error but this time chose not to reboot into recovery. Then I rebooted manually, and the phone boots into the OS. I powered down and held Vol up + power + menu and released power button at Samsung logo, and was successful in booting into TWRP. Exited and rebooted took me back to the OS. So I'm not quite sure what it was the first time around that got me stuck into booting TWRP everytime.
Glad you got it fixed! :good:
I'll close this thread.
Dear all,
I have read through most (if not all) the other "bricked" device threads, but they don't really fit my problem.
I was on TWRP (sthg) and CM 12.1 (latest) here from the forum.
Everything worked fine for ages.Yesterday I used the device to the latest miliAmpere and only later the connected the complete empty Tab to the Power and restarted it.
Next morning the device showed "Encryption failed" and something that I have to do a factory reset. There was a "reset"-button, but I didn't used it and shutted down the Tab via the power Off function.
Since then the device is not reacting. Currently it is bootlooping into TWRP (!). I cannot switch it off and it actually gets rather hot. The only way to stop this "cycle of death" is to go to download mode...
I already tried to change the recovery to CWM and also to TWRP again via ODIN. ODIN worked fine, but I still cannot start the recovery. TWRP makes a boot loop with its logo and CWM loops without showing anything.
I wonder what will be the next best steps. Odin is working fine, so I don't want to ruin that as well.
What do you think? Is the Bootloader corrupt?
Why does it always boot into recovery (I can't get into a System-Bootloop)?
Any help is really appreciated!
Best,
Jan
After I have reinstalled the original firmware from sammobile, I could boot into recovery. I then factory reseted, flashed TWRP via ODIN and switched back to CM12.1.
I lost all my data, but at least I still have my Tab
Best,
Jan
Today at 12:52 AM
My phone was rooted. I was using s5 rom proyect and my recovery was Philz Touch Recovery. I was happily using this rom for arround 8 months. Recently my phone was responding slow and my storage was almost full. One day while watching youtube videos my phone got hang! I just removed the battery and tried to restart. But there was a failure and no vibration. The phone is simply dead. I connected my charger and of :crying:course there was no indication. Later I went through several post to learn how to revive my phone from hard brick. I downloaded debrick.img file and made a bootable memory card. This time I was able to switch on my phone but it went through bootloop. The recovery mode takes too long to load and wiping cache and dalvik cache or even reset was not possible because of some error like E: failed to mount ......
Then I went into the download mode. and installed a firmware from sam mobile. Later I flashed CWM recovery through odin successfully.
But this bootloop still exists. Whenever I try to go into recovery mode it still takes a long time. And istead of loading CWM recovery it loads philz recovery mode that was previously installed
Please help I am tired
So I was trying to switch over from supersu -> magisk and something happened and now I can only access erecovery (can't access twrp or when I boot normally I just get the honor logo there forever). When I tried downloading latest version I get an error. What can I do? Please help ASAP since this is my first phone and I don't wanna mess up already
*EDIT
I can actually boot into twrp and my PC can access my phone but the only thing in the storage is the folder "TWRP" which is empty.
I faced the same problem and I fixed it somehow but I don't remember how actually I did that. But I guess I did first format the device using twrp and then flashed the magisk agin.(try it, but I am not sure if it was that or not, i did that about 3-4 months ago)
I bricked my device when I went to twrp and did a wipe when I was trying to fix a bug where it said there was 0mb in storage.
Hi, guys.
I picked this xt1033 and it had the microusb input damaged, so i replaced it, but since then, it got stucked on motorola logo.
I guessed that the system got corrupted and then i uploaded some new system. It went through nicely, but when it rebooted got stucked again. So, i'ved unlocked it bootloader (to start from zero) and re-locked it, putting a new system from the ground and apparently it ended well, but it got stucked again on logo (and later i've founded that it didn't lock). I've begin to put TWRP to install a custom rom on it (to see if i've could pass throgh that) and founded that my files was still there (EVEN AFTER I'VE UNLOCKED THE BOOTLOADER, who would've erased everything from inside), system, images and even whatsapp files. MTP Service give-me a taste of what was inside and everything was there, nothing corrupt.
So i'ved erased it and put a new rom, TWRP said it did it and was asking for reboot, so i did.
And it got stucked again and nothing was erased.
So the thing is, it's internal storage is freezed and i can't do anything with it.
Could you guys help me? Thanks in advance.
i may be wrong here... but i dont remember unlocking bootloader erased my data.... but it was long time ago...
coming back to your problem.. have you tried using repair option in twrp?
also try wiping all partitions and do a recovery reboot to see if it works
access_unlimited said:
i may be wrong here... but i dont remember unlocking bootloader erased my data.... but it was long time ago...
coming back to your problem.. have you tried using repair option in twrp?
also try wiping all partitions and do a recovery reboot to see if it works
Click to expand...
Click to collapse
Already done.
I could only enter TWRP by boot it on bootloader, not flashing ('cuz was impossible to write on memory and was saying that the flash was successful).
TWRP said it wipe it completely without any error, but it's was there.
And by ordering to reboot on Recovery Mode, it went back to original recovery and trying to erase from there do the same thing (said that was complete, but everything is still there).
Same problem here, this is a problem with emmc bricked