Factory Reset from Root, stuck in Bootloop [SOLVED] - Verizon Samsung Galaxy S7 Questions & Answers

I'm able to get into Stock Recovery, but I'm unsure what to do next as my PC won't recognize it at all since OEM Unlock and Debugging are not able to be turned on.
THIS HAS BEEN SOLVED!

What was the solution?

what was the solution
wat was the solution to this being solved? I have to second that.

Related

[Q] I9505 stuck on Boot screen after failed update

Hi guys
I`ve got a major Problem Here. Please help!!
Me and a friend wanted to update my rooted Galaxy s4 from The unofficial to the official Kitkat Firmware. But The update failed. We tried again but still no succes. I didnt have enough space on my SD card. So I did a factory reset, installed twrp and let Odin install a small custom Rom. Odin succesfully installed it but Then I got stuck in The Boot screen. Probably I didnt turn on USB debugging
After days of surching The web I found out that I could change The rights for USB debugging over ADB tool. But i get stuck on The <su> command after entering <ADB shell>. The command cant be executed or something like that.
I then noticed that the root had gone with the factory reset. I installed that and now my PC (adb) wont recognize the phone anymore.
What should I do? Im still quite a noob so please dont critizise me if I missed something obvious.
Should I use ADB or is there a better sollution?
Please please help.
Hope that theres a sollution.
Keep posting
illias9 said:
Hi guys
I`ve got a major Problem Here. Please help!!
Me and a friend wanted to update my rooted Galaxy s4 from The unofficial to the official Kitkat Firmware. But The update failed. We tried again but still no succes. I didnt have enough space on my SD card. So I did a factory reset, installed twrp and let Odin install a small custom Rom. Odin succesfully installed it but Then I got stuck in The Boot screen. Probably I didnt turn on USB debugging
After days of surching The web I found out that I could change The rights for USB debugging over ADB tool. But i get stuck on The <su> command after entering <ADB shell>. The command cant be executed or something like that.
I then noticed that the root had gone with the factory reset. I installed that and now my PC (adb) wont recognize the phone anymore.
What should I do? Im still quite a noob so please dont critizise me if I missed something obvious.
Should I use ADB or is there a better sollution?
Please please help.
Hope that theres a sollution.
Keep posting
Click to expand...
Click to collapse
Do you have a custom recovery? Try to install it. I recommend CWM 6.0.4.6.
Later that, flash any flashable rom(remeber: correct model). Later flashing, reboot.

[Q]Phone can't get recognized by pc, download mode available

Hi,
yesterday I got d802 phone to fix it. First the phone was stuck at LG screen with certification error which I fixed. Phone was recognized by PC and i installed twrp on phone. I tried everything (i guess) and now phone is stuck at LG screen and it doesnt move. Now i cannot go back to twrp recovery but i can get to download mode but phone isn't recognized by pc so i cannot flash kdz file to phone. I'm really stuck at this point. Is this real hard brick or is there any way to fix it? Any ideas what should i do or something i can try?
I tried to plug phone in other computers and it's the same thing. My laptop recognized that something is plugged in once but it didn't know what was it so by now. Somehow from time to time phone doesn't go to download mode but it goes in hardware key control mode.
Hope someone can help...
So far i manged to get to recovery mode but adb sideload isn't working. I tried to wipe everything and that didn't help. As we speak factory reset is in progress but I think it's stuck on formatting cache. I hope I'll be able to get the phone recognized in download mode. Any suggestions are appreciated
I have made some progress. ADB is working now and i pushed cyanogenmod and on installation it says that it cannot mount data and cache. I think that main problem is that phone isn't rooted and now I'm trying to root phone via adb. If someone knows anyway to do this that would be great

Op5 not detected by pc- stuck at powered by android.

Hi all,
need help for my op5, been reading from the net but cant find solution.
currently it stuck at powered by android. i have tried using unbrick step, but not working because the phone will turn on when plug in the cable to connect pc
https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
It stuck after factory reset through twrp.
-already unlock bootloader.
- cannot go in recovery.
- cannot bootloader.
- adb not detect device.
thanks,any suggestion n help anyone?
sidqara said:
Hi all,
need help for my op5, been reading from the net but cant find solution.
currently it stuck at powered by android. i have tried using unbrick step, but not working because the phone will turn on when plug in the cable to connect pc
https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
It stuck after factory reset through twrp.
-already unlock bootloader.
- cannot go in recovery.
- cannot bootloader.
- adb not detect device.
thanks,any suggestion n help anyone?
Click to expand...
Click to collapse
You followed step 4 and 5 of the unbrick guide already?
Why you are in this situation? What's happening before and what is your rom, bootloader status?
You followed step 4 and 5 of the unbrick guide already?
4. yes done, im using w10 64bit
5. when connect phone to pc, it boot up to powered by android.
Why you are in this situation? What's happening before and what is your rom, bootloader status?
unlock bootloader rooted with custom rom, then change to oos.
got few error-android not working, so im gonna do clean flash again. go to twrp, factory reset. then its happen.
:silly:
sidqara said:
You followed step 4 and 5 of the unbrick guide already?
4. yes done, im using w10 64bit
5. when connect phone to pc, it boot up to powered by android.
Why you are in this situation? What's happening before and what is your rom, bootloader status?
unlock bootloader rooted with custom rom, then change to oos.
got few error-android not working, so im gonna do clean flash again. go to twrp, factory reset. then its happen.
:silly:
Click to expand...
Click to collapse
And you really pressed the volume up button and then connect it to the PC?
When coming from a custom rom it's highly recommended to wipe system, data, cache and format internal storage too.
strongst said:
And you really pressed the volume up button and then connect it to the PC?
When coming from a custom rom it's highly recommended to wipe system, data, cache and format internal storage too.
Click to expand...
Click to collapse
yup, i'm positive im pressing the volume button, been tried with 2 different laptop, same.
and previously i have succeed unbrick my friend op3, and no issue at all. as i can remember the phone will not turn on rite? when connect to PC.
Update.
succeed, problem solved.
disassemble battery, phone until it wont turn on when connect to pc, lucky it work.
then unbrick using unbrick tools. next plan to change screen n fingerprint scanner.
im happy , bought op5 for a cheap price.

S7 Edge Hero2lte Exynos SM-G35F bricked device

Hi Guys,
Today I think I bricked my phone and I would appreciate any help.
I will describe the whole situation.
So around 2019 May, I rooted my device and decided to flash a stock based,debloated custom rom. Everything work just fined including downloading mode and recovery menu. Today, I decided to try out [S7/S7 Edge][OneUI Pie][JetBlackUI] LightROM, however strangely I was not able to boot either to TWRP neither to downloading mode via key combination.
However I had install TWRP app and from there i was able to boot to recovery mode,install the new rom and try it out.
For some reason root was not enabled in the new rom, so i figured I will try to do it via TWRP however I was unable to boot, since root access is needed to boot from TWRP app + key combo still did not work.
After searching on google, I found a poprgram which can do the trick. (Recovey-Download (CMD)
With this I was able to boot to recovery mode. Now I thought, since all this mess up was started with the new roms, I decided to restore my original stock rom, which I had a back up of. It booted up first and seemed okay, but I was curious if this solved the issues with the key comb, so I tried it going downloading mode, but it only worked with the program ((Recovey-Download (CMD)), and I saw that it is probably not gonna be good, since it only had the blue screen, but no data in the upper left corner.
Then I restarted the device and now it say " Custom binary blocked by FRP lock". and turns off itself.
I saw that FRP lock could be solved easly with Odin fresh install, problem is I have no idea how to go downloading mode. ( Assuming at this point I still can).
Sorry for the long essay but i think the more detail the easier to diagnose. Also, thank you for reading.
I would greatly appreciate any help.
BR
Csaba
Managed to solve it with USB JIG.
Is your phone an Exynos/Snapdragon variant?
csesztes said:
Managed to solve it with USB JIG.
Click to expand...
Click to collapse
Hey, how did you manage to get your phone into dl mode with an USB jig? I want to try this out, but you're the only one here who's confirmed that you were able to do this on an S7 Edge.

Nexus 6P stuck in bootloop. Bootloader unlocked and USB debugging enabled!

I'm trying to recover files from it but do not know where to start. Every thread I see either has their bootloader locked or can't access recovery mode.
My bootloader is unlocked, USB debugging is enabled and I do have access to recovery mode. I'm just wondering what to do next in order to access my photos using my PC.
If someone could help, it would be greatly appreciated. It got stuck in bootloop not long after I changed the battery.
P.S. my phone is not rooted nor have I rooted it before. Hopefully it isn't needed in order to recover files from it (even though I heard it could help).
Update: Alright so I literally heated my Nexus with a hair dryer and it got off bootloop. Hilarious. Hopefully it keeps working and doesn't go back into bootloop...

Categories

Resources