Related
ive been testing kernals on my telus fascinate t959d to see if there was any way to get around the no developer issue and came across the love off my live.
the kernels name is "Voodoo-stable-5.0.-Froyo-GT-I9000-odin-pda".
From leaked stock 2.2, i flashed this kernel over the stock through odin. during the initial boot, the female droid voice walked me thru voodoo setup. wait afew minutes after your phone is done loading to allow voodoo to completely enable itself or u will get fc issues. To get to Red clockwork recovery, while your phone is off, hold both volume bottons and the power button. continue holding those 3 buttons until the 2nd i9000 popsup then release all 3 buttons. That should load u into clockwork recovery voodoo. This just basically opened the floodgates for rom testing for me. im running nero v4.1 on my TELUS FASCINATE t959d with no errors at all.
imma upload and post the link
this is the omega leaked 2.2 files in cause u need emergency odin reflash
http://forum.xda-developers.com/showthread.php?t=868829
this is the voodoo enabled kernel
http://rapidshare.com/files/442330146/Voodoo-stable-5.0.1-Froyo-GT-I9000-odin-pda.tar to install this, just download odin, get yout phone into download mode, place the file in the pda slot, and go. i suggest u go back to stock b4 u start for a wiped stock install. if u need help, email me at [email protected] Thx to omega for creating my interest in android custom roms
UPDATE!!!
i just exchanged the previous kernal for a i9000 advanced zoodoo OC/UV and its working mint with nero 4.1. heres the thread to the other kernals
http://forum.xda-developers.com/showthread.php?t=909540
telus fascinate users rejoice!!!!! we r now up to date with everything
after playing around some more ive realized the telus t959d can use most i9000 kernels with no issues. the only 2 issues ive found running advanced voodoo is theres no home button but since i hate having apps running in the background that doesnt bother me and when your phone completely dies, and u plug it in, the battery charge screen gliches out and needs a battery pull. i can easily get around both for the features of a overclocked or undervolted kernel. as far as roms go, most i9000 roms and most vibrant roms work! after i got the rom up and running i just reflashed the proper kernel 4 my phone and the telus modem pulled from omegas leak and bam! ive tested both i9000s darkys v8.0 gingerbread but didnt like the icons for sms and gmail and also nero v4.1 for vibrant with flashed telus modem and i9000 kernel which works mint. running right now. advanced voodoo comes with a custom boot which overwrites the poopy i9000 image and replaces it with a red voodoo anvanced screen. so instead of seeing the sght959d then i9000, it says sgh t959d then advanced voodoo then nexus x boot. looks sweet
Not quite "mint" from your own description.
These are some of the problems I had running kernels / Roms meant for other phones, are you experiencing any of the same?
1- Reversed volume buttons
2- GPS not working (as in won't even start)
3-No FM radio
4- Plugging in the USB cable caused the phone to go into a shutdown/boot loop
GREAT NEWS!!! FINALLY!
Tho.. since Im noob in this world.. Im going to wait a little more until we find suitable (i.e. no homekey error stuff ) and stable!!
Great Great Great GREAT! Thanks LINKSLOVESANDROID!!!!
Please update more and more about your "experiment" Hehehe
daoom said:
Not quite "mint" from your own description.
These are some of the problems I had running kernels / Roms meant for other phones, are you experiencing any of the same?
1- Reversed volume buttons
2- GPS not working (as in won't even start)
3-No FM radio
4- Plugging in the USB cable caused the phone to go into a shutdown/boot loop
Click to expand...
Click to collapse
i had these same issues while running a vibrant kernel. install a i9000 kernel. use 1 of the 1s i packaged in the 1st 2 posts. i flashed a i9000 kernel to get clockwork. then used clockwork to flash nero v4.1 which comes with a vibrant kernel in the rom which automatically overwrites your previous i9000 kernel u flashed b4 hand to get clockwork running. i then used odin to flash a i9000 kernel over the vibrant kernel. Then used the telus modem pulled from omegas 2.2 leAK and flashed that over phone in odin Which left my telus fascinate with the following
-1.3 Ghz Overclock / Undervolted Kernel(Thx U Voltage Control)
-Advanced Voodoo v666.2 i think.... with voodoo sound and advanced voodoo bootscreen
-Nero v4.1 Gingerbread Looks NICE!!!
-working voice calls and text messages
-3d gaming working mint with overclock
-google maps is working properly- navigation seems to not b able to find location thou i didnt wait long and i was indoors
-fm radio is not there because it was not made 4 i9000s just the t959d but isnt a big deal 4 me cause u need to have the headphones that came with the phone hookedup to use as a antenna. if u dont have those exact heapdhones plugged in, the phone says something like please attach headphones for antenna signal." better to just geta internet streaming radio app
- flashing the i9000 kernel solved the following issues
proper volume rockers configuration
and the charging issue. now charging works fine. the only time i had a issue was when i charged my phone while it was turned off and it needed a battery pull. but then i plugged it back in while off and it worked fine.
basically, the only issue i can see being a problem for some is the no home button just 2 back buttons. but honestly, the android os told me to use back more often then home so it saves system ram and doesnt have too much background apps running.
so basically, if your want a custom rom, the only downside is theres no home button and navigation MAY not work.
on the plus side, your phone will become super fast to the point stock rom is slow. ill b posting a video in the coming days of my rom setup from phone startup to shutdown to PROVE this method works
Another user has asked supercurio to make us a custom kernel, supercurio said in his vibrant kernel thread that he would, but that was a couple of days ago. Please post the vid, this intrests me, I can live with the back and home button problems, but am worried about the usb boot loop.
EDIT: I've just flashed the kernel you suggested. Home acts like back, but everything else seems fine so far. I booted into clockwork and enabled voodoo, plus I also O/C to 1200mghz. When I get home i'm going to plug it into usb and see what happens. Hopefully no bootloop!
OK so I have big market place problems, from what I can gather, the phone is recognized by the market as an i9000, which means I can't get some apps that i've had before...everything works but home...just sucks that the market does not work...will try to fix with market enabler...
roccos_van said:
Another user has asked supercurio to make us a custom kernel, supercurio said in his vibrant kernel thread that he would, but that was a couple of days ago. Please post the vid, this intrests me, I can live with the back and home button problems, but am worried about the usb boot loop.
EDIT: I've just flashed the kernel you suggested. Home acts like back, but everything else seems fine so far. I booted into clockwork and enabled voodoo, plus I also O/C to 1200mghz. When I get home i'm going to plug it into usb and see what happens. Hopefully no bootloop!
OK so I have big market place problems, from what I can gather, the phone is recognized by the market as an i9000, which means I can't get some apps that i've had before...everything works but home...just sucks that the market does not work...will try to fix with market enabler...
Click to expand...
Click to collapse
i just noticed it wont lemmie donwload afew games on the market cause of the i9000 kernel. if u find a fix lemmie know..i just stumbled across a 1.6 ghz overclocked kernel. gonna check to see fi thias wqorks
LINKSLOVESANDROID said:
i just noticed it wont lemmie donwload afew games on the market cause of the i9000 kernel. if u find a fix lemmie know..i just stumbled across a 1.6 ghz overclocked kernel. gonna check to see fi thias wqorks
Click to expand...
Click to collapse
Market is totally f'd up. Tried to fix by:
- go back to stock kernel - no good
- factory reset - no
- clockwork wipe data/cach - no good
- flash a new rom and start fresh - no good
I'm going to ODIN back to complete stock now, and re-root. I would recommend to NOT FLASH this kernel, the market does not work properly. Nothing is there; no rom manager, no sgs anything and your paid apps will be GONE.
I'm so glad that this topic is on its way!
A question from a noob tho... Is flashing other ROM kernel is the only way we can have custom ROMS?
Why can't we have our own?? (
If you can post up a video so i can check out what you've posted, i would be willing to help out and find solutions for some of the problems at hand.
Right now i'm alittle wary about this.
cowvun said:
If you can post up a video so i can check out what you've posted, i would be willing to help out and find solutions for some of the problems at hand.
Right now i'm alittle wary about this.
Click to expand...
Click to collapse
There are two problems i had:
1. The market is f'd up...i'm on some wierd test market and can't get access to my paid apps, or any other apps for that matter, only test apps. See here: http://forum.xda-developers.com/showthread.php?t=878181&page=5 and here: http://forum.xda-developers.com/showpost.php?p=10736976&postcount=89
2. Home acts like back, which is a big problem since you can't multitask because as you hit back to do the next thing, you will close whatever you were doing before.
Other than those two problems everything worked fine.
wwowz said:
I'm so glad that this topic is on its way!
A question from a noob tho... Is flashing other ROM kernel is the only way we can have custom ROMS?
Why can't we have our own?? (
Click to expand...
Click to collapse
until a developer decides we are a big enough group of users that we deserve our own "hiding spot" we will have to use i9000 kernels to use custom roms. rumor has it the creator of voodoo supercurio is developing a kernel for our phones which will lead to custom roms. until then, i9000 kernels r the way togo. i have a i9000 advanced voodoo kernel overclocked at 1.28 ghz and undervolted to save battery running a vibrant custom rom called nero v5 which basically skinned the entire setup to look like gingerbread and got rid of the samsung bloatware. honestly, even after we have our own custom kernel ill b sticking with i9000 kernels. just because development has been rediculously slow with the telus t959d fascinate. its taken this long b4 a kernel was even thought about. until it has its own development team creating new roms like every other sgs model on a weekly basis, i9000 wuill have the go ahead. i9000 kernels can run i9000 roms and vibrant roms. and there development communitys are huge! try the above method using custom i9000 kernel. the only issue is theres no home button and afew apps wont download because it thibnks your ussing a i9000. only app i notcied was that 3d mmorpg wont download. i cant remember the name of it. but other then that its great. i got psx4droid running final fantasy 9 overclocked with voodoo. runs MINT!!!! ill gladly walk u through the entire process over msn or facebook etc. send me a email [email protected].
roccos_van said:
There are two problems i had:
1. The market is f'd up...i'm on some wierd test market and can't get access to my paid apps, or any other apps for that matter, only test apps. See here: http://forum.xda-developers.com/showthread.php?t=878181&page=5 and here: http://forum.xda-developers.com/showpost.php?p=10736976&postcount=89
2. Home acts like back, which is a big problem since you can't multitask because as you hit back to do the next thing, you will close whatever you were doing before.
Other than those two problems everything worked fine.
Click to expand...
Click to collapse
i jhad no problems with market. works perfect for me. i just got my girlfriends hd camera so imma record a video at some point tonight. most likely start a fresh thread with proper step by step instructions to get it up to the point i have mine
thanks for the reply! I would go ahead with the kernel but the only downside I'm worried about is the home key I use it all the time XD
LINKSLOVESANDROID said:
ive been testing kernals on my telus fascinate t959d to see if there was any way to get around the no developer issue and came across the love off my live.
the kernels name is "Voodoo-stable-5.0.-Froyo-GT-I9000-odin-pda".
From leaked stock 2.2, i flashed this kernel over the stock through odin. during the initial boot, the female droid voice walked me thru voodoo setup. wait afew minutes after your phone is done loading to allow voodoo to completely enable itself or u will get fc issues. To get to Red clockwork recovery, while your phone is off, hold both volume bottons and the power button. continue holding those 3 buttons until the 2nd i9000 popsup then release all 3 buttons. That should load u into clockwork recovery voodoo. This just basically opened the floodgates for rom testing for me. im running nero v4.1 on my TELUS FASCINATE t959d with no errors at all.
imma upload and post the link
this is the omega leaked 2.2 files in cause u need emergency odin reflash
http://forum.xda-developers.com/showthread.php?t=868829
this is the voodoo enabled kernel
http://rapidshare.com/files/442330146/Voodoo-stable-5.0.1-Froyo-GT-I9000-odin-pda.tar to install this, just download odin, get yout phone into download mode, place the file in the pda slot, and go. i suggest u go back to stock b4 u start for a wiped stock install. if u need help, email me at [email protected] Thx to omega for creating my interest in android custom roms
Click to expand...
Click to collapse
i cannot find a cwm_froyo.tar for telus fascinate anywhere. every link in these forums give me a recovery zip but only has recovery.bin in it..anyone help? this is going to be my first attempt at flashing a new rom so i am pretty nervous and i dont want to brick my phone, i amalready rooted, i have cw rom manager on my phone and everytime i flash cwm recovery it says it was successful i go to recovery and my phone reinstalls stock recovery without cwm, any info or links to tuts would be apreciated...
this is the thread i have been trying to use...http://forum.xda-developers.com/showthread.php?t=948722
question
figured this one out
wwowz said:
thanks for the reply! I would go ahead with the kernel but the only downside I'm worried about is the home key I use it all the time XD
Click to expand...
Click to collapse
use Galaxy Tuner.... enables gestures to replace the missing home key. works great
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
corruptsmurf said:
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Click to expand...
Click to collapse
Well that i a good start. Good to see some reading before the jump in feet first.
corruptsmurf said:
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
Click to expand...
Click to collapse
That's why we're here.
corruptsmurf said:
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
Click to expand...
Click to collapse
Edited: added Later
ADB is a commander center/protocol (if you will) that allows you to control your phone via a PC/Mac/Linux. You can push files which would be taking the file and "pushing" to the phone. Or "pulling" files from the phone and putting them on the computer. It's simply as it states, pushing and pulling the files.
To see what a Kernel is read This.
A ROM is the phones physical Operating system. Similar to what Window, Mac or Linux world be.
corruptsmurf said:
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Click to expand...
Click to collapse
Before you can flash Clockwork Mod you need to root your phone and turn s=off. For one of the methods, - before you can start you need to set up the ADB (Android Debug Bridge). See my signature for the quickest and most painless way to get that set up. You will also need VISIONary.apk. A quick Google Search will find it for you. Link
corruptsmurf said:
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
Click to expand...
Click to collapse
If you want a 2.3 based ROM you will need to flash Recovery image 3.0.0.6, link can be found in my signature, and hit up the development section to read reviews on different ROMs. I personally like the plain AOSP look so that leave Cyanogen(mod). But i know TeamRoyal has put together some newer ROMs that i haven't tampered with yet.
I do everything on my phone through CWM (clockworkmod) or terminal emulator, so there's no need for a PC, unless to download the files and transfer them to my SDcard, as I don't understand adb. Anyways, I'm gonna explain this very short and sweet cuz I was once in your shoes, and remember how much I had to read to understand something That could've been explained so simply.
Think of it this way. You're building the software version of a car. Now, if the whole car is the ROM, then the engine is what would be the kernel. And flashing would then be another word for installing , Now, a toyota with a ferrari engine, would be a custom ROM. While a toyota with a ferrari engine and BMW insignias all over it would then be a custom themed ROM.
**Remember, you can never install a car on something, but you can always install something in a car**
Ex. You can never flash a ROM on a kernel, but you can always flash a kernel on a ROM.
Anyways, first off, you will need CWM recovery to flash. Get it from the market. In the app itself, flash (this is the "flash" in the app) recovery 3.0.0.6. This will flash (this flash is not in the app) anything; any ROM, any kernel, etc. as long as its a FLASHABLE ZIP.
To boot into the recovery (the place you do flashing), hold both volume down and power buttons down as you either turn on or restart your phone. The screen you see is the bootloader. Choose recovery using the volume buttons, and use the power button to select it.
Going to flash a new ROM? Do a factory reset (in recovery), wipe cache (in recovery), and wipe delvik cache (this is in advance in recovery). Then install zip. Its pretty straight forward from there.
Going to flash an updated ROM, skip factory reset (as this deletes all data on your phone) and do the rest.
After you've flashed the ROM, you can now flash the kernel.
Note that, kernels are ROM specific. Read what kinds of ROM's the kernel is for before you flash it.
There, easy as pie, yeah? Hope that helped.
I recommend cyanogenmod 7 (Gingerbread based ROM) with faux's kernel (Gingerbread based kernel)
Sent from my HTC Glacier using XDA App
corruptsmurf said:
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
Click to expand...
Click to collapse
Neidlinger's got your back.
1. Glad you're reading before doing. What a welcome change of pace!
2. Flashing is the process of installing new software. We "flash" it to the phone's memory.
3. ADB is using a computer to control the phone via command-prompt from DOS. Push is a command which sends a file from your computer to your phone. Do a search, there are lots of good guides on ADB. TrueBlueDrew made one just recently that I highly recommend.
Here's Drew's thread. Don't forget to hit his thanks button! - http://forum.xda-developers.com/showthread.php?t=928370
4. Start with Clockwork Recovery and a nandroid backup. That's good practice. CWR2 is compatible with Froyo (2.2) ROMs. CWR3 is compatible with Gingerbread (2.3) ROMs. CWR 3.0.0.6 is compatible with BOTH. Very convenient.
5. I say start with CM7. It's extremely stable, even though it's still in development. A ROM is a complete OS replacement for the phone. ROMs contain kernels, which control the most basic hardware, such as processor. If you flash a custom kernel on your stock ROM, you can overclock it more. You can also flash custom kernels on top of custom ROMs for different battery life, clock speed, etc.
To be honest I don't even bother with custom kernels since this phone is so damn fast out of the box I really don't see the point.
QUICK TIPS FOR CM7 - On your first boot, let it sit for 5-10 mins before setting up. There are background processes running and interrupting can harm stability. BEFORE you sign into google for the first time, after it's finished sitting, reboot. This will clear out any wifi glitches and give you smooth sailing.
Have fun!
BTW, I think most ROM's have a kernel already built in. People install custom kernels because they can have fixes for bugs, help with battery life, overclocked frequencies, no lags, etc. Otherwise, you can just flash the ROM, and if you're satisfied with the kernel its running on, then obviously you'll have no need to flash a custom kernel.
Sent from my HTC Glacier using XDA App
Uchennadi said:
BTW, I think most ROM's have a kernel already built in. People install custom kernels because they can have fixes for bugs, help with battery life, overclocked frequencies, no lags, etc. Otherwise, you can just flash the ROM, and if you're satisfied with the kernel its running on, then obviously you'll have no need to flash a custom kernel.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
This is pretty much spot on. The developers have included kernels that they feel make the OS preform at it's peak. and most of them will allow for overclocking. However on some of them you may need to use a program called "setCPU" to adjust the frequencies. Cyanogen(mod) will have this built into the ROM natively. However most of the veterans will not promote running your phone in an over clocked status 100% of the time. most of us leave the phone at 1Ghz or slower. There are physical reasons, ie the constant expansion and contract of the chip isn't good for the mother board.
If i were you i'd stick with the Stock Kernel and leave it running as it. That way the developer can adjust their ROM, if you use an 3rd party kernel they aren't familiar with the coding so it's not going to act correct.
I'm not putting down what the kernel coders do, they do an awesome job. but for a n3wb i'd leave well enough alone.
6/5/2011 EDIT : Going to alter this post for two reasons. First, the information inside is pretty old news and stale for most, and not even very relevant for new users. Second, there is STILL confusion between these two branches that needs to be ironed out, imo.
If you are considering modding your new GTAB, I would suggest reading this. It's going to be a long read, but you'd rather not brick your device, right?
Some Terminology Pre-Reqs to Understand
"Soft-brick". The device is not booting up properly anymore, but is potentially fixable by using a tool called "nvflash".
"APX Mode". The is a low-level mode on the GTablet where you can makes repairs and un-brick the device.
"Nvflash". This is the name of the actual tool you use, when you are in APX mode.
"Clockworkmod". This is an alternate recovery tool. It adds a few things that the 1.1-based stock recovery does not have, such as full image backups, wiping user data and SD repartitioning. The 1.2-based stock recovery is a little better, but clockworkmod still has more options than 1.2 standard recovery
"/data partition". This is the area on the device where all your user data and user apps reside. A factory reset will wipe this area.
"/sdcard partition". This is the area on the device where all your content resides. It's also the area that gets mounted on your PC.
"Data wipe" or "User data wipe". This is a factory reset -- all user apps and data will be erased. Content in the device's /sdcard is not touched.
"SD repartition". This is a data wipe and a wipe of /sdcard. So both areas are erased.
"ROM" as defined for use should be considered a BOOT ROM. This is the base program running on your tablet, like an operating system it is the first line of code to load and while not every rom is a full replacement of the viewsonic operating system only one can be loaded at a time. (thanks mERRIL!)
"Kernel" as used here is the tablets details and settings written out so the software knows how to interact with the hardware. This is where things like overclocking can be done, along with changing the way your backlight or wifi utilizes power. (thanks mERRIL for both of these!)
Two Development Branches, and How to Check which version you have
This is the FIRST thing any new Gtablet user should check imo, before you attempt to mod your device. Viewsonic / US Merchants released a new development branch with a new bootloader and kernel (which they later pulled), and older mods do NOT play nice with it. There have been reports that at least a few TigerDirect users have gotten 4349 OOTB.
So, to check which branch you are on if you are on STOCK: Go to Settings -- About Tablet -- Tapu UI Version. If your firmware starts with "1.1", then you are on the 1.1 (old) branch. If your firmware starts with "1.2", then you are on the 1.2 (new) branch. Also an obvious difference between the two is that the 1.2 branch adds a lockscreen to the tablet.
The "Two Cliffs" analogy
Try to think of these two branches as two cliffs. If you are on either side and want to mod your device, the safest way is to use a mod that is built around the branch you are on. Here on XDA Developers site, most of their mods and custom kernels are based on the 1.1 branch (as of this writing). For 1.2 based mods, there are several options but most of them are not posted here on XDA. So you have options regardless of which branch you are on. There is no advantage of using one over the other, except possibly vendor support - 1.1 is still the ROM offered by the vendor, given that their one released 1.2 ROM was pulled.
It is possible to jump from 1.1 to 1.2, and back again. But think of this as a bridge between the two. I have done extensive tests in the last month on this, and it does work MOST of the time if you follow directions. But even when doing everything right , there is still a small chance that you will "fall of the bridge" and into the abyss (soft-brick). And if you attempt to jump between them with clockworkmod, you will fall for sure, 100% of the time. Think of clockworkmod as a "bridge that is out".
The most sturdy bridge, going on my own testing, is the one based on build 1.1-3588 full stock. This makes sense because this is what Viewsonic would want you to be on, before jumping to 1.2. The reverse (1.2-4349 stock, for example) is also fairly sturdy. But again, it is a higher risk than staying within the same branch.
I'm on a 1.2-based stock ROM. What are my modding options?
If you are on the 1.2 branch, there are actually quite a few options right now. The challange for a user is finding them and understanding that you have to be careful if you try to use a 1.1 mod instead (see the "Two Cliffs Analogy", above).
The current 1.2 based options on XDA are:
- Calkulin+Clemsyn 1.5ghz Froyo Combo VERSION 6
- Beasty's 2.2.1 ROM (Adam) + Clemsyn ver 11 1.5ghz kernel
- Clem / roebeet Honeycomb alpha combo (this is a Clem creation and is actually forked from my own HC port)
- Honeycomb Android Illuminate for The Gtablet
The current 1.2 based options NOT hosted on XDA are:
- Century Eyes (Froyo based "EDEN" port)
- Mountain Laurel (Froyo based "TapnTap" port)
- Brilliant Corners (Froyo based "VEGA"/"Viewpad" port)
- Bottle of Smoke (Honeycomb port, currently is a mashup from the Adam and VEGA devs)
Pershoot and Clem both have 1.2 kernels that you can use, as of this writing. Not all of that information is here, some are on other sites.
I'm on a 1.1-based stock ROM. What are my modding options?
On XDA, there are still a number of mod options and customized kernels, at your disposal. Again, a 1.1 to 1.1 mod should be fairly safe to attempt. If you want to jump to 1.2, I would recommend reading the modder's post to see if there are instructions for 1.1 jumpers. If not, the SAFEST way to jump is to flash back to 3588 stock (including stock recovery) and then flash to 4349 using stock recovery - that will get you onto the 1.2 dev branch.
There are still a lot of 1.1-based options, if you want to stick to that path. To name a few:
- VEGAn-TAB (probably the most popular GTAB mod, so far)
- VEGAn-TAB Ginger Edition
- Cyanogenmod 7.x
- G-Harmony
- Calkulin's G-Tab ROM
- TNT Lite (similar to Calkulin's ROM, and currently retired)
- gADAM (currently retired, as well)
There are also a few custom kernels for 1.1, specifically the ones by Pershoot and Clemsyn, here at XDA.
OK, so I've confirmed that I'm on one dev branch but I want to use a mod that's on another dev branch - what do I do?
My suggestions:
1- Read the modder's first post, for possible instructions.
2- If there are no instructions for branch jumpers, DO NOT assume that it's safe to jump. Ask the modder first, to be sure.
I am generalizing here, but the older 1.1 mods might not have instructions for 1.2 users, as you didn't exist at the time the mod was created. Imo, the SAFEST way to jump to a mod that's on another branch is to use stock. So 3588 stock to 4349 stock (using standard recovery) to go up, and 4349 stock to 3588 stock (using standard recovery) to go down. The main reason why it's the safest is because stock has the bootloader image in there, which is required to jump.
I attempted a 1.1 to 1.2 (or vice versa) jump, and now I'm stuck at the birds. Is this a soft-brick?
Yes, it's a soft-brick if you are stuck at the birds. You'll need nvflash the device to fix it. There is information here on XDA on how to do that, or you can find this on other tablet sites.
I attempted a 1.1 to 1.2 (or vice versa) jump, and now I'm stuck at the GTablet screen, or I'm boot looping. Is this a soft-brick?
Probably not - more likely is that you just need to do a data wipe, or a SD repartition if that does not work.
I have a Hannspad (or an Olipad) - does this apply to me?
I believe that it does, going on what I've read. Both these devices seem to be based on the TapUI, and the 1.2 development branch. So attempting a 1.1 GTAB ROM will likely have the same pitfalls. Also keep in mind that even 1.2-based GTAB ROMs have issues. for example, the Hannspad can boot a 1.2-based ROM (like "Bottle of Smoke") but the side keys won't work because the hardware is different. I don't have these devices myself, but I am going on third-party information.
Roebeet, can I safely install over the 3588 Stock Enhancement and Market Fix? I hate to lose the Market but definitely don't want to deal with a brick right now. Another user indicated he/she installed the update over a similarly configured machine and it worked but then applied the Stock Enhancement and Market fix and soft bricked.
I appreciate all the work you do for other users, including me.
interesting!!!
I love my devs!!! Seriously you guys rock!!!
P.S. I am sticking with Vegan GingerEdition
Great post and good info roebeet - stickied for the immediate future.
MSU_Sparty said:
Roebeet, can I safely install over the 3588 Stock Enhancement and Market Fix? I hate to lose the Market but definitely don't want to deal with a brick right now. Another user indicated he/she installed the update over a similarly configured machine and it worked but then applied the Stock Enhancement and Market fix and soft bricked.
I appreciate all the work you do for other users, including me.
Click to expand...
Click to collapse
I haven't tested all scenarios, as there are just too many of them. I specifically picked VEGAn as I know that's a very popular ROM and I could see new stock users flashing to that.
Rule of thumb: If you are going from a 1.1-based ROM to a 1.2-based ROM (or vice versa) and use clockworkmod, you will soft-brick your device.
Great work! More coffee for Roebeet
I guess ... better stick to TNT Lite 4.4 for now.
I am curious about (not in any hurry tho)
cwm+TnT Lite 4.4 ->fixrecovery.sh -> stock 3588 ->OTA 4349
--
msu_sparty.
I ran 3991 for a good while during the time the Wooters needed help.
I tried to install the Enhancement Pack on 3991 and it semi-bricked my
G-Tablet.
I wouldn't try it until someone tests it for sure -- unless you want to
be the tester!!!???
Rev
cbay said:
Great work! More coffee for Roebeet
I guess ... better stick to TNT Lite 4.4 for now.
I am curious about (not in any hurry tho)
cwm+TnT Lite 4.4 ->fixrecovery.sh -> stock 3588 ->OTA 4349
--
Click to expand...
Click to collapse
cwm+TnT Lite 4.4 ->fixrecovery.sh -> OTA 4349. This might work. Haven't tested it yet, but I will. It worked for build 3991, so it might work with 4349.
EDIT: One test, one success. Again, YMMV.
As a new tab owner where do I find the build number please?
Thank you
roebeet said:
cwm+TnT Lite 4.4 ->fixrecovery.sh -> OTA 4349. This might work. Haven't tested it yet, but I will. It worked for build 3991, so it might work with 4349.
Click to expand...
Click to collapse
Does fixrecovery.sh also add/enable the OTA updater? Or is there a update.zip for 4349 somewhere?
thanks for all the work,
--
Can 3588 enhancement be loaded with gapps for android market?
SoCal2 said:
As a new tab owner where do I find the build number please?
Thank you
Click to expand...
Click to collapse
Just go to settings-about device
butchconner said:
msu_sparty.
I ran 3991 for a good while during the time the Wooters needed help.
I tried to install the Enhancement Pack on 3991 and it semi-bricked my
G-Tablet.
I wouldn't try it until someone tests it for sure -- unless you want to
be the tester!!!???
Rev
Click to expand...
Click to collapse
Can you point me in the right direction to unbrick this thing? It semi-bricked mine, and I don't know where to start.
SoCal2 said:
As a new tab owner where do I find the build number please?
Thank you
Click to expand...
Click to collapse
Settings about
Thank god I was impatient and installed vegan 5.1.1 before this happened! Was waiting for ota 3588 before root as I was on 3389 this morning. I'm sure you guys won't be long figuring out if there anything worthwhile here.
cbay said:
Does fixrecovery.sh also add/enable the OTA updater? Or is there a update.zip for 4349 somewhere?
thanks for all the work,
--
Click to expand...
Click to collapse
No, it does not. All it does is flashes back 3588 recovery which is the recovery needed to flash between a 1.1-based and 1.2-based ROM.
yay! what we all knew to be the case a month ago is finally confirmed.
SoCal2,
The version number etc. is at Setting/About.
Rev
just lou,
A good start would be to read this thread. If you can do this procedure, it will NVFlash you back to stock version 2638 -- which we call bekit 1105 a lot.
http://forum.xda-developers.com/showthread.php?t=861950
Once you get to 2638, you can set up wifi and it will fairly quickly bring you an OTA Update notice and you can move up to 3588 -- and you can go where you want
from there.
Rev
Well best I recall mine was running 3588--whatever upgraded when I got it a couple weeks ago.
Sae the upgrade a few minutes ago, and opted to load it.
Now sits at "home", shows current (working) time, that I have linksys, that it is charged ((86%) and that sound is on.
Nothing else works. Oh yes, there is lower right hand icon showing an open padlock.
This came up after upgrade. I've powered off and on a couple of times.
Any recommendations?
I downloaded the experimental version of cm11 and found out that the only way to install it is to convert the kernel and install it through Odin
So I took the boot.img from the zip file and converted it to .tar.md5 using CygWin
Then I proceeded to do everything else required (Opening latest CWM from Broadcom, mounting everything and flashing ext4 formatter)
After this I shut down my phone from the "Shut down" option on CMW and connected it to my computer
Then I opened Odin and put the boot.tar.md5 file to the PDA slot and ran the program
Odin installed the kernel, even though it seemed fast fast because it took about 2 seconds
After this my phone booted again, I expected it to boot to the new CWM 6 like it did with the person that gave the instructions but it booted to stock recovery!
The instructions told to install the ROM itself after installing the kernel. When I did this it said "This rom is designed for "totoro". Your device is "GT-S5360" ". It is the same thing?
Does anyone have any idea why this happens? Have I done something wrong?
Also after I used the ext4 formatter, a bunch of errors appeared at the screen
Also I understand that this is an experimental version and that there is a danger of bricking your phone. My phone is 3 years old and I only use it for testing roms and it is not my main phone. Also I do not care if it gets bricked as it has no value.
And also I understand that this is just an experimental version. I appreciate the developers over everything and hope they keep on the amazing work. I just wanted to get a heads on on what awesome stuff they are doing
Thank you for your help, it is very much appreciated
No support here
The devs have made it quite clear that this is for devs only and is experimental and NOT for public use and you should NOT flash it
I dont see why you would want to anyway as nothing works on it other that it boots - this means no phone no wifi bluetooth gps audio and so on
If you really want to see what cm11 looks like im sure you can find an emulator or watch youtube vids
marcussmith2626 said:
No support here
The devs have made it quite clear that this is for devs only and is experimental and NOT for public use and you should NOT flash it
I dont see why you would want to anyway as nothing works on it other that it boots - this means no phone no wifi bluetooth gps audio and so on
If you really want to see what cm11 looks like im sure you can find an emulator or watch youtube vids
Click to expand...
Click to collapse
I have a Galaxy S3 that is running cm11 too, I just want to test it on this phone as it is my old phone and it is fun to test all kinds of crazy stuff on it
Also it is weird how the name of the ROM in the download site is "userdebug" and they said that they want testers on the link to the site
galaxyYtester said:
I have a Galaxy S3 that is running cm11 too, I just want to test it on this phone as it is my old phone and it is fun to test all kinds of crazy stuff on it
Click to expand...
Click to collapse
Than wait until a full supported public beta version is released - no ETAs
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.