I'm having trouble connecting to the mobile network after I, very stupidly, tried to install Magisk on my phone after rooting it using this method: "Root For The S7/S7 Edge Oreo Is Finally Here!!" (search this in the xda forums, I can't upload links yet)
After installing Magisk, I tried to boot and got this message on the screen that basically said I couldn't boot due to a change to the boot image. I fixed that by installing the "G930PVPU6CRE7_G930PSPT6CRE7_SPR" stock firmware from sammobile. After this is that the problem presented itself. I could boot again and everything was pretty much fine except I could not get the phone to connect to the Sprint network. I've wiped and flashed the phone several times, I have even downloaded the stock firmware from different sources and nothing. I also tried activating the phone through the setting with no success.
Somebody, please help me, I've spent my whole day on this and I am getting stressed out.
Related
I've rooted and replaced the ROM on 3 other Android devices. I've spent two or three nights on this. Googling and reading page after page to try to get this right. I know I'm seriously lacking in knowledge, but I just can't stand the bloatware and lack of control over an OEM ROM. I knew I was taking a risk, but I did my best to be diligent without spending an excessive amount of time. All that said, I appreciate, in advance any help anyone can offer me. Whether that's direct advice or directing me to proper resources that I can't seem to find.
Samsung S5 SM-G900P (kltespr)
I had rooted it. I replaced the Sprint stock ROM (5.0.1 I think) with CM12.1 (which just got an OTA). I had TWRP 2.8.7 on it.
Unfortunately, I needed my research suggested I needed a Touchwiz ROM in order to activate phone service on the cell provider I'd chosen (Ting).
So I selected MOAR v7 and started following the directions here:
at galaxys5root.com/sprint-galaxy-s5-custom-roms/moar-lollipop-rom-for-sprint-galaxy-s5-w-2-8ghz-oc
I made a backup. I wiped the system/cache/davlik/etc.
I installed the Android 5.0 Bootloader TAR (G900P NDK Lollipop) per the instructions via Odin and using the Bootloader option. The flash failed. I can repeat the failure (ran Odin as admin, tried multiple USB ports, restarted the computer etc). I've since tried to send several recovery ROMS or OS ROMS (pardon if I'm using the wrong terminology here) to the device, but all I can get is download mode or a screen that says Samsung Galaxy S5 powered by Android (with Kernel is not Seandroid enforcing at the top). Sending TWRP via Odin has worked with a PASS, but still can't startup the device.
I can provide more detailed logs or information about where I'm stuck and how, but on the off chance that this is an obvious thing I'm going to stop here unless more detail would be useful.
Again, I'm grateful in advance for any help.
Moshker
Follow up and how I fixed my brick
This post is intended as a follow up in case anyone runs into a similiar problem and stumbles onto my post.
After trying several different bootloaders, including the stock ones from Samsung (multiple download attempts, very slow speeds, some didn't pass md5 check), and full ROM efforts via Odin 3.10.7 I was finally able to get one ROM to take.
G900PVPU3BOG1_G900PSPT3BOG1_SPR from androidfilehost.com/?fid=24052804347794921
After getting the phone activated on Ting I used Odin to push Chainfire Auto Root (408). I verified root after restart. Used Nandroid to make a new backup. I used Flashify to install TWRP 2.8.7. I restarted to recovery and DID NOT use TWRP to wipe the system/data/etc and instead loaded the MOAR7.0.OA6 ROM. During the ROM install process it asked if I'd like to wipe system/cache/davlik/etc. I did. The ROM installed successfully. I ran a Nandroid restore to bring back my apps and data. Most restored properly.
I still don't really understand what went wrong, why my efforts to fix it failed, and why the last thing I tried worked.
Really loving MOAR. I'm using the Numix theme and it's just incredibly clean and fast. CM12.1 had intermittent micro-freezes/lags that were driving me a little nuts and MOAR is really smooth and quite fast. I was pretty disappointed in CM as I had it a long time ago on an original DInc (7.2!).
Anyway, if you're phone is bricked, keep on fighting the good fight.
Hi, I've been reading the thread for CF auto root to give it a go. I've downloaded the drivers (I've got 1.5.51 now installed, haven't been able to find later ones), I've got the 2.74 SU version that helps to overcome a recent security policy update issue reverting root status and the CF auto root zip file (CF-Auto-Root-hero2lte-hero2ltexx-smg935f.zip) which has odin 3.10.6 included (not quite sure if I can use any recent odin version). I even got my stock firmware com sammobile and extract the proper boot.img from the AP* file (just in case I got something wrong at sometime). I've enabled the OEM unlock too on developer options. I understand I can give it a go without having to go with a custom recovery (still not sure and haven't got the whole picture about the dm-verity thingy and what effects has on the device but someone mentioned something like loosing the encryption or so). This is my first try on getting root on my s7 edge G935F (international version), so it shouldn't have any boot.img problem (but trying to be prepare since I can't go about without my phone being working).
So, I've got my phone into download mode, started odin, loaded on AP the tar.md5 file from the CD auto root zip file (CF-Auto-Root-hero2lte-hero2ltexx-smg935f.tar.md5), connect the device throuhg usb cable and I was expecting Odin to recognize it but nothing happens. Since in the threads I've been researching for s7 edge there is no indication on waiting to see something happening on ODIN (but in some other threads - not s7 edge related though - mention something about having to see a blue indicator on COM), I'm not quite sure if I'm expected to just hit start even if no apparent change is happening on ODIN nor there is some drivers installing/configuring when connecting the device on download mode. Since I'm quite new to this, I'm no sure if I should connect the device first with some other option enabled, like USB debugging or if I'm missing something quite obvious for someone familiar with flashing with odin?
Kind regards for any help!
PS. I did tried to find an answer through searching but foung nothing related s7 edge wise so I'm at a loss not even knowing if just hitting start without having the device recognized on ODIN will do any harm at all (that newbie I am)
Try odin 3.11
Aldo plug your phone in first and than once recognised load the autoroot to ap
skinza said:
Try odin 3.11
Aldo plug your phone in first and than once recognised load the autoroot to ap
Click to expand...
Click to collapse
Thank you skinza for your reply, I did tried what you suggested and although it wasn't enough for getting it solved it helped me to know I was on the correct path and that I could use an updated odin.. finally, the problem was on embarrassing one since I went into download mode but hadn't push the volume up to get into the actual ODIN mode (too newbie of me but I was trying to follow the instructions I'd found and none were that specific - a bit afraid of messing it up). Nonetheless, thanks again for your time! Kind regards!
Edit: Now I'm rooted (thanks CF) and it took less than expected (a couple of mins or so). I didn't go the custom recovery way, so it might have been that.
cmanh said:
Thank you skinza for your reply, I did tried what you suggested and although it wasn't enough for getting it solved it helped me to know I was on the correct path and that I could use an updated odin.. finally, the problem was on embarrassing one since I went into download mode but hadn't push the volume up to get into the actual ODIN mode (too newbie of me but I was trying to follow the instructions I'd found and none were that specific - a bit afraid of messing it up). Nonetheless, thanks again for your time! Kind regards!
Edit: Now I'm rooted (thanks CF) and it took less than expected (a couple of mins or so). I didn't go the custom recovery way, so it might have been that.
Click to expand...
Click to collapse
Not a problem mate
Just fyi you will need twrp if you want to install custom roms like superman rom or echo rom etc
skinza said:
Not a problem mate
Just fyi you will need twrp if you want to install custom roms like superman rom or echo rom etc
Click to expand...
Click to collapse
Thanks again! for now I won't be going for a custom rom but wanted to be able to install a firewall to stop some apps from draining my prepaid data (limited)..
I was planning on having xposed installed but it seems I need a custom recovery for that as well.. I used to have xprivacy on a previous nexus 4 and loved I could limit some permissions that are still missing now on marshmallow but haven't got a grip yet as per the effects due to the dm-verity thing.. would you happen to know anything about it? and I was also wondering about if I do need to have the OEM unlock still enabled now that I'm rooted? (The later because I'd been robbed of my cellphones in the past - even recently a new s7 edge that didn't last me even a month and wouldn't want to let them have an easy pie on having the device available)
Regards!
I'm facing the same issue but even after going into download mode properly after pressing vol up
odin doesn't detect my s7 edge
I've installed all the drivers also
Singhathia said:
I'm facing the same issue but even after going into download mode properly after pressing vol up
odin doesn't detect my s7 edge
I've installed all the drivers also
Click to expand...
Click to collapse
Got the same issue. I'm new with this. My colleague wants me to learn and test and load Lineageos on some brand new S7 G930F devices he gave me which I have already switched to dev mode with OEM unlock and USB debugging on and the devices smoothly jumped into ODIN downloading.... mode
I also have the proper Samsung USB Driver installed. (did it several times after ODIN didn't recognize my device)
However, according to the manual, I should start up ODIN, then connect the device via USB cable to the workstation (as unsuccessful I already tried 3 workstations with Windows 7 and Windows 10) whilst having the phone in download mode... .BUT NOTHING APPEARS in the Log field and the ID:COM Box doesn't change colour and my manual says that it should.
My workstation however recognizes the devices with positive messages so I guess the drivers are good.
My co-worker gave me ODIN v3.10, but as this didn't work I downloaded and installed V3.12, but unfortunately also without any luck.
What am I doing wrong?
which OS?
S7 edge SM-G935F
Hey guys,
i tried rooting my s7 edge but after i got into TWRP my phone went into a bootloop. when i got back download mode, odin still found my phone, though everytime i tried to enter TWRP again, odin said there was a FAIL and my phone immediatly went back into bootloop. I tried to reinstall the samsung usb drivers but now odin cant find my phone anymore.
Before i screw up even more, can someone please help me? right now im stuck in download mode and odin 12, 11, and 10 all wont recognize my phone, also not if i use different cables. my windows laptop however still gives me the device found and device disconnected sound everytime i (dis)connect my phone.
any ideas?
thanks
EDIT: Okay i tried my USB 3.0 port and now odin found my phone. just weird... now i just need to solve the problem that I'm still stuck in the Bootloop but that probably doesnt belong in this thread
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 have an SAMSUNG s8 SM-G950F which I purchased threw Amazon as new from Italy, I live in the UK.
I decided to try rooting it Following these steps
1st of all I tried using Odin3.V3.10.6 and using CF-Auto-Root-dreamlte-dreamltexx-smg950f.tar.md5
Al this seemed to do was factory reset my phone it still worked fine but was not rooted.
so I tried the method below, from that site, wont let me post links so took the . out
galaxys8root com galaxy-s8-root how-to-root-galaxy-s8-or-s8-plus-exynos
When it game time to to do the 2nd key combination (step11) for the twrp, to load the boot loader i missed it, and my phone was stuck, at boot screen and would do nothing, i tired to use Odin to write the file again it never happened.
I did some more goggling saw that web site is out of date and there was a new version of twrp, downloaded twrp-3.2.1-0-dreamlte.img.tar and tried using odin to flash that, still was not having it, still stuck at the screen. Figured out how to get my phone back into usb upload mode and tried again, and then i kept getting the message that their was no P part partition and it failed.
Tried this a few times did some more goggling, saw the thing about doing it letting it fail, reboot the phone and do it straight away this did not work with the twrp-3.2.1-0-dreamlte.img.tar, but did work with CF-Auto-Root-dreamlte-dreamltexx-smg950f.tar.md5 file.
This let my phone boot again, and was rooted, but this caused me issues with running apps and I saw there was no way to hide the cf auto root so decided to just reset my phone.
This worked but now my phone fails the Safety test and i can not use apps that need it....
So was wondering if any one could advise me what my best course of action is, can i put my phone back to stock some how so it will pass the saftynet again or do I need to try the twrp so i can use magika and hide the fact its rooted?
Thanks in advance, included some screen shots from the software screen in case it helps..
Hello XDA. I recently revived my G6 after it sat in my drawer for years and was delighted to see HavocOS on Oreo still running on it. I popped in my T-Mobile SIM and voila, service. My only issue was horrible data speeds. I tried every network settings and apn fix that is relevant to my device but I was still stuck with virtually no 4G data. So, my last resort was to flash back to stock. Now, I dont know if there is a specific method for this device as I forgot how complicated the root exploit was. But I went ahead and downloaded the latest stock .kdz (20g), LGUP and the drivers and proceeded as normal to flash the kdz over. I had SEVERAL issues getting my device model to be recognized and finally grabbed the right LGUP version that worked. I proceeded to flash the kdz when it gave me an error round 31%. I did much troubleshooting research and came up empty, finally decided to try flashing the stock version it was on (20a) to just restore it.
This worked. I thought I was saved until the phone froze on the T-Mobile logo while booting and didnt budge for an hour. Much more googling and I found a thread that looked promising and seemed to help. At first. It flashed the kdz, gave me the error, and when I tried to flash the dz, nothing. I retried LGUP with 20a stock, unknown model. I tried to go back through the whole rooting process again and stick it out with minimal service. The FWUL/lglaf portion of the guide is where I got stuck. My device would not be recognized in FWUL, I couldnt get wifi so plugged in my ethernet. And then I kept getting "USB configuration not set" and "input/output" errors, and I noticed that while booting FWUL, the step "Loading Kernel Modules" fails. So I assumed that FWUL was not loading any modules, including USB's (which explained the errors), so I booted up my own Manjaro install and cloned the same project there. Knowing all my modules work now, I still get the "Input/Output" error.
So now I'm led to believe this phone is hard-bricked. It registers as a port in Window's Device Manager, "LG AndroidUSB SerialNet" or something like that. I tried following the unknown model guide again to no avail. I'm at a loss. Whatever info is needed for debugging I'll provide. I'm dualbooting Win10 and Manjaro so any methods are viable.
Which specific stock KDZ(s) did you try to flash on your phone (full kdz name)? You need to seperate flashing and rooting as two separate tasks because from your post I can't tell if you are able to boot after flashing stock kdz or not. First, if your phone is not booting, you gotta recover from that and flash a stock kdz.
Also, try using the Dev patched LG UP from this post (thank the dev while you are there): https://forum.xda-developers.com/lg...ssflashing-t3780969/post76510671#post76510671
Try the 'Partition DL' option when you flash and select all partitions in the next window.
Once you are able to boot a stock rom, you can try using a VMWare such as virtual box, install/mount FWUL in a virtual environment and use that to root the phone. I think the process is somewhere here on the runningnak3d's guide or on another post, I will try find a link later.