Fully working nvflash(APX Mode) for Toshiba Folio 100
Working :
- bootloader (toshiba logo)
- fully working fastboot
issue :
- Blank MBR after flashing from fastboot
I'm working this based on [REQ] Toshiba folio 100 BCT and partition dumps Thread
And reference from Hacking the Toshiba AC100
I'm running this on Toshiba AS100 also known as Folio 100 wtih 8GB of internal storage
it should be working on 16GB version
files :
bootloader.bin --> Toshiba Folio 100 bootloader
busybox --> busybox v1.18.4
Fix-MBR.cmd --> Fix MBR after flashing from fastboot
folio100.xls --> my summary about partition table on folio 100 and ac100
new.bct --> downloaded form my folio 1000
NVFlash-Folio100.cmd --> all-in-one working nvflash and partition script
NVFlash.txt --> nvflash documentation
env.cmd --> start command prompt with adb,fastboot and nvflash support
flash.cfg --> i created this config file based on my summary
part.run --> parititon creation script
part.txt --> fdisk partition parameter
part-layout.txt --> Fdisk partition layout
Before you run NVFlash-Folio100.cmd you need to download CWM Recovery image from
Files needed :
1. cwm.img --> CWM Recovery
download from :
[RECOVERY][UPDATE] Unofficial port of ClockworkMod Recovery for folio100 - BETA
[recovery] CWM for Betelgeuse v0.3 - Now with USB support
note : extract the file until you got recovery.img,then rename it to cwm.img
2. boot.img --> Kernel image
3. system.img --> System partition image
4. recovery.img --> Recovery image
Download working ROM :
DISCONTINUED - [ROM][19-feb-2011] FolioMod v1.4 for Toshiba Folio100
Driver :
1. Toshiba Folio 100 ADB and Fastboot driver
This is standard Google USB Driver,i have modified some entries for working on Toshiba Folio 100
Download link
2. NVIDIA USB Boot-recovery driver also known as APX Driver
Download link
After you have all needed file double click NVFlash-Folio100.cmd
Connect your device using micro usb cable in APX mode
After finished flash from NVFlash your device will automatically boot to CWM Recovery
While CWM Recovery on standby menu,press any key to continue the script for partition and formating
After that just reboot your device.
If you just flashed your device using fastboot enter CWM Recovery and run Fix-MBR.cmd
Note :
APX mode --> On Toshiba boot screen press Power 4x then Vol- (if you have enter this mode,you need to full flash from NVFlash)
Fastboot mode --> On Toshiba boot screen press Power 3x then Vol-
Recovery mode --> On Toshiba boot screen press Power + Vol+
If you stuck on something just long press the power button,it will power off the device
if you're already flashed from NVFlash and unable to enter APX Mode,you need to disassembly your device.Disconnect cable from NAND and then power on the device.After it connected in APX mode,you can connect the NAND cable and flash it using NVFlash.
For disassembly reference Folio 100 Disassembly - Pictures
The NAND flash is connected using white short film cable.
Folio100-NVFlash-Final.zip download link
Thanks a lot! Great work!!!
what does it do?
Is it a Custom Rom or something else?
Crunon said:
what does it do?
Is it a Custom Rom or something else?
Click to expand...
Click to collapse
Fully working solution for bricked and corupted internal storage partition of Toshiba Folio 100.
Thanks so much.
I followed your guide and save my friend's table
need help please
nvramFolio stucks:
D:\temp\Folio100-NVFlash-Final>nvflash.exe --bct %bct% --setbct --bl %bl% --configfile %config% --odmdata 0x000c0075 --c
reate --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 2
chip sku: 0x8
chip uid: 0x17006181434001d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: new.bct
- 4080/4080 bytes sent
new.bct sent successfully
command failure: bootloader download failed
Click to expand...
Click to collapse
How long do I have to wait? I wait 15min.
then I tryed this:
D:\temp\Folio100-NVFlash-Final>nvflash.exe --bl %bl% --configfile %config% --odmdata 0x000c0075 --create --go
Nvflash started
uid read failed
Click to expand...
Click to collapse
I used driver from the link and in both cases I had done a hard reset.
THX for help!
Miraculix666 said:
nvramFolio stucks:
How long do I have to wait? I wait 15min.
then I tryed this:
I used driver from the link and in both cases I had done a hard reset.
THX for help!
Click to expand...
Click to collapse
If the process have failed,you need to turn off your device and then turn it back on before starting a new process.that why you got this :
Code:
Nvflash started
uid read failed
"UID read failed" is the message after power down.
I assume an error while flashing the bootloader. right?
The history for the error was:
-ICS_r4 cwm_0.3_Betelegeuse (all fine)
-update cwm5. & ICS_alpha (internal sd missing in ICS, internal sd acsessible in cwm)
-trying format and wipe from fastboot and cwm
-internal sd missing in cwm
-flashing back to cwm 0.3 & ICS_r4 (internal sd missing)
-flashing cwm5. & ICS_alpha (internal sd missing)
-found out partition table is corrupted (no info at fdisk)
-tryed to fix that way http://forum.xda-developers.com/showthread.php?t=1470823&page=18 boot.zip)
-tryed to fix that way http://bb2k.org/folio100wiki/index...._.28included_in_the_TV-Dock.29_doesn.27t_work
from adb and then I had this
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
~ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 1944064.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x00,0x00 of partition table 5 will be corrected by w(rite)
Command (m for help): p
p
Disk /dev/block/mmcblk0: 15.9 GB, 15925772288 bytes
1 heads, 16 sectors/track, 1944064 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 129 32896 262144 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 32897 163968 1048576 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 163969 164224 2048 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 164225 1943360 14233088 5 Extended
Partition 4 does not end on cylinder boundary
Click to expand...
Click to collapse
-flashed update_createpart.zip (now only APX booting.)
I tryed:
D:\temp\Folio100-NVFlash-Final>nvflash.exe --bct new.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0
x000c0075 --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 2
chip sku: 0x8
chip uid: 0x17006181434001d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: new.bct
- 4080/4080 bytes sent
new.bct sent successfully
Click to expand...
Click to collapse
(stays at this point for a hour)
then I tryed:
nvflash.exe --configfile %config% --odmdata 0x000c0075 --create --format_all
Click to expand...
Click to collapse
and
nvflash.exe --bct %bct% --setbct --configfile %config% --odmdata 0x000c0075 --create
Click to expand...
Click to collapse
I made a reset after 15min in cause of no response.
should I disassemble? If yes, connecting nand with power on or
disconnect->on->off->connect->on->nvflash
Is it required that the power plug is connected?
If you intrested, i can guide you via gtalk.check my PM.
Here Full log of successful NVFlash-Folio100.cmd
folio dead
After programming with nflash I have a problem the folio will not start more ... Fix-MBR gives me this error log
connect your device in CWM Recovery
Premere un tasto per continuare . . .
28 KB/s (146 bytes in 0.005s)
The number of cylinders for this disk is set to 486016.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): Changing display/entry units to sectors
Command (m for help): First sector (2645008-31105023, default 2645008): First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): First sector (2645008-31105023, default 2645008): First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): First sector (2645008-31105023, default 2645008): First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): First sector (2645008-31105023, default 2645008): First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Using default value 2645008
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Value is out of range
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Value is out of range
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Value is out of range
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Value is out of range
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Value is out of range
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Value is out of range
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Value is out of range
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Using default value 2645999
Command (m for help):
Disk /dev/block/mmcblk0: 15.9 GB, 15925772288 bytes
4 heads, 16 sectors/track, 486016 cylinders, total 31105024 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 2048 526335 262144 83 Linux
/dev/block/mmcblk0p2 526336 2623487 1048576 83 Linux
/dev/block/mmcblk0p3 2623488 2627583 2048 83 Linux
/dev/block/mmcblk0p4 2627584 31105023 14238720 5 Extended
/dev/block/mmcblk0p5 2628608 2644991 8192 83 Linux
/dev/block/mmcblk0p6 2646016 4743167 1048576 83 Linux
/dev/block/mmcblk0p7 4744192 4754431 5120 83 Linux
/dev/block/mmcblk0p8 4754448 31105023 13175288 83 Linux
/dev/block/mmcblk0p9 2627600 2628607 504 83 Linux
/dev/block/mmcblk0p10 2645008 2645999 496 83 Linux
Partition table entries are not in disk order
Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table
" "
" Please reboot your device "
" "
folio is dead??
retry with full flash from NVFlash-Folio100.cmd
puppet13th said:
retry with full flash from NVFlash-Folio100.cmd
Click to expand...
Click to collapse
After another flash, log this message:
extraneo said:
After another flash, log this message:
Click to expand...
Click to collapse
when you're getting this :
Code:
waiting device to bootup . . .
press any key if the device have entered CWM Recovery . . .
unmount /cache from recovery
then continue that nvflash script
puppet13th said:
when you're getting this :
Code:
waiting device to bootup . . .
press any key if the device have entered CWM Recovery . . .
unmount /cache from recovery
then continue that nvflash script
Click to expand...
Click to collapse
Thanks for help but no change. same message.
Great guide and great tools.
Just one question: after I've run the NVFlash-Folio100.cmd, you say to run fixmbr. This throws an error message
connect your device in CWM Recovery
Press any key to continue . . .
28 KB/s (146 bytes in 0.005s)
The number of cylinders for this disk is set to 485840.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): Changing display/entry units to sectors
Command (m for help): First sector (2627600-31093759, default 2627600): First se
ctor (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): First sector (2627600-31093759
, default 2627600): First sector (2627600-31093759, default 2627600): Value is o
ut of range
First sector (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): First sector (2627600-31093759
, default 2627600): First sector (2627600-31093759, default 2627600): Value is o
ut of range
First sector (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): First sector (2627600-31093759
, default 2627600): First sector (2627600-31093759, default 2627600): Value is o
ut of range
First sector (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): Using default value 2627600
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Las
t sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Value
is out of range
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Val
ue is out of range
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Las
t sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Value
is out of range
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Val
ue is out of range
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Las
t sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Value
is out of range
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Val
ue is out of range
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Las
t sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Value
is out of range
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Usi
ng default value 2628607
Command (m for help):
Disk /dev/block/mmcblk0: 15.9 GB, 15920005120 bytes
4 heads, 16 sectors/track, 485840 cylinders, total 31093760 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 2048 526335 262144 83 Linux
/dev/block/mmcblk0p2 526336 2623487 1048576 83 Linux
/dev/block/mmcblk0p3 2623488 2627583 2048 83 Linux
/dev/block/mmcblk0p4 2627584 31093759 14233088 5 Extended
/dev/block/mmcblk0p5 2628608 2644991 8192 83 Linux
/dev/block/mmcblk0p6 2646016 4743167 1048576 83 Linux
/dev/block/mmcblk0p7 4744192 4754431 5120 83 Linux
/dev/block/mmcblk0p8 4754448 31093759 13169656 83 Linux
/dev/block/mmcblk0p9 2627600 2628607 504 83 Linux
Partition table entries are not in disk order
Command (m for help): The partition table has been altered!
Calling ioctl() to re-read partition table
" "
" Please reboot your device "
" "
Press any key to continue . . .
Click to expand...
Click to collapse
I'm also getting "E: Can't mount /cache/recovery/command" and similar strings when CWM is running... At present, Folio100-NVFlash-Final is the only way I'm able to get the tablet working, and cannot install any other rom...
any advice on how/if this can be fixed?
yellowumbrella said:
Great guide and great tools.
Just one question: after I've run the NVFlash-Folio100.cmd, you say to run fixmbr. This throws an error message
I'm also getting "E: Can't mount /cache/recovery/command" and similar strings when CWM is running... At present, Folio100-NVFlash-Final is the only way I'm able to get the tablet working, and cannot install any other rom...
any advice on how/if this can be fixed?
Click to expand...
Click to collapse
I reported the same problem. NVflash contains a BUG??? ... perhaps it is better not to use it.
Well, it was/is my only option to get the tablet working at present. After my friend kicked it into apx mode, nvflash was the only solution (as far as I'm aware). And now if I try to flash other roms and fail, the only way to get the tablet working is to force apx and use nvflash...
Sent from my SGH-T849 using XDA
Hint : if you have entered CWM stage,the nvflash solution was working properly.
After that you need to create partition table for it
I have successfully done this for 8GB version.
Maybe the partition layout was diffrent between 8GB and 16GB.
I can try to help trought gtalk chat.
If you instrested , pm me.
Sent from my ST17i using Tapatalk
puppet13th said:
Maybe the partition layout was diffrent between 8GB and 16GB.
I can try to help trought gtalk chat.
If you instrested , pm me.
Click to expand...
Click to collapse
I have the same Problem with my 16gb Folio.
Recovery works, but thats all...
Can you poste the right way if it works with yellowumbrella?
Hello all ,
I linked a serial cable to my allwinner a20 based Android Tv box.
It can not pass after the boot logo and next is all what it display in serial console.
Somebody pelase help i need to reisntall linux on it ,if you knwo any u boot keys that i have to press on the uboot serial consoel pelase help.I tryed to press ransom keys but i see nothin.
Here is all i see when it start:
====================================
HELLO! BOOT0 is starting!
boot0 version : 3.0.0
dram size =512
sum=0x9c3bd8cf
src_sum=0x9c3bd8cf
Ready to disable icache.
Jump to secend Boot.
[ 0.133]
U-Boot 2011.09-rc1-dirty (Nov 08 2013 - 11:06:32) Allwinner Technology
[ 0.141]version: 1.1.0
[ 0.144]pmbus: ready
axp read error
probe axp20x failed
axp_probe error
boot_clock = 912
dcdc2_vol = 1400
axp set dcdc2_vol to 1400 failed
dcdc3_vol = 1250
ldo2_vol = 3000
ldo3_vol = 2800
ldo4_vol = 2800
power_start = 0
storage_type = -1
usb_recovery = 0
find power_sply to end
fel key old mode
run key detect
no key found
no key input
dram_para_set start
dram_para_set end
[ 0.293]DRAM: 512 MiB
relocation Offset is: 15b27000
user_gpio config
user_gpio ok
DRV_DISP_Init: opened
[ 0.560]boot_disp.output_type=2
[ 0.563]boot_disp.output_mode=5
[ 0.567]boot_disp.auto_hpd=1
workmode = 0
[ 1.871]NAND: NAND_UbootInit
NB1 : enter NAND_LogicInit
nand : get id_number_ctl from script, 3
not burn nand partition table!
NB1 : nftl num: 3
init nftl: 0
NB1 : NAND_LogicInit ok, result = 0x0
[ 2.381]sunxi flash init ok
In: serial
Out: serial
Err: serial
--------fastboot partitions--------
-total partitions:12-
-name- -start- -size-
bootloader : 1000000 1000000
env : 2000000 1000000
boot : 3000000 1000000
system : 4000000 20000000
recovery : 24000000 2000000
databk : 26000000 2000000
misc : 28000000 1000000
private : 29000000 1000000
sysrecovery : 2a000000 21000000
data : 4b000000 40000000
cache : 8b000000 17000000
UDISK : a2000000 0
-----------------------------------
base bootcmd=run setargs_nand boot_normal
bootcmd set setargs_nand
key 0
recovery key high 6, low 4
cant find fstbt value
Fastboot detected, will boot fastboot
to be run cmd=run setargs_nand boot_fastboot
the user data'magic is bad
WORK_MODE_BOOT
board_status_probe
sunxi_bmp_display
WORK_MODE_BOOT
[ 2.509]Hit any key to stop autoboot: 0
run usb fastboot
sunxi_fastboot_init
recv addr 0x41000000
send addr 0x582580a8
delay time 0
usb init ok
------------------------------------------------------------------
After this nothing .Please help me
After searching all google and reading documantation ,I contacted the box seller and he gied me the files i neeeded.
I used a image file named sun7i_A20v2.0_android_sugar-ref001_2014.09.04_TakenYBSJ.img and a windwos software to flash it via usb named PhoenixPacketV333
To flash teh device you muist hava a serial console to the box (veru easy to do if you have the cable ) ,and keep pushed the key 2
on serial consle (putty) while powering the device ,so it enter in fel mode ( something like recovery mode ,it accept usb connection) .Then oyu need a usb male to male cable to conect the android tv box usb port to the windows usb port ,and start flasing using the PhoenixPacketV333 software.
If somebody needs more help or files just write here I check daily .
have a nice day all!
Hello
I've bricked Oppo F1s when I've tried to flash it
this is infinity read info log
Wait for phone...
Phone found! [ 1087 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6755
BB_CPU_NME : [MediaTek] Helio[P10]|MT6755_S00
BB_CPU_EXT : 0xCB00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x01000000
BromVer : 0x0005
BLVersion : 0x00FE
PreLoader : NOT Active [ Erased ]
BootLdrSS : SIGNED with SPRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
DAgent configured successfully
Connection agent : BROM
[DA_ERROR] : DRAM Configure failed!
ErroCode : 0x2122and I get this message error if I try to flash it with MT6750
Error: STATUS_INSUFFICIENT_BUFFER
EMICFG_NOT_ACCEPTED_CONFIG
Boot Error!
Operation Failed
Elapsed: 00:00:52
Reconnect Power/Cable!
Click to expand...
Click to collapse
it says that's an MT6755 processor , but when I try to flash it with Mt6755 with sp flashtool and NCK mtk soft it says that's version mismatch and it's and MT6750 device
Can you help to choose the right firmware please ?
octopus82 said:
Hello
I've bricked Oppo F1s when I've tried to flash it
this is infinity read info log
it says that's an MT6755 processor , but when I try to flash it with Mt6755 with sp flashtool and NCK mtk soft it says that's version mismatch and it's and MT6750 device
Can you help to choose the right firmware please ?
Click to expand...
Click to collapse
I have pretty much the same problem with my MOTO M (XT1662). It happened after I did the "Format whole flash" in SP flash tool.
Now the SP flash tool is giving me the following,
Chip Info
=======
Chip name: MT6755
Chip Version: 0x0000cb00
Ext Clock: EXT_26M
Extern RAM Type: DRAM
Extern RAM Size: 0xc0000000 (!!!)
SRAM Size: 0x00040000
EMMC Flash
=========
Boot 1 Size: 0x400000
Boot 2 Size: 0x400000
RPMB Size: 0x400000
GP1 Size: 0x0 (same for GP2, GP3 and GP4)
UA Size: 0x747c00000
No matter what ROM I'm trying to flash (stock or custom) , I always get the error "STATUS_INSUFFICIENT_BUFFER (0xC0010007)".
It looks like it has to do something with the External RAM Size (0xc0000000).
I found this firmware "XT1662_Kungfu_m_MT6755_USR_S0924_1612291517_mp7V2.3_CN (RepairMyMobile.in)", which seems to be what I need but I can't get pass this error.
Any help will be greatly appreciated.
i have the same problem
STATUS_INSUFFICIENT_BUFFER (0xC0010007)
i try to update with OTA and failed too
anyone can help ?
Hello i have A8 2018 sm-a530f which has the emmc files corrupted , i need to revive and when i connect to the Easy Jtag Plus i get the error Partition info not found ,guide repair procedures and below is the log data
Setting interface to EasyJtag2/ISP
Setting bus width to 1 Bit
Setting frequence to 36 MHz
CMD Pullup Level: 445 mV
CMD Active Level: 1192 mV
EMMC Device Information :
EMMC CID: 150100424A5444345200523F424BB5A7
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400D
EMMC Manufacture : SAMSUNG , EMMC NAME: BJTD4R , HEX: 424A544434xx , S/N: 523F42xx , rev. 0x00
EMMC Manufacture ID: 0x15 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 11/2018
EMMC ROM 1 (Main User Data) Capacity: 29820 MB (000747C00000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 16384 KB (000001000000) Counter: 0 , Response: Maybe not clean
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD Information :
Extended CSD rev: 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG]: 0x48 , Boot from: ROM2 (Boot partition 1)
Boot Bus Config: 0x01 , width 4bit
H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
Backup saved: BJTD4R_523F424B_20210404_201644.extcsd
EMMC Init completed.
Scanning soft partitions
Partition table not found
Get firmware version
Firmware info not found
NOTE: I HAVE THE BACK UP FILE BUT I DO NOT KNOW WHICH FILES TO LOAD , MAY SOMEONE CHECK THE ATTACHMENT AND TELL ME WHICH FILES TO LOAD LIKE (Select eMMC Image file *.bin) from THIS BACK UP.MAY SOMEONE TELL ME FROM THE BACK UP WHICH ONE IS ( eMMC ROM1 Image file, eMMC ROM2 Image file, eMMC ROM3 Image file, eMMC GP1 Image file, eMMC ExtCSD file. IN THEIR ORDER.
gruka said:
Hello i have A8 2018 sm-a530f which has the emmc files corrupted , i need to revive and when i connect to the Easy Jtag Plus i get the error Partition info not found ,guide repair procedures and below is the log data
Setting interface to EasyJtag2/ISP
Setting bus width to 1 Bit
Setting frequence to 36 MHz
CMD Pullup Level: 445 mV
CMD Active Level: 1192 mV
EMMC Device Information :
EMMC CID: 150100424A5444345200523F424BB5A7
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400D
EMMC Manufacture : SAMSUNG , EMMC NAME: BJTD4R , HEX: 424A544434xx , S/N: 523F42xx , rev. 0x00
EMMC Manufacture ID: 0x15 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 11/2018
EMMC ROM 1 (Main User Data) Capacity: 29820 MB (000747C00000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 16384 KB (000001000000) Counter: 0 , Response: Maybe not clean
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD Information :
Extended CSD rev: 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG]: 0x48 , Boot from: ROM2 (Boot partition 1)
Boot Bus Config: 0x01 , width 4bit
H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
Backup saved: BJTD4R_523F424B_20210404_201644.extcsd
EMMC Init completed.
Scanning soft partitions
Partition table not found
Get firmware version
Firmware info not found
NOTE: I HAVE THE BACK UP FILE BUT I DO NOT KNOW WHICH FILES TO LOAD , MAY SOMEONE CHECK THE ATTACHMENT AND TELL ME WHICH FILES TO LOAD LIKE (Select eMMC Image file *.bin) from THIS BACK UP.MAY SOMEONE TELL ME FROM THE BACK UP WHICH ONE IS ( eMMC ROM1 Image file, eMMC ROM2 Image file, eMMC ROM3 Image file, eMMC GP1 Image file, eMMC ExtCSD file. IN THEIR ORDER.
Click to expand...
Click to collapse
I think there are not many users who are able to help in your case.
I only found this thread about emmc repair for your device:
Samsung A520f ,A530f Dead boot repair direct emmc file download
gsm flash,gsm flash file,gsm crack,combine file,easy firmware,frp file,gsm firmware,gsm file,samsung firmware,samsung dump,all android flashing tool,
www.awaismobile.com
Yes i downloaded the file ,how do i know this file is rom 1 ,Rom2,Rom 3, and ex PLEASE I DENTIFY FOR ME