CLOCKWORKMOD-RECOVERY FOR GALAXY S II (AT&T)
Click to expand...
Click to collapse
for use with Stock ROMs
I'll update it every time something important has changed, like CWM changes or kernel updates from samsung.
It's built from samsung kernel sources + teamhacksung initramfs template.
Instructions
Power your device off
Boot into Download-Mode using Volume Up + Volume Down + Power
Hit Volume Up to accept the warning
Start Odin
Choose "SGH-I777_ClockworkMod-Recovery_X.X.X.X.tar" as PDA (no repartition)
Connect your Phone
Start flashing
After reboot you can easily root your device using SuperOneClick
Usage
Volume Up + Power brings your Phone into Recovery Mode.
VolUp + VolDn = Highlight Up/Dn
Power = toggles menus off/on
Home = Select
Back = Back
Download
Testing - 5.0.2.3: http://www.multiupload.com/QQKN7NJAFT (md5: 4fb905992461586966ee1a7991206e93)
Don't forget to thank koush for his awesome work on ClockworkMod / ROMManager.
INITRAMFS TEMPLATE FOR DEVELOPERS
Click to expand...
Click to collapse
Here's a initramfs template you can use as a base for your haxx0ry:
https://github.com/teamhacksung/clockworkmod_galaxys2att_initramfs
It's KG1 initramfs + ClockworkMod Recovery and necessary modifications to make it work.
Instructions
git clone https://github.com/teamhacksung/clockworkmod_galaxys2att_initramfs gingerbread
remove hidden directorys from your cloned repo like .git
use it as your initramfs source
To make sure to include fresh modules (vermagic) use a buildscript like this:
build.sh (inside your kernel dir)
Code:
#!/bin/bash
INITRAMFSDIR=/home/user/android/samsung/galaxys2att_initramfs
TOOLCHAIN=/home/user/android/cyanogenmod/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
make c1_rev02_usa_att_defconfig
make -j8 CROSS_COMPILE=$TOOLCHAIN CONFIG_INITRAMFS_SOURCE="$INITRAMFSDIR"
cp drivers/bluetooth/bthid/bthid.ko $INITRAMFSDIR/lib/modules/
cp drivers/net/wireless/bcm4330/dhd.ko $INITRAMFSDIR/lib/modules/
cp drivers/samsung/j4fs/j4fs.ko $INITRAMFSDIR/lib/modules/
cp drivers/scsi/scsi_wait_scan.ko $INITRAMFSDIR/lib/modules/
cp drivers/samsung/vibetonz/vibrator.ko $INITRAMFSDIR/lib/modules/
make -j8 CROSS_COMPILE=$TOOLCHAIN CONFIG_INITRAMFS_SOURCE="$INITRAMFSDIR"
Example updater-script: http://pastebin.com/RXqiVTMv
Kernel Sources: http://opensource.samsung.com
greets
codeworkx
It is vol up+down and power to get into recover
Can't wait till I get one today! Great work!
Sent from my SGH-I897 using XDA App
Also running root now too ty!
jivy26 said:
Also running root now too ty!
Click to expand...
Click to collapse
Are the buttons working like described?
Yes they are working fine no issues. Root with superoneclick was fairly straight forward as well.
jivy26 said:
Yes they are working fine no issues. Root with superoneclick was fairly straight forward as well.
Click to expand...
Click to collapse
I wish it was that easy for me. Coming from the iPhone jailbreaking scene, this stuff is like jibberish. They need a "rooting the gsII for dummies."
brock.higdon said:
I wish it was that easy for me. Coming from the iPhone jailbreaking scene, this stuff is like jibberish. They need a "rooting the gsII for dummies."
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1285894
brock.higdon said:
I wish it was that easy for me. Coming from the iPhone jailbreaking scene, this stuff is like jibberish. They need a "rooting the gsII for dummies."
Click to expand...
Click to collapse
jivy26 said:
http://forum.xda-developers.com/showthread.php?t=1285894
Click to expand...
Click to collapse
:doh:
I leave the general forum for 5 minutes. Haha
Can someone who has flashed this and NOT flashed anything else get a system dump for us?
CodeworkX check pm dropbox link is in there
Sent from my SAMSUNG-SGH-I777 using xda premium
jivy26 said:
CodeworkX check pm dropbox link is in there
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Thank you very much.
edit: nvm, someone else did it
brock.higdon said:
Explain a little further because I am not real bright but I may can help. I followed the "easy root" instructions in the general forum. Have not done anything else since.
Click to expand...
Click to collapse
He is trying to help Devs. All he needs to do is boot into CWM goto backup and backup. After its complete boot into phone then upload system img to dropbox and pm codeworkx(if they need more sources).
With Working CWM Recovery we can flash root
Download Here
drop the file on your SD card and "choose 'su-3.0-efgh-signed.zip' file to flash" from CWM recovery (flash file from sd - choose zip - YES- reboot system)
IRC = #sgs2-att on irc.freenode.net
Looks like you guys will have a rooted system image before I can even get to the store!
Could you PM me a link to the system dump so I can start looking at it?
Entropy512 said:
Looks like you guys will have a rooted system image before I can even get to the store!
Could you PM me a link to the system dump so I can start looking at it?
Click to expand...
Click to collapse
Sent
Sent from my SAMSUNG-SGH-I777 using xda premium
jivy26 said:
Sent
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Thanks. I have, in theory, a stock rooted Heimdall-flashable image now.
Less than an hour until my AT&T store opens - hopefully they give me some sort of FAN discount.
BTW, one small question (already PMed you this) - what is the partition size of /system?
Entropy512 said:
Thanks. I have, in theory, a stock rooted Heimdall-flashable image now.
Less than an hour until my AT&T store opens - hopefully they give me some sort of FAN discount.
BTW, one small question (already PMed you this) - what is the partition size of /system?
Click to expand...
Click to collapse
Should be:
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 536870912
codeworkx said:
Should be:
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 536870912
Click to expand...
Click to collapse
512M right on the dot.
This means that in theory, Fenny and I have flashable stock and stock rooted images now. We'll know in a few hours. My AT&T store doesn't open for 45 more minutes and I'm not sure what discounts I may have available. If I get the right deal, I'll flash from my laptop, dump kernel, and upload the kernel from Panera.
Related
HOW-TO * Flash the Eng-Release to the Slide
eugene373 said:
This is not ment to be an everyday Rom!! It's only Vital for the testkey in recovery that gets flashed!!
Flash this, update the Radio & flash to a new Rom like Slidemeroot2.zip
The only thing we need is the Recovery from it.
Also this should be Sticky atm, as this is the only way as of now to flash a recovery!
The Recovery gives use the abilty to flash any update.zip after it is signed with testkeys... But we are using ClockworkMod Recovery due to options it has..
Click to expand...
Click to collapse
Before we Start, You must Have ROOT & Downloaded this .zip and Place on your Sdcard
File is Here > http://outboundlink.net/anxo/dr_ta_...://www.4shared.com/file/OsmF_ZD7/ESPRIMG.html
Files Needed Before We Start > SlideEng-package.zip
Step 1.
adb push /{the folder u downloaded it to}/flash_image /data/local
Step 2.
adb push /{the folder u downloaded it to}/mtd0.img /data/local
Step 3.
adb shell
Step 4.
su
Step 5.
cd /data/local
Step 6.
chmod 04755 *
Step 7.
/data/local/flash_image misc /data/local/mtd0.img
Step 8.
Power Off Phone!
Step 9.
Power on Using Volume Down + Power
Step 10.
hit Volume Up to Update!!!
Enjoy!!!
~Eugene
eugene373 said:
Uploading and Making how-to
Click to expand...
Click to collapse
This is excellent news! a much easier way to get root on this device!
Not sure if it's an alternate way, I think it's a downgrade after root is applied... We'll have to wait and see.
your right, fer, its a downgrade for an engineering build that you can do ONCE YOU HAVE ROOTED
So is this to unroot, once rooted?
forgive an ignorant question, but what does this gain us?
no this is to downgrade the build to engineering
just finished installing the update, system is rebooting now, will inform how it is eugene totally deserves props for this... donate if you can, i know i am as soon as my check clears
oh and his phone support is as good as golden ^^
king you were going to make a rooting vid right
yeah, but it'd prob be best for multiple people to make one, that way if someone doesnt understand how i do it then they may understand your way better, got me?
thnk u Eugene todays my bday n i was very happy to wake up to ROOT
HighRidas said:
thnk u Eugene todays my bday n i was very happy to wake up to ROOT
Click to expand...
Click to collapse
No Problem & happy Birthday
Is this build lighter? Im just wondering... can wait for a2sd! I might try out the old app by marcus until we get a rom with the scripts added.
sino8r said:
Is this build lighter? Im just wondering... can wait for a2sd! I might try out the old app by marcus until we get a rom with the scripts added.
Click to expand...
Click to collapse
lighter on the system....data went from 135mb free to 74mb free because this is the build from before the final build freed up some memory
hey eugene!
Is the"ENG" the same evo looking rom you have on your slide?
no.. eng is engineering build, means it was what they produced before the release build to test **** on
kingofyo1 said:
no.. eng is engineering build, means it was what they produced before the release build to test **** on
Click to expand...
Click to collapse
so where do i find it? lol
uhh the first page of this thread
So is there any way to revert back to the release build yet? Just wondering.
r0adki111 said:
So is there any way to revert back to the release build yet? Just wondering.
Click to expand...
Click to collapse
Yeah that's a great question. My best friend did this to his phone and I actually read through before I flashed the image. He said his phone is running slow and wants to revert back. Is there anyway yet to get back to the original build?
Messed around and tried to root a AT&T Galaxy S 2. I'm rooted but now back and search keys do not work on the bottom on the phones. I guess i need the stock AT&T kernel to flash back to?
Any help would be great thanks.
Source for the kernel has been released.just a matter of time untill the devs create something wonderfull you might look on samsungfirmware.com
I havent seen a kernel specific to the att version. Not sure if anyone has made one yet. You might be stuck untill e get one but I dont think it will be to long. Good money says D.G. Is already on it.
sent from my Infuse at Tranquility Base.
My Fault
I knew I should of waited i just wanted to run Titanium Backup
How did you get the ATT version so soon?
Sent from my GT-I9100 using XDA App
Yeah International kernels dont support bottom keys since they aren't on the Int' version so if you used one of the kernels you will need to go stock like you said or wait for DG to cook up his genius like another poster said.
This might not be the right place for this question and I know it's still very early but anyone think there'll be a way to unlock the AT&T SGS2 for other carriers? I know the Captivate could be unlocked simply by rooting and downloading an app from the market. I only ask because I'll be getting the phone on release day and I'm heading out of the country for 3 weeks. would love to use it wherever I go.
All you have to do is call ATT and ask a rep for the unlock code for your phone once you have it in your hands and they will give it to you.
Make sure to write it down and save it somewhere.
Sent from my SAMSUNG-SGH-I897 using XDA App
it's that simple? i was under the impression I had to wait 6 months for that
illmac said:
it's that simple? i was under the impression I had to wait 6 months for that
Click to expand...
Click to collapse
There may be a waiting period that i'm not sure about. I was under the impression you just had to have the phone's imei number and verification you own the phone and they would give you the unlock code on request.
Sent from my SAMSUNG-SGH-I897 using XDA App
Lol. Wondering same thing.
ronj1986 said:
How did you get the ATT version so soon?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Sent from my I897 using XDA App
Nerz said:
Lol. Wondering same thing.
Sent from my I897 using XDA App
Click to expand...
Click to collapse
Yeah, no kidding. I'm glad dg is working on it though! I sent him a PM and he never did respond though.
dayv said:
All you have to do is call ATT and ask a rep for the unlock code for your phone once you have it in your hands and they will give it to you.
Make sure to write it down and save it somewhere.
Click to expand...
Click to collapse
illmac said:
it's that simple? i was under the impression I had to wait 6 months for that
Click to expand...
Click to collapse
It is that simple. However, a lot of recent new phones had been put on 10-month exclusivity clause by AT&T that includes Captivate which means AT&T won't give you unlock code until 10 months after the phone has been released.
The normal waiting period is 90-day if you purchase on contract. But given GS2 will be on 10-month lock, you won't get your code until next summer.
post a tutorial on how to get it and ill upload it for you.
ronj1986 said:
How did you get the ATT version so soon?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
First rule about fight club...
alton987 said:
Messed around and tried to root a AT&T Galaxy S 2. I'm rooted but now back and search keys do not work on the bottom on the phones. I guess i need the stock AT&T kernel to flash back to?
Any help would be great thanks.
Click to expand...
Click to collapse
Someone who has not flashed a modded kernel will have to pull it.
The good news is - you have the first step. See http://forum.xda-developers.com/showpost.php?p=17777056&postcount=42
Now that you have a rooted kernel with a stock /system, you can get a system partition dump.
Get ADB up and running, and paste the results of running the following command in an ADB shell:
Code:
mount
From that we can figure out which partition is the system partition. After that, the following command (need to put correct system partition into it) will create a system dump:
Code:
dd if=/dev/systempartitionlocation of=/sdcard/system.img bs=1M
If you upload that dump to multiupload and put the link here, someone (maybe myself, although I'm 50/50 on whether I'll actually purchase a device) can root that dump and make an Odin-flashable system partition image. This can be flashed to a phone that has the stock kernel to get root and dump the stock kernel.
Entropy512 said:
Someone who has not flashed a modded kernel will have to pull it.
The good news is - you have the first step. See http://forum.xda-developers.com/showpost.php?p=17777056&postcount=42
Now that you have a rooted kernel with a stock /system, you can get a system partition dump.
Get ADB up and running, and paste the results of running the following command in an ADB shell:
Code:
mount
From that we can figure out which partition is the system partition. After that, the following command (need to put correct system partition into it) will create a system dump:
Code:
dd if=/dev/systempartitionlocation of=/sdcard/system.img bs=1M
If you upload that dump to multiupload and put the link here, someone (maybe myself, although I'm 50/50 on whether I'll actually purchase a device) can root that dump and make an Odin-flashable system partition image. This can be flashed to a phone that has the stock kernel to get root and dump the stock kernel.
Click to expand...
Click to collapse
I have the same problem, can anyone dump a zImage and upload to somewhere? Thanks in advanced!
keeploading said:
I have the same problem, can anyone dump a zImage and upload to somewhere? Thanks in advanced!
Click to expand...
Click to collapse
zImage can't be dumped without a rooted /system.
Do you have root via kernel? If so, get a dump as described above so someone can root their /system and get the stock zImage
Entropy512 said:
Someone who has not flashed a modded kernel will have to pull it.
The good news is - you have the first step. See http://forum.xda-developers.com/showpost.php?p=17777056&postcount=42
Now that you have a rooted kernel with a stock /system, you can get a system partition dump.
Get ADB up and running, and paste the results of running the following command in an ADB shell:
Code:
mount
From that we can figure out which partition is the system partition. After that, the following command (need to put correct system partition into it) will create a system dump:
Code:
dd if=/dev/systempartitionlocation of=/sdcard/system.img bs=1M
If you upload that dump to multiupload and put the link here, someone (maybe myself, although I'm 50/50 on whether I'll actually purchase a device) can root that dump and make an Odin-flashable system partition image. This can be flashed to a phone that has the stock kernel to get root and dump the stock kernel.
Click to expand...
Click to collapse
Stop kidding yourself Entropy. You're getting this phone. You're addicted now.
I'll be getting mine tomorrow.
And my m8 is getting his the same day.
I don't get off work until 6, but I will be flashing mine with an i9100 kernel, and obtaining a system image. Then I will be flashing my m8's with that image, and dumping the zimage to flash back to my own, that is if you all haven't gotten it done by then.
Fenny said:
I'll be getting mine tomorrow.
And my m8 is getting his the same day.
I don't get off work until 6, but I will be flashing mine with an i9100 kernel, and obtaining a system image. Then I will be flashing my m8's with that image, and dumping the zimage to flash back to my own, that is if you all haven't gotten it done by then.
Click to expand...
Click to collapse
Sweet. FYI, some processing is needed to make a dumped image Odin-flashable for native ext4 phones.
http://forum.xda-developers.com/showthread.php?t=1081239
Now that the new hboot doesn't allow S-ON devices to flash kernels I went ahead and adapted this for the LTE. It's something I started for the Evo 3D back in January, but when a new way to get S-OFF was found I sat it aside and had forgotten about it.
When used it tries to flash the kernel like normal and doesn't do anything special if able to, otherwise it will copy a script to the system partition and install the kernel when the ROM tries to boot up. All that's needed is for a few lines to be added to the updater-script and it can do the rest.
I'll update this with more information at a later time, but for now I just want to say thank you to everyone who has helped contribute ideas and tested. As always, any help with improving it is welcomed.
How To Use It
This is mainly for ROM and kernel devs to use before releasing, but it can easily be added to any that don't normally use it. For more detailed instructions see Page 3.
Download and add the "kernel" folder to your update zip
Edit your updater-script and use the following when you are ready to install the boot.img
Code:
ui_print("Installing Kernel, please wait...");
package_extract_file("boot.img", "/tmp/boot.img");
package_extract_dir("kernel", "/tmp/kernel");
set_perm_recursive(0, 2000, 0777, 0777, "/tmp/kernel");
run_program("/tmp/kernel/install_kernel.sh", "/tmp/boot.img", "/tmp/bootready.tmp");;
ifelse(file_getprop("/tmp/bootready.tmp","kernel.ready") != "READY",(
ifelse(file_getprop("/tmp/bootready.tmp","kernel.ready") == "STARTUP",
ui_print("Kernel Will Be Installed On Startup."),
ui_print("ERROR: Kernel Not Installed!")
)
));
Sign the zip and it can then be installed like normal from any device with a custom recovery
Changes
v0.57
flashboot.sh - Fixed the case statement that verifies the kernel flashed properly
flashboot.sh - Moved the call for DD to save the old kernel so that it always gets used
Downloads/Sources
Kernel Folder on DevHost (MD5: 27eB86aae3562e147d86b8dfe7a04786)
Google Code
Github - All files including the flashboot binary source
How Can I Test It With S-OFF?
If you comment out the dd command that writes the boot.img it will act like your device has S-ON.
Edit install_kernel.sh and change:
Code:
echo "-Trying to write the new boot.img and verify it's MD5"
$BBDD if=$BOOTPADDED of=$BLOCKBOOT; sync
rm -f $BOOTOLD
to:
Code:
echo "-Trying to write the new boot.img and verify it's MD5"
#$BBDD if=$BOOTPADDED of=$BLOCKBOOT; sync
rm -f $BOOTOLD
Where Are The Log Files?
In the recovery it uses: /tmp/recovery.log
On boot it uses: /data/local/bootinfo.txt
What Does This Need To Work?
A custom recovery
A valid kernel already installed with init scripts to start either /system/bin/app_process or /system/bin/netd
What Recoveries Does It work With?
Most of my testing has been done with TWRP, but it should work just as well with any other recovery
Why Did My Phone Reboot Back To The Recovery?
If it is unable to flash the kernel it will leave the old one in place and reboot back to the recovery. If you are able to, please pull the log file from /data/local/bootinfo.txt and send it to me so I can see what needs to be fixed.
What If I Get A Bootloop?
Either the kernel you flashed doesn't work with your ROM or there was an error and it's unable to reboot back to the recovery. If you hold volume down it should bring up the bootloader, from there use the volume and power buttons to select 'Recovery'.
Why Does My Phone Boot Straight To The Bootloader?
You either managed to wipe your boot partition (kernel) or sometimes this will happen when upgrading hboots. If you are S-ON you will need to flash a new boot image from fastboot.
Reserved for later use
Cute
Does this work for AOSP based kernels as well?
-Cupper- said:
Cute
Click to expand...
Click to collapse
Thanks Cupper
sivarticus85 said:
Does this work for AOSP based kernels as well?
Click to expand...
Click to collapse
Yup, it's all the same to it. The only thing it needs to work is for some sort of kernel to already be installed.
good stuff!!!!!!!
Good stuff man. Like always, xhausx contributing genius stuff for all. Thanks. :thumbup:
Sent from my EVO using xda premium
Awesome. Thanks.
via eVo.
implimenting in my next installer
Zarboz said:
implimenting in my next installer
Click to expand...
Click to collapse
Would be a nice setup, aroma choose the way to install, boot.img or anykernel flash
Then you can flash the modules either way...
Thanks for the script. It will definitely get used.
Zarboz said:
implimenting in my next installer
Click to expand...
Click to collapse
ca1ne said:
Would be a nice setup, aroma choose the way to install, boot.img or anykernel flash
Then you can flash the modules either way...
Thanks for the script. It will definitely get used.
Click to expand...
Click to collapse
Let me know if you need any help implementing it. I know the instructions aren't very detailed yet so I'll see about clarifying them some more here in a little bit.
Cool man
Sent from my EVO using xda premium
I don't mean to highjack anyone thread I was ready to do this since meanrom went with the evilz kernal. since I was s-on on the 1.15 boot. I was going to do this till I found a app on the market place called flash image gui which installed the kernal right on the phone.was simple and just plain easy no typeing anthing in just a click of a buttone.
cgrimm9 said:
I don't mean to highjack anyone thread I was ready to do this since meanrom went with the evilz kernal. since I was s-on on the 1.15 boot. I was going to do this till I found a app on the market place called flash image gui which installed the kernal right on the phone.was simple and just plain easy no typeing anthing in just a click of a buttone.
Click to expand...
Click to collapse
I used Flash Image GUI on my NS4G all of the time. The last 2 updates were to add this phone and the Nexus 7. It takes about 10 seconds to flash a kernel or recovery img. Its a JoeyKrim app...so you know its legit. It actually saved me last night when testing a N7 kernel overclocked over 1.99. . The kernel somehow made my N7 not boot to recovery no matter what I tried so I stuck a different kernel in that app, flashed it and once it booted I flashed the CWM 6.0.1.0 and I was completely fixed. Money well spent.
Edit..XhausX, I bought my first 2 HTCs ever about 2 weeks ago. They are both s on 1.13 but I need to either return on to full stock or use your rooted stock. I need to help my mother out. She's using a Samsung Moment! Ouch.... I am downloading that now. Is it a simple wipe and flash? If its more difficult, I will gladly shoot a donation your way if you can help me. I think I prefer her to be rooted stock so your odex version is the call...should have mentioned I know squat about the HTC methods. Regaw_Leinard got me where I am now
Sent from my EVO using Xparent SkyBlue Tapatalk 2
cgrimm9 said:
I don't mean to highjack anyone thread I was ready to do this since meanrom went with the evilz kernal. since I was s-on on the 1.15 boot. I was going to do this till I found a app on the market place called flash image gui which installed the kernal right on the phone.was simple and just plain easy no typeing anthing in just a click of a buttone.
Click to expand...
Click to collapse
Since the kernel is only writeable from the rom this does something similar, except it does it after you flash the rom and it's automatic.
You could look at it as the rom itself installs it's own kernel. That's one of the reasons why it may look so convoluted, but for a rom/kernel dev to actually implement it is easy once you know how it works.
JohnCorleone said:
I used Flash Image GUI on my NS4G all of the time. The last 2 updates were to add this phone and the Nexus 7. It takes about 10 seconds to flash a kernel or recovery img. Its a JoeyKrim app...so you know its legit. It actually saved me last night when testing a N7 kernel overclocked over 1.99. . The kernel somehow made my N7 not boot to recovery no matter what I tried so I stuck a different kernel in that app, flashed it and once it booted I flashed the CWM 6.0.1.0 and I was completely fixed. Money well spent.
Edit..XhausX, I bought my first 2 HTCs ever about 2 weeks ago. They are both s on 1.13 but I need to either return on to full stock or use your rooted stock. I need to help my mother out. She's using a Samsung Moment! Ouch.... I am downloading that now. Is it a simple wipe and flash? If its more difficult, I will gladly shoot a donation your way if you can help me. I think I prefer her to be rooted stock so your odex version is the call...should have mentioned I know squat about the HTC methods. Regaw_Leinard got me where I am now
Sent from my EVO using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
If you no longer need it rooted personally I would get s-off first and then run the latest RUU to restore it to stock. That way you'll always be able to re-root anytime without hassle, but the device can still be completely stock and used normally.
Zarboz said:
implimenting in my next installer
Click to expand...
Click to collapse
+1 on that, where do i add this in the updater and what do we do with Blk21 just leave it or will it work around it.
Is it possible to get a mirror of the Dev-Host file? The 'drivers are currently being updated', and I wanted to try adding this to my stock 2.13.651.1 ROM so as to avoid the inevitable questions from noobs that are S-ON about why the ROM won't boot .
Evolutionmods said:
+1 on that, where do i add this in the updater and what do we do with Blk21 just leave it or will it work around it.
Click to expand...
Click to collapse
Usually it's best to run it last so everything else is already in place. It will also check the recovery for the mount point, so that line won't be needed with it.
For your paranoid android rom you could use something like this: http://pastebin.com/rGVDKK2u
I'm not able to test it atm though so you'll probably want to verify it's good first.
Captain_Throwback said:
Is it possible to get a mirror of the Dev-Host file? The 'drivers are currently being updated', and I wanted to try adding this to my stock 2.13.651.1 ROM so as to avoid the inevitable questions from noobs that are S-ON about why the ROM won't boot .
Click to expand...
Click to collapse
mirror: https://dl.dropbox.com/u/18734200/kernel-installer-v0.56.zip
xHausx said:
Usually it's best to run it last so everything else is already in place. It will also check the recovery for the mount point, so that line won't be needed with it.
For your paranoid android rom you could use something like this: http://pastebin.com/rGVDKK2u
I'm not able to test it atm though so you'll probably want to verify it's good first.
mirror: https://dl.dropbox.com/u/18734200/kernel-installer-v0.56.zip
Click to expand...
Click to collapse
And of course the Dropbox link is now dead too .
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.
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?