I was rooting my sons Kindle Fire HD 7 4th Gen on rom 4.5.3
I installed TWRP but wiped the system not thinking. Now all I get is an error message saying:
This package is for "full_ariel" products; this is a "omni_ariel".
E:Error excuting updater binary in zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
Error flashing zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
All I get is white amazon logo when normal boot and TWRP recovery and I have ADB access.
I need a rom that will flash that'll get be back up and running. I even tried some custom ones but get same error.
Is there a way to push stock rom to a folder and reboot and it'll install? If so, what do i rename file and where do i put it?
n2outlaw said:
I was rooting my sons Kindle Fire HD 7 4th Gen on rom 4.5.3
I installed TWRP but wiped the system not thinking. Now all I get is an error message saying:
This package is for "full_ariel" products; this is a "omni_ariel".
E:Error excuting updater binary in zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
Error flashing zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
All I get is white amazon logo when normal boot and TWRP recovery and I have ADB access.
I need a rom that will flash that'll get be back up and running. I even tried some custom ones but get same error.
Is there a way to push stock rom to a folder and reboot and it'll install? If so, what do i rename file and where do i put it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=62349128
n2outlaw said:
Now all I get is an error message saying:
This package is for "full_ariel" products; this is a "omni_ariel".
E:Error excuting updater binary in zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
Error flashing zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
All I get is white amazon logo when normal boot and TWRP recovery and I have ADB access.
I need a rom that will flash that'll get be back up and running. I even tried some custom ones but get same error.
Is there a way to push stock rom to a folder and reboot and it'll install? If so, what do i rename file and where do i put it?
Click to expand...
Click to collapse
I'd try using TWRPs advanced/adb sideload to sideload the 4.5.3 update bin. (Leave it named as bin.) Keep wifi off. If it works, follow one of the root guides from the point of blocking ota updates in 4.5.3, rooting and reinstalling TWRP. If it doesn't work you will have lost TWRP as well as system, so may want to see if someone posts a surefire solution. (If you use windows, you'll have to install or update the adb driver once you enter TWRP's sideload mode.) Good luck!
DoLooper said:
I'd try using TWRPs advanced/adb sideload to sideload the 4.5.3 update bin. (Leave it named as bin.) Keep wifi off. If it works, follow one of the root guides from the point of blocking ota updates in 4.5.3, rooting and reinstalling TWRP. If it doesn't work you will have lost TWRP as well as system, so may want to see if someone posts a surefire solution. (If you use windows, you'll have to install or update the adb driver once you enter TWRP's sideload mode.) Good luck!
Click to expand...
Click to collapse
I did try that and from USB and the same thing.
sd_shadow said:
http://forum.xda-developers.com/showthread.php?p=62349128
Click to expand...
Click to collapse
Thanks!! I used a link inside of the one you gave.
Return to Stock
Related
You want to update your device, you have the OTA zipfile, but you don't know how to use it, you don't want to bricked your device!
That's why I've wrote this guide. I'm not the writer, just an adaptor for xda member
By downloading, flashing these files and use this guide you agree to the following:
Your warranty is now void.
We are NOT responsible for bricked devices, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this guide before use it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, I will laugh at you with all of my teeth.
Support is limited. I do this as a hobby in our free time. I'll do my best to help you if you state your problem in clear English, with as much information as you can (what mods you selected, have you wiped, when exactly does the error occur, what type of phone you have, what carrier, logcat and so on. The more information you offer, easier for me to help you. If you do not ask for support in clear English and with no information what-so-ever we will ignore your issue
Click to expand...
Click to collapse
Before to flash or use fastboot lines command, you need to read quietly this guide. Download all files in one folder (it's easier to find all files in the same folder).
Prerequisite: Your Nexus 7 LTE should be running Android 4.4.2 (KOT49H) or (KVT49L -for Verizon). You will not lose your data using this method
Step 1.
Download the update zip
=> Download link for almost of users => cac1a204d3770a20fdce28f6ed3418fdd36abd5d.signed-razorg-KTU84L-from-KOT49H.cac1a204.zip - md5: 34adc31c6647de18547c405133072381
=> Download link for Verizon users => f0c2187ff1dba772cff3fa7f99f0e6bd38ecb62b.signed-razorg-KTU84L-from-KVT49L.f0c2187f.zip - md5: 663b29478d60babb2f0cbb6fc506f111
Charge your Nexus 7 to at least 60% battery level
Don't forget to enable USB debugging
Don't forget - Backup your tab’s storage,
you can choose to change the file’s name to ‘update.zip’. take care
Be sure to read the instructions and carry on...
Step 2.
Reboot your Nexus 7 LTE and hold the Vol+Down button while it's booting up.
Once you see the fastboot menu and the word Start, press Vol+Up a few times until you see Recovery and then press the Power button to enter recovery
You will see an Android with a red exclamation point.if you have stock recovery
Now press Vol+Up+Power together, and you should see the menu below:
Select the 2nd option called apply update from adb.
Step 3.
Connect your Nexus 7 LTE to your computer with your USB cable.
Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
Place the update.zip package from Google in the Android SDK/platform-tools folder on your computer, but do not unzip it. And open up a command prompt
(cmd in Windows)
(regular shell in Linux and Mac) in the same directory as the zip file.
and type
Code:
adb sideload <the name of the zip file that you've done>.zip
if you have changed the name of the update file to ‘update.zip’, then enter: adb sideload update.zip
You should see the progress bar go up to 100%, like so:
sending: 'sideload' 100%
Click to expand...
Click to collapse
At this point, the device should have started installing the update 4.4.3 OTA :victory:
Step 4.
Reboot - you're done.
Enjoy Android 4.4.3 on your Nexus 7 LTE... we just need to waiting the next release for KK4.4.4
Just in case
Reserved for me
Is this zip compatible with TWRP? I tried flashing the zip but it failed, and I did verify the md5 checksum was correct.
Hizpanick said:
Is this zip compatible with TWRP? I tried flashing the zip but it failed, and I did verify the md5 checksum was correct.
Click to expand...
Click to collapse
I've tried before to install my OTA update and the install is failed. I'm with TWRP also
That's why I'll edit my OP without this process. I have rename the zip file to update.zip
For info I have this result:
Code:
- verifying current system
"/system/bin/debuggerd" has unexpected contents
E:Error executing updater binary in zip '/sdcard/update.zip
Error flashing sip '/sdcard/update.zip
Updating partition details
So if you haven't received the OTA update for 4.4.3, use the adb sideload process.
So I tired with the adb sideload process, and still get the same failure:
"/system/bin/app_process" has unexpected contents.
E: Error executing updater binary in zip "/data/media" (looks like it cuts off at this point)
Since I have TWRP, I used adb sideload by going to Advanced ->Adb sodeload and then swiping to turn on adb sideload. My ADB version is 1.0.31, and the file did copy succesfully.
EDIT: Maybe this doesn't work for me because I'm stock rooted?
Hizpanick said:
So I tired with the adb sideload process, and still get the same failure:
"/system/bin/app_process" has unexpected contents.
E: Error executing updater binary in zip "/data/media" (looks like it cuts off at this point)
Since I have TWRP, I used adb sideload by going to Advanced ->Adb sodeload and then swiping to turn on adb sideload. My ADB version is 1.0.31, and the file did copy succesfully.
EDIT: Maybe this doesn't work for me because I'm stock rooted?
Click to expand...
Click to collapse
I haven't been able to get this to install either. Does root or custom recovery cause the installation to fail?
Sent from my Nexus 7 using Tapatalk
i am getting a status 7 error in /tmp/update.zip
help?
I don't know exactly what is the problem. I've used this process for updating my N7.
After the flash with adb sideload, I am back completely stock, unlocked, rooted but stock recovery, not twrp.
Sent from my N7 LTE from XDA Assist and use TapatalkPro
So I found out why I was getting my particular error and it was because I had Xposed framework installed. I uninstalled that and was able to flash the OTA. However, I lost root, but kept TWRP. So I flashed the updated SuperSU.zip (http://www.androidfilehost.com/?fid=23501681358555830) and I had root back. Re-installed Xposed Framework and now everything is updated and working
So you got the update to flash in twrp?
I uninstalled xposed and it still doesn't work with stock recovery and kernel. Got too much setup to redo it all
Sent from my SCH-I605 using Tapatalk
worked for me.
Okay xda, I'm in a bit of a pickle here. Last night I tried to flash the Siyah kernel, Siyah-s3-v1.9.1.tar using Odin3 v3.09 on my Galaxy S3 which was currently running Android 4.4.2 on Slimkat, with stock everything else. As soon as I tried this I knew it was completely the wrong thing and knew something was going to go wrong. Sure enough, the Siyah splash screen comes on for a couple of seconds, then goes to a black screen and gets stuck there.
At this point all I can do is watch it do a couple of seconds of the splash screen, put it into Download mode, or put it into recovery mode. The first time I tried recovery mode it was the CWM recovery, but I can no longer get this to happen, so I'm stuck with stock recovery. When just plugged in my phone has a red LED, and the battery status screen you get when you start charging a turned off phone comes up.
I read a guide on here about how to fix a failed flashing with Odin (I forget which one), which led me to flashing I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5 I believe, or if that's not it the stock Samsung firmware. So that goes down, and now I get stuck in the stock Samsung bootloader.
I've since tried to flash a .zip of Stock samsung firmware and Cyanogenmod 11 with another phone's SD card (which I no longer have access to), to no avail. At least that hasn't made it any worse.
What should I do? Ideally I want to get my phone back without losing any data, but I feel a reset may be the only way. Eventually, I want to be able to use it on Cyanogenmod11 with the Boeffla kernel.
Thanks!
Do you get any error messages in stock recovery?
ArkThompson said:
Do you get any error messages in stock recovery?
Click to expand...
Click to collapse
When I first get into it it says on the bottom
# MANUAL MODE #
-- Applying Multi-CSC....
Applied the CSC-code : BIU
Successfully applied multu-CSC.
Which I assume is normal. I can't check again, but I did get an error while flashing CM11 which went very similarly to
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
I can't flash .zip files from External Storage at the moment, so other suggestions would be preferred.
I did try converting .zip files into .tar files with 7z but I don't think it was successful.
Obesidia said:
When I first get into it it says on the bottom
# MANUAL MODE #
-- Applying Multi-CSC....
Applied the CSC-code : BIU
Successfully applied multu-CSC.
Which I assume is normal. I can't check again, but I did get an error while flashing CM11 which went very similarly to
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
I can't flash .zip files from External Storage at the moment, so other suggestions would be preferred.
I did try converting .zip files into .tar files with 7z but I don't think it was successful.
Click to expand...
Click to collapse
You're trying to flash custom ROMs in the stock recovery?
ArkThompson said:
You're trying to flash custom ROMs in the stock recovery?
Click to expand...
Click to collapse
Pretty much, yeah, I was trying anything.
What next?
Obesidia said:
Pretty much, yeah, I was trying anything.
What next?
Click to expand...
Click to collapse
You need a custom recovery to flash custom ROMs. You could try flashing one in Odin and then flashing a stock ROM .zip using the recovery.
ArkThompson said:
You need a custom recovery to flash custom ROMs. You could try flashing one in Odin and then flashing a stock ROM .zip using the recovery.
Click to expand...
Click to collapse
I'll try that, but how do I get the .zip file in the right place to install from SD Card?
Obesidia said:
I'll try that, but how do I get the .zip file in the right place to install from SD Card?
Click to expand...
Click to collapse
Use ADB (USB debugging is enabled by default in custom recoveries).
ArkThompson said:
Use ADB (USB debugging is enabled by default in custom recoveries).
Click to expand...
Click to collapse
Okay thanks! I'll try that and get back.
ArkThompson said:
Use ADB (USB debugging is enabled by default in custom recoveries).
Click to expand...
Click to collapse
First time doing this, and I have discovered I have no idea what to do. I'm using
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
as a guide but I don't even know how to open the adb so I can input something into the command line.
Obesidia said:
First time doing this, and I have discovered I have no idea what to do. I'm using
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
as a guide but I don't even know how to open the adb so I can input something into the command line.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2141817
You need to use the adb push command to move the file onto your phone. You just use cmd (type cmd into run and press enter).
ArkThompson said:
http://forum.xda-developers.com/showthread.php?t=2141817
You need to use the adb push command to move the file onto your phone. You just use cmd (type cmd into run and press enter).
Click to expand...
Click to collapse
I tried that but I got an error about the file locations. I think it's because there was a space in the one of the folder names, or at least that's what the command line suggested; it basically said "could not push file to '...\Desktop\Fix'" but the folder is called Fix phone.
I was about to rename the folder and move it to C:\ but I just went to reboot the phone in cwm recovery and it said DOES NOT HAVE ROOT ACCESS. ROOT NOW?
I selected yes and it rebooted as normal and got stuck in the samsung boot animation, so no progress there.
I have a backup in CWM recovery from a couple of months ago, I've just found but obviously doing that would lose all my recent pictures and messages. There isn't really a way to get them back by continuing with this method, is there?
Obesidia said:
I tried that but I got an error about the file locations. I think it's because there was a space in the one of the folder names, or at least that's what the command line suggested; it basically said "could not push file to '...\Desktop\Fix'" but the folder is called Fix phone.
I was about to rename the folder and move it to C:\ but I just went to reboot the phone in cwm recovery and it said DOES NOT HAVE ROOT ACCESS. ROOT NOW?
I selected yes and it rebooted as normal and got stuck in the samsung boot animation, so no progress there.
I have a backup in CWM recovery from a couple of months ago, I've just found but obviously doing that would lose all my recent pictures and messages. There isn't really a way to get them back by continuing with this method, is there?
Click to expand...
Click to collapse
I think you probably lost your messages when you flashed a stock ROM with Odin. Your pictures could be ok, check with adb and pull them if they are still there.
What's going on I had my watch rooted tried, make it back to stock tried it, rooted it and once more tried it I get error 7 everytime
I'm using Ubuntu 14
I can't even sideload
Drivers are all working
But for some reason my Linux machine won't talk to my watch
Can someone help all I need is some codec
I'm sure this has been answered before (infact, I remember answering this exact question).. The stock recovery has ADB broken, so sideloading doesn't work, nor does ADB's shell. The reason you're getting error 7 is because you re-rooted, which changes app_process32, which the update is looking to patch and finds that it doesn't have what it expected there. That said, here's something you can do.
Follow the instructions found somewhere else on these to push the update to /cache/recovery with the watch rooted, I'm not sure if the stock recovery image has an apply /sdcard/update.zip option, but you may be able to get away with pushing the update there.
If you're using the /sdcard/update.zip option, make sure that the update is pushed. If your watch is rooted, you need to unroot it manually by using the image found in the Restore Tools image. (If you're on 5.1 I believe it's 49Ksystem.img but I can't remember.), you'll be doing fastboot flash system <system-image>, then reboot into recovery and hit the apply update.zip option. You're done.
If stock recovery does NOT have an apply update.zip option, you need to search on the G Watch forum here, there is a proceedure that involves pushing the ZIP to /cache/ and writing a recovery script into /cache/recovery. You will need to stage that, but instead of rebooting when the instructions tell you, you need to reboot to the bootloader (adb reboot-bootloader) and preform the step I stated above, reflashing your current version's system image. Once finished, simply reboot and the OS will start updating automatically.
NOW! The Easy Way!
Download the latest LG G Watch Restore Tool package (I think it's 9.8 now), it has been updated with the latest Android Wear image. So all you need to do is start it and run Return to Stock, your watch will be restored to 5.1.1
Hi everyone
I own an Amazon Fire HD 6 and I love it. It's a powerful little machine, but Fire OS 4.5.3 sucks. I've been looking to root it and run a custom ROM on the device since I got it in December 2014, but I never got around to doing it until now. (And there weren't instructions back then.)
I managed to follow instructions posted by @bibikalka that have proven to be very helpful, but I started encountering a problem at step 2).
bibikalka said:
[DONE] 0) get ADB drivers working on your PC, etc:
http://forum.xda-developers.com/fire-hd/general/root-supersu-stable-appstore-custom-t3113311
Tip: A quick way to debug your adb connectivity issues is to use USBDeView : http://www.nirsoft.net/utils/usb_devices_view.html
[DONE] 1) Determine your FireOS version, versions up to 4.5.3 are rootable, 4.5.4 will need to be upgraded to 5.0.2 and then downgraded to 4.5.3 :
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
[DONE, WITH EXCEPTION] 2) Disable OTA updates ( adb shell ; pm block com.amazon.dcp or "Debloater" http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 ),
sideload Kingroot ( http://androidxda.com/download-kingroot-application ),
and let it root. Don't bother with SuperSu at this stage, you'll get it done later.
Click to expand...
Click to collapse
My Fire HD 6 shows up without error in
Code:
adb devices
but when I attempted to sideload Kingroot via
Code:
adb reboot recovery
I got the following error:
Code:
Fire System Recovery
Your Fire doesn't seem to be able to boot. Reseting your device to Factory defaults may help you to fix this issue.
I've since attempted to reset it to Factory defaults, but after trying to boot into recovery afterward, I didn't have any success.
I took it a step further by using the following code to install Kingroot:
Code:
adb install Kingroot_V4.5.0.722.apk
This worked and Kingroot rooted the device without error, but I'm curious to know if this is a big deal since I didn't sideloading the app.
The problem I have now is with sideloading the TWRP image. Without access to recovery, this doesn't appear to be possible. But how can I get my recovery back? I've done some research and apparently this is so messed up that I may need to purchase a factory cable, but I'm curious to know if anyone has any other advice or can help me better understand what went wrong.
Thanks in advance.
Is recovery gone?
pantyman said:
I managed to follow instructions posted by @bibikalka that have proven to be very helpful, but I started encountering a problem at step 2).
My Fire HD 6 shows up without error in . . . adb devices . . . but when I attempted to sideload Kingroot via . . . adb reboot recovery . . . I got the following error:
Fire System Recovery
Your Fire doesn't seem to be able to boot. Reseting your device to Factory defaults may help you to fix this issue.
Click to expand...
Click to collapse
Please do nothing more until @bibikalka or someone else can help you deal with the recovery issue. I'll just point out a few things:
(1) You don't sideload an apk in recovery. (I suspect you know this. For an apk, sideload just means copy/move the apk to the device and install it, with a file manager usually, whereas "adb sideload" from recovery is for bin, zip files.)
I've since attempted to reset it to Factory defaults, but after trying to boot into recovery afterward, I didn't have any success.
Click to expand...
Click to collapse
(2) I assume you got above error again. This is where you need someone else's help.
I took it a step further by using the following code to install Kingroot:
Code:
adb install Kingroot_V4.5.0.722.apk
This worked and Kingroot rooted the device without error, but I'm curious to know if this is a big deal since I didn't sideloading the app.
Click to expand...
Click to collapse
(3) Not a big deal. You got it installed.
The problem I have now is with sideloading the TWRP image. Without access to recovery, this doesn't appear to be possible.
Click to expand...
Click to collapse
(4) You don't adb sideload TWRP. Although there are other methods, we've been using TWRP Manager or Flashify. (Guide). As said, I wouldn't do anything until you figure out the status of recovery.
But how can I get my recovery back? I've done some research and apparently this is so messed up that I may need to purchase a factory cable, but I'm curious to know if anyone has any other advice or can help me better understand what went wrong.
Click to expand...
Click to collapse
Factory (fastboot) cable's don't work with this device; you get into fastboot mode with "adb reboot fastboot," but doing that would be a bad idea right now.
DoLooper said:
Please do nothing more until @bibikalka or someone else can help you deal with the recovery issue. I'll just point out a few things:
(1) You don't sideload an apk in recovery. (I suspect you know this. For an apk, sideload just means copy/move the apk to the device and install it, with a file manager usually, whereas "adb sideload" from recovery is for bin, zip files.)
(2) I assume you got above error again. This is where you need someone else's help.
(3) Not a big deal. You got it installed.
(4) You don't adb sideload TWRP. Although there are other methods, we've been using TWRP Manager or Flashify. (Guide). As said, I wouldn't do anything until you figure out the status of recovery.
Factory (fastboot) cable's don't work with this device; you get into fastboot mode with "adb reboot fastboot," but doing that would be a bad idea right now.
Click to expand...
Click to collapse
Thanks a lot for all of your advice, @DoLooper. I've since actually gotten everything to work by following instructions by @r3pwn on his alternate unbricking method for the Kindle Fire HDX 7" & 8.9"
No issues for me any more! The only thing I have to look for now is a good launcher for this thing. I'm not a big fan of the Vire Launcher.
I'm having this same problem but was unable to fix via the thread linked.
Help please?
So I got the 5.12.10 update for the weekly developer ROM and it installed stock recovery over TWRP and unrooted my phone. The first time I rooted I managed to flash TWRP with stock recovery, but it isn't working this time. I've had a lot of trouble trying to install via ADB drivers. Help please?
PytSkee said:
So I got the 5.12.10 update for the weekly developer ROM and it installed stock recovery over TWRP and unrooted my phone. The first time I rooted I managed to flash TWRP with stock recovery, but it isn't working this time. I've had a lot of trouble trying to install via ADB drivers. Help please?
Click to expand...
Click to collapse
Did you rename TWRP to update.zip and put it on the root of the internal storage before flashing? If yes and it still failed, you'll have to give us a bit more info as to why it failed to flash (any error messages f.e.?). Should be fairly trivial to flash TWRP and SuperSU
elaurens said:
Did you rename TWRP to update.zip and put it on the root of the internal storage before flashing? If yes and it still failed, you'll have to give us a bit more info as to why it failed to flash (any error messages f.e.?). Should be fairly trivial to flash TWRP and SuperSU
Click to expand...
Click to collapse
It wasn't too difficult the first time, but the recovery seems to be using some sort of signature on the ROM's. All it tells me is that "Install update.zip failed! update.zip signature verification failed." It is named update.zip on the root of internal storage.
PytSkee said:
It wasn't too difficult the first time, but the recovery seems to be using some sort of signature on the ROM's. All it tells me is that "Install update.zip failed! update.zip signature verification failed." It is named update.zip on the root of internal storage.
Click to expand...
Click to collapse
Hm, from what I've found on the miui forum, you're not the first one having this issue. These are the "possible" solutions I've gathered from a couple of threads.
1) Flash TWRP using fastboot (rename twrpxxxx.zip to recovery.zip and place it in the same folder as the fastboot executable):
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
2) Update your current ROM (stable/developer) to the latest version if that isn't the case yet and try flashing TWRP again trough the update app
3) Flash TWRP using Flashify
1. download flashify app from playstore and give root acces
2. download img of twrp for redmi 2 note and put in your sd card (I prefer sdext root folder)
3. Open flashify, select "recovery image", find the img file you've downloaded
4. confirm flash, wait until it's done
4) Re-download a copy of TWRP or use a different one (like this one for example)
Let me know how it went..
So I tried Flashify and every time I tried to use it, the app froze right before/after selecting the recovery image. I did, however, manage to make the ADB and fastboot methods work on my desktop PC. I have no idea what I did wrong before, maybe the wrong ADB drivers? Anyway, I did get it working, so thank you
PytSkee said:
So I tried Flashify and every time I tried to use it, the app froze right before/after selecting the recovery image. I did, however, manage to make the ADB and fastboot methods work on my desktop PC. I have no idea what I did wrong before, maybe the wrong ADB drivers? Anyway, I did get it working, so thank you
Click to expand...
Click to collapse
Used windroid to do all these: http://en.miui.com/forum.php?mod=viewthread&tid=167882&extra=pag
Sent from my Redmi Note 2 using Tapatalk
timberwolf60 said:
Used windroid to do all these: http://en.miui.com/forum.php?mod=viewthread&tid=167882&extra=pag
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
I remember seeing this right after I ordered my phone. I had totally forgotten about it by the time I got it though, as it was more than a month later But thanks for reminding me, I already have it installed on my home PC!