Database Info

Whoops. Need help flashing the proper CWM

So. I HAD the proper CWM installed for this device, this was this morning.
Of course though, I always have to mess with stuff and ALWAYS without nandroiding first. Im so dumb!
I was in rom manager and went ahead and flashed the CWM for a xoom . Now when I enter cwm I get errors mounting the external sd . It wont mount even manually do I cant flash anything. Isn't there a way to put the proper cwm into a zip file and flash through cwm using update?
Sent from my Inspire 4G using XDA App

Ok I have the appropriate version of cwm flashed but I am still unable to mount the external sdcard. Is there anyway to flash roms and kernals from the internal storage?
Sent from my Inspire 4G using XDA App

first, it's "kernel"
try this
http://forum.xda-developers.com/showthread.php?t=1123429

finalhit said:
first, it's "kernel"
try this
http://forum.xda-developers.com/showthread.php?t=1123429
Click to expand...
Click to collapse
Sorry for the misspelling and thank you for the info. Technically im not bricked though and that's a guide for unbricking. Is there any easier way to get my external card mounted as I don't have a windows computer on hand to manually install the rom?
Or if I could just install a zip from the internal storage.
Sent from my Inspire 4G using XDA App

it's not just for unbricking. basically, it does a very thorough job of restoring your device to the correct configuration. i imagine you flashing the wrong cwm screwed something up. nvflash restores your device more cleanly, so unless your device has hardare issues, it should fix it.
but yes, you do need a pc to do this...
Sent from my Transformer TF101 using Tapatalk

finalhit said:
it's not just for unbricking. basically, it does a very thorough job of restoring your device to the correct configuration. i imagine you flashing the wrong cwm screwed something up. nvflash restores your device more cleanly, so unless your device has hardare issues, it should fix it.
but yes, you do need a pc to do this...
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Im already running a modded rom - primordial 3.1, but wanted to flash to prime 1.5 anyway. I hope this solves my problems.
Ill borrow my roommates pc tonight and get it done. Thanks for the help guys.
Sent from my Inspire 4G using XDA App

Just in case anyone stumbles across this in the future, I was able to get it worlkng by formatting my sd card. It was the only thing I could do to get CWM to recognize the card.

[Q] HELP xoom root!

ok so i rooted my xoom the other day flashed hammer head 2.1. restored my tablet to stock rooted rom buwhen i did i have now found a way to lock my device. i can boot up and have my su icon available to me however i cannot gain root access even through adb it tells me the file system is read only. so i figured i some how unrooted the device and proceeded to begin the root process for honeycomb. however when trying to push su over to the tablet it tells me the file failed to transfer because the file system is read only what do i do now? Any help would be appreciated.

Ok i have now some how erased my device completely it stops at the moto dual core boot screen. I still have cwm but thats it. Im at a loss guys. Bout to warranty this by runnin over it!
Sent from my ADR6400L using XDA Premium App

josephparlangeli said:
Ok i have now some how erased my device completely it stops at the moto dual core boot screen. I still have cwm but thats it. Im at a loss guys. Bout to warranty this by runnin over it!
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
your a noob mate seriously... these board are full of people like you... 1.. download the stock images from
http://developer.motorola.com/products/software/MZ604_HWI69.zip/
if your device is a wifi only and then push the files with fastboot...
ie.. unzip the folder into where the adb fastboot exe are
1. fastboot flash system system.img
2. fastboot flash boot boot.img
3. fastboot flash user user.img
4. fastboot flash recovery recovery.img (as you obviously cant handle root..)

Dont have to be an ass about it. But yeah already tried that when i try to push the files it tells me there is no such directory found. So i made sure in cwmr the system was mounted then it tries to transfer but tells me the directory is read only. So i tried the unlock procedure to make sure the tablet was unlocked. everything goes smoothly till i try to transfer the files again.
Sent from my ADR6400L using XDA Premium App

josephparlangeli said:
Dont have to be an ass about it. But yeah already tried that when i try to push the files it tells me there is no such directory found. So i made sure in cwmr the system was mounted then it tries to transfer but tells me the directory is read only. So i tried the unlock procedure to make sure the tablet was unlocked. everything goes smoothly till i try to transfer the files again.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Not talking mounting in cwm here bud
Get to fastboot mode not android recovery same process power plus vol down
Then flash the files not push as mounting in cwm only put the files on sd card not flashing it outright from what your reply was
I was a noob once and soft bricked everything and yet i read and read and fixed stuff myself through searching.. Cuz ultimately if its bricked what do u have to lose then ey lol just find and try everything cant make a worse paperweight than one u may already have eh
But get to fastboot not cwm then flash the files like i said and it will almost certainly work
Sent from my HTC Sensation 4G using XDA Premium App

Thats my other problem my sd card slot isnt wrkn that was my initial instinct. If i try to flash to the sd card it says no directory found. Ive used 3 different sd cards and get the same message. Im really thinkin i got a bad sd slot even when it was rooted and running i had issues with the sd card not wrking. I had several back ups on it when it did wrk and those dissappeared as well. I bought the xoom soley because of the sd card slot was pretty much going to be my saving grace when doing back ups if i ever messed up. I tried wrking it in fastboot as well if i try to flash to the system its read only. If i flash to the sd card directory not found. I know these questions are irritating to more savy individuals and i looked around trust me the last thing i like to do is say der i dun broke it i need an adult. Im just makin sure i didnt over look something more savy ppl know about. I honestly think its bricked at this point. Ive tried what you said and any other way i can think of but i alway get some kind of error.
Sent from my ADR6400L using XDA Premium App
Sent from my ADR6400L using XDA Premium App

What version of clockwork mod recovery are you using?

I believe is 4.0.0.2 i just got to wrk i know its the latest release tho.
Sent from my ADR6400L using XDA Premium App

josephparlangeli said:
I believe is 4.0.0.2 i just got to wrk i know its the latest release tho.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would use this recovery instead of 4.0.0.2.

Ok thats a very helpful link. Did not know they had a special recovry for the xoom or realize that it wiped out all media if i didnt have this recovery. Lesson learned however i think its bricked solid now cuz it wont charge or come on at all may very well be a bad unit but i c where i went wrong with su as well i flashed 3.0 with out the chmod 4577 during the su update from cwm. Well im going to grab another one from bb and c what happens the unit is non responsive at this point. Thanks to everyone that posted here for the help.
Sent from my ADR6400L using XDA Premium App

josephparlangeli said:
Ok thats a very helpful link. Did not know they had a special recovry for the xoom or realize that it wiped out all media if i didnt have this recovery. Lesson learned however i think its bricked solid now cuz it wont charge or come on at all may very well be a bad unit but i c where i went wrong with su as well i flashed 3.0 with out the chmod 4577 during the su update from cwm. Well im going to grab another one from bb and c what happens the unit is non responsive at this point. Thanks to everyone that posted here for the help.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
you needed to flash the recovery with FASTBOOT.. not adb push chmod stuff; much easier and the process works
read the top post again.. get the recovery.img file (the v3 one the other fellow told you to grab)
1. hold the volume down button and the power button... some text will come on up the top about fasboot protocol and then
2. leave it plugged in to your computer and DONT TOUCH THE XOOM...
3. get your cmd.exe prompt window out and navigate to where your adb.exe AND fastboot.exe files are (should be tools or platform-tools...)
4. Place the recovery.img file into the explorer window where the adb.exe and fastboot.exe both are.... (this should be there as u keep trying to use adb commands but do it again to make sure)
5. type fastboot flash recovery recovery.img
thats the recovery.img flashed...

Got my xoom replaced the other day works fine have root flashed the above mention cwm and everything worked fine. Funny thing tho when they checked to see if the original device had been unlocked they said it was still locked and they gave me a replacement. Other wise id have had to use the warranty i bought. Just thought that was odd.
Sent from my ADR6400L using XDA Premium App

josephparlangeli said:
Got my xoom replaced the other day works fine have root flashed the above mention cwm and everything worked fine. Funny thing tho when they checked to see if the original device had been unlocked they said it was still locked and they gave me a replacement. Other wise id have had to use the warranty i bought. Just thought that was odd.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Well, there's your answer. You did not successfully unlock.
Glad that you learned some useful things.

flying honey comb on xoom mz601
Hi everybody. I install new image for my xoom MZ601 (tiamat last version).
Xoom from Hongkong (CHINA) with 3G.
i make all steps about unlock bootloader and root. After all that steps - i have ClockworkRecovery v 3.2.0.0 (solarnz-R4c-100611-1150). After reboot (motorola logo) i see all time honeycomb flying.
I need help.
opps: i unbrick my device on android 3.0.1. Now try again to install 3.2 by Tiamat
3.2 doesn't work. SAD

aKolp2010 said:
Hi everybody. I install new image for my xoom MZ601 (tiamat last version).
Xoom from Hongkong (CHINA) with 3G.
i make all steps about unlock bootloader and root. After all that steps - i have ClockworkRecovery v 3.2.0.0 (solarnz-R4c-100611-1150). After reboot (motorola logo) i see all time honeycomb flying.
I need help.
opps: i unbrick my device on android 3.0.1. Now try again to install 3.2 by Tiamat
3.2 doesn't work. SAD
Click to expand...
Click to collapse
You should open a new thread with your issue. Seems the OP in this one has fixed his issues by replacing his Xoom. You'll get better attention by creating a new thread in this forum.

Root Problem SuperOneClick

Hello,
I've got a Skyrocket i727 and am stuck on the psneuter part when trying to root. I'm sorry for posting here since I'm sure the answers lie somewhere, but I've been researching since yesterday and haven't found it. I'm on a satellite internet connection that is pretttty slow.
Anyways, so I have the drivers installed, and then run SuperOneClick as Admin on windows 7. I click root and it runs until psneuter then appears to be stuck. It freezes there. When I close the black command screen that has opened it suggests I turn off debugging mode. When I try to close debugging mode it just stays at Waiting for Device...
So, what am I missing?
Thanks so much in advance.

SuperOneClick didn't work on mine because it had updated to 2.3.6 from 2.3.5...Which one do you have?

You need to use this method if your on android 2.3.6
http://forum.xda-developers.com/showthread.php?t=1340526

My phone
I'm using Gingerbread.uckj2
android 2.3.5

ddxv said:
I'm using Gingerbread.uckj2
android 2.3.5
Click to expand...
Click to collapse
Try this method. It worked better than any I've tried. Make sure you READ the OP. If you have any more questions let us know.
http://forum.xda-developers.com/showthread.php?p=19223405
Sent from my SAMSUNG-SGH-I727 using xda premium

So, I've done some reading about CWM and am still not quite sure what it is. Does it replace my current setup? Do I lose my stuff?
Edit: for anyone else following this topic I found this info about cwm:
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/

Is it possible to do this without having an external sd card?

Must have external SD. CWM is an aftermarket recovery that replaces your stock recovery. It allows you to flash roms, make nandroid backups restore nandroid backups ect.....
Sent from my SAMSUNG-SGH-I727 using xda premium

ddxv said:
Is it possible to do this without having an external sd card?
Click to expand...
Click to collapse
I had this issue over the weekend. Go out to samsungs site and find the kids drivers. In the superclick in the "exploit" switch to zergrush, click root. It should say do you want to install drivers, click yes and it shouldn't take more then 10 minutes.

[Q] Getting my hands on a bricked g2x today....

he said he bricked it trying to upgrade to ICS.
is the sticky at the top still the way to unbrick it? i noticed that a couple links were dead in the first post. granted i didn't go through all 17 pages, just wanted to make sure there wasn't anything newer then whats already been posted.
edit: he did say that the screen is showing s/w if that matters

Was it bricked by flashing a o2x rom? I think that may be the hardest brick I have heard of but still fixable. I believe if that is the case than following the sticky should restore the baseband and everything else.
Honestly though I would first try just reflashing CWM via nvflash, boot into recovery and load a stable GB rom. If that works, great.

LurkerRWO said:
Was it bricked by flashing a o2x rom? I think that may be the hardest brick I have heard of but still fixable. I believe if that is the case than following the sticky should restore the baseband and everything else.
Honestly though I would first try just reflashing CWM via nvflash, boot into recovery and load a stable GB rom. If that works, great.
Click to expand...
Click to collapse
he just said things went haywire when trying to flash ICS. i've been messing around with the sticky but can't get anything to work....yet!

im on windows 7 if that matters
and after i boot into recovery the screen is just flashing black. any ideas?

everything i do with flashing it just sits at the prompt saying "flashing" and nothing else happens.

blackbeasst said:
he just said things went haywire when trying to flash ICS. i've been messing around with the sticky but can't get anything to work....yet!
Click to expand...
Click to collapse
You apparently you did not even read the first post. XP only, will not work with Windows 7.
"As many have stated, pushing the v21E_00.kdz via the KDZ_FW_UPD program does work. It's just touchy.
This is a step by step guide to get you back in to working shape.
Note: You MUST do this via a PC running Windows XP. Running Vista/7 in compatibility mode is not going to work, period.
Edit: As an alternative, a virtual environment running XP will do the job. Those steps are up to you."

That's not true. I updated the baseband using win7 on my first try. No need for comparability mode.
Sent from my LG-P999 using XDA App

LurkerRWO said:
That's not true. I updated the baseband using win7 on my first try. No need for comparability mode.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Can confirm that too. Was working fine on 32 bit win7, using the method from the stickies upgrading wind's June baseband.
Sent from my LG-P999 using xda premium

duple and lurker, thanks for the confirmation that it works with 7
when i try and push the kdz i get the dreaded phone not found.

ok im on my xp machine here at work and heres what i got:
Part 1: Download the files you will need below.
V21E_00.kdz
KDZ_FW_UPD_EN
One-Click-G2x-recovery-flasher-06-16.rar
LG USB Drivers G2x
Part 2:
1) Install the LG G2x USB drivers to your WinXP machine.
2) Extract the entire contents of the One-Click recovery in to a folder and keep it handy.
3) Remove the battery from the phone. Hold both volume buttons and plug in the USB cable. If you are asked for a driver, look in the APX folder where you extracted the One-Click recovery archive.
4) Run OneClickRecoveryFlasher.exe and flash the stock recovery. Wait for the process to finish and close all windows and unplug the phone.
no problems with above steps. after that nothing works. when i put the battery back in and turn on thats when i get the flashing black screen, not back to the s/w screen.
5) Put the battery back into the phone and turn it on. You will be back at the S/W Upgrade screen. This is where you want to be! Now plug the USB cable back in to the phone. If everything is up to snuff you should have no driver problems at this point.
6) Extract KDZ_FW_UPD_EN.7z in to a folder. Inside is a msxml.msi. You need to run and install this first!
7) Run KDZ_FW_UPD.exe.. Leave the type set to CDMA and the phone mode set to DIAG. DO NOT CLICK ON "Read phone information"
8) Click the folder icon and load the V21E_00.kdz
9) Click launch software update (and pray!)

ok just for craps and giggles i tried booting into recovery and actually got the box with arrow and android! but it then reboots back to the lg screen and then flashing black screen

WOOT! finally able to get into CWM recovery!
is all that needs to be done now is install a stable rom?

double WOOT! back up and running. time to test the functionality of if though!
edit: can't find the sim and no service.

blackbeasst said:
double WOOT! back up and running. time to test the functionality of if though!
Click to expand...
Click to collapse
Delighted to hear that. So, another confirmation of the "old" folks stating it's 99.9% un-brickable.
Sent from my LG-P999 using xda premium

DupleX01 said:
Delighted to hear that. So, another confirmation of the "old" folks stating it's 99.9% un-brickable.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
and im a tard. sim was inserted bass akwards

blackbeasst said:
and im a tard. sim was inserted bass akwards
Click to expand...
Click to collapse
Congrats man.
Sent from my LG-P999

wifi seems to be flaky. keeps scanning and dropping work and home network
also it appears that the market wasn't on that version of the rom. is that a quick fix?

Now you have the recovery and baseband sorted, start from scratch and do a full wipe(including system internal/external SD). Then flash a stable ROM Weapon/EB to make sure everything is good. Just my 2 cents
Sent from my LG-P999 using xda premium

DupleX01 said:
Now you have the recovery and baseband sorted, start from scratch and do a full wipe(including system internal/external SD). Then flash a stable ROM Weapon/EB to make sure everything is good. Just my 2 cents
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
im was lucky to get it up and running, so im still a flashing noob! but what is considered a stable rom for this phone?
i grabbed one from cyanmod earlier today. i think it was from around 3/13?

blackbeasst said:
im was lucky to get it up and running, so im still a flashing noob! but what is considered a stable rom for this phone?
i grabbed one from cyanmod earlier today. i think it was from around 3/13?
Click to expand...
Click to collapse
You were lucky, indeed!
A CM nightly can be stable too, however I would flash either Weapon or Eagles Blood for a couple of days to have a piece of mind that everything is working cool. The most important would be a proper full wipe (cache, dalvik, system under mounts and storage, battery stats and imho internal and external SD too) too get rid of the previous mess caused by the unsuccessful flash, etc.
Sent from my LG-P999 using xda premium

TF101 Stuck in Recovery

A buddy of mine has a TF101 and has been itching to get on JB now that there's a handful of unofficial ROMs. I personally rooted and installed ICS on it some time ago so it's rooted and everything, blah blah. He lives across town so I was walking him through the installation via Gtalk. Had I been actually with him I don't think this stupid crap would have happened, but anyway.
So the first part of this journey was a dumb mistake as I was having him install the EuroSkank ROM for the wrong device. The only Android device I have is a Galaxy Nexus so when I went to searching ROMs for his Transformer I just typed Transformer into 'Find Your Device' and thoughtlessly went with the first selection. I had him flash a couple TF300T ROMs, which of course didn't boot with his TF101. In the process of troubleshooting I had him restore into ICS, which worked fine, and updated CWM which was a few versions behind. He still had a version with orange text so figured an updated Recovery may solve the issue. ROM files and Gapps were on the external sdcard, for whatever reason the newer version of CWM doesn't read the external sdcard so the files are now inaccessible. This coincidentally is also where his backed up ICS ROM is. The only thing on his internal memory that is accessible is the Android HD Super Wipe, which is worthless for now, lol.
At this point in time does it seem the only solution is to use ADB to issue some commands and push files etc? The problem with that (drum roll) is that the USB data cord is apparently messed up because the two PC's in the household do not recognize a device when it's plugged in.
It's been a hell of a ride and I curse CWM for removing the feature to read external SD. Or can it be enabled somehow? Would appreciate any (constructive) input, thanks.

Ok, seems the only solution is gonna be a new USB data cord. One's been ordered so I assume that'll solve this issue once it's here!

New data cord arrived, device still isn't detected in Windows. Seems like the data port on the tablet is borked. Is there anyway this thing can be recovered? There's no ROM to flash on the device's internal memory. ROM's etc are stored on the external sdcard which aren't accessible. Lost cause?

Do you have the correct drivers install?
What about NVFlash? Are you able to get into APX mode and does the
PC see the TF in APX mode?

belvedere said:
New data cord arrived, device still isn't detected in Windows. Seems like the data port on the tablet is borked. Is there anyway this thing can be recovered? There's no ROM to flash on the device's internal memory. ROM's etc are stored on the external sdcard which aren't accessible. Lost cause?
Click to expand...
Click to collapse
Hahahahahaha sorry that was soo funny... i think you are on CWM 5.x.x.x. which allows only internal memory access, so do the following
1) Download nvflash (easy tool) from following link
http://forum.xda-developers.com/showthread.php?p=26893961
2) download universal naked drivers from the above link
3) download the latest ASUS stock firmware from the Asus website
4) press down volume up+power buttons together to get into APX mode ( in this mode screen will remain blank) now follow the instruction from the link to unroot and flash latest Asus firmware...
5) use easy flash to root and install recovery...
6) easy flash will install rogue recovery by default, so if you like it use it otherwise download and flash TWRP 2.2.1..
Remember to read all instructions and you should be good to go... good luck....
Sent fom my Transforme T101 using xda app-developers app

Having the same problem. Stuck in recovery while trying to flash the stable cm9.
Sent from my Galaxy Nexus using xda app-developers app

adrianlorion said:
Having the same problem. Stuck in recovery while trying to flash the stable cm9.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Care to explain little more ?
Sent from my Transformer TF101 using xda app-developers app

baseballfanz said:
Do you have the correct drivers install?
What about NVFlash? Are you able to get into APX mode and does the
PC see the TF in APX mode?
Click to expand...
Click to collapse
Followed your instructions and problem solved. I'm back to 4.0.3 with root and searching for a Rom to flash.
Sent from Samsung Galaxy Nexus.
Devices:
Samsung Galaxy Nexus
Asus Transformer tf101
---------- Post added at 09:34 PM ---------- Previous post was at 09:23 PM ----------
udupa82 said:
Hahahahahaha sorry that was soo funny... i think you are on CWM 5.x.x.x. which allows only internal memory access, so do the following
1) Download nvflash (easy tool) from following link
http://forum.xda-developers.com/showthread.php?p=26893961
2) download universal naked drivers from the above link
3) download the latest ASUS stock firmware from the Asus website
4) press down volume up+power buttons together to get into APX mode ( in this mode screen will remain blank) now follow the instruction from the link to unroot and flash latest Asus firmware...
5) use easy flash to root and install recovery...
6) easy flash will install rogue recovery by default, so if you like it use it otherwise download and flash TWRP 2.2.1..
Remember to read all instructions and you should be good to go... good luck....
Sent fom my Transforme T101 using xda app-developers app
Click to expand...
Click to collapse
Quoted the wrong post. Followed these steps and it worked no problem.
Sent from Samsung Galaxy Nexus.
Devices:
Samsung Galaxy Nexus
Asus Transformer tf101