Database Info

HELP!!! Clockworkmod not flashing properly Brainmasters ICS and Linux Ubuntu 11.10

I flashed latest clockwork mod after installing brainmasters ics tweaked. When i noticed my mms wasnt working i decided to re flash another rom but when i booted into recovery it got back into fastboot mode and tells me "no boot or recovery img"
I have re flashed all versions through rom manager but they wont stick. I tried to push it with fastboot and my computer but my Ubuntu 11.10 wont recognize my Ns4g. I installed all the android sdk, adb, and fastboot files but when I type ./adb devices its doesn't come up with my device. ./fastboot flash boot recovery3101.img doesnt work either. Juat says <waiting on device>

flash image by GUI
search market for this app and use it to flash kernel image.
I'm on mobile
Sent from my Nexus S 4G using xda premium

1st. post in the correct section. This way you can get your answer quicker and you're not annoying everyone.
2nd. Find yourself a WINDOWS PC and install android SDK and all drivers for your phone to be recognizable. Then follow one of the posts in here to flash recovery.
You could also install ROM manager from the market and use it to flash recovery through it but its always good to have a proper SDK setup for this type of emergency.

This has happened to me before and I have fixed it by flashing the latest cwmr multiple times.
Try using a different USB cable if your com still doesn't recongize it.
PS now I use twrp and i like it a lot better
Sent from my Nexus S 4G using xda premium

I didnt see any other NS4g section. Sorry bud.
Would flash image gui work well to flash twrp?
When i use rom manager it says successfully flashes rom but then i reboot and get the sane no boot or recovery img. I dont have access to a windows pc...
Can a mod please move this to the nexus help section?

As stated, reboot from and get rom Manager from market. Try reinstalling recovery or scroll down and there is an option to use older versions and flash an older version.
Sent from my Nexus S 4G using xda premium

toddlmr said:
As stated, reboot from and get rom Manager from market. Try reinstalling recovery or scroll down and there is an option to use older versions and flash an older version.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Okay todd,
As stated before, back in my FIRST post i have rom manager and I havr flashed all versions of cwm available. 3.0.0.0 to 5.0.2.0 but none of them stick.
I just got flash image gui and tried to flash twrp and it said it was successful but when i rebooted i got the same no boot or recovery img

Make sure you have debug turned on.
Sent from my Nexus S 4G using xda premium

I had this happen to me when I first flashed a ICS port. the only thing that worked for me was to dl the Flash Image GUI from the market & flash your cwm file.
courtesy of my Nexus S 4G using Tapatalk

bnitty said:
I had this happen to me when I first flashed a ICS port. the only thing that worked for me was to dl the Flash Image GUI from the market & flash your cwm file.
courtesy of my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
+1 agreed it works like a lucky charm.
Sent from my BB GPA19x Linux S 4G using xda premium

might not be what you want to hear, but... maybe start from scratch again. find a guide that lets you revert to the stock image and then reroot. sometimes... you just have to start with a clean slate. good luck man. sounds like a stressful / annoying issue to have.

ehac1680 said:
Make sure you have debug turned on.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I never turn it off
bnitty said:
I had this happen to me when I first flashed a ICS port. the only thing that worked for me was to dl the Flash Image GUI from the market & flash your cwm file.
courtesy of my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
info[]box1 said:
+1 agreed it works like a lucky charm.
Sent from my BB GPA19x Linux S 4G using xda premium
Click to expand...
Click to collapse
I just tried to flash twrp and then cwmr 5.0.2.0 with Flash Image GUI and neither of them stuck...
Is it my only option to ask my friends if I can use their computer? I hate loading things on peoples computer. I feel bad...

mercado79 said:
might not be what you want to hear, but... maybe start from scratch again. find a guide that lets you revert to the stock image and then reroot. sometimes... you just have to start with a clean slate. good luck man. sounds like a stressful / annoying issue to have.
Click to expand...
Click to collapse
Im okay with starting over but I cant even get my computer to recognize my NS4G. I'm using Ubuntu 11.10 and I have Android sdk and fastboot on my computer but when I boot my phone into fastboot it isn't recognized by my computer. All "./adb devices" or "./fastboot devices" brings up is nothing!
If I can get my Linux machine to recognize my phone I would gladly return to stock unrooted and start over.

Flash twice in rom manager. See if that changes anything. Don't reboot between just one after another. Also, in rom manager hit menu and clear download cache before you try flashing.

info[]box1 said:
flash image by GUI
search market for this app and use it to flash kernel image.
I'm on mobile
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Its flash image GUI by joeykrim......
Sent from my Nexus S 4G using xda premium

Ochochinko said:
Im okay with starting over but I cant even get my computer to recognize my NS4G. I'm using Ubuntu 11.10 and I have Android sdk and fastboot on my computer but when I boot my phone into fastboot it isn't recognized by my computer. All "./adb devices" or "./fastboot devices" brings up is nothing!
If I can get my Linux machine to recognize my phone I would gladly return to stock unrooted and start over.
Click to expand...
Click to collapse
No ./ its just fastboot
So it should look like
# fastboot devices
# fastboot flash recovery recovery.img
Etc.
Sent from my Nexus S 4G using xda premium

This happened to me and I was freaking out until I updated super users binary then flashed clockworkmod and it worked fine.
Sent from my Nexus S 4G using xda premium

Oops didn't read both pages

I've had this happen to me several times. The problem happens any time I use an app (i.e. Rom Manager or Flash Image GUI) to flash a new recovery.
The only way I've been able to resolve it is to
1. Flash cwm 3.1.0.1 with fastboot
2. Go into recovery and flash cwm 5.0.2.0.
3. DO NOT update CWM when relaunching Rom Manager or like app.
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
No ./ its just fastboot
So it should look like
# fastboot devices
# fastboot flash recovery recovery.img
Etc.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Either work if he is in the right directory.
@OP: Did you follow the Ubuntu guide to have it recognize your device? I'm on Ubuntu and everything works fine for me.
http://forum.xda-developers.com/showthread.php?t=883032
Greetz

Cwm?

My cwm cannot find my sd card so that means I can't flash zip files. Can anyone help me get cwm 4.0.0.9? Currently I have cwm 5.0.2.7
Sent from my myTouch 4G Slide using xda premium

What's the error? Is it that weird Lum thing?
Sent from my Bulletproof_Doubleshot using xda app-developers app
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
Also the one your on is the most stable, have you tried messing with your SD? This happens to me every once in a while. I just reboot.
Sent from my Bulletproof_Doubleshot using xda app-developers app

AgentCherryColla said:
What's the error? Is it that weird Lum thing?
Sent from my Bulletproof_Doubleshot using xda app-developers app
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
Also the one your on is the most stable, have you tried messing with your SD? This happens to me every once in a while. I just reboot.
Sent from my Bulletproof_Doubleshot using xda app-developers app
Click to expand...
Click to collapse
I think its the lum thing when using terminal emulator but some told me to flash 5.0.2.7 and I did and it's messed up
Sent from my myTouch 4G Slide using xda premium

Is there a problem with the true official CWM release or are you just wanting to change? And at this point, unless you are trying to apply an "update.zip" file you don't need access to your external card.....unless I am just misunderstanding your issue. ADB will flash your new recovery directly to the correct partition on your internal system memory. Won't it??
BTW Agent.....what is that weird "Lum" thing? I've not run across that term.

its the error with opening sdcards on cwm 6.x

xmc wildchild22 said:
its the error with opening sdcards on cwm 6.x
Click to expand...
Click to collapse
Thank you XMC....I'm always anxious to learn. :good:
Do you have any idea why that type of error would pop up out of the clear blue like that?

WeekendsR2Short said:
Is there a problem with the true official CWM release or are you just wanting to change? And at this point, unless you are trying to apply an "update.zip" file you don't need access to your external card.....unless I am just misunderstanding your issue. ADB will flash your new recovery directly to the correct partition on your internal system memory. Won't it??
BTW Agent.....what is that weird "Lum" thing? I've not run across that term.
Click to expand...
Click to collapse
Can you help me with this step by step
Sent from my myTouch 4G Slide using xda premium

K7Cobb said:
Can you help me with this step by step
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
You really won't have any problems. I promise. It flashes just like any other version of CWM thru adb. Just download it from my "Tools" thread, place it where you normally flash a file from, rename the file to boot.img. Then from your command window on your computer you just do the following string of commands:
reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Remember? :good:

flash boot?
WeekendsR2Short said:
You really won't have any problems. I promise. It flashes just like any other version of CWM thru adb. Just download it from my "Tools" thread, place it where you normally flash a file from, rename the file to boot.img. Then from your command window on your computer you just do the following string of commands:
reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Remember? :good:
Click to expand...
Click to collapse
Hang on, isn't he trying to flash his recovery? I've never done it through fastboot, but I can't help but think that flashing a recovery image to the boot partition won't turn out well... There is an option in fastboot to flash recovery, but again, I've never used it.
The way I've always flash recovery images is (in terminal emulator or ADB)
flash_image recovery /sdcard/name-of-recovery.img
As I was looking up this command, I saw someone (well, not just anyone, kornyone) suggest using ROM Manager... Although you would, of course, have to flash an older version of CWM.

My guess could be stupid but try redownloading cwm and reflash cwm recovery ...
Sent from my myTouch_4G_Slide using xda app-developers app

@Weekend um says something about reboot is not recognized as an external command,operable program or batch file. Have any idea as to why this shows and could you help with this problem

K7Cobb said:
@Weekend um says something about reboot is not recognized as an external command,operable program or batch file. Have any idea as to why this shows and could you help with this problem
Click to expand...
Click to collapse
It's an Android command, you need to either run it through ADB Shell or through the Terminal Emulator (You ran it directly in the Windows command line)
Do you have ADB and fastboot setup? If not, go download Android SDK from Google and get it installed. (Be sure to install Platform Tools as well as Tools)
If you haven't setup the Android SDK before, you'll need to install the Java SDK too.
The second two commands he provided are not ADB commands, they should be run directly from the directory where fastboot is installed, which is the Android SDK Install location\platform-tools.
The default Android SDK install location (as of the new version I downloaded yesterday) is C:\Users\(Your Name)\AppData\Local\Android\android-sdk . The old default location was C:\Program Files (x86)\Android\android-sdk . I like that one better. You can use whichever you wish, just be sure you remember where it is.
I can't post links, otherwise I'd link you to a guide. Sorry :/

Nvm thank you all
Sent from my myTouch 4G Slide using xda premium

Sompom said:
Hang on, isn't he trying to flash his recovery? I've never done it through fastboot, but I can't help but think that flashing a recovery image to the boot partition won't turn out well... There is an option in fastboot to flash recovery, but again, I've never used it.
The way I've always flash recovery images is (in terminal emulator or ADB)
flash_image recovery /sdcard/name-of-recovery.img
As I was looking up this command, I saw someone (well, not just anyone, kornyone) suggest using ROM Manager... Although you would, of course, have to flash an older version of CWM.
Click to expand...
Click to collapse
Your way will work but I promise the ADB fastboot flash sequence will too. It's the only way I've ever flashed my recoveries. Always more than one way to skin a cat.
---------- Post added at 10:49 PM ---------- Previous post was at 10:37 PM ----------
K7Cobb said:
@Weekend um says something about reboot is not recognized as an external command,operable program or batch file. Have any idea as to why this shows and could you help with this problem
Click to expand...
Click to collapse
Sorry......I just kinda took something for granted. (as usual)
Before you can run that string I told you about you have to tell your system it is an ADB command. ACTUALLY it's like this:
ADB reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Sorry for my oversight. I hope it didn't cause you much grief.

I do the stuff correct. But when I go to clock work it still says 5027
Sent from my myTouch 4G Slide using xda premium

So when you enter the command it tells you "sending image" and then the time?
After that it tells you "writing image" then the time and then something to the effect of "transfer complete"? If it does then somehow you've gotten the images confused and renamed the 5.0.2.7 image and put that one in your flashing folder and not the 4.0.0.9 image.
It's always your choice what you run on your phone but I still don't understand your opposition to the official CWM release. ANYway....Good Luck in your attempt.

WeekendsR2Short said:
So when you enter the command it tells you "sending image" and then the time?
After that it tells you "writing image" then the time and then something to the effect of "transfer complete"? If it does then somehow you've gotten the images confused and renamed the 5.0.2.7 image and put that one in your flashing folder and not the 4.0.0.9 image.
It's always your choice what you run on your phone but I still don't understand your opposition to the official CWM release. ANYway....Good Luck in your attempt.
Click to expand...
Click to collapse
Omg it does not work Clearly if I'm having problems. Not meant to be taken in a mean way but I keep telling people the same thing
Sent from my myTouch 4G Slide using xda premium

Omg. What is wrong with this???!?!?!?!?!? I need MAJOR HELP!!!
Sent from my myTouch 4G Slide using xda premium

What I'm trying to find out is how in the crap you got 5.0.2.7 on your phone to start with. If you flashed it thru terminal emulator you can put 4.0.0.9 on there the very same way. If you flashed it thru ADB you can put 4.0.0.9 on there the very same way. See what I'm saying? Have you ever flashed anything or did you get it on there thru maybe Rom Manager. I'm just looking for a clue. SEE? I know you're having a problem but we need to more than "it's not working".

K7Cobb said:
I do the stuff correct. But when I go to clock work it still says 5027
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I am running 5.5.0.4 and ROM manager reports the version as 5.0.2.7. Seems to work fine here.
Hastily spouted for your befuddlement

Any important thing to know about before/after rooting and unlocking

As above, is there any good tips or useful tips that I should know before rooting and unlocking this device? I mean things such as not doing a factory reset in the bootloader as that can cause a brick
Thanks
Sent from my R800i using xda app-developers app

+1
i also want to know that
EDIT:
Is a good idea make a sticky thread where we can see what we should't do....to prevent brick the device while nvflash isn't available on jb bootloaders

Is there anything that can't be done in TWRP that can be done in CWM?

cwm can't do any backup in my device (search in this forum)
twrp work fine
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Thanks for the reply. Do they both have the exact same functions? Can TWRP read the SD card?

http://forum.xda-developers.com/showthread.php?t=1672108
+external sd
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Thank you.
Sent from my R800i using xda app-developers app

From my recent experience with unlocking my Tf300T:
1. Read all directions slowly and multiple times.
2. Only method to flash TWRP was putting recovery.blob in C:\android\platform-tools no other method would work. All i would get was soft
brick. You don't need all the one step tools, videos. etc. While these might be helpful to some, once I put blob in correct folder and pushed via ADB it was simple.
3. Once you unlock you can not go back and you loose your warranty.
4. Root has to come in your ROM. Currently there is not root method for us.
Good luck and have fun. May I suggest Energy Rom. I love it.

+1 for TWRP.
CWM wouldn't work properly on my tab. It wouldn't flash zips or make backups properly. I'm not putting CWM down by any means because I use it on my phone and it works flawlessly. It just didn't work the way it should for me on my TF300T.

Thanks for the help but I thought you had to put TWRP.blob in the root of the SD card?
Sent from my R800i using xda app-developers app

No you don't put it on SD card. It needs to go in the sdk platform tools folder on your c drive
Sent from my HTC EVARE_UL using xda premium

You put in on the root of the SD card if you're using terminal emulator on the tablet don't you?
Sent from my R800i using xda app-developers app

How would I go about getting TWRP without root? Just realised I'll need a recovery to root the tablet since I'm upgraded to JB
Sent from my R800i using xda app-developers app

UndisputedGuy said:
How would I go about getting TWRP without root? Just realised I'll need a recovery to root the tablet since I'm upgraded to JB
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
You must.....
Unlock the bootloader
Reboot into the bootloader - power plus vol down
In the bootloader select the USB icon while having your tablet connected to a PC that can do adb
Flash twrp using fastboot per instructions on the twrp site.
You now have recovery for flashing other zip files, like the superuser zip to get root.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Thank you for the assistance. I don't suppose there are any guides for TWRP on this forum or is it relatively straight forward?
Sent from my R800i using xda app-developers app

UndisputedGuy said:
Thank you for the assistance. I don't suppose there are any guides for TWRP on this forum or is it relatively straight forward?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
As long as you put the blob in the right folder and flash it correctly it should take you less than 5 min to get recovery. Then toy just have to wait until your first ROM is downloaded to flash it. Just follow directions on Twrp site. Quicker way to get cmd line in sdk-platform tools is, while in that file, right click on empty white space and hold ctrl. Will open adb in correct directory and make it stupid simple.
Sent from my HTC EVARE_UL using xda premium

I found this:
You will need fastboot for this method. Download the above file, check the md5, rename to twrp.blob and put the file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere). Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm). The device will now be in fastboot mode. Plug the device into your computer. Run the following command via the command line:
fastboot -i 0x0B05 flash recovery twrp.blob
Which does help but I'm not sure where on my PC I have to enter the command line?
Sent from my R800i using xda app-developers app

UndisputedGuy said:
I found this:
You will need fastboot for this method. Download the above file, check the md5, rename to twrp.blob and put the file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere). Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm). The device will now be in fastboot mode. Plug the device into your computer. Run the following command via the command line:
fastboot -i 0x0B05 flash recovery twrp.blob
Which does help but I'm not sure where on my PC I have to enter the command line?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
open the terminal and go to fastboot file using cd command (windows)...exemple cd:\fastboot
when you are in that place run
fastboot -i 0x0B05 flash recovery twrp.blob

So do I just need to type those two commands on terminal? Is there anything else I need to download besides the TWRP file? I appreciate the help, thanks.
Sent from my R800i using xda app-developers app

UndisputedGuy said:
So do I just need to type those two commands on terminal? Is there anything else I need to download besides the TWRP file. I appreciate the help, thanks.
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
yes i think so.
i never do this so im typing what i read.
i belive in god so im wainting for nvflash on jb bootloader :laugh:

No update.....

Can any one tell the reason why am i not getting the update of 4.1.2 on i9020........i have listened mostly have got it......and also my phone is unrooted
Sent from my Nexus S using xda premium

umarshafi said:
Can any one tell the reason why am i not getting the update of 4.1.2 on i9020........i have listened mostly have got it......and also my phone is unrooted
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
What carrier are you on? Is it 9020a or 9020t? Are you on the stock rom and stock recovery? Have you manually looked for an update? (Clearing Google Services Framework data then going to Settings > About phone > System updates)

Yes i have checked manually by settings........from where to check the i9020a or i9020t......
Sent from my Nexus S using xda premium

Plz tell whats the meaning of clearing google services framework data........and how to do it.....
Sent from my Nexus S using xda premium

umarshafi said:
Plz tell whats the meaning of clearing google services framework data........and how to do it.....
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Go to the Settings, Applications, swipe to all and search for Google Services Framework.
Then clear data.

Still its showing system is up to date
Sent from my Nexus S using xda premium

umarshafi said:
Yes i have checked manually by settings........from where to check the i9020a or i9020t......
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Check the IMEI sticker at the back of phone under the battery.

Sorry but couldnt find only written there is a3lGTI9020..........
Sent from my Nexus S using xda premium

Yes its i9020a.......plz can any one tell why am i not getting an update
Sent from my Nexus S using xda premium

Odp: No update.....
Update it manually using fastboot tool with google android images.
Sent from my Nexus S

Does it require root....????
Sent from my Nexus S using xda premium

Can you plz tell the most easy way of rooting my mobile......
Sent from my Nexus S using xda premium

umarshafi said:
Does it require root....????
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Root not required to update factory images, but device must be unlocked (see step 9)
Install Android SDK Tools
When SDK Manager runs, select Android SDK Platform Tools and Google USB Driver, see attached pic
If missed, run SDK Manager again as Administrator
Download Google Factory Images for your device (eg. sojua for i9020a) and JB4.1.2
Extract (7-zip or whatever) the tar file (.tgz) into C:\Program Files\Android\android-sdk\platform-tools folder
Open Windows Prompt, change directory to platform-tools folder
Put your Nexus S in Bootloader (fastboot) mode. (Power off, press power-on while holding Vol-Up)
Test fastboot connectivity, should show your nexus device
Code:
fastboot devices
Unlock bootloader if not already unlocked. This will wipe all data. So backup first.
Code:
fastboot oem unlock
Run flash-all.bat. This will flash bootloader, radio(baseband) and system rom. You can execute the commands within manually if desired.
To root, I like the manual way.
Download Clockworkmod Recovery and save into platform-tools folder
Download Superuser and copy into SD/USB of your Nexus S.
Boot into fastboot and flash Clockworkmod Recovery
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Select RECOVERY in fastboot menu and boot into clockworkmod recovery.
Install zip from sdcard -> choose zip from sdcard, select the Superuser-3.2-arm-signed.zip that you copied in step 2.
Reboot and you are rooted.

Adb sideload not working

Adb detects my device but whenever i try to flash something through sideload it say error closed ,i have win 8.1 is that a problem?
Sent from my Nexus 5 using XDA Free mobile app

bhavstech said:
Adb detects my device but whenever i try to flash something through sideload it say error closed ,i have win 8.1 is that a problem?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Can you run any other adb commands? adb devices for example?
Are you using your recovery properly to activate adb sideload mode?

rootSU said:
Can you run any other adb commands? adb devices for example?
Are you using your recovery properly to activate adb sideload mode?
Click to expand...
Click to collapse
only adb devices work

bhavstech said:
only adb devices work
Click to expand...
Click to collapse
So you've booted into recovery?
adb devices works there?
What recovery do you have?
how did you activate adb sideload in recovery?
What was the adb command you used to side load?
What is the full error?
Please answer all questions
Sent from my Nexus 5 using Tapatalk

rootSU said:
So you've booted into recovery?
adb devices works there?
What recovery do you have?
how did you activate adb sideload in recovery?
What was the adb command you used to side load?
What is the full error?
Please answer all questions
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
1.yes
2.twrp
3.twrp>advanced>adb sideload
4.adb sideload xyz.zip
5.error is "error closed"
can it be incompatibility with win8.1 bcoz this is the first time i m using adb win8.1 with before i used it on win7
edit: blustacks was creatin a problem its solved

Bluestacks? Interesting and good to know!
Sent from my Nexus 5 using Tapatalk

rootSU said:
Bluestacks? Interesting and good to know!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yeah i reinstalled the driver (i thought my laptop had some issue with driver)then the error said :"more than one devices or emulators connected" so when i exited bluestacks(android app "emulator") it flashed properly