device was working fine i forgot way back what rom i used honeycomb somthing ,
although i wanted to just clean it out and all the apps, so i went into setting and clicked factory reset , it booted into cwm i chose factroy reset/cashe again from there , now bootup says booting into recovery kernel and starts cwm 3.0.2.8 ,shows gtab 1.2 and NI adam rev5
formatted sd card to 2048/0 , data wipe /cashe etc. same thing happens
i was reading a bunch about nvflashing here http://forum.xda-developers.com/showthread.php?t=861950 although that was for people who couldnt boot cwm.
any ideas , or do i need to nvflash?
revized said:
any ideas , or do i need to nvflash?
Click to expand...
Click to collapse
No need for nvflash. See this thread.
rajeevvp said:
No need for nvflash. See this thread.
Click to expand...
Click to collapse
thanks bro! you did it! its running fine again! :good: fastest thing i have ever done it seems!
update: keeps saying FC android keyboard has stopped responding?
and the keyboard wont appear
revized said:
update: keeps saying FC android keyboard has stopped responding?
and the keyboard wont appear
Click to expand...
Click to collapse
Can't say what's wrong without looking at the logs, but, since you said you wanted to clean out everything (ie. you don't mind losing data), do this in CWM:
1. Repartition the internal SD card.
2. Format /cache.
This will get your ROM installation into a clean, freshly installed, state.
rajeevvp said:
Can't say what's wrong without looking at the logs, but, since you said you wanted to clean out everything (ie. you don't mind losing data), do this in CWM:
1. Repartition the internal SD card.
2. Format /cache.
This will get your ROM installation into a clean, freshly installed, state.
Click to expand...
Click to collapse
I format the sd 2048/0 and click wipe cashe partition then boot system, got same fc keyboard as before
revized said:
I format the sd 2048/0 and click wipe cashe partition then boot system, got same fc keyboard as before
Click to expand...
Click to collapse
Hmm. Now its getting interesting. Time to collect some logs.
1. Boot into CWM.
2. Repartition internal SD card. (Remove any external SD cards from the slot first.)
3. Format /cache (mounts and storage menu).
4. Run these adb commands on your PC immediately after completing steps 2 and 3.
Code:
C:\SOME\PATH> [B]adb push [I]C:\SOME\PATH\[/I]t.sh /tmp[/B]
C:\SOME\PATH> [B]adb shell chmod 700 /tmp/t.sh[/B]
C:\SOME\PATH> [B]adb shell /tmp/t.sh > log.txt[/B]
Post the log.txt file here.
okay thank you, i am installing the adb thing right now , although i dont understand was i supposed to do something with that file inside the t.zip you posted ?
rajeevvp said:
Hmm. Now its getting interesting. Time to collect some logs.
1. Boot into CWM.
2. Repartition internal SD card. (Remove any external SD cards from the slot first.)
3. Format /cache (mounts and storage menu).
4. Run these adb commands on your PC immediately after completing steps 2 and 3.
Code:
C:\SOME\PATH> [B]adb push [I]C:\SOME\PATH\[/I]t.sh /tmp[/B]
C:\SOME\PATH> [B]adb shell chmod 700 /tmp/t.sh[/B]
C:\SOME\PATH> [B]adb shell /tmp/t.sh > log.txt[/B]
Post the log.txt file here.
Click to expand...
Click to collapse
revized said:
i dont understand was i supposed to do something with that file inside the t.zip you posted ?
Click to expand...
Click to collapse
Yes.
Transfer the t.sh file in the t.zip file to the gTablet and then run it. All the necessary commands are listed.
Just use the correct directory in place of the C:\SOME\PATH, and do all the steps, 1-4, which are given.
OK I will try to do this, I am a n00b and was never able to use adb before when I tried along time ago. And now I have a xp. 64Bit pc and have a lot of troubles with small things I never did before. I can do this. LoL
rajeevvp said:
Yes.
Transfer the t.sh file in the t.zip file to the gTablet and then run it. All the necessary commands are listed.
Just use the correct directory in place of the C:\SOME\PATH, and do all the steps, 1-4, which are given.
Click to expand...
Click to collapse
i am back rajeevvp ! dont bail out on me , i am ready to get this thing done its been awhile although its time , this is all possible because of people like you and my son who says he wants to try and fix it !
( ps i am waaaay to n000bed to use adb ) but he even wants to dev andy apps so this may be a language he can understands just fine .
UPDATE: turns out He ummm. wwell hehe. decided wipe cache partition, part SD card, fix permissions, format boot, system, sd, data and cache. now upon normal boot up we (me my son and the gtab get magic value mismatch.lol
i was going to have him learn how to run adb stuff get your log and now i cant pout in the t.sh file because i assume it only allows transfering to sd card with normal boot up because i tried to put it on micro and cwm doesnt have a option to search for external sdcard, so now ummm ,upon searching for the magic value mismatch i found this article and seems very intense for a small person like me.
http://www.slatedroid.com/topic/19880-guide-restore-g-tablet-after-a-failed-recovery-mode-updatezip/
help!
Related
it keeps saying
formatting /data...
Error formatting /data!
I need to format data because I'm getting lots of system errors. Does anybody know how to fix this?
I'll need to see some logs to find out what's wrong. Boot the gTab into ClockworkMod, attach the USB cable to the tablet, and run these commands on your PC after you've tried to format data. Note that you must have adb set up for the commands to work.
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
C:\SOME\PATH> [B]adb pull /tmp/recovery.log reclog1.txt
[/B]C:\SOME\PATH> [B]adb pull /cache/recovery/log reclog2.txt[/B]
Post the dmesg.txt and reclog?.txt files here.
Sorry for being a noob, but where do I download the adb from?
bdds13 said:
Sorry for being a noob, but where do I download the adb from?
Click to expand...
Click to collapse
There is a guide for this.
Sorry I installed the adb, but I could never get it to recognize my device. I think im fine now, I had to repartition the sd card and it also wiped data so im fine for now. But I got so frustrated with the ABD I guess I had to spend more time on it, but oh well.
Finally I was able to wipe data. I had to re-partition the sd card to 2048M and then 0. After it partitioned I was able to wipe data with no errors.
If you repartitioned the (internal) SD card, then your /data was also formatted in the process--in fact, the entire SD card would've been reset to an original and empty state.
I'm curious now as to how the /data partition got so screwed up that even formatting it failed. Did you lose that partition somehow?
Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
There is a partition on the internal flash named "bootdata" that stores a files named BCB and BootCnt. The secure bootloader updates BootCnt on every non-sdcard boot and if it gets too high it will automatically boot into the recovery partition instead of the boot partition. So, if you're making any custom ROM to be run from the internal flash then you'll want to reset that file in a boot script somewhere. The shell command "dd if=/dev/zero of=/bootdata/BootCnt bs=1 count=4" would do it (Assuming you've mounted the bootdata partition )
The BCB file is similar in that if the secure bootloader boots into the recovery partition for any reason, it will write to that file and will always boot into the recovery partition until that file is cleared. The shell command to clear that file is "dd if=/dev/zero of=/bootdata/BCB bs=1 count=1088"
The bootdata partition just contains a standard vfat filesystem so you just mount it normally.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
bauwks said:
Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
There is a partition on the internal flash named "bootdata" that stores a files named BCB and BootCnt. The secure bootloader updates BootCnt on every non-sdcard boot and if it gets too high it will automatically boot into the recovery partition instead of the boot partition. So, if you're making any custom ROM to be run from the internal flash then you'll want to reset that file in a boot script somewhere. The shell command "dd if=/dev/zero of=/bootdata/BootCnt bs=1 count=4" would do it (Assuming you've mounted the bootdata partition )
The BCB file is similar in that if the secure bootloader boots into the recovery partition for any reason, it will write to that file and will always boot into the recovery partition until that file is cleared. The shell command to clear that file is "dd if=/dev/zero of=/bootdata/BCB bs=1 count=1088"
The bootdata partition just contains a standard vfat filesystem so you just mount it normally.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
Yup. On the NookColor these had the same functions. Lived on /rom instead of /bootdata however.
Note: My CWM image doesn't probably handle BCB or bootcnt yet (I do in my CM9 image but that is another thing )
nemith said:
Yup. On the NookColor these had the same functions. Lived on /rom instead of /bootdata however.
Note: My CWM image doesn't probably handle BCB or bootcnt yet (I do in my CM9 image but that is another thing )
Click to expand...
Click to collapse
My Ubuntu image does not mount this partition.
bauwks said:
Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
Yep-- this is all taken care of in cm9
Update: I don't think you mentioned, but for completeness, there's also the serial file in /rom at devconf/DeviceId that will trigger a rom reformat if it goes missing. there are also some edge conditions that will trigger recovery/flashing such as the presence of certain update.zip files on SD. Also SD boots are treated differently by default, don't increase the boot count, etc. In short, this is very similar to how NookColor works with the added disadvantage of having to deal with, rather than simply ignore or remove, these various "go to recovery' conditions.
I can verify that Bauwks script works and allows internal booting without a bootloop.
Nemith, if you find the time can you add something like this to your CWM recovery.img? I think just adding the /bootdata mount and dd calls to the init.rc file should work. I was going to build my own CWM .img but figured you already had the source code handy.
I'de like to dabble in a CM7 port soon, while CM9 and Ubuntu ports are in-work
Thanks for all your hard work guys!
CWM recovery bootloop
bauwks said:
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
I flashed cm9 alpha 0.2 on my nook tablet using the nook tablet recovery apk. It booted into cyanoboot, however it had an error message that said disc majic error. I noticed I had put the wrong boot image on my sd card from the alpha 0.1. I rebooted 8 times and booted into cwm. Now in cwm I flashed a backup of my tablet. I then made the common mistake of clicking reboot recovery. Then trying to fix the bootloop into cwm recovery while unaware of the sevarity of what I was doing I went into mounts and storage and formated each bootdata, cache, data, emmc, rom, and system. I just restored my backup again and now I know what I need to do. My stock Nook recovery was overwriten when I clicked reboot recovery. Also I formated my rom folder and that might have contained my serial number and info.
I basicaly deleted my partions. while stuck in the cwm boot loop. Can you please send me or send me the link to a step by step way that I can get my nook tablet 16gb stuck in the cwm boot loop back to normal.
I tried using fastboot but I dont know the commands to open it. Also I dont know how to use adb either. I have a 2gig, and a 256 mb micro sd. I have a windows pc. Can you show me step by step how to restore those partions, how to do it on adb or fastboot, or the update zip method. I need help as soon as possible. Thanks.
Its similar to this
This seems like the only place folks are looking at bcb in much detail, so I thought I'd post an observation: on the simple touch, if you boot from noogie after issuing an "erase and deregister" command from the OS, the bcb file contains command strings.
I don't know what reads the strings, but after erase and deregister, bcb seems to be used to tell the device to run recovery:
recovery --wipe_data
is an ascii string from bcb on a deregistered and not yet rebooted glowworm - I put the noogie disk in, did the erase and deregister, then dumped the partitions once it came back up.
the command flags available in recovery as of cupcake are documented at
http://www.netmite.com/android/mydroid/cupcake/bootable/recovery/recovery.c
Just wanted to bump this so more people know about it, because I didn't and I reformat my /bootdata.
Can anyone make an image of it for restore purposes?
An image of /factory would be nice as well But less important as we're all (likely) using CM.
edit
Actually disregard this.. I have the nook hd+, but the /bootdata format info will probably be handy for any nook device.
Don't format bootdata or factory!
roustabout said:
This seems like the only place folks are looking at bcb in much detail, so I thought I'd post an observation: on the simple touch, if you boot from noogie after issuing an "erase and deregister" command from the OS, the bcb file contains command strings.
I don't know what reads the strings, but after erase and deregister, bcb seems to be used to tell the device to run recovery:
recovery --wipe_data
is an ascii string from bcb on a deregistered and not yet rebooted glowworm - I put the noogie disk in, did the erase and deregister, then dumped the partitions once it came back up.
the command flags available in recovery as of cupcake are documented at
http://www.netmite.com/android/mydroid/cupcake/bootable/recovery/recovery.c
Click to expand...
Click to collapse
pbassjunk said:
Just wanted to bump this so more people know about it, because I didn't and I reformat my /bootdata.
Can anyone make an image of it for restore purposes?
Click to expand...
Click to collapse
To fix the Recovery Boot Loop caused by invalid/missing BCB and BootCnt in /bootdata, flash Succulent's flashable_fix_bootloop.zip posted at his blog http://iamafanof.wordpress.com/2013...-1-jellybean-sdcard-img-for-nook-tablet-0110/ (see under heading "I am stuck in a recovery boot loop?").
An image of /factory would be nice as well But less important as we're all (likely) using CM.
Click to expand...
Click to collapse
/factory contains a backup copy of stock ROM as well as a backup copy of the device data in /rom partition (romdata.zip), the latter includes data that is unique to each Nook (such as MAC address, security certificate, etc.) and hence is not replaceable with a copy from another Nook.
...
Don't format bootdata or factory!
Click to expand...
Click to collapse
Nor /romdata. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more info.
I created a flashable zip as well, which should reset that partition to a stock (zero-count) state. Hopefully it's not unique per device (I don't think it is, as I've used this successfully on two distinct devices.)
Is a fix being baked into any official roms, CM and the like? I don't mind the workaround via scripting, but the two I bought and modded I gave as gifts, so when they break (they both have) I definitely hear about it and receive the units back again for fixing.
ZIP is attached. Please let me know if it works or doesn't work for you, should you end up using it.
weasel5i2 said:
I created a flashable zip as well, which should reset that partition to a stock (zero-count) state. Hopefully it's not unique per device (I don't think it is, as I've used this successfully on two distinct devices.)
Is a fix being baked into any official roms, CM and the like? I don't mind the workaround via scripting, but the two I bought and modded I gave as gifts, so when they break (they both have) I definitely hear about it and receive the units back again for fixing.
ZIP is attached. Please let me know if it works or doesn't work for you, should you end up using it.
Click to expand...
Click to collapse
Having trouble with the /bootdata/BCB/ and my nook hd+ booting into recovery. Am I just supposed to flash the fix to the SD card boot partition?
tinkering said:
Having trouble with the /bootdata/BCB/ and my nook hd+ booting into recovery. Am I just supposed to flash the fix to the SD card boot partition?
Click to expand...
Click to collapse
You might want to see leapinlar's tip #10 in his post http://forum.xda-developers.com/showpost.php?p=35811322&postcount=1 for the Nook HD/HD+.
digixmax said:
You might want to see leapinlar's tip #10 in his post http://forum.xda-developers.com/showpost.php?p=35811322&postcount=1 for the Nook HD/HD+.
Click to expand...
Click to collapse
Thanks for the link to leapinlar's post. That helps me to understand the problem and fix a bit better. I didn't see the zip that seemed to fit my situation on his post. I did a SD install non-rooted and I see only only emmc fixes on his post. I tried your fix with these steps and I must have done something wrong. Maybe you could point me in the right direction.
DL, unzip, write image to sd using PC(could only write the .img, don't know what to do with the folder) , put SD into nook HD+, try to boot= no boot
Does the device have to be rooted to flash the repair zip? I don't think I am utilizing the fix properly.
tinkering said:
...
DL, unzip, write image to sd using PC(could only write the .img, don't know what to do with the folder) , put SD into nook HD+, try to boot= no boot
Does the device have to be rooted to flash the repair zip? I don't think I am utilizing the fix properly.
Click to expand...
Click to collapse
No, the device does not have to be rooted to get flashed.
If this is your first time trying to boot off SD, it's possible that your HD+ is one of the units that have difficulty booting off SD card -- see http://forum.xda-developers.com/showthread.php?t=2288688.
Is your device still on stock ROM and stock Recovery?
digixmax said:
No, the device does not have to be rooted to get flashed.
If this is your first time trying to boot off SD, it's possible that your HD+ is one of the units that have difficulty booting off SD card -- see http://forum.xda-developers.com/showthread.php?t=2288688.
Is your device still on stock ROM and stock Recovery?
Click to expand...
Click to collapse
Sorry, I probably should have updated my last post. I was attempting to flash the repair incorrectly. Unfortunately, I have a new problem and have moved my question to the "[Q][Panic] HD+ won't boot, can access CWM SD but can't mount sdcard or emmc" thread.
The device would boot from SD. Was running CM10.2 and CWM recovery. The trouble I am having now is that I can't flash anything from the SD in CWM recovery because it wont mount the SD. (See details in thread referenced above.)
Thanks
Hello, fellow gTablet users!
I'm kinda newbie here, so first of all my apologies to everyone if that was already asked, 'cause I did some research on the matter and couldn't find all the necessary info for solving my particular issue.
Ok, so here's the deal. I was using my gTab for about half-year now. When I received it, I installed VeganTab-7 Ginger Edition on it (thanks for the devs - very nice ROM!) and it worked flawlessly until yesterday. But then something not good happened and the tablet stopped booting. Now it starts from birds screen, goes on to G-Tabdevs screen, after which VeganTab GingerEd boot screen appears, it has flashing letters for a couple of seconds and then tablet goes black and tries to boot again. I guess it's a boot loop so it's kinda soft brick and I'll have to do wipe data/factory reset through CWM to solve the issue. So this isn't the biggest problem - I've already found all the instructions.
The real problem is that I didn't make backup of my data (guilty!), but I don't want to lose some of it, especially the browser data. I was using Opera Mobile, so I guess that its data should be on /data partition. So I'll need an advice on how I can dump the necessary data before doing factory reset!
I've already tried connecting to desktop, using guide from this (http://forum.xda-developers.com/showthread.php?t=1010943) thread (third method from it), but it didn't work, at least on my Win7 Pro x64 SP1: the tablet shows as removable disk, but I can't access it. I tried to mount /data or /sdcard partitions through CWM recovery menu, but it tells me that it can't find /dev/block/... - I guess that's block device, associated with those partitions. So what are my best options of backuping data?
And the last question: I'll probably install some other ROM just to try something different, but unfortunately I don't remember what loader I have. I'm nearly sure that I installed VeganTab for 1.1, 'cause I did it back in May 2011 and there wasn't one available for 1.2 yet. But just to make sure: how can I find my loader version before I do reset? Or maybe I just have to do the reset and look for it when back on stock ROM?
Seriously, guys, doesn't anybody know how to solve these problems?
Boot into CWM first, then try mounting both /data and /sdcard using the CWM menu. Note down the exact error message displayed in each case. Then connect the USB cable and run these ADB commands on your PC:
Code:
C:\> [B]adb shell dmesg >dmesg.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk3 > fdisk.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk2 >> fdisk.txt[/B]
Post the error messages and those 2 .txt files here.
Thank you for reply, rajeevvp.
When I'm trying to mount /data and /sdcard it says respectively:
Code:
E:Can't mount /dev/block/mmcblk3p2
(No such file or directory)
Error mounting DATA:!
E:Can't mount /dev/block/mmcblk3p1 (or /dev/block/mmcblk2p1)
(No such file or directory)
Error mounting SDCARD:!
Unfortunately I didn't have ADB installed. Now I'm trying to use the guide from here: http://forum.xda-developers.com/showthread.php?t=902860, but fail on step 4, cause there is nothing like "Nvidia harmony" appearing under other devices in my dev manager, just "Nvidia Tegra 2 USB Device" under Disk Drives and "USB Mass Storage Device" under Universal Serial Bus Controllers. I guess these devices are gTablet's internal memory presented as disk drive...
I'll try to install ADB and then write back how it worked.
Interesting error messages. Now I really have to see those text files.
If you're having problems installing ADB on Windows, try using Linux.
Ok, thanks you very much! I'll try that, but unfortunately tomorrow, as it's already too late here.
Btw, I read your post about linux - you're suggesting Knoppix Live CD there. Is it mandatory to use it? I mean I already have PartedMagic live CD burned, maybe I could use it instead...
anary said:
I mean I already have PartedMagic live CD burned, maybe I could use it instead...
Click to expand...
Click to collapse
If sudo and adb work, then no problem.
rajeevvp said:
Boot into CWM first, then try mounting both /data and /sdcard using the CWM menu. Note down the exact error message displayed in each case. Then connect the USB cable and run these ADB commands on your PC:
Code:
C:\> [B]adb shell dmesg >dmesg.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk3 > fdisk.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk2 >> fdisk.txt[/B]
Post the error messages and those 2 .txt files here.
Click to expand...
Click to collapse
Ok, I finally managed to do it. Sorry for the delay.
The files are attached. Did everything how you told me.
Actually I don't think that I understand too much in Android inner mechanics But having looked through these files, I thought that inner sdcard device (mmcblk3) doesn't seem to produce any strange behavior...
Btw, thanks a lot for your advice about using Knoppix - it's really very easy and handy!
anary said:
But having looked through these files, I thought that inner sdcard device (mmcblk3) doesn't seem to produce any strange behavior...
Click to expand...
Click to collapse
You have lost your /data partition altogether. You are supposed to have 2 partitions on that internal SD card: a 14GB FAT32 partition and a 2GB ext3 partition. You only have a single FAT32 partition spanning the entire SD card now.
I may be able to help you get both partitions back if you give me these details:
1. How and when did this happen?
2. Current ROM.
3. Current version of CWM.
4. Did you try to repartition the (internal) SD card recently?
5. Have you ever repartitioned the internal SD card? If yes, then using which version of CWM?
6. After you noticed the problem what steps did you take to fix the problem?
Yeah, I remember I was curious where it stores OS's kernel if all it has is FAT32 partition - now I get it...
Ok, here are the details:
1. I don't really know what has happened, but I guess that it happened when I tried to use tablet like cardreader for microsd card. During that I sort of formatted external sd - maybe that actually was internal memory? I checked through file manager though, and all the files seemed intact...
2. VeganTab GingerEd from this thread: http://forum.xda-developers.com/showthread.php?t=1031250. I'm pretty sure that I didn't install anything except for it.
3. Don't know. But it says ClockworkMod Recovery v2.5.1.1-bekit-0.8 in recovery menu, so I guess its version is maybe 0.8.
4. No I didn't, at least intentionally.
5. I think I did it just once, when installing the ROM. I'm pretty much sure that I used this instructions for repartitioning: http://viewsonic-gtablet-for-dummies.webs.com/repartition.htm (not exactly this, but I did the same as it's written there). To install the ROM I used the instructions from the ROM thread, mentioned above. I didn't whant to do a lot of modding, just wanted the device to work at least better than with stock ROM, so didn't try to change any other low-level things.
6. I just tried to mount partitions through CWM recovery and I tried wiping out cache partition and Dalvik cache. Nothing else.
anary said:
Yeah, I remember I was curious where it stores OS's kernel if all it has is FAT32 partition - now I get it...
Click to expand...
Click to collapse
The OS kernel is not stored on the SD cards. They're stored on a "boot" partition on the NAND flash. And, if the OS was messed up you would get hung up on the initial splash screen (the one with the 3 birds)--you wouldn't go into a boot loop.
1. I don't really know what has happened, but I guess that it happened when I tried to use tablet like cardreader for microsd card. During that I sort of formatted external sd - maybe that actually was internal memory?
Click to expand...
Click to collapse
That's what caused this problem. CWM-2.5.1.1-bekit-0.8 does not work on the external SD card (but, CWM-2.5.1.3 and CWM-4.0.1.5 do).
Did you format the internal SD card using CWM?
I checked through file manager though, and all the files seemed intact...
Click to expand...
Click to collapse
Files where? The internal SD card or the external one? And, how did you check this? After formatting the internal SD card, the very next boot into the ROM would've put you into a boot-loop because the /data partition is missing.
I think I may be able to get stuff from /data, but, everything on /sdcard is most likely gone. (Actually, the files are most likely all there, but, without direct access to the tablet, it's very difficult to get the retrieve any of them.) Just don't touch the tablet until I've figured out the commands you will have to use.
That's what caused this problem. CWM-2.5.1.1-bekit-0.8 does not work on the external SD card (but, CWM-2.5.1.3 and CWM-4.0.1.5 do).
Did you format the internal SD card using CWM?
Click to expand...
Click to collapse
No, I was going to format external SD card and I tried to do it through Android (or maybe VeganTab) menu. I think that doing this, I could accidentally format internal SD, but I'm not sure this could be done from within the OS. During the same logon session I checked files on internal SD with file manager and all of them were where they should have been. So I thought that all was ok. But when I rebooted next time, it wasn't booting... That's why I told you that maybe it was because of formatting.
And just to be clear: I didn't do anything using CWM after it stopped booting, apart from wiping system and Dalvik caches.
Do you have a large capacity micro SD card (anything larger than the maximum amount of data that's currently on the internal SD card) that you can use to save retrieved data into?
rajeevvp said:
Do you have a large capacity micro SD card (anything larger than the maximum amount of data that's currently on the internal SD card) that you can use to save retrieved data into?
Click to expand...
Click to collapse
Yep. Won't be any problem.
anary said:
Yep. Won't be any problem.
Click to expand...
Click to collapse
OK. Format that micro SD to contain a single DOS partition; then we'll proceed.
rajeevvp said:
OK. Format that micro SD to contain a single DOS partition; then we'll proceed.
Click to expand...
Click to collapse
Ok. That's done.
Boot into CWM, go into the "mounts and storage" menu, unmount all mounted partitions, connect the USB cable, and run these commands using ADB--do not back out of that "mounts and storage" menu while we're fixing this. We're trying to see if the data on the current /sdcard partition can be retrieved.
Code:
$ [B]adb shell[/B]
~ # [B]mount -r /dev/block/mmcblk3p1 /sdcard[/B]
~ # [B]ls -l /sdcard[/B]
If the ls listing looks OK, then we force a filesystem check before copying the data to the external micro SD card:
Code:
~ # [B]mount -r /system[/B]
~ # [B]umount /sdcard[/B]
~ # [B]/system/bin/fsck_msdos -f -y /dev/block/mmcblk3p1[/B]
If the listing doesn't look OK, then the data on /sdcard is lost.
Post the exact output of each command.
Ok, mount says this:
Code:
mount: mounting /dev/block/mmcblk3p1 on /sdcard failed: Invalid argument
and ls after that gives no output - I think it shouldn't give any, 'cause I didn't mount anything...
Does this mean I'm screwed?
Try this mount command:
Code:
~ # [B]mount -r -t vfat /dev/block/mmcblk3p1 /sdcard[/B]
The same result.
I think I stupidly posted this in the General forum, so hopefully I'll have better luck here. Here's what I wrote before:
Hi, I'm trying to unbrick USB on my Atrix using this guide: http://forum.xda-developers.com/showthread.php?t=751265 but every time I try and use the fastboot command 'fastboot oem enableqxdm 0' I get 'FAILED error:00120000'.
I am really tearing my hair out! failing this, would flashing via fastboot fix this error? I tried reflashing using fastboot with the CM9 ROM I had handy but adb didn't like it (my installation is borked you see, I can get into recovery but can't reflash the ROM 'cause my sc cards can't be read...so I'm in a bit of a vicious circle here).
If anyone can help I would be so grateful.
Which recovery are you using atm?
Hey,
I'm using ROM Racers custom ROM, from here: http://forum.xda-developers.com/showthread.php?t=1204500
Would that make a difference?
That's a recovery, not a ROM. derp
Just messing with ya. But if you have Romracer's recovery you should be able to mount your storage from within recovery. There should be a "mounts & storage" option in the menu. That should allow your computer to read the card and/or internal as usb storage. Or, if you have a card reader you can put the necessary files on your sd card that way.
markdjj said:
Hey,
I'm using ROM Racers custom ROM, from here: http://forum.xda-developers.com/showthread.php?t=1204500
Would that make a difference?
Click to expand...
Click to collapse
live4nyy said:
That's a recovery, not a ROM. derp
Just messing with ya. But if you have Romracer's recovery you should be able to mount your storage from within recovery. There should be a "mounts & storage" option in the menu. That should allow your computer to read the card and/or internal as usb storage. Or, if you have a card reader you can put the necessary files on your sd card that way.
Click to expand...
Click to collapse
Yeah thanks but I know this...Ok, here is my problem: I can't mount the internal or external card in recovery, it comes up with ERROR: can't mount / emmc and Error: can't mount / sdcard . I can't mount either card on the PC either and as described in trying to fix the USB connectivity it comes up with the 0x120000 described above in fastboot. On top of that the installation of my ROM is borked (which was Jokersax's ICS beta but I have several others on file I could use)...so I can't reflash the handset. ALL I can do is get into recovery - and a fat lot of good that is doing me!
On top of all that, the reason I ended up like this seemed to be when I erased the internal memory card from my Mac...and this was out of pure frustration fro the mysterious random reboot issue, for which I'd tried almost everything else. But one step at a time eh?
So if anyone can help I'd be really glad right now...
Do you have a card reader? Have you tried formatting the sd card (either through recovery or through the computer using "mounts & storage")? Do you have another sd card that you can try?
Can you be more specific as well? When exactly are you getting the "error" and have you tried "mount usb storage" option in "mounts & storage"? Do you only have a Mac or do you have access to a Windows computer?
markdjj said:
Yeah thanks but I know this...Ok, here is my problem: I can't mount the internal or external card in recovery, it comes up with ERROR: can't mount / emmc and Error: can't mount / sdcard . I can't mount either card on the PC either and as described in trying to fix the USB connectivity it comes up with the 0x120000 described above in fastboot. On top of that the installation of my ROM is borked (which was Jokersax's ICS beta but I have several others on file I could use)...so I can't reflash the handset. ALL I can do is get into recovery - and a fat lot of good that is doing me!
On top of all that, the reason I ended up like this seemed to be when I erased the internal memory card from my Mac...and this was out of pure frustration fro the mysterious random reboot issue, for which I'd tried almost everything else. But one step at a time eh?
So if anyone can help I'd be really glad right now...
Click to expand...
Click to collapse
Ok, I cannot mount the sd card in any way, either through recovery or on the PC.* the SD card is fine as it the phone registered the card as empty (and read the empty card fine) until it started refusing to read anything at all.* Mount USB storage option definitely does not work (it was working and then it stopped)
*
The error comes from trying the USB unbrick solution (link in my original post at the top)...in fastboot I am trying 'fastboot oem enableqxdm 0' and then in red writing the ERROR 0x120000 (or whatever it was, it's above) appears on the screen of the Atrix and in the command line box on the PC (I am using my windows 7 laptop for all this btw, don't want to confuse you with my mentioning of the Mac above).
*
So...I either need a way to flash from Fastboot so I can get a working system again at least AND/OR I need to fix the USB connectivity (so I can mount the internal/external card on my PC) and fix the mounting in the Atrix itself.* If I can fix the mounting issue (both mounting within Recovery and mounting on the PC) I can then reflash (and use my SD cards again).
*
Any ideas?
I would think reflashing a newer recovery fron fastboot might help you with your problem if your current recovery is borked. (CWM 5.8.1.8 maybe?)
Ok, so I have installed the CMW touch recovery over fastboot...and I can now mount the external SD card. I have also managed to erase the external SD card using fastboot (fastboot erase sdcard) but the phone still can't see it. The internal memory is untouchable either through recovery or fastboot
markdjj said:
Ok, so I have installed the CMW touch recovery over fastboot...and I can now mount the external SD card. I have also managed to erase the external SD card using fastboot (fastboot erase sdcard) but the phone still can't see it. The internal memory is untouchable either through recovery or fastboot
Click to expand...
Click to collapse
Try a fastboot -w command and flash a new ROM from the external see if it works. It would be easier if we knew what caused you to have this problem...
Right, some good news...I have managed to partition my SD card from recovery (only to 4 gigs though but it's a start...), managed to put my and now I am rebooting as I type...although it's taking a long time to reboot...
Maybe I should do a fastboot -w first
littleemp said:
Try a fastboot -w command and flash a new ROM from the external see if it works. It would be easier if we knew what caused you to have this problem...
Click to expand...
Click to collapse
Yeah it's still not booting, even though I installed the rom from recovery.
Thinking back my troubles started when a) I wiped both the internal and external to fat 32 from my Mac and then b) I converted all file systems to ext4 from the advanced menu. Yeah, that may be it...
markdjj said:
Yeah it's still not booting, even though I installed the rom from recovery.
Thinking back my troubles started when a) I wiped both the internal and external to fat 32 from my Mac and then b) I converted all file systems to ext4 from the advanced menu. Yeah, that may be it...
Click to expand...
Click to collapse
Yep... that'll do it.
littleemp said:
Yep... that'll do it.
Click to expand...
Click to collapse
So...in order to fix this, can I simply reformat from a Linux box?
markdjj said:
So...in order to fix this, can I simply reformat from a Linux box?
Click to expand...
Click to collapse
to be honest... no clue. I really never thought of messing with the partitions like that.
Hey Guys,
I have always used CWM Rom Manager but now it only bricks the phone when installed. "Encryption Error - Factory Reset", but that does not work, have to use AP Fastboot and reinstall JellyBean. Now that I have it up again, I want a recovery solution besides Titanium Backup that will backup the entire phone, like CWM did. So, I installed SafeStrap. (Rooted with Android 4.1.2)
Now I would like to format the internal SD Card to start fresh, but when I boot to recovery in SafeStrap, Wipe does not format the internal card. The terminal window in the Wipe action shows that it cannot find block device. But, the File Manager in recovery works just fine and the backup seemed successful. When I go to Advanced, Settings, there is one setting that cannot be unchecked. "Use rm -rf instead of Format?" No, I do not want to wipe the existing partition, I want to format the entire internal SD partition, so I do indeed want Format like CWM would do. Is there a way to uncheck this box and how do you do it?
SafeStrap does have a Terminal, use at your own risk. So do I need to Format the internal SD Card by command line? Command line Syntax, please? Since this is a deadly serious operation, I would hope to get an answer and someone to confirm it, if possible. Familiar with Linux so that might help.
Anyone can help, please?
Update:
I checked out the SafeStrap Terminal. It is very, very crude, does not display much information like a Linux shell would. I can enter parted or at least the command echos to the screen, but the print command does not even show the partitions on the block device for the Internal SD Card, /dev/block/mmcblk1p25. There must be a better way...
I think you have to go to the SLOT like the ROM-SLOT-1 to do this.The stock rom slot dosent allow you to format or wipe anything.
Sent from my XT910 using xda app-developers app