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
Related
Hi people.
I´m facing a problem with my Tab 2 P3100. Some time ago i´ve installed a costum rom ( cyanogen 10.1 ) and everything was fine, but now after one minute tablet restart and after 1 minute ir restart again and so on. I´ve try to install another recovery by ODIN and with CWM because i have CWM 6.0.1.3, but no success. After try install another recovery, CWM stills there!!!! With ODIN and with CWM the recovery i get a message that "new" recovery is installed, but when i restart recovery 6.0.1.3 stills there. I´ve already try to format sd card, wipe everything, but tablet is the same, with all my apps and configurations, everything i tried is useless. Can anyone help me with this? Tank you...
Sounds like your EMMC lifetime is over... it became read only.
Hello everyone, I need help with my Galaxy Tab p5100.
Few days ago, I switched from CM 10.3, to SlimKat. To do so, I had to install the CWM 6.0.4.5. I did this through recovery mode (I had an earlier version and flashed the new version through the older one) and it worked just fine.
I unlocked the root feature, installed some apps, including the Xposed Module, Greenify and BootManager.
Everything was working just fine til yesterday. Before sleeping, I turned off the tab.
Today, and all of a sudden, as soon as I turned the tab on, it keept on rebooting every two minutes for no apparent reason. It just starts, boots into Slimkat, then it reboots.
At first I thought it might be a malfunctioning app, so I booted into safe mode, it stayed a little longer than 2 mins without a reboot, then it rebooted again. Tried that more than once.
I did a factory reset, wiped cache, cleared Dalvik and formatted system from the mount and storage section. Still the problem was there, and surprisingly all my apps and personal data was still there!!
Tried the back up and reset option from the ROM itself, while on safe mode, and still nothing happened.
I tried to flash CM 10.3 back via the CWM, it tells me that it succeeded, then I reboot and SlimKat is still there!
I tried to install the TWRP via Odin, and the Odin said PASS. Then when I rebooted into recovery I found that CWM 6.0.4.5 still there!!
I tried to flash the TWRP via the existing CWM, and again it says operation is successful but when I reboot into recovery I find that CWM is still taking over.
I even tried to flash the official JB 4.2.2 ROM via Odin, and it FAILED. (the P5100XXDMH1.tar file)
I feel pretty helpless and I don't know what to do. Any help would be appreciated.
Thanks in advance!
Update 1: I can delete an app or two before the tab restarts, and when I did and the tab restarted, the apps were restored!
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
Long story short I was running latest nightly of cm13, I decided to flash to cm14 to try nougat. I had backups, during the process I pulled an idiot and wiped everything dalvik, system,data,internal storage,cache . So now I have no backups, I can still get into TWRP and attempt to flash Roms but I've tried countless ones and same outcome, TWRP just restarts half a second after it tries to flash, I've even tried the stock rom with no luck.it starts and gets to MTP enabled installing "name of rom" and then reboots . I've been using a tablet to install the Roms onto an sdcard and then using the sdcard to flash, I'm hoping it's an sdcard issue and I'm waiting to get the laptop to try and put the Roms on internal phone storage and try. I'm hoping I won't have to go back to unroofed stock using kdz tot. If anyone knows what's wrong please help.
Well I tried flashing to stock and can't get into download mode, computer won't recognize phone. So I decided to try updating Twrp flashed the image, rebooted and now I'm stuck on [11050] fast boot mode started. Nothing gets me out of that.