Database Users

[q] omg need help. Mytouch 4g stuck on mytouch 4g screen.

Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.

thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
calm down take a breather us XDA users got your back, OK take out the battery and put it back in then go to the Hboot ( hold power and volume down) then once you get to the Hboot Settings use volume down to get to RECOVERY (i think its the third one) then once you get into Clockwork Recovery scroll down to (Backup and Restore) click then press (Restore) and then choose your Restore file it usually Year-month-day hope i helped you donate pls if i did
BE SURE TO KEEP THE CHARGER IN!!
p.s. if it turns off while its restoring even with the charger in let it boot into recovery mode and let it charge up a bit
incase you still need help gtalk me [email protected]
and p.s. CWM 3.0.0.5 is for gingerbread only

Certain roms require certain versions of clockworkmod. I don't know if this also applies to restoring from backups, though. Which type of rom did you flash?

If he flashed the add on 3.0.0.5 has ext3/ext4 support. Should be able to flash froyo and TB Rome.
Sent from my HTC Glacier using XDA App

3.0.0.6 supports ext3/ex4 3.0.0.5 only does Gingerbread
Edit: I'm being a dumbass yea what he said was right I'm overly tired and I have to explain to her why I was being a dumbass and trying to flash through fastboot but what I don't understand is why its still stuck at the boot screen

thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
Three options
Option one: (easiest)
Since you flashed 3.0.0.5 you must flash a Gingerbread ROM, (Which you can download from here ). Make sure to flash the G/apps after you flash the ROM.
Option two:
you can flash a 2.x.x.x Recovery image, or flash 3.0.0.6 via script or manually do it via the HBoot.
Option three:
Flash the PD15IMG and start over from ground one.

thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.

thisisjay said:
thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.
Click to expand...
Click to collapse
Ah. i think i see what happened. You rooted your phone. downloaded Clockwork Rom Manager, then flashed a recovery image (which was version 3.x). then tried to flash a 2.2 ROM.
Okay. so what.....
a common mistake but one that can be avoided by doing a little research.
Clockwork's 3.0.0.5 recovery image is only compatible with Gingerbread (2.3) based ROMs.
Clockwork's 2.x recovery image are only compatible with FroYo (2.2) based ROMs.
gorilla is 2.2 So it's not cannot be flashed by the recovery image you are using.
if that is correct then the text in the recovery image should be orange in color. If that is correct.....If i were in your shoes i'd load CM7 w/ the GAPPS > download CWRM from the markert > scroll to the bottom (all clockwork recoveries) and flash the newest 2.x. then boot into recovery / make sure the text is GREEN, not ORANGE, wipe then flash your GorillaSense.

Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App

danger-rat said:
Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
3.0.0.5 is not backwards compatible, which is the official 3.x that you download via the Application. 3.0.0.6 which is "beta" flashed via the HBoot is backwards compatible.
It's seriously jacked if you ask me.
to go from lets say CM6 > CM7 one would do a nandroid backup of CM6, then go to CWRM flash the 3.0.0.5 recovery image > boot into recovery and flash the CM7.
now to get back to a 2.2 ROM you have to scroll to the bottom of CWRM app's and flash a 2.x version of the recovery then do your nandroid restore, flash the 2.2 recovery image.
From what i've heard once 3.0.0.6 is finished you can use that for everything.

What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App

danger-rat said:
What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I haven't had any problems with mine. The only problem that was noted was the 3.0.0.5 prior to the official release wouldn't do Nandroid Backups directly from the application. Some were reporting it work work from the recovery image, but mine never did.
and i have a feeling the reason it's screwing with Partitions is this (CM7/CW3.x) is a Ext4 set up. And CM6/CW2.x is a Ext3 set up.
but since it went official the only problem i've seen is people flashing the the wrong recovery for the wrong ROM. People are flashing 3.x because 3 is higher than 2 so they think it's an upgrade and have no clue on the who/what/when/wheres and whys of what its for.

The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App

danger-rat said:
The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yea between Google's way of doing thing and HTC, but i'm sure the chip-set has something to do with that. and with the sexy nexi only having 512Mb of memory the factor of tricking the phone to use the SD card has something to do with it i'm sure.

i have the 3.x recovery and i can flash iceglacier which is a 2.2 rom with out any issues. what i can't do is restore my backup from my other phone onto this replacement i just got. i made the backup with the 3.x recovery but i just keep getting stuck at the mytouch bootup screen... gonna try flashing the 2.x recovery and see if it lets me do the restore.

hey there everyone. just giving an update.......phone is still messed up. we tried putting gingerbread on and no go....tried flashing to PD15IMG and starting over. no go, it kept saying that "main version older <bad>" the phone wont go past the htc screen. im going on day 3 and no phone. *sigh* open for more advice. should i just buy another phone?

OMG OMG OMG i fixed it.......thank you for this post http://forum.xda-developers.com/showthread.php?t=957457 i re downloaded the PD(insert file name) and it worked. i broke down in tears. thank you guys sooooo much.

I used the .zip file to restore my mytouch, but now it wont go into Hboot.

I got the same problem and is fixed thanx to this link
http://forum.xda-developers.com/showthread.php?t=957457
now I have to root the phone again
Thank you

Thank goodness someone had this problem
I just ran into the same issue. whew good thing xda is here!!! Thanks fellas

[UNOFFICIAL] Team Win Recovery Project for Thunderbolt (10/9 1.1.1-rbox.1)

When the Team Win Recovery Project (twrp) was first working for the Thunderbolt, it didn't fully support the ext3 filesystem, which is what most ROMs used. I initially added that, and over time added extra features. With the 1.1.0 release of TWRP, there is an official build from Team Win that supports both the ext3 and ext4 filesystem. There are some features in my builds that people like that aren't in the official build, so for now I will continue to release my version. As usual, this should work, but I make no guarantees. And of course the source is on github: https://github.com/androidrbox/Team-Win-Recovery-Project
Version 1.1.1-rbox.1: http://www.mediafire.com/file/ye85b3n1f72nen3/twrp111rbox1_PG05IMG.zip (MD5SUM: 31ae566360d4729ff1be2a5a67952777)
The same warning from the TWRP website applies here. Backups from 1.0.3 and below are not compatible with 1.1.1.
Flash this like any other PG05 image in the bootloader.
If you like what I'm doing, feel free to donate. Thanks!
Known Problems:
Under certain circumstances, recovery may fail to start. Running 'recovery' from within adb shell, running adb reboot recovery, or pulling the battery should fix it. This is still being investigated.
10/9: Updated to version 1.1.1-rbox.1
Sync'd to the official TWRP 1.1.1.
The follow is the list of features ontop of the base 1.1.1 that are from all my previous builds.
Added a ClockworkMod Theme
Added a haptic feedback toggle
Show the charging status in the header
Added a capacitive button backlight toggle
Show minutes and seconds during backup/restore
Allow continuous scrolling
Fixed a bug where the capacitive buttons stopped working
Added touchscreen support

Great recovery. SO much faster! I love it

Thanks for posting, will update sticky tonight to include link and info.

Been using this recovery for about a week now and I am loving it!! Great support from the OP as well!! Keep it up!

Whats the advantage of this over the other recovery
Sent from my ADR6400L using XDA Premium App

qubanaso said:
Whats the advantage of this over the other recovery
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
For one it's faster IMO, you can charge while in recovery, search key selects items (instead of abusing you poor power button lol), you can change the color of the text, etc, etc, etc
I've been real pleased with it, and the support thus far has been outstanding!! Not only acknowledging request, but actually implementing them

qubanaso said:
Whats the advantage of this over the other recovery
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I, too have been using this since it was posted on umm...another site. The changes to requests have been swift and accurate.
I think the menus are more intuitive. You have the option to backup/restore: system/data/recovery/boot. It charges while in recovery and shows you the percent. No issues with md5 as each partition has it's own. You can simply rename the folder that they all reside in.

Gonna give this a try.... Sounds promising
Sent from my PUR3 A05P using Tapatalk

YankInDaSouth said:
For one it's faster IMO, you can charge while in recovery, search key selects items (instead of abusing you poor power button lol), you can change the color of the text, etc, etc, etc
I've been real pleased with it, and the support thus far has been outstanding!! Not only acknowledging request, but actually implementing them
Click to expand...
Click to collapse
I probably try a different rom every week our so. The current clockwork does charge your phone while wiping and installing. faster is better but from what I see its just uI differences
The light does not display while charging in clockwork but you will notice the phone power dos not go down much if at all on clockwork.

I decided to upload a sort of preview of something I've been working on for a few weeks. It allows you to use the touchscreen to scroll. It's not perfect but it works. There's also no checkbox to enable/disable it, so I have decided to leave the previous versions link up as well. But as long as you don't touch the screen, using this version is not different than the previous. Using the volume keys for scrolling is unaffected.

I'm liking the touch screen support.

I'm trying to flash Shift 1.4 onto my Phone and it says E: Can't Open /tmp/sideload/package.zip (bad)

EchoX860 said:
I'm trying to flash Shift 1.4 onto my Phone and it says E: Can't Open /tmp/sideload/package.zip (bad)
Click to expand...
Click to collapse
Sounds like a bad download....redownload and check md5 make sure in matches
Sent from my BLACKAO5P using XDA App

What is the proper way to wipe clean and install a rom using this recovery?
Also what is the proper way to backup the current rom before wiping clean and installing a new rom using this recovery?
Thanks in advance!!
Sent from my BLACKSOURC3 using XDA App

Wow. See you have touchscreen enabled in recovery. Thats something I've been wanting for a long time. Have you pushed the commits for it to github? I didn't see it on there nor a tag for '1.0.3-rbox.3

drellisdee said:
Wow. See you have touchscreen enabled in recovery. Thats something I've been wanting for a long time. Have you pushed the commits for it to github? I didn't see it on there nor a tag for '1.0.3-rbox.3
Click to expand...
Click to collapse
I haven't pushed it yet. I'll see if I can get that done this weekend.

If i'm having problems can i return to clockwork recovery by just flashing Clockwork in Rom Manager ?. Does BootManager work with this recovery ?. Thanks .

jawonder said:
If i'm having problems can i return to clockwork recovery by just flashing Clockwork in Rom Manager ?. Does BootManager work with this recovery ?. Thanks .
Click to expand...
Click to collapse
What is not working?
There is always the PG 05 clockwork recovery that can be flashed in bootloader, if you using rom manager doesn't work. I don't know about Bootmanager never used that app

jerrycycle said:
What is not working?
There is always the PG 05 clockwork recovery that can be flashed in bootloader, if you using rom manager doesn't work. I don't know about Bootmanager never used that app
Click to expand...
Click to collapse
I'm not having any problems now just asking ahead of time. I figure it out that i can flash the clockwork recovery zip like a radio in hboot. One other thing i did a backup and rename it "BamfForeverDH" without the Quotes, when i boot into recovery and try to do a backup the backup is not there. Do i have to name the it a special name or i just have to leave it with the name it was backed up with . I love this recovery it's fast, looks great and is very user friendly and BootManager works fine with it.

Ok got it, flash rom, backup restore, everything's working fine.

ClockworkMod Touch Recovery For Shift

Now available for the Evo Shift, go try it out and let us know what ya think about it!

If it aint broke, don't fix it.

VICODAN said:
If it aint broke, don't fix it.
Click to expand...
Click to collapse
I don't care I would still like a ICS touch recovery for the shift that works with rom manager.

I saw this a couple of days ago. I wouldn't mind getting it.
Sent from my PG06100 using Tapatalk

Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G

notsointeresting said:
Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G
Click to expand...
Click to collapse
Yeah according to koush's twitter he just "hacked" touch into cwm recovery so I'm sure he'll work on it more. Twrp is a nice recovery and koush is a really good recovery developer so I'm sure he'll make it better if possible. It's funny after finding out about twrp 2.0 being in development before it was even released I asked koush if it was possible to have touch in cwm. Now we're getting it lol.

notsointeresting said:
Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G
Click to expand...
Click to collapse
Using it on my NS4G and honestly I like it better than TWRP. Everything being larger is reassuring, in TWRP I was always nervous because there was such a small area to select. With the items being so close in TWRP I always wanted my volume keys to work so I could make fine maneuvers and in CWM Touch they do. So you can use it just like regular CWM or with touch. Nice if you mess up your touch screen. And of course it also works with ROM Manager. I downloaded it from the site but I may actually donate the $2 for it too.

Touch recovery has just become available on my SHIFT!!! CHECKIN' IT OUT NOW, VERY COOL!
Let Me Put My Shift In U

letmeputdatipin said:
Touch recovery has just become available on my SHIFT!!! CHECKIN' IT OUT NOW, VERY COOL!
Let Me Put My Shift In U
Click to expand...
Click to collapse
I know I tested it for him last night but it's not stable. I wouldn't purchase it quite yet. Download it from the site and test it out. It will boot into recovery for about 5-10 secs format your cache then reboot to system/rom. Strange bug. It would be nice if someone else could confirm this.

sparksco said:
I know I tested it for him last night but it's not stable. I wouldn't purchase it quite yet. Download it from the site and test it out. It will boot into recovery for about 5-10 secs format your cache then reboot to system/rom. Strange bug. It would be nice if someone else could confirm this.
Click to expand...
Click to collapse
I just flashed it through fastboot and haven't seen that issue. I'm actually in the process of making a backup
Edit: Weird thing.. made a backup and rebooted, everything was gone. It brought my ROM completely back to barebones.. even gapps were gone. Restoring with Touch now to see what happens.
Sent from my Android powered Tenderloin

crump84 said:
I just flashed it through fastboot and haven't seen that issue. I'm actually in the process of making a backup
Edit: Weird thing.. made a backup and rebooted, everything was gone. It brought my ROM completely back to barebones.. even gapps were gone. Restoring with Touch now to see what happens.
Sent from my Android powered Tenderloin
Click to expand...
Click to collapse
Hmm, well I did fastboot erase recovery before flashing, not sure if that has anything to do with it. What recovery did you flash this on top of, just the previous cwm recovery? You can also report bugs to him on irc freenode #koush

sparksco said:
Hmm, well I did fastboot erase recovery before flashing, not sure if that has anything to do with it. What recovery did you flash this on top of, just the previous cwm recovery? You can also report bugs to him on irc freenode #koush
Click to expand...
Click to collapse
Yeah I was coming from the previous version of cwm. I just did a restore and everything is fine. Ill probably mess with it a little later when I have some free time.
Sent from my Android powered Tenderloin

I'm not at my pc to try fastboot again but I did flash the previous cwm recovery and it works fine. Then I flashed the new touch recovery with the flash_image command in terminal emulator and I'm getting the same results as before. This is really annoying me because I would like to get this recovery working and I don't know WTH is going wrong here. Maybe it's the new firmware update? I doubt it. Anyways hope to here from more people that try this out.
Edit: when I get a chance later I'll flash with fastboot without running the fastboot erase recovery command and see how it goes.

I must have got lucky... I used joey krim's GUI Flash App and flashed it over the top of the prior clockwork mod recovery... I'll spend a little time tonight trying to replicate...
Sent from my PG06100 using Tapatalk

Well just used the touch recovery to flash my first ROM and had no issues. Maybe my first experience was fluke.
Anyway, liking this recovery so far.

I'm gonna be using GUI flash like Drob since its just easier for me

question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?

jrny99 said:
question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?
Click to expand...
Click to collapse
I'm nit sure about that (although I feel it should be .zip but probably wrong), but you could use Flash Image GUI from the Market or use fastboot from your PC. You'd just stick the .img file in the same folder as fastboot, cd there and type "fastboot flash recovery whateveryounamedit.img". Personally I like Flash Image, works well for flashing kernels too.

jrny99 said:
question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?
Click to expand...
Click to collapse
Yeah, just to reiterate what J-Ice already said... don't rename the img, just flash through fastboot.

I can confirm this is not working for at least one other person on the latest firmware update via twitter messaging...I've tried GUI, fastboot, flash_image, all same results.

[Recovery] Clockworkmod 5.8.4.3

Due to koush for releasing a wonderful tool to the android community i threw in the current cwm into the builder and it came out with a new and shiny version!
Known Issues
Don't boot into recovery using rom manager, as is it will boot u into older version.. but if u delete the recovery-update.zip in the clockworkmod folder it will boot into the new recovery but with an error
The background images for the recovery are huge x_X
Recovery: recovery-clockwork-5.8.4.3-desirec.img
md5sum: db3e9d93c7f1f52a427b7f6ca427cabf

mine, just in case!

Do you have an Eris that you're testing this on? I was under the impression that CWM and ROM Manager didn't play nicely with the Eris. What's your experience been?

KarateExplosion6 said:
Do you have an Eris that you're testing this on? I was under the impression that CWM and ROM Manager didn't play nicely with the Eris. What's your experience been?
Click to expand...
Click to collapse
ya, I have an Eris.. I think that was long time ago which has been solved before even the latest official cwm..
I left the Eris long ago but keep it around as a pmp, since my trackball doesnt scroll and the mic is busted.. when I started using it again I couldn't flash anything new because I was on amonRA.. so I took the plunge and used cwm and I haven't ran into a single issue.. there, that's my Eris history xP right now I have it on cm7.2 stable
Sent from my Galaxy Nexus using Tapatalk 2

swordrune10 said:
ya, I have an Eris.. I think that was long time ago which has been solved before even the latest official cwm..
I left the Eris long ago but keep it around as a pmp, since my trackball doesnt scroll and the mic is busted.. when I started using it again I couldn't flash anything new because I was on amonRA.. so I took the plunge and used cwm and I haven't ran into a single issue.. there, that's my Eris history xP right now I have it on cm7.2 stable
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Fantastic! I was actually looking for someone running CM7.2 Stable. My brother is using my Eris and I've had him on xtrSense forever. I'd like to flash him up to Gingerbread. What do you think of the stable release?

KarateExplosion6 said:
Fantastic! I was actually looking for someone running CM7.2 Stable. My brother is using my Eris and I've had him on xtrSense forever. I'd like to flash him up to Gingerbread. What do you think of the stable release?
Click to expand...
Click to collapse
the only thing I have to say since I barely use the thing is that I have installed is a 32gb sdcard and before on 7.1 it sometimes didn't finish the boot cycle because every so often it gets stuck at checking sdcard.. now its more likely to boot completely.. don't get me wrong, it still sometimes gets stuck on boot... again fault is because of the 32gb sdcard.. and me having to have lots of music...
Sent from my Galaxy Nexus using Tapatalk 2

swordrune10 said:
the only thing I have to say since I barely use the thing is that I have installed is a 32gb sdcard and before on 7.1 it sometimes didn't finish the boot cycle because every so often it gets stuck at checking sdcard.. now its more likely to boot completely.. don't get me wrong, it still sometimes gets stuck on boot... again fault is because of the 32gb sdcard.. and me having to have lots of music...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Shouldn't matter to my brother. He doesn't even use an SD card!!

KarateExplosion6 said:
Shouldn't matter to my brother. He doesn't even use an SD card!!
Click to expand...
Click to collapse
x_X before I switched I used cm5 (unofficial) on Eris, it was good.. gingerbread is ok on it.. but ics on a better phone is a lot better
Sent from my Galaxy Nexus using Tapatalk 2

swordrune10 said:
Due to koush for releasing a wonderful tool to the android community i threw in the current cwm into the builder and it came out with a new and shiny version!
Known Issues
Don't boot into recovery using rom manager, as is it will boot u into older version.. but if u delete the recovery-update.zip in the clockworkmod folder it will boot into the new recovery but with an error
The background images for the recovery are huge x_X
Recovery: recovery-clockwork-5.8.4.3-desirec.img
md5sum: db3e9d93c7f1f52a427b7f6ca427cabf
Click to expand...
Click to collapse
How does the tool work? I want to get this to work on my htc hero gsm

jordfaz said:
How does the tool work? I want to get this to work on my htc hero gsm
Click to expand...
Click to collapse
what u do is u go to the site and insert a recovery ( even stock ) for ur device and it builds it for ur based on cwm.. fortunately ( or unforunately, if u wanted to do it urself ) there was already one done for the hero =] .... yes that means i looked through a good amount of them just to see what people were building x.x

swordrune10 said:
ya, I have an Eris.. I think that was long time ago which has been solved before even the latest official cwm..
Click to expand...
Click to collapse
There are lots of posts on this site (and on others), many relatively recent, from people with Erises that cannot boot that almost all started with a person who was running with ClockworkMod as their recovery image; none that I know of from people who started with Amon_RA. Scary Alien made a trackball-optional version of Amon_RA (with Amon_RA's permission) for the Eris which works with the hardware keys as well as the trackball. See http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
So, be careful with Clockwork Recovery.

doogald said:
There are lots of posts on this site (and on others), many relatively recent, from people with Erises that cannot boot that almost all started with a person who was running with ClockworkMod as their recovery image; none that I know of from people who started with Amon_RA. Scary Alien made a trackball-optional version of Amon_RA (with Amon_RA's permission) for the Eris which works with the hardware keys as well as the trackball. See http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
So, be careful with Clockwork Recovery.
Click to expand...
Click to collapse
I seriously think the issues have been resolved.. the way koush works on them brings what he did before to the next recovery he makes.. if that issue was still around there would be a lot of phones not booting..
Sent from my Galaxy Nexus using Tapatalk 2

swordrune10 said:
I seriously think the issues have been resolved.. the way koush works on them brings what he did before to the next recovery he makes.. if that issue was still around there would be a lot of phones not booting..
Click to expand...
Click to collapse
There was just an issue a week or two ago. http://forum.xda-developers.com/showthread.php?t=1702130
That's pretty typical - for some reason, these phones end up with bad blocks in some partitions (usually system.img, cache.img) that are difficult to resolve.
Note that you can install ROM Manager on a CM ROM and hit "install recovery". This installs an update.zip file in the root of the SD card. From Amon_RA you can flash the update.zip and it will start Clockwork. That method seems to be safe and is the way that I flash, Nandroid, etc., on the Eris.
Again, this seems to be an Eris issue with Clockwork as the default recovery. If it works for you, that's fine, but I would try to get on the 1.49.2000 S-OFF bootloader so that you can use fastboot as a recovery tool if you are not on that bootloader already.

doogald said:
There was just an issue a week or two ago. http://forum.xda-developers.com/showthread.php?t=1702130
That's pretty typical - for some reason, these phones end up with bad blocks in some partitions (usually system.img, cache.img) that are difficult to resolve.
Note that you can install ROM Manager on a CM ROM and hit "install recovery". This installs an update.zip file in the root of the SD card. From Amon_RA you can flash the update.zip and it will start Clockwork. That method seems to be safe and is the way that I flash, Nandroid, etc., on the Eris.
Again, this seems to be an Eris issue with Clockwork as the default recovery. If it works for you, that's fine, but I would try to get on the 1.49.2000 S-OFF bootloader so that you can use fastboot as a recovery tool if you are not on that bootloader already.
Click to expand...
Click to collapse
Yeah, that's how I always thought was the safest way to do it--running CWM from ROM Manager.

Yep, been using ROM Manager, and CWM through update.zip via Amon RA for a year and a half now without any issues. I don't think I'd ever be tempted to flash CWM over Amon RA; I'd rather have the best of both worlds without wondering if I'm taking any additional risk.

well.. I understand everyone's opinion and its cool.. I tried working on making a recovery.zip that just restarted the recovery not overwrite it, but it just wouldn't do it =/
Sent from my Galaxy Nexus using Tapatalk 2

[VIDEO] Idiot's Guide - How to Install CM10 on the HP Touchpad

This is my FINAL VERSION of my Idiots Guide for the HP Touchpad. Now that a stable enough version of CM10 is available, I finally created a guide for you.
Here are links to the files you will need:
CM10 03/04/2012 Build
GAPPS 10/11/2012
ACMEInstaller3
Moboot 3.8
Anything else that you might need, you'll find on http://www.reverendkyle.com

Thanks for the video. It came just in time as I just purchased a used TP that had an older version of android ICS already on it and I wanted to upgrade but seeing as how this is the first device I have sort of inherited already rooted, it is hard to just jump in and know everything that I would have learned from the beginning like i did with my previous phones.
Anyways, I did everything you said except I used the newest AOKP rom. But my tp is still booting to the older version of android that I had on it. Any ideas? Feel free to pm me if you prefer that.

aujbman said:
Thanks for the video. It came just in time as I just purchased a used TP that had an older version of android ICS already on it and I wanted to upgrade but seeing as how this is the first device I have sort of inherited already rooted, it is hard to just jump in and know everything that I would have learned from the beginning like i did with my previous phones.
Anyways, I did everything you said except I used the newest AOKP rom. But my tp is still booting to the older version of android that I had on it. Any ideas? Feel free to pm me if you prefer that.
Click to expand...
Click to collapse
If the AOKP ROM is using a unique uImage file, then you may see two different entries on your moboot screen for two different Android builds.
What does your moboot menu have in it?

Maybe your install failed. Try downloading and flashing it again. If you're trying AOKP JB, you should wipe both /data and dalvik cache to avoid a boot loop!
If using AcmeInstaller3 remember to rename the ROM with ”update-” at the beginning so that it looks like update-AOKPJB_UnOfficial.zip
Sent from my SAMSUNG-SGH-T989 using xda premium

-SGA- said:
Maybe your install failed. Try downloading and flashing it again. If you're trying AOKP JB, you should wipe both /data and dalvik cache to avoid a boot loop!
If using AcmeInstaller3 remember to rename the ROM with ”update-” at the beginning so that it looks like update-AOKPJB_UnOfficial.zip
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I believe it was the "update-" thing that was keeping it from updating. I followed another video tutorial which provided files that had the "update" in front of them and it worked.
I haven't tried yet but now that it worked will the regular method of wiping and flashing through recovery work? (Like, if I want to try out different JB Roms) Are there any files that need to be in a particular place for the recovery method to work? I tried that method first and it would never take, would always revert back to the original version. Don't know if, because I just jumped in and haven't been here from the beginning, I am just missing a necessary step that is hardly even talked about anymore.

Love your work Rev! Thank you again for everything that you do!
Update went like clockwork, unfortunately I can't seem to get the camera to work (not a terrible loss, but I was sorta excited to see it actually working with this release).

Jubmasterflex said:
Love your work Rev! Thank you again for everything that you do!
Update went like clockwork, unfortunately I can't seem to get the camera to work (not a terrible loss, but I was sorta excited to see it actually working with this release).
Click to expand...
Click to collapse
I can attest to the improved battery life on this cm10 build. Amazingly, it holds battery life when it's sleeping now.

Thank you so much for taking the time in making the video for us. Your instructions are easy to follow, hard for anyone to mess up.
(The hosting site for the files is not working, not sure if you were aware)

Hi, I have CM9 running on my TP. With the latest release, the camera works great. But before updating it to CM10, I'd like to know about the issues currently in this build.
Thanks.

Where does one go when the goo.im site appears down, to get the needed files? Mirror somewhere?

ljderm said:
Where does one go when the goo.im site appears down, to get the needed files? Mirror somewhere?
Click to expand...
Click to collapse
Don't go for external mirrors unless some recognized developer suggests them. Best will be to wait for goo.im to come up again, being a prime site, it won't be down for long.

The goo servers do appear to go down on occasion. They always come back up a bit later.

Problem with installing GAPPS using ACMEInstaller3
Excellent tutorial for an idiot like me. Thanks for again for the guide! Question:
I followed the instructions step by step and was able to get CM10 installed successfully. However, I wasn't able to get GAPPS installed using this method. From researching I understand sometimes there is a problem installing GAPPS through ACMEInstaller3 and one can simply get GAPPS installed through CWM Recovery. However, I would like to use/have TWRP instead so is there a way to get GAPPS installed properly through ACMEInstaller3 and then I can install TWRP through GooManager?
Alternatively, is there a way to install GAPPS without using CWM Recovery?
Or, I guess I can install CWM Recovery first, then install TWRP Recovery, then remove CWM Recovery while keeping TWRP and not go back to the stock Recovery? I tried to search the forums and wasn't able to find instructions on removing CWM Recovery WHILE still keeping CM10 and not go back to the Stock recovery.
Any help would be much appreciated. Thanks in advance for your help.

@reverendkjr - appreciate your videos. they're awesome. definitely helped me (and several other friends) many times and saved a ton of time. super easy to follow.

Yes you can install TWRP normally, flash gapps in CWM then install goomanager app, open and click the 3 dot menu and install custom recovery script then it will install it
Now using a root file manager go to the directory called boot and delete uimage.cwm.img (this is from memory but still should be correct
Sent from my cm_tenderloin using XDA Premium HD app

waynekirby said:
Yes you can install TWRP normally, flash gapps in CWM then install goomanager app, open and click the 3 dot menu and install custom recovery script then it will install it
Now using a root file manager go to the directory called boot and delete uimage.cwm.img (this is from memory but still should be correct
Sent from my cm_tenderloin using XDA Premium HD app
Click to expand...
Click to collapse
Dumb question. I had dual boot installed with moboot and one day my dumbarse clicked erase SD card.well it did...EVERYTHING accept twrp. I successfully reinstalled webos and installed preware. Its actually pretty cool.its like a fledgling play store for webos. Now....where should i go from here.i no longer think twrp is on it. All i have is webos with preware.sorry if this is newbie
Sent from my Galaxy Nexus using xda premium

Crwolv said:
Dumb question. I had dual boot installed with moboot and one day my dumbarse clicked erase SD card.well it did...EVERYTHING accept twrp. I successfully reinstalled webos and installed preware. Its actually pretty cool.its like a fledgling play store for webos. Now....where should i go from here.i no longer think twrp is on it. All i have is webos with preware.sorry if this is newbie
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
My goodness you have forgotten everything, you will need to install acmeuninstaller 3, moboot, CMW and the rom you want along with the relevant gapps. Sounds complicated this thread will make it easy
http://forum.xda-developers.com/showthread.php?t=2147284 and has all the necessary links. Have fun.
Sent from my Transformer Prime TF201 using Tapatalk 2

Heck ya i did lol. That refreshed my memory instead of a long video. Thank yo very much

Awesome!
Sent from my cm_tenderloin using xda app-developers app

Great vid!! Finally got CM10 on my Touchpad.