Related
Hello everyone! My names Danny, sorry I'm extremely frustrated at the moment and apologize for not introducing myself properly in what ever you call your newcomer section here, but I'm ripping my hair out at the moment.
So last night for the 4th time I tried to root my Galaxy S4, again unsuccessfully. While I admit I am no programmer, computer whiz, or rocket scientist, I have previously rooted my old S3 and my girlfriend's Moto Photon successfully in the past, on the 1st try (although they were pretty simple 1 click roots no more difficult than the one I used here, or so I thought.) Now last night I tried to use the CF-Autoroot again for the 3rd time, which i figured after the first 2 attempts was doomed to failure also. This may be due to the fact that I updated it, but I don't know. I'm hoping someone here can point me in the direction of a root that will work with my phone, show me where I may have went wrong in the install,or give some instruction on how to delete the update so I can use the CF-Autoroot. As long as my phone will still function as normal, I could care less which option is used, however I do not have any programming experience whatsoever, so a simpler root would be excellent. I'll give you all the info I can below.
Software version: L720VPUAMF9
Hardware version: L720.08
Model #: SPH-L720
Android version: 4.2.2
Baseband version: L720PUAMF9
Kernal version: 3.4.0-953334
[email protected] # 1
Tue Jun 25 09:36:29 KST 2013
Build #: JDQ39.L720VPUAMF9
SE Linux Status: Permissive
Secure boot status: Type: Samsung
Device Status: Custom (No Triangle Away quite yet, as I'm not sure if it is yet supported on the S4, or if I even need it since I plan on keeping the phone)
Root was done on HP Windows 7 laptop 64-bit, with the phone in camera mode prior to turning off and going into download mode.
I followed the instructions on honai-android.blogspot(dotcom) using CF-Autoroot and Odin V3.07 to the T, except I have yet to get the drivers to install correctly (or so it tells me, everything works fine,) and in Step 4 it says the box should turn yellow and a port number displays, but in my case did not. It did display the "Added" message in the little box like it should have, but it did go through the whole process and I got a PASS notification as it says I should have. I have no idea why it won't work, other than maybe the drivers are screwing me. Ran Root Checker and it tells me "Please wait for Root Check to complete. System appears to be running very slow," and Titanium Backup won't work either. Root checker stayed like this all night last night while I slept.
Also I would appreciate some help reverting it back from the root I apparently didn't install, although I know some of it went through, or Root Checker would just say I didn't have superuser access.
I'm hoping one of you guys here might be able to help me out with this problem, and I greatly appreciate any help I can get. If anymore information is needed, just ask. Much thanks in advance.
You said you used Odin in camera mode? Did you mean download mode? I didn't have to install any drivers to get Odin to work. If you didn't get a yellow box with a com number in it the Odin didn't write anything to your phone. If you look here in the dev section there is a thread titled cf auto root. Download the zip file there and follow those directions and give it another try.
SGS4 Sent
ifly4vamerica said:
You said you used Odin in camera mode? Did you mean download mode? I didn't have to install any drivers to get Odin to work. If you didn't get a yellow box with a com number in it the Odin didn't write anything to your phone. If you look here in the dev section there is a thread titled cf auto root. Download the zip file there and follow those directions and give it another try.
SGS4 Sent
Click to expand...
Click to collapse
No my S4 was in camera mode. There are 2 options when I plug my phone in via USB to the PC, either camera mode or media device mode, PTP and MTP respectively. This is how it was set up before I turned the phone off to go into download mode, didn't think it made a difference, but I wanted to give as much info as possible. The phone went through all the downloading stuff on-screen with the red pirate android guy and everything while Odin was downloading to the phone, and Odin also said Added in the message box so I figure Odin recognized the device was present. I'll check out that thread though, thank you:good: I'll be back here if it doesn't rectify the situation.
I see my first problem, stupid tutorial I used the first time said to put Odin in Repartition and F-Reboot. QBKing says only Autoreboot. Man I hate crappily done tutorials.
Just also noticed he mentions the yellow box and com/port number are vital to the success of the root, something I overlooked all 3 times I tried it.
Stuck at the stupid com box again, now it wont change at all and i'm not getting the added message either....
Downloaded the drivers for the phone he gave also and still nothing....tried 3 different USB cables like he suggested too and still stuck.
Think I might need to unroot or delete the other crap I installed before? I'm out of ideas.
pumpdatbass420 said:
Stuck at the stupid com box again, now it wont change at all and i'm not getting the added message either....
Downloaded the drivers for the phone he gave also and still nothing....tried 3 different USB cables like he suggested too and still stuck.
Think I might need to unroot or delete the other crap I installed before? I'm out of ideas.
Click to expand...
Click to collapse
ok try this from the beginning
1. reset phone factory reset via recovery ( hold power up - home - and power button ) simultaneously and once you see blue recovery text top left corner let all the buttons go. select factory reset and proceed with reboot.
2. press ##3424# and select pda and make sure you have MTP-ADB selected
3. try rooting your phone via ODIN
PS: if it does not work change step 2 under PDA setting to DM-MODEM-ADB then root and once rooted change it back to step MTP-ADB
let us know if this works for you
saj070 said:
ok try this from the beginning
1. reset phone factory reset via recovery ( hold power up - home - and power button ) simultaneously and once you see blue recovery text top left corner let all the buttons go. select factory reset and proceed with reboot.
2. press ##3424# and select pda and make sure you have MTP-ADB selected
3. try rooting your phone via ODIN
PS: if it does not work change step 2 under PDA setting to DM-MODEM-ADB then root and once rooted change it back to step MTP-ADB
let us know if this works for you
Click to expand...
Click to collapse
Step 2...am I doing this on the phone or in Odin? MTP-ADB as well?
pumpdatbass420 said:
Step 2...am I doing this on the phone or in Odin? MTP-ADB as well?
Click to expand...
Click to collapse
step 2 is open dialer on the phone - how else you going to press ##3424#
i thought that was a given sorry
It's cool, I ask just in case. While I do consider myself a bright individual, I do not know very much about newer cell phones or android (this is only my 2nd smart phone, before the Photon I had been using my Blackjack without net. That phone lasted forever!) And before the Photon had never modded any cell phone in any way save an extended battery.
pumpdatbass420 said:
It's cool, I ask just in case. While I do consider myself a bright individual, I do not know very much about newer cell phones or android (this is only my 2nd smart phone, before the Photon I had been using my Blackjack without net. That phone lasted forever!) And before the Photon had never modded any cell phone in any way save an extended battery.
Click to expand...
Click to collapse
no problem better be safe than sorry ')
let us know how it went.
It's aliiiiiiive
Ok so oddly enough, after I performed steps 1 & 2, when I rebooted my phone I notice SuperSU was in my apps list. So for $#*^$ and giggles I downloaded Root checker to test it out and sure enough it says device is rooted. Go figure.
Thanks so much for your help guys, my girlfriend was starting to worry about me out here smashing keys and grunting like an animal trying to get this to work. :highfive:
pumpdatbass420 said:
Hello everyone! My names Danny, sorry I'm extremely frustrated at the moment and apologize for not introducing myself properly in what ever you call your newcomer section here, but I'm ripping my hair out at the moment.
So last night for the 4th time I tried to root my Galaxy S4, again unsuccessfully. While I admit I am no programmer, computer whiz, or rocket scientist, I have previously rooted my old S3 and my girlfriend's Moto Photon successfully in the past, on the 1st try (although they were pretty simple 1 click roots no more difficult than the one I used here, or so I thought.) Now last night I tried to use the CF-Autoroot again for the 3rd time, which i figured after the first 2 attempts was doomed to failure also. This may be due to the fact that I updated it, but I don't know. I'm hoping someone here can point me in the direction of a root that will work with my phone, show me where I may have went wrong in the install,or give some instruction on how to delete the update so I can use the CF-Autoroot. As long as my phone will still function as normal, I could care less which option is used, however I do not have any programming experience whatsoever, so a simpler root would be excellent. I'll give you all the info I can below.
Software version: L720VPUAMF9
Hardware version: L720.08
Model #: SPH-L720
Android version: 4.2.2
Baseband version: L720PUAMF9
Kernal version: 3.4.0-953334
[email protected] # 1
Tue Jun 25 09:36:29 KST 2013
Build #: JDQ39.L720VPUAMF9
SE Linux Status: Permissive
Secure boot status: Type: Samsung
Device Status: Custom (No Triangle Away quite yet, as I'm not sure if it is yet supported on the S4, or if I even need it since I plan on keeping the phone)
Root was done on HP Windows 7 laptop 64-bit, with the phone in camera mode prior to turning off and going into download mode.
I followed the instructions on honai-android.blogspot(dotcom) using CF-Autoroot and Odin V3.07 to the T, except I have yet to get the drivers to install correctly (or so it tells me, everything works fine,) and in Step 4 it says the box should turn yellow and a port number displays, but in my case did not. It did display the "Added" message in the little box like it should have, but it did go through the whole process and I got a PASS notification as it says I should have. I have no idea why it won't work, other than maybe the drivers are screwing me. Ran Root Checker and it tells me "Please wait for Root Check to complete. System appears to be running very slow," and Titanium Backup won't work either. Root checker stayed like this all night last night while I slept.
Also I would appreciate some help reverting it back from the root I apparently didn't install, although I know some of it went through, or Root Checker would just say I didn't have superuser access.
I'm hoping one of you guys here might be able to help me out with this problem, and I greatly appreciate any help I can get. If anymore information is needed, just ask. Much thanks in advance.
Click to expand...
Click to collapse
try doomlord easy root
Thanks for the tip but I already got it rooted. Just took a few more steps than I thought due to some overlooked details with the initial install.
New problem!
Trying to get QBKings Native Hotspot mod to work and it wont let me transfer services.odex to the system folder but services.jar is transferring fine? Any ideas? I'm baffled here yet again. Tried 3 different root browsers but JUST services.odex wont transfer!!!!!
Sorry for joining late, but how are you transferring the file? ADB, SD?
Hello, everybody.
First I'd like to thank xda for existing and providing for such a great place for customization of phones, getting information and giving great tools.
Now, I'm a complete and utter newbie when it comes to this, this is my first android device ever and I haven't bothered doing any customization with phones ever since I retired my old Motorolla a925 in 2007 or so.
So I'm trying to be really cautious when installing a new ROM and have some questions:
First one is concerning TWRP. I cannot install it. I downloaded Goomanager like I was told, pushed the 'install OpenRecoveryScript' but it says that "No recoveries were found for your device". I suspect this is because the phone I bought was already rooted. My friends visited Dubai previous week and brought it for me from there.
If this helps, my build is N9005XXUMBMI7. Also, I cannot update my device because "Your device has been modified. Software updates are not available."
Do I have to install updates and TWRP manually or change my build?
Second, what kind of ROM would you guys suggest? What are the most popular ones?
There are so many of them and since I'm so new about all of this I have barely any idea how they differ from one another. Someone told me that Cyogenmod is really great for Android devices and suggested Slim Bean but after searching a bit on the net it seems that they are not available for Note 3. Does anyone know if they are developing them for Note 3 yet and when they will be available?
My personal criteria for custom ROMs go like this: improving the performance and batter as much as possible. Removing as much as possible of bloatware, freeing up as much as possible space.
Third,
reading the installation guides I'm not certain if when I'm installing a custom ROM should I keep the ROM files on the computer, connect the phone and then install. Or should I put the files in the internal memory? Or do I put them on the SD card, put the SD card into the phone and install from there?
Thanks for reading this, I apologize if I made an impasse. I tried to search a little bit but couldn't find answers.
DkayBlack said:
Hello, everybody.
First I'd like to thank xda for existing and providing for such a great place for customization of phones, getting information and giving great tools.
Now, I'm a complete and utter newbie when it comes to this, this is my first android device ever and I haven't bothered doing any customization with phones ever since I retired my old Motorolla a925 in 2007 or so.
So I'm trying to be really cautious when installing a new ROM and have some questions:
First one is concerning TWRP. I cannot install it. I downloaded Goomanager like I was told, pushed the 'install OpenRecoveryScript' but it says that "No recoveries were found for your device". I suspect this is because the phone I bought was already rooted. My friends visited Dubai previous week and brought it for me from there.
If this helps, my build is N9005XXUMBMI7. Also, I cannot update my device because "Your device has been modified. Software updates are not available."
Do I have to install updates and TWRP manually or change my build?
Second, what kind of ROM would you guys suggest? What are the most popular ones?
There are so many of them and since I'm so new about all of this I have barely any idea how they differ from one another. Someone told me that Cyogenmod is really great for Android devices and suggested Slim Bean but after searching a bit on the net it seems that they are not available for Note 3. Does anyone know if they are developing them for Note 3 yet and when they will be available?
My personal criteria for custom ROMs go like this: improving the performance and batter as much as possible. Removing as much as possible of bloatware, freeing up as much as possible space.
Third,
reading the installation guides I'm not certain if when I'm installing a custom ROM should I keep the ROM files on the computer, connect the phone and then install. Or should I put the files in the internal memory? Or do I put them on the SD card, put the SD card into the phone and install from there?
Thanks for reading this, I apologize if I made an impasse. I tried to search a little bit but couldn't find answers.
Click to expand...
Click to collapse
First your device must be rooted. to check if it is rooted get Root checker from playstore and run it. Go to main page of TWRP, search for your device ie Samsung galaxy Note 3, choose your device code ie International hlte or whatever your device code may be. Click it then go down the list of servers to download the file to your computer. once the file has been downloaded, use Odin to flash it under PDA then reboot.
After you have Custom Recovery installed, you can Flash any ROM written for your device model ie N9005 or N900 etc...To flash ROMs you need to have the ROM zip file in either your internal storage or your external SD Card. I most of the time download them straight into my my SD Card to save myself from transferring the file from my computer to my phone.
Good luck.
doodydood said:
First your device must be rooted. to check if it is rooted get Root checker from playstore and run it. Go to main page of TWRP, search for your device ie Samsung galaxy Note 3, choose your device code ie International hlte or whatever your device code may be. Click it then go down the list of servers to download the file to your computer. once the file has been downloaded, use Odin to flash it under PDA then reboot.
After you have Custom Recovery installed, you can Flash any ROM written for your device model ie N9005 or N900 etc...To flash ROMs you need to have the ROM zip file in either your internal storage or your external SD Card. I most of the time download them straight into my my SD Card to save myself from transferring the file from my computer to my phone.
Good luck.
Click to expand...
Click to collapse
Thanks.
My device is definately rooted. I didn't root it myself though. I checked with the rootchecker and even have few apps istalled which need root, like
Adaway.
The TWRP installation through Goomanager seemed to be the most retard-proof so I'm concerned that if I get error messages doing it that way there might be something wrong with my phone so I didn't try other methods (even though I was aware of them)
To clarify, 'External SD card' is the normal card which you can put in and out of the phone (like SIM)? Because when I heard 'external' I tend to think about something that is outside the phone connected by usb.
Ok guys, can someone explain me how to use Odin? Assume that I'm a complete retard.
What version do I use for Note 3 n9005? I searched around but couldn't find any versions that explicitly said that they are compatible with my phone. I am talking about the desktop version of course not the mobile one.
How do I use it? Could I get step by step instructions, please? I downloaded the TWRP file from their site, now what?
There are guides and videos on the net and I watched/read some of them but none for my device. I am (understandably) nervous about my very first attempt at installing a custom ROM. Don't want to turn my expensive phone into a brick. Still, I'm willing to take chances to remove all the bloatware and improve the battery life.
Also could I get answers for my previous questions about ROMs?
Use mobile odin pro. Purchase if needed. Its all you need for flashing. Didnt look at pc eversince. Anyway back to topic. Download .tar file for twrp for ur phone model. Open mobile odin. Download whatever needed by mobile odin. Load the twrp recovery.tar file and flash away.
Sent from my SM-N9005 using Tapatalk
hayabusa08 said:
Use mobile odin pro. Purchase if needed. Its all you need for flashing. Didnt look at pc eversince. Anyway back to topic. Download .tar file for twrp for ur phone model. Open mobile odin. Download whatever needed by mobile odin. Load the twrp recovery.tar file and flash away.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I was hoping on doing this without using any money. Is doing it with the mobile version the safest method? If it is really much safer than other variants, I'll spend some money just for that.
DkayBlack said:
I was hoping on doing this without using any money. Is doing it with the mobile version the safest method? If it is really much safer than other variants, I'll spend some money just for that.
Click to expand...
Click to collapse
here you are have a look and all will come clear
http://www.youtube.com/watch?v=dcWkKuU9Fyo
I have a brand new sprint samsung galaxy s4 and would like to do an one click odin root but every link on this site doesnt work to download odin 1.85 they all popup with the odin and Japanese in a popup after unzipping????? Can I get a working Odin 1.85 link and the correct tar file download so I can root my phone. PLEASE I would prefer to do the same as I did with my s2 and do a CWM and use SuperSU but use odin to do my rooting. Am I missing something here with rooting my phone? Im a NOOB so I would greatly appreciate someone to give me the easiest instructions on how to root my phone where Ill have a custom recovery just like the old school odin one click for the sprint galaxy s2 epic touch. I don't wanna mess up my brand new phone but loved the rooting rights I had with my old s2 but with being able to have the benefits of the new kitkat version. Anyones expert help would be greatly appreciated!!!!
Look for CF-AutoRoot (ChainFire) http://forum.xda-developers.com/showthread.php?t=2257101
Sent from my Nexus 7 using XDA Free mobile app
hey buddy this site relies heavily on its users doing their own research, you are unlikely to find many helpful replies to this question since it is very well documented if you use the search function...or google. Or just even browse through the threads a bit. But I'll throw you a bone.
1. Download Chainfire's CFautoroot. Thanks chainfire! He conveniently includes a compatible version of odin in the zip (v3.07 if I'm not mistaken).
2. Extract the zip, and run odin.
3. Press the PDA button and select the CF-Auto-Root-jfltespr-jfltespr-sphl720.tar that was extracted from chainfire's zip.
4. Completely power off your phone. If you are unsure if it is completely off, pull the battery. Press and hold the power button and vol down until it boots into download mode. Press vol up to continue.
5. Connect your phone via usb to your computer.
6. Make sure odin recognizes your phone (one of the little boxes should read com x, where x is a number. it was com4 for me). if it doesn't you will need to install the samsung mobile phone drivers. if you plugged your phone into your computer since you've had it, you likely have these drivers installed already.
7. Press start.
8. Profit! You are now probably rooted. or your phone is bricked. ha just kidding - but please research a little next time before you ask a question
PS - this voids your warranty. also you should go click on some ads in chainfire's website.
I can't seem to figure out how to downgrade back to a stock ROM after installing this:
lineage-14.1-20170331-UNOFFICIAL-trltetmo.zip (can't post link yet)
I believe it's the Nougat 7.1.1
I want to downgrade to 6.0.1 or 5.1.1
One message I see is "Recovery is not Seandroid Enforcing". Seems like all fixes suggest reinstalling stock ROM, which I'm trying to do, but can't.
Phone is a Samsung Note 4 SM-N910W8 (Rogers)
What's your steps to downgrade to 6.0.1? Did you download Rogers ROM and ODIN it(google is your best friend)?
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
If ODIN starts and stops immediately, you have a different problem. Did you install the Samsung Android USB driver properly. Anyway, you have a software issue, fix it first. I suggest you watch a few related video on youtube.
ziggy1971 said:
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
Click to expand...
Click to collapse
Currently no response.
In the freezer... I'm waiting.
Not sure which I should follow first:
Debrick here: https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
or
The following from https://forum.xda-developers.com/showpost.php?p=72338162&postcount=2622
SUREFACE said:
It Sounds that You have a "FULL BRICK" !
The Only way, that REALY can Help is a "USB-JIG".
And Hope, that this One Brings Your Device back in Download-Mode!
You can Build Your Own One, see here : https://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707
Or Buy One! See Here: https://www.amazon.de/Download-Repair-Stecker-Samsung-Galaxy/dp/B004VN5ZYS
And You need a REPAIR ROM ! Take A Look here for Your Variant : https://mega.nz/#F!Ax0gxSzZ!Qq_eJWX678bQHBhn7BHNDQ
Hope that this will Work!
Click to expand...
Click to collapse
Since yesterday I did the following:
- reset my system with a backup image (Bare Metal Restore with True Image) I only have some basic software installed.
- downloaded and installed SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0
Is your phone booting up and functioning? If it is, why are you talking about debrick? I'm assuming that you're "new" to all this. I suggest you read up(especially the stickies) and be comfortable before you go further.
ziggy1971 said:
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
Click to expand...
Click to collapse
ziggy1971 said:
Not sure which I should follow first:
Debrick here: https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
or
The following from https://forum.xda-developers.com/showpost.php?p=72338162&postcount=2622
Since yesterday I did the following:
- reset my system with a backup image (Bare Metal Restore with True Image) I only have some basic software installed.
- downloaded and installed SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0
Click to expand...
Click to collapse
No, it doesn't boot up at all now.
I know I initially said "I" installed the custom ROM, I didn't, I bought it that way. The previous owner won't do anything to help. The only thing he did was provide a link to the ROM he had installed, nothing more, not even the tutorial related to it, I found that on my own (wait, he's made it more than clear how incompetent/ignorant I am as a person).
I've been searching and reading for 3 days straight now. Getting to the point again where I accept defeat, assume the money lost.
Moving on... I've rooted other phones before without issues.
I follow a tutorial on how to downgrade to a stock ROM.
http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
Odin stops with various errors.
I could still boot device into TWRP-3.1.0
Reflashed LineageOS 14.1 ROM from SD to get it working again.
LineageOS 14.1 ROM would boot up, run for almost a minute and a half and shut down.
Pull battery, reboot into LineageOS 14.1 ROM, same thing.
Run Odin, connect device to computer, try to flash stock ROM, error again (different one). Somehow, it says "There is no PIT partition"
I followed this tutorial: https://forum.xda-developers.com/no...te-4-pit-files-repartiton-f-g-c-t-w8-t3282641
Odin says FAIL.
Now, it does NOTHING.
I follow this tutorial: Debrick here: https://forum.xda-developers.com/not...k-img-t3488114
Yes, the whole freezer thing overnight.
I have the latest USB drivers installed.
When I connected to the PC, an error popped up saying "...drivers not installed properly..." so I let Windows Update install the correct drivers.
I can connect to the PC now, press the power button for more than 10 seconds, eventually a popup message says "USB Device Not Recognized by Windows"
I've tried the following stock ROMs, 4.4.4, 5.1.1. I finally managed to download 6.0.1, but haven't been able to try it.
All I can say is that if you can boot into TWRP(I assumed you install the N910T version), then your phone is not bricked. All these "debricking" you're doing is potentially harming than fixing.
You assume the risk, when you buy 2nd hand. But based on what you're saying, it sounds like it may also have hardware issues(I don't think software will fix). Was it working when you got it? If you can return it, I suggest you do.
Another pc or windows version may work
A more trustworthy guide on using ODIN:
http://forums.androidcentral.com/am...w-flash-stock-rom-via-odin-new-interface.html
mnopy said:
Another pc or windows version may work
Click to expand...
Click to collapse
I will try with another PC, two batteries, different USB cables, different versions of the USB drivers, and so on.
Anything I missed?
ziggy1971 said:
I will try with another PC, two batteries, different USB cables, different versions of the USB drivers, and so on.
Anything I missed?
Click to expand...
Click to collapse
QualcommDrv
this is the Qualcomm Drivers(x86 and x64, choose your system's version and install) .
Without that your pc will not recognize your phone.
Uninstall everything related to samsung from your pc.
Kies, smart link, usb drivers. Use revo-unistaller for this to be sure nothing have left behind.
Go to control panel>system>device manager and remove anything that is related to your phone . If prompt delete drivers associated with that, say yes. Reboot your pc
Have saved QualcommDrv, samsung usb drivers and Odin. These are the tools you are going to need and must have.
after uninstall everything, unzip and install QualcommDrv.
Take off your battery, press power buton for 10 sec . Connect the phone to pc (without battery)
QualcommDrv will install the correct drivers for your phone. After that If in devices and printers it is recognized as Qualcomm 8084 .... its ok to proceed . if not , check again drivers and their installation
If windows says device drivers are not correctly installed and prompt to download and install, stop and cancel it.
IT will replace the QualcommDrv and you will not be able to see your phone correctly.
You need to keep QualcommDrv installed. When this is done and you are sure its correct and working, unplug your phone and install Samsung usb drivers. Reboot pc
unzip odin in desktop (or where ever its easy to access).
with your phone freezed and battery charged try to go to download mode. If succeed, connect to pc and with odin try to flash stock rom. If not ......
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
That what you need to have correct and working in order to START. THIS IS ONLY THE FIRST STEP
YOU HAVE TO UNDERSTAND
this is a hardware failure of the motherboard and will never will be completely fixed. These steps will only help you resurrect your phone and maybe give you the chance to be able to use it again.
It has nothing to do with software that failed to install. It was just the result and not the real problem, which is a diffect motherboard like thousand others. Sadly this is a common problem with Note 4 that happened to many users.
I have the same problem and I also bought it second hand knowing its problematic but not how much.
After that I realized the problem and the solutions to it. Every one of us is having a slightly different behavior of the phone.
I, for example cannt use the phone without the ext sdcard with unbrick image in it. When I take it out phone, will not start, reboot , do nothing.With the card in it its working almost perfect.
So have patience and read and search to know what you are dealing with.
Good luck
I managed to revive the Note 4 using a stock ROM.
Now, I have more questions like;
- Is this a problem on ALL models of the Note 4 or is it limited to a certain model?
ziggy1971 said:
I managed to revive the Note 4 using a stock ROM.
Now, I have more questions like;
- Is this a problem on ALL models of the Note 4 or is it limited to a certain model?
Click to expand...
Click to collapse
I don't believe you truly downgraded. I'm assuming you were on a 6.0.1 bootloader running a compiled 7.1.1 ROM. It probably hosed some partitions, and other things. Flashing the Stock ROM normalized it.
Most of time flashing a stock touchwiz rom will fix the "damage" that results in flashing a CM ROM.
dicksteele said:
I don't believe you truly downgraded. I'm assuming you were on a 6.0.1 bootloader running a compiled 7.1.1 ROM. It probably hosed some partitions, and other things. Flashing the Stock ROM normalized it.
Most of time flashing a stock touchwiz rom will fix the "damage" that results in flashing a CM ROM.
Click to expand...
Click to collapse
I have no idea what kernel, bootloader, etc. were/are used in the LineageOS ROM.
What I'd like to do is take a stock ROM and remove the unnecessary BLOATWARE and keep all the rest as it is.
Personal blurb: Why can't OS makers simply do that, make an OS!!! Windows, Android, it really doesn't matter, they're all the same.
ziggy1971 said:
I have no idea what kernel, bootloader, etc. were/are used in the LineageOS ROM.
What I'd like to do is take a stock ROM and remove the unnecessary BLOATWARE and keep all the rest as it is.
Personal blurb: Why can't OS makers simply do that, make an OS!!! Windows, Android, it really doesn't matter, they're all the same.
Click to expand...
Click to collapse
There is nothing stopping you from doing that but you.
Don't waste your breath saying I don't know how. There are TONS of guides on XDA.
That's exactly how I started learning. With that desire.
And here's what was most likely on it
https://forum.xda-developers.com/note-4/orig-development/rom-cyanogenmod-14-1-t3506613
dicksteele said:
There is nothing stopping you from doing that but you.
Don't waste your breath saying I don't know how. There are TONS of guides on XDA.
That's exactly how I started learning. With that desire.
And here's what was most likely on it
https://forum.xda-developers.com/note-4/orig-development/rom-cyanogenmod-14-1-t3506613
Click to expand...
Click to collapse
"I don't know how" generally isn't in my vocabulary. It's more like, where do I start, what do I need, where's a good tutorial explaining the what, how, and why of doing things.
Do I need to go all the way into the Java source code or are there other ways of removing some of the built-in apps?
Any tutorial/info suggestions are more than welcome. I'm not that familiar with the lingo of ROM customizing, so my searches are pretty much limited to that; "Android ROM customizing" is about the jist of it right now.
ziggy1971 said:
"I don't know how" generally isn't in my vocabulary. It's more like, where do I start, what do I need, where's a good tutorial explaining the what, how, and why of doing things.
Do I need to go all the way into the Java source code or are there other ways of removing some of the built-in apps?
Any tutorial/info suggestions are more than welcome. I'm not that familiar with the lingo of ROM customizing, so my searches are pretty much limited to that; "Android ROM customizing" is about the jist of it right now.
Click to expand...
Click to collapse
take a look here,
https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885
here:
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and here:
https://forum.xda-developers.com/showthread.php?t=2467004
and maybe here:
https://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
I cannt built but I can test, so go for it and tell us if we can help in the next step
logosA said:
take a look here,
https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885
here:
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and here:
https://forum.xda-developers.com/showthread.php?t=2467004
and maybe here:
https://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
I cannt built but I can test, so go for it and tell us if we can help in the next step
Click to expand...
Click to collapse
Those are good.
Some more are here
https://forum.xda-developers.com/general/xda-university
https://forum.xda-developers.com/chef-central/android
https://forum.xda-developers.com/showthread.php?t=1272270
https://forum.xda-developers.com/showthread.php?t=2069130
https://forum.xda-developers.com/showpost.php?p=5626301&postcount=4
https://forum.xda-developers.com/showthread.php?t=1590192
https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
There are essentially two ways to do what you want.
Use the unpack tool above, extract the system.img from a Stock ROM
https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
I get my stock ROMs from here
http://updato.com/firmware-archive-select-model?q=n910c&rpp=15&order=date&dir=desc
Remove the bloatware or apps you don't want.
Use the app same app that you used to extract the system.img to repack it.
Use the https://forum.xda-developers.com/chef-central/android/tool-afaneh-tar-kitchen-t3603649
to build a tar and flash with ODIN.
Second option use a kitchen. I'm testing the one below today to see if it works.
https://forum.xda-developers.com/ch...0-0-deluxe-kitchen-graphic-interface-t3579100
SuperR works great. But you need a Linux environment to run it.
I use virtualbox on my Win10 machine. I use premade images from here
http://www.osboxes.org/virtualbox-images/
Personally I use the Ultimate Edition.
Or use cygwin. I gave you plenty of links to learn how that works. It's a pain that's why I use virtualbox.
Hi All
Looking for a best tutorial to follow and the right one for my phone really don't want to brick it, obviously :/. as there seems to be a few versions for the S7
I have the following: S7 android 8.0.0 SM-G930F not sure what else I need to know! I'm in the UK so I assume UK phones come with Exynos cpu's
and as far as I am aware android 8 is Oreo! but when they say Stock Rom I assume they mean the same as what came with the phone the original rom?
if so is there an alternative stable rom without the crap included or is it just as simple to delete every thing you don't want now it's rooted! and does that mean if I reset the phone its back to normal with all the crap included! or is there a way to keep it rooted even after reset! and should anything be disabled I.e prepare the phone before attempting to root like any kind of auto encryption that needs disabling and just one more question
if at anytime the rooting process hangs for a ridiculous amount of time when should I throw in the towel! and what are the chances of retrieving the phone back to original state! or does a dirty shutdown brick it?.
I started the root process but failed at first hurdle!, followed instructions install Odin3_v3.13.1 but when I connected the phone nothing showed up in Odin? though I will have another go just to confirm I followed it correctly, I'll update this when it's done.
this was the tutorial I followed:
Easy 4 Newbie [Root Guide]SM-G930F, G935F, G930FD, G935FD (Samsung Galaxy S7 Edge)
Warning ! Please note that the official TWRP for Nougat on Galaxy S7/ S7 Edge is not available yet but based on my experience the Marshmallow version is working on Nougat. By installing a custom recovery on your S7 and S7 Edge and rooting it...
forum.xda-developers.com
I know alot of questions I would really appreciate any help and clarification on the above.
many thanks
Regards
Daz
Look pal, rooting the phone is just like being an adult, it means you will get rid of Samsung's "Child Care".
Yes, UK models use Exynos chip, but you have to be sure, look at your baseband version, if it is G930FXXX, then you are good.
ROMs are in two shapes:
Stock-based: These are just like the one you are using, or other Samsung phones does, like Samsung Experience, One UI, TouchWiz. Maybe MIUI and FlymeOS will come into account, as there are ROMs based on them + Samsung's.
AOSP: These are pure Android ROMs, with few modifications to the core, but keeping the UI as close to the source as possible, Google & OnePlus phones come with a near-to-pure operating systems.
Changing a ROM is not risky, as long as you follow the instructions, without any unaccounted improvising.
Before you install a ROM, read the working and bug list, to make sure you are installing something you have an idea of.
You need to install TWRP recovery (or any other one you like), and format data, in order to be able to travel among ROMs and/or root your device.
Formatting is only required because the phone is forcibly encrypted, and TWRP can not decrypt it, at least not for this device.
Rooting is simply about flashing a 5-MB file, Magisk, then rebooting to system, no need to wipe data.
No need to do any additional steps, unless you are trying to hide root from some apps and/or pass SafetyNet.
Mohamedkam000 said:
Look pal, rooting the phone is just like being an adult, it means you will get rid of Samsung's "Child Care".
Yes, UK models use Exynos chip, but you have to be sure, look at your baseband version, if it is G930FXXX, then you are good.
ROMs are in two shapes:
Stock-based: These are just like the one you are using, or other Samsung phones does, like Samsung Experience, One UI, TouchWiz. Maybe MIUI and FlymeOS will come into account, as there are ROMs based on them + Samsung's.
AOSP: These are pure Android ROMs, with few modifications to the core, but keeping the UI as close to the source as possible, Google & OnePlus phones come with a near-to-pure operating systems.
Changing a ROM is not risky, as long as you follow the instructions, without any unaccounted improvising.
Before you install a ROM, read the working and bug list, to make sure you are installing something you have an idea of.
You need to install TWRP recovery (or any other one you like), and format data, in order to be able to travel among ROMs and/or root your device.
Formatting is only required because the phone is forcibly encrypted, and TWRP can not decrypt it, at least not for this device.
Rooting is simply about flashing a 5-MB file, Magisk, then rebooting to system, no need to wipe data.
No need to do any additional steps, unless you are trying to hide root from some apps and/or pass SafetyNet.
Click to expand...
Click to collapse
Hi Mohamedkam000
Thanks for replying. I'm not confused about why I want to root the phone. I'm just trying to understand the inner workings and the risks as I'm not as clued up with phone OS's as I am windows. I don't care about warrantees or hiding the the fact it's rooted I just want a clean rooted phone free of big brother well inside at least I know you will never completely keep them out but making it hard is a start lol.
Thank you very much for all the above especially on clarifying about the roms and the reason TWRP formats due to encryption nice one
My Baseband version slightly different though it's G930FXXU8ETI3 not sure if having a U instead of a third X makes any difference!
and I posted wrong tutorial I'm actually following this one below again not sure if that matters.
Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )
Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1...
forum.xda-developers.com
Again many thanks for clarifying that lot up very informative and much appreciated.
Kind regards
Daz
CitizenSmith said:
Hi Mohamedkam000
Thanks for replying. I'm not confused about why I want to root the phone. I'm just trying to understand the inner workings and the risks as I'm not as clued up with phone OS's as I am windows. I don't care about warrantees or hiding the the fact it's rooted I just want a clean rooted phone free of big brother well inside at least I know you will never completely keep them out but making it hard is a start lol.
Thank you very much for all the above especially on clarifying about the roms and the reason TWRP formats due to encryption nice one
My Baseband version slightly different though it's G930FXXU8ETI3 not sure if having a U instead of a third X makes any difference!
and I posted wrong tutorial I'm actually following this one below again not sure if that matters.
Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )
Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1...
forum.xda-developers.com
Again many thanks for clarifying that lot up very informative and much appreciated.
Kind regards
Daz
Click to expand...
Click to collapse
It doesn't matter which version of Android you are using, root is the same.
However, on stock ROMs, it might sometimes get rough, as you may end up with Wi-Fi not working (happened to me Q1 2020).
If you really want to learn how Android OS works, then rooting the stock ROM is not your way.
Try AOSP ROMs, preferably start with Oreo ones, you can root in 3 common way, LineageOS SU Add-on, Magisk, Super SU.
But before you tickle your phone, you have to make a backup of your current device, of every partition, EFS is the most important partition, so make sure it is safe.
Baseband version doesn't matter a lot, unless you're paranoid with updates, it is sorted alphabetically, each string on its own.
The phone is more similar to a linux machine than to a Windows PC.
Edit: To root stock ROM, you have to flash dm verity, so you don't end up encrypted again.
Mohamedkam000 said:
It doesn't matter which version of Android you are using, root is the same.
However, on stock ROMs, it might sometimes get rough, as you may end up with Wi-Fi not working (happened to me Q1 2020).
If you really want to learn how Android OS works, then rooting the stock ROM is not your way.
Try AOSP ROMs, preferably start with Oreo ones, you can root in 3 common way, LineageOS SU Add-on, Magisk, Super SU.
But before you tickle your phone, you have to make a backup of your current device, of every partition, EFS is the most important partition, so make sure it is safe.
Baseband version doesn't matter a lot, unless you're paranoid with updates, it is sorted alphabetically, each string on its own.
The phone is more similar to a linux machine than to a Windows PC.
Edit: To root stock ROM, you have to flash dm verity, so you don't end up encrypted again.
Click to expand...
Click to collapse
Thanks again for clearing quite a few things up I thought rooting stock rom would have been far safer way forward wow how wrong was I! but I guess I am just trying to find any kind simile to windows in any way but as you pointed out again it's more like Linux which again I've only played around with ubuntu and mint for a short period so again not to up on Linux lol.
It's funny I was just reading up on AOSP ROMs then got your message. I see they have a stable but not complete! Android 10 not that I would consider it need as I need a stable OS so Oreo is fine for me.
I have backed up phone using Smart Switch on the PC I assume that copy's every thing that's needed, I reset the phone in anticipation all be it prematurely but at least it restored all my data so if anything that was a good test of the back up at least .
I will have look at some AOSP ROMs and see what's involved there, I'll check out their tutorial hopefully it will include the whole process including root.
I gather by your comment using a AOSP ROM you don't need to use dm-verity or will that still be needed!.
The first thing to do is to flash (install) TWRP, it's a custom recovery (think of it as a mini OS that can boot before Android), that will be the base for any of your future tinkering.
Here is the thread, read the FP carefully: [Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
Once TWRP installed, you can do many things:
Install addons like Magisk. Magisk is the tool you use to obtain root. Forget SuperSU, its outdated, and don't works in modern versions of Android.
Install a custom ROM (this subforum is the perfect place to find them).
Backup & restore an image of your current ROM (very useful).
mooms said:
The first thing to do is to flash (install) TWRP, it's a custom recovery (think of it as a mini OS that can boot before Android), that will be the base for any of your future tinkering.
Here is the thread, read the FP carefully: [Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
Once TWRP installed, you can do many things:
Install addons like Magisk. Magisk is the tool you use to obtain root. Forget SuperSU, its outdated, and don't works in modern versions of Android.
Install a custom ROM (this subforum is the perfect place to find them).
Backup & restore an image of your current ROM (very useful).
Click to expand...
Click to collapse
Thanks Mooms for the input
I tried to follow your links tutorial which he gives three options only one is any good to me and that was installing twrp using Odin but I'm having issues at every turn!. I can't even get Odin to recognise my phone it just wont pick it up I have Samsung driver installed and I have reinstalled many times I found an article claim to have a workaround but that was BS just selling some other app I even change the driver as described on there page,
7 Tips to Fix Odin Not Detecting Phone
Are you using Odin flash tool to flash your Samsung phone but it is not recognized by Odin? Here are 7 tips to fix Odin not detecting phone.
www.imyfone.com
.
but that did nothing so reinstall normal driver again.
feels like it's just not meant to be :/
Thanks again.
CitizenSmith said:
Thanks again for clearing quite a few things up I thought rooting stock rom would have been far safer way forward wow how wrong was I! but I guess I am just trying to find any kind simile to windows in any way but as you pointed out again it's more like Linux which again I've only played around with ubuntu and mint for a short period so again not to up on Linux lol.
It's funny I was just reading up on AOSP ROMs then got your message. I see they have a stable but not complete! Android 10 not that I would consider it need as I need a stable OS so Oreo is fine for me.
I have backed up phone using Smart Switch on the PC I assume that copy's every thing that's needed, I reset the phone in anticipation all be it prematurely but at least it restored all my data so if anything that was a good test of the back up at least .
I will have look at some AOSP ROMs and see what's involved there, I'll check out their tutorial hopefully it will include the whole process including root.
I gather by your comment using a AOSP ROM you don't need to use dm-verity or will that still be needed!.
Click to expand...
Click to collapse
AOSP ROMs are pure, you can't say they are not complete. They are complete, and what OEMs do, like Samsung and Xiaomi is just a customization that you can do, too.
It is preferred that when you take a backup, take it with TWRP, just to ensure you backed up phone's partitions, along with "EFS".
The root procedure on Android 6+ is done by patching the Kernel (boot.img), so unless you take backup of that, you cannot keep root.
There are stable custom ROMs, custom ROMs are meant for custom adjustments, however the stability depends on your phone, and the way you use it, you can compare AOSP vs. Stock and see the difference.
AOSP ROMs doesn't need dm verity, well, at least not if the developer did not mention the encryption part.
Mohamedkam000 said:
AOSP ROMs are pure, you can't say they are not complete. They are complete, and what OEMs do, like Samsung and Xiaomi is just a customization that you can do, too.
It is preferred that when you take a backup, take it with TWRP, just to ensure you backed up phone's partitions, along with "EFS".
The root procedure on Android 6+ is done by patching the Kernel (boot.img), so unless you take backup of that, you cannot keep root.
There are stable custom ROMs, custom ROMs are meant for custom adjustments, however the stability depends on your phone, and the way you use it, you can compare AOSP vs. Stock and see the difference.
AOSP ROMs doesn't need dm verity, well, at least not if the developer did not mention the encryption part.
Click to expand...
Click to collapse
Some of the roms I have looked at mention external touch buttons at bottom of phone do not work or something else in the phone I'm just reading their comments.
I understand about the stock & custom rom's now that's not my problem at least not at the moment as I am miles away from choosing a rom! as I can't even get out the starting gate!. I can not get TWRP on my phone as the only way I can see to get it on a unrooted! phone is to use Odin but as I said Odin doesn't work at least not for me it does not see my phone. I would love to take a back up using twrp but that won't happen until I find a way to get TWRP on a unrooted phone. what crazy paradox is this!. you can't root phone without twrp installed and twrp won't install on a unrooted phone!. that makes perfect sense.
CitizenSmith said:
Some of the roms I have looked at mention external touch buttons at bottom of phone do not work or something else in the phone I'm just reading their comments.
I understand about the stock & custom rom's now that's not my problem at least not at the moment as I am miles away from choosing a rom! as I can't even get out the starting gate!. I can not get TWRP on my phone as the only way I can see to get it on a unrooted! phone is to use Odin but as I said Odin doesn't work at least not for me it does not see my phone. I would love to take a back up using twrp but that won't happen until I find a way to get TWRP on a unrooted phone. what crazy paradox is this!. you can't root phone without twrp installed and twrp won't install on a unrooted phone!. that makes perfect sense.
Click to expand...
Click to collapse
Does your phone allow MTP communication? I mean can you transfer files when the phone is turned on?
Does the phone show any notification about a usb connection?
If not, then you have probably a bad USB cable, at least, or you have a hardware issue that can go as deep as a burned charging port.
If yes, then either your USB cable is not as fast as the phone requires, or you haven't installed the Samsung USB Drivers on your PC.
Unfortunately, you cannot root your device without PC, at least not since Lollipop.
CitizenSmith said:
Thanks Mooms for the input
I tried to follow your links tutorial which he gives three options only one is any good to me and that was installing twrp using Odin but I'm having issues at every turn!. I can't even get Odin to recognise my phone it just wont pick it up I have Samsung driver installed and I have reinstalled many times I found an article claim to have a workaround but that was BS just selling some other app I even change the driver as described on there page,
7 Tips to Fix Odin Not Detecting Phone
Are you using Odin flash tool to flash your Samsung phone but it is not recognized by Odin? Here are 7 tips to fix Odin not detecting phone.
www.imyfone.com
.
but that did nothing so reinstall normal driver again.
feels like it's just not meant to be :/
Thanks again.
Click to expand...
Click to collapse
Which version of Odin are you using ?
Use this version (latest): Odin v3.14.4
Which version of the Samsung USB drivers are you using ?
Use this version (latest): https://developer.samsung.com/mobile/android-usb-driver.html
Mohamedkam000 said:
Does your phone allow MTP communication? I mean can you transfer files when the phone is turned on?
Does the phone show any notification about a usb connection?
If not, then you have probably a bad USB cable, at least, or you have a hardware issue that can go as deep as a burned charging port.
If yes, then either your USB cable is not as fast as the phone requires, or you haven't installed the Samsung USB Drivers on your PC.
Unfortunately, you cannot root your device without PC, at least not since Lollipop.
Click to expand...
Click to collapse
Hi
Yes I can transfer files.
Yes phone asks to allow or block file transfer and it ohone shows up in Devices and Drives list and I can access the phone directory and shows up as Samsung s7 icon.
I will try another USB lead but the one I'm using is new and wasn't cheap but still a possibility I have had leads that weren't suitable for other things I was trying so it is worth a try.
Thanks
mooms said:
Which version of Odin are you using ?
Use this version (latest): Odin v3.14.4
Which version of the Samsung USB drivers are you using ?
Use this version (latest): https://developer.samsung.com/mobile/android-usb-driver.html
Click to expand...
Click to collapse
When I downloaded Odin this was latest one Odin3_v3.13.1 though I have doubts that one version update will fix this issue as I did not see many if any people having my issue so they all used Odin and I believe theirs are fine even with older versions! but as I said Mohamedkam it's worth a try I will down load that version and give it a try.
As for the Samsung usb driver I believe that is where I got mine
SAMSUNG_USB_Driver_for_Mobile_Phones no version visible under properties on file version 1.7.23.0.
The USB connection seems to be fine I have uninstalled then re-download and reinstalled a couple of times.
I can transfer files no problem it shows up as Galaxy S7 Icon with card and phone drive inside.
I'll update shortly thank you.
Update:
I just went to try new Odin and whilst checking my phone have seen I have Offical TWRP app installed? I have no clue as to how that's got in there! as Odin did not show phone so I could select nothing!.
In the phone I open app and if i select backup existing recovery it opens and Select Folder tab and under that Selected Folder: /sdcard Filename: Recovery .img and at the bottom of screen Root access required.
I just hope it's installed correctly!. it is showing in playstore my apps as well just to confirm. if this is now installed what should I do next Now not sure what tutorial to start following.
I am just going to try the new odin and see if it picks up the phone back soon.
OK Seem that it now shows up in the new Odin. at least I think it has! in the log window I see this: <ID:0/004> Added!!
I didn't see that before.
Would be grateful if you could tell me how to proceed from here!
Correct, you don't need he latst version of Odin or the Samsung drivers, bit it was just to be sure.
You need to be in download mode, but before, you must have checked OEM unlock & USB debug in developer options (mandatory).
I've written a tutorial with images here (in French):
Samsung Galaxy S7 (edge) - Mangez un Oreo! [Topic Unique] - Page : 487 - Téléphone Android - Technologies Mobiles - FORUM HardWare.fr
mooms said:
Correct, you don't need he latst version of Odin or the Samsung drivers, bit it was just to be sure.
You need to be in download mode, but before, you must have checked OEM unlock & USB debug in developer options (mandatory).
I've written a tutorial with images here (in French):
Samsung Galaxy S7 (edge) - Mangez un Oreo! [Topic Unique] - Page : 487 - Téléphone Android - Technologies Mobiles - FORUM HardWare.fr
Click to expand...
Click to collapse
As I said the older version did not show any kind of data what's so ever and the phone was in download mode. phone displayed "Downloading" which I believe it says that even if it's not doing anything! so a tutorial explained. I think it must have installed the Official TWRP app even though phone did not show up in Odin everything was blank however when I installed the new version of Odin like you suggested it then showed up as <ID:0/004> Added!!. so your suggestion work thanks for that and I did enable OEM unlock & USB debug I did long time ago.
I would check out your tutorial but unfortunately I don't speak French and translating instructions is too risky but thank you for the offer but I'll carry on look around still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
CitizenSmith said:
As I said the older version did not show any kind of data what's so ever and the phone was in download mode. phone displayed "Downloading" which I believe it says that even if it's not doing anything! so a tutorial explained. I think it must have installed the Official TWRP app even though phone did not show up in Odin everything was blank however when I installed the new version of Odin like you suggested it then showed up as <ID:0/004> Added!!. so your suggestion work thanks for that and I did enable OEM unlock & USB debug I did long time ago.
I would check out your tutorial but unfortunately I don't speak French and translating instructions is too risky but thank you for the offer but I'll carry on look around still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
Click to expand...
Click to collapse
Take a note that, when you flash TWRP, you have to boot immediately to the recovery, so as to enforce its existence, cause I remember they phone has an original recovery backed up somewhere, and gets triggered when you reboot directly to system instead of the unofficial binary.
I advise you to watch guides on YouTube, it's more .. understandable.
CitizenSmith said:
still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
Click to expand...
Click to collapse
I recommend to go with ALEXNDR ROM: zero bugs, everything works perfectly (it's based on stock ROM).
[ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 * Encryption support [Jul-10]
Important notes for Developers / Chefs !!! This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it...
forum.xda-developers.com
Mohamedkam000 said:
Take a note that, when you flash TWRP, you have to boot immediately to the recovery, so as to enforce its existence, cause I remember they phone has an original recovery backed up somewhere, and gets triggered when you reboot directly to system instead of the unofficial binary.
I advise you to watch guides on YouTube, it's more .. understandable.
Click to expand...
Click to collapse
Yer I read that but I've ended up with TWRP installed and did not do that process because I was unaware it installed until it showed up.
As I said I'll just keep looking for now I know I'll find one that works for me from start to finish.
and I've been checking youtube but wouldn't want to use any links their providing but it may help familurise myself with the whole process if i watch enough of them.
Thanks again for your help.
mooms said:
I recommend to go with ALEXNDR ROM: zero bugs, everything works perfectly (it's based on stock ROM).
[ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 * Encryption support [Jul-10]
Important notes for Developers / Chefs !!! This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi Mooms
I will check that out many thanks. I wonder if you could help me here. I am in the middle of the rooting process but have hit a snag. again!
I have now installed TWRP successfully then no-verity-opt-encrypt-3.1 all went fine and I'm at point of flashing Magisk but have an issue when I swipe to flash is gives me a error in red saying "invalid zip file format !"
I downloaded it from github here.
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I click on "code" tab and then "download zip" and I placed that in a download folder on my sd card when I select it I get the above error any ideas as to why I am getting this am I downloaded the correct file?
thanks for any assistance you could give.