Database Info

[Q][A700] Post OTA Update Rooting.

After the recent update (AV043_A700_RV07RC06_PA_CUS1 / AV043_A700_1.029.00_PA_CUS1) which wiped unlocked bootloader and root.....
I've re-unlocked my bootloader. Had a few issues with system hanging, that I didn't have before, but it seems the unlock was a success as outlined in the thread by alx5962.
I'm not prepared to root again using method 2 (which worked just peachy, by the way) until I hear if the existing files/method will work with the new OTA firmware or if I would end up bricked.
Has anyone tried to root since the OTA?

ExtremeRyno said:
After the recent update (AV043_A700_RV07RC06_PA_CUS1 / AV043_A700_1.029.00_PA_CUS1) which wiped unlocked bootloader and root.....
I've re-unlocked my bootloader. Had a few issues with system hanging, that I didn't have before, but it seems the unlock was a success as outlined in the thread by alx5962.
I'm not prepared to root again using method 2 (which worked just peachy, by the way) until I hear if the existing files/method will work with the new OTA firmware or if I would end up bricked.
Has anyone tried to root since the OTA?
Click to expand...
Click to collapse
I was able to root the new update no problem with one of the scripts I downloaded here.
I can post it later after work if you want.
Its whichever one has the ICS Batch script in it that reboots your tablet into fast-boot, it worked.

Itchiee said:
I was able to root the new update no problem with one of the scripts I downloaded here.
I can post it later after work if you want.
Its whichever one has the ICS Batch script in it that reboots your tablet into fast-boot, it worked.
Click to expand...
Click to collapse
Yes, please. Post script if possible.
Please also let us know of any post rooting issues with the new update.

OK, I'll post it up when I get home.
I haven't noticed any issues, but then I haven't been really using it much since I got my Nexus 7 ♥
Edit - OK, I used the attached zip file, extract, right click the flash-ICS-patchedBoot.bat file and run as administrator.
Make sure USB debugging is checked on the tablet before running this file.

After you run the script it will boot the tablet into boot loader mode, it will copy over a few files, then the tablet will reboot with the script saying waiting for device, and will wait and wait... Once your tablet is up again it will have SuperUser installed, then you can install Busy box if you wish, or my fave Root Explorer, and the script will still be waiting for device... You can close it.

Yep, confirmed Method 2 still works. Hooray! Was a pain in the butt not having Button Savior.

Bricked MAXX, Need Help

Hello,
I have been crack flashing for a long time, but when I got the Droid Maxx from verizon I was disappointed at the lack of an unlocked bootloader. I had been running safestrap and was getting the phone ready to return for a refund so I can get the developer edition.
So, it looks like using safestrap I completely wiped the system partition. I can get the phone to boot to flashboot mode or to the safestrap flash screen but that is all.
Using RSDlite I attempted to flash 12.9.0, but get the return message "Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned FAIL. On the phone it said:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT."
So it looks like the issue might be because I am flashing the FXZ file for 12.15.15, but I cannot find the FXZ file for it.
I also tried using House of Moto. Attached is a screen shot of what I get.
So basically it looks like I have no ROM whatsoever. Is there a way out of this so I can return the phone for a refund?
Thanks in advance!

I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?

kclantz said:
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
Click to expand...
Click to collapse
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.

ahjee said:
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
Click to expand...
Click to collapse
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.

rds217 said:
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
Click to expand...
Click to collapse
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing

So I just got back from the Verizon store, I went in to see if they could flash the files I need. They told me they couldn't but gave me a number at motorola to see if they would e-mail the files to me.
Unfortunately that didn't work. Motorola said I could send the phone in for a repair, and that was my only option.
I think I'll take the second option and wait until someone posts the files and flash them with RSD Lite.
I just hope that happens soon, as I am wanting to return the phone and get the developer edition. I have until Saturday to return it and I doubt they will give me a refund with it in this state.

ahjee said:
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
Click to expand...
Click to collapse
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
jcase said:
If you used 1.1 and have a problem with recovery coming back, run the following command:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse

rds217 said:
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
Click to expand...
Click to collapse
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.

kclantz said:
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
Click to expand...
Click to collapse
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk

erishasnobattery said:
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Thanks, that was what I was afraid of. I guess now I will check obsessively for the new FXZ files. Got have some way to spend my day (you know, as opposed to doing my job ).

[Q] Can you ROOT G2 4.4.2 yet? Tried with ioroot

I was wondering if rooting is possible on T-mobile's LG G2 yet on the 4.4.2 KitKat update. I had root privileges before and then when I updated I lost them. I'm not interested in going back to 4.2.2. Then I came across ioroot25, claiming to have added support for 4.4.2 devices. The process was only like 2 steps, the first being to root into recovery. Whenever I try to do that I see the little android dude on my screen for a fraction of a second saying something like installing system update (main point being, the root batch file from ioroot25 isn't getting the device to go into recovery, meaning I CAN'T accept the adb update, which was step two)
ANY SOLUTION?

tayloretl said:
I was wondering if rooting is possible on T-mobile's LG G2 yet on the 4.4.2 KitKat update. I had root privileges before and then when I updated I lost them. I'm not interested in going back to 4.2.2. Then I came across ioroot25, claiming to have added support for 4.4.2 devices. The process was only like 2 steps, the first being to root into recovery. Whenever I try to do that I see the little android dude on my screen for a fraction of a second saying something like installing system update (main point being, the root batch file from ioroot25 isn't getting the device to go into recovery, meaning I CAN'T accept the adb update, which was step two)
ANY SOLUTION?
Click to expand...
Click to collapse
From what I understand, the d801 is the only device that there's this problem with. It doesn't work at the moment but they're working on a fix for it.
Freegee is working for recovery now tho once u get root.

Yeah, really sucks... T-Mobile is a no go atm. No way to boot into stock recovery from 4.4.2
http://forum.xda-developers.com/showthread.php?p=51523100

Hey guys. Any update on the TMO 4.4.2 root or is it still unsolved?

deepac said:
Hey guys. Any update on the TMO 4.4.2 root or is it still unsolved?
Click to expand...
Click to collapse
Very much not resolved yet...It is like candy got handed out to all the kids and we got skipped hahahaha!
---------- Post added at 10:16 PM ---------- Previous post was at 09:49 PM ----------
Well here we go... At least it is a fix of some kind.
http://forum.xda-developers.com/showthread.php?p=51566197

Still waiting :/

chmura said:
Still waiting :/
Click to expand...
Click to collapse
same here. where can we get an update?

buenarc said:
same here. where can we get an update?
Click to expand...
Click to collapse
For all other G2 models, the ioroot method (version 25) works. One prerequisite for that method is access to recovery. We (d801 owners) do not have access to recovery. Attempts to access recovery are being documented in the thread titled "[Please Read] We need help to try and find out how to get into stock 4.4 recovery!" Keep your eye on that thread. If we can get access to recovery, we can use ioroot.

Is it possible to restore bloatware apps?

Hello all.
I rooted my Razr HD after the most recent update (prior to KitKat), so I'm rooted but not unlocked. In my ultimate wisdom, I completely removed (did not merely freeze) some bloatware apps, and only today am learning they are necessary to receive OTA updates.
A factory reset did not restore the apps.
Is it possible to get these bloatware apps back onto my device, or am I pretty much screwed?
If there is a way to restore them, am I screwed anyway due to having previously rooted my device and not having a way to flash a ROM?
My apologies if these questions are dumb; I've been looking for information regarding this for a couple hours and have come up empty so far.

Depending on what version you are currently on, you will need to get the correct FXZ image to fastboot onto your device to return it to stock.
Go here to fix you right up:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
Sent from my Nexus 7 using Tapatalk

Thanks a lot for the advice and the links. The process seems to work ok up until it tries to flash system.img.ext4, at which point it returns the message "Phone returned FAIL.; phone connected". If I remove that one line from the XML file, everything else goes through with no issues, so that seems to be the last thing holding me back.
When I attempt to boot the phone, I receive the following:
No valid PIV block in SP for system
piv validation failed (system)
Fastboot Reason: Boot Failure
Click to expand...
Click to collapse
I will double-check some things and try one more thing before I declare myself stuck again.

Well, I'm glad I ran my double-checks because I would have wasted someone else's time otherwise. After updating to a slightly more recent version of RSD Lite, it got all the way through the reflash process.
My phone boots now. The stock apps are back. I'm letting all my apps update before I attempt the KitKat update, but I'm feeling confident about this. iBolski, I can't thank you enough, and I will love you forever.

A little help..
Thanks for posting this! However I'm running into an issue. I downloaded the latest firmware for my XT907 as well as the latest version on RSD Lite, but when I go to flash the stock image I get an error message that says "unknown fastboot command [getvar]. Any ideas??

Worked for me
Thank you iBolski. The process failed the first time I ran RSD Lite, but it worked the second time. I did not unplug the phone or take it out of Fast Boot mode before trying it the second time. This is very helpful.

froyton said:
Well, I'm glad I ran my double-checks because I would have wasted someone else's time otherwise. After updating to a slightly more recent version of RSD Lite, it got all the way through the reflash process.
My phone boots now. The stock apps are back. I'm letting all my apps update before I attempt the KitKat update, but I'm feeling confident about this. iBolski, I can't thank you enough, and I will love you forever.
Click to expand...
Click to collapse
Eustace2 said:
Thank you iBolski. The process failed the first time I ran RSD Lite, but it worked the second time. I did not unplug the phone or take it out of Fast Boot mode before trying it the second time. This is very helpful.
Click to expand...
Click to collapse
Glad it helped.
---------- Post added at 03:05 PM ---------- Previous post was at 03:00 PM ----------
moodaddy said:
Thanks for posting this! However I'm running into an issue. I downloaded the latest firmware for my XT907 as well as the latest version on RSD Lite, but when I go to flash the stock image I get an error message that says "unknown fastboot command [getvar]. Any ideas??
Click to expand...
Click to collapse
Go back to the following link and get the latest FXZ generator. SamuriHL has been updating it as people have been reporting issues:
http://www.droidrzr.com/index.php/topic/45349-rsd-script-generator/
He updated it yesterday to handle issues for your phone (XT907) and the XT926s as well. See if that fixes your issue. Otherwise, I'm not sure how else to help you.

Droid Mini/Ultra/Maxx SU6-7.7?

Just wondering if anyone has any insight on SU6-7.7 on the Droid line? Whether or not anyone know or hear anything about downgrading to a different SU version? I have the firmware file for the latest SU6-7.7 in case anyone wants it.
https://drive.google.com/open?id=0B7hPMTc_G5VPMFVqZmdMSXJEbjA
It would be nice if Motorola/Lenovo would let us do what we want with a phone they no longer "support".

Thanks, I was looking for this.

RichardCA said:
Thanks, I was looking for this.
Click to expand...
Click to collapse
Sure thing! Let me know if you need anything else!

SalmanJohnson2011 said:
Sure thing! Let me know if you need anything else!
Click to expand...
Click to collapse
OK, since you asked...
On a Motorola phones that still have their stock, factory install intact, they do this clever thing where they cycle between a few different boot logo's, with slightly different colors in the Motorola logo on each boot.
Is there any way to replicate that after you're unlocked?

RichardCA said:
OK, since you asked...
On a Motorola phones that still have their stock, factory install intact, they do this clever thing where they cycle between a few different boot logo's, with slightly different colors in the Motorola logo on each boot.
Is there any way to replicate that after you're unlocked?
Click to expand...
Click to collapse
I believe that you can replace the stock boot logo with an unlocked or locked bootloader. There are a quite a few logos to choose from. When you pick one, you fastboot the image.

Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?

RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
Not sure at the moment. XD I'll reply back to this post or PM you if I do. Thanks again! If you have any more info, please let me know!

RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
When you flashed it to your mini/ultra, where you on SU6-7.7?

SalmanJohnson2011 said:
When you flashed it to your mini/ultra, where you on SU6-7.7?
Click to expand...
Click to collapse
I jumped around a lot. I was playing with marshmallow and lollipop builds and needed to revert back. But I was on the Motorola stock SU4.21 when I flashed it.
I used the process on this page, and got zero errors:
http://forum.xda-developers.com/showthread.php?t=2580060

Help please!!!
Hi everyone im not so good at rooting and fllashing ect ect. iv done it before but always watching youtube videos lol. so i have the droid mini now its a verizon carrier unlocked with android 4.4.4 SU6.7.7 and i would like to install CM so i can customize my phone more also want to get rid of all the bloatware if anyone could please let me knoe if its possible and walk me through this i would really apreciate it!! Thanks in advance :fingers-crossed:

edgar1994 said:
Hi everyone im not so good at rooting and fllashing ect ect. iv done it before but always watching youtube videos lol. so i have the droid mini now its a verizon carrier unlocked with android 4.4.4 SU6.7.7 and i would like to install CM so i can customize my phone more also want to get rid of all the bloatware if anyone could please let me knoe if its possible and walk me through this i would really apreciate it!! Thanks in advance :fingers-crossed:
Click to expand...
Click to collapse
To my knowledge, I don't think you can install custom roms once you install the latest SU update. Beings that you're on SU6-7.7 like me, there's not much you can do until someone comes out with another exploit.

Can I revert to su6-7 after having su6-7.7 update? I could do that after su6-7.3 update though.

ashal said:
Can I revert to su6-7 after having su6-7.7 update? I could do that after su6-7.3 update though.
Click to expand...
Click to collapse
Nope. I've tried and it doesn't work.

SalmanJohnson2011 said:
To my knowledge, I don't think you can install custom roms once you install the latest SU update. Beings that you're on SU6-7.7 like me, there's not much you can do until someone comes out with another exploit.
Click to expand...
Click to collapse
Man this really sucks i hope someone finds a way around this :crying:

edgar1994 said:
Man this really sucks i hope someone finds a way around this :crying:
Click to expand...
Click to collapse
I Agreed dude. I'm with you! I don't know why I keep getting Verizon phones. XD Regardless of what I learned. Haha

SalmanJohnson2011 said:
Nope. I've tried and it doesn't work.
Click to expand...
Click to collapse
Did you try downgrading directly from SU6-7.7 to SU6-7 or you went like SU6-7.7 to 7.3 to 7.2 to SU6-7?
Because for SU6-7.3 I downgraded one by one.

ashal said:
Did you try downgrading directly from SU6-7.7 to SU6-7 or you went like SU6-7.7 to 7.3 to 7.2 to SU6-7?
Because for SU6-7.3 I downgraded one by one.
Click to expand...
Click to collapse
For me, I tried going down one update at a time and it still doesn't work.

it says devoloper phones only
can I flash to my ultra even tho its not a dev phone??

RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
In case this helps anyone: I recently updated to SU6-7.7 from SU4.21 following the guidance in this thread and referenced resources on a XT1030 (Moto Mini). Initially I tried to get cute and only flashed the system image and modem upgrades; was rewarded with a bootloader loop that did not resolve after a full TWRP restore of the previous build. Next take including everything in the zip except boot.img and recovery.img as my device is unlocked and wasn't sure if flashing boot.img would relock the bootloader. Also wanted to maintain a true recovery. Everything worked fine except the WiFi radio which refused to engage (Bluetooth was ok). After a bit of fiddling dropped back to fastboot and flashed boot.img. Device restarted just fine with bootloader remaining unlocked. Whohoo! I should also note the all of the above was a 'dirty flash'. Never erased the userdata partition; all apps came back just fine. Oh yeah, had to reflash SuperSU but that's pretty standard after a system wipe.
Thanks to all the key contributors in this thread and elsewhere in the forum. After some miserable bootloops a couple years back (foolishly accepted VZW OTA) I froze the rom and vowed never to update it. It's nice to be running the terminal release of KitKat for this device which as several stability/usability features baked in along with the usual security updates (now dated but better than 2014!). I had considered CM 12.1 and CM 13 but needed fully hardware functionality that only seems to come with stock builds.

root successful
Davey126 said:
In case this helps anyone: I recently updated to SU6-7.7 from SU4.21 following the guidance in this thread and referenced resources on a XT1030 (Moto Mini). Initially I tried to get cute and only flashed the system image and modem upgrades; was rewarded with a bootloader loop that did not resolve after a full TWRP restore of the previous build. Next take including everything in the zip except boot.img and recovery.img as my device is unlocked and wasn't sure if flashing boot.img would relock the bootloader. Also wanted to maintain a true recovery. Everything worked fine except the WiFi radio which refused to engage (Bluetooth was ok). After a bit of fiddling dropped back to fastboot and flashed boot.img. Device restarted just fine with bootloader remaining unlocked. Whohoo! I should also note the all of the above was a 'dirty flash'. Never erased the userdata partition; all apps came back just fine. Oh yeah, had to reflash SuperSU but that's pretty standard after a system wipe.
Thanks to all the key contributors in this thread and elsewhere in the forum. After some miserable bootloops a couple years back (foolishly accepted VZW OTA) I froze the rom and vowed never to update it. It's nice to be running the terminal release of KitKat for this device which as several stability/usability features baked in along with the usual security updates (now dated but better than 2014!). I had considered CM 12.1 and CM 13 but needed fully hardware functionality that only seems to come with stock builds.
Click to expand...
Click to collapse
Dear i have successfully rooted mine droid mini su6-7.7 with kingo root (not global) v3.4 successfully now i have superuser app in system directory
---------- Post added at 05:42 AM ---------- Previous post was at 05:20 AM ----------
Dear friends i have successfully root mini droid mini su6-7.7 with kingo root v3.4 (not kingo root global). actually i was trying to flash su4.21 over su6-7.7 with RSD lite v6.1 but failed with max get var and after that tried to flash with RSD lite 5.1 again failed without any error. after all of there method i thought of giving a try to kingo root. i downloaded 2 apps kingo root globalv4.9.7 and kingo root v3.4, kingo root global failed to root but.... kingo root v3.4 succeeded to roo. now i have superuser app in system driectory.
but problem is that after removing system app (amazon) when i restarted the phone all the apps came back and superuser app gone. i don't know why so my request to look into this method .
i have tested this method and worked 100% and i have no intention of making fun of me. i have both the apps but don't know how to upload here
Thanks