Related
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
Hi. I have an korean exynos galaxy s7 and I'm trying to compile stock kernel source.
The source itself compiles successfully but when I flash it on my device it gets stuck on SAMSUNG logo.
I used stock dtb.img and repacked boot.img with xiaolu's mkboot script.
I've also disabled TIMA, patched ramdisk to disable encryption check but still no luck.
Anyone who knows the solution please reply. My kernel source is here : https://github.com/kykdev/test/commits/herolte
Thanks in advance.
Solved, compiling on linux mint 17.3 was the problem. Switched to Ubuntu 16.04 and now I can boot it.
EDIT: Stuck at boot logo again. damn it.
kykint said:
Solved, compiling on linux mint 17.3 was the problem. Switched to Ubuntu 16.04 and now I can boot it.
Click to expand...
Click to collapse
can you give us the zip to flash.
rfb813 said:
can you give us the zip to flash.
Click to expand...
Click to collapse
Forgot to edit my post. It successfully booted only once. Shortly after its first boot it rebooted suddenly and then, stuck at boot logo again.
나의 SM-G930K 의 Tapatalk에서 보냄
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for Lineage OS is available in the Lineage OS Github repo.
Install instructions:
* Reboot into recovery
* Wipe data, system and cache if it's a fresh install (any rom which is not official Lineage, including Cyanogenmod).
* No wipes required if you're updating from a previous official build of Lineage (wipe cache and dalvik cache recommended).
* Flash ROM and, optionally, Gapps and Root. Reboot.
Download links:
* OfficialROM: https://download.lineageos.org/v521 [nightly]
* Gapps: Open GApps
* Root: https://download.lineageos.org/extras [su (arm)]
Source Code: https://github.com/LineageOS
Version Information
Status: Nightly
Last Updated 2017-04-28
I have flashed your build and all is well so far except for the Developer Options isn't accessable. I only use this for the Advanced reboot options and root access options. Any way to get this accessable or should I wait for the next build? Thanks
Hawksronny said:
I have flashed your build and all is well so far except for the Developer Options isn't accessable. I only use this for the Advanced reboot options and root access options. Any way to get this accessable or should I wait for the next build? Thanks
Click to expand...
Click to collapse
The past couple of builds somehow broke the Developer Options. Im going to guess and say it has something to do with the code for 7.1.2 being merged as there have been a lot of things changed in the Settings repo. Ive been trying to use older Settings and Developer apks but none have worked.
I have narrowed down the boot issue to the sepolicy file inside the ramdisk.
On the latest build developer options is just a white blank screen. . Now I can't figure out how to get into recovery mode, I usually just boot into recovery through adb but I can't use adb without turning on USB debugging
pdxmark78 said:
On the latest build developer options is just a white blank screen. . Now I can't figure out how to get into recovery mode, I usually just boot into recovery through adb but I can't use adb without turning on USB debugging
Click to expand...
Click to collapse
no need to wipe if coming from previous nightly. if u dnt wipe u can keep ur adb and root options without needing to go into developer settings.
to get into recovery hold vol. down and power until the LG screen appears
then let go of the power button ,while still holding the vol dwn. count 1sec then press and hold power again.
you will be brought to a screen asking if u want to favtory reset press yes then yes again.
it will not wipe anything but it will then reboot in recovery
New build up. Going to work you magic
Munns86 said:
New build up. Going to work you magic
Click to expand...
Click to collapse
Unfortunately the older ramdisk isn't going to work with the new builds as they're 7.1.2. We're going to have to wait until the issue is found and fixed in the source. Ive tried every workaround i can think of ive gotten it as far as a bootloop with the device being recognized in adb, monitor etc. going to try and debug see if i can figure out why its looping.
Looks like the last workung nightly is going to be 04/14, for now.
HighRidas said:
Unfortunately the older ramdisk isn't going to work with the new builds as they're 7.1.2. We're going to have to wait until the issue is found and fixed in the source. Ive tried every workaround i can think of ive gotten it as far as a bootloop with the device being recognized in adb, monitor etc. going to try and debug see if i can figure out why its looping.
Looks like the last workung nightly is going to be 04/14, for now.
Click to expand...
Click to collapse
Well thanks all the same. You've done great work. We've pretty much handed the answer to the maintainer that you've found and they still have done nothing.
i'm keep getting update error. update completes around 45%.. then E:unknown command in red... anyone knows what to do? it goes to boot screen, then blank screen... does not boot.
alphakp295 said:
i'm keep getting update error. update completes around 45%.. then E:unknown command in red... anyone knows what to do? it goes to boot screen, then blank screen... does not boot.
Click to expand...
Click to collapse
Try re-downloading sounds like a corrupted file.
Well some possible good news. The next build should be fixed. The problem was cleared on the regression tracker.
New build is up on the official site and is confirmed working
Developer options still freezes. but, if you do not wipe, your settings should remain
v521-Resurrection-Remix-N-v5-8-x-OMS-LG-G-Tab-X-8.0
Recently acquired this nifty little tablet. I've toyed around and upgraded to stock Nougat (v52120f).
I've followed the dirtycow method for rooting and installing TWRP. I am able to successfully sideload latest nightlies of LOS (lineage-14.1-20170505-nightly-v521-signed) and/or Resurrection (RR-N-v5.8.3-20170509-v521-Nightly). After the flash, both my wifi and bluetooth MAC addresses have changed from the original. Restoring back to stock restores the original MAC addresses.
Stock - 5c:af:06:xx:xx:xx
LOS - 00:0a:f5:23:47:54
RR - 00:0a:f5:23:47:54
Anyone else seen this issue?
Hi is there a way to have irda blaster (infrared) working with this ROM? Thanks
jotade said:
Hi is there a way to have irda blaster (infrared) working with this ROM? Thanks
Click to expand...
Click to collapse
if you want to try this kernel out. flash image in recovery. can't guarantee it will work as i don't have anything to test it on but i enabled everything, that I could find, IR-rc related
https://www.mediafire.com/file/07397adkju2on9g/boot.img
HighRidas said:
if you want to try this kernel out. flash image in recovery. can't guarantee it will work as i don't have anything to test it on but i enabled everything, that I could find, IR-rc related
https://www.mediafire.com/file/07397adkju2on9g/boot.img
Click to expand...
Click to collapse
Thanks i will try but flash via fastboot flash boot boot.img? O how. Please let me know
jotade said:
Thanks i will try but flash via fastboot flash boot boot.img? O how. Please let me know
Click to expand...
Click to collapse
in twrp recovery select install image then select the downloaded .img file and select boot.
Information:
The Pitchblack Recovery was released today. I just saw their post in the telegram group, and thought it would be nice to share here too.
Didnt test it yet, and dont know if I have time to do so the next month.
https://sourceforge.net/projects/pitchblack-twrp/files/daisy/
Update Log:
-Updated recovery to android 9
-added sdcard support
-fixed otg
-updated kernel to latest pie
- minor fixes
greetings
Anybody try it yet
one man from 4pda saw what after install this recovery his wifi was broken
eremitein said:
one man from 4pda saw what after install this recovery his wifi was broken
Click to expand...
Click to collapse
From what i have read on other recovery's it seems like a kernal issue at this point on the wifi
This recovery is working fine? No bugs?
did someone try it?? can it decrypt???
foudroid said:
can it decrypt???
Click to expand...
Click to collapse
i doubt that decryption works with this recovery - as there is no single word of decryption within the update log - its sad that there is so so little interest in developing for our really nice a2 lite
ilovebytes said:
i doubt that decryption works with this recovery - as there is no single word of decryption within the update log - its sad that there is so so little interest in developing for our really nice a2 lite
Click to expand...
Click to collapse
On a good note dev has been picking up a lil bit.
i hope you are right an we see some progress with a fully working recovery and then some good roms for the a2 lite - as it is a realy great device for the little money it costs - unfortunatly i am not able to do or at least try some developing myself as i am lacking the mandatory skills to do so
ilovebytes said:
i hope you are right an we see some progress with a fully working recovery and then some good roms for the a2 lite - as it is a realy great device for the little money it costs - unfortunatly i am not able to do or at least try some developing myself as i am lacking the mandatory skills to do so
Click to expand...
Click to collapse
I'm in the same boat lol
Can't boot the image via fastboot, only endless boot animation.
Regarding to wifi the problem probably is, that the wifi kernel module is not compiled or included when building the kernel for the boot.img. This is very important with AB devices, because they use boot partition as recovery and therefore has to include kernel.
opal06 said:
Regarding to wifi the problem probably is, that the wifi kernel module is not compiled or included when building the kernel for the boot.img. This is very important with AB devices, because they use boot partition as recovery and therefore has to include kernel.
Click to expand...
Click to collapse
our device using external wifi module
if you compiled it in kernel zImage then wifi will don't work anyway
Maintainer of PB here,
It's to inform that i rolled out this on the request of some users.
Flashing guide is :
fastboot boot recovery.img
Don't flash the img otherwise you will get wifi issues.
Manish4586 said:
Maintainer of PB here,
It's to inform that i rolled out this on the request of some users.
Flashing guide is :
fastboot boot recovery.img
Don't flash the img otherwise you will get wifi issues.
Click to expand...
Click to collapse
Looking forward to trying does everything work like restore n backup
Manish4586 said:
fastboot boot recovery.img
Click to expand...
Click to collapse
As written above: only endless boot animation. Any ideas?
Thanks!
encryption worked?
You can select sd-card, but it still shows content of internal storage...
So I upgraded to android 10 open beta and now viper4android keeps asking to install the drivers and twrp isnt asking for my password so I cant access storage or anything from twrp
I am on twrp 3.3.1-4
Did you try removing the password from your current rom.
Robert235 said:
Did you try removing the password from your current rom.
Click to expand...
Click to collapse
Just tried and still nothing it comes up with swipe to allow modifications and I do that but internal storage is still 0
That's Strange, I remember both on the OnePlus 6 and OnePlus 7 Pro when switching from stock ROM to AOSP having a password used to cause issues with twrp. I wonder if the new version of twrp installer will work.
I wanna try a factory reset but it wont let me
D.Va said:
I am on twrp 3.3.1-4
Click to expand...
Click to collapse
Your on the wrong twrp version.
Flash the latest unofficial twrp.
twinnfamous said:
Your on the wrong twrp version.
Flash the latest unofficial twrp.
Click to expand...
Click to collapse
I would but I can't and I've never had issues with the official twrp builds I personally think it's just the beta causing some weird encryption bug
D.Va said:
I would but I can't and I've never had issues with the official twrp builds I personally think it's just the beta causing some weird encryption bug
Click to expand...
Click to collapse
Why can't you?
The unofficial is maintained by the same person as official.
Also it's not a bug. It's the change in encryption /decryption. So if you won't use unofficial then you can wait patiently for official to update there source and build.
twinnfamous said:
Why can't you?
The unofficial is maintained by the same person as official.
Also it's not a bug. It's the change in encryption /decryption. So if you won't use unofficial then you can wait patiently for official to update there source and build.
Click to expand...
Click to collapse
I can't cause my twrp is showing Internal Storage as 0 and won't mount stuff and I can't wipe
The unofficial twrp comes with a .img file and zip. Use a PC to boot into the .img with fastboot then use that booted image which should allow decryption and flash the zip.
D.Va said:
I can't cause my twrp is showing Internal Storage as 0 and won't mount stuff and I can't wipe
Click to expand...
Click to collapse
Do you have magisk installed?
Use the twrp installer zip.
twinnfamous said:
Your on the wrong twrp version.
Flash the latest unofficial twrp.
Click to expand...
Click to collapse
Solved. NVM, it just popped out as soon as I asked the stupid question.
Can you please tell me where can I find the unofficial twrp? It's like a freaking unicorn, evading my desperate searches.
stefanaroman88 said:
Solved. NVM, it just popped out as soon as I asked the stupid question.
Can you please tell me where can I find the unofficial twrp? It's like a freaking unicorn, evading my desperate searches.
Click to expand...
Click to collapse
Look here. https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322