Related
I was running stock 4.1.1 rooted with NO cwm and I accepted the OTA undate two days ago. Now, I have SU still installed but nothing can obtain root permissions. I used Wugz toolkit to reflash su binaries through TWRP a few times and still no dice. Any thoughts?
Trickee360 said:
I was running stock 4.1.1 rooted with NO cwm and I accepted the OTA undate two days ago. Now, I have SU still installed but nothing can obtain root permissions. I used Wugz toolkit to reflash su binaries through TWRP a few times and still no dice. Any thoughts?
Click to expand...
Click to collapse
Here you go. Just follow the directions. It works fine for 4.1.2.
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
veeman said:
Here you go. Just follow the directions. It works fine for 4.1.2.
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
Click to expand...
Click to collapse
Welp, I've never actually used adb to push anything manually myself, but now is as good as time as any to try it. The link to CWM on that page is dead. Where else can I get it?
Trickee360 said:
Welp, I've never actually used adb to push anything manually myself, but now is as good as time as any to try it. The link to CWM on that page is dead. Where else can I get it?
Click to expand...
Click to collapse
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
veeman said:
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
got it. thanks much
Will only boot to stock recovery
veeman said:
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
jphilli85 said:
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
Click to expand...
Click to collapse
You can just root again and you will have root access.
I lost root too, so I just opened wugtoolkit and hit root. no unlock needed so no loss of programs either.
jphilli85 said:
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
Click to expand...
Click to collapse
Any news about this. I stay in the same problem.
Here's my experience:
Stock ROM, rooted, custom kernel.
Got the notification for the 4.1.2 OTA update, so I did a nandroid backup in TWRP. Then I flashed back to the stock recovery and boot.img.
I was thinking that I might lose root, based on other's problems. Looked into installing Root Keeper by Voodoo. In the description it said the same feature is built into SuperSU. Problem was it's built into the paid version, which I didn't have (discovered this after it was too late). Installed 4.1.2 OTA. I lost root. My bootloader was updated to 3.41. I also was not able to flash a recovery. Fastboot flash would not work, Wugs toolkit didn't work. Tried several methods. After reading several threads that have been pretty active for the last few days, here's what finally worked for me. Found it in another thread, which I can't find at the moment.
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the JRO03D factory image
fastboot flash recovery TWRP img
fastboot reboot-bootloader
TWRP recovery started up :laugh:.
flashed SuperSU to re-root, it was sucessful.
updated busybox binaries.
installed OTA rootkeeper, so hopefully this won't happen again.
I'm not really sure I want to try flashing the 3.41 bootloader.
What a pain in the A.
Now it's time to flash faux kernel.
jayyo said:
Here's my experience:
Stock ROM, rooted, custom kernel.
Got the notification for the 4.1.2 OTA update, so I did a nandroid backup in TWRP. Then I flashed back to the stock recovery and boot.img.
I was thinking that I might lose root, based on other's problems. Looked into installing Root Keeper by Voodoo. In the description it said the same feature is built into SuperSU. Problem was it's built into the paid version, which I didn't have (discovered this after it was too late). Installed 4.1.2 OTA. I lost root. My bootloader was updated to 3.41. I also was not able to flash a recovery. Fastboot flash would not work, Wugs toolkit didn't work. Tried several methods. After reading several threads that have been pretty active for the last few days, here's what finally worked for me. Found it in another thread, which I can't find at the moment.
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the JRO03D factory image
fastboot flash recovery TWRP img
fastboot reboot-bootloader
TWRP recovery started up :laugh:.
flashed SuperSU to re-root, it was sucessful.
updated busybox binaries.
installed OTA rootkeeper, so hopefully this won't happen again.
I'm not really sure I want to try flashing the 3.41 bootloader.
What a pain in the A.
Now it's time to flash faux kernel.
Click to expand...
Click to collapse
So, the bootloader 3.41 is the problem?
Southmad said:
So, the bootloader 3.41 is the problem?
Click to expand...
Click to collapse
For some people, yes. No idea why.
veeman said:
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
Would that image work ok for Galaxy s3? Or there is no difference at all, just matter the 4.1.2 android version?
Cuz i updated my device throught Kies (cuzz from the device itself it didnt allow, stating that the image has been modifyied :angel: ) and after that even with the persistent mode on Super SU the root is gone
Hi,
I have a rooted Nexus 4 with android 5.0 lollipop build LRX21T.
I have TWRP recovery installed version : v2.8.0.1
The device id rooted via placing the zip file in the device and flashng it via TWRP recovery.
But i am not able to update to android 5.0.1 via google OTA update.
Everytime i try to install the 5.0.1 OTA it goes to TWRP recovery.
I found that the downloaded OTA update file is placed in /cache folder , so i try to update it manually but failed as it shows some update partition error.
"E: error executing updater binary in zip '/cache/e93b********************.signed-occam-LRX22c-from-LRX21T.e93b****.zip"
update partition details.....
I think i am getting this error because the device is rooted.
Can someone guide me how to update my device..and if this because of the rooted device how to unroot without going back to stock.
Thanks in advance....
You can't flash the ota in twrp. You have to be 100% stock recovery, system, kernel, and radio. Flash the stock recovery with fastboot then try the ota.
Sent from my Nexus 9 using XDA Free mobile app
I flashed the stock recovery the OTA update continued in the stock recovery , then it showed a error....and i had to restart the phone ...now the ota update has disappeared with the phone still in android 5.0 ...Can you tell me how to get the OTA update back...?
1)Does the error came because the phone is still rooted ?
2) If so how do i remove the root with returning stock .?
3) also if i root and return to stock will it wipe my phone apps and their data...
Now i got the OTA update downloaded manually on my laptop and and booted into stock recovery to try to sideload the zip it gave me the error
"package expects build fingerprint of google /occam/mako:5.0/LRX21T or google /occam/mako:5.0/LRX22C user release keys; this device has google/occam/mako:4.4/KRT160 user release keys .....
This is weird as i am running android android lollipop 5.0 LRX21T and not android kitkat....
Did you flash mods while rooted?
Sent from my Nexus 4
arkangel72 said:
Did you flash mods while rooted?
Sent from my Nexus 4
Click to expand...
Click to collapse
Tried both...with and without Root....same error....
Try flashing factory image.
The OTA will flash only on the stock recovery it won't work in any modified/custom recovery. So flash stock recovery first then you are good to go.
Edit: You may also try flashing the factory image, u may lose your data while doing that
Head to https://developers.google.com/android/nexus/images and download the latest image, flashing procedure is explained there too.Its not compulsory to lock bootloader afterwards BTW, its personal preference.
sachin.parmar100 said:
The OTA will flash only on the stock recovery it won't work in any modified/custom recovery. So flash stock recovery first then you are good to go.
Edit: You may also try flashing the factory image, u may lose your data while doing that
Head to https://developers.google.com/android/nexus/images and download the latest image, flashing procedure is explained there too.Its not compulsory to lock bootloader afterwards BTW, its personal preference.
Click to expand...
Click to collapse
Actually i dont want to flash stock as i will lose all the data in the process....
Any other way....?
If there is no other way could you please suggest any tool kit which will backup all data including sms ,contact, call logs and all app data and /data/media folder. in one go ...?
use advanced backup from twrp backup menu and select data only to create a nandroid backup of data only
you can also use titanium backup to backup to choose what to backup and restore it afterwards but it will need root again.
sync your contacts with google server
Flah rom in fastboot
Download factory image, flash system, bootloader and recovery manually. You won't lose your data.
You need stock recovery to proceed flashing the OTA, custom recovery won't flash the OTA, i don't think being rooted is the issue Just flash the stock recovery to solve the problem.
sachin.parmar100 said:
You need stock recovery to proceed flashing the OTA, custom recovery won't flash the OTA, i don't think being rooted is the issue Just flash the stock recovery to solve the problem.
Click to expand...
Click to collapse
Rooted IS an issue. You can't be rooted and apply the OTA file, it will fail every time. As a previous poster has said, the phone MUST have stock bootloader, recovery and be not rooted for the stock OTA's to apply. If they see any modification during the process, they abort. It's been discussed many times.
Yaz75 said:
Rooted IS an issue. You can't be rooted and apply the OTA file, it will fail every time. As a previous poster has said, the phone MUST have stock bootloader, recovery and be not rooted for the stock OTA's to apply. If they see any modification during the process, they abort. It's been discussed many times.
Click to expand...
Click to collapse
thanks for pointing out i was so wrong
Hi! I have my phone rooted and it has TWRP installed. Recently, I received the 5.1.1 OTA update, but when I hit the install button, it boots to the recovery and does nothing. How do I install the update using my current recovery?
Thanks!
__ByTeS__ said:
Hi! I have my phone rooted and it has TWRP installed. Recently, I received the 5.1.1 OTA update, but when I hit the install button, it boots to the recovery and does nothing. How do I install the update using my current recovery?
Thanks!
Click to expand...
Click to collapse
Flash the stock images directly, or flash your phone back to stock/unroot and download the OTA from your phone and it will install.
If you have a custom recovery, the OTA will always fail verification checks I think now on 5.+.
ariesgodofwar said:
Flash the stock images directly, or flash your phone back to stock/unroot and download the OTA from your phone and it will install.
If you have a custom recovery, the OTA will always fail verification checks I think now on 5.+.
Click to expand...
Click to collapse
But if I flash the stock image, I'll have to reinstall the apps, and such. Right?
__ByTeS__ said:
But if I flash the stock image, I'll have to reinstall the apps, and such. Right?
Click to expand...
Click to collapse
Yes, unless you back them up. Otherwise, you will have to redownload and install. You will also lose anything you have stored locally unless you remove the -w from the flashall.bat script (which will prevent the wipe of the partitions).
just download the image from google and extract the system and boot images and flash them in fastboot
Hi. My phone status:
PLK-L01
PLK-L01C432B180
EMUI version 3.1
5.0.2
rooted with TWRP boot recovery.
I'm looking for steps to update to android version 6.0.1 without losing all of my data, and keeping phone rooted and same recovery.
Is this something which is possible?
The only steps I have found is to how to replace stock recovery to update OTA.
I expect I would then need to root phone again afterwards.
Is this the recommended way of updating, or can I manually perform the update safely, and are there tried and tested instructions for this?
Many Thanks in advance for any responses.
M.
unroot before updating and flash stock recovery
hoodoo_mc said:
Hi. My phone status:
PLK-L01
PLK-L01C432B180
EMUI version 3.1
5.0.2
rooted with TWRP boot recovery.
I'm looking for steps to update to android version 6.0.1 without losing all of my data, and keeping phone rooted and same recovery.
Is this something which is possible?
The only steps I have found is to how to replace stock recovery to update OTA.
I expect I would then need to root phone again afterwards.
Is this the recommended way of updating, or can I manually perform the update safely, and are there tried and tested instructions for this?
Many Thanks in advance for any responses.
M.
Click to expand...
Click to collapse
Completely unroot from settings menu in SuperSU app, Download latest firmware that is B380, use Huawei update extractor to extract stock recovery from update.app which you will get by extracting firmware, flash it in bootloader mode.
Copy update.app to dload folder in SD card, turn off your phone. Press and hold power, Vol up, vol down until a reboot. Let go of power after booting but keep other two pressed for five, six sec more.
muradulislam said:
Completely unroot from settings menu in SuperSU app, Download latest firmware that is B380, use Huawei update extractor to extract stock recovery from update.app which you will get by extracting firmware, flash it in bootloader mode.
Copy update.app to dload folder in SD card, turn off your phone. Press and hold power, Vol up, vol down until a reboot. Let go of power after booting but keep other two pressed for five, six sec more.
Click to expand...
Click to collapse
Hi. Many thanks for the prompt response.
That all seems straight forward, I just have one step I'd like you to confirm, if you would, and an additional question:
"flash it in bootloader mode"
So, after unrooting the phone, I will still have TWRP recovery available to use?
And, once I am at latest 6 firmware, do I need to use something like SRK Tools to reroot, or will SuperSU app still be installed and able to perform the re-root?
Thanks,
M.
hoodoo_mc said:
Hi. Many thanks for the prompt response.
That all seems straight forward, I just have one step I'd like you to confirm, if you would, and an additional question:
"flash it in bootloader mode"
So, after unrooting the phone, I will still have TWRP recovery available to use?
And, once I am at latest 6 firmware, do I need to use something like SRK Tools to reroot, or will SuperSU app still be installed and able to perform the re-root?
Thanks,
M.
Click to expand...
Click to collapse
After the unroot, the twrp recovery will still be there. You need to replace it with stock recovery by flashing it in bootloader mode, only then you can upgrade.
After upgrading to 6.0 you need to flash twrp again (in bootloader mode) and then flash SuperSU 2.62 (in twrp, for a root). Don't flash any other version.
muradulislam said:
After the unroot, the twrp recovery will still be there. You need to replace it with stock recovery by flashing it in bootloader mode, only then you can upgrade.
After upgrading to 6.0 you need to flash twrp again (in bootloader mode) and then flash SuperSU 2.62 (in twrp, for a root). Don't flash any other version.
Click to expand...
Click to collapse
Many Thanks.
I think I know what I'm doing now.
(famous last words)
hoodoo_mc said:
Many Thanks.
I think I know what I'm doing now.
(famous last words)
Click to expand...
Click to collapse
Don't worry mate, we will all be here
muradulislam said:
Don't worry mate, we will all be here
Click to expand...
Click to collapse
Thanks for the support.
OK, I'm going to leave it for today, and try again tomorrow.
Basically, I go through the steps to flash the stock recovery but can't complete this first step ;
By the way, there are 2 files in the update.app - recovery.img and recovery2.img. Does it matter which one I use?
And does the header file need to be in the same location, or can that be ignored for this step?
Anyhoo, after flashing via command line, and then do the final 'fastboot reboot' the phone just goes into a continuous boot loop until I interrupt by holding down all of the buttons.
Am I doing something wrong here?
I seem to remember I had this same issue when I first got the phone and was trying to get TWRP recovery installed using this method, and can't for the life of me remember how I got through it
@hoodoo_mc
you have to use recovery.img for the system recovery partition! >>> fastboot flash recovery recovery.img
recovery2.img is for the e-recovery partition only!
the header files could be ignored!
But you should flash the boot.img also! >>> fastboot flash boot boot.img >>> because SuperSU has made some changes to your boot partition!!!
to be absolutely save, you should flash the system.img to prevent other problems at last! >>> fastboot flash system system.img
If you use the B380 file to update, you will not loose your data! But it could be clever to backup your personal data and your files with the HUAWEI Backup app!
Good Luck!
non-toxic said:
@hoodoo_mc
you have to use recovery.img for the system recovery partition! >>> fastboot flash recovery recovery.img
recovery2.img is for the e-recovery partition only!
the header files could be ignored!
But you should flash the boot.img also! >>> fastboot flash boot boot.img >>> because SuperSU has made some changes to your boot partition!!!
to be absolutely save, you should flash the system.img to prevent other problems at last! >>> fastboot flash system.img system
If you use the B380 file to update, you will not loose your data! But it could be clever to backup your personal data and your files with the HUAWEI Backup app!
Good Luck!
Click to expand...
Click to collapse
Thank you so much guys @non-toxic and @Mansehra
Using your help I successfully upgraded to B380 and have my phone rooted again with TWRP recovery, and no data lost.
Cheers,
M.
hoodoo_mc said:
Thank you so much guys @non-toxic and @Mansehra
Using your help I successfully upgraded to B380 and have my phone rooted again with TWRP recovery, and no data lost.
Cheers,
M.
Click to expand...
Click to collapse
Enjoy your phone buddy... Don't forget to get greenify and titanium backup.
I love these two apps.
;
muradulislam said:
Don't forget to get greenify and titanium backup.
Click to expand...
Click to collapse
where is it for if you can use TWRP and HUAWEI Update together??
BTW: Had compared greenify with Lollipop and MM and for me greenify makes no sense!
Power consumption was the same as without! (on my device = 6%/24h! -GSM2 -no WLAN -no GPS -noBT -no DATA sync)
non-toxic said:
;
where is it for if you can use TWRP and HUAWEI Update together??
BTW: Had compared greenify with Lollipop and MM and for me greenify makes no sense!
Power consumption was the same as without! (6%/24h!)
Click to expand...
Click to collapse
For me it does make sense as I don't want Facebook and similar apps to run in the background nagging me with updates. I want them to run and update myself when I have time and tap on them. For battery, it does save some juice for me.
What's the comment about TWRP and Huawei update.
I am not sure what you mean by it.
ah, ok i see... it is neccesarry for YOU!
BtT. and thx bro:good:
Hey guys, i sucessfull flashed a patched boot.img to my phone. After that i got Root, everythings worked fine. But when I used to deleted System apps with Titanium Backup,I need to restart my Phone, after that it stucks at Bootloop and wont finish.
So I decide to flash my stock rom again, using Odin but it wont flash it, I got a error message. After that I tried it with the combinated Rom file that I found online. I thought it's a stock rom. But It wasn't. After flashing it successfully with Odin, I see it wasn't the stock rom. It's useless. So I tried to go into download mode but it wont. It's just black. So I tried go into recovery mode ( stock Recovery because no twrp avaible for now). And Recovery works after that I go into bootloader (download mode). And tried to flash stock rom. But it wont flash. I just get a error message.
I need your advice guys. What should I do now
I'm using 9.0 pie
Oem unlock: ON
USB-DEBUGGING: ON
ROOTED: YES
No Twrp
download a stock firmware from sammobile, with the version 9.0 pie, and try to flash it with odin,
i think that you couldn't use odin because you tried to flash and older version of android,
also try to use in case of not working the samsung emergency backup softawre (smart switch)
tell me if you fail
also copy the odin error fail message
Brx_denniz said:
Hey guys, i sucessfull flashed a patched boot.img to my phone. After that i got Root, everythings worked fine. But when I used to deleted System apps with Titanium Backup,I need to restart my Phone, after that it stucks at Bootloop and wont finish.
So I decide to flash my stock rom again, using Odin but it wont flash it, I got a error message. After that I tried it with the combinated Rom file that I found online. I thought it's a stock rom. But It wasn't. After flashing it successfully with Odin, I see it wasn't the stock rom. It's useless. So I tried to go into download mode but it wont. It's just black. So I tried go into recovery mode ( stock Recovery because no twrp avaible for now). And Recovery works after that I go into bootloader (download mode). And tried to flash stock rom. But it wont flash. I just get a error message.
I need your advice guys. What should I do now
I'm using 9.0 pie
Oem unlock: ON
USB-DEBUGGING: ON
ROOTED: YES
No Twrp
Click to expand...
Click to collapse
I'll like to know something.. Was 9.0 stable? Because I'm thinking of upgrading myself but don't know how safe it is.. I mean, any lags or experienced bugs? Thanks.. And also, I apologize concerning your phone situation.
Same problem
Brx_denniz said:
Hey guys, i sucessfull flashed a patched boot.img to my phone. After that i got Root, everythings worked fine. But when I used to deleted System apps with Titanium Backup,I need to restart my Phone, after that it stucks at Bootloop and wont finish.
So I decide to flash my stock rom again, using Odin but it wont flash it, I got a error message. After that I tried it with the combinated Rom file that I found online. I thought it's a stock rom. But It wasn't. After flashing it successfully with Odin, I see it wasn't the stock rom. It's useless. So I tried to go into download mode but it wont. It's just black. So I tried go into recovery mode ( stock Recovery because no twrp avaible for now). And Recovery works after that I go into bootloader (download mode). And tried to flash stock rom. But it wont flash. I just get a error message.
I need your advice guys. What should I do now
I'm using 9.0 pie
Oem unlock: ON
USB-DEBUGGING: ON
ROOTED: YES
No Twrp
Click to expand...
Click to collapse
Any solution to test problem?
jeffersonveloso_06 said:
Any solution to test problem?
Click to expand...
Click to collapse
No, to delete the system apps you must fully root using TWRP and flashed magisk. Not by using patched boot image using magisk. Deleting system apps will fail by using patched magisk method. To fully root the device you must flash magisk using TWRP and then, you can delete or modify any system apps
HELLPP
Hi EVERYONE
I don't know how to create a Post to ask this question, so unfortunately, I am ''rudely'' interupting this conversation to hopefully reach out to the person who can help me!
I recently acquired a Samsung SM-A920F (fantastic phone, I love it , I definitely recommend Android).
Now unfortunately, no matter what I do, what method I use, what keys I press, what drivers I download, what program I use; it WILL NOT give me root access... I've had a few ''bootloops'' during the process, but nothing I couldn't recover from...
I don't know why I can't root it! PLEASE PLEASE, FOR THE LOVE OF GOD, HELP ME.
How do you unlock bootloader
Brx_denniz said:
Hey guys, i sucessfull flashed a patched boot.img to my phone. After that i got Root, everythings worked fine. But when I used to deleted System apps with Titanium Backup,I need to restart my Phone, after that it stucks at Bootloop and wont finish.
So I decide to flash my stock rom again, using Odin but it wont flash it, I got a error message. After that I tried it with the combinated Rom file that I found online. I thought it's a stock rom. But It wasn't. After flashing it successfully with Odin, I see it wasn't the stock rom. It's useless. So I tried to go into download mode but it wont. It's just black. So I tried go into recovery mode ( stock Recovery because no twrp avaible for now). And Recovery works after that I go into bootloader (download mode). And tried to flash stock rom. But it wont flash. I just get a error message.
I need your advice guys. What should I do now
I'm using 9.0 pie
Oem unlock: ON
USB-DEBUGGING: ON
ROOTED: YES
No Twrp
Click to expand...
Click to collapse
hi ... first I like to how you do unlock the bootloader for the A92018 SM-A920F because i had unlock the OEM but bootloader still locked and the option to unlocked it didnt appeaer in the download mode in my phone . thank U for help .. now for your phone you have to download the official software from this site and flash your phone with odin and your done thank U