I've had a Galaxy SM-T510 for about 18 months. I installed a custom ROM and it worked fine. When it booted up I received a message "Bootloader is unlocked and security cannot be guaranteed, press power button" and when you pressed the power button it booted up fine. Recently, I installed TWRP and when I rebooted it goes to the some "Bootloader is unlocked, etc" error message, but when you press the power key it restarts and loops to the same point. Holding the power key, with volume up, volume down or both makes no difference. I installed Fonepaw which appears to only work in Download mode which I can't access. If I run Odin or Kies it doesn't recognise that there is a phone attached. Any suggestions?
I've solved the problem. Holding down both volume up & volume down at the same time, and plugging it in puts the device into download mode.
Actually, I haven't solved the problem. I can now install an OS thru either Odin or TWRP, but all the OS I have tried go into a bootloop and the device never finishes booting up.
I'm disappointed no one has any suggestions. I decided to replace TWRP with Orange Fox and installed Lineage, the device of course went into a bootloop. I then booted it into recovery and it went into TWRP. So I installed Orange Fox and wiped everything, I reebooted and this time it went into Orange Fox. I reinstalled Lineage -> another bootloop, tried to get back into recovery and it was TWRP.
BillSchutt said:
I'm disappointed no one has any suggestions. I decided to replace TWRP with Orange Fox and installed Lineage, the device of course went into a bootloop. I then booted it into recovery and it went into TWRP. So I installed Orange Fox and wiped everything, I reebooted and this time it went into Orange Fox. I reinstalled Lineage -> another bootloop, tried to get back into recovery and it was TWRP.
Click to expand...
Click to collapse
You aren't getting help because you are posting in the wrong place. And, if you are coming from an old custom ROM, you have to first flash the right stock ROM. I no longer have a 510 so I'm not sure which stock ROM you need but if you check the first post for the custom ROM you want in the ROMs, kernels and recovery thread, it should tell which one it is based on.
Related
Greetings.
I am sure there is an answer on XDA but an hour of Googling has got me stumped. Please point me to the right answer.
Starting point
Rooted N900T, stock rom, stock recovery.
What I did
Installed ROM Manager
Told ROM Manager to install the latest CWM for my phone. Completed with no errors.
Tried to boot into recovery with the standard "hold power, vol down, and home" but I could never get into recovery. It would look like it would start to boot into recovery then it would reset and boot into the regular ROM.
Then I told ROM Manager to reboot me into recovery.
Then it went badly... I am stuck in a boot loop that continuously shows going into recovery, then samsung logo, then repeat.
I have pulled the battery, tried to go into download mode, tried connecting USB, tried Odin.
What I want is a working phone. I would like to back up the stock rom and go to CM12 nightlies but for now I will just take a working phone.
Please help,
David
think I found the answer at http://forum.xda-developers.com/showthread.php?t=2666432
At least I got out of the loop, not fixed but progress.
That worked, the only other piece of info you might need if someone else has this problem is that there is no PDA button on the latest version Odin, it is called AP
Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.
If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.
Hey guys and gals, I decided to take my new PH-1 and root it after getting the latest OTA (this is an unlocked Sprint variant). I flashed the twrp for my build and there was an error, tried it again and the same error so I rebooted back into fastboot and it flashed but I didn't reboot into recovery. Flashed it again and booted into recovery but it was just a black screen as if the phone wasn't turned on. The closest I've gotten to recovery was the android laying down and it said "no command" but I forced a reboot at that point (I think I could have pressed up on the volume and pressed the power button to get to it from there but I haven't been able to get back to it).
I ended up flashing a modded boot image for root with Magisk 14.3 and that worked but I can't reboot my phone, it just goes to the blank screen like it isn't on and I can start it up again by holding the power button down for 15 sec. and it seems to function fine but I can't flash the OTA file to go back to complete stock or to go to the Oreo beta.
If anyone could give me some insight into this problem or a way of fixing it I would grateful, thank you.
I recently installed twrp instructions and installed a custom ROM. Even since then the device boots normally into twrp recovery only. to boot into the rom, I have to boot through recovery, press power + volume dn and then it boots to the regular ROM. Should I start over on this or is there a way to change that preference so the device boots normally into the OS instead of twrp.
Sorry if this has been answered somewhere else already. I looked.
gnaneswarv said:
I recently installed twrp instructions and installed a custom ROM. Even since then the device boots normally into twrp recovery only. to boot into the rom, I have to boot through recovery, press power + volume dn and then it boots to the regular ROM. Should I start over on this or is there a way to change that preference so the device boots normally into the OS instead of twrp.
Sorry if this has been answered somewhere else already. I looked.
Click to expand...
Click to collapse
I am facing same issue. I don't have twrp or custom rom but stock recovery and stock rom. Everytime I boot or restart my phone it goes to recovery mode!! I couldn't find solution yet and its very annoying.
Try following the steps in this thread: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325 Of course, ensure you have backups before erasing anything.
Hi Everyone,
I originally flashed LineageOS and it wirked beautifully. Then I thought I wanted root.... After trying some things that didn't work I flashed my tablet back to stock to get it working again and then attempted to reinstall LineageOS cleanly. But now, after flashing the recovery with Heimdall, when I power off with Vol-down and Power and immediately switch back to Vol-up and power, the regular warning screen shows up with the standard message: "This tablet's bootloader is unlocked and it's software integrity can't be verified..." Then the same screen with a yellow warning triangle
added and below that another warning triangle and in Red "This tablet is not running Samsung's official software" and you will have problems...
After this screen appears the tablet freezes and becomes unresponsive to all but the Power and vol-down shutdown. It then reboots and freezes again.
I can get back to Download mode and reflash the stock with Odin but loading the lineage recovery seems impossible.
I can get to the stock recovery with adb reboot recovery
Is there some way to bypass what looks like a security measure? Does someone know more about this?
In the stock recovery is has the option to enter fastboot. Is this a real fastboot, as in I could load a recovery straight from my computer?
Not sure how to get back to LineageOS, or what my next step should be.
Thanks in advance,
Murphy
Update: I got it working again and reinstalled LineageOS
What worked was using Asomeslayerg's Guide to Unlocking and Rooting the S6 Lite with updated instructions in the comments from gbeyts667. Thanks to those fine souls!
It seems some combination of using an older version of the stock image (I used the one from the guide from around last year) and patching with magisk re-enabled my ability to enter recovery mode after flashing the lineage recovery.
I hope this helps someone else.
Has anyone used magisk to root LineageOS on the S6 lite? Does it work? Can you just use the lineage recovery for that?
Would love to know! Thanks in advance.