Hey guys,
unfortunately i think i bricked my prime
Today i flashed crombi-kk rom which worked flawlessly fine. I came from HairyBean 2.31 so all i did was to up update my TWRP via fastboot and then flash the rom. As said, that worked fine. After my first boot of the rom i thought that i would like to test the "F2FS" option. For this i updated TWRP to v2.8 via the zip-file from this thread: http://forum.xda-developers.com/showthread.php?t=2772093 . This also worked and i've got my TWRP to the new version.
Now i wanted to format the /data partition to F2FS so i went to
Wipe>>Advanced Wipe>>Choose Data>>Repair or Change File System>>Change File System>>F2FS
At this time it told me that it can't UNmount the partition and therefore it couldn't change the file-system.
Dumb as i am i thought: "Okay, then why don't just unmount the partition" so i did this (Mount>>Disabled "Data") an then retried to format the data partition with f2fs. During this process i have to assume that something went wrong? It gave me some error which i fool can't remember.
From this point i couldn't access the /data partition anymore, i can't mount it nor can i boot into Android.
I still have access to TWRP and can get to fastboot access. I have no ADB Access in TWRP - it just can't recognize the prime. In Windows-Hardware Manager it just says: Transformer?! (i have universal naked driver installed)
Forget the last sentence - it seems that my USB-Cable is partly broken. Sometimes it recognizes the prime and sometimes not!
Is it gone forever or is there still hope to recover it?
Hopefully someone can help me, i'm really desperate
P.S.: D didn't want to make things worse, so i stopped messing around with it - would it help to reflash the ne0zone75_tf300t.blob file? Is this even possible if i already updated the TWRP to a newer version?
NiffStipples said:
I still have access to TWRP and can get to fastboot access.
Click to expand...
Click to collapse
As long as this is the fact, we don' t call it 'bricked'.
Try following one after another:
1. TWRP>>Wipe>>Advanced>>[check / data]>>repair file system, flash ROM again.
2. Fastboot:
Code:
fastboot -i 0x0b05 erase userdata
- then flash ROM again.
3. Last ressort: Flash stock ROM and start from scratch.
... hope you've pulled your nvflash files. Good luck!
... you might also want to flash another TWRP, though ne0zone75's normally works well. Try the official 2.8.3.0 (for tf300t because you are on Hairy Bean), works good with my prime.
Thanks a lot for your reply
I've tried the steps you provided:
1) While repairing the data partition it said again that it can't mount the data partition. (Picture of it in the attachment)
2) Reflasing the rom worked okay but as expected it couldn't boot (stuck in bootscreen) - in TWRP the /data partiton was again unmountable
3) erasing the userdata via fastboot gave me the following:
Code:
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
At this time i didn't tried to reflash the rom because i don't think it would change anything?!
4) i only have the old nvflash files from ages ago when i started flashing with androwook - i fear they are the wrong ones? I don't have any clue what to do with these - are there good instructions to get the tab back to it's factory state?
Last but not least - do you have a link for the right TWRP you're talking about. I don't want to gave the wrong one a try
NiffStipples said:
Thanks a lot for your reply
I've tried the steps you provided:
1) While repairing the data partition it said again that it can't mount the data partition. (Picture of it in the attachment)
2) Reflasing the rom worked okay but as expected it couldn't boot (stuck in bootscreen) - in TWRP the /data partiton was again unmountable
3) erasing the userdata via fastboot gave me the following:
Code:
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
At this time i didn't tried to reflash the rom because i don't think it would change anything?!
Click to expand...
Click to collapse
Sounds as if partition table is faulty.
1. You could try to redo the Hairy Bean procedure.
2. If you feel lucky, then you could try to format partition manually using
Code:
mkfs.ext4 /dev/block/mmcblk0p8
4) i only have the old nvflash files from ages ago when i started flashing with androwook - i fear they are the wrong ones?
Click to expand...
Click to collapse
nvflash files don't grow sour; you could try without changing to wheelie your blob.bin. If it works, you are safe and can continue with the other blobs.
I don't have any clue what to do with these - are there good instructions to get the tab back to it's factory state?
Click to expand...
Click to collapse
Best instruction you find here: http://forum.xda-developers.com/showthread.php?t=1894867
Last but not least - do you have a link for the right TWRP you're talking about. I don't want to gave the wrong one a try
Click to expand...
Click to collapse
I have actually the (official) one from http://www.techerrata.com/browse/twrp2/tf300t
Good Luck!
Okay, now i know why they always say that flashing is nothing for noobs
I'm a little bit confused - what (in your opinion) is the best shot i should give a try?
Formatting manually (from where? In TWRP or via adb? I'm on Windows)
Reflash everything with NVFLASH (is that possible without any hassle - the NVFLASH files are from ICS-times and i'm on JB/KK?!)
I know it's annoying to help someone who doesn't know what he's doing - hope you have time to get me through this flashing nightmare :/
NiffStipples said:
Okay, now i know why they always say that flashing is nothing for noobs
Click to expand...
Click to collapse
Everybody starts as a noob.
I'm a little bit confused - what (in your opinion) is the best shot i should give a try?
Formatting manually (from where? In TWRP or via adb? I'm on Windows)
Click to expand...
Click to collapse
I would first do that manually from TWRP>>Advanced>>Terminal Command>>Select Folder (root)>>type in: mkfs.ext4 /dev/block/mmcblk0p8
Reflash everything with NVFLASH (is that possible without any hassle - the NVFLASH files are from ICS-times and i'm on JB/KK?!)
Click to expand...
Click to collapse
Important is, that blob.bin works with
Code:
wheelie.exe -r --blob blob.bin
After that you should flash 'bricksafeTF201.img' and 'unlock-token-TF201'. Then you can flash any blobs of unblobbed ROMs you can find in the internet or flash stock ROM (JB). Then proceed to fastboot custom recovery and zipflash custom ROM.
I know it's annoying to help someone who doesn't know what he's doing - hope you have time to get me through this flashing nightmare :/
Click to expand...
Click to collapse
I went through any misstep you can think of with the three of 'em: TF201, TF300T, TF700T.
Mmmmh, the command
Code:
mkfs.ext4 /dev/block/mmcblk0p8
gives me back:
Code:
mkfs.ext4: not found
NiffStipples said:
Mmmmh, the command
Code:
mkfs.ext4 /dev/block/mmcblk0p8
gives me back:
Code:
mkfs.ext4: not found
Click to expand...
Click to collapse
Oops! My bad, try
Code:
make_ext4fs /dev/block/mmcblk0p8
.
.... for information's sake type
Code:
fdisk -l /dev/block/mmcblk0p8
You should get
Code:
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Hooray! :victory: Thanks a lot - everything is back where it belongs
Just for the learning effect - do you have any idea what did go wrong in my case and how would i correctly change the format of the data partition to f2fs? I think i've read a lot of times that this would improve rom speeds a lot?!
NiffStipples said:
Hooray! :victory: Thanks a lot - everything is back where it belongs
Just for the learning effect - do you have any idea what did go wrong in my case and how would i correctly change the format of the data partition to f2fs? I think i've read a lot of times that this would improve rom speeds a lot?!
Click to expand...
Click to collapse
Congrats!
If you would care to tell what you did last, one could make a guess, what went wrong.
... and yes, changing /data (only!) to f2fs makes a tremendous difference in speed. Normally TWRP complies the job without probs. What TWRP do you have now?
I prefer @ne0zone75's which I linked some posts before. They work on all my tabs.
I have installed v2.8.3.0 from the site you gave me above
Mh, as said in the first post i did the following steps to change the format
I tried Wipe>>Advanced Wipe>>Checked "Data">>Repair or Change File System>>Change File System>>Choose F2FS
Then the system gave me an error that it couldn't access the partition because it was mounted or couldn't be unmounted or something like this
So i went back to Mount>>unchecked "Data"
And then again to Advanced Wipe>>...>>Change File System>>F2FS
After that something went wrong because after that step i couldn't mount the data partition anymore?!
NiffStipples said:
I have installed v2.8.3.0 from the site you gave me above
Mh, as said in the first post i did the following steps to change the format
I tried Wipe>>Advanced Wipe>>Checked "Data">>Repair or Change File System>>Change File System>>Choose F2FS
Then the system gave me an error that it couldn't access the partition because it was mounted or couldn't be unmounted or something like this
So i went back to Mount>>unchecked "Data"
And then again to Advanced Wipe>>...>>Change File System>>F2FS
After that something went wrong because after that step i couldn't mount the data partition anymore?!
Click to expand...
Click to collapse
Yes, but what did you to fix it then?
Oh sorry, now i get it
I just used your command for repartitioning(?!?): make_ext4fs /dev/block/mmcblk0p8
I am still of two minds of f2fs on these tablets.. Just gone back to ext4 to compare... As was getting to sticky on the F2fs with redraws and lag..
Anyway good to hear a successful conclusion on the come back by the OP
NiffStipples said:
Oh sorry, now i get it
I just used your command for repartitioning(?!?): make_ext4fs /dev/block/mmcblk0p8
Click to expand...
Click to collapse
Good! Glad, it helped you. Now you could try the 'mkfs.f2fs' command also.
Already tried that - this time it worked without problems :highfive:
Thanks again for the great help!! F2FS brings the prime to a whole new level, now i just have to figure out how to change the dock layout language
NiffStipples said:
Already tried that - this time it worked without problems :highfive:
Thanks again for the great help!! F2FS brings the prime to a whole new level, now i just have to figure out how to change the dock layout language
Click to expand...
Click to collapse
That should be no problem. If you click in dock, there should be a keyboard icon in notification area, clicking it settings dialog will appear. Additional in settings>>language and input>>physical keyboard you can set keyboard layout of dock.
das chaos said:
Oops! My bad, try
Code:
make_ext4fs /dev/block/mmcblk0p8
.
.... for information's sake type
Code:
fdisk -l /dev/block/mmcblk0p8
You should get
Code:
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Click to expand...
Click to collapse
DC,
I wonder if this is why my f2fs where playing up for me?
using your commands I get the following..
Code:
[email protected]:/ $ su
[email protected]:/ # fdisk -l /dev/block/mmcblk0p8
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
[email protected]:/ #
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
this is what I am looking at as a problem maybe?
is there a terminal command to see all the partitions and sizes?
I might have to take this thing back to scratch and start again as been flashing left right and center on it of late.
dgcruzing said:
DC,
I wonder if this is why my f2fs where playing up for me?
using your commands I get the following..
Code:
[email protected]:/ $ su
[email protected]:/ # fdisk -l /dev/block/mmcblk0p8
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
[email protected]:/ #
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
this is what I am looking at as a problem maybe?
is there a terminal command to see all the partitions and sizes?
I might have to take this thing back to scratch and start again as been flashing left right and center on it of late.
Click to expand...
Click to collapse
No that's normal for f2fs, only fat systems have readable PT. What I was interested was geometry of fs and that is the same as mine. So everything is o.k. You have your tab up and running - that counts.
There is a free app Storage Partitions in the store, which can do no more than show information about partitions. Mainly an exploit of commands
Code:
cat /proc/mounts
and
Code:
cat /proc/partitions
das chaos said:
No that's normal for f2fs, only fat systems have readable PT. What I was interested was geometry of fs and that is the same as mine. So everything is o.k. You have your tab up and running - that counts.
There is a free app Storage Partitions in the store, which can do no more than show information about partitions. Mainly an exploit of commands
Code:
cat /proc/mounts
and
Code:
cat /proc/partitions
Click to expand...
Click to collapse
Used that one and another to have a look..
This is what I get, just for the hell of it..
As said for me.. F2Fs on this one doesn't play nice and the last few days I am back to Ext4..
Running it in and let it settled, putting it through its paces with plenty of tabs in chrome open and multitasking back and forwards in to Tapatalk and it runs normal with out lag and redraws..
I am using apex as a launcher and under F2Fs with kept in memory set..it was redrawing to the max and timing out from coming out of sleep..
Playing with other tweaks to see if can get it to a sweet spot.
Will let it settle for a few days and play then swop back and see which is better with the tweaks added
Related
hi, i recieved a eris from a friend of mine with the intentions on fixing it and using it. when i power it on there's just a black backlit screen.. no splash, nothing. if i plug usb in it goes to a htc screen with 4 triangles in the corners. i've tried the ruu update and it gives an 110 error at the end saying something about files not found, i unhooked the usb and it went to a white screen with hboot 1.49 , n s-on n all that stuff.. and it showed info from the ruu, and it showed that the system and boot(or recovery, i cant remember exactly) failed and they were red. i can connect with fastboot but not with adb.. is there anything i can do to atleast get the phone working.. fastboot oem boot doesnt work for me, it just gives a long list of errors
fastboot will do nothing useful for you if you have the 1.49.0000 S-ON bootloader.
The basic definition of a brick for the Eris is this:
1.49.0000 S-ON bootloader + no recovery + non-booting OS = brick
So, let's review.
1) You have 1.49.0000 S-ON. There is no PB00IMG.zip available to you that can change that using Hboot (without performing some magic with a custom recovery first), and fastboot is worthless with S-ON. So, no go there.
2) You didn't mention (or your description was lacking detail) what happens when you try to go into the Hboot menu (cold start with Vol-Down+End). From there you might be able use the menu to try to launch the recovery boot, to see whether (a) it is the stock recovery, (b) it is a custom recovery, or (c) it fails to start. You should try that next.
If that doesn't work, try a cold start with Vol-Up + End. (You need to keep holding both the buttons down until the screen lights up). That is an alternate way to get to the recovery (when a 1.49.xxxx bootloader is on the phone).
If you have a "stock" recovery, you will see a splash screen with an image of the phone and a triangle with an exclamation point in it. (Pressing Vol-Up+End after you see that splash screen will show a blue menu). If you have Amon_RA's custom recovery, you will see a green menu.
3) If your kernel boots, but the OS is "hanging", there is a remote possibility that you can initiate a factory reset from the "hung" OS. This is a long shot, but you power up the phone normally and then press together Vol-Up+Send+End after waiting a couple of minutes. This might make it bootable. (As I said, "long shot". The fact that you have 1.49.0000 on the phone suggests that the prior owner tried some things - and apparently failed at it.)
bftb0
thanks for the response
i tried all of that just now and all i get is a black backlit screen unless i connect usb which gives me a black screen with HTC n four exclamation point triangles in the corners. and there isnt anything i can do from that screen and its bricked huh?
SoSicWiTiT said:
thanks for the response
i tried all of that just now and all i get is a black backlit screen unless i connect usb which gives me a black screen with HTC n four exclamation point triangles in the corners. and there isnt anything i can do from that screen and its bricked huh?
Click to expand...
Click to collapse
That's not a very good sign. I will say, however, that it is very strange that you can get the phone into RUU mode but not have a working bootloader - those two observations are mutually exclusive.
For grins, you could check to see if perhaps your Vol-Up/Vol-Down keys are broken by doing the following:
- Cold start the phone by pressing Send + End simultaneously (make sure to press Send first so that you are not initiating a normal boot; hold both keys down until the screen lights up). Make sure you pull the battery and have the USB cable disconnected when you pull the battery before you try this (to insure that the phone is "really" off).
If that works, the phone will be in Fastboot mode. You might be able to get into Hboot (but not recovery if your Vol-Up/Vol-down keys are broken) at that point with the command
Code:
fastboot reboot-bootloader
from a USB-connected PC.
Under normal circumstances, you can navigate from Fastboot Mode to Hboot and then from there to the Recovery boot - but this requires working Vol-Up or Vol-Down keys.
There is a very, very slim chance that if you can get Hboot launched this way (that is "fastboot reboot-bootloader")... and try to apply the Leak-V3 "PB00IMG.zip" file. If I recall correctly, you don't need Vol-Up/Vol-Down to apply an HTC PB00IMG.zip file - just the trackball press.
I'm not optimistic though - I think that the Leak-V3 (and all other Leak PB00IMG.zip) files probably will just fail with "Main Version is Older Messages".
As for other avenues of approach, there are no publicly known exploits of the RUU mode (= oem-78 mode).
Good luck
well
actually after staying up n working at it for 48 hours, i'm halfway done with a solution...and maybe the first ruu exploit.
i decided to run the 2.1 RUU and after it does its install wizard thing, i navigated to the temp folder where it installed all the files. i took the root rom (pb00img.zip) n renamed it to "rom.zip" then over wrote the version in the temp folder and started the ruu (clicked next and what not).. it failed as usual with error 110.. but afterward i noticed my phone says
pb00100 xc ENG S-OFF
HBOOT-1.49.2000
and before i did the file swap and ruu it said
pb00100 XC ENG S-ON
HBOOT-1.49.0000
so now i might be able to flash a custom recovery thru fastboot since i have s-off now
if not.. still.. its progress
Hmmm, interesting.
Whether or not that qualifies as new behavior sort of depends on what your "friend" did to the phone prior to getting it into the nearly bricked state. If they had previously run the jcase "Flash any RUU" method, then the Root ROM would have "taken" with the Hboot method... although in your case, since you "couldn't get there from here", my hat's off to you for a clever way of making the best of what you have!
Since you have the S-off bootloader, you might be tempted to direct-boot Amon_Ra without even bothering to flash it:
Code:
fastboot boot recovery-RA-Eris-v1.6.2.img
to see if your phone springs to life... congrats if you see a menu!
bftb0 said:
Since you have the S-off bootloader, you might be tempted to direct-boot Amon_Ra without even bothering to flash it:
Code:
fastboot boot recovery-RA-Eris-v1.6.2.img
to see if your phone springs to life... congrats if you see a menu!
Click to expand...
Click to collapse
i did that right after i seen it say "S-OFF". i get to the menu but when i try to flash a rom it gives me an error after formatting system.
Code:
E:Can't symlink /system/xbin/arp
E:Failure at line 65:
symlink /system/xbin/busybox SYS
TEM:xbin/arp
and after hours or more reading, everything is pointing to the boot and system partitions being corrupted by a bad flash of some sort.
i think i might have hit the end of the road..
EDIT
i managed to somehow get all the regular hboot, fastboot, n recovery to work and flashed amon_ra and can get to it from volup+power.. even got the 3 skateboarding droids on normal power on..
but cant flash any roms , from amon's ( gives the error above )or pb00img from hboot (at the end has "failed-PU" next to system..)
any idea's?
I have a couple ideas (still typing them up) ... in the meantime, if you boot Amon_RA and then open up a shell from the PC ("adb shell") and then
- check the output of "dmesg" to insure that the MTD partition table is still intact; you should see something like this towards the beginning of the boot log:
Code:
NAND_EBI2_ECC_BUF_CFG: 1ff
flash_id: 5501bcec size 20000000
Creating 6 MTD partitions on "msm_nand":
0x00001ff60000-0x000020000000 : "misc"
0x000002c60000-0x000003160000 : "recovery"
0x000003160000-0x0000033e0000 : "boot"
0x0000033e0000-0x00000dde0000 : "system"
0x00000dde0000-0x000015fe0000 : "cache"
0x000015fe0000-0x00001ff60000 : "userdata"
- try mounting (in turn) each of /system, /data, /sdcard, e.g.:
Code:
mount /sdcard
mount /data
mount /system
/cache should already be mounted.
Which mounts fail?
bftb0
The scenario you describe has come up before - or at least very similar symptoms.
Note that Nandroid restore will fail because it uses standard Unix tools such as "rm" to clear filesystems, so if a partition will not mount because of a corruption issue, nandroid will fail. I suppose that the same thing is true of the /sbin/recovery utility running underneath the booted recovery kernel (but I have not read the source code to verify that it is attempting to "mount" the filesystems first - if it didn't do that, it would need to understand the raw format details of yaffs2, and I think that is a stretch).
Unfortunately the filesystem formatting tools provided by Amon_RA do not include tools for repairing the mtd (NAND flash) - they are for the SD card/ extN filesystems. It is my impression, however, that the "yaffs2" filesystem is "format free" - meaning that a clean (Flash memory) "yaffs2" filesystem is simply a bunch of zero'ed pages - no superblocks, or Inode lists, - none of that. This suggests that the equivalent of "dd if=/dev/zero of=/dev/mtd/mtdNNN bs=..." could "repair" a yaffs2 file system by simply wiping it... but let's try something a little less crude than that (see below).
I had one of the file systems in my phone in this state at one time and I was able to repair the problem by reflashing the Root ROM - otoh, XDA user "stick" tried this and it seemed to produce a permanent brick in his case, so I am reluctant to recommend you do that. (You might, however, want to perform the jcase "Flash any RUU" hack to the "misc" partition so that you have flexibility to apply any PB00IMG.zip file)
Because the "flash_image" tool (in /sbin/flash_image in Amon_RA) writes both boot images and yaffs2 image files to arbitrary mtd partitions (and raw binary files to "misc"!), there is a chance that it is merely the equivalent of "dd for the MTD device" - so that you could "repair" a corrupted yaffs2 filesystem by simply overwriting it with a valid yaffs2 image file. The repair strategy here would be to:
- Unpack any PB00IMG.zip file and move the contents to a folder on the SD card. (Verify the md5sums of the files on the SD card before you use them - use this reference)
- Use "flash_image" from Amon_RA to flash the corresponding image file for the offending ("won't mount") partition, e.g.
Code:
flash_image system /sdcard/unpacked-PB00IMG/system.img
If this succeeds, see if you can "mount /system".
bftb0
PS Don't try flashing "system.img" using fastboot. However it is engineered (by the HTC bootloader) it will fail due to space issues. It is possible that the HTC bootloader uses the /cache partition to temporarily stage the file, which is only 130 MB compared to 159.5 MB for the /system partition - but whatever the explanation, the experimental result is that that on the Eris, you can not flash /system from fastboot. All the other partitions, no problem - but not the /system partition.
thanks,
i tried what you suggested and it let me mount all 3 of those partitions, and i tried using flash_image to flash the system.img i extracted and in return got a million and one errors..
starting with mtd: ECC error soft 0 hard 1 (continuing until about a hundred something)
then
mtd: not writing bad block at (basically the entire /system hex range)
then finally
error writing system: no space left on device
SoSicWiTiT said:
thanks,
i tried what you suggested and it let me mount all 3 of those partitions, and i tried using flash_image to flash the system.img i extracted and in return got a million and one errors..
starting with mtd: ECC error soft 0 hard 1 (continuing until about a hundred something)
then
mtd: not writing bad block at (basically the entire /system hex range)
then finally
error writing system: no space left on device
Click to expand...
Click to collapse
Was the partition table information correct? (I have seen innocuous "write error" messages on my phone, but they only occurred on regular block boundaries - not for every page; but in that case I don't think I ever saw an "out of space" message. Assuming everything was performed correctly, your phone is behaving as if large blocks of flash memory are being skipped due to "bad blocks")
Did you unmount the filesystems prior to doing the writes?
That is very mystifying.
If you can mount /system, or /data, what happens when you go in and do a
Code:
mount /system
cd /system
rm -rf /system/*
mount /data
cd /data
rm -rf /data/*
cd /
If those succeed, unmount everything
Code:
cd /
for x in /system /data /sdcard ; do
umount $x
done
Run an Amon_RA "wipe data/factory reset", and try and flash a ROM.
???
bftb0
One other thing you could try - I have never used it, so I don't know what effect it will have - is to use fastboot mode to erase the "system" and "data" partitions, and see if that has any effect on your ability to flash a ROM.
In fastboot (boot w/ Send+End) mode:
Code:
fastboot erase system
fastboot erase data
And then afterward boot into Amon_RA and try flashing a ROM.
I suppose you could also erase the boot partition this way, but you probably ought to do them one at a time just to minimize erase operations - and then if an operation fails in Amon_RA, examine the log file at
Code:
adb shell cat /cache/recovery/log
to see if it provides further elaboration on the nature of the error(s).
bftb0
Something else to try:
The symptoms you have (esp. since it appears that /system and /data will mount correctly) appear as if you "run out of space" when flashing ROMs to NAND. I suppose that could occur if somehow a bunch of pages in flash memory got (erroneously) marked invalid. Unless there is some means to clear flash memory so that bad page indicators are cleared, there is no way to reclaim those pages. (It is my impression that brand new NAND flash chips are already programmed with bad pages pre-marked)
It would be nice if the partition erase function of fastboot actually performed the page reclaim/retesting/re-marking operation - but there is no way to know whether that happens, as the HTC bootloader acts as the interpreter of "fastboot commands" passed over the wire (USB). It is free to implement whatever bad page management strategy that HTC desires - and frankly, a "never reclaim bad pages" policy is fairly reasonable when you consider that most consumer phones are flashed perhaps only 3 or 4 times in their lifetime - if that.
Something to try: if you perform a manual wipe of either /system or /data (after mounting them), do a "df" to see how much free space the kernel thinks they have - for a normal phone, that should be pretty darn close to the partition size. E.G.
Code:
> adb shell
# mount /system
# df /system
# mount /data
# df /data
# umount /system
# umount /data
# exit
>
If it seems "short" by a substantial amount, try installing a "small footprint" ROM, such as CELBFroyo 3.2 - it only uses about 100216 KB (97.9 MB).
Just a thought; I realize this is grasping at straws, but there is little for you to lose (which you knew right from the get-go).
bftb0
wow seriously i appreciate all the help you've provided , you need a donate button lol.
the system partition is 66% used (bad blocks im guessing) after a format leaving 59,648 useable
but the data partition is fine with 1% used. and 162,176 usable
but i havent lost all hope yet and this is entertaining me.
custom mtd maybe..swap /data to mtdblock3 (the bad one, system) and and /system to mtdblock5 (where data currently is).. or use a memory card idk?
here's where i got the idea
http://forum.xda-developers.com/showthread.php?t=717874
SoSicWiTiT said:
the system partition is 66% used (bad blocks im guessing) after a format leaving 59,648 useable
Click to expand...
Click to collapse
Holy crap!
For grins, could you do a "cat /proc/yaffs" and post up the section for the "system" partition? (You need /system to be mounted when you run that command).
Here's what mine looks like after performing an erase with fastboot, booting into Amon_RA, and then mounting it:
Code:
Device 1 "system"
startBlock......... 0
endBlock........... 1359
totalBytesPerChunk. 2048
nDataBytesPerChunk. 2048
chunkGroupBits..... 0
chunkGroupSize..... 1
nErasedBlocks...... 1359
nReservedBlocks.... 5
blocksInCheckpoint. 0
nTnodesCreated..... 0
nFreeTnodes........ 0
nObjectsCreated.... 200
nFreeObjects....... 96
nFreeChunks........ 86976
nPageWrites........ 0
nPageReads......... 0
nBlockErasures..... 0
nGCCopies.......... 0
garbageCollections. 0
passiveGCs......... 0
nRetriedWrites..... 0
nShortOpCaches..... 10
nRetireBlocks...... 0
eccFixed........... 0
eccUnfixed......... 0
tagsEccFixed....... 0
tagsEccUnfixed..... 0
cacheHits.......... 0
nDeletedFiles...... 0
nUnlinkedFiles..... 0
nBackgroudDeletions 0
useNANDECC......... 1
isYaffs2........... 1
inbandTags......... 0
I wonder what your "nRetireBlocks" count is.
I only poked around in the HTC "msm_7k" kernel code a little while ago for some clues, so I'm no expert. There does not seem to be any useful knobs to turn by using mount options.
Because Flash filesystems have to deal with new bad pages as they develop, I'll bet the phone could be completely fixed if there was a way to clear the bad pages - ( if they were actually bad, then on the first write use the write would fail, the pages would be marked bad, and the FS driver would recover gracefully - just as normally happens).
But as you say, that would probably require a custom kernel at the minimum with patches to the mtd driver. I do wonder if the kernel driver for the MTD device exposes any hooks (ioctls, etc) that would let you write a (privileged) userspace app which could wipe the raw pages status info.
This YAFFs doc suggests that certain tuning operations can be performed by writing options to /proc/yaffs, including control of tracing. One of the things that seems possible to control is the number of write attempts per page.
I'll have a look at your URL; no promises, though.
bftb0
[ Edit ] PS - do you have any idea what your friend did to get the phone in this state? Maybe flashing a ROM with really, really low battery? It seems hard to believe that an actual hardware problem occurred - moreover, this is not the first phone where very similar symptoms were exhibited.
I'm wondering if a busybox with mtd-utils compiled in might be of some assistance; in particular the "flash_eraseall" tool. (Perhaps use it with the "-N" option?)
lookit recent versions of the "flash_erase.c" code (excerpted from above Git link):
Code:
static void display_help (void)
{
printf("Usage: %s [options] MTD_DEVICE <start block> <block count>\n"
"Erase blocks of the specified MTD device.\n"
"Specify a count of 0 to erase to end of device.\n"
"\n"
" -j, --jffs2 format the device for jffs2\n"
[COLOR=green][B] " -N, --noskipbad don't skip bad blocks\n"[/B][/COLOR]
" -u, --unlock unlock sectors before erasing\n"
" -q, --quiet display progress messages\n"
" --silent same as --quiet\n"
" --help display this help and exit\n"
" --version output version information and exit\n",
PROGRAM_NAME);
}
(I don't have that version of busybox - I see references made to it in a few posts here on XDA, but I don't know it's origin or where to get it)
bftb0
[ Edit ] looked around for a bit and couldn't find anything pre-built; looks like you might have to build mtd-utils using the NDK for Android. Time for bed for me; here's the link to the mtd-utils project.
i found out that my friend installed rom manager n clockwork recovery and did a flash that failed then ran the 2.1 ruu thinking it would fix it. and that's how the phone got to the state i started with.
i actually got a rom to flash (kinda) with some info from that link i posted. i patched my recovery with files from that link which gave it a custom mtd (table) , i shrunk cache and used the extra space to make up for the bad blocks in system and bind mounted cache to and ext partition on my sd card... and all would be great BUT i realized that the boot partition is corrupt too.. ( which makes sense, since clockwork is known to corrupt both)
so my solution was to flash boot.img to recovery and just boot normally with volup+powerand use amon ra by "fastboot boot " if i need to.
but i cant flash the zip file that patches the kernel to boot using the custom mtd because it's script copies,unpacks,patches then repacks boot.img from /boot but my boot.img is on recovery so im either going to have to edit the .sh in the zip or have someone do the whole custom mtd thing and use the same mtdpartmap.txt and have them nandbackup then give me the boot.img from the backup folder so i can flash it to recovery.
OR have someone manually patch my boot.img file... but i highly doubt i'm going to be able to figure that out or find anyone todo it.
and i'll post the system section of that command in a second.
SoSicWiTiT said:
i found out that my friend installed rom manager n clockwork recovery and did a flash that failed then ran the 2.1 ruu thinking it would fix it. and that's how the phone got to the state i started with.
i actually got a rom to flash (kinda) with some info from that link i posted. i patched my recovery with files from that link which gave it a custom mtd (table) , i shrunk cache and used the extra space to make up for the bad blocks in system and bind mounted cache to and ext partition on my sd card... and all would be great BUT i realized that the boot partition is corrupt too.. ( which makes sense, since clockwork is known to corrupt both)
so my solution was to flash boot.img to recovery and just boot normally with volup+powerand use amon ra by "fastboot boot " if i need to.
but i cant flash the zip file that patches the kernel to boot using the custom mtd because it's script copies,unpacks,patches then repacks boot.img from /boot but my boot.img is on recovery so im either going to have to edit the .sh in the zip or have someone do the whole custom mtd thing and use the same mtdpartmap.txt and have them nandbackup then give me the boot.img from the backup folder so i can flash it to recovery.
OR have someone manually patch my boot.img file... but i highly doubt i'm going to be able to figure that out or find anyone todo it.
and i'll post the system section of that command in a second.
Click to expand...
Click to collapse
I was going to say, holy crap that's a lot of work - but then I've been struggling for a couple hours trying to build mtd-utils (or at least "flash_erase"). I've got all the Makefiles happy (by dropping non-essential parts of the build that require "libuuid"), but now I'm struggling with the linker/toolchain issues to try to avoid the hassles of dynamic link libraries for Amon_RA.
I still think that whatever it is that Clockwork does to get all those flash pages marked as if they are bad is a software error or some sort - so that if you can get
flash_eraseall -N
to do its thing on mtd3, you will recover all those "bad" pages in the system partition. (It is hard to believe that massive physical damage to eeprom would only show up in one or two logical partitions).
Cheers.
bftb0
FWIW,
SoSicWiTiT said:
OR have someone manually patch my boot.img file... but i highly doubt i'm going to be able to figure that out or find anyone todo it.
Click to expand...
Click to collapse
Have a look at this android-dls.com tutorial if you haven't already seen it. Use "split_bootimg.pl" to split apart the boot image into the kernel and compressed ramdisk, and then the ramdisk is just a gzipp'ed "cpio" archive.
The hardest bit about this is finding a verstion of "mkbootimg" - there are some floating around on XDA, or you can build it from the github sources.
It's not too bad, the only secret sauce is the load address for the Eris, which is 0x11200000
This is an excerpt from a shell script I use for repacking boot images - it's the essential part (everything else in the script is just glue).
Code:
mkbootimg --kernel ${_KFIL} --ramdisk new-${_RAMDGZ} --cmdline 'no_console_suspend=1 console=null' --base 0x11200000 --output new-${_BNAM}
i edited the shell script thats supposed to patch it to the best of my abilities (changed all boot.img txt to recovery.img) and it has mkbootimg and everything it needs in the zip, so im going to replace the script in the zip and try flashing it...
and something weird just happened.. i forgot i put boot.img for my rom on /recovery . so in shell just now, i typed reboot recovery expecting amon RA and the phone booted into the os???
even though i patched amon ra with custom mtd to install the rom ( system :300,000 - enough to skip bad blocks, cache: 30,000 ) my boot.img is mtd is set to see 176,000 right?
EDIT
i think i flashed that zip with my version of the script earlier to see what happened and i guess it worked..
Code:
C:\droid\tools>adb shell
sh-3.2# df /system
df /system
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock3 307200 229296 77904 75% /system
sh-3.2# df /cache
df /cache
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock4 61440 36500 24940 59% /cache
sh-3.2# df /data
df /data
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock5 101888 2608 99280 3% /data
sh-3.2#
I believe I narrowed down my problem to needing to format the different mmcblk’s so I can get one of the different recoveries to restore the image. As to what I have tried and have not keep reading.
So one day decided to try cm7 via SD Card, and it looked impressive. However It said something about issues with the sd card. I had no Idea what it would do to the nook ( I should've read the the instructions more thoroughly)
So I reboot only to find the nook looping back to cwm recovery (it was rooted).
After some searching I try the Ubuntu restore. It got stuck at the MLO part, I decided maybe it takes a while and i guess it Zeroed out mmcblk5 (I guess i'm not sure of anything at this point). The only issue later I find is that Ubuntu doesn't do any formatting, it just blanks out the partition and reloads it. After that failed attempt CWM just freezes at the cardboard box
I gave this a try
http://forum.xda-developers.com/showthread.php?t=1663836
but it spends a while with 1 red x and then reboots into locked recovery.
Giving it another try, I start apply the method described in:
http://forum.xda-developers.com/showthread.php?t=1605664
but “scripts” zip file gives a 404 error at Drop box.... the other files worked like a charm. It did get me pretty close and gave me this state (3 drives formatted in ext, I just need the others to format and restore). Thanks meghd00t!
List of devices attached
0000000000000000 recovery
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 15.6GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.3MB 33.6MB 17.3MB boot
5 33.6MB 83.9MB 50.3MB rom
6 83.9MB 134MB 50.3MB bootdata
7 134MB 522MB 388MB factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 14.5GB 12.9GB media
11 14.5GB 15.6GB 1139MB ext4 userdata
So now I am trying
http://forum.xda-developers.com/showthread.php?t=1545766
See post#2. However I am no linux guru and I am stuck at the step that says
Copy device and vendor folder from Nook-Tablet to ~/android/system/
I followed the instructions on
http://forum.xda-developers.com/showthread.php?t=1570022
To setup ubuntu on the vm box. I can connect to the nook via adb on windows 7 but it refuses to work from Ubuntu, it just wont show (I added the adb_usb.ini and launched adb via sudo). I tried to pull from windows but it doesn't look right and think it would be best if I pull it from Ubuntu.
P.S.
Oh also, since I reason that my partitions are pretty much gone I tried to pull it from the cm7 sd image. unless someone knows how for me to mount the mmcblk’s and extract the needed files from there.
Fixed Somewhat ...
Well I found the missing files to get this method to work.
http://forum.xda-developers.com/showthread.php?t=1605664
Then I applied the Ubuntu recovery.
http://forum.xda-developers.com/showthread.php?t=1470910
However the nook just boots then it says: Please restart your device and try again, and powers down...
For some reason I cant get the acclaim_update.zip to work. Can anyone please help or send me in a new direction?
Please restart...
Riddler9884 said:
Well I found the missing files to get this method to work.
http://forum.xda-developers.com/showthread.php?t=1605664
Then I applied the Ubuntu recovery.
http://forum.xda-developers.com/showthread.php?t=1470910
However the nook just boots then it says: Please restart your device and try again, and powers down...
For some reason I cant get the acclaim_update.zip to work. Can anyone please help or send me in a new direction?
Click to expand...
Click to collapse
That is the notice that the Nook is trying to load Recovery but there is not a recovery.img
I note in the op that you tried Megd00t's repart. It is absolutely solid in my opinion. I even intentionally bricked my nt8 to film the video that shows how to make it work.
If you try it again, you should be able to use an SDCard version of Clockworkmod to flash any *.zip to the device. See my series of videos here: http://www.youtube.com/playlist?list=PL676779C4F7BE8FEB&feature=mh_lolz
PM me if you have questions. I have not yet finished the accompanying articles describing the processes.
I am stumped
I performed this again
http://forum.xda-developers.com/show....php?t=1605664
with the added lines from the DD recovery
for blocks 7, 8 and 9
No go - It boot loops the stock recovery
Then I applied the Ubuntu recovery.
http://forum.xda-developers.com/show....php?t=1470910
Same result - It boot loops the stock recovery
by what I read both of these are supposed usually do the trick but it still doesn't do it. I followed the advice that cwm should be able to apply any zip
but the stock bn update zip doesnt work
acclaim update fails
heck the ribbon rom fails
it gave a status one. What am I overlooking?
Would there be a way to make a disk image of the entire nook with all the sub partitions defined?
It would have blocks 1-9 with their stock info and the rest of the partitions zeroed out. So they loaded with info when you boot to recovery?
Stock cannot be flashed without mod
Riddler9884 said:
I followed the advice that cwm should be able to apply any zip
but the stock bn update zip doesnt work
acclaim update fails
heck the ribbon rom fails
it gave a status one. What am I overlooking?
Click to expand...
Click to collapse
My error. (Sorry) The B&N update file (the BN acclaim update is the same) cannot be flashed without modification. Meghd00t posted a "howto" I believe but I don't have a link right now.
However, you SHOULD be able to flash the Ribbon Root and other custom ROMs using CWM. I don't know where you should go now...
---------- Post added at 06:02 PM ---------- Previous post was at 06:00 PM ----------
Riddler9884 said:
Would there be a way to make a disk image of the entire nook with all the sub partitions defined?
It would have blocks 1-9 with their stock info and the rest of the partitions zeroed out. So they loaded with info when you boot to recovery?
Click to expand...
Click to collapse
I believe that is Albert Wertz's process. You might want to check it out. His file is a CWM "Backup" image that you should be able to "Restore" (with CWM). Might be worth a try...
Well I am not sure but I believe what fixed it was:
repartitioning the Nook using: http://forum.xda-developers.com/showthread.php?t=1605664
Then Using: SD_R3NT16or8gbV4_7
http://forum.xda-developers.com/showthread.php?t=1528625
I flashed flash-restore-stock.zip from:
http://forum.xda-developers.com/showthread.php?t=1545766
followed up by using the restore feature in SD_R3NT16or8gbV4_7
to complete the missing info
I almost got my nook back. Now I just need to work out how to get my sn back.
Riddler9884 said:
Well I am not sure but I believe what fixed it was:
repartitioning the Nook using: http://forum.xda-developers.com/showthread.php?t=1605664
Then Using: SD_R3NT16or8gbV4_7
http://forum.xda-developers.com/showthread.php?t=1528625
I flashed flash-restore-stock.zip from:
http://forum.xda-developers.com/showthread.php?t=1545766
followed up by using the restore feature in SD_R3NT16or8gbV4_7
to complete the missing info
I almost got my nook back. Now I just need to work out how to get my sn back.
Click to expand...
Click to collapse
Hey sounds like you are almost there.
The sn is under the SDCard door. I saw a post somewhere on XDA about a process for manually putting it back in the device memory. Search here and Google.
Sent from my NookTablet using XDA
I tried
http://forum.xda-developers.com/showthread.php?t=1610069
I guess it works depending on how much you have cleared from the nooks internal memory in the process of restoring the nook.
I kind of put this together based on what I saw here
http://nookdevs.com/NookColor_Fix_Boot_Loops
Look at the section that says
echo -n -e "\x08\x00\x00\x00" > /mnt/devconf/BootCnt
i did a little research
Their method didn't work form me, but it gave me insight. I worked out the chmod by what was said here
http://forum.xda-developers.com/showthread.php?t=1586281
~ # echo -n -e "20201700########" > /rom/devconf/SerialNumber
~ # echo -n -e "20201700########" > /rom/devconf/DeviceID
~ #echo -n -e "5867########" > /rom/devconf/MACAddress
~ # cd /rom/devconf
/rom/devconf # chmod 440 MACAddress
/rom/devconf # chmod 440 DeviceID
/rom/devconf # chmod 440 SerialNumber
Update - It Couldn't Register but I did find this out by chance:
When I originally got my tablet and rooted the google play store saw this under My Devices:
(From a pc, Log in, all the way at the bottom, My Devices tab)
Maker-> Barnes&Noble
Model-> BNTV250
I went back in recently after restoring and got this:
Maker-> Bn
Model-> Nook Tablet
Maybe one of the restores was messing with changing the name for Compatibility? I used so many things I cant tell where the above came from.
repart.img
Riddler9884 said:
Maybe one of the restores was messing with changing the name for Compatibility? I used so many things I cant tell where the above came from.
Click to expand...
Click to collapse
What is the ID that is displayed when you connect with ADB? In all of my (3 months) trial of being "bricked", I did not stop getting my serial number as the id when I connected with adb. But, nothing else on the internal memory worked. The only way I could use the Nook was with an external SD-based ROM (I used CM7a).
What I suggest is (repeat this after each different attempt to fix your issues): Try Meghd00t's repart.img again. Let it clear everything and restore back to stock. You might be pleasantly surprised! I sure was.
Here is a link to my step-by-step guide. http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Nope no more, re-imaging the nook for this test. My wife will kill me if I keep ignoring her to tinker with the nook, Especially since it was for her to read her novels.
After loading albertwertz image and having access to android market and the amazon store has her happy.
Registering the B&N would just be a plus.... I need a tablet I will just get a Samsung 7 inch tablet.
Restore serial number on Nook
Riddler9884 said:
Nope no more, re-imaging the nook for this test. My wife will kill me if I keep ignoring her to tinker with the nook, Especially since it was for her to read her novels.
After loading albertwertz image and having access to android market and the amazon store has her happy.
Registering the B&N would just be a plus.... I need a tablet I will just get a Samsung 7 inch tablet.
Click to expand...
Click to collapse
I found this on one of Succulent's posts:
- To get your serial number back, you need to perform factory restore (8 failed boot method)
- The one that prompt,
Clearing data…
A reset is being performed.
This may take a few minutes
Click to expand...
Click to collapse
Here is a link to the thread: http://forum.xda-developers.com/showthread.php?t=1545766
Hello,
I running into some trouble using Parted via adb shell to resize some partition on eMMC chip on my Gnote (SGH-i717D). So basically, i'm following this guide: http://forum.xda-developers.com/showthread.php?t=1887864
However, parted will give the the error "Can't have a partition outside the disk!" at any query I submit. After investigating (using fdisk), indeed some partitions are outside the "disk":
... total 30775296 sectors...
end of mmcblk0p4 = 30777343
end mmcblk0p28 = 30777343
Not too sure how this happened... I know how to ajust under Linux (i.e. this guide) but thru adb shell, I cant use most tools I normally have at hand under linux. I was thinking a full format of the device under recovery and reinstall the ROM would maybe fix the issue? (although I doubt it will touch partition size, only wipe them)
Any ideas, workarounds, suggestions?
I run this ROM: http://forum.xda-developers.com/showthread.php?t=2268617
I run this Kernel: http://forum.xda-developers.com/showthread.php?t=2427617
Thanks.
Really? nobody has an idea?
Ive been searching for a while for a forum that explains how to root the new nabi 24" BIG TAB HD. trying to install clockworkmod on the tablet.. if anyone can point me in the direction of what I'm looking for that would be greatly appreciated.
jmmac said:
Ive been searching for a while for a forum that explains how to root the new nabi 24" BIG TAB HD. trying to install clockworkmod on the tablet.. if anyone can point me in the direction of what I'm looking for that would be greatly appreciated.
Click to expand...
Click to collapse
As far as I know nobody has talked about it on here except you.
Depending on what kernel patches or android security fixes it has you might be able to try some root programs. There certainly will not be a clockworkmod or TWRP for it yet.
If none of the root methods work it might be possible to use the Dreamtab TWRP.(http://forum.xda-developers.com/android/development/recovery-twrp-2-7-1-0-nabi-dreamtab-hd8-t2813917) If it's like the previous Nabi tablets the bootloader will be unlocked, and you could try booting from that TWRP. The screen and the landscape/portrait might be messed up but it could work. In the last software update to the dreamtab they locked the bootloader so the BIG TAB might be as well. It could be unlocked by
Code:
fastboot oem unlock
^^^ This will ERASE all the data on the tablet.
If you want to try the TWRP way let me know but of course there are dangers involved.
If you try it alone be aware that if you try the dreamtab TWRP load it by
Code:
fastboot boot recovery.img
and NOT
Code:
[STRIKE]fastboot flash recovery recovery.img[/STRIKE]
or you will overwrite your current stock recovery.
also interested! any further info would be great!
schlager said:
also interested! any further info would be great!
Click to expand...
Click to collapse
Do either of you have one? Or just asking?
aicjofs said:
Do either of you have one? Or just asking?
Click to expand...
Click to collapse
i plan to buy one in the next few weeks. mainly need it so i can have two sheets of music in front of me. if there is another tablet that can do that, let me know.
aic, I got one for the kids for Xmas. The Nabi2's have been good but wont last forever, I liked the multi user option and big ass screen on the big tab. Well see how it works out! Once they open and spend time with it I'll be interested in rooting for adaway and such.
codest3r said:
aic, I got one for the kids for Xmas. The Nabi2's have been good but wont last forever, I liked the multi user option and big ass screen on the big tab. Well see how it works out! Once they open and spend time with it I'll be interested in rooting for adaway and such.
Click to expand...
Click to collapse
I have no idea about the BigTab but if it's like the DreamTab it will update when you boot it up. It's hard to get around it. If it does it will likely patch a lot of the more recent exploits that can gain you root. There is the option to try the dream tab recovery like I said above but be really careful with that.
Also one of the Dreamtab updates locked the bootloader. This isn't a big deal as it was unlockable via fastboot. However, if you let the kiddoz, or you start installing a whole bunch of stuff, when you unlock the bootloader you will wipe the tablet back to factory(normal behavior). Best to unlock it as soon as possible.
I own the big tab 20" was able to root using http://forum.xda-developers.com/showthread.php?t=2473747
I did have to unlock the bootloader and tried booting the dream tab recovery from fastboot no dice there so wasn't gonna risk flashing it.
The process took about 20 mins maybe less fully automated it froze at some point so I reset the big tab and tried again at which point kingo program told me I was already rooted download SU was able to update the binary's normal method and been good to go since. Word of warning it does preform a factory reset when you unlock the bootloader so be prepared for that.
I have been working on compiling CWM for the Nabi big tab 20" I'm close but I can't seem to figure out the path for the sdcard currently the recovery boots but can't back anything up with out the correct path entered into the recovery.fstab. This particular tablet does not have a real sdcard nor does it have a slot for an external one. Any help on this would be appreciated when I get it sorted out will add a link for the recovery.
this is what I currently have in my recovery.fstab.
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,data=writeback,nodelalloc,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MDA /metadata emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,data=ordered,noauto_da_alloc,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/TRD /app ext4 defaults wait
/dev/block/sda1 /sdcard vfat defaults voldmanaged=sdcard:auto
When I boot into recovery and attempt to perform a backup to sdcard I get E:Can't mount backup path.
You could download and try a rooting apk like towelroot framaroot or z4root if it has a low android firmware like 2.3.6 or something but only for z4root
I already got it rooted using Kingo root, these tablets are new on the market running kitkat 4.4.4, the end goal I am trying to achieve is making a custom rom but a neassacery first step is to get a working custom recovery so I can backup my stock rom just in case I blow up my tablet =)
lmortal said:
I have been working on compiling CWM for the Nabi big tab 20" I'm close but I can't seem to figure out the path for the sdcard currently the recovery boots but can't back anything up with out the correct path entered into the recovery.fstab. This particular tablet does not have a real sdcard nor does it have a slot for an external one. Any help on this would be appreciated when I get it sorted out will add a link for the recovery.
this is what I currently have in my recovery.fstab.
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,data=writeback,nodelalloc,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MDA /metadata emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,data=ordered,noauto_da_alloc,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/TRD /app ext4 defaults wait
/dev/block/sda1 /sdcard vfat defaults voldmanaged=sdcard:auto
When I boot into recovery and attempt to perform a backup to sdcard I get E:Can't mount backup path.
Click to expand...
Click to collapse
Did you get that from pulling the stock recovery and extracting the recovery.fstab from the ramdisk?
The internal is likely on /data/media, or data/media/0 if it's like all the other Nabi's. Pretty sure /dev/block/sda1 to mount sdcard is not going to work. I'm not as knowledgeable at CWM as I enjoy TWRP so I'm not sure if there is a boardconfig.mk change you can do or if you need to symlink it in an init.rc file.
aicjofs said:
Did you get that from pulling the stock recovery and extracting the recovery.fstab from the ramdisk?
The internal is likely on /data/media, or data/media/0 if it's like all the other Nabi's. Pretty sure /dev/block/sda1 to mount sdcard is not going to work. I'm not as knowledgeable at CWM as I enjoy TWRP so I'm not sure if there is a boardconfig.mk change you can do or if you need to symlink it in an init.rc file.
Click to expand...
Click to collapse
There was something else there originaly but it didn't work either so I ended up using the following from cat /proc/mounts:
/dev/fuse/mnt/shell/emulated /sdcard fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permisions,allow_other nonremovable
Using the above line in the recovery.fstab allowed cwm to see the sdcard but was still unable to mount it. I have been playing around with different things but I am fairly new to this so my knowledge is limited.
lmortal said:
There was something else there originaly but it didn't work either so I ended up using the following from cat /proc/mounts:
/dev/fuse/mnt/shell/emulated /sdcard fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permisions,allow_other nonremovable
Using the above line in the recovery.fstab allowed cwm to see the sdcard but was still unable to mount it. I have been playing around with different things but I am fairly new to this so my knowledge is limited.
Click to expand...
Click to collapse
I'm not really sure without seeing any of your code(device tree), finished recovery or any of the stock recovery.
I haven't made CWM in so long. Something like?
/dev/null /sdcard datamedia defaults recoveryonly
dd the mmcblock0pX for the recovery and boot and we can make something work. How much space is the recovery partition?
aicjofs said:
I'm not really sure without seeing any of your code(device tree), finished recovery or any of the stock recovery.
I haven't made CWM in so long. Something like?
/dev/null /sdcard datamedia defaults recoveryonly
dd the mmcblock0pX for the recovery and boot and we can make something work. How much space is the recovery partition?
Click to expand...
Click to collapse
I sent you a pm with a drop box link with my files in the mean time gonna try compiling with your suggestion and see what happens.
---------- Post added at 04:17 PM ---------- Previous post was at 03:36 PM ----------
I tried compiling with:
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
/dev/null /sdcard fuse datamedia,recoveryonly defaults
It compiled successfully and I was able to flash it, the sdcard showed up in the mount menu but was not mountable still.
---------- Post added at 05:10 PM ---------- Previous post was at 04:17 PM ----------
Okay so my latest build using:
/dev/block/sda1 sdcard fuse defaults nonremovable
Allowed backup to the sdcard of everything with the exception of /data got "Error while making a backup image of /data!"
Also still unable to mount sdcard under the mounts and storage menu.
I believe the reason for the error while backing up data was due to available space when I restarted the tablet there was only 99.59MB available and I think the data would have needed more space then that.
I kept running into problems with CWM recovery but with the help of aicjofs I was able to compile a working TWRP with usb drive support, I don't yet have enough post to make an outside link so if some one can pm me I can give the link to be posted here with the recovery I made.
Working TWRP 2.8.1.0 for Nabi BigTab 20
Here is a TWRP recovery 2.8.1.0 for the Nabi BigTab 20" model
TWRP 2.8.1.0 for NV20A(BigTab20)
Built by @lmortal. We spent a lot of our Sunday sorting all the issue so click the thanks button for Imortal in the post above this one!
aicjofs said:
Here is a TWRP recovery 2.8.1.0 for the Nabi BigTab 20" model
TWRP 2.8.1.0 for NV20A(BigTab20)
Built by @lmortal. We spent a lot of our Sunday sorting all the issue so click the thanks button for Imortal in the post above this one!
Click to expand...
Click to collapse
Fixed an error where /addon was not mounting. re uploaded recovery image to the above link.
I can't unlock my bootloader.
lmortal said:
I own the big tab 20" was able to root using http://forum.xda-developers.com/showthread.php?t=2473747
I did have to unlock the bootloader and tried booting the dream tab recovery from fastboot no dice there so wasn't gonna risk flashing it.
The process took about 20 mins maybe less fully automated it froze at some point so I reset the big tab and tried again at which point kingo program told me I was already rooted download SU was able to update the binary's normal method and been good to go since. Word of warning it does preform a factory reset when you unlock the bootloader so be prepared for that.
Click to expand...
Click to collapse
I've ben trying to root my Big Tab 24". You said you had to unlock the bootloader. I can't get it into bootlad mode or unlock the bootloader. I tried fastboot. I tried every button combination I could think of. (not too many considering it only has three physical buttons) I tried rooting it with Kingo without unlocking the bootloader. Nothing is working. Please help. What am I doing wrong or not doing right?
Fastboot is the boot loader make sure you have USB debugging enabled and connect the tab to a PC you can then use the command "adb reboot-bootloader" the command to unlock is "fastboot OEM unlock"
Phone is Elephone P7000, I can flash various stock roms and custom to it, doesn't boot into recovery unless I use CWM, which I can boot into and connect via adb.
Chip is MT6752, I've never flashed over bootloader or userdata, just the rest. Got it working a couple times, with different roms though would freeze after a while or a x has stopped working (I've had this phone since it was released and never updated the stock rom - I got the x has stopped working error before ever flashing anything and it got stuck in a boot loop after that), resetting stuck in boot loop, haven't got it working since then despite multiple flashing attempts. I have not tried firmware upgrade with SP Tool since that does the whole lot also haven't tried formatting.
Typically rebooting from CWM would help (just regular, not into fastboot), but to no avail anymore.
Memory Test on sptool passed everything except for nand flash which says it was not found.
in adb shell frompc via CWM recovery running.
fdisk -l /dev/block/mmcblk0
fdisk: can't open '/dev/blockmmcblk0': I/O error
obviously mmcblk1 (the external SD card) works just fine.
parted /dev/block/mmcblk0 print
Error: /dev/block/mmcblk0: unrecognised disk label
Again mmcblk1 will be fine.
It shows up using cat /proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
e2fsck /dev/block/mmcblk0
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0
Could this be a zero-length partition?
C:\adb>adb shell
~ # mke2fs -n /dev/block/mmcblk0
mke2fs -n /dev/block/mmcblk0
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
954720 inodes, 3816960 blocks
190848 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3909091328
117 block groups
32768 blocks per group, 32768 fragments per group
8160 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
~
Is there any chance of repairing this partition with a tool like you can on a PC?
Otherwise what should I do from here?
Athiril said:
Phone is Elephone P7000, I can flash various stock roms and custom to it, doesn't boot into recovery unless I use CWM, which I can boot into and connect via adb.
Chip is MT6752, I've never flashed over bootloader or userdata, just the rest. Got it working a couple times, with different roms though would freeze after a while or a x has stopped working (I've had this phone since it was released and never updated the stock rom - I got the x has stopped working error before ever flashing anything and it got stuck in a boot loop after that), resetting stuck in boot loop, haven't got it working since then despite multiple flashing attempts. I have not tried firmware upgrade with SP Tool since that does the whole lot also haven't tried formatting.
Typically rebooting from CWM would help (just regular, not into fastboot), but to no avail anymore.
Memory Test on sptool passed everything except for nand flash which says it was not found.
in adb shell frompc via CWM recovery running.
fdisk -l /dev/block/mmcblk0
fdisk: can't open '/dev/blockmmcblk0': I/O error
obviously mmcblk1 (the external SD card) works just fine.
parted /dev/block/mmcblk0 print
Error: /dev/block/mmcblk0: unrecognised disk label
Again mmcblk1 will be fine.kcuf
It shows up using cat /proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
Is there any chance of repairing this partition with a tool like you can on a PC?
Otherwise what should I do from here?
Click to expand...
Click to collapse
Ok bro heres how to repair your phone.You need a firmware image of your device and you need some way to flash it.Google
"your device" firmware then download and flash it.Everything will be repaired and your device will be in working order.
boyam99 said:
Ok bro heres how to repair your phone.You need a firmware image of your device and you need some way to flash it.Google
"your device" firmware then download and flash it.Everything will be repaired and your device will be in working order.
Click to expand...
Click to collapse
I'm not sure if you read what I've written, I've reflashed the phone repeatedly, apart from the preloader since that could be disastrous, and userdata partitions.
Anyone else reading: I want to try parted mklabel to give it a new label, but not sure what label to give it, and then try resuce under parted.
Athiril said:
I'm not sure if you read what I've written, I've reflashed the phone repeatedly, apart from the preloader since that could be disastrous, and userdata partitions.
Anyone else reading: I want to try parted mklabel to give it a new label, but not sure what label to give it, and then try resuce under parted.
Click to expand...
Click to collapse
hey am trying to help you dont say am not helping
---------- Post added at 08:39 AM ---------- Previous post was at 08:30 AM ----------
Athiril said:
I'm not sure if you read what I've written, I've reflashed the phone repeatedly, apart from the preloader since that could be disastrous, and userdata partitions.
Anyone else reading: I want to try parted mklabel to give it a new label, but not sure what label to give it, and then try resuce under parted.
Click to expand...
Click to collapse
do u have a backup of your device.If the stock rom isnt working its either a software problem or its the phone
---------- Post added at 08:39 AM ---------- Previous post was at 08:39 AM ----------
Athiril said:
I'm not sure if you read what I've written, I've reflashed the phone repeatedly, apart from the preloader since that could be disastrous, and userdata partitions.
Anyone else reading: I want to try parted mklabel to give it a new label, but not sure what label to give it, and then try resuce under parted.
Click to expand...
Click to collapse
do u have a backup of your device.If the stock rom isnt working its either a software problem or its the phone