Related
Hello,
I'm developing my own ROM using the "XDA ROM Kitchen". However once Clicking "Build Rom" I obtain the error "All workspaces are busy now. Try again in 20 seconds or so..." I will list my setup.
------------------------------------------------
OS: SuSE Linux 10.0.0.42
kernel-default-2.6.16_rc1_git3-4
kernel-source-2.6.16_rc1_git3-4
kernel-syms-2.6.16_rc1_git3-4
------------------------------------------------
Webserver
XAMPP for Linux 1.5.1
Includes:
Apache 2.2.0
MySQL 5.0.18
PHP 4.4.1
PHP 5.1.1
Perl 5.8.7
Install directory = #/opt/lampp/
------------------------------------------------
RomKitchen date = 04/01/2005
Install directory = #/opt/lampp/htdocs/kitchen_template/
Rom used = 3.17.03ENG
MKROM date = 04/01/2005
Run locally via
"localhost/kitchen_template/"
I select any adequate options, and select build rom (tested on all three options) and error "All workspaces are busy now. Try again in 20 seconds or so..." Is displayed.
The Rom directory structure is as follows:
'/opt/lampp/htdocs/kitchen_template/'
'/opt/lampp/htdocs/kitchen_template/data'
'/opt/lampp/htdocs/kitchen_template/download'
'/opt/lampp/htdocs/kitchen_template/kitchen.local'
'/opt/lampp/htdocs/kitchen_template/workspace'
'/opt/lampp/htdocs/kitchen_template/workspaces'
The ROM location is as follows:
'/opt/lampp/htdocs/kitchen_template/data/00_Select your Base ROM/3.17.03 ENG O2-Euro/_/cfg/rom.nb1'
------------------------------------------------
Could anyone please help me evaluate the problem and perhaps correct this? such as after install configurations. I would greatly appreciate it also share my kitchen once complete.
Thanking in advance
John
*bump*
Hello,
Still no avail with this problem, I descovered php5 is not compatible and php4 fixes many issues, yet still no fix for the 20 second error.. please anyone?
John
Shadow_relm said:
However once Clicking "Build Rom" I obtain the error "All workspaces are busy now. Try again in 20 seconds or so..."
Click to expand...
Click to collapse
check the workspace directory. There have to be write access by you apache user, and it has to be empty. This error normally cames when it isn´t possible to create a workspace, or all workspaces are in use....
Stefan
LumpiStefan said:
Shadow_relm said:
However once Clicking "Build Rom" I obtain the error "All workspaces are busy now. Try again in 20 seconds or so..."
Click to expand...
Click to collapse
check the workspace directory. There have to be write access by you apache user, and it has to be empty. This error normally cames when it isn´t possible to create a workspace, or all workspaces are in use....
Stefan
Click to expand...
Click to collapse
Thankyou Works fine now , all i got to do is alter a few things, is it posible to obtain the WMP10 files and include into this rom? If not that is cool.
John
Hello,
Sorry, The error still appears now its constatly again. and i am incapable of compiling roms. any suggestions?
thankyou
Re: Hello,
Shadow_relm said:
Sorry, The error still appears now its constatly again. and i am incapable of compiling roms. any suggestions?
thankyou
Click to expand...
Click to collapse
Update, I can now creat NK.nb1 and NK.nbf files with the kitchen, the files flash perfectly and flawlessly. Yet when running installer EXE it displays the usual..
Creating ROM... Please be patient.
Copying ROM files
Why not using the time for donating? ;-)
Running mkrom
Your ROM is done. (click here to view the log)
But uppon downloading the rom its only 200-500kb the logg says as follows
no files for configid 26220739 2620749 27202 20404 20408 20412 23410write xip block starting at 81800000, with 27 fileswrite xip block starting at 81980000, with 0 filesthis rom seems to be 3.17.03 ENG 2003-05-15 o2eurothis bootloader seems to be V5.22 2003-05-15 17:46:5580000000 - 80040000 -- bootloader 0 files 1 modules80040000 - 8026a804 -- kernel 13 files 11 modules802c2000 - 8057d330 9 OS 15 files 32 modules80580000 - 8075a69c 8 SHELL 79 files 27 modules80780000 - 80a13b04 7 BROWSING 9 files 14 modules80a40000 - 80d8a33c 6 COREAPPS 46 files 30 modules80dc0000 - 80ebd150 5 SYNC 12 files 22 modules80ec0000 - 810388e0 4 24MAPPS 13 files 13 modules81080000 - 81348248 3 24MCONSUMER 69 files 1 modules81400000 - 814019a4 -- xip chain 10 xip entries81440000 - 817f6f14 1 MISC 209 files 40 modules81800000 - 8189ec94 10 XDA_DEVELOPERS1 27 files 0 modules81900000 - 81925800 -- bitmap : 101a301a .. beb6fc8d81940000 - 81944000 -- operator rom 0 files81980000 - 81981054 11 XDA_DEVELOPERS2 0 files 0 modules../rom.exe: found a preamble of 31232 bytes adding: English/NK.nbfzip I/O error: No space left on devicezip error: Output file write failure (write error on zip file)
Hi !
Little mistake in title, Tab is 8.9"
Need a little help (if possible) !
I tried to unlock a French Galaxy Tab 8.9" (P7300) locked on Orange
I think method is similar to other devices from Samsung Galaxy Family
http://forum.xda-developers.com/showthread.php?t=843323
In order, i did :
Backup of Efs folder
In nv_data.bin file, i've edited 0x181469 from 01 to 00 (on Windows computer)
Deteled nv_data.bin and nv_data.bin.md5 in Efs folder
Put back new/modded nv_data.bin in Efs folder
Reboot
With non-Orange network sim, Tab still asks for a network unlock code
I took back "new" nv_data.bin to computer to read it, and byte 0x181469 have been changed back to 01
nv_data.bin.md5 created in folder (or taken from .nv_data.bak.md5)
If you read joined nv.log, you can see that my modded nv_data.bin has been replaced by backed one (due to nv_data.bin.md5 file deleted) :
Thu Oct 13 00:08:42 2011: MD5 open fail. (No MD5 file) : /efs/nv_data.bin.md5
Thu Oct 13 00:08:42 2011: backup NV restored.
Thu Oct 13 00:22:10 2011: MD5 open fail. (No MD5 file) : /efs/nv_data.bin.md5
Thu Oct 13 00:22:10 2011: backup NV restored.
Thu Oct 13 00:27:20 2011: MD5 open fail. (No MD5 file) : /efs/nv_data.bin.md5
Thu Oct 13 00:27:20 2011: backup NV restored.
I tried at least 3 times
So, everytime i reboot without md5 file, my Tab restored bak file (instead of regenerating new one), unlock is then impossible
My files : http://www.megaupload.com/?d=S7KHDOQ9
pero123 reported that he could unlock his GT 10.1 (which has a lot of similarities with the 8.9) with an app:
http://forum.xda-developers.com/showpost.php?p=18567730&postcount=7
Did you give this a try?
Yes, dagentooboy got a great guide to unlock the 10.1 which is also working for the 8.9!!!
Check this out:
http://forum.xda-developers.com/showthread.php?t=1336659
I confirm, worked like a charm on my 8.9'' locked to Orange
So does the free app from Helroz work with the P7300 or do I need to buy the paid version from DaGentooBoy?
confirmation needed
MaluNoPeleke said:
So does the free app from Helroz work with the P7300 or do I need to buy the paid version from DaGentooBoy?
Click to expand...
Click to collapse
hi guys can someone confirm if this will work on P7300 using the free apps and not the paid version..thanks
help
I need this efs folder backup for save my p7300, anyone can help me? please? (sorry for my bad english.
Thread closed...
Thread closed...
Thread closed...
Looks good.
mAYBE AN init.FILE
heX79 said:
Current road-block, custom CWM built with recovery builder using stock 4.1.1 recovery (insecure & fstab)
-Can't mount /system even though adb shell returns #.
Something is changing the blocks:
Code:
/dev/block # ls -l
ls -l
[COLOR="Red"]brw------- 1 root root 7, 0 Jan 1 00:00 loop0
brw------- 1 root root 7, 1 Jan 1 00:00 loop1
brw------- 1 root root 7, 2 Jan 1 00:00 loop2
brw------- 1 root root 7, 3 Jan 1 00:00 loop3
brw------- 1 root root 7, 4 Jan 1 00:00 loop4
brw------- 1 root root 7, 5 Jan 1 00:00 loop5
brw------- 1 root root 7, 6 Jan 1 00:00 loop6
brw------- 1 root root 7, 7 Jan 1 00:00 loop7[/COLOR]
brw------- 1 root root 179, 0 Jan 1 00:00 mmcblk0
brw------- 1 root root 179, 1 Jan 1 00:00 mmcblk0p1
-rw-rw-rw- 1 root root 1088 Jan 1 00:00 mmcblk0p8
drwxr-xr-x 3 root root 60 Jan 1 00:00 platform
/dev/block #
Click to expand...
Click to collapse
wouldnt that be an init file be renaming them?
---------- Post added at 03:34 PM ---------- Previous post was at 03:31 PM ----------
FriedBacon said:
wouldnt that be an init file be renaming them?
Click to expand...
Click to collapse
Code:
fastboot boot boot.img
copies file onto device but then fastboot hangs.
How long did you let I load for? I found it took about 45-60 seconds for it to start booting after running fastboot boot boot.IMG.
Sent from my A110 using xda app-developers app
HAHAHA
fringle said:
How long did you let I load for? I found it took about 45-60 seconds for it to start booting after running fastboot boot boot.IMG.
Sent from my A110 using xda app-developers app
Click to expand...
Click to collapse
I flashed it onto my device so i wait a few minute and see if it loads. otherwise im stuck in "softbrick" or w/e lol
I can also confirm this, any attempts to boot the 4.1.1 kernel on 4.1.2, have not been successful. I tried the stock one and the insecure one. Maybe the bootloader is checking the kernel? Just a wild guess at this point. I'm sure we'll figure more out, once Skellums is ready with another recovery to test.
Still hoping some devs pop in to help guide us a bit. I know there are devs here that can probably crack this wide open, trouble is they most likely don't own the device.
Just messaged Paul O'Brien of Modaco fame. Hopefully he can give us some tips if he's not too busy.
heX79 said:
I can also confirm this, any attempts to boot the 4.1.1 kernel on 4.1.2, have not been successful. I tried the stock one and the insecure one. Maybe the bootloader is checking the kernel? Just a wild guess at this point. I'm sure we'll figure more out, once Skellums is ready with another recovery to test.
Still hoping some devs pop in to help guide us a bit. I know there are devs here that can probably crack this wide open, trouble is they most likely don't own the device.
Click to expand...
Click to collapse
I've been busy over the last few days so I haven't had a lot of time to look at this further.. I'm wondering if the system backup from the CWM backup that fringle posted could be flashed with fastboot? The system portion isn't an img file, but I'm looking to see how it can be converted. Of course I wouldn't suggest doing this as it would overwrite everything in your /system (that's if it even worked!)
Skellums said:
I've been busy over the last few days so I haven't had a lot of time to look at this further.. I'm wondering if the system backup from the CWM backup that fringle posted could be flashed with fastboot? The system portion isn't an img file, but I'm looking to see how it can be converted. Of course I wouldn't suggest doing this as it would overwrite everything in your /system (that's if it even worked!)
Click to expand...
Click to collapse
Isn't this the update.zip I asked for earlier? I just can't figure out how to make one from a cwm backup.
Just posted a possible 4.1.2 boot.img file http://forum.xda-developers.com/showpost.php?p=36510887&postcount=414 if someone wants to give it a try. It did boot on 4.1.1 so I'm not sure if it will work but always worth a shot.
Edit:
We have at least one report of this working, just waiting to see if they still get mount errors in cwm.
Looks like it's booting but not allowing changes, insecure one posted here:
http://forum.xda-developers.com/showpost.php?p=36515118&postcount=425
Hopefully it will be working
So none of them returned root prompt but at least we now have a working boot.img file for 4.1.2.
fringle said:
Just posted a possible 4.1.2 boot.img file http://forum.xda-developers.com/showpost.php?p=36510887&postcount=414 if someone wants to give it a try. It did boot on 4.1.1 so I'm not sure if it will work but always worth a shot.
Edit:
We have at least one report of this working, just waiting to see if they still get mount errors in cwm.
Looks like it's booting but not allowing changes, insecure one posted here:
http://forum.xda-developers.com/showpost.php?p=36515118&postcount=425
Hopefully it will be working
So none of them returned root prompt but at least we now have a working boot.img file for 4.1.2.
Click to expand...
Click to collapse
So I built CWM from source using the 4.1.2 boot.img posted by fringle... No idea if it works or not or makes any difference.
Usual disclaimers, I'm not responsible for any damage caused by using this. I hold no responsibility for loss of data or the inability to boot your device.
Edit: Helps if I attach the file...
We've got Root
Looks like we finially beat it.
http://forum.xda-developers.com/showpost.php?p=36562865&postcount=469
Yup. And there's a 4.1.2 root guide made by me.
Of course, you're all in the thanks section.
Great job guys. Great work.
Sent from my Acer Iconia Tab A110 using XDA Premium HD app
Hey guys, I'm trying to compile and test the Xiaomi Redmi 3S kernel sources. I would like to know if someone could explain how we can compile it. Here I'm going to talk what steps I did and what result I got (bad bad xD).
I have to say that I'm a noob about ROM and kernel building, but I have some development skills.
Well, I followed this guide from Anik1199 (thanks!! ):
http://en.miui.com/thread-293285-1-1.html
After clone the git repository (of course, branch for "land" device) and compile the sources I had to do the following changes to fixes some errors:
Fixed some relative paths due a "no such file or directory" errors (about 5-6 files). At the moment I put my custom absoule path to see that I can compile
After that, I get this error
Code:
drivers/soc/qcom/subsystem_restart.c:1480:19: error: 'WT_SUBSYSTEM_REASTART_LEVEL' undeclared (first use in this function)
if (0 == strncmp(WT_SUBSYSTEM_REASTART_LEVEL, "SYSTEM", 6))
Following the instructions given by Anik1199 on this post:
http://en.miui.com/thread-293285-4-1.html
I fixed this error successfully . As he say, we have to define the WT_SUBSYSTEM_REASTART_LEVEL constant (by the way, it's a little strange the name right? "reastart" insted of "restart"? xD):
Code:
#define WT_SUBSYSTEM_REASTART_LEVEL "related"
After all this fixes the compilation process finished... but, instead to get "zImage" I get some files (in root_sources/arch/arm64/boot) with the following names:
Code:
drwxrwxrwx 1 ercea users 4096 ene 3 21:52 dts
-rwxrwxrwx 1 ercea users 28 ene 2 12:37 .gitignore
-rwxrwxrwx 1 ercea users 23465344 ene 3 22:00 Image
-rwxrwxrwx 1 ercea users 227 ene 3 22:00 .Image.cmd
-rwxrwxrwx 1 ercea users 9387806 ene 3 22:00 Image.gz
-rwxrwxrwx 1 ercea users 147 ene 3 22:00 .Image.gz.cmd
-rwxrwxrwx 1 ercea users 9387806 ene 3 22:00 Image.gz-dtb
-rwxrwxrwx 1 ercea users 145 ene 3 22:00 .Image.gz-dtb.cmd
-rwxrwxrwx 1 ercea users 1188 ene 2 12:37 install.sh
-rwxrwxrwx 1 ercea users 1243 ene 2 12:37 Makefile
"dts" is a folder, the rest are files. I don't know what is the kernel, "Image"? or "Image.gz"?
I assumed that the kernel file was "Image" (without extensions). So, following the guide, I can see that the next steps are:
Take my original/current boot.img. The ROM that I've installed is this modified MIUI version (based in beta 6.12.29):
https://forum.xda-developers.com/redmi-3/development/rom-redmi3-pro-ido-thunder-unofficial-t3435852
Unpack the boot.img file using mkbootimg
Rename my "Image" compiled file to "kernel"
Copy the renamed file "kernel" and paste inside the boot.img unpacked folder
Repack the folder to "boot.img"
After this process, I copy my original and compiled kernels in my phone and I restarted to recovery (TWRP). Then, I flashed my compiled kernel ("Install", then "Install Image", select my compiled kernel and select "boot" partition). When I restart my phone... I got bootloop :crying::crying::crying: Even I couldn't enter in Recovey/TWRP, I had to use my PC to flash again the TWRP recovery and enter it.
What am I doing wrong? The "Image" file is wrong and I have to get "Image.gz" file?. If someone could compile our Redmi 3s sources, please, could you explain how did you do it?
Sorry the big text (and my bad English), thanks in advantage
Cheers!
Please, anyone?
I think that my problem is unpacking and repacking the boot.img because if I unpack original boot.img and, without any modifications, repack the same boot folder, when I flash it, I get bootloop... I follow this instructions but I don't know what I'm doing wrong :
https://github.com/xiaolu/mkbootimg_tools
I tested packing boot.img with "Image", "Image.gz" and "Image.gz.-dtb" files (renamed to "kernel") without sucess :S. I don't know what to do....
Regards!
EDIT: Sorry double post :S
maybe you should ask personally to someone who know how to compile source code, like anik, zwliew, hriday etc. sorry for my bad english
Sent from my Redmi 3S using Tapatalk
Stuck
ercea said:
Please, anyone?
I think that my problem is unpacking and repacking the boot.img because if I unpack original boot.img and, without any modifications, repack the same boot folder, when I flash it, I get bootloop... I follow this instructions but I don't know what I'm doing wrong :
https://github.com/xiaolu/mkbootimg_tools
I tested packing boot.img with "Image", "Image.gz" and "Image.gz.-dtb" files (renamed to "kernel") without sucess :S. I don't know what to do....
Regards!
Click to expand...
Click to collapse
I am stuck on the same place as you're. But I tried it on Lineage OS and the one I compiled back using everything stock(no change of kernel) worked fine. So I think the problem isn't unpacking or repacking. There's something in the kernel.
ercea said:
Please, anyone?
I think that my problem is unpacking and repacking the boot.img because if I unpack original boot.img and, without any modifications, repack the same boot folder, when I flash it, I get bootloop... I follow this instructions but I don't know what I'm doing wrong :
https://github.com/xiaolu/mkbootimg_tools
I tested packing boot.img with "Image", "Image.gz" and "Image.gz.-dtb" files (renamed to "kernel") without sucess :S. I don't know what to do....
Regards!
Click to expand...
Click to collapse
@ercea
So I tweaked around a little bit and found out that the one we are gonna use to boot is Image.gz-dtb. But in our case the dtb(s) are not built itself by the kernel(i am still searching why). So I used spilt-append-tool and extracted dtb(s) from the unpacked kernel and pasted them in arch/arm64/boot/dts. I know this doesn't mean anything but still makes the kernel boot.
Edit : After a little more messing I found out that the dtb(s) required to make the booting kernel reside in arch/arm64/boot/dts/qcom. So I made a script that copies all the dtb(s) to arch/arm64/boot/dts.
And it is working.
aweosomeabhijeet said:
@ercea
So I tweaked around a little bit and found out that the one we are gonna use to boot is Image.gz-dtb. But in our case the dtb(s) are not built itself by the kernel(i am still searching why). So I used spilt-append-tool and extracted dtb(s) from the unpacked kernel and pasted them in arch/arm64/boot/dts. I know this doesn't mean anything but still makes the kernel boot.
Edit : After a little more messing I found out that the dtb(s) required to make the booting kernel reside in arch/arm64/boot/dts/qcom. So I made a script that copies all the dtb(s) to arch/arm64/boot/dts.
And it is working.
Click to expand...
Click to collapse
Wow!! Thank you! I will try it after work, I abandoned it after a few tests without success (and I very noob for fix this kind of problems xD). I will check your tips and tell if it works for me (I'm sure that yes ).
Regards and thanks again for your help!
Good evening everyone!
I recently bought a Junsun V1 head unit for my Golf 7. I specifically chose it because of the AC8227L SOC, which is a renamed MT8127. It includes a few more peripherals that are useful in car infotainment systems, but the core is identical.
I'm in the process of creating a new firmware from scratch, to replace the chinglish, buggy stock one. However, I have not succeeded yet.
What I have done so far is create a TWRP image for it, completely from source, using the prebuilt kernel. It's available here (any mirrors will be appreciated and linked in this post):
https://mega.nz/file/1Gp2gJ5S#gAxcP1WK8nwXivYTpAlyEsWNoWwNZBZ8VTs3fm57gEc
I have also dumped the firmware from the 2GB + 32GB version: https://mega.nz/file/hXhEjTab#AowvrX36nn9rXIkeu_zgnGmLyDxtiSUSWswwmXcN46k
To install install TWRP simply put it on the "RECOVERY" section in SP Flash Tool using the scatter and preloader provided in the firmware dump. Uncheck everything else and press flash.
You'll need a type-a to type-a USB cable connected to the 4-pin USB connector (not the 6-pin), and then give power to the unit.
Any other information about the device, serial communication between android and the MCU, decompiled apps, modified apps, etc are also welcome!
I hope this is useful for somebody.
UPDATE 07-01-2021:
I've been reverse engineering the MainUI apk for a week now. I've extracted the MCU communication protocol, now I'm trying to extract the DSP protocol, and CAN will be next.
The touch buttons on the left side of the unit is managed by this .apk as well, and that has already been reverse engineered, only the implementation has to be done with the available API I wrote.
All help is welcome. You can find the source code in github. The important work is being done in native libraries, the java stuff is useless right now. https://github.com/Iscle/MainUI
root
hi, i think i have a HU similar to yours ( se e attached pucture ). Btw did you manage to root the original fw? what about your development, it sounds interesting...
root
......see attachment
maxou2 said:
hi, i think i have a HU similar to yours ( se e attached pucture ). Btw did you manage to root the original fw? what about your development, it sounds interesting...
Click to expand...
Click to collapse
maxou2 said:
......see attachment
Click to expand...
Click to collapse
If you can install TWRP then you will be able to root.
iceblue1980 said:
If you can install TWRP then you will be able to root.
Click to expand...
Click to collapse
magisk?
maxou2 said:
magisk?
Click to expand...
Click to collapse
Anything you want but I would really recommend SuperSU as Magisk doesn't work as intended on these units. Also make sure you run SuperSU v2.79 and no higher. As for TWRP, only version 3.0.2 is stable in my experience.
I'm stuck unlocking the bootloader, the command "fastboot oem unlock" works and the unit ask to confirm by pressing vol+, unfortunately the touch on the panel does not work... tried to put a wireless keyboard dongle on the other USb but it doesn't work....
{
"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"
}
Magisk works just fine, I actually recommend it over SuperSU, as SuperSU is practically obsolete nowadays.
Also, no need to unlock the bootloader, just flash the recovery image as I explained on the first post.
Just made a deep study and tests on this unit, here my results, thoughts, mods and other considerations hoping this will help.
Being scared to brick the unit I used a conservative approach by making step by step mods rather than flash the firmware at the first post.
Here's my changment pattern:
Firmware : Before rooting I updated to the last version of the firmware the vendor gave me ( the latest OEM firmware ).
It's an OTA update ( use the "five fingers screen touch & move" method ) after putting the the files .bin and .upd in a USB key connected to a USB port when you powerup the unit.
I enclose a link to download it.
OTA update
I've made a DUMP of the partitions ( by using the SP tool Readback feature, you can find a lot of tutos on the internet how to use it ) and with the WwR tools i managed to have a full flashable original FW backup.
Another interesting method is to retrieve the partition content on a "live" system by use a shell and the dd unix command :
Enable the developer option on the system and connect the 4 wire USB port to a PC ( by using a 4 wire male to male USB cable ).
If you have an ADB command environment installed on your PC you can just fire a "adb shell" command,
followed by an "su @#zxcvbnmasdfghjklqwertyuiop1234567890,." to have a shell with superuser rights.
Now you can navigate trought your file system as root.
Anyway here's the partions table :
/dev/block/platform/soc/11230000.mmc/by-name # ls -l
lrwxrwxrwx 1 root root 21 Dec 3 14:26 ANDROID -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Dec 3 14:26 ARM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Dec 3 14:26 BOOTIMG -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Dec 3 14:26 CACHE -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Dec 3 14:26 DKB -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Dec 3 14:26 EXPDB -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Dec 3 14:26 FRP -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Dec 3 14:26 KB -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Dec 3 14:26 LK -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Dec 3 14:26 LOGO -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Dec 3 14:26 METAZONE -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Dec 3 14:26 MISC -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Dec 3 14:26 NVRAM -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Dec 3 14:26 ODMDTBO -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Dec 3 14:26 PROTECT_F -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Dec 3 14:26 PROTECT_S -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Dec 3 14:26 PRO_INFO -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Dec 3 14:26 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Dec 3 14:26 SECCFG -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Dec 3 14:26 SEC_RO -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 Dec 3 14:26 TEE1 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Dec 3 14:26 TEE2 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Dec 3 14:26 VENDOR -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Dec 3 14:26 forfanzone -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Dec 3 14:26 tszone -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Dec 3 14:26 userdata -> /dev/block/mmcblk0p26
Just use the dd unix command to dump every partitions content to a /sdcard directory where you can easily copy to an external USB stick or PC via adb pull.
E.g: dd if=/dev/block/mmcblk0p10 of=/sdcard/TWRP/boot_from_dd.img
Luckily I didn't have to use these datas to unbrick my system...
TWRP : I used another version ,it's a v3.3.1, works well. Flashed with SP Flash tool and the scatter contained in the .zip firmware at first post. I enclosed it so someone can tell what's the best option amongst these.
ROOT : Flashing magisk zip from TWRP worked flawlessy, but in my case i experienced an additional delay at boot ( let's say between 20-30 sec ), now a cold boot takes about 1 minute whereas with no root it was about 35 secs. I suspect this is due to the magisk modification to the boot process .
HW mods, temp controls and other infos will follow.
Any questions, just ask.
I have v1 1ram 16rom with ac8227l, but when I tried to update my radio I was only able to with an update-ty.zip with a manual process like this:
What I can do????
this is the last firmware that junsun send to me https://drive.google.com/file/d/1OjZcB0yqVQsu8O63l58VrMneZBmr25p5/view?usp=sharing
jabatillo_2001 said:
this is the last firmware that junsun send to me https://drive.google.com/file/d/1OjZcB0yqVQsu8O63l58VrMneZBmr25p5/view?usp=sharing
Click to expand...
Click to collapse
jabatillo_2001 said:
I have v1 1ram 16rom with ac8227l, but when I tried to update my radio I was only able to with an update-ty.zip with a manual process like this:
What I can do????
Click to expand...
Click to collapse
Your update process is very different from mine, probably you should tick every checkbox ( the most dangerous could be the MCU IMHO ) and start the update process. You should check first with the vendor, but it seems the correct procedure if the files he sent you match your Head Unit.
BTW take some picture of the MCu version, FW revision etc... of your unit.
Actually the compressed file they sent you contains BOOT, SYSTEM, TEE AND VENDOR updated partitions, and .bin update file ( usually the mcu update are .bin file but in my experience are really smaller then the one contained in the zip so it's diffucult to know what is for ).
So probably you should tick the "Sistema - > update_ty.zip" ONLY and start the update process....
The update only works with this name of file update-ty.zip, others don't work. My problem is bluetooth, It Connects and disconnects all the time. I'm crazy with this, I think the problem is bttool.apk or MTK but I'm not sure.I'm not allow to call or answer calls, either I can't dial by numbers.
I need to try some other firmware to resolve the problem.
Perhaps you can give me one idea or some trick to help me.
Thanks a lot.
My Android mobile XDA app don't work properly, after I'll attach you photos of my radio characteristics.
maxou2 said:
Actually the compressed file they sent you contains BOOT, SYSTEM, TEE AND VENDOR updated partitions, and .bin update file ( usually the mcu update are .bin file but in my experience are really smaller then the one contained in the zip so it's diffucult to know what is for ).
So probably you should tick the "Sistema - > update_ty.zip" ONLY and start the update process....
Click to expand...
Click to collapse
jabatillo_2001 said:
The update only works with this name of file update-ty.zip, others don't work. My problem is bluetooth, It Connects and disconnects all the time. I'm crazy with this, I think the problem is bttool.apk or MTK but I'm not sure.I'm not allow to call or answer calls, either I can't dial by numbers.
I need to try some other firmware to resolve the problem.
Perhaps you can give me one idea or some trick to help me.
Thanks a lot.
My Android mobile XDA app don't work properly, after I'll attach you photos of my radio characteristics.
Click to expand...
Click to collapse
Need to be sure that the firmware in this thread match your unit first, take pictures of your system infos. BTW your unit is only 1 GB RAM right?
Can you post the link where you bought it? ( Probably aliexpress... )
Keep in mind that generally on these chinese HU the BT is not managed by the android system as with cellphones, it's the MCU and dedicated apk that usually do that ( you do not have any BT option in the android system settings ).
So:
1) Did you try with a system reset?
2) Can you reach an advanced system option menu ( a little bit tricky in my unit ) where you can interact deeply ( BE VERY CAREFUL ) with several options, here you can set some BT systemwide parameters.
3) Maybe an MCU update could also help
1) yes
2)Wells, only development options of Android, the firmware not contains BT options. If you turn off BT, It turns off automatically. BT music only works if you play by mobile, neither by radio.
3) Perhaps, but it's the same problem, to update MCU I need a file named m51_update. You can see in image.
I have a A2 Lite of Xiaomi, but I try in a note 6 pro and the same problem.
What can I do?
I don't know what I can modify native MCU, but I like to probe another compatible ROM.
All my test, without rooting, are around Android 8.1 BT problems..
Bttool.apk don't work properly, disconnects for example, when I try to syncronize the contacts.
I'm afraid to brick It installing by flashing.
maxou2 said:
Keep in mind that generally on these chinese HU the BT is not managed by the android system as with cellphones, it's the MCU and dedicated apk that usually do that ( you do not have any BT option in the android system settings ).
So:
1) Did you try with a system reset?
2) Can you reach an advanced system option menu ( a little bit tricky in my unit ) where you can interact deeply ( BE VERY CAREFUL ) with several options, here you can set some BT systemwide parameters.
3) Maybe an MCU update could also help
Click to expand...
Click to collapse
maxou2 said:
Need to be sure that the firmware in this thread match your unit first, take pictures of your system infos. BTW your unit is only 1 GB RAM right?
Can you post the link where you bought it? ( Probably aliexpress... )
Click to expand...
Click to collapse
The firmware I posted on the first post was also extracted with SP Flash Tools + WwR tools. I sent it to a friend who uploaded a dump made with dumpyara here: https://git.rip/dumps/ffkj/ff-5000
This way we can navigate the filesystem easily, and grab anything we need.
I'm in the process of creating a kernel source for this SoC, I don't know if it will work, but if it does, the first thing I'll do is overclock it haha
jabatillo_2001 said:
1) yes
2)Wells, only development options of Android, the firmware not contains BT options. If you turn off BT, It turns off automatically. BT music only works if you play by mobile, neither by radio.
3) Perhaps, but it's the same problem, to update MCU I need a file named m51_update. You can see in image.
I have a A2 Lite of Xiaomi, but I try in a note 6 pro and the same problem.
What can I do?
I don't know what I can modify native MCU, but I like to probe another compatible ROM.
All my test, without rooting, are around Android 8.1 BT problems..
Bttool.apk don't work properly, disconnects for example, when I try to syncronize the contacts.
I'm afraid to brick It installing by flashing.
Click to expand...
Click to collapse
You should check your HU Hardware parameters, so you can figure is this thread is for you.
System "About device" - see picture.. Take a picture of the values on the screen.
After that touch the Gear icon on the top right of the screen a popup menu will appear, digit 8888 and ok.
An advanced system setting menu will appear, choose "others", scroll down and you'll see some BT options ( see picture ), try to change them.
Save and reboot.
If your system doesn't have such as menus I strongly recommend you to check elsewhere because probably your HU is different from mine.