Related
As the title implies, I've failed in my attempt to root my S7 Edge. I can access the custom download tool as well as the TWRP tool that I installed via Odin. However, I have no SD card and my attempts to use ADB have been unsuccessful. Right now I am looking for an option to reset my device to factory settings. I don't care about my previous data, as this is a relatively new phone. However, I believe my warranty is voided, and that is why I am posting here.
What are my options at this point? If it helps, a micro SD is arriving via Amazon tomorrow afternoon. Ultimately, I'd like to be able to install a custom ROM or root my existing Nougat that I started with (my original intention).
As for how the process may have failed, the tutorial I watched didn't seem to make it clear that I had to enable USB debugging. I enabled OEM Unlock, but not USB Debugging. Any help would be greatly appreciated. :good:
EDIT: Smart Switch does not support the device for emergency recovery. I really think I messed up my phone
EDIT 2: After suddenly disconnecting during the download process of a fresh firmware via sammobile, I restarted the device to reach an error screen telling me to use Smart Switch Emergency recovery. However, my device was not supported. Following a guide online, I clicked on the More tab at the top right corner of the Smart Switch program and chose "Emergency software recovery and initialization". I entered the relevant information for my device and the recovery process began (fingers crossed). After it has completed, I am now once again booting my factory firmware. I'll leave this post here because I couldn't find a similar post on the first couple pages of the forum or with the search function.
Now, can anyone direct me to a proper beginners' guide to rooting the S7 Edge? I'm fresh off of iOS, which I've used and been jailbreaking for the past nine years. I thought it would only slightly more complex, but I see due to the many different versions of the same device, rooting can be quite tricky.
Edit 3: New question which I can't find the answer to anywhere... Do you need an SD card to root? I'm resetting my phone for the second time now. Got a boot loop after using ADB sideloader to install supersu.
Where did you get the stock firmware? I have the unlocked sm-g935u... made an unbelievable stupid mistake and my three day old s7 edge is partly functional (only bare essentials), but whatever I did before wasn't wiped when I did a factory wipe so my phone thinks it's rooted even though it most certainly is not. (And many features and apps won't work bc of it. )
I can't find anything useful about theNougat firmware. I'm really desperate. My company bought me this and i broke it within a week. :'(
I'm completely at a loss at this point.
I attempted to root my Samsung S7 (AT&T) with Odin, and received an error. This is my first time ever rooting a phone, and I am generally oblivious to this kind of stuff. I disconnected the phone, and it began bootloop. I loaded it into download mode, and attempted to reset to stock. However, I have had endless issues trying to flash the stock firmware to my phone. At one point I unplugged the device once again, and I received the "use Emergency Restore" error screen. I tried to restore with Smart Switch, but I was not able to access my S/N (box is nowhere to be found, managed to find a S/N on Samsung's website since I registered it but Smart Switch wouldn't take it). So, I figured trying to restore with Odin was my last option. I have tried at least 3 different Odin versions, both modified and not, and not a single one of them has worked. I've received Complete(write) errors, Model Dispatch Fail errors, and Re-Partition errors. I've tried about 3 different firmware files as well, and while I think the one I have right now is most recent, none of them seem to be working. I thought maybe an issue I was encountering was that USB debugging or whatever it's called was disabled, but I have no way of telling because I cannot boot my phone.
I was fiddling around with all of this from 11pm to 6am last night, and picked it back up as soon as I woke up. I've been freaking out about this for hours.
I feel like I'm running in circles here. I don't understand what I'm doing wrong. I'm recovery bootlooped as well. The only thing I can boot is download mode.
I wasn't very cautious with this process, and I am completely unfamiliar with most lingo on these forums and the whole process in general. I really regret trying to do this. So -- is there anything else I can try to do to fix it? Or is my phone bricked for good??? I'm endlessly frustrated and have honestly felt like crying a few times over this. I shouldn't have messed with something I know nothing about. :crying:
I thank you for your patience in dealing with me as a beginner + appreciate any help you're able to give.
Cheers.
aerialslam said:
I'm completely at a loss at this point.
I attempted to root my Samsung S7 (AT&T) with Odin, and received an error. This is my first time ever rooting a phone, and I am generally oblivious to this kind of stuff. I disconnected the phone, and it began bootloop. I loaded it into download mode, and attempted to reset to stock. However, I have had endless issues trying to flash the stock firmware to my phone. At one point I unplugged the device once again, and I received the "use Emergency Restore" error screen. I tried to restore with Smart Switch, but I was not able to access my S/N (box is nowhere to be found, managed to find a S/N on Samsung's website since I registered it but Smart Switch wouldn't take it). So, I figured trying to restore with Odin was my last option. I have tried at least 3 different Odin versions, both modified and not, and not a single one of them has worked. I've received Complete(write) errors, Model Dispatch Fail errors, and Re-Partition errors. I've tried about 3 different firmware files as well, and while I think the one I have right now is most recent, none of them seem to be working. I thought maybe an issue I was encountering was that USB debugging or whatever it's called was disabled, but I have no way of telling because I cannot boot my phone.
I was fiddling around with all of this from 11pm to 6am last night, and picked it back up as soon as I woke up. I've been freaking out about this for hours.
I feel like I'm running in circles here. I don't understand what I'm doing wrong. I'm recovery bootlooped as well. The only thing I can boot is download mode.
I wasn't very cautious with this process, and I am completely unfamiliar with most lingo on these forums and the whole process in general. I really regret trying to do this. So -- is there anything else I can try to do to fix it? Or is my phone bricked for good??? I'm endlessly frustrated and have honestly felt like crying a few times over this. I shouldn't have messed with something I know nothing about. :crying:
I thank you for your patience in dealing with me as a beginner + appreciate any help you're able to give.
Cheers.
Click to expand...
Click to collapse
If you can at least get into download mode, then simply flash it with the latest STOCK firmware for your particular model.
That will bring it back to life, and you can attempt rooting it again, if you dare
aerialslam said:
I'm completely at a loss at this point.
I attempted to root my Samsung S7 (AT&T) with Odin, and received an error. This is my first time ever rooting a phone, and I am generally oblivious to this kind of stuff. I disconnected the phone, and it began bootloop. I loaded it into download mode, and attempted to reset to stock. However, I have had endless issues trying to flash the stock firmware to my phone. At one point I unplugged the device once again, and I received the "use Emergency Restore" error screen. I tried to restore with Smart Switch, but I was not able to access my S/N (box is nowhere to be found, managed to find a S/N on Samsung's website since I registered it but Smart Switch wouldn't take it). So, I figured trying to restore with Odin was my last option. I have tried at least 3 different Odin versions, both modified and not, and not a single one of them has worked. I've received Complete(write) errors, Model Dispatch Fail errors, and Re-Partition errors. I've tried about 3 different firmware files as well, and while I think the one I have right now is most recent, none of them seem to be working. I thought maybe an issue I was encountering was that USB debugging or whatever it's called was disabled, but I have no way of telling because I cannot boot my phone.
I was fiddling around with all of this from 11pm to 6am last night, and picked it back up as soon as I woke up. I've been freaking out about this for hours.
I feel like I'm running in circles here. I don't understand what I'm doing wrong. I'm recovery bootlooped as well. The only thing I can boot is download mode.
I wasn't very cautious with this process, and I am completely unfamiliar with most lingo on these forums and the whole process in general. I really regret trying to do this. So -- is there anything else I can try to do to fix it? Or is my phone bricked for good??? I'm endlessly frustrated and have honestly felt like crying a few times over this. I shouldn't have messed with something I know nothing about. :crying:
I thank you for your patience in dealing with me as a beginner + appreciate any help you're able to give.
Cheers.
Click to expand...
Click to collapse
Did you finally recover your phone? I'm in the same problem here since yesterday and feel your frustration right now. My phone is a Samsung S7 model SM-G930A from AT&T.
I found this thread https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039 and I following the "Return to stock part", now downloading the firmware. Hope it helps.
I'm stucked in the blue screen "An error ocurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". Of course I try the Smart Switch but says that my model is not supported!
How can you recovered the download mode? I press the on/off button for some seconds and the screen turn of, but it turn on again with the freaking blue screen "An error ocurred while updating the device software. ...". I tried all the possible button combinations.
Thanks and good luck.
Stock firmware
Make sure when you go into download mode and flash that plugging the phone in is the LAST thing you do. I.e. plug phone in only after it is in download mode and only after you open Odin. Secondly, make sure you flash the STOCK firmware, as in Android Marshmallow v6.0.1 . Additonally, make sure that the re-partition option is NOT ticked, and also you might want to try turning off auto-reboot, and just hold the power button after unplugging once the status bar is all the way full and Odin says complete. Also, you need to make absolutely sure that you're getting the firmware for your exact device. I.e. SM-G930A stock firmware is NOT compatible with SM-G930F models. You could also try reinstalling the Samsung drivers. I just flashed to stock firmware then updated back to Nougat yesterday, mostly without a hitch by following these guidelines. There is a download page on rootmygalaxy with all the stock firmwares, that's what I used (I'd link but I just registered here). There is a very helpful guide on droidviews about how to update to Nougat 7.0 once you have finished flashing the stock firmware.
If I were you, I would just avoid rooting altogether. Rooting for me caused very bad performance and battery life, and it wasn't really worth the trouble. Sure, getting in-app-purchases for free was nice but I never tried flashing a custom ROM or anything because most of the stories I read involved soft bricks, bootloops, etc.
Hopefully not having USB Debugging and OEM unlock ticked doesn't brick your phone, I'm doubtful that it will. For the poster above me, make sure your phone is all the way off, the download mode button combo is vol. down+power+home all at the same time, and hold them. A screen should pop up saying press vol. up to continue. If you're still having problems, I regret to say that I am also relatively new to this and I am not all that knowledgeable.
I just made a post about my unrooting process, hopefully it helps!
https://www.youtube.com/watch?v=o6ryOQepX2Q Video shows booting into Download Mode. Or take it to a Best Buy that has a Samsung Sales section.
Hey all......I created a thread awhile back when I borked my phone trying out a new treble rom that was supposed to be so easy even a nOOb could flash it, and it ended up messing up my phone to the point where the only way for me to get it back was to follow the thread to disassemble the phone and short the chip out.
Then, the screen was not responsive on ANY rom I flash except for MM and it worked with any up to B29. I tried a few times to upgrade all in vain but I was always able to flash MM B29 and have it work again.
Flash forward to last night and my itchy trigger upgrade finger did it again and I attempted to flash the Oreo from ZTE. It flashed fine but, again, no responsive screen. I thought well, maybe I could try Nougat again and I flash many different versions and in different ways (used miFlash, EDL tool, MiFavor recovery, twrp) and all resulted in the screen not being responsive. Sigh, so I flashed MM B29 but now it will not detect any sim or even allow wifi to be turned on.
I have tried multiple times to reflash MM B29 using all the different ways above and even went back and forth between roms. I tried the original way most of us first unlocked the bootloader and flashed through all those stepped zip packages from B20 to B29 and still nothing. I finally used twrp to erase/format all data and made certain the partitions were formatted as ext4 and tried again, still no sim.
I realize that my imei is not showing and even tried a program to flash? that to the phone.
NOW, what needs to be said is during ALL of this flashing the phone signal/sim DID show......yes.......the sim DID WORK......when I flashed anything other than MM B29. LOL. Of course, the issue is none of those roms allow the screen to work.
Please, if anyone can help I would appreciate it very much. I'm thinking by flashing the Oreo from ZTE it may have changed something that the MM B29 rom is not changing to allow the phone to read the imei/sims.
I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps ?
Syberclone said:
I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps
Click to expand...
Click to collapse
I appreciate the suggestions. Unfortunately, the DFU tool doesn't seem to work for me as it remains listed as Disconnected even after choosing the correct port.
I have always flashed the MM B29 EDL rom (A2017U_B29_MARSHMALLOW_FULL_EDL) that contains the correct modem. As I said, it always worked before.
As far as checking APN/network settings, well, there are none to check because the sim is not detected so all of those choices are greyed out. The signal bars fr both sims are blank in the notification area and of course wifi does not turn on.
I just finished another round of trying different roms to flash including LOS 15. LOS came up to the welcome screen (just like all the others) AND the AT&T logo with LTE full signal bars showing. Again, the screen does not respond to touch so it's all useless. I am at a loss as to why flashing MM B29 is no longer working for me.
Stop using guides mentioned in Axon7 thread,or stop listening to other users.Only thing i see here are bricks.
Probably you have hardware fault
The Axon 7 has been the worst phone for being bricked.
I've flashed ROMs on HTC's, Motorola and Google phones all without problems.
There are way too many packages and bootstacks etc, etc that cause problems and confusion.
So I wouldn't say don't follow threads or users advice.
My advice is research, research and research some more.
Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?
djprez said:
Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?
Click to expand...
Click to collapse
Did you installed a vendor partition?
Predatorhaze said:
Did you installed a vendor partition?
Click to expand...
Click to collapse
I am not certain. If the Oreo update that I downloaded directly off the ZTE site has one, then yes. If that is the cause, how would I modify it?
@djprez: To my knowledge, ZTE's official B12/B20 do not have a vendor partition. ZTE will almost certainly never add Treble support for the A7, if they are going to do so then now is an ideal time, since the A7 is an end-of-life device and no longer being manufactured.
Long story short I'm working on loading a new (has not been used) LG V20 with Lineage OS and obviously have to pre-root the phone but I'm having problems and any help would be appreciated.
I'm currently working on trying to get DirtySanta working but in the command line when I run "run-as con" during ./step1.sh I get, "run-as: unknown package: con"
My questions are...
What am I missing?
Are there step by step instructions for completely re-loading these phones to LineageOS from factory to fully running?
The phone has the factory Android 8.0.0 and has NO data on it that needs to be saved. FastBoot is NOT working, I've tried many times.
Enable OEM unlock is not a option in the developer options on the phone.
Visseroth said:
Long story short I'm working on loading a new (has not been used) LG V20 with Lineage OS and obviously have to pre-root the phone but I'm having problems and any help would be appreciated.
I'm currently working on trying to get DirtySanta working but in the command line when I run "run-as con" during ./step1.sh I get, "run-as: unknown package: con"
My questions are...
What am I missing?
Are there step by step instructions for completely re-loading these phones to LineageOS from factory to fully running?
The phone has the factory Android 8.0.0 and has NO data on it that needs to be saved. FastBoot is NOT working, I've tried many times.
Enable OEM unlock is not a option in the developer options on the phone.
Click to expand...
Click to collapse
If you took the time to the dirty santa thread then you'd know that your phone's security patch date is date where ds has been patched, you need to be on a security patch date prior to Dec 2016
Sent from my LG-H910 using XDA Labs
Now I remember why I didn't post on these threads much. People just assUme that the posting person is a COMPLETE idiot.
This is a HELP forum where people come to get HELP and information, there's no reason to point fingers. A simple, "BTW that version you're running is a patched version, you'll need to roll it back to a prior, follow these links..." version would have done just fine.
With that I'd reply........
I realized I needed a older firmware last night when I was fighting with it for hours. I rolled it back to a firmware, dated 12-24-2016 and managed to get BadSanta to work but it caused my phone to go into a non-stop vibrate, it wouldn't complete boot and was basically bricked. I then found from another site that explained EXACTLY how to put the phone in download mode and then re-flashed the ROM (BTW, for those that don't know, you power off, hold the volume up and then plug in your data cable) but then put Android 7.0 Build number NRD90M.
The problem I am running into is everyone's information isn't is sync.
Some say how to proceed but don't say on what build number to proceed.
Some say to roll back to Android 7 Naugut but don't say which version because there are many versions of that version.
Personally I don't understand why a ROM can't be flashed via the download mode but then again I'm not a programmer.
So with that, after many hours I've made some progress but I am disappointed in how complicated and time consuming it is. I'm seriously considering a Pinephone for me and this phone (once completed) for my wife.
Right now I'm in the process of following this thread....
https://forum.xda-developers.com/v20/how-to/lgv20-vs995-verizon-aio-post-06-19-2017-t3624326
Later, after I get some work done.
Thanks for the reply though.
Well seems the BadSanta isn't working on my phone, as soon as I get past step3 and it reboots the screen is all scrambled and the vibrate motor runs continuously.
I've managed to get into TWRP once and followed the instructions but it bricks the phone at the LG startup screen.
Reloading the fastboot image doesn't do any good.
So seems I'm stuck with the stock firmware.
Can't say I didn't try.
Instructions I followed are here...
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Visseroth said:
Well seems the BadSanta isn't working on my phone, as soon as I get past step3 and it reboots the screen is all scrambled and the vibrate motor runs continuously.
I've managed to get into TWRP once and followed the instructions but it bricks the phone at the LG startup screen.
Reloading the fastboot image doesn't do any good.
So seems I'm stuck with the stock firmware.
Can't say I didn't try.
Instructions I followed are here...
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Click to expand...
Click to collapse
The vibration is normal if it's the VS995, which I'm sure you are using, right?
And the phone is not bricked, it's normal to see that warning at the start-up screen (about the device being corrupt....). Just be patient and give it time to boot.
The scrambled screen (static on boot) is also normal, just flash lineage 17.1, afaik it doesn't have static on the vs995
On a side note: double check the dirtysanta thread, you'll find most of these there
Really? I tried for many hours, multiple times and no go.
Yes it is the VS995, I guess I forgot to post that.
I did at one point get to a point where I could see a image behind all the garbled corruption on the screen and I did know that the corrupt notification was normal, that's how I made it to the TWRP once but I just couldn't get the screen fuzzy corruption to go away and the phone was still stuck vibrating non-stop.
Maybe I'm missing something?
And I only managed to get to the TWRP bootloader once.
Are all the features on the phone working on LineageOS 17.1?
I really wanted to get the phone not only up to date but limit the spying as much as possible with a device already designed to spy.
This phone is really for my wife, I'm thinking of ordering myself a PinePhone and giving that a whirl.
Visseroth said:
Really? I tried for many hours, multiple times and no go.
Yes it is the VS995, I guess I forgot to post that.
I did at one point get to a point where I could see a image behind all the garbled corruption on the screen and I did know that the corrupt notification was normal, that's how I made it to the TWRP once but I just couldn't get the screen fuzzy corruption to go away and the phone was still stuck vibrating non-stop.
Maybe I'm missing something?
And I only managed to get to the TWRP bootloader once.
Are all the features on the phone working on LineageOS 17.1?
I really wanted to get the phone not only up to date but limit the spying as much as possible with a device already designed to spy.
This phone is really for my wife, I'm thinking of ordering myself a PinePhone and giving that a whirl.
Click to expand...
Click to collapse
On stock, after it is done booting, press the power button once to turn off the main screen, then cover the upper left corner with your hand till the second screen turns off (abt 5 - 7 sec). Turn the screen back on and use your phone.
About lineage,
UPDATE: In case anyone stumbles across this thread.
I had turned off my VIRUS protection, NOT my firewall. After turning off my Windows Firewall, rebooting the phone again,MSMTool fired right up. Few hours down the drain, but progress! Thread can be marked as solved I guess.
Greetings,
I've got a fully functional working OnePlus 6T Tmobile variant with bootloader unlocked on LineageOS. It works fine, I can get to all modes, I did a factory reset, but I need to get it back to fully stock before I send it back to OnePlus for tradein.
The MSMTool keeps hitting the Sahara Communication error after 16 seconds. I've tried all the USB ports on my laptop, I've installed drivers, I've tried different USB cables, I've rebooted the laptop, I've turned off all firewalls/virus protections.
I really thought this was going to be easy, but I have 100 tabs open from Reddit and here,and I'm making no progress.
I don't have a copy of my original ROM from when I flashed it a few years ago.