Related
[ROM][STOCK] Samsung Galaxy S 4.2 WIFI YP-GI1CW ->CODE GI1XXLF1
With the full firmware available, I rooted it simply unpacking factoryfs.img using sgs2toext4 and ext4_utils, injecting SU binary + SuperSU and after repack it, I made a tarball and flashed it throught Odin 3.04.
After that I've installed from GPlay the busybox installer.
Rooted factoryfs.img
Flash using Odin 3.04.
Important: This is only for YP-GI1CW version on XXLF1 !
This is working very good for me, but use at your own risk.
Thanks to zebluk and alice90, who were able to get the first root on this device.
Ozelot64 said:
[ROM][STOCK] Samsung Galaxy S 4.2 WIFI YP-GI1CW ->CODE GI1XXLF1
With the full firmware available, I rooted it simply unpacking factoryfs.img using sgs2toext4 and ext4_utils, injecting SU binary + SuperSU and after repack it, I made a tarball and flashed it throught Odin 3.04.
After that I've installed from GPlay the busybox installer.
Flash using Odin 3.04.
Important: This is only for YP-GI1CW version on XXLF1 !
This is working very good for me, but use at your own risk.
Thanks to zebluk and alice90, who were able to get the first root on this device.
Click to expand...
Click to collapse
Odin says MD5 hash value is invalid
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
MD5 hash value is invalid
CODE_GI1XXLF1_factoryfs_Rooted.md5 is invalid.
End...
edit: works aufter add .tar to the filename
ChaosChris said:
Odin says MD5 hash value is invalid
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CODE_GI1XXLF1_factoryfs_Rooted.md5 is invalid.
<OSM> End...
edit: works aufter add .tar to the filename
Click to expand...
Click to collapse
I don't know why there is this change in the filename, my original is CODE_GI1XXLF1_factoryfs_Rooted.tar.md5.....anyway, I'm reuploading the rar with the correct file inside.
Sorry for the inconvenience
ChaosChris said:
Odin says MD5 hash value is invalid
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CODE_GI1XXLF1_factoryfs_Rooted.md5 is invalid.
<OSM> End...
edit: works aufter add .tar to the filename
Click to expand...
Click to collapse
Ozelot64 said:
I don't know why there is this change in the filename, my original is CODE_GI1XXLF1_factoryfs_Rooted.tar.md5.....anyway, I'm reuploading the rar with the correct file inside.
Sorry for the inconvenience
Click to expand...
Click to collapse
Done, link updated in OP
@ChaosChris: could you please delete the old links in "quote" of your post ? Thx
AW: [ROM][STOCK+ ROOT] Samsung Galaxy S 4.2 WIFI YP-GI1CW rooted factoryfs.img GI1XX
Ozelot64 said:
Done, link updated in OP
@ChaosChris: could you please delete the old links in "quote" of your post ? Thx
Click to expand...
Click to collapse
Yes no Problem
Gesendet von meinem Nexus S mit Tapatalk 2
Hey Ozelot64, your link ti the rooted factory.fs is down.
404: Page not found – the page http://goo.gl/AC4 does not exist.
If you typed in or copied/pasted this URL, make sure you included all the characters, with no extra punctuation.
Click to expand...
Click to collapse
Whenever I use SP_Flash_Tools v3.xx on my HDC Note, I received the following error messages ..
1 Error message – BROM ERROR : S_UNSUPPORTED_VER_OF_DA (1022)
[DA] DA binary file contains an unsupported version in its header!
2 ‘Cannot initializes scatter file. Please check the name is legal’.
The above messages appears on different version of the SPFlash Tools.
What went wrong?
First of all see the case from @shazzl - HERE. Brick i9205 solved.
We must have our debrick.img on extSdCard to caution if we brick our phone. This is made from pit.file like we see on updater_script from the .zip (partition mmcblk0).
Download the .zip attached, flash it in your preferred recovery (CWM or TWRP) and it will create the dump file needed for this debrick method from @KAsp3rd See it HERE. Thanks @[B]KAsp3rd[/B]
Once you have flashed it you will find a file called debrick.img on your internal sdcard. It should be 128MB in size. Copy it to extSdCard and to Your Pc.
For a I9205 bricked We can use the method from @KAsp3rd, used by @shazzl. Thanks by Your guide.
I created already my Sdcard prepared by Win32DiskImager from Windows option.
See also THIS help from @DocHoliday77. Thanks @DocHoliday77.
Replace T999 by Your phone name.
Make that, take care.
PS: If You upgrade from 4.2.2 to 4.3 make new debrick.img. The contents inside pit.file can have differences.
EDIT: New HARD BRICK fixed on one Note 3 N9005 4.4.2 Kitkat. Whit success, see it HERE.
Replaced the titre to:
[HARD-BRICK Fixed] I9205 Make your debrick.img and have it on extSdCard by security
Thaks for this unbrick solution. Now we can root and flash away
so what exactly do i need to put on my external sd card I am confused....
magicninja said:
so what exactly do i need to put on my external sd card I am confused....
Click to expand...
Click to collapse
It's simple.
- Put the .zip on Sdcard
- By custom recovery flash it.
- You have on internal Sdcard the debrick.img file.
- Copy it to extSdCard to be safe.
It's all.
Hi..how can i make this debrick.img file out of the .pit file for the i527m mega or get the partial sys dump files, as it does not explain on how to make the partial sys dump files..could somebody shed some light on this part..thanks.
starmaster10 said:
Hi..how can i make this debrick.img file out of the .pit file for the i527m mega or get the partial sys dump files, as it does not explain on how to make the partial sys dump files..could somebody shed some light on this part..thanks.
Click to expand...
Click to collapse
Just flash the zip file from recovery. That's all you need to do. Then use windiskimage to write the image to a sdcard.
Silesh.Nair said:
Just flash the zip file from recovery. That's all you need to do. Then use windiskimage to write the image to a sdcard.
Click to expand...
Click to collapse
Hi..that part i knew, it is making the partial system dump files from the .pit file is were i am kinda lost on..unless it is not made from the .pit file, the META-INF folder and dd file...thanks for replying.
The debrick.IMG is the dump file.
Sent from my GT-I9205 using Tapatalk
Silesh.Nair said:
The debrick.IMG is the dump file.
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
I am still confused then as i thought you use the I9200-Partial_Sys_Dump_for_debrick or I9205-Partial_Sys_Dump_for_debrick to flash with the recovery to get the debrick.img file, but how do you make these I9200-Partial_Sys_Dump_for_debrick or I9205-Partial_Sys_Dump_for_debrick files that have this META-INF folder (with the update-binary and updater-script are in) and dd file inside the zip file, in my case for the i527m..thanks. :good:
pit file location ( mmcblk0 ) is the same for all samsung phones afaik.
Don't get confused by the zip file names. All it does is this.
run_program("/tmp/dd", "if=/dev/block/mmcblk0", "of=/sdcard/debrick.img", "bs=1M", "count=128");;
Silesh.Nair said:
pit file location ( mmcblk0 ) is the same for all samsung phones afaik.
Don't get confused by the zip file names. All it does is this.
run_program("/tmp/dd", "if=/dev/block/mmcblk0", "of=/sdcard/debrick.img", "bs=1M", "count=128");;
Click to expand...
Click to collapse
Okay kinda getting it..what program do i use to run that command, do i use the shell terminal emulator program on the phone for this or can i use the I9205-Partial_Sys_Dump_for_debrick zip file to make my debrick.img file for my i527m as i just tried it and it made a debrick.img file, but will it work for the i527m mega.
starmaster10 said:
Okay kinda getting it..what program do i use to run that command, do i use the shell terminal emulator program on the phone for this or can i use the I9205-Partial_Sys_Dump_for_debrick zip file to make my debrick.img file for my i527m as i just tried it and it made a debrick.img file, but will it work for the i527m mega.
Click to expand...
Click to collapse
I tried on Terminal Emulator, not work for me.
The original Mod is This: http://forum.xda-developers.com/showpost.php?p=45725480&postcount=45 Thanks @DocHoliday77
After have looked the updater_script from .zip I only replace the name T999 to I9205 or N9005 or I9195, but the Mod is always the same:
package_extract_file("dd", "/tmp/dd");
set_perm(0, 0, 0777, "/tmp/dd");
ui_print("Data Dump running...");
run_program("/tmp/dd", "if=/dev/block/mmcblk0", "of=/sdcard/debrick.img", "bs=1M", "count=128");;
delete("/tmp/dd");
PS: You can rename Your to i527m-Partial_Sys_..... no problems, must work also. Or use the T999... is same.
ValenteL said:
I tried on Terminal Emulator, not work for me.
The original Mod is This: http://forum.xda-developers.com/showpost.php?p=45725480&postcount=45 Thanks @DocHoliday77
After have looked the updater_script from .zip I only replace the name T999 to I9205 or N9005 or I9195, but the Mod is always the same:
package_extract_file("dd", "/tmp/dd");
set_perm(0, 0, 0777, "/tmp/dd");
ui_print("Data Dump running...");
run_program("/tmp/dd", "if=/dev/block/mmcblk0", "of=/sdcard/debrick.img", "bs=1M", "count=128");;
delete("/tmp/dd");
PS: You can rename Your to i527m-Partial_Sys_..... no problems, must be work also. Or use the T999... is same.
Click to expand...
Click to collapse
Thank you for clearing that up as I thought I could just rename the file as it is the same for all samsung phones..
Sent from my SGH-I527M Mega 6.3
please help
@ValenteL, here is the thread where I've exposed my problems.
To make short, my phone harbricked, @Silesh.Nair drove me to solution (by you and @shazzl). But I stuck in Odin with this : I MISS pit file. Could you help me please? Where can I found this file, and what to do with?
I quote me :
so I've test with your file but doesn't work. I've also tried with the one in the thread , nothing too.
In fact the phone boot but not totaly as it's supposed to do. I press power button then vibrate and then the logo doesn't appear but there is this screen :
Code:
[COLOR="Lime"]BOOT RECOVERY MODE[/COLOR]
CHECK BOOT PARTITIONS. .
COPY FROM T-FLASH. .
WRITE 139008 sectors. .
[COLOR="Red"]FLASH WRITE FAILURE[/COLOR]
ddi : mmc_read failed
[COLOR="red"]ODIN MODE[/COLOR]
PRODUCT NAME: GT-I9205
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
[COLOR="Gray"]QUALCOMM SECUREBOOT: ENABLE
BOOTLOADER AP SWREV: 1[/COLOR]
----------------------------------------
I can't go into any mode (download or recovery), just boot to the screen above.
I've tried to "ODIN" a firmware ( I9205XXUAMG7_I9205XEFAMG1_I9205XXUAMG5_HOME.tar.md5 that I had on pc ) : when plug phone it tells me "added" with blue item (so normal no ? ), *.md5 = good analysis. But when I click on start it tells me that I miss PIT file
Click to expand...
Click to collapse
Exactly what says by odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9205ZHUCML4_I9205ZZHCML4_I9205ZHUCML4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
and on phone it writes this following previous tag :
Code:
MMC: mmc_read fail
[COLOR="Red"]ODIN : flash read failure[/COLOR]
Mukiai said:
@ValenteL, here is the thread where I've exposed my problems.
<OSM> I9205ZHUCML4_I9205ZZHCML4_I9205ZHUCML4_HOME.tar.md5 is valid.
Click to expand...
Click to collapse
Hi @Mukiai
I have here my pit file attached-2 created whit cmd attached-1 for I9205, and I made it on XX Rom. But You try to flash one ZH, differente regions. I don't know if it work.
You have also the PIT analyzes where you see the inside from Pit file. (Identifier is the partition number).
I never tried this, but if You need try on Odin in PIT. Try this at Your responsibility, alright?
I hope this help to solve Your problem.
PS: The cmd attached-1 is only to devices until 16 GB.
EDIT: I retourned to Your post and You have There is no PIT partition. It seem that is the partition that not exist and not the Pit file.
Try that but if not work may be the partition must be created. For that I unknown how we must make. May be using a debrick.img???
I had a same case on N8000 about partition efs deleted, it must been created before include the efs files. Have HERE my case. I don't know if some Dev's can help like this example for efs on Post #4. May be @Silesh.Nair can help. Thanks.
You have here my debrick.img : https://meocloud.pt/link/a4d65b2a-2a55-4983-8b69-446b137a1d93/I9205-debrick.img.tar/
ValenteL said:
Hi @Mukiai
I have here my pit file attached-2 created whit cmd attached-1 for I9205, and I made it on XX Rom. But You try to flash one ZH, differente regions. I don't know if it work.
You have also the PIT analyzes where you see the inside from Pit file. (Identifier is the partition number).
I never tried this, but if You need try on Odin in PIT. Try this at Your responsibility, alright?
I hope this help to solve Your problem.
PS: The cmd attached-1 is only to devices until 16 GB.
EDIT: I retourned to Your post and You have There is no PIT partition. It seem that is the partition that not exist and not the Pit file.
Try that but if not work may be the partition must be created. For that I unknown how we must make. May be using a debrick.img???
I had a same case on N8000 about partition efs deleted, it must been created before include the efs files. Have HERE my case. I don't know if some Dev's can help like this example for efs on Post #4. May be @Silesh.Nair can help. Thanks.
You have here my debrick.img : https://meocloud.pt/link/a4d65b2a-2a55-4983-8b69-446b137a1d93/I9205-debrick.img.tar/
Click to expand...
Click to collapse
Thanks,
I will try this.
@Silesh.Nair drive me to you and you drive me to him. and @shazzl help too. So normally all have to be fine.
Mukiai said:
Thanks,
I will try this.
@Silesh.Nair drive me to you and you drive me to him. and @shazzl help too. So normally all have to be fine.
Click to expand...
Click to collapse
Give me feed back about You make. I hope You safe Your Mega.
Good luck.
ValenteL said:
Give me feed back about You make. I hope You safe Your Mega.
Good luck.
Click to expand...
Click to collapse
No problem . For now i'm waiting the end of download of a cml1 firmware from sammobile. Again 1 or 2hours.
I've test with others firmware on my pc, but no luck for now.
Is my procedure good ? :
debrick.img on microsd with win32. (here the result on my sd). Then put my sd in phone , then battery, then power button.
after my phone boot on the screen I've describe in my previous post
Code:
[COLOR="Lime"]BOOT RECOVERY MODE
[.....]
[COLOR="Gray"]BOOTLOADER AP SWREV: 1[/COLOR][/COLOR]
run Odin
plug my phone ("added" with blue image)
add Pit file on PIT (tick re-partition)
add firmware on PDA (wait )
Start
Click to expand...
Click to collapse
My tries are with both Odin v3.0.7 and v3.0.9 and two different cables.
I'm waiting CML1 to try like you and @shazzl, but waiting the end of download, I've tried with CML4 and two others, no luck.
For ZHUCML4
Odin:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9205ZHUCML4_I9205ZZHCML4_I9205ZHUCML4_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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Phone:
Code:
MMC: mmc_read fail
[COLOR="Red"]PIT FAIL : TOTAL SECTORS (0)[/COLOR]
Click to expand...
Click to collapse
---------- Post added at 10:09 PM ---------- Previous post was at 09:32 PM ----------
with CML1 on odin v3.0.7
Odin :
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9205XXUCML1_I9205OXXCML2_I9205XXUCML1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone :
Code:
MMC: mmc_read fail
[COLOR="Red"]PIT FAIL : TOTAL SECTORS (0)
ODIN : flash read failure[/COLOR]
Mukiai said:
Is it normal that after use win32 item , the properties of my sd says that the size is in mb (near 16 mb are free and 47 mb are usedand capacity total 64mb : a deep hole from 16gb???? )?
Click to expand...
Click to collapse
ValenteL said:
It's normal. The sdcard have 17 partitions but the windows only see the first from 64 MB. 16 are hidden for windows.
You can see them on Control Panel / Admnistrative Tools / Computer Management / Storage / Disk Management (local) ...
and here You see the sdcard, may be F: whit 17 partitions.
Power off on Mega, put the sdcard, Power and must be something to work on it. It write the first 128 MB from emmc, pit file included. And use the guide from @shazzl .
Here I can't help more because I never had a hard brick and not make all process. I made only the sdcard to debrick and analyzed it on Pc.
Click to expand...
Click to collapse
Mukiai said:
Phone :
Code:
MMC: mmc_read fail
[COLOR="Red"]PIT FAIL : TOTAL SECTORS (0)
ODIN : flash read failure[/COLOR]
Click to expand...
Click to collapse
It is not good this. 0 sectors on PIT ???
See the guide from @shazzl to debrick:
1. If your phone only detected QHSUSB_DLOAD follow this guide.
2.1. Download Win32DiskImager
2.2 Download debrik.img thank to @ValenteL for the file.
2.3 Unzip both items and run win32diskimager
2.4 Select Image File debrick.img
2.5 Select Device ( put your sdcard in 16gb or 32bg )
2.6 Click write ( note this will format your sdcard plz backup your data )
2.7 After finish put your sdcard to your phone. you will se a magical your phone will boot.
3.1 After it boot turn off the phone and go to download mod.
3.2 Open odin and flash the stock frameware ( i flash I9205XXUCML1 )
4. After boot go to setting, more storage and format your sdcard
hello to all Users my name is Daniel
I have a LG E460 mobile phone and i need Hebrew on this model morelocale2 not work on this model sow I try to install firmware of LG E450F with the LG KDZ update tool bat no Lucky its failed give me error on The beginning
22:26:17 : Launching SW update
22:26:17 : Unpacking KDZ
22:26:36 : KDZ file extraced
22:26:51 : Files were extracted.
22:26:51 : LGMobileDL Load.
22:26:51 : Port = -1
22:26:51 : Connecting to phone
22:27:09 : Check Phone mode = 1
22:27:36 : Phone type check.......
22:28:09 : BinPath is a empty!!
22:28:09 : LoadLibrary Error(126)
22:28:11 : ===FINISHED===
Bat if i convert the same file to octopus firmware oct file and use the octopus box its work and flash the file all work good just One thing does not work the touch buttons work bat the light not turn on i need your help if you can help me with my problem how i can fix the light problem thank you for all helps
Hi everybody!
Trying to downgrade my stock KitKat V20D LG L9 II to some previous version via LG Flash Tool 2014 (tutorial http://forum.xda-developers.com/showthread.php?t=2797190) but still getting stuck:
During the flashing the progress stops at 4 % and shows "Upgrade stopped due to an error"
Tried to use various firmware from http://lg-phone-firmware.com/index.php?id_mod=37 but non was working.
I have correct drivers + reinstalled multipletimes, COM port set to 41, tried two USB cables and 2 ports, tried both in Download Mode and with running phone.
The official LG Mobile Support Tool works fine - I can reinstall latest FW via it!
Running Win7.
Anything else I should try?
I'm really desperate now, spent 5 hours with no reason.
Thanks
Lukas
just try other lg flash tool. But if begines and it randomly errors, is probably the cable/usb port/computer issues. On my pc for example on most ports randomly erorrs, rarely finishes, and on other ports, works perfectly everytime. (i do have an unfit powersuplly so ....)
Neither the older LG Flash Tool is not working for me.
And I tried 3 different cables, different ports... And I have no other computer available right now. But the errors are not random, it simply dosnt work at all.
can u post the flasher log pls.
How can i get a log from LG Flash Tool 2014?
Dont know where the log is on LG Flash Tool 2014, but try the older version in the attachement, and the log is right in the main window.
http://www.filedropper.com/lgd605olderflashandrequiredcrap
This was simple - this tool doesnt recognize my phone at all.
[R&D Test Tools Log File]
14:22:43 : Launching SW update
14:22:43 : Unpacking KDZ
14:22:52 : KDZ file extraced
14:23:55 : Files were extracted.
14:23:55 : LGMobileDL Load.
14:23:55 : Port = -1
14:23:55 : Connecting to phone
14:24:16 : PHONE WAS NOT FOUND!
14:24:18 : ===FINISHED===
Phone is on, connected in "LG Software" mode with original LG cable, COM port set to 41, USB debuggind enabled.
Ha, interesting!
In Download mode, the phone is recognized! But still not flashing, shows attached error message:
[R&D Test Tools Log File]
15:24:01 : Launching SW update
15:24:01 : Unpacking KDZ
15:24:12 : KDZ file extraced
15:25:16 : Files were extracted.
15:25:16 : LGMobileDL Load.
15:25:16 : Port = -1
15:25:16 : Connecting to phone
15:25:30 : Check Phone mode = 2
15:25:30 : Phone type check.......
15:25:30 : LGMobileDL.DLL Loading....
15:25:30 : _SetAuthMark Fail
15:25:31 : _SetAuthMark Ok : wAuthMark(65535)
15:25:31 : _DetachDLL Call
15:25:36 : _DetachDLL Call End
15:25:36 : Param : Path = C:\ProgramData\LGMOBILEAX\Phone\BIN_LGD605AT-00-V10a-EUR-XX-AUG-13-2013+0_Develop.wdb
15:25:36 : Param : moduleDir =
15:25:36 : Param : waitTime = 33000
15:25:36 : Param : UsbHighSpeed = 0
15:25:36 : Param : PhoneMode = 2
15:25:36 : Param : BinVersion = D60510A_00
15:25:36 : Param : AuthMark = 65535
15:25:36 : Call fn_StartUpgrade
15:27:17 : 3GQCT : wParam = 100, lParam = 0
15:27:17 : Step : Upgrade Error error code = 0
15:27:17 : ResetStartInfo() Call
15:27:17 : _DetachDLL Call
15:27:22 : _DetachDLL Call End
15:27:22 : FreeLibrary Call
15:27:22 : FreeLibrary Call End
15:27:22 : ResetStartInfo() Call End
15:27:22 : ===FINISHED===
Click to expand...
Click to collapse
flash the kdz in download/rescue mode. Check what drivers apear in windows device manager thing (LG modem there ?). Make sure the phone battery is full. Did u install the msxml and windows enabler? Reinstall drivers. It errores on all ports in the same place, or it starts to send data and crashes after. Run the application in "administrative mode".
Everything tried, no effect.
But I tried to flash another version of firmware - D60520c_00.kdz and it worked!
So problem is solved now, thanks for your time
EDIT:
Chm, the 20C version is also not rootable :-/
Will try another computer to make downgrade.
Second computer, totally same situation! :/
Problem is probably in the phone, not in computer config.
lukas.stepka said:
Second computer, totally same situation! :/
Problem is probably in the phone, not in computer config.
Click to expand...
Click to collapse
is the 10A u got valid ? try a different one. Also 20D (and prob 20C too) is rootable, the only problem is that u just cant install a custom boot on it.
Yes, i tried dirrefent versions, non was working.
Are they? How?
http://forum.xda-developers.com/showthread.php?t=2732311 method also was not working for me.
And I want cyanogenmode, so I need probably custom recovery, do I?
lukas.stepka said:
Yes, i tried dirrefent versions, non was working.
Are they? How?
http://forum.xda-developers.com/showthread.php?t=2732311 method also was not working for me.
And I want cyanogenmode, so I need probably custom recovery, do I?
Click to expand...
Click to collapse
for 20A-20D root: http://forum.xda-developers.com/opt...ot-l9-d605-stock-recovery-4-4-2-v20a-t2964723 , make an primary ext2/3/4 partition, boot in mormal recovery, and aplly zip (root_v2A.zip)
But if u want custom recovery u must go V10A. (unless TWRP workes installed via 20x, but i dont belive so, i use CWM so i dont know) Keep on trying different versions of 10A/computers, dont know what to say, if 1 kdz worked all should ...
OMG, of course, I was updating wrong file. Thank you, so the root is done now. First step, better than nothing.
OK, so if I want cyanogenmode, I have no chance now?
The 20C is only one KDZ which is working, older are not flashable for me. Tried different computers, cables, drivers, ports...