Can get my nexus 7 to take the 4.1.2. os update? I loaded Clock Work Recovery and can see the error message? See attached .txt. file.
Can anyone help resolve why, I've tried about 50 different ways and no cigar:crying:
stevey00 said:
Can get my nexus 7 to take the 4.1.2. os update? I loaded Clock Work Recovery and can see the error message? See attached .txt. file.
Can anyone help resolve why, I've tried about 50 different ways and no cigar:crying:
Click to expand...
Click to collapse
Patching BrowserProviderProxy.odex failed. Get the bootloader, system.img, boot.img from the 4.2 factory image and flash those via fastboot. Afterwards, boot clockwork recovery and wipe cache and dalvik.
stevey00 said:
Can get my nexus 7 to take the 4.1.2. os update? I loaded Clock Work Recovery and can see the error message? See attached .txt. file.
Can anyone help resolve why, I've tried about 50 different ways and no cigar:crying:
Click to expand...
Click to collapse
You probably added the stock Ics browser for flash or something. Part of that procedure is to rename the file BrowserProviderProxy.odex to a backup name like BrowserProviderProxy.odex1. All you need to do is rename it back to the proper name. You can use something like root explorer or command line.
---------- Post added at 05:43 PM ---------- Previous post was at 05:36 PM ----------
Here is the original thread http://forum.xda-developers.com/showthread.php?t=1780746
UncleCemka said:
You probably added the stock Ics browser for flash or something. Part of that procedure is to rename the file BrowserProviderProxy.odex to a backup name like BrowserProviderProxy.odex1. All you need to do is rename it back to the proper name. You can use something like root explorer or command line.
---------- Post added at 05:43 PM ---------- Previous post was at 05:36 PM ----------
Here is the original thread http://forum.xda-developers.com/showthread.php?t=1780746
Click to expand...
Click to collapse
I had the same problem with es explorer. So I went to settings - root settings - unchecked each option and then rechecked it. Then i went back to the system - apps folder and renamed it - no problems. Good luck.
Plz anybody tell How to move all apps to sd without doing partition in sd card...??
Sent from my galaxy y using xda premium
Root your phone and install link2sd then select an app an select move to sd (u can move all apps like this) linking is better though as it saves more space
PHONE SLOW CLICK ME?
_____________________________________
"Your signature has been granted superuser permissions"
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
Ur welcome
PHONE SLOW CLICK ME?
_____________________________________
"Your signature has been granted superuser permissions"
There are some apps that are transfarable on their own without any app or root permissions..
Just go to settings>apps>manage apps > select app > move to sd.
.
.
Nd for others u can try
droidsail app2sd .
Or app2sd or any other way
** rooting is new for me,
nd i am a noob to root....**
Hey guys, I just upgraded from my good old galaxy s3 to the htc one m8 (ATT), pretty stoked.
I was having issues with unlocking my bootloader. I installed the Android SDK properly, but no matter what I did, I could never get fastboot to work. I always got an error message saying "adbwinapi.dll is missing". I searched online and came across these two threads:
http://forum.xda-developers.com/showthread.php?t=781386
http://androidforums.com/threads/adbwinapi-dll-not-found-error.609867/
which unfortunately didn't have the right solutions
What finally worked for me was copying adb.exe, adbWinApi.dll , and Fastboot.exe to the folder I downloaded from htcdev "fastboot-win". I then ran cmd prompt from that folder (shift + right click) and entered the command "fastboot oem get_identifier_token" which finally worked.
TLDR: copy adb.exe, adbwinapi.dll and fastboot.exe from SDK install folder to the folder you downloaded from htc dev unlock.
hopefully this will be useful for someone stuck with my same issue.
Was getting the same issue
This totally worked when I encountered this. No sure why the files needed to be moved over but voila. Nice tip.
Thank you very much
it is worked!!!
Worked Thank you
xxkid123 said:
Hey guys, I just upgraded from my good old galaxy s3 to the htc one m8 (ATT), pretty stoked.
I was having issues with unlocking my bootloader. I installed the Android SDK properly, but no matter what I did, I could never get fastboot to work. I always got an error message saying "adbwinapi.dll is missing". I searched online and came across these two threads:
http://forum.xda-developers.com/showthread.php?t=781386
http://androidforums.com/threads/adbwinapi-dll-not-found-error.609867/
which unfortunately didn't have the right solutions
What finally worked for me was copying adb.exe, adbWinApi.dll , and Fastboot.exe to the folder I downloaded from htcdev "fastboot-win". I then ran cmd prompt from that folder (shift + right click) and entered the command "fastboot oem get_identifier_token" which finally worked.
TLDR: copy adb.exe, adbwinapi.dll and fastboot.exe from SDK install folder to the folder you downloaded from htc dev unlock.
hopefully this will be useful for someone stuck with my same issue.
Click to expand...
Click to collapse
Copied .Worked like a charm. Thanks mate.:good:
Fix for adbwinapi.dll is missing
hello
---------- Post added at 07:00 AM ---------- Previous post was at 06:56 AM ----------
thanks for this article
---------- Post added at 07:05 AM ---------- Previous post was at 07:00 AM ----------
thanks
---------- Post added at 07:48 AM ---------- Previous post was at 07:05 AM ----------
thanks for this post
---------- Post added at 08:12 AM ---------- Previous post was at 07:48 AM ----------
i also need help
---------- Post added at 08:33 AM ---------- Previous post was at 08:12 AM ----------
if you want to help then come here.
---------- Post added at 08:49 AM ---------- Previous post was at 08:33 AM ----------
thanks
You should install HTCSync before trying to connect this device to a PC. HTCSync install includes all the necessary files for adb/fastboot, and should remove the missing DLL error.
khushbu1 said:
if you want to help then come here
Click to expand...
Click to collapse
If your issue is directly relevant to the thread subject, feel free to post it here. Otherwise, find a relevant thread, or create a new one.
For that matter, all "help" threads (including this one, actually) should be posted in the Q&A section, not here in "General": https://forum.xda-developers.com/htc-one-m8/help
Also, I would make the constructive suggestion: Please don't post to this forum like it's a twitter feed or SMS. Take a few minutes to compose your forum post, and think about what you are trying to say or ask, before hitting the post/reply button. Posting a few words or a single sentence every 5 minutes is confusing and clutters up the forum.
For example, if you ask for help, post as much information as possible about your device (carrier, region version, OS version), the events that led up to the issue, step-by-step description of what you have done or tried to fix the problem, specific file names of anything you installed, etc. A lot of folks will ask for help by just posting a sentence or two, which is simply the wrong way to go about it. Just forces us to request all the basic information they should have provided to begin with.
I Already Update my Mate 7-TL10 Gold Edtion to Lollipop, it's working very well and smoothly also Smart Screenshot working perfectly (EVERYTHING IS THERE) So.........
(Follow the steps):-
--------------------------------------------------------------------------------------------------------
1. Download Mate 7 RollBack EMUI3.1+Android5.1 to EMUI3.0+Android 4.4 (MT7-TL09 / MT7-TL10).
2. In SD Card Create Folder dload.
3. Copy the file ROM that you downloaded and past in folder dload.
4. Go to Settings ==> Updater ==> Menu ==> Local Update ==>Select file UPDATE.APP
5. Now Download the Stock ROM for your model MT7-TL09 / MT7-TL10 (version B120 or version B123).
6. Copy the file ROM that you downloaded and past in folder dload.
7. Go to Settings ==> Updater ==> Menu ==> Local Update ==>Select file UPDATE.APP ((Note: It will erase all data in Internal Storage))
8. After that download file UPDATE_CUST.app form ((Knuckle snapshot working? It is in this video!)).
9. Copy the file ROM that you downloaded and past in folder dload.
10. Now hold three buttons ((Volume Up + Volume Down + Power Button)).
11. Until vibrate your phone release Power Button and keep Holding Volume Up + Volume Down Until coming EMUI Updater
12. You will see the Update has failed such Restart you phone
13. Now Download the Stock ROM for your model MT7-TL09 / MT7-TL10 (version B130 or version B137).
14. Copy the file ROM that you downloaded and past in folder dload along with UPDATE_CUST.app
15. Now hold three buttons ((Volume Up + Volume Down + Power Button)).
16. Until vibrate your phone release Power Button and keep Holding Volume Up + Volume Down Until coming EMUI Updater
17. EMUI Updated Successfully.
18. Now Download the Stock ROM for your model MT7-TL09 / MT7-TL10 (version B324).
19. Copy the file ROM that you downloaded and past in folder dload.
20. Go to Settings ==> Updater ==> Menu ==> Local Update ==>Select file UPDATE.APP (Note: No need to reset Factory or Wipe Cache)
Now you can ROOT the Mate 7 From ([OFFICIAL] Android lollipop update for TL09/TL10 Post #360)
--------------------------------------------------------------------------------------------------------
There you Go!!!........Enjoy!:highfive:
--------------------------------------------------------------------------------------------------------
Here's my screenshot for Mate 7:-
Pic 1 / Pic 2 / Pic 3 / Pic 4 / Pic 5 / Youtube
--------------------------------------------------------------------------------------------------------
Sorry i dont understand what you. Hve done
---------- Post added at 11:48 PM ---------- Previous post was at 11:43 PM ----------
Can explain whit à simple way
---------- Post added at 11:49 PM ---------- Previous post was at 11:48 PM ----------
Can you explain whit simple way
Try as i might, its seemingly impossible for me to flash UPDATE_CUST.app no matter what base firmware I'm on, despite expecting it to "fail" as in your instructions. It seems to make no difference. Is there no other way to flash the contents of the file? like a TWRP flashable zip?
Step 17. EMUI Updated Successfully. -> For me the update (B123 to B130 with UPDATE_CUST.app present) was super slow, and it fails right at the very end after hanging for a few mins
Prof1977 said:
Sorry i dont understand what you. Hve done
---------- Post added at 11:48 PM ---------- Previous post was at 11:43 PM ----------
Can explain whit à simple way
---------- Post added at 11:49 PM ---------- Previous post was at 11:48 PM ----------
Can you explain whit simple way
Click to expand...
Click to collapse
Such Follow the steps........
If Not....Soon I will insert pic for the steps
Yes do it plz
So I've been trying to root the xt but currently cannot find any links that are up to date, like the TWRP. Is there an up to date guide on how to root the xt?
Seriously..? There are plenty of guides posted. Other than that, just follow the instructions from yueng's twrp post to install madvane's version (or better yet, Google around for better instructions, and just use madvane's file). Then you just flash whatever SU manager you like (I prefer magisk).
I really don't want to sound like a jerk, but.. if you can't handle that, you really shouldn't be rooting your phone. It's a whole new level of PITA that only someone who's extremely tech savvy can reap more benefits than utter, miserable pain.
See post 1:
https://forum.xda-developers.com/huawei-ascend-xt/help/huawei-ascend-xt-h1611-t3507933
There are other instructions elsewhere you can search for, but those should work for rooting the XT.
ordinary_peoples said:
So I've been trying to root the xt but currently cannot find any links that are up to date, like the TWRP. Is there an up to date guide on how to root the xt?
Click to expand...
Click to collapse
divineBliss said:
See post 1:
https://forum.xda-developers.com/huawei-ascend-xt/help/huawei-ascend-xt-h1611-t3507933
There are other instructions elsewhere you can search for, but those should work for rooting the XT.
Click to expand...
Click to collapse
I've tried those and almost every other one I've been able to find...the twrp or recovery file in the first part of that post doesn't exist...and the rest I've found are corrupt or also don't exist...found everything else I need as far as I know except that...
-n0cturne- said:
Seriously..? There are plenty of guides posted. Other than that, just follow the instructions from yueng's twrp post to install madvane's version (or better yet, Google around for better instructions, and just use madvane's file). Then you just flash whatever SU manager you like (I prefer magisk).
I really don't want to sound like a jerk, but.. if you can't handle that, you really shouldn't be rooting your phone. It's a whole new level of PITA that only someone who's extremely tech savvy can reap more benefits than utter, miserable pain.
Click to expand...
Click to collapse
you got links for yuengs post? or even just the link for mads version? I can't find it to save my life haha
but on another note I've rooted a few phones before just the xt is giving me a hard time and finding a twrp that works is proving more difficult than I thought..even searches on here and google...but that's really all I'm missing is that..
ordinary_peoples said:
you got links for yuengs post? or even just the link for mads version? I can't find it to save my life haha
but on another note I've rooted a few phones before just the xt is giving me a hard time and finding a twrp that works is proving more difficult than I thought..even searches on here and google...but that's really all I'm missing is that..
Click to expand...
Click to collapse
I did find one posted by madvayne under the unofficial 5/21/17 thread but everytime I try to flash it it says it cannot open it, it's with adb and fastboot so not sure....
ordinary_peoples said:
I did find one posted by madvayne under the unofficial 5/21/17 thread but everytime I try to flash it it says it cannot open it, it's with adb and fastboot so not sure....
Click to expand...
Click to collapse
So in developer options you have "Enable OEM unlock" enabled and in security have "Unknown Sources" enabled?
yuweng's TWRP is in the zip file and the img file needs to be renamed after unzipping depending on what instructions you are following to boot or flash it:
https://forum.xda-developers.com/showpost.php?p=71184622&postcount=1425
As you said, the original TWRP link in the OP of that thread is broken.
ordinary_peoples said:
I did find one posted by madvayne under the unofficial 5/21/17 thread but everytime I try to flash it it says it cannot open it, it's with adb and fastboot so not sure....
Click to expand...
Click to collapse
---------- Post added at 10:44 PM ---------- Previous post was at 10:25 PM ----------
You can try this too:
https://forum.xda-developers.com/huawei-ascend-xt/how-to/huawei-ascend-xt-h1611-feb27-2017-t3564389
popeye2014 said:
So in developer options you have "Enable OEM unlock" enabled and in security have "Unknown Sources" enabled?
Click to expand...
Click to collapse
yeah both are enabled....adb fastboot all works...tried twrp in with adb and fastboot and says cant open...phones definitely unlocked and obviously bootloader is unlocked.
Post the command you are running and a listing of the directory contents of the directory you were in which you ran the command.
ordinary_peoples said:
yeah both are enabled....adb fastboot all works...tried twrp in with adb and fastboot and says cant open...phones definitely unlocked and obviously bootloader is unlocked.
Click to expand...
Click to collapse
---------- Post added at 11:12 PM ---------- Previous post was at 11:03 PM ----------
And post the full error message screen.
divineBliss said:
Post the command you are running and a listing of the directory contents of the directory you were in which you ran the command.
---------- Post added at 11:12 PM ---------- Previous post was at 11:03 PM ----------
And post the full error message screen.
Click to expand...
Click to collapse
for twrp I've tried
adb shell reboot bootloader...to get into fastboot/rescue
fastboot devices ..to double check its still recognized
fastboot boot TWRP.img
also have tried fastboot flash twrp or flash recovery twrp...
and do you mean where are the commands being ran from?
maybe I'm just putting the wrong things but I swear I've followed it exactly...but even then something is wrong...
The "thanks button" for those who don't know what it is:
https://www.xda-developers.com/introducing-the-thanks-button-on-xda/
Yes, post the dir output from where you are running "fastboot".
ordinary_peoples said:
for twrp I've tried
adb shell reboot bootloader...to get into fastboot/rescue
fastboot devices ..to double check its still recognized
fastboot boot TWRP.img
also have tried fastboot flash twrp or flash recovery twrp...
and do you mean where are the commands being ran from?
maybe I'm just putting the wrong things but I swear I've followed it exactly...but even then something is wrong...
Click to expand...
Click to collapse
fastboot boot TWRP.img comes up as cannot load TWRP.img : no such file or directory
ran from cmd out of windows
even running from cmd out of the adb folder which goes to user not system it says the same thing
but not sure how to get the dir output....noobish lol never had to since all my other roots went fine but this phone
Is TWRP.img in same folder as fastboot.exe file? It seems to not be.
ordinary_peoples said:
fastboot boot TWRP.img comes up as cannot load TWRP.img : no such file or directory
ran from cmd out of windows
even running from cmd out of the adb folder which goes to user not system it says the same thing
but not sure how to get the dir output....noobish lol never had to since all my other roots went fine but this phone
Click to expand...
Click to collapse
divineBliss said:
Is TWRP.img in same folder as fastboot.exe file? It seems to not be.
Click to expand...
Click to collapse
you would think that would be it but nope its in there lol
Type "dir" from the same command line window you typed fastboot command from and post the output. Does TWRP.img show up in the output of the dir command?
ordinary_peoples said:
you would think that would be it but nope its in there lol
Click to expand...
Click to collapse
divineBliss said:
Type "dir" from the same command line window you typed fastboot command from and post the output. Does TWRP.img show up in the output of the dir command?
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Users\baileycancino>adb devices
List of devices attached
A9M0216913010982 device
C:\Users\baileycancino>adb shell reboot bootloader
C:\Users\baileycancino>fastboot devices
1967e115 fastboot
C:\Users\baileycancino>fastboot boot TWRP.img
cannot load 'TWRP.img': No such file or directory
C:\Users\baileycancino>dir
Volume in drive C is OS
Volume Serial Number is AEFB-B6F6
Directory of C:\Users\baileycancino
01/02/2018 10:14 PM <DIR> .
01/02/2018 10:14 PM <DIR> ..
01/02/2018 09:30 PM <DIR> .android
12/30/2017 01:18 AM <DIR> .AndroidStudio3.0
10/21/2017 02:27 AM <DIR> .TianTianVM
01/02/2018 10:35 PM <DIR> Contacts
01/02/2018 10:35 PM <DIR> Desktop
01/02/2018 10:35 PM <DIR> Documents
01/02/2018 10:35 PM <DIR> Downloads
09/22/2017 06:56 PM <DIR> Dropbox
01/02/2018 10:35 PM <DIR> Favorites
01/02/2018 10:35 PM <DIR> Links
01/02/2018 10:35 PM <DIR> Music
12/05/2017 02:32 PM <DIR> OneDrive
01/02/2018 10:35 PM <DIR> Pictures
01/02/2018 10:35 PM <DIR> Saved Games
01/02/2018 10:35 PM <DIR> Searches
01/02/2018 10:35 PM <DIR> Videos
0 File(s) 0 bytes
18 Dir(s) 34,665,484,288 bytes free
C:\Users\baileycancino>
that's running cmd from the folder that has adb and fastboot
not sure if the dir is correct...sorry lol
Nope, fastboot, adb, TWRP.img are not in that dir output. Just find TWRP.img and move it into your directory you listed above, then the fastboot boot TWRP.img command will work .
---------- Post added at 12:20 AM ---------- Previous post was at 12:14 AM ----------
Tell me it's working....
ordinary_peoples said:
yeah both are enabled....adb fastboot all works...tried twrp in with adb and fastboot and says cant open...phones definitely unlocked and obviously bootloader is unlocked.
Click to expand...
Click to collapse
Filenames can be finicky.. rename whatever the unzipped image file is to 'twrp.img', and try again. Again, I'd use yuwengs instructions to install madvane's 5-21-17 version. Just make sure to backup your default recovery first in case something goes wrong - can Google for more complete twrp install directions, it's fairly universal besides the necessity to use an img built for your device.
---------- Post added at 03:16 PM ---------- Previous post was at 02:58 PM ----------
Take it you don't have much command prompt or console experience...
Download and install 'minimal adb and fastboot' and 'universal adb driver' (both can be found on xda or via a Google search). Find the directory you installed 'minimal adb and fastboot' into and copy the twrp img there (now would be a good time for a crc check). Find the shortcut in your start menu for 'minimal adb and fastboot', right click it and run as administrator (or go to properties and enable running as administrator by default). Type 'dir' in the cmd prompt that pops up and confirm that the twrp img is there, then type 'adb devices' to confirm your phone is connected and recognized. Then proceed with the twrp install directions..
What do you need root for? Unlike what many claim, it doesn't make your phone faster - it's for advanced users with specific needs. Getting the phone unlocked and rooted is the easy part, compared to keeping it running smoothly afterward..
I wanted/have root so I could debloat the phone myself and avoid AT&T bloatware crap from running to save RAM/CPU/battery. But yes, just rooting the stock ROM won't improve anything without further action.
OP's problem with being unable to access TWRP.img is that TWRP.img is not in the directory where they ran the fastboot command and its path wasn't specified in the fastboot command. Obviously they have fastboot in the command path since it's not in the dir listing and still ran.
My guess is that they resolved the issue since they stopped posting.
-n0cturne- said:
Filenames can be finicky.. rename whatever the unzipped image file is to 'twrp.img', and try again. Again, I'd use yuwengs instructions to install madvane's 5-21-17 version. Just make sure to backup your default recovery first in case something goes wrong - can Google for more complete twrp install directions, it's fairly universal besides the necessity to use an img built for your device.
---------- Post added at 03:16 PM ---------- Previous post was at 02:58 PM ----------
Take it you don't have much command prompt or console experience...
Download and install 'minimal adb and fastboot' and 'universal adb driver' (both can be found on xda or via a Google search). Find the directory you installed 'minimal adb and fastboot' into and copy the twrp img there (now would be a good time for a crc check). Find the shortcut in your start menu for 'minimal adb and fastboot', right click it and run as administrator (or go to properties and enable running as administrator by default). Type 'dir' in the cmd prompt that pops up and confirm that the twrp img is there, then type 'adb devices' to confirm your phone is connected and recognized. Then proceed with the twrp install directions..
What do you need root for? Unlike what many claim, it doesn't make your phone faster - it's for advanced users with specific needs. Getting the phone unlocked and rooted is the easy part, compared to keeping it running smoothly afterward..
Click to expand...
Click to collapse