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.
Related
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!
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
I searched the forums before posting. 73 results came up and I read through and followed instructions of 7 different posts that seemed similar to mine (including the ones that appear when making a new thread), but nothing has worked or I haven't found a situation like mine.
Hi.
I have a HUGE problem and need help.
I was on Cyanogen OS 12.1 and decided to install the latest Cyanogen OS 13.1. I downloaded the flashable zip. Booted into TWRP recovery and installed the zip file. I had always allowed my phone to reinstall Super SU in the past with great succes, but it seems I shouldn't have done that according to someone in Oneplus forums. Now my phone is stuck on the bootup animation that says "Cyanogen MOD ready". I also cannot boot into the recovery or safe mode using hardware keys. Please help! I don't want to lose my phone or my data!
Thanks for any advice.
note: I used the signed flashable zip from here.
EDIT: I was able to boot into recovery using the command "fastboot boot recovery.img". I cleared dalvik cache and flashed COS 13.1 zip. Currently waiting for phone to boot. Hope it doesn't get stuck on the bootup screen again.
EDIT2: It looks like my phone has booted successfully and is now optimizing apps for COS update! If I don't follow up, it means everything worked out great again!
EDIT 3: My phone finished "optimizing" apps. I thought it would take me to my launcher as all other times I've updated. To my surprise, the phone seemed to reboot and was stuck on the "splash screen" (Cyanogen MOD ready). After that, I got the "Android is starting" "Optimizing app xx of xxx" message again, which is incredibly weird and I think my phone might be in a bootloop. PLEASE HELP!
EDIT 4: I remembered that I did a nandroid backup last February so I restored it with "restore" in TWRP. My phone has been stuck on the "Cyanogen" boot screen for about 40 minutes. I'm lost.
To recap everything:
1. I was trying to manually upgrade from COS 12.1 to COS 13.1
2. My phone was rooted, had TWRP recovery and ADB debugging was enabled in dev options. I can enter fastboot mode using hardware keys. I cannot enter recovery using hardware keys (shows a blank screen), but I can enter recovery using "fastboot boot recovery.img.
3. After I flashed COS 13.1, I was asked (in TWRP) if I wanted to install SU and I said yes and flashed it. This is when I was in a loop of being stuck on COS 13.1 splash screen for about 5-10 minutes and then my phone was "optimizing app xx of xxx" for 15 minutes and then rebooted and did everything all over again.
4. I tried to restored a nandroid backup using "restore" in TWRP, but phone is stuck in "cyanogen" splash screen for more than 40 minutes.
No replies...
Not sure what to do at this point.
I ended up wiping data and performing a factory reset through TWRP. Might try to upgrade again in the future.
I was trying to get lineageos on my s6 edge+ but it is stuck in a samsung logo loop after being unable to flash the rom and now it won't go back into TWRP either.
Initially I flashed the official TWRP for the zenlte which worked fine, it just did not want to install the rom due to apparently not having any device data. (Rom is for zenlte, this device is . (or something along those lines))
after a few attempts and doing a quick wipe I flashed an unofficial twrp and thats when it started looping without being able to get back into recovery mode.
Download mode does still work after a power off but flashing the official twrp again makes no difference.
This is a little beyond me and I'm not entirely sure what is going on.
The last phone I installed a custom rom on was an s4 so I'm a bit out of the loop with this new security stuff. I would have expected to at least be able to boot back into twrp.
Ok some progress:
Recovery mode worked again after leaving phone off (but still attached to computer) for a while. (I had given up but decided to try again after a few hours)
Partitions were missing / corrupted. Did a full format.
Installing rom still gave the 'device type is .' message.
Edited the rom zip to allow "" and " " ( in META-INF\com\google\android\updater-script )
Flashed rom + gapps + magisk in 1 go.
This ended up in LineageOS trying to start but rebooting into recovery after about 5 minutes.
Re-instralled just the rom, this gave a few errors about Magisk missing, re-installed Magisk as well before wiping cache and rebooting.
Now it came up with the welcome screen rather quickly.
Weird, but problem solved any ways.
Thanks! That was also my problem.
For the last couple years I've been following this process to retain root using the TWRP A/B Retention Script and installing Magisk to the inactive slot after OTA and everything been fine and dandy. However, after the last time I performed this process Magisk would immediately crash when I tried to launch its app. Upon investigating I noticed that the file it downloaded for flashing was suspiciously small, so I suspect it flashed a corrupted file. I had already successfully rebooted my phone several times after the OTA, so I figured it was just Magisk that got corrupted and TWRP must be fine. I recently tried to reboot into recovery and discovered that TWRP is broken too. My phone briefly flashes the TWRP logo before the screen goes black and it tries to reboot into recovery again.
I've been able to get into fastboot by simultaneously holding down the power button and both volume buttons. However, none of the options in fastboot actually get my anywhere. Choosing start, recovery mode, or power off just get me back into the TWRP bootloop, and restart bootloader obviously just keeps me in fastboot.
I assume I need to reflash TWRP and Magisk, but I'm not sure how to go about that. Can someone point me in the right direction? Thanks.
This is how I proceeded:
Downloaded the latest TWRP image (twrp-3.6.2_11-0-guacamole.img) from here: https://dl.twrp.me/guacamole/
Verified the md5sum to ensure the download wasn't corrupted.
fastboot boot twrp-3.6.2_11-0-guacamole.img
In TWRP, Advanced > Flash Current TWRP
Now I have a working recovery, but I still can't boot into my system. When I go to Reboot > System in TWRP it just boots back into recovery.
I enabled MTP in TWRP and copied off all the data I cared about, then used the "Flash Factory Images" option in the TOOL ALL IN ONE to flash 9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip. I tried it without checking the box to erase everything, hoping I could keep my data, but that didn't work. With that box checked though I was able to boot again, but I cannot turn on WiFi for some reason. I'm hoping the OTA will fix that issue. Does anyone know how to get WiFi working again or why it may have stopped working?
altayh said:
I cannot turn on WiFi for some reason. I'm hoping the OTA will fix that issue.
Click to expand...
Click to collapse
Fortunately enough the first OTA did indeed solve the WiFi issue. Now I've applied all of the OTAs and finally have my phone in a proper working state again.