Related
Long story short:
EDIT: I somehow magically (after 2 hours of trying) got into recovery, cleaned and wiped everything and booted into MIUI. Switched to CM 12.1, leaving this thread for anyone that experiences the same problem.
1. I was running CM11-R24, with an early version of the Xcelerate kernel. All was fine and well but today it restarted on its own a couple of times. It would enter a bootloop that I managed to get out of by going into recovery and rebooting from there.
2. Bootloop happened again, couldn't get into recovery.
3. Installed newest twrp recovery via fastboot. No change.
4. Managed to hardbrick my phone by installing a wrong .img of a global version.
5. Managed to revert back to a softbrick by installing the right (hopefully) global version of my mobile phone.
6. I did manage to read a logcat inbetween and I remember there being something about the kernel settings being nulled to default, because there was a failed boot 2 times in a row.
Links:
Hard-brick to soft-brick procedure I followed - http en.miui.c o m thread-54139-1-1.html
Used global version: Singapore 50? Going to try other versions
Settings in MiFlash tool (using 2014.11 version). - http postimg.o r g /image/hh122e54j
Current problems:
1. When powering up the phone, it will not go beyond the Mi logo.
2. When trying to enter recovery (volup+power) I enter another loop. It is normally 10-15 seconds of Mi logo, power down, 3-5 seconds of Mi logo, power down. Repeat. I do not stop holding the recovery combination while this happens.
3. I have installed via fastboot all of these recoveries - TWRP 2830, TWRP 2860, Philz latest recovery. After installing each of them, I can not enter recovery mode again. Flashing a new recovery doesn't seem to change that.
I have access to fastboot, currently I installed the stable fastboot rom version "armani_images_JHCCNBH45.0_4.3_cn_e7e373f319".
I can not get adb to recognize the device, only fastboot. Can't get a logcat because of it. If you think I might be doing it wrong, please walk me through the process.
How do I get it back to working condition? The phone was bought in Bulgaria from a retailer, but I don't know which country it was originally shipped from, only that it's a WCDMA version.
Throw it away and get your self some reliable phone unlike redmi , it's a crap lots of issue ... I prefer Motorola .
ford.sushil said:
Throw it away and get your self some reliable phone unlike redmi , it's a crap lots of issue ... I prefer Motorola .
Click to expand...
Click to collapse
Oh oh oh don't be rude everyone has his own priorities and financial limitations
Bootloop
Dude, I have the same problem, can you help plus?
Hi Folks,
I have a Tab S 8.4 wifi that I seem to have broken. I was attempting to restore the stock Marshmallow rom and something has gone horribly wrong. This is what I did:
1. I installed the latest stock rom by Odin and booted
2. I then downloaded and installed CF auto root/TWRP for the SM-T700, however, I failed notice that I had left NAND erase checked in the Odin settings so now all I get is the device attempting boot into TWRP which doesn’t work.
The device won’t turn off to allow me to use the buttons to access download mode which I know is what I need. I have tried draining the battery completely but as soon as power is restored it attempts to boot into the failed recovery again and is, in effect, stuck on the TWRP screen, periodically flashing the screen. It its broken TWRP state, the computer recognises it as a USB MTP device but will not recognise with the correct drivers to allow me to use ADB to force it into the download.
Does anybody have any suggestions? Otherwise I have a £250 paperweight!
unsrm said:
Hi Folks,
I have a Tab S 8.4 wifi that I seem to have broken. I was attempting to restore the stock Marshmallow rom and something has gone horribly wrong. This is what I did:
1.I installed the latest stock rom by Odin and booted
2.I then downloaded and installed CF auto root/TWRP for the SM-T700, however, I failed notice that I had left NAND erase checked in the Odin settings so now all I get is the device attempting boot into TWRP which doesn’t work.
The device won’t turn off to allow me to use the buttons to access download mode which I know is what I need. I have tried draining the battery completely but as soon as power is restored it attempts to boot into the failed recovery again and is, in effect, stuck on the TWRP screen, periodically flashing the screen. It its broken TWRP state, the computer recognises it as a USB MTP device but will not recognise with the correct drivers to allow me to use ADB to force it into the download.
Does anybody have any suggestions? Otherwise I have a £250 paperweight!
Click to expand...
Click to collapse
The file you flashed doesn't work on Marshmallow.
Use the updated twrp and supersu in the dev section.
ashyx said:
The file you flashed doesn't work on Marshmallow.
Use the updated twrp and supersu in the dev section.
Click to expand...
Click to collapse
Thanks for the reply ashyx, I don't current have a way to achieve that as I cannot access download mode. Any suggestions on how to do that?
unsrm said:
Thanks for the reply ashyx, I don't current have a way to achieve that as I cannot access download mode. Any suggestions on how to do that?
Click to expand...
Click to collapse
You can access download mode anytime irrespective of the current state the device is in.
Hold POWER + HOME + VOL DOWN until the device boots in to download mode.
ashyx said:
You can access download mode anytime irrespective of the current state the device is in.
Hold POWER + HOME + VOL DOWN until the device boots in to download mode.
Click to expand...
Click to collapse
I did't realise it would work in any mode!
Thought I'd tried it but obviously not held long enough.
You are a star! Thank you so much.
Chris
hello,
I tried to flash twrp to my p605 but when I boot to recovery I get this message " Recovery is not Seandroid Enforcing".
The only solution is to reflash twrp checking autoboot to fix problem. I have tried various versions of twrp. how I could fix this problem?
I am not rooted and I attach some info of my device.
thanks a lot.
any idea please?
Two ways to fix this error
georgew2 said:
any idea please?
Click to expand...
Click to collapse
It is likely you used the wrong TWRP for your Note (LTE version for P605). Be sure to use this xda forum for version and instructions. Sadly I have also made this error on various devices I have owned over the years. lol
https://forum.xda-developers.com/showthread.php?t=2515656
The first method is to boot into recovery and wipe data and reset to factory. The drawback here is you lose (probably) all your data, and it may not work then you have to try the second method anyway.
1: Power off your Samsung Galaxy Note 10.1. Make sure that it's completely turned off, this is the tricky part because of the bootloop. It takes patience and timing.
2: Now press; power, home and volume up to enter the recovery mode
3: Hold the buttons for at least 5 seconds until the android logo appears on the screen
4: The screen will be redirected to the recovery mode of your Samsung Galaxy Note 10.1
Use the volume button to navigate between the options and power button to select the highlighted option.
The second method, especially if that does not work, is to use ODIN to re-flash stock firmware onto your device. That is a process that using search will get you great detailed instructions, much better than I can describe.
Linuxmon
(search is your friend)
thanks for your time to help me. i downlaod twrp files from here: https://twrp.me/devices/samsunggalaxynote1012014qcom.html
I wonder if the new security udpate of february 2017 causes problems of installing twrp.
i will consider if i will try one of these methods.
Hi there,
first of all, sorry for my bad english.
I want to remove the Stock ROM from my Tablet (Samsung Galaxy Tab S4 | SM-T830) and install something else (https://www.getdroidtips.com/android-12samsung-galaxy-tab-s4/).
For some Reason Samsung forced me to do a factory reset to unlock the bootloader (maybe I did it wrong, but now it happened, so it is how it is). Now the OEM Unlock Options says "Bootloader is already unlocked", but when I go into Download mode, I have multiple Problems:
1.: When I enter download mode by Booting into Recovery (adb reboot recovery) and choose "reboot to bootloader", OR by entering it directly using "adb reboot bootloader", I dont get the Warning Screen so I get into download mode directly.
2.: When entering Dowload mode as descibed in problem 1, I also dont get the informations at the Top left, I only see the Download Icon on a blue background but when restarting the tablet and holding Volume Up and Volume Down simuntainuasly, it will show the warning (in the correct cyan colors) and in the next step it shows me those status informations at the top left.
3.: However, regardless to how I get into download mode, the colors of the download mode screen will change to a blue filter version after one second. but I did never activate any blue filter on the device, and on any other device, the colors are displayed correctly.
4.: Any instalation with Odin3 failed on the device, regardless to how i got into download mode
In any online article I read, noone has any problems with installing something when in download mode.
Also, the KG-Status is displayed as "checking, I dont know if this is good or not.
What am I doing wrong, why can't I install anything on the device?
what is wrong with download mode? post a picture.
drivers installed correctly? check in windows device manager.
what does not work with Odin? what error message?
First of all, thank you for your reply!
1.: The Picture shows that the is something wrong with the Download mode of the Tab S4, because the Colors are not being displayed correctly (as you can see, the colors of the other devices are much more cyan), and I would not have mentioned that if the device would just be unable to show colors correctly, but in the Warning before the Download mode, the Colors are displayed as they are on the other devices, so the eventually the device wants to tell me something, but I dont know what.
2.: Well, I am pretty sure that the drivers are installed Correctly, because Flashing a Galaxy Tab S2, Galaxy S8 and Galaxy S5 worked perfectly with the same driver.
3.: I'l attach a Screenshot of Odin.
ALso, what does "KG STatus: Checking" mean? Is it the reason for the problem, or is it good? On the Web I could only find "Kg Status: Locked" and "KG Status: Unlocked". should I unlock it? If yes, how?
you say any installation with Odin3 failed. you are trying to flash TWRP.
try to flash something different.
https://topjohnwu.github.io/Magisk/install.html#instructions
not sure about the display, though.
Well, I have a porblem with the Program that is mentioned in the Guide you linked, Frija asks for a CSC, and I dont know what I have to enter there, I only know that the device is a SM-T830/gts4lwifi.
CSC is region code
Rooting, ODIN, Firmware, CSC Information And Myths Debunked / Noob's Guide To Samsung Devices
Since a lot of people will have their Galaxy S22 Ultra soon and I myself am thinking about either getting an S21 Ultra or S22 Ultra, I wanted to summarise a lot of information I found out during researching as Samsung devices are quite different...
forum.xda-developers.com
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Well, if RMM/KG state is prenormal you would see message "Only official released binaries are allowed to be flashed"
Anyway, try to flash official ROM and wait for KG state while device is connected to internet.
you can download according to your region from https://samfw.com/firmware/SM-T830
T830Guy said:
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Click to expand...
Click to collapse
Setting the 7 days back works
T830Guy said:
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Click to expand...
Click to collapse
try this: https://forum.xda-developers.com/t/...-twrp-and-magisk.4059227/page-2#post-88134465
Steps I've done:
1. Unlocked bootloader, OEM unlock is enabled
2. Downloaded and installed Samsung Drivers
3. Download TWRP / SHARP Recovery
4. Downloaded Odin
5. Got my phone into Download mode (KG State - Checking, FRP - off, OEM LOCK - off)
6. Ran Odin, device detected in Odin
7. Put the tar file into the AP
8. Clicked "Start" in Odin, passed successfully
9. Holding Volume Down, Volume Up & Power Button
10. Released Volume Down on black screen
11. Released Power Button on Samsung logo
12. Still holding Volume Up button
That's how far I was able to come. The device just bootloops itself and I can't get it to open TWRP / SHARP. Got it into download mode again and flashed it with the stock firmware, but want to install custom ROM through the TWRP / SHARP. First time trying to flash custom rom, am I doing something wrong? Any help appreciated.
Reference:
[RECOVERY][Official] TWRP 3.7.0_11 for Galaxy A50
*** Disclaimer I am not responsible for any damage you made to your device You have been warned Features: Android 11, 12 and 13 support Supported Devices: A505F A505FN A505G A505GN A505GT Downloads...
forum.xda-developers.com
GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI.
Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI. - GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP r...
github.com
You need to connect type c cable to boot into twrp.
Connect your phone to computer or laptop or tv with cable , then use key combination to boot to twrp.
Press power key and volume up at the same time when your phone connected to pc with cable.
Sharath Mane said:
You need to connect type c cable to boot into twrp.
Connect your phone to computer or laptop or tv with cable , then use key combination to boot to twrp.
Press power key and volume up at the same time when your phone connected to pc with cable.
Click to expand...
Click to collapse
Type C cable has been connected from pc to the phone since booting into download mode, as it is required. Even after exiting the download mode and trying to boot to TWRP the phone is still connected onto it, but it just boot loops.
but it just boot loops
Click to expand...
Click to collapse
You see some red text... something like only official crap allowed...
Then maybe try other Firmware.... because """funny""" Bootloader...
IMHO similar problem like in this thread...
can't flash with odin even though bootloader being unlocked
i've got an a50 that i want to install TWRP on so i won't have to use the abomination that download mode is. i've unlocked bootloader, yet when i try to flash the TWRP .tar in odin it fails and the phone gives the following error code: "Only...
forum.xda-developers.com
Only idea....
I can not see your device nor I have Crystal Ball.
Best Regards
EQuak said:
Steps I've done:
1. Unlocked bootloader, OEM unlock is enabled
2. Downloaded and installed Samsung Drivers
3. Download TWRP / SHARP Recovery
4. Downloaded Odin
5. Got my phone into Download mode (KG State - Checking, FRP - off, OEM LOCK - off)
6. Ran Odin, device detected in Odin
7. Put the tar file into the AP
8. Clicked "Start" in Odin, passed successfully
9. Holding Volume Down, Volume Up & Power Button
10. Released Volume Down on black screen
11. Released Power Button on Samsung logo
12. Still holding Volume Up button
That's how far I was able to come. The device just bootloops itself and I can't get it to open TWRP / SHARP. Got it into download mode again and flashed it with the stock firmware, but want to install custom ROM through the TWRP / SHARP. First time trying to flash custom rom, am I doing something wrong? Any help appreciated.
Reference:
[RECOVERY][Official] TWRP 3.7.0_11 for Galaxy A50
*** Disclaimer I am not responsible for any damage you made to your device You have been warned Features: Android 11, 12 and 13 support Supported Devices: A505F A505FN A505G A505GN A505GT Downloads...
forum.xda-developers.com
GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI.
Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI. - GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP r...
github.com
Click to expand...
Click to collapse
I had the same issue. If u are on the newest binary flash that stock https://samfw.com/firmware/SM-A505FN/DCO/A505FNXXS9CUF1 after set it up w wifi u dont need to log in to a google account and flash ur recovery and it will work
EQuak said:
Steps I've done:
1. Unlocked bootloader, OEM unlock is enabled
2. Downloaded and installed Samsung Drivers
3. Download TWRP / SHARP Recovery
4. Downloaded Odin
5. Got my phone into Download mode (KG State - Checking, FRP - off, OEM LOCK - off)
6. Ran Odin, device detected in Odin
7. Put the tar file into the AP
8. Clicked "Start" in Odin, passed successfully
9. Holding Volume Down, Volume Up & Power Button
10. Released Volume Down on black screen
11. Released Power Button on Samsung logo
12. Still holding Volume Up button
That's how far I was able to come. The device just bootloops itself and I can't get it to open TWRP / SHARP. Got it into download mode again and flashed it with the stock firmware, but want to install custom ROM through the TWRP / SHARP. First time trying to flash custom rom, am I doing something wrong? Any help appreciated.
Reference:
[RECOVERY][Official] TWRP 3.7.0_11 for Galaxy A50
*** Disclaimer I am not responsible for any damage you made to your device You have been warned Features: Android 11, 12 and 13 support Supported Devices: A505F A505FN A505G A505GN A505GT Downloads...
forum.xda-developers.com
GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI.
Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI. - GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP r...
github.com
Click to expand...
Click to collapse
I got exactly the same problem....no I am facing a bootlooping device.....jay! ... :-(
@EQuak did you read the Stickies before posting in Development?
Your post does not qualify for Development and has been moved to Questions and Answers.
You are REQUIRED to read and follow the Forum Rules!
15. Keep threads / posts on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum / thread in which you are posting.
General Forums - For news and announcements relating to your device.
Q&A Help & Troubleshooting Forums - For all question / request threads and posts. If there is no Q&A Help & Troubleshooting forum, use the General Forum of the relevant device
Accessories Forum - For posts related to accessories relevant to the device
Development Forums (ones with the word development in the title) - For Developers to post release threads e.g. ROMs and Kernels including modifications to kernels, bootloaders, ROMs, etc., as well as R&D development discussion threads designed with an end goal
Themes and Apps Forums - For the posting of Themes and / or Apps as well as announcements & discussions including modifications made to Themes and Apps.
Click to expand...
Click to collapse
TabletopDock9 said:
I had the same issue. If u are on the newest binary flash that stock https://samfw.com/firmware/SM-A505FN/DCO/A505FNXXS9CUF1 after set it up w wifi u dont need to log in to a google account and flash ur recovery and it will work
Click to expand...
Click to collapse
Did it, still boot loops...
EQuak said:
Did it, still boot loops...
Click to expand...
Click to collapse
Hmmm. What twrp version u use?
TabletopDock9 said:
Hmmm. What twrp version u use?
Click to expand...
Click to collapse
Originally I've used the version 3.7.0_11 (reference: https://forum.xda-developers.com/t/...-7-0_11-for-galaxy-a50.4581017/#post-88552901) but have tried also one more version from 1 youtube vid (saddly don't know the version of twrp), but they both failed. I've also tried to use a different recovery called "SHRP" but it failed again.
EQuak said:
Originally I've used the version 3.7.0_11 (reference: https://forum.xda-developers.com/t/...-7-0_11-for-galaxy-a50.4581017/#post-88552901) but have tried also one more version from 1 youtube vid (saddly don't know the version of twrp), but they both failed. I've also tried to use a different recovery called "SHRP" but it failed again.
Click to expand...
Click to collapse
I use this https://t.me/androidhowto2020/126453
TabletopDock9 said:
I use this https://t.me/androidhowto2020/126453
Click to expand...
Click to collapse
Just tried it and it boot loops. I'm gonna try and record a step-by-step video of my process to see if you could spot any mistakes I make during the process, because I'm really at my wits' end.
EQuak said:
Just tried it and it boot loops. I'm gonna try and record a step-by-step video of my process to see if you could spot any mistakes I make during the process, because I'm really at my wits' end.
Click to expand...
Click to collapse
Did you solved this yet? Im facing same problem, Ive tried about 4 different TWRP and SHRP also but non of them worked. Also first time doing this. Only option I could now do is to flash back some random stock ROM to atleast have functioning phone. But I cannot set up Gpay anymore because it says the device is rooted - And in reality it is not, even system says state of phone as Official. I dont know what to do.
DracieVajko said:
Did you solved this yet? Im facing same problem, Ive tried about 4 different TWRP and SHRP also but non of them worked. Also first time doing this. Only option I could now do is to flash back some random stock ROM to atleast have functioning phone. But I cannot set up Gpay anymore because it says the device is rooted - And in reality it is not, even system says state of phone as Official. I dont know what to do.
Click to expand...
Click to collapse
No, I haven't found any solution so far to it since the problem occurred. Guessing It may be caused by a CSC code since we are both form Slovakia? Really don't know...
EQuak said:
No, I haven't found any solution so far to it since the problem occurred. Guessing It may be caused by a CSC code since we are both form Slovakia? Really don't know...
Click to expand...
Click to collapse
I was thinking about it too. Like, my phone is from Orange, so probably there is something which is blocking the whole thing. Only way I was able to install system was through Odin. But for Odin Ive found only stock roms, custom roms work only with TWRP...
EQuak said:
No, I haven't found any solution so far to it since the problem occurred. Guessing It may be caused by a CSC code since we are both form Slovakia? Really don't know...
Click to expand...
Click to collapse
Maybe I found something now. I had one old Galaxy J3 2016, Also from Orange operator as my A50. And it did worked perfectly on the first try and only thing I've did was enabling USB debugging in developer options, which I've forgot on my A50 before. So maybe this could be the problem at least in my scenario? But yet I didn't got time to try it on A50 again.
DracieVajko said:
Maybe I found something now. I had one old Galaxy J3 2016, Also from Orange operator as my A50. And it did worked perfectly on the first try and only thing I've did was enabling USB debugging in developer options, which I've forgot on my A50 before. So maybe this could be the problem at least in my scenario? But yet I didn't got time to try it on A50 again.
Click to expand...
Click to collapse
You're a lifesaver, just tried it with the A50 and I successfully booted into TWRP. Definitely works!
Edit: Another thing that may fixed the issue is just not updating the software. I just went through the process of setting it up but right after I booted into the android, I just turned it off and got it into download mode and flashed it with TWRP.
EQuak said:
You're a lifesaver, just tried it with the A50 and I successfully booted into TWRP. Definitely works!
Edit: Another thing that may fixed the issue is just not updating the software. I just went through the process of setting it up but right after I booted into the android, I just turned it off and got it into download mode and flashed it with TWRP.
Click to expand...
Click to collapse
Im happy it worked. But sadly for my A50 it still bootloops and nothing, I have no idea why so Im stuck with stock OS on which Google Pay and few Samsung apps wont work cause "phone is rooted" (no it isnt, its on official rom) and since I cant flash TWRP I cant do anything Ive also tried your method to quickly set up fresh android (without wifi) and right after I went to reboot and flashing :/