Hello.
What is the last and best custom ROM for the Galaxy Wifi 5.0, and where can I find the files?
Thanks.
Meticulus.co.vu to download the latest but listen to me you need to start with cwm, then flash meticulous 4.4.4 to update the cwm, then flash twrp to get 5.1.1 installed, here. I figured out the exact steps to get this device working perfectly again. Firstly the twrp folder on the external sd card has to be renamed TWRP because it has extra strange characters after the TWRP. Now we know how to restore our backup, we can start by ODIN back to stock, then Framaroot v1.4.1 root the device then download entropys daily driver kernel cwm, the flash it via terminal emulator, reboot, then you have to install meticulous carbon 4.4.4 to fix the partitions and update the cwm to adb sideload the twrp. So you can then flash Meticulus Carbon 5.1.1 and both updates and 5.1.1 pico gapps. Good to go. Meticulus made the kernel overclock to 1.7ghz and it runs pretty darn good honestly. I modded the build.prop vm dalvik heap limit to 384m from 128m to get some extra performance out of it.
chris1892006 said:
Meticulus.co.vu to download the latest but listen to me you need to start with cwm, then flash meticulous 4.4.4 to update the cwm, then flash twrp to get 5.1.1 installed, here. I figured out the exact steps to get this device working perfectly again. Firstly the twrp folder on the external sd card has to be renamed TWRP because it has extra strange characters after the TWRP. Now we know how to restore our backup, we can start by ODIN back to stock, then Framaroot v1.4.1 root the device then download entropys daily driver kernel cwm, the flash it via terminal emulator, reboot, then you have to install meticulous carbon 4.4.4 to fix the partitions and update the cwm to adb sideload the twrp. So you can then flash Meticulus Carbon 5.1.1 and both updates and 5.1.1 pico gapps. Good to go. Meticulus made the kernel overclock to 1.7ghz and it runs pretty darn good honestly. I modded the build.prop vm dalvik heap limit to 384m from 128m to get some extra performance out of it.
Click to expand...
Click to collapse
I have tried but something went wrong.
Now when I boot I have a black screen with "NUTELLA" and a logo with "M".
If I use recovery mode a menu with yellow items is shown but every installation from ZIP file fails with the error:
E: failed to map file
Installation aborted.
Any suggestion ?
Thanks !
erlofp said:
I have tried but something went wrong.
Now when I boot I have a black screen with "NUTELLA" and a logo with "M".
If I use recovery mode a menu with yellow items is shown but every installation from ZIP file fails with the error:
E: failed to map file
Installation aborted.
Any suggestion ?
Thanks !
Click to expand...
Click to collapse
www.meticulus.co.vu/p/yp-g70.html
1st download this - https://androidfilehost.com/?fid=24591023225177417 + update 1 & 2 here =
https://androidfilehost.com/?fid=24665542585483890
https://androidfilehost.com/?fid=24686680535466961
2nd make sure you have cwm 5.0.2.7 because that Meticulus KK Carbon 4.4.4 rom will update to the version of cwm required to install twrp 2.8.0.0
3rd install the twrp 2.8.0.0 after you updated your cwm via the rom above, it auto-updates the cwm to the version required to have to flash twrp 2.8.0.0
twrp here - https://androidfilehost.com/?fid=24686680535466961
then install Meticulus 4.4.4 KK Carbon 4.4.4 make sure to put them in folders to know the KK is 4.4.4 and LP is 5.1.1
it fixes the partitions so it can take the 5.1.1 meticulous rom make sure to install the updates
ps - 4.4.4 is faster than 5.1.1
test 4.4.4 KK kit kat first then try 5.1.1 …. I'm using 5.1.1 because its newer but its really slow.
rom 5.1.1 - https://www.androidfilehost.com/?fid=24572369242688755
update 1 - https://www.androidfilehost.com/?fid=24665542585483911
update 2 - https://www.androidfilehost.com/?fid=24686680535466111
Finally I has been able to restore my device and install KK.
Now I will try it for some days and then will decide if upgrade to CM12
Some problems because .meticulus site is down today ( deleted ???? ) and because Odin with Win10 doesn't recognise my device. fortunately I still have a WinXP machine that works like a charms !
erlofp said:
Finally I has been able to restore my device and install KK.
Now I will try it for some days and then will decide if upgrade to CM12
Some problems because .meticulus site is down today ( deleted ???? ) and because Odin with Win10 doesn't recognise my device. fortunately I still have a WinXP machine that works like a charms !
Click to expand...
Click to collapse
KK works but seems slower than 2.3.6.
Is CM12 even slower than KK ?
erlofp said:
KK works but seems slower than 2.3.6.
Is CM12 even slower than KK ?
Click to expand...
Click to collapse
Yeah I'm using Slim Rom 4.3.1 right now but the camera is broken the pictures are blurry and the result is a corrupt file capture. So now I have to find another rom that'll work better.
Meticilius roms are laggy as all get out so idk what to do. I'm going to re-read my post on how to do these tricks anyway its been a while since i messed with it.
*UPDATE* I find Meticulus 4.4.4 works best for now at least the camera isnt broken but no overclock stability sadly but its fine. If only this device had 2gb ram it would be way more fun to play around with.
sadly the link posted for TWRP for the YPG70 was just the same link all over again.
does anyone happen to have the most recent TWRP?
what I want to do is repurpose my Galaxy Wifi Player to view the remote status of my car, so all it needs is a working screen, web browser and wifi.
speculatrix said:
sadly the link posted for TWRP for the YPG70 was just the same link all over again.
does anyone happen to have the most recent TWRP?
what I want to do is repurpose my Galaxy Wifi Player to view the remote status of my car, so all it needs is a working screen, web browser and wifi.
Click to expand...
Click to collapse
https://www.mediafire.com/file/uyhoyrubtjtzzm9/TWRP-2.8.0.0-venturi-flashable.zip/file
thanks @chris1892006 that's very kind of you.
chris1892006 said:
Meticulus.co.vu to download the latest but listen to me you need to start with cwm, then flash meticulous 4.4.4 to update the cwm, then flash twrp to get 5.1.1 installed, here. I figured out the exact steps to get this device working perfectly again. Firstly the twrp folder on the external sd card has to be renamed TWRP because it has extra strange characters after the TWRP. Now we know how to restore our backup, we can start by ODIN back to stock, then Framaroot v1.4.1 root the device then download entropys daily driver kernel cwm, the flash it via terminal emulator, reboot, then you have to install meticulous carbon 4.4.4 to fix the partitions and update the cwm to adb sideload the twrp. So you can then flash Meticulus Carbon 5.1.1 and both updates and 5.1.1 pico gapps. Good to go. Meticulus made the kernel overclock to 1.7ghz and it runs pretty darn good honestly. I modded the build.prop vm dalvik heap limit to 384m from 128m to get some extra performance out of it.
Click to expand...
Click to collapse
Is there any video to follow steps? Please help me. Thank you.
I'm sorry but I forgot how to do it from the gingerbread is what it comes with by stock right? Reading my posts on here I tell exactly how to do it around these threads somewhere around here on xda. Sorry bro. Keep in touch. BTW - the device is best left stock because its useless for anything for anything other than for musicolet music player or music folder player & mx player. I'd be pleased with stock because all I use mine for is Music only.
Related
------------- SOLVED! --------------
Hello all,
First of all I want to say I'm pretty new to flashing ROMs etc.
Currently I'm at stock 4.3 Jellybean and I want to flash my SGS3 to the new CM 11 ROM.
I rooted my phone following this tutorial: vvvvvv.telefoonrooten.nl/samsung/samsung-galaxy-s3-root/ (sorry if its in Dutch, but it uses the CF-Root-SGS3-v6.3 and Odin).
After I rooted I copied both the CM11 ROM and GAPPS to my external SD, I went to recovery and tried to install the new custom ROM but I got an error (status 7) and it was aborted.
Also if I try to reboot it won't boot normally as it should be but it goes back to recovery mode automatically...
I fixed to get back to Jellybean by flashing the stock rom (unrooting?) it via Odin.
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Thanks in advance,
Steelbear
Steelbear said:
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Click to expand...
Click to collapse
please read the thirst post in a rom/kernel/whatever thread. and maybe if you havent done it already you should also read the stickies in general section.
FAQ (Read before post !!)
- If you obtain Error 7 when you tried to install ROM in CWM or TWRP
Install the latest version of CMW or TWRP
Click to expand...
Click to collapse
BTW latest philz touch recovery works too
Since you went back to stock and you already know how to root, I suggest you go to Play Store and download ROM Manager to help you install latest CWM recovery on your device.
Or you can simply go to CWM website, pick the version of the recovery for your phone and flash it via Odin.
Hope it helps.
Steelbear said:
Hello all,
First of all I want to say I'm pretty new to flashing ROMs etc.
Currently I'm at stock 4.3 Jellybean and I want to flash my SGS3 to the new CM 11 ROM.
I rooted my phone following this tutorial: vvvvvv.telefoonrooten.nl/samsung/samsung-galaxy-s3-root/ (sorry if its in Dutch, but it uses the CF-Root-SGS3-v6.3 and Odin).
After I rooted I copied both the CM11 ROM and GAPPS to my external SD, I went to recovery and tried to install the new custom ROM but I got an error (status 7) and it was aborted.
Also if I try to reboot it won't boot normally as it should be but it goes back to recovery mode automatically...
I fixed to get back to Jellybean by flashing the stock rom (unrooting?) it via Odin.
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Thanks in advance,
Steelbear
Click to expand...
Click to collapse
I had the same problem the fix is quite easy
flash the latest CWM 6.0.4.4 and flash cm11 it will work fine
Blackwolf10 said:
I had the same problem the fix is quite easy
flash the latest CWM 6.0.4.4 and flash cm11 it will work fine
Click to expand...
Click to collapse
Indeed it worked! I found it out myself yesterday. Went to the CWM site and downloaded the latest version (6.0.4.4.) and flashed it through Odin. But thanks for your input anyways (to all who replied) !
An alternative solution that I often use is to open the Updater Script in META-INF folder in the ROM's zip and delete first lines, where it gets device model as property.
Obviously it's an UNSAFE operation (because that lines avoid to install ROMs of other phone on mine) but when I'm sure that ROM I've downloaded is for my phone I do it and it works
I am currently on cm-10.1.3 galaxy s2 i9100 intl (International, NOT G). It has CM-based Recovery v6.0.3.6. How do I upgrade to new rom cm-11 nightly?
1. Can the above CM-based Recovery v6.0.3.6 be usd for the flashing? Any link to a detailed post would be appreciated? I have seen references to problems if the above used, or first one has to goto cm-10.2 etc. It looks like cm-10.2 has been pulled back, I do not see that among cm downloads area.
2. Using the built in 'CM Check for updates' I downloaded the latest cm-11 nightly, it went without any error. But I do not see that .zip file anywhere. Where is that supposed to be?
Any help is appreciated.
CqN said:
I am currently on cm-10.1.3 galaxy s2 i9100 intl (International, NOT G). It has CM-based Recovery v6.0.3.6. How do I upgrade to new rom cm-11 nightly?
1. Can the above CM-based Recovery v6.0.3.6 be usd for the flashing? Any link to a detailed post would be appreciated? I have seen references to problems if the above used, or first one has to goto cm-10.2 etc. It looks like cm-10.2 has been pulled back, I do not see that among cm downloads area.
2. Using the built in 'CM Check for updates' I downloaded the latest cm-11 nightly, it went without any error. But I do not see that .zip file anywhere. Where is that supposed to be?
Any help is appreciated.
Click to expand...
Click to collapse
The cm11 zip file will most likely be in your internal sd card. You should be able to flash it from there from recovery, but first I would update the recovery to something more recent
Just download the latest philz recovery from HERE You want the "latest philz" from the third post. Flash this recovery, reboot into recovery(not system), do a full wipe after any backups you want to do, then flash the cm11 zip and compatible gapps(optional)
There are other recoveries you can use, just use the latest one if possible, philz is what I use
noppy22 said:
The cm11 zip file will most likely be in your internal sd card. You should be able to flash it from there from recovery, but first I would update the recovery to something more recent
Just download the latest philz recovery from HERE You want the "latest philz" from the third post. Flash this recovery, reboot into recovery(not system), do a full wipe after any backups you want to do, then flash the cm11 zip and compatible gapps(optional)
There are other recoveries you can use, just use the latest one if possible, philz is what I use
Click to expand...
Click to collapse
Thank you very much for your very helpful reply. I have more to clarify now.
A. Well, I found out why I dont see the cm-11 zip file. (I did search in the *nix console with
'find / -name cm-*.zip'. Couple of the other older zips do show up.). To see the problem I had to watch during the full download; towards the end it has a very brief popup like 'MD5 check failed'. I have no idea why the latest cm-11-20150426-nightly md5 is failing at my end!! The previous 20150412 could not be downloaded either (though I was not there to catch the md5 error, but since there was no file, I assume it failed similarly.) So I tried the 20150406, and that did ask me if I wanted to flash, I cancelled that, and the zip is in the /storage/sdcard0/cmupdater/ . Good.
B. I had never used any philz recovery tool before. So to flash this new recovery, I use the current CM-based Recovery v6.0.3.6, just like I load the gapps zip?
B1. When you say philz, from third post, this one? 8th September 2012, 11:40 PM |#3 ?
It says it 'can be flashed in stock recovery 3e: No Yellow Triangle'. Mine is no longer the stock recovery, since I had updated to the v6.0.3.6. My phone has a Yellow Triangle on boot! Does this mean I cannot use this one? Kindly explain.
So philz recovery is different flavour from the CM-10.1.3 based I have? I had used the flashing only once before to come from the stock to the 10.1.3. Are these two recoveries fully compatible?
C. I had already downloaded the gapps zip for cm-11. The date of that is rather old; I assume there is only one gapps zip version for the cm-11?
D. Since there have been so many cm-11 NIGHTLYs out there, no stable, or monthly, how does one select one of the more stable among them. I really do not need the latest, the primary reason is the main version Andorid upgrade, and I want the ones after the battery drain problem, and the music stop problems were fixed. Is there any place where they give a relative 'goodness' grading to these NIGHTLYs?
Thank you for your continuing help.
noppy22 said:
The cm11 zip file will most likely be in your internal sd card. You should be able to flash it from there from recovery, but first I would update the recovery to something more recent
Just download the latest philz recovery from HERE You want the "latest philz" from the third post. Flash this recovery, reboot into recovery(not system), do a full wipe after any backups you want to do, then flash the cm11 zip and compatible gapps(optional)
There are other recoveries you can use, just use the latest one if possible, philz is what I use
Click to expand...
Click to collapse
This is a continuation of my last reply to you. Double checking: The latest zip file I see at the goo.im downloads site phiilz_touch->CWM_Advanced_Editiion->i9100 is
philz_touch_6.48.4-i9100.zip Sun, 06 Jul 2014 22:47:33 GMT
Should I flash this from my CM-based Recovey v6.0.36 ?. After this flash, i suppose I can do a regular phone booting also, before flashing the cm-11? Thank you.
CqN said:
This is a continuation of my last reply to you. Double checking: The latest zip file I see at the goo.im downloads site phiilz_touch->CWM_Advanced_Editiion->i9100 is
philz_touch_6.48.4-i9100.zip Sun, 06 Jul 2014 22:47:33 GMT
Should I flash this from my CM-based Recovey v6.0.36 ?. After this flash, i suppose I can do a regular phone booting also, before flashing the cm-11? Thank you.
Click to expand...
Click to collapse
The latest philz is correct - 6.48.4. Yes you can flash it from your recovery, it is just an updated version of the v6.0.3.6, something like 6.0.4.something with touch ui. It will work flashing later android versions where the earlier one may not. Just flash it and reboot straight back into recovery when you are ready to do your backups, wipes and installs.
The nightly cm11's are all very stable at this stage; I would download the latest, but the more important bug fixes were implemented from about mid january(eg. fpbug fix). Anything after that would be ok. The gapps, I would download the latest just before I flashed the rom, you are better off with the latest play services etc. As long as they are compatible to 4.4.4, you can choose whatever gapps you want. I like minimal gapps by @jajb for example, but it's up to you. HERE are most of the gapps available at the moment.
If you can I would download the rom by pc. You are recommended to check the md5 sum whenever you download roms/gapps to make sure the download was successful
noppy22, Thank you. That clears up many things. The link to the gapps is a big help. I had previously read somewhere that my phone needed a small foot print gapps, because the system (?) partition was ony about 500mb. That was what I had downloaded, but I can check the newer ones.
How do I check the md5 checksum after the download? I have access to the terminal, and I can use minimal *nix commands, once i know the utility name At philz, there were .zip and .zip.md5 of the same version date. Can I flash either one? I know, as I mentioned in two msgs ago, when I use the system download of nightly, it automatically checks the md5, and saves only if it is correct. But I simply downloaded the gapps, and the .zip of he philz, so I do not know how to check the md5. Info-zip versions of zip has their own integrity check with unzip -t, but the unzip in busybox of Android appears minimal without those features. Thank you agian, I am almost ready to upgrade, as soon as I hear back from you
CqN said:
noppy22, Thank you. That clears up many things. The link to the gapps is a big help. I had previously read somewhere that my phone needed a small foot print gapps, because the system (?) partition was ony about 500mb. That was what I had downloaded, but I can check the newer ones.
How do I check the md5 checksum after the download? I have access to the terminal, and I can use minimal *nix commands, once i know the utility name At philz, there were .zip and .zip.md5 of the same version date. Can I flash either one? I know, as I mentioned in two msgs ago, when I use the system download of nightly, it automatically checks the md5, and saves only if it is correct. But I simply downloaded the gapps, and the .zip of he philz, so I do not know how to check the md5. Info-zip versions of zip has their own integrity check with unzip -t, but the unzip in busybox of Android appears minimal without those features. Thank you agian, I am almost ready to upgrade, as soon as I hear back from you
Click to expand...
Click to collapse
Yes you are generally better off with a smaller gapps package due to the smaller /system in the s2, more so in the newer lollipop roms.
You can check the md5 in a variety of ways, google will tell you ways to if you want to search, and there are apps in the market that check for you. I personally use hashtab, which you download to your pc. It gives you a tab in "properties" that allows you to compare the md5 value against the download site
Thank you. I got my s2 running on 4.4.4, thanks to your help. Everything went fine; I will reload another newer 'small' gapps pkg soon.
As for the md5 check, I was wondering if there is a way to do that from the phone (after a download) or using philz recovery, after download of a .zip.
CqN said:
Thank you. I got my s2 running on 4.4.4, thanks to your help. Everything went fine; I will reload another newer 'small' gapps pkg soon.
As for the md5 check, I was wondering if there is a way to do that from the phone (after a download) or using philz recovery, after download of a .zip.
Click to expand...
Click to collapse
Just go to play store and search for "md5 checker". There are several there. Sorry I haven't used any, so can't recommend but they should be able to give you a reference point
I have run into a problem, and I am stuck. While playing with the setting of profiles, I lost wifi, and the cell connection permanently. It is possible there is bug in the new profile version. Anyway, I flashed again the same nightly (after wipe for loading a new rom), and then this time without the gapps re-flashing, booted the system up. Both the wifi and the cell connected this time. Of course there was no google apps. So, I reflashed the philz advanced (the cm flash always gets rid of the philz advanced), then added the same apps pkg as before. But then when I booted the system up, both the wifi and the cell were not connecting!!
Any suggestions? Thank you.
PS. A related question. Does philz provide a way to save all the installed up and their setting to the external sdcard, and then reboot it? I am particularly interested in the settings save and restore.
CqN said:
I have run into a problem, and I am stuck. While playing with the setting of profiles, I lost wifi, and the cell connection permanently. It is possible there is bug in the new profile version. Anyway, I flashed again the same nightly (after wipe for loading a new rom), and then this time without the gapps re-flashing, booted the system up. Both the wifi and the cell connected this time. Of course there was no google apps. So, I reflashed the philz advanced (the cm flash always gets rid of the philz advanced), then added the same apps pkg as before. But then when I booted the system up, both the wifi and the cell were not connecting!!
Any suggestions? Thank you.
PS. A related question. Does philz provide a way to save all the installed up and their setting to the external sdcard, and then reboot it? I am particularly interested in the settings save and restore.
Click to expand...
Click to collapse
I don't know about the connection problems, you could post the problem in the cm11 thread as it is more specific to that rom. I have heard problems in cm12 with using gapps not released by cm, so you could try cm gapps HERE
Other than using the backup feature of philz, there isn't really any option to save settings. You could check out titanium backup from the market. It has the most comprehensive features for backing up apps and settings, although I have had problems with re-installing stuff using it, but plenty of people swear by it....
Hey guys
I installed CM 13.0 (2016/01/02) on my i9300
Then installed GApps and everything was working fine
TWRP Recovery and SU were installed too
When I tried to open SU though (to enable root options) it said that SU Binary was not installed and that I had to manually re-root it
I used the CF-Auto-Root method but I still got the same message
Then I remember that I had installed a Kernel on my S4 i9500 when I had updated it to CM 12.1
So I googled and downloaded SiyahKernel v1.9.1
Now my phone is stuck on the boot-up. I get the S3 logo, then a purple eye and then a blank screen
I tried booting into recovery and reinstalling CM 13 but it just closes after displaying "Installing update"
Download mode re-rooting doesn't remove the kernel
Another website suggested I use another kernel but I wanted to get help before I did any more stupid things
Any help is appreciated
Joserin said:
Hey guys
I installed CM 13.0 (2016/01/02) on my i9300
Then installed GApps and everything was working fine
TWRP Recovery and SU were installed too
When I tried to open SU though (to enable root options) it said that SU Binary was not installed and that I had to manually re-root it
I used the CF-Auto-Root method but I still got the same message
Then I remember that I had installed a Kernel on my S4 i9500 when I had updated it to CM 12.1
So I googled and downloaded SiyahKernel v1.9.1
Now my phone is stuck on the boot-up. I get the S3 logo, then a purple eye and then a blank screen
I tried booting into recovery and reinstalling CM 13 but it just closes after displaying "Installing update"
Download mode re-rooting doesn't remove the kernel
Another website suggested I use another kernel but I wanted to get help before I did any more stupid things
Any help is appreciated
Click to expand...
Click to collapse
Looks like you totally screwed it up. Siyah on CM13?! you gotta be kidding me. Never ever install siyah again unless you're on stock ROM. Now I recommend 2 methods to you:
1. Backup efs and put it on your PC if you didn't back it up before. Full wipe your phone using twrp. Then extract the CM13 zip file on your PC then grab the boot.img file to an SD and put it on your phone and flash it using twrp. It will recover the stock CM13 kernel and then try to flash your CM13 zip. Better to download the updated ones. Be sure to use the latest twrp. And always use CM13 official root in developer options, trust me it's better.
2. If you couldn't flash CM13 again the only way I recommend is to flash stock using odin and then flash from the ground and bring your phone up.
JohnSmit268 said:
Looks like you totally screwed it up. Siyah on CM13?! you gotta be kidding me. Never ever install siyah again unless you're on stock ROM. Now I recommend 2 methods to you:
1. Backup efs and put it on your PC if you didn't back it up before. Full wipe your phone using twrp. Then extract the CM13 zip file on your PC then grab the boot.img file to an SD and put it on your phone and flash it using twrp. It will recover the stock CM13 kernel and then try to flash your CM13 zip. Better to download the updated ones. Be sure to use the latest twrp. And always use CM13 official root in developer options, trust me it's better.
2. If you couldn't flash CM13 again the only way I recommend is to flash stock using odin and then flash from the ground and bring your phone up.
Click to expand...
Click to collapse
It's okay I fixed it. I installed QS i9300 and then re-flashed CM and GApps. But the SuperSU is still bugged
A cursory reading said that CM is auto-rooted on stable versions and there is no stable version of CM 13 for the i9300 yet so I guess that might be the issue. The phone's working fine now, just no root access :3
Joserin said:
It's okay I fixed it. I installed QS i9300 and then re-flashed CM and GApps. But the SuperSU is still bugged
A cursory reading said that CM is auto-rooted on stable versions and there is no stable version of CM 13 for the i9300 yet so I guess that might be the issue. The phone's working fine now, just no root access :3
Click to expand...
Click to collapse
You read it wrong. It already have internal root. Go to setting--> about device and then tap build number constantly to enable developer settings. There you can find root access options. Turn it on for apps only or adn and apps and done.
Thank me if I helped you.:good:
JohnSmit268 said:
You read it wrong. It already have internal root. Go to setting--> about device and then tap build number constantly to enable developer settings. There you can find root access options. Turn it on for apps only or adn and apps and done.
Thank me if I helped you.:good:
Click to expand...
Click to collapse
I already did that.. Root Checker Basic says I do not have proper root access and the TWRP Manager tool also says I do not have root
It is really weird. I'm on i9300 official nightlies and have working root!
I rooted my S3 with this (by m0xx) https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
I downloaded the 20160102 Nightly from this website https://download.cyanogenmod.org/?device=i9300
GApps from this website (ARM, 6.0, Stock) http://opengapps.org/
and TWRP via ODiN with https://twrp.me/devices/samsunggalaxys3internationalexynos.html (twrp-2.8.6.1-i9300.tar)
Idk if I did anything wrong or downloaded an older version... I know there's TWRP 2.8.7 but I dunno how to install the img file, I knew tar would be compatible with ODiN
Joserin said:
I rooted my S3 with this (by m0xx) https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
I downloaded the 20160102 Nightly from this website https://download.cyanogenmod.org/?device=i9300
GApps from this website (ARM, 6.0, Stock) http://opengapps.org/
and TWRP via ODiN with https://twrp.me/devices/samsunggalaxys3internationalexynos.html (twrp-2.8.6.1-i9300.tar)
Idk if I did anything wrong or downloaded an older version... I know there's TWRP 2.8.7 but I dunno how to install the img file, I knew tar would be compatible with ODiN
Click to expand...
Click to collapse
If twrp offers to root then don't do that method. Flash superSU 2.4.6.zip and on reboot you will see the app logo in your drawer or if not there it will be above developer options in settings. Open and allow it to update binary.
kush2.0 said:
If twrp offers to root then don't do that method. Flash superSU 2.4.6.zip and on reboot you will see the app logo in your drawer or if not there it will be above developer options in settings. Open and allow it to update binary.
Click to expand...
Click to collapse
Already tried that. SU binary just doesn't update. I even downloaded the Update zip and flashed from recovery, it still asks to update the binary after reboot. There is no TWRP option to update the binary either, it directly goes to the normal method and fails everytime. Tried like 20 times probably
I'd say flash back to stock and start over. Installing siyah probably borked something.
shivadow said:
I'd say flash back to stock and start over. Installing siyah probably borked something.
Click to expand...
Click to collapse
The only reason I installed Siyah was because the binary wasn't installed. Multiple attempts to root didn't fix the issue.
Also I did flash stock ROM because after installing Siyah the phone wouldn't go past the S3 logo screen
What recovery version are you using then?? ??
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
Joserin said:
The only reason I installed Siyah was because the binary wasn't installed. Multiple attempts to root didn't fix the issue.
Also I did flash stock ROM because after installing Siyah the phone wouldn't go past the S3 logo screen
Click to expand...
Click to collapse
I really dont thing a custom kernel for cm13 aosp roms exists for sgs3 gti9300
kush2.0 said:
What recovery version are you using then?? ??
Click to expand...
Click to collapse
kush2.0 said:
What recovery version are you using then?? ??
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
I really dont thing a custom kernel for cm13 aosp roms exists for sgs3 gti9300
Click to expand...
Click to collapse
Yea I didn't know that before I installed it (it was 3 AM I was frustrated at SU)
Current TWRP version is 2.8.6.1
Joserin said:
Yea I didn't know that before I installed it (it was 3 AM I was frustrated at SU)
Current TWRP version is 2.8.6.1
Click to expand...
Click to collapse
Personally I would download twrp manager from play store if you havnt already got it. Flash/install twrp 2.8.7.X and boot into the newer twrp and flash superSU 2.4.6.zip. Try that before going back to stock.
kush2.0 said:
Personally I would download twrp manager from play store if you havnt already got it. Flash/install twrp 2.8.7.X and boot into the newer twrp and flash superSU 2.4.6.zip. Try that before going back to stock.
Click to expand...
Click to collapse
Uhm TWRP Manager doesn't work without root. Already tried that
@Joserin, you did your very best to make it complicated. Go back to firmware to get a clean base, as said several times before. Firmware doesn't mean a Touchwiz-based custom-ROM! Download it from sammobile.com and follow the instructions on downloadsite.
Joserin said:
Uhm TWRP Manager doesn't work without root. Already tried that
Click to expand...
Click to collapse
Yeah sorry you do need root access. Your probably better of doing what rp158
Said. Your twrp recovery isn't up to date enough to install a new cm13 based ROM.
rp158 said:
@Joserin, you did your very best to make it complicated. Go back to firmware to get a clean base, as said several times before. Firmware doesn't mean a Touchwiz-based custom-ROM! Download it from sammobile.com and follow the instructions on downloadsite.
Click to expand...
Click to collapse
Meh Id rather just let it be for what it is. It's my dad's phone and I just wanted him to have AdAway, he's not much of a tech-head.
Thanks people
No root access to S3 when upgraded to CM 13; affecting full access Ext SDcard
Before upgrading to CM 13 for my I 9300 (Int) I was on CM 11 and I had full root access on my device.
In fact I still have that recovery file which I backed up before upgrading to CM 13.
I was able to get root whenever I typed "SU" within the terminal window.
Then CM 13 became available for my device so I upgraded to it by following a few simple steps.
Most Everything works perfectly ...... except for one important problem !
I no longer have root access on my device !!!
Of course the first obvious fix was to try to enable root access by selecting it within the Developer Options to grant root access to Apps and ADB; but that didn't work. And I have tried numerous other possible solutions: reflashing SuperSU2.67, wiping everything clean and reinstalling CM 13 and Gapps from scratch, and other such recommendations but nothing has worked for this problem.
Some of my apps that need to write to the external SD card are unable to work but the apps work if I change the path to the internal storage.
Whenever I need to delete a file from my external SD using ES File Explorer it forces me to go to the CM File manager to approve the deletion.
I am unable to select "Root Access mode" within the CM File manager.
And my little "$" does not change to "#" when I type "SU" in the terminal window.
So all this is definitely a problem with us simply not having root access to our S3 devices.
I really would like to revive this topic because I am pretty sure that Joserin and I are not alone in this one.
The CM 13 is much nicer than the CM 11 and there must be a way to cross this hurdle.
Joserin, please let us know if by chance you have found a solution.
Thanks to all; awaiting your suggestions ......
kevin.a69 said:
Before upgrading to CM 13 for my I 9300 (Int) I was on CM 11 and I had full root access on my device.
In fact I still have that recovery file which I backed up before upgrading to CM 13.
I was able to get root whenever I typed "SU" within the terminal window.
Then CM 13 became available for my device so I upgraded to it by following a few simple steps.
Most Everything works perfectly ...... except for one important problem !
I no longer have root access on my device !!!
Of course the first obvious fix was to try to enable root access by selecting it within the Developer Options to grant root access to Apps and ADB; but that didn't work. And I have tried numerous other possible solutions: reflashing SuperSU2.67, wiping everything clean and reinstalling CM 13 and Gapps from scratch, and other such recommendations but nothing has worked for this problem.
Some of my apps that need to write to the external SD card are unable to work but the apps work if I change the path to the internal storage.
Whenever I need to delete a file from my external SD using ES File Explorer it forces me to go to the CM File manager to approve the deletion.
I am unable to select "Root Access mode" within the CM File manager.
And my little "$" does not change to "#" when I type "SU" in the terminal window.
So all this is definitely a problem with us simply not having root access to our S3 devices.
I really would like to revive this topic because I am pretty sure that Joserin and I are not alone in this one.
The CM 13 is much nicer than the CM 11 and there must be a way to cross this hurdle.
Joserin, please let us know if by chance you have found a solution.
Thanks to all; awaiting your suggestions ......
Click to expand...
Click to collapse
I flashed QSi9300KK on my phone (with kernel. I forget the name but it was the third option - not Agni or stock) and after that TWRP and then CM13. Everything's working fine now, even root access.
Remember do not pick the first two kernels in the installer, they didn't work correctly. Third one works like a charm.
my mate 2 is still in the original Android version 4.3. I never updated it. Now I am thinking to update the phone to latest Lollipop B322, May I know how I can do it? Will this update reset my phone to the factory mode? How can I still recover my phone to the current state after updated to new Lollipop? Sorry for my naive questions. Thanks in advance for your help!
If your on 148, I think you need to hit an intermediate update first. It will reset your phone to stock, but you can install TWRP backups. Not sure if you can restore old system images. I know the partition sizes get larger on android 5 builds
Sent from my Ascend Mate 2 using Tapatalk
Do clean installs only. So backup everything first. A backup of all apps can be useful as it was for me but some apps from jelly bean didn't work on lollipop and I had to find and alternative. Some apps just had errors and I just had to re downoad them from the play store. So backup first. Also the custom recovery you have on 4.3 will need to be updated for newer ROM on this phone. Use your old twrp first to back up your stock 4.3 first.
Then go like this:
Build 148 ->
Build 309 (lollipop)
Factory reset (repartitions internal storage) ->
Build 322 (gives you new bootloader) ->
Factory reset (so all is ready) ->
All set to install custom ROM. Update your custom recovery to the one the ROM you want requires.
Remember to do clean installs and wipe cache and davlik. If you use xposed flash the ROM, Gapps and xposed then so you don't have to wait on Android to rebuild the davlik cache later when you've restored your 100+ apps (takes a while).
@superbass311 made a bunch of YouTube videos to get you updated. They're in the how to guide thread
http://forum.xda-developers.com/showpost.php?p=61682557&postcount=7
how can I root official b322 ?
thanks
notoriouspk said:
how can I root official b322 ?
thanks
Click to expand...
Click to collapse
If I remember right you can install a custom recovery TWRP and then boot into TWRP and it will ask if you want to root. There are other options to root the phone as well. I just flashed from B322 -> custom rom which was already rooted. If you're staying on stock b322 though I think TWRP will do it for you.
arcadesdude said:
Do clean installs only. So backup everything first. A backup of all apps can be useful as it was for me but some apps from jelly bean didn't work on lollipop and I had to find and alternative. Some apps just had errors and I just had to re downoad them from the play store. So backup first. Also the custom recovery you have on 4.3 will need to be updated for newer ROM on this phone. Use your old twrp first to back up your stock 4.3 first.
Then go like this:
Build 148 ->
Build 309 (lollipop)
Factory reset (repartitions internal storage) ->
Build 322 (gives you new bootloader) ->
Factory reset (so all is ready) ->
All set to install custom ROM. Update your custom recovery to the one the ROM you want requires.
Remember to do clean installs and wipe cache and davlik. If you use xposed flash the ROM, Gapps and xposed then so you don't have to wait on Android to rebuild the davlik cache later when you've restored your 100+ apps (takes a while).
@superbass311 made a bunch of YouTube videos to get you updated. They're in the how to guide thread
http://forum.xda-developers.com/showpost.php?p=61682557&postcount=7
Click to expand...
Click to collapse
arcadesdude said:
If I remember right you can install a custom recovery TWRP and then boot into TWRP and it will ask if you want to root. There are other options to root the phone as well. I just flashed from B322 -> custom rom which was already rooted. If you're staying on stock b322 though I think TWRP will do it for you.
Click to expand...
Click to collapse
thanks for ur response Twrp asked if I want to root it ..it booted fine but no SU ...checked root it wasn't there ....at the moment I am running cm 13.0 rooted which works fine ...can u give me a link for stock rooted B322 ? thanks
btw which is better cm 13 or B322 rooted ?
notoriouspk said:
thanks for ur response Twrp asked if I want to root it ..it booted fine but no SU ...checked root it wasn't there ....at the moment I am running cm 13.0 rooted which works fine ...can u give me a link for stock rooted B322 ? thanks
btw which is better cm 13 or B322 rooted ?
Click to expand...
Click to collapse
If TWRP root didn't work you can flash SuperSU.zip file using TWRP.
http://forum.xda-developers.com/ascend-mate2/help/how-one-root-upgraded-to-5-1-t3148167
http://androiding.how/how-to-flash-supersu-using-twrp-recovery-and-root-any-android-device/
A limitation of B322 over a custom rom like CM is that Xposed doesn't work on B322. So if you want lots of features and customization go with a custom rom like CM13 (which I will eventually be upgrading to it is just a lot of work to migrate 200+ apps & settings lol). A positive of B322 is EMUI (Huawei's stock rom aka B322) is extra battery life. I hear that CM13 is just as good in that regard but I haven't tried it yet. So I'd say a custom rom would be better than stock B322 (even if it is rooted) just because of the ability to use Xposed.
Thank you so much for your reply! I am still having two questions:
1. Before upgrade, i should backup data. Can I just use the backup function in handset which i found from Settings/About phone/System Update/Local Update/? I don't know about TWRP.
2. to upgrade from B148 to B322, can I just follow this instruction: http://consumer.huawei.com/us/support/manuals/detail/index.htm?id=52025&key4=mate 2
4.1 Force upgrade
---Step 1. A MICRO SD card of 4G or more should be available. The MICRO SD card
made by Sandisk, Kingstone, or Kingmax is recommended.
---Step 2. Format the MICRO SD card (This operation is optional).
If your phone’s system is B3XX, you should skip Step 3 and Step 4.
---Step 3. Copy the Software: recovery package file UPDATE.APP and main package file
UPDATE_VENDOR.APP to a directory named dload.
---Step 4. Copy the entire dload folder (with UPDATE.APP and
UPDATE_VENDOR.APP in it) to the root directory of the MICRO SD card.
If your phone’s system is B126 or B148, you should skip Step 5.
---Step 5. Copy the upgrade package UPDATE_VENDOR.APP to a directory named
dload and copy the dload folder to the root directory of the MICRO SD card.
---Step 6. Make sure your handset is power off. Insert the MICRO SD card into the
handset. Press the VOLUME UP and VOLUME DOWN keys and POWER key to
power on the phone(picture4.1.1) , when the HUAWEI logo is showed , release
the POWER key and keep pressing the VOLUME UP and VOLUME DOWN
keys(picture 4.1.2) until your phone is entered the Software Upgrade
Software Upgrade Guideline
2015-9-3 Page 5, Total8
Mode(picture 4.1.3).
4.1.1 4.1.2
4.1.3
---Step 7. When the progress bar stops, your handset will reboot and enter the new
system.
Thanks!!
arcadesdude said:
Do clean installs only. So backup everything first. A backup of all apps can be useful as it was for me but some apps from jelly bean didn't work on lollipop and I had to find and alternative. Some apps just had errors and I just had to re downoad them from the play store. So backup first. Also the custom recovery you have on 4.3 will need to be updated for newer ROM on this phone. Use your old twrp first to back up your stock 4.3 first.
Then go like this:
Build 148 ->
Build 309 (lollipop)
Factory reset (repartitions internal storage) ->
Build 322 (gives you new bootloader) ->
Factory reset (so all is ready) ->
All set to install custom ROM. Update your custom recovery to the one the ROM you want requires.
Remember to do clean installs and wipe cache and davlik. If you use xposed flash the ROM, Gapps and xposed then so you don't have to wait on Android to rebuild the davlik cache later when you've restored your 100+ apps (takes a while).
@superbass311 made a bunch of YouTube videos to get you updated. They're in the how to guide thread
http://forum.xda-developers.com/showpost.php?p=61682557&postcount=7
Click to expand...
Click to collapse
Best to have a full system backup using TWRP. Also having a full backup from Titanium Backup will allow you to restore apps which can be faster than installing them over. If you don't have too many apps it isn't a big deal. It does let you save app settings.
Also use an app to back up phone log and sms if you want that history.
I don't know about the built in backup. Haven't used it.
piapiaworld said:
Thank you so much for your reply! I am still having two questions:
1. Before upgrade, i should backup data. Can I just use the backup function in handset which i found from Settings/About phone/System Update/Local Update/? I don't know about TWRP.
2. to upgrade from B148 to B322, can I just follow this instruction: http://consumer.huawei.com/us/support/manuals/detail/index.htm?id=52025&key4=mate 2
...
Click to expand...
Click to collapse
You can do that. I think that will work. You might have to flash it twice if there are issues after the first time. Then once it is B322 do a factory reset/restore just in case as well. All data is lost in the process of upgrading.
arcadesdude said:
If TWRP root didn't work you can flash SuperSU.zip file using TWRP.
http://forum.xda-developers.com/ascend-mate2/help/how-one-root-upgraded-to-5-1-t3148167
http://androiding.how/how-to-flash-supersu-using-twrp-recovery-and-root-any-android-device/
A limitation of B322 over a custom rom like CM is that Xposed doesn't work on B322. So if you want lots of features and customization go with a custom rom like CM13 (which I will eventually be upgrading to it is just a lot of work to migrate 200+ apps & settings lol). A positive of B322 is EMUI (Huawei's stock rom aka B322) is extra battery life. I hear that CM13 is just as good in that regard but I haven't tried it yet. So I'd say a custom rom would be better than stock B322 (even if it is rooted) just because of the ability to use Xposed.
Click to expand...
Click to collapse
Thanks for those important pointers and the OP for this topic.
I also like my 2 year old HAM2 so much i just picked up another one as a fallback device perhaps if not daily handset.
I will leave that one JellyBean but i do plan to upgrade the next one to Lollipop 322 i hope.
On the old Mate 2 i flashed through TWRP the very latest SuperSU zip 2.76 i think.
I assume it's best to always use the latest version of it? Is that ok?
Mirror-Mirror said:
Thanks for those important pointers and the OP for this topic.
I also like my 2 year old HAM2 so much i just picked up another one as a fallback device perhaps if not daily handset.
I will leave that one JellyBean but i do plan to upgrade the next one to Lollipop 322 i hope.
On the old Mate 2 i flashed through TWRP the very latest SuperSU zip 2.76 i think.
I assume it's best to always use the latest version of it? Is that ok?
Click to expand...
Click to collapse
I also have a backup HAM2...very useful phone and must props to the devs for working on all the custom recoveries, roms and apps which help make our phones really customizable and usable.
Yes. Update SuperSU using the zip in TWRP 'install.' I just upgraded my own phone to CM13.0 (snapshot) and it fixed some issues (with other issues remaining...always a tradeoff lol!). SuperSu latest version works great! It's a good idea to use the newest version but remember if it isn't broke why take the chance to upgrade it and make it broken?
arcadesdude said:
I also have a backup HAM2...very useful phone and must props to the devs for working on all the custom recoveries, roms and apps which help make our phones really customizable and usable.
Yes. Update SuperSU using the zip in TWRP 'install.' I just upgraded my own phone to CM13.0 (snapshot) and it fixed some issues (with other issues remaining...always a tradeoff lol!). SuperSu latest version works great! It's a good idea to use the newest version but remember if it isn't broke why take the chance to upgrade it and make it broken?
Click to expand...
Click to collapse
It's been a long time since I bothered with ROM's, rooting etc. but another MT2-L03 in the stable demanded to get those hands dirty again.
As usual I errored some things a little, lost root, and even managed to muff TWRP backups with Error 255 or whatever. But Mate 2 is ever so forgiving. It was just a matter of reflashing the Stock Recovery and then firmware, Factory Reset, and install anew the UPDATE.APP+VENDOR (aka:Lollipop!) redo which cleaned everything out so that TWRP 3.02 installed and backed up as expected as well as ROOTED!! :good:
It took getting onboard the L24-LIW Honor 5X to make me appreciate the Mate 2 even more.
Hello i wanted to Flash Lineage Os on my s2 but ran into some problems. I came from omnirom with twrp 2.7.1.0 installed.
So the flash process hung itself up i tried again and it didnt work.
Well i suppose the bootloader is unlocked cause i flashed omnirom right.
Since i already deleted omnirom i cant check now with the dialpad.
So I thought about updating twrp but since its not after 2.8.4 i cant flash .img files.
I would prefer to flash it without heimdall cause i have only strangely configured computers available.
So I tried to flash twrp 3.0. 4 or something like this which I found as a zip file the installation runs just fine says it was successful but after rebooting to recovery it is 2.7 again.
I dont necessarily want to update twrp if i can flash lineage but i guess i have to?
Are there any recommendations for a lost soul.
All the best
Sorry for the false place for this maybe someone can move it to the right spaxe thx
Swarion said:
Hello i wanted to Flash Lineage Os on my s2 but ran into some problems. I came from omnirom with twrp 2.7.1.0 installed.
So the flash process hung itself up i tried again and it didnt work.
Well i suppose the bootloader is unlocked cause i flashed omnirom right.
Since i already deleted omnirom i cant check now with the dialpad.
So I thought about updating twrp but since its not after 2.8.4 i cant flash .img files.
I would prefer to flash it without heimdall cause i have only strangely configured computers available.
So I tried to flash twrp 3.0. 4 or something like this which I found as a zip file the installation runs just fine says it was successful but after rebooting to recovery it is 2.7 again.
I dont necessarily want to update twrp if i can flash lineage but i guess i have to?
Are there any recommendations for a lost soul.
All the best
Sorry for the false place for this maybe someone can move it to the right spaxe thx
Click to expand...
Click to collapse
Please follow one of the guides available, like this one, or the one in my signature.
You have to be aware that twrp 3 requires kernel isorec support, so you must have a kernel that supports isorec, and also you must have a 1GB system partition to be able to install any nogut or mm rom.
thank you so much managed to find this guide before you answered.
anyway thanks so much my s2 is running lineage smoothly and now we saved some piece of electronics of garbage to early the planet and me are thanking you so much for every one having the same problem as me go with philz touch recovery and then flash the twrp you want from there
all the best