I am trying 2 days well 24hrs solid almost now to get root on a Galaxy S10+ I suspect is the beyond2lte it's been nothing short of living hell I am growing to hate this S10+ as a result of this to be honest, it has a moisture detected warning cvlearly a myth but any wasy it's running but it cannot flash past mobdem.bin once creating a patched AP when using home_csc file in the arrangement of files to flash it gets to modem bin choosing the alternate csc file included it only gets to vendor.img when flashing with this patched AP file switching the AP to the original can flash either option without issues.
I don't understand what the problem is I tried without reboot andc with makes no difference any way but just incase, also switched the cable and ports still no good I am using windows 11 is this potentially the cause by any chance does it have to be windows 10 to weork fully I don't know but I desperately need help guys please.
The only other logic I can assume to be possibnly right is it's stuck on this modem because it isn't the beyond2lte so if it isn't how do you know which it is?
Related
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
so heres the situation, a couple weeks ago my sammy a5 meet a horrible end and ive been without a phone. My buddy gave me his old s7 edge, its got cracked screen and has been sitting inn a drawer(hes rocking a pixel xl instead). so got it home charged it up turn it on and it got this blue sceen says there was a problem updating.
so longer story short got the stock 6.0.1 for bell 935w8 but i only run ubuntu, now while im able to flash smaller tars or img files flashing all stock at once wont work with either heimdall or Jodin3.
thought i could maybe flash twrp and go straight into custom roms i cant flash anything onto the device because of FAP lock in download mode.
Can anyone help me out? i know this would be easier with a windows comp but i dont have one.
can anyone help me
Im using a Galaxy s7 edge exynos and I have been trying ALL day to return to stock firmware. (was aiming for 6.0, but when that didnt work I started trying 7.0 with slightly more success...) I was previously rooted via magisk using TWRP. I am not able to flash all 4 files at once via odin, (BL, AP, CP, CSC) I quickly get an error on both the device and odin (decive says binary 2 device something... Odin stops at either Param.bin or cm.bin depending on which CSC I use) the BL file seems to be the one that refuses to flash (from any of the 4 versions of odin i have and using different firmware versions that previously worked on the phone)
I am able to flash just the AP, CP, and CSC but when android loads up my mobile data doesnt work and many other things dont work correctly as well ...
I am so confused as to what I can even possibly do now. Im sitting here with a phone that wont correctly software update that I cant correctly root and has no mobile data. No full 4 files will correctly flash without odin error. TWRP gives me crap now too. I have wiped and formatted all the data many times hoping id missed something.
Send help
also
I try to manually update and it says "registering device" for a sec and then "Process failed" Like android 7.0 is running but not how it was before. I did update to newest update via the phone before i decided to try to revert to android 6.0 again because I was having issues connecting my pokemon go+
Hmmmm I still have problems with 5ghz and mobile data but i got magisk to install... luckily im not using this for phone purposes. this is the best i can do without help
What is yohr phone model ?
G935f
G935f
Currently running g935fd
Did you flash and Oreo rom by anychance?
"Maybe", i say maybe if you did thats why you cant go back to a < 8.0 version
riseofsand said:
Did you flash and Oreo rom by anychance?
"Maybe", i say maybe if you did thats why you cant go back to a < 8.0 version
Click to expand...
Click to collapse
I didn't try anything with oreo until like 10 hours of failing everything and reading everything I could find. It was unofficial and apps wouldn't install or update correctly. So actually what I got to semi work was 7.0 again. Build G935FXXU1DPLT. It doesn't show cell tower signal or work with 5ghz anymore but I got magisk installed and I can run apps off of wifi. (Same as before 8.0 but got magisk working this time)
I'd still like to try to get my 5ghz and cell signal (just in case something happens to my main phone) but I'm scared to soft brick my phone for the 1000th time in 2 days when I managed to get it semi working.
CactuarKing said:
I didn't try anything with oreo until like 10 hours of failing everything and reading everything I could find. It was unofficial and apps wouldn't install or update correctly. So actually what I got to semi work was 7.0 again. Build G935FXXU1DPLT. It doesn't show cell tower signal or work with 5ghz anymore but I got magisk installed and I can run apps off of wifi. (Same as before 8.0 but got magisk working this time)
Click to expand...
Click to collapse
Last time something like that happend to me, is because i was flashing the wrong stock rom (same model but wrong original carrier) sometimes it does matter, sometimes not
I was worried I might have messed it up for good as well luckily I'm not completely stuck but I still dont understand why I couldnt just 100% flash my OS via odin like I always do. Although I got cocky and started without following instructions up on the computer this time. Just my luck
double check mod #it can change with different roms my s5 tmobile g900t originally now its grown into g935f S7 edge
I have lost the phone that has been working for ages. I am broke atm. Please help I need to use my phone. I was trying to get my radio to work again because I lost data a couple weeks back. So I have spent more time than I even should have for this trying to fix it.
I have run Odin 3.07 with
lineage-15.1-20190210-UNOFFICIAL-jfltexx
lineage-14.1-20190212-nightly-jfltexx-signed
and
open_gapps-arm-7.1-pico-20190209
I have wiped everything and tried 2 different system boards ;
from download mode I have
used I337MVLSGQB1_I337MOYAGQB1_I337MVLSGQB1_HOME.tar
to reload with nothing checked but F. Reset Time.
pulled out the cable then the battery.
went straght to recovery (system was going there already) to do first stage unpack with android and progress bar.
It said BAR and END
I went in back in after restart, and a full wipe.
And after a long wait .. the system very glitchy, slow like something was running in the background (modem ?) if I open the phone app it wont close and calls are silent. then resets over and over..
I have tried custom roms, and flashing latest modem and original ? Whats up ? anyone
PLEAESSEEE help soon .. I am going crazy cuz this is literally my only phone and I need to use it !!!!
Had an old system board and tried to replace it and ended up in the same place with the second board ?!?! what is going on !
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
I know your post was a while ago but you cannot use Odin to flash a custom ROM.
Are you flashing the latest stock ROM from sammobile.com or updato.com?
audit13 said:
I know your post was a while ago but you cannot use Odin to flash a custom ROM.
Are you flashing the latest stock ROM from sammobile.com or updato.com?
Click to expand...
Click to collapse
I ended up using the pixel experience rom. I am sure I have the wrong bootloader and modem for i337m though. It works with data when I reset network settings and re-enable. Data each reboot. For the longest time lineage 9505 ROMs worked until like Feb 5th I saw the data just fall use just fall off. I couldn't get chatr to work anymore. It was a nightmare I went to stock and , pitted the phone and it would only function until I added TWRP and tried a nougat rom or even with latest modem. Wifi was evn a problem. Now I am using like a lollipop bootloader with the green battery charging and modem isn't right. When I flash a different modem and bootloader in Odin and rip the battery and then cableit doesn't even change .
Wtf?
futiless said:
I ended up using the pixel experience rom. I am sure I have the wrong bootloader and modem for i337m though. It works with data when I reset network settings and re-enable. Data each reboot. For the longest time lineage 9505 ROMs worked until like Feb 5th I saw the data just fall use just fall off. I couldn't get chatr to work anymore. It was a nightmare I went to stock and , pitted the phone and it would only function until I added TWRP and tried a nougat rom or even with latest modem. Wifi was evn a problem. Now I am using like a lollipop bootloader with the green battery charging and modem isn't right. When I flash a different modem and bootloader in Odin and rip the battery and then cableit doesn't even change .
Wtf?
Click to expand...
Click to collapse
I'm not sure how you could flash the wrong bootloader unless it was flashed using TWRP or CWM. To confirm, boot into download mode to see the model # listed on the screen.
Are the modem and bootloader matched; i.e. the phone is running a 5.0 bootloader and modem? To easily ensure that both are matched, you can flash the latest stock ROM using Odin.
If the modem version is not changing after being flashed, it is possible that the internal memory is faulty.
audit13 said:
I'm not sure how you could flash the wrong bootloader unless it was flashed using TWRP or CWM. To confirm, boot into download mode to see the model # listed on the screen.
Are the modem and bootloader matched; i.e. the phone is running a 5.0 bootloader and modem? To easily ensure that both are matched, you can flash the latest stock ROM using Odin.
If the modem version is not changing after being flashed, it is possible that the internal memory is faulty.
Click to expand...
Click to collapse
Can you tell me what version the latest boot loader and modem is for Canadian i337m
I haven't had an s4 for a long time but it was running the latest OH1 firmware: https://updato.com/firmware-archive-select-model?record=8D5422F720B911E6949E0CC47A44B7B2
Got a huge problem with a AT&T phone Samsung Galaxy Note 4. Got it from an ebay handler. It was supposed to be rooted. However, after installing Magisk software (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I got the message "System software not authorized by ATT has been found on your phone". Whenever I turn it on, I see it and the phone doesn't start. Since more than 6 months have passed, the ebay handler declined to help. I called AT&T, but since the phone is rooted, they declined to repair it even after I offered to pay. There are some solutions I found online for other samsung galaxy models, but none which works for note 4.
Tried to restore the system to the factory version, it said that restoration has been successful, but I still see the AT&T message.
I followed the instructions to unbrick the phone by reinstalling the firmware - the method that should work for all phones (not just note 3) https://www.youtube.com/watch?v=bv_NCfYemEs with the firmware for SM-N910A , however no matter how long I waited, the download process never completed.
Any suggestions?
Thanks!
vmmessage said:
Got a huge problem with a AT&T phone Samsung Galaxy Note 4. Got it from an ebay handler. It was supposed to be rooted. However, after installing Magisk software (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I got the message "System software not authorized by ATT has been found on your phone". Whenever I turn it on, I see it and the phone doesn't start. Since more than 6 months have passed, the ebay handler declined to help. I called AT&T, but since the phone is rooted, they declined to repair it even after I offered to pay. There are some solutions I found online for other samsung galaxy models, but none which works for note 4.
Tried to restore the system to the factory version, it said that restoration has been successful, but I still see the AT&T message.
I followed the instructions to unbrick the phone by reinstalling the firmware - the method that should work for all phones (not just note 3) https://www.youtube.com/watch?v=bv_NCfYemEs with the firmware for SM-N910A , however no matter how long I waited, the download process never completed.
Any suggestions?
Thanks!
Click to expand...
Click to collapse
Grab latest firmware for N910A from here
https://androidfilehost.com/?fid=745425885120746376
Make sure samsung usb drivers are properly installed on your pc before you begin.
STEPS
1 Download odin and Firmware and Extract it.
2 open odin tool and upload firmware in AP slot.
Odin can take up to 5 minutes to upload firmware so be patient
3 put phone into download mode
4 connect phone via usb cable and hit start.
5 After FLASH once odin shows pass boot into stock recovery by pressing 3 button combo volume up+ home+ power.
6 in recovery do wipe cache+ wipe data factory reset.
7 reboot system and wait 10 to 5 minutes.
DONE
Trex888 method should be good, however you may need to find the pit file and flash it before odin back to stock. I bought my note 4 already rooted, but the person that did it used the wrong files to flash. Mine was good but buggy. The rom flashed was not verizon, and it locked out some partitions including the one where the imei was held. I had to fix the partitions with the pit file then reflash to a different rom and i was good to go after that.
Thanks
Thanks for the reply! Great! I will try that - very hopeful
tattmann said:
Trex888 method should be good, however you may need to find the pit file and flash it before odin back to stock. I bought my note 4 already rooted, but the person that did it used the wrong files to flash. Mine was good but buggy. The rom flashed was not verizon, and it locked out some partitions including the one where the imei was held. I had to fix the partitions with the pit file then reflash to a different rom and i was good to go after that.
Click to expand...
Click to collapse
You dont need dedicated pit file unless your device has errors such as "dm verity verification failed" or failed to mount cache/efs etc etc.
If stock rom flashing by odin went smoothly no require for repartition or pit file.
Playing with pit file and repartition is extremely dangerous and can cause device to hard brick so i would not recommend unless some serious issues with device.
Fyi every samsung stock firmware has pit file in the system image by default and odin take advantage of it by it self during flashing.
Have a nice day.
Trex888 said:
You dont need dedicated pit file unless your device has errors such as "dm verity verification failed" or failed to mount cache/efs etc etc.
If stock rom flashing by odin went smoothly no require for repartition or pit file.
Playing with pit file and repartition is extremely dangerous and can cause device to hard brick so i would not recommend unless some serious issues with device.
Fyi every samsung stock firmware has pit file in the system image by default and odin take advantage of it by it self during flashing.
Have a nice day.
Click to expand...
Click to collapse
in my case, whoever flashed my phone flashed an f file instead of the v file. It lost the imei and would not recognize a sim card. I tried flashing original firmware but the imei was still gone. The ONLY thing that saved mine was to find the correct pit file and flash it before firmware. It fixed my issue and got me back up and running. every original fw flash for me failed until I flashed just the pit. I cannot explain why the original fw included in the odin package would NOT work. Hence the statement of "you may need to" instead of "you will have to".