neXusRecoveryCWM based recovery with touch controls
NOTICE: UMS MOUNTING IS A DRIVER ISSUE, FORCE YOUR WAY THROUGH IT !!!
See this for Help:
http://forum.xda-developers.com/showpost.php?p=36703043&postcount=58
http://forum.xda-developers.com/showpost.php?p=36705993&postcount=62
Features:
All CWM options + more
Navigation via swipe up down gestures.
Select and Back via Swipe Right and Left.
Battery Level and Time Display
All options working. UMS, graphic, no reboot
HOW TO FLASH:
Download "recovery.img"
Use "fastboot flash recovery recovery.img" in Fastboot mode
Reboot to recovery
DOWNLOADS
v1.1 Beta
SPECIAL EDITION V1.1: Link: http://d-h.st/8FS
NORMAL RELEASE:
DL Link:
http://d-h.st/AFe
v1.0 Initial Build
DL Link:
http://d-h.st/4R7
BUGS:
NONE YET
Code:
Special credits:
- Koush
- Lloir
- Claudyy
- TeamUtterChaos
- frostincredible
- Talatus
- cobje
OLD VERSION(Discontinued):
http://d-h.st/NBc
Nice one, added to Index.
Please put date of release in headline, and do it in future with next releases so we can track it.
Cheers mate, and thanks in for your work.
nlooooo said:
Nice one, added to Index.
Please put date of release in headline, and do it in future with next releases so we can track it.
Cheers mate, and thanks in for your work.
Click to expand...
Click to collapse
you're welcome. But it seems everyone is busy in new year celeb so no one testing
Thanks for that. I have the version that came with hasoon toolkit but it jumps left and right as you go down and up! Is this on the same?
Yasir Javed Ansari said:
you're welcome. But it seems everyone is busy in new year celeb so no one testing
Click to expand...
Click to collapse
I'm using your recovery and I like touch recovery. Backup and restore works flawlessly
Don't you want to continue your TWRP ?
ckpv5 said:
I'm using your recovery and I like touch recovery. Backup and restore works flawlessly
Don't you want to continue your TWRP ?
Click to expand...
Click to collapse
I always want an alternative to CWM coz it has bare basic features. TWRP was an option which had open source code so i tried it. But cant seem to be able to boot it. Something important is missing. But i may abandon it coz madmaxx said he might support desire X with 4EXT. and once 4ext comes, all the others will be rendered useless(kidding of course)
Regards
Yasir
So mount USB storage still doesn't work?
give me 1 more day
@Yasir Javed Ansari
Very happy with the progress of this Recovery, expecting more from you
Very happy with the progress of this Recovery......nice work
awesome ! i suppose the usb mount issue is the "e: unknown volume for path /sd-ext thing ?
Any progress my friend?
Syncing the jellybean tree is taking HELL more time than i imagined. But cobje is working on the device tree.
You can expect these in next release:
- graphic fixed
- sdcard mount (un-mounting has bugs if u guys have noticed or not)
- random reboot (still testing)
Regards
Noob question: what is the easiest way to flash a recovery without dozens of adb commands?
Only way now is
"fastboot erase cache"
"fastboot flash boot boot.img"
Sent from my awesome fridge
MaartenXDA said:
Only way now is
Sent from my awesome fridge
Click to expand...
Click to collapse
You mean
fastboot flash recovery recovery.img-path
fastboot reboot-recovery
fastboot erase cache
nlooooo said:
You mean
fastboot flash recovery recovery.img-path
fastboot reboot-recovery
fastboot erase cache
Click to expand...
Click to collapse
Ops yeah, thought he said kernel :3
Sent from my awesome fridge
swissly said:
Noob question: what is the easiest way to flash a recovery without dozens of adb commands?
Click to expand...
Click to collapse
MaartenXDA said:
Ops yeah, thought he said kernel :3
Sent from my awesome fridge
Click to expand...
Click to collapse
Are you sure?
Read my lips...
Graphic has been fixed , but as the recovery is closed source, I can't feed custom board config to fix UMS. That's why I'm also working on twrp.
Sent from my HTC Desire X
Hi Yasir, thank you so much for the fixes.
Graphics are working %100.
Backing up is working, will test restore soon.
What else would you like me to test?
Related
Hey all,
i just found in amon_ra netherlands blog, that he released 1.8.0
Version 1.8.0
http://www.androidworld.nl/41059/amon-ra-maakt-nieuwe-aw-recovery-voor-nexus-one/
Reported Errors: NoNe
i alsou found 1.8.0.1 on alternate coding.
Version 1.8.0.1:
http://alternate-coding.com/recovery-RA-nexus-v1.8.0.1-aw.img
Reportet Errors: USB-MS Toggle possibly not working (has to be done twice)
Flash Instructions:
#download the file
#copy to android-sdk\tools (or the folder where your fastboot.exe is)
#connect your device in fastboot mode
#open cmd and navigate to android-sdk\tools
#check if device is present with
Code:
fastboot devices
#flash recovery with
Code:
fastboot flash recovery <filename>
Works fine here and does everything it is supposed to be.
As i dont speek netherlands, i dont know anything about the
release notes/changes....just wanted to let u all know
Changelog for 1.8.0:
#Completely ignore verification
#Added menu loop scrolling
Changelog for 1.8.1:
#supports SLCD AND AMOLED
Changelog:
Completely ignore verification
Added menu loop scrolling
Get Google Chrome man, auto translate
Changelog AW-recovery V1.8.0:
- Completely ignore verification (both unsigned and signed can you flash zips)
- Added course menu (to roll from bottom to top)
thanks will try it out!
Translation:
http://translate.google.com/transla...very-voor-nexus-one/&sl=nl&tl=en&hl=&ie=UTF-8
I just downloaded it and flashed it to recovery. All looks good and I like the new blue. Different. Went into recovery and did a Nandroid backup, seems to be working ok.
Thanks
xxxid dutch just me or is the download button soooo well hidden a normal person cannot see it
Ok found it IN THE TEXT in case I am not the only one who is confused here is the link
http://dl.dropbox.com/u/4548341/awrecovery.img
Thyrus said:
xxxid dutch just me or is the download button soooo well hidden a normal person cannot see it
Ok found it IN THE TEXT in case I am not the only one who is confused here is the link
http://dl.dropbox.com/u/4548341/awrecovery.img
Click to expand...
Click to collapse
Humurous because the article says: "This means that we rejoice with the latest version not yet available on XDA-Developers."
Haha...it's released now!
Flashed on Nexus One...
All works just FINE.
Thank you for the news.
techlogik said:
Humurous because the article says: "This means that we rejoice with the latest version not yet available on XDA-Developers."
Haha...it's released now!
Click to expand...
Click to collapse
thanks to tigger it is
sweeeeeeet....
this has been posted in Amon_Ra's thread for a couple days
http://forum.xda-developers.com/showpost.php?p=7912159&postcount=1124
Thyrus said:
thanks to tigger it is
Click to expand...
Click to collapse
Couldnt stand to let XDA wait ^^
Also i found this on alternate coding:
http://alternate-coding.com/recovery-RA-nexus-v1.8.0.1-aw.img
but didnt try yet! ^^
Downloaded and flashed... Works great! Thanks!
madj42 said:
Downloaded and flashed... Works great! Thanks!
Click to expand...
Click to collapse
dija flash 1.8.0.1 ?
RinTinTigger said:
Couldnt stand to let XDA wait ^^
Also i found this on alternate coding:
http://alternate-coding.com/recovery-RA-nexus-v1.8.0.1-aw.img
but didnt try yet! ^^
Click to expand...
Click to collapse
Wait a second, that first link is for v1.8.0
This is for 1.8.0.1???
Can someone verify the latest and validity and that their recovery actually shows 1.8.0.1 with the above link?
I already was a guinea pig for the 1.8.0 and verified..someone else's turn...haha
techlogik said:
Wait a second, that first link is for v1.8.0
This is for 1.8.0.1???
Click to expand...
Click to collapse
aye, i just recently found it in a german forums linkingf to alternative coding
RinTinTigger said:
aye, i just recently found it in a german forums linkingf to alternative coding
Click to expand...
Click to collapse
Ok, fine, let me nand backup and flash this one...here it goes...will report back momentarily.
EDIT:
Ok, I just flashed that second link, it shows the same version in RA recovery as the first link download I flashed.
Build : RA-nexus-v1.8.0
When he released 1.7.0.1, it shows that in the RA utility.
Just use the first link, it is an accurate description of the actual version form what I can tell. There doesn't appear to be a 1.8.0.1.
Just flashed v1.8.0...very nice and much easier to read! Love the blue vs. the red
i can't get my computer to recognize my device, so if i want to do it by terminal emulator i have to do this?.....
copy "awrecovery.img" to the root of my sd card
then go in to terminal emulator and type "su", and then type "recovery flash_image/SDcard/awrecovery.img"
and then type "reboot recovery" and then that should do it? or am i doing something wrong? i just want to be sure before i mess anything up......lol
su
flash_image recovery /sdcard/awrecovery.img
reboot recovery
i flashed few days back
SubyWill said:
i can't get my computer to recognize my device, so if i want to do it by terminal emulator i have to do this?.....
copy "awrecovery.img" to the root of my sd card
then go in to terminal emulator and type "su", and then type "recovery flash_image/SDcard/awrecovery.img"
and then type "reboot recovery" and then that should do it? or am i doing something wrong? i just want to be sure before i mess anything up......lol
Click to expand...
Click to collapse
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.
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?
This is for 201 user running KatKiss android 5.0 !!!!!
DEV THREAD
KatKiss-5.0_TF201T_014b_signed.zip
The original thread this spinoffed from: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783
Couple of issues I've had as a newbie to flashing Androids, I hope I get these right. I already wrote about these in the Q&A, but I think we could start the thread with these:
1) You must upgrade you're bootloader. The last OTA was 4.1.1 (?), you need 4.2.1. Without upgrading, the device will try to boot but after a minute or two, it will reboot over and over again. I used instructions from CROMBi-kk http://forum.xda-developers.com/showthread.php?t=2773812#4. EDIT: or just follow lj50036's instructions below in #3
2) Do not install K.A.T apps. Or if you had it in your KatKiss 4.4, do not restore it from the backups. I had lagginess, short and permanent freezes, reboots. After removing it, TF201 has worked like a charm. EDIT: May have been a coincidence...
The boost in stock OTA Android from Asus is huge. The device responds immediately to touch and is way faster than I could have ever hoped. Thank you timduru and others involved!
lj50036 said:
UPGRADE INSTRUCTIONS, STEP BY STEP
This may help
Starting from a stock bootloader V 10.4.2.18
What you will need
Woking fastboot & adb / SDcard optional
TWRP for a 201 = twrp_tf201t.blob
@ne0zone75 TWRP for the 300 = ne0zone75_tf300t.blob
HairyBean BL & TWRP: This is effectively turn your 201 into a 300 <---- which is a flashable zip inside the zip that you downloasd
All 3 of the above file are in a zip in the Download section @ the top of every page of the thread ...... THIS ZIP IS NOT FLASHABLE...Your must unzip it to get to the real files !!! The name of this zip is
upgrade_tf201_to_tf300t.zip
foo 201 ROM zip
A fully charged tablet
All the above files in the same directory as your fastboot.exe (if using windows) In your home folder on linux....
The process
Lets start with the TWRP recovery for the 201, let flash it with fastboot...
Power your tablet off and with the [ VOL DOWN & POWER ] buttons boot the tablet into the bootloader
Once there [ VOL DOWN ] untill the green box is on the USB ICON then [ VOL UP ] to select fastboot
Let make sure your PC can see your tablet with this command.
Code:
fastboot devices
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
Then
Code:
fastboot -i 0x0b05 reboot-bootloader
[ VOL UP ] ON RCK to enter recovery
Once in TWRP check to see if adb is working...
Code:
adb devices
Ok now that we know that is working let go ahead and push the HairyBean BL onto the tablet
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now under the install tab in TWRP fine the folder and flash it....
reboot once it has fishined..If ask to install SuperUser say NO..........
LET THE BLUE BAR FILL !!!!!!!!! Once it has finished it will reboot into Hairybean TWRP....
Once booted into recovery, run this command to boot into fastboot
Code:
adb reboot-bootloader
You will see that the USB icon is missing now, this is good... If you still see the USB icon DON'T go to the next step
Now lets flash @ne0zone75 TWRP recovery
Code:
fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob
Once that has finished let reboot into bootloader
Code:
fastboot -i 0x0b05 reboot-bootloader
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Now lets push foo.zip onto your tab
Code:
adb push foo.zip /sdcard
Find it under the install tab and flash it..
REBOOT into android, first boot can take up to 15 minutes
Click to expand...
Click to collapse
Thx Josh
apartypooper said:
2) Do not install K.A.T apps. Or if you had it in your KatKiss 4.4, do not restore it from the backups. I had lagginess, short and permanent freezes, reboots. After removing it, TF201 has worked like a charm.
Click to expand...
Click to collapse
I doubt that it was the app causing that,
but Lollipop is only supported since the version 2.0.1 of the K.A.T app,
so if you want it to work that's definitely the one you need to use, and not restore an older version.
For the freezes that were discussed in the previous thread, I've noticed it happens alot when using the browser .
random reboots
Big fan of all the developers keeping the prime alive, thankyou very much.
Very glad this Q&A has been opened, not got many posts so cant post on developer parts.
Usually find answers by reading, but realized thats just not enough any more, got to help the developers, if they are still willing to help us.
As it is written everywhere that most of the developers no longer have a tf201.
So ive been reading up on getting logcats, kmsg etc.
If their is anything i can post here, please let me know.
Been getting a few random reboots myself.
Thanks again
goosebickel said:
Big fan of all the developers keeping the prime alive, thankyou very much.
Very glad this Q&A has been opened, not got many posts so cant post on developer parts.
Usually find answers by reading, but realized thats just not enough any more, got to help the developers, if they are still willing to help us.
As it is written everywhere that most of the developers no longer have a tf201.
So ive been reading up on getting logcats, kmsg etc.
If their is anything i can post here, please let me know.
Been getting a few random reboots myself.
Thanks again
Click to expand...
Click to collapse
After one of these random reboot can you post a last_kmsg plz...
Let the tab boot after said random reboot and run this command from terminal ....
Code:
adb pull /proc/last_kmsg
Thx Josh
lj50036 said:
After one of these random reboot can you post a last_kmsg plz...
Let the tab boot after said random reboot and run this command from terminal ....
Code:
adb pull /proc/last_kmsg
Thx Josh
Click to expand...
Click to collapse
It wouldn't let me upload as txt file, so i stuck it in a zip
Hope it helps
timduru said:
I doubt that it was the app causing that,
but Lollipop is only supported since the version 2.0.1 of the K.A.T app,
so if you want it to work that's definitely the one you need to use, and not restore an older version.
Click to expand...
Click to collapse
You're probably right. I installed KatKiss a week ago and it had been unstable and laggy until I froze K.A.T with link2sd. I unfroze it now and everything seems fine. *knock knock*
The device froze twice a moment ago (before unfreezing K.A.T). According to logcat, the device registered pushing power buttons on both the tablet and keyboard, but the screen stayed frozen. I was able to restart the launcher (nova) from adb shell, but it froze again soon after. I now switched back to launcher3, lets see if works better
goosebickel said:
It wouldn't let me upload as txt file, so i stuck it in a zip
Hope it helps
Click to expand...
Click to collapse
The first thing that needs to happen is I need to work on a zImage + ramdisk ......
I am working on this as we speak ..... :good:
Thx Josh
camera logcat
Camera boots up fine but crashes when photo is taken.
Got a logcat if it helps
Thanks again for all the help
goosebickel said:
Camera boots up fine but crashes when photo is taken.
Got a logcat if it helps
Thanks again for all the help
Click to expand...
Click to collapse
Well I found this ....
The service starting ......
Code:
I/CameraService( 8115): CameraService started (pid=8115)
I/CameraService( 8115): Loaded "NVIDIA Development Platform Camera HAL" camera module
And the cam not liking this ....
Code:
E/NvOmxCamera( 8115): Could not get config for CONFIG_LENS_PHYSICAL_ATTR (80001001)
Lets see where this goes ..... :good:
Thx Josh
Bootlooping at this point.. Sometimes I don't get the last message but anyways it would not boot.
Maybe I don't have a compatible bootloader? I'm coming from PA 4.5, I'll give this a look tomorrow and see if I can get what's wrong
Enviado desde mi XT1068
zodiark said:
Bootlooping at this point.. Sometimes I don't get the last message but anyways it would not boot.
Maybe I don't have a compatible bootloader? I'm coming from PA 4.5, I'll give this a look tomorrow and see if I can get what's wrong
Enviado desde mi XT1068
Click to expand...
Click to collapse
Well what is your bootloader version ?
That pic looks like the preinit from crombi ?
I am working on things as fast as I can .....
Let me put something together ...
Thx Josh
Yes, it's because of my bootloader, I need to update it to the 4.2 version.
I'll try to update it this afternoon, thanks for your help and your work!
Enviado desde mi XT1068
Will twrp 2.7 work in flashing this ROM, comparability pack, and gapps
Itzamistry said:
Will twrp 2.7 work in flashing this ROM, comparability pack, and gapps
Click to expand...
Click to collapse
Yep that will do it for now ...
I am working on somethings ....
Should know more a bit later today ...
Thx Josh
Upgraded bootloader and reinstalled.. WOW! That's all I can say. It's fast, feels snappy, just amazing! It's like a new tablet.
Again thanks to everyone who made this ROM, very good job!
Has anyone tried using the ROM's encryption feature? I've had issues where the password/pin is not recognized in the past. Wondering if its a result of the custom 201/301 bootloader and recovery. Right now on tf201 with Twrp geass 2.7, geass v7 kernel and katkiss v36. Had PW issue with twrp 2.8.2
Sent from my Nexus 4 using Tapatalk
lj50036 said:
Yep that will do it for now ...
I am working on somethings ....
Should know more a bit later today ...
Thx Josh
Click to expand...
Click to collapse
Im up for testing if you need a guinnie pig.
## I TAKE NO RESPONSIBILITY IF YOU BRICK YOUR DEVICE##
THIS IS A MATERIAL TWRP IMG THAT I MADE FOR THE PAYTON
I HAVE TESTED THIS WHIT MY OWN DEVICE
ITS IS FULLY STABLE NOW YOU ALL TO ENJOY!!!
BUT IM STILL TWEAKING THING
INSTALL THE SAME WAS AS EVERY OTHER TWRP IMG
RECOMMEND CLEAN INSTALL DO NOT INSTALL OVER OTHER TWRP
reboot to bootloader
run this command
Fastboot boot TWRP-payton-material.img
wait for it to boot
then flash the installer zip
IF YOU KEEP REBOOTING BACK INTO TWRP REFLASH MAGISK
TO GET THE ADD ON TO BE ABLE TO CHANGE COLOR LAYOUT AND ALL THAT
AFTER FLASH COMPLETELY REBOOT BACK TO OS
THEN REBOOT BACK TO TWRP CLICK THE ICON NEXT TO SETTING IN THE TOP RIGHT
IT WILL ASK YOU FOR UI.ZIP CLICK CHANGE THEME SWIPE TO FLASH AND THERE YOU GO
DOWNLOAD
I HOPE EVERYONE ENJOYS!!!
FEATURES SO FAR
EVERYTHING IS WORKING!!!
MTP(YES)
OTG(YES)
ADB SIDELOAD(YES)
DECRYPTION(YES)
BONUS TWEAKS BUILT IN (YES)
GROUP AND BUG REPORTS
will this stay in place with a rom OTA (like havoc?)
themedicduck said:
will this stay in place with a rom OTA (like havoc?)
Click to expand...
Click to collapse
At this time i cant give a 100% yes
I only have a couple of beta tester as of right now
But they have reported it work like normal
so I do be leave that it will
if you do a OTA and it fails please tell me asap
Im still working on it but is stable enough to be beta tested :good:
FizzyAps said:
At this time i cant give a 100% yes
I only have a couple of beta tester as of right now
But they have reported it work like normal
so I do be leave that it will
if you do a OTA and it fails please tell me asap
Im still working on it but is stable enough to be beta tested :good:
Click to expand...
Click to collapse
Good deal.
I'm guessing dirty flashing this over my current TWRP is a bad idea? Clean install?
Recommend clean install do not install over other twrp
FizzyAps said:
Recommend clean install do not install over other twrp
Click to expand...
Click to collapse
Ok.
Did you do anything special to get this to build?
What sources are you using? Omni trees or los?
gee one said:
Did you do anything special to get this to build?
What sources are you using? Omni trees or los?
Click to expand...
Click to collapse
I de-compiled the official 3.2.3-1 and syberhexen 3.2.3-0
and re-compiled
them together with the themed ui the us see to get stable result
so mix of both
gee one said:
Did you do anything special to get this to build?
What sources are you using? Omni trees or los?
Click to expand...
Click to collapse
you can follow the build and updates on all are twrps here
https://t.me/motox4twrp
themedicduck said:
will this stay in place with a rom OTA (like havoc?)
Click to expand...
Click to collapse
There is no longer a recovery partition, instead recovery is built into the boot.img on X4 (and all other slot A/B devices)
So when you flash a rom, that file gets updated and you loose twrp.
The only way around that would be a custom installer that manually installs twrp during flash.
SchmilK said:
There is no longer a recovery partition, instead recovery is built into the boot.img on X4 (and all other slot A/B devices)
So when you flash a rom, that file gets updated and you loose twrp.
The only way around that would be a custom installer that manually installs twrp during flash.
Click to expand...
Click to collapse
Gotcha ok. I think I get it now. So if I don't want TWRP to be overwritten, I'll just have to manually flash updates every time like I do now.
themedicduck said:
Gotcha ok. I think I get it now. So if I don't want TWRP to be overwritten, I'll just have to manually flash updates every time like I do now.
Click to expand...
Click to collapse
You have to flash TWRP after every rom flash whether its OTA or manual.
Thank you for providing the decrypt function.
But I use a 6x6 pattern, and it is literally impossible to succeed with my pattern since the dots are so close together. Possible to spread them out?
I need to know: What are the bonus tweaks built in? Thanks
flieswithhawks said:
I need to know: What are the bonus tweaks built in? Thanks
Click to expand...
Click to collapse
Everything listed in the post
Which installer, TWRP-payton-Material-stb1 or TWRP-payton-material-installer? What's the difference?
flieswithhawks said:
I need to know: What are the bonus tweaks built in? Thanks
Click to expand...
Click to collapse
BONUS TWEAKS BUILT IN (YES)
It says right there. (YES)
I'd also like a list of what exactly the bonus tweaks are, as they are apparently mixed in with regular non-tweaked content.
So, in the context of recovery images... how exactly is there such a thing as a "dirty" flash? A flash is a flash for the recovery image. It is contained. What am I missing?
Please tell me!
TWRP-payton-Material-stb1.img or TWRP-payton-material.img - what's the difference, which one to use? Will the project be further developed - 3.3.1-0?
Thank you for a good job!
@FizzyAps Nicely done. Although I wish I could get the theme used when booting from the IMG file (TWRP-payton-material.img). -- That was impressive! Unfortunately, I see that the installer (and the ui.zip) do not include that. Still, it is both a visual and tech improvement over the current stock TWRP.