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
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!
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.
(all ROMs referenced in this post are stock from sammobile for the N915R4, which is the model of phone I'm working on)
Bought a Note Edge off the bay and proceeded to downgrade it to 4.4.4 (was running on 5.0 or 5.0.1). Tried to root via some idiot's forum post somewhere that used odin to flash CFAR then TWRP then install the SU binary or something like that.. obviously, bootloop. Factory reset produced the same results sooo.. reinstalled 4.4.4 via odin and the phone booted up just fine. (After that rootfail, any boot to recovery gets me the red ! android logo, which it had not up to that point.) Unfortunately, the menus and such weren't the farmiliar dark I was hoping they'd be (like they were on my old 4.2.2 s3 or the 4.4.2 s5) so after a little more research, I decided to upgrade back to 5.0.1 so I could root and install samsung's S6 theme engine. Downloaded OG1 instead of OC5 and for some reason halfway through it quit out on me, phone said interrupted; get on kies, and odin said FAIL. Well, crap. Rebooted into download mode and re-flashed this time thinking my usb cable had just come loose and this time it completed and odin said PASS. Phone rebooted and went through the "optomizing apps" bit.. then bootlooped. Booted into recovery and wiped data/factory reset. Bootlooped. Fack. Re-flashed 4.4.4 thinking I'd just forgotten to enable usb debugging that time and if I did in 4.4.4 after reflashing it, I could reflash 5.0.1 and it would be fine. re-flashed 4.4.4 successfully.. and managed to eliminate the bootloop.. instead it booted up and froze after the us cellular logo. wipe data/factory reset.. bootloop. shlt. :crying: re-flashed 4.4.4 again, bootloop, re-flashed 5.0.1 thinking the bootloader had gone retarded, wiped data/factory reset before even checking for bootloop, and... bootloop. downloaded OC5 thinking maybe the phone originally came to me with that version of 5.0 on it (so if I installed it it would work) and flashed that.. odin said Pass and phone got to/through the "optomizing apps" part again, then bootlooped. wiped data/factory reset.. bootloop. goddammit. :silly:
Right now I can boot into recovery and into download mode but other than that I'm stuck as to what to try next. Obviously wiping data / factory resetting does NOT fix my problem, and that's the only solution google gives me no matter how I phrase the question.
What Do, xda?
Dumbest. Fix. Ever. Downloaded Kies3 from Samsung. Opened Tools -> Emergency Firmware Recovery. Plugged phone in. Didn't see the phone. Booted phone into download mode. Didn't see the phone. battery pull and re-set up. Closed EFR, returning to Kies3 Home. Turned phone on. Bootlooped. Booted to phone setup screen. Phone is working again and running on 4.4.4.
First off, I cannot boot into recovery so this isn't an option for me right now.
Phone: T-mobile Samsung Galaxy S6 (SM-G920T)
Firmware: Lollipop 5.0.2 or 5.1.1
**Not sure because I factory reset it this morning after updating to 5.1.1 yesterday.
Brick happened later in the day today.**
Rom: Successfully flashed TWRP this morning before brick occurred
Rooted: Yes, with Xposed Framework installed as well
So I rooted my S6 yesterday with no issue, then flashed TWRP today so that I could install Xposed. That went well until I downloaded a few modules in Xposed, rebooted my phone and the System UI kept crashing and wouldn't open. I entered recovery mode and attempted a factory reset through TWRP. Rebooted and got stuck at the Samsung logo with the "IS NOT SEANDROID ENFORCING" message above it still, so the wipe clearly wasn't successful. After that I realized my phone was bricked/in a bootloop or whatever so I kept trying to wipe it in various ways in TWRP. I even went into advanced wipe mode and selected every option (system, data, dalvick, cache, etc...even internal storage unfortunately, which I think screwed me).
Finally gave up and went into Odin (using latest version, 3.12) and flashed the SAME stock firmware I did the last time this happened (it worked then but not this time). Basically no matter how many times I try to flash stock firmware, Odin either gets stuck or fails. Tried both a G920T firmware tar.md5 file for 5.0.2 AND 5.1.1 and the 5.1.1 says passed every time but STILL does not get past the Samsung Logo screen ("SEANDROID NOT ENFORCING" message is gone now though, so I figure it did something) and the 5.0.2 firmware files just say fail every time. For some reason every time this happens all I can do is force restart the phone and enter download mode via HOME+VOL DOWN+POWER buttons but it just stays on the logo screen when I hold down the HOME+VOL UP+POWER buttons to enter recovery.
So I'm pretty much in a pickle. I'm at a total loss. I've done everything I know to do for the last 6 hours, including deleting the .md5 from the firmware files and all that mess. Can't find a .pit file in the firmware zip after it's extracted either and I've seen some threads say that I need one. I'm afraid this phone is a goner, so if anyone has any suggestions please let me know. Thank you in advance!
Hi !
I just want to be sure that you`ve followed the exact steps described here
https://forum.xda-developers.com/galaxy-s6/general/how-to-unroot-unbrick-galaxy-s6-t3110608
Good luck !
How can in get out of this boot loop, any advice, answers, help appreciated?
As background my Lenovo Tab 4 10 plus (stock 7.1 rom) had a failed SD card so I replaced the card and factory reset and thought I would try TWRP, Linageos 17.1 with magisk and relevent gapps - this all worked fine other than a Skype issue. I then found an 18.1 rom and tried that and this is where it seems to have gone wrong I set it up in the same ways as the 17.1 rom but with Andriod 11 gapps to suit, did a factory reset and 30 seocnds in I got the boot loop.
To fix it I tried going back to the 17.1 rom set-up that had worked but this then boot looped even with a full recovery reset. I have gone back to the stock rom backup in TWRP again with a recovery reset same boot loop. I have even used the Lenovo recovery tool to EDL mode flash a newly downloaded stock rom and it's still boot looping. I can only think that the 18.1 andriod 11 rom changed something fundimental but I can't find what?
Further I have another problem, the EDL flash worked but it locked the bootloader, however as I can't get in to Andriod with the boot loops, I can't switch ADB mode on so I can't unlock the bootloader to get TWRP up again.
So is there a way to start ADB without access to develeoper settings maybe through fastboot or recovery which I can get in to? Unlock the bootloader without ADB? Does anyone know why after the 18.1 Andriod 11 based rom, I have this continous boot loop?
I have a tb-x704f wich was totally caught in a boot loop, but I manisched to get back to working stock.
I was running firmware s000056 when I flashed twrp without backing up anything. I thought I never would have to go back to nougat, but standby time on lineage os was just not good for me, as I only use my tablet maybe half an hour a day, and I had to charge several times a week nevertheless.
So I tried to get back to stock and awesome standby time.
It was not easy bootloop after bootloop.
Tried Lenovo rescue and smart assistant multiple times, factory reset before and after flash, without SD card inserted etc, but bootloop.
Tried flashing the rom downloaded from the rescue tool with qfil but same result.
I then tried flashing the files with miflash 2016.08.30.0 still the same rom as I thought it had to be s000056. Miflash stopped halfway with some kind of error.
I then downloaded a stock rom from lenovo-forums.ru http://lenovo-forums.ru/topic/24135-lenovo-tab4-a10-plus-proshivka-tb-x704f_s000037_170703_row_qfil/
from the link in the discussion in the bottom of the site.
I had twrp still so from there I got into terminal and wrote "reboot edl" to get into emergency download mode and then flashed away. I presume that I could just as well had gotten in to edl mode by pressing vol+ and vol- simultaneously and then connected to PC holding those to buttons pressed. When the tablet was finished it was off, so I started going to recovery and wipeed cache and did a factory reset. Then booted and instead of bootloop it showed the Lenovo screen with a progress bar underneath. I successfully booted and took a update and then i am back to stock s000056.
The rom I got from lenovo-forums.ru stated it was only for EU and wi-fi model only. I am in Denmark and my tablet is WiFi only.
I think chances for success is greater using miflash than other tools when recovering from bootloop, but then again I don't know. Maybe I could just have flashed the s000037 rom with qfil or maybe I was just lucky, who knows.
But this what worked for me.
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
pallep said:
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
Click to expand...
Click to collapse
Thanks kind man You helped finish my struggle!
The only thing I want to add is that the ROM from the original link is no longer available, so I found the correct ROM using Google from the original filename here https://firmware247.com/lenovo-tab4-a10-plus-tb-x704f-firmware/