Develop Bugs

Rom Manager/Clockwork Recovery

As most of you already know I have no trackpad and due to this I can't use custom recoverys. I've been campaigning for an option to use power to select so I can use recovery again.
Now I have a problem that I can't flash any froyo roms but can flash others fine. I've narrowed down the problem I think. It's definitely not SD card related or ext related. I think the rom manager does not wipe every necessary thing that it needs to. When I could use recovery before I could flash froyo roms. Now I have rom manager as my only option and it only seems to wipe data cache and ext.

ROM Manager didn't wipe SD-EXT for me.
If you use linux then format your card in it and try again. Maybe this helps.
Will post again when something crosses my mind
EDiT: Just read your post again. Are you shure it's not SD?
OK. Then try using... damn you and your trackball

BlackLine7 said:
ROM Manager didn't wipe SD-EXT for me.
If you use linux then format your card in it and try again. Maybe this helps.
Will post again when something crosses my mind
EDiT: Just read your post again. Are you shure it's not SD?
OK. Then try using... damn you and your trackball
Click to expand...
Click to collapse
Yeah i have tried reformat of sd card. Tried a new sd card with only fat32 on it. Tried a version of froyo without a2sd.
Really stuck haha.

So what's stopping you going stock and taking it back for exchange? The T-Mobile ROM is available so I'd just do that!!

Warranty void. It's only the trackpad it would be fine if I wasn't such a rom whore lol

The warranty isn't void if you go back to stock...they won't even know you flashed a Rom
Sent from my HTC Desire using Tapatalk

j2kquest said:
The warranty isn't void if you go back to stock...they won't even know you flashed a Rom
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Read his sig. LOL
Edit: For those of you in tapatalk and can't see signatures.
Probably the first person in the WORLD to drop their Desire in a drink!
Repaired via disassembly and using Contact Cleaner. Thanks user abc27.
A FIVER GOES TO THE FIRST PERSON TO MAKE A RECOVERY FOR THE DESIRE THAT ACCEPTS ANY OTHER THAN TRACKPAD PRESS TO CONFIRM. I HAVE NO TRACKPAD SO CAN USE NOBODYS RECOVERY!
Click to expand...
Click to collapse

socktug said:
Read his sig. LOL
Edit: For those of you in tapatalk and can't see signatures.
Click to expand...
Click to collapse
Ha thank you. Yeah water damage equals instantly void. I opened it up and fixed it but 2 months later the trackpad is totally gone. I just really want the ability to use recovery fully again.

What if you test your luck and bring it back like this?
With stock rom ofc
If they say no... you could just pay for the trackpad!

BlackLine7 said:
What if you test your luck and bring it back like this?
With stock rom ofc
If they say no... you could just pay for the trackpad!
Click to expand...
Click to collapse
that makes sense....(htc sense ) nah, but really.....if it costs even 50 bucks id still say thats worth it....a 400quid phone with limited usability....?

The phones fine. I only need trackpad for recovery. Or alternate button.

I wouldn't hope too much on someone developing another recovery...
What if you edit the rom you are using and remap you trackpad press to another button?
Like the search button which i personally never use
EDiT: I'm not 100% shure this would work in recovery... but it's worth a try!

I'm pretty sure it needs to be edited within the recovery its not rom specific.

Hmm... your point seems right since all the modules are loaded in the rom and none of them is used for recovery...
I will check the AMDesireRecovery and look where they have all those button settings

BlackLine7 said:
Hmm... your point seems right since all the modules are loaded in the rom and none of them is used for recovery...
I will check the AMDesireRecovery and look where they have all those button settings
Click to expand...
Click to collapse
Thanks. I have no idea where to start. All i know is that it is possible. Clockwork 2.0.0.3 had it but it couldn't mount the sd card or anything but the power button did select! I don't know how to edit a recovery or what file controls what. I mean there is a "keys" file but is that keys as in buttons or something else?

I think that the keys file is the verification if the zip is signed... I may be wrong...
What if we somehow merge the files of a recovery which uses power to select with a newer recovery?
Can you provide 2.0.0.3 of ClockWorkMod?

Ok just tried straight swapping the keys file and that did nothing. No response.
EDIT: Give me 2 mins.
EDIT2: Uploading very slowly. It would be great to have 2.0.0.3 merged with 2.0.1.4 (latest) as that would give me all the functionality i need.

Oh damn... the recoveries need to be signed so the stock recovery can eat them...
Do we need a special sign for that?

Yeah. There is a thread on here somewhere that has the tools for signing them...it's on the first page i'll have a quick look.
Here http://forum.xda-developers.com/showthread.php?t=709141 bottom of the post.

I know how to sign files but I was wondering if we need some HTC cert for signing.
I will try to do it with the normal one if needed.
We have a problem... if I edit the files and put it back together I can't test it coz I have flashed the permanent version. :S

[RELEASE] Bandroidx's Bravo Bootstrap Custom Recovery

Ok all, waiting is finally over. Thanks for being so patient! I got the donate version up on the market, if you dont have the market in your country or can't make the purchase I will have a free version out (w/ banner ads) in a couple of days once I finish testing that version.
https://market.android.com/details?id=com.bandroidx.motobravo.bootstrap
Couple of notes:
1) When you hit the bootstrap button the first time, it could take a few seconds, wait until you get a success message before touching the screen again. if you get a force close message, please select wait. Usually it takes just 3-5 seconds. It can take longer though especially if you have just rooted, i recommend rebooting after rooting always.
2) After you bootstrap recovery you do not need to bootstrap again until you update to a new version of my app, after upgrading you should bootstrap once. After that you just load the app and hit reboot recovery.
3) If you are not familiar with the bootstrap process (like on the dx/d2) please be aware this does not replace your stock recovery like regular CWM. The Custom recovery can only be started by loading the app and clicking bootstrap recovery.
4) Tested more on 2.2 but 2.1 should also be fine if you havent upgraded yet (why?)
Heydabop is working on his CWM flashable boot animation and I am going to start looking into doing a bravo ROM. Thanks for all heydabop's awesome graphics!
Enjoy!

bandroidx said:
Ok all, waiting is finally over. Thanks for being so patient! I got the donate version up on the market, if you dont have the market in your country or can't make the purchase I will have a free version out (w/ banner ads) in a couple of days once I finish testing that version.
https://market.android.com/details?id=com.bandroidx.motobravo.bootstrap
Couple of notes:
1) When you hit the bootstrap button the first time, it could take a few seconds, wait until you get a success message before touching the screen again. if you get a force close message, please select wait. Usually it takes just 3-5 seconds. It can take longer though especially if you have just rooted, i recommend rebooting after rooting always.
2) After you bootstrap recovery you do not need to bootstrap again until you update to a new version of my app, after upgrading you should bootstrap once. After that you just load the app and hit reboot recovery.
3) If you are not familiar with the bootstrap process (like on the dx/d2) please be aware this does not replace your stock recovery like regular CWM. The Custom recovery can only be started by loading the app and clicking bootstrap recovery.
4) Tested more on 2.2 but 2.1 should also be fine if you havent upgraded yet (why?)
Heydabop is working on his CWM flashable boot animation and I am going to start looking into doing a bravo ROM. Thanks for all heydabop's awesome graphics!
Enjoy!
Click to expand...
Click to collapse
Wow, this will change everything for sure! Great job

Any screenshots. I am getting some info together from the x10 guys. When I get all my stuff together I will probably need your assistance band.
Sent from my SEX10 using XDA Premium App

zax10 said:
Any screenshots. I am getting some info together from the x10 guys. When I get all my stuff together I will probably need your assistance band.
Sent from my SEX10 using XDA Premium App
Click to expand...
Click to collapse
just search the market for bravo recovery, it has 2 screen shots.
as for the X10, no problem let me know.

Works fine! Great app! Feels good to be able to nandroid

Thanks!
PS everyone, http://forum.xda-developers.com/showthread.php?p=13183184
that thread is my development thread, will have my rom development, etc. This will just be a release thread (for those who look in this sub forum for this, it makes sense)
but to keep the development comments together, we will post mostly over in that thread not this one.
feel free to post specifics related to this app here if you want, i monitor both threads.

bandroidx said:
Thanks!
PS everyone, http://forum.xda-developers.com/showthread.php?p=13183184
that thread is my development thread, will have my rom development, etc. This will just be a release thread (for those who look in this sub forum for this, it makes sense)
but to keep the development comments together, we will post mostly over in that thread not this one.
feel free to post specifics related to this app here if you want, i monitor both threads.
Click to expand...
Click to collapse
Once again I feel cheep. Is there any other way to get this app? I'm 16. I've got no credit card yet...I should mail you $20 for all the work you've been doing...give me an address and I'd do it. If I had a credit card I'd be giving a lot of money to you and a ton of other devs.

bandroidx said:
I will have a free version out (w/ banner ads) in a couple of days once I finish testing that version.
Click to expand...
Click to collapse
This is something new…

Hope it goes up soon. I'm 16 and I've got no credit card. I'm dieing to test some things.

I bought it, but I don't know how to access CWM :/
I'm lame.

hippyman said:
I bought it, but I don't know how to access CWM :/
I'm lame.
Click to expand...
Click to collapse
download the rom to the sd card.
open my bravo recovery app
click "bootstrap recovery" and wait until it says success.
then click reboot recovery.
then it will reboot into cwm. then choose to install a zip from the sdcard using vol up and down to move up and down, and use the menu button on the front to select the option you want and use back to go back.

I clicked on backup and restore, was that the right thing to do to do a nandroid backup?
It's frozen on a black screen. :/

I hit home button, which led to random screen. Sorry. I'm new to using roms, if you havent noticed..

hippyman said:
I hit home button, which led to random screen. Sorry. I'm new to using roms, if you havent noticed..
Click to expand...
Click to collapse
actually that brings up a good point, the home button toggles the screen on and off. this is useful for rare cases where the recovery starts with the screen off, etc. its also good if you are going to be working in adb in recovery for a while because it will drain battery fast, turning off the display may help a little.

bandroidx said:
I will have a free version out (w/ banner ads) in a couple of days once I finish testing that version.
Click to expand...
Click to collapse
Look's like free version is very unstable for now

Cka3 said:
Look's like free version is very unstable for now
Click to expand...
Click to collapse
I think he got caught up in ROM dev and such, but IIRC, he was close to finally having a market version.

I wonder when the add version will be out. I don't have a card lol.

bandroidx said:
in a couple of days once I finish testing that version.
Click to expand...
Click to collapse
Testing...1...2..3

BravoMotorola said:
I wonder when the add version will be out. I don't have a card lol.
Click to expand...
Click to collapse
cka3 said:
Originally Posted by bandroidx
in a couple of days once I finish testing that version.
Testing...1...2..3
Click to expand...
Click to collapse
check your pm's.

When i pull the battery and then put it back in to boot up, shouldn't the recovery boot first? The droid x recovery bootstrap does that. It would be a good feature to have because if i brick my phone and can't boot into recovery, i can't restore a backup.
Tell me if I'm doing something wrong, thanks

[Q] We Can Now Dual Boot With Boot Manager App!!!

Disclaimer: I didn't create Boot Manager and am not affiliated with the developers in anyway.
I didn't see anyone posting this yet so I figured some of you might be interested.
There's an app on the market now called Boot Manager that's 2.99 and allows you to dual boot up to 5 roms. You still have your main rom which is stored directly in your phone's memory and then up to four more that are stored and run from your sdcard. Because you're running secondary roms from your sdard those may not run as fast as your main phone rom but my preliminary testing has been pretty good.
Boot manager is simple to set up and use and requires no special skills. You don't even need to partition your sdcard.
All you have to do is put whatever roms you wish to run on your sdcard and then install them through Boot Manager. Initially setting up the roms takes maybe 15 minutes but once your done you can boot back and forth very quickly, much faster than doing nandroids.
Enjoy
Update: I'm now running 2 AOSP roms Kushdeck's 1.3b2(main rom) and SalvageMod 1.4 and a Sense rom SynergyRls1 and haven't noticed any major issues. Gps works on each rom as well as 4g. Synergy does have some lag and for this reason took some patience and a little longer to initially set up but it works decently for running off of an sdcard. On a side note I've heard claims that Synergy does have some lag issues running normally.
I plan on ordering a better sdcard with a faster class rating such as class 4 or 6 so hopefully this will decrease lag but overall I'm very impressed with Boot Manager. If nothing else this gives you a chance to test drive roms without having to go through the whole process of replacing your daily driver.
PLEASE READ: I've reached out to one of the developers of this app who's from XDA and asked for his help in answering the problems some of you are having. I wish I could help more especially since this a paid app and you guys deserve to have an app that work. Below are the links to email support through the app website as well as the one of the developers Conap who's from XDA. Maybe if they receive enough emails they will shoot over to this thread to help.
Sorry I can't help more. All I can do is verify that it's working on my Evo but don't have enough advanced skills to do a lot more.
App Support Address: [email protected]
Conap Contact (One of the Devs from XDA): http://forum.xda-developers.com/member.php?u=2468293 (I just pm'd him)

aerajan said:
Disclaimer: I didn't create Boot Manager and am not affiliated with the developers in anyway.
I didn't see anyone posting this yet so I figured some of you might be interested.
There's an app on the market now called Boot Manager that's 2.99 and allows you to dual boot up to 5 roms. You still have your main rom which is stored directly in your phone's memory and then up to four more that are stored and run from your sdcard. Because you're running secondary roms from your sdard those may not run as fast as your main phone rom but my preliminary testing has been pretty good.
Boot manager is simple to set up and use and requires no special skills. You don't even need to partition your sdcard.
All you have to do is put whatever roms you wish to run on your sdcard and then install them through Boot Manager. Initially setting up the roms takes maybe 15 minutes but once your done you can boot back and forth very quickly, much faster than doing nandroids.
Enjoy
Click to expand...
Click to collapse
Fantastic alternative to being able to update prl/data profile on aosp considering that functionality hasn't been adapted to aosp yet.

mattykinsx said:
Fantastic alternative to being able to update prl/data profile on aosp considering that functionality hasn't been adapted to aosp yet.
Click to expand...
Click to collapse
Yea that's a good point. I'm running Kushdeck's 1.3b2 gb aosp as my main rom and didn't even think of that.

https://market.android.com/details?id=com.drx2.bootmanager

Alright, this looks really great. Love the idea. Just wondering for those who have it, since there are different kernels associated with each ROM (going from CM to Synergy) would you have to go back in and wipe battery stats? Also, would vipermod carry from ROM to ROM or would you need to set it up for every ROM?
How much room on the SD card would you need to boot 5 ROMS?
edit: quite a bit of room, have over a gig on sd card and can't load synergy. Have to do some cleaning later. Wish it could import nands, that would rock.
edit 2: cleared room, installed synergy on slot 1, rebooted, hanging on evo 4g screen..... bah

Im trying this now. I have Mikg as my phone rom and installing miui as a test. Will report back when I do some testing on kernals and battery life.

I'm getting error on editing boot.img when trying to install salvage.
Edit: even though this is an app, someone move it to the dev section. Needs more attention.
Sent from my PC36100 using XDA Premium App

i need some more instructions. What are we supposed to wipe in the Rom Installer section? Also, how do you flash Gapps?
hasn't worked yet, boo... 2 battery yanks and nand restores
Edit: Got into salvagemod from synergy through the app. Didn't flash the Gapps, so it wouldn't recognize the app, so when I tried to go back to the "phone ROM", I get a "boot.img failed to flash, not rebooting" error.

yeah crazy... stuck in splash screen sooooo yay no bueno thus far...

locoboi187 said:
I'm getting error on editing boot.img when trying to install salvage.
Edit: even though this is an app, someone move it to the dev section. Needs more attention.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Try doing it again. I've had that happen. Also the developer does state that not all roms will work. I've had 1 so far not work but I know Salvage works because I'm running it as a secondary right now.
alaman68 said:
i need some more instructions. What are we supposed to wipe in the Rom Installer section? Also, how do you flash Gapps?
hasn't worked yet, boo... 2 battery yanks and nand restores
Edit: Got into salvagemod from synergy through the app. Didn't flash the Gapps, so it wouldn't recognize the app, so when I tried to go back to the "phone ROM", I get a "boot.img failed to flash, not rebooting" error.
Click to expand...
Click to collapse
Good question. That confused me first also. You only need to do wipes if you're installing a new rom over an original one in a slot. If the slot is empty you don't need to do any wipes.
I can't address the other problem since I'm not technically proficient enough with the app yet to give you suggestions. Sorry
To flash gapps just install the rom but don't reboot install gapps over the rom in the same slot.
jbrawley1 said:
yeah crazy... stuck in splash screen sooooo yay no bueno thus far...
Click to expand...
Click to collapse
Try doing it again or try another rom. My first tries didn't work either. Also as I mentioned above the developer says this doesn't work with all roms yet.

It takes a while. Since it's booting from your sdcard it's not quite as fast the first time as when you normally flash a rom. Mine stayed on splash screen for a little while to the first time I rebooted. Also try another rom just to see if that works for you.

aerajan said:
Try doing it again. I've had that happen. Also the developer does state that not all roms will work. I've had 1 so far not work but I know Salvage works because I'm running it as a secondary right now.
Good question. That confused me first also. You only need to do wipes if you're installing a new rom over an original one in a slot. If the slot is empty you don't need to do any wipes.
I can't address the other problem since I'm not technically proficient enough with the app yet to give you suggestions. Sorry
To flash gapps just install the rom but don't reboot install gapps over the rom in the same slot.
Try doing it again or try another rom. My first tries didn't work either. Also as I mentioned above the developer says this doesn't work with all roms yet.
Click to expand...
Click to collapse
Ext2 or ext4?
Sent from my PC36100 using XDA Premium App

Omfg will download and test this out ASAP and report back results!!
Sent from my PC36100

locoboi187 said:
Ext2 or ext4?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Ext 2 because it's compatible with more roms.

aerajan said:
Ext 2 because it's compatible with more roms.
Click to expand...
Click to collapse
still no go, error building the boot
Sent from my PC36100 using XDA Premium App

Ok, well I've contacted one of the developers of this app who's also from XDA to see if he will come over here to answer some questions since I'm not able to help as much as I wish and you guys paid for this.
Also if you go back to OP I've posted links to email support or one of the devs who's from XDA. I pm'd him personally asking if he's willing to shoot over here and try to help. If you get the time send him a PM. Maybe if enough people from here contact him he will help.

aerajan said:
Ok, well I've contacted one of the developers of this app who's also from XDA to see if he will come over here to answer some questions since I'm not able to help as much as I wish and you guys paid for this.
Click to expand...
Click to collapse
Thanks
Sent from my PC36100 using XDA Premium App

It does not work on my evo. tried everything but it errors out while finishing building the rom.
Their description does say which phones it supports and EVo is not on there. They probably wont respond to any evo users (at least according to their description, since its a non supported phone).

pottyvick said:
It does not work on my evo. tried everything but it errors out while finishing building the rom.
Their description does say which phones it supports and EVo is not on there. They probably wont respond to any evo users (at least according to their description, since its a non supported phone).
Click to expand...
Click to collapse
I wonder what steps the other guy took to get it working on his evo
Sent from my PC36100 using XDA Premium App

well... ive gotten this to work with Miui as main rom, and Synergy Kingdom port 7/23 but confirmed i dont believe that synergy rls 1+God Mode ive tried tons this wont work...
pretty cool you can switch between aosp and sense pretty easily i like this lots hope in the future it becomes more stable and compatible!

Clockword Mod / Rom Manager Observation

I noticed something weird here, I backup up my system with rom manager, and flashed cyanogen 7. Cyanogen decided to loop its boot animation constantly. So I think ok restore, go into restore choose menu options and press power button. All I got was a logo from rom manager on screen and nothing else. So after panicing a little I realised something, it would seem in the current version of clockwork recovery that the button assignments have changed, the power button no longer selects menu options but the circular button in the centre of the bottom row of buttons does!
Just thought I'd mention this in case anyone else has similar worries as it doesn't seem to be documented anywhere I have looked.

bean12345 said:
So after panicing a little I realised something
Click to expand...
Click to collapse
I panicked too seeing there are still people using that pos software. Ditch rom manager for being responsible for more bricks than most of us these days can count.
Sent from my HTC Desire using Tapatalk 2

Which software are you referring to, rom manager, cyanogen or clockwork. Also what rom would you recommend, I could use one that will handle an ext partition to conpensate for lack of internal memory

bean12345 said:
Which software are you referring to, rom manager, cyanogen or clockwork. Also what rom would you recommend, I could use one that will handle an ext partition to conpensate for lack of internal memory
Click to expand...
Click to collapse
rom manager is known for f*****g up phones and CWM recovery has problems to when it comes to partitioning sdcards, ditch them both and go for 4ext recovery its better in everyway.
Oh and bout asking erklat about whats the best rom to use..... well... good luck with that lol
Sent from my HTC Desire

I think advising him to send me a pm asking that would have probably been a good joke
Sent from my HTC Desire using Tapatalk 2

erklat said:
I think advising him to send me a pm asking that would have probably been a good joke
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
hahaha that would of been funny... dam, why didnt i think of that
Sent from my HTC Desire

Erklat is right, there is no reason to use ROM Manager (i said it before countless times), and do yourself a favor and switch recovery to 4ext.

just looked at 4Ext recovery control, it ain't exactly user friendly is it. Damn thing says it needs updating then refuses to do so, and also insists on busybox which wants to take what little internal memory I have left. Thank god I kept a restore image!

[RECOVERY] Clockwork-Recovery-Standard-v6.0.1.5

This is the newest version of Clockwork Recovery- 6.0.1.5 -non-touch
I claim no credit for any of this. I am only posting this because the latest version available on the official ClockworkMod page is still 6.0.1.0.
This recovery was compiled from source, along with a personal CM10 project I'm working on. Please note that this is included with the CyanogenMod source, so anyone building it will end up with the newest recovery image in their OUT folder.
So, for anyone still using Clockwork Recovery, (I do), here you are!
All credit to Koushik Dutta (Koush)--the creator of what I think is still a great recovery.
More info on his work can be found at http://www.ClockworkMod.com/rommanager

Thanks dude!

Here is the touch version of 6.0.1.5 http://d-h.st/1Kk. I built this last night using the recovery builder found here http://builder.clockworkmod.com/ with the 6.0.1.0 version as a base.
EDIT/ I FORGOT TO MENTION. I AM NOT RESPONSIBLE FOR ANYTHING WORKING OR NOT WORKING WITH THIS RECOVERY. I ASSUME NO RESPONSIBILITY FOR BROKEN DEVICES. USE AT YOUR OWN RISK. THANK YOU

myepicyear said:
This is the newest version of Clockwork Recovery- 6.0.1.5 -non-touch
I claim no credit for any of this. I am only posting this because the latest version available on the official ClockworkMod page is still 6.0.1.0.
This recovery was compiled from source, along with a personal CM10 project I'm working on. Please note that this is included with the CyanogenMod source, so anyone building it will end up with the newest recovery image in their OUT folder.
So, for anyone still using Clockwork Recovery, (I do), here you are!
All credit to Koushik Dutta (Koush)--the creator of what I think is still a great recovery.
More info on his work can be found at http://www.ClockworkMod.com/rommanager
Click to expand...
Click to collapse
Is 6.0.1.5 the version that has the option for tar (non-blob) backup?

Yes it has that option
Sent from my Galaxy Nexus using xda premium

TransWarp said:
Is 6.0.1.5 the version that has the option for tar (non-blob) backup?
Click to expand...
Click to collapse
Yes, this version includes both tar and dup (data blob) backup formats. Tar formatting was re-added in 6.0.1.2.
So you can have either quick, large backups; or slower, slimmer backups with this version.
There's also an interesting adb sideload option as well. Not useful for most casual users, however, the more adventurous users will have a purpose for it from time to time.

10characters

FrostyF7 said:
Thanks dude!
Click to expand...
Click to collapse
You are very welcome sir! Thank you for visiting the very first thread that I've ever posted on XDA. Never even started a question thread before. I'm working pretty freaking hard, on personal projects, as well as school stuff, so you should be seeing a lot more from me in the not-too-distant future. I've been looking forward to contributing more for a long time, and I'm excited to give back something with some more substance. I never stop learning at xda. I owe a lot to this place. :fingers-crossed:

myepicyear said:
You are very welcome sir! Thank you for visiting the very first thread that I've ever posted on XDA. Never even started a question thread before. I'm working pretty freaking hard, on personal projects, as well as school stuff, so you should be seeing a lot more from me in the not-too-distant future. I've been looking forward to contributing more for a long time, and I'm excited to give back something with some more substance. I never stop learning at xda. I owe a lot to this place. :fingers-crossed:
Click to expand...
Click to collapse
Thanks for this CWM. The touch version is nice to have, if your device supports it. I have one question though. Is this version still buggy? Any issues so far? Why hasn't it been posted on Koush's site yet? I would give it a whirl but I'm a bit wary; I wouldn't want to mess with my working 6.0.1.0 touch unless I'm 100% positive this has no issues.
Thanks again.

ezeuba said:
Thanks for this CWM. The touch version is nice to have, if your device supports it. I have one question though. Is this version still buggy? Any issues so far? Why hasn't it been posted on Koush's site yet? I would give it a whirl but I'm a bit wary; I wouldn't want to mess with my working 6.0.1.0 touch unless I'm 100% positive this has no issues.
Thanks again.
Click to expand...
Click to collapse
You're welcome. I wholeheartedly appreciate you visiting my thread.
To answer your questions- no, this version is nothing to be afraid of, and definitely not buggy. In fact, the first couple releases of 6.0.x.x were extremely buggy for many people, and 6.0.1.2 was were things seemed to get evened out. If you are still on 6.0.1.0, I would personally suggest updating to at least 6.0.1.2, as it is at least as stable as 6.0.1.0, while adding in a new feature or two. Most issues at the start of v6 releases were about people's backups being extremely slow, and it turned out to mainly be a conflict between Google Play Music and the way the data blob backup folders were executed/cleaned during backup. Google Play Music has a unique way of storing it's music, and it seemed to be responsible for terrible backup times and rebooting during backup(on some devices--never happened to me).
I was using 6.0.1.2 until a few days ago, and everything was always awesome. This version has backups in data blob format going considerably faster for me. It also has an adb-sideload option incorporated ( newest TWRP includes it too). These are the biggest differences, and there is nothing experimental to be wary of. I definitely understand any hesitation, and I think that it's better to be responsible/careful than to be sorry later. As for the exact reason why Koush hasn't put it on the website yet, I couldn't tell you for sure. He's always done releases this way, and if I had to guess, I'd say he waits for more "milestone" type releases to put a new official version up; which does cut down on the questions, help-requests, and other frantic stuff that new releases bring. 6.0.1.0 isn't the most polished or full-featured, but nothing is really wrong, and he probably just doesn't wanna cause a hype.
Again though, this is 100% safe to update to, and will just polish the experience up a bit. It only gets better, regardless of how significantly.
Let me know if you have any more questions. I'd be happy to help
Nick

myepicyear said:
You're welcome. I wholeheartedly appreciate you visiting my thread.
To answer your questions- no, this version is nothing to be afraid of, and definitely not buggy. In fact, the first couple releases of 6.0.x.x were extremely buggy for many people, and 6.0.1.2 was were things seemed to get evened out. If you are still on 6.0.1.0, I would personally suggest updating to at least 6.0.1.2, as it is at least as stable as 6.0.1.0, while adding in a new feature or two. Most issues at the start of v6 releases were about people's backups being extremely slow, and it turned out to mainly be a conflict between Google Play Music and the way the data blob backup folders were executed/cleaned during backup. Google Play Music has a unique way of storing it's music, and it seemed to be responsible for terrible backup times and rebooting during backup(on some devices--never happened to me).
I was using 6.0.1.2 until a few days ago, and everything was always awesome. This version has backups in data blob format going considerably faster for me. It also has an adb-sideload option incorporated ( newest TWRP includes it too). These are the biggest differences, and there is nothing experimental to be wary of. I definitely understand any hesitation, and I think that it's better to be responsible/careful than to be sorry later. As for the exact reason why Koush hasn't put it on the website yet, I couldn't tell you for sure. He's always done releases this way, and if I had to guess, I'd say he waits for more "milestone" type releases to put a new official version up; which does cut down on the questions, help-requests, and other frantic stuff that new releases bring. 6.0.1.0 isn't the most polished or full-featured, but nothing is really wrong, and he probably just doesn't wanna cause a hype.
Again though, this is 100% safe to update to, and will just polish the experience up a bit. It only gets better, regardless of how significantly.
Let me know if you have any more questions. I'd be happy to help
Nick
Click to expand...
Click to collapse
Top notch response. Thanks...
---------- Post added at 05:30 AM ---------- Previous post was at 05:22 AM ----------
One question. How does the sideload thingy work? What's it all about?

Anytime

myepicyear said:
Anytime
Click to expand...
Click to collapse
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.

crossen0 said:
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.
Click to expand...
Click to collapse
The same way you installed twrp? Boot into fast boot mode and fastboot flash recovery name-of-recovery.img. Replace name of with the actual name of the image. Or you could download and install flash GUI and flash the image through the app.
Sent from my Galaxy Nexus

crossen0 said:
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.
Click to expand...
Click to collapse
Though your question may be a bit noobish, it is an absolutely essential process to learn in the custom Android world, and for fear of looking stupid, many beginners skip asking and learning about this very amazing tool. So before I go any further, I'd like to compliment you on being confident enough to ask for help when you need it. It's an extremely important skill that many of us forget around here, as we all want to be seen as a "know-it-all" sometimes, severely inhibiting our abilities to advance. So yeah, just wanted to mention that, lol.
Now, the tool to do this is fastboot. Are you familiar with the concepts of adb and/or fastboot in any way?
Also, what computer operating system do you use?

myepicyear said:
Though your question may be a bit noobish, it is an absolutely essential process to learn in the custom Android world, and for fear of looking stupid, many beginners skip asking and learning about this very amazing tool. So before I go any further, I'd like to compliment you on being confident enough to ask for help when you need it. It's an extremely important skill that many of us forget around here, as we all want to be seen as a "know-it-all" sometimes, severely inhibiting our abilities to advance. So yeah, just wanted to mention that, lol.
Now, the tool to do this is fastboot. Are you familiar with the concepts of adb and/or fastboot in any way?
Also, what computer operating system do you use?
Click to expand...
Click to collapse
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app

crossen0 said:
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Definitely try to learn fast boot man. The toolkits are cool, but a minor mistake can make using one a nightmare. If you learn fastboot, you will always be able to fix your device. Plus it is the proper and preferred method for flashing a recovery, radio, or bootloader. It is an invaluable tool for for flashing.
Sent from my Galaxy Nexus using Tapatalk 2

crossen0 said:
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm happy to be able to help man.
If you want a quick fix until I have some time to more time to explain fastboot thoroughly, I can do that for the moment.
The toolkit that mkskip has put together for everyone is very handy. It is basically like having all the essential tools, like fastboot, installed for you in their most lean form, without needing the whole android SDK installed. It also gives you a logical interface to interact with all that stuff. The toolkit installs all these tools within a folder on the root of your C drive. If you go to the root of your C drive, you'll see that folder, which is called 'Galaxy Nexus Toolkit'(or something). If go inside that directory, there's a folder called put imgs to flash here. There are several ways to do things in the toolkit folders, but basically, this is one folder you can insert imgs in to fastboot flash them.
Let me know if you're with me so far. I'm going by my memory of all this stuff because I don't use toolkits or Windows anymore. I can guide you through this, and during the process, hopefully broaden your understanding of fastboot at the same time. I'll need you to do some searching of your own during the process, or it wont make any sense at all, but I can definetly guide you through.

There's no need for the toolkit to flash a recovery.
Literally just CD to the folder the .img is in and run "fastboot flash recovery (whatever your recovery is named).img".

063_XOBX said:
There's no need for the toolkit to flash a recovery.
Literally just CD to the folder the .img is in and run "fastboot flash recovery (whatever your recovery is named).img".
Click to expand...
Click to collapse
Dude, I'm not stupid. I'm trying to explain it in a way he is already familiar with.
Jesus.