Database Users

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!

Completely Ruined my Partitions - Need Glow Restore IMG

Hello everyone,
Yesterday evening I bought a Nook Touch with Glow, went home, backed it up, or so I thought (my backup in retrospect is only 75mb and when I restore it, it does try to boot but says "Install Failed"), then proceeded to install android with Glownooter. Most of the programs I tried to launch closed after a few seconds (though I followed the instructions and installed both .zip parts), so I was going to restore and try again.
Following the restore instructions, I blew out the entire Nook partition table in preparation and now I feel I am screwed without external help. I tried everything last night for three hours...
Could anyone upload a stock .img file for me please? I really want to use the device and don't think it would be right for me to return it to the store for an exchange because of a mistake I made. Currently my SD card has nooter on it, but last night I had CWM open with the factory.zip someone posted and tried installing that zip to no avail... I even tried the n2T-Recovery_0.2.
Thank you.

trimalchioinwestegg said:
Hello everyone,
Yesterday evening I bought a Nook Touch with Glow, went home, backed it up, or so I thought (my backup in retrospect is only 75mb and when I restore it, it does try to boot but says "Install Failed"), then proceeded to install android with Glownooter. Most of the programs I tried to launch closed after a few seconds (though I followed the instructions and installed both .zip parts), so I was going to restore and try again.
Following the restore instructions, I blew out the entire Nook partition table in preparation and now I feel I am screwed without external help. I tried everything last night for three hours...
Could anyone upload a stock .img file for me please? I really want to use the device and don't think it would be right for me to return it to the store for an exchange because of a mistake I made. Currently my SD card has nooter on it, but last night I had CWM open with the factory.zip someone posted and tried installing that zip to no avail... I even tried the n2T-Recovery_0.2.
Thank you.
Click to expand...
Click to collapse
The partition table of the NSTG is the same as the NST.
I am in the same situation, and so far I have not had a huge success reviving mine but perhaps this thread could assist you in the right direction. Remember to save /rom information before trying anything
http://forum.xda-developers.com/showthread.php?t=1805936
good luck!

srgarfi said:
The partition table of the NSTG is the same as the NST.
I am in the same situation, and so far I have not had a huge success reviving mine but perhaps this thread could assist you in the right direction. Remember to save /rom information before trying anything
http://forum.xda-developers.com/showthread.php?t=1805936
good luck!
Click to expand...
Click to collapse
I know - I read that thread front to back last night and made no progress either.
Am I correct to assume that a backup image from someone would restore all partitions and completely solve our problem?
If so, if someone would upload an image in virgin state it would solve problems for everyone. I'm completely surprised that such an image is so elusive.

Anybody's full backup image will wipe out all your personalized data in /rom and /factory/rombackup.zip.
Generally, AFAIK, all these Nooters can screw up your Nook but not re-partition it or format it.
Make an effort to get to get your /rom back.

Renate NST said:
Anybody's full backup image will wipe out all your personalized data in /rom and /factory/rombackup.zip.
Generally, AFAIK, all these Nooters can screw up your Nook but not re-partition it or format it.
Make an effort to get to get your /rom back.
Click to expand...
Click to collapse
Is /rom an item unique to each device, or are you worried about me losing books/login information in "personalized data"? I had done nothing with my device except get past initial startup when I rooted it, so I have no personal items (books or otherwise) invested. I'm sorry if this is a silly question, but I don't understand.
Edit: Also, I used the magic (something) application to delete all partitions from the nook prior to the restore because it would not let me restore until then. If I had known my backup was invalid I would never have done that.

Attached is an image of what my restore contains. It does try to boot, but then says "Install Failed."
Note there is a romrestore.zip.

trimalchioinwestegg said:
I know - I read that thread front to back last night and made no progress either.
Am I correct to assume that a backup image from someone would restore all partitions and completely solve our problem?
If so, if someone would upload an image in virgin state it would solve problems for everyone. I'm completely surprised that such an image is so elusive.
Click to expand...
Click to collapse
Yes, that's the idea.
But as Renate mentions, that would overwrite you /rom partition with invalid data from another device (mac address, serial, and things like that).
But in the same situation I managed to salvage my /rom partition, so if I ever install such an image from someone elses' NSTG i coudl overwrite /rom with the data from my own device.
It could be also possible to generate such an image of an NSTG and then carefully unpack, delete the most sensitive files from /rom and repack the image to share. That way no sensitive infromation would be shared/compromised.
If you happen to stumble on such an image, please let me know.
BTW, those /boot files you have, could you pack them in a zip file and send it to me or post it here in the forums? I formatted my /boot partition and I could make good use of yours (no sensitive/personal information contained in there)

srgarfi said:
Yes, that's the idea.
But as Renate mentions, that would overwrite you /rom partition with invalid data from another device (mac address, serial, and things like that).
But in the same situation I managed to salvage my /rom partition, so if I ever install such an image from someone elses' NSTG i coudl overwrite /rom with the data from my own device.
It could be also possible to generate such an image of an NSTG and then carefully unpack, delete the most sensitive files from /rom and repack the image to share. That way no sensitive infromation would be shared/compromised.
If you happen to stumble on such an image, please let me know.
BTW, those /boot files you have, could you pack them in a zip file and send it to me or post it here in the forums? I formatted my /boot partition and I could make good use of yours (no sensitive/personal information contained in there)
Click to expand...
Click to collapse
I'm throwing in the towel because my /rom partition is gone and I understand all of that now. Tonight I will exchange for another (against my conscience) and make a proper backup before I do anything going forward.
In my research I found this:
search.4shared.com/postDownload/2YsbIxQJ/nook_glow_partition_files__023.html
It is all of the files except rom, and you will find the boot files in the 0 directory.
Good luck, and thanks for the help everyone.

Did you check both the p1 (/boot) and p3 (/factory) partitions to see if you had rombackup.zip?
Of course check p2 (/rom) for devconf.
Try repartitioning your Nook. You'll need CWR on an SD card with ADB or Noogie and Linux tools.
The script nookpart.sh is in my signature.

trimalchioinwestegg said:
I'm throwing in the towel because my /rom partition is gone and I understand all of that now. Tonight I will exchange for another (against my conscience) and make a proper backup before I do anything going forward.
In my research I found this:
search.4shared.com/postDownload/2YsbIxQJ/nook_glow_partition_files__023.html
It is all of the files except rom, and you will find the boot files in the 0 directory.
Good luck, and thanks for the help everyone.
Click to expand...
Click to collapse
Are you sure you can't recreate the partition table and mount /rom to get access to your files?
It is explained in the thread I mentioned. If so, then it would be fairly easy to recover your device.
Be careful when returning the NSTG to B&N, some of the operations performed are not covered in the warranty and they could want to charge you....
Anyway, thanks for that pointer! I'll see if I can use it to revive my NSTG

srgarfi said:
Are you sure you can't recreate the partition table and mount /rom to get access to your files?
It is explained in the thread I mentioned. If so, then it would be fairly easy to recover your device.
Be careful when returning the NSTG to B&N, some of the operations performed are not covered in the warranty and they could want to charge you....
Anyway, thanks for that pointer! I'll see if I can use it to revive my NSTG
Click to expand...
Click to collapse
Good thing I bought it at Staples.

Renate NST said:
Did you check both the p1 (/boot) and p3 (/factory) partitions to see if you had rombackup.zip?
Of course check p2 (/rom) for devconf.
Try repartitioning your Nook. You'll need CWR on an SD card with ADB or Noogie and Linux tools.
The script nookpart.sh is in my signature.
Click to expand...
Click to collapse
I fired up CWR but saw no USB activity on the computer (for ADB). Could you please tell me how to get ADB running? I did download your script and was interested in trying, but only got USB Disk mode on Noogie (which I couldn't get ADB to work with).
Thank you!

ADB on CWR can be a bit tricky.
It seems like the daemon dies sometimes on disconnecting and stuff.
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
http://forum.xda-developers.com/wiki/ADB
Boot it up on CWR first, then connect the USB cable.
In Windows it should show both Removable storage and ADB on the taskbar.
Code:
adb usb
adb shell
Make sure that you have the CWR with USB ADB and not Wifi ADB.

trimalchioinwestegg said:
I fired up CWR but saw no USB activity on the computer (for ADB). Could you please tell me how to get ADB running? I did download your script and was interested in trying, but only got USB Disk mode on Noogie (which I couldn't get ADB to work with).
Thank you!
Click to expand...
Click to collapse
Some easy instructions here http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
And search for a file named "ADB + Fastboot + Drivers.zip" in the forum.
With all that you can get ADB running in a Windows machine in no time.

Renate NST said:
ADB on CWR can be a bit tricky.
It seems like the daemon dies sometimes on disconnecting and stuff.
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
http://forum.xda-developers.com/wiki/ADB
Boot it up on CWR first, then connect the USB cable.
In Windows it should show both Removable storage and ADB on the taskbar.
Code:
adb usb
adb shell
Make sure that you have the CWR with USB ADB and not Wifi ADB.
Click to expand...
Click to collapse
Forgive me, but where would I find CWR with USB ADB? I currently have CWM-based Recovery v5.0.2.7 from the Glownooter thread. The 2gb image.
At the bottom of the black screen I have some errors, though:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Nothing reacts when I plug in USB.

srgarfi said:
Some easy instructions here http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
And search for a file named "ADB + Fastboot + Drivers.zip" in the forum.
With all that you can get ADB running in a Windows machine in no time.
Click to expand...
Click to collapse
I did successfully install ADB and the Android SDK earlier, but it is not running on my Nook under CWM and I do not know how to get it on there. The guide says "The Nook must specifically have an adbd daemon running on either WiFi or USB. The stock Nook has no adbd."
Do you know how?

trimalchioinwestegg said:
I did successfully install ADB and the Android SDK earlier, but it is not running on my Nook under CWM and I do not know how to get it on there. The guide says "The Nook must specifically have an adbd daemon running on either WiFi or USB. The stock Nook has no adbd."
Do you know how?
Click to expand...
Click to collapse
You should have adb.exe somewhere. From a command window in windows (start menu, execute cmd.exe), go to the path where adb.exe resides and type "adb devices": this will tell if your nook is hooked and accessible.

srgarfi said:
You should have adb.exe somewhere. From a command window in windows (start menu, execute cmd.exe), go to the path where adb.exe resides and type "adb devices": this will tell if your nook is hooked and accessible.
Click to expand...
Click to collapse
I do.
C:\Users\XXXX\AppData\Local\Android\android-sdk\platform-tools>adb usb
error: device not found
C:\Users\XXXX\AppData\Local\Android\android-sdk\platform-tools>adb devices
List of devices attached
I don't believe ADB is running on the nook, which is currently booted into CWM.
I do see the showing USB Mass Storage Device in device manager, but I cannot access the device as I can in noogie.

You may have the CWR running WiFi ADB (which doesn't make sense to me because you can't select AP).
If you have USB ADB running on CWR you should see on the USB in the taskbar two things, Mass Storage and ADB.

Renate NST said:
You may have the CWR running WiFi ADB (which doesn't make sense to me because you can't select AP).
If you have USB ADB running on CWR you should see on the USB in the taskbar two things, Mass Storage and ADB.
Click to expand...
Click to collapse
How can I make CWR use USB?

Lost A LOT of storage after installing a new rom

Hi everyone, this is my first thread
I recently rooted my 16gb WiFi only nexus 7. After installing 3 different roms (touchwiz, cyanogenmod 10, and xenon HD) I didn't like touch wiz or cyanogenmod, and I'm currently running xenon HD. However, when I opened my storage today, of said I had 3.6gb remaining. I thought it may have been all the apps, so I factory reset it, reset the partition, and deleted all data via recovery mode. That gave me about 1 more gigabyte. I opened ES file explorer and deleted everything there. I still have only 4.6 gigabytes usable. Anyone else have this issue?
Thanks
Sent from my Nexus 7 using xda app-developers app

Well, I deleted some old backups and now I have 7.5 gb of storage, which should do for now. But I still have that 6 GB leftover, anyone know whats wrong?
Thanks
Sent from my Nexus 7 using xda app-developers app

OK. Now I mucked around in the mounting/unmounting stuff, and now it won't boot. It's stuck at the Google screen. Someone help please???
Sent from my Nexus 7 using xda app-developers app[/QUOTE]

You are not the only person who has experienced this.
Bottom line is you need to rebuild the /data filesystem, which necessitates getting everything off of it including any nandroid backups plus anything worth saving in /sdcard
Either the "format data" option in TWRP, or using fastboot.
Code:
fastboot erase userdata
fastboot format userdata
I've had the latter create short file systems - and also not create short file systems.
Whatever causes this it seems to depend on prior state in the filesystem, even though I don't think things should behave this way. I've also had TWRP's "Format data" menu option create new, empty, & corrupted ext4 file systems. Ugh - I hope your luck is better than mine.
Note that you can run "df -k /data" in the recovery (after you have created the new filesystem by either method) to find out how big it is; better to check things are OK right away, rather than after you've put effort into restoring things or flashing ROMs.
Long boring thread, but related.
http://forum.xda-developers.com/showthread.php?t=2184486
good luck
Edit: no point in restoring the wedged /data backup. I hope you have earlier backups.

bftb0 said:
You are not the only person who has experienced this.
Bottom line is you need to rebuild the /data filesystem, which necessitates getting everything off of it including any nandroid backups plus anything worth saving in /sdcard
Either the "format data" option in TWRP, or using fastboot.
Code:
fastboot erase userdata
fastboot format userdata
I've had the latter create short file systems - and also not create short file systems.
Whatever causes this it seems to depend on prior state in the filesystem, even though I don't think things should behave this way. I've also had TWRP's "Format data" menu option create new, empty, & corrupted ext4 file systems. Ugh - I hope your luck is better than mine.
Note that you can run "df -k /data" in the recovery (after you have created the new filesystem by either method) to find out how big it is; better to check things are OK right away, rather than after you've put effort into restoring things or flashing ROMs.
Long boring thread, but related.
http://forum.xda-developers.com/showthread.php?t=2184486
good luck
Edit: no point in restoring the wedged /data backup. I hope you have earlier backups.
Click to expand...
Click to collapse
I basically have nothing I need on my tablet, so I'm fine deleting everything on it, if that's what you mean. I'll try, but thanks:good:

nicetaco said:
I basically have nothing I need on my tablet, so I'm fine deleting everything on it, if that's what you mean. I'll try, but thanks:good:
Click to expand...
Click to collapse
Wait, is that for getting back the storage or actually letting it boot up? Because right now the storage is the least of my concerns.

What I described is for getting back lost space (by recreating from scratch the ext4 filesystem in the userdata partition).
As it doesn't touch either the boot partition or the system partition, your tablet should certainly be able to boot. If you don't do a restore of /data from a backup, the result will be like a factory reset of whatever rom you had on the tablet.
Just make sure to check the size of the data partition before you start re-customizing or restoring data from backups to make sure that you got the full size of the partition.

bftb0 said:
What I described is for getting back lost space (by recreating from scratch the ext4 filesystem in the userdata partition).
As it doesn't touch either the boot partition or the system partition, your tablet should certainly be able to boot. If you don't do a restore of /data from a backup, the result will be like a factory reset of whatever rom you had on the tablet.
Just make sure to check the size of the data partition before you start re-customizing or restoring data from backups to make sure that you got the full size of the partition.
Click to expand...
Click to collapse
Ughhh its still not turning on...

nicetaco said:
Ughhh its still not turning on...
Click to expand...
Click to collapse
Please re-read this quote from your 2nd thread in this fiasco.
Nico_60 said:
How do you want to know what's happening to your device if don't tell us which commands you have done exactly with fastboot and why ?
Click to expand...
Click to collapse
If you screwed around with your system partition and it wouldn't boot before, then with a freshly formated and empty /data filesystem, of course it still will not boot. The instructions I provided in this thread only involved the userdata partition!
But you didn't say "I did such and such and it still hangs during the initial boot phase where the X logo is flashing on the screen"; instead you said:
"Ughhh its still not turning on".
WTF? Has your problem now morphed into a dead battery problem, or is the language you are using just incredibly imprecise?
Anyway, Flash a new ROM using the custom recovery. Any ROM - you pick. Maybe not that Xenon ROM or whatever it is called. See if the new ROM boots. And then immediately after it boots, check to see what size the /data partition is.
And if you come back into this thread anymore please be specific about what you are attempting and exactly what symptoms you are observing.
good luck

bftb0 said:
Please re-read this quote from your 2nd thread in this fiasco.
If you screwed around with your system partition and it wouldn't boot before, then with a freshly formated and empty /data filesystem, of course it still will not boot. The instructions I provided in this thread only involved the userdata partition!
But you didn't say "I did such and such and it still hangs during the initial boot phase where the X logo is flashing on the screen"; instead you said:
"Ughhh its still not turning on".
WTF? Has your problem now morphed into a dead battery problem, or is the language you are using just incredibly imprecise?
Anyway, Flash a new ROM using the custom recovery. Any ROM - you pick. Maybe not that Xenon ROM or whatever it is called. See if the new ROM boots. And then immediately after it boots, check to see what size the /data partition is.
And if you come back into this thread anymore please be specific about what you are attempting and exactly what symptoms you are observing.
good luck
Click to expand...
Click to collapse
OK. I tried to install a new rom, but I can't because I have USB debugging off, which I can't turn on

bftb0 said:
You are not the only person who has experienced this.
Bottom line is you need to rebuild the /data filesystem, which necessitates getting everything off of it including any nandroid backups plus anything worth saving in /sdcard
Either the "format data" option in TWRP, or using fastboot.
Code:
fastboot erase userdata
fastboot format userdata
I've had the latter create short file systems - and also not create short file systems.
Whatever causes this it seems to depend on prior state in the filesystem, even though I don't think things should behave this way. I've also had TWRP's "Format data" menu option create new, empty, & corrupted ext4 file systems. Ugh - I hope your luck is better than mine.
Note that you can run "df -k /data" in the recovery (after you have created the new filesystem by either method) to find out how big it is; better to check things are OK right away, rather than after you've put effort into restoring things or flashing ROMs.
Long boring thread, but related.
http://forum.xda-developers.com/showthread.php?t=2184486
good luck
Edit: no point in restoring the wedged /data backup. I hope you have earlier backups.
Click to expand...
Click to collapse
Thank you, bftb0!
I was looking around for this after I discovered my lack of space. I read about it before, but couldn't dig up the post. Thanks for informing us! Enjoy the thanks!

nicetaco said:
OK. I tried to install a new rom, but I can't because I have USB debugging off, which I can't turn on
Click to expand...
Click to collapse
ADB is available in the custom recovery... so long as you have the right drivers installed on your PC. And that is NOT controlled by some setting in the most recent ROM that you flashed - it is always running in the custom recovery.
One of the quirks about ADB in the recovery with the Nexus7 is that it claims a different USB address than "ADB Composite Interface" that the regular OS does. This might mean that ADB works correctly with the regular OS booted, but not when the custom recovery is booted, depending on what drivers you have installed. Yes, you need yet another driver installed even though they are both "ADB" connections. But that is a Windows driver issue, not a problem with the N7.
You can also use an OTG cable and a USB drive with TWRP if that is easier. Put your ROM on the memory stick and then use TWRP's "external memory". To be most compatible, make sure the USB stick is formatted in a FAT format. (I don't know if TWRP can handle NTFS).
upichie said:
Thank you, bftb0!
I was looking around for this after I discovered my lack of space. I read about it before, but couldn't dig up the post. Thanks for informing us! Enjoy the thanks!
Click to expand...
Click to collapse
I wonder if I can I trade them in for some coupons or something

@bftb0, I was not able to use adb while in TWRP but i found THIS and it was the solution, what do you think about this "fix"?

bftb0 said:
ADB is available in the custom recovery... so long as you have the right drivers installed on your PC. And that is NOT controlled by some setting in the most recent ROM that you flashed - it is always running in the custom recovery.
One of the quirks about ADB in the recovery with the Nexus7 is that it claims a different USB address than "ADB Composite Interface" that the regular OS does. This might mean that ADB works correctly with the regular OS booted, but not when the custom recovery is booted, depending on what drivers you have installed. Yes, you need yet another driver installed even though they are both "ADB" connections. But that is a Windows driver issue, not a problem with the N7.
You can also use an OTG cable and a USB drive with TWRP if that is easier. Put your ROM on the memory stick and then use TWRP's "external memory". To be most compatible, make sure the USB stick is formatted in a FAT format. (I don't know if TWRP can handle NTFS).
I wonder if I can I trade them in for some coupons or something
Click to expand...
Click to collapse
Holy crap I forgot about the OTG cables. Thanks, I'll try it!

nicetaco said:
Holy crap I forgot about the OTG cables. Thanks, I'll try it!
Click to expand...
Click to collapse
Thank you so much. That did it.
First problem fixed through XDA developers
Enjoy my thanks

Nico_60 said:
@bftb0, I was not able to use adb while in TWRP but i found THIS and it was the solution, what do you think about this "fix"?
Click to expand...
Click to collapse
The ADB daemon - "adbd" is definitely sitting there running inside the custom recovery. Even if you can't communicate with it because of a lack of a driver, you should nevertheless be able to see it as an unknown device in the PC's device manager.
I have done the same hack - hand editing the .INF file - with both the Google SDK drivers and the Asus drivers, and in both cases it worked fine (one driver for everything: ADB in the OS, ADB in TWRP/CWM, and fastboot with the bootloader).
I have also used the Google SDK driver without modification plus the XDA Universal Naked driver. That means using the Google driver for fastboot and ADB when the OS is booted, and the XUN driver for custom recoveries only.
At the present time the ONLY driver I have installed is a hacked version of the Asus drivers.
Win 7 complains about signing when doing this (for the Asus drivers for sure, I can't remember if the Google driver is signed or not).
As I mentioned, Win 7 Pro x64. I suppose the whole "violated signing" might make life even more difficult with Win 8 though.

bftb0, did you personally experience the problem of losing space on the internal memory? I tried your advice, but it didn't work. I'm on PAC(man) ROM. I booted into TWRP, did the data wipe (not factory reset, the full wipe that wipes the everything) but I still only have 13 gb available (on my 32 gb Nexus 7). I rebooted into TWRP and did a factory reset AND wipe data, but I am still missing half of my internal memory.
Do you need to do this on the stock ROM for it to work? Any other tips would be greatly appreciated.

upichie said:
bftb0, did you personally experience the problem of losing space on the internal memory? I tried your advice, but it didn't work. I'm on PAC(man) ROM. I booted into TWRP, did the data wipe (not factory reset, the full wipe that wipes the everything) but I still only have 13 gb available (on my 32 gb Nexus 7). I rebooted into TWRP and did a factory reset AND wipe data, but I am still missing half of my internal memory.
Do you need to do this on the stock ROM for it to work? Any other tips would be greatly appreciated.
Click to expand...
Click to collapse
Yes, it really did happen to me.
After it happened I took the trouble to download 4 different versions of TWRP (2.4.1.0-2.4.4.0), and I re-created the ext4 filesystem with:
- each of the different versions of TWRP and
- fastboot format userdata
after each, I did a "e2fsck -f -n <block-device>" on the (unmounted) userdata partition to see that they were clean, and I also dumped the output of "tune2fs -l <block-device>" to a file for comparison. Other than things that I would expect to be different (e.g. partition UUID identifier strings and timestamps), I noticed no differences. And also, I couldn't reproduce the problem for the life of me.
Above you mention full "data wipe". In TWRP (v2.4.1.0), this is presented as a separate button in the "Wipe" sub-menu where it (the last button in the first column) is labeled "Format Data". I suppose this is what you mean, but thought I would be explicit to avoid any confusion. (The "factory reset" procedure in the two custom recoveries - both CWM and TWRP - can not possibly re-create the ext4 filesystem in /data, as the /data/media/0 SD card files are in there. But the "Format Data" button does destroy & recreate the whole filesystem).
If you press on this button and at the same time capture the output of the "ps" command, you will see that TWRP recovery invokes the /sbin/make_ext4fs in the following way
Code:
make_ext4fs -l -32768 /dev/block/mmcblk0p<PARTNUM>
(CWM probably uses a different external command as it does not seem to have a "make_ext4fs" command in it's ramdisk. Probably mke2fs with ext4 options on the command line)
Anyways, I can't say I have my finger on exactly how to resolve the problem as I can not re-created it. But it did happen to me.
One thing you can try rather than using TWRP's "make_ext4fs" command (underneath that button "Format Data") is to reboot into the bootloader from TWRP, and do the file system formatting in fastboot instead of TWRP, as in:
Code:
fastboot format userdata
(noobs: caution, this is a full userdata wipe)
and then bop back into the recovery and check things with "tune2fs" report
Code:
tune2fs -l /dev/block/mmcblk0p<PARTNUM>
My 32G N7 shows a total block count of 7503608 (x 4k/block = 29.3 GiB) doing this.
As I mentioned before, it's a good idea to check to see you have the right size before you start restoring stuff to avoid wasting time. You can do it above with "tune2fs -l", or because TWRP seems to want to mount /data and /sdcard when it boots, just run
adb shell df -k /data
to get a report of total and used size.
Sorry this isn't more definiitve. I would have spent more time looking at this, but it is tedious as you need to unload the whole d*mn SD card in order to experiment. Thank goodness my 30GB partition only has about 10Gigs of stuff on it.
good luck

bftb0 said:
Yes, it really did happen to me.
After it happened I took the trouble to download 4 different versions of TWRP (2.4.1.0-2.4.4.0), and I re-created the ext4 filesystem with:
- each of the different versions of TWRP and
- fastboot format userdata
after each, I did a "e2fsck -f -n <block-device>" on the (unmounted) userdata partition to see that they were clean, and I also dumped the output of "tune2fs -l <block-device>" to a file for comparison. Other than things that I would expect to be different (e.g. partition UUID identifier strings and timestamps), I noticed no differences. And also, I couldn't reproduce the problem for the life of me.
Above you mention full "data wipe". In TWRP (v2.4.1.0), this is presented as a separate button in the "Wipe" sub-menu where it (the last button in the first column) is labeled "Format Data". I suppose this is what you mean, but thought I would be explicit to avoid any confusion. (The "factory reset" procedure in the two custom recoveries - both CWM and TWRP - can not possibly re-create the ext4 filesystem in /data, as the /data/media/0 SD card files are in there. But the "Format Data" button does destroy & recreate the whole filesystem).
If you press on this button and at the same time capture the output of the "ps" command, you will see that TWRP recovery invokes the /sbin/make_ext4fs in the following way
Code:
make_ext4fs -l -32768 /dev/block/mmcblk0p<PARTNUM>
(CWM probably uses a different external command as it does not seem to have a "make_ext4fs" command in it's ramdisk. Probably mke2fs with ext4 options on the command line)
Anyways, I can't say I have my finger on exactly how to resolve the problem as I can not re-created it. But it did happen to me.
One thing you can try rather than using TWRP's "make_ext4fs" command (underneath that button "Format Data") is to reboot into the bootloader from TWRP, and do the file system formatting in fastboot instead of TWRP, as in:
Code:
fastboot format userdata
(noobs: caution, this is a full userdata wipe)
and then bop back into the recovery and check things with "tune2fs" report
Code:
tune2fs -l /dev/block/mmcblk0p<PARTNUM>
My 32G N7 shows a total block count of 7503608 (x 4k/block = 29.3 GiB) doing this.
As I mentioned before, it's a good idea to check to see you have the right size before you start restoring stuff to avoid wasting time. You can do it above with "tune2fs -l", or because TWRP seems to want to mount /data and /sdcard when it boots, just run
adb shell df -k /data
to get a report of total and used size.
Sorry this isn't more definiitve. I would have spent more time looking at this, but it is tedious as you need to unload the whole d*mn SD card in order to experiment. Thank goodness my 30GB partition only has about 10Gigs of stuff on it.
good luck
Click to expand...
Click to collapse
.
I'm a total command prompt beginner here, so could you explain where I'm doing the fastboot format command? In a terminal on the device? Using adb on my windows machine? I tried all that I could think of, but none of it worked. No form of wiping the device (yes, via "format data" in TWRP) seems to work. I'm still missing half of my storage.
EDIT: Okay, so I ran the command--I had to have the device in the bootloader, duh. Unfortunately, it still did not work. When recreating the file system, it said there was a total of ~3.5 million blocks--half what I saw reported in the other thread. Not surprising, since I'm missing half of my storage. How come this is working for other people but not me? I tried doing both at the same time, but to no avail. This is getting stupid.

upichie said:
EDIT: Okay, so I ran the command--I had to have the device in the bootloader, duh. Unfortunately, it still did not work. When recreating the file system, it said there was a total of ~3.5 million blocks--half what I saw reported in the other thread. Not surprising, since I'm missing half of my storage. How come this is working for other people but not me? I tried doing both at the same time, but to no avail. This is getting stupid.
Click to expand...
Click to collapse
Arrgh. Did you do the "fastboot erase userdata" first?
Here's what the fastboot format looked like on my device when I did this last (3/13):
Code:
$ fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 4.974s]
finished. total time: 4.979s
$ fastboot format userdata
erasing 'userdata'...
OKAY [ 4.454s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 30734811136
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7503616
Block groups: 229
Reserved block group size: 1024
Created filesystem with 11/1875968 inodes and 161774/7503616 blocks
sending 'userdata' (139197 KB)...
writing 'userdata'...
OKAY [ 33.733s]
finished. total time: 38.194s
As I said, I was unable to reproduce the problem even though I tried. But it almost seems like the creation of the new filesystem is inferring something from somewhere (but where?) about the userdata partition size which is incorrect. Almost like it happens because of something it sees in the prior filesystem (which is being destroyed). So it becomes irreproducible unless you can recreate the same starting condition.
There's other mysterious crap going on here too. See the output above? The part where it says "sending 'userdata' (139197 KB)" ? It will say this no matter where you run the command from, and there is no 139 MB "userdata.img" file in the folder it runs from!!! 139 MB? For a filesystem which is empty when you mount it?
I don't know. Here's one more thing to try, though. In addition to doing the "erase" & "format" commands, perhaps you could actually flash the userdata image from the stock ROM
Code:
fastboot erase userdata
fastboot format userdata
fastboot flash userdata userdata.img
and then when you boot to the custom recovery, perform a "factory reset" - or try doing the "Format Data" thing in TWRP after (or before?) the above steps.
If none of this works, I suppose you could try the equivalent sorts of things with CWM and see if you get a different result.
You don't need to permanently install CWM with a hard flash - you can just soft-boot it for a single session:
Code:
fastboot boot recovery-clockwork-touch-6.0.2.3-grouper.img
Sorry this is so vague, but you know how it goes - you stumble into a problem, start fooling around until it gets fixed - and because you weren't really expecting the problem in the first place, you haven't written down the exact conditions and steps. Like I said, I tried to re-create the problem a variety of ways - but failed at that effort.
good luck

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,

Kobo Arc Development

So I was randomly flying around on Google today, and I noticed that someone had claimed to root the Kobo Arc, and gave written instructions here -- http : // www . mobileread . com / forums / showthread.php?p=2584491 (Remove the spaces, XDA won't let me post an actual link, since I don't have 10 posts yet). After running through this myself, I went on the Google Play store and used root checker. Much to my surprise, it worked, and my device now has root access. I even tested with Root Explorer, and mounted the system partition as R/W, and I can move things in and out of it. I'm currently working on trying to get a custom ROM working, but I'm worried that I will cause a brick, since Cyanogen doesn't support the Arc. (yet...)

ThunderBird2678 said:
So I was randomly flying around on Google today, and I noticed that someone had claimed to root the Kobo Arc, and gave written instructions here -- http : // www . mobileread . com / forums / showthread.php?p=2584491 (Remove the spaces, XDA won't let me post an actual link, since I don't have 10 posts yet). After running through this myself, I went on the Google Play store and used root checker. Much to my surprise, it worked, and my device now has root access. I even tested with Root Explorer, and mounted the system partition as R/W, and I can move things in and out of it. I'm currently working on trying to get a custom ROM working, but I'm worried that I will cause a brick, since Cyanogen doesn't support the Arc. (yet...)
Click to expand...
Click to collapse
confirmed, was just going to post this but was beaten to it.
http://www.mobileread.com/forums/showthread.php?t=218928
ive attached the file but please go to that website and pay homage to whoever did this work...now to the next stop, a ROM
Device now has a working custom recovery see post 15
Sent from my Arc using xda app-developers app

dazza9075 said:
confirmed, was just going to post this but was beaten to it.
http://www.mobileread.com/forums/showthread.php?t=218928
In terms of a ROM do we not need a compatible boot loader that will allow unsigned ROMs?
ive attached the file but please go to that website and pay homage to whoever did this work...now to find a man about a ROM
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
i have absolutely no idea what im doing but I think I have dumped 12 partitions using
dd if=/dev/block/mmcblk0p10 of=/sdcard/p10.img
is there anyone around that fancies a challenge? im in a position where bricking this thing isn't really much of a problem so if someones up for a challenge and wants to help im willing to lend myself and the device to this

Warning : Block of Text Ahead.
dazza9075 said:
confirmed, was just going to post this but was beaten to it.
In terms of a ROM do we not need a compatible boot loader that will allow unsigned ROMs?
ive attached the file but please go to that website and pay homage to whoever did this work...now to find a man about a ROM
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
Haha. As soon as I found a thread called "root the Kobo Arc" on Google, I posted it here right away. Sorry if I deprived you of the satisfaction! *troll*
Joking aside, I'm not too sure about the bootloader. I think it's pretty locked down (since I put a nexus 7's cyanogenmod onto the data partition and rebooted. It tried to updated, but said validation failed, or something of that sort). I can't install any custom recoveries either, since I have no idea how to do it in the first place, and there's none made for the Arc.
Also, I analyzed the Arc with the "Droid Examiner" App from the play store (That is a really great app, just so you know), and found that it uses a board called "zeus". The funny thing, though, is that one of Sony's Xperia phones, also has a board called "Zeus", and there's Cyanogenmod for that (albiet not the latest version). However, these two devices have nothing in common. The closest thing to an Arc that has Cyanogenmod is the Nook HD/HD+, which uses the exact same chip (OMAP TI 4470).
If someone is smart enough (not me) to analyze the Cyanogenmod files for the Nook, and see how they work, that may lead into flashing the Arc.
Anyway, I'm resetting the Arc, since I'm having weird cases where the Arc would freeze after booting it from sleep mode, and I'd have to turn it off and on again. I think that was something else I did, since it happened before the root, but neh, I might as well try this all from factory default settings.
Sorry for the block of text, guys!
P.S. Using the stock Jelly Bean boot animation on the Arc looks amazing!:laugh:

Haha, its cool, like yourself I just happened to Google kobo arc root and for once my googe fu was up to the task and the root appeared
I've been looking at starting my own recovery mod branch but its no simple task by the looks of it, if their are similar devices we can use all their data and tweak it to ours which would help a lot!
Oh I think we have fast boot, I held vol down and pushed power on, it just sat at the kobo arc screen, I used the nexus 7 driver from the universal adb/fastboot driver I found on here and it connected up http://forum.xda-developers.com/showthread.php?t=2263822
I stumbled on some to good to be true program on Xda dev that apparently can root anything and unlock any bootloader once your in fastboot mode. I have tried that part and it said it was successful but i have no idea how to test this out yet, the program does a bunch of other stuff too, the adb stuff worked as did apk sending, and the rooting options knew i was rooted, it also has flashing functions, I'll be damed if I can find it now I'm at home though , I'll have another look.
I don't mind doing leg work but if someone can read the map it would be very helpful!
Edit, found it
http://forum.xda-developers.com/showthread.php?t=2399385
http://www.mediafire.com/?vwxpq62pa927s9c
Sent from my Arc using xda app-developers app

dazza9075 said:
Haha, its cool, like yourself I just happened to Google kobo arc root and for once my googe fu was up to the task and the root appeared
I've been looking at starting my own recovery mod branch but its no simple task by the looks of it, if their are similar devices we can use all their data and tweak it to ours which would help a lot!
Oh I think we have fast boot, I held vol down and pushed power on, it just sat at the kobo arc screen, I used the nexus 7 driver from the universal adb/fastboot driver I found on here and it connected up http://forum.xda-developers.com/showthread.php?t=2263822
I stumbled on some to good to be true program on Xda dev that apparently can root anything and unlock any bootloader once your in fastboot mode. I have tried that part and it said it was successful but i have no idea how to test this out yet, the program does a bunch of other stuff too, the adb stuff worked as did apk sending, and the rooting options knew i was rooted, it also has flashing functions, I'll be damed if I can find it now I'm at home though , I'll have another look.
I don't mind doing leg work but if someone can read the map it would be very helpful!
Edit, found it
http://forum.xda-developers.com/showthread.php?t=2399385
http://www.mediafire.com/?vwxpq62pa927s9c
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
Um... Okay. I've installed the drivers (I think I installed them correctly), and I booted my device using "volume down + power". I have it connected to my System, but whenever I try to use one of the options in the Android Root Toolkit, it tells me it's waiting for the device. I don't know what I did wrong, but something's clearly not working.
As far as the recovery goes, I think that looking at the Nook Tablet from TWRP would work quite nicely. It runs on a similar processor ( I believe it's a OMAP TI 4430 ), and it seems to be quite similar in specs to the Arc. If only I was a bit better at programming...

ThunderBird2678 said:
Um... Okay. I've installed the drivers (I think I installed them correctly), and I booted my device using "volume down + power". I have it connected to my System, but whenever I try to use one of the options in the Android Root Toolkit, it tells me it's waiting for the device. I don't know what I did wrong, but something's clearly not working.
As far as the recovery goes, I think that looking at the Nook Tablet from TWRP would work quite nicely. It runs on a similar processor ( I believe it's a OMAP TI 4430 ), and it seems to be quite similar in specs to the Arc. If only I was a bit better at programming...
Click to expand...
Click to collapse
im usig the generic android adb driver and the bootloader driver for fast boot
im dumped all partitions and mapped them all out, see below for file system details
But again I'm blindly stabbing in the dark and most tutorials are a bit lacking in depth or not relevant to the kobo :/
Sent from my Arc using xda app-developers app

127|[email protected]:/ # blkid
/dev/block/dm-2: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-1: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-0: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p4: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
[email protected]:/ #

Okay, so I can't even push apps to the Arc using ADB. I think you have to boot into recovery (power + volume up). I don't know how to use the terminal at all (I'm lost, I know D: ), so I don't have that installed on the Arc. I remember being able to do ADB even with my Sony Reader (First gen, PRST1), so I'm not sure why the Arc isn't quite working. I have both drivers installed, BTW.
As for the recovery, I can't even find a method to flash it. I'm still trying everything I can, though. :\
Sent from my Arc using xda app-developers app

ive mapped out the following partitions and any info ive found about each of them, im not in a position to help at the moment, got a big day at work tomorrow, as mentioned above ive used several tools,
SuperSU,
ROM toolbox pro
busybox
remount
Below is a list of all the available partition names and numbers
/dev/block/mmcblk0p1 xloader
/dev/block/platform/omap/omap_hsmmc.1/by-name/xloader
348KB
/dev/block/mmcblk0p2 bootloader
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootloader
1.50MB
/dev/block/mmcblk0p3 cypto
/dev/block/platform/omap/omap_hsmmc.1/by-name/crypto
Completely empty
64KB partition size
/dev/block/mmcblk0p4 EFS
Mounted as /FACTORY
/dev/block/mmcblk0p4:UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/efs /factory ext4 ro,relatime,barrier=1,data=ordered 0 0
20MB
/dev/block/mmcblk0p5 misc
/dev/block/platform/omap/omap_hsmmc.1/by-name/misc
Completely empty
128KB partition size
/dev/block/mmcblk0p6 Bootlogo
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootlogo
Contains kobo arc picture
4MB partition size
/dev/block/mmcblk0p7 Logos
/dev/block/platform/omap/omap_hsmmc.1/by-name/logos
contains the battery charge logo
28MB partition size
/dev/block/mmcblk0p8 recovery
/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
data contains a GZ file, when decompressed we get a 8.5MB file of unknown type, exact same as in boot
5MB of data
16MB partition size
/dev/block/mmcblk0p9 boot
/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
data contains a GZ file, when decompressed we get a 8.5MB file of unknown type, exact same as n recovery
4.5MB of data
8MB partition size
/dev/block/mmcblk0p10 CACHE
Mounted as /CACHE
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache ext4
rw,nosuid,nodev,noatime,errors=panic,barrier=1,nom blk_io_submit,data=ordered 0
0
768MB partition size
/dev/block/mmcblk0p11 SYSTEM
Mounted as /SYSTEM
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/system /system ext4
rw,relatime,barrier=1,data=ordered 0 0
910MB partition size
/dev/block/mmcblk0p12 USERDATA
Mounted as /DATA
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata /data ext4
rw,nosuid,nodev,noatime,errors=panic,barrier=1,nom blk_io_submit,data=ordered 0
0
12GB partition size

Watching with interest. The root works. No frills CPU installed and working. There may be hope for this thing yet:good:

Moved to new thread and more appropriate forum - keep up the good work guys

im not sure that's going to work you know, ive had some permission errors with adb which suggests the root isn't full, terminal on the device works fine, but adb just has some problems, adb shell and the su seems to fix them.
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
http://www.addictivetips.com/android/make-nandroid-backups-on-android-without-booting-into-recovery/
im busy today but ive found these useful
i think Clockwork Recovery should be our focus at this point or if you have dumped your partitions(?) attempt to construct a rom for later use
or this should work too
Install any Custom Recovery with flash_image:
Just like the previous method, this method also requires following advanced steps and is not recommended if the first method is working for you. flash_image is a tool for Android devices that lets you rewrite your phone’s system partitions with partition image files and installing it to your device requires ADB. If you don’t already have ADB installed, check out our guide on installing ADB. Once you have ADB installed, flash the custom recovery image as follows:
WARNING: It is very important that the recovery image that you use in this method is compatible with your device. Else it will not work and flashing it could possibly brick your device.​
Download flash_image and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands: adb push c:\flash_image /sdcard/adb push c:\recovery.img /sdcard/adb shellsumount -o remount, rw /systemcp /sdcard/flash_image /system/bincd /system/binchmod 777 flash_imageflash_image recovery /sdcard/recovery.imgThis will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ thrice.

dazza9075 said:
im not sure that's going to work you know, ive had some permission errors with adb which suggests the root isn't full, terminal on the device works fine, but adb just has some problems, adb shell and the su seems to fix them.
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
http://www.addictivetips.com/android/make-nandroid-backups-on-android-without-booting-into-recovery/
im busy today but ive found these useful
i think Clockwork Recovery should be our focus at this point or if you have dumped your partitions(?) attempt to construct a rom for later use
or this should work too
Install any Custom Recovery with flash_image:
Just like the previous method, this method also requires following advanced steps and is not recommended if the first method is working for you. flash_image is a tool for Android devices that lets you rewrite your phone’s system partitions with partition image files and installing it to your device requires ADB. If you don’t already have ADB installed, check out our guide on installing ADB. Once you have ADB installed, flash the custom recovery image as follows:
WARNING: It is very important that the recovery image that you use in this method is compatible with your device. Else it will not work and flashing it could possibly brick your device.​
Download flash_image and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands: adb push c:\flash_image /sdcard/adb push c:\recovery.img /sdcard/adb shellsumount -o remount, rw /systemcp /sdcard/flash_image /system/bincd /system/binchmod 777 flash_imageflash_image recovery /sdcard/recovery.imgThis will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ thrice.
Click to expand...
Click to collapse
I've already tried that recovery method (I spent about two hours just googling), and it doesn't work with the Arc. The ADB won't let me push the image over.
As for Cyanogenmod, I tried something yesterday. A person on the Mobileread forums (apparently a Kobo employee) put out an update.zip file for the Kobo Arc. The file was quite old, and it's really just the 4.1.1 update that (I hope) we're all running. He said that as long as you put it on the root of the data partition, the Arc will flash it immediately. When I tried taking a Nexus 7's Cyanogenmod file and sticking it in the same place, the Arc started flashing it, but then just said there was an error with the update. So I personally think that you do require a properly signed ROM.
However, if you open up Kobo's update.zip using Winrar, a sidebar pops up that says "signed by SignApk". I don't know too much about this, but couldn't we use this "signapk" to sign our own ROMS and flash them?
Just a thought.

​
ThunderBird2678 said:
As for Cyanogenmod, I tried something yesterday. A person on the Mobileread forums (apparently a Kobo employee) put out an update.zip file for the Kobo Arc. The file was quite old, and it's really just the 4.1.1 update that (I hope) we're all running. He said that as long as you put it on the root of the data partition, the Arc will flash it immediately. When I tried taking a Nexus 7's Cyanogenmod file and sticking it in the same place, the Arc started flashing it, but then just said there was an error with the update. So I personally think that you do require a properly signed ROM.
However, if you open up Kobo's update.zip using Winrar, a sidebar pops up that says "signed by SignApk". I don't know too much about this, but couldn't we use this "signapk" to sign our own ROMS and flash them?
Just a thought.
Click to expand...
Click to collapse
I think there is a problem with the setup, I just flashed a CW recovery image and it worked, or didn't rather! but the concept did, transferred, flashed using adb, I had to replace it though as it was totally borked and kept restarting, apparently the touch based recovery methods can be like that, ill have some good time tomorrow night (UK time) if your about, and ill keep at it tonight if I get a chance!
copy recovery to adb location
adb push recovery.img /sdcard/
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell and type
adb reboot recovery
fixed it by holding power button and vol down to boot to fastboot recovery
then ran
fastboot flash recovery inputrecovery.img
inputrecovery being my original recovery file taken from partition 8!
ive updated the partition map on the post above with my progress, but it looks like we can flash to them my name so its probably less relevant now
oh ive ditched the drivers I was using and reinstalled the drivers from the official SDK, generic android adb for within android and android bootloader for fastboot
EDIT
Yaaas!! recovery replaced
ok, deleting or renaming /etc/install-recover.sh appears to have stopped custom recovery being changed back to stock after reboot, I used the recovery builder to make a build from partition 8, which it did without error, flashed using the above commands.​
Still don't know what im doing though, but progress is progress ​
ill post a link to the custom recovery ive made soon, we need to make up some fstab file listing all the mounts etc, i tried one but it must be borked as recovery couldnt see anything​
​

ok i have a working recovery http://jenkins.cyanogenmod.com/job/recovery/35325/artifact/
its not quite done, i need to mount the sdcard, its physical location is mounted, ie /data, but its virtual mount isn't /storage/sdcard
I have asked for some help so hopefully someone can help be on this, I think it needs to be symlinked
im going to need some help soon, so if your reading this with a kobo arc, I need you! im needing a hand folks! if your stuck getting this far let me know and we can PM to get it working
oh and recovery is also now persistant by deleting or renaming /etc/install-recover.sh"

Sorted folks!
I have made a stable and thus far, a working custom recovery.
its mounting everything and backing up / restoring works as it should, unless anyone can find any issues I consider this step in building a complete ROM completed,
you must have root, download arctic.apk and install on your tablet, you will need to enable unknown sources In dev options first
you must have android and java sdk also installed, you will need to add the google usb drivers in the android sdk, you will find them in the "extras"
Enable usb debug on the arc and install the generic google adb usb drivers
Delete or rename /etc/install-recover.sh this will make the custom recovery persistent
Copy the recovery.img to the SDCard, either by using drag and drop in windows ( to root of "internal storage") or by adb push, if you use adb push then remember to copy recovery.img to the same folder as adb
adb push recovery.img /sdcard/
The next job is to open up a command window and navigate to adb folder, type the following exactly, even better copy and paste them!
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell (ctrl+C) and type
adb reboot recovery
and bobs your uncle, one happy new recovery

Thanks for your hard work. Everything works quite well.
Sent from my Arc using Tapatalk 4

cancuck said:
Thanks for your hard work. Everything works quite well.
Sent from my Arc using Tapatalk 4
Click to expand...
Click to collapse
that's the easy bit, I have a feeling I need to make a couple of changes to the recovery.img but noting major, just a couple of other mounts I may have missed
I probably would like some help with the next bit however.
im just trying to build a development platform, I have a loathing for Linux as a desktop so will need to re educate myself without throwing my laptop out of the window, after that "challenge" the ROM should be easy

Well, I've just done it, and it works. Everything seems to be in order for the time being. I'm going to muck around with the new capabilities, and see what I can do.