[RECOVERY][EXYNOS] CWM for the Samsung Galaxy S5 G900H - Galaxy S 5 Android Development (Exynos)

Clockworkmod Recovery for the SM-G900H Exynos S5
Note: No one but yourself is responsible for what you do to your device.
People to Thank
Clockworkmod/Koush - for thier awesome recovery
Phil3759 - for hooking me up with his repo
Known Issues
Let me know.
How to install with Odin
(USB) Disconnect your phone from your computer
Start Odin3-vX.X.exe
Click the PDA button, and select CF-Auto-Root-....tar.md5
Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
(USB) Connect the phone to your computer
Make sure Repartition is NOT checked
Click the Start button
Wait for Android to boot
Done (if it took you more than 30 seconds, you goofed)
The Goods
k3gxx.tar - Please post feedback in this thread if you download(ed) and install this.
XDA:DevDB Information
Clockworkmod Recovery SM-G900H Exynos, a Tool/Utility for the Samsung Galaxy S 5
Contributors
PlayfulGod, Phil3759
Version Information
Status: Testing
Created 2014-04-19
Last Updated 2014-04-20

Tried the flags we discussed
You end up with a zImage-dtb, but it has no DTB embedded data
You can verify by comparing it to the zImage: they are same
Also, no DTB files were created during compiling
The end is a zImage without the DTB info

Phil3759 said:
Tried the flags we discussed
You end up with a zImage-dtb, but it has no DTB embedded data
You can verify by comparing it to the zImage: they are same
Also, no DTB files were created during compiling
The end is a zImage without the DTB info
Click to expand...
Click to collapse
Yea I noticed that b4 I broke mine from compiling. lol Not overly concerned with it atm. I'm sure the kernel gurus will work their magic.

Haven't installed it yet.
But I am dying hard to get a kernel for exynos with Boeffla or Faux audio driver.

Thank you for the CWM recovery!
Getting my Galaxy S5 tomorrow! And only have this one SM-G900H variant in my country. I will be replacing the recovery with this as soon as I get it!
ODIN v3.09, in case anyone needs it: http://www.devfiles.co/download/CAHmXM6c/Odin_v3.09.zip

thank you very much.it works perfect

Hello
Tks for this CWM ! What's the version of the CWM ? And anyone have tried this -->> http://forum.xda-developers.com/showthread.php?t=2726186
Whats the difference ?
Tks

scumpicule said:
Hello
Tks for this CWM ! What's the version of the CWM ? And anyone have tried this -->> http://forum.xda-developers.com/showthread.php?t=2726186
Whats the difference ?
Tks
Click to expand...
Click to collapse
prolly no difference, would have to compare device trees. lol
Mine is version 6.0.4.8 as yours should be if you synced cm src b4 building.
Nice OP btw.

PlayfulGod said:
prolly no difference, would have to compare device trees. lol
Mine is version 6.0.4.8 as yours should be if you synced cm src b4 building.
Nice OP btw.
Click to expand...
Click to collapse
Thanks
But It's the @Chenglu work. I've just write the thread. I would like to be a developper, but it requires time & knowledge... But now, I don't have.
Maybe later . There is no age to learn

scumpicule said:
Thanks
But It's the @Chenglu work. I've just write the thread. I would like to be a developper, but it requires time & knowledge... But now, I don't have.
Maybe later . There is no age to learn
Click to expand...
Click to collapse
nope sure isnt, I didnt get into computers until I was in my early 30's and only been messing with android for almost 4 years now.

Has nay1 install it yet? is it working for 900H?

I`m guessing the recovery doesn't work for the SM-G900M model as I've tried the process a couple of times and can't seem to be able to boot into recovery mode, only download?

blustosa said:
I`m guessing the recovery doesn't work for the SM-G900M model as I've tried the process a couple of times and can't seem to be able to boot into recovery mode, only download?
Click to expand...
Click to collapse
this one would not work on the G900M no
try here
http://forum.xda-developers.com/showthread.php?t=2697523

PlayfulGod said:
this one would not work on the G900M no
try here
http://forum.xda-developers.com/showthread.php?t=2697523
Click to expand...
Click to collapse
Couldn't get that one to work either

blustosa said:
Couldn't get that one to work either
Click to expand...
Click to collapse
I know at least 1 or 2 reported it working on the K900M.
(not this one ppl)

PlayfulGod said:
I know at least 1 or 2 reported it working on the K900M.
(not this one ppl)
Click to expand...
Click to collapse
Might be different for the SM-G900M perhaps? Shame...

blustosa said:
Might be different for the SM-G900M perhaps? Shame...
Click to expand...
Click to collapse
I meant G900M.

PlayfulGod said:
I meant G900M.
Click to expand...
Click to collapse
Could it perhaps have anything to do with the fact it was already rooted? If so, anyway to go back and redo the process?

blustosa said:
Could it perhaps have anything to do with the fact it was already rooted? If so, anyway to go back and redo the process?
Click to expand...
Click to collapse
shouldnt matter.

PlayfulGod said:
shouldnt matter.
Click to expand...
Click to collapse
Gave another go without the auto boot. Ran the whole thing, then it was left at the blue reset on Odin. So I pulled the cable, pulled the battery, and did the recovery reset with the volup, menu and power thing.
Goes then to the message "recovery is not seandroid enforcing " and then just reboots the phone regularly without ever going through recovery.
Something wrong in the process or the way I did it?

Related

[SOLVED] Boot Loop [Cant acess Recovery mode] Galaxy Ace s5830

Problem was solved by taking it to samsung service!
They changed a main piece. The motherboard!
DO NOT USE GALAXY_UNLOCKER.APK if you dont want your phone tottaly bricked!
There are other ways to unlock it!
raul2100 said:
Hello,
I dont know IF posting in the right place, but I searched the whole forum for a proper answer how to "unbrick" my boot loop-ed Samsung Galaxy Ace S5830..
Now I've tried installing several firmwares using Odin multi downloader v4.83 but none of them helped me, after all I cant access Recovery Mode!
I can acess Download mode, Emergency Dmod (arm9) and RAMDUMP (arm9)
I have: Android 2.3.3 GingerBread on T-Mobile Carrier (Hungary)!
How did I get here: rooted with SuperOneClick 2.3.2 and used an app for unlock (Galaxy Ace Unlock.apk) witch was probably the main source of the problem... Had no problems until I decided to reboot, rebooted successfully, the problem I had then was No carrier, then tried a second reboot and ever since then I'm stuck into a boot loop with no access whatsoever to RECOVERY MODE.
After installing firmware and waiting the 5 minutes in Odin, my device reboots intro a boot loop after about 2:32 min and nothing can be done furthermore...
I've serched the forum and found that data.rfs is missing in the firmwares... maybe that the source of the problem to... I dont know...
Please help me fix this problem!! Thank you!
p.s: noob alert
Click to expand...
Click to collapse
You'll just have to keep flashing roms via Download Mode until one works (try flashing the stock rom).
P.S.: Your device has it's own forum: http://forum.xda-developers.com/forumdisplay.php?f=1164.
Theonew said:
You'll just have to keep flashing roms via Download Mode until one works (try flashing the stock rom).
P.S.: Your device has it's own forum: http://forum.xda-developers.com/forumdisplay.php?f=1164.
Click to expand...
Click to collapse
Which ones should I try? Any Advice is helpfull!
raul2100 said:
Which ones should I try? Any Advice is helpfull!
Click to expand...
Click to collapse
As I said - the stock rom.
Theonew said:
As I said - the stock rom.
Click to expand...
Click to collapse
just tried, not working: S5830SERKPH 2.3.4 stock rom
raul2100 said:
just tried, not working: S5830SERKPH 2.3.4 stock rom
Click to expand...
Click to collapse
Are you flashing it correctly? Make sure you do everything in step C here: http://forum.xda-developers.com/showthread.php?t=1034145.
Theonew said:
Are you flashing it correctly? Make sure you do everything in step C here: http://forum.xda-developers.com/showthread.php?t=1034145.
Click to expand...
Click to collapse
every single step, when it should reboot it goes straight to boot loop, and still no recovery menu...
raul2100 said:
every single step, when it should reboot it goes straight to boot loop, and still no recovery menu...
Click to expand...
Click to collapse
Try flashing this one: http://www.hotfile.com/dl/137316855/e3bb576/S5830BUKS2_S5830VDHKS1_VDH.zip.html.
I've tried that today, didn't work either.
raul2100 said:
I've tried that today, didn't work either.
Click to expand...
Click to collapse
Try flashing a Froyo rom then: http://droidangel.blogspot.com/2011/05/samsung-galaxy-ace-s5830-original-stock.html.
Theonew said:
Try flashing a Froyo rom then: http://droidangel.blogspot.com/2011/05/samsung-galaxy-ace-s5830-original-stock.html.
Click to expand...
Click to collapse
well, now it wont even start! I think I've bricked it,
cant even boot it, nor download mode nor nothing...
raul2100 said:
well, now it wont even start! I think I've bricked it,
cant even boot it, nor download mode nor nothing...
Click to expand...
Click to collapse
Did you choose the one for your device (country+carrier)? Anyways, see here on how to unbrick it: http://forum.xda-developers.com/showthread.php?t=1071970.
Theonew said:
Did you choose the one for your device (country+carrier)? Anyways, see here on how to unbrick it: http://forum.xda-developers.com/showthread.php?t=1071970.
Click to expand...
Click to collapse
dident picked the one for my carrier or country, cause there no description on them... so I picked the 1st one, I did the unbricking btw.. but still got boot loop
raul2100 said:
dident picked the one for my carrier or country, cause there no description on them... so I picked the 1st one, I did the unbricking btw.. but still got boot loop
Click to expand...
Click to collapse
Did you use the cooper.ops?
Theonew said:
Did you use the cooper.ops?
Click to expand...
Click to collapse
yes, I did!
Tried a second froyo firmware that was for my region, still not working..
raul2100 said:
yes, I did!
Tried a second froyo firmware that was for my region, still not working..
Click to expand...
Click to collapse
It seems like your motherboard is damaged so you'll have to take it in under warranty.
Theonew said:
It seems like your motherboard is damaged so you'll have to take it in under warranty.
Click to expand...
Click to collapse
Thank you for your help until now & Happy New Year! I'd still like to solve this problem somehow before I take it under warranty! Witch I was planning to do tomorrow!
I dont understand how can my motherboard be damaged? If it would be damaged then probably I't would not even start in the 1st place.
I forgot to mention that I had a Movetosd app installed also, but I dont remember the full name of the app...
Any other Ideas?
raul2100 said:
Any other Ideas?
Click to expand...
Click to collapse
You have done everything you could and it's still not fixed (even the things other people did when they had the same problem - it worked for them, but not for you), so warranty is the only other way to get it fixed (or at least replaced).
Theonew said:
You have done everything you could and it's still not fixed (even the things other people did when they had the same problem - it worked for them, but not for you), so warranty is the only other way to get it fixed (or at least replaced).
Click to expand...
Click to collapse
Thank you for the help Theonew! Appreciate! I've taken it into warranty service, hopefully they wont find my device inappropriate for free service, and so I dont have to pay for it...
The only problem is that I have to wait at least 8 days untill I get it back..
Anyway, I've researched this Galaxy Unlock apk. and it seems thats the main source of the problem.
Thanks again!

[MOVED][CLOSED]ClockWorkMod Recovery try while its hot!!!

Hi guys,
Download links for ClockWorkMod Recovery both touch and non touch.
Now moved here
Bugs : You tell me.
Thanks,
Dark Passenger
Credits : People who made this possible.
Lloir(base tree).
Claudy(bug fixes).
Cobje(bug fixes and major porting).
neXus PRIME(major porting and finishing touches).
Dark Passenger(finishing touches and final bug fixes).
Gweedo767(clockworkmod maintainer and the person to make us official).
Note:This thread shall be moved to development forum once rom manager integration is complete
How to install.
prerequisites
unlocked bootloader.
fastboot
a usable brain.
>reboot to bootloader/fastboot mode
>open a fastboot terminal and type
>fastboot flash recovery <recovery_name>.img
>fastboot reboot-bootloader
>fastboot erase cache(precaution)
Thanks guys.
I have tested flash, wipes and it works (I tried flashing AromaFM and it worked, not an entire ROM) but if I select mount storage it doesn't work!
Also, I'm in ICS (1.14) ROM not JB
pfff.....why is that...?
this recovery : http://forum.xda-developers.com/showthread.php?t=2076245
has the same bug... i cant mount sd :S
gbueno6 said:
I have tested flash, wipes and it works (I tried flashing AromaFM and it worked, not an entire ROM) but if I select mount storage it doesn't work!
Also, I'm in ICS (1.14) ROM not JB
Click to expand...
Click to collapse
mhb92 said:
pfff.....why is that...?
this recovery : http://forum.xda-developers.com/showthread.php?t=2076245
has the same bug... i cant mount sd :S
Click to expand...
Click to collapse
same tree.
so except ums no other bugs ? graphics okay ...
also adb and adb sideloading.
Can some one give me a log for the ums behaviour.
Thanks.
Dark Passenger said:
Can some one give me a log for the ums behaviour.
Thanks.
Click to expand...
Click to collapse
I can't because I don't know how to :crying:
All I can do is confirm you that all wipes are working and that no graphic glitches were found!
I'm sorry
gbueno6 said:
I can't because I don't know how to :crying:
All I can do is confirm you that all wipes are working and that no graphic glitches were found!
I'm sorry
Click to expand...
Click to collapse
Advanced-Copy Log to SD.
xpirt
gbueno6 said:
I can't because I don't know how to :crying:
All I can do is confirm you that all wipes are working and that no graphic glitches were found!
I'm sorry
Click to expand...
Click to collapse
alternative to what @xpirt told
Code:
adb pull /cache/recovery/last_log
EDIT do this after you try UMS(if on windows wait for sometime for the drivers to install like atleast 10 min) and boot into the rom.
xpirt said:
Advanced-Copy Log to SD.
xpirt
Click to expand...
Click to collapse
I can't "copy log to sd" it just says "show log".
Dark Passenger said:
alternative to what @xpirt told
Code:
adb pull /cache/recovery/last_log
EDIT do this after you try UMS(if on windows wait for sometime for the drivers to install like atleast 10 min) and boot into the rom.
Click to expand...
Click to collapse
Ok, I have copied the last_log file (i tried usb mass storage and waited for some minutes before copying the file). I'm unrooted so I picked up the file with AromaFM.
I hope it helps!
PD: There's also something weird that happened to me with the other CWM recovery: when I switched off the phone to charge it, the orange light blinks for 15 seconds and the phone starts again! It doesn't happen with TWRP recovery (the "starting process", not the blinking). EDIT: The restart issue does NOT happen with this recovery. Yeyyyy!!
@OP, why panicking? ums will work just fine
you need to add proper lines in BoardCOnfig.mk and ramdisk. You should have waited for me to fix it as i gave you my tree. Anyways Try uncommenting the line for UMS_LUNFILE which is commented, and delete the next two lines after it. Compile it with that and tell me.
neXus PRIME said:
@OP, why panicking? ums will work just fine
Click to expand...
Click to collapse
I'm a generally panicky sort of person...
neXus PRIME said:
you need to add proper lines in BoardCOnfig.mk and ramdisk. You should have waited for me to fix it as i gave you my tree. Anyways Try uncommenting the line for UMS_LUNFILE which is commented, and delete the next two lines after it. Compile it with that and tell me.
Click to expand...
Click to collapse
Yes its your tree and actually the fix became apparent with the log.
Thank you for everything you have done for this devices recovery and I have no plans of changing that.The recovery is now fully functional and bugfree as soon as Gweedo767 is free he will be doing an official build(dont hold your breadth may take a while).
Post that official builds shall be available on clockworkmod.com and this thread will cease to exist(at least it will be locked).
And @neXus PRIME will you be updating your thread with this info since you will be the main maintainer.
Thank you ,
Dark Passenger.
Thanks for all your work making CWM official.:good::good:
btw, i said the "panic" thing in a light-hearted way.
The recovery tree is originally LLOIR's, later on modified by cobje(therbom), Clauddy, and then final fixed tree by neXusPRIME (me). Please give credits to all of them.
Secondly, i like TWRP far more than CWM, so i invite you to be the official CWM maintainer if you are willing. We can work on recoveries together.
I currently have JB and ICS TWRP 2.5.0.0 ready to be released but only do it when i receive JB OTA.
Lastly, NOTE that the tree you are using for OFFICIAL CWM is only ICS COMPATIBLE. You will need to modify the recovery.fstab for JB compatible recovery by changing the mount points for SYSTEM,DATA,CACHE as they are in JB ROM proc/emmc. Then you will rebuild and CWM will be able to flash ROMs for people with hboot 1.25.0.0
Regards
Yasir
neXus PRIME said:
Thanks for all your work making CWM official.:good::good:
btw, i said the "panic" thing in a light-hearted way.
The recovery tree is originally LLOIR's, later on modified by cobje(therbom), Clauddy, and then final fixed tree by neXusPRIME (me). Please give credits to all of them.
Secondly, i like TWRP far more than CWM, so i invite you to be the official CWM maintainer if you are willing. We can work on recoveries together.
I currently have JB and ICS TWRP 2.5.0.0 ready to be released but only do it when i receive JB OTA.
Lastly, NOTE that the tree you are using for OFFICIAL CWM is only ICS COMPATIBLE. You will need to modify the recovery.fstab for JB compatible recovery by changing the mount points for SYSTEM,DATA,CACHE as they are in JB ROM proc/emmc. Then you will rebuild and CWM will be able to flash ROMs for people with hboot 1.25.0.0
Regards
Yasir
Click to expand...
Click to collapse
1. Its my pleasure.
btw so was mine
2.all credits will be present once official builds are online and I open a thread for it.(maybe you could make your thread jb version so there are both versions present for those who want it).
3.wat a coincidence I like cwm better than TWRP. no offence seem to work.Also the recovery tree as always is open for anyone with a github account to modify.
4.Same here the tree submited is for ics and will be updated only when i get the jb update(knew about the mount points from the various thread actually from your post I think).
PS do you know whats needed and/or where I can get the sources for touch recovery.
PPS in your recovery.fstab(cwm version) the internal sdcard(emmc) is mounted as vfat where as in cm its emmc.
gbueno6 said:
Ok, I have copied the last_log file (i tried usb mass storage and waited for some minutes before copying the file). I'm unrooted so I picked up the file with AromaFM.
I hope it helps!
PD: There's also something weird that happened to me with the other CWM recovery: when I switched off the phone to charge it, the orange light blinks for 15 seconds and the phone starts again! It doesn't happen with TWRP recovery (the "starting process", not the blinking). EDIT: The restart issue does NOT happen with this recovery. Yeyyyy!!
Click to expand...
Click to collapse
so there are no problems other than UMS.
can you please confirm.
thanks.
Dark Passenger said:
so there are no problems other than UMS.
can you please confirm.
thanks.
Click to expand...
Click to collapse
Yes, other than UMS, no more issues!
PD: I won't be able to test it again because I upgraded to JB!! ^^
Thank you very much for your work!
gbueno6 said:
Yes, other than UMS, no more issues!
PD: I won't be able to test it again because I upgraded to JB!! ^^
Thank you very much for your work!
Click to expand...
Click to collapse
cool :jealous: i might have to wait a tad bit longer for that
also if possible can you hold out on the update for a few more days might be the first to try out official builds.
Dark Passenger said:
cool :jealous: i might have to wait a tad bit longer for that
also if possible can you hold out on the update for a few more days might be the first to try out official builds.
Click to expand...
Click to collapse
I'm afraid I can't! I was very excited watching that my operator updated to JB (they never updated our ROM before) that I made it and now I'm in JB.
I'm sorry!
Also, if you want me to test it in JB, let me know it and I'll be very happy to help!
Have a great day
gbueno6 said:
I'm afraid I can't! I was very excited watching that my operator updated to JB (they never updated our ROM before) that I made it and now I'm in JB.
I'm sorry!
Also, if you want me to test it in JB, let me know it and I'll be very happy to help!
Have a great day
Click to expand...
Click to collapse
aye aye aye I just got an official build hot off jenkins.
Any one willing to test and let me know if ums is good and alls well.
latest built
@gbueno6 cab you test ums (yes in JB) it should work fine don't try anything else wont work.

Has anyone got the TWRP Recovery to work??

Has anyone successfully gotten to TWRP Recovery to install for their Omate?
I have tried to do it using GooManager, but it says it cant find it.
I have also attempted to do the alternate methods but cant find a scatter file for it ?
Is there any tutorial on this that has worked for anyone?
fibroman said:
Has anyone successfully gotten to TWRP Recovery to install for their Omate?
I have tried to do it using GooManager, but it says it cant find it.
I have also attempted to do the alternate methods but cant find a scatter file for it ?
Is there any tutorial on this that has worked for anyone?
Click to expand...
Click to collapse
I installed TWRP on my TrueSmart this morning via adb while booted to Android. Rename the file that you download to twrp.img and then do the following:
adb push twrp.img /sdcard/twrp.img
adb shell dd if=/sdcard/twrp.img of=/dev/recovery
Done.
Dees_Troy said:
I installed TWRP on my TrueSmart this morning via adb while booted to Android. Rename the file that you download to twrp.img and then do the following:
adb push twrp.img /sdcard/twrp.img
adb shell dd if=/sdcard/twrp.img of=/dev/recovery
Done.
Click to expand...
Click to collapse
Thanks for the info. I now have it installed.
But when trying to do a backup it says( Failed )
Updating Partition details...
Kernel does not have support for running this application.
I was having the same issue. Did exactly what Dees_Troy suggested and it worked like a charm.
Thanks!
Now to wait for roms, because the stock one blows so far.
mortis2600 said:
I was having the same issue. Did exactly what Dees_Troy suggested and it worked like a charm.
Thanks!
Now to wait for roms, because the stock one blows so far.
Click to expand...
Click to collapse
Ouch!!! I can always take Operative and instead of a 100MB file make it +600MB file and call it a "ROM" if it will help.
fibroman said:
Thanks for the info. I now have it installed.
But when trying to do a backup it says( Failed )
Updating Partition details...
Kernel does not have support for running this application.
Click to expand...
Click to collapse
Try running the backup again. If you get an error, adb pull /tmp/recovery.log without rebooting and attach or paste the log to a paste site.
Lokifish Marz said:
Ouch!!! I can always take Operative and instead of a 100MB file make it +600MB file and call it a "ROM" if it will help.
Click to expand...
Click to collapse
Sorry, I have a fairly high standard of roms at this point.
Dont want to go too far off topic, but I've had some issues with bluetooth (pairs, doesn't stay connected, thus making the companion app useless), battery life, etc.
I may have to run tasker scripts to emulate some of the things I want it to do with notifications and turning the screen on. Finally, if I install a new launcher, it'd be wonderful if it didn't cover up the notifications bar.
mortis2600 said:
Sorry, I have a fairly high standard of roms at this point.
Dont want to go too far off topic, but I've had some issues with bluetooth (pairs, doesn't stay connected, thus making the companion app useless), battery life, etc.
I may have to run tasker scripts to emulate some of the things I want it to do with notifications and turning the screen on. Finally, if I install a new launcher, it'd be wonderful if it didn't cover up the notifications bar.
Click to expand...
Click to collapse
I quit anyways so no biggie
mortis2600 said:
Sorry, I have a fairly high standard of roms at this point.
Click to expand...
Click to collapse
Then.... build.... your.... own?
Be a part of the solution.
Sent from my Galaxy Nexus using Tapatalk 2
Lokifish Marz said:
I quit anyways so no biggie
Click to expand...
Click to collapse
Did you build the stock rom? If so, I meant no offense.
mortis2600 said:
Did you build the stock rom? If so, I meant no offense.
Click to expand...
Click to collapse
It was built from broken, crappy Umeox firmware so better battery life, memory management and pretty much every fix or improvement came form me. Like I said I'm done so no offense taken.
Lokifish Marz said:
It was built from broken, crappy Umeox firmware so better battery life, memory management and pretty much every fix or improvement came form me. Like I said I'm done so no offense taken.
Click to expand...
Click to collapse
I don't have yours installed. Mine is just running completely stock firmware right now.
And it sucks that you're quitting. Your build looked to be the one thing that might make the OS on this thing worth using.
---------- Post added at 08:09 PM ---------- Previous post was at 07:42 PM ----------
kuronosan said:
Then.... build.... your.... own?
Be a part of the solution.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
If I had the expertise to do so, I would be inclined to do so. Sadly, I'll just have to settle for reporting bugs and making feature requests and being happy to have my device at all.
[SOLVED] backup failed on TWRP
fibroman said:
Thanks for the info. I now have it installed.
But when trying to do a backup it says( Failed )
Updating Partition details...
Kernel does not have support for running this application.
Click to expand...
Click to collapse
If you are getting 'Unable to create folder' error, then rename the backup name and it should work :good:
nbarm2 said:
If you are getting 'Unable to create folder' error, then rename the backup name and it should work :good:
Click to expand...
Click to collapse
That did the trick!!! Renaming the backup. Thanks.
One final question here: I have been using apps like goomanager to reboot into recovery, but how can you enter TWRP straight from turning the watch on.
Is there a key combo that needs to be held when turning the watch on to get right into TWRP? I tried holding down the bottom right key and that did not work.
Hold both keys for 10 seconds then toggle to recovery
Sent from my Galaxy Nexus using Tapatalk 2
kuronosan said:
Hold both keys for 10 seconds then toggle to recovery
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This, but your battery pretty much has to be fully charged or else it will just flash the Omate logo on the screen for a couple seconds and then shut off.

[WIP] CWM 6 (Booting and Testing)

Download
Mega
Installing
You can't flash this yet (I'm working on that, I promise) but you can boot from it!
NOTE: THIS IS A WIP. Not a lot has been really tested yet and this is posted merely for your enjoyment atm.
I don't suggest flashing anything yet, not that there is anything to flash heh.
Also, I take no responsibility if you break your watch, yada, yada.
To do this, make sure you have Android's tools (for fastboot), an unlocked bootloader, and the watch connected to your computer in Debug mode.
> adb reboot bootloader
<wait for the reboot to happen>
> fastboot boot /path/to/recovery.img
Click to expand...
Click to collapse
Enjoy!​
Did u push the tree to github?
1st built for me was a no go
wouldn't twrp make more sense since its touch based?
D-FUSE said:
Did u push the tree to github?
1st built for me was a no go
Click to expand...
Click to collapse
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
ptesmoke said:
wouldn't twrp make more sense since its touch based?
Click to expand...
Click to collapse
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
ptesmoke said:
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
Click to expand...
Click to collapse
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
dude1981 said:
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
jamcar said:
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Click to expand...
Click to collapse
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Click to expand...
Click to collapse
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Click to expand...
Click to collapse
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
PlayfulGod said:
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Click to expand...
Click to collapse
It's only booting because it doesn't work when flashed to recovery. The file size is around 8 mb whereas the legitimate recovery is 23 mb, which I'm sure is an issue. Is it possible that I'm only creating a ramdisk that gets paired with the watch's kernel and I need to make an image with both of them? Sorry, this whole uBoot stuff confuses me a bit.
PlayfulGod said:
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Click to expand...
Click to collapse
Heh, I'm not actually afraid of git, I guess, I'm afraid of the whole "making a device-specific git repo that can be easily pulled while building CM." I guess I just don't have the time atm to set it up properly, but dw, I'll get to it this weekend! :fingers-crossed:
dude1981 said:
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, the iOS mod is something I downloaded awhile ago for my N5. I'm afraid I don't have the link anymore. Sorry, man.
Pepski said:
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
Click to expand...
Click to collapse
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Smith7018 said:
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Click to expand...
Click to collapse
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Pepski said:
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Click to expand...
Click to collapse
Weird... I don't even think you need root to push to /sdcard/ but I could be wrong. I'd suggest trying /sdcard/emoji.zip so it knows where to resolve. Also, I don't use Windows, but does the backslash work on adb as a file separator?
what happened to development on this?

[Q] Can't Load CWM/TWRP on MDK

[SOLVED]
Turns out CMW 6.0.4.7 will not flash to this device - solution was to use the app "Flashify" from the play store which simply and easily installed TWRP
Thanks joshm.1219!
[SOLVED]
I am at a complete loss for a fix. Short story is: I wasn't receiving any MMS, so I finally decided to ODIN back to stock and used this method so I could keep my data. Here's what happened next:
- ODIN passed but I couldn't get past the Verizon logo
- Tried several suggested fixes but the last resort one worked; I wiped data & factory reset (thus defeating the purpose of the no-wipe ODIN... w/e)
- Everything loads fine, TouchWiz works but I get a Factory Mode popup and can't lock my screen. (still can't lock my phone even now but will use this method if I think I'm stuck with TouchWiz)
- I use this method to unlock bootloader and root - root confirmed.
- Try to install CWM recovery or TWRP (btw, where the hell did GooManager go and why is it so hard to find now) and they say successful but I simply can't boot into them, just keep getting the factory recovery screen which won't let me flash any roms or any non-signed .zips
- MMS Still doesn't work!
- I call VZW in desperation and somehow they magically reset my account services and MMS works again! (I probably could have done this in the first place and not lost my ROM/Data and sanity if I'd known)
I have looked high and low for a solution but have found none. I also have been unable to find a REGULAR stock MDK file to flash on this phone - I can only find the NO-WIPE version which doesn't even allow you to keep your data. I'm confused and frustrated and would love some active help, I just can't find the right threads/posts/ect.
Thank you kindly for any advice.. I love my S4 and have been using PA, PAC, CM and other ROMS since the day I got it - I need that back! TouchWiz is just... I just don't like it.
Try this one.
http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR
FernBch said:
Try this one.
link
Click to expand...
Click to collapse
Thanks for the original stock.. sadly I am still ending up with the Android System Recovery and despite installing CWM Recovery, I just can't get to it. I also still get the ridiculous Factory Mode popup.
Any ideas? I'm so sad :'(
From off it's either home+volume down+power or home+volume up+power. One boots into stock recovery the other will boot into CWM.
Hold all three until you see some small blue text in the upper left of the screen.
FernBch said:
From off it's either home+volume down+power or home+volume up+power. One boots into stock recovery the other will boot into CWM.
Hold all three until you see some small blue text in the upper left of the screen.
Click to expand...
Click to collapse
Thanks for the effort but I'm well aware of that. As I said in the OP, I've been using custom ROMs on this since day one - the issue is that I cannot boot into CMW Recover, despite having a successful install via the app.
Dumb question, which app are you using? I use RomManager to install CWM (up to 6.0.4.7) and I have a flashable zip of 6.0.5.0.
877
FernBch said:
Dumb question, which app are you using? I use RomManager to install CWM (up to 6.0.4.7) and I have a flashable zip of 6.0.5.0.
Click to expand...
Click to collapse
I'm using ROM Manager but it won't work. I'd love to try ODIN flashing the CWM Recovery if you have the file for my MDK build.
I may have it on my PC at home. When I get there (60-90 min) I'll look. If I do I'll post up to Dropbox and give you a link.
Ok, I've searched my HDD and I don't have the CWM file. What I do have is the MDK all-in-one root+recovery tool for the I545. I can put it up and upload it if the file isn't too large but I don't know if that'll help you.
CWM 6.0.5.0 flashable zip is in the CM11 thread but I don't know if the recovery image in the file is good for you, either
Just use Flashify to get TWRP
joshm.1219 said:
Just use Flashify to get TWRP
Click to expand...
Click to collapse
I was about to complain about your assumption that I knew what that was.. then I found it on the play store and it actually worked! Thank you so much - now here's to hoping I can find a nice stable 4.4.4 ROM to put back on here!
I'm still at a loss for why ROM Manager was unable to flash CWMR but I guess I don't _need_ to know, I am so happy this is a big step after 3 days of touchwiz hell!
voice.lex said:
I was about to complain about your assumption that I knew what that was.. then I found it on the play store and it actually worked! Thank you so much - now here's to hoping I can find a nice stable 4.4.4 ROM to put back on here!
I'm still at a loss for why ROM Manager was unable to flash CWMR but I guess I don't _need_ to know, I am so happy this is a big step after 3 days of touchwiz hell!
Click to expand...
Click to collapse
As far as I know, the latest CWM doesn't work on our devices.
joshm.1219 said:
As far as I know, the latest CWM doesn't work on our devices.
Click to expand...
Click to collapse
Well, that explains it - Thank you so much!
voice.lex said:
Well, that explains it - Thank you so much!
Click to expand...
Click to collapse
No problem :thumb:
This thread might be dead, but rather than starting a new one for what is probably a stupid question, I'll ask it here and see what happens. I've been having major trouble flashing any 5.0 rom on my MDK VZW S4....Seems like every ROM fails when flashing. I have a feeling my issue is an outdated version of TWRP (2.5.0.2), but I am very hesitant to update because it seems like everyone has been having issues with 2.8.1.0. With this being said, are you guys currently running the most current version of TWRP and would you mind advising which .img file worked via Flashify? Not sure whether to use the jfltexxx or jfltevzw...or if it even matters.
I'm sure I've left out pertinent information, but let me know what I'm missing and I'll update accordingly.
I've been using the latest version of TWRP 2.8.1.0 and running Euroskank Lollerpop with zero issues. Coincidentally, TWRP just got updated today to 2.8.3.0 which i have yet to flash but will do so shortly. I would recommend JFLTEVZW based on my usage. Not sure if the other variant works or not but it appears you have a verizon device so stick with JFLTEVZW.
760hacker said:
I've been using the latest version of TWRP 2.8.1.0 and running Euroskank Lollerpop with zero issues. Coincidentally, TWRP just got updated today to 2.8.3.0 which i have yet to flash but will do so shortly. I would recommend JFLTEVZW based on my usage. Not sure if the other variant works or not but it appears you have a verizon device so stick with JFLTEVZW.
Click to expand...
Click to collapse
Thank you very much for getting back to me. When you flashed 2.8.3.0, was it a .zip file from recovery or a .IMG through flashify or another app? Thanks again for your help!
swh969 said:
Thank you very much for getting back to me. When you flashed 2.8.3.0, was it a .zip file from recovery or a .IMG through flashify or another app? Thanks again for your help!
Click to expand...
Click to collapse
.IMG file, flashify is so simple!
Sent from my Nexus 7 using Tapatalk
760hacker said:
.IMG file, flashify is so simple!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm going to give it a shot! Thanks again for your help.
Worked like a charm. Thanks @760hacker

Categories

Resources