Database Info

brick , help please

i have unlocked and root my phone
i tried to flash some rom with no Success.....always stock on boot animation
What happened after all my "games" with the phone is that the recovery cant access the sd memory !
i always got this :
e: cant mount /sdcard with any option : flash from zip or restore.
so now i cant flash any rom or made a restore ....
the good news is that fastboot and recovery work...
but my phone doesn't have a working rom now
it happened after i tried to to factory reset from fast boot
what can i do ??

Try to flash your originally RUU to restore your stock ROM.

as i said i cant flash ....
not from the recovery

You don't need the recovery to flash your RUU, because the RUU is a .exe from your computer.
Try this : http://forum.xda-developers.com/showthread.php?t=1630459 -> The 8th post.

i did everything on post 8
i Stuck on the adb push
i put the utb.zip in the same folder where the adb.exe
i write the command in cmd while my phone is in recovery mode
i got this :
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
what to do ???

its ok now
thanks

Please press Thanks button if I help you

Michael77500 said:
Please press Thanks button if I help you
Click to expand...
Click to collapse
Please don't solicit thanks, it makes you look like an attention whore, a really cheap french one

[Recovery] official cwm 6.0.1.9 [update 11/16]

Removed all my Dropbox links because they disabled my account due to too much traffic, if you guys want them back please consider donating a buck or two for a Mediafire Pro account...​I didn't develop this, just getting the word out that's it's officially available for the Nexus 7. You can either install the "normal" version or touch version from ROM Manager
UPDATE 11/16 new version posted by Koush 6.0.1.9
CWM Regular
CWM Touch
Here is the CWM ZIP by osm0sis:
Touch 6.0.1.9
Regualr 6.0.1.9
You NEED an unlocked bootloader in order to flash this check this thread on how-to unlock/root etc Nexus 7 Toolkit
If you just want to apply an OTA update and you haven't got it, you can do so by booting into CWM without installing it or having root.
first download and save OTA files from OTA 4.1.1 files and save to your /sdcard
then use
./adb reboot bootloader
./fastboot boot recovery-clockwork-touch-6.0.1.9-grouper.img
select install zip from sdcard
toggle signature verification and make sure it's disabled
select the file you downloaded earlier and install
reboot and you will be updated
Click to expand...
Click to collapse
If you want to have CWM permantly installed, first make sure you have root...use Root Explorer or any other file manager with root access and go to /system and delete recovery-from-boot.p
now use
./adb reboot bootloader
./fastboot flash recovery recovery-clockwork-touch-6.0.1.9-grouper.img
./adb reboot
Click to expand...
Click to collapse
You now have CWM installed.
I'm not responsible if you brick your tablet, it blows up mid flash etc
Make sure you know how to use ADB and have the SDK installed, you need that in order to do all of the above steps
Also make sure you have the recovery files saved to /sdk/platform-tools and also fastboot.exe has to be there also
Any commands that start with ./ are for linux/osx...just remove those when using windows
Click to expand...
Click to collapse

If you already have CWM or another recovery installed and would like to replace it with 6.0.0.6 Touch, I have packaged this file as a flash able zip file.
Download the zip file from http://db.tt/t13uCIRV and flash in recovery. To test, go to advanced -> reboot recovery and CWM Touch 6.0.0.6 should load up.
** edit 7/21/12**
Here's the zip file for the new touch recovery 6.0.1.0 http://db.tt/pLDeKXEf
Feel free to mirror!
Sent from my Nexus 7 using xda app-developers app

Flashing when I get home thanks.
Sent from my Galaxy Nexus using xda app-developers app

I flashed this from rom manager and so far have not had any of the problems I have had in some of the interim CWM's like inability to delete back ups or mounting system.

hey dude it's 6.0.0.6 not 6.0.6

mrich137 said:
If you already have CWM or another recovery installed and would like to replace it with 6.0.0.6 Touch, I have packaged this file as a flash able zip file.
Download the zip file from http://db.tt/t13uCIRV and flash in recovery. To test, go to advanced -> reboot recovery and CWM Touch 6.0.0.6 should load up.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Shano56 said:
hey dude it's 6.0.0.6 not 6.0.6
Click to expand...
Click to collapse
oops, typo...thanks, I will fix it now

Same here. Flashed via CWM with no issues what so ever. Shocking how much faster backups are now!
Sent from my Nexus 7 using xda premium

I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks

BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
It works as long as you're connected to a computer, so you can access recovery from bootloader you just need to be hooked to a computer.

I know right,,,almost seems like it is not doing it right but I have went back to a previous backup and it flashed fine!
JoeM01 said:
Same here. Flashed via CWM with no issues what so ever. Shocking how much faster backups are now!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
If you know how to use ADB you can always fastboot a recovery.img,,,,this thing is almost impossible to truly brick. IN order to get into fastboot just connect to your computer and run adb with these commands
adb reboot bootloader
once in fastboot mode write this
fastboot devices
that will tell you if your device is connected and reading in fastboot mode if it is you will see something like fastboot and some numbers next to it. If nothing you do not have the fastboot drivers installed.
then to fastboot flash a recovery.img write this
fastboot flash recovery r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever recovery.img you are using or have in your tools folder of you SDK location).
and in order to get right into CWM if you cant boot write this
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img
hope that helps
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse

camblue said:
I know right,,,almost seems like it is not doing it right but I have went back to a previous backup and it flashed fine!
Click to expand...
Click to collapse
Flashed fine here also. Works without flaw so far.

BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
Did you install the ota after you rooted and installed the recovery? I soft bricked too and I think that was the reason why. Something about the ota overwrote the recovery partition. Best thing to do is download ROM manager and click the first option to flash cwm. Then click the next button to boot into recovery. Then just flash the zip I posted to upgrade to touch.
**edit** just tried to boot into recovery from the boot loader and got stuck at the Google screen too. Holding all three buttons rebooted and started up as normal. Maybe the boot loader boot into recovery is pointing to a different partition for some reason?
Booting into recovery from ROM manager works though. That's how I've been getting in.
Sent from my Galaxy Nexus using xda app-developers app

thanks for the heads up

BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
What did you try?

Can you adb boot into recovery from the bootloader?
Oh and you can't 'adb reboot' in fastboot just hit the power button.

yes and can do this while in fastboot (bootloader mode)
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever the name of your recovery.img is)
BennyJr said:
Can you adb boot into recovery from the bootloader?
Oh and you can't 'adb reboot' in fastboot just hit the power button.
Click to expand...
Click to collapse

camblue said:
yes and can do this while in fastboot (bootloader mode)
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever the name of your recovery.img is)
Click to expand...
Click to collapse
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.

BCD90 said:
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
Click to expand...
Click to collapse
Bootloader = fastboot. Any adb commands wont work

BCD90 said:
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
Click to expand...
Click to collapse
Which is correct. You won't be able to do adb commands in the bootloader. The command he asked you to try was a fastboot command, which should work
Sent from my Galaxy Nexus using xda app-developers app

Make sure the drivers are installed had this problem with windows 7 download the naked driver pack and follow the instructions
Sent from my Nexus 7 using xda premium

Recovery no longer allows me to select files from memory (twrp)

I updated now I can't do anything. Im able to book ROM and to boot into recovery but am no longer able to select anything while in recovery.. basically if i want to changes roms or whipe data and etc.. i can't do that anymore..
Is there a way to revert back to stock? ( bootloader is unlocked before this happened and rom is rooted)
Is there a way to fix this? same thing happens when i install clockworkmod recovery..
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4

let it boot and set for 30 min then reflash twrp and it works same thing happened to me

toolhas4degrees said:
let it boot and set for 30 min then reflash twrp and it works same thing happened to me
Click to expand...
Click to collapse
Can you recommend which version of twrp to use ? Link?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 4

I"m still trying to fix this issue.. any help would be great

dilfatx said:
I"m still trying to fix this issue.. any help would be great
Click to expand...
Click to collapse
twrp 2.5 is the only one that has no issues as of now.

FIXED!
After doing some more extensive reading and trials and errors.. these two threads where helpful
[UNLOCKED BL] Method 2: Update using fastboot
Notes:
You will keep all your data
This is the best method to update your tablet if you want to keep all your data, and the safest one
Ensure you have the correct drivers for the tablet installed on your computer, or you will have a "waiting for device" error
To update using fastboot, follow this steps:
If you don't have fastboot yet, download it from here an unpack it somewhere on your computer
Extract the Asus firmware file and put the blob file inside fastboot folder
Open a command line on fastboot folder (write "cmd" on Windows search bar at the Start menu, and then
Code:
cd "FOLDER WHERE YOU EXTRACTED FASTBOOT"
, or you can just use SHIFT + RIGHT CLICK on the folder and select "Open command line window here" or something like that)
Reboot the tablet holding the volume down key until you see some icons. Use the volume down key to select the USB icon and then volume up to select it
Connect the tablet to the computer if you didn't do so
Write
Code:
fastboot -i 0x0B05 flash staging blob
, hit enter and wait until it completes
Hold the power button for 10 seconds to reboot the tablet
You are now updated to Android 4.2
Click to expand...
Click to collapse
and to install recovery I used this step from the same thread
[UNLOCKED BL]-- Installing TWRP (Recovery) --
Since this new update brings a new bootloader, older recovery versions from 4.1 won't work at all. Don't try to flash one!
This guide will give you a recovery that works just fine on the new bootloader. And yes, it can read/write to an external SD just fine. Follow this steps to install the new recovery on your device:
Connect the tablet to the computer
Reboot the tablet using the proper button on the power menu, holding Volume down until you see three icons (RCK, Android and Wipe Data)
Download this file and unpack it (it contains fastboot and a version of TWRP 2.5.0.0 that works with the new bootloader)
Open a command line on the extracted folder (you can use the instructions I wrote in Method 2 if you don't know how to do this) and type
Code:
fastboot -i 0x0b05 flash recovery twrp.blob
Wait for the script to complete. Once it is done, reboot the tablet by holding volume down and power button for 10 seconds or using
Code:
fastboot reboot
on the command line. Don't enter recovery directly!
You have now the new recovery for Android 4.2 .
Click to expand...
Click to collapse
from [GUIDE][14/09]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices and it was successful using this specific method :laugh:

dilfatx said:
After doing some more extensive reading and trials and errors.. these two threads where helpful
and to install recovery I used this step from the same thread
from [GUIDE][14/09]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices and it was successful using this specific method :laugh:
Click to expand...
Click to collapse
Thank you for this, I have had to go back to 2.4.4 because it was the only working one, going to try this when I'm home.
Got it working (updated from 2.4.4 to 2.5.0 finally made it work thanks and now my external SD can finally be used going to buy one only for backups

frankgreimes said:
Thank you for this, I have had to go back to 2.4.4 because it was the only working one, going to try this when I'm home.
Got it working (updated from 2.4.4 to 2.5.0 finally made it work thanks and now my external SD can finally be used going to buy one only for backups
Click to expand...
Click to collapse
no problem

[Q]bootloop when going to new ROM

hi,
i wanted to flash a custom rom(SOKP). so first i did a factory reset, then i tried to flash the rom but it aborted. i wiped cache and tried to boot my phone up because i wanted to install a different zip(maybe something went wrong while downloading). now my phone does not boot any more. it stays in the PA bootanimation. my pc does not recognize the phone anymore. it can only go into fastboot mode and recovery mode. another factory reset doesn't work. what can i do now?
greets, jamie

chimmychenga said:
hi,
i wanted to flash a custom rom(SOKP). so first i did a factory reset, then i tried to flash the rom but it aborted. i wiped cache and tried to boot my phone up because i wanted to install a different zip(maybe something went wrong while downloading). now my phone does not boot any more. it stays in the PA bootanimation. my pc does not recognize the phone anymore. it can only go into fastboot mode and recovery mode. another factory reset doesn't work. what can i do now?
greets, jamie
Click to expand...
Click to collapse
Download the zip again on pc and transfer it to phone using adb push command in recovery.

varuntis1993 said:
Download the zip again on pc and transfer it to phone using adb push command in recovery.
Click to expand...
Click to collapse
thanks but the prompt is saying that it's a read only file system

chimmychenga said:
thanks but the prompt is saying that it's a read only file system
Click to expand...
Click to collapse
what recovery are u using? And what rom are u pushing?
And use this command
Code:
adb push /pathonpc /sdcard

varuntis1993 said:
change its owner than on pc and what recovery are u using? And what rom are u pushing?
And use this command
Code:
adb push /pathonpc /sdcard
Click to expand...
Click to collapse
i'm using CWM and i try to install 'SOKP-RC-01-20140401-hammerhead.zip' it's a stable release of Audio god.

chimmychenga said:
i'm using CWM and i try to install 'SOKP-RC-01-20140401-hammerhead.zip' it's a stable release of Audio god.
Click to expand...
Click to collapse
I think you wrote the command wrong. Can you show a screen shot of command promt?
EDIT-also type adb root to see whether it is running as root or not

now i got a prompt with the copy speed but nothing is copied:S

chimmychenga said:
now i got a prompt with the copy speed but nothing is copied:S
Click to expand...
Click to collapse
did it say successful? It would be better if u share a screenshot
Check in your sd card

tthis is what i get

chimmychenga said:
tthis is what i get
Click to expand...
Click to collapse
It has successfully copied....reboot ur recovery and go to download folder and see if the file exists or not.
EDIT- I just checked ur screenshot again...it shows around 162 MB file but the file size should be around 300 MB
Download it again or flash the stock files to go back to stock

varuntis1993 said:
It has successfully copied....reboot ur recovery and go to download folder and see if the file exists or not.
EDIT- I just checked ur screenshot again...it shows around 162 MB file but the file size should be around 300 MB
Download it again or flash the stock files to go back to stock
Click to expand...
Click to collapse
i finally got it installed. i made a stupid mistake i unmounted /system and usb storage. i did a adb sideload and it succesfully installed. thanks for the replies BTW:laugh:

Problem flashing recovery

Hoping someone can help. I've unlocked bootloader easily, however, im having a problem flashing recovery. Each time i get failed remote error image is not a boot image....it starts to write and then fails. ive tried with cwm and twrp. i am placing the file in my adb folder, and renaming it to recovery.img so really i dont know whats wrong. never had this issue ever before. i checked to see if it was flashed, and nothing was there, showing a dead robot with an exclamation. cannot figure it out!

it goes in the same folder on your computer as where fastboot is located. then fastboot flash recovery recovery.img

I have fastboot, adb and recovery image in the same folder on my desktop.

mgf8384 said:
I have fastboot, adb and recovery image in the same folder on my desktop.
Click to expand...
Click to collapse
the android laying on its back is the stock recovery btw. did you rename the recovery properly? is it still an img file?

mgf8384 said:
Each time i get failed remote error image is not a boot image....
Click to expand...
Click to collapse
Its not a boot image, Its a recovery image. You sure your typing the correct command?
Esit: Just done some googling and someone had the same problem. Was due to a bad download.
Edit 2: ah just read again and you said you tried 2 types of recovery. Scrap my 1st edit then?
Sent from my Nexus 5 using XDA mobile app

mgf8384 said:
Hoping someone can help. I've unlocked bootloader easily, however, im having a problem flashing recovery. Each time i get failed remote error image is not a boot image....it starts to write and then fails. ive tried with cwm and twrp. i am placing the file in my adb folder, and renaming it to recovery.img so really i dont know whats wrong. never had this issue ever before. i checked to see if it was flashed, and nothing was there, showing a dead robot with an exclamation. cannot figure it out!
Click to expand...
Click to collapse
You'll just be doing wrong and no, nothing needs to be in the same folder of you installed it properly. Click the link in my signature to the sticky thread and read my adb and fastboot thread.
Also ensure "hide known file extensions" is turned off in windows.
If you need more help, you should post screenshots of your cmd window.
Sent from my Nexus 5 using Tapatalk

Thank you all. Setting somewhere in my PC I think. When .img.img was typed it worked. ( i tried fastboot flash recovery rec and then hit tab) Checked properties in the recovery zip and it's named just recovery.img so don't understand why it had to be typed twice? If anyone knows please tell me so I can correct it.

mgf8384 said:
Thank you all. Setting somewhere in my PC I think. When .img.img was typed it worked. ( i tried fastboot flash recovery rec and then hit tab) Checked properties in the recovery zip and it's named just recovery.img so don't understand why it had to be typed twice? If anyone knows please tell me so I can correct it.
Click to expand...
Click to collapse
the way it was renamed.

There's no need to rename it....for future flashes.

KJ said:
There's no need to rename it....for future flashes.
Click to expand...
Click to collapse
i rename it to simple 3-4 letter words, for ease of typing

simms22 said:
i rename it to simple 3-4 letter words, for ease of typing
Click to expand...
Click to collapse
Just brought it up, cause in this case...he wouldn't have had an issue if he left it.
But yeah, I do that too. Lol

mgf8384 said:
Thank you all. Setting somewhere in my PC I think. When .img.img was typed it worked. ( i tried fastboot flash recovery rec and then hit tab) Checked properties in the recovery zip and it's named just recovery.img so don't understand why it had to be typed twice? If anyone knows please tell me so I can correct it.
Click to expand...
Click to collapse
Because you had "hide file extensions" on in windows like I said.
File was called whatever.img but you can only was whatever because. .img is hidden. So when you rename it, it only let's you rename whatever (leaving .img hidden and unchanged) so you rename what's visible to recovery.img and results are obvious
(whatever).img > (recovery.img).img
So the quick lesson - turn off "hide known file extensions" in windows. Not just for this reason but for your own security. .exe files with word doc icons etc
Sent from my Nexus 5 using Tapatalk
---------- Post added at 08:42 AM ---------- Previous post was at 08:41 AM ----------
simms22 said:
i rename it to simple 3-4 letter words, for ease of typing
Click to expand...
Click to collapse
Or type first letter or two then press tab
Sent from my Nexus 5 using Tapatalk

Hello everyone.
I had to move back to the factory image because of a bad flash. After resetting, i try to install TWRP or CWM using fastboot. The recovery works the first time its installed, but goes away when I reboot my phone. By goes away i mean I see googles recovery (dead robot) once I reboot the phone and then boot into recovery.
I tried to flash a ROM while TWRP works but once I do, I cant see any of my files on the SD card. This means I cannot flash anything even if I booted in TWRP and this brings me back around to flashing the factory image.
Any help is much appreciated.

siddjazz said:
Hello everyone.
I had to move back to the factory image because of a bad flash. After resetting, i try to install TWRP or CWM using fastboot. The recovery works the first time its installed, but goes away when I reboot my phone. By goes away i mean I see googles recovery (dead robot) once I reboot the phone and then boot into recovery.
I tried to flash a ROM while TWRP works but once I do, I cant see any of my files on the SD card. This means I cannot flash anything even if I booted in TWRP and this brings me back around to flashing the factory image.
Any help is much appreciated.
Click to expand...
Click to collapse
Go to general and read the sticky thread about 5.0 roms and recovery