Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your beloved i9500 (S4). Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods in the future. Thankyou to 'as i9000' for giving me the stock recovery and stock boot.img. As you can see, it works:
Acuap said:
Hey! I can confirm that it works flawlessly on i9500. No Bricks, instalation went smooth, boots to CWM without problems. Gonna post some more details later. See ya!
Click to expand...
Click to collapse
This has not been tested by me but is reported to work, but is still experimental. I hold no responsibility
for any problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $700.
Put a scare in you didn't I?
I have provided CWM and the stock recovery if you encounter any issues, you can always flash back. It is Odin flashable.
Downloads:
CWM Experimental #2: http://d-h.st/jca
Stock Recovery: http://d-h.st/1OW
Changelog:
Code:
[I][U]Experimental #2[/U][/I]
Mount partitions fix
Backup / restore directories fixed^
Now with touch
[I][U]Experimental #1[/U][/I]
Public release
Thank you. I have always preferred to use CWM for custom recovery. By chance, are you planning to release a i9505 version of CWM. I'm sure one will surface as soon as the official phone release or as soon as the forum splits, but I thought I would ask just in case. Again, thank you.
scott14719 said:
Thank you. I have always preferred to use CWM for custom recovery. By chance, are you planning to release a i9505 version of CWM. I'm sure one will surface as soon as the official phone release or as soon as the forum splits, but I thought I would ask just in case. Again, thank you.
Click to expand...
Click to collapse
Yeah I can build for it too. I just require the stock recovery img and thr stock boot.img
After trying TWRP i don't want to come back to CWM anymore.
Thanks! Gonna try it today and give you info if this works!
emwno said:
Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your beloved i9500 (S4). Thankyou to 'as i9000' for giving me the stock recovery and stock boot.img
This has not been tested by me and is extremely experimental. I hold no responsibility for
any problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $700.
Put a scare in you didn't I?
Anyways I have provided CWM and the stock recovery if you encounter any issues, you can always flash back. It is Odin flashable.
Downloads:
CWM Experimental #1: http://d-h.st/MWE
Stock Recovery: http://d-h.st/1OW
Click to expand...
Click to collapse
Can i add your recovery in my tool?
Inviato dal mio GT-I9070 con Tapatalk 2
Hey! I can confirm that it works flawlessly on i9500. No Bricks, instalation went smooth, boots to CWM without problems. Gonna post some more details later. See ya!
sorg said:
After trying TWRP i don't want to come back to CWM anymore.
Click to expand...
Click to collapse
how long until TWRP is released for the S4 after it's released?
I've always used CWM or CWM-based, so this time I'm going to try TWRP
Ill build that too. after CWM is fixed completely.
KINGbabasula said:
Can i add your recovery in my tool?
Inviato dal mio GT-I9070 con Tapatalk 2
Click to expand...
Click to collapse
sure
PLUG313 said:
how long until TWRP is released for the S4 after it's released?
I've always used CWM or CWM-based, so this time I'm going to try TWRP
Click to expand...
Click to collapse
TWRP is opensource. Technically, SGS4 is not much different from SGS3 (from TWRP point of view). So, it won't be a problem to compile for those who already has SGS4 and has experience with compilation.
sorg said:
TWRP is opensource. Technically, SGS4 is not much different from SGS3 (from TWRP point of view). So, it won't be a problem to compile for those who already has SGS4 and has experience with compilation.
Click to expand...
Click to collapse
I dont think so. I have compiled twrp before many times and it has never worked like that for me. A device tree needs to be set up for the i9500 which im working on to compile twrp (maybe im wrong here)
CWM works flawlessly
If any i9505 user or Korean galaxy s4 user reads this. Please post your devices stock recovery.img and stock boot.img. so thst I can provide CWM for you as well
Experimental #2 released. Now more reliable with backup / restore
emwno said:
I dont think so. I have compiled twrp before many times and it has never worked like that for me. A device tree needs to be set up for the i9500 which im working on to compile twrp (maybe im wrong here)
Click to expand...
Click to collapse
Only very basic device setup required for TWRP. Can try some existing device with the same display resolution and then tweak some parameters.
I will try it by myself when i will get SGS4.
sorg said:
Only very basic device setup required for TWRP. Can try some existing device with the same display resolution and then tweak some parameters.
I will try it by myself when i will get SGS4.
Click to expand...
Click to collapse
I have setup the tree for both building source roms and twrp recovery. Tho, the device tree for roms is incomplete, you can find it here: https://github.com/emwno/android_device_samsung_ja3g . And as for the twrp, I cant build it as ill need to sync source code again. (wiped some directories accidentally)
who have galaxy S4 ???
PM me please
emwno said:
I have setup the tree for both building source roms and twrp recovery. Tho, the device tree for roms is incomplete, you can find it here: https://github.com/emwno/android_device_samsung_ja3g . And as for the twrp, I cant build it as ill need to sync source code again. (wiped some directories accidentally)
Click to expand...
Click to collapse
For SGSIII i build just TWRP binary, not whole recovery image. I like to make my own custom ramfs. I don't use exfat_fuse. I use native samsung kernel modules with simple modification of TWRP to let it think it uses FAT volume. Also i use sdcard binary to mount /sdcard as it mounted in android to avoid files access rights mess. That's why i get only TWRP binary linked statically (instead of dynamically).
I use CM9 source tree. When i got first patches for SGSIII TWRP - they were for CM9. So I continue to use CM9 since there are absolutely no reason to switch to CM10.x in terms of recovery building.
Because my recovery requires some amount of manual work and many tries, i cannot make it without having device in hands. So, i will wait for SGS4.
If there won't be SGS4 tree in CM, then i'm going to use SGSIII's one with adjusted resolution. Everything else should be the same as in SGSIII, IMHO.
sorg said:
For SGSIII i build just TWRP binary, not whole recovery image. I like to make my own custom ramfs. I don't use exfat_fuse. I use native samsung kernel modules with simple modification of TWRP to let it think it uses FAT volume. Also i use sdcard binary to mount /sdcard as it mounted in android to avoid files access rights mess. That's why i get only TWRP binary linked statically (instead of dynamically).
I use CM9 source tree. When i got first patches for SGSIII TWRP - they were for CM9. So I continue to use CM9 since there are absolutely no reason to switch to CM10.x in terms of recovery building.
Because my recovery requires some amount of manual work and many tries, i cannot make it without having device in hands. So, i will wait for SGS4.
If there won't be SGS4 tree in CM, then i'm going to use SGSIII's one with adjusted resolution. Everything else should be the same as in SGSIII, IMHO.
Click to expand...
Click to collapse
I should have thought of that. ... anyways I set up one with the twrp flags. Tried building on a 32bit system but failed to do so. If you want, I can send you everything you will need
Will it support extfat?
Because if extfat is the default file system on a S4,there is no point without it.
... And don't give me no license BS. M$ already got my cash when I put my 649€ on the electronic stores counter.
Sent from my GT I9300
Related
MUST READ BEFORE PROCEED
- This ROM is AP N7100 XXUEMJ2 CP XXUEMJ2 CSC LBEMJ2 and beleved to be PreOfficial
- This ROM have KNOX security effect on bootloader
- I have flashed this ROM with bootloader and even after that I was able to downgrade MG1 ROM as well reflash this ROM again.
- Pre and post flashing EFS backup highly recommended
- This ROM have bootloader and you have to flash separately (Edit : Now you can use this ROM without bootloader too, read installation instruction)
- Recommend to wipe data (factory reset) before flashing ROM
- No one here on XDA is responsible for any bad effect on your device, You are flashing this at your own risk.
Installation Instruction
- Download Prerooted,Deodexed,Zip aligned N7100XXEMJ2 Here Direct MIRROR (Thanks to @MojoManagement ) here is other MIRROR (thank to @kunals.shah for mirror)
- Download Philz recovery if you don't have already. (you can use other but I have tested this one only)
- Copy ROM zip file to SD card and flash it with CWM.
- After Installation of this ROM, you want have WIFI working, You have to Download This Patch and extract to get patch.tar.md5 and flash with PDA tab of Odin to get wifi working. (remember this patch I have tested on MJ2 and using on other ROM may cause serious issue.)
PS : Who have already flashed bootloader and want to get rid of bootloader follow this steps
Downgrade to 4.1.2 (I have tested MG1 My prerooted)
Flash Philz latest recovery
Flash MJ2 from above said link
Flash above said patch
- Reboot normally
Special Notes
- SuperSu zp won't work to root this ROM, though you need not to do it, as This rom is already prerooted.
- If you restore app with Titanium backup, many of applications may not work, but need not to worry, follow this to make it work.
Install terminal emulator from Play store. open it, execute superSu permission and follow below said command
Code:
su
restorecon -R -v /data/data
After this you can close terminal and you will have working app which you have restored with titanium.
Remember you have to follow this everytime you restore data from titanium backup.
To All My Dr.Ketan ROM users, If you can't hold your horse, proceed with this and you will be able to flash my update based on this ROM most probable without wipe, Can't promise but may be before week end.
Reports coming Note3 packages from titoo doesn't working
Click to expand...
Click to collapse
Enjoy latest preofficial ROM
AOSP Theme for this ROM
Flash with CWM.
reserved too
two more
last
Thank you for all your work mate, I know how anoying is to upload 1.6 GB every time
Should we wait for this or continue with your custom rom since it has all N3 stuff and features..since its new so i guess it wont have all features and especially air command.
I am asking this because my bandwidth wont allow me to download after 15gb and i've already used 13gb(dr.ketan's custom rom is already in downlaoding queue)
#Respect
We will reading OP very clearly Before flash it. We understand the risk factor.. Heartfelt thanks bro.. No words to express our feeling .
Seems way too risky with KNOX integrated into this.
if you get cold feet after flashing mj2 rom before entering download mode to flash the new bootloader you can just get back into phillz recovery and restore your last nan i guess,....you have time to decide till then
Mj2? There was a leak I missed?
Thx u very much! Our team still w8 for u @namfat
this is kind of scary. never happen to me before. i was excited to try out the new leak, but having read dr's instruction. i felt uneasy...feels like having an icrap device which can't be downgraded either...
My only mumbling in my head now is..."will the current Note 3 mods work on this pre-release?
There is no reason for not to work
When Samsung will release Kernel Source for this 4.3?
SandeepEmekar said:
When Samsung will release Kernel Source for this 4.3?
Click to expand...
Click to collapse
They need to release 4.3 first ^^
Sent from my GT-N7100 using XDA Premium 4 mobile app
Moe5508 said:
My only mumbling in my head now is..."will the current Note 3 mods work on this pre-release?
Click to expand...
Click to collapse
its working fine. i have already test it
63%
edan1979 said:
its working fine. i have already test it
Click to expand...
Click to collapse
Any difference way to install with MI6 version ? or the same ?
And u try to take some mod with xposed modules, these work well or not :good:
And @dr.ketan what's about ur mod for MI6, it still working well ?
VERIZON SAMSUNG GALAXY S3 (D2VZW)
ATTENTION: I will be stopping official Safestrap support on 9/1/2014. For more information please see:
https://plus.google.com/111109372727398356624/posts/AtoJ3xLj35b
*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
CURRENTLY THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
THANK YOU @BeansTown106 FOR HELPING ME DEBUG THIS
CURRENT PROJECT STATUS:
v3.71: Testing
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.1.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (3-4 on the S3 due to partition size and internal space) for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
Requirement: Allow APK install from Unknown Sources
Download the Safestrap APK
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press under the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting.
By "under", I mean on the touch key portion of the front display on either side of the center button.
DOWNLOADS:
CONFIRM THAT YOU ARE USING A VERIZON WIRELESS SAMSUNG GALAXY S3 (d2vzw)
BETA Safestrap-JFLTEVZW-3.71.apk (updated 2014-01-10)
XDA: XDA Download
Mirror 1: Crackflashers
Mirror 2: Goo.im Download
ALSO DOWNLOAD THE KERNEL MODULES .ZIP THAT MATCHES YOUR BUILD # (FLASH THIS AFTER ROMS):
d2vzw ML1: Download
As of version 3.6x, Safestrap Recovery is now based on TWRP 2.6.3.x. For more on TWRP you can visit their website: http://www.teamw.in/
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
For the purposes of direct user testing I've established a channel on freenode.net IRC: #safestrap
I'm in the channel mostly all the time, but may not be active for discussion.
XDA:DevDB Information
Safestrap Recovery v3.71, Tool/Utility for the Verizon Samsung Galaxy S III
Contributors
Hashcode, DeesTroy & TeamWin
Version Information
Status: Alpha
Created 2014-01-10
Last Updated 2014-08-12
Reserved
Reserved
This is a great feat nice work
Sent from my SCH-I535 using XDA Premium 4 mobile app
This may sound weird, but I prefer having the option of a sort of dual boot, having one safe system that always works, and one for aosp nighties and tinkering. I have an unlocked bootloader, and don't want that to change, can I use safestrap?
rhcp1253 said:
This may sound weird, but I prefer having the option of a sort of dual boot, having one safe system that always works, and one for aosp nighties and tinkering. I have an unlocked bootloader, and don't want that to change, can I use safestrap?
Click to expand...
Click to collapse
Yes, but it's pretty unsupported. And I may need to take a look at the AOSP ramdisk to make sure I re-route internal storage correctly.
NOTE: all ROMs must use the same kernel.
Hashcode said:
Yes, but it's pretty unsupported. And I may need to take a look at the AOSP ramdisk to make sure I re-route internal storage correctly.
NOTE: all ROMs must use the same kernel.
Click to expand...
Click to collapse
So if im using verizons 4.3 update, any other rom i install needs to be on that same 4.3 kernel?
Good job man...
Sent from my SCH-I535 using Tapatalk
Nice work hash glad I could help debug/test for ya
Sent from my SM-N900V using Tapatalk
Good Job Hash !
Dadud said:
So if im using verizons 4.3 update, any other rom i install needs to be on that same 4.3 kernel?
Click to expand...
Click to collapse
Yes this will only work for tw 4.3 roms at the moment
Sent from my SM-N900V using Tapatalk
BeansTown106 said:
Nice work hash glad I could help debug/test for ya
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
OH damn, I forgot to give you a credit in the OP fixing!
Hashcode said:
OH damn, I forgot to give you a credit in the OP fixing!
Click to expand...
Click to collapse
Lol no worries buddy thanks always up for helping with safestrap-izzle lol
Sent from my SM-N900V using Tapatalk
Hashcode said:
Yes, but it's pretty unsupported. And I may need to take a look at the AOSP ramdisk to make sure I re-route internal storage correctly.
NOTE: all ROMs must use the same kernel.
Click to expand...
Click to collapse
That would be awesome if we could.
Sent from my SCH-I535 using xda app-developers app
I dont need to use this but you made roms on my old bionic possible so Thank you for bringing this to the sgs3 community. You sir are a legend.
Sent from my SCH-I535 using Tapatalk
BeansTown106 said:
Yes this will only work for tw 4.3 roms at the moment
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
If 4.3 is on my stock partition do I need to get kernel modules installed, or is that only when moving between versions?
tsachi said:
If 4.3 is on my stock partition do I need to get kernel modules installed, or is that only when moving between versions?
Click to expand...
Click to collapse
Beans sent me the ML1 modules and they are now available in the "Downloads" section as a 2nd flash.zip for when you install ROMs to rom-slots.
http://forum.xda-developers.com/devdb/project/?id=2405#downloads
tsachi said:
If 4.3 is on my stock partition do I need to get kernel modules installed, or is that only when moving between versions?
Click to expand...
Click to collapse
u will need to install the kernel module package as any tw 4.3 roms out now use a custom kernel and have the wrong modules for the stock kernel. i just sent them to hash so he should have in OP soon
@Hashcode - This isn't a request, only a "just curious" question.
if you use TWRP and goo manager, you can 'flash a rom' from goo manager, select the order to be flashed and decide if you want to wipe cache or not. press go and it will reboot the phone, start TWRP and carry out your request (I'm sure your familiar with this, i just wanted to be clear in my question) Is this something that would work with safestrap based on TWRP or is it a no-go since Safestrap is invovled?
Thanks
If i decide to go through with this can I still access the untouched system? Or will I be stuck on one of the 3-4 slots until I Odin Back to full stock?
Hello,
My One SV:
Android 4.2.2 Stock
Moonshine S-Off
HtcDev Unlocked
Custom recovery (TWRP 2.7)
Rooted
When my battery goes to 0% and the phone shuts down, when I plug the USB cable, the phone shows the battery charging sign and then starts in recovery mode, BUT the touchscreen doesn't work, the volume buttons don't work, only the power button works. I always have to wait a few minutes for it to charge up (showing in TWRP 3%+, otherwise it will not power on), remove the battery and the USB cable, put the battery in and power it on, then plug in the USB cable to continue charging.
I have to mention that this was happening also when it was:
Android 4.1.2 Saturn III something mod
S-On
HtcDev Unlocked
Custom recovery (clockworkmod)
Rooted
I've bought this phone second-hand, so I don't know how it behaved when was fully stock.
Thanks,
Sebastian.
The TWRP build you are using doesn't have the proper offmode charging binary. There is a TWRP version which has been built for your device that shall solve this problem for you but I unfortunately do not have the link since it is based on the international K2 variants and I am on a US version.
Another method would be to unpack the TWRP recovery, and unpack your stock 4.2.2 based recovery. Swap the kernel binary from stock recovery over to custom recovery. Then, decompress the ramdisk for both. Swap out the binaries inside the ramdisk as well.
Take note on what arguments you must use to rebuild your stock 4.2.2 based recovery because you must rebuild TWRP using those same arguments. If you do it correctly then this should also resolve your issue.
If you know how to build TWRP from source then I would update the source to reflect more so on 4.2.2. That would be the preferred method if necessary.
Modding.MyMind said:
The TWRP build you are using doesn't have the proper offmode charging binary. There is a TWRP version which has been built for your device that shall solve this problem for you but I unfortunately do not have the link since it is based on the international K2 variants and I am on a US version.
Another method would be to unpack the TWRP recovery, and unpack your stock 4.2.2 based recovery. Swap the kernel binary from stock recovery over to custom recovery. Then, decompress the ramdisk for both. Swap out the binaries inside the ramdisk as well.
Take note on what arguments you must use to rebuild your stock 4.2.2 based recovery because you must rebuild TWRP using those same arguments. If you do it correctly then this should also resolve your issue.
If you know how to build TWRP from source then I would update the source to reflect more so on 4.2.2. That would be the preferred method if necessary.
Click to expand...
Click to collapse
Well, mine is k2_u. Does that change anything?
fbpw131 said:
Well, mine is k2_u. Does that change anything?
Click to expand...
Click to collapse
Nope
Modding.MyMind said:
Nope
Click to expand...
Click to collapse
I've misunderstood, my bad.
Well, I've unpacked my TWRP image, it shows a lot of files, however, if I unpack my "recovery.img" stock recovery, it's "ramdisk" folder it's empty.
Bummer
fbpw131 said:
I've misunderstood, my bad.
Well, I've unpacked my TWRP image, it shows a lot of files, however, if I unpack my "recovery.img" stock recovery, it's "ramdisk" folder it's empty.
Bummer
Click to expand...
Click to collapse
So.. before I started installing ubuntu in dualboot with my windows, I checked old.splatterhand's posts, and as always, he posted the compiled version link in this post: http://forum.xda-developers.com/showthread.php?p=41456540#post41457062
Everything works nice now.
fbpw131 said:
So.. before I started installing ubuntu in dualboot with my windows, I checked old.splatterhand's posts, and as always, he posted the compiled version link in this post: http://forum.xda-developers.com/showthread.php?p=41456540#post41457062
Everything works nice now.
Click to expand...
Click to collapse
The version you have linked is for boost, not for k2u
old.splatterhand said:
The version you have linked is for boost, not for k2u
Click to expand...
Click to collapse
ooops, i guess that's why I lost all my data, it changed the partition somehow and it got wiped.
Yup, bad idea!
old.splatterhand said:
Yup, bad idea!
Click to expand...
Click to collapse
So I should flash the old recovery back, the one with the battery issue
At least that.
And pray that no important partition is wiped!
old.splatterhand said:
At least that.
And pray that no important partition is wiped!
Click to expand...
Click to collapse
Too late for praying, it's back on and seems fine. What should I check to make sure I'm ok?
The ones from here don't work: https://goo.im/devs/OpenRecovery/k2_u/
fbpw131 said:
The ones from here don't work: https://goo.im/devs/OpenRecovery/k2_u/
Click to expand...
Click to collapse
Use the twrp from 1. post of my thread you have linked.
And live with this bug, its only cosmetical. Or try to find someone who can fix it.
old.splatterhand said:
Use the twrp from 1. post of my thread you have linked.
And live with this bug, its only cosmetical. Or try to find someone who can fix it.
Click to expand...
Click to collapse
It's more than a visual bug. I need to pull out the battery for the phone to restart. I'll be living with it.
I've lost only some music and a bloons td 5 savegame but I could have lost much more. I have Sky/One Drive for my photos.
I'll wait and see if someone will ever build it. I should be able to compile it myself, but it's better if someone that really knows those config params do it. I'm done messing, this was as close to a brick as it can get. Lucky me!
fbpw131 said:
It's more than a visual bug. I need to pull out the battery for the phone to restart. I'll be living with it.
Click to expand...
Click to collapse
Don't put your phone off for charging. I never did and never noticed that bug
I'll wait and see if someone will ever build it. I should be able to compile it myself, but it's better if someone that really knows those config params do it. I'm done messing, this was as close to a brick as it can get. Lucky me!
Click to expand...
Click to collapse
I also think so, thats why i never messed with recoveries or kernels
old.splatterhand said:
Don't put your phone off for charging. I never did and never noticed that bug
Click to expand...
Click to collapse
It happens when my battery goes empty. This happens because of another bug.
Well, i don't know how often you use TWRP to flash things or make a backup. But a workaround could be, to use the stock recovery and only use TWRP when you need it.
So, where could find the stock recovery firmware?
Inside this firmware.zip - 33.62 MB
SUPERSTARZ GALAXY ON5
1.
DEBLOATED
2.
DEKNOXED
3.
ROOTED
4.
BUSYBOX
5.
Pixel Launcher
6.
Google Dialer (set as default to use)
Made with android kitchen
Also it comes with Xposed Framework for Samsung Devices
http://www.mediafire.com/?mpcqi611rb42tad
Aroma installer version one
Instructions for flashable zip. Wipe everything except internal storage and Micro Sd. Backup your Rom first!!!. Then flash the build and enjoy Thank you and Credits to all the Android kitchens which provides options for stock Roms until a custom one is made. Credits to [email protected]
http://superstarmobility.weebly.com
http://paypal.me/czarsuperstar/
Don't forget to hit the Thanks button.
DON'T FORGET TO MAKE A NANDROID BACKUP.
DON'T FORGET TO HIT THE THANKS BUTTON AND LEAVE FEEDBACK ON THE ROM
link2sd test recovery images: Beta.
Next post for information.
Link2sd Twrp images blue thank to @ashyx
Recovery tar :http://www.mediafire.com/?ysugtwzzusxgvw7
Recovery image:http://www.mediafire.com/?tln7q406dmejeq5
Beta for now.
Image can be installed through current Twrp or use Odin to flash the tar.
Thanks man! I really like this phone and I'm glad to see that development is starting to pick up..
This is great, now if we can only get this debloated lol
Bloatware
This is partially debloated. When @sandix is done with this it will be really debloated.
[email protected] said:
This is partially debloated. When @sandix is done with this it will be really debloated.
Click to expand...
Click to collapse
That's great, I can't wait.
I've been running it for two days now and haven't had a problem yet. Good work. Can't wait for further development. Couple of questions though, have you been able to set SELinux to permissive? And you said this is a insecure boot.img, what's the advantage of that? I'm still trying to understand the purpose of an insecure boot.img.
Sent from my SM-G550T1 using XDA Labs
N3TiK said:
I've been running it for two days now and haven't had a problem yet. Good work. Can't wait for further development. Couple of questions though, have you been able to set SELinux to permissive? And you said this is a insecure boot.img, what's the advantage of that? I'm still trying to understand the purpose of an insecure boot.img.
Sent from my SM-G550T1 using XDA Labs
Click to expand...
Click to collapse
It's permissive. Notice the red text upon booting up it SECANDROID NOT ENFORCING SO I THINK IT'S PERMISSIVE.
N3TiK said:
I've been running it for two days now and haven't had a problem yet. Good work. Can't wait for further development. Couple of questions though, have you been able to set SELinux to permissive? And you said this is a insecure boot.img, what's the advantage of that? I'm still trying to understand the purpose of an insecure boot.img.
Sent from my SM-G550T1 using XDA Labs
Click to expand...
Click to collapse
https://www.google.com/search?q=ins...d-metropcs-us&sourceid=chrome-mobile&ie=UTF-8
[email protected] said:
I made a flashable zip from my nandroid back up using Super R's Android kitchen.
I have one uploaded : http://www.mediafire.com/?n1qcqfgbqxfmatp
Made with Super R's Android kitchen.
Init support
Rooted (SuperSu)
Busybox
OPTIONAL
This is the flashable on5 kernel zip:
http://www.mediafire.com/?gia58k15lollkgx
Instructions for flashable zip. Wipe everything except internal storage and Micro Sd. Backup your Rom first than after flash restore only data , modem and efs. Thank you and Credits to Super R's Android kitchen which provides options for stock Roms until a custom one is made. Credits to [email protected]
http://superstarmobility.weebly.com
http://paypal.me/czarsuperstar/
The above method is if you want to keep your data that was backed up. The Rom can be flashed and setup as a new device.
Don't forget to hit the Thanks button.
DON'T FORGET TO MAKE A NANDROID BACKUP.
DON'T FORGET TO HIT THE THANKS BUTTON AND LEAVE FEEDBACK ON THE ROM
Click to expand...
Click to collapse
Feedback is welcome.
What is some of the bloat that is removed?
stefanthehuman said:
What is some of the bloat that is removed?
Click to expand...
Click to collapse
I took some Google apps out and METRO apps. I left the device unlock app and mymetro. I am going to take @sandix back up and run it through the kitchen. Than after upload you will have to wait for him to release it since it is his work.
Anything issues to report? I finally finished setting up my build environment using Ubuntu 16 so I am going to see if I can get a custom build going.
Currently running the rom, it's going pretty well.
Kinda sad that the kernel doesn't make SELinux permissive but I guess I can live with it.
UPDATE: Scratch that, the phone completely refuses to boot after install xposed + modules.
Inorizushi said:
Currently running the rom, it's going pretty well.
Kinda sad that the kernel doesn't make SELinux permissive but I guess I can live with it.
UPDATE: Scratch that, the phone completely refuses to boot after install xposed + modules.
Click to expand...
Click to collapse
What version of xposed did you use? You need the one for Samsung devices.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
This should help you out. Be mindful that it takes a long time to boot up.
[email protected] said:
What version of xposed did you use? You need the one for Samsung devices.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
This should help you out. Be mindful that it takes a long time to boot up.
Click to expand...
Click to collapse
Same one I've used since I first setup this phone. I rebooted after enabling the modules and took a quick nap. Phone was still at the metro pcs part of the boot.
Inorizushi said:
Same one I've used since I first setup this phone. I rebooted after enabling the modules and took a quick nap. Phone was still at the metro pcs part of the boot.
Click to expand...
Click to collapse
I would suggest that you reflash and don't use the last xposed modules you enable as that maybe what is keeping the phone from booting up.
If a problem occurs from the Rom zip itself please let me know so I can address the issue and if you figure out a fix let me know. [email protected]
Link2sd Twrp images blue thank to @ashyx
Recovery tar :http://www.mediafire.com/?ysugtwzzusxgvw7
Recovery image:http://www.mediafire.com/?tln7q406dmejeq5
Beta for now.
Image can be installed through current Twrp or use Odin to flash the tar.
TEAM WIN RECOVERY PROJECT (TWRP) version 3.2.1-0
What is TWRP?
Is a fully touch-based custom recovery, which allow you to flash some zip files, backup some partitions and restore the device.
This recovery is specific to Galaxy S6 Edge, model 404SC(SM-G925Z/Japan model, carrier Softbank). But i tested and worked on the Galaxy S6 Edge SCV31/carrier Au KDDI too. I didn't tested in any "Docomo" variant. In case you want to try, send me an message and i will provide the modified "stock kernel", to be able to boot on system.
I recommend to not try to flash this in any internacional model.
Compiled with the latest omni sources 8.1.
https://github.com/omnirom/android_bootable_recovery/
Warning:- I will take no responsability for anything bad, that can happen after flash this recovery!
Flashing this recovery, will trip the KNOX and void the Warranty. If you are ok with that, proceed downloading the recovery, flash with the Odin and enjoy.
In case you want to keep the warranty, this is not for you!
Starting from Lollipop, flashing any custom binary, will end up in stuck at boot. This is due to dm_verity. To be able to boot on system, after flash the TWRP recovery, is necessary to flash an modified kernel.
You can flash my custom permissive kernel for 404SC, from this link:- https://www.androidfilehost.com/?fid=818070582850510939
Kernel source code:- https://github.com/frankbrazillian/android_kernel_samsung_404SC
This kernel is very close as stock, only making this kernel permissive... Compiled with Linaro toolchain gcc 7.
Or if you want to keep the "stock kernel", you can find the link to the model 404SC and SCV31 stock kernel, on the second post.
You will find the link to "stock recovery" too, in case you want to revert.
How to flash the Recovery?
I recommend to flash with Odin3 v3.12~
Link to download Odin:-
https://drive.google.com/file/d/1etF4YP6nJYq-CQEzZJqDv7YS39rQSsbT/view?usp=drivesdk
Note:- After flash the TWRP recovery with Odin, is necessary to put the device in recovery mode(pressing the combo POWER + HOME + VOLUME UP), and swipe to allow modifications when prompted, to make this recovery permanent. If you won't swipe to allow modifications or leave the device restart to system before enter on recovery mode on first boot, the TWRP recovery will be replaced automatically for the "Stock recovery", and you will need to flash the TWRP recovery again.
In case you still have doubts, post an message and i will try to help you.
How to root your device?
Download the latest SuperSu from this link:- (https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip), or the latest Magisk from this thread :- (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) and flash with the TWRP recovery. Since both root tools are systemless, if you wipe the data/factory reset, you will lost the root access. After flash the SuperSU with TWRP recovery, you will see an red message on top of the screen on boot, saying the Kernel is not SEANDROID ENFORCING. Don't worry, this is normal, since the SuperSU will edit the Kernel to be able to get root access.
Feel free to test and let me know if this recovery worked for you...
And please press the "Thanks" button, if this helped you in anyway...
Regards....
Frank.
Contributors:- @Frankbrazillian
Credits:- @Dees_Troy for the Tutorial how to and for share the Source code.
@jcadduono for the Zerolte device tree.
@adipurn for test on SCV31 (Kddi) and confirm is working.
@crzyone01 for test on SC04G (Docomo), and confirm is working.
Version :- 3.2.1-0
Device tree :-
https://github.com/frankbrazillian/android_device_samsung_404SC
Kernel :-
https://github.com/frankbrazillian/android_kernel_samsung_404SC
Omnirom source:-
https://github.com/omnirom/android_bootable_recovery/
Link to download the TWRP recovery:-
https://www.androidfilehost.com/?fid=818070582850510940
md5:- 0d2ab48a6c84d7e8ff2e85d51adee1c9
...............................................................................................................................
UPDATED TO TWRP version 3.2.2-0.
Fixed the Mtp not able to mount when on TWRP.
https://androidfilehost.com/?fid=11050483647474833296
.......................................................................................................................................
UPDATE 2018/07/08
I have add an guide to fix some problems after flash any custom binary or root the device on Nougat.
Check this post to see how to fix...
https://forum.xda-developers.com/showpost.php?p=76994790&postcount=30
......................................................................................................................................
Obs:- In the screenshots, the header color is mustard, but on the device is the real color "blue".
Since this doesn't interfere in anything, i just leave in this way....
Some screenshot's about the Kernel permissive and root.
In case you want to revert back to stock or want to keep the Stock kernel.
After flash the Twrp recovery, is necessary to flash this Stock kernel or the Custom permissive one. Both are already modified to be able to boot on system. If you flash only the Twrp recovery on Stock rom, you will be stuck at boot. This is due to dm-verity.
Link to download the Stock kernel for 404SC
https://drive.google.com/file/d/1ZAcX_Hm4Ln7-ZtEte-TIE4_xEvSQHVXS/view?usp=drivesdk
Link to download the Stock recovery for 404SC
https://drive.google.com/file/d/1_b6Dk95bxIvhjEyM9xuGB1RJER7eHWpJ/view?usp=drivesdk
......................................................................................................................................
Obs:- For the SCV31 model, i didn't compiled yet the Custom permissive kernel, so is necessary to flash this Stock kernel, after flash the Twrp recovery or the device won't boot, due to dm-verity. This stock kernel is modified to be able to boot on system.
Link for download the Stock kernel for SCV31
https://drive.google.com/file/d/1Od4mY9mdC2hQMEM9txDicXfaiPYuqjdH/view?usp=drivesdk
Link for download the Stock recovery for SCV31
https://drive.google.com/file/d/13BlClQdF3lARk2SfJ9hd6ux5Z1VTYENn/view?usp=drivesdk
A Firmware switch Stock & Costum that was Magic. XD
YouLose66 said:
A Firmware switch Stock & Costum that was Magic. XD
Click to expand...
Click to collapse
Yes... I will release an stock and custom edition... You can create an backup with TWRP and switch between both.
YouLose66 said:
A Firmware switch Stock & Costum that was Magic. XD
Click to expand...
Click to collapse
Basically exploiting the buffer between reboots while in DL mode. Smart. Hopefully when they fix it they simply throw an autoreboot after file complete, rather than some obnoxious knoxx hoops to jump through. I'm going to test this on my s6 right now. Actually I bet they end up making a softknoxx that gets flagged after any download, and throws a verify function.
So... Anyone who flashed this recovery on 404SC or SCV31 on Nougat, can give me some feedback?
Any issue? Worked for you?
@adipurn ..... Custom permissive kernel for SCV31 NN, with the deepsleep fixed, already done.
I will send you to test, ok?
Compiled with Gcc linaro 7.
Still need some fixes....
---------- Post added at 06:31 PM ---------- Previous post was at 06:03 PM ----------
[/COLOR]
Frankbrazillian said:
@adipurn ..... Custom permissive kernel for SCV31 NN, with the deepsleep fixed, already done.
I will send you to test, ok?
Compiled with Gcc linaro 7.
Still need some fixes....
Click to expand...
Click to collapse
And now i have no delay incoming messages such as WA etc. and it looks like this fixed it for me.
Phone goes into deep sleep normal and now the battery drain is back to normal.
Thank a lot for your work [emoji4]
Sent from my [device_name] using XDA-Developers Legacy app
adipurn said:
---------- Post added at 06:31 PM ---------- Previous post was at 06:03 PM ----------
[/COLOR]And now i have no delay incoming messages such as WA etc. and it looks like this fixed it for me.
Phone goes into deep sleep normal and now the battery drain is back to normal.
Thank a lot for your work [emoji4]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
My pleasure!
I will be fixing the other issues and send to you test again. Thank's for helping me with the tests!
it works on my scv31, but there are some issues.
1. settings might not display the latest changes
2. can not reboot after flash a custom rom.
3. MTP is not work
450026937 said:
it works on my scv31, but there are some issues.
1. settings might not display the latest changes
2. can not reboot after flash a custom rom.
3. MTP is not work
Click to expand...
Click to collapse
Hi....
What do you mean, settings might not display the latest changes?
About the reboot problem, this can be a problem with the rom itself and not the TWRP. Can you give me the link of the rom you flashed? I need to reproduce the problem.
About the MTP, i'll try to fix it....
Maybe i will build an recovery specific for this model, just in case.
Thank's for your feedback anyway....
Regards....
Frankbrazillian said:
Hi....
What do you mean, settings might not display the latest changes?
About the reboot problem, this can be a problem with the rom itself and not the TWRP. Can you give me the link of the rom you flashed? I need to reproduce the problem.
About the MTP, i'll try to fix it....
Maybe i will build an recovery specific for this model, just in case.
Thank's for your feedback anyway....
Regards....
Click to expand...
Click to collapse
1. setting problem
i changed some settings and had some other operation, when i back to setting screen, i found all(some) setting are reset.
i can't remember the details, maybe just ignore this feedback.
2.reboot problem
i queued rom and kernel task, after all completed, the reboot is frozen in progress.
here is the rom i flashed.
https://forum.xda-developers.com/ga...om-aurora-g920-5-f-s-k-l-t-s8-port-3-t3640762
450026937 said:
1. setting problem
i changed some settings and had some other operation, when i back to setting screen, i found all(some) setting are reset.
i can't remember the details, maybe just ignore this feedback.
2.reboot problem
i queued rom and kernel task, after all completed, the reboot is frozen in progress.
here is the rom i flashed.
https://forum.xda-developers.com/ga...om-aurora-g920-5-f-s-k-l-t-s8-port-3-t3640762
Click to expand...
Click to collapse
I was talking with adipurn who are helping me with tests of the custom kernel and he said, they can flash custom rom with TWRP without any bootloop, but the TWRP are not working with aroma. I need to figured it out, what is necessary to get aroma working on TWRP.
The link of the rom you post, i believe is not for your model... It's for internacional model or some chinese variant. Thats why you got problems...
Untill i fix the compatibility with aroma, try to flash some custom firmware specific for your model SCV31.
As soon as i can fix the mentioned issues, i'll update the thread with the links for download.
Thank's again for your feedback.
Regards......
Frank.
Frankbrazillian said:
I was talking with adipurn who are helping me with tests of the custom kernel and he said, they can flash custom rom with TWRP without any bootloop, but the TWRP are not working with aroma. I need to figured it out, what is necessary to get aroma working on TWRP.
The link of the rom you post, i believe is not for your model... It's for internacional model or some chinese variant. Thats why you got problems...
Untill i fix the compatibility with aroma, try to flash some custom firmware specific for your model SCV31.
As soon as i can fix the mentioned issues, i'll update the thread with the links for download.
Thank's again for your feedback.
Regards......
Frank.
Click to expand...
Click to collapse
Actually the aurora rom work for most model if you flash the right kernel, and i am using it now. ( i reboot device by force )
I can't post outside links, cause i'm new here.
The rom and kernel is downloaded from other post by aurora team( not in xda ),and scv31 is in the support list.
450026937 said:
Actually the aurora rom work for most model if you flash the right kernel, and i am using it now. ( i reboot device by force )
I can't post outside links, cause i'm new here.
The rom and kernel is downloaded from other post by aurora team( not in xda ),and scv31 is in the support list.
Click to expand...
Click to collapse
Don't worry... I think i already know how to get the Aroma installer working with the TWRP recovery.
I will fix the mtp too.
Regards....
I'm going to give this a shot on an old Docomo SC-04G I have lying around. Any tips or suggestions for the process? I see you mentioned about the source code but I'm not sure what I would need to change before re-compiling it. I do not have any experience with making a kernel passive.
crzyone01 said:
I'm going to give this a shot on an old Docomo SC-04G I have lying around. Any tips or suggestions for the process? I see you mentioned about the source code but I'm not sure what I would need to change before re-compiling it. I do not have any experience with making a kernel passive.
Click to expand...
Click to collapse
Hi crzyone... Are you on Nougat already? Did you know how to extract the boot.img and recovery.img from stock rom? If you are, please send me this 2 images to i edit to you be able to boot, after flash the TWRP....
Regards....
Yes, that device is on 7.0 already. 7.0/SC04G0MU1CQF1. No, I don't know how to extract the stock boot.img or recovery.img. Trying to find some instructions on the forums right now.
crzyone01 said:
Yes, that device is on 7.0 already. 7.0/SC04G0MU1CQF1. No, I don't know how to extract the stock boot.img or recovery.img. Trying to find some instructions on the forums right now.
Click to expand...
Click to collapse
That's ok! I will download the rom and extract the images.
After, i'll send to you ok?
Regards....
crzyone01 said:
Yes, that device is on 7.0 already. 7.0/SC04G0MU1CQF1. No, I don't know how to extract the stock boot.img or recovery.img. Trying to find some instructions on the forums right now.
Click to expand...
Click to collapse
Ok... Here is the link to download the stock kernel and stock recovery in case the Twrp won't work on your model... This is specific for the SC-04G model on Nougat.
Kernel:-
https://drive.google.com/file/d/1gEh32YnXxJk5qWgT4WPVtX3vjRGMxivQ/view?usp=drivesdk
Recovery:-
https://drive.google.com/file/d/1X0hRIUgZBKk4PuRLtPrETqFRG3cyFNaq/view?usp=drivesdk
First flash the TWRP recovery with Odin and after flashed, the phone will boot. Don't let the device restart to System.... Put the phone in recovery mode, (Power button + home + volume up). Swipe to allow changes to system. After put the phone in download mode and flash the "modified" stock kernel to be able to boot.
Reboot the device and you are ready to go...
Let me know if worked for you....
I will be uploading an new Twrp version, as soon as i fix the issues..
Press the thanks button if helped and enjoy....