Database Users

Run nandroid-mobile.sh via adb.

Hi
I have problem when i does nandroid i get the massege
Run nandroid-mobile.sh via adb.
And i try to do it wheb i connect to the pc and when i'm not
I have nexus one cm6
Thenks

Unmount your sdcard.
from recovery mount then unmount

How i'm doing mount from recovery?and unmount???

The option mount sdcard from recovery.

yet didn't find it

Its very easy to solve this. Just charge your phone for an hour or so. Then boot to recovery, run nandroid . Everything will be fine.
This prob arises cos ur low on battery.
gud luk
Sent from my Nexus One using XDA App

Yeah. You're battery is too low. It won't let you run for safety reasons.

I've had this error (or a similar one) when I didn't have enough space on the SD card...

i have enough place and enogh battery but still it didn't do it

This fixed this problem for me:
- Enter Recovery
- Mount USB
- Open up a cmd window in your tools/adb folder
- Type: adb remount
- Then: adb shell mkdir /system/sd
It supposedly occurs because there is a missing SD folder in the System folder.

how to do mount usb at the recovery?
i connected my nexus and do the cmd and type the commend and it give me these
remount failed:invalid argyment

ok here is the thing that i did..and yet you can see the "not fouand "at the end..
also i tried after these to do regular from the phone and yet i get the same massege at the start
http://yfrog.com/1g42509115j
you can look here

if you're using amon-RA recovery press USB MS toggle to mount your sd card while it's connected to your computer.

and what after?i did ot and than tried to do again nandroid and it the same

did you rename the nandroid file/folder? make sure there are no spaces.

I7210I said:
Hi
I have problem when i does nandroid i get the massege
Run nandroid-mobile.sh via adb.
And i try to do it wheb i connect to the pc and when i'm not
I have nexus one cm6
Thenks
Click to expand...
Click to collapse
britoso said:
did you rename the nandroid file/folder? make sure there are no spaces.
Click to expand...
Click to collapse
Britoso got the answer
I had this problem for the first time EVER a few days ago.
I thought it was because I upgraded from amon_ra 1.7, to 1.8.
THE PROBLEM IS DUE TO THE FILENAME, make sure to remove spaces, or replace them with dashes or underscores.
Access the nandroid folder on your sdcard in any way possible: via usb cable, or stick it in a card reader and do it that way. there are many ways to rename the nandroid folder.

ok i removed the folder NANDROID from my sdcard and yet it doesn't help it's create a new folder but the massege s come back and the folder is full so what is going on there?

The suggestion was to RENAME not REMOVE - though I don't really think it was the right suggestion anyway (your file naming convention looks good, from the image you posted).
I recommend you pay close attention to your typing though, because there are a lot of input errors in the image you posted, and that's a sure way to screw things up...
Adb is telling you that you don't have an md5 file for that nandroid, so I'd try listing the folder contents to confirm (you may have deleted it). I would also try the other backups, and hope one works...
Which recovery do you have? I think Amon Ra's will let you run nandroid from the phone, which might be a better/safer option?
Sent from my Nexus One using XDA App

first of all i have recovery-RA-nexus-v1.7.0.1 (amon)
and i tried to do the nandroid from the recovery...and at the start i get the message Run nandroid-mobile.sh via adb.
the funny is that i did upgrade to my frend phone and i get the same message to (from 5.0.7 to cm6)

ok ...good news..
i changed the recovery to clockware and now i did backup..
so the setioation is that i have a file called NANDROID and one more fie called clockware backup so i can be sure that the backup s good now?and i can erase the file nandroid?

Need recovery! Please help!

Hello All!
After power ON Vibrant have a message:
Android system recovery <2e>
Samsung Recovery Utils
- for BML -
reboot system now
reinstall pakages
delete all user data
delete cache data
update media, please wait
E:Can't mount /dev/block/mmcblk0p1 (or /dev/bloc
k/mmcblk0)
(Invalid argument)
E:copy_dbdata_media:Can't mount SDCARD:
copy default media content failed.
In download mode cannot enter. Try any combinations.
Odin see phone, but cannot upload nothing after START
Date of manufacture: 10/08
Via ADB reboot download only reboot, cannot entering download mode.
Please help me. Thank you.

you are in recovery, thing is update.zip isnt clockwork.

98classic said:
you are in recovery, thing is update.zip isnt clockwork.
Click to expand...
Click to collapse
And what to do? Have a idea?

pm me your email, i'll make it super easy for you.
edit nvm, i attached it. download, extract, make sure phone is good through usb and on, run the .bat it'll push cw to your phone and then just run "reinstall packages"
let me know if it worked.

98classic said:
pm me your email, i'll make it super easy for you.
edit nvm, i attached it. download, extract, make sure phone is good through usb and on, run the .bat it'll push cw to your phone and then just run "reinstall packages"
let me know if it worked.
Click to expand...
Click to collapse
D:\push_cw>adb push update.zip /sdcard/update.zip
* daemon not running. starting it now *
* daemon started successfully *
failed to copy 'update.zip' to '/sdcard/update.zip': Permission denied

hmmm, you arent mounting storage to pc right?
edit: works fine on my phone, wonder whats up with yours.
edit2: you can download a rom, rename it update.zip and drop it in that folder and it will push it to phone. basically it'll push anything named update.zip to your main sd

98classic said:
hmmm, you arent mounting storage to pc right?
edit: works fine on my phone, wonder whats up with yours.
edit2: you can download a rom, rename it update.zip and drop it in that folder and it will push it to phone. basically it'll push anything named update.zip to your main sd
Click to expand...
Click to collapse
I think that not have ROOT access to phone. Any idea?

maybe? root it http://forum.xda-developers.com/showthread.php?t=739300

I think this is solution can make if phone full worked. Bot now i have brick.

if it turns on it aint bricked

loading from SD-CARD
Have a solutions, that download system from SD-Card (memory card in a slot)?
for example:Format external Memory Card in EXT2, upload image of OS on SDcard, after loading phone from memory card and installing.
Really need recovery my bricked.
Thank you.

[HELP] Nook boots directly to ClockWorkMod recovery

I just flashed the CWM to my nook, but now when I try to turn it on, it runs directly into CWM recovery menu. I tried flashing to NC_1.3.zip, even tried dualboot, it does not help.

morph3us5 said:
I just flashed the CWM to my nook, but now when I try to turn it on, it runs directly into CWM recovery menu. I tried flashing to NC_1.3.zip, even tried dualboot, it does not help.
Click to expand...
Click to collapse
What ROM did you flash? CM7? Telll us specifically what you did.

Did something rather stupid, I did dd if=%path to cyanogen mod% of=/dev/block/vold/179:0, believing that it should write to my uSD card, but it written the internal memory instead. Fixed this by booting into Nookie-Froyo, fdisked the partition, and boot to clockworkmod again to restore the whole thing. Now I lack the ROM partition in /dev/block/mmcblk0p2. Is there a guide somewhere or tool to rebuild that partition?

Hey this is happening to me to I can't get in to anything but recovery.
morph3us5 said:
I just flashed the CWM to my nook, but now when I try to turn it on, it runs directly into CWM recovery menu. I tried flashing to NC_1.3.zip, even tried dualboot, it does not help.
Click to expand...
Click to collapse
Sent from my PG06100 using Tapatalk

After few days of research, I found the solution!!!! I am back in CM7!!!!!
morph3us5 said:
Did something rather stupid, I did dd if=%path to cyanogen mod% of=/dev/block/vold/179:0, believing that it should write to my uSD card, but it written the internal memory instead. Fixed this by booting into Nookie-Froyo, fdisked the partition, and boot to clockworkmod again to restore the whole thing. Now I lack the ROM partition in /dev/block/mmcblk0p2. Is there a guide somewhere or tool to rebuild that partition?
Click to expand...
Click to collapse
You need to re create DeviceID, MACAddress and SerialNumber under devconf/ in mmcblk0p2 (FAT).
DeviceID (I used "BNRV200", not sure if it is correct).
MACAddress (I used "11:22:33:44:55:66", not sure if it is correct).
SerialNumber (It is under the SD card door)

...and how can I do that? Which program can I use? I think this'll save me, considering my Nook is unregisterable for some reason...

Try with ADB + CWR uSD card
Boot with CWR card with NC connected to USB.
do adb shell:
# mkdir /rom
# mount /dev/block/mmcblk0p2 /rom
# ls /rom/devconf
# mkdir /bkp
# mount /dev/block/mmcblk0p3 /bkp
# ls /bkp
and pos what you see.
after that:
# umount /rom /bkp
Turn it off.

Take out your SD card then try to boot, sounds like cwm is running off you SD
Sent from my HTC_A510c using XDA App

bigsheep123 said:
Try with ADB + CWR uSD card
Boot with CWR card with NC connected to USB.
do adb shell:
# mkdir /rom
# mount /dev/block/mmcblk0p2 /rom
# ls /rom/devconf
# mkdir /bkp
# mount /dev/block/mmcblk0p3 /bkp
# ls /bkp
and pos what you see.
after that:
# umount /rom /bkp
Turn it off.
Click to expand...
Click to collapse
I think recreating the information within the Nook Color's memory would solve all my problems, since without registration, the Nook stock refuses to update. I tried updating through regular means, but the Stock refuses to take any update or any CWM-flashed ROM.
Android311 said:
Take out your SD card then try to boot, sounds like cwm is running off you SD
Sent from my HTC_A510c using XDA App
Click to expand...
Click to collapse
I do, and then the screen just goes black after the initial boot up.

neoage said:
I think recreating the information within the Nook Color's memory would solve all my problems, since without registration, the Nook stock refuses to update. I tried updating through regular means, but the Stock refuses to take any update or any CWM-flashed ROM.
I do, and then the screen just goes black after the initial boot up.
Click to expand...
Click to collapse
These steps are not flashing with CWM, they are just entering to clockwork recovery system wich allow you access to NC's internal memory.
You need to create three files:
/rom/devconf/DeviceID
/rom/devconf/MACAddress
/rom/devconf/SerialNumber
and fill them with your NC's info...
I dont know exactly wich data must be in those files...
EDIT:
With these files I can run CM7 but not sure for NC stock...

I'll try anything, even if it's random gibberish. I need my Nook back.

neoage said:
I'll try anything, even if it's random gibberish. I need my Nook back.
Click to expand...
Click to collapse
I found a complete list of files you need (maybe, maybe not)...
Archive: rombackup.zip
Length Date Time Name
--------- ---------- ----- ----
rom/devconf/BootCnt
rom/devconf/DeviceID
rom/devconf/MainboardSN
rom/devconf/WiFiBackupCalibration
rom/devconf/MACAddress
rom/devconf/ProductID
rom/devconf/Backlight
rom/devconf/EventType
rom/devconf/DeviceAttribute
rom/devconf/Platform
rom/devconf/DateManufactured
rom/devconf/PublicKey
rom/devconf/HashOfPrivateKey
rom/devconf/ean
rom/devconf/ModelNumber
rom/devconf/SerialNumber
rom/devconf/BootCount
--------- -------
957 17 files
I only want to know their format...

The question is, how can I access these files to edit them? What program can I use to see them? It's possible that if I can see them, I can extract them, edit them, then inject them into the Nook. There has to be a way around the missing addresses and numbers...

neoage said:
The question is, how can I access these files to edit them? What program can I use to see them? It's possible that if I can see them, I can extract them, edit them, then inject them into the Nook. There has to be a way around the missing addresses and numbers...
Click to expand...
Click to collapse
I need that file too.
I just want it as a sample because these files are different for each nook.
How did you lost those files?
If you didnt repartitioned your nook you can look here.
You can access them with CWR + ADB.

I keep giving this advice, I feel like a broken record. Oh well, at least it can be helpful...
Do a hard reboot and take your nook directly back to stocking condition. Hold down power,n, and the volume keys all at the same time for ~10 seconds until the nook turns off. It will flash, and reboot, when it begins to load (if you still have the cyanogen screen, as soon as it appears) hold down all the same buttons again until it goes off again. Do this 8 times total. On the final reboot, the nook will load into froyo, go through the normal B&N registration process and then in settings of the nook OS, erase and dereguster device to complete the wipe. That will send it back to stock.
I have seen this fix anything from a black screen to a completely erased system directory. Give it a shot.

mateorod said:
I keep giving this advice, I feel like a broken record. Oh well, at least it can be helpful...
Do a hard reboot and take your nook directly back to stocking condition. Hold down power,n, and the volume keys all at the same time for ~10 seconds until the nook turns off. It will flash, and reboot, when it begins to load (if you still have the cyanogen screen, as soon as it appears) hold down all the same buttons again until it goes off again. Do this 8 times total. On the final reboot, the nook will load into froyo, go through the normal B&N registration process and then in settings of the nook OS, erase and dereguster device to complete the wipe. That will send it back to stock.
I have seen this fix anything from a black screen to a completely erased system directory. Give it a shot.
Click to expand...
Click to collapse
Thanks. But this method only work if you have third partition (factory) intact.
And all I need is a file located at that partition wich I dont have :S

on my first attempt to put cm7.1 on my emmc using cwm I had the same or a very similar thing happen to me.
I somehow ended up with a bad boot partition. I followed a thread on here that had to do with "reformat and a repartition", (cant find it right now) but downloaded and installed these zips through a cwm card then installed an update for b&n 1.4 zip (I was running 1.3 ) but it worked allowing me to go to stock.
Then I tried it again only this time when I first booted to cwm on the main menu I hit wipe data/factory reset then installed zips and all is well.
*forum.xda-developers.com/showpost.php?p=14101197&postcount=1

I Think the file he's talking about is "E_Recovery". When I tried to register the Nook, I got a message that said that this file was missing...

For All sdcard issues

09/01/2012:
this tutorial may work for those who are having encryption issues on ics or jb roms (the error is related to mmcblk0p2(data))
well, after some months of work, here´s an tutorial about how to fix the mostly common sdcard issues.
1º Of all :***Be sure of what you´re doing,or else you can corrupt the partition table of you sdcard/brick your phone,and I´ll not be responsible of it***
2º-Do Not send me PMs, post here so everyone that have the same problem can now how to fix it.
3º-If you are an starter, you can post here your questions,but be sure that you haven´t found answers on Google or other threads.
and 4º-Read ALL topic before start and try one solution than the other,they´re in order of difficulty and risk of get an "permanent" brick.
0 - Always backup your EFS folder, maybe its not related to this thread but it´s also very important to remember.
I -If you have a folder called "voodoo" in your sdcard, you may have voodoo enabled on your ROM, so be sure of disabling it before trying a new rom or a stock rom.
if you´re on another rom already and having problems in mounting partitions, try to flash you last rom or a kernel that supports voodoo and it´s compatible with your new rom.
II-If you´re getting problems in mounting DBDATA,Download a full rom that contains DBDATA to flash with odin(or only flash dbdata,but you´ll have to do a full wipe later). To see if it haves dbdata.rfs by opening your .tar file in 7zip or others.
III-If you´re getting Can´t mount data (dev/block/mmcblkl0p2) File exists, try to flash an kernel with voodoo suport,if it still the same, format data in the menu of your recovery.
IV-If you´re getting can´t mount sdcard (/dev/block/mmcblk0p1)File exists, try to access it via ADB and send pull file command to recover your files(must have root),if you could do that, so try to format it via recovery.If not work,Download gparted, burn it on cd (it´s an CD with a tool of linux) and go to ADB shell to run this command:
su
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
now
reboot your PC in gparted and format mmcblk0p1(it´s the first partition) in FAT32.
Done
V-If you´re getting cant mount sdcard (/dev/block/mmcblk0p1) with (invalid argument) You can try the fix IV and see if it works,if not, proceed to VI.
VI-If you´re getting cant mount data(dev/block/mmcblk0p2) or can´t mount sdcard (/dev/block/mmcblk0p1) with (invalid argument) or (no such file or directory) you may have to do this:
***search on google for 'fdisk' commands first***
You MUST*¹ remake your partition table manually,so the phone have the /data partition back to boot.
*¹
In some cases you can use gparted to do this, without doing it manually,
you shoud only mount mmcblk0 before.
you can run this command line on adb shell to mount it:
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
You Will have to format it and it MUST have the partitions as said below.
YOU SDCARD MUST HAVE THE FOLLOWING PARTITION TO BOOT ON AND RECOGNIZE INTERNAL SDCARD:
/dev/block/mmcblk0p1
AND
/dev/block/mmcblk0p2
Start:
Open ADB,comnect your phone and proceed.
run adb shell
su
fdisk /dev/block/mmcblk0
p (you should see your partition table,POST HERE BEFORE CONTINUING)
YOU ARE NOW ABOUT TO REMAKE YOUR PARTITIONS:
partition 1 will correspond to mmcblk0p1(SDcard) and partition 2 will correspond to mmcblk0p2 (DATA)
**DO ONLY AS I SAY HERE, UNLESS YOU MAY GOT I/O ERROR ON YOUR SDCARD AND ITS ALL OVER. I say because it happened to me and i had to dissolder the internal sdcard an use only the external.**
**********IF YOU DONT HAVE ANY IDEA OF LINUX COMANDS: DO NOT PROCEED !!!!!!!!!*************
tap on adb:
n (will create a new partition)
1 (partition number)
press enter on keyboard so it selects the first block
get a calculator and estimate the size of the partition 1.IT MUST HAVE around 2GB left.
write the block number you got in calculator(BE SURE OF WHAT YOU TAPE HERE)
t
b (partition 1 is done and formatted as fat 32)
Now again:
n
2
enter on keyboard
enter again so it select the last block
(DO NOT TYPE COMMAND "T" FOR PARTITION 2, IT BY DEFAULT SET TO LINUX EXT FORMAT)
p (you will see you new partition table)
****IT MUST HAVE 2 partitions, partition 1 is in fat 32 format and partition 2 is in linux format(AND MUST HAVE AROUND 2GB)****
w (IT WILL WRITE YOU NEW PARTITION TABLE ON YOU SDCARD,SO BE SURE IT's ALL CORRECT)
Done,
now tap:
q
fdisk /dev/block/mmcblk0
p (you should see your new partition table, if ok reboot your phone, flash an stock rom for vibrant (I sugest an T959UVJFD ROM only to correctly format your partitions),root it,backup it,and enjoy,You can put a custom rom if you want so.)
If You have an error That does not appear here and you think it may me related to you sdcard just ask. In one or two days I or others developers may post here a possible solution.
Thanks For Google and some XDA users who indirectly helped me doing this.
You can try Paragon Hard Disk Manager in place of gparted
but remember: mmcblk0p1 is FAT32 and mmcblk0p2 in EXT2 (in truth it´s not EXT2, its in rfs, but the stock rom T959UVJFD is the only that I have absolute sure that will do the conversion).
Sorry for my bad english, it´s not my native language.

Great post doiiido!
Hay doiiido, you have been thanked and this post has been added to the [REF][KERNEL] ✰ The Official Vibrant Kernel ßible Thread ✰ → 07/05/12.
Great post!

News
Original pos by: ferhanmm
link to it:
http://forum.xda-developers.com/showthread.php?t=1665123
[FIX] Data wipe error or Can't mount /dev/block/mmcblk0p1
Data wipe error, Can't mount /dev/block/mmcblk0p1, or Vibrant screen boot loop even after flashing stock odin JFD phone will not boot. Phone will only boot Eugenes JK2 but internal and external storage will still list as corrupted and Lists 0.00 MB in storage.
Internal storage has been destroyed, I’ve been able to fix a phone using this technique to be mostly working. The external SD card will always have to be in the phone for this to work.
1. Partitioning the MicroSD Card
Get an 8gb(or larger) micro sd card. Class 10 would be better here. Put it into a Card Reader, then run Gparted.
Gparted (usb method is easiest) - http://gparted.sourceforge.net/liveusb.php
Using Gparted, delete everything else and create 2 partitions and :
6000mb FAT32 as PRIMARY
1607mb(remainder) Reiser as PRIMARY
2. Flash to Stock
Open up Odin flash stock JFD with pit file and repartition checked.
After phone boots completely, power off.
3. Flashing CM9
Take MicroSD out of phone an put it in pc, then copy update.zip, GAPPS, Cyanogenmod Rom all to the FAT32 partition that we created earlier. In Windows it should show up where all of your drives are listed in.
update.zip (https://www.dropbox.com/s/ju5eg5ernxcaqpt/update.zip),
GAPPS (http://www.goo-inside.me/gapps/gapps...317-signed.zip)
CyanogenMod Rom Zip(http://download.cyanogenmod.com/get/...mtd-signed.zip)
Enter recovery mode with volume buttons and power.
Reinstall packages twice.
Install zip from sd card select update-cm-9-20120520-nightly-vibrantmtd-signed.zip phone will boot loop on vibrant screen so take out the battery then enter recovery a second time installing the cm9 update again.
Then flash Gapps zip the same way.
When phone boots up camera, and gallery will not work until the next step.
4. Edit Vold.Stab file
Downlad ES File Explorer from play store.
Hit Menu button, settings, Check box for Root Explorer, Check box for mount file system, check box for Up to Root
Press Up once, you should now be at "/"
Open system directory, open etc directory, scroll to bottom and select Vol.fstab, select Text, Select ES Note Editor, update text to the following:
#internal sdcard dev_mount emmc /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
#external sdcard dev_mount sdcard /mnt/emmc auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
After edits, click back and click yes to save changes. Exit out of es file explorer and restart phone. Post results:
Should work with any version of CM9, newer nightlies would obviously be preferred. Will make more detailed guide soon.
Credit to these guys for providing the solution -
http://www.youtube.com/watch?v=zdMhYYdMB08
http://forum.xda-developers.com/show....php?t=1447303
Samsung Vibrant

News
Original post by:
draikz
Link to original post:
http://forum.xda-developers.com/showthread.php?t=848737
** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly **
Fixing so-called "Bricks"/Odin Errors
This guide is open to contribution/editing/correcting
I DO REALIZE THAT MOST OF THESE LINKS ARE BROKEN, PLEASE SCAN THE THREAD TO FIND UPDATED LINK. I'M NOT VERY ACTIVE ANYMORE, SORRY!
-----------------------------------------------------------------------------------------------------
BOOT CYCLE
This is where you get the annoying Samsung Screen/Galaxy S screen.
DOWNLOAD REQUIRED (CREDITS TO JUSTANOTHERCROWD):
Quote:
Originally Posted by justanothercrowd
JFD ODIN Images from Samsung (PDA)
www.justanotherdev.slackdev.com/T959UVJFD.tar
MD5:632730f6b637f53e5b10e5cbc8b966a7
512 PIT File (PIT Extract first!)
www.justanotherdev.slackdev.com/s1_odin_20100512.rar
MD5:b5628c8e183fdd8f4c703321ca40e33a
ODIN
www.justanotherdev.slackdev.com/Odin3.rar
ALL 3 Files plues the root update.zip
http://tinyurl.com/2bc5b6r
thx to KopyKatKiller
1. Get into Download Mode (WITH THE PHONE PLUGGED IN) by following the steps below
*Turn off the phone until you get to the charging battery screen (keep in mind, your phone is currently PLUGGED IN)
*Press volume up and down, and power all at once.
*As soon as the screen turns black, release your power button.
2. Unplug phone from USB
3. Open Odin (in Administrator if you're running W7 or Vista), try one of the ones I attached to this post, at least one of them is bound to work, some don't work for me, but works for others, some doesn't work for others, but works for me, whatever floats your boat
4. Load in the files into Odin that you have downloaded from above Just load in the files corresponding to the text field.
DO NOT CHECK REPARTITION.
5. Plug in your phone with the DL mode
6. Click start and wait for the magic
-----------------------------------------------------------------------------------------------------
NO-BOOT PHONES
This is where your phone does NOT turn on, no combo of buttons works and power button does nothing.
DO THIS ONLY WHEN YOU PLUG IN YOUR PHONE AND NOTHING SHOWS UP ON THE SCREEN!!! If else, follow the steps from above.
This method is basically same as above, EXCEPT the way you get into Download Mode as your phone is HARD BROKEN.
1. Download all the files required in the "BOOT CYCLE" section of this post.
2. Remove everything from your phone (SD card, sim, battery).
3. Plug your phone into your computer WITHOUT the battery, as you have already taken it out in the last step.
4. Press and HOLD vol. up and vol. down.
5. As you are HOLDING these buttons, reattach your battery.
6. You should be in Download Mode.
7. Unplug phone from USB
8. Follow steps 4-8 from the "BOOT CYCLE" section.
Troubleshooting:
-Odin stuck at some random process?
*Switch to another odin
*Make sure you did NOT check repartition, if you did, just repeat all the steps over again, except for the downloading parts, obviously.
-Phone not responsive?
*Try "NO-BOOT PHONES"section of this guide
-Phone stuck at Galaxy S logo screen?
*Put it in to DL mode, and run Odin again, it's just a bad install.
-All three ODIN is nonfunctional, stuck or giving "FAILED" errors?
*DO NOT CLOSE ODIN ONCE IT HAS FAILED!
*Unplug your phone
*Replug in your phone, get it into DL mode
* Unplug once it is in DL mode
*Replug and ODIN should recognize your phone
*Leave all the settings the same, then click "Start" again.
-Cannot get into download mode using the method I listed? Use the method(s) below:
Soldering Method
More methods coming soon
-----------------------------------------------------------------------------------------------------
I know how much of a pain posting in the Q/A section can be and the wait time is pretty bad, so if you need help regarding UNBRICKING and ONLY UNBRICKING feel free to post in here.
Hope you enjoy, this is my first guide, please don't flame. Any comments or suggestion is suggest, or if you have your own method I'll also post it
POST YOUR RESULTS!
-Steven
The only forums this guide should be posted on is XDA, DZ, and PHANDROID under the username DRAIKZ and EXPLOSIVE. If it helped you, feel free to donate a coke or two!

Flashing Now Fails

I've been flashing N7 with no issues as recently as over the weekend. Today I tried to flash a new ROM and it failed. Tried a second, different ROM, same result. Do not know what I did. Any thoughts?

Error log would help greatly.

How do I get/generate the log? Haven't had to do it before.
Thanks,
Paul

The logs= errors displayed on the screen provided by the interface you use to flash the rom (recovery, computer...)

Does this help any?
TWRP V2.4.4.0
Updating partition details
E: Unable to open zip file
Error flashing zop
Updating partition details...

do I need to create a partition? Never get more details despite the tease.
Thanks,

First -
Try and download a different (NEWER) TWRP. Re-flash TWRP. Try again
or
Have you tried completely wiping the device? And pushing a ROM from ADB or using a USB OTG and Memory stick?
I had issues with my nexus becoming VERY unstable. Leading to issues.
I completely, and I mean completely, wiped. To the point that all that device basically had was a recovery, and a bootloader.
I proceeded to flash again, BOOM all fixed up.

Is there a new TWRP?
I did a factory restore after wiping everything thing, if that is what you mean?
It was working as expected last week, don't know what I did to screw it up

Boot recovery try the operation, choose advanced then copy log to sdcard. The paste the log results.
sent via electromagnetic radiation.

ibsk8 said:
Boot recovery try the operation, choose advanced then copy log to sdcard. The paste the log results.
sent via electromagnetic radiation.
Click to expand...
Click to collapse
Did this, and it said it copied but I am unable to locate it. It says 0\media\data But that folder structure doesn't exist, at least according to file expert

Will a complete wipe/restore create a partition?

pmgreen said:
Will a complete wipe/restore create a partition?
Click to expand...
Click to collapse
None of the instructions currently found in this forum alters the partitioning of the N7. Not fastboot & not the custom recovery, either.
You are chasing a red herring I think. That message you see is about the recovery performing a scan to check to see if there is a change in file systems (or partitioning of external devices) ... which might have occurred in preceding (custom recovery) operations, but didn't in this particular case.
pmgreen said:
Does this help any?
TWRP V2.4.4.0
Updating partition details
E: Unable to open zip file
Error flashing zop
Updating partition details...
Click to expand...
Click to collapse
Focus your efforts here; it certainly looks like a first-order problem.

bftb0 said:
None of the instructions currently found in this forum alters the partitioning of the N7. Not fastboot & not the custom recovery, either.
You are chasing a red herring I think. That message you see is about the recovery performing a scan to check to see if there is a change in file systems (or partitioning of external devices) ... which might have occurred in preceding (custom recovery) operations, but didn't in this particular case.
Focus your efforts here; it certainly looks like a first-order problem.
Click to expand...
Click to collapse
Think reinstalling TWRP would help? It was working fine so I'm a bit stumped what changed and why

pmgreen said:
Think reinstalling TWRP would help? It was working fine so I'm a bit stumped what changed and why
Click to expand...
Click to collapse
You can also soft-boot a recovery without actually flashing it, e.g.
Code:
fastboot boot custom-recovery.img
I suppose you could then poke around and see if it is having troubles mounting any of the normal partitions (/data, /system, or /cache). Look in the kernel boot log of the recovery (cat /proc/kmsg or "dmesg") to see if anything looks strange, etc.
There have been a couple of reports from folks who developed problems that looked like eMMC flash media errors - loss of partitions, failure to mount /data, et cetera. At the moment though, your symptoms are very generic and non-specific, as in "it doesn't boot".
I suppose you saw no errors at all reported on the screen during that stock-install-via-fastboot procedure?

bftb0 said:
You can also soft-boot a recovery without actually flashing it, e.g.
Code:
fastboot boot custom-recovery.img
I suppose you could then poke around and see if it is having troubles mounting any of the normal partitions (/data, /system, or /cache). Look in the kernel boot log of the recovery (cat /proc/kmsg or "dmesg") to see if anything looks strange, etc.
There have been a couple of reports from folks who developed problems that looked like eMMC flash media errors - loss of partitions, failure to mount /data, et cetera. At the moment though, your symptoms are very generic and non-specific, as in "it doesn't boot".
I suppose you saw no errors at all reported on the screen during that stock-install-via-fastboot procedure?
Click to expand...
Click to collapse
The only error is that it can't open the zip. I've tried downgraded TWRP, then upgrading back. Tried flashing the existing rom.
Nothing has worked. The N7 is functional, just will not allow me to flash

pmgreen said:
The only error is that it can't open the zip. I've tried downgraded TWRP, then upgrading back. Tried flashing the existing rom.
Nothing has worked. The N7 is functional, just will not allow me to flash
Click to expand...
Click to collapse
Well, if the source material can't be opened, then there is nothing to be flashed.
So maybe it is better to call this a "can't open files" problem instead of a "can't flash" problem.
Are there any special characters in the file name ... or spaces? If so, try renaming the file so the name only contains [a-z], [A-Z], [0-9] plus dash, underscore, and dot.
The other thing that can happen is if you drop a file in /data/media/0 as the root user, it will show up under /sdcard, but can't be read by non-privileged users via the /sdcard/ path. I'm not sure what the exact details are here - much less why this would effect the recovery (as you would expect everything to be running as root there) - but you can detect this problem by using a terminal emulator, and looking for differences in ownership or file permission:
Code:
$ su
# cd /data/media/0
# ls -ld *
use chown and chmod as appropriate to fix files as needed

bftb0 said:
Well, if the source material can't be opened, then there is nothing to be flashed.
So maybe it is better to call this a "can't open files" problem instead of a "can't flash" problem.
Are there any special characters in the file name ... or spaces? If so, try renaming the file so the name only contains [a-z], [A-Z], [0-9] plus dash, underscore, and dot.
The other thing that can happen is if you drop a file in /data/media/0 as the root user, it will show up under /sdcard, but can't be read by non-privileged users via the /sdcard/ path. I'm not sure what the exact details are here - much less why this would effect the recovery (as you would expect everything to be running as root there) - but you can detect this problem by using a terminal emulator, and looking for differences in ownership or file permission:
Code:
$ such
# cd /data/media/0
# ls -ld *
use chown and chmod as appropriate to fix files as needed
Click to expand...
Click to collapse
Thanks bftb, you are correct it's a can't open zip. No error than fail and it can't open the zip. It says updating partition but nothing changes
The file names are from the developers, once of which I recently successfully flashed. Tried coping the log to the SD card, but unable to find /data/media/0. Do I need to recreate a partition?

(FYI there was an auto-correct typo in my prior post - "su" not "such". Derp)
pmgreen said:
Do I need to recreate a partition?
Click to expand...
Click to collapse
No. (There is no way to do that with the tools we have anyway)
Unless what you mean by "recreate" is rebuild/reinitialize a filesystem in a partition - that's a possibility.
You need to try and figure out why you can't read files.
As a workaround, you can put files on a USB key (FAT formatted, not NTFS) and using TWRP access them by putting the USB key on the other end of a OTG cable.
Your posts are a bit vague - I can't even tell if you have tried other ROM files, whether you checked them to see if they are the correct size/checksum, etc.

pmgreen said:
Tried coping the log to the SD card, but ...
Click to expand...
Click to collapse
At this point, your best approach is still to follow the initial advice of 'ibsk8'. Look in the log file for any further details about errors that occurred.
The logs are typically in /cache/recovery/ or (while the custom recovery is running) in /tmp
Use "adb pull" to get the log file to your PC and have a look at it. If you can't find anything obvious in there, then cut-n-paste the file to http://pastebin.com and provide the link to us.

bftb0 said:
At this point, your best approach is still to follow the initial advice of 'ibsk8'. Look in the log file for any further details about errors that occurred.
The logs are typically in /cache/recovery/ or (while the custom recovery is running) in /tmp
Use "adb pull" to get the log file to your PC and have a look at it. If you can't find anything obvious in there, then cut-n-paste the file to http://pastebin.com and provide the link to us.
Click to expand...
Click to collapse
I am not familiar using ADB pull. Tried using a root file manager to access the log but don't see.
Greatly appreciate your help, let me know what other info I should paste.
Thanks,