[Q] Rescue Killed Shield Tablet K1 - Shield Tablet Q&A, Help & Troubleshooting

i'm trying to rescue my killed Shield K1.
we know that the tablet is still in APX-Mode and there is the possibilty sending commands with nvflash.
what we need is the cpuid or uid which is to get with a special script (thx Moscow Desire). in many cases was people able to find out the "cpuid" and obtain the SKB
. eg. hier with iconia a500 : http://forum.xda-developers.com/showthread.php?t=1751978
i also tried to get the SBK from my K1 with a modificated script(changed the "vid_pid to 0x0955, 0x7F40" and "received_length" to 16) but without success. i got a wrong uid (just last seven digits was true the first eight digits was ziros) and thus a wrong SBK.
if we get the right uid we can be able to use nvflash.
hier is some questions:
how many digits are the right cpuid from K1?
can someone make a script for our purpose?
thanks for your help.
regards
Cappy
-------
#include <libusb-1.0/libusb.h>
#include <stdio.h>
#include <stdint.h>
int main(void)
{
unsigned char data[64];
int received_length;
int r = 1;
libusb_context* ctx = NULL;
libusb_device_handle* dev_handle = NULL;
libusb_init(&ctx);
dev_handle = libusb_open_device_with_vid_pid(ctx, 0x0955, 0x7F40);
if(dev_handle)
{
r = libusb_bulk_transfer(dev_handle, 0x81, data, sizeof(data), &received_length, 10000);
if (r == 0)
{
if(received_length == 16)
{
printf("uid: %#016lx\n", *(uint64_t*)data);
}
else
{
r = 1;
printf("Error: We got %d bytes of data insetad of the 8 bytes we expected...\n", received_length);
}
}
else
{
printf("Error: USB read failed!\n");
}
libusb_release_interface(dev_handle, 0);
}
else
{
printf("Error: Failed to open device!\n");
}
libusb_exit(ctx);
return r;
}

Hello Friend, Could you please whatsapp to me (+91 9940962929) so i can support you on this.

Can you please keep all the info or support public, so anyone else with the same problem can participate! I also have a deactivated Shield tablet that I'm very keen on repairing so any info on how to eventually do it is highly appreciated!

grujic.ljubomir said:
Can you please keep all the info or support public, so anyone else with the same problem can participate! I also have a deactivated Shield tablet that I'm very keen on repairing so any info on how to eventually do it is highly appreciated!
Click to expand...
Click to collapse
Hi, we already have the ground team working on it..Since I am also in and i needed you peoples to join so it can be useful for discussion in persons rather we go public...Maybe once we are successful we can post it in public and support peoples..!

Great to know that people are seriously working on this! Wishing you luck and eagerly waiting for the solution

grujic.ljubomir said:
Great to know that people are seriously working on this! Wishing you luck and eagerly waiting for the solution
Click to expand...
Click to collapse
i think so many ppl w8ting for solution. I have at home to one killed tablet.

to know the status of work ..whatsapp to 9940962929..
Sent from my SM-N920G using XDA-Developers mobile app

Any news on this?

Since on the subject of possibly dead tablets:
If anyone has a bricked tablet and wants to sell it PM me. I got a working one but the front is very cracked so looking to buy a dead one for the parts. eBay has no listing at all for parts. ?
Please reply here or PM me if interested.

Hi i try to get cpuid, the code you nave posted are true but when i try it i understand the:
printf("uid: %#016lx\n", *(uint64_t*)data);
To be (i think):
printf("uid: %#016lx\n", *(uint128_t*)data);
but for uint128 need to h!ve 128bit processor
i think... but i don't know if correct.

I am also trying to solve this problem for quite some time now and I am interested in
- getting the cpuid or uid
- getting the SBK
- getting shofel2_t124 to work properly

Related

[DEV] Adding your ROM to ROM Manager

It's easy, it's free. And here's how you do it!
You will need to create two simple JavaScript files:
A file that describes your ROMs that you send to me.
A file that you host that lists your ROMs, so you can update your ROM Manager section.
First, your developer/ROM description file:
Code:
{
// This is what name you want your ROMs to show up under.
developer: "CyanogenMod",
// Your id. This should have no spaces or other funny characters.
// This would ideally be your Github id, so when you send me your manifest
// I can verify who you are. But it can be anything really.
id: "cyanogen",
// The display summary. Two lines max.
summary: "Mods and bacon for Dream, Sapphire, Droid, and Nexus One",
// The location of the developer's manifest.
manifest: "http://gh-pages.clockworkmod.com/ROMManagerManifest/cyanogenmod.js",
// The list of devices that this developer's ROMs support.
// If you don't support a device, just don't list it!
roms:
{
sholes: true,
passion: true
}
}
Send me that file! [email protected]
Link to developer sample: http://gh-pages.clockworkmod.com/ROMManagerManifest/samples/developer.js
And now, create your ROM list file:
Code:
{
// The version of the manifest, so ROM Manager knows how to load it
version: 1,
// The homepage for your ROM, if you have one.
homepage: "http://www.cyanogenmod.com/",
// The donate link for yuor ROM, if you have one.
donate: "https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3283920",
// Your list of ROMs
roms:
[
{
// Display name of the rom
name: "CyanogenMod 5.0.5",
// Display summary of the rom
summary: "Stable",
// Device that this rom runs on
device: "sholes",
// This is the download URL of your ROM.
// These URLs should have unique filenames per version!
// Ie, don't use a zip with the same name
// as that of a previous version with a new version.
// Otherwise ROM Manager will continue using the
// old cached zip on the SD card.
// This must be a direct download,
// and not a Mediafire type link.
url: "http://www.droidaftermarket.com/koush/motorola/sholes/cyanogen_sholes-ota-eng.koush_5.0.5.zip"
},
// Antother, older ROM!
{
name: "CyanogenMod 5.0.4",
summary: "Stable",
device: "sholes",
url: "http://www.droidaftermarket.com/koush/motorola/sholes/cyanogen_sholes-ota-eng.koush_5.0.4.zip"
}
]
}
Link to manifest sample: http://gh-pages.clockworkmod.com/ROMManagerManifest/samples/simplemanifest.js
And you're done!
If you're a pro dev, you can even create a ROM customizer. But I won't get into that here
Follow this link for more information: http://www.koushikdutta.com/2010/03/rom-manager-and-third-party-roms.html
Bump. We need more ROMs added to this awesome mod!
I hope that Paul @ modaco decides to up his roms to rom manager.
Koush can you please answer me one question. Is it at all possible to add an extra button as confirm within recovery? My trackpad is totally broken. I have asked loads of times. I'm not demanding anything as such just want to know,
1. Is it possible to physically implement? Power button or menu to confirm?
2. If it is possible is there a chance you can add it to a future release.
I feel like a broken record going on about it but i'm really big on rom flashing but worried about flashing roms now incase i get stuck and need to use recovery!
Thanks.
clockworkmod is the best thing IMO for the htc desire, after root of course
honestly its just pleasing to know its there as a safeguard
thanks for all your work
ephumuris said:
I hope that Paul @ modaco decides to up his roms to rom manager.
Koush can you please answer me one question. Is it at all possible to add an extra button as confirm within recovery? My trackpad is totally broken. I have asked loads of times. I'm not demanding anything as such just want to know,
1. Is it possible to physically implement? Power button or menu to confirm?
2. If it is possible is there a chance you can add it to a future release.
I feel like a broken record going on about it but i'm really big on rom flashing but worried about flashing roms now incase i get stuck and need to use recovery!
Thanks.
Click to expand...
Click to collapse
Yeah, Koush! Honestly, I feel bad for Ephu. Unluckiest son of a ***** in these here parts.
Ha more like stupidity! Dropping my phone in a drink lol. Il buy a replacement trackpad as soon as it is possible. I think mine is 100% dead now. I just want an alternative button as I'm a Rom whore lol.

Compass fix for n00bs...

Hi,
As many people, I encoutered the compass issue after updating to 2.3.3
I've browsed all forums and found several fixes (8 move, installing Google Skymap, factory reset, calibrating upside down, etc etc)
None of these work, which sucks because I'm going on holiday in a few days to climb and camp on Mount Olympos (Greece)
Since one of the reasons was to enjoy the night sky without the city lights destroying the great view of the stars, I'm really hoping I can fix the compass before I go so I can use skymap.
I've found 2 fixes, but I couldn't find a good explaination on how to install them.
On was changing some line of codes in a driver, the other one was flashing some file (but not with Odin)
I have a Samsung Galaxy Gio with 2.3.3
Is there any way for me to fix this. Hopefully with a good step by step instruction?
Thanks in advance.
c20h25n3o said:
Hi,
As many people, I encoutered the compass issue after updating to 2.3.3
I've browsed all forums and found several fixes (8 move, installing Google Skymap, factory reset, calibrating upside down, etc etc)
None of these work, which sucks because I'm going on holiday in a few days to climb and camp on Mount Olympos (Greece)
Since one of the reasons was to enjoy the night sky without the city lights destroying the great view of the stars, I'm really hoping I can fix the compass before I go so I can use skymap.
I've found 2 fixes, but I couldn't find a good explaination on how to install them.
On was changing some line of codes in a driver, the other one was flashing some file (but not with Odin)
I have a Samsung Galaxy Gio with 2.3.3
Is there any way for me to fix this. Hopefully with a good step by step instruction?
Thanks in advance.
Click to expand...
Click to collapse
flash back to 2.2
That's my final option indeed.
But my battery lasts 3 days now, with Froyo not even 1. That's why I really hope to find another solution.
battery last for 3 days? how can? what is your rom?
can you share those 2 fixes? maybe i can help. i want to fix my compass on galaxy gio too.
sorry for bad english.
I’m sorry but no compass program will ever work with this kernel! I extracted the bad code from the kernel. Here it is:
c024d3e8: mov r1, #4 @ r1: RBUFF_SIZE
c024d3f8: mov r1, #4 @ r1: RBUFF_SIZE
c024d42c: str ip, [r4, #76] @ atomic_set(&data_ready, 1)
c024d430: str r0, [r4, #68] @ r0 (contents of buffer) into sense_data (part 1)
c024d434: strb r1, [r4, #72] @ r1 (contents of buffer) into sense_data (part 2)
It should read as follows: ...
c024d3e8: mov r1, #5
c024d3f8: mov r1, #5
c024d42c: str r0, [r4, #68]
c024d430: str r1, [r4, #72]
c024d434: str ip, [r4, #76] @ data_ready: 1
Click to expand...
Click to collapse
Found this online, fix made by KUDZUS.
This is one fix.. The other one I found on XDA and was a .ko file. But i'm not sure if that was phone-specific or for all Gingerbread roms.
elot01 said:
Since yesterday there is a fix for the Compass problem in the GB rom's
It is a new kernel from snq and works for (at least) most GB rom's and probably all GB rom's.
I have not had time to try it, but in most rom threads there are people who have tried it and it works!!!!!
The fix can be found here:
http://forum.xda-developers.com/showthread.php?t=1039004
If you want the flashable version, you can find it on the line with this text (on the previous page link):
or click on the link below:
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1039004&v=1&libid=1306265553578&out=http%3A%2F%2Fdl.dropbox.com%2Fu%2F13432479%2Fmsm-2.6.35-bravo-GB%2Fg308ba26%2Fv04_to_v05-img-upd-flash.zip&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D628%26order%3Ddesc%26page%3D2&title=%5BKERNEL%5D%5BGB%2FSENSE%5D%202.6.35.10%20%5Bv05%5D%20%7C%20OC1152%20%7C%20LZMA%20%7C%20COMPASS%20%7C%20fixes%20%2Baddtl%20modules%20-%20xda-developers&txt=here
Have fun with it. I will when i have time to flash it
Click to expand...
Click to collapse
Plus I have NO idea how to flash this.
This fixes are for Desire.
I have Gio and after update 2.3.3 have compass problem too.
c20h25n3o said:
Found this online, fix made by KUDZUS.
This is one fix.. The other one I found on XDA and was a .ko file. But i'm not sure if that was phone-specific or for all Gingerbread roms.
Plus I have NO idea how to flash this.
Click to expand...
Click to collapse
applied this using recovery mode on S5660XXKQ3 (2.3.4).
does not work
It's really bizarre a problem that has been known for 2 month still hasn't been fixed.
It's a pity the Desire fix doesn't apply to all Gingerbread phones.
Time Google wakes up and fixes this, too bad the bugtracker has so many different mentions of it. Would have been better if everyone replied to the same one (issue 16741).
It still doesn't have an owner.
probably a bug fixed in version 2.3.4
http://forum.xda-developers.com/showpost.php?p=16170963&postcount=249
Hi
Code: *#*#2663#*#*
TSP Phone: 03
TSP IC: 2
HW: 1
TSP IC version 9 compass is working properly, my version is 2, if anyone knows how to do update to 9?
After pressing update several times, i have 09 now and still nothing works.
Blegh

[Q] HTC Incredible S + Accessory Development Kit (ADK)

Hi XDA.
I am new to this forum but have been working with Android devices and application development for about a year.
Recently I switched phone and bought the HTC Incredible S.
Besides of the phone development I have an electronics consultancy company doing different development jobs and electronics hardware reviews.
This week we got the Arduino MEGA ADK to review but I am unable to install the DemoKit application on my phone.
This is the log from Eclipse:
Code:
Installation error: INSTALL_FAILED_MISSING_SHARED_LIBRARY
E/PackageManager(1448): Package com.google.android.DemoKit requires unavailable shared library com.android.future.usb.accessory; failing!
This seems like a problem regarding the missing Google API on the phone. Though the phone is currently running Android 2.3.5 with Kernel version 2.6.35.9.
After a Google search it seemed like the Google API was first included in the kernel version at and above 2.6.35 - but then why doesn't it work.
My question is if HTC have removed this from the Kernel?
And what can I do to get the Google API to my phone so I can use it with the ADK?
Best Regards
Thomas Jespersen
you are missing 2 library's:
android.hardware.usb.accessory.xml sould be placed in /system/etc/permissions/
and
com.android.future.usb.accessory.jar sould be placed in /system/framework/
you can extract them out of an up to date ported sense rom of a htc sensation.
I made an update package for that problem but i can't share the link here because I do not have posted enough post to do so.
I will try to PM the link to you.
Tell me if it works, then I know that i can buy a HTC incredible s for my development.
Hydergine said:
you are missing 2 library's:
android.hardware.usb.accessory.xml sould be placed in /system/etc/permissions/
and
com.android.future.usb.accessory.jar sould be placed in /system/framework/
you can extract them out of an up to date ported sense rom of a htc sensation.
I made an update package for that problem but i can't share the link here because I do not have posted enough post to do so.
I will try to PM the link to you.
Tell me if it works, then I know that i can buy a HTC incredible s for my development.
Click to expand...
Click to collapse
Thanks, I will be waiting for your PM.
Currently my phone isn't Rooted, but I would definitely do that if it is necessary to install this fix, so I can do the ADK development with it.
ADK
Indeed your phone needs to be rooted and have Clockworkmod installed.
As far as I know it is not hardware or firmware specific since it worked on my htc HD2 an on my HTC hero(partly). I could install the demokit.apk and it would not crash since there was no support in my kernel it could not communicate with my arduino.
Since my HD2 and my hero both run an old kernel and flashing other kernels did not work out very well I was forced to buy a nexus S (yesterday).
But since your phone has the 2.6.35 kernel and 2.3.5 from stock I think this could be the solution.
You could try to check if your kernel supports the ADK first, because you are not rooted and you maybe do not want to root your phone if it does not work afterwards.
If you have got the arduino part up and running you could try this:
#include <Max3421e.h>
#include <Usb.h>
#include <AndroidAccessory.h>
Code:
AndroidAccessory acc("Google, Inc.",
"DemoKit",
"DemoKit Arduino Board",
"1.0",
"h t t p : / / w w w DOT android DOT c o m ",
"0000000012345678");
void setup();
void loop();
void setup()
{
Serial.begin(115200);
Serial.print("\r\nStart");
acc.powerOn();
}
void loop()
{
byte msg[3];
if (acc.isConnected()) {
Serial.print("Accessory connected. ");
int len = acc.read(msg, sizeof(msg), 1);
Serial.print("Message length: ");
Serial.println(len, DEC);
}
delay(100);
}
Change the "DOT" to "." and remove the [spaces] in the above otherwise I could not post this because of that "10 posts rule"
Just paste this in an empty skech and upload. The extra libraries are easy to find. Even if you are using the arduino 2009 or the arduino uno the custom files are also pretty easy to find.
The serial monitor schould say:
Code:
Start
Device addressed... Requesting device descriptor.
found possible device. swithcing to serial mode
device supports protcol 1
Device addressed... Requesting device descriptor.
found android acessory device
config desc
interface desc
if the serial monitor dislpay's something like this:
Code:
Start
Device addressed... Requesting device descriptor.
found possible device. swithcing to serial mode
Data packet error: 5could not read device protocol version
I would seriously consider buying another phone because the above was what i was getting with my HD2 on every available kernel and rom. I have been wasting my time since december.
As you see after all I had to buy an other phone after all.
I hope this helps
hi
You never get HD2 to use ADK?
i bought an arduino mega adk and i want to use it..
i don't have money to buy a new phone...
any advice? thanks
What is your current phone?
I have seen a google G1 working with ADK, i would sugest to maybe buy a second had phone that has 2.3.4 or higher on stock rom. For instance my mom's samsung galaxy mini can handle ADK on stock rom and I bought it for her Christmas for 100€, new in the store. So I think you can pick up a second hand one for a decent price (like 60€) maybe that could be the solution.
If you are going to buy a phone and you are not sure if it works with ADK take your laptop with you and use the test program that I mentioned in my last post, if the software doesn't recognize the phone you can still walk away from it.
I would really not recommend to start messing around with kernels and the library's for me it was a pain in the ass. If I would have worked all the hours that I have spend messing around, I could have bought a new HTC sensation.
hi
How Bad i can't use my HD2 with ADK..
well, i can't pay for an expensive phone but i can do and efford to buy some other phone i like HTC Sensation xl, or Motorola Atrix 2, but they are a expensive for me.. do you know if they work with ADK? other option can be a galaxy tab with 3.1 or motorola Xoom.. but i want a phone with ADK.
i haven't try my hd2 with kernel 2.6.35 with the sketch that you post.. so i'll give it a try and extract the files that someone mentioned i found them in my actual ROM..
i know it's difficult but maybe i get them to work.. thanks
htc sensation xl
I know for shure that a htc sensation xl because my girlfriend has one and I did try some stuff with that one since my hd2 wasn't compatible with ADK. I have heard people having trouble with ADK on samsung tablets so if youre are going to buy one be sure to test it before u pay for it.
Hydergine said:
you are missing 2 library's:
android.hardware.usb.accessory.xml sould be placed in /system/etc/permissions/
and
com.android.future.usb.accessory.jar sould be placed in /system/framework/
you can extract them out of an up to date ported sense rom of a htc sensation.
I made an update package for that problem but i can't share the link here because I do not have posted enough post to do so.
I will try to PM the link to you.
Tell me if it works, then I know that i can buy a HTC incredible s for my development.
Click to expand...
Click to collapse
I have now tested this on a stock but rooted ROM with 2.3.5, and 2.6.35 kernel, installed using Clockworkmod - and unfortunately it didn't work.
It gave me the complete same error as before I installed the files (*.usb.accessory.*).
Thank you anyways. I will be trying some different ROMs today to see which of them supports the ADK. Though I will be trying the Sense ones as I would like to keep using Sense.
You are right my explanation was not clear enough, the kernel needs to be compiled with the right flags set. Some developers take all the options but most of them just set the flags needed for the rom to run.

ZTE Grand X V970M Development

Hi all! ^^.
You guys might have (or not) noticed that ZTE has been developing some cool phones lately. This time it's the ZTE Grand X V970M. Here in Venezuela it's a big boom, running out of stock mere hours after arriving in a store, due to its cheap price and capabilities.
I've had Motorola Defy and HTC Magic before and even though this ZTE doesn't feel as heavy or "sturdy" as those phones, it's blazing fast and features ICS already, so it's pretty awesome, not to mention a nice GPU. It also features a MK6577 SoC, kind of rare in the Android world as I can't seem to find any CM/AOSP/AOKP/Stock compilation guide or ROM .
Small review aside, I'm not asking for XDA to make a sub-forum for the Grand X series (though if XDA does it would be awesome, there's a big community building up on facebook for development and such), but making a single-thread-has-them-all isn't a bad idea for the meanwhile, I guess.
The point of this thread is to contain information on how to develop for the V970M: ROM cooking, kernel compiling, etc. aswell to find out WTF did ZTE include in the phone software, such as custom apps, build.prop settings, you know, to dissect and discover what can we modify on this device so it performs even better. Well, that's the essence of hacking isn't it? to get more knowledge and make everything work in a customized way?
I will start with a list of non-common APKs I found in the stock ROM (RET-VE-QB128D-P175A20V1.0.0, the most up-to-date and stable yet), as there are some I don't know what is their purpose, it would be a good idea to have a dictionary of sorts.
You guys can help by providing links to ROMs, cool stuff, apps, hardware info that could be useful, etc so we can at least get some concise and good info for when XDA makes us a sub-forum (yay!, right? XD).
Anyways, time to reserve a few posts, let's have fun developing! ^^
- DARKGuy
Guides, FAQs and CUSTOM ROMS
Real useful guides + custom ROM by bgcngm! -> http://forum.xda-developers.com/showthread.php?t=1856578
HOWTOs
Unpack system.img (or any other .img) from the ZTE stock ROMs (says it's for SGS but it works for ZTE, just rename system.img to system.ext4.img and there you go)
Porting CWM Recovery to MT6577 phones (they "work" but you can only scroll using volume keys and menu. No other button does an action so it's kinda useless but good tutorial and know-how nonetheless)
Porting CWM Touch Recovery to MT6577 phones (I haven't tested this one yet. Since it's based on Lewa's I'd dare to say it works as Lewa's stock one works pretty good so my opinion is based on that
Development
ZTE Kernel Source Code (Tegra2 only!): http://support.zte.com.cn/support/news/NewsDetail.aspx?newsId=1002402
Info
"Unknown" APK files in /system/app:
Code:
ActivityNetwork.apk = ???
ArabicPack.apk = Arabic lang pack?
AtciService.apk = ???
BackupRestoreConfirmation.apk = Shows up when you activate a backup/restore operation, it seems, according to Bin4ry's root script as it invokes a function which does that.
CangjieQwertyPack.apk = Chinese lang pack?
CDS_INFO.apk = ???
CellConnService.apk = ???
ChsHandWritePack.apk = Chinese lang pack?
ChsPack.apk = Chinese lang pack?
ChtPack.apk = Chinese lang pack?
dm.apk = ???
EngineerCode.apk = MediaTek Eng/Debug APK?
EngineerMode.apk = MediaTek Eng/Debug APK?
EngineerModeSim.apk = MediaTek Eng/Debug APK?
fota_zte.apk = OTA Updates?
FrenchPack.apk = French lang pack?
Galaxy4.apk = Live wallpaper it seems
GMS_Maps.apk = Google Maps
InternalEngineerMode.apk = MediaTek Eng/Debug APK?
LatinImeDictionaryPack.apk = Is this standard from Android?
LocationEM.apk = ???
MediaTekLocationProvider.apk = MediaTek GPS-related app?
MobileLog.apk = ???
ModemLog.apk = ???
MTKAndroidSuiteDaemon.apk = MediaTek Eng/Debug APK?
MtkBt.apk = MediaTek Eng/Debug APK? (Bluetooth?!)
MTKThermalManager.apk = MediaTek APK?
MtkVideoLiveWallpaper.apk = MediaTek APK?
MtkWeatherProvider.apk = MediaTek APK?
MtkWeatherSetting.apk = MediaTek APK?
MtkWorldClockWidget.apk = MediaTek APK?
Omacp.apk = ???
PartnerBookmarksProvider.apk = ZTE bookmarks?
Phonesky.apk = Google Play Store (wtf with this name? lol)
PortugueseBrPack.apk = Portuguese lang pack?
PortuguesePtPack.apk = Portuguese lang pack?
RussianPack.apk = Russian lang pack?
SDCardUpdate.apk = Enables updating through SDCard, a-la Huawei?
SharedStorageBackup.apk = ???
SmsReg.apk = ???
SpanishPack.apk = Spanish lang pack. Does not seem to contain Spanish dictionary for LatinIME :/
Stk1.apk = SIM 1 SimToolkit modified APK, it seems
Stk2.apk = SIM 2 SimToolkit modified APK, it seems
StkSelection.apk = Default SimToolkit app selector. Seems to select default SIM for making calls/SMS/etc.
VpnDialogs.apk = Standard from Android?
YGPS.apk = What is this? there's another GPS APK in here, what does it do?
Aaaaand reserved!
darkguy2008 said:
Development
ZTE Kernel Source Code (!): http://support.zte.com.cn/support/news/NewsDetail.aspx?newsId=1002402
Click to expand...
Click to collapse
Just one note: this is the kernel source code for ZTE GrandX Tegra2 based, not for the MT5677 based V970. It's not useful for any development of V970 / V970M.
Moreover... you have posted the link to my thread and stated it as a guide. That's much more than a guide as it includes custom ROMs for V970. Please edit your post.
bgcngm said:
Just one note: this is the kernel source code for ZTE GrandX Tegra2 based, not for the MT5677 based V970. It's not useful for any development of V970 / V970M.
Moreover... you have posted the link to my thread and stated it as a guide. That's much more than a guide as it includes custom ROMs for V970. Please edit your post.
Click to expand...
Click to collapse
Hi Bruno! good to see you here! ^^
I've read that note about the kernel before, but it has me thinking since I read it... are you sure it can not help in *any* way to at least help develop a custom kernel or something? I mean there must be stuff we can use/grab from it, no?
Well, I considered your thread a guide because it answers FAQs and provides links to tutorials and such including your roms, though it's kind of mixed, I agree it was my fault, sorry! I've edited it accordingly, hope it's alright now!
Btw I sent you a PM, did you get some time to read it? hehe. Greets!
False alarm nevermind lol xD
do you a great CUSROM for this Phone?

New L09C432B360 Working for Charles

Good evening guys, noticing that the code provided in this this thread does not work (recognizes a personalized version of the firmware 1,3x GB not the right one of 2,2x GB) anyone has the right one to update from B131?
Anyway i noticed that there is a new update since few days that aims to correct battery drain etc if you got the code of it, you're welcome. Noticing that the code provided in this thread does not work (it jumps flashing from a 2xx MB file).
Thanks in advance to anyone will provide codes for our L09 version.
topgraphics said:
Good evening guys, noticing that the code provided in this this thread does not work (recognizes a personalized version of the firmware 1,3x GB not the right one of 2,2x GB) anyone has the right one to update from B131?
Anyway i noticed that there is a new update since few days that aims to correct battery drain etc if you got the code of it, you're welcome. Noticing that the code provided in this thread does not work (it jumps flashing from a 2xx MB file).
Thanks in advance to anyone will provide codes for our L09 version.
Click to expand...
Click to collapse
Hi, this worked for me today. If not for you try a dload method factory reset to B131 before process or double check your charles method.
B360 :
{
"status": "0",
"autoPollingCycle": "1",
"components": [{
"name": "FRD-L09C432B360",
"version": "FRD-L09C432B360",
"versionID": "73856",
"description": "FRD-L09C432B360 (2017/01/18)",
"createTime": "2017-01-18T01:57:51+0000",
"url": "http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v73856/f1/"
}]
}
Click to expand...
Click to collapse
B360bis :
{
"status": "0",
"autoPollingCycle": "1",
"components": [{
"name": "FRD-L09C432B360",
"version": "FRD-L09C432B360",
"versionID": "74864",
"description": "FRD-L09C432B360 (2017/02/06)",
"createTime": "2017-01-18T01:57:51+0000",
"url": "http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v74864/f1/"
}]
}
Click to expand...
Click to collapse
None of those codes work. Currently I downgraded from B360 to B131. And got stucked.
Codes you provided are the same I listed on the thread post. Thanks anyway.
topgraphics said:
Good evening guys, noticing that the code provided in this this thread does not work (recognizes a personalized version of the firmware 1,3x GB not the right one of 2,2x GB) anyone has the right one to update from B131?
Anyway i noticed that there is a new update since few days that aims to correct battery drain etc if you got the code of it, you're welcome. Noticing that the code provided in this thread does not work (it jumps flashing from a 2xx MB file).
Thanks in advance to anyone will provide codes for our L09 version.
Click to expand...
Click to collapse
When refreshing your updater, click the menu and choose 'Download latest full package' option. This should give you correct packages.
Sent from my FRD-L04 using XDA Labs

Categories

Resources