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
Related
*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.
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...
Hello,
I've just received new phone, Alcatel One Touch Fire E (6015X).
This phone has got installed FirefoxOS,
my question is can I install android somehow?
I was looking for that information however not found anything what would help me.
kmlnvm said:
Hello,
I've just received new phone, Alcatel One Touch Fire E (6015X).
This phone has got installed FirefoxOS,
my question is can I install android somehow?
I was looking for that information however not found anything what would help me.
Click to expand...
Click to collapse
Hello,
I'm looking for a recovery image of this phone, do you know of any location to find one? Or could you possibly make one very please to help such people out? Hamachi (Flame) builds dont work.
uxuxux said:
Hello,
I'm looking for a recovery image of this phone, do you know of any location to find one? Or could you possibly make one very please to help such people out? Hamachi (Flame) builds dont work.
Click to expand...
Click to collapse
if you could tell me how to extract it from my phone, i can make it for you
jecustoms said:
if you could tell me how to extract it from my phone, i can make it for you
Click to expand...
Click to collapse
Hey, thanks for your offer. I found a guide for the Alcatel Flame, but I think we are interested in Step 5 only.
Code:
Step 5: Create backup images
Now start shell on the phone using adb shell command and dump backup images to SD card:
$ cat /dev/mtd/mtd0 >/mnt/sdcard/boot.img
$ cat /dev/mtd/mtd1 >/mnt/sdcard/system.img
$ cat /dev/mtd/mtd5 >/mnt/sdcard/userdata.img
$ cat /dev/mtd/mtd7 >/mnt/sdcard/recovery.img
When finished (you may also dump some more MTD partitions if you like), transfer those files to your computer. You may again use ADB for that:
$ mkdir hamachi-backup
$ I="boot.img system.img userdata.img recovery.img"
$ for i in $I; do adb pull /mnt/sdcard/$i hamachi-backup/; done
I can't link yet but it's from Krzysztof Adamski's blog, the full post is titled Alcatel One Touch Fire Hacking (Mini)Guide.
Maybe it would be enough, as the alcatel source for this device is not available yet on their sourceforge page, I'm not sure if it's possible to make a full recovery image without that.
I found another mention of such thing on the b2g-dev mail list
Code:
> You can backup the partitions from a working phone using 'dd' to dump
> them (you can find the relevant devices under /dev/block) and then use
> fastboot to flash them on the bricked phone (provided that fastboot
> still works).
first of all, i am a total noob..
"Now start shell on the phone using adb shell command"
what does it mean? how can start it?
I was toying around with some stuff in my Chromebooks firmware with an external flasher. I messed something up and forgot to backup my stock bios like an *****. Can someone send me theirs by opening a developer shell and typing: sudo flashrom -r bios.bin then send me the file produced. Thank you!
Help with same issue... PLEASE
cammykool said:
I was toying around with some stuff in my Chromebooks firmware with an external flasher. I messed something up and forgot to backup my stock bios like an *****. Can someone send me theirs by opening a developer shell and typing: sudo flashrom -r bios.bin then send me the file produced. Thank you!
Click to expand...
Click to collapse
I have the same problem could a stock rom be provided to me as well...would be greatly appreciated this is my first chromebook project....
cammykool said:
I was toying around with some stuff in my Chromebooks firmware with an external flasher. I messed something up and forgot to backup my stock bios like an *****. Can someone send me theirs by opening a developer shell and typing: sudo flashrom -r bios.bin then send me the file produced. Thank you!
Click to expand...
Click to collapse
sorry only got this error:
Block protection could not be disabled!
Reading flash... bios.bin: Read-only file system
FAILED.FAILED
I saw a post on reddit about sanitizing an android device but I was wondering how I could execute the command? I managed to root my device but I'm at a loss as to how to execute it. Through adb? But it doesn't seem to be a valid command.
Help is much appreciated.
The script is:
Code:
cd /data; for i in 0 1 2 3 4 5 6 7 8 9; do cat /dev/urandom > $i; rm $i; done
thumbtwists said:
I saw a post on reddit about sanitizing an android device but I was wondering how I could execute the command? I managed to root my device but I'm at a loss as to how to execute it. Through adb? But it doesn't seem to be a valid command.
Help is much appreciated.
The script is:
Click to expand...
Click to collapse
Do you know what these commands are supposed to do?
Sent from my Sony Xperia Z3 Compact using XDA Labs
Ticklefish said:
Do you know what these commands are supposed to do?
Sent from my Sony Xperia Z3 Compact using XDA Labs
Click to expand...
Click to collapse
Yeah, the poster described it as:
"That will perform a deletion of free space that is superior to "military grade", and unlike some proprietary app, I know exactly what it's doing.
PS. In case you can't read it- It loops 10 times. Each loop it creates a file, starting with the file name "/data/0". It fills that file with random information and will stop when the storage area is full. All freespace will have been consumed by the random information in that file. Then immediately delete the file, and the space will be free again, and the freespace will be random information. Repeat this process 9 more times with file names "1", "2", "3", and so on..."