I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Nexicovx said:
I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Click to expand...
Click to collapse
Your recovery is not corrupt. That is the stock recovery boot that you are seeing.
Anyways, how come you can't access ADB or fastboot? Because right now, that would be the easiest and fastest way to install TWRP back.
Nexicovx said:
I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Click to expand...
Click to collapse
I am guessing the android man image you can see in recovery is laying on its back with its front flap open? Also says No Command?
If so, when on that page, hold the power button in and while holding it click up volume.
You'll see the stock recovery then.
Good luck
dadvs1 said:
I am guessing the android man image you can see in recovery is laying on its back with its front flap open? Also says No Command?
If so, when on that page, hold the power button in and while holding it click up volume.
You'll see the stock recovery then.
Good luck
Click to expand...
Click to collapse
When you get that Android lying down, press the Power Button followed by Volume Up. That will put you into recovery.
Could you not live boot the recovery? fastboot boot twrp.img.
Nexicovx said:
I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Click to expand...
Click to collapse
Maybe im not fully understanding you, but it sounds like you can boot recovery and you can boot Android to the welcome screen. If I was you I would try
1.) Take out your sim and skip the full setup process to get straight to your home screen. Then turn on debugging in dev options > adb reboot bootloader
2.) Boot to android welcome screen, turn off phone turn back on holding volume down and power to get to the bootloader.
Fastboot wont work while you're in recovery. The main idea is to get to the bootloader so you can fastboot flash stock ROM and start from scratch
tonystarks260 said:
Maybe im not fully understanding you, but it sounds like you can boot recovery and you can boot Android to the welcome screen. If I was you I would try
1.) Take out your sim and skip the full setup process to get straight to your home screen. Then turn on debugging in dev options > adb reboot bootloader
2.) Boot to android welcome screen, turn off phone turn back on holding volume down and power to get to the bootloader.
Fastboot wont work while you're in recovery. The main idea is to get to the bootloader so you can fastboot flash stock ROM and start from scratch
Click to expand...
Click to collapse
Hello, we appreciate your help
But from what I read and understand, the user, Nexicovx thinks that the Android bot with the exclamation mark, is a sign of corrupt recovery. While it is only the regular behaviour of the stock recovery.
When you boot into stock recovery, he would not be taken to it straight away. It will first show the screen, where the Android bot with some sort of warning sign appears. At that point, he would just have to press the Volume up key, and tap the power button once. This will trigger the stock recovery.
Now, to what you can do @Nexicovx. You need to access a PC and the USB cable. Boot your 6P into bootloader mode by powering it off first, and then press and hold the Volume Down and Power keys altogether until you see the bootloader mode. From there, you can flash the TWRP recovery. Download the latest image from here: https://dl.twrp.me/angler/
And now use the following command to flash it:
Code:
fastboot flash recovery twrp-3.0.2-0-angler.img
Once that is done, you can reboot into TWRP and flash your desired ROM.
Thanks everyone. I misunderstood what the stock recovery looked like and surprisingly I didn't see much information related to this. I have since gotten my phone up and running thanks to your replies.
I forgot exactly what the problem was but I did get it sorted. Thank you.
Nexicovx said:
Thanks everyone. I misunderstood what the stock recovery looked like and surprisingly I didn't see much information related to this. I have since gotten my phone up and running thanks to your replies.
I forgot exactly what the problem was but I did get it sorted. Thank you.
Click to expand...
Click to collapse
Good to know that. :highfive:
I do have one final issue that I haven't resolved yet but I'm going to do another test next week. I live in China and with the latest update I can't install GApps (when the phone reboots after flashing my phone can't connect to the internet even though I'm through a VPN Wifi connection which works perfectly if I don't install GApps).
I'm going to try the last known security update I was using on Pure Nexus from 2/18 and see if this works. I don't remember which Vendor image I used then but I'm not sure if it is too important. I'll post here if it fixes my troubles. I'm having wifi troubles on the latest build and this is what is making me think I'm having my GApps trouble.
Nexicovx said:
I do have one final issue that I haven't resolved yet but I'm going to do another test next week. I live in China and with the latest update I can't install GApps (when the phone reboots after flashing my phone can't connect to the internet even though I'm through a VPN Wifi connection which works perfectly if I don't install GApps).
I'm going to try the last known security update I was using on Pure Nexus from 2/18 and see if this works. I don't remember which Vendor image I used then but I'm not sure if it is too important. I'll post here if it fixes my troubles. I'm having wifi troubles on the latest build and this is what is making me think I'm having my GApps trouble.
Click to expand...
Click to collapse
It could be a vendor issue.
Good to know!
Related
Hi, basically i recently flashed the miui rom via rom manager on my nexus 7 and once it had flashed the rom it went to restart and it won't go past the mi boot screen. I also can't go into recovery via fastboot mode as it just goes the google screen.
What Should I do?
Djamel.K said:
Hi, basically i recently flashed the miui rom via rom manager on my nexus 7 and once it had flashed the rom it went to restart and it won't go past the mi boot screen. I also can't go into recovery via fastboot mode as it just goes the google screen.
What Should I do?
Click to expand...
Click to collapse
I think you might still be able to re-install the stock ROM.
Go to this thread and scroll down to "Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader". You should probably read the whole post in case I missed something.
Good luck
I don't know if this will help but from what I've read you can't get into recovery through fastboot unless you're plugged into a pc. What you can do is plug your tablet into the pc and then hold the volume up/down buttons as well as the power button. Then just select recovery and you should be able to get into it.
I'm not an expert on this but it has happened to me where I would get stuck at the google screen so I did a lot of reading about it. From what I understand, this is an issue with the bootloader. It was designed that way and this problem will continue as until google decides to fix it.
I hope this helps
bacon_n_icecream said:
I don't know if this will help but from what I've read you can't get into recovery through fastboot unless you're plugged into a pc. What you can do is plug your tablet into the pc and then hold the volume up/down buttons as well as the power button. Then just select recovery and you should be able to get into it.
I'm not an expert on this but it has happened to me where I would get stuck at the google screen so I did a lot of reading about it. From what I understand, this is an issue with the bootloader. It was designed that way and this problem will continue as until google decides to fix it.
I hope this helps
Click to expand...
Click to collapse
It won't let me select recovery and when it did earlier it didn't work
Hello all,
Any help with this would be seriously appreciated. I rooted my Nexus 10 a while back, maybe two years ago. I'm not very proficient with this stuff. Anyhow I decided to do the OTA upgrade to 5.0...I was concerned something would go wrong unless I went to stock first, but I read that the only thing that would happen is root would be removed.
Anyhow, the tablet appears stuck while booting. I see the Google screen first with the unlocked indicator on the bottom. A few seconds later is the Android logo on its back, a red triangle over it with an exclamation point and "no command" written below". It stays that way for a minute or so, tries to reboot and goes back to the no command screen. I can't even power off, when I try to do so it just powers back on by itself and ends up at the no command screen again.
I tried booting into recovery (power, volume up, volume down). My options from here are either Start, Restart Bootloader, Recovery Mode or Power Off. Every option I choose leads to the No Command Screen (except power off, which powers off). No idea what to do from here.
Any help at all would be appreciated. As you can probably tell I don't have much experience with this and just wanted to go back to unrooted stock. If you have advice, please be clear. I can follow directions well enough, just don't have much experience here. Thanks in advance.
Same here, bootloop.
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Guys, if your device is connected in fastboot (try "fastboot devices") then you can flash roms or recovery (and then flash rom) from there. There are multiple threads with the same problems out there which were fixed. E.g: http://forum.xda-developers.com/nexus-10/help/bricked-t2948546
In my example, I flashed TWRP recovery from fastboot, then installed custom ROM from recovery (official ROM failed to install for some reason). Try this, it might help.
danweis said:
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Click to expand...
Click to collapse
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Aresmar said:
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Click to expand...
Click to collapse
I also had the same problem... I followed these instructions and now my Nexus 10 can boot normally (it took a long time to boot).
Only problem is all my data was deleted.... stup*d f*cking sh*t!!!!!!!
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.
You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.
If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
kruc Ire said:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
Click to expand...
Click to collapse
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
kruc Ire said:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
Click to expand...
Click to collapse
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
duffycop said:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
Click to expand...
Click to collapse
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
kruc Ire said:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
Click to expand...
Click to collapse
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..
I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.
I'm trying to contact with some developers and see if anyone can help me build a device tree.
]
Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.
However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1
pedrovay2003 said:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Click to expand...
Click to collapse
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?
lg leon h345 lollipop 5.1.1
This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.
I had to reboot my device due to problems with my speaker. Now i'm not able to boot anymore.
I'm only able to get into ODIN Mode, and flashing new FW or TWRP does nothing. It'll flash correctly, but as soon as it sends the reboot command the device powers off and does not boot, and no, it does not reach the "Galaxy s8, powered by android screen".
It does not want to power on, and only responds to the odin button combo, can't boot into recovery either since nothing works.
I was running the latest version of Renovate Ice if that matters.
I've searched trough some other threads, but it seems like i'm the only one that's having this problem.
Any help or thoughts would be greatly appreciated!
Edit 1: I've tried flashing both AQK7 and AQG5. Both flash fine, but as soon as odin sends the reboot command to my phone, it turns off and does not turn on.
Auto Reboot is ticked. Same goes for any version of TWRP, it will flash, but when it has to reboot the device turns off and does not turn on. There's nothing on the screen, its completely black and the only thing that does work is Download Mode. I've also tried ereasing nand, and repartitioning storage. Both seem to have 0 effect. As stated in one of my replies, i was running the latest build of renovate-ice with magisk, no other mods, or themes installed.
Im a bit confused - you can only boot into download mode (not into twrp?) and the phone is in bootloop? Have you flashed anything (mod?) before or activated a substratum theme which could cause this?
The only thing I can think of is a) you delete in twrp file manager the corrupted file, if there is something like this or b) a twrp restore from a backup. Boot into download mode and then do not press vol up to go into odin mode but press vol down to reboot - then immediately press the combo for twrp and you will get to the recovery. This helped my s8 many times when I was in a bootloop and couldnt boot up twrp
FloM94 said:
Im a bit confused - you can only boot into download mode (not into twrp?) and the phone is in bootloop? Have you flashed anything (mod?) before or activated a substratum theme which could cause this?
The only thing I can think of is a) you delete in twrp file manager the corrupted file, if there is something like this or b) a twrp restore from a backup. Boot into download mode and then do not press vol up to go into odin mode but press vol down to reboot - then immediately press the combo for twrp and you will get to the recovery. This helped my s8 many times when I was in a bootloop and couldnt boot up twrp
Click to expand...
Click to collapse
Thanks for the reply! Other than using the Renovate-Ice rom, and running magisk the thing was pretty much stock. wasn't messing around in twrp either. Its not stuck in a bootloop either, it just refuses to do anything other than go in and out of DL mode. The phone does not respond to any button imputs other than DL mode. As stated in the OP it does not boot at all, just a black screen. i've already tried to reflash a stock FW and TWRP, but that does not seem to work...
try the method I did - this is the last thing I could think of, before reflash the whole phone with odin
More info about your speaker problem
popmpopm said:
More info about your speaker problem
Click to expand...
Click to collapse
There isn't much to say about the problem ,it just stopped working, hence why i rebooted the phone, and ran in to the problem i'm having right now.
FloM94 said:
try the method I did - this is the last thing I could think of, before reflash the whole phone with odin
Click to expand...
Click to collapse
Doesn't work sadly, but thanks for the help anyways!
but you havent installed Viper4Arise or anything like that?
Because of this my speaker also stopped working a few weeks ago
if you can get into download mode then get into download mode and leave phone, then download samsung smart switch for your pc (older version like 4.1.17022_20 from here http://www.filehorse.com/download-samsung-smart-switch/29268/ that allows phone based recovery), once installed open it, then click on more at top right, (do not update the software if you get a prompt) select emergency device recovery...., then click on right tab (device initialisation) and fill in your phone details etc., connect your phone (in download mode) and follow the process, maybe it works, you'll need to root and install TWRP again but thats no big issue.
Jostian said:
if you can get into download mode then get into download mode and leave phone, then download samsung smart switch for your pc (older version like 4.1.17022_20 from here http://www.filehorse.com/download-samsung-smart-switch/29268/ that allows phone based recovery), once installed open it, then click on more at top right, (do not update the software if you get a prompt) select emergency device recovery...., then click on right tab (device initialisation) and fill in your phone details etc., connect your phone (in download mode) and follow the process, maybe it works, you'll need to root and install TWRP again but thats no big issue.
Click to expand...
Click to collapse
I've tried this just now, and it still gives me the same result, it goes trough the process, but as soon as it has to reboot it doesn't boot anymore.
Thanks for the suggestion though!
FloM94 said:
but you havent installed Viper4Arise or anything like that?
Because of this my speaker also stopped working a few weeks ago
Click to expand...
Click to collapse
i think phone is damaged by water or dropped s8 so fragile phone ! its happen to me with s5 the phone dead after speaker problem !!
popmpopm said:
i think phone is damaged by water or dropped s8 so fragile phone ! its happen to me with s5 the phone dead after speaker problem !!
Click to expand...
Click to collapse
I've had a case on the phone since day one, and I've checked for water damage, but there is non. The tab that is supposed to indicate it is untouched. But thanks for your input! I appreciate it
I have the same problem. Its look like is bootloader issue. try flash this soft :
G950FOWA1AQCC_Recovery
But if you are on newest rom it wont work.
Hello, you can solve this problem?
Not sure I am posting in the right spot, but pretty sure the people that can answer are in this section.
After putting it off for months, I upgraded my 6T T Mobile converted to international to OOS 10.3.3 with the ElemetalX kernel, and xxxNoLimits 10.2. Did this several days ago, no problems. Great battery, smooth performance. Even getting 2 days with my VPN on and mock location set to "always".
I went into app ops and noticed almost every app now has "access location from media" and started going through and denying that permission for almost, if not all, the apps. I remember a couple of system apps I did that to. Google play framework being one of them, and, I think, google play services. There may have been 1 or 2 more system apps I did this with also.
I do not have a google account on my phone. I don't want to make it any easier for my pocket tracking device to track me than I have to.
I added an open source mock location app a day or so ago, not problems.
About 5 or so minutes after finishing up in app opps, I went to get the kiddo some food and looked down and noticed my phone rebooting. Now, it is in an endless boot loop.
I can hold power + up volume and get it to power down, but can't get back into TWRP recovery. Figured a quick reflash puts me back to zero and I can start over.....more carefully....but the phone is not cooperating.
I should be able to use adb and flash TWRP that way and use adb to reboot to recovery ( going to have to brush up on the how to before I start though.).
Any thoughts as to WHAT I have done and WHY I am now stuck on endless boot( w XXX animation )??
Is there an easy fix I am overlooking?
Thanks in advance,
JC
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool
Can you get into fastboot? Then you might be able to boot TWRP again temporarily?
Thanks, that gets my into TWRP, unfortunately, my dumb ass deleted the last OTA update after I flashed it. Should be able to side load it onto the phone, then flash it via TWRP.
Well, things just took a turn for the worse. I forgot to flash twrp after sideloading the os. Now it is keeps booting into Oneplus recovery. Still shows bootloader is unlocked though. I have done everything except a total wipe. Maybe I can still get TWRP back........
PattayaGlock said:
Well, things just took a turn for the worse. I forgot to flash twrp after sideloading the os. Now it is keeps booting into Oneplus recovery. Still shows bootloader is unlocked though. I have done everything except a total wipe. Maybe I can still get TWRP back........
Click to expand...
Click to collapse
Flash twrp recovery via adb commands, you'll find tutorials on several XDA forums or YouTube