*late edit*
I think after all this posting I might be close to what is going on. When I boot, it looks like /system isn't mounting. I will paste the output of the recovery log at the end of this post, for someone to confirm. Maybe my fstab was changed at some point? If anyone can post a current fstab file that would be great too.
Okay, I'll try to be succinct. I had a working CM10, but could never really get flash to work without crashing on me. So I decided to go with Androwook. I went through the nvflash, everything went according to the tutorial. I have all my backup .imgs, etc. I still have full access to the device via fastboot, nvflash, and TWRP. I can't recall the entire series of events, but at some point when I tried to install the WW_epaduser_10_4_2_9_UpdateLauncher.zip, it halfway installed, tried to format the internal storage (which later I found it had) and then rebooted with the droid on his back, red exclamation point. Uh oh. So I was able to get recovery reflashed, and since then, no matter what rom I install, nothing will boot! Last thing I have tried was the Prime Full Wipe, adb pushed a couple of roms to internal storage and flashed and no love.
Can anyone please guide me in the right direction here? Right now, my boot still says "AndroidRoot 9.4.2.28r01" which tells me its still the .mobi loader right? Will that affect the rom image loading up?
I tried playing with the nvflash, but not really quite sure what I am doing. I can "wheelie -b blob.bin" from the blob I pulled during the nvflash procedure. After that, I can successfully "nvflash --resume --rawdevicewrite 0 2944 bricksafe.img" This doesn't give any win, however. I have the other files but the documentation on how to MAKE nvflash backups is all over. How to USE them doesn't seem to be. Any and all help is greatly appreciated.
Oh no...
wolfeyes30 said:
Oh no...
Click to expand...
Click to collapse
Originally Posted by rayman View Post
No, no guide yet.
We purposedly left out the procedure for doing a full restore until it is explicitly required.
Our experience is that if we give the instructions for this, people will do it for every little brick that could easily be fixed in other ways and it's just not a good idea
For 99% of cases, you can restore by simply flashing the partitions that have been broken, e.g.
Bootloader having issues => nvflash -r --download 4 bootloader.bin
Broken or stock recovery => nvflash -r --download 5 recovery.img
Broken or stock boot partition => nvflash -r --download 6 boot.img
Broken system partition => nvflash -r --download 10 system.img
stock system.img, boot.img etc can be retrieving by using the blobunpack tool on the blob file (different blob ) inside official ASUS images (downloaded from support.asus.com). When unpacked, blob.APP => system, blob.LNX => boot.img, blob.SOS => blob.LNX.
There are very few cases where you will brick further than this and when/if that happens, we'll be happy to help people through it, assuming they have ALL the backups we mention on androidroot.mobi! In everyday usage, you won't need those backups, but when/if something really bad happens, they could mean the difference between a brick and a recoverable tablet.
Click to expand...
Click to collapse
I think this is where I need to be. Of course i just broke it worse, now I can *only* access the device via nvflash. In my inifinite wisdom, I renamed "bootloader.ebt" to "bootloader.bin" and flashed it. I then tried to flash "bricksafe.img" and that did not fix anything. I can see that there's a way to blob-extract what I need from the above post, but I don't see the bootloader.img conversion listed in there. Maybe it's named as it should be on extration.
I am tempted to try doing a wheelie using the "ebtblob.bin" instead of the "blob.bin" since these other images I recovered have the .ebt extension. But there's extreme lack of documentation, and I don't want to make it worse. Anyone?
I tried doing this:
Try the following:
1) Download *externallinknotallowed*/androidroot.mobi/download/rec_bootloader.bin
2) Boot device into nvflash with Wheelie
3) nvflash -r –download 4 rec_bootloader.bin
4) nvflash -r –go, shutdown regularly and see if it boots again normally.
Click to expand...
Click to collapse
and got what looks like a syntax issue
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
[email protected]:~/Downloads/tf201_nvflashpack$ ./nvflash -r –download 4 rec_bootloader.bin
Nvflash v1.5.66719 started
[resume mode]
unknown command: –download
[email protected]:~/Downloads/tf201_nvflashpack$
Click to expand...
Click to collapse
I looked through the nvflash manpage and don't see anything regarding a -download flag.
jrodder said:
I think this is where I need to be. Of course i just broke it worse, now I can *only* access the device via nvflash. In my inifinite wisdom, I renamed "bootloader.ebt" to "bootloader.bin" and flashed it. I then tried to flash "bricksafe.img" and that did not fix anything. I can see that there's a way to blob-extract what I need from the above post, but I don't see the bootloader.img conversion listed in there. Maybe it's named as it should be on extration.
I am tempted to try doing a wheelie using the "ebtblob.bin" instead of the "blob.bin" since these other images I recovered have the .ebt extension. But there's extreme lack of documentation, and I don't want to make it worse. Anyone?
I tried doing this:
and got what looks like a syntax issue
I looked through the nvflash manpage and don't see anything regarding a -download flag.
Click to expand...
Click to collapse
Okay.
[email protected]:~/Downloads/tf201_nvflashpack$ ./nvflash --resume --download 4 rec_bootloader.bin
Nvflash v1.5.66719 started
[resume mode]
sending file: rec_bootloader.bin
/ 1021997/1021997 bytes sent
rec_bootloader.bin sent successfully
So it was a syntax thing, I read a bit closer. I now have bootloader again, roms still won't load up. I might take a rest for tonight. I am sure this is fixable, just checking to see if there's any guru out there that can help a brother out.
jrodder said:
Okay.
[email protected]:~/Downloads/tf201_nvflashpack$ ./nvflash --resume --download 4 rec_bootloader.bin
Nvflash v1.5.66719 started
[resume mode]
sending file: rec_bootloader.bin
/ 1021997/1021997 bytes sent
rec_bootloader.bin sent successfully
So it was a syntax thing, I read a bit closer. I now have bootloader again, roms still won't load up. I might take a rest for tonight. I am sure this is fixable, just checking to see if there's any guru out there that can help a brother out.
Click to expand...
Click to collapse
I can't seem to mount /DATA from within TWRP, it also started asking me for a password. I just reinstalled it again (I think) via adb, and it's still asking me for a password? I can cancel by it, but it's nothing I set and have never seen before.
jrodder said:
.........I have all my backup .imgs, etc. I still have full access to the device via fastboot, nvflash, and TWRP. I can't recall the entire series of events, but at some point when I tried to install the WW_epaduser_10_4_2_9_UpdateLauncher.zip, ....
Click to expand...
Click to collapse
I did this exact same thing going through the steps for the AndroWook HairyBean instructions.
I now have a new bootloader (doesn't say AndroidRoot) and I can't seem to do anything.
I'm actually lost when it comes to finding out whether or not I'm able to boot to APX mode.
How can I tell if I'm in APX mode?
If I get into APX mode, do you know how to restore the bootloader?
ANY help would be greatly appreciated.
--Charlie
ecatsab said:
I did this exact same thing going through the steps for the AndroWook HairyBean instructions.
I now have a new bootloader (doesn't say AndroidRoot) and I can't seem to do anything.
I'm actually lost when it comes to finding out whether or not I'm able to boot to APX mode.
How can I tell if I'm in APX mode?
If I get into APX mode, do you know how to restore the bootloader?
ANY help would be greatly appreciated.
--Charlie
Click to expand...
Click to collapse
Well this is the blind leading the blind but... you know you are in APX mode when you hold up on the volume, press and hold power and it vibrates. Screen should stay totally black. On windows a device will show up. For me at home on linux, I just have to test it by trying to do a wheelie, and it works. Glad to know I'm not the only soul screwed after this androwook flashing attempt. I am certain it is recoverable, but can't for the life of me make it happen. Restoring the bootloader would be done as I outlined above in one of my replies. Grab the recovery image and flash it. if you google the command I used, you should find the url. XDA won't let me post links...
Hope that helps.
jrodder said:
Well this is the blind leading the blind but... you know you are in APX mode when you hold up on the volume, press and hold power and it vibrates. Screen should stay totally black. On windows a device will show up. For me at home on linux, I just have to test it by trying to do a wheelie, and it works. Glad to know I'm not the only soul screwed after this androwook flashing attempt. I am certain it is recoverable, but can't for the life of me make it happen. Restoring the bootloader would be done as I outlined above in one of my replies. Grab the recovery image and flash it. if you google the command I used, you should find the url. XDA won't let me post links...
Hope that helps.
Click to expand...
Click to collapse
I am starting to think my whole issue is with something wonky that happened with the partitioning of the internal storage. I unpacked the stock ASUS blob, so try and push the system data via nvflash.
[!] Done - your device should now be ready for nvflash
[email protected]:~/Downloads/tf201_nvflashpack$ ./nvflash -r --download 10 system.img
Nvflash v1.5.66719 started
[resume mode]
system.img is too large for partition
command failure: partition download failed
[email protected]:~/Downloads/tf201_nvflashpack$
Click to expand...
Click to collapse
That's not the first time I had seen that, as I get that same error trying to push the 700mb blob file for the Androwook Hairybean 1.2.
Here is the listing of file structure from adb shell:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 491.3M 48.0K 491.3M 0% /dev
/dev/block/mmcblk0p2 421.3M 16.5M 404.8M 4% /cache
/dev/block/mmcblk0p8 27.2G 431.5M 26.7G 2% /data
/dev/block/mmcblk0p8 27.2G 431.5M 26.7G 2% /sdcard
~ #
Click to expand...
Click to collapse
Is that what it's supposed to be? I read about a staging partition, which is where the blob has to sit when being sent. Is that an actual partition that is supposed to exist separate from what is listed?
I did find this from another post where a user had blown up his partitions:
Note the error on /data. Could not format /data either using the CWM mounts and storage menu. I named the partitions I knew about and formatted /data (mmcblk0p8) from adb shell:
Number Start End Size File system Name Flags
1 38.3MB 575MB 537MB ext4 system
2 575MB 1024MB 449MB ext4 cache
3 1024MB 1026MB 2097kB misc
4 1026MB 1585MB 559MB ext3 staging
5 1585MB 1591MB 5243kB fat32 btmac
...
8 1596MB 63.6GB 62.0GB ext4 data
Click to expand...
Click to collapse
I will continue to try and find out how, but if ANYONE can tell me how I can automagically format the internal storage to its proper config, I'd be grateful. I tried everything via TWRP 2.2.2, but it doesn't seem to be working. I don't have another tablet to test with for sanity purposes, but if it matters I cannot ever mount the "sdcard" from the mount menu, with internal storage selected. I've gone through and tried all the wipe and format options many times.
**still trying***
More reading, I understand now that my only option is figuring out nvflash, as it supercedes fastboot after it has been installed. So, I grabbed my current partition structure, seems awfully high but without someone to help me sanity check that I don't know if its correct or not. I see an option that looks like it would be great, but appears to need a config file that I don't have.
--format_all
formats all existing partitions on the target device using the config file,
including partitions and the bct
Click to expand...
Click to collapse
PartitionId=2
Name=BCT
DeviceId=18
StartSector=0
NumSectors=768
BytesPerSector=4096
PartitionId=3
Name=PT
DeviceId=18
StartSector=768
NumSectors=128
BytesPerSector=4096
PartitionId=4
Name=EBT
DeviceId=18
StartSector=896
NumSectors=2048
BytesPerSector=4096
PartitionId=5
Name=SOS
DeviceId=18
StartSector=2944
NumSectors=2048
BytesPerSector=4096
PartitionId=6
Name=LNX
DeviceId=18
StartSector=4992
NumSectors=2048
BytesPerSector=4096
PartitionId=7
Name=CER
DeviceId=18
StartSector=7040
NumSectors=2048
BytesPerSector=4096
PartitionId=8
Name=IMG
DeviceId=18
StartSector=9088
NumSectors=2048
BytesPerSector=4096
PartitionId=9
Name=GP1
DeviceId=18
StartSector=11136
NumSectors=256
BytesPerSector=4096
PartitionId=10
Name=APP
DeviceId=18
StartSector=11392
NumSectors=131072
BytesPerSector=4096
PartitionId=11
Name=CAC
DeviceId=18
StartSector=142464
NumSectors=109568
BytesPerSector=4096
PartitionId=12
Name=MSC
DeviceId=18
StartSector=252032
NumSectors=512
BytesPerSector=4096
PartitionId=13
Name=USP
DeviceId=18
StartSector=252544
NumSectors=136576
BytesPerSector=4096
PartitionId=14
Name=PER
DeviceId=18
StartSector=389120
NumSectors=1280
BytesPerSector=4096
PartitionId=15
Name=YTU
DeviceId=18
StartSector=390400
NumSectors=128
BytesPerSector=4096
PartitionId=16
Name=CRA
DeviceId=18
StartSector=390528
NumSectors=1280
BytesPerSector=4096
PartitionId=17
Name=UDA
DeviceId=18
StartSector=391808
NumSectors=7368960
BytesPerSector=4096
PartitionId=18
Name=GPT
DeviceId=18
StartSector=7760768
NumSectors=128
BytesPerSector=4096
Click to expand...
Click to collapse
Sorry to hear you also have this issue. I broke mine in a very similar way and have been struggling to repair it too. Do you have a compiled version of the blob unpack tool? I can only find the source and I was hoping to avoid having to setup the tools for compiling that and hoped there was a validated Windows exe available somewhere?
Was annoying to have spent ages on the NVFlash backup procedure to now have that being (at the moment!) zero help whatsoever...
rtg2 said:
Sorry to hear you also have this issue. I broke mine in a very similar way and have been struggling to repair it too. Do you have a compiled version of the blob unpack tool? I can only find the source and I was hoping to avoid having to setup the tools for compiling that and hoped there was a validated Windows exe available somewhere?
Was annoying to have spent ages on the NVFlash backup procedure to now have that being (at the moment!) zero help whatsoever...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1890912
rtg2 said:
Sorry to hear you also have this issue. I broke mine in a very similar way and have been struggling to repair it too. Do you have a compiled version of the blob unpack tool? I can only find the source and I was hoping to avoid having to setup the tools for compiling that and hoped there was a validated Windows exe available somewhere?
Was annoying to have spent ages on the NVFlash backup procedure to now have that being (at the moment!) zero help whatsoever...
Click to expand...
Click to collapse
After about two days of messing with it, I did finally get success. I didn't bother updating this post, mainly because I wasn't entirely sure what I had done that made the difference. In retrospect, I was quite close most of the time. Reformatting /data to ext3 helped, as well as using my nvflash with bricksafe.img. I also wonder if I might have had a bad download, considering the chain of events. I *swear* I did all the things that needed to be done many times, but in the final round after a night of sleep I used fresh downloaded images of the TWRP recovery and CM10. Bottom line is, as long as you have done the nvflash tutorial properly, and backed up all the items as instructed, you should always be able to recover.
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 apologize if this has been covered in another thread but I have been doing multiple searches on XDA and in google trying to find a solution but so far no luck. Long time reader of XDA but first time poster.
Details -
I successfully used NVFLASH, loaded Clockworkmod 0.8 and loaded Vega-Ntab gingerbread edition (stable RC1 I believe its called). I have been running this for a month or so with no major issues but I want to test out Vega-Ntab 5.1 and Brilliant Corners. Thinking of going with 5.1 for the hardware acceleration for gaming etc. Oh I also received my new Gtab with bootloader 1.2 and I downgraded that to 1.1 successfully before loading Vega-Ntab gingerbread. I think I can handle loading the new roms etc (may have to switch to 1.2 for Brilliant Corners I believe) but I want to do a full backup before doing so with clockworkmod so I can go back to gingerbread if I decide I liked it the best. But clockworkmod will not do a backup for me. I have tried multiple times and it always freezes/hangs at the same point. On the screen I see
ClockworkMod Recovery v2.5.1.1-bekit-0.8
SD card space free: 9697MB
Backing up boot...
Backing up recovery...
Backing up system... and here it will go no further
I have let it set at that point for hours but nothing changes. I checked the clockworkmod backup folder and it has a folder dated the current date of the backup but the contents is only boot.img and recovery.img and nothing else so I think that confirms it really isnt completing the backup.
I am unsure what the cause or solution to this is. I thought about reloading clockworkmod 0.8 but I don't think I can do this since it's already loaded. I thought about loading a newer version but from what I have read gingerbread and the other 1.1 roms will not work with anything but 0.8. I could just do a melt and repour and just go back to stock level and load 5.1 or Brilliant Corners but then I lose any apps I have loaded. I am not concerned about the majority of them but I have loaded a couple good ones as of late from Amazon that were the free app of the day and I am unsure whether I can "reload" these at a later date without being forced to pay. I have also paid for a couple games but I am assuming I can reload those without issue. I did back up all of the apps I paid for and amazon games that I loaded that I got for free (normally have to pay) with titanium backup. So assuming I can restore these with titanium backup after loading brilliant corners or vegan 5.1 then I guess the only thing that I lose by not being able to do a full backup/restore with clockwork is that if I want to go back to gingerbread then I have to start from scratch for reloading the rom.
So is the problem I am having running the back up successfully a known issue that I just can't seem to find a discussion thread about?
Thanks in advance for any help or advice.
Boot into ClockworkMod Recovery and get me a dmesg output (kernel messages) using adb. See this post for how.
Attach the dmesg.txt to your next post.
thanks for the reply. Unfortunately I am not having any luck getting the dmesg.txt file for you. I downloaded the iso image for Knoppix 6 but when I boot off the disc it starts processing everything but then it gives an error "the file /mnt-system/knoppix/knoppix is broken. then after about 30 secs it gives the following
/sbin/init: line 76: syntax error near unexpected token '/usr/share/fonts/type1/gsfonts/a010013l.pfb'
/sbin/init: line 76: '/URWGothicL-Book (usr/share/fonts/type1/gsfonts/a010013l.pfb);
I will try and download the iso from a different site and burn another disc.
I also tried a different route and loaded SDK manager to get to ADB by that route. I am running windows 7 if that makes a difference. I am not 100% sure when I am supposed to run the adb command line you listed. Do I have my gtab running clockworkmod and then mount USB so it will show up on my pc? Do I have to try and perform a backup and then run the adb command when it freezes? I don't think I can do that because if I navigate away from the mount USB it automatically unmounts it. Anyway adb doesn't appear to be seeing the gtab anyway. When I run the SDK manager it does not find any android devices. If I run the "adb devices" command it comes back with no devices. So I am not sure what basic thing I am missing to get adb or SDK to recognize the gtab.
I apologize for my lack of knowledge on adb. Your first link says if I have adb already set up to run adb shell dmesg > dmesg.txt while in clockworkmod so I am assuming I do this after mounting USB to get the pc to recognize the gtab.
I will try download and burn another iso image from a different location and see if I can boot off a disc. Assuming this time it is successful do I run the ADB command you listed in the second link while the GTab is mounted to USB and recognized by the pc? Hopefully ADB will see it if I can get this to work.
*update* I downloaded the ISO image from a different location. When I went to the folder it was downloaded to I noticed that the first ISO image I downloaded was only approx 100MB in size instead of 700+ mb. So I am re-burning another disc. Hopefully this will allow me to boot properly.
*update #2* I was able to successfully boot off of the new disc. Now I just need to figure out how and where to enter the adb command line in your link ($ sudo ./adb shell dmesg > dmesg.txt) i tried this using the Shell option but it says command not found. If I choose the File Manager option and navigate to where the adb file is that was in your linked zip file it just prompts me to edit/copy/move/rename or delete the file. I am out of time tonight so I will work on it more tomorrow. The good news though is that when I use File Manager the Gtab is listed so it is at least recognized. Now I just need to figure out how to get the dmesg.txt file you request but making some progress... I think
ashton555 said:
*update #2* I was able to successfully boot off of the new disc. Now I just need to figure out how and where to enter the adb command line in your link ($ sudo ./adb shell dmesg > dmesg.txt)
Click to expand...
Click to collapse
Step by step instructions in this post.
thanks a bunch. Those instructions were easy to follow and made sense. I have never used linux before but alot of it reminded me back of my old unix days (terminal commands that is).
Anyway I think I did everything correct and I am now attaching the txt file.
Thanks again for your help and patience with this Linux newbie let me know if I need to provide any additional information.
ashton555 said:
Anyway I think I did everything correct and I am now attaching the txt file.
Click to expand...
Click to collapse
You did indeed. And I can't see any obvious problems with the NAND-flash device, judging from the kernel messages.
Since you've already tried to take backups using CWM before, that action should've created a log file. This file might be useful. Retrieve it. Inside an xterm window on Linux, run:
Code:
hostpc$ [B]sudo ./adb pull /cache/recovery/log recovery.log[/B]
Attach this "recovery.log" file.
Next, try to read, one by one, the NAND flash partitions that CWM usually backs up. Here's an example run on my gTablet:
Code:
hostpc$ [B]sudo ./adb shell[/B] [I]Get into the shell in CWM[/I]
~ # [B]dump_image boot /dev/null[/B]
~ # [B]dump_image recovery /dev/null[/B]
~ # [B]dump_image system /dev/null[/B]
mtd: read error at 0x029a0000 (I/O error)
mtd: read error at 0x02da0000 (I/O error)
~ # [B]dump_image cache /dev/null[/B]
~ #
Type in only the commands in bold.
As you can see, my "system" partition on the NAND flash has errors (and the kernel also report this when it boots), but, the command will not hang. According to the kernel message that you just supplied, you don't have any errors on your onboard NAND flash, so, theoretically, you shouldn't get any errors at all. But, we'll see if the dump_image command hangs when reading system just like CWM does.
And if the dump_image command does hang somewhere, we can see if formatting just that system partition will get it working again. There is a utility on this board which we could use for doing that, though I've never tried it.
I successfully completed the next two tasks. I am attaching the recovery.log file. Note I had an issue copying the .log file to where I could access it in win7 (for some reason I cant attach a file while in linux). I opened it with a word processor and then saved it to my c drive which messed up the formatting. So I opened it in Word to get the formatting correct and saved it as a txt file so thats why the attached file is recovery.txt. Let me know if it messed it up to where its not useable.
On the second task
~ # dump_image boot /dev/null
this worked fine and quick
~ # dump_image recovery /dev/null
this worked fine and quick
~ # dump_image system /dev/null
this worked but took maybe 10-15 seconds
~ # dump_image cache /dev/null
this one gave an I/O error but completed the dump
mtd: read error at 0x00080000 (I/O error)
ashton555 said:
Let me know if it messed it up to where its not useable.
Click to expand...
Click to collapse
The file is just fine... and I can't see any error messages in it.
~ # dump_image system /dev/null
this worked but took maybe 10-15 seconds
Click to expand...
Click to collapse
This is normal -- "system" partition is ~200MB.
~ # dump_image cache /dev/null
this one gave an I/O error but completed the dump
mtd: read error at 0x00080000 (I/O error)
Click to expand...
Click to collapse
This also looks like normal behaviour, but, I'm puzzled that the kernel did not report any bad blocks on this partition. Check if this is a transient error:
1. Repeat the "dump_image cache ..." command a few times and see if the I/O error location is the same.
2. Try to "fix" the error on the cache partition by using the "wipe cache partition" menu item in CWM. Do this a couple of times.
3. Run the "dump_image cache ..." command again.
4. Attempt another full system backup using CWM.
If step 4 fails, we'll see if the writing of the backup to the sdcard is the problem, because the reading seems to be completing without any hangs as of now.
BTW, the most important partitions are all being read fine. The "cache" partition is not that important -- it can be empty (but not corrupt) each time the system boots and only the initial bootup might go a little slower.
And, if, in the end of all this, you can't use CWM at all, you can still make a full system backup using nvflash and a few Unix commands.
1. Repeat the "dump_image cache ..." command a few times and see if the I/O error location is the same
....i did the dump 4 times and it always gave the same I/O location
2. Try to "fix" the error on the cache partition by using the "wipe cache partition" menu item in CWM. Do this a couple of times
.... I wiped the cache 4 times successsfully
3. Run the "dump_image cache ..." command again.
.... same I/O error location
4. Attempt another full system backup using CWM
.... still freezing at backing up system
So I guess I need to try and do the backup with NVFlash and unix/linux commands? If you have a link on how to do that I will give it a try or I can search for it and see if there is a discussion thread on it.
Thanks again for your help and trying to resolve this
Question - if I started over from scratch and went back to stock and then loaded vegan gingerbread would this issue possibly correct itself? Also more importantly if I back up some apps using titanium backup before I go back to stock can I then restore them with Titanium once I have vegan ginger back loaded? Also if I loaded vegan 5.1.1 could I restore the same apps I backed up in vegan ginger? Hopefully that made sense. I don't mind starting from scratch if I need to I just wasnt sure if I would permanently lose certain apps I have loaded. It's only about 10 apps I care about
*update* - well I think I am going to be forced to start over anyway. After wiping the cache a couple times and attempting another backup (froze again at backing up system) I now can't get the gtab to boot completely. It is stuck at the flashing vegan ginger edition screen. It flashes for awhile then the screen goes black then it goes back to the flashing screen again. I know you said it would take longer to boot up the first time after wiping the cache but was doing the flash cycling for over an hour which I assume is too long? I tried wiping the cache again and I also wiped the davlik cache as someone suggested in another thread but it is back to being stuck in the flashing screen loop. Assuming I do have to start over can I at least boot to CWM, mount ext USB and copy off the titanium backup files I made so I can restore some of the paid for apps?
ashton555 said:
3. Run the "dump_image cache ..." command again.
.... same I/O error location
Click to expand...
Click to collapse
Looks like a permanent I/O error in the cache partition, then. But, I don't understand why it is "system" which is hanging on backup.
4. Attempt another full system backup using CWM
.... still freezing at backing up system
Click to expand...
Click to collapse
Get me the recovery.log.
So I guess I need to try and do the backup with NVFlash and unix/linux commands?
Click to expand...
Click to collapse
I'll think this over during the weekend. In the mean-time, read through this thread. You can safely take a complete backup of your tablet while I do a bit of experimentation on a clockworkmod-like solution. But, I suspect that you may not be able to backup "cache" using nvflash going by the I/O errors. I have errors on my "system" partition and a nvflash backup fails on it, but CWM doesn't have any problems backing up and restoring.
Question - if I started over from scratch and went back to stock and then loaded vegan gingerbread would this issue possibly correct itself?
Click to expand...
Click to collapse
Probably not. But, see this thread. It shows you how to wipe all the partitions on the NAND flash device. We don't need to format the entire NAND flash. We can see if doing a few repeated formats of the "system" and "cache" partitions gets CWM working again, if you're willing to wipe "system"--you will have to load Vegan-Ginger right after this.
Also more importantly if I back up some apps using titanium backup before I go back to stock can I then restore them with Titanium once I have vegan ginger back loaded? Also if I loaded vegan 5.1.1 could I restore the same apps I backed up in vegan ginger? Hopefully that made sense. I don't mind starting from scratch if I need to I just wasnt sure if I would permanently lose certain apps I have loaded. It's only about 10 apps I care about
Click to expand...
Click to collapse
I haven't used Titanium backup so I can't say how well it works, but, judging from the reports that other users have made, what you're suggesting should work without any problems. User downloaded applications are stored either on /data or on /mnt/sdcard (for apps moved to SD card). Since your SD cards don't seem to be affected, you can go ahead with Titanium backup.
ashton555 said:
Assuming I do have to start over can I at least boot to CWM, mount ext USB and copy off the titanium backup files I made so I can restore some of the paid for apps?
Click to expand...
Click to collapse
Yeah, copy the files in CWM, then just do a "wipe data/factory reset" and see if it boot loop goes away.
But, before you do that, gimme a half-hour and I'll send you commands which you can use to save the files in /data and /sdcard. I just have to compile and test a new version of busybox. The tar command already present in CWM doesn't seem to work properly for me.
Attaching the recovery file
I am running the nvflash back up right now.
It successfully did part-1.img through part-11.img with no errors. The last thing it said though is
"rem CACHE PARTITION BACKUP NOT NEEDED
"nvflash.exe" -r --read 12 part-12.img
press enter to continue
Is this maybe because I wiped the cache and it's empty?
I looked on my ext SD card and the titanium backup files are there (except for a couple I had forgotten do ....) so I think I am okay for going back to square one if need be.
I will go ahead (tomorrow probably) try doing what is described thread about wiping partitions on the NAND device and just formating the system and cache partitions. I am assuming that at this point I guess its okay to go ahead and try to load vegan tab 5.1.1 instead of ginger again since I wanted to try out 5.1.1 anyway or if you have any experience with it would you recommend Brilliant Corners instead since its a newer rom. I think I will have to reload the 1.2 bootloader which is okay.
ashton555 said:
Attaching the recovery file
Click to expand...
Click to collapse
No errors in there.
The last thing it said though is
"rem CACHE PARTITION BACKUP NOT NEEDED
"nvflash.exe" -r --read 12 part-12.img
press enter to continue
Is this maybe because I wiped the cache and it's empty?
Click to expand...
Click to collapse
I think so. The cache partition isn't that important anyway, so it can be skipped.
I will go ahead (tomorrow probably) try doing what is described thread about wiping partitions on the NAND device and just formating the system and cache partitions.
Click to expand...
Click to collapse
I would suggest that you copy the Titanium backed-up apps safely away immediately, then format just the system and cache partitions as per that thread. You will need to be in APX mode to use nvflash.
Immediately after the nvflash, (since the system partition is now gone), boot into CWM, then do a factory reset, repartition the internal sdcard, copy the Vegan-5.1.1 update file onto the now clean sdcard through the PC and then flash it. This should give you a clean slate.
Then check if you can do a backup using CWM. If you still can't, then I'll see if a solution can be devised to do partial backups.
And, I have tried neither Vegan* nor Brilliant Corners, so the choice is up to you.
Sorry, my test commands aren't working so I can't send you those commands I promised to back up your /data and /system--I suspect a bad USB cable.
Original message> Hi guys,
does anybody knows how to restore folio and take it back to life?
My son played with my tablet and he messed something.
Now I have bricked tablet, black screen, no toshiba logo after turn on, nothing just green led :/
Only thing working is when I connect usb cable to pc, It connect as ATX.
I found some threads but they are so complicated
Can somebody help me and write for me restoration guide for dummies?
Edit: Does anybody have full dumps? I need bootloader, bct for start.
EDIT> I will pay 30 EUR to Who will help me to restore my dead tablet.
I need all dumps, bootloader, bct and short batch file for nvflash.
On what partition is bootloader? I can dump it but I don't know on what partition it is and I know a very little about nvflash.
Jon2555 said:
On what partition is bootloader? I can dump it but I don't know on what partition it is and I know a very little about nvflash.
Click to expand...
Click to collapse
I think bootloader is in ../prebuilt/bootloader.bin
I found good restore guide:
Backing Up
Download the latest Linux For Tegra (L4T) package from here and unzip it
Open a terminal and change to the following directory: linux4tegra/nvflash
the following command sends the vanilla bootloader into your device RAM (it will not overwrite anything)
# LD_LIBRARY_PATH=. ./nvflash --bl ../prebuilt/fastboot.stock.bin --go
the following command saves your disk partitioning (very important!)
# LD_LIBRARY_PATH=. ./nvflash -r --getpartitiontable partitiontable.txt
use the following command with to save the partitions one by one to your harddisk (see Partition Layout for details)
# for i in $(seq 2 14); do LD_LIBRARY_PATH=. ./nvflash -r --read $i part-$i.img; done
You should endup with part-2.img, part-3.img [...] up to part-14.img, and partitiontable.txt.
Keep them in a safe place if you intend to play a bit with your AC100.
Restoring
In the partitiontable.txt, you should see following pattern (you need the highlighted values for each partition you want to restore):
PartitionId=[PartitionId]
Name=...
DeviceId=18
StartSector=[StartSector]
NumSectors=[NumSectors]
BytesPerSector=2048
Open a terminal and change to the following directory: linux4tegra/nvflash
Reload the vanilla bootloader using the following command:
# LD_LIBRARY_PATH=. ./nvflash --bl fastboot.bin --go
For earch part-[PartitionId].img you want to restore, execute the following command:
# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite [StartSector] [NumSectors] part-[PartitionId].img
Reboot your device.
Do you manage to get folio to life?
cmjm said:
Do you manage to get folio to life?
Click to expand...
Click to collapse
not yet because I don`t have correct dumps and bootloader :/ so I am waiting for someone who dump me this and prepare script for nvflash.
I heared that bootloader.bin is in .../prebuilt but where is it???
Sent from my IDEOS S7 Slim using XDA App
ok, thank you.
Let's see if someone can do that for us.
you have installed the drivers apx.
Someone to help us.
I want and I asked where is the bootloder???
Sent from my Xoom using Tapatalk
In my I can no longer view, I'll try to search the web.
I can not find it. funny find several people who says that had solved the problem but no one is able to help.
yeah, I am also curious where is bootloader. There are two ways where can it be:
in partition 0 or 1 or somewhere in file tree. I don`t know :/
btw I have RMA this tablet and will get new from them. After that I could try to dump it.
this is good news.
I've tried everything and still nothing.
Gives news when you can.
I searched a bit in android git and find that prebuilt is in source code that Toshiba didn't release, only kernel... Only hope is dumping.
Sent from my IDEOS S7 Slim using XDA App
Any news??
cmjm said:
Any news??
Click to expand...
Click to collapse
finally I`ve give up. After RMA I received for small repay toshiba thrive so I don`t need dump anymore.
Thank you guys for all.
Is there a Solution?
How much do you have to pay?
I sent it to Toshiba and they have repair it for free.
Sent from my Desire HD using XDA App
So I am stuck in a bootloop and no obvious way out.
US Galaxy Player 4.0
Rooted and been on custom roms for a year now. Problem started after upgraded to latest CM. Tried going back to stock but no luck in resolution. I am able to get into recovery and download mode and flash with odin. I can run adb shell. Just won't boot. The error message I get is as follows:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
In my adb shell I can see that there is no "mmcblk0..." files at all.
I have tried to go through the full stock recovery and used the PIT files and the stock rom through odin. I get the same boot loop and cant get the data to wipe due to the same error. I can flash anything through Odin easily without fail but everything is stuck in boot loop. I just don't seem to have /data to wipe.
There are some other posts around which indicate the Partition may be screwed but I am not sure what it is supposed to look like or the command line syntax to use to correct.
http://forum.xda-developers.com/showthread.php?t=1468213&highlight=wipe+data+shell
I have several nandroid backups on an external location but now I can't get the external card to recognize in CWM so haven't been able to try to revert backwards that way. I have backup of efs and all other stuff just can't seem to get to it.
Anybody with Ideas or direct help are greatly appreciated
map1122 said:
So I am stuck in a bootloop and no obvious way out.
US Galaxy Player 4.0
Rooted and been on custom roms for a year now. Problem started after upgraded to latest CM. Tried going back to stock but no luck in resolution. I am able to get into recovery and download mode and flash with odin. I can run adb shell. Just won't boot. The error message I get is as follows:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
In my adb shell I can see that there is no "mmcblk0..." files at all.
I have tried to go through the full stock recovery and used the PIT files and the stock rom through odin. I get the same boot loop and cant get the data to wipe due to the same error. I can flash anything through Odin easily without fail but everything is stuck in boot loop. I just don't seem to have /data to wipe.
There are some other posts around which indicate the Partition may be screwed but I am not sure what it is supposed to look like or the command line syntax to use to correct.
http://forum.xda-developers.com/showthread.php?t=1468213&highlight=wipe+data+shell
I have several nandroid backups on an external location but now I can't get the external card to recognize in CWM so haven't been able to try to revert backwards that way. I have backup of efs and all other stuff just can't seem to get to it.
Anybody with Ideas or direct help are greatly appreciated
Click to expand...
Click to collapse
This is how we fix that with the Player 5 : http://forum.xda-developers.com/showthread.php?t=2398120&page=4 (read the whole thread from page 4 on)
You'll need to do pretty much the same thing but you need an image from the Player 4.:good:
recrtora above
Thank you Meticulus. I see that you were involved in the thread I referenced too and this is where I figured I needed to go. However this is where I get tripped up. The main issue being that I don't have an image from a 4.0 US player. The thread I linked to had the Intl Player shown... There were even a few requests for the US version later on in the thread.
So- Anyone want to share their US player working partition table?
Is this information contained in the .PIT files somehow?
anyway to retrieve this?
map1122 said:
Thank you Meticulus. I see that you were involved in the thread I referenced too and this is where I figured I needed to go. However this is where I get tripped up. The main issue being that I don't have an image from a 4.0 US player. The thread I linked to had the Intl Player shown... There were even a few requests for the US version later on in the thread.
So- Anyone want to share their US player working partition table?
Is this information contained in the .PIT files somehow?
anyway to retrieve this?
Click to expand...
Click to collapse
As far as I know that's the only way to do it is with the picture.... Be patient, I'm sure someone will post an image...
@zaclimon ???
Needed: out put of fdisk on mmcblk0
Code:
adb root
adb shell
fdisk -l /dev/block/mmcblk0
Then post a screenshot, or just the output.:highfive:
Meticulus said:
As far as I know that's the only way to do it is with the picture.... Be patient, I'm sure someone will post an image...
@zaclimon ???
Needed: out put of fdisk on mmcblk0
Code:
adb root
adb shell
fdisk -l /dev/block/mmcblk0
Then post a screenshot, or just the output.:highfive:
Click to expand...
Click to collapse
Here it is, do note that it's a intl device though too.
zaclimon said:
Here it is, do note that it's a intl device though too.
Click to expand...
Click to collapse
That's definately not what I expected... to see from the 4.0's partition table...
Meticulus said:
That's definately not what I expected... to see from the 4.0's partition table...
Click to expand...
Click to collapse
We only have mmc blocks for the actual storage of the device. The system partition and others are pure raw nand (which is why we use mtd and yaffs2)
Envoyé depuis mon Nexus 7 avec Tapatalk 4
zaclimon said:
We only have mmc blocks for the actual storage of the device. The system partition and others are pure raw nand (which is why we use mtd and yaffs2)
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Click to expand...
Click to collapse
So then, will recreating these partitions solve the OP problem?
Meticulus said:
So then, will recreating these partitions solve the OP problem?
Click to expand...
Click to collapse
Most probably because it will only touch /data and internal storage. Actually this is the first time I see a problem like this for the 4.0.
Envoyé depuis mon Nexus 7 avec Tapatalk 4
So any confidence in the international vs the US version being the same?
Now the next thing is I used the command fdisk to start trying to recreate the partitions using the post instructions you recommended. I did not get an option for "new". I attached the output from the shell command. Tried looking up shell command references on fdisk but is not helping me here. Is it because there is not mmcblk0 at all? I don't seem to be getting into the command mode of the fdisk command.
If I use fdisk -l /dev/block/mmcblk0 I get "no such file or directory"
map1122 said:
So any confidence in the international vs the US version being the same?
Now the next thing is I used the command fdisk to start trying to recreate the partitions using the post instructions you recommended. I did not get an option for "new". I attached the output from the shell command. Tried looking up shell command references on fdisk but is not helping me here. Is it because there is not mmcblk0 at all? I don't seem to be getting into the command mode of the fdisk command.
If I use fdisk -l /dev/block/mmcblk0 I get "no such file or directory"
Click to expand...
Click to collapse
Hmm... Can post a list of /dev/block ?
Code:
adb shell
ls /dev/block
Here you go.
map1122 said:
Here you go.
Click to expand...
Click to collapse
Hmmmmm .... see if you can get here: /sys/bus/platform/devices/s3c-sdhci.0 and post the output
Like so?
map1122 said:
Like so?
Click to expand...
Click to collapse
yes.... I'm not sure what's wrong but id recommend installing a full odin flashable rom...
Not sure what that would be for the 4.0..
Here is another place you can check /sys/bus/platform/devices/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0
Here is the output of that. No further.
I am already on fresh Odin flash. Several attempts actually. I have been able to flash back to Stock (and use PIT) files, access stock recovery. I did this first to think I could restore to OEM. Then flash the Terra-Silent kernel to obtain CWM and the IcyFusion Rom (did this again this morning so I could get adb to link). These are the only Odin flashable that I am aware of for the 4.0. Obviously nothing boots because the issues discussed here.
Thank you.
what does "partition SD Card" in the Advanced and Debugging menu in CWM do?
map1122 said:
Here is the output of that. No further.
I am already on fresh Odin flash. Several attempts actually. I have been able to flash back to Stock (and use PIT) files, access stock recovery. I did this first to think I could restore to OEM. Then flash the Terra-Silent kernel to obtain CWM and the IcyFusion Rom (did this again this morning so I could get adb to link). These are the only Odin flashable that I am aware of for the 4.0. Obviously nothing boots because the issues discussed here.
Thank you.
Click to expand...
Click to collapse
I don't know if those are "full" odin flashable roms.
Try here: http://forum.xda-developers.com/showthread.php?t=1531850
Yes, that is the one I am using to revert to stock and additional PIT. I checked MD5 sums too.
Would this kind of thing be backed up in a nandroid?
map1122 said:
Yes, that is the one I am using to revert to stock and additional PIT. I checked MD5 sums too.
Would this kind of thing be backed up in a nandroid?
Click to expand...
Click to collapse
No, It wouldn't be backed up in android...
I'm betting that the U.S. Odin ROM on that page is not a "full" recovery rom either... I'm downloading right now to check. If it isn't, we need to find out how safe it is to flash an INT version first then flash a USA over it.
On the 5.0, we can do that... and everything is OK but don't know about 4.0...
EDIT: Seem like the only difference is that INT has bootloaders and USA does not. That doesn't help us...
Hi all,
Thanks in advance for your help.
I've bricked--like totally bricked--my Nabi 2. On startup, it goes to the Nabi logo, flashes black for a moment and returns to the logo, and is unresponsive. I've tried starting up holding vol+, but nothing happens; no bootloader gets loaded.
How can I restore my device? I have installed nabilabs on my PC, but the Nabi device isn't recognized. I have installed both 32/64 bit drivers. I've also installed pdanet.
Thanks for your responses.
DB
dbbergen said:
Hi all,
Thanks in advance for your help.
I've bricked--like totally bricked--my Nabi 2. On startup, it goes to the Nabi logo, flashes black for a moment and returns to the logo, and is unresponsive. I've tried starting up holding vol+, but nothing happens; no bootloader gets loaded.
How can I restore my device? I have installed nabilabs on my PC, but the Nabi device isn't recognized. I have installed both 32/64 bit drivers. I've also installed pdanet.
Thanks for your responses.
DB
Click to expand...
Click to collapse
I have a similar situation. Major difference is that TWRP (v2.8.4.0) is installed and running, but there's no OS on it otherwise. I have tried various downloads (such as "246stock.zip", and TWRP says there was an error installing on ALL zip files I have tried. It can't be a bad download, since I have re-downloaded the files,. on different machines, and I get the same error each time. NabiLab and NabiLabGUI don't seem to work if there is not already a working OS on the tablet.
Seems like what I need is something like the microSD-based flash/install I used for my Nook Tablet (acclaim) to put CM11 on it. Is there, in fact, a way to outright flash a .IMG file of some sort onto this? Or have I already ruined this already worthless P.o.S.? At this point I'd be just as happy to run something like CyanogenMod on it, and forget the disaster that is the Nabi2 interface and bloatware (then hunt down some other utility for time and access controls).
Images tried, all of which gave me "Error flashing zip"
1937stock.zip
205stock.zip
2127stock.zip
246stock.zip
jelabarre59 said:
I have a similar situation. Major difference is that TWRP (v2.8.4.0) is installed and running, but there's no OS on it otherwise. I have tried various downloads (such as "246stock.zip", and TWRP says there was an error installing on ALL zip files I have tried. It can't be a bad download, since I have re-downloaded the files,. on different machines, and I get the same error each time. NabiLab and NabiLabGUI don't seem to work if there is not already a working OS on the tablet.
Seems like what I need is something like the microSD-based flash/install I used for my Nook Tablet (acclaim) to put CM11 on it. Is there, in fact, a way to outright flash a .IMG file of some sort onto this? Or have I already ruined this already worthless P.o.S.? At this point I'd be just as happy to run something like CyanogenMod on it, and forget the disaster that is the Nabi2 interface and bloatware (then hunt down some other utility for time and access controls).
Images tried, all of which gave me "Error flashing zip"
1937stock.zip
205stock.zip
2127stock.zip
246stock.zip
Click to expand...
Click to collapse
Those zips aren't flashable. You have to extract and restore them.
Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 2.4.6 ROM and bootloader.
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 246stock.zip files you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 2.4.6 ROM.
- Download this http://forum.xda-developers.com/showpost.php?p=50349692&postcount=89
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
- Reboot
Alternatively you can "restore" the new kitkat for Nabi. Just replace the instructions for 2.4.6 files above with these below.
3.0.13 stock zip
https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
3.0.13 bootloader
https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing
Not sure how bad your situation was but you may have to do a factory reset in TWRP as well. Try that if it doesn't boot after successfully doing the above.
aicjofs said:
Those zips aren't flashable. You have to extract and restore them.
Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 2.4.6 ROM and bootloader.
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 246stock.zip files you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 2.4.6 ROM.
- Download this http://forum.xda-developers.com/showpost.php?p=50349692&postcount=89
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
- Reboot
Alternatively you can "restore" the new kitkat for Nabi. Just replace the instructions for 2.4.6 files above with these below.
3.0.13 stock zip
https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
3.0.13 bootloader
https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing
Not sure how bad your situation was but you may have to do a factory reset in TWRP as well. Try that if it doesn't boot after successfully doing the above.
Click to expand...
Click to collapse
Just an update, I managed to get a warranty replacement, because it decided it didn't want to charge anymore. Got one of the newer units as a replacement, which has the much better power connector, and am running it as-is for the time being (their updated firmware isn't *as* bad, will have to see what happens with the Mattel ownership).
I am having the same type of issue. I currently have TWRP v2.3.3.0 (Nabi 1.9.3.7) installed, but it shows no OS installed. I attempted to restore to the 30.0.13 stock at got the following message:
E:Unable to wipe '/system'.
and got the Failed on the screen. I also attempted to use the wipe function on the system and got E: Unable to mount for /data, /data, /system, /cache, /data, /addon.
Any help would be greatly appreciated.
biglerad said:
I am having the same type of issue. I currently have TWRP v2.3.3.0 (Nabi 1.9.3.7) installed, but it shows no OS installed. I attempted to restore to the 30.0.13 stock at got the following message:
E:Unable to wipe '/system'.
and got the Failed on the screen. I also attempted to use the wipe function on the system and got E: Unable to mount for /data, /data, /system, /cache, /data, /addon.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You don't have the right TWRP version probably. That's the ICS version. Try the JB or KK version. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
OK, I had managed to repair the Nabi2s which was bricked before (the trick to "backup" the core files of the specific system, then extract files from 2_0_141107stock.zip), and restore. But for some reason it lost WiFi completely, so I figured I'd try re-flashing again. Now I have no TWRP, and cannot even make the device visible to boot to TWRP. Is it time to take out the sledgehammer, then send the pieces back to the founders at what used to be Fuhu?
I have gone round ans round on the site, tries to find which threads I had followed before, and I seriously think I NEVER want to buy another device where I can't wipe the HDD with a dd command, and boot an installer with a USB or DVD ever again.
jelabarre59 said:
OK, I had managed to repair the Nabi2s which was bricked before (the trick to "backup" the core files of the specific system, then extract files from 2_0_141107stock.zip), and restore. But for some reason it lost WiFi completely, so I figured I'd try re-flashing again. Now I have no TWRP, and cannot even make the device visible to boot to TWRP. Is it time to take out the sledgehammer, then send the pieces back to the founders at what used to be Fuhu?
I have gone round ans round on the site, tries to find which threads I had followed before, and I seriously think I NEVER want to buy another device where I can't wipe the HDD with a dd command, and boot an installer with a USB or DVD ever again.
Click to expand...
Click to collapse
If you can get to the bootloader screen you should be able to bring up fastboot and get TWRP back on tablet(or just boot to TWRP temporarily)
Did that tablet ever receive an update past KitKat?
No Wifi is usually one of two things.
1) Kernel(boot partition) doesn't match kernel modules(system partition). Fix: Restore both boot and system in TWRP.
2) The wifi conf is bad. Fix: Factory reset/wipe data partition Note: loses all personal data.
3) I suppose if there was an update past kitkat, maybe the bootloader or the misc partition got an update. Don't go down that route yet.
Here is the general flow for restoring things, should have everythin you need if you can get fastboot to come up:
https://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
My original(and only) notes on Nabi2s
https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
https://forum.xda-developers.com/showpost.php?p=58623597&postcount=2507
aicjofs said:
If you can get to the bootloader screen you should be able to bring up fastboot and get TWRP back on tablet(or just boot to TWRP temporarily)
Click to expand...
Click to collapse
There's the problem. At this point the tablet only gets as far as the initial Nabi logo. Trying the "<Vol+><power>" option gives me the "Booting Android recovery..." followed shortl by the dead android. That's all the tablet will do.
Is there no way to make a microSD boot? That was what I would do with my Nook Tablet ("acclaim"). Seriously, whomever thought Android should be automatically locked out from the very people who bought/paid for/own the devices should be smacked by each and every Android user out there.
Thanks very much for the info. Took me 2 days to find this.
aicjofs said:
If you can get to the bootloader screen you should be able to bring up fastboot and get TWRP back on tablet(or just boot to TWRP temporarily)
Here is the general flow for restoring things, should have everythin you need if you can get fastboot to come up:
https://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
My original(and only) notes on Nabi2s
https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
https://forum.xda-developers.com/showpost.php?p=58623597&postcount=2507
Click to expand...
Click to collapse
All these instructions presume I can get to a "recovery/bootloader" screen, which this tablet will NOT do. It gets the initial Nabi logo, and that's as far as it will ever go. You could leave it there for 5 hours and that's all it will do (happened to do that once letting it charge, and the Nabi likes to boot as soon as it gets power).
I would try your "nvflash", but it's a MSWin executable, and I'm running Linux.
I'm just wondering; if I had the appropriate image file, is there a way to do a raw dump/write to the USB port, forcing the data to a particular device? If I tail /var/log/syslog, then plug in the Nabi2s, I get these messages in the syslog (and nothing else from the tablet after that):
Code:
kernel: [ 5973.824134] usb 2-1: new high-speed USB device number 4 using ehci-pci
kernel: [ 5973.986609] ehci-pci 0000:00:1d.7: port 1 reset error -110
kernel: [ 5975.192071] usb 2-1: new high-speed USB device number 5 using ehci-pci
kernel: [ 5975.346686] ehci-pci 0000:00:1d.7: port 1 reset error -110
In theory there should be a raw device there somewhere (lsusb doesn't see it)
jelabarre59 said:
All these instructions presume I can get to a "recovery/bootloader" screen, which this tablet will NOT do. It gets the initial Nabi logo, and that's as far as it will ever go. You could leave it there for 5 hours and that's all it will do (happened to do that once letting it charge, and the Nabi likes to boot as soon as it gets power).
I would try your "nvflash", but it's a MSWin executable, and I'm running Linux.
I'm just wondering; if I had the appropriate image file, is there a way to do a raw dump/write to the USB port, forcing the data to a particular device? If I tail /var/log/syslog, then plug in the Nabi2s, I get these messages in the syslog (and nothing else from the tablet after that):
Code:
kernel: [ 5973.824134] usb 2-1: new high-speed USB device number 4 using ehci-pci
kernel: [ 5973.986609] ehci-pci 0000:00:1d.7: port 1 reset error -110
kernel: [ 5975.192071] usb 2-1: new high-speed USB device number 5 using ehci-pci
kernel: [ 5975.346686] ehci-pci 0000:00:1d.7: port 1 reset error -110
In theory there should be a raw device there somewhere (lsusb doesn't see it)
Click to expand...
Click to collapse
Keep in mind I had the Nabi 2S for all of a day, so what I am about to say only applies to the Nabi 2 not 2S. If you see no menu then there is a non functioning bootloader, or at least it doesn't load all the way. It won't front any USB port, and you won't see it with lusb. There is a way to manually start "forced recovery" though(or there was on the Nabi2) See this: https://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701 If you can short the solder joints, I would assume the 2S has them too. That will start the 3pserver on the tegra itself, and bring up a USB interface. I don't think you need the APX driver for linux but you might check. There are plenty of linux nvflash binaries out there. Here is one that should work for tegra3 for sure: http://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/ or search github and compile your own. That would allow what you want, however... I'm not sure where the bootloader partition is. In the notes I linked above I listed a cat /proc/partitions which I will markup below
179 0 15269888 mmcblk0
179 1 8192 mmcblk0p1 <---likely recovery partition but maybe boot
179 2 8192 mmcblk0p2 <---likely boot partition but maybe recovery
179 3 2048 mmcblk0p3 <---if like a Nabi 2 the EKS with crypto key
179 4 2048 mmcblk0p4 <---if like a Nabi 2 the linux backup partition table.
179 5 2097152 mmcblk0p5 <--- preload aka addon partition with all the Nabi apps and media
179 6 1572864 mmcblk0p6 <--- system partition
179 7 2097152 mmcblk0p7 <--- cache partition
179 8 2048 mmcblk0p8 <--- not sure
179 9 32768 mmcblk0p9 <---if like a Nabi 2 the USP or staging partition for placing blob files for flashing
179 10 2048 mmcblk0p10 <---Not sure
179 11 9435136 mmcblk0p11 <--- data partition
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
The problem here is the Nabi 2 had a 6MB partition that was clearly the bootloader. A 2MB that was the Nvidia/Tegra partition table(different structure then a linux PT), and a 4MB partition for the device parameters. Those are "nvidia partitions" and don't show up in the linux partition table. For the Nabi 2 the bootloader was nvidia partition 4
I would go about it like this:
Tear open the Nabi and see if it has the pins to force tegra to 3pserver
Get nvflash binary or compile one
Get the bootloader.bin from here(note the name is bootloader2S.bin and the commands below I have bootloader.bin so rename it: https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
Force the tablet to 3pserver with the pins
Check to see if it's there with lusb
Use the commands(if you are a linux guy I assume you know you may need sudo, or ./nvflash, etc, etc)
nvflash --bl bootloader.bin --getpartitiontable partitiontable.txt
^^^examine the partitiontable.txt and see if it clarifies where the bootloader might be. They like to call it EBT in tegra. I would tell you how to flash the botloader but I just don't know where it is. The bootloader tries to load the boot.img from the boot partition, and has some sort of watchdog where if it doesn't load boot.img in such and such amount of time, it will try and load recovery.img. If that doesn't happen it just sits there staring at you. You could try and flash boot and recovery and maybe that brings you back to something more familiar. Examine the partition table text and find out which is boot and recovery. Boot is usually LNX, and recovery SOS.
If you are still in nvflash mode after all of this and havent shut down the tablet use commands below. If you have to restart you need have a first command of "nvflash --bl bootloader.bin <some command>" then all subsequent commands just need "nvflash --resume <some command>"
If it's exactly like a Nabi 2 then this would be the flow. So if your partitiontable.txt shows EBT as 4, SOS as 7, and LNX as 8
nvflash --resume --rawdeviceread 0 3072 nabibricksafe.img
nvflash --resume --read 4 04_EBT_raw.img
nvflash --resume --read 7 07_SOS_raw.img
nvflash --resume --read 8 08_LNX_raw.img
<optional>
nvflash --resume --download 4 bootloader.bin
nvflash --resume --download 7 twrp.img
nvflash --resume --download 8 twrp.img
nvflash --resume --go
^^^I have no idea about the 3072. That gets the first 3 "nvidia partitions" on a Nabi2 but that may not be long enough for a 2S, you can make it a larger read to be on the safe side(maybe 6000). You are basically reading the critical part of the tablet, backing up the current partition 4, 7, and 8, before reloading 7,8 with TWRP. Then tablet should restart. Remember if you have to restart the tablet the "resume" won't work, you will need to issue something with -bl bootloader.bin after a fresh boot as the first command of the session. You could add
nvflash --resume --download 4 bootloader.bin
in the above if the partition table confirms its the bootloader partition(EBT). In fact that may actually be the ONLY command you need to bring back the bootloader text, I'm just being cautious since it's not my tablet and taking a conservative approach.
That will put TWRP in both boot and recovery partitions so that hopefully you can boot TWRP somehow. If we can, then we can go back and fix things in TWRP. This may be all you need.
Side note: I never used nvflash on a 2S so who even knows if all this typing means anything, and maybe the emmc is just bad and none of this matters. I'm just try to give you all the major things I can think of to save you time. Good luck!
jelabarre59 said:
Just an update, I managed to get a warranty replacement, because it decided it didn't want to charge anymore. Got one of the newer units as a replacement, which has the much better power connector, and am running it as-is for the time being (their updated firmware isn't *as* bad, will have to see what happens with the Mattel ownership).
Click to expand...
Click to collapse
Thank you very much you saved my day
---------- Post added at 08:10 AM ---------- Previous post was at 08:08 AM ----------
aicjofs said:
Keep in mind I had the Nabi 2S for all of a day, so what I am about to say only applies to the Nabi 2 not 2S. If you see no menu then there is a non functioning bootloader, or at least it doesn't load all the way. It won't front any USB port, and you won't see it with lusb. There is a way to manually start "forced recovery" though(or there was on the Nabi2) See this: https://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701 If you can short the solder joints, I would assume the 2S has them too. That will start the 3pserver on the tegra itself, and bring up a USB interface. I don't think you need the APX driver for linux but you might check. There are plenty of linux nvflash binaries out there. Here is one that should work for tegra3 for sure: http://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/ or search github and compile your own. That would allow what you want, however... I'm not sure where the bootloader partition is. In the notes I linked above I listed a cat /proc/partitions which I will markup below
179 0 15269888 mmcblk0
179 1 8192 mmcblk0p1 <---likely recovery partition but maybe boot
179 2 8192 mmcblk0p2 <---likely boot partition but maybe recovery
179 3 2048 mmcblk0p3 <---if like a Nabi 2 the EKS with crypto key
179 4 2048 mmcblk0p4 <---if like a Nabi 2 the linux backup partition table.
179 5 2097152 mmcblk0p5 <--- preload aka addon partition with all the Nabi apps and media
179 6 1572864 mmcblk0p6 <--- system partition
179 7 2097152 mmcblk0p7 <--- cache partition
179 8 2048 mmcblk0p8 <--- not sure
179 9 32768 mmcblk0p9 <---if like a Nabi 2 the USP or staging partition for placing blob files for flashing
179 10 2048 mmcblk0p10 <---Not sure
179 11 9435136 mmcblk0p11 <--- data partition
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
The problem here is the Nabi 2 had a 6MB partition that was clearly the bootloader. A 2MB that was the Nvidia/Tegra partition table(different structure then a linux PT), and a 4MB partition for the device parameters. Those are "nvidia partitions" and don't show up in the linux partition table. For the Nabi 2 the bootloader was nvidia partition 4
I would go about it like this:
Tear open the Nabi and see if it has the pins to force tegra to 3pserver
Get nvflash binary or compile one
Get the bootloader.bin from here(note the name is bootloader2S.bin and the commands below I have bootloader.bin so rename it: https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
Force the tablet to 3pserver with the pins
Check to see if it's there with lusb
Use the commands(if you are a linux guy I assume you know you may need sudo, or ./nvflash, etc, etc)
nvflash --bl bootloader.bin --getpartitiontable partitiontable.txt
^^^examine the partitiontable.txt and see if it clarifies where the bootloader might be. They like to call it EBT in tegra. I would tell you how to flash the botloader but I just don't know where it is. The bootloader tries to load the boot.img from the boot partition, and has some sort of watchdog where if it doesn't load boot.img in such and such amount of time, it will try and load recovery.img. If that doesn't happen it just sits there staring at you. You could try and flash boot and recovery and maybe that brings you back to something more familiar. Examine the partition table text and find out which is boot and recovery. Boot is usually LNX, and recovery SOS.
If you are still in nvflash mode after all of this and havent shut down the tablet use commands below. If you have to restart you need have a first command of "nvflash --bl bootloader.bin <some command>" then all subsequent commands just need "nvflash --resume <some command>"
If it's exactly like a Nabi 2 then this would be the flow. So if your partitiontable.txt shows EBT as 4, SOS as 7, and LNX as 8
nvflash --resume --rawdeviceread 0 3072 nabibricksafe.img
nvflash --resume --read 4 04_EBT_raw.img
nvflash --resume --read 7 07_SOS_raw.img
nvflash --resume --read 8 08_LNX_raw.img
<optional>
nvflash --resume --download 4 bootloader.bin
nvflash --resume --download 7 twrp.img
nvflash --resume --download 8 twrp.img
nvflash --resume --go
^^^I have no idea about the 3072. That gets the first 3 "nvidia partitions" on a Nabi2 but that may not be long enough for a 2S, you can make it a larger read to be on the safe side(maybe 6000). You are basically reading the critical part of the tablet, backing up the current partition 4, 7, and 8, before reloading 7,8 with TWRP. Then tablet should restart. Remember if you have to restart the tablet the "resume" won't work, you will need to issue something with -bl bootloader.bin after a fresh boot as the first command of the session. You could add
nvflash --resume --download 4 bootloader.bin
in the above if the partition table confirms its the bootloader partition(EBT). In fact that may actually be the ONLY command you need to bring back the bootloader text, I'm just being cautious since it's not my tablet and taking a conservative approach.
That will put TWRP in both boot and recovery partitions so that hopefully you can boot TWRP somehow. If we can, then we can go back and fix things in TWRP. This may be all you need.
Side note: I never used nvflash on a 2S so who even knows if all this typing means anything, and maybe the emmc is just bad and none of this matters. I'm just try to give you all the major things I can think of to save you time. Good luck!
Click to expand...
Click to collapse
Thank you guys keep up the good work
Hello i have a serious problem with nabi jr tab of my friend's , the model no. is SNBJR-MT5C , my friend was using busybox and adb , when he tried to add .bak file for fuhu in system/apps ,because he wanted to get rid of the password each time device starts, this resulted in a bootloop , because there was no twrp installed , as this device was running kitkat , he tried using a backup from here somewhere in xda but without scatter and files.md5 , so he manually make files.md5 and generated scatter from mtk droid tools from firmware.info , but when he tried flash from sp flash tool , it did not accept that scatter, because pre-loader and mbr has start address 0 , because scatter version was wrong, mtk droid tools generated MT6582_sctter.txt, but it was MT8127 SoC , MT6582 - v111, MT8127 - v112 , so he got v112 from somewhere , and then retried and it got DA(Download Agent) error , so he made a mistake and changed DA and it bricked it completely , now its black screen and it wont turn on , even wont go in fastboot/recovery mode by holding power button and volume + or - buttons , also not showing anything in pc device manager , its totally dead , does anyone had the same experience ? or can anyone guide me about anything? Thanks
aicjofs said:
Keep in mind I had the Nabi 2S for all of a day, so what I am about to say only applies to the Nabi 2 not 2S. If you see no menu then there is a non functioning bootloader, or at least it doesn't load all the way. It won't front any USB port, and you won't see it with lusb. There is a way to manually start "forced recovery" though(or there was on the Nabi2)
Click to expand...
Click to collapse
I managed to get all the pieces of my daughter's Nabi 2S in one place (well, except for the bumper, I had multiples so I must have one still available. But did find the right charger cable). Since she has a different tablet to use for now (I was given 4 XO tablets; one, maybe two actually work) I could send this to a developer who wants to dabble with the hardware. Mind you, it's bricked, so it powers up but can't get to recovery menus, etc. The Nabi 2S doesn't appear to have the solder joints to do a forced recovery, but there is something that looks like it might be a button to do the same thing.
It's April 2018, if there's a developer who wants to try out other experiments on a Nabi2s that's otherwise bricked, you can still contact me. The Nabi is sitting in a box in the closet, it's not doing anything, and my daughter is now using an OLPC OX tablet instead (hey, got 4 of them for free, 2 actually power up).
(yeah, want to re-flash that second one someday as well, just to get it to a clean, stripped-down base to start from).
Hello bro I have a different situation here I have a nabi 2 nv7a I installed twrp on it and deleted the previous ROM to install new one but unfortunately when I try to install any ROM it shows error e\ unable to mount storage then I figured that the solution for it is to change the type of internal storage but the twrp I installed doesn't have any option of changing the type I went to wipe internal storage there was only one option that swipes and when I wipes then it also shows e/unable to mount and there is no option of changing type and I'm unable to change my twrp because I have no is plssss someone help