Installed Beanstalk yesterday, and today my device doesnt find any simcard what can i do? i did a nandbackup, but i get in a boot loop while restoring to it, any advice? (my device is warranty void 0x1) thanks
big_b0sss said:
Can you not flash stock rom via odin?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Trying that now, i managed to get the backup to load, and it found my simcard, but i had no network :/ im flashing "N9005XXUENB4_N9005HTSENB3_HTS" which is the Swedish 4.4.2 stock rom. ill try my best to fix this, if this doesn't work, i might have to smash my phone and get a new one xD bought it this sunday ^^ luckily i got a s3 as backup phone xD
Unfortunately this is what i got out of it:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005HTSENB3_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
any idea?
[SOLVED!]
The problem is now solved (i think)
[SOLUTION:]
Flashed "N9005XXUENB4_N9005PRTENB1_PRT" which is the Poland 4.4.2 stock rom, noticed i didn't have to unlock my simcard and that i lost my connection all the time, so basically what i did after that was removing the pincode to my simcard and now, it's working like a charm (for now).
mattish.91 said:
Installed Beanstalk yesterday, and today my device doesnt find any simcard what can i do? i did a nandbackup, but i get in a boot loop while restoring to it, any advice? (my device is warranty void 0x1) thanks
Click to expand...
Click to collapse
Can you not flash stock rom via odin?
Sent from my SM-N9005 using XDA Premium 4 mobile app
big_b0sss said:
Can you not flash stock rom via odin?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Trying that now, i managed to get the backup to load, and it found my simcard, but i had no network :/ im flashing "N9005XXUENB4_N9005HTSENB3_HTS" which is the Swedish 4.4.2 stock rom. ill try my best to fix this, if this doesn't work, i might have to smash my phone and get a new one xD bought it this sunday ^^ luckily i got a s3 as backup phone xD
Unfortunately this is what i got out of it:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005HTSENB3_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
any idea?
[SOLVED!]
The problem is now solved (i think)
[SOLUTION:]
Flashed "N9005XXUENB4_N9005PRTENB1_PRT" which is the Poland 4.4.2 stock rom, noticed i didn't have to unlock my simcard and that i lost my connection all the time, so basically what i did after that was removing the pincode to my simcard and now, it's working like a charm (for now).
Related
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUFNF4_N9005OLBFNG1_N9005XXUFNF2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please help
j0ndav3 said:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUFNF4_N9005OLBFNG1_N9005XXUFNF2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please help
Click to expand...
Click to collapse
Download and install a custom rom here (AOSP or Stock and etc). Assuming you have a custom recovery.
Graffiti Exploit said:
Download and install a custom rom here (AOSP or Stock and etc). Assuming you have a custom recovery.
Click to expand...
Click to collapse
I cannot boot in recovery mode. What can I try?
I don't know what to do.. (
j0ndav3 said:
I cannot boot in recovery mode. What can I try?
I don't know what to do.. (
Click to expand...
Click to collapse
From what version did you come from exactly? You can't flash an older one from your current one.
Install a custom recovery through Odin. Download one here at the forums.
Graffiti Exploit said:
From what version did you come from exactly? You can't flash an older one from your current one.
Install a custom recovery through Odin. Download one here at the forums.
Click to expand...
Click to collapse
from 4.4.2 but i tried to install a same 4.4.2 version with download booster and kids mode that's why i tried to manual update my note 3 n9005
sorry im a noob.. thanks..
j0ndav3 said:
I cannot boot in recovery mode. What can I try?
I don't know what to do.. (
Click to expand...
Click to collapse
Do you can boot in Download mode?
porcelana said:
Do you can boot in Download mode?
Click to expand...
Click to collapse
Yes i can boot in Donwload mode..
Is it possible to update my 4.4.2 to 4.4.2 with download booster? because to my previous version, there's no download booster that's why I tried to install that firmware..
j0ndav3 said:
Yes i can boot in Donwload mode..
Is it possible to update my 4.4.2 to 4.4.2 with download booster? because to my previous version, there's no download booster that's why I tried to install that firmware..
Click to expand...
Click to collapse
Is your new image from a same region as your old one ?
If you had a let's say UK Version of firmware, you cannot flash with a Hong Kong one. That's when problems start.
Don't worry, this is not a big deal. We just need more info.
having same problem here.. currently stuck with SweetRom 4.4.2 v20 with video camera not working!
Colide said:
Is your new image from a same region as your old one ?
If you had a let's say UK Version of firmware, you cannot flash with a Hong Kong one. That's when problems start.
Don't worry, this is not a big deal. We just need more info.
Click to expand...
Click to collapse
I had a Hongkong version then I tried to install the Philippine version I think that's the problem. Thanks I hope I can fix this
)))))))))
Colide said:
Is your new image from a same region as your old one ?
If you had a let's say UK Version of firmware, you cannot flash with a Hong Kong one. That's when problems start.
Don't worry, this is not a big deal. We just need more info.
Click to expand...
Click to collapse
Thanks Colide! I already fixed my phone! Thanks for your tips! I really appreciate it! many thanks!
With my LITTLE knowledge on how to flash an image with odin i tried to flash the latest 5.0 from sammobiles.
i get the following
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOB6_N9005XEOGBOA4_N9005XXUGBOA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Ext4)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
after this i get a screen where it says "Firmware upgrade encountered an issue"
Please help !
p.s i do not know the original firmware of the phone.
Read the faqs and guides first .
Flash another firmware .
I am trying to flash a stock rom on my Note 4 Exynos Version, with odin I have tried the latest version as well as some older ones. I have tried flashing both kit kat & lollipop but always get the same error. I have usb debugging ticked.
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
why is this happening?
Ta
Any help guys?
@home said:
Any help guys?
Click to expand...
Click to collapse
you are facing a locked bootloader as we all are (both exy and snap) the only solution to fix your bootloop is to install apps like phone info then find out what your phone PDA version is then find the exact PDA from Sammobile or if you you are Having an 910C flash latest COJ5 rom or if you are on 910H try installing COJ4 rom (just download and install the latest frimware from sammobile or ... and you will be just fine )
ArmanFGT said:
you are facing a locked bootloader as we all are (both exy and snap) the only solution to fix your bootloop is to install apps like phone info then find out what your phone PDA version is then find the exact PDA from Sammobile or if you you are Having an 910C flash latest COJ5 rom or if you are on 910H try installing COJ4 rom (just download and install the latest frimware from sammobile or ... and you will be just fine )
Click to expand...
Click to collapse
I followed your instructions and this is what I'm getting. Now what I need to do further? Previously I was using Sixperience ROM.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> modem.bin
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
sirius_gamer said:
I followed your instructions and this is what I'm getting. Now what I need to do further? Previously I was using Sixperience ROM.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> modem.bin
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
well , i dont really know what the XmitData_write is , as i havent seen it since my s4 (everything was fine) ..
i think wiping would solve the Prob...
or maybe USB cable or odin version (+drivers)
2. if nothing works around ... try using KIES emergency updating ... its always the sweety
odin3 v 3.12
i have same problem;
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
sdstc said:
odin3 v 3.12
i have same problem;
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
problem is using UN-OFFICIAL USB CABLE
use FACTORY CABLE FIXes problem
sdstc said:
problem is using UN-OFFICIAL USB CABLE
use FACTORY CABLE FIXes problem
Click to expand...
Click to collapse
@sdstc is right you can fix __XmitData_Write with changing the cable
i used an original sammy cable and it didnt work. than i used another sammy cable and then it just worked
my device was a Tab S btw no note 4 or s4
bu arada cok sagol sdstc kardes
TimurAlaskara_TR said:
@sdstc is right you can fix __XmitData_Write with changing the cable
i used an original sammy cable and it didnt work. than i used another sammy cable and then it just worked
my device was a Tab S btw no note 4 or s4
bu arada cok sagol sdstc kardes
Click to expand...
Click to collapse
i all the time face with that error and i forgot use original cable
(ne için teşekkür?)
sdstc said:
i all the time face with that error and i forgot use original cable
(ne için teşekkür?)
Click to expand...
Click to collapse
Sen olmasan telefon hala bozuktu cunku sjsjsj
help plz
sdstc said:
problem is using UN-OFFICIAL USB CABLE
use FACTORY CABLE FIXes problem
Click to expand...
Click to collapse
<OSM> Please wait..
<OSM> N910CXXS2DQG1_N910COXA2DPH1_N910CXXU1DPC1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Everything was okay, but my screen broke and then I sent it to repair it. Then it came back with another csc (AUT) and I wanted to change it by odin to the normal one (DRE), but "FAIL" appears. Could somebody please help?
Here´s the data:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXS1CQD1_G900FDRE1CPJ2_G900FXXS1CQA3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> NON-HLOS.bin
<ID:0/007> rpm.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> tz.mbn
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Ext4)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
tm60405 said:
Everything was okay, but my screen broke and then I sent it to repair it. Then it came back with another csc (AUT) and I wanted to change it by odin to the normal one (DRE), but "FAIL" appears. Could somebody please help?
////EDIT: okay, just took a AUT firmware and it works (idc if i dont have DRE csc anymore lol):laugh::laugh::laugh::laugh::laugh:////
Click to expand...
Click to collapse
: (Samsung Galaxy s5 SM-G900F) i use android 5.0 in this file... Help i really need my phone but when i try to flash this happen:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BOC7_G900FTEN1BOB1_G900FXXU1BOC7_HOME.tar.MD5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
help me now my phone has a wierd yellow triangle with a !. it sais firmware update encountered an issue please sellect recovery in kies and try again??
CarlJohnson.CJ said:
: (Samsung Galaxy s5 SM-G900F) i use android 5.0 in this file... Help i really need my phone but when i try to flash this happen:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BOC7_G900FTEN1BOB1_G900FXXU1BOC7_HOME.tar.MD5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
help me now my phone has a wierd yellow triangle with a !. it sais firmware update encountered an issue please sellect recovery in kies and try again??
Click to expand...
Click to collapse
Do you have original cable (biggest problems are caused by bad cables), on witch version of android where you before ?