Hi, it seems I have a proper challenge for Stympy (or anyone else up for the task).
I already flashed new ROM on my P780 (not without any pain) and a friend asked me to do the same on his phone, I did it the first time without any problem using the working configuration for mine but can't do it again.
We are both on 2014+ 4gb chinese phones (as it seems to have its importance).
I'm trying to flash using the exact same combination of tools that works before :
- SP flash tool V3.1304.0.Sn119
- ROM : P780_S136_140306_Lang
- Preloader (provided here http://forum.xda-developers.com/lenovo-p780/help/lenovo-p780-chineese-speed-version-t2874161)
It starts flashing, I get the purple bar charging then it stops with an error_no_space (5069). I've noticed on the lower left corner that EXT_RAM_SIZE is 8192Mb DRAM while it should be 4096Mb for my 4gb version right ? And whatever the micro SD card I put in, EMMC_USER_SIZE is set to 28 Gb.
Do I need to add that the phone only response is the bleeping when connected to the computer or when the reset button is pressed.
Thanks for any help on this topic, any response will be highly appreciated.
Jeanrien said:
Hi, it seems I have a proper challenge for Stympy (or anyone else up for the task).
I already flashed new ROM on my P780 (not without any pain) and a friend asked me to do the same on his phone, I did it the first time without any problem using the working configuration for mine but can't do it again.
We are both on 2014+ 4gb chinese phones (as it seems to have its importance).
I'm trying to flash using the exact same combination of tools that works before :
- SP flash tool V3.1304.0.Sn119
- ROM : P780_S136_140306_Lang
- Preloader (provided here http://forum.xda-developers.com/lenovo-p780/help/lenovo-p780-chineese-speed-version-t2874161)
It starts flashing, I get the purple bar charging then it stops with an error_no_space (5069). I've noticed on the lower left corner that EXT_RAM_SIZE is 8192Mb DRAM while it should be 4096Mb for my 4gb version right ? And whatever the micro SD card I put in, EMMC_USER_SIZE is set to 28 Gb.
Do I need to add that the phone only response is the bleeping when connected to the computer or when the reset button is pressed.
Thanks for any help on this topic, any response will be highly appreciated.
Click to expand...
Click to collapse
Try again without changing the preloader.
P780_S136_140306_Lang ROM is made specialy for your phone Lenovo P780 SPEED Edition.
But this time use V5 of SP Flash Tool from HERE.
Tell me what is going on!
Good Luck.
Thanks for the suggestion, but unfortunately still not working, same error : ERR_NO_SPACE (5069)
I chose 'Download only' option,
- Download DA 100%
- Bootloader charge at 100% then stuck and I get the error message
On the left chip info is MT6589_S00 and still Extern RAM size 0x40000000 (while SRAM size is 0x00020000)
I did a memory test, I don't know if it can be useful to you (I have a 8 Go SD card in), here is the report :
============ Memory Detection Report ===========
Internal RAM:
Size = 0x00020000 (128KB)
External RAM:
Type = DRAM
Size = 0x40000000 (1024MB/8192Mb)
NAND Flash:
ERROR: NAND Flash was not detected!
EMMC:
EMMC_PART_BOOT1 Size = 0x0000000000200000(2MB)
EMMC_PART_BOOT2 Size = 0x0000000000200000(2MB)
EMMC_PART_RPMB Size = 0x0000000000200000(2MB)
EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
EMMC_PART_USER Size = 0x00000000e7000000(3696MB)
Jeanrien said:
Thanks for the suggestion, but unfortunately still not working, same error : ERR_NO_SPACE (5069)
I chose 'Download only' option,
- Download DA 100%
- Bootloader charge at 100% then stuck and I get the error message
On the left chip info is MT6589_S00 and still Extern RAM size 0x40000000 (while SRAM size is 0x00020000)
I did a memory test, I don't know if it can be useful to you (I have a 8 Go SD card in), here is the report :
============ Memory Detection Report ===========
Internal RAM:
Size = 0x00020000 (128KB)
External RAM:
Type = DRAM
Size = 0x40000000 (1024MB/8192Mb)
NAND Flash:
ERROR: NAND Flash was not detected!
EMMC:
EMMC_PART_BOOT1 Size = 0x0000000000200000(2MB)
EMMC_PART_BOOT2 Size = 0x0000000000200000(2MB)
EMMC_PART_RPMB Size = 0x0000000000200000(2MB)
EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
EMMC_PART_USER Size = 0x00000000e7000000(3696MB)
Click to expand...
Click to collapse
When you flash with SP Flash Tool and you want to do a clean instalation select firmware upgrade not download. On download option information is not overwriten.
Soooo... Try with firmware upgrade option. Good luck.
Haven't been able to work on this for a while, but here I'm back.
I tried to upgrade firmware with the following result :
On SP flash tool V3 :
SP flash tool error (8045)
No valid partition management table for storage device
On SP flash tool V5 :
Failed to get PMT info
Which is essentially the same error if I understand well. And still 'space error' when trying to download.
I asked other question to the owner of the phone and apparently he did format (potentially including bootloader) before bringing it to me, could that have an effect on EMMC which does not match and cause space errors ? Someone know how to fix that ?
Jeanrien said:
Haven't been able to work on this for a while, but here I'm back.
I tried to upgrade firmware with the following result :
On SP flash tool V3 :
SP flash tool error (8045)
No valid partition management table for storage device
On SP flash tool V5 :
Failed to get PMT info
Which is essentially the same error if I understand well. And still 'space error' when trying to download.
I asked other question to the owner of the phone and apparently he did format (potentially including bootloader) before bringing it to me, could that have an effect on EMMC which does not match and cause space errors ? Someone know how to fix that ?
Click to expand...
Click to collapse
No. This is not the cause ! Why your friend format the phone? What windows do you use ? Windows 7 is the best ! Divers are mutch better !
I have the same problem when I tried flash from ROW to ROW +. When I tried to flash usual ROW version , always flashing ended successfully. I have Lenovo 4Gb version before 2014. Please write if You find solution
I'm using Windows 7. Don't know why he formatted it. I guess because nothing was working and he saw the option...
I tried again with S136 without result. I'll try to download a fresh copy of ROM P780_S136_140306_Lang and try again. I see nothing else right now.
Jeanrien said:
I'm using Windows 7. Don't know why he formatted it. I guess because nothing was working and he saw the option...
I tried again with S136 without result. I'll try to download a fresh copy of ROM P780_S136_140306_Lang and try again. I see nothing else right now.
Click to expand...
Click to collapse
Would you be prepared for a team viewer session ?
Why not, we can arrange that. Do you need me to download specific files beforehand ?
Download stock firmware for your phone. Stock not modified in any way... Ok?
hy, is there any upate for this issue? i think i had the same one, stympy must be aware of it.
here is the screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is the error for firware upgrade:
and this this the error update using SPF v 3.xx
any help would be appreciate
tegrex said:
hy, is there any upate for this issue? i think i had the same one, stympy must be aware of it.
here is the screenshot:
this is the error for firware upgrade:
and this this the error update using SPF v 3.xx
any help would be appreciate
Click to expand...
Click to collapse
When I get back home ill study the problem and aill return with some idea.
Send from my Lenovo P1 Pro
same problem!
Please help I have the same problem!
Thank you.
blagotan said:
Please help I have the same problem!
Thank you.
Click to expand...
Click to collapse
tegrex said:
hy, is there any upate for this issue? i think i had the same one, stympy must be aware of it.
here is the screenshot:
this is the error for firware upgrade:
and this this the error update using SPF v 3.xx
any help would be appreciate
Click to expand...
Click to collapse
So... i am home.
Now... look what could work... but i am not to sure, so i need feedback from you.
- Download the latest mtkdroidtools
- Connect your phone and save the block map (stored 2 files and one of them will be named PMP)
- leave only PMP and rename it in the usual form of scatter
- Through it, you can flash the firmware without any mistakes
If this do not work you must go to a service store and format all the flash.... with programer device.
Waiting for feedback.
MTK droid tools not recognize bricked device
Thank you for answer.
How to connect my bricked device to MTK droid tools it is not recognized ? How to save file?
Thank you.
I'm having the exact same problem and it's driving me crazy. I can flash the preloader succesfully, but anything else gives me error 5069 (S_DL_PMT_ERR_NO_SPACE. Trying to flash the original firmware (P780_S144_140726)
Any advice would be appreciated
stympy said:
So... i am home.
Now... look what could work... but i am not to sure, so i need feedback from you.
- Download the latest mtkdroidtools
- Connect your phone and save the block map (stored 2 files and one of them will be named PMP)
- leave only PMP and rename it in the usual form of scatter
- Through it, you can flash the firmware without any mistakes
If this do not work you must go to a service store and format all the flash.... with programer device.
Waiting for feedback.
Click to expand...
Click to collapse
mtk droid tools cant read my device.. i try adb from the prompt also no devices detected, maybe because no usb debugging enabled before the phone crashed
tegrex said:
mtk droid tools cant read my device.. i try adb from the prompt also no devices detected, maybe because no usb debugging enabled before the phone crashed
Click to expand...
Click to collapse
fyi this is the capture from memory test
does it indicate the hardware problem, the dead emmc maybe?
tegrex said:
fyi this is the capture from memory test
does it indicate the hardware problem, the dead emmc maybe?
Click to expand...
Click to collapse
Dead or near death....
Related
Hi,
New NSS beta is available for download. It will implement installing and restoring
of the bootloader as single click solution. Although the Qcom loader could be
installed via normal flashing, it is much easier this way. Also recovery is intended
to save manual hex editing or cmd line commands.
1. Download the new version
2. Extract to a folder, start the program
3. Insert the 2 loaders in \loaders\special\wp7\ - the qualcom file: RM803_12w07_prod_generic_nokia_osbl.esco,
posted by xorizont here , second file: RM803_11w48_prod_raw_nokia_osbl.bin attached (unzip first)
4. Go to Flashing->WP7 Tools
You are ready to play. Quick description:
- Read PMM button - reads the PMM partition with Nokia specific values(product
code, MAC addresses, et), you can edit in the boxes
- Write PMM button - writes back to the partition a selected value (via Update
checkbox)
Install button - use this to quickly install Qcom loader on 710(no way to load on
800 as the cert is checked)
Parse FS button - you can use this to test NSS partition parser and compare
against 3rd party tool, to make sure something catastrophically wrong will not
happen during recovery
Restore button - This will attempt to recover the Nokia production loader (so called DLOAD)
via raw NAND write into partition 2 of the connected phone. Make
sure you start in Normal mode as NSS will need to check phone type and battery
value (to make sure wrong file is not written to 800, or if the battery is critically
low)
Please keep in mind, this is a Beta version, it has been tested only on one phone
and is possible to be a major phone killer, so thread lightly. It is offered as it is,
with the hope of being useful, and I can't be held responsible for fatal results.
My best recommendation is to check the partitions after write/recovery with
3rd party tool and make sure all is ok before restarting the phone power. All this
until some recovery method is found (if somebody has found flashing routines in
SECBOOT or other loader, pls PM me).
BR, Chris
Thanks for this nice tool!
I just wanted to stress that:
- Read PMM button - reads the PMM partition with Nokia specific values(product
code, MAC addresses, et), you can edit in the boxes
- Write PMM button - writes back to the partition a selected value (via Update
checkbox)
Click to expand...
Click to collapse
Are only possible when the phone has the qualcomm loader right? Because only then it's possible to overwrite the values using the NAND access mode (Qualcomm MSD).
Hi,
Yes, only in NAND mode, on phones that have it. If you have Nokia DLOAD loader
and not hacked phone, you can only read those value via JSON call to NCSD appl.
There isn't any method coded to change them in Normal mode(at least i did not
find one yet).
BR
Bph&co said:
Hi,
Yes, only in NAND mode, on phones that have it. If you have Nokia DLOAD loader
and not hacked phone, you can only read those value via JSON call to NCSD appl.
There isn't any method coded to change them in Normal mode(at least i did not
find one yet).
BR
Click to expand...
Click to collapse
It's good to see there is now a userfriendly way of doing stuff like this. Thanks again
now all we need is a tool to write an .nb file with one click. can one do it?
mariosraptor said:
now all we need is a tool to write an .nb file with one click. can one do it?
Click to expand...
Click to collapse
To be honest i have no idea how that exactly works - is there a need for a file
system parser and proper replacing of a file, or just writting to a const location
in the last partition.
The mount never worked on my Ubuntu install(and i am complete Linux newbie).
Bph&co said:
To be honest i have no idea how that exactly works - is there a need for a file
system parser and proper replacing of a file, or just writting to a const location
in the last partition.
The mount never worked on my Ubuntu install(and i am complete Linux newbie).
Click to expand...
Click to collapse
Thanks God. there is someone else like me in linux.( humor, no offense ofcourse ;-) )
mate i have no idea how it works. nobody wants to write a very accurate tutorial.
not being able to flash the custom rom was the reason that i reverted my bootloader.
To unlock bootloader I used to NCS and firmware posted by xorizont. So how make connection under Windows7 before flash xorizont's firmware if Nokia is in DLOAD mode?
this is very helpfull for many people to get to qulcomm on 710!
+1
So You are able to load Qualcomm B. via NSS even if on the moment I have got DLOAD?
Hi,
New Beta - 0.47.1 - with ability to write moded OS files(.nb).
OS File button - select .nb file
Write OS button - loads the file onto the last partition (change to OSBL mode first)
As with the previous beta - make sure you check the partion parser for errors.
Write will be verified, but not the exact write address, so maybe good to have a
look with WinHex before restarting the phone.
BR
Already a new version, you're working hard man! ;-)
So if i understand correctly, you have automated the process of 'block writing' (which without this tool requires using dd) the created custom roms to the correct partition on the Lumia?
Of course this requires Qualcomm bootloader; for the 710 your tool can load this even if the phone currently has the newer Nokia DLOAD.
Hi,
Yes, i work even in my sleep Right now killing myself with the baseband diss, but
decided to have a break and make this.
It seems the OsBuilder creates raw partition image, to fit exactly into the OS part
of the NAND chip. So all i do is open the usb device as physical disk, parse the
partition structure and do a low level read/write to absolute addresses.
Yes, it is mostly for 710, but write OS function should be working for 800 with
Qcom loader too, just can't test it as i don't have such phone.
Also the Install/Recovery should work forever on a 710, unless Nokia/MS release
some updated bootloader that somehow prevents loading of the signed Qcom
loader and the user does a full flash (or via sneak Zune update) and overwrite
the current DLOAD loader.
BR
Bph&co said:
Hi,
New Beta - 0.47.1 - with ability to write moded OS files(.nb).
OS File button - select .nb file
Write OS button - loads the file onto the last partition (change to OSBL mode first)
oh man you are a superstar. you did what i said it was missing. no more (hopefully) screwd phones.
@Mods please make this sticky.
Click to expand...
Click to collapse
Amazing tool!
I just used it to load Full Unlock Image for Lumia 710 by lucifer3006!
No more linux stuff needed, this is great and almost one-click windows solution!
Thank you!
When we talking about copy moded nb file into partition You mean sdx9 is default partition?
Hi,
The sdb thingi is something from Linux. On low level there are 4 primary partitions
in MBR, all the rest are logical, so the last entry in MBR points to the first logical one,
that for itself contains primary part and next one is logical as well. The last entry
in this linked list is the OS partition.
BR
1. OK I went through this. Tell me please how is possible to unlock bootloader if Lumia is in DLOAD mode? NSS can't reconized WP in this mode.
2. In case of relocking bootloader did I need copy Your specific RM803_11w48_prod_raw_nokia_osbl.bin or download an from navifirm?
I hope it's add backup and restore the "DPP.BIN" function!
like this!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you very much!
djtonka said:
1. OK I went through this. Tell me please how is possible to unlock bootloader if Lumia is in DLOAD mode? NSS can't reconized WP in this mode.
2. In case of relocking bootloader did I need copy Your specific RM803_11w48_prod_raw_nokia_osbl.bin or download an from navifirm?
Click to expand...
Click to collapse
Hi,
1 - Maybe you have Zune running and NSS can't open the port ? Use the kill Zune
services option in NSS please
2 - Yes this specific loader is needed (its extract from an original file) and is hash
checked before writting to the second partition to prevent dead phones
BR
Hi devs,
hoping on help of people who better know about this materia than me, I hope to create a workaround for OTA repair on faulty Iconia B1-A71 from Acer.
In this case we need devs who has knowledge about stock JB and also testers, who has a B1 with problems on installing OTA Updates with "Invalid partition settings" on FAT.
Status:
More and more user of B1 report the problem of updating their device by OTA. It appears to be a mass problem, which Acer has no solution for.
After checking on rooting issues we already know, that there is a difference in dumchar_info between "normal" and "faulty" B1´s:
Android Partition:
http://forum.xda-developers.com/showpost.php?p=40987372&postcount=197
Normal - android 0x0000000026500000 0x00000000020e8000 2 /dev/block/mmcblk0p3
Faulty - android 0x0000000015e00000 0x00000000020e8000 2 /dev/block/mmcblk0p3
Furthermore there is a difference (and this I assume is the problem for OTA routines) on FAT partition:
Normal - fat 0x0000000148638000 0x00000000882e8000 2 /dev/block/mmcblk0p6
Faulty - fat 0x00000001b0a38000 0x00000000232e8000 2 /dev/block/mmcblk0p6
Those who was in charge of rooting the B1 knows, that we have dumped the android partition by dd using the offset shown in dumchar_info.
In this logic it would be impossible to dump a faulty B1 system.img by using the normal offests - you would not "meet the partition/bits", if you use wrong data.
BUT - as we found out it was possible to dump the system.img from a faulty B1 using the offset of a normal B1! User agentdeep confirms a successful root from scratch on Linux base using the normal offsets: http://forum.xda-developers.com/showpost.php?p=40988791&postcount=202
Now my idea:
- According entonjackson pawitp already assume, that the dumchar_info may be wrong, since otherwise agentdeep would have a bricked device. IF we can proof that OTA checks this value - would it make sense to push a corrected dumchar_info through the ENGMODE backdoor? Anyone out there, who is able to save and extract the OTA, to see the routine?
- If it dont work, does it make sense to try a root from scratch on Linux - and fix the dumchar_info afterwards? Is it possible?
- How can I check a report of existing partitions on Android? Do I have to run busybox from terminal, to start fdisk? I would like to validate the partition information inside the dumchar_info...
This subject may be not as hot as a rooting thread - but more and more user report their problem with update errors, and we may help lots of them ... and show Acer, how this work has to be done...
Thank you in advance!
Sub.
I would like to try that procedure enton asked me by replacing 15e to 265 in dumchar_info. But knowing there is no way I can restore my nandroid backup if something bad happens, I will hold for now
Nice to meet you here, agentdeep I was hoping you will join this thread, since you are the one who made me thinking about this solution...
From my point of view the risk of bricking the tab after changing the dumchar_info is ... pretty low. As long as we have a working system you still can switch back to your origin value. But at that point I would also like to get some more background from the Linux masters in here. Currently I have a problem to understand about the dumchar_info - what is it? How it is created? Do I understand right, that it is an output from Linux kernel?
When this file is accessed? On boot? Which result we will have, if we change it? Is it a properties file, used to set up partitions - or just an info? IF it is only an information we can change it without any fear...
https://github.com/ameer1234567890/...To-Gather-Information-About-Partition-Layouts
This page gives us the information, that "fat" is not just the format - it is the internal memory on MTK based devices. Which finally gives me more inscentive to believe that we have an issue with 8gb and 16gb versions. On that I have seen a thread in a different forum, where a user reported to have opened the B1 and found out that there were 16gb internal memory instead of 8gb as shown in the device properties.
Probably we have "masked" 16gb-versions declared as 8gb???
alba81 said:
Nice to meet you here, agentdeep I was hoping you will join this thread, since you are the one who made me thinking about this solution...
From my point of view the risk of bricking the tab after changing the dumchar_info is ... pretty low. As long as we have a working system you still can switch back to your origin value. But at that point I would also like to get some more background from the Linux masters in here. Currently I have a problem to understand about the dumchar_info - what is it? How it is created? Do I understand right, that it is an output from Linux kernel?
When this file is accessed? On boot? Which result we will have, if we change it? Is it a properties file, used to set up partitions - or just an info? IF it is only an information we can change it without any fear...
Click to expand...
Click to collapse
1st, thanks for the thread! It's really been time to create one for this issue.
I will put a link on the 1st post of my thread to this one, for people experiencing this issue.
Regarding agentdeep, I also think changing the dumchar_info won't brick the device. But we should first make sure it won't brick.
Although I'm using Linux for like 10 years now, I cannot help a lot at this moment.
But if there will be a solution, I will put it immediatly into my toolkit
So, I made a small calculation for the offsets, and this seems to confirm a wrong information in the dumchar_info:
Normal B1 Offset Android size:
Hex: 26500 Dez: 156928 Multiplied with 4096=642777088 Divided by 1024 = 627.712kB
Faulty B1 Offset Android size:
Hex: 15e00 Dez: 89600 Multiplied with 4096=367001600 Divided by 1024 = 358.400kB
If you take into consideration, that the system.img.gz takes (in packed form!) about 350 MB, unpacked even 627,712kB (size of the parition, see above) - then it appears that the information MUST be wrong - if I am right with my calculation...
Following this we have these values for internal memory on both versions:
Normal B1 Offset FAT size:
Hex: 148638 Dez: 1345080 Multiplied with 4096=5509447680 Divided by 1024 = 5.380.320kB
Faulty B1 Offset FAT size:
Hex: 1b0a38 Dez: 1772088 Multiplied with 4096=7258472448 Divided by 1024 = 7.088.352kB
Anyone with 15e can check available space on internal memory? In fact it should be about 5GB as I remember (have the B1 not with me now).
Maybe I am writing complete bull**** here? Anyone can confirm my calculation..??
Thanks in advance!
alba81 said:
So, I made a small calculation for the offsets, and this seems to confirm a wrong information in the dumchar_info:
Normal B1 Offset Android size:
Hex: 26500 Dez: 156928 Multiplied with 4096=642777088 Divided by 1024 = 627.712kB
Faulty B1 Offset Android size:
Hex: 15e00 Dez: 89600 Multiplied with 4096=367001600 Divided by 1024 = 358.400kB
If you take into consideration, that the system.img.gz takes (in packed form!) about 350 MB, unpacked even 627,712kB (size of the parition, see above) - then it appears that the information MUST be wrong - if I am right with my calculation...
Following this we have these values for internal memory on both versions:
Normal B1 Offset FAT size:
Hex: 148638 Dez: 1345080 Multiplied with 4096=5509447680 Divided by 1024 = 5.380.320kB
Faulty B1 Offset FAT size:
Hex: 1b0a38 Dez: 1772088 Multiplied with 4096=7258472448 Divided by 1024 = 7.088.352kB
Anyone with 15e can check available space on internal memory? In fact it should be about 5GB as I remember (have the B1 not with me now).
Maybe I am writing complete bull**** here? Anyone can confirm my calculation..??
Thanks in advance!
Click to expand...
Click to collapse
Yeah internal space is 5.12 GB like posted here in bullbrands post:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: this is after swapping internald and external sd...
The calculation looks good, but i don't know why the f... you multiply with 4096 and divide by 1024... I'm working as a developer and now I really feel stupid, because I really just don't know.
entonjackson said:
The calculation looks good, but i don't know why the f... you multiply with 4096 and divide by 1024... I'm working as a developer and now I really feel stupid, because I really just don't know.
Click to expand...
Click to collapse
Dont worry I could explain as follows: 4096 is the qty of bits you write at once on dd, and 1024 - logically to convert bits to KB.
Well, so we see that nothing is right in the dumchar_info, at least on Android and FAT partition, on faulty B1´s. Now we know there is a mistake - and need to validate the right offsets. Anyone has experience with fdisk on Android? Do I have to run it from busybox from terminal emulator?
And can anyone experienced tell us the specifications of dumchar_info? I found out it is a MTK-own chart, which is not existing on other CPU based devices .... which means for me - it can not be that critical in regards to format table, right?
On a rooted device - can we use a log to see when the dumchar_info is triggered?
alba81 said:
Dont worry I could explain as follows: 4096 is the qty of bits you write at once on dd, and 1024 - logically to convert bits to KB.
Well, so we see that nothing is right in the dumchar_info, at least on Android and FAT partition, on faulty B1´s. Now we know there is a mistake - and need to validate the right offsets. Anyone has experience with fdisk on Android? Do I have to run it from busybox from terminal emulator?
And can anyone experienced tell us the specifications of dumchar_info? I found out it is a MTK-own chart, which is not existing on other CPU based devices .... which means for me - it can not be that critical in regards to format table, right?
On a rooted device - can we use a log to see when the dumchar_info is triggered?
Click to expand...
Click to collapse
Ah I see. very easy. so bs=4096 is blocksize and well ok 1024 I already guessed could be convertion from bits to bytes. alright.
Then I would say, yes. the calculation makes sense indeed.
Now we only need someone that tries to write the right parition info into dumchar_info.
volunteers hands up! :victory:
entonjackson said:
Now we only need someone that tries to write the right parition info into dumchar_info.
volunteers hands up! :victory:
Click to expand...
Click to collapse
The biggest problem on that point is - you need to have either root, or do it by obtaining "temporary backdoor root" through ENGMODE. And the qty of user having root on faulty B1 is still pretty low...
alba81 said:
The biggest problem on that point is - you need to have either root, or do it by obtaining "temporary backdoor root" through ENGMODE. And the qty of user having root on faulty B1 is still pretty low...
Click to expand...
Click to collapse
i know busybox has fdisk binary.
adb doesn't know fdisk?
Where can I call it thru ADB?
Starting busybox from internal memory thru Terminal Emulator also makes me problems ... permission denied.
alba81 said:
Where can I call it thru ADB?
Starting busybox from internal memory thru Terminal Emulator also makes me problems ... permission denied.
Click to expand...
Click to collapse
There is none. I thought fdisk comes with adb, but... no.
But maybe we need no fdisk. If i understood it right, wie only must edit the dumchar_info so the system "believes" it has the right partitions again.
Yes, obviosly the update process checks this value. As you already checked the /proc/emmc shows different values, and /proc/mtd is empty. /proc/partitions contain different information type.
Before changing an important value I think we need to validate that any change in dumchar_info remains after reboot, since the update failure notification appears in recovery mode during update - right?
Edit:
I do not get access to dumchar_info. Going through ES File Manager I set the properties, and even it shows after changing its saved - its not. How can I get the rights? And how I can take the rights for system away to not be able to access it any more? Each time I open the properties of it I see a different date ... is it in permanent access?? Or do I need a different file Explorer?
Edit2:
Wikipedia is my friend. Ok, now I know - dumchar_info is a procfs, generated by the kernel during boot and not saved. So I am affraid ... we are stuck on a faulty kernel issue?
Where does the kernel gain this Information from during boot? Anybody an idea?
I hope this helps
agentdeep said:
I hope this helps
Click to expand...
Click to collapse
Thank you - I will validate later on, once I am at home ... have now only my n8000 with me.
Ok, checked - my version is the same, except:
[email protected] (after Linux version 3.4.0)
which I think can not be that important, since all other release data is similar. So it is not the kernel we have to fight with - at least...
Ok, so following on this subject we need to see what comes up in the future:
http://forum.xda-developers.com/showpost.php?p=41168837&postcount=295
At least the reason seems to be confirmed from Acer site - a faulty format which is reported.
IMHO it can not be only the update with the problem, the device itself reports a different format in dumchar_info, not the update.
Well - we´ll stay tuned...
hi there,
i have a faulty B1 with root....also i tried the Factory Reset Workaround several times, it does not work for me....everytime about 10-15% i got the message "partition error...bla".
So if you want me to to test things...go on
I'm new here, however I successfully rooted my device using the "toolkit" even though I have
Code:
Faulty - android 0x0000000015e00000 0x00000000020e8000 2 /dev/block/mmcblk0p3
Thanks to Enton.
My internal storage is reported to be just 5.17GB (not 8GB as expected) confirming the figures in a previous post.
I complained to acer support about the size of the internal storage being nearly 3GB short of what it should be and that I thought it was down to a "memory allocation error".
There response was " As you have mentioned in the previous e-mail internal storage shows as a 5.17GB, I would like to inform you that the other space of the unit is occupied by Android Operating System, customer will not be able to use the complete 8GB from the unit, as Operating system needs a space. "
Is this complete and utter BS? I understand 4.1.2 Jelly Bean is just over 200MB.
Can someone please confirm.
BTW if any dumps are required from my "faulty" device (I do not have the partition error though) I'm happy to try.
BTW2 I've installed the new PMTUpdate patch "FixG1PMT" and that did nothing for my problem.
iam install zendrokat on my wave s8530
and it is nice but after 2 day my mobile is dead (dont boot to android )
but install zendrokat agin but dont install hapen E:format_volum make_ext4fs failed on dev/block/mmcblk1p3 error while formating /system !
and install bada but dont install when flash file factory error (ERR : FFS FORMAT )
i think NAND IS dead i need format nand to install bada or android again
Sloved prople
tell me or Mr.BenzoX to help you
pllllllllllllllllllllllllllllllllllllllllllllz i need help mee
Maybe more details...
Firmwareversion for bada?
For me in Germany XXLA1 is good idea...
If you have changed Bootfiles for Android, then maybe your Firmware needs Bootfiles from Firmwarepackage... Sometimes partition different...
Windows Version?
XP ?
7 ?
8.1 ??
Multiloader Version ?
ML 5.67 ?
5.64 ?
Best Regards
Try flashing bada again and then try!
And did u clean bada through recovery?
In Recovery go to
Zen settings>open recovery script>clear_bada_for_android_nand, press that, it will clear whole bada and u will space for android!
Or try formating system from mounts & storage and then try.
Romancy said:
iam install zendrokat on my wave s8530
and it is nice but after 2 day my mobile is dead (dont boot to android )
but install zendrokat agin but dont install hapen E:format_volum make_ext4fs failed on dev/block/mmcblk1p3 error while formating /system !
and install bada but dont install when flash file factory error (ERR : FFS FORMAT )
i think NAND IS dead i need format nand to install bada or android again
Click to expand...
Click to collapse
Open recovery mode -- Full wipe data -- yes
After , You can use the Android os on wave
when mount system ERROR MOUNTINIG SYSTEM !!
and flashing bada ERROR FFS FORMAT
and clear bada via script dont solved and dont delete file in nand and my memory is dead when clear bada via script
and flashing bada ERROR FFS FORMAT
Click to expand...
Click to collapse
Again, about bada...
If wrong Bootloader, then partiton table/info is different...
So which Firmware you try?
With Boot or without?
And here:
http://forum.xda-developers.com/showpost.php?p=49740223&postcount=3
Best Regards
Romancy said:
when mount system ERROR MOUNTINIG SYSTEM !!
and flashing bada ERROR FFS FORMAT
and clear bada via script dont solved and dont delete file in nand and my memory is dead when clear bada via script
Click to expand...
Click to collapse
I had every kind of problems during installing, changing rom verison from CM to ZendK, from ZendK to CM..
some time i thought that my phone was hard bricked ore something like that...
trust me, insist! be strong, don't leave. use "search" option, try different bada versions (s4 style turko saved me)
try multiloader from different pc
try find your problem in different forum pages
you will resolve soon!
http://forum.xda-developers.com/showpost.php?p=20534612&postcount=15
Here you can find LinkS for bada Firmware...
http://netfolder.in/folder.php?folder_id=SWFbK6M
For S8530...
So again, what you have tried?
bada 1 or 2 or 3 or 4 or...
Try this one and report:
S8530XXLA1_v2.0_DBT.zip
Use ML 5.67
Btw., as info...
You have 2 types of NAND...
512 MB OneNAND
2000 MB moviNAND
Best Regards
plllllllllllllllllllllllllllllllllllllllllllz
iam tell Tigrouzen but he tell me my NAND is dead
i want to install any OS on SD card i need eny OS my mobile now is dead plllllllz help me
and iam flashed bada 2 and bada 1.2 but dont solved pllllllllllllllllllllllllz help
plllllllllllllllllllllllllllllllllllllllllllz
Click to expand...
Click to collapse
Please open your eyes and try to answer... MORE precise...
Use Screenshots if you are not able to answer...
Here is bada Firmware Collection = MANY files to try...
http://netfolder.in/folder.php?folder_id=SWFbK6M
How to help you, if you ignore MANDATORY Basics...
1.
WINDOWS VERSION?
XP, 7 or 8 or what ever?
2.
Multiloader Version?
5.62 or 5.64 or 5.65 or 5.67 or what ever?
3.
Firmwareversion EXACT f. few Chars...
XXLA1 DBT ? Or ?
4.
Be sure you know what you do...
If FFS not work, then check if CSC and/or ShpApp.app
You not need for tests to select all files...
Look here, Screenshot of ML...
http://forum.xda-developers.com/showthread.php?t=1732287
Best Regards
i have win 7 and multiloader v5.65 and 5.67 and 5.62 and i have bada 2 custome room and stock room and i have bada 1.2
but all this dont solve any thing happen ERROR FFS FORMAT (NAND IS dead )
i need any OS even if on SD (live SD ) and i want recovery nand to install bada again i want help me and thanx all XDA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same test again, but this time use:
1.
Multiloader 5.67
2.
Use Stock/Original stuff like this one:
S8530XXLA1_v2.0_DBT.zip
3.
Round 1.
All files select...
If again FFS
Round 2.
Select all files again, except FFS
NO FFS this time.
Post result if success...
If CSC or SHP App also fail, then deselect them too...
Post result..
Summary:
- ML 5.67
- Use Original files instead Custom Firmware to prevent funny sideeffects...
- deselect FFS...
Only if all 3 FFS + CSC + SHP App fails, then you have an bigger problem...
Good luck.
Best Regards
can be use this now S8530XXJKA or 8530BOLD1_S8530CROLK1_CRO_Full_D-A-CH or NO
error CSC + SHAP + FFS dont write can you help me now or dont solved for ever
CSC + SHAP + FFS...
Click to expand...
Click to collapse
You mean if you flash only CSC = NO
If you flash ONLY SHP = NO success ?
Best Regards
iam flashed CSC only = NO
SHAP only =NO
FFS only = NO
All files = NO
Romancy said:
iam flashed CSC only = NO
SHAP only =NO
FFS only = NO
All files = NO
Click to expand...
Click to collapse
u should try bada 1.2 firmware ,
it may flash successfully.
if still err , than try with different pc , windows xp/7 etc.
the reason behind why i use sd rom is , it no affect bada , and also faster if u have good sd.
ok i will flash on Xp and tell you again but Stay with me to solved this proplem plllz
I haven't had enough to get a One now, but I'm pretty interested in the phone. Yesterday I saw a thread on Chinese forum, saying that LOGO.bin contains the image shown in fastboot mode, and thus everyone can choose his preferred image (like CM's) even if he uses ColorOS. So I tried to extract the bitmap from LOGO.bin and replace it with my own picture.
Now I've succeed PARTIALLY in identifying the BIN file format and extracting the images. There's no enough time to dig into replacing the pictures though, but I think it won't be hard.
Here is what I find, for those "aggressive" themers and ROM devs who want custom boot splash screen:
The BIN file starts with the following structure:
C:
struct SPLASHHEADERINDEX {
char magic_code[8]; // = { 'S', 'P', 'L', 'A', 'S', 'H', '!', '!' };
int img_width;
int img_height;
int reserved; // What's this? I haven't figured that out.
int img_offset[6];
char padding[468]; // The header is 512 bytes. Thanks [user=5757424]@chillstep1998[/user] !
};
Right after this structure, the raw data of boot splash image begins. Every pixel is described by 3 bytes in B-G-R order. The pixels begin at the upper left corner and then stored in the order of left to right & up to down. You can read (img_width * img_height * 3) bytes and write them into a BMP file. NOTE that BMP files require 4-pixel alignment for every horizontal row (Google that for details, otherwise you will get a "Broken image" info in image viewers) In order to avoid this problem, I wrote a simple program in VB.NET and used Bitmap.SetPixel and Bitmap.Save to solve it.
This is the VB code for this procedure. (I can't do GUI programs in C++...)
Code:
Dim bmp As New Bitmap(img_width, img_height)
Dim color As Color
For y = 0 To img_height - 1
For x = 0 To img_width - 1
b = fs.ReadByte 'fs is the FileStream of BIN file. Already sought to correct offset.
g = fs.ReadByte
r = fs.ReadByte
If b = -1 Then b = 0
If g = -1 Then g = 0
If r = -1 Then r = 0
color = color.FromArgb(r, g, b)
bmp.SetPixel(x, y, color)
Next
Next
There are some zeros after (img_width * img_height * 3) bytes. I don't know what's for...
Then let's look at the other images. Their offsets are in the img_offset array of SPLASHHEADERINDEX. They have headers like this:
C:
struct SPLASHHEADERNONINDEX {
char magic_code[8]; // "SPLASH!!" without \0
int img_width;
int img_height;
int reserved; //Still don't know
char padding[492];
};
Right after the structure is the raw data. Process that as mentioned above.
The image at img_offset[0] is the one shown in fastboot mode
[1] is AT current test (original Chinese: AT电流测试. What's AT?)
[2] is RF test
[3] is WLAN test
[4] is charging
[5] is low battery warning
Previews for new images are coming soon...
However: there is one bug: the images extracted are "mis-placed". You need to move 0x0 to 164xHEIGHT (163xHEIGHT maybe) area to the right side of the image to get the correct pic. The images extracted from ColorOS' LOGO.bin are listed as follows:
SPOILER:
[0]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[1]
[2]
[3]
[4]
[5]
Boot splash
Does anyone know the cause of this mis-place problem? Although that can be solved easily in the code, but it's not very reliable. Maybe it's related to the "reserved" member?
Since the format is rather simple, modding and repacking will be easy. When I get some free time I'll make a tool for this...
still dangerous. We don't know whether there's logo signiture check, even if we know how to make a logo.bin.
But good job!
dlhxr said:
still dangerous. We don't know whether there's logo signiture check, even if we know how to make a logo.bin.
But good job!
Click to expand...
Click to collapse
Can't come up with any reason why there should be signature check for logo, especially when we can use home-made modem fimwares and kernels without any problem... But it's worth considering since there's "reserved" member. ColorOS gets 0x00 0x00 0x00 0x00 and CM 0x00 0x00 0x00 0x01 in boot splash's "reserved" int. Haven't checked other 6 images though.
We already know how to make our own logo.bin...there's a thread in the "Themes and Apps" section.
treChoy said:
We already know how to make our own logo.bin...there's a thread in the "Themes and Apps" section.
Click to expand...
Click to collapse
Wow I didn't notice it before... This thread is revealing secrets of the magic and pushing it further
But he says the header is 512 bytes, which is different from what I've found. I will take a look. However, since there are pics as small as ~300*30, skipping 512bytes may cause visible loss of the content. Maybe that's for splash screen only.
updateing said:
Wow I didn't notice it before... This thread is revealing secrets of the magic.
But he says the header is 512 bytes, which is different from what I've found. I will take a look. However, since there are pics as small as ~300*30, skipping 512bytes may cause visible loss of the content. Maybe that's for splash screen only.
Click to expand...
Click to collapse
As far as they've discovered on the thread, they've only really uncovered the workings of the splash screen. We know that fastboot is also affected by the LOGO partition, but we don't know how that ties in with the bootloader. The ColorOS LOGO.bin displays, "已進人fastboot..." when in fastboot mode, and the International LOGO.bin displays "Fastboot Mode" with the Cyanogen mascot.
One thing is for certain though: this is DANGEROUS. There's a very good possibility of bricking because of the LOGO partition's relationship with the bootloader. I was talking to another developer here about his work with the LOGO partition, and he said he bricked his phone, but recovered it by holding the power button, and then manually writing the correct LOGO partition using the 'dd' command.
I've contacted OnePlus support about this, so we should hear word back around Easter.
treChoy said:
As far as they've discovered on the thread, they've only really uncovered the workings of the splash screen. We know that fastboot is also affected by the LOGO partition, but we don't know how that ties in with the bootloader. The ColorOS LOGO.bin displays, "已進人fastboot..." when in fastboot mode, and the International LOGO.bin displays "Fastboot Mode" with the Cyanogen mascot.
One thing is for certain though: this is DANGEROUS. There's a very good possibility of bricking because of the LOGO partition's relationship with the bootloader. I was talking to another developer here about his work with the LOGO partition, and he said he bricked his phone, but recovered it by holding the power button, and then manually writing the correct LOGO partition using the 'dd' command.
I've contacted OnePlus support about this, so we should hear word back around Easter.
Click to expand...
Click to collapse
Hope OnePlus support team is open to this kind of mod...
As for the developer you mentioned, could you please ask him if he entered Qualcomm DLOAD mode and used some .hex file to boot the phone into mass-storage mode? I know when this (QHSUSB DLOAD device) shows up, the bootloader has already failed and this is the last recovering method of the phone. Seen it on my Xperia TX...
And the method mentioned in this thread will also work on CM's LOGO.bin, except for the 164xH issue.
updateing said:
Hope OnePlus support team is open to this kind of mod...
As for the developer you mentioned, could you please ask him if he entered Qualcomm DLOAD mode and used some .hex file to boot the phone into mass-storage mode? I know when this (QHSUSB DLOAD device) shows up, the bootloader has already failed and this is the last recovering method of the phone. Seen it on my Xperia TX...
And the method mentioned in this thread will also work on CM's LOGO.bin, except for the 164xH issue.
Click to expand...
Click to collapse
The developer is @demkantor . And I was wrong about how he unbricked his device. He said that after messing around with the LOGO partition, he got the dreaded "QHUSB_BULK" error, but after a few seconds, his OPO rebooted on his own. He had to 'dd' the regular LOGO partition to get his bootloader up and running. Original thread here: http://forum.xda-developers.com/oneplus-one/help/qhsusbbulk-help-t2848238
treChoy said:
The developer is @demkantor . And I was wrong about how he unbricked his device. He said that after messing around with the LOGO partition, he got the dreaded "QHUSB_BULK" error, but after a few seconds, his OPO rebooted on his own. He had to 'dd' the regular LOGO partition to get his bootloader up and running. Original thread here: http://forum.xda-developers.com/oneplus-one/help/qhsusbbulk-help-t2848238
Click to expand...
Click to collapse
I have once seen somewhere that you can find specific .hex file (e.g. MPRG8960.hex for MSM8960) to download into the phone by QPST Service Programming. Then the phone will boot into mass storage mode, where computer will recognize the phone as a removable disk drive. Now the whole internal storage is "mounted" on the computer and you can use dd to restore then.
(Google'd and it says only QHSUSB_DLOAD need the hex file. QHSUSB_BULK should be mounting the internal storage to computer automatically and dd will be available. Not sure about that. Example: http://forum.xda-developers.com/showthread.php?t=2582142&page=1)
yeah the header is 512 bytes. Now the images are all correct :victory:
Flashing a bad LOGO.bin did send me to the QHSUB_DLOAD mode and I tired rebooting holding down all three buttons. It did seem to work but after a bit it seemed to just boot on its own. Then I just used an adb shell to run dd commands to flash the proper .bin and all has been well since then
Still have been to busy with our newborn to look into anything deeper but between this thread and the one by @chillstep1998 and treChoy and other it looks to be all good!
Glad all is coming together on this end, keep up the great work all
dear thread creater.. i tell u what is that zeros after anything.
actualy android reads anything in block size.. like this
4,4,4,4,4.....
or 8,8,8,8,8.....
or 16,16,16,16...
or....
or...
or...
or 512,512,512,512...
or......
so.. if block size is 512 then it would read 512 bytes first..
now think what if there is only 50 or 51 bytes.. if will be a error.. if it has code to handle errors.. it is slow.
this is called alignment.. we say header is aligned to 512 bytes.
to make alignment it would add padding of NULLs(chr(0) in vb)
same nulls for the end of file to make it aligned to some size.
thank you.
m9j_cfALt said:
dear thread creater.. i tell u what is that zeros after anything.
actualy android reads anything in block size.. like this
4,4,4,4,4.....
or 8,8,8,8,8.....
or 16,16,16,16...
or....
or...
or...
or 512,512,512,512...
or......
so.. if block size is 512 then it would read 512 bytes first..
now think what if there is only 50 or 51 bytes.. if will be a error.. if it has code to handle errors.. it is slow.
this is called alignment.. we say header is aligned to 512 bytes.
to make alignment it would add padding of NULLs(chr(0) in vb)
same nulls for the end of file to make it aligned to some size.
thank you.
Click to expand...
Click to collapse
Thanks! I know there are some alignment rules, but didn't expect them to be here. I've seen aligning the whole file to 4 bytes or so, but little do I know that a section header needs alignment as well. I guess that's because this LOGO.bin is used in such a low-level "environment" that we don't have enough time & space to handle the non-aligned data. Am I right?
updateing said:
Thanks! I know there are some alignment rules, but didn't expect them to be here. I've seen aligning the whole file to 4 bytes or so, but little do I know that a section header needs alignment as well. I guess that's because this LOGO.bin is used in such a low-level "environment" that we don't have enough time & space to handle the non-aligned data. Am I right?
Click to expand...
Click to collapse
Hi man!
Do you know how change the battery animation when the phone is charging(when is off)?
I've tried to change the imgs in /res/images/charger, but you know, it doesn't work eheheh...
Can you help me?
Reive said:
Hi man!
Do you know how change the battery animation when the phone is charging(when is off)?
I've tried to change the imgs in /res/images/charger, but you know, it doesn't work eheheh...
Can you help me?
Click to expand...
Click to collapse
I don't have a OPO to test, all these analysis are theoretical. So I may not be able to help. Sorry...
Hi all, I have a D101 10.1in phablet that I bricked.
I do have a backup for SP flash Tool but when I try to boot, I get to the splash screen with Decrypt failed, Boot Error!!!
I bricked by using files from another tablet files same model because get error after busy box installation and try a clean installation
I have tried formatting it... and put my old backup just to fix the problem but after the 1 situation get "Decrypt failed, Boot Error!!!"
When I format it. It seems to work because there is nothing at all when I try to boot it.
When I flash the backup I get the splash screen again... (So it's alive... well barely)
here are the details of the phablet:
- MODEL : d101
- MANUFACTURER : alps
- VERSION : 4.2.2 > JELLYBEAN
- PRODUCT NAME : d101
- DISPLAY ID : ALPS.JB3.MP.V1
- BOARD : d101
- MTK PLATFORM : MT6572
- BUILD ID : JDQ39
- BUILD VERSION : vCC01C
- PDA : vCC01C
- UDISK LABEL : vCC01C
- SERIAL NO. : 0123456789ABCDEF
In the Attach Files i give you guys the boot.img lk.bin logo.bin preloader.bin recovery.img secro.bin uboot.img and MT6572_Android_scatter.txt
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
oficial info
pecifications:
General
Operating System - Android 4.2
CPU - MT Cortex A7 Dual-Core
Processor Speed - 1.2GHz
RAM - 1G
Hard Drive Capacity - 8GB
Extended Memory - Support external TF card extend up to 32GB
Gravity Sensor - Yes, 4-dimensional G-sensor
Flash Player - Yes, Support Flash Player 11.0
Click to expand...
Click to collapse
Display
Display Size - 10.1 Inch
Display Technology - Capacitive Touch Screen
Multi-Touch - Yes, 5 points
Display Resolution - 1024 x 600 pixels
Click to expand...
Click to collapse
Camera
Front Camera - 0.3MP
Rear Camera - 2.0MP
Click to expand...
Click to collapse
Connections
Wi-Fi - Yes, Wi-Fi 802.11 b/g/n
3G - Yes, Support external USB 3G modem
GPS - Yes
Bluetooth - Yes, Bluetooth 4.0
Click to expand...
Click to collapse
Telephone - Yes,
2G:GSM850/900/1800/1900MHz
3G:WCDMA850/2100MHz
Click to expand...
Click to collapse
Input/Output Connectors
Ports
1 x Micro USB Interface
1 x Earphone Jack
1 x TF Card Slot
2 x SIM Card Slot
Audio/Video - 3.5mm headphone jack
Built-in stereo loud speaker
Built-in microphone
Battery
Battery Capacity - 4200mAh
Power Adapter
Input 100-240V~50/60HZ / Output 5V 2A
Color - White
Dimensions(L x W x H) - 243 x 165.8 x 10mm
Net Weight - 513g
Accessories
1 x Power Adapter, 1 x OTG Cable
Click to expand...
Click to collapse
You solved this problem? I have the same
Sadly no fix yet
Rebelation said:
Sadly no fix yet
Click to expand...
Click to collapse
I stubbornly looking for a solution to this problem
same problem here
i face the same problem in my XTOUCH PF81 tablet .
lets check some conditions :
what the type of flashing tool you used ?
is the boot file used extension .mpn or .img ??
did you used the correct project number ? (incase of wiselink tool)
1. SP_Flash_Tool_v3.1344.0.212 or SP_Flash_Tool_v3.1316.0.150
2. img
3 How to understand the project number?
Try the wiselink flash tool 4.1 , i think your tablet project number is td710
Where we can Check that project number
check this
Rebelation said:
Where we can Check that project number
Click to expand...
Click to collapse
https://docs.google.com/document/d/1XEl6O7RNls4TzVYieq0ut6IbP19BTEHewvMGaFofw8U/edit?usp=sharing
at the opening of writes (incorrect scatter file format)
Probably need another scatter
muhammad sadiq said:
https://docs.google.com/document/d/1XEl6O7RNls4TzVYieq0ut6IbP19BTEHewvMGaFofw8U/edit?usp=sharing
Click to expand...
Click to collapse
neoxlam said:
at the opening of writes (incorrect scatter file format)
Probably need another scatter
Click to expand...
Click to collapse
just change it from scatter.txt to scatter.sca , and remeber to remove the tick from force high speed , duel core need the full speed option .
wiselink update necessary?
neoxlam said:
wiselink update necessary?
Click to expand...
Click to collapse
no , for me the new version not work , i used 4.1 and didnt accept update , after install its will ask to install drivers update , i think you are already have the preloader drivers so disregard it .
Well that make flash but still the problem did you fix your tab with that flash tool?
Tried in different ways, the error persists
is a great tool but is just to flash nothing more
dont fix the Decrypt failed, Boot Error!!!
I suggested that the need to find a test point on the board. With its aid, you can unlock preloader, but I do not know how to find a test point
Rebelation said:
is a great tool but is just to flash nothing more
dont fix the Decrypt failed, Boot Error!!!
Click to expand...
Click to collapse
im try to flash the boot.img by fastboot command , and its flashed , but when im try the : fastboot erase userdata , its fail due to security reason , i do think this is our problem , system need to be wiped to get boot !!!
muhammad sadiq said:
im try to flash the boot.img by fastboot command , and its flashed , but when im try the : fastboot erase userdata , its fail due to security reason , i do think this is our problem , system need to be wiped to get boot !!!
Click to expand...
Click to collapse
the problem of wipe or not comes when the system start and this is not the problem of "Decrypt failed, Boot Error!!!"
when you have that problem of wipe you get stuck on logo loop and this is not the problem
this is before system starts because he don't recognize charging nothing because dont recognize the nothing
this problem is about decryption system tree is like lost key to decrypt the files and participation´s
imagine like Linux if you encrypt the files of the system with key and if your system loses that key don't recognize so the system you need put key again or format and install again new fresh
all d101 tablets are the same no mather what seller or logo comes on the tab all are the sam matherboard all are fake mtk6582 some come with android 4.4 but also a fake is just clone rom of 4.2 this tablet are great tablets for normal users for us we like root and install all **** and make or own system this tab is s **** because the system comes encrypet when we try do something broken the encrypt system
we have just 4 options
1 Find the point of the encryption point on the bootloaders and make skip that verification
2 find away to get the encryption key and place it again
3 make a new and fresh undecrypt android system installation
4 put this tablet on the trash and buy new one
i agree with the last option
4 put this tablet on the trash and buy new one
hahahahaha:good: