Related
Hello HTC Shift users,
I found how to visible recovery partition.
Warning;
I will no response for your data lost with this method.
Requirement;
1. ICC (IDE HDD Capacity Changer)
http://homepage3.nifty.com/k-takata/mysoft/icc.html
It's writen only Japanese.
Download icc007a.lzh and unpack ICC.EXE from archive.
2. TestDisk for DOS (Undelete partition)
http://www.cgsecurity.org/wiki/TestDisk_Download
Download testdisk-6.9.dos.zip and unpack TESTDISK.EXE and CWSDPMI.EXE from archive.
3. USB-FDD and One blank FD
How to;
1. Make MS-DOS startup disk
Connect USB-FDD to SHIFT and insert blank FD.
Format FD with checked "Create an MS-DOS startup disk" option.
Copy ICC.EXE, TESTDISK and CWSDPMI.EXE to startup disk.
2. Boot from startup disk
Restart SHIFT.
Press Fn+F10 on boot screen.
Select Boot from USB-FDD.
Wait command prompt "A:\>".
3. Change HDD size
Enter command as "ICC -i" for show HDD size ( keep this value for restore ).
> ModelNumber: "TOSHIBA MK4009GAL "
> Maximum Capacity (28bit LBA): 78126048 (38147MB)
> Current Capacity (28bit LBA): 71826615 (35071MB)
> Current Capacity (48bit LBA): 71826615 (35071MB)
Enter command as "ICC" and input new capacity as "max".
Restart SHIFT and boot from startup disk again.
4. Mount hidden partition
Enter command as "TESTDISK" for search and mount hidden partition.
> Results
> * HPFS - NTFS 0 1 1 4470 254 63 71826552 [HTCShift]
> NTFS, 36 GB / 34 GiB
> P FAT32 LBA 4471 0 1 4863 254 63 6313545 [NO NAME]
> FAT32, 3232 MB / 3082 MiB
Restart SHIFT.
After this procedure, you can show hidden partition as Local Disk(D.
Attention;
Recovery boot (Fn+F3) will be disable after visible hidden partition !
If you want to enable recovery boot, use "ICC" and enter "71826615LBA".
riki0081 from Japan.
riki0081 said:
...
3. Change HDD size
Enter command as "ICC -i" for show HDD size ( keep this value for restore ).
> ModelNumber: "TOSHIBA MK4009GAL "
> Maximum Capacity (28bit LBA): 78126048 (38147MB)
> Current Capacity (28bit LBA): 71826615 (35071MB)
> Current Capacity (48bit LBA): 71826615 (35071MB)
Enter command as "ICC" and input new capacity as "max".
Restart SHIFT and boot from startup disk again.
...
Click to expand...
Click to collapse
Hello Riki0081,
I've exactly the same numbers as yours but I'm getting a "Can't set max address" when I'm validating the 78126048 input.
Any suggestions?
(booting on Bootable USB dongle, with Win98 DOS system files, no config.sys/autoexec.bat)
Yann
YannR said:
Hello Riki0081,
I've exactly the same numbers as yours but I'm getting a "Can't set max address" when I'm validating the 78126048 input.
Any suggestions?
(booting on Bootable USB dongle, with Win98 DOS system files, no config.sys/autoexec.bat)
Yann
Click to expand...
Click to collapse
Hello Yann,
I show two answer for clear problems.
1) Enter "max". It's not number.
2) Enter "78126048LBA". The "LBA" is very important.
And if you enter number with ICC.EXE, you have to reboot.
You can change this number only one time without reboot.
best regards,
riki0081
riki0081 said:
Hello Yann,
I show two answer for clear problems.
1) Enter "max". It's not number.
2) Enter "78126048LBA". The "LBA" is very important.
And if you enter number with ICC.EXE, you have to reboot.
You can change this number only one time without reboot.
best regards,
riki0081
Click to expand...
Click to collapse
Hello Riki,
While you were kindly replying to me, I kept trying hard... I didn't saw your reply until I reach my goal.
By the way, I tried "78126048LBA" without success. I didn't try to input "max" but I guess entering equivalent number was ok. But still failing and getting the above error message...
So, I tried to launch ICC.EXE with the "-b" option (BigDisk mode) and I've got the change effective!
Switching Off and On the Shift and booting installed Vista. Going to "Disk Management" tool, "Extend Volume" up to the max... I've now +3GB space available to Vista! (to readers : make sure you have a Disk image to be used as Recovery tool)
Thank you for the tip and your help!
Yann
I maybe thick...
I have followed the directions to make the hidden partition. I can change the size of the HDD using ICC.exe but I get stuck on how to use TESTDISK to mount the hidden partition so that when Vista boots is see's the hidden partition as another drive. please help this novice.
CowboyJoe said:
I have followed the directions to make the hidden partition. I can change the size of the HDD using ICC.exe but I get stuck on how to use TESTDISK to mount the hidden partition so that when Vista boots is see's the hidden partition as another drive. please help this novice.
Click to expand...
Click to collapse
Hello CowboyJoe,
I feel sorry for delay response because I'm travelling without USB-FDD.
I try TESTDISK again and I found no problems. When you will get stuck ?
Run TESTDISK
[ Create ][ Append ][ No Log ] <- select No Log
Disk 80 - 40 GB / 37 GiB
[Proceed ][ Quit ] -< select Proceed
[Intel ] select here
[EFI GPT]
[Mac ]
[None ]
[Sun ]
[XBox ]
[Return ]
[ Analyse ] select here
[ Advanced ]
[ Geometry ]
[ Options ]
[ MBR Code ]
[ Delete ]
[ Quit ]
1 * HPFS - NTFS 0 1 1 4470 254 63 71826552 [HTCX9500]
[Quick Search] [ Backup ] <- select Quick Search
Should TestDisk search for partition created under vista ? [Y/N] <- Press N
Disk 80 - 40 GB / 37 GiB - CHS 4863 255 63
Partition Start End Size in sectors
* HPFS - NTFS 0 1 1 4470 254 63 71826552 [HTCX9500]
P FAT32 LBA 4471 0 1 4863 254 63 6313545 [NO NAME]
Enter: to continue
[ Quit ] [Deeper Search] [ Write ] <- select Write
riki0081
What to do with all the files off the hidden Partition
Thanks. I did the deeper search and found the 3gig partition. I selected it and did a "P" to list files. I then copied all the files and directories to the USB stick. The biggie is XVISTA.WIM which is approx. 2gig in size. Now how would I execute or launch the file to do an install on to a fresh HDD. I know that with the fresh HD I will not be able to do this like before using FN+F3. But thats ok. But at least I have a copy of the Initial Install of Vista Business for the Shift as it comes from the OEM.
CowboyJoe said:
Thanks. I did the deeper search and found the 3gig partition. I selected it and did a "P" to list files. I then copied all the files and directories to the USB stick. The biggie is XVISTA.WIM which is approx. 2gig in size. Now how would I execute or launch the file to do an install on to a fresh HDD. I know that with the fresh HD I will not be able to do this like before using FN+F3. But thats ok. But at least I have a copy of the Initial Install of Vista Business for the Shift as it comes from the OEM.
Click to expand...
Click to collapse
Hello CowboyJoe,
Do you want to copy files from hidden recovery partition to USB stick ?
Show this thread.
http://forum.xda-developers.com/showthread.php?t=393070
riki0081
Yes. That is what I am doing. After I backup and restore the hidden partition to a USB, how do I do the second part which is to restore MBR to track 0?
CowboyJoe said:
Yes. That is what I am doing. After I backup and restore the hidden partition to a USB, how do I do the second part which is to restore MBR to track 0?
Click to expand...
Click to collapse
Hello CowboyJoe,
I'm using Acronis True Image Home. When you restore from backup to USB drive,
you can select one option from two.
1) FAT32
2) MBR and Track 0
I attach screen capture of Acronis.
I feel sorry that I'm using Japanese version ( not English ).
You can not select both options at same time.
I recommend, restore FAT32 at 1st, restore MBR and track 0at 2nd.
riki0081
Thanks, I got it to work. I was able to reimage the HDD and get rid of the 3gig in hidden partition to provide more space.
Hi Riki0081...
I've problem..
With testdisk i've paste the two partition at the same, but my primary partition are ok..
Because now when i quick search the partition with testdisk i've one partition HPFS - NTFS with 71826552 and second partition HPFS - NTFS with 78126048...
In testdisk there's a tool i can restore mbr with backup... You have backup, or how i can solve this problem??? thanks!!!
killer_t said:
In testdisk there's a tool i can restore mbr with backup... You have backup, or how i can solve this problem??? thanks!!!
Click to expand...
Click to collapse
Hello killer_t,
I attach archived two files.
One is BACKUP.LOG for restore, another one is TESTDISK.LOG for information.
Would you restore yourself ?
best regards,
riki0081 from Japan
riki0081 said:
Hello killer_t,
I attach archived two files.
One is BACKUP.LOG for restore, another one is TESTDISK.LOG for information.
Would you restore yourself ?
best regards,
riki0081 from Japan
Click to expand...
Click to collapse
Thank you, yes i whant to restore my-self..
hi all
I need your help. I think that I have done all the procedure and I have stack to step 3. Change HDD size, when I must put the max capacity.
I have try all this :
"78126048LBA" (is the same as I sow with ICC -i)
"78126048 LBA"
"78126048"
"MAX"
every time whith reboot but nothing.....?
curent Capacity is 69304410 (33840MB) and my shift is the 9501 model
I can not change the maximum capasity and ofcource I can't see the RP.
(Sory for my bad english)
Please HELP
Hellllp deleted my Windows Vista & Recovery on HTC Shift
Help CowieBoy, can you do me a favor? I accidentally write on the Modified HD, now I lost the Windows Vista & Recovery File, can you please Upload all the Recovery File on Megaupload I now its a bit inconvenient but hope you can give it a try? Pls pls I really need your help & I would really appreciate it.
The biggie is XVISTA.WIM which is approx. 2gig in size. Now how would I execute or launch the file to do an install on to a fresh HDD. I know that with the fresh HD I will not be able to do this like before using FN+F3. But thats ok. But at least I have a copy of the Initial Install of Vista Business for the Shift as it comes from the OEM.
Hello,
Can you help me to solve my problem with my shift (I can't restore my Vista with Fn+F3, because il doesn't find anything...).
So I tried (hard) to make visible my recovery partition (I did it from a usb key bootable).
What I did is following the previous steps, and when I hit "write", there was a problem (no more Vista at bootup). But I recover from it and now, this is what I found doing the same steps :
ICC -i
>same things than before, same characteristics
ICC -b
>78126048LBA
and it says "Capacity is changed. Reboot".
TestDisk
I did everything 'till :
> * HPFS-NTFS 0 1 1 4861 254 63 78107967
This is different from what I'm supposed to have, because there is one missing...
After a "Deeper search" : I have 5 lines instead of 2 in your example...
> HPFS-NTFS 0 1 1 4861 254 63 78107967
> HPFS-NTFS 0 32 33 4470 254 63 71824567 [Systeme]
> HPFS-NTFS 0 32 33 4470 254 63 71824567 [Systeme]
> FAT32 LBA 4471 0 1 4863 30 62 6299432 [no name]
> FAT32 LBA 4471 0 1 4863 30 62 6299432 [no name]
What is my problem, because, of course, I can't see the hidden partition...
Thank you.
Soween said:
Hello,
Can you help me to solve my problem with my shift (I can't restore my Vista with Fn+F3, because il doesn't find anything...).
So I tried (hard) to make visible my recovery partition (I did it from a usb key bootable).
What I did is following the previous steps, and when I hit "write", there was a problem (no more Vista at bootup). But I recover from it and now, this is what I found doing the same steps :
ICC -i
>same things than before, same characteristics
ICC -b
>78126048LBA
and it says "Capacity is changed. Reboot".
TestDisk
I did everything 'till :
> * HPFS-NTFS 0 1 1 4861 254 63 78107967
This is different from what I'm supposed to have, because there is one missing...
After a "Deeper search" :
> HPFS-NTFS 0 1 1 4861 254 63 78107967
> HPFS-NTFS 0 32 33 4470 254 63 71824567 [Systeme]
What is my problem, because, of course, I can't see the hidden partition...
Thank you.
Click to expand...
Click to collapse
You have wrong to digit ICC -b
Your recovery partition now are destroyed...
If you want put all file in hidden partition and recompile it with bartpe do this:
Run TESTDISK
[ Create ][ Append ][ No Log ] <- select No Log
Disk 80 - 40 GB / 37 GiB
[Proceed ][ Quit ] -< select Proceed
[Intel ] select here
[EFI GPT]
[Mac ]
[None ]
[Sun ]
[XBox ]
[Return ]
[ Analyse ] select here
[ Advanced ]
[ Geometry ]
[ Options ]
[ MBR Code ]
[ Delete ]
[ Quit ]
1 * HPFS - NTFS 0 1 1 4470 254 63 71826552 [HTCX9500]
[Quick Search] [ Backup ] <- select Quick Search
Should TestDisk search for partition created under vista ? [Y/N] <- Press N
Disk 80 - 40 GB / 37 GiB - CHS 4863 255 63
Partition Start End Size in sectors
* HPFS - NTFS 0 1 1 4470 254 63 71826552 [HTCX9500]
P FAT32 LBA 4471 0 1 4863 254 63 6313545 [NO NAME]
[ Quit ] [Deeper Search] [ Write ] <- select Deeper Search
run totally deepersearch, and you have to find the fat32 [NO NAME] partition, and if you don't find the hpfs [HTCX9500] partition you have to create one..
Select [HTCX9500] primary bootable, and [NO NAME] primary
Write partition table and reboot.
Now you can see the HPA partition, but you can't use that in future with FN+F3!!
Sorry, I was typing the final "deepersearch" thing when you answered, it changes a little what you are saying, sorry...
Soween said:
Sorry, I was typing the final "deepersearch" thing when you answered, it changes a little what you are saying, sorry...
Click to expand...
Click to collapse
Typing deeper search, but you have to wait ALL searching time (100%)
RF/Radio properties of the ServiceMode Application
Thread Difficulty: HARD
Thread Noob Patience: LOW
Thread Topic
This thread is a Reference and Research & Development thread for
investigating and to better document the various radio related variables
as found and displayed by the ServiceMode application. Here we are
particularly concerned with those found in Samsung phones, but as
you will see, this is more modem (BP/CP) dependent than phone model
dependent. So much of this info should also apply to other devices
using the same modem.
Off Topic?
If you have questions that does not directly concern the main focus
of this thread, please ask in the general forum. If you ask support
questions here, they will be deleted without warning.
If you're just looking for info how to enter the Service Menu on a recent
Samsung, look in this thread:
[REF][ServiceMode] How to make your Samsung perform dog tricks
Background
Because the ServiceMode (SM) application is really running in the
Modem under its own RTOS, it is limited in the presentation. So what
you see running in the AOS ServiceMode application is really just a
Java wrapper to code that is running in the RTOS. This severely
limits the information presented, if accessible at all.
Most mobile device manufacturers doesn't want their users to have
access to the ServiceMode functions, for various and good reasons.
Perhaps the best reason is that you can easily hard-brick your
device and/or mess up all the internal radio related settings.
However, we are already used to this, so why not have a better look
at the mobile network parameters within our devices. These can be
extremely useful from identifying network problems to detect and
prevent illegal or clandestine mobile network monitoring.
So what are the limiting factors of the ServiceMode Application?
It is a Java wrapper application that is usually made by
the device manufacturer (Samsung, HTC, Nokia etc) that
need to be present and compatible with your AOS FW.
(API, RIL etc)
The actual code is running in Modem RTOS and usually queried
by ServiceMode.apk by the use of a RIL_REQUEST_OEM_HOOK_RAW request,
that allows requests to circumvent the normal RIL filter.
The parameters present depends on the Modem FW versions.
(You will find many misspellings and other FUBAR objects in
various modem SM presentations.)
The displayed RF related parameters depend on the Modem HW,
and are thus completely different in an Intel XMM modem, than
for an Qualcomm MSM type modem/processor SoC, and so on.
The displayed RF related parameters depend on the network
you are currently using and connected to.
But the mobile network interface is transparent from the AOS AP point
of view, so a large set of radio parameters must comply to the 3GPP
standards in order for your device to function properly. But only a
very small subset of these RF parameters are part of the non-internal AOS API.
We want more!
By carefully looking at all the details and information that is
presented by the SM application, we can find out many more and
useful network details, such as ciphering modes, network types,
bands, and technology used. But to do this we need to understand
the language used. Unfortunately, many times the language does
not reflect the current 3GPP standards, so we are left to guess,
until some anonymous modem RF-expert/developer come along and
correct us.
So if you happen to know anything specific, this is where you
can really help this thread...
ServiceMode Vocabulary
Here I try to resolve some of the more obscure sounding items,
as found in the SM of mainly two devices.
(a) Samsung Galaxy S2 (GT-I9100, XXKI1 with Intel XMM6260 modem)
(b) Samsung Galaxy S4-mini (GT-I9195, XXUBML4 with Qualcomm MSM8930AB SoC)
In post#2 you will find an almost complete menu structure for
the UMTS MENU items as found in (b). I have not posted the items
for the LTE or CDMA menus, since I don't have that network, which
means I don't know how they would look. So feel free to post your
own findings, if you use those.
Also, remember that the end-point/detailed view of the menu
items, depend on your current network. I.e. you will see
different items, when connected to GSM vs. WCDMA, and so on.
In post#3 I show the detailed explanations of the various
3GPP defined RR timers as shown under the NAS/MM items.
In post#4 I attempt to describe the specific end-point menu items:
Code:
[SIZE=2] [1] BASIC INFORMATION
[1] MM INFORMATION
[2] MM REJECT CAUSE
[3] GMM REJECT CAUSE
[3] AS INFORMATION
[4] NEIGHBOUR CELL
[/SIZE]
I still need help deciphering some of those values.
(What exactly do they represent and mean?)
The root MAIN MENU
Code:
MAIN MENU
[1] [B]UMTS[/B]
[2] CDMA
[3] LTE
[4] SIM- Not Used. ==> <E>
[5] DOCOMO DEBUG SCREEN
[6] run EFS SYNC()
[7] DEBUG SCREEN
The UMTS MENU tree
Here is an almost complete menu structure for the UMTS MENU items
found in a GT-I9195. I have not posted the items for the LTE or CDMA
menus, since I don't have that network, which means I don't know how
they would look. So please post your own findings, if you use those.
Code:
[SIZE=2][1] UMTS MAIN MENU
[1] DEBUG SCREEN
[2] VERSION INFORMATION
[3] UMTS RF NV
[4] GSM RF NV
[5] AUDIO
[6] COMMON
[7] LTE BAND CONFIG CHECK
------------------------------
[1] DEBUG SCREEN
[1] BASIC INFORMATION ==> <E> Code: 0011
[2] NAS INFORMATION
[3] AS INFORMATION
[4] NEIGHBOUR CELL
[5] GPRS INFORMATION
[6] SIM INFORMATION
[7] HANDOVER
[8] PHONE CONTROL
[9] ANTENNA/ADC
[1] // BASIC INFORMATION ==> <E>
RRC: IDLE, Band1
MCC-MNC:nnn-01
RX: 10663, RI: -59, CID: hhhhh
TX: 9713, PSC: 394
EcIo: -4, RSCP: -63
SpeechVER: FR FR FR
L1: PCH_Sleep
Drx cycle: 64
SIB19 is received
therm: 162 LNA: 0
Service: Available
[2] NAS INFORMATION
[1] MM INFORMATION
[2] MM REJECT CAUSE
[3] GMM REJECT CAUSE
[4] PS REJECT CAUSE
[5] RESET MM&GMM REJECT List
[6] EF_RAT INFORMATION
[7] SAT REFRESH INFO
[8] SMC RESULT INFO
[9] CALL END CAUSE
[1] // MM INFORMATION
mm: Idle
MCC-MNV: nnn-01
LAC: hhh, RAC: nn
TIMER_T32: 10(S) 11(S) 12(A)
13(S) 20(S) 30(S) 40(S)
GmmState: Registered(3)
SubState: normal(0)
PmmMode: IDLE(1)
rej_cause: 0, IuAttCnt: 0
TMSI: hhhhhhh
[2] // MM REJECT CAUSE
MM reject Information List
1. Time: 1M 6D 0h00m00s
Type: 0, Cause:0 000-000, GSM
2. Time: 1M 6D 0h00m00s
Type: 0, Cause:0 000-000, GSM
3. Time: 1M 6D 0h00m00s
Type: 0, Cause:0 000-000, GSM
4. Time: 1M 6D 0h00m00s
Type: 0, Cause:0 000-000, GSM
5. Time: 1M 6D 0h00m00s
Type: 0, Cause:0 000-000, GSM
6. Time: 1M 6D 0h00m00s
Type: 0, Cause:0 000-000, GSM
[3] // GMM REJECT CAUSE
GMM reject Information List
1. Time: 4M 9D 14h19m02s
Type: 4, Cause:7 nnn-01, UMTS
2. Time: 1M 6D 0h00m00s
Type: 0, Cause:0 000-000, GSM
3. Time: 1M 6D 0h00m00s
Type: 0, Cause:0 000-000, GSM
4. Time: 1M 6D 0h00m00s
Type: 0, Cause:0 000-000, GSM
5. Time: 1M 6D 0h00m00s
Type: 0, Cause:0 000-000, GSM
[4] // PS REJECT CAUSE
PDP and PDN recet List
- No Data
[5] // RESET MM&GMM REJECT List <== Immediately clears reject list!
[6] // EF_RAT INFORMATION
Boot-up EF_RAT
NONE(-1)
Refreshed EF_RAT
1.GSM_WCDMA(1), 000-000
2.GSM_WCDMA(1), 000-000
3.GSM_WCDMA(1), 000-000
4.GSM_WCDMA(1), 000-000
5.GSM_WCDMA(1), 000-000
[7] // SAT REFRESH INFO
<exactly the same as above>
[8] // SMC RESULT INFO --> <E>
RRC: IDLE, Band1
MCC-MNC: nnn-01
RX: 10663, RI: -59, CID: hhhhh
TX: 9713, PSC: 394
EcIo: -4, RSCP: -63
SpeechVER: FR FR FR
L1: PCH_Sleep
Drx cycle: 64
SIB19 is received
therm: 162 LNA: 0
Service: Available
[9] // CALL END CAUSE --> <E>
<exactly the same as above>
[3] // AS INFORMATION
RRC: IDLE, Band1
WCDMA: IDLE
RX: 10663, RI: -59, CID: hhhhh
TX: 9713, PSC: 394
EcIo: -4, RSCP: -63
VOC: FR FR FR, 0
L1: PCH_Sleep
CQI: 0, Sam: 0
[4] // NEIGHBOUR CELL
Aset: [/SIZE][SIZE=2][SIZE=2]10663[/SIZE] 394 -60 -7 53 29 <== rapid changes
Sych: [/SIZE][SIZE=2][SIZE=2]10663[/SIZE] 403 -83 -51 31 -15
Sych: [/SIZE][SIZE=2][SIZE=2]10663[/SIZE] 403 -83 -51 31 -15
Sych: [/SIZE][SIZE=2][SIZE=2]10663[/SIZE] 403 -83 -51 31 -15
Asych: [/SIZE][SIZE=2][SIZE=2]10663[/SIZE] 422 -121 -49 29 -1
Asych: [/SIZE][SIZE=2][SIZE=2]10663[/SIZE] 262 -121 -49 0 0
Asych: [/SIZE][SIZE=2][SIZE=2]10663[/SIZE] 102 -121 -49 0 0
Asych: [/SIZE][SIZE=2][SIZE=2]10663[/SIZE] 450 -121 -49 0 0
[5] GPRS INFORMATION
FUNCTION:ds_gprs_information
[6] SIM INFORMATION
[1] General Info
[2] QMI UIM status
[3] CHECK NV
[1] // General Info
SIM Phase: 0
Card Capability: USIM
SIM voltage class: 1.8V SIM
None
None
Proactive command:
00 00 00 00 00 00 00 00 00 00 - ^^ (10 Hex)
[2] // QMI UIM status
CARD_STATE: Present
CARD_ERROR: Unknown
APP_TYPE: USIM
APP_STATE: Ready
PERSO_STATE: Ready
PERSO_FEATURE: Unsupported
PIN1_STATE: Enabled_Verified
pin1_num(3), puk1_num(10)
PIN2_STATE: Enabled_Not_Verified
pin2_num(3), puk2_num(10)
[3] // CHECK NV
CHECK NV
Band pref: Unexpected value
RTRE Configuration: SIM based
FTM Mode: Online Mode
ENS: Disabled
UIM CLASS: UMTS
[7] HANDOVER
[1] HANDOVER GtoG
[2] HANDOVER GtoW
[3] HANDOVER WtoG
[4] HANDOVER TEST
[8] PHONE CONTROL
[1] DRX CONTROL
[2] FAKE SECURITY CONTROL
[3] NAS CONTROL
[4] UE STATE CONTROL
[5] SIMULATION
[6] NETWORK LOCK
[7] NETWORK CONTROL
[1] // DRX CONTROL
DRX: Not Active
[1] DRX: ON
[2] DRX: OFF
[2] // FAKE SECURITY CONTROL
FAKE SECURITY: OFF
[1] FAKE SECURITY: ON
[2] FAKE SECURITY: OFF
[3] NAS CONTROL
[1] CIPHERING CONTROL
[2] INTEGRITY CONTROL
[3] SIM CLASS CONTROL
[4] REVISION CONTROL
[5] RRC(HSPA) CONTROL
[6] DUALMODE IMPROVEMENT CONTROL
[7] NAS AVOID SECURITY CONTROL
[1] // CIPHERING CONTROL
CIPHERING CONTROL: ON
[1] CIPHERING: ON
[2] CIPHERING: OFF
[2] // INTEGRITY CONTROL
INTEGRITY CONTROL: ON
[1] INTEGRITY: ON
[2] INTEGRITY: OFF
[3] // SIM CLASS CONTROL
UIM CLASS: UMTS
[1] UIM CLASS: UMTS
[2] UIM CLASS: GSM
[4] REVISION CONTROL
[1] DISPLAY REVISION
[2] CHENGE REVISION
[5] RRC(HSPA) CONTROL
[1] DISPLAY RRC REVISION
[2] CHANGE RRC REVISION
[6] // DUALMODE IMPROVEMENT CONTROL
DUALMODE IMPROVEMENT: NOT ACT
[1] DUALMODE IMPROVEMENT: ON
[2] DUALMODE IMPROVEMENT: OFF
[7] NAS AVOID SECURITY CONTROL
AVOID_SECURITY_CHECK: NOT ACT
[1] SECURITY_CHECK: ON
[2] SECURITY_CHECK: OFF
[4] UE STATE CONTROL
[1] CALL CONNECT STATE
[2] CHANGE RAT TO WCDMA
[3] CHANGE RAT TO GSM
[5] SIMULATION
[1] Modem Assert (Reset)
[2] SW WATCHDOG
[3] HW WATCHDOG
[4] CP Logging (Started)
[5] Realtime Log(OFF) - Don't! <== WTF?
[6] NETWORK LOCK
[1] PERSO SHA256 Info
SHA256_ENABLE_FLAG [1]
[7] NETWORK CONTROL
[1] GCF
[2] BAND SELECTION ==> Code: [B]2263[/B] "BAND"
[3] SERVICE DOMAIN
[4] AQUISITION ORDER
[5] PLMN(AUTO/MANUAL) SELECTIO
[6] FPLMN
[7] IMSI replacement
[1] GCF
[1] GSM/(E)GPRS/WCDMA REL8
[2] GSM/(E)GPRS/WCDMA REL7
[3] GSM/(E)GPRS/WCDMA REL6
[4] GSM/(E)GPRS/WCDMA REL5
[5] SETTING CANCELLATION
[2] BAND SELECTION
[1] Automatic
[2] WCDMA Band Preference
[3] GSM Band Preference
[4] LTE Band Preference
[3] // SERVICE DOMAIN
[1] CS + PS (*)
[2] CS ONLY
[3] PS ONLY
[4] // AQUISITION ORDER
[1] Automatic
[2] GSM_UMTS
[3] UMTS_GSM (*)
[4] No Change
[5] // PLMN(AUTO/MANUAL) SELECTIO
[1] AUTOMATIC (*)
[2] MANUAL
[6] FPLMN
[1] FPLMN READ
[2] FPLMN DELETE ALL
[3] FPLMN DELETE EXCL DOM
[7] // IMSI replacement
[1] Enable
[2] Disable (*)
[9] ANTENNA/ADC
ds_antenna_adc
------------------------------
[2] VERSION INFORMATION
[1] SW VERSION
[2] HW VERSION
[3] UMTS RF
[1] RF NV READ
[2] RF NV WRITE
[3] UMTS DIVERSITY CONTROL
[4] RF CALIBRATION CHECK
[4] GSM RF
[1] RF NV READ
[2] RF NV WRITE
[5] AUDIO ==> Locked! See Note (a)
...
[6] COMMON
[1] FTM
[2] DEBUG INFO
[3] RF SCANNING
[4] DIAG CONFIG
[5] WCDMA SET CHANNEL
[6] NV REBUILD
[7] FACTORY TEST
[8] FORCE SLEEP
[9] GPS
[1] FTM : OFF ==> Locked! See Note (b)
[1] NOT SUPPORT
[2] FTM : OFF
[2] DEBUG INFO
[1] MM REJECT CAUSE
[2] LOG DUMP
[3] UI DEBUG POPUP - N/S
[3] RF SCANNING
[1] SETTING
[2] START RF SCANNING
[3] RESULT TO PC
[4] RESULT TO SCREEN
[4] DIAG CONFIG
[1] USB ( )
[2] UART (*)
[3] DBG MSG ON (*)
[4] DBG MSG OFF ( )
[5] WCDMA SET CHANNEL
[6] NV REBUILD
[7] FACTORY TEST
[8] FORCE SLEEP
[9] GPS
co_gps_menu
[7] LTE BAND CONFIG CHECK --> <E>
[/SIZE]
(Where I have replaced my LAC/CID with "nnnnn" and "hhhhh", respectively)
Note that the end-point/detailed view of the menu items, depend on your
current network. I.e. you will see different items, when connected to GSM vs. WCDMA.
For example. Here is a picture comparing the BASIC INFORMATION view for LTE, CDMA and GSM/UMTS, respectively.
{
"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"
}
(Picture stolen from THIS website. Sorry, there is no owner/contact info there to ask for permission.)
So what does all those numbers mean?
That's what we will try to figure out in the next posts and in this thread! But first I will show you
another menu view. The menu that concerns the MM (Mobile Management) MENU items.
To get to the picture below:
MAIN MENU > [1] UMTS MAIN MENU > [1] DEBUG SCREEN > [2] NAS INFORMATION > [1] MM INFORMATION
Which should result in:
Code:
[SIZE=2]mm: Idle
MCC-MNV: nnn-01
LAC: hhh, RAC: nn
[B]TIMER_T32[/B]: [B]10[/B](S) [B]11[/B](S) [B]12[/B](A)
[B]13[/B](S) [B]20[/B](S) [B]30[/B](S) [B]40[/B](S)
GmmState: Registered(3)
SubState: normal(0)
PmmMode: IDLE(1)
rej_cause: 0, IuAttCnt: 0
TMSI: hhhhhhh[/SIZE]
< placeholder >
As you can see, these include the values of a few important RR timers used. In the menu above they are
marked with (S) or (A), for STOPPED and ACTIVE, respectively. These timers are discussed further in
the next section.
The Mobility Management (MM) Timers: MS-side
All the MM timers are defined and thorough;y explained in [1]. But here I
summarize the timers we have found in our SM as shown above. Where we
have the following timers clearly visible:
Code:
[SIZE=2]T3210
T3211
T3212
T3213
T3220
T3230
T3240
[/SIZE]
Here's a summary table also taken and edited from [1].
The very brief 3GPP summary for T3210/11/12/13 is:
< WIP placeholder>
The very brief 3GPP summary for T3220/30/40 is:
Code:
[SIZE=2][B]T3220[/B] Timer is used during the MM states of:
- IMSI Detach Initiated
Timer is started at IMSI Detach.
Timer is stopped when: release from RM-sublayer
At expiry it: "enter Null or Idle, ATTEMPTING TO UPDATE" ??
[B]T3230[/B] Timer is used during the MM states of:
- Wait For Outgoing MM Connection
- Wait For Additional Outgoing MM Connection
- Wait TO Re-establish MM connection
Timer is started in the mobile station when:
- the MS makes a Ciphering Mode (CM) service request
- the MS makes a Ciphering Mode (CM) re-establishment request
Timer is stopped when:
- the MS makes a CM setting
- the MS receives a CM Service Reject
- the MS receives a CM Service Accept
At expiry it provides a release indicator.
[B]T3240[/B] Timer is started in the mobile station when:
- the mobile station receives a LOCATION UPDATING ACCEPT message completing a location updating procedure in the cases specified in subclauses 4.4.4.6 and 4.4.4.8;
- the mobile station receives a LOCATION UPDATING REJECT message in the cases specified in subclause 4.4.4.7;
- the mobile station has sent a CM SERVICE ABORT message as specified in subclause 4.5.1.7;
- the mobile station has released or aborted all MM connections in the cases specified in 4.3.2.5, 4.3.5.2, 4.5.1.1, and 4.5.3.1;
- the mobile station receives the paging message from network and enter the MM state 9 (WAIT FOR NETWORK COMMAND).
Timer is stopped, reset, and started again at receipt of an MM message.
Timer is stopped and reset (but not started) at receipt of a CM message that initiates establishment of an CM connection (an appropriate SETUP, REGISTER, or CP-DATA message as defined in 3GPP TS 24.008, 3GPP TS 24.010 [21] or 3GPP TS 24.011 [22]).
If timer expires, the MS shall abort the RR connection and enter the MM state MM IDLE.
[/SIZE]
References:
[1] "Mobile Radio Interface Layer 3 specification, Core Network Protocols"
3GPP TS 24.008 V12.5.0 (2014-03): (678 pages)
[2]
The Variable Vocabulary
Here is a list of variable names, and their inferred meaning, as found in the SM shown above.
Code:
[SIZE=2]
RX : Receive/Down-Link Channel aka "DL CH"
TX : Transmit/Up-Link Channel aka "UL CH"
RI : [dBm] RSSI (Receive Signal Strength Indicator)
CID : Cell ID
PSC : Primary Synchronization Code
EcIo : [1] Ec/Io = RSCP / RSSI = Eb/No - Gp
RSCP : [dBm] Received Signal Code Power [2,3] RSCP = RSSI + Ec/No
SpeechVER : The Voice Codec in use [EFR/FR/HR/AMR]
L1 : [FACH,DCH,BCH,PCH_Sleep]
Drx cycle : Discontinuous Reception (DRX) Cycle
therm : Thermal Power (
LNA : Low Noise Amplifier ???
mm: Idle : Mobile Management connection status ??
lu: Upda :
SS: Avail : Subsystem System Simulator ?? Secondary Synchronization Signal ??
RAC : Routing Area Code
TIMER_T32: 10 (S) : Really refers to the T3210 timer, and where
GmmState: Registered(3) :
SubState: normal(0) :
PmmMode: IDLE(1) :
rej_cause:0 :
luAttCnt:0 : Location Update (IMSI Attach?)/(Attempts?) Count
TMSI: 9xxxxxxd : Temporary Mobile Subscriber Identity
AS INFORMATION: : Access Stratum
VOC :
CQI : Channel-Quality Indication
Sam :
"Specific Anthropomorphic Mannequin" ??
"Service Aware Manager" (Alcatel/Lucent) ??
[/SIZE]
As you can see there are many not yet clearly defined items.
To clarify these (and others) is the main purpose of this thread!
< more crazy dragons to be >
< more crazy dragons to be >
A very nice book chapter and collection of useful baseband info and document links.
Benoit Michau, 2014
"Analyse de sécurité des modems mobiles"
[French]
Click to expand...
Click to collapse
LNA
E:V:A said:
The Variable Vocabulary
Here is a list of variable names, and their inferred meaning, as found in the SM shown above.
Code:
[SIZE=2]
LNA : Low Noise Amplifier ???
Click to expand...
Click to collapse
LNA = Line Noise Attenuator/Attenuation
oddball3 said:
LNA = Line Noise Attenuator/Attenuation
Click to expand...
Click to collapse
Thanks for your attention, but I don't think that is correct, because this is a radio device and not an ADSL-router or other "line" dependent device. You'll have to try harder to convince me. Links to a reliable source, helps.
E:V:A said:
Thanks for your attention, but I don't think that is correct, because this is a radio device and not an ADSL-router or other "line" dependent device. You'll have to try harder to convince me. Links to a reliable source, helps.
Click to expand...
Click to collapse
Not spot on, but proof of concept:
http://www.w3eee.com/Noiz .html
I had the perfect site I wanted to post here for you, and just to prove what a crappy country this is, our power utility decided to cut supply to our area :-\ I reckon I was about two sentences away from perfection haha!! Was so disappointed it's taken me since then to work up the enthusiasm to try again!!
Edit: Good Reference source - http://ieeexplore.ieee.org/xpl/logi...re.ieee.org/xpls/abs_all.jsp?arnumber=6471543
Few from me
PSC : Primary Scrambling Code (not synchronization)
L1 : RRC State [FACH,DCH,BCH,PCH_Sleep]
GmmState: Registered(3) : GPRS Mobiity Management status
PmmMode: IDLE(1) : Packet Mobiity Management status
E:V:A said:
Code:
[SIZE=2]mm: Idle
MCC-MNV: nnn-01
LAC: hhh, RAC: nn
[B]TIMER_T32[/B]: [B]10[/B](S) [B]11[/B](S) [B]12[/B](A)
[B]13[/B](S) [B]20[/B](S) [B]30[/B](S) [B]40[/B](S)
GmmState: Registered(3)
SubState: normal(0)
PmmMode: IDLE(1)
rej_cause: 0, IuAttCnt: 0
TMSI: hhhhhhh[/SIZE]
As you can see, these include the values of a few important RR timers used. In the menu above they are
marked with (S) or (A), for STOPPED and ACTIVE, respectively. These timers are discussed further in
the next section.
Click to expand...
Click to collapse
Interesting. But that way we can only know if a Timer is Stopped or Active.
How can we know the Value of these Timers?
Thanks.
vndnguyen said:
How can we know the Value of these Timers?
Click to expand...
Click to collapse
We can try to read its value from one of the SIM card EF files. I forgot which. We can also read it from the /dev/diag RF diagnostics device or possibly from the QMI (Qualcomm) debug ports. Or we can leave phone still and read the start/stop flags when they change. Or you can call the technicians of the MNO and ask.
E:V:A said:
We can try to read its value from one of the SIM card EF files. I forgot which.
Click to expand...
Click to collapse
I can read the EF files on the SIM cards. But the problem is that we don't know which EF files store those timers?
We can also read it from the /dev/diag RF diagnostics device or possibly from the QMI (Qualcomm) debug ports.
Click to expand...
Click to collapse
Can you give some detailed instruction about it? I have no idea on it.
Or we can leave phone still and read the start/stop flags when they change.
Click to expand...
Click to collapse
This is not a good way to read.
Or you can call the technicians of the MNO and ask.
Click to expand...
Click to collapse
Yes, I'm working at that MNO. But I still want to read those timers directly from the phone.
problem with gsm
hi gays.
i`ve a prblem with my phone.
in gsm(2g) don`t have signal but in 3g yes.
with this service menu... can i reparair?
please help me
hola chicos, tengo un problema: teniendo mi cel en gsm 2g no me toma señal, se queda sin servicio, pero al cambiar a 3g tengo altiro señal.
puedo con este menu repararlo y como? se agradece la ayuda
sirkuazar said:
hi gays.
i`ve a prblem with my phone.
in gsm(2g) don`t have signal but in 3g yes.
with this service menu... can i reparair?
please help me
hola chicos, tengo un problema: teniendo mi cel en gsm 2g no me toma señal, se queda sin servicio, pero al cambiar a 3g tengo altiro señal.
puedo con este menu repararlo y como? se agradece la ayuda
Click to expand...
Click to collapse
Gays? I'm not a gay LOL
You would rather check your sim card as well as the mobile service before playing around with your phone. You can put the sim card into another phone to see if it works, etc...
:laugh::laugh::laugh::laugh:
vndnguyen said:
Gays? I'm not a gay LOL
You would rather check your sim card as well as the mobile service before playing around with your phone. You can put the sim card into another phone to see if it works, etc...
Click to expand...
Click to collapse
HHHHHHHHH
How does adb daemon can be run as root on custom ROM and not on stock ROM (throws message like "not possible on production devices"). Are there any specific settings that prevent this or /sbin/adbd executable itself is different?
(
on omniROM the build.prop are set properly as not to allow root by default:
[email protected]:/ $ getprop|grep secure
[ro.adb.secure]: [1]
[ro.secure]: [1]
[sys.settings_secure_version]: [1]
)
user vs. userdebug build might be one difference
Hello All,
So I got my Axon 7 the other day. Using one of the guides from this site, I started to flash it using (Win 10 64 bit) ADB to Lineage OS. Long story short as per the title, it didn't end well. I'm no expert but I've managed to flash a couple of phones before with success. I did read up and I was careful.
Obviously the point of this post is, I've not had any luck trying to recover it and now my phone is bricked. Its got stuck in DFU mode. My pc recognises it when connected to USB (hold Vol+/Vol-, insert USB), it shows as Handset Diagnostic Interface (DFU) (Com7) in the device manager.
I've not been able to anything with it. I made up and used a deep flash cable but it didn't work.
Can anyone recommend a good phone fixer in South of England that can sort my phone and get it going again?
It's ****ed up. you have to do the semi brick trick.
Sn8K said:
It's ****ed up. you have to do the semi brick trick.
Click to expand...
Click to collapse
As in 4th category brick repair?
https://forum.xda-developers.com/showpost.php?p=70948893&postcount=28
coremania said:
First try it yourself, read the thread from controllerboy
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Shut down the phone and try to press both volume buttons while connecting the usb cable to get edl mode running. With zadig try to get the right driver working.
You should read the thread to rescue your phone, a lot of people managed to fix their phones.
Click to expand...
Click to collapse
Thanks for the reply. That very post by controllerboy was my guide. I think it was at step 20 or 21 things went awry. The method you suggest, I've tried many times and believe me I've read many of the rescue threads. Perhaps I've missed something somewhere. I've used Zadig and I have WinUsb drivers installed.
I've tried the Axon7Toolkit, QPST and Miflash software.
coremania said:
https://forum.xda-developers.com/showpost.php?p=70948893&postcount=28
Click to expand...
Click to collapse
Thanks for that. Curiously I'd read that post before, but before I got to this stage of "brickness".
I don't have my A7 with me right now, but I do remember on one of the countless connections to my pc over the weekend that I did see "? device" in response to an "adb devices" command.
That gives me hope! Thanks for your memory jogging post : )
HVMan01 said:
As in 4th category brick repair?
Click to expand...
Click to collapse
Sorry for the delay .. not often on my computer theses times ...
Yeah, was talking about that one. Or even another way, is to use warranty as I did when my A7 went down the same way as your.
To be sure, i've relocked bootloader (fastboot should always be accessible in your case by powering phone + Vol Down) and described my problem as a sudden boot failure after a failed OFFICIAL recovery update.
They've trusted me ... And changed my motherboard.
I'm not sure I could do that now. I thought I'd had a lucky break re comment about adb and the ? device message. Couldn't repeat that though. Going to have to find a good repairer to get into the hardware! Thanks for taking time to reply, much appreciated.
Update. With phone connected to pc, have managed to get it recognised and shows as "Qualcomm HS-USB QDLoader 9008" in the Device Manager. No other instances of the device appear there.
Using Adb in administrator mode, commands won't reach it. Axon7tool is the same.
But.......using the current version of Qualcomm's QFIL, it now finds the phone on port 9. At this stage I'm attempting to flash a TWRP recovery image only.
I get an error. This is the log, can anyone make sense of it?
Thanks
------------------------------------------------------------
Start Download
Program Path:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_ufs_firehose_8996_ddr_zte1.elf
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'E:\Downloads\Qualcomm_Flash_Image_Loader_v2.0.0.5(1)\Qualcomm_Flash_Image_Loader_v2.0.0.5\QSaharaServer.exe -p \\.\COM9 -s 13:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_ufs_firehose_8996_ddr_zte1.elf 'Current working dir: C:\Users\Nick\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Program Files (x86)\Qualcomm\QPST\bin\prog_ufs_firehose_8996_ddr_zte1.elf
14:19:32: Received file 'load.cmm'
14:19:32: 1372 bytes transferred in 0.000000 seconds
14:19:32: File transferred successfully
14:20:28: Received file 'DDRCS1.BIN'
14:20:28: -2147483648 bytes transferred in 55.593000 seconds (36.8392MBps)
14:20:28: File transferred successfully
14:21:23: Received file 'DDRCS0.BIN'
14:21:23: -2147483648 bytes transferred in 54.985000 seconds (37.2465MBps)
14:21:23: File transferred successfully
14:21:23: Received file 'PMSG.BIN'
14:21:23: 1048576 bytes transferred in 0.031000 seconds (32.2581MBps)
14:21:23: File transferred successfully
14:21:23: Received file 'OOPS.BIN'
14:21:23: 1048576 bytes transferred in 0.015000 seconds (66.6667MBps)
14:21:23: File transferred successfully
14:21:23: Received file 'RAMCON.BIN'
14:21:23: 1048576 bytes transferred in 0.016000 seconds (62.5000MBps)
14:21:23: File transferred successfully
14:21:23: Received file 'PIMEM.BIN'
14:21:23: 16777216 bytes transferred in 0.375000 seconds (42.6667MBps)
14:21:23: File transferred successfully
14:21:23: Received file 'DDR_DATA.BIN'
14:21:23: 4096 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'RST_STAT.BIN'
14:21:23: 4 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'PMIC_PON.BIN'
14:21:23: 8 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'IPA_MBOX.BIN'
14:21:23: 256 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'IPA_HRAM.BIN'
14:21:23: 12032 bytes transferred in 0.016000 seconds (0.7172MBps)
14:21:23: File transferred successfully
14:21:23: Received file 'IPA_SRAM.BIN'
14:21:23: 8192 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'IPA_DRAM.BIN'
14:21:23: 16128 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'IPA_IRAM.BIN'
14:21:23: 16384 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'MSGRAM.BIN'
14:21:23: 24576 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'DATARAM.BIN'
14:21:23: 81920 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'CODERAM.BIN'
14:21:24: 163840 bytes transferred in 0.000000 seconds
14:21:24: File transferred successfully
14:21:24: Received file 'OCIMEM.BIN'
14:21:24: 262144 bytes transferred in 0.016000 seconds (15.6250MBps)
14:21:24: File transferred successfully
14:21:24: Successfully downloaded files from target
14:21:24: ERROR: function: is_ack_successful:943 SAHARA_NAK_INVALID_IMAGE_TYPE
14:21:24: ERROR: function: sahara_start:825 Exiting abruptly
14:21:24: ERROR: function: sahara_main:854 Sahara protocol error
14:21:24: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
------------------------------------------------------------------------------------------------
HVMan01 said:
Update. With phone connected to pc, have managed to get it recognised and shows as "Qualcomm HS-USB QDLoader 9008" in the Device Manager. No other instances of the device appear there.
Using Adb in administrator mode, commands won't reach it. Axon7tool is the same.
But.......using the current version of Qualcomm's QFIL, it now finds the phone on port 9. At this stage I'm attempting to flash a TWRP recovery image only.
I get an error. This is the log, can anyone make sense of it?
Thanks
------------------------------------------------------------
Start Download
Program Path:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_ufs_firehose_8996_ddr_zte1.elf
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'E:\Downloads\Qualcomm_Flash_Image_Loader_v2.0.0.5(1)\Qualcomm_Flash_Image_Loader_v2.0.0.5\QSaharaServer.exe -p \.\COM9 -s 13:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_ufs_firehose_8996_ddr_zte1.elf 'Current working dir: C:\Users\Nick\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Program Files (x86)\Qualcomm\QPST\bin\prog_ufs_firehose_8996_ddr_zte1.elf
14:19:32: Received file 'load.cmm'
14:19:32: 1372 bytes transferred in 0.000000 seconds
14:19:32: File transferred successfully
14:20:28: Received file 'DDRCS1.BIN'
14:20:28: -2147483648 bytes transferred in 55.593000 seconds (36.8392MBps)
14:20:28: File transferred successfully
14:21:23: Received file 'DDRCS0.BIN'
14:21:23: -2147483648 bytes transferred in 54.985000 seconds (37.2465MBps)
14:21:23: File transferred successfully
14:21:23: Received file 'PMSG.BIN'
14:21:23: 1048576 bytes transferred in 0.031000 seconds (32.2581MBps)
14:21:23: File transferred successfully
14:21:23: Received file 'OOPS.BIN'
14:21:23: 1048576 bytes transferred in 0.015000 seconds (66.6667MBps)
14:21:23: File transferred successfully
14:21:23: Received file 'RAMCON.BIN'
14:21:23: 1048576 bytes transferred in 0.016000 seconds (62.5000MBps)
14:21:23: File transferred successfully
14:21:23: Received file 'PIMEM.BIN'
14:21:23: 16777216 bytes transferred in 0.375000 seconds (42.6667MBps)
14:21:23: File transferred successfully
14:21:23: Received file 'DDR_DATA.BIN'
14:21:23: 4096 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'RST_STAT.BIN'
14:21:23: 4 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'PMIC_PON.BIN'
14:21:23: 8 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'IPA_MBOX.BIN'
14:21:23: 256 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'IPA_HRAM.BIN'
14:21:23: 12032 bytes transferred in 0.016000 seconds (0.7172MBps)
14:21:23: File transferred successfully
14:21:23: Received file 'IPA_SRAM.BIN'
14:21:23: 8192 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'IPA_DRAM.BIN'
14:21:23: 16128 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'IPA_IRAM.BIN'
14:21:23: 16384 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'MSGRAM.BIN'
14:21:23: 24576 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'DATARAM.BIN'
14:21:23: 81920 bytes transferred in 0.000000 seconds
14:21:23: File transferred successfully
14:21:23: Received file 'CODERAM.BIN'
14:21:24: 163840 bytes transferred in 0.000000 seconds
14:21:24: File transferred successfully
14:21:24: Received file 'OCIMEM.BIN'
14:21:24: 262144 bytes transferred in 0.016000 seconds (15.6250MBps)
14:21:24: File transferred successfully
14:21:24: Successfully downloaded files from target
14:21:24: ERROR: function: is_ack_successful:943 SAHARA_NAK_INVALID_IMAGE_TYPE
14:21:24: ERROR: function: sahara_start:825 Exiting abruptly
14:21:24: ERROR: function: sahara_main:854 Sahara protocol error
14:21:24: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Wich TWRP version do u flash when u get this error?
TWRP_3.1.1-1_Axon7.img
I myself could never get win 10 to flash or detect my axon had to install win7 to properly flash it.
HVMan01 said:
TWRP_3.1.1-1_Axon7.img
Click to expand...
Click to collapse
Look in this XDA forum for axon7 in the gudies thread for a post that is named download center.
In there u have a different TWRP file. Try to flash that file instead.
Have you tried booting to FTM mode by long pressing vol down + power when the device is powered off. If you can, then you can have adb access. On cmd it will come up as "? devices" when you try adb devices.
In reply #13, yes I've tried other Axon7 TWRP files. Using Qualcomm's QFIL, all ends up with error log stating
----------------------------------------------------------
14:21:24: ERROR: function: is_ack_successful:943 SAHARA_NAK_INVALID_IMAGE_TYPE
14:21:24: ERROR: function: sahara_start:825 Exiting abruptly
14:21:24: ERROR: function: sahara_main:854 Sahara protocol error
14:21:24: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
---------------------------
So not sure what's up (yet). Obviously the .xml files need a tweek.
At reply #14. I cannot get ADB access now no matter what key combination I press, and I've tried, oh how I've tried : (
Hi, have you finished your problem ?
Unfortunately not. I need to fix the errors shown in the log above @ #15.
Possibly someone knows? As I said before, I cannot access the phone via the ADB command set or fastboot for that matter.
A bit late, but I guess u tried to bring your phone to edl mode. And changing the drivers via zadig.
I mean shut down phone, press both volume buttons while connecting to USB. If it's blank, you just have to manage zadig to use the right driver and start from scratch.
coremania said:
A bit late, but I guess u tried to bring your phone to edl mode. And changing the drivers via zadig.
I mean shut down phone, press both volume buttons while connecting to USB. If it's blank, you just have to manage zadig to use the right driver and start from scratch.
Click to expand...
Click to collapse
Ok so phone is off, as in no red light on. Both vol buttons pressed, connected to USB.
Device recognised sound, shows as Qualcomm HSUSB QDLoader 9008 com4.
Minimal ADB and Fastboot running in administrator mode, entered ADB devices, none found. Tried ADB reboot, got error no devices/emulators found.
Started QFIL, can't run meta build with .mbn as no mbn files in anything I have to flash phone with. Can do a flat build but this just fails with the same errors as in #15.
Have looked at supposed "fixed" sahara/QFIL fail problem vids on YouTube. No answers found there.
So just stuck right now.
https://forum-lw-1.xda-cdn.com/images/smilies/frown.gif
HVMan01 said:
Ok so phone is off, as in no red light on. Both vol buttons pressed, connected to USB.
Device recognised sound, shows as Qualcomm HSUSB QDLoader 9008 com4.
Minimal ADB and Fastboot running in administrator mode, entered ADB devices, none found. Tried ADB reboot, got error no devices/emulators found.
Started QFIL, can't run meta build with .mbn as no mbn files in anything I have to flash phone with. Can do a flat build but this just fails with the same errors as in #15.
Have looked at supposed "fixed" sahara/QFIL fail problem vids on YouTube. No answers found there.
So just stuck right now.
https://forum-lw-1.xda-cdn.com/images/smilies/frown.gif
Click to expand...
Click to collapse
Hey could you clarify some things?
Why are you trying adb on EDL mode? (it only works on FTM, anyways)
Can't you just use MiFlash? After all this, I guess you should've already thought about the 4th category brick repair method. I did it, it worked. just sayin.
Okay, so once again I am diving head-first into finding a factory replacement radio for 2015+ Mustangs, and after spending a few months talking with a manufacturer in China, I was able to get a Test unit. What I'm trying to find out is, since they sent me a pile of software (what they claim is everything they have on the unit) is there anyone who might be able to help me figure out a method to gain ROOT access?
All I know about it is that it's based on the MediaTek MT3561 with 2GB RAM, 32GB ROM. I have the entire image used to install the software on the device (at least I think I do.)
If someone is interested in assisting me with it long-term after ROOT, to eliminate "Engrish," misspellings, and updating some images, I would definitely compensate them for it!
Here's a link to the software I have:
https://drive.google.com/file/d/1LGMAm2IcDlbEa3sW-w3aK5GIN8rutPqQ/view?usp=drivesdk
I'm surprised that nobody is interested in a bounty...?
Bump!
Okay, so I tried some of the methods I've found on the forum to no avail, and decided to adb over WiFi into my unit, and list the contents of /system/bin/ I don't know if this is even useful information, but I'm REALLY looking for some kind of help.
View attachment 4418899
cool
Can anyone at least tell me what information I need to get from this device physically, or the build.prop (or whatever) to work on taking steps to gain ROOT?
PatrickHenninger said:
Can anyone at least tell me what information I need to get from this device physically, or the build.prop (or whatever) to work on taking steps to gain ROOT?
Click to expand...
Click to collapse
A long shot possibility here. It might be worthwhile to look at techniques used by people to root similar devices to your radio running the same version of Android. For example, the Ownice C500 head unit. It appears that unit uses the same MediaTek CPU as yours. Also perhaps do a little searching for other brand name head units using that CPU and see if/how those units can be rooted. You may be able to find the answer that you need.
Good luck finding root for your unit.
PoppaRoxie1986 said:
A long shot possibility here. It might be worthwhile to look at techniques used by people to root similar devices to your radio running the same version of Android. For example, the Ownice C500 head unit. It appears that unit uses the same MediaTek CPU as yours. Also perhaps do a little searching for other brand name head units using that CPU and see if/how those units can be rooted. You may be able to find the answer that you need.
Good luck finding root for your unit.
Click to expand...
Click to collapse
Hey, I appreciate the reply- I've actually already done that as far as I know how. The only method I've seen so far involves using a command in the terminal involving "Forfan guoboneedav -" and another running "[email protected]" but neither of those work. I don't know if forfan is a file name/command or what, but it gives me the error "forfan not found" or something like that.
PatrickHenninger said:
Hey, I appreciate the reply- I've actually already done that as far as I know how. The only method I've seen so far involves using a command in the terminal involving "Forfan guoboneedav -" and another running "[email protected]" but neither of those work. I don't know if forfan is a file name/command or what, but it gives me the error "forfan not found" or something like that.
Click to expand...
Click to collapse
My pleasure. My first guess would be that forfan is a script/executable found in the system folder on the Ownice units maybe not on yours perhaps. Not sure what it does or supposed to do, but the rest of their method seems reasonable enough.
Did you by chance get that arm64.zip, extract the contents to sd card, and try the rest of that method involving terminal past the forfan line? I have an Intel Sofia based head unit which is different from yours but I am familiar enough with the command prompt/shell scripts to try to help.
PoppaRoxie1986 said:
My pleasure. My first guess would be that forfan is a script/executable found in the system folder on the Ownice units maybe not on yours perhaps. Not sure what it does or supposed to do, but the rest of their method seems reasonable enough.
Did you by chance get that arm64.zip, extract the contents to sd card, and try the rest of that method involving terminal past the forfan line? I have an Intel Sofia based head unit which is different from yours but I am familiar enough with the command prompt/shell scripts to try to help.
Click to expand...
Click to collapse
Yeah, I did try that to no avail, I get permission denied as soon as I try to run the mount command. If I could connect to the stupid thing with USB, I'd use my laptop, or bring it in the house and power it up on my counter to use fastboot or something.
If any of this stuff helps, here's the build.prop and some pictures I took during installing an update via USB, and the screen when I gave the terminal command to reboot recovery.
{
"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"
}
127|[email protected]_66_m0:/ $ getprop
[af.rf_info]: [273]
[anim.allapps]: [0]
[anim.workspace]: [0]
[bgw.current3gband]: [0]
[bluetooth.fw.adv.num]: [40]
[bluetooth.fw.energyreport]: [true]
[bluetooth.fw.irk.num]: [40]
[bluetooth.fw.rpa]: [true]
[bluetooth.fw.scanfilter.num]: [40]
[bluetooth.fw.scanresult.size]: [8160]
[camera.disable_zsl_mode]: [1]
[cdma.operator.ltmoffset]: [-20]
[cdma.operator.sid]: [1541]
[cdma.ril.eboot]: [0]
[cdma.simswitch.offmd3]: [0]
[cdma.version.baseband]: [SIXTH.CBP.MD.MP2.V47_P3, 2017/03/06 17:11]
[curlockscreen]: [0]
[cycle.allapps]: [false]
[cycle.workspace]: [false]
[dalvik.vm.dex2oat-Xms]: [4m]
[dalvik.vm.dex2oat-Xmx]: [512m]
[dalvik.vm.dex2oat-swap]: [false]
[dalvik.vm.heapgrowthlimit]: [192m]
[dalvik.vm.heapmaxfree]: [8m]
[dalvik.vm.heapminfree]: [512k]
[dalvik.vm.heapsize]: [512m]
[dalvik.vm.heapstartsize]: [16m]
[dalvik.vm.heaptargetutilization]: [0.75]
[dalvik.vm.image-dex2oat-Xms]: [64m]
[dalvik.vm.image-dex2oat-Xmx]: [64m]
[dalvik.vm.isa.arm.features]: [default]
[dalvik.vm.isa.arm.variant]: [cortex-a53]
[dalvik.vm.isa.arm64.features]: [default]
[dalvik.vm.isa.arm64.variant]: [cortex-a53]
[dalvik.vm.lockprof.threshold]: [500]
[dalvik.vm.mtk-stack-trace-file]: [/data/anr/mtk_traces.txt]
[dalvik.vm.stack-trace-file]: [/data/anr/traces.txt]
[debug.MB.running]: [0]
[debug.atrace.tags.enableflags]: [0]
[debug.force_rtl]: [0]
[debug.hwc.bq_count]: [4]
[debug.hwc.compose_level]: [0]
[debug.hwc.dump_level]: [0]
[debug.hwui.render_dirty_regions]: [false]
[debug.md_monitor.ModemSuffix]: [1_lwg_n]
[debug.mdlogger.Running]: [0]
[debug.mdlogger.log2sd.path]: [internal_sd]
[debug.mtk.aee.db]: [4:/data/aee_exp/db.fatal.03.JE <http://db.fatal.03.JE> ]
[debug.mtklog.netlog.Running]: [0]
[debug.program_binary.enable]: [1]
[dev.bootcomplete]: [1]
[dhcp.ipv6.wlan0.dns1]: []
[dhcp.ipv6.wlan0.dns2]: []
[dhcp.ipv6.wlan0.ipaddress]: []
[dhcp.ipv6.wlan0.leasetime]: []
[dhcp.ipv6.wlan0.result]: []
[dhcp.wlan0.result]: [failed]
[drm.service.enabled]: [true]
[fmradio.driver.enable]: [1]
[gps.clock.type]: [20]
[gps.gps.version]: [0x3561]
[gsm.baseband.capability]: [503]
[gsm.current.phone-type]: [2,,,,,,,,,,1]
[gsm.gcf.testmode]: [0]
[gsm.network.type]: [1xRTT]
[gsm.nitz.time]: [1518610430487]
[gsm.operator.alpha]: []
[gsm.operator.idpstring]: [011]
[gsm.operator.iso-country]: [us]
[gsm.operator.isroaming]: [false]
[gsm.operator.numeric]: [31003]
[gsm.project.baseband]: [ATC6737M_65_M0_HW(LWG_DSDS)]
[gsm.project.baseband.2]: [ATC6737M_65_M0_HW(LWG_DSDS)]
[gsm.ril.cardtypeset]: [1]
[gsm.ril.cardtypeset.2]: []
[gsm.ril.ct3g]: [0]
[gsm.ril.ct3g.2]: [0]
[gsm.ril.eboot]: [-1]
[gsm.ril.fulluicctype]: []
[gsm.ril.fulluicctype.2]: []
[gsm.ril.init]: [0]
[gsm.ril.uicctype]: []
[gsm.ril.uicctype.2]: []
[gsm.serial]: [06C18V03000180100012 10P]
[gsm.sim.operator.alpha]: []
[gsm.sim.operator.iso-country]: []
[gsm.sim.operator.numeric]: []
[gsm.sim.retry.pin1]: [-1]
[gsm.sim.retry.pin1.2]: []
[gsm.sim.retry.pin2]: [-1]
[gsm.sim.retry.pin2.2]: []
[gsm.sim.retry.puk1]: [-1]
[gsm.sim.retry.puk1.2]: []
[gsm.sim.retry.puk2]: [-1]
[gsm.sim.retry.puk2.2]: []
[gsm.sim.ril.mcc.mnc]: []
[gsm.sim.ril.mcc.mnc.2]: []
[gsm.sim.ril.phbready]: []
[gsm.sim.ril.phbready.2]: []
[gsm.sim.state]: [ABSENT]
[gsm.simswitch.offmd1]: [0]
[gsm.version.baseband]: [MOLY.LR9.W1444.MD.LWTG.MP.V94.P6, 2017/09/06 21:43]
[gsm.version.ril-impl]: [Viatelecom-cdma-ril suffix Version-temp]
[init.svc.MtkCodecService]: [running]
[init.svc.NvRAMAgent]: [running]
[init.svc.PPLAgent]: [running]
[init.svc.adbd]: [running]
[init.svc.adbec]: [running]
[init.svc.adbusbmuxd]: [running]
[init.svc.agpsd]: [running]
[init.svc.atc_ipod_core]: [running]
[init.svc.auto_recovery]: [stopped]
[init.svc.baidu_carlife]: [stopped]
[init.svc.bootanim]: [stopped]
[init.svc.bootlogoupdater]: [stopped]
[init.svc.ccci_fsd]: [running]
[init.svc.ccci_mdinit]: [running]
[init.svc.cmddumper]: [running]
[init.svc.conn_launcher]: [running]
[init.svc.console]: [running]
[init.svc.debuggerd]: [running]
[init.svc.debuggerd64]: [running]
[init.svc.dhcpcd_wlan0]: [stopped]
[init.svc.didisrv]: [stopped]
[init.svc.drm]: [running]
[init.svc.emdlogger1]: [running]
[init.svc.emsvr_user]: [running]
[init.svc.enableswap]: [stopped]
[init.svc.flash_recovery]: [stopped]
[init.svc.gas_srv]: [running]
[init.svc.gatekeeperd]: [running]
[init.svc.ged_srv]: [running]
[init.svc.gsm0710muxd]: [running]
[init.svc.guiext-server]: [running]
[init.svc.healthd]: [running]
[init.svc.installd]: [running]
[init.svc.key_learn]: [stopped]
[init.svc.keystore]: [running]
[init.svc.lmkd]: [running]
[init.svc.logd]: [running]
[init.svc.logd-reinit]: [stopped]
[init.svc.mcu-daemon]: [running]
[init.svc.md_monitor]: [running]
[init.svc.media]: [running]
[init.svc.mnld]: [running]
[init.svc.mobile_log_d]: [running]
[init.svc.netd]: [running]
[init.svc.netdiag]: [running]
[init.svc.nvram_daemon]: [stopped]
[init.svc.p2p_supplicant]: [running]
[init.svc.perfprofd]: [running]
[init.svc.pq]: [running]
[init.svc.program_binary]: [running]
[init.svc.ril-daemon]: [stopped]
[init.svc.ril-daemon-mtk]: [running]
[init.svc.servicemanager]: [running]
[init.svc.slpd]: [running]
[init.svc.sn <http://init.svc.sn> ]: [running]
[init.svc.statusd]: [running]
[init.svc.stp_dump]: [running]
[init.svc.surfaceflinger]: [running]
[init.svc.terservice]: [stopped]
[init.svc.thermal]: [running]
[init.svc.thermal_manager]: [stopped]
[init.svc.thermald]: [running]
[init.svc.ueventd]: [running]
[init.svc.vold]: [running]
[init.svc.vtservice]: [running]
[init.svc.wifi2agps]: [running]
[init.svc.wmtLoader]: [stopped]
[init.svc.xlogboot]: [stopped]
[init.svc.xlogdebugchanged]: [stopped]
[init.svc.zygote]: [running]
[init.svc.zygote_secondary]: [running]
[media.wfd.portrait]: [0]
[media.wfd.video-format]: [5]
[mediatek.wlan.chip]: [CONSYS_MT3561]
[mediatek.wlan.ctia]: [0]
[mediatek.wlan.module.postfix]: [_consys_mt3561]
[mtk.md1.starttime]: [1s Wed Feb 14 12:13:02 2018 ]
[mtk.md1.status]: [ready]
[mtk.md3.status]: [ready]
[mtk.vdec.waitkeyframeforplay]: [1]
[mtk_wifi.fwpath]: [STA]
[net.bt.name <http://net.bt.name> ]: [Android]
[net.cdma.boottimes]: [1]
[net.cdma.mdmstat]: [ready]
[net.cdma.poker]: [red.joker]
[net.cdma.via.card.state]: [locked_or_absent]
[net.cdma.via.service.state]: [in service]
[net.change]: [net.dns1]
[net.dns1]: [192.168.0.1]
[net.hostname]: [android-475de8eb01454016]
[net.nsiot_pending]: [false]
[net.qtaguid_enabled]: [1]
[net.tcp.default_init_rwnd]: [60]
[persist.af.hac_on]: [0]
[persist.atc.bt.inbandringtone]: [disable]
[persist.current.usb.mode]: [host2_0]
[persist.current.usb.protocol]: [usb2_0]
[persist.gemini.sim_num]: [1]
[persist.log.tag]: [D]
[persist.logd.enabled]: [1]
[persist.mediascanner.thread.no <http://persist.mediascanner.thread.no> ]: [1]
[persist.meta.dumpdata]: [0]
[persist.mtk.aee.dal]: [0]
[persist.mtk.sf.fps.upper_bound]: [60]
[persist.mtk.volte.enable]: [1]
[persist.mtk.wcn.combo.chipid]: [0x0321]
[persist.radio.actual.svlte_slot]: [3]
[persist.radio.cfu.change.0]: [0]
[persist.radio.cfu.iccid.0]: [8901260751781527894f]
[persist.radio.cfu.timeslot.0]: []
[persist.radio.default.sim]: [0]
[persist.radio.fd.counter]: [15]
[persist.radio.fd.off.counter]: [5]
[persist.radio.fd.off.r8.counter]: [5]
[persist.radio.fd.r8.counter]: [15]
[persist.radio.flashless.fsm]: [0]
[persist.radio.flashless.fsm_cst]: [1]
[persist.radio.flashless.fsm_rw]: [1]
[persist.radio.gprs.prefer]: [1]
[persist.radio.ia]: []
[persist.radio.ia-apn]: []
[persist.radio.ia-pwd-flag]: [0]
[persist.radio.mobile.data]: [8901260751781527894f,0]
[persist.radio.multisim.config]: [ss]
[persist.radio.new.sim.slot]: []
[persist.radio.reset_on_switch]: [true]
[persist.radio.sim.status]: []
[persist.radio.simswitch]: [1]
[persist.radio.simswitch.iccid]: [8901260751781527894f]
[persist.radio.svlte.mode]: [svlte]
[persist.radio.svlte_slot]: [3]
[persist.radio.terminal-based.cw]: [disabled_tbcw]
[persist.radio.unlock]: [false]
[persist.radio.ut.cfu.mode]: [disabled_ut_cfu_mode]
[persist.ril.bip.disabled]: [0]
[persist.service.acm.enable]: [0]
[persist.service.bdroid.bdaddr]: [22:22:6f:2d:d4:4b]
[persist.sys.bootanimation]: [0]
[persist.sys.can.version]: [SF02V1.44.011BYPT6]
[persist.sys.dalvik.vm.lib.2]: [libart.so]
[persist.sys.debug.multi_window]: [false]
[persist.sys.door.not.hide]: [1]
[persist.sys.first_time_boot]: [false]
[persist.sys.handbrake.reverse]: [1]
[persist.sys.led.settings]: [0]
[persist.sys.mobilenet]: [easyconn]
[persist.sys.music.type]: [local_music]
[persist.sys.mute.state]: [2]
[persist.sys.navi.state]: [stopped]
[persist.sys.override]: [true]
[persist.sys.pq.adl.idx]: [0]
[persist.sys.pq.brightidx]: [2]
[persist.sys.pq.contrastidx]: [3]
[persist.sys.pq.gsatidx]: [9]
[persist.sys.pq.shp.idx]: [4]
[persist.sys.profiler_ms]: [0]
[persist.sys.radio.type]: [local_radio]
[persist.sys.reverse]: [normal]
[persist.sys.sd.defaultpath]: [/storage/emulated/0]
[persist.sys.timezone]: [America/New_York]
[persist.sys.usb.activation]: [yes]
[persist.sys.usb.config]: [mass_storage,adb]
[persist.sys.video.channel]: [3]
[qemu.hw.mainkeys]: [1]
[ril.active.md <http://ril.active.md> ]: [5]
[ril.cardtype.cache]: [255]
[ril.cdma.emdstatus.send]: [1]
[ril.cdma.report]: [0]
[ril.cdma.report.case]: [0]
[ril.cdma.switching]: [0]
[ril.current.share_modem]: [1]
[ril.data.allow]: [0]
[ril.ecc.service.category.list]: []
[ril.ecclist]: []
[ril.ecclist1]: []
[ril.external.md <http://ril.external.md> ]: [1]
[ril.fd.mode]: [1]
[ril.first.md <http://ril.first.md> ]: [1]
[ril.flightmode.poweroffMD]: [1]
[ril.ia.iccid]: []
[ril.iccid.sim1]: [N/A]
[ril.iccid.sim1_c2k]: [N/A]
[ril.iccid.sim2]: [N/A]
[ril.imsi.status.sim1]: [0]
[ril.ipo.radiooff]: [0]
[ril.ipo.radiooff.2]: [0]
[ril.mux.ee.md1]: [0]
[ril.mux.report.case]: [0]
[ril.pid.1]: [799]
[ril.radio.ia]: []
[ril.radio.ia-apn]: []
[ril.radiooff.poweroffMD]: [0]
[ril.read.imsi]: [1]
[ril.ready.sim]: [false]
[ril.specific.sm_cause]: [0]
[ril.switch.modem.cause.type]: [255]
[ril.switch.modem.delay.info <http://ril.switch.modem.delay.info> ]: ["FFFFFF",255,0]
[ril.telephony.mode]: [0]
[rild.libargs]: [-d /dev/ttyC0]
[rild.libpath]: [mtk-ril.so]
[rild.mark_switchuser]: [0]
[ro.adb.secure]: [0]
[ro.aee.build.info <http://ro.aee.build.info> ]: [mtk]
[ro.allow.mock.location]: [0]
[ro.audio.silent]: [0]
[ro.aux.disabled]: [com.clw.aux]
[ro.avin.disabled]: [com.clw.avin]
[ro.baseband]: [unknown]
[ro.board.platform]: [mt3561t]
[ro.boot.bootreason]: [wdt_by_pass_pwk]
[ro.boot.hardware]: [mt3561]
[ro.boot.mode]: [normal]
[ro.boot.name <http://ro.boot.name> ]: [android]
[ro.boot.serialno]: [59Z58TCIBQINSCSW]
[ro.bootimage.build.date]: [Wed Jan 10 01:28:58 CST 2018]
[ro.bootimage.build.date.utc]: [1515518938]
[ro.bootimage.build.fingerprint]: [alps/evb3561t_66_m0:6.0/MRA58K/V1.00.00-20180110:userdebug/test-keys]
[ro.bootloader]: [unknown]
[ro.bootmode]: [normal]
[ro.build.characteristics]: [default]
[ro.build.date]: [Wed Jan 10 01:15:59 CST 2018]
[ro.build.date.utc]: [1515518159]
[ro.build.description]: [full_evb3561t_66_m0-userdebug 6.0 MRA58K V1.00.00-20180110 test-keys] [ro.build.display.id <http://ro.build.display.id> ]: [full_evb3561t_66_m0-userdebug 6.0 MRA58K V1.00.00-20180110 test-keys]
[ro.build.fingerprint]: [alps/evb3561t_66_m0:6.0/MRA58K/V1.00.00-20180110:userdebug/test-keys]
[ro.build.flavor]: [full_evb3561t_66_m0-userdebug]
[ro.build.host]: [ubuntu-server]
[ro.build.id <http://ro.build.id> ]: [MRA58K]
[ro.build.product]: [evb3561t_66_m0]
[ro.build.product.id <http://ro.build.product.id> ]: [10]
[ro.build.tags]: [test-keys]
[ro.build.type]: [userdebug]
[ro.build.user]: [imotor]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [V1.00.00-20180110]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.release]: [7.1.2]
[ro.build.version.sdk]: [23]
[ro.build.version.security_patch]: [2016-06-01]
[ro.c2k.irat.support]: [1]
[ro.calculator.disabled]: [com.android.calculator2]
[ro.camera.sound.forced]: [0]
[ro.carrier]: [unknown]
[ro.cdma.cfall.disable]: [*730]
[ro.cdma.cfb.disable]: [*900]
[ro.cdma.cfb.enable]: [*90]
[ro.cdma.cfdf.disable]: [*680]
[ro.cdma.cfdf.enable]: [*68]
[ro.cdma.cfnr.disable]: [*920]
[ro.cdma.cfnr.enable]: [*92]
[ro.cdma.cfu.disable]: [*720]
[ro.cdma.cfu.enable]: [*72]
[ro.cdma.cw.disable]: [*740]
[ro.cdma.cw.enable]: [*74]
[ro.com.android.mobiledata]: [true]
[ro.config.alarm_alert]: [Alarm_Classic.ogg]
[ro.config.notification_sound]: [pixiedust.ogg]
[ro.config.ringtone]: [Ring_Synth_04.ogg]
[ro.config.time_12_24]: [12]
[ro.config.version]: [InteNavi-F_002_180110_V3.1.033-180110-14:27]
[ro.config.wallpaper]: [/bootlogo/config/wallpaper]
[ro.crypto.state]: [unencrypted]
[ro.dalvik.vm.native.bridge]: [0]
[ro.debuggable]: [1]
[ro.default.bootlogo]: [general]
[ro.dialer.disabled]: [com.android.dialer]
[ro.dvb.disabled]: [com.imotor.dvb]
[ro.dvr.type]: [ir]
[ro.email.disabled]: [com.android.email]
[ro.expect.recovery_id]: [0x439d02fc2a478a35a3cddd82069ded6e6e5bff5b000000000000000000000000]
[ro.frp.pst]: [/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/frp]
[ro.gemini.smart_sim_switch]: [false]
[ro.hardware]: [mt3561]
[ro.have_aacencode_feature]: [1]
[ro.have_aee_feature]: [1]
[ro.imdvr.disabled]: [com.imotor.camera]
[ro.kernel.zio]: [38,108,105,16]
[ro.manual.disabled]: [com.imotor.help]
[ro.mediatek.chip_ver]: [S01]
[ro.mediatek.gemini_support]: [false]
[ro.mediatek.platform]: [MT3561T]
[ro.mediatek.project.path]: [device/atc/evb3561t_66_m0]
[ro.mediatek.version.branch]: [alps-mp-m0.mp1]
[ro.mediatek.version.release]: [android-trunk-m0-V0.0.2]
[ro.mediatek.version.sdk]: [4]
[ro.mediatek.wlan.p2p]: [1]
[ro.mediatek.wlan.wsc]: [1]
[ro.mount.fs]: [EXT4]
[ro.mtk.c2k.slot2.support]: [1]
[ro.mtk_agps_app]: [1]
[ro.mtk_antibricking_level]: [2]
[ro.mtk_audenh_support]: [1]
[ro.mtk_audio_ape_support]: [1]
[ro.mtk_audio_change_support]: [1]
[ro.mtk_audio_tuning_tool_ver]: [V1]
[ro.mtk_besloudness_support]: [1]
[ro.mtk_bessurround_support]: [1]
[ro.mtk_bg_power_saving_support]: [1]
[ro.mtk_bg_power_saving_ui]: [1]
[ro.mtk_bip_scws]: [1]
[ro.mtk_bt_support]: [1]
[ro.mtk_c2k_support]: [1]
[ro.mtk_cam_lomo_support]: [1]
[ro.mtk_cam_mfb_support]: [3]
[ro.mtk_cam_vfb]: [1]
[ro.mtk_cta_drm_support]: [1]
[ro.mtk_cta_set]: [1]
[ro.mtk_default_data_off]: [1]
[ro.mtk_dhcpv6c_wifi]: [1]
[ro.mtk_dialer_search_support]: [1]
[ro.mtk_dual_mic_support]: [1]
[ro.mtk_eap_sim_aka]: [1]
[ro.mtk_emmc_support]: [1]
[ro.mtk_enable_md1]: [1]
[ro.mtk_enable_md3]: [1]
[ro.mtk_external_sim_support]: [1]
[ro.mtk_fd_support]: [1]
[ro.mtk_flight_mode_power_off_md]: [1]
[ro.mtk_flv_playback_support]: [1]
[ro.mtk_fm_recording_support]: [1]
[ro.mtk_gps_support]: [1]
[ro.mtk_ipo_support]: [1]
[ro.mtk_is_tablet]: [0]
[ro.mtk_lte_support]: [1]
[ro.mtk_md_sbp_custom_value]: [1]
[ro.mtk_md_world_mode_support]: [0]
[ro.mtk_miravision_image_dc]: [1]
[ro.mtk_miravision_support]: [1]
[ro.mtk_mobile_management]: [1]
[ro.mtk_modem_monitor_support]: [1]
[ro.mtk_perf_response_time]: [1]
[ro.mtk_perf_simple_start_win]: [1]
[ro.mtk_perfservice_support]: [1]
[ro.mtk_pq_support]: [2]
[ro.mtk_privacy_protection_lock]: [1]
[ro.mtk_rild_read_imsi]: [1]
[ro.mtk_search_db_support]: [1]
[ro.mtk_send_rr_support]: [1]
[ro.mtk_shared_sdcard]: [1]
[ro.mtk_sim_hot_swap]: [1]
[ro.mtk_slow_motion_support]: [1]
[ro.mtk_subtitle_support]: [1]
[ro.mtk_svlte_support]: [1]
[ro.mtk_tetheringipv6_support]: [1]
[ro.mtk_thumbnail_play_support]: [1]
[ro.mtk_umts_tdd128_mode]: [1]
[ro.mtk_usb_cba_support]: [1]
[ro.mtk_volte_support]: [1]
[ro.mtk_wappush_support]: [1]
[ro.mtk_wfd_sink_support]: [1]
[ro.mtk_wfd_sink_uibc_support]: [1]
[ro.mtk_wfd_support]: [1]
[ro.mtk_widevine_drm_l3_support]: [1]
[ro.mtk_wifi_mcc_support]: [1]
[ro.mtk_wlan_support]: [1]
[ro.mtk_wmv_playback_support]: [1]
[ro.mtk_world_phone]: [1]
[ro.mtk_world_phone_policy]: [0]
[ro.opengles.version]: [196608]
[ro.otaupdate.disabled]: [com.imotor.upgrade]
[ro.personal.disabled]: [com.imotor.personal]
[ro.product.board]: []
[ro.product.brand]: [alps]
[ro.product.cpu.abi]: [arm64-v8a]
[ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: [arm64-v8a]
[ro.product.device]: [evb3561t_66_m0]
[ro.product.locale]: [zh-CN]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [alps]
[ro.product.model]: [MT3561]
[ro.product.name <http://ro.product.name> ]: [full_evb3561t_66_m0]
[ro.rcc.disabled]: [com.imotor.rcctransfer]
[ro.recognition.disabled]: [com.clw.recognition]
[ro.recovery_id]: [0x439d02fc2a478a35a3cddd82069ded6e6e5bff5b000000000000000000000000]
[ro.revision]: [0]
[ro.runtime.firstboot]: [1518628404619]
[ro.secure]: [1]
[ro.serialdemo.disabled]: [com.clw.serial]
[ro.serialno]: [59Z58TCIBQINSCSW]
[ro.sf.hwrotation]: [0]
[ro.sf.lcd_density]: [240]
[ro.sim_me_lock_mode]: [0]
[ro.sim_refresh_reset_by_modem]: [1]
[ro.software.ui]: [UIA101]
[ro.steeringwheel.disabled]: [com.android.steerwheel]
[ro.sys.usb.bicr]: [yes]
[ro.sys.usb.charging.only]: [yes]
[ro.sys.usb.mtp.whql.enable]: [0]
[ro.sys.usb.storage.type]: [mtp]
[ro.telephony.default_network]: [4]
[ro.telephony.sim.count]: [2]
[ro.tpms.disabled]: [com.imotor.tpms.main]
[ro.tv.type]: [2]
[ro.update.disabled]: [com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$Receiver]
[ro.weather.disabled]: [com.autochips.weather]
[ro.wifi.channels]: []
[ro.wlan.mtk.wifi.5g]: [1]
[ro.zygote]: [zygote64_32]
[ro.zygote.preload.enable]: [0]
[security.perf_harden]: [1]
[selinux.reload_policy]: [1]
[service.adbec.enable]: [1]
[service.adbusbmuxd.enable]: [1]
[service.bootanim.exit]: [1]
[service.nvram_init]: [Ready]
[service.wcn.coredump.mode]: [2]
[service.wcn.driver.ready]: [yes]
[sys.boot.reason]: [0]
[sys.boot_completed]: [1]
[sys.ipo.autotest]: [1]
[sys.ipo.pwrdncap]: [2]
[sys.ipowin.done]: [1]
[sys.oem_unlock_allowed]: [1]
[sys.settings_system_version]: [4]
[sys.sysctl.extra_free_kbytes]: [7200]
[sys.sysctl.tcp_def_init_rwnd]: [60]
[sys.usb.config]: [mass_storage,adb]
[sys.usb.ffs.ready]: [1]
[sys.usb.state]: [mass_storage,adb]
[sys.usb.vid]: [0E8D]
[viatel.device.asci]: [uart.4.ttyMT]
[viatel.device.at <http://viatel.device.at> ]: [sdio.4.ttySDIO]
[viatel.device.at2]: [sdio.6.ttySDIO]
[viatel.device.at3]: [sdio.7.ttySDIO]
[viatel.device.data]: [sdio.1.ttySDIO]
[viatel.device.ets]: [sdio.2.ttySDIO]
[viatel.device.excp.data]: [sdio.12.ttySDIO]
[viatel.device.excp.msg]: [sdio.11.ttySDIO]
[viatel.device.fls]: [sdio.3.ttySDIO]
[viatel.device.gps]: [sdio.5.ttySDIO]
[viatel.device.pcv]: [sdio.0.ttySDIO]
[vold.has_adoptable]: [1]
[vold.path.internal_storage]: [/storage/emulated/0]
[vold.post_fs_data_done]: [1]
[vold.support_external_sd]: [1]
[wfd.dummy.enable]: [1]
[wifi.direct.interface]: [p2p0]
[wifi.interface]: [wlan0]
[wifi.tethering.interface]: [ap0]
[wlan.driver.status]: [ok]
[wlan.wfd.security.image]: [1]
[email protected]_66_m0:/ $
Bump, I'm relentless!
Okay, I made some potential progress last night. I used the update files I got from the manufacturer and Magisk to patch the Boot.IMG file. I tried to put that patched BOOT.IMG into the update.zip and use the auro-recovery feature of the Head Unit to load it, and it fails the signature verification. That tells me I need to unlock the bootloader somehow. In Dev Options, I have a button for "Allow OEM Unlock" that I turned on, I just have to figure out the process. I'm going to keep trying to get this done! My first 2 things to try are just using ADB over WiFi and sending "fastboot oem unlock" and see what happens. Then I'll try rebooting with a USB keyboard attached into a weird "fastboot" screen the unit has built in. I just know it doesn't connect to my PC via USB, regardless of what I try.
Did you try to type "su" at the command prompt when you logged into it via adb? Most chinese car radios are root right out of the box.
As far as a bounty goes (or actually what you are proposing sounds more like a support contract than a bounty), I certainly wouldn't want to assume any kind of responsibility for those things. Not without source code (your link is just to a system update package, which is basically worthless).
Your first post is interesting. Are you a car dealer? Would you consider supporting a project that is better than low end locked down chinese crap?
https://github.com/HiKey960-Car
luciusfox said:
Did you try to type "su" at the command prompt when you logged into it via adb? Most chinese car radios are root right out of the box.
As far as a bounty goes (or actually what you are proposing sounds more like a support contract than a bounty), I certainly wouldn't want to assume any kind of responsibility for those things. Not without source code (your link is just to a system update package, which is basically worthless).
Your first post is interesting. Are you a car dealer? Would you consider supporting a project that is better than low end locked down chinese crap?
https://github.com/HiKey960-Car
Click to expand...
Click to collapse
I'm not a car dealer, no. I'm not looking for a support contract, just someone to help me root it, and perhaps clean up some Engrish from the few places I've found it.
I did try running su but I get permission denied. That was via adb over wifi and from the terminal.
Tomorrow I'll be putting it on my bench to try using fastboot and adb via USB.
USB woes
Well, I spent the weekend with it on my kitchen counter, trying to access it via ADB, but no matter what I do, my PC doesn't acknowledge that it's even connected to anything. In fact, none of the laptops in my house did. It just straight-up ignores the fact that something was just plugged into the USB port. -and yes, USB Debugging mode is turned on, and I have the ADB drivers installed on my laptop as well as Android Studio. I also tried everything below while connected to my laptop in various order.
Now, the head unit has options for USB mode, HOST and DEVICE. (As well as the option to use USB 2.0 or 1.1 for some reason?) When it's in HOST mode, it reads USB drives just fine for files, and lets me use a USB Keyboard but in Device mode, it doesn't. In fact, it does nothing via USB in Device mode. So, I'm wondering if maybe it's related to USB OTG settings that I can't access via the UI or something. Thoughts are appreciated.
Also, I can run terminal commands on it, and I can navigate through just fine, but get permission denied when I type "su" the prompt. I can use "reboot" just fine, and "reboot recovery" tries to launch some integrated auto-installation of recovery on the USB drive. If I run "reboot bootloader" it just goes to a black screen and says "FASTBOOT" at the bottom. It doesn't respond to keyboard or anything in that state though.
Anyone have any thoughts?
Well, it would definitely have to be in device mode for ADB to work over USB. Probably has a USB hub in between the port and the socket though, so you would need to figure out where the hub IC is, and how to connect to the SoC side of it.
Have you tried ADB over IP?
Try running "setprop persist.adb.tcp.port 5555" and then reboot, then try to "adb connect <ip address of radio>" and then "adb shell".
Fastboot has the same requirement as adb... device mode, and wiring.
Not sure what you mean by "ADB drivers installed on my laptop". ADB does not require drivers.
What does your host machine's kernel say when you try plugging in? Check the bottom of dmesg just after plugging in. Also check what "lsusb" outputs.
You starting to get a good picture of what makes chinese radios suck?
luciusfox said:
Well, it would definitely have to be in device mode for ADB to work over USB. Probably has a USB hub in between the port and the socket though, so you would need to figure out where the hub IC is, and how to connect to the SoC side of it.
Have you tried ADB over IP?
Try running "setprop persist.adb.tcp.port 5555" and then reboot, then try to "adb connect <ip address of radio>" and then "adb shell".
Fastboot has the same requirement as adb... device mode, and wiring.
Not sure what you mean by "ADB drivers installed on my laptop". ADB does not require drivers.
What does your host machine's kernel say when you try plugging in? Check the bottom of dmesg just after plugging in. Also check what "lsusb" outputs.
You starting to get a good picture of what makes chinese radios suck?
Click to expand...
Click to collapse
Yes, if you read my earlier posts, you'd see I can adb via ssh. My laptop detects nothing in any way, shape or form.
I have the MediaTek USB drivers installed for ADB.
Also, if you have a way to manufacture a unit en masse that does everything this one does for under $300USD, feel free to tell me more.
The fact that I'm trying to gain access that I'm not intended to have doesn't make it suck.
As for finding the hub, I've got a picture of the guts, but that's not much help.
PatrickHenninger said:
Yes, if you read my earlier posts, you'd see I can adb via ssh. My laptop detects nothing in any way, shape or form.
I have the MediaTek USB drivers installed for ADB.
Also, if you have a way to manufacture a unit en masse that does everything this one does for under $300USD, feel free to tell me more.
The fact that I'm trying to gain access that I'm not intended to have doesn't make it suck.
As for finding the hub, I've got a picture of the guts, but that's not much help.View attachment 4428019
Click to expand...
Click to collapse
One of the reasons why my first question to you was if you are a car dealer or not, is because if you were and wanted to build something that was good and not too terribly expensive, I could certainly arrange it, but not if you just want to buy one for you and one for your wife/gf. Are you interested in placing an order for... say 10,000 units? Also understanding that they won't look like the prototype in the picture. I would happily stick them in a nice DDIN box and switch some of the external USB parts to more integrated, specifically the AMFM radio and sound card. Switch those over to integrated i2s+i2c.
Your statement "The fact that I'm trying to gain access that I'm not intended to have doesn't make it suck." doesn't make any sense. Did you buy it or not? If you did, then I would think that it BELONGS TO YOU, and therefore it is INTENDED for you to actually use in whatever way you see fit. And there is no valid reason whatsoever that it should be locked out of your (the owner's) access. In fact, the very notion that anyone would believe that this kind of configuration is in any way acceptable makes me sick to my stomach.
Not to mention the fact that the manufacturer is in violation of software licensing agreements (GPL on the kernel, and proprietary on the google applications and other software that is pirated).
luciusfox said:
One of the reasons why my first question to you was if you are a car dealer or not, is because if you were and wanted to build something that was good and not too terribly expensive, I could certainly arrange it, but not if you just want to buy one for you and one for your wife/gf. Are you interested in placing an order for... say 10,000 units? Also understanding that they won't look like the prototype in the picture. I would happily stick them in a nice DDIN box and switch some of the external USB parts to more integrated, specifically the AMFM radio and sound card. Switch those over to integrated i2s+i2c.
Your statement "The fact that I'm trying to gain access that I'm not intended to have doesn't make it suck." doesn't make any sense. Did you buy it or not? If you did, then I would think that it BELONGS TO YOU, and therefore it is INTENDED for you to actually use in whatever way you see fit. And there is no valid reason whatsoever that it should be locked out of your (the owner's) access. In fact, the very notion that anyone would believe that this kind of configuration is in any way acceptable makes me sick to my stomach.
Not to mention the fact that the manufacturer is in violation of software licensing agreements (GPL on the kernel, and proprietary on the google applications and other software that is pirated).
Click to expand...
Click to collapse
I'm not a car dealer. I am working directly with a manufacturer in China to custom build these units for at least 50 people to start, and onward into the hundreds. Will it reach thousands, or tens-of-thousands? No idea. It's all part of a group-buy.
Anyhow, a DDIN will not work in these cars. It has to include everything shown in the picture, with the exception of my bench power supply. Even a regular dash kit for our cars (by Metra, Spectre, whoever) is in the $350-$450 range, NOT including the radio- ergo, this is the best current solution. Long story short, whatever you can build just won't work for what I'm doing.
Yes, my statement DOES make sense. 99% of what this unit is designed to do, it does an amazing job of. The 1% of failure comes from 1 screen that has a poor English translation, and it's part of a system app that I can't replace with my modified version without root access to replace it. Considering it's using open source, I'm not sure what they're pirating, since the only apps it comes with (aside from their in-house music player, radio app, and HVAC controller) would be Google Play and Adobe Reader.
I decided to look through some of your posts, and see you singing the same song in the majority of them. You talk smack about every device you don't like, you're condescending, and the only opinion that seems to matter to you is yours. In fact, the only help (and I use that term loosely) that you've offered here, is to attempt things that I already stated I had tried, but perhaps you were too preoccupied by your own inflated ego to bother reading all the details, and went straight to attempted condescension. While I appreciate your potential intent of assistance, I don't believe you're capable of offering any kind of helpful input, or information with any kind of value- with that, I say "Good day, sir."
Enjoy your Batman comics.
PatrickHenninger said:
I'm not a car dealer. I am working directly with a manufacturer in China to custom build these units for at least 50 people to start, and onward into the hundreds. Will it reach thousands, or tens-of-thousands? No idea. It's all part of a group-buy.
Anyhow, a DDIN will not work in these cars. It has to include everything shown in the picture, with the exception of my bench power supply. Even a regular dash kit for our cars (by Metra, Spectre, whoever) is in the $350-$450 range, NOT including the radio- ergo, this is the best current solution. Long story short, whatever you can build just won't work for what I'm doing.
Yes, my statement DOES make sense. 99% of what this unit is designed to do, it does an amazing job of. The 1% of failure comes from 1 screen that has a poor English translation, and it's part of a system app that I can't replace with my modified version without root access to replace it. Considering it's using open source, I'm not sure what they're pirating, since the only apps it comes with (aside from their in-house music player, radio app, and HVAC controller) would be Google Play and Adobe Reader.
I decided to look through some of your posts, and see you singing the same song in the majority of them. You talk smack about every device you don't like, you're condescending, and the only opinion that seems to matter to you is yours. In fact, the only help (and I use that term loosely) that you've offered here, is to attempt things that I already stated I had tried, but perhaps you were too preoccupied by your own inflated ego to bother reading all the details, and went straight to attempted condescension. While I appreciate your potential intent of assistance, I don't believe you're capable of offering any kind of helpful input, or information with any kind of value- with that, I say "Good day, sir."
Enjoy your Batman comics.
Click to expand...
Click to collapse
Whatever you say. When those chinese pieces of trash set a bunch of cars on fire, don't come crying to me.