Related
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
Please see this safer/easier/faster method instead of using the one below http://forum.xda-developers.com/showthread.php?p=36976137#post36976137
Original guide provided below for historial purposesonly, seriously use hte one above:
Please refrain from repackaging, or rehosting my materials, ask prior to deciding to.
If this guide fails, or the auto script (which I will not recommend you use) fails, please do a factory reset before attempting again.
If you appreciate this, please make sure you check out my original article on the AndroidPolice. Without the support of AP, I wouldn't spend nearly as much time doing this. To the bloggers who will chose to link to a forum post, rather than the original post on a better blog, you suck.
http://www.androidpolice.com/2012/11/24/exclusive-how-to-unlock-the-droid-dnas-bootloader/
Donations for new test devices can be made at the paypal link to the left. I reserve the right to send leftover funds to whatever charities I feel like. Generally I choose Boys and Girls club of america, sometimes I choose seasonal charity, or a medical related one.
Known Problems:
Adb server is out of date
Uninstall HTC Sync, Samsung Kies, etc any software that talks to the phone.
If you get stuck, please immediately find someone in our chat that knows what they are doing. It is very easy to brick your phone if you follow these directions incorrectly, or if a problem arises!
Need faster help? or Want to help visit our chat
http://chat.andirc.net:8080/?channels=#droid-dna
Credits:
Original development: jcase
Awesome saver of the day: Sean Beaupre
Crash test dummy: dsb9938 (I bricked his phone making this!)
Artem and all @AndroidPolice for putting up with my nonsense.
Special thanks to Fuses for recommending a better target, and the numerous testers that let me play with their new phones.
Click to expand...
Click to collapse
Warning: This is semi complicated, and is known to ruin phones if done incorrectly. Proceed at your own risk
Needed:
1gb free space on the phone.
Working adb, must support the adb restore feature (ICS and up!)
Downloads:
backup.ab (300mb) mirrors: http://d-h.st/tau - http://depositfiles.com/files/9c61r4lgo - http://www.filefactory.com/file/2va8yp2i1h99/n/backup.ab
DNA_TeamAndIRC mirrors - http://d-h.st/D4r - http://www.putlocker.com/file/F357F205F5235B3D - http://rapidgator.net/file/59342799/DNA_TeamAndIRC.zip.html
Unzip DNA_TeamAndIRC, put runme.sh, CIDGen.apk and backup.ab into the directory where adb is (or anywhere if you have your paths setup right).
Please Check the readme.txt before continuing!
Code:
adb install CIDGen.apk
Run the CIDGen app on your phone, enter the last digit of your IMEI (NOT YOUR MEID) and press generate. Then confirm the generated file exists.
Code:
adb shell ls -l /sdcard/CIDBLOCK.img
If CIDBLOCK.img does not exist, run the app and try again. Do not proceed without generating a CIDBLOCK.img, it is needed to repair the phone and unlock.
Once you have CIDBLOCK.img on your sdcard, open two terminals (command prompts) and continue
In the first terminal/cmd prompt run these commands:
Code:
adb push runme.sh /data/local/tmp/
adb shell chmod 755 /data/local/tmp/runme.sh
adb shell /data/local/tmp/runme.sh
runme.sh will continue to loop and spit out No such file or link failed errors, just leave it running for now.
In the other terminal/cmd prompt run this commands:
Code:
adb restore backup.ab
Then allow the restore on your phone. Once the process is finished, you can go back to the looping terminal and stop it with control + c, or close the terminal
At this point, do not continue unless you are certain you can do this. Past this point, is where people can brick if they do not follow the directions correctly. If you run into a problem, find someone to help you. Do NOT power your phone off or reboot it. Leave it charging and find someone.
Code:
adb shell rm /data/data/com.htc.usage/files/exploit/*
adb shell mv /data/DxDrm /data/DxDrm_org
adb shell mkdir /data/DxDrm
adb shell ln -s /dev/block/mmcblk0p5 /data/DxDrm/DxSecureDB
adb reboot
Once the phone is rebooted, open two terminals and repeat the restore exploit:
In the first one:
Code:
adb shell /data/local/tmp/runme.sh
This process will also loop forever and give out lots of "No such file" or "link failed" errors - again, just leave it running.
In the second terminal, restore the backup again:
Code:
adb restore backup.ab
After the restore is done, we will undo the DxDrm symlink attack and write the new CIDBLOCK.img:
Code:
adb shell mv /data/DxDrm /data/DxDrm_trash
adb shell dd if=/sdcard/CIDBLOCK.img of=/dev/block/mmcblk0p5
If this returns an "out of space error" come to our chat, and find either jcase or beaups. Do not reboot. Do not continue.
Code:
adb reboot
After reboot, you can go to http://HTCDev.com, and unlock through their official process. Choose the "All other supported models" option when selecting your phone.
Cheers!
Is there a one-click for this?
Sorry, I couldn't resist!
Support chat: http://chat.andirc.net:8080/?channels=#droid-dna
D
.
no comment...
btw great job guys!! :good:
dsb9938 said:
Is there a one-click for this?
Sorry, I couldn't resist!
D
.
Click to expand...
Click to collapse
Awesome.....now I just need the actual phone.
UPS HURRY UP!!!
awesome
Awesome work J and D...
Aight D where is the "cubed" lol
gramsey1911 said:
Awesome work J and D...
Aight D where is the "cubed" lol
Click to expand...
Click to collapse
Next week! Sheesh.
D
.
dsb9938 said:
Next week! Sheesh.
D
.
Click to expand...
Click to collapse
I'm feenin ova here for the cubed...lol
dsb9938 said:
Is there a one-click for this?
Sorry, I couldn't resist!
Support chat: http://chat.andirc.net:8080/?channels=#droid-dna
D
.
Click to expand...
Click to collapse
Lol.... I'm going to wait for the one click, can't afford to brick my device while trying to unlock with 2 kids running around lol...
P.s. thank you j case and DSB for the unlock and root
Sent from my HTC6435LVW using xda premium
typeriz said:
Lol.... I'm going to wait for the one click, can't afford to brick my device while trying to unlock with 2 kids running around lol...
P.s. thank you j case and DSB for the unlock and root
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I wouldnt trust a one click, i automated the PITA part already with the CIDGEN app
This is for the new bootloader right. Just wanna make sure.
Sent from my HTC Droid DNA
typeriz said:
Lol.... I'm going to wait for the one click, can't afford to brick my device while trying to unlock with 2 kids running around lol...
P.s. thank you j case and DSB for the unlock and root
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I just did it, and it's really not that hard, took maybe 10 minutes, just copy and paste the commands and you should be good :good:
So I was able to unlock with this method via HTCDev, I installed TWRP and the insecure kernel, but my SuperSU will not work after I flashed the file in recovery. None of my apps can get root access, and I cannot update the superuser binary via SuperSU. What's going on here?
Argumentation said:
I just did it, and it's really not that hard, took maybe 10 minutes, just copy and paste the commands and you should be good :good:
Click to expand...
Click to collapse
I'm going to wait till I put the kids to bed, tonight. Thanks again !!
Sent from my HTC6435LVW using xda premium
---------- Post added at 04:32 PM ---------- Previous post was at 04:29 PM ----------
TheBiles said:
So I was able to unlock with this method via HTCDev, I installed TWRP and the insecure kernel, but my SuperSU will not work after I flashed the file in recovery. None of my apps can get root access, and I cannot update the superuser binary via SuperSU. What's going on here?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=34551547
How unlock and root work on the Droid DNA.
I belive you have to manually update it
Sent from my HTC6435LVW using xda premium
jonah1234 said:
This is for the new bootloader right. Just wanna make sure.
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
Huh, this is for the htc droid dna in general.
TheBiles said:
So I was able to unlock with this method via HTCDev, I installed TWRP and the insecure kernel, but my SuperSU will not work after I flashed the file in recovery. None of my apps can get root access, and I cannot update the superuser binary via SuperSU. What's going on here?
Click to expand...
Click to collapse
Sounds like bad or incorrect su binary
Try Superuser instead of SuperSU
WHERE IS THE IMEI!?
madzozs said:
Try Superuser instead of SuperSU
Click to expand...
Click to collapse
That worked! I'm not sure why SuperSU doesn't work, but oh well!
jonah1234 said:
WHERE IS THE IMEI!?
Click to expand...
Click to collapse
On your box!
Never mind. Figured out the issue. Now it's just hanging at full restore. There's no password right? I selected restore my data and nothing happens.
thebiles said:
that worked! I'm not sure why supersu doesn't work, but oh well!
On your box!
Click to expand...
Click to collapse
found it haha i fail
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Thank you! I'll update my guides now you made some folks very happy today.
Sent from my VS980 4G using Tapatalk 4
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
Phew, you were one of the guys I was worried about who were unlucky enough to be stuck in boot loop WITHOUT adb. Glad he got you working again!
WACOMalt said:
Phew, you were one of the guys I was worried about who were unlucky enough to be stuck in boot loop WITHOUT adb. Glad he got you working again!
Click to expand...
Click to collapse
I am too LOL Thanks for all your help
I had nothing to do with it, all thanks go to thecubed/IOMonster
Sent from my VS980 4G using Tapatalk 4
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
Cool! :victory:
Glad to see you have yours working. I left mine at home today and brought the S4 instead so I'll fix my G2 tonight. Thanks for the help everyone!
jspradling7 said:
Cool! :victory:
Glad to see you have yours working. I left mine at home today and brought the S4 instead so I'll fix my G2 tonight. Thanks for the help everyone!
Click to expand...
Click to collapse
Yeah that's what I did yesterday as well used my s4 glad I didn't sell it yet
thecubed said:
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Click to expand...
Click to collapse
I could swear I said just nuke the FOTA partition sometime yesterday as usual awesome job.
thecubed said:
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Click to expand...
Click to collapse
Thank you!! Where do I send the beer money?
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
---------- Post added at 09:45 AM ---------- Previous post was at 09:16 AM ----------
Walter21026 said:
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
Click to expand...
Click to collapse
Nevermind I found it, not used terminal before in recovery, phone back up and running
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
I was upset yesterday worrying about you guys. I am happy to see you happy. Thanks much OP for the fix.
I am rooted and installed TWRP recovery but reverted back to the stock recovery before accepting the VZW OTA update. I'm now stuck in a boot loop and I can't get ADB to recognize my device when plugged in via USB. When I plug in my phone it shows the following:
Fastboot mode started
udc_start()
-reset-
-portcharge-
-reset-
-portcharge-
fastboot: processing comands
Any idea why this is happening and how I can get my phone to boot normally?
Walter21026 said:
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
---------- Post added at 09:45 AM ---------- Previous post was at 09:16 AM ----------
Nevermind I found it, not used terminal before in recovery, phone back up and running
Click to expand...
Click to collapse
I too get the file folder. How do i get the terminal command in TWRP?
synplex said:
I too get the file folder. How do i get the terminal command in TWRP?
Click to expand...
Click to collapse
When you see the file folder just ignore that and hit "select "on the bottom right and that will bring it up. Just type the command from there
Thanks it worked!:laugh: Should I flash stock now update via OTA then reroot and reflash TWRP??
synplex said:
Thanks it worked!:laugh: Should I flash stock now update via OTA then reroot and reflash TWRP??
Click to expand...
Click to collapse
I didn't. From what I've read its just best to flash the new TWRP and not worry about the new OTA. Besides there is nothing relevant about the OTA enough to worry about going through all the trouble of installing the OTA. Also the devs have pulled all the new update files and they will use those in their Roms
Walter21026 said:
I didn't. From what I've read its just best to flash the new TWRP and not worry about the new OTA. Besides there is nothing relevant about the OTA enough to worry about going through all the trouble of installing the OTA. Also the devs have pulled all the new update files and they will use those in their Roms
Click to expand...
Click to collapse
Yea, let's just wait for a ROM worth flashing and "F OTA"
How can we get the OTA if we have TWRP installed?
Can we falsh stock recovery and then accept the Update?
If so can someone please post the Stock Recovery IMG?
My phone is at the LG screen and the notification light is blinking but thats it. How can I adb anything or get into twrp?
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?
Like a FOOL, I allowed myself to press "update" when I got a new system update screen this morning, while I was half asleep. It rebooted and went to TWRP. I'm on @runningnak3d 's Nougat v30b update. I tried a wipe and reflash the 30b update, but each reboot goes only to TWRP. If anyone can help me sort this out, I'd appreciate it. Nothing like doing stuff wrong when you are waking up. Thanks johnm
You're not the only fool.... same issue here :-/
Try this. https://forum.xda-developers.com/showpost.php?p=73457443&postcount=166
LexQ45 said:
Try this. https://forum.xda-developers.com/showpost.php?p=73457443&postcount=166
Click to expand...
Click to collapse
...aaaand we're back!
I'd ask how, but I don't think I'd understand the explanation.
LexQ45 said:
Try this. https://forum.xda-developers.com/showpost.php?p=73457443&postcount=166
Click to expand...
Click to collapse
yeah @LexQ45! saved us sleepy idiots days of refreshing this thread to see if someone could bestow the magic! special thank you to @RainGater, right on!!
jmacie said:
yeah @LexQ45! saved us sleepy idiots days of refreshing this thread to see if someone could bestow the magic! special thank you to @RainGater, right on!!
Click to expand...
Click to collapse
So this 85.3 mb system update that keeps nagging, we just need to get it into the form of an update.zip, and flash that. I'm gonna need some help with that. I'm glad people are still reading these v10 threads, or I'd be hung out to dry. Good Luck all! Thanks again!
If someone will grab the update.zip off their phone, I will be glad to make it safe to flash. It used to be in /cache but they may have moved its location. If it is not in /cache then:
* adb shell
su
find / -name update.zip
Post a link here and @ mention me
-- Brian
This is odd. For some reason, after I did the encryption fix a few post back, it's now asking for a knock code. I have no idea why it's asking me for one. Anyone else come across this?
runningnak3d said:
If someone will grab the update.zip off their phone, I will be glad to make it safe to flash. It used to be in /cache but they may have moved its location. If it is not in /cache then:
* adb shell
su
find / -name update.zip
Post a link here and @ mention me
-- Brian
Click to expand...
Click to collapse
Got the update.zip-- https://1drv.ms/u/s!Aj2kG39SSb1iheAMAuixcT9Bl2udgQ
Thanks @runningnak3d , I'm sure your continued help is appreciated by all! Thank you!
I just took a quick look with root explorer, and DO NOT flash that. It will increment ARB, lock your boot loader, and wipe out TWRP.
I will be able to look and see if there is any part of it that is worth flashing once I am in front of my PC again, but I wanted to get the warning out.
Keeping an eye on this thread. Just received the update notification. Being that I use this on cricket I assumed I wouldn't get the update but it showed up today.
Guess I was the only one that experienced that knock code entry. Well, FYI, if you install that update, you may be asked to use a knock code that you never configured. Blah.
All in all, just reinstalled everything and started from scratch. Woohoo!
Any flashable zip file?
nah chet