Bootlooped Samsung Galaxy S5 Neo; TWRP recovery broken; Magisk rooted - General Questions and Answers

Hello.
So recently, I wanted to uninstall Magisk to experiment further with my phone. I had no experience with SuperSU or custom ROMs and wanted to try it out. I went to uninstall Magisk, but instead restoring the full stock firmware, I uninstalled Magisk root. To fix this, I thought I would need to re-flash Magisk and have it wipe its partition or whatever it's called of the device so that SuperSU can root it. So I went to recovery mode by pressing power button + volume up + home button (I have TWRP recovery installed and it was working since the previous week), however, it just went on a boot loop for 5-10 minutes. I tried taking off the battery, but TWRP would not load after. So I tried to turn the device on. It went on a bootloop. I went to the mode where you download a custom OS (volume down + power button + home button) to "cancel" the process and restart the device. It worked, and my device restarted properly.
Now here is when I become a big idiot. I went on the TWRP app (I don't remember if I made it a system app or not) and found that all of its root options were still there. I go on other apps that rely on root; Greenify, Servicely, etc, and they functioned without telling me that my root was gone. So I downloaded the latest version of TWRP and "flashed" it through the TWRP app. I then rebooted my phone. It went on a bootloop.
I tried the methods I mentioned above, but the phone wouldn't start. Since I was away for 5 days without a computer, I kept trying. I tried to remove the battery for intervals of 5 minutes, 10 minutes, half an hour to put it back and then to turn it on. I repeated booting to recovery, regularly booting and the custom OS "cancel" thing I did after removing the battery for extended periods of time. Nothing worked.
Now I'm back home and trying to fix my phone with a laptop. Bad news is, I got a new laptop, and I haven't connected my phone with it at all, so the laptop doesn't recognize the phone. I tried my old laptop, but it wouldn't recognize my phone either. I installed ADB and Fastboot but it wouldn't recognize the device. I also tried Odin, but it didn't detect the device either. My bootloader is unlocked; I'm pretty sure I left OEM unlocking on before this happened (and USB debugging too). Please help me. I
I know I sound like a complete idiot (and tech noob) but I just want to fix this.

MCMarsBoyee said:
Hello. So recently, I wanted to uninstall Magisk to experiment further with my phone. I had no experience with SuperSU or custom ROMs and wanted to try it out...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within one of the following Q&A type threads that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3207909
https://forum.xda-developers.com/showthread.php?t=3298654
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Related

How do I Unbrick? Small twist

Ok so here is the issue. My Nexus S i9020a has a power button that is no longer working. Whenever I put the battery in, it automatically boots up, to reboot I take the battery out and slide back in. I want to bring it back for warranty since my bro got the warranty until 2014 or so. I had previously had a couple of custom ROMs on it. I wanted to flash stock ROM and lock the bootloader.
When I boot into recovery (hold up while I put the battery in), I can't do anything. Even the volume up/down doesn't do anything, and of course pressing the power button doesn't select anything. So I got ROM Manager and found a copy of the stock rom. ROM Manager was supposed to install the rom from the .zip file, which it sort of did. It wiped everything and installed. I left it on while I went to do something. When I came back, the phone is stuck in the bootup animation.
If I was able to do anything in recovery I would just reflash a different ROM and go again.
I have watched some videos, and tried the Oneclick Unbrick, but doesn't work. I've read some other threads here that talked about getting Linux on a USB, or other mod. But I am trying not to go that route, as it seems pretty complicated.
When the phone is in the bootup animation and I connect it to the computer, I hear the sound that Win7 detects new hardware. If I am in the bootloader Win7 does not play any of that sounds.
I remember using adb and I still have the files on my computer from when I unlocked and rooted.
Not sure what should I do now?
also, all of my soft button lights are on during the boot animation. read in one of the threads that different lights on mean different modes. so not sure if this means anything.
hi, I am afraid the bad functioning of power button is responsible of all of these problems,
probably you can send it for warranty as is now
---------- Post added at 12:15 PM ---------- Previous post was at 12:10 PM ----------
have you tried already the linux app UnBrickable Resurrector ?
maybe you would be able to install the stock rom via fastboot
Possible fix: Remove all drivers and reinstall via Nexus root toolkit. Go to adb and flash TWRP, or CWM Touch Recovery (make sure it's touch-enabled), then flash a new rom.
Permanent fix: As far as I can remember (I also had this issue about 6 months ago) samsung will still recognize the warranty even when your bootloader is unlocked, at least in my place. The issue you're returning with is a hardware issue, not a software issue. So tell them to just replace the power button and you'll do the rest. As long as the samsung warranty sticker on top of the screw is in-tact, you're good to go. Again, this is my experience in a samsung service center near my place. I don't know how they deal with things elsewhere.
if this can help, I read in forums that also in Italy samsung support fixes nexus s in warranty even with unlocked bootloader, this is not a direct experience though
So I have tried the wugfresh Nexus Root Toolkit and tried installing different drivers. None of them can detect the phone when it is in the bootloader, windows only makes a sound when the phone is trying to boot up.
I've tried the "Flash Stock + Unroot" button but as soon as it tries checking the fastboot it cannot detect anything. The mini description says all it needs it to have the phone in the bootloader, but I can't get it to do anything else.
I have tried the guide at DroidViews (can't post links yet), but in the command prompt, fastboot just keeps waiting for the device again, windows does not detect the phone unless it starts to boot and enters the bootloop.
what do I do now?
eugene188 said:
So I have tried the wugfresh Nexus Root Toolkit and tried installing different drivers. None of them can detect the phone when it is in the bootloader, windows only makes a sound when the phone is trying to boot up.
I've tried the "Flash Stock + Unroot" button but as soon as it tries checking the fastboot it cannot detect anything. The mini description says all it needs it to have the phone in the bootloader, but I can't get it to do anything else.
I have tried the guide at DroidViews (can't post links yet), but in the command prompt, fastboot just keeps waiting for the device again, windows does not detect the phone unless it starts to boot and enters the bootloop.
what do I do now?
Click to expand...
Click to collapse
Remove all android/samsung drivers and install PDAnet drivers. PDAnet detects the phone even on bootloader.
ej8989 said:
Remove all android/samsung drivers and install PDAnet drivers. PDAnet detects the phone even on bootloader.
Click to expand...
Click to collapse
I just tried the PDAnet, I choose the Samsung drivers, then once it pops up with the screen to ask me to connect the phone then I'm stuck. Whether I put the battery in and let it bootloop or hold vol+ and put the battery in, it doesn't get past the screen. Only thing I could do was "skip USB" which still installed PDAnet but possibly without USB support and just bluetooth support.
I even tried it on my brother's laptop which is still in a relatively clean OEM state but the got stuck at the same place.

Help! Can't figure out how to re-enable root

Okay, so! Greetings all.
Back about a month ago, I successfully rooted my phone with KingoRoot, flashed TWRP 2.8.0, and installed Crdroid 7.1 Nougat for my D850.
Now, everything was fine and well, besides being one of the very unlucky users to have their phone stop being a beautiful piece of technology and, instead, become very burdensome and aggravating. It would require a battery pull, sometimes two times back to back (if it would soft reset on first pull and get stuck in boot loop), about once or twice every 3 hours, to as often as a few times an hour.
So, I tried something new. I went back to LineageOS' website and looked through the other D850 releases(all of what, 3?) and settled on the AOSP 7.1 ROM.It seemed like it'd be a great idea, having everything functioning and not having to deal with battery pulls every day. Now my phone is practically nonfunctional, as it doesn't receive cell service and can't read SIM cards.
Needed Information:
-Phone is an LG D850, running a (nonfunctional) custom AOSP 7.1 ROM
-Phone seems to lack root access, and can't be One-Click rooted as is (Haven't been successful with any one click program yet)
-Phone is also lacking in recovery (Tried to access via adb, manual hard buttons, and neither worked)
Now for the actual question: What can I do to make my phone function again, whether I have to reinstall my backup of my previous fail (thus requiring TWRP and root) or just get it back to a truly stock ROM?
Thank you all for your time and consideration. I'll check back in the morning.
Warning: I am no expert, in fact I'm barely a noob, but one thing I do well, and that is I always do a backup. That being said it appears there are two paths to salvation. Get your recovery working or go back to stock. If you installed a recovery but can't get back to it try shutting off phone then pressing power and volume down simultaneously. When logo appears release buttons and then immediately press both again. It will offer a decision screen where you use vol up/down to select. Choose yes on both, (it will not reset the phone as indicated). This should get you into recovery, from there you may be able to flash the needed rom, gapps, root, etc. My suggestion is to load the needed files onto your sd card beforehand. If this fails there is the downgrade via LGUP. This is pretty nifty. I had to rely on the expertise of a Mr. Heyelton and his post, https://forum.xda-developers.com/showthread.php?t=2785089. To my knowledge the POS known as the AT&T d850 can only be rooted at KK. Mr. Heyelton's guide can get you there. from there you can stay with stock, upgrade to a higher stock (?) or proceed to root, TWRP and rom the phone. Don't forget to upgrade your modem, https://forum.xda-developers.com/att-lg-g3/general/modems-collection-d850-21r-20f-10d-t3213856.
alliance1975 said:
Warning: I am no expert, in fact I'm barely a noob, but one thing I do well, and that is I always do a backup. That being said it appears there are two paths to salvation. Get your recovery working or go back to stock. If you installed a recovery but can't get back to it try shutting off phone then pressing power and volume down simultaneously. When logo appears release buttons and then immediately press both again. It will offer a decision screen where you use vol up/down to select. Choose yes on both, (it will not reset the phone as indicated). This should get you into recovery, from there you may be able to flash the needed rom, gapps, root, etc. My suggestion is to load the needed files onto your sd card beforehand. If this fails there is the downgrade via LGUP. This is pretty nifty. I had to rely on the expertise of a Mr. Heyelton and his post, https://forum.xda-developers.com/showthread.php?t=2785089. To my knowledge the POS known as the AT&T d850 can only be rooted at KK. Mr. Heyelton's guide can get you there. from there you can stay with stock, upgrade to a higher stock (?) or proceed to root, TWRP and rom the phone. Don't forget to upgrade your modem, https://forum.xda-developers.com/att-lg-g3/general/modems-collection-d850-21r-20f-10d-t3213856.
Click to expand...
Click to collapse
Hey man. I wanted to say thanks for pointing me in the right direction. :good: :highfive: I managed to flash it back to stock, and I'll just figure out a different rom to go with. As far as fixing the issue with the recovery not coming up, I have no idea. It was just messed up, I guess. The phone wouldn't go to recovery even after selecting yes both times on the factory reset screen; it would just go black and a red+blue notification light would pop up. Was weird. Managed to get it to stock though, so it's better than it was. Thank you!

Pixel will not power on after TWRP 3.2.1.2 flash

Pixel not powering on, I flashed TWRP 3.2.1.2 and tried to flash superuser 2.82 SR5. Superuser never installed but the phone seemed to be working fine, I went back into twrp a few times and everything seemed fine. So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on?? any help from anyone, I tired plugging it into the wall and it does not seem to power on at all or even charge. Thanks in a advance for any help!
I had an issue like this. Hold down the power button and down volume button at the same time. Keep holding it down. It took 20-30 seconds for me.
By the way, what version of Android are you on? SuperSU won't work on Android 8.1. You have to use Magisk. You can use the latest Magisk but if you want to use @Chainfire's FlashFire app, you have to use Magisk v14.2.
I think flashing SuperSU is what broke your ****. Try flashing SuperSU uninstaller and then reboot into recovery and flash magisk
KittyRgnarok said:
I think flashing SuperSU is what broke your ****. Try flashing SuperSU uninstaller and then reboot into recovery and flash magisk
Click to expand...
Click to collapse
His phone won't turn on lol
shagbag913 said:
His phone won't turn on lol
Click to expand...
Click to collapse
He didn't give any details as to what he means by won't turn on. To me that means system isn't working and bootloader and recovery are intact. Your phone doesn't need to boot properly to flash a zip
KittyRgnarok said:
He didn't give any details as to what he means by won't turn on. To me that means system isn't working and bootloader and recovery are intact. Your phone doesn't need to boot properly to flash a zip
Click to expand...
Click to collapse
He said his phone will not power on. He also said he plugged it in and It still wouldn't power on. It sounds to me that his phone won't power on lol.
shagbag913 said:
He said his phone will not power on. He also said he plugged it in and It still wouldn't power on. It sounds to me that his phone won't power on lol.
Click to expand...
Click to collapse
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
KittyRgnarok said:
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
Click to expand...
Click to collapse
"So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on??"
---------- Post added at 11:51 PM ---------- Previous post was at 11:47 PM ----------
Aphex^ said:
Pixel not powering on, I flashed TWRP 3.2.1.2 and tried to flash superuser 2.82 SR5. Superuser never installed but the phone seemed to be working fine, I went back into twrp a few times and everything seemed fine. So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on?? any help from anyone, I tired plugging it into the wall and it does not seem to power on at all or even charge. Thanks in a advance for any help!
Click to expand...
Click to collapse
I would try holding the power button for a good 5 mins, some say that can turn it back on. If that doesn't work plug it into a PC and look to see what its name is on your PC. If it says "Qualcomm HS-USB QDLoader 9008", unfortunately its hard bricked.
Actually
KittyRgnarok said:
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
Click to expand...
Click to collapse
Your actually are talking about the problem I just did a couple of hours ago...I was so mad...Like WTH did I do wrong. THANK YOU FOR YOUR HELP
Hello everyone,
If you are trying to flash TWRP to an android oreo 8.1 google pixel, it will not work, so DON'T ATTEMPT IT! I have tried this before and your best bet as of now is to flash the bootloader back to stock. If you need to use it for whatever reason just fastboot into it.
Also, SuperSU doesn't work with Android 8.1 Oreo, as it isn't compatible. The new method is using Magisk Manager.
If you can't turn on your phone, then this means your bootloader is completely damaged and you will need to replace your phone.
mcbeat257 said:
Hello everyone,
If you are trying to flash TWRP to an android oreo 8.1 google pixel, it will not work, so DON'T ATTEMPT IT! I have tried this before and your best bet as of now is to flash the bootloader back to stock. If you need to use it for whatever reason just fastboot into it.
Also, SuperSU doesn't work with Android 8.1 Oreo, as it isn't compatible. The new method is using Magisk Manager.
If you can't turn on your phone, then this means your bootloader is completely damaged and you will need to replace your phone.
Click to expand...
Click to collapse
You definitely can flash twrp on an 8.1 pixel. I have it right now. Also, most of the time that does mean it is hard bricked, but sometimes these phones can trick you. If you think your phone is bricked because the screen is off and there is no response, hold the power button down for 1 to 2 minutes, SOMETIMES it can come back on.
I had a similar issue where the phone would not turn on after I was loading TWRP via Fastboot. I went to sleep that night thinking I had bricked it. Held every button down for at least 90 seconds and every combination of buttons. Woke up in the morning to try it one more time before I gave up and it easily booted up but only had 1% battery. I had charged it fully before trying to load TWRP. I plugged it in and charged it and was good to go including Fastboot booting into TWRP and then flashing SuperSu and the Xposed framework. Both work fine. Rooted and using Xposed modules.
I came here to see if I could flash TWRP to the phone. Apparently I can, but would love to know what the steps are so as not to screw anything up or mess up which partition, etc.
What the freak did I just read. Seems to me the issue is not twrp but whatever people are trying to flash using twrp. @mcbeat257 TWRP works just fine. Been running the latest for several months now. Works on 8.1 both stock and custom roms, even on Android P DP2. So If you can't make it work while several others users have then I would say you're not eligible to give advice as to say "do not attempt it!". You must be doing something wrong. Please stop spreading false information. I'd be happy to help you out if you describe the procedure you've been going about to flash it to make it work.
As to the OP, try as shagbag913 told you to do. Press the power button for some minutes. Or try power-button+volume down (See if you manage to get into the bootloader menu). If it doesn't work then connect your device to your computer and see if it's recognized. If it's flat dead and won't turn on then motherboard might be toast. If it's recognized as shagbag913 said as a Qualcomm HS-USB QDLoader 9008 then it's hardbricked.
---------- Post added at 01:59 PM ---------- Previous post was at 01:39 PM ----------
724A said:
I had a similar issue where the phone would not turn on after I was loading TWRP via Fastboot. I went to sleep that night thinking I had bricked it. Held every button down for at least 90 seconds and every combination of buttons. Woke up in the morning to try it one more time before I gave up and it easily booted up but only had 1% battery. I had charged it fully before trying to load TWRP. I plugged it in and charged it and was good to go including Fastboot booting into TWRP and then flashing SuperSu and the Xposed framework. Both work fine. Rooted and using Xposed modules.
I came here to see if I could flash TWRP to the phone. Apparently I can, but would love to know what the steps are so as not to screw anything up or mess up which partition, etc.
Click to expand...
Click to collapse
There is an entire thread for twrp and how to flash: https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314

Questions about 1st time root SM-J700P w/7.1.1

Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.
J727P
Nupid Stoob said:
Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.
Click to expand...
Click to collapse
ok you have an older phone the J700P you can start by downloading odin an twrp recovery an superSU zip you can get twrp from here !https://twrp.me/devices/samsunggalaxyj72015qcomsprint.html
an odin from here
https://mega.nz/#!nYVDXBAC!_cTWbW4_Ow8sZMWcZvO7bVwEEBFlD1DQsB5NeFhj1EY
An just google latest superSU zip to find that !
good luck !
step 1 enable oem in development settings !
step 2 put phone into download mod an flash twrp then boot into twrp recovery an flash superSU zip !
Thank you for the info. I'm presently confused. Here's what I've done:
I ran Odin and flashed with twrp-3.2.1-0-j7ltespr.img.tar. It went through successfully going off odin's message.
Vol. up + home + power. It'll eventually show a yellow triangle with the white trash can guy on it's side stating "No Command". Power + up gets the Android Recovery screen.
At this point, am I supposed to choose the Wipe Data/factory reset option? I see tuts that seem suggest I should already be in the twrp UI or something. I've tried watching vids and looking at a handful of tuts, but either they are the wrong phone, too old, the button combos show something else entirely, etc.
Thanks!
Anyone? Videos show the buttons vol. up + home + power as booting right into twrp recovery gui. For me, it's going into "Android Recovery" screen. Is there an extra step with Odin or something that I missed? Or am I supposed to wipe/boot in the Android Recovery screen and it'll boot the twrp recovery gui? If bricking something I'm not familiar with wasn't a concern, I'd be courageous with it.
I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?
J700P
Nupid Stoob said:
I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?
Click to expand...
Click to collapse
Ok when flashing twrp with Odin first uncheck auto reboot in options flash twrp pull battery replace battery an boot into twrp an flash superSU zip then reboot system !
Thank you so much Peter! That did the trick THANK YOU :good:
For posterity to anyone else w/limited root knowledge with a SM-J700P Virgin variant running 7.1.1 (and what was most recent factory updates until this point); Flashed the twrp-3.2.1-0-j7ltespr.img.tar again w/o auto reboot in options of Odin, pulled battery once safe (i.e. you get the "Pass" message from Odin confirming everything went as planned) to get out of the downloading screen, replaced battery, booted the recovery (vol up + power + home) and it finally booted into the twrp recovery gui. Selected the "Install" option, then went to where the supersu.zip was stored on the SD (I created a separate "supersu" folder via PC connection for easy locating; internal phone memory card looks to now be unlocked, so can most likely use that if you don't have a SD card). Checked the "reboot once installed option" in the gui box and swiped to install supersu,zip and verified it was rooted via app after phone fully booted back up.
BTW, If anyone gets a hang/crash in Odin immediately after trying to select a twrp tar image in the "AP" box, try downloading the twrp image via PC instead of the through the phone (the legit twrp site that has the repository of past/current .tar), and just put it somewhere like Odin folder on desktop. Somehow, mine were getting corrupted via phone download through the twrp app, and Odin would NOT recognize the file was bad/corrupt when trying to select it via the AP box and hangs instead of giving a warning message. I ran into this earlier on then noticed the file was too small for some reason after viewing it on my PC, hence the Odin hang that needed a task manager kill.
I hate to necro an old thread but I still do not want to create an entire new topic for a single question. If I was to follow this info will it wipe the phone or will it simply root it while keeping all data on the phone? I ask as it is my wife's old phone and she would be pissed if I wiped her apps and everything on accident since she wont be able to remember what she had.
Edit: also when I add the TWRP file to odin it immediately hang/crashes like OP mentions but I am already DLing via pc. any thoughts?

I made a goof rooting my phone, please help

So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Zacigator said:
So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Click to expand...
Click to collapse
U are in edl mode u need to search for blank flash it should get u back up and running
Zacigator said:
So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Click to expand...
Click to collapse
Did you get it running

Categories

Resources