Database Users

Bought Evo on eBay... has s-off but recovery goes to red triangle

Ok bought an evo on eBay, after getting rid of my evo for a blackberry and realizing I made a huge mistake. It's used but like new.
I go to the boot screen and it says s-off. Then I select recovery but it goes to an evo with a red triangle.
What can I do?
Thanks
Sent from my PC36100 using XDA App

If you can acess the bootloader, I would recommend searching in the rooting wiki and look for a PCIMG file place that in the root of the sd card(hopefully your comp has a media reader) and insert the sd card with that file and the bootloader should detect when you select recovery.
What that file does is resets everything on the phone to stock. if you could find a RUU that might work but if your comp cant see the phone its useless i hope this helps
oh hey just stole this from a post from mattykins(thanks for the link) http://forum.xda-developers.com/showthread.php?t=884060

josh995 said:
Ok bought an evo on eBay, after getting rid of my evo for a blackberry and realizing I made a huge mistake. It's used but like new.
I go to the boot screen and it says s-off. Then I select recovery but it goes to an evo with a red triangle.
What can I do?
Thanks
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
If you're s off, your rooted. The triangle means you have no recovery. All you need to do is flash a PC36IMG of recovery, using the bootloader. Once you do that, you'll have recovery, and can flash a rom of your choice. That's it. No need to re root or ruu or anything like that. Just recovery, that's it.
Sent from my PC36100 using XDA App

k2buckley said:
If you're s off, your rooted. The triangle means you have no recovery. All you need to do is flash a PC36IMG of recovery, using the bootloader. Once you do that, you'll have recovery, and can flash a rom of your choice. That's it. No need to re root or ruu or anything like that. Just recovery, that's it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
or you could install clockwork mod and make it even easier on yourself by installing recovery through there

k2buckley said:
If you're s off, your rooted. The triangle means you have no recovery. All you need to do is flash a PC36IMG of recovery, using the bootloader. Once you do that, you'll have recovery, and can flash a rom of your choice. That's it. No need to re root or ruu or anything like that. Just recovery, that's it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Could you do a huuuuge favor for a newbie and link me to the file I need to flash?
Sent from my PC36100 using XDA App

iitreatedii said:
or you could install clockwork mod and make it even easier on yourself by installing recovery through there
Click to expand...
Click to collapse
This would probably be the easiest thing. DL clockwork from the market and install the recovery I prefer amon_ra it will be at the bottom under alternate recoveries. Also do a nand backup as soon as you have a recovery.

I agree with above, just get rom manager from the market and flash a recovery...simple
We're comin from a pure power source.

josh995 said:
Could you do a huuuuge favor for a newbie and link me to the file I need to flash?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
SUre, give me one sec to upload a file for you. And as the other guys suggested, flashing a recovery using ROM manager would be your easiest bet. HOWEVER, if you dont have the SUPER USER app, (which i bet you do not), rom manager wont work. t herefore you cant flash anything with it.
So give me one sec, and i'll upload what you need to flash, with instructions for ya
EDIT: I attatched a recovery for you. It's Amon Ra V2.3. Download the PC36IMG, and leave it named exactly as it is. Place the file on the main directory (root) of your sd card. Power your phone off completely. Then boot to the bootloader by holding the power and volume down buttons simultaneously. When it gets to the bootloader, after a sec it will scan for files, and find the PC36IMG. It will then ask you if you want to update, so select yes (volume UP). Once it's done flashing, it'll ask you to reboot. Select no. Then choose the 'recovery' option from the bootloader menu. You should now successfully boot into Amon Ra V2.3 recovery. From that point, you can create a backup of your current setup. Then you can perform a full wipe, and then flash the rom of your choice.

And what ever you do DON'T restore a nandroid from your old phone. You will wipe out your 4g if the wimax partition is included in the nandroid.
Sent from my PC36100 using XDA App

k2buckley said:
SUre, give me one sec to ........
Click to expand...
Click to collapse
Thanks man, a lot!

josh995 said:
Thanks man, a lot!
Click to expand...
Click to collapse
You're welcome. Never a problem at all. Let us know if you need any more assistance getting things up and running.

Ok that worked. I now have Amon ra recovery
But, lol, one more question. Amon ra has changed since I've had an evo.. now when I select backup, it has a list of things I want to back up with "[x]" next to them. Which items should I select? It didn't have that feature in the past so I'm a little lost.
Sent from my PC36100 using XDA App

josh995 said:
Ok that worked. I now have Amon ra recovery
But, lol, one more question. Amon ra has changed since I've had an evo.. now when I select backup, it has a list of things I want to back up with "[x]" next to them. Which items should I select? It didn't have that feature in the past so I'm a little lost.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Right, that feature was added after version 1.8.0 (which I still use). I believe you want to check all of the boxes, for your first backup. (I'm not sure if you need to have everything checked after that, but I'm sure it couldn't hurt). I've seen people say that you only need to back up your wimax one time, then keep the file in a safe place (it's your RSA keys), however I just can't see what the problem is with backing it up each time. I kind of like the simplicity of 1.8.0, just hit backup and let it do it's thing. Whatever the heck 1.8.0 automatically backs up on its own, works perfectly fine for me, lol.
So I would just check everything off, and then let it perform the backup.
EDIT: and sorry I don't have more info on that for ya. I'm sure someone else who regulrarly uses ar 2.3 will chime in, and give you a more solid answer. I just simply don't use that recovery, as I never saw a need to 'upgrade' from 1.8.0, because it has always worked flawlessly for me. If it ain't broke, don't fix it. I'd say you could use 1.8.0 if you wanted to, but I believe it won't work on the 004 hardware phones with the 0040000 size erase block.

Ok cool.
Thanks again
And yes i remember the simple way, things are supposed to get easier as time goes on, not more complicated, haha!
Sent from my PC36100 using XDA App

Rooting a 4g

OK so I'm commingle from the epic and I want to root for titanium but I've seen there is different varrent and different ways to root what meatod will work and I have looked and searched before I get the plaza use search I just don't want to brick using wrong root meathod thank you in advance for who ever is willing to help
Sent from my Nexus S 4G using XDA App

+1
Sent from my Nexus S 4G using XDA App

Do you have SDK and working fastboot? That is step one.

Yep
Sent from my Nexus S 4G using XDA App

*note* i did not develop this method entirely i scrapped it together from multiple posts found here on xda. I give credit to those who did the work first. it worked fine for me hopefully it works for you too.
download sdk tools and install
download fastboot drivers and install
both found here
after that, download clockwork recovery
also download superuser files you want eclair/froyo su it works for gingerbread too.
open command prompt and enter the following
Code:
fastboot devices
if it doesn't return your phone in the following line double check that your fastboot drivers are properly installed.
if it does enter the following
Code:
fastboot oem unlock
follow the onscreen prompt on your phone. volume up to "yes" and hit power to confirm
Your phone is now unlocked. next step installing a recovery.
navigate to the folder where the clockwork recovery image is located.
Code:
cd C:\users\#username#\downloads
or wherever the file is on your pc.
then enter the following
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
you now have a proper recovery installed on your phone you may now vol dn to recovery and hit power to confirm
VERY IMPORTANT
in recovery vol dn to "backup and restore" power to confirm
select Backup and hit power again.
you just created a nandroid backup of your phone if you ever mess it up you can restore it back to when it was stock and problem free
In recovery vol dn to "mounts and storage" power to confirm
then choose "Mount USB storage"
copy the SU zip to the root of your phone's storage
then "Unmount"
then "+++++Go Back+++++"
then "install zip from sdcard"
then "choose zip from sdcard"
Choose su-2.3.6.1-ef-signed.zip
then select "Yes - Install su-2.3.6.1-ef-signed.zip"
Reboot your phone and you should now have a stock rooted phone.

Ty Joe I will do this as soon as I get home
Sent from my Nexus S 4G using XDA App

tildog said:
No I have not but did not want to start on anything till I confirmed that the method will not brick I will dl. Sdk. And drivers tonight at work ATM
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
It's really *really* hard (if not damn near impossible) to actually brick a nexus-s. Just so ya know ;D

netarchy said:
It's really *really* hard (if not damn near impossible) to actually brick a nexus-s. Just so ya know ;D
Click to expand...
Click to collapse
That is good to know I had a few scares on my epic I know how to do stuff but on the epic was always a onclick meathod so this looks a little overwhelming in comparison but easyenof otherwise
Sent from my Nexus S 4G using XDA App

tildog said:
That is good to know I had a few scares on my epic I know how to do stuff but on the epic was always a onclick meathod so this looks a little overwhelming in comparison but easyenof otherwise
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Just remember to make a nandroid backup in clockwork after you're done rooting, so you always have a working setup to fall back on if something should go wrong in the future

tildog said:
That is good to know I had a few scares on my epic I know how to do stuff but on the epic was always a onclick meathod so this looks a little overwhelming in comparison but easyenof otherwise
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
i just came from the evo and rooted that phone way before any one click roots where out. Trust me the nexus s is 100 times easier to root than any other phone it's actually pretty quick and easy, i just went into great detail so anyone could be able to follow it hopefully. I think i have seen some 1 click roots for the ns but i never looked into them once i saw how relatively pain free it is to do this way.
i remember having to copy and paste adb commands and spamming them while my phone rebooted. and hopefully... hopefully it would unlock the evo.

just out of curiousity as i wont know until tomorrow, but does gingerbreak work? if so just using the sdk and using adb to push it seems like it would be faster..

shabbypenguin said:
just out of curiousity as i wont know until tomorrow, but does gingerbreak work? if so just using the sdk and using adb to push it seems like it would be faster..
Click to expand...
Click to collapse
Yes there has been success using that. You could i suppose gain root with gingerbreak and then use that to flash clockwork recovery. You would be rooted and able to flash Roms through clockwork. Bootloader would remain locked.

Thanks all. I'll try this later tonight and report back. I've seen a few root methods around here but wanted to make sure it was no different for the ns4g before I actually got into it.
So to confirm one more time Joe's method he posted here should work for the ns4g as well, right?
Sent from my Nexus S 4G using XDA App

matt2053 said:
Yes there has been success using that. You could i suppose gain root with gingerbreak and then use that to flash clockwork recovery. You would be rooted and able to flash Roms through clockwork. Bootloader would remain locked.
Click to expand...
Click to collapse
Yea but its a quick and easy way to root. Until there is more support for the ns4g no real reason to unlock

shabbypenguin said:
Yea but its a quick and easy way to root. Until there is more support for the ns4g no real reason to unlock
Click to expand...
Click to collapse
Yeah for sure, I'm not saying its good or bad. Just pointing out the difference in that method. Some people prefer to keep the bootloader locked anyway. Unlocking it is always one command line away.
Sent from my Nexus S using XDA App

shabbypenguin said:
Yea but its a quick and easy way to root. Until there is more support for the ns4g no real reason to unlock
Click to expand...
Click to collapse
Not totally sure regarding roms, but my latest kernel builds *should* be compatible ;D
(Disclaimer: always nandroid before flashing customs!!)

netarchy said:
Not totally sure regarding roms, but my latest kernel builds *should* be compatible ;D
(Disclaimer: always nandroid before flashing customs!!)
Click to expand...
Click to collapse
cool thanks for the support man

Running into an issue on ns4g. I can unlock and install Clockwork 3.0.0.5 but when I try to Nand backup it says it can't find cache. I've tried to manually mount it but won't do it there either. Any suggestions?

oubravs2b said:
Running into an issue on ns4g. I can unlock and install Clockwork 3.0.0.5 but when I try to Nand backup it says it can't find cache. I've tried to manually mount it but won't do it there either. Any suggestions?
Click to expand...
Click to collapse
Install clockwork 3.0.2.4
Make sure you've renamed the /system/etc/install-recovery.sh script (if you haven't already) as well so clockwork isn't overwritten by the stock recovery.

netarchy said:
Install clockwork 3.0.2.4
Make sure you've renamed the /system/etc/install-recovery.sh script (if you haven't already) as well so clockwork isn't overwritten by the stock recovery.
Click to expand...
Click to collapse
Good to go I think - thanks netarchy!
So for you all that are trying to follow joe's steps, they are correct except the download linked in his post will give you the 3.0.0.4 version of Clockwork and you need the one referenced by netarchy (3.0.2.4). All worked as planned after that.
Rooted and ready to flash netarchy's kernel on ns4g!

Flashing CleanCB

For the life of me, I cannot get either version to flash. I've read, and reread this thread (I'm a reader) as well as everything in general - the wiki (I'm a reader). Just need 2 say that before JC is brought up in any response I get. At any rate, I boot into cw, wipe and flash. Each time and I've tried 4 times now, I get stuck at the Samsung screen. I'm on EL30, also have the modem and I'm rooted...I've done this many times bu cannot get this ROM to work for me....and I oh so wanna buy the dev a beer.
Any help would be greatly appreciated.
Sent from my SPH-D700 using xda premium

Have you tried redownloading? Maybe you got a bad download.
Sent from my SPH-D700 using XDA App

What CWM are you running? And is the CleanGb build MTD or BML
Sent from my SPH-D700 using XDA Premium App

I am on ClockworkMod 5.0.2.7
Tried downloading 4 different times
First tried flashing BML - twice
stuck on Samsung screen
nandroided back
Tried flashing MTD
stuck on Samsung screen
Tried one last time to flash BML - had to nandroid back again.
I've read a lot, a whole lot and I still cannot figure it out.

OK, try reflashing CWM 5.0.2.7 first. then do a Factory Data reset in CWM then flash the ROM right after. Don't use ROM Manager. See how that works. If you tried the MTD version then use that one. You may want to Odin back to BML with repartition checked if you want to try that one.

kennyglass123 said:
OK, try reflashing CWM 5.0.2.7 first. then do a Factory Data reset in CWM then flash the ROM right after. Don't use ROM Manager. See how that works. If you tried the MTD version then use that one. You may want to Odin back to BML with repartition checked if you want to try that one.
Click to expand...
Click to collapse
Ok....tried that with high hopes and got:
checking state of bml/mtd...
assert failed: run_program("/tmp/updater.sh")==0
E:Error in /sdcard/CleanGB-MTD-1.zip
(Status 7)
Installation aborted
going to nandroid back again...if that works

Did try redownloading the rom &reflashing it?
Your problem seems to be a bad download. I had a problem with MTD because of ACS recovery, then i had a bad download
Sent from my SPH-D700 using XDA Premium App

Looks like you are getting bad downloads or your sd card is corrupted. You may need to backup and reformat your sd card.
Sent from my SPH-D700 using xda premium

I'm beginning to think this download (second MTD download) is bad. I totally removed my card - put all the info on my computer, inserted a new card, flashed and got the same error. Gonna delete the download and try again.

Capricorn27 said:
I'm beginning to think this download (second MTD download) is bad. I totally removed my card - put all the info on my computer, inserted a new card, flashed and got the same error. Gonna delete the download and try again.
Click to expand...
Click to collapse
That worked! Thanks guys! You were very helpful. Now who do I owe a beer?

Capricorn27 said:
That worked! Thanks guys! You were very helpful. Now who do I owe a beer?
Click to expand...
Click to collapse
Haha...another epic Epic is thanks enough. Glad you are up and running.
Sent from my SPH-D700 using xda premium

Capricorn27 said:
That worked! Thanks guys! You were very helpful. Now who do I owe a beer?
Click to expand...
Click to collapse
Glad to hear you got it to work. Enjoy it!
Sent from my SPH-D700 using XDA App

Wow...talking about "reading" everything....named the ROM incorrectly in my subject line. (I JUST edited it) I'm going to blame that on the fact that I stare at a computer screen all day.
Again - many thanks and good night!
Sent from my SPH-D700 using xda premium

WinRAR is your friend. To test the integrity of a ROM zip file, open with WinRAR, click on Commands > Test archived files and it should come back with "no errors found" if it's a good download.

mi7chy said:
WinRAR is your friend. To test the integrity of a ROM zip file, open with WinRAR, click on Commands > Test archived files and it should come back with "no errors found" if it's a good download.
Click to expand...
Click to collapse
very helpful information. I have read a lot about people having issues with bad downloads. Nice to know you can check them like that. I have noticed in flashing various roms that I have come across some random glitches. Perhaps this could be the culprit. Thanks again.

Users should ALWAYS verify the integrity of ROM downloads using the md5 sums posted by the developer. If you download directly to your phone you can use the "properties" view in Root Explorer. If you've got it on your PC you can use the utilities found here - http://www.winmd5.com/

[RECOVERY] Clockworkmod Recovery TOUCH 5.5.0.4 | everything works except adb (5/15)

I am currently working on porting gweedo's touch recovery to the touchpad. So far I have a working clockworkmod 5.5.0.4 with the cool battery percentage mod but the touch part is not ready yet.
I just wanted to release this as a fully functional recovery (except adb).
1) boot into clockworkmod
2) mounts and storage >> mount /boot
3) adb push uImage.CWMRT5504 /boot/uImage.CWMRT5504
4) reboot and see it in the moboot menu
The touchscreen driver doesnt work but this is a completely working clockworkmod recovery (backups, restore, installing zips, etc.) (except adb)
Thanks
uImage.CWMRT5504 (install file)
LINK: HERE
KNOWN ISSUES:​
- touchscreen doesnt work (yet)
- adb doesnt work in recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Changelog:
- fixed the mount points to be a fully functional recovery. (thanks gdanko)

Pretty cool man!
Sent from my Touchpad using xda premium

good job man
Sent from my SGH-T989 using xda premium

I played around and it works pretty well! No bugs that I could find.
The only feedback I would give is that when you flash ROMs it sucks that the soft touch keys on the screen get in way of a lot of the wording. The horizontal blue line also would strike through words and it looks cruddy.
Any way to change where the message output is placed?

Can't wait to try this out. Keep the work going.

Can someone post mirrors for the downloads. They are both down.

LinuxNewb said:
I played around and it works pretty well! No bugs that I could find.
The only feedback I would give is that when you flash ROMs it sucks that the soft touch keys on the screen get in way of a lot of the wording. The horizontal blue line also would strike through words and it looks cruddy.
Any way to change where the message output is placed?
Click to expand...
Click to collapse
this should be fixed in this beta 14. and also the links are updated to an unlimited bandwidth server.

I hate to be "that guy," but I looked into this before and I don't think you can get the touchscreen working. On the TouchPad, the screen is controlled by a userland-based driver versus a kernel based driver. That's swell, but since CWM is basically only a kernel, it can't load the driver. I'd love to have someone prove me wrong, really. I just couldn't figure out a way to load it on CWM
Also, you're compiling it wrong if it only works temporarily when flashed. I believe that's like "make kernel" (or the equivalent, it's been awhile lol). I can'r remember the correct command, but I might have solved it by compiling CM and then removing the recovery portion? *shrug*
Good luck, though! I meant this to be taken as someone sharing their knowledge to help others, not as a deterrent. Please, continue with this and make an awesome CWM!

I'm not a kernel/recovery dev so I wouldn't even know where to begin looking at this but I know there was a touch based recovery back before CM9 called TeamWin Recovery Project (TWRP). Maybe it might help to look back at how they got it working and see if the same process can be used for CWM?
Here's the link to the original thread with TWRP thread.
http://forum.xda-developers.com/showthread.php?t=1400649
Hope it helps. I would like to see this work. I love the touch based CWM on my GNex.

Is this still in development?

so finally got mounts to work so this is now a fully functional recovery. the only things not working are the touch options and adb. once i get ts_srv to initialize then swipe gestures will finally work. but for now its still at least a good recovery.

So everything in the touch recovery works besides the touch?
Sent from my Galaxy Nexus using XDA

blckngldhwk said:
So everything in the touch recovery works besides the touch?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
LOL not sure if you are trying to be a smart-a** or honestly asking. you must not be asking for reals since the OP answers that question.
its still an updated CWM from the original 5.0.2.6. so its still better than the one from before.

sk8erwitskil said:
LOL not sure if you are trying to be a smart-a** or honestly asking. you must not be asking for reals since the OP answers that question.
its still an updated CWM from the original 5.0.2.6. so its still better than the one from before.
Click to expand...
Click to collapse
Well in the previous post he mentions adb does NOT work in this new version and I'd consider that a critical part of recovery. Any info on progress related to that? Great work.

famewolf said:
Well in the previous post he mentions adb does NOT work in this new version and I'd consider that a critical part of recovery. Any info on progress related to that? Great work.
Click to expand...
Click to collapse
Yes I agree that adb is a critical part. I'll be looking at init.rc to why adb isn't starting. Just haven't had a chance yet.
Sent from my SAMSUNG-SGH-I727 using XDA

you should really edit the main subject line, since no adb and no touch do not equal "FULLY WORKING RECOVERY." Not sure why anyone would bother using it at this point to be honest

sk8erwitskil said:
Yes I agree that adb is a critical part. I'll be looking at init.rc to why adb isn't starting. Just haven't had a chance yet.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
You may want to search on "Aroma File Manager" (gui file manager you kick off from within recovery by installing the .zip) and see if you can potentially add a direct link to it in recovery...that would be VERY useful addon nobody else currently has as aroma file manager is relatively new.

The aroma touch installers are on most of the roms for my Xperia Arc. I wouldn't say nobody's using them yet as its the latest trend amongst developers. An aroma installer could benefit the touchpad community for those who want to choose what they do and don't want in the rom. But I'm gunna assume for the moment that if a touch recovery won't recognize touch that aroma probably won't work either.

Matt Devo said:
you should really edit the main subject line, since no adb and no touch do not equal "FULLY WORKING RECOVERY." Not sure why anyone would bother using it at this point to be honest
Click to expand...
Click to collapse
Well it is a fully functional recovery. Any recovery aspect you need (backup, restore, install, fix permissions) ALL work. Therefore, it's a working recovery. Touch is an extra and not a requirement to use recovery. So next time you should try thinking before you put down your ignorant ideas.
Sent from my SAMSUNG-SGH-I727 using XDA

sk8erwitskil said:
Well it is a fully functional recovery. Any recovery aspect you need (backup, restore, install, fix permissions) ALL work. Therefore, it's a working recovery. Touch is an extra and not a requirement to use recovery. So next time you should try thinking before you put down your ignorant ideas.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Yes but you say Fully Working and Touch... well if adb is nonfunctional then its not FULLY functional and if Touch isn't working then its not TOUCH then is it... so yes... the thread should be pulled or the title modified
Sent from my cm_tenderloin using Tapatalk 2

I think I broke it

Not sure exactly what happened. I was using the tablet and all of a sudden the bottom three buttons disappeared as well as the top bar. The system kept getting force closes. I rebooted and it just sat in the reboot mode. I tried to recover from the system but that is not working. I cant seem to get the system to mount via usb now. I am in clockwork mod v5.8.0.2 and do not see an option. If I could mount it I could put an img file back on and get it to work. Any help would be great.

xndrxw said:
Not sure exactly what happened. I was using the tablet and all of a sudden the bottom three buttons disappeared as well as the top bar. The system kept getting force closes. I rebooted and it just sat in the reboot mode. I tried to recover from the system but that is not working. I cant seem to get the system to mount via usb now. I am in clockwork mod v5.8.0.2 and do not see an option. If I could mount it I could put an img file back on and get it to work. Any help would be great.
Click to expand...
Click to collapse
You could try to flash back the stock software to see if that helps? Look here for some help.
Are you running a custom ROM or anything else? ALSO, once you do manage to get everything fixed, I would upgrade your CWM to the most current version 6.0.1.0 by flashing this in the older (5.8.0.2) version.

Sounds like it might be permission related, you could try a 'fix permissions' in recovery
Sent from my GT-I9300 using Tapatalk 2

Permissions did not fix it. I am trying to figure out the ADB.

xndrxw said:
Permissions did not fix it. I am trying to figure out the ADB.
Click to expand...
Click to collapse
Just do a bunch of reading! We were all noobs once

I keep getting the message "error: cannot load 'bootloader-grouper-3.34.img' . It seems like something is wrong with the file. Is there a way I could just flash another Rom on this way or even update the clockwork mod using adb?

xndrxw said:
I keep getting the message "error: cannot load 'bootloader-grouper-3.34.img' . It seems like something is wrong with the file. Is there a way I could just flash another Rom on this way or even update the clockwork mod using adb?
Click to expand...
Click to collapse
Did you download the nakasi file from the google site? You shouldn't have an issue with that. And you can update CWM using ADB, just check over in the Android Development section.

A lot of people have been having problems with the nexus 7, best bet is return it and get a new one
Sent from my Galaxy Nexus using xda app-developers app

Finally got it working. Now just need to install the new clockwork mod and move this thing to the GlazedJellyBean rom.

Boooty said:
A lot of people have been having problems with the nexus 7, best bet is return it and get a new one
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
This is seriously not the advice to be giving out on the forums for a minor software issue on an unlocked and rooted tablet especially.

Boooty said:
A lot of people have been having problems with the nexus 7, best bet is return it and get a new one
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Worst advice i've heard, ever.

Sooo true.. You root/ unlock its yours NOT GOOGLES TO REPLACE
CharliesTheMan said:
This is seriously not the advice to be giving out on the forums for a minor software issue on an unlocked and rooted tablet especially.
Click to expand...
Click to collapse
similar issue with TWRP.. I did temp root thru nexus root/recovery app (thanks dev) Then pushed cwm recovery to data/media.. Booted back into temp cwm from above and flashed up to date cwm.. will stick with cwm for now..
good luck OP .

xndrxw said:
Finally got it working. Now just need to install the new clockwork mod and move this thing to the GlazedJellyBean rom.
Click to expand...
Click to collapse
i'm having the same issue. how did you finally get it to work? i've redownloaded the file a bajillion times and still nothing. HELP