Related
Hi to all,
I created this thread here is for existing users, potential users, interested users and experienced users or any casual visitors who wants to know more about the rom. Well, SGS users will ask why create a thread just for this, when there is another one over at the development section. The answers are listed as follows:
To reduce the number of posts in the other thread (reduce spamming) thereby not bogging down the developers with issues that can be solved by the users. And they can spend their time to concentrate what they do best, which is improving the MIUI Rom.
To consolidate questions, problems, bug reports, comments in one place. As you can see from the other thread, many a times, some of the posts which benefits the users were consumed by newer posts. While there is a SEARCH function, I can understand it can sometimes be a challenging task just to sieve through the searched posts results. I know we can't eliminate users posting repeated issues, but at least this will attempt to reduce those posts.
To allow new xda members who are on MIUI but unable to post their ideas, comments, etc. This is also an important avenue to allow new xda members to have a voice. While they may be new, they might have tips, tricks and also can help to resolve issues. Issues brought up can be shared by everyone too.
To allow the developers concentrate on improving the MIUI rom. Who doesn't want a better MIUI? Of course the developers doors will always be open, and will help out whenever they can, but wouldn't it be better for us to let them concentrate on what they do best, and what we want best?
So, to make it successful, I need you guys to help one another out, like what I have seen over the other thread.
This thread belongs to all of you, and I am sure that there is active participations in here.
MIUI has a pretty long history. However, for our device, MIUI has just evolved. Likewise, the user base has just started to grow. There will be times when even the most experienced user or developer will get stumped too, and not able to come up with a solution to resolve. We can see from the other thread that there are diverse views regarding battery life, sdcard issue, etc etc. We will not know since the usage pattern of each individual is as good as your fingerprint. No one is alike. Therefore we seek your understanding that issues not solved immediately will be looked into seriously by the team. There will always be limitations for every rom, regardless what base they come from.
All we ask is whether this rom fits your usage or not. And the only way for you is to try it out. Feel it, experience it, and judge for yourself if this rom fits you, can you live with the shortcomings of the rom. If you decide that this rom doesn't fit your daily needs, you can just simply flash to another rom that fit your needs better. And you can at least tell yourself that I have tried but it is not suitable.
Is this thread some form of advertising? Well, again different interpretations for different people. We will not go into that as we believe the QUALITY OF THE ROM WILL SPEAK FOR ITSELF.
One thing that can be said though, credits goes to the cm7 team, the official MIUI developers too. And each day, we can see breakthroughs. I do foresee a bright future for this rom here.
FAQ Section
[Written by Galnet, g00ndu and me]
Before asking for help, please read through post 1 to post 4. Most of the issues have been addressed in this 4 posts. By doing so, you are helping to keep this thread clean.
1. APP RELATED:
1.1 Apps crashing all the time!
Simply enter recovery mode and do a Format on Data, System, Cache
1.2.1 Apps restored from backup not working
I would always flash from clean and redownload all your apps from market. I know you can backup and restore, but to me this causes alot of issues which people bring up all the time. If you want a clean install and avoid any issues in the long run, then 15 - 20 minutes of redownloading isn't as bad as hours of issues!
Also, if you want to try to restores apps using Titanium Backup, restore "APP ONLY," restoring data causes problems.
1.2.2 3rd party apps force closing
Turn off compatibility mode. Settings > Programs Tab > Manage Applications > All Tab > Select app > Turn off OR IF IT STILL FORCE CLOSES Settings > Programs Tab > Manage Applications > All Tab *again* > Select app > Clear Data > Uninstall and then reinstall using Market.
1.3 Apps not installing
Clear market cache and try again.
1.4 Can't See Paid Apps in Market
Download SGS-Tools and select Market Fix and apply then reboot.
1.5 Downloading from Market Not working
Goto Downloads Press Menu Key and switch Settings to WiFi or Mobile network.
1.6 Searching not working
Simply enter search advanced settings and turn off searching within SMS (Mentioned on Original Post)
2. HARDWARE RELATED:
2.1 SD-CARD Not working or other issues with Camera or Sensors
When flashing if you don't see the Cyanogen Logo after the Samsung one when turning the phone on to enter recovery (After flashing cm7-galaxys-initial-kernel.tar) , then STOP flashing process as you have done something wrong or are trying to install coming from a JVK rom. Downgrade to Froyo or if need be JM1 and start the process over.
Also, camera is not working properly (known bug) – poor saturation and multiple lines running through image.
2.2 External SD card not detected
If your external sd card is not detected even when the kernel had corrected the issue, you most likely has the 2.3.3 bootloaders. You may flash the bootloader (definitely not recommended) or you can restart using EZBase rom or follow galnet's guide in his site.
2.3 Auto rotation/accelerometer not working
If your auto rotation/acceleromter is not working (despite having it enabled in Settings > Common Tab > Display Settings > Auto-rotate screen) then hard reboot (completely switch off device, wait 10+ seconds, and then switch device back on)
2.4 High Battery Drain
Known CM7 bug that is not fixed yet.
2.5 Battery only reports ~96% on full charge
This is a function implemented on ALL 2.2.1+ ROMS (including MIUI, which is based off CM7 2.3.3) so that the battery of the devices do not overcharge. Samsung ROMS falsely report 100% charge, but in actual fact, it also charges to ~96% and that if you watch closely, after a few minutes, the battery will rapidly drop back down to ~96% and stablise.
http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
2.5 Battery has stopped charging
Battery is known to stop charging when it gets too hot. This is to protect the battery and phone from exploding.
2.6 Phone turns on when I insert charger
This is a known bug (or function LOLS) which is present in the Nexus S ROMS and because the SGS MIUI ROM is a derived from the MIUI Nexus S ROM, SGS will also have this bug/function.
3. ETC:
3.1 Where do I start?
Have a look at Galnet's MIUI Guide and note that you can start from ANY Froyo ROM (Stock and Custom) as long as your device has a Froyo Bootloader.
3.2 Flashing from JVK to MIUI
You must first downgrade the firmware to Froyo (which MUST include a Froyo Bootloader - check in zip via WinRar for boot.bin and sbl.bin) It has been found that the Gingerbread bootloader has caused major problems. It is recommended that you downgrade to Eclair JM1 then upgrade to JS5 (files are avaliable on Galnet's Website) and then follow Galnet's MIUI guide to flash MIUI.
Note that flashing/using any Gingerbread modems such as JVK will not cause problems, it is only the Gingerbread bootloader that is causing problems.
3.3 IMEI SCREWED!
Flash back to JS5 or another Official Rom and it will be restored!
3.4 FLASH AT OWN RISK
If you don't have a clue what you are doing or ODIN is a strange word, then please go over to Galnet's MIUI guide and read it before flashing, make sure you understand the risks and note that the developers are not always available to answer your questions instantly!
3.5 Applying a downloaded theme:
Move theme file anywhere onto your phone's memory (should have a .mtz file extension) > Open Theme Manager > Press on Capacitive Menu Button > Import Theme > Locate and Select the theme you added onto your phone's memory
Alternatively, you can directly move the theme (.mtz) file to sdcard/MIUI/theme/
3.6 (SOME) Themes not changing lockscreen
Check that the theme supports MIUI Gingerbread 1.4.8, older MIUI FROYO themes will not work.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
COPY AND PASTE:
(Insert FAQ here)
In the future, please refer to the MIUI FAQ Section[/URL ] before posting.
TIPS AND TRICKS
1. Download seems to get stuck forever. Download only works with wifi.
To fix, open up the Download App, click menu, select toggle 3g /wif. This normally will work. If it doesn't work, try for 2 or 3 times. Remember to cancel the download from the app. If it still doesn't work, reboot and try again. The best fix will be to boot into recovery, and do a wipe / factory reset and reboot. Before downloading, go to the download app to activate the 3g / wifi toggle.
2. Speaker phone is too loud (Thanks to Ekin)
Goto DSPManager > Phone Speaker > Enable equalizer
Then drag all the zeros on the graph down to about -3.0 but keep them all roughly the same. This will lower the volume on the loudspeaker for everything, fixing your problem. When you want to watch a movie and want to make it louder, go back here and just swipe it to disable. So its only one swipe to get it on/off. In order to keep the settings, you need to hit the Back button for it to register correctly.
Raising it/enabling bass boost seems to kill the quality a little bit, so I recommend not to do those.
I have a Nokia headset that I use, and its a little quite so I do the same trick (except I raise the "headset" equalizer) and this nifty trick is basically the same as the voodoo sound hack which takes proper use of the high-quality sound card inside the Hummingbird.
3. Choppy / Laggy graphics and interface (Thanks to whitesox311)
In the settings under battery options....it has " power saving mode" on automatically....if you disable this it gets rid of all the issues. Also, if you leave "Hi-res graphics" turned off in the launcher settings it vastly improves smoothness.
4a. How to get Swype to work (Thanks to Prototype159)
Download the swype installer.
Follow the directions all the way til the end.
Hit the finish button. Reboot.
If it didn't work, clear data and uninstall swype and the swype installer. Try again.
If you change the kernel, you will have to redo it again.
4b. How to get Swype to work (Thanks to agha123)
Follow the instructions to the tee on this web page ,
http://www.androidpeek.com/2010/12/get-swype-keyboard-working-on-miui-rom/
5. Screenshot (Thanks to hacksome)
Pressing Menu + Volume DOWN -->> Screenshot!
reserved
Sent from my GT-I9000
Hmm...good timing. I have some questions on my own.
I have been reading the installation procedures for a while. This particular line intrigues me
6: Pull out the USB cable and start (in download mode) with 3-button-combo in recovery mode (waiting until samsung logo appears)
How do I start recovery mode within download mode? I don't want to take any risks but wish to understand fully on what I will be doing before I commit.
Another question: Assuming that later I decided MIUI is too buggy, is there a backtrack procedure? Usually I will just reflash with ODIN to a stock rom(eg: JPY) to rid of all the lagfixes etc then to maybe Doc's rom for example.
Since this is a ASOP sort of ROM in GB. how do I go about it?
Noob questions I know but I rather be noob now then to beg for help around later
i dont have the maps application in my rom. After installation i dont see any maps app.
mystifiyer said:
Hmm...good timing. I have some questions on my own.
I have been reading the installation procedures for a while. This particular line intrigues me
6: Pull out the USB cable and start (in download mode) with 3-button-combo in recovery mode (waiting until samsung logo appears)
How do I start recovery mode within download mode? I don't want to take any risks but wish to understand fully on what I will be doing before I commit.
Another question: Assuming that later I decided MIUI is too buggy, is there a backtrack procedure? Usually I will just reflash with ODIN to a stock rom(eg: JPY) to rid of all the lagfixes etc then to maybe Doc's rom for example.
Since this is a ASOP sort of ROM in GB. how do I go about it?
Noob questions I know but I rather be noob now then to beg for help around later
Click to expand...
Click to collapse
It means exactly that. In download mode hold the 3 buttons (vol up, power & home) and release all keys when the Samsung logo appears. After about 5 seconds you will see recovery mode.
You can easily backtrack. In Odin use a fw that has all three files and tick repartition. I use jpu.
Sent from my GT-I9000 using XDA App
sxi200 said:
It means exactly that. In download mode hold the 3 buttons (vol up, power & home) and release all keys when the Samsung logo appears. After about 5 seconds you will see recovery mode.
You can easily backtrack. In Odin use a fw that has all three files and tick repartition. I use jpu.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
@mystifyer,
this is the same answer i will give. it is correct.
thanks sxi200.
Sent from my GT-I9000
vivekrk44 said:
i dont have the maps application in my rom. After installation i dont see any maps app.
Click to expand...
Click to collapse
maps can be downloaded from market.
Sent from my GT-I9000
This is new! I didn't know we can do that!
Shall give it a try this Friday Thanks for the explanation
Another question:
I understand also that ASOP roms don't have the very good codec support. Fair enough. Some threads I seen has mentioned of Moboplayer. I gave it a try. Works well enough in hardware acceleration mode but software decoding mode looks really slow.
Now my question is: Does software decoding mode works better in ASOP roms than say a generic lagfixed rom?
vivekrk44 said:
i dont have the maps application in my rom. After installation i dont see any maps app.
Click to expand...
Click to collapse
Download from Market.
mystifiyer said:
This is new! I didn't know we can do that!
Shall give it a try this Friday Thanks for the explanation
Another question:
I understand also that ASOP roms don't have the very good codec support. Fair enough. Some threads I seen has mentioned of Moboplayer. I gave it a try. Works well enough in hardware acceleration mode but software decoding mode looks really slow.
Now my question is: Does software decoding mode works better in ASOP roms than say a generic lagfixed rom?
Click to expand...
Click to collapse
wow, this one i dont really know. i am not sure if there were bemchmarks being made on that or not.
not a good comparison, but still say this. i ran quadrant for this two roms, and the framerate for samsung is better in 3D, and not much different on 2D.
dont forget samsung did not release the sourcecode, and cyanogenmod do it from scratch. but nevertheless it is still good in aosp.
Sent from my GT-I9000
Prasad007 said:
Download from Market.
Click to expand...
Click to collapse
tks buddy, glad you are here too.
Sent from my GT-I9000
g00ndu said:
tks buddy, glad you are here too.
Sent from my GT-I9000
Click to expand...
Click to collapse
Likewise.
No problem. I will know it after I try this Friday. I can share it then, provided nothing goes wrong.
Quite a fair bit of adventurous users tend to dive in straight without checking the cons of a ASOP rom, only to regret and then flash back. I don't really want to fall in this category.
Multimedia is big for me as I watch alot of animes. This codec problem might give me abit of a headache with the software decoding and probably missing code support.
I think I asked enough. Shall camp here and explore other users' problems.
Thanks for the feedback. Appreciate it.
Did the galnet's instructions and the result is the same. so tired by the way
dr.bahaeddin said:
Did the galnet's instructions and the result is the same. so tired by the way
Click to expand...
Click to collapse
I've PM'ed you, I advise you do a 3 file install of JP2 via ODIN to make sure all your files on the phone aren't corrupted.
Once you have got Froyo installed then please get back to us. (Boot into Froyo and make sure it's all working correctly)
galnet said:
I've PM'ed you, I advise you do a 3 file install of JP2 via ODIN to make sure all your files on the phone aren't corrupted.
Once you have got Froyo installed then please get back to us. (Boot into Froyo and make sure it's all working correctly)
Click to expand...
Click to collapse
got your message man downloading right now. maybe my internal sd makes files corrupted?
dr.bahaeddin said:
got your message man downloading right now. maybe my internal sd makes files corrupted?
Click to expand...
Click to collapse
Pass mate, but if you have a felling this could be the case then format the internal sd, after installing Froyo and then copy the required MIUI files back across to your internal sd and then try to proceed in flashing MIUI again.
galnet said:
Pass mate, but if you have a felling this could be the case then format the internal sd, after installing Froyo and then copy the required MIUI files back across to your internal sd and then try to proceed in flashing MIUI again.
Click to expand...
Click to collapse
ok now i'm on JP2 everything works fine.
Ok been running 4.04 for a sometime now. I got it as it first came out.
Some issues that u have noted outside of the bricking issue. **disclaimer I am running my own built version of this ROM deoxeded zipaligned bla bla bla plenty of tweaks etc and the ROM is faultless(not really it has its faults and I am about to list them) with exception of a few things that may or may not be kernel related. IT DID NOT flash the new .pit file. I have built the ROM as according to 4.03 builds and used Siyah kernel.
1. initial boot and dalvik cache build takes an extremely long time. Easily mistaken for bootloops and possibly another reason people prematurely ejected this ROM
2. Android is upgrading/updating splash does not exist. Further adds to the concern that phone has enternal bootloops...it doesn't it just doesn't warn you. It goes back to the gingerbread days where you wore a big question mark ? on your head "What is my device doing?"
3. Bluetooth enablement does not work. We go from 4.03 that had wifi issues much similar to fixed wifi and issues with bluetooth. Sux. Guess you cant win eh?
My guess is that this is specifically related to the kernel and framework. Ihave the framework decompiled now and I will be looking into maybe making some adjustments to allow for the bluetooth drivers in 4.03 kernels to interact with 4.04, rather than a whole new re-reslease of kernels just to combat this issue.
4. USB not detectable in Windows 7? Hmmm I am not sure what happened here? It worked flawlessly for 2 days and then all of a sudden not recognised? USB speeds were perfect when it did work, reflashing the ROM did not fix this? My guess is that this is also kernel<->framework related. Also to note here that within the siyah recovery you can mount USB no issues and transfere, so no eMMC corruptions before you freak out.
5. Vol down + power button for screen capture does not work? This again maybe because of the kernel used?
Can anyone give any reason for me not running the new pit and flashing stock kernel? Does the stock kernel require that there is a repartition or is this an assumption?
Additional notes: Further testing my eMMC with Gotbrickbug *MASSIVE thanks to chainfire for this support* personal thanks from me. Thanks Chainfire you're a legend! After testing it revealed oddly enough that my eMMC was inconclusive, so not that it helped me much, but I have flashed this firmware now several times and have not had any issues. Everything working smoothly and 100% except for the above mentioned.
I am tempted to flash the standard kernel now (again no repartition) and then do CFroot for the stock kernel image on this firmware to see if these issues are alleviated in 4.04?
Additional to this is that I have the 15 toggles mod by Jkay translated and compiled with exception of the last file on systemUI for 4.04. I would REALLY love to have this ROM running for everyone.
Any input suggestions warnings (besides the brick scare - I am not scared cause I doubt my phone will brick considering I have flashed it so many times now with the phone acting the same every single time)are welcomed. Please use your head when you respond and not your bricked phone, I would like intelligent answers and discussions. Preferrably not from n00bs or those that are only rehashing all that has spilled out across the petition thread already.
My understanding is that it is a repartition issue with bricking not a kernel or ROM issue its self. My understanding is that I can flash any kernel I like I can flash the stock one and I should be able to flash a rooted one after it to get back if I want?
Proceedure now:
Flash ROM
Flash kernel
Flash CFroot
Flash Modded recovery
Happy days?
I think most of those issues are due to Siyah, because I've tried the same builds running the stock kernel, and I didn't encounter most of them. Bluetooth fine, USB fine, etc. Nothing major. Still went back to LGP because the 4.0.4 implementations are quite ugly at this point.
Again flashed this ROM no problems.
I also attempted to run 4.04 czech republic version of this ROM to which it did not boot or run. Just to let those know that were considering doing this. I had 3 apks from that 4.04 build that refused to deodex? Also the sizes of all apks in this version of 4.04 (which does not come with a supplied .pit file) are vastly different to those in the Euro 4.04 supplied with .pit?
Yet to download and try 4.04 Chinese version? I figured someone else has probably already done this....the chinese are fast lil buggers. They don't much around! haha. If anyone has feel free (and please I would like you to contribute) to comment in this thread on your findings?
James
PS: Just about to flash standard kernel on unpartitioned GS2 if all goes well I will implement CF-Root. Cheers
donalgodon said:
I think most of those issues are due to Siyah, because I've tried the same builds running the stock kernel, and I didn't encounter most of them. Bluetooth fine, USB fine, etc. Nothing major. Still went back to LGP because the 4.0.4 implementations are quite ugly at this point.
Click to expand...
Click to collapse
Did you re-partition when you flashed stock kernel? I like the sounds of this. I have the 4.04 working nicely.....if i can achieve the above I will create a ROM and upload. Thank you for your valuable input
I may even test with the czec 4.04 kernel and see what happens there? Hmmm
Kernels are identicle sizes but not the same?
czec zimage: MD5 2A4AE1B758D934E2AD1791E318F94424
europe zimage: MD5 FCB26E67AE9E7F701793B6014E4AF7D2
see attached for additional size details? I am wondoering if czec might be better for no repartition was/is used in this 4.04 build?
James
WOW! I flashed standard kernel and I now have bluetooth enabled and I STILL kept root access. yeeeeeeeew! stoked!
Jarmezrocks said:
WOW! I flashed standard kernel and I now have bluetooth enabled and I STILL kept root access. yeeeeeeeew! stoked!
Click to expand...
Click to collapse
No fix for USB enablement? I have switched the customboot.sh for the MTP application. I however don't have MTP.apk in system? I may place this apk and then re-try to see if I might be able to get the thing to be recognised by my PC.
USB Mass storage is now working via the old method. I need to have the MTP client in system/app for this to work. No longer getting the USB device not recognised which is great.
Any kernel devs want to share with me how to embed the correct components in the kernel to allow for customboot.sh to work? I am certain then that USB mass storage will work when that script can be run and enabled at boot. I dare say that boot animations should work then also.
4.04 is starting to shape up nicely now
I decided to go into custom ROMs, but it's been nothing but trouble ever since.
NOTE: I own two cables and it's the same with both
I updated to the latest nougat build with Cosmic OS, and then realized my phone wasn't recognized by my computer anymore.
Tried RR, same deal.
Went back to MM oxygen OS, and all my problems were gone.
I loved Nougat, so I made a backup of MM and decided to stay on Cosmic OS for now, even though It's not recognized by my computer unless I put it in fastboot mode.
Two weeks into Cosmic OS, I realized that my phone has been charging a lot slower than usual (I used to just leave it overnight, and when I tried to charge during the day I realized that it was charging too slow)
I then thought: what if it's my cable about to die?
So I broke out my backup cable, same thing.
Again, back in Oxygen OS, the problem was gone.
I don't know what to do about this. I am tired of OOS, and don't want to go back, but slow charging is a huge disadvantage and I don't think it's good for my battery either.
update: I've tried RR, CosmicOS, LineageOS, and AOSiP.. all of them with the same issue for me.. I don't know why
I just keep having to restore that OOS 3.6.0 backup i made after accidentally bricking my phone after trying CosmicOS/RR for the first time lol
It is because of the ****ty charging drivers by Oneplus. They work for half of the users and break for other half. Boeffla has a kernel with 2 different versions of this driver baked in his kernel. Try both these variants and see if any works for you.
Harpratap said:
It is because of the ****ty charging drivers by Oneplus. They work for half of the users and break for other half. Boeffla has a kernel with 2 different versions of this driver baked in his kernel. Try both these variants and see if any works for you.
Click to expand...
Click to collapse
Thanks! I'll give it a try!
Never messed with kernels in the past, but it's worth the shot
EDIT: I forgot to mention in the OP, that my computer will not recognize the phone even when i am on TWRP, for some strange reason.. would the kernel solve that as well?
Also, I see that boeffla is only for CM based ROMs, I don't really like LineageOS compared to Cosmic OS, do you think it would work anyway?
Niko. said:
Thanks! I'll give it a try!
Never messed with kernels in the past, but it's worth the shot
EDIT: I forgot to mention in the OP, that my computer will not recognize the phone even when i am on TWRP, for some strange reason.. would the kernel solve that as well?
Also, I see that boeffla is only for CM based ROMs, I don't really like LineageOS compared to Cosmic OS, do you think it would work anyway?
Click to expand...
Click to collapse
No, a kernel won't fix that. Something wrong with your PC driver. Nothing related to phone.
You can try but it has slim chances of working.
Harpratap said:
No, a kernel won't fix that. Something wrong with your PC driver. Nothing related to phone.
You can try but it has slim chances of working.
Click to expand...
Click to collapse
I tried it on two PCs and had the same problem on both
the installation thing for the OP drives wasn't even showing up
Niko. said:
I tried it on two PCs and had the same problem on both
the installation thing for the OP drives wasn't even showing up
Click to expand...
Click to collapse
Download universal adb drivers? It's just a simple setup file and works for almost all Android phones
Niko. said:
I tried it on two PCs and had the same problem on both
the installation thing for the OP drives wasn't even showing up
Click to expand...
Click to collapse
Do you get the option to change from charging to file transfer on the phone when you plug it in.
When you pull the menu down you should have a USB setting thing.
pops106 said:
Do you get the option to change from charging to file transfer on the phone when you plug it in.
When you pull the menu down you should have a USB setting thing.
Click to expand...
Click to collapse
I dont have that option when I drop down the status bar. In developer options when I select file transfer , it goes back to charging . I've used two different PC's and I'm pretty confident that I have installed the drivers correctly . And MTP doesn't work in twrp either . I'm on stock oxygen os right now any ideas ?
Everything you say tells me you should try a different cable. If that doesn't work, I have no idea.
Murbert said:
Everything you say tells me you should try a different cable. If that doesn't work, I have no idea.
Click to expand...
Click to collapse
I've used 3 cables and 4 different PC's nothing
Thanks to everyone for all of your replies. I was kinda stubborn about the whole "trying a different cable" thing because everything was working normally on my old cable, as long as I was on Oxygen OS..
I will never know why, but changing the cable did the trick. Now getting charging a lot faster than I was used to, even on my old setup!
Loving Nougat on CosmicOS!
Niko. said:
Also, I see that boeffla is only for CM based ROMs, I don't really like LineageOS compared to Cosmic OS, do you think it would work anyway?
Click to expand...
Click to collapse
Buddy read the boeffla's OP carefully. Its for stock OOS right?
Hi,
I've been reading for some hours and did not want to bother you with one more beginner's question but I prefer to ask before rather than pulling my hair off and discovering that I did something wrong. Here are my questions.
I have a Nexus 7 2012 Wifi with android v5.1.1 running on it, extremely slow.
1)To flush a new ROM I saw one movie on youtube that was using the android default bootloader, but here on the forum I read (and later learned what it means) about TWRP. Do I need to first install TWRP on my Nexus 7? can you please help me with a link to a tutorial or even better to a youtube movie on how to install it.
2) I remember a long time ago I flushed the v5 ROM by using an OTG USB Cable, I can't use an normal cable right?
3) Which ROM to choose. I'm not that picky, I guess any would be better than the current one. I read that v7 is pretty good, but there are too many ROMs and I got lost in the acronyms. I need a ROM that will run as fast as possible (at least decently). I do not need any google aps, but I read somewhere that sometimes if you choose a ROM without the gapps (I guess this is the acronym used right) then you do not get even the Google Play. I need Google play to install Chrome and a few applications for my son. (to learn a second language: Duolingo)
More than I do not need. It would be good if the battery would last longer, but it's not a problem if I need to charge it every now and then.
I learned that the ROM that I need is called grouper (wifi only).
4) OTA means over the air. Now I guess that all the rooms for android v7 are unofficial ROMs (meaning not provided by google, sorry if I got it wrong). In this case, does the OTA refers to the security patches provided by Google to patch their OS? or does it refer to the installation of a new ROM without the USB cable, directly from the internal memory
5) I do not care about the internal data, I can delete it all, but I did a factory reset of a Samsung Galaxy A10 (a more recent tablet) and I regretted it dearly, because I had forgotten the username and password that I created when I first used the device, and then I had to take it to an official Samsung repair shop to have it fixed, as it couldn't be used without the original account (username and password). I guess this is not the case for older versions. I can of course check my current Google account that I created while using this tablet for the first time. I checked the Users on the tablet, and I can't really find a Google account, but just a local account. In any case, could anyone of you confirm that if I clean all the data it shouldn't be a problem to install a new ROM afterwards.
Many thanks for your time and efforts in answering the above questions, but also to develop new cool great amazing ROMs that bring old devices back to life.
I think the easiest way to go is using Nexus Root Toolkit and Pure Nexus MM rom. Using NRT is pretty easy as long as driver works. It'll unlock bootloader and install TWRP. After installing rom install Parrot Mod and tablet will be reasonably quick way faster than stock lollipop. Thats what I have and it's still usable.
Sent from my Nexus 6 using Tapatalk
Hjicons said:
I think the easiest way to go is using Nexus Root Toolkit and Pure Nexus MM rom. Using NRT is pretty easy as long as driver works. It'll unlock bootloader and install TWRP. After installing rom install Parrot Mod and tablet will be reasonably quick way faster than stock lollipop. Thats what I have and it's still usable.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hi,
I guess I should be doing something similar with this tutorial (ok the NRT version is newer now).
https://www.youtube.com/watch?v=tdFQtmgHC5M
And then flush the custom ROM that you were talking about the Pure Nexus MM Rom, which is not in the above video.
Do I need an OTG USB cable for that? I need to be careful and test first as the USB port connection was phisicaly tricky (I need to ensure the connection and then do not touch the USB cable anymore so that it does not disconnect). I think if I'm very careful it should be working eventually.
Many thanks
Any USB cable that allows computer to recognize Nexus 7 as a device is ok. Before doing anything make sure that full driver test is successful. Next is OEM unlock which will wipe the device, then TWRP flash and root. Then flash stock from NRT and boot.
Next download PN MM rom, copy to some directory on Nexus 7, boot into TWRP, install, boot. Repeat same with Parrot Mod (flash from TWRP). After that tablet will be usable. ROM build that I have is MTC19Z
Sent from my Nexus 6 using Tapatalk
Hey guys listen up, your gonna love this! I have a grouper too and i have it using 7.1.2 tried your methods and ended up here, its incredible if you can do these things :
1) Change your data and cache to f2fs which wipes your internal storage.
2) Install crdroid ROM from this week with june kernel.
https://forum.xda-developers.com/nexus-7/development/rom-crdroidv3-8-3-nexus-7-2012-t3710834
3) DO NOT install GAPPs (for ultimate otherwise pico I guess but this beast is old and tired we are trying for ultimate efficiency.)
Ohh and use NRT 2.1.9 to install your select couple of apk's thats it for performance.
4) Despite all warnings try ParrotMod it works for me.
Literally many times faster than PureNexus..
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.