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.
Related
I decided to install the new CM 10.2 with its 4.3 android today. In the guide I was using it also said to install AJK kernel so I did
and now I have everything working except ROOT permissions. And I can't figure out what did I do wrong. Here are the steps I took expecting to have my phone rooted and with cm 10.2 at the end:
1. I installed the new kernel by their official instructions in recovery mode
2. Installed SuperSU in recovery
3. Installed CM 10.2 in recovery
4. Installed GAPPS in recovery
5. rebooted phone
Could you please tell me what am I missing or what did I do wrong? I already rooted my phone before so I can't seem t figure out what am I doing wrong now.
Any help is much appreciated, thank you all.
warriotox said:
I decided to install the new CM 10.2 with its 4.3 android today. In the guide I was using it also said to install AJK kernel so I did
and now I have everything working except ROOT permissions. And I can't figure out what did I do wrong. Here are the steps I took expecting to have my phone rooted and with cm 10.2 at the end:
1. I installed the new kernel by their official instructions in recovery mode
2. Installed SuperSU in recovery
3. Installed CM 10.2 in recovery
4. Installed GAPPS in recovery
5. rebooted phone
Could you please tell me what am I missing or what did I do wrong? I already rooted my phone before so I can't seem t figure out what am I doing wrong now.
Any help is much appreciated, thank you all.
Click to expand...
Click to collapse
go to setting-->about phone-->click multiple times on cynogenmod mod 10.2 then a popup msg appear after that go to devloper option then select root may be ur root disable just check apps+adb now your phone easily access rooted apps
If I help you then hit a thanks button
gauravgymnast08 said:
go to setting-->about phone-->click multiple times on cynogenmod mod 10.2 then a popup msg appear after that go to devloper option then select root may be ur root disable just check apps+adb now your phone easily access rooted apps
If I help you then hit a thanks button
Click to expand...
Click to collapse
Wow. Thank's dude. I'm sure I didn't have to do this before, so weird. Thank you so much
So I just successfully installed CM13 on my i9300. Everything works fine, but I just found out I lost root rights.
I went and downloaded the Super SU app from the PlayStore, launched it and that gave an error that there's no SU binary installed and I need to manually root again.
So I downloaded UPDATE-SuperSU-v2.65-20151226141550.zip, put it on the sdcard, rebooted into CWM Recovery, installed the zip and booted back into the system (when prompted to fix boot I selected no as recommended), but now I STILL HAVE NO ROOT RIGHTS and the Super SU app still gives the same error.
Is there a specific SuperSU.zip I should be installing in recovery to make it work?
Or is something wrong with the recovery and do I need to flash that through Odin? (I don't think this is the case though, as flashing CM13 and gapps went completely fine)
Thanks for any isnight and tips
There is already Root option in developer settings.Can you try it?
ArdaCsknn said:
There is already Root option in developer settings.Can you try it?
Click to expand...
Click to collapse
In Developer Options I have set Root Access to Apps and ADB it didn't give any error, but doesn't seem to be doing anything either... In file manager I can't reach root, Root Checker app fails, Super SU gives than binary error, and another app that requires Root Access says I don't have it as well..
warriotox said:
In Developer Options I have set Root Access to Apps and ADB it didn't give any error, but doesn't seem to be doing anything either... In file manager I can't reach root, Root Checker app fails, Super SU gives than binary error, and another app that requires Root Access says I don't have it as well..
Click to expand...
Click to collapse
Flash rom again and dont flash SuperSu its better now without using SuperSU
I got the same problem. I tried to root with odin again but it didnt work...
Flash cm13, wipe data and cache and flash cm13 again. Cm13 should be pre rooted.
Sent from my HTC One M9 using Tapatalk
Hi Guys, I have the same problem too after CM13. Unfortunately rooting again with ODIN flashed stock recovery back and am stuck on CM13 now with no root and stock recovery. Can someone help please? Below is the detailed description of what happened.
----------------------------
1. My Samsung Galaxy SIII International (I9300) was rooted and I had CM11 stable/snapshot version there since last 2-3 weeks.
2. Yesterday, I tried upgrading the latest CM13 nightly for my device.
3. While doing so, and rebooting, it asked me the normal message "root possibly lost, fix, yes or no". I accidentally pressed no.
4. Then I noticed after CM13 was flashed, that I do not have root access anymore. Please note that at this point in time, I was not aware that it has to be explicitly enabled in developer options.
5. I came to know that I lost root when I tried to boot in to recovery (CWM) to install gapps.
6. Now, under the impression that I do not have root anymore, I tried to root again with Odin as I had been doing all these days.
- By doing that, ODIN removed my custom recovery (CWM) and flashed it with stock recovery.
- Though ODIN said PASS after reboot, I still do not have root access.
7. Removed cache, wipe data, and factory reset, multiple times but no help.
8. Enabled root for both apps and adb in Developer options, but no use.
9. I also tried KINGO root ( a very popular tool for SGS3 these days) but in vain.
10. Now, am stuck with CM13 and stock recovery and unable to do anything with ROM manager or anything else as I do not have root anymore.
11. Am able to install few apks for whatsapp and facebook for now and living with it, but it wouldn't let me install playstore apk too anymore.
Highly appreciate any quick feedback.
same here after rooting once cm13 by developer option, for some reason i had to use hide my root app, now unable to get root back
Its a problem with the s3, it forgets root. The most reliable is chainfire and sticking with a stock rom.
You must:
Wipe to factory,
flash an original rom via odin,
Boot straight to recovery and wipe to factory again,
Flash original rom again,
Boot straight to recovery and wipe to factory,
Allow the phone to boot.
You must flash at least twice and reset to factory at least twice, even tho I sad it thrice, to kill all remnants of the old rooted rom.
Then you can flash chainfire via odin and go from there.
Beamed in by telepathy.
Dear All,
Sorry if am re-posting the same, and as am new here and need an urgent help, started this thread.
1. My Samsung Galaxy SIII International (I9300) was rooted and I had CM11 stable/snapshot version there since last 2-3 weeks.
2. Yesterday, I tried upgrading the latest CM13 nightly for my device.
3. While doing so, and rebooting, it asked me the normal message "root possibly lost, fix, yes or no". I accidentally pressed no.
4. Then I noticed after CM13 was flashed, that I do not have root access anymore. Please note that at this point in time, I was not aware that it has to be explicitly enabled in developer options.
5. I came to know that I lost root when I tried to boot in to recovery (CWM) to install gapps.
6. Now, under the impression that I do not have root anymore, I tried to root again with Odin as I had been doing all these days.
- By doing that, ODIN removed my custom recovery (CWM) and flashed it with stock recovery.
- Though ODIN said PASS after reboot, I still do not have root access.
7. Removed cache, wipe data, and factory reset, multiple times but no help.
8. Enabled root for both apps and adb in Developer options, but no use.
9. I also tried KINGO root ( a very popular tool for SGS3 these days) but in vain.
10. Now, am stuck with CM13 and stock recovery and unable to do anything with ROM manager or anything else as I do not have root anymore.
11. Am able to install few apks for whatsapp and facebook for now and living with it, but it wouldn't let me install playstore apk too anymore.
Highly appreciate any quick feedback.
Many Thanks,
BR,
Shiva
I belive you need to flash the stock 4.3 jellybean rom with odin, and root it afterwards.
Silviu_gs3 said:
I belive you need to flash the stock 4.3 jellybean rom with odin, and root it afterwards.
Click to expand...
Click to collapse
Many Thanks, seems to be a good option and I will try that.
You need a recent version of twrp recovery
rchtk said:
You need a recent version of twrp recovery
Click to expand...
Click to collapse
TWRP 3.0.0..???????????
First of all.. Update TWRP to 3.0.2, you are NOT supposed to see the message that tells you that root is gone, as (official) CM13 includes root from now on.
For root, inside Android go to Settings > Developer Options > Root > Only apps.
Do it via Odin as only 3.0.2 is available in a .tar file (latest version), should not be hard.
Not only that, but upgrading from CM11 to CM13 is not recommended, as it causes multiple compatibility issues with installed apps (afaik).
You are better off with wiping it all and install CM13 Clean, and if you decide to; you must also flash Gapps (optional) directly after CM13 (no reboot).
Read more on the official thread: http://forum.xda-developers.com/gal...t/rom-cyanogenmod-13-nightlies-i9300-t3272811
SGS3 I9300: Root and Custom Recovery lost after CM13 - SOLVED
Dear All,
Thank you for your valuable advice and suggestions. I used ODIN to flash back to stock ROM and now everything works as it is like out of the box. I will root again perhaps in a few days and the flash the stable release of CyanogenMod. Will keep you posted. I wish the Android M snapshot is released by then.
Thanks again,
Cheers,
Shiva
I use clockworkmod to update the binaries in SuperSu but when it end, the cm 13 stop working and stay on the loading screen, so i have to recover the rom.
Someone else have the same problem?
Sorry for my english but i'm from spain.
thanks!
I had this problem as well.
I use RR Marshmallow ROM and whenever I try to flash SuperSU binary (tried multiple versions) from recovery (both TWRP and CWM), I always got stuck at bootloop.
BUT - I found an easy (temporary) solution (SuperSU will still say it needs to update, but root will be working)
After days of having pain by trying to flash Binary I figured out I was doing something wrong.
I had to reflash same ROM again to get out of bootloop (you don't need to do factory reset if you are going to have SAME ROM and SAME version of ROM).
At least root is now working and update notification doesn't bother me anymore.
First download SuperSU from Play Store if you haven't already and then just go to Settings > Developer options > Root access and set it to Apps only. Reboot your phone and voila - every root app will now work and ask for your permissions. Hope I helped! Hope I'll find solution to flash update correctly as well so everything will be in order as it should be.
Forcellrus said:
I had this problem as well.
I use RR Marshmallow ROM and whenever I try to flash SuperSU binary (tried multiple versions) from recovery (both TWRP and CWM), I always got stuck at bootloop.
BUT - I found an easy (temporary) solution (SuperSU will still say it needs to update, but root will be working)
After days of having pain by trying to flash Binary I figured out I was doing something wrong.
I had to reflash same ROM again to get out of bootloop (you don't need to do factory reset if you are going to have SAME ROM and SAME version of ROM).
At least root is now working and update notification doesn't bother me anymore.
First download SuperSU from Play Store if you haven't already and then just go to Settings > Developer options > Root access and set it to Apps only. Reboot your phone and voila - every root app will now work and ask for your permissions. Hope I helped! Hope I'll find solution to flash update correctly as well so everything will be in order as it should be.
Click to expand...
Click to collapse
Thank you so much.
I did it yet but i'm searching for the final fix ^^ that you say works for now, but we have the same problema.
greetings!
pleoncas said:
Thank you so much.
I did it yet but i'm searching for the final fix ^^ that you say works for now, but we have the same problema.
greetings!
Click to expand...
Click to collapse
Glad it works!
Still looking for solution, haven't found one yet. I'm sure I will laugh when I find out how easy it was, yet hard to find out I will let you know if I succeed.
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.