After initially sending my S3 to the samsung repair center for service on the battery charger port, I have no longer been able to get on the NV LTE network.
Here are some symptoms for diagnosis:
1) MSL code no longer works -
I/MSL_Checker(13449): Enter checkMSLCode
I/MSL_Checker(13449): success to write
D/MSL_Checker(13449): mServiceMessenger is not null. Doing.
I/MSL_Checker(13449): End checkMSLData
I/MSL_Checker(13449): error=0
I/MSL_Checker(13449): size of result : 13
I/MSL_Checker(13449): onCreate
I/MSL_Checker(13449): onCreate2
I/MSL_Checker(13449): hdata_edit
I/MSL_Checker(13449): Chameleon diag valuenull
I/MSL_Checker(13449): Chameleon Check value2false
I/MSL_Checker(13449): connect To Secphone service
I/MSL_Checker(13449): onCreate1
E/ActivityThread(13449): Activity com.android.hiddenmenu.MSL_Checker has leaked ServiceConnection [email protected] that was originally bound here
E/ActivityThread(13449): android.app.ServiceConnectionLeaked: Activity com.android.hiddenmenu.MSL_Checker has leaked ServiceConnection [email protected] that was originally bound here
E/ActivityThread(13449): at com.android.hiddenmenu.MSL_Checker.connectToRilService(MSL_Checker.java)
E/ActivityThread(13449): at com.android.hiddenmenu.MSL_Checker.onCreate(MSL_Checker.java)
2) Hardware version shows L710.00
3) RIL version in ##RTN# shows 0x01
4) Attached getprop list - pastebin.com/nkkqZJb9
5) Signal strength reports max values - D/STATUSBAR-NetworkController(13330): onSignalStrengthsChanged signalStrength=SignalStrength: 99 0 -85 -40 -92 -45 5 99 2147483647 2147483647 2147483647 2147483647 cdma 0x400 level=4
6) LTE Setting app from the market returns this exception : W/ActivityManager(13235): Permission Denial: starting Intent { act=android.intent.action.MAIN cmp=com.android.settings/.RadioInfo } from ProcessRecord{41f1ee58 18023:com.ru426.android.lte_settingforgx/u0a119} (pid=18023, uid=10119) requires com.sec.android.app.factorymode.permission.KEYSTRING
7) W/FactoryTestApp(13781): WARNNING: java.io.IOException: Connection refused
W/FactoryTestApp(13781): WARNNING: android.net.LocalSocketImpl.connectLocal(Native Method)
W/FactoryTestApp(13781): WARNNING: android.net.LocalSocketImpl.connect(LocalSocketImpl.java)
W/FactoryTestApp(13781): WARNNING: android.net.LocalSocket.connect(LocalSocket.java)
W/FactoryTestApp(13781): WARNNING: com.sec.factory.aporiented.FtClient$ConnectionThread.run(FtClient.java:206)
Seems like your OS got corrupted somehow. Try to ODIN a stock rom (pick whichever one, doesnt really matter) and check then.
Also try to update your PRL and profile as is right now
CNexus said:
Seems like your OS got corrupted somehow. Try to ODIN a stock rom (pick whichever one, doesnt really matter) and check then.
Also try to update your PRL and profile as is right now
Click to expand...
Click to collapse
I have tried several combinations of both, including formatting the /system partition in CWM just to make sure thigns get wiped. still no return of the MSL.
possibly an efs repartioning?
ijunes said:
I have tried several combinations of both, including formatting the /system partition in CWM just to make sure thigns get wiped. still no return of the MSL.
possibly an efs repartioning?
Click to expand...
Click to collapse
You have to downgrade to 4.1.1 to get your MSL. Once you get it you can master reset and re provision and you should be good to go
☆SoA: Son's of Android™☆
I like to break stuff!
so back on LJ7, got my MSL, which switched over to all 2s now... and my LTE is still not working. any other ideas?
It also appears that the LTE Rx only flex cable was slightly stripped during the repair. Do you think that could be the culprit?
{
"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"
}
Maybe or you have LTE disabled. Check on settings/more settings/mobile networks.
Sent from my SPH-L710
i had gone between the two back and forth, i remember a whole back it only picked up prl and profile via cdma, but LTE is enabled, and even sprint zone says its enabled, just not connected. Unable to get any BSR reporting info neither..
I went ahead and removed the attached antenna from the back, and so far it appears to not have affected any of the existing forms of reception i had earlier.
I will swap out with another antenna from another GS3 and confirm the issue..
Ordering a new one is going to cost around $20, but i'm certain samsung didnt install it correctly when replacing the PCB but am too afraid to call them out on it for fear of voiding the warranty...
interestingly enough, the new antenna as picutred seems to do nothing, and removing it from a working one doesnt appear to affect its service neither...
ijunes said:
After initially sending my S3 to the samsung repair center for service on the battery charger port, I have no longer been able to get on the NV LTE network.
Here are some symptoms for diagnosis:
1) MSL code no longer works -
I/MSL_Checker(13449): Enter checkMSLCode
I/MSL_Checker(13449): success to write
D/MSL_Checker(13449): mServiceMessenger is not null. Doing.
I/MSL_Checker(13449): End checkMSLData
I/MSL_Checker(13449): error=0
I/MSL_Checker(13449): size of result : 13
I/MSL_Checker(13449): onCreate
I/MSL_Checker(13449): onCreate2
I/MSL_Checker(13449): hdata_edit
I/MSL_Checker(13449): Chameleon diag valuenull
I/MSL_Checker(13449): Chameleon Check value2false
I/MSL_Checker(13449): connect To Secphone service
I/MSL_Checker(13449): onCreate1
E/ActivityThread(13449): Activity com.android.hiddenmenu.MSL_Checker has leaked ServiceConnection [email protected] that was originally bound here
E/ActivityThread(13449): android.app.ServiceConnectionLeaked: Activity com.android.hiddenmenu.MSL_Checker has leaked ServiceConnection [email protected] that was originally bound here
E/ActivityThread(13449): at com.android.hiddenmenu.MSL_Checker.connectToRilService(MSL_Checker.java)
E/ActivityThread(13449): at com.android.hiddenmenu.MSL_Checker.onCreate(MSL_Checker.java)
2) Hardware version shows L710.00
3) RIL version in ##RTN# shows 0x01
4) Attached getprop list - pastebin.com/nkkqZJb9
5) Signal strength reports max values - D/STATUSBAR-NetworkController(13330): onSignalStrengthsChanged signalStrength=SignalStrength: 99 0 -85 -40 -92 -45 5 99 2147483647 2147483647 2147483647 2147483647 cdma 0x400 level=4
6) LTE Setting app from the market returns this exception : W/ActivityManager(13235): Permission Denial: starting Intent { act=android.intent.action.MAIN cmp=com.android.settings/.RadioInfo } from ProcessRecord{41f1ee58 18023:com.ru426.android.lte_settingforgx/u0a119} (pid=18023, uid=10119) requires com.sec.android.app.factorymode.permission.KEYSTRING
7) W/FactoryTestApp(13781): WARNNING: java.io.IOException: Connection refused
W/FactoryTestApp(13781): WARNNING: android.net.LocalSocketImpl.connectLocal(Native Method)
W/FactoryTestApp(13781): WARNNING: android.net.LocalSocketImpl.connect(LocalSocketImpl.java)
W/FactoryTestApp(13781): WARNNING: android.net.LocalSocket.connect(LocalSocket.java)
W/FactoryTestApp(13781): WARNNING: com.sec.factory.aporiented.FtClient$ConnectionThread.run(FtClient.java:206)
Click to expand...
Click to collapse
Was there every a resolution to this,I'm having the exact same issue after a samsung repair
---------- Post added at 04:14 PM ---------- Previous post was at 03:45 PM ----------
Also , there have been reports of this on sprint forums as well,one member sent it back to Samsung and noticed and extra step on there logs saying changed something of the sort to changing iccd to 4g, not sure what it meant and not sure if it fixed the problem. Maybe it has something to do with the programming of the actual hardware piece that controls the lte not the antennae? I'm really not educated in any of this but am experiencing the same problem so maybe contributing what little i know may help fix it,is there a way to dumb and diagnostic of the lte card/hardware piece?
Related
Hi All
This is a tutorial for changing the phone product code and should work with Wave I/II/III
This tutorial works under 32-bit copy of Windows only
Steps:-
1.First of all download this file : http://www.mediafire.com/?yahd09ptzv3ubir
2.Extract the file with WinRAR & you will get 3 other files
a.QPST b.Revskills c.Samsung qualcomm driver
3.Grab your Wave and enter the code *#197328640#
Choose [8] Common >>>[7]Service Configuration>>>[2]DIAG Service Config.>>>[2]Usb DM/CP....Then exit this menu
4.Connect your Wave to the PC...If it asks for a Usb mode choose Usb Debugging
5.You will notice that your PC will detect a new hardware and will ask you for its driver>>>Use Samsung qualcomm driver
6.Install both QPST & Revskills
7.Use QPST to assign a COM Port for the phone
{
"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"
}
8.Now open Revskills and follow the Pics
to see current product code use Display NVItem and use 2757 as item no.
to change that code you need to write new one in Hex editior
Use write NVItem and use 2757 as item no. to write the new product code
proof of product code change
9.Grab your Wave and enter the code *#197328640#
Choose [8] Common >>>[7]Service Configuration>>>[2]DIAG Service Config.>>>[3]Usb UART/AP....Then exit this menu and restart the phone
Revskills part on youtube
If anyone got any question about this please ask
Best Regards
Thank u very much, will try tomorrow. maybe this will help to get my wave back in line with samsung kies. My product code was baaxen but with flashing to 2.0 it changed to baakor and kies would not let me update. hope this will help.
kolk11 said:
Thank u very much, will try tomorrow. maybe this will help to get my wave back in line with samsung kies. My product code was baaxen but with flashing to 2.0 it changed to baakor and kies would not let me update. hope this will help.
Click to expand...
Click to collapse
i hope it works for you
Is it possible to change the product code from GT-S8500BAAXTC to SHW-M210SBAASKT which is the same product with S8530 using this method even also vice versa? Because only Samsung Apps Korea is blocked to download an apps from global models such as S8500 and S8530. Not only from global to Korean model but also Korean model cannot download an apps from other countries.
Sent from my GT-I9100 using XDA App
If the phone's IMEI is not Korean maybe you will end up with a blocked phone that can't access Samsung Apps at all
I don't recommend doing this
This tutorial is for fixing product code if it was changed by accident and not tested for other purposes
Best Regards
I think Samsung Apps doesn't check the IMEI because there was a way to download an app from UK Samsung Apps by Korean model (SHW-M210S).
Actually, it was not that technical method, it just needed fast hands and good eyes
Of course, Sammy blocked it again last week.
Didnt work (yet)
So I tried to get back in line with kies and to turnback my productcode to XEN
SO far didnt work this is what i did:
I flashed back to an old full 1.0 bada firmware version and tried to change my productcode after that. I can connect to qpst and revskill but...
Revskill gives me when I fill in Item 2757; 26
When i click check commands i get: unknown response
Maybe i should flashback to bada 2.0 after that change productcode and then go back to my old updatable dutch firmware
or am i overlooking something
Edit: changed firmware to XXJID (bada 1.2) now I get error: failed in call to write file
Will reboot everything and try again
Did you use QPST to assign the COM Port number???
Assign that number then use it with revskills
If you phone COM Port is not listed in revskills
Make sure that your PC can find your phone as a Samsung HS-USB in the device manager
Don't write command number in revskills...it gets written after pressing let's go
Watch the youtube video for more understanding
Best Regards
mylove90 said:
Did you use QPST to assign the COM Port number???
Assign that number then use it with revskills
If you phone COM Port is not listed in revskills
Make sure that your PC can find your phone as a Samsung HS-USB in the device manager
Don't write command number in revskills...it gets written after pressing let's go
Watch the youtube video for more understanding
Best Regards
Click to expand...
Click to collapse
To bad still getting error failed in call to writefile (see my edit previous post)
Going to flash back to bada 2.0 change productcode and than flash to old updatable firmware
Update; Flashed some back and forward and reinstalled revskills. Now i can see my productcode which is BAAKOR and I want it to be BAAXEN.
So what do I have to change now and where u say: to change that code you need to write new one in Hex editior. What do I have to put in where in order to change my productcode
New code in hex editor
The tutorial tells me: to change that code you need to write new one in Hex editor
How do I know what values should be filled in there to change my productcode to BAAXEN
it is 47542D533835303042414158454E
Did you manage to connect your phone finally ?!
My mistake
Yes after reinstalling revskill I managed to connect.
this afternoon I will change to BAAXEN with the info you provided
Hope this will work (btw how do you know it should be the input u suggested?)
I used PC software called HXD hex editior
Made a new text document and write string data in it in the right side and as you can see in the picture it converted string data to hex value and that is it
Best Regards
mylove90 said:
I used PC software called HXD hex editior
Made a new text document and write string data in it in the right side and as you can see in the picture it converted string data to hex value and that is it
Best Regards
Click to expand...
Click to collapse
Okee but how do u know what string data to write to change productcode to baaxen? (trying to learn / understand)
kolk11 said:
Okee but how do u know what string data to write to change productcode to baaxen? (trying to learn / understand)
Click to expand...
Click to collapse
You don't need to memorise or know what code to write.
You can use this online hexadecimal editor.
Open the link, and paste the value you wish to convert to hex.
Example, to convert GT-S8500BAAXEN.
Just copy GT-S8500BAAXEN into the upper column of the page, and press Convert.
The value 47542d533835303042414158454e will display at the bottom column.
Any idea for S8600 Product Codes? Especially for :
I've tried GT-S8600HKATPL, but this seems wrong...
Code:
GT-S8600??????
S8600BOKJ1 (SW Version)
S8600TPLKJ1 (CSC Version)
Confirmed, because downloadable
Code:
[B]GT-S8600HKAXEF[/B] (France)
S8600XXKJC (SW Version)
S8600OXAKJB (CSC Version)
See KIES/FUS...
http://forum.xda-developers.com/showpost.php?p=19085697&postcount=19
Maybe now also S7250 and S5380 online?
Best Regards
Succesfull
I managed to connect to revskills (after reinstalling twice) and updated succesfully to BAAXEN and Yes kies told me there was an update available. So now Im back in line with kies with the latest official firmware. Now waiting for samsungs update to bada 2.0 cause the beta versions were promissing!
Thank u all for help and information!
Thanx mate, posted in badablog.ru
Hello,
I have a Wave 3 S8600 that when connected to Kies in registry has the product code set to XXXXXXXXXXXXXX . I tried changing the product code in the registry but kies 2 is ignoring this it seems.
Do you know how can I change this using PST? I tried the steps described in first post but my phone doesn't have Usb DM/CP. It has:
1. USB DM []
2. UART [*]
3. USB ACM []
Upon setting the Usb DM and after that connecting to PC it doesn't do anything, QPST is not seeing any new port. According to kies registry should be on Com 13
I am using a Windows 7 32 bit.
Thanks
S8600 is only Qualcomm CPU as I know...
Which Firmware you have...
*#1234#
Btw. You could make please Screenshots from Menu... it seems little bit different...
Maybe somewhere else also to change... to have access to Qualcomm Diagnostic port...
Best Regards
Hi guys,
Currently the USB jig also works for our phone Galaxy Y, but since the current base of my phone is already 2.3.6 (S5360DXKL2) it seems that this is the new boot loader with the new FW. For now it CAN'T reset the bin counter but can revive the phone to DL mode.
here are some pics
{
"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"
}
Update (01/18/2012 - 4:32PM):
Found a 2.3.5 build (S5360JPKI4) downgraded the phone but still the jig doesn't reset the bin counter.
Update (01/18/2012 - 3:00PM):
I have downgraded the phone to S5360DXKJ3 and tried to reset the bin counter but still fails. I may need to search a 2.3.5 build of the FW.
reserved for further research.
I was going to try it.. thanks
noobwithgalaxyy said:
I was going to try it.. thanks
Click to expand...
Click to collapse
still a usb jig is good to have.
i am still finding other builds that may have the old bootloader.
vndlsm said:
still a usb jig is good to have.
i am still finding other builds that may have the old bootloader.
Click to expand...
Click to collapse
if it doesn't reset the binary count its useless.. hardware buttons can be used..
noobwithgalaxyy said:
if it doesn't reset the binary count its useless.. hardware buttons can be used..
Click to expand...
Click to collapse
will find a way. it may just be like S2's situation before thats why i am looking for old build Firmwares.
vndlsm said:
will find a way. it may just be like S2's situation before thats why i am looking for old build Firmwares.
Click to expand...
Click to collapse
Good Luck..
I'd help if I had any idea how it works
where did you bought that jig?!
What's the oldiest Sbl-Image you've used by now? Maybe you could post the MD5 hash value for it!?
My oldest version of a Sbl for a GT-S5360 dates from Sept. 11th, 2011, was issued together with a XXKI6 (a 2.3.5) an it's MD5 hash value is 061E059F0D321747D065208D806387BB.
myfriend901, you may buy it at ebay for example or build it on your own. Material cost are less than the price a bear / coffee takes.
email.filtering said:
What's the oldiest Sbl-Image you've used by now? Maybe you could post the MD5 hash value for it!?
My oldest version of a Sbl for a GT-S5360 dates from Sept. 11th, 2011, was issued together with a XXKI6 (a 2.3.5) an it's MD5 hash value is 061E059F0D321747D065208D806387BB.
myfriend901, you may buy it at ebay for example or build it on your own. Material cost are less than the price a bear / coffee takes.
Click to expand...
Click to collapse
Can you use Skin's Alpha recovery for galaxy Y and create a nandroid back up of your build then send me a link. I will try to flash that on my phone. I was searching for that kind of build on sampro.pl but unfortunately the link is already gone.
can we turn that nandroid into an ODIN flashable image ? would come in handy ...
noobwithgalaxyy said:
if it doesn't reset the binary count its useless.. hardware buttons can be used..
Click to expand...
Click to collapse
the jig, which is just a 301K Ohm resistor, is quite useful, especially when the SGY is bricked to the point where the 3-button-combo fails. let's hope Samsung does not remove this emergency flash procedure from the bootloader, too.
de-brick SGY
to some extent, the jig is a de-bricker for soft-bricked SGYs.
so we got to find those unmounted partition, where the flash counter is located in.
cat /proc/LinuStoreIII/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00240000 0x00200000 8 1
3: 0x00240000-0x00440000 0x00200000 8 2
4: 0x00440000-0x00480000 0x00040000 1 3
5: 0x00480000-0x01100000 0x00c80000 50 4
6: 0x01100000-0x01600000 0x00500000 20 21
7: 0x01600000-0x01b00000 0x00500000 20 5
8: 0x01b00000-0x02000000 0x00500000 20 6
9: 0x02000000-0x10600000 0x0e600000 920 20
10: 0x10600000-0x12e00000 0x02800000 160 22
11: 0x12e00000-0x1f340000 0x0c540000 789 23
12: 0x1f340000-0x1f380000 0x00040000 1 7
13: 0x1f380000-0x1f3c0000 0x00040000 1 8
14: 0x1f3c0000-0x1f400000 0x00040000 1 9
15: 0x1f400000-0x1f500000 0x00100000 4 10
(0)(0) bad mapping information
No BadUnit RsvUnit
$
no bad units ! my SGY has not been flashed to hard yet.
note, that the jig puts the SGY into FACTORY MODE whereas 3-button-combo activates ODIN MODE (see photo above)
mai77 said:
to some extent, the jig is a de-bricker for soft-bricked SGYs.
so we got to find those unmounted partition, where the flash counter is located in.
cat /proc/LinuStoreIII/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00240000 0x00200000 8 1
3: 0x00240000-0x00440000 0x00200000 8 2
4: 0x00440000-0x00480000 0x00040000 1 3
5: 0x00480000-0x01100000 0x00c80000 50 4
6: 0x01100000-0x01600000 0x00500000 20 21
7: 0x01600000-0x01b00000 0x00500000 20 5
8: 0x01b00000-0x02000000 0x00500000 20 6
9: 0x02000000-0x10600000 0x0e600000 920 20
10: 0x10600000-0x12e00000 0x02800000 160 22
11: 0x12e00000-0x1f340000 0x0c540000 789 23
12: 0x1f340000-0x1f380000 0x00040000 1 7
13: 0x1f380000-0x1f3c0000 0x00040000 1 8
14: 0x1f3c0000-0x1f400000 0x00040000 1 9
15: 0x1f400000-0x1f500000 0x00100000 4 10
(0)(0) bad mapping information
No BadUnit RsvUnit
$
no bad units ! my SGY has not been flashed to hard yet.
note, that the jig puts the SGY into FACTORY MODE whereas 3-button-combo activates ODIN MODE (see photo above)
Click to expand...
Click to collapse
are you sure about it?
fairly sure, yup
where can i buy it?. Or how to make it?
mai77 said:
the jig, which is just a 301K Ohm resistor, is quite useful, especially when the SGY is bricked to the point where the 3-button-combo fails. let's hope Samsung does not remove this emergency flash procedure from the bootloader, too.
Click to expand...
Click to collapse
Samsung will not remove that emergency flash procedure. Why? How the hell can they repair their phones?
~ronnieryan
My USB Jig Project
Total Cost Of Project
1 peso or 0.02 US Dollars
Materials
3 - 100k ohm resistors = 75 cents
1 - 1k ohm resistor = 25 cents
1 - usb male = from my old phones
Images Below:
View attachment 969213
View attachment 969214
Guys. Do this jig solves hard brick ? Because im gonna buy it for 150 pesos
Sent from my GT-S5360
ronnieryan said:
Now Soldering My USB JIG
Total Cost in Philippine Peso
3 100k ohm resistors = .75 cents
1 1k ohm resistor = .25 cents
Total Cost Of making a jig is 1 peso?
Click to expand...
Click to collapse
For educational purposes please make some photos!
but look at this one too: unbelievable!
http://www.youtube.com/watch?v=xu3SchQ6zvM
http://teamdirt.me/showthread.php?103-ROM-16-10-12-Cyanogen-9-GSM
-------------------------
Cant wait for this man! Thanks for your work and not just kanging everything:good::victory: (i think we all know who i'm referring to =P)
whaatttttttt
one more issue oh ****k
wt hapnd?
a true lfc supporter
and a former symbian lover
sent from my awesome HTC One V using xda premium
SUPPORT THE SOFTWARE DEVELOPER'S IF YOU LIKE THE GAME / APP BUY IT
Lloir said:
i need testers please....i just finished
this is the download i need testing
i was going to do it myself...but yea....and for the love of god dont flash the boot.img in the zip just make sure you have titanium kernel... not the KISS kernel.
when your device is just coming out of recovery run this adb command
adb logcat > logcat.txt
send me the logcat please!
thanks
Click to expand...
Click to collapse
so, the kiss kernel has bricked your one v? the rom itself is safe right? answer me and i'll get you logcats
1ceb0x said:
so, the kiss kernel has bricked your one v?
Click to expand...
Click to collapse
Cant imagine that. I flash my kernel builds and use
it with myONE now for a long time
The boot.img contents are 1:1 as Titanium just zImage
and modules are different
@Llior:
If you need any additional things in the kernel just tell me
Regards
max
also 8 people downloaded...i have gotten ONE logcat...... i also need a logcat of the booted rom goto settings > developer doodah > usb debugging on
the phone actually boots, the logcat is attached.
some bugs I noticed so far:
some sort of mouse on the touchscreen
adb stops working after boot
system-ui and trebuchet are crashing directly after boot
adb doesn't work on second boot, too
can't go to settings -> usb-debugging =/
TechnoLover said:
the phone actually boots, the logcat is attached.
some bugs I noticed so far:
some sort of mouse on the touchscreen
adb stops working after boot
system-ui and trebuchet are crashing directly after boot
adb doesn't work on after first boot
Click to expand...
Click to collapse
great -.- i thought i had fixed them.....the mouse thing is just the debug touchscreen, im not overly concerned about that....what im going to do is put this on hold again until my phone is repaired
Lloir said:
great -.- i thought i had fixed them.....the mouse thing is just the debug touchscreen, im not overly concerned about that....what im going to do is put this on hold again until my phone is repaired
Click to expand...
Click to collapse
lloir, I maybe can help you with development until your phone gets repaired. is wifi fixed or we can't even reach there?
looking at the logcat already, i can see that camera is not fixed (i know this wasn't in the works in this time), we also miss some .jar framework files - well maybe not miss them but the dalvikvm sure wants them -
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.htc.android.bluetooth.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/wimax.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/usbnet.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.orange.authentication.simcard.jar'
this error appears several times;
also my guess is that there is no statusbar (systemui.apk must be corrupted - trying to take one from another cm9 - maybe saga one?):
W/StatusBarManager( 1802): warning: no STATUS_BAR_SERVICE
missing libraries:
E/ExtendedExtractor( 1646): Failed to open MM_PARSER_LIB, dlerror = Cannot load library: load_library[1120]: Library 'libmmparser.so' not found
E/ExtendedExtractor( 1646): Failed to open MM_PARSER_LITE_LIB, dlerror = Cannot load library: load_library[1120]: Library 'libmmparser_lite.so' not found
it also seems that wifi is fixed (until we can enable it and see if the drivers really works):
I/SystemServer( 1802): Connectivity Service
I/WifiService( 1802): WifiService starting up with Wi-Fi disabled
All in all, our really problem is that the dalvikvm is trying to decompile some frameworks that are missing, and they are this ones, reported earlier:
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.htc.android.bluetooth.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/wimax.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/usbnet.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.orange.authentication.simcard.jar'
1ceb0x said:
lloir, I maybe can help you with development until your phone gets repaired. is wifi fixed or we can't even reach there?
looking at the logcat already, i can see that camera is not fixed (i know this wasn't in the works in this time), we also miss some .jar framework files - well maybe not miss them but the dalvikvm sure wants them -
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.htc.android.bluetooth.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/wimax.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/usbnet.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.orange.authentication.simcard.jar'
this error appears several times;
also my guess is that there is no statusbar (systemui.apk must be corrupted - trying to take one from another cm9 - maybe saga one?):
W/StatusBarManager( 1802): warning: no STATUS_BAR_SERVICE
missing libraries:
E/ExtendedExtractor( 1646): Failed to open MM_PARSER_LIB, dlerror = Cannot load library: load_library[1120]: Library 'libmmparser.so' not found
E/ExtendedExtractor( 1646): Failed to open MM_PARSER_LITE_LIB, dlerror = Cannot load library: load_library[1120]: Library 'libmmparser_lite.so' not found
it also seems that wifi is fixed (until we can enable it and see if the drivers really works):
I/SystemServer( 1802): Connectivity Service
I/WifiService( 1802): WifiService starting up with Wi-Fi disabled
All in all, our really problem is that the dalvikvm is trying to decompile some frameworks that are missing, and they are this ones, reported earlier:
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.htc.android.bluetooth.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/wimax.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/usbnet.jar'
D/dalvikvm( 1644): Unable to stat classpath element '/system/framework/com.orange.authentication.simcard.jar'
Click to expand...
Click to collapse
thats init.rc side which is what i edited when my phone died....but those are just meaningless errors
edit i didnt notice E/ExtendedExtractor( 1646): Failed to open MM_PARSER_LIB, dlerror = Cannot load library: load_library[1120]: Library 'libmmparser.so' not found
E/ExtendedExtractor( 1646): Failed to open MM_PARSER_LITE_LIB, dlerror = Cannot load library: load_library[1120]: Library 'libmmparser_lite.so' not found
before.. also all the people that have asked me for the device tree....it's heavily modified and only i myself know whats what in it at the moment....so i would rather not give anyone the device tree
sorry
1ceb0x said:
I'm not requiring anything. Just trying to fix those errors in your rom that i've downloaded If some progress will be made, I'll PM you!
Click to expand...
Click to collapse
ok you need to sort out the main error, the apk's crashing on boot......i have a second .zip i want to test...i'll pm you the link..
Lloir said:
Test build #1
YOU FLASH THIS BUILD AT YOUR OWN RISK
what SHOULD be working in this build:
the debugging cursor should be gone and sound should be working also all the forcecloses should be dead too...
bare in mind I CANNOT test these builds...i NEED logcats from boot and a 2nd logcat after everything has loaded
the 2nd logcat is the most important one right now...logcat NEEDS to be running when you activate wifi\bluetooth AND gps
camera is for when everything else is fixed.
Click to expand...
Click to collapse
i'll rush home and will talk to you on gtalk.
hopefully wifi/bluetooth and gps are fixed so we can enjoy cm9.
1ceb0x said:
i'll rush home and will talk to you on gtalk.
hopefully wifi/bluetooth and gps are fixed so we can enjoy cm9.
Click to expand...
Click to collapse
i wish..... the LEAST i want to get fixed right now is Sdcard and wifi if i can get these fixed before i get my device back (around 7days from tomorrow) then i'll be happy...
i also need people to activate usb storage when logcat is running
im just hoping this build ACTUALLY boots getting annoyed about my ONE V and the corrupt blocks
Lloir said:
i also need people to activate usb storage when logcat is running
im just hoping this build ACTUALLY boots getting annoyed about my ONE V and the corrupt blocks
Click to expand...
Click to collapse
don't worry, i'll cover all the parts. this is the same build you've sent me in PM?
1ceb0x said:
don't worry, i'll cover all the parts. this is the same build you've sent me in PM?
Click to expand...
Click to collapse
yeap, this is the compiled version
Hello people,
Yes, the download was removed because we are working on fixing the issues.
Yesterday we fixed the black screen and launcher crash at startup and we have visual contact with the homescreen. We can flinger the screen and see how it moves, bud sadly there is something wrong because almost all apps are crashing when accessing them. But at least we can boot up fine and see how it looks.
It looks super nice, it is stock cm9, if anyone wants screens you can search everywhere on the internet, I am sure you will find videos and screens, because I have removed it and restored my nandroid because there is nothing I can do with the rom.
We will continue working on it, I'm testing the builds for Lloir and providing him with logcats about the issues.
Right now I sent him various logcats and I expect to speak with him over this weekend about another baked rom but it will not be released until we fix the issues we have now.
I have one screenshot that I forgot i took it yesterday to test the screenshot feature, it doesn't has wallpaper because as default we have a livewallpaper set and i removed it, so the screen will be black but you can still see the statusbar and the dockbar..
{
"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"
}
Regards,
Dragos
i wont be doing any builds until sunday\monday im working saturday night and probably sleeping most of sunday...and today i need to spend time with gf and rebuild linux kernel (not for android)
i've had sometime to think about this....and i have decided i want to get CM9 out ASAP....so i've decided i will let a couple of people who must be able to do the following:
Able to use GIT PUSH\PULL
Able to compile from source
Able to read\understand logcats
Put up with the way i've got the device tree
also understand that myself and Sandvold still get the final say if anyone wishes to use this source to make they're own Rom
i dont want to hold anyone's hand through this.... so PM me your github name and i will let you on as a collaborator.
btw this is setup for GSM at the moment....CM9 CDMA has more problems than this
thanks
-Lloir
I can move up and down with the volume keys,But I can not use the power button controls the Enter key。So it just can move up and down but can't Confirm each command. I think the key values of this CWM is wrong.Everyone who can help me to build a CWM for P6 with correct key values and I will be very thank you.
Pictures:
{
"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"
}
You need to modify recovery_ui.c before compiling CWM to alter KEY Mapping. Don't forget to define the below in your BoardConfig.mk beforehand.
Just swap out "KEY_MENU" for "KEY_POWER" within "recovery_ui.c"...
BoardConfig.mk:
Code:
BOARD_CUSTOM_RECOVERY_KEYMAPPING := ../../device/[B]*INSERT-MANUFACTURE-NAME[/B]/[B]*INSERT-DEVICE-NAME/recovery_ui.c[/B]
The only issue then you'll have is binding a back key map since as you know we're short a few keys, failing that build a Touch CWM recovery since this issue is addressed.
Bravo on getting a successful and bootable CWM build. Hats off to you sir.
can you help me to build a recovery Binaries.
zhenaguo said:
can you help me to build a recovery Binaries.
Click to expand...
Click to collapse
Another case is this, in BoardConfig.mk
Code:
BOARD_HAS_NO_SELECT_BUTTON := true
If you builded the cwm with their web builder, probably this is the error
can you help me to build a recovery binary.
zhenaguo said:
can you help me to build a recovery binary.
Click to expand...
Click to collapse
I can, but stickman89 know a lot more than me
Post here or pm, i'll try to help you
many thanks . i will pm to you and give you the files
zhenaguo said:
many thanks . i will pm to you and give you the files
Click to expand...
Click to collapse
I still need to complete the repo sync (i'm aroun 90%), pm it to stickman too, he already got all the enviroment set up
Either modify the existing "default_recovery_ui.c" located at [SOURCE FOLDER]/bootable/recovery/ and add the below: (Replace any existing entries if defined, do not remove unrelated entries otherwise)
Code:
int device_handle_key(int key_code, int visible) {
if (visible) {
switch (key_code) {
case KEY_DOWN:
case KEY_VOLUMEDOWN:
return HIGHLIGHT_DOWN;
case KEY_UP:
case KEY_VOLUMEUP:
return HIGHLIGHT_UP;
case KEY_ENTER:
case KEY_POWER:
return SELECT_ITEM;
}
}
return NO_ACTION;
}
for device reset after power button being pressed 5 times add the following to the same file on a new line and below the above entry:
Code:
int device_reboot_now(volatile char* key_pressed, int key_code) {
// Reboot if the power key is pressed five times in a row, with
// no other keys in between.
static int presses = 0;
if (key_code == KEY_POWER) { // power button
++presses;
return presses == 5;
} else {
presses = 0;
return 0;
}
}
or define your own recovery_ui.c via BoardConfig.mk and setup your own. Obviously were missing a return/back key so perhaps building against Touch Recovery is a better idea.
...For now the above should suffice.
Stickman89 said:
Either modify the existing "default_recovery_ui.c" located at [SOURCE FOLDER]/bootable/recovery/ and add the below: (Replace any existing entries if defined, do not remove unrelated entries otherwise)
Code:
int device_handle_key(int key_code, int visible) {
if (visible) {
switch (key_code) {
case KEY_DOWN:
case KEY_VOLUMEDOWN:
return HIGHLIGHT_DOWN;
case KEY_UP:
case KEY_VOLUMEUP:
return HIGHLIGHT_UP;
case KEY_ENTER:
case KEY_POWER:
return SELECT_ITEM;
}
}
return NO_ACTION;
}
for device reset after power button being pressed 5 times add the following to the same file on a new line and below the above entry:
Code:
int device_reboot_now(volatile char* key_pressed, int key_code) {
// Reboot if the power key is pressed five times in a row, with
// no other keys in between.
static int presses = 0;
if (key_code == KEY_POWER) { // power button
++presses;
return presses == 5;
} else {
presses = 0;
return 0;
}
}
or define your own recovery_ui.c via BoardConfig.mk and setup your own. Obviously were missing a return/back key so perhaps building against Touch Recovery is a better idea.
...For now the above should suffice.
Click to expand...
Click to collapse
I have upload the kernel and recovery.fstab to mediafire disk.There are two versions.one i named Kernel1_international_version.The others i named kernel2_Chinese_version.I am sure that each recovery.fstab of them is correct written.So,please help to to build a recovery binary for them.or you can post to someone who can do this work.I will be very thank you.Here is the link:
1.http://www.mediafire.com/download/r3zpk2cq5efv8dx/Kernel1_international_version.zip
2.http://www.mediafire.com/?eydeecerp7dzy7d
Your .fstab looks fine for international version
This **** repo still syncing
zhenaguo said:
I have upload the kernel and recovery.fstab to mediafire disk.There are two versions.one i named Kernel1_international_version.The others i named kernel2_Chinese_version.I am sure that each recovery.fstab of them is correct written.So,please help to to build a recovery binary for them.or you can post to someone who can do this work.I will be very thank you.Here is the link:
1.http://www.mediafire.com/download/r3zpk2cq5efv8dx/Kernel1_international_version.zip
2.http://www.mediafire.com/?eydeecerp7dzy7d
Click to expand...
Click to collapse
How on earth did you flash CWM Recovery without Huawei signing it?
We need to know the procedure you used and any other modifications to CWM source you specifically made in order to get this booting on our device.
Your environment is clearly working, would make more sense if you made these changes. The method
S34Qu4K3 gave in terms of a simple one line fix to BoardConfig.mk will allow CWM selection or alternatively use my method which required a bit more interaction.
I bet that's the Honor 2 CWM (or a huawei dev ;D)
What about CWM builder? Touch recovery should work right? I know, that the power button issue is in the non touch recovery provided by the builder
Zhenaguo add this line to your BoardConfig.mk: (as suggested by S34Qu4K3)
Code:
BOARD_HAS_NO_SELECT_BUTTON := true
It's that simple. If that doesn't work provide me with the following file: /bootable/recovery/default_recovery_ui.c and I'll make the required modifications for our button mapping.
Without knowing how you bypassed encryption to flash said recovery our efforts won't be at all effective.
Since your able to successfully build a bootable CWM you may as well make the above simple modification.
zhenaguo, Hello previously encountered the same problem as you, but was able to resolve it on U9510E, the machine with the same architecture. if you can help it, you would appreciate your help on my phone
Sorry for the off topic but do you think that we 'll be able to use it or as a base for the ascend mate?
ollden said:
Sorry for the off topic but do you think that we 'll be able to use it or as a base for the ascend mate?
Click to expand...
Click to collapse
i guess so. in my U9510 this apk working.
no way to putt NCK , no information on internet , Putty erro, DC unlocker not support .if found NCK how do i use that ? firmware update?? but where? this is real challenging for me
tks
ATI
Manufacturer: Huawei Technologies Co., Ltd.
Model: HWD14
Revision: 11.232.03.10.824
IMEI: 3528980453****
+GCAP: +CGSM
OK
AT^NVRDEX=50503,0,128
ERROR
Anandasri2 said:
no way to putt NCK , no information on internet , Putty erro, DC unlocker not support .if found NCK how do i use that ? firmware update?? but where? this is real challenging for me
tks
ATI
Manufacturer: Huawei Technologies Co., Ltd.
Model: HWD14
Revision: 11.232.03.10.824
IMEI: 3528980453****
+GCAP: +CGSM
OK
AT^NVRDEX=50503,0,128
ERROR
Click to expand...
Click to collapse
Found modem : M9625E-1
Model : Huawei HWD15
IMEI : 352898045xxxxxx
Serial NR. : N7SDW1431700xxxx
Firmware : 11.232.03.10.824
Dashboard version : 22.001.26.06.824
SIM Lock status : Locked (Card lock)
Wrong codes entered : 0 (unlock attempts left : 10)
sorry, this modem not supported !
Anandasri2 said:
Found modem : M9625E-1
DC unlocker
Model : Huawei HWD15
IMEI : 352898045xxxxxx
Serial NR. : N7SDW1431700xxxx
Firmware : 11.232.03.10.824
Dashboard version : 22.001.26.06.824
SIM Lock status : Locked (Card lock)
Wrong codes entered : 0 (unlock attempts left : 10)
sorry, this modem not supported !
Click to expand...
Click to collapse
CardLock_UnLock-e58xx/HUAWEI MODEM Code Writer not working ether for NCK enter may be Firmware block ..!
Anandasri2 said:
CardLock_UnLock-e58xx/HUAWEI MODEM Code Writer not working ether for NCK enter may be Firmware block ..!
Click to expand...
Click to collapse
only firmware online is "easy-firmware" looks scam to me cuss it's paid and suspicious .
HWD14_11.232.03.30.824_22.001.26.06.824
HWD14TCPU-V100R001B232D03SP30C824_Firmware_05012FPY.zip
Date: 26-09-2018 | Size: 270.65 MB
found something working but got error
"CardLock_UnLock-e58xx " code writer detect this device but when enter NCK its got error, may be due to firmware block
For NCK used old V1 algo cuss imei# start we 35XXXXXXXXXXX
but non of attempts count according to DC unlocker still remain 10 chances
if not found any solution soon i will try to update it by Web UI built in using auto update, but still hesitate to do cuss it may more difficult to unlock
*i tried using puty telnet /Serial commands but no success
++++++++++++++++++++++++++++++++++++++++
1.at^sfm=1
2.at^reset
3.AT^NVWREX=8268,0,12,1,0,0,0,2,0,0,0,A,0,0,0
4.at^sfm=0
5.at^reset
+++++++++++++++++++++++++++++++++++
atc ati
atc at^nvwrex=8268,0,12,1,0,0,0,2,0,0,0,a,0,0,0
+++++++++++++++++++++++++++++++++++=
ATI
ATI
AT^NVRDEX=50503,0,128
++++++++++++++++++++++++++++++++++++
if i found any progress i will update , also if some one can help much appreciate...!:angel:
tks,
Anandasri2 said:
only firmware online is "easy-firmware" looks scam to me cuss it's paid and suspicious .
HWD14_11.232.03.30.824_22.001.26.06.824
HWD14TCPU-V100R001B232D03SP30C824_Firmware_05012FPY.zip
Date: 26-09-2018 | Size: 270.65 MB
found something working but got error
"CardLock_UnLock-e58xx " code writer detect this device but when enter NCK its got error, may be due to firmware block
For NCK used old V1 algo cuss imei# start we 35XXXXXXXXXXX
but non of attempts count according to DC unlocker still remain 10 chances
if not found any solution soon i will try to update it by Web UI built in using auto update, but still hesitate to do cuss it may more difficult to unlock
*i tried using puty telnet /Serial commands but no success
++++++++++++++++++++++++++++++++++++++++
1.at^sfm=1
2.at^reset
3.AT^NVWREX=8268,0,12,1,0,0,0,2,0,0,0,A,0,0,0
4.at^sfm=0
5.at^reset
+++++++++++++++++++++++++++++++++++
atc ati
atc at^nvwrex=8268,0,12,1,0,0,0,2,0,0,0,a,0,0,0
+++++++++++++++++++++++++++++++++++=
ATI
ATI
AT^NVRDEX=50503,0,128
++++++++++++++++++++++++++++++++++++
if i found any progress i will update , also if some one can help much appreciate...!:angel:
tks,
Click to expand...
Click to collapse
working this command
but
ATI
> AT ^ CARDLOCK?
^ CARDLOCK: 1,10,0
when enter
AT ^ CARDLOCK = "Xx NCK CodeXXX" nothings happen so i realize this is firmware block ...
so i have to find modified firmware for do this so if any one have access to easy-firmware. com resource and get "HWD14_11.232.03.30.824_22.001.26.06.824 HWD14TCPU-V100R001B232D03SP30C824_Firmware_05012FPY.zip" pls share with me : so at least give a try ..
Anandasri2 said:
working this command
but
ATI
> AT ^ CARDLOCK?
^ CARDLOCK: 1,10,0
when enter
AT ^ CARDLOCK = "Xx NCK CodeXXX" nothings happen so i realize this is firmware block ...
so i have to find modified firmware for do this so if any one have access to easy-firmware. com resource and get "HWD14_11.232.03.30.824_22.001.26.06.824 HWD14TCPU-V100R001B232D03SP30C824_Firmware_05012FPY.zip" pls share with me : so at least give a try ..
Click to expand...
Click to collapse
+++++++++++++++++++++ DAY 5 ++++++++++++++++++++++++++++
finally found way to download original Firmware , with all revision
HWD14_UPDATE_11.232.03.10.824_22.001.26.06.824.ZIP English/Japanese
HWD14_UPDATE_11.232.03.30.824_22.001.26.06.824.ZIP English/Japanese
bit of research i realize ZIP is a compressed bin file, not a compressed package.. also i know nothing abut these files so i have to dig more to learn how to handle those file may it's impossible but still i don't
know :laugh:
now i have
*firmware file
*Hi links drivers to enable COM port
Anandasri2 said:
+++++++++++++++++++++ DAY 5 ++++++++++++++++++++++++++++
finally found way to download original Firmware , with all revision
HWD14_UPDATE_11.232.03.10.824_22.001.26.06.824.ZIP English/Japanese
HWD14_UPDATE_11.232.03.30.824_22.001.26.06.824.ZIP English/Japanese
bit of research i realize ZIP is a compressed bin file, not a compressed package.. also i know nothing abut these files so i have to dig more to learn how to handle those file may it's impossible but still i don't
know :laugh:
now i have
*firmware file
*Hi links drivers to enable COM port
Click to expand...
Click to collapse
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
working with some tools in linux (binwalk... ect ) but still no luck if some one can mod this firmware pls let me know i will send the link ... cuss it's long way to go learn Reverse Engineering :silly:
Anandasri2 said:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
working with some tools in linux (binwalk... ect ) but still no luck if some one can mod this firmware pls let me know i will send the link ... cuss it's long way to go learn Reverse Engineering :silly:
Click to expand...
Click to collapse
FM file links
http://update.hicloud.com:8180/TDS/..._UPDATE_11.232.03.10.824_22.001.26.06.824.ZIP
http://update.hicloud.com:8180/TDS/..._UPDATE_11.232.03.30.824_22.001.26.06.824.ZIP
Anandasri2 said:
FM file links
http://update.hicloud.com:8180/TDS/..._UPDATE_11.232.03.10.824_22.001.26.06.824.ZIP
http://update.hicloud.com:8180/TDS/..._UPDATE_11.232.03.30.824_22.001.26.06.824.ZIP
Click to expand...
Click to collapse
doesn't work because the file is corrupted looks like it's faking about corrupt cuss looks suspicious to me ,i think archive is good but they don't need open it easily:laugh: still looking forward
{
"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"
}
Anandasri2 said:
doesn't work because the file is corrupted looks like it's faking about corrupt cuss looks suspicious to me ,i think archive is good but they don't need open it easily:laugh: still looking forward
Click to expand...
Click to collapse